[WIP] Explain cli

What changes are proposed in this pull request?
Added explain method in cli.py
How is this patch tested?
Tested Locally
Release Notes
Is this a user-facing change?

[ ] No. You can skip the rest of this section.
[x] Yes. Give a description of this change to be included in the release notes for MLflow users.

(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components

[ ] area/artifacts: Artifact stores and artifact logging
[x] area/build: Build and test infrastructure for MLflow
[ ] area/docs: MLflow documentation pages
[ ] area/examples: Example code
[ ] area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry
[ ] area/models: MLmodel format, model serialization/deserialization, flavors
[ ] area/projects: MLproject format, project running backends
[ ] area/scoring: Local serving, model deployment tools, spark UDFs
[ ] area/server-infra: MLflow server, JavaScript dev server
[ ] area/tracking: Tracking Service, tracking client APIs, autologging

Interface

[ ] area/uiux: Front-end, user experience, JavaScript, plotting
[ ] area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models
[ ] area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry
[ ] area/windows: Windows support

Language

[ ] language/r: R APIs and clients
[ ] language/java: Java APIs and clients
[ ] language/new: Proposals for new client languages

Integrations

[ ] integrations/azure: Azure and Azure ML integrations
[ ] integrations/sagemaker: SageMaker integrations
[ ] integrations/databricks: Databricks integrations

How should the PR be classified in the release notes? Choose one:

[ ] rn/breaking-change - The PR will be mentioned in the "Breaking Changes" section
[ ] rn/none - No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" section
[x] rn/feature - A new user-facing feature worth mentioning in the release notes
[ ] rn/bug-fix - A user-facing bug fix worth mentioning in the release notes
[ ] rn/documentation - A user-facing documentation change worth mentioning in the release notes

Creating an upstream PR - https://github.com/mlflow/mlflow/pull/4359


Updated dependencies

Updated dependencies due to a warning build_runner gave on builds

Sorry, my pull requests are including a lot more changes than intended.  I'm just going to restart with a fresh version of the project.


fix access token on /token end-point

Check and fix access token which is shown on /token end-point. It should include scope claim, see discussion in https://github.com/dmwm/rucio-flux/pull/62

fixed in this commit: https://github.com/dmwm/auth-proxy-server/commit/a7168957a1a4361330f63e0c55a9b1c18c4cca90 The change will appear in 0.2.31 tag


sx1302: upgrade hal to v2.1.0

Why

upgrade to v2.1.0 version of sx1302_hal so we are on the latest
How

upgrade hal to v2.1.0

bring in latest repo from upstream
update dockerfile
update build script
update sx1302 fixes (see #23) for updated repo
remove some unecessary files and code
update config.json files to add com_type and com_path and fine_timestamping

References

Closes: #24
Relates-to: #23

FYI this is a required update for us to be able to support sx1303 chipset.
Will sort the merge conflicts shortly

Looks good other than merge conflicts.


TSConfig - compilerOptions/paths not working for back-end microservices

At the moment, when trying to import from @bundles/ or @root/, TS will throw an error regarding the fact that it can not find the module:
[ERROR] Error: Cannot find module '@bundles/AppBundle/something

When fixing this, we need to keep in mind jest & the built version (i.e. it should work when running node dist/index.js).

@qfl1ck32 if you can find time this week to solve it, it would be great!


[omnibus] Package SysVInit files

What does this PR do?

Reintroduces the SysVInit service files in the debian package of the Agent, that were removed from the package in https://github.com/DataDog/datadog-agent/pull/25885.
Motivation

Fixes the debian package on SysVInit systems. See #27523.
Additional Notes

n/a
Possible Drawbacks / Trade-offs

n/a
Describe how to test/QA your changes

I checked the debian Agent 7 package produced by the CI:
$ root@9d628bb236d5:/mount# dpkg -c datadog-agent_7.56.0~rc.2.git.9.54fd928.pipeline.38985799-1_amd64.deb | grep /etc/init.d
-rw-r--r-- root/root      1026 2024-07-11 20:22 ./etc/init/datadog-agent-sysprobe.conf
-rw-r--r-- root/root       769 2024-07-11 20:22 ./etc/init/datadog-agent-process.conf
-rw-r--r-- root/root       947 2024-07-11 20:22 ./etc/init/datadog-agent-security.conf
-rw-r--r-- root/root       607 2024-07-11 20:22 ./etc/init/datadog-agent.conf
-rw-r--r-- root/root       709 2024-07-11 20:22 ./etc/init/datadog-agent-trace.conf
drwxr-xr-x root/root         0 2024-07-11 20:22 ./etc/init.d/
-rwxr-xr-x root/root      3271 2024-07-11 20:22 ./etc/init.d/datadog-agent-trace
-rwxr-xr-x root/root      3570 2024-07-11 20:22 ./etc/init.d/datadog-agent
-rwxr-xr-x root/root      3266 2024-07-11 20:22 ./etc/init.d/datadog-agent-process
-rwxr-xr-x root/root      3470 2024-07-11 20:22 ./etc/init.d/datadog-agent-security

Upon installing the package, the datadog-agent service is present and can be started with service datadog-agent start.

/merge


Scanner: Optionally skip scanning packages with a concluded license

If we already know the concluded license and have authors, we do not
necessarily need to detect licenses and copyrights anymore.
Signed-off-by: Sebastian Schuberth<EMAIL_ADDRESS>

Closing this unmerged as it might be confusing for the user to not see any detected licenses if there is a concluded license, esp. as the detected licenses at some point have been the basis to determine the concluded license. For the reason the potential performance gain also is rather low, as we only save downloading the stored / known scan results, not doing the (initial) scan itself.

Looks like I had this idea already over a year ago, @blaumeiser-at-bosch 😁 So I'd like to revive the discussion about this, esp. as my argument that "the potential performance gain also is rather low" does not hold if you have lots of inventory data with concluded licenses that would make even the initial scan superfluous.

And if required, we could also only do this if an --skip-concluded (or so) option is passed to the scanner.

Hello @sschuberth , from my point of view, it is a semantically slightly different thing, that is why I would appreciate this. The difference is, that a concluded license implies that some(one|thing) draw a conclusion out of the given data. This is more then drawing the same conclusion out of the same metadata. If you trust the conclusion (which should typically be the case), a scan, even a reused one is sounds to be superfluous.
One point to consider, though, is, if there is no scan, this implies, that the copyright information in the curations with the concluded license are also the right ones. That is a side effect that needs to be considered, from my point of view, but I have no idea, what the consequence is in ORT.

One point to consider, though, is, if there is no scan, this implies, that the copyright information in the curations with the concluded license are also the right ones.

Good point about the missing copyright statements, and also the missing (original) license texts. Without a scan, we get no copyright statements, and only have the generic license texts for known licenses. That could be a problem esp. as ORTs curations do not support curating / add copyright statements.
@fviernau is there a mechanism to "inject" copyright statements without a scan to have ever happened for a specific package?

Good point about the missing copyright statements, and also the missing (original) license texts. Without a scan, we get no copyright statements, and only have the generic license texts for known licenses. That could be a problem esp. as ORTs curations do not support curating / add copyright statements.

Being able to also curate copyrights might make sense. Typically, copyright statements are simply gathered, I saw components were it definitely makes sense to bring copyright statements to a conclusion because the same copyright holder has copyrights in multiple files.

@fviernau is there a mechanism to "inject" copyright statements without a scan to have ever happened for a specific package?

I'm not aware of any such mechanism, @sschuberth.

All, I've revived this PR, so please give it another look.

It would be more important to explain why authors are relevant here than in the code comment further down.

Let me see if I can reword that.

Btw, I don't remember, was it already implemented that authors are associated as copyright holders to declared licenses?

Yes: https://github.com/oss-review-toolkit/ort/pull/3726


[WIP][Feature] Fix dupe comment notifications [OSF-6528]

Purpose
Comments send dupe emails if they are replies or at mentions. This fixes that.

Changes

Fix bug where user object was being checked against a list of string guids.
Add an exclude context variable to stop dupes.

Side effects

Greatly refactored/tidied code (no more 3 nested deep if statements in a for loop)
Added line comments.

Code Notes
Exclude includes the user._id, which means checks for target_user._id and checks if user._id are no longer necessary as they are filtered in the list comprehension.
Ticket
[#OSF-6528]
https://openscience.atlassian.net/browse/OSF-6528

QA Notes
pending

Isn't updating on pushes. Closing and reopening new one.


Cannot pass env vars to k6 tests via k6-operator resource

Brief summary
Hey team, I've been trying to get my k6 tests running via k8s using the k6-operator, but I'm unable to pass any environment variables.
I've looked in detail at the community forum and demo app, and whatever syntax is there does not seem to work for me.
The runnerSpec go file seems to forward the env vars declared within the spec.runner. However, my tests keep failing right when bootstrapping because the vars provided are unavailable.
I've tried several syntax combinations with different indentations, some of them failed to be parsed, and all others do not throw errors, but they don't seem to work either.
k6-operator version or image
make deploy executed from commit sha 151472705d2e35d1c6d9158affed2ab127c305ba (latest in the repo main branch at time of writing)
K6 YAML
apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: k6-distributed
spec:
  parallelism: 4
  script:
    configMap:
      name: my-test-file-dev
      file: my-test-file-dev.js
  runner:
    image: danielfigueiredoc/demo-k6-operator:latest
    env:
      - name: REMOTE_ENV
        value: staging

Other environment details (if applicable)
No response
Steps to reproduce the problem
My docker file is the same as the demo / recommended in k6-operator docs
FROM golang:1.19-alpine as builder
WORKDIR $GOPATH/src/go.k6.io/k6
ADD . .
RUN apk --no-cache add git
RUN CGO_ENABLED=0 go install go.k6.io/xk6/cmd/xk6@latest
# TODO - Want more extensions?! Provide additional `--with ...` lines to the following command:
RUN CGO_ENABLED=0 xk6 build \
    --output /tmp/k6

FROM alpine:3.16
RUN apk add --no-cache ca-certificates \
    && adduser -D -u 12345 -g 12345 k6
COPY --from=builder /tmp/k6 /usr/bin/k6

USER 12345
WORKDIR /home/k6

ENTRYPOINT ["k6"]

It is all very simple; tests run fine without env var assertions. But I added this check when my test bootstraps:
import { fail } from 'k6';
//  ...

const env = __ENV.REMOTE_ENV;

if (!env) {
  fail('no REMOTE_ENV given');
}

When I run kubectl apply -f ./path/to/k6-resource.yml the k6-distributed-initializer job kicks in, I can see the pod being created and immediately failing with:
time="2023-03-22T15:05:41Z" level=error msg="GoError: no REMOTE_ENV given\n\tat go.k6.io/k6/js/modules/k6.(*K6).Fail-fm (native)\n\tat getRemoteEnv (file:///....)

If I swap the script with a sample test requiring no env vars, it works fine.
Everybody seems to provide the env vars as I do, so I think something is up with my setup that I can't figure out yet.
I've also tried to provide env vars via config map but got the same behaviour: there are no failures when running the command, but tests crash as env vars are unavailable. I swapped the runner.env with this:
  envFrom:
  - configMapRef:
      name: trade-mobile-sessions-dev-env-vars

Any help would be much appreciated; I'm not sure what's going on. The only difference between my code and https://github.com/javaducky/demo-k6-operator is that I create my local cluster using minikube, which should not matter theoretically.
Expected behaviour
Be able to provide env vars somehow to the k6 tests being executed.
Actual behaviour
Env vars are not available.

I finally discovered the issue; it appears that when running k6 through the operator + k8s the environment variables are only available at a different time.
The test case I was trying to run had the static options const referencing environment variables such as:
// common file
function getRemoteEnv() {
  const env = __ENV.REMOTE_ENV;

  if (!env) {
    fail('no REMOTE_ENV given');
  }

  return env;
}

// test file imports getRemoteEnv from common file
export const options = {
  vus: 10,
  duration: '10s',
  thresholds: {
    'http_reqs{expected_response:true}': ['rate>10'],
  },
  tags: {
    env: getRemoteEnv(),
  }
};

We used to run k6 via nomad, and this evaluation works fine, but running this way this env var is not yet available. It is after because I can see it when logging within the test case or within the setup function call.
I don't fully understand why yet, but at least the problem is solved!

Hi @danielfigueiredo, thanks for opening the issue! Could you please try the following simple example:
---
apiVersion: k6.io/v1alpha1
kind: K6
metadata:
  name: k6-sample
spec:
  parallelism: 1
  script:
    configMap:
      name: "env-vars"
      file: "env-var.js"
  cleanup: "post"
  runner:
    env:
      - name: REMOTE_ENV
        value: staging

and
import { sleep } from 'k6';

export let options = {
    vus: 10,
    duration: '30s',
    discardResponseBodies: true,
};

// Run with:
// k6 run -e REMOTE_ENV=something env-var.js

const testvar = __ENV.REMOTE_ENV;

export default function () {
    console.log("testvar is", testvar);
    console.log("env var is", __ENV.REMOTE_ENV);
    sleep(1);
}

So without custom images and complex outputs. The above works for me. Would these work in your setup? I think it makes sense to go step by step to figure out at which point the issue appears: right now it's not clear :sweat_smile:

OK, I think its a bit clearer now what happens here. Thanks for the write up!
This script likely fails on k6 archive command here. k6 archive has a different behaviour than k6 run and by default it tries to omit passing env vars in options for security reasons. This is somewhat hinted at in this doc. IMHO, these small differences could be explained better to be less obscure. By the way, there is apparently an open k6 issue to improve this UX: https://github.com/grafana/k6/issues/2744
Now what we can do with this from k6-operator's side:

avoid using such scripts where env var must be evaluated in options :slightly_smiling_face:
add --include-system-env-vars option to k6 archive command in initializer job as default.

even though k6 archive avoids env vars by default as a security measure; in theory, initializer job is a small background job, which is not sending anything anywhere and it is meant to be executed on user's infra. So this change might be acceptable in this case.

we might want to go with the changes proposed in this issue instead: https://github.com/grafana/k6-operator/issues/193

This could use some more thinking and evaluating. Opinions are welcome!

Thank you for all the help
I can try these but this issue should be resolved as it wasn't a real bug. It is behaving as per design

Yes, @danielfigueiredo you're right, it works as expected now. Even if it also could be improved :smile: I'm fine either way: we'll need to get to #193 some day and your issue is already linked there so we'll re-visit this case then. Let's close this one then :+1:
Thank you again for reporting this relatively rare case!

hey you can do something like this if you want to pass the environment variables in the test.js
use the arguments like this :
argument : -e FOR_RPS: {{ .Values.for_rps }}
FOR_RPS can now be used to pass in the options argument
pls dont remove this functionality


Can't disable world gen

With mekanism <IP_ADDRESS> i can't seem to stop ores generating.
Might be something i'm doing wrong so here the config.
http://pastebin.com/Q2j1cbge

Are you sure that Mekanism ores are generating?

just updated to 212. seems to be fine now. sorry for bugging you


Break up past from future values in timeline + change gradient

Show a visual break between today & future values by displaying 2 charts: past and future values;
Change gradient to match a bit closer to the design, automatically places gradient color break point dynamically based on where 0 is on the canvas;
Show transparent gradient for future values;
Also fix catastrophes to only show past values -- otherwise we see tiny interpolated values shortly after 2022.

On desktop the gap is pretty large, but not sure how else to introduce the line break through ChartJS (and doing it via hacky HTML/CSS sounds not ideal/tricky -- it would hide e.g. the chart horizontal lines)... I don't think it's too weird as-is, but it's not ideal.
Mobile:

Desktop:

J'ai fait starter le dataset futur à 2022 direct, comme ça y'a plus de gap. Je trouve que ça fait plus beau.


[Suggestion] update topk limitation in accordance with #7095

Note: This repository is ONLY used to solve issues related to DOCS.
For other issues, please move to other repositories.

Is there anything that's missing or inappropriate in the docs? Please describe.
Describe what the problem is, and where is it. Ex. I think it's better to add/change [...] in [Install Milvus].
Describe your suggestion
A clear and concise description of what you want to change or add.
Additional reference
Provide any other reference docs or websites about your request.

issue fixed, closing the issue


Support ClientAuth with SSL for Kafka

Describe the proposal
It seems that the ClientAuth SSL authentication is not supported in by the Kafka pubsub component.
kafka.go :
 func updateAuthInfo(config *sarama.Config, saslUsername, saslPassword string) {
	config.Net.SASL.Enable = true
	config.Net.SASL.User = saslUsername
	config.Net.SASL.Password = saslPassword
	config.Net.SASL.Mechanism = sarama.SASLTypePlaintext

	config.Net.TLS.Enable = true
	config.Net.TLS.Config = &tls.Config{
		//InsecureSkipVerify: true,
		ClientAuth: 0,
	}
}

We are using SSL with Client Certificate to authenticate a consumer or a producer. The sarama provider seems to support it. Is it possible to consider supporting this auth mecanism?

Yes, that's a very plausible requirement.

Sorry to necro this one, but is there any chance we could get this feature for Kafka pub-sub with SSL authentication?


design document revision

Address revisions to the design document noted after approval of initial draft in pull request https://github.com/capstone-coal/coal/pull/9.

Is this complete

@browtayl ping

Sorry, @lewismc, your previous comment got past me. The issue is currently unresolved. According to Heidi, it looks like we're due to revise this and the other documents on the 17th.

ok doke

@heidiaclayton @xiaomei7 We can refer to the comments in the Design draft pull request when we revise the document. Note that there are also comments to address for the tech review.

Here's info on citing GDAL if we need it:
http://trac.osgeo.org/gdal/wiki/FAQGeneral#HowdoIciteGDAL

closing this issue as changes will be implemented along with the rest of our winter midterm.


Fix internal_function_pointer tests

The problem was the following:

thread '' panicked at era_vm/src/state.rs:360:51:
index out of bounds: the len is 119 but the index is 1343

Throwing an error for this case fixes the tests.
To run these tests:
cargo run --verbose --features lambda_vm --release --bin compiler-tester -- --path tests/solidity/simple/internal_function_pointers

LGTM


(Building for production) Can’t find variable: assert

Using choo to prototype an interface, and I want to build it for production/deployment (supporting IE/Safari is necessary). I followed the suggestions in the readme and landed with this build command:
NODE_ENV=production browserify \
    -t envoy \
    -g yo-yoify \
    -g unassertify \
    -g es2020 \
    -g uglifyify \
    index.js \
    | uglifyjs -c -o dist/bundle.js

When loading a single view, things work fine. But navigating to another view or performing an action based on send() causes an error to appear in the console: ReferenceError: Can't find variable: assert.
Looking at bundle.js, there seem to be two assert statements remaining, even after running unassertify as a global transform:
assert.fail("choo: send() cannot be called from Node")

and
assert.ifError(o,"nanoraf: infinite loop detected")

Admittedly this might not be a choo issue—the one remaining assert is from choo, the other is from nanoraf—and it could very well be unassertify that’s causing this mess up, but I wanted to ping folks here first to see if I was going about it wrong somewhere.

Okay, I think I might have something:
unassertify removes assert() statements following the patterns set out in the Node.js standard assert API. (unassertify lists supported patterns.) Looking at the assert statements that remain in the compiled bundle, neither match any of the assert formats:

assert.fail('choo: send() cannot be called from Node');

Proper/supported format for assert.fail(): assert.fail(actual, expected, message, operator)

assert.ifError(inRenderingTransaction, 'nanoraf: infinite loop detected')

Proper/supported format for assert.ifError(): assert.ifError(value)

This isn’t an issue with unassertify, then, but one with these two assert statements specifically. Rewriting the assert statements to use the proper format should fix this issue.

Update on this: I created two PRs to address this issue.

The one for nanoraf alone fixes the specific issue noted here—swapping out upstream nanoraf for my fork with the fix causes the compiled JS to work properly, without errors in the console. Looking at the compiled JS, the nanoraf call to assert is gone.
The one for choo isn’t necessary to fix the issue noted here—the nanoraf PR alone is enough for that. It is necessary, though, to ensure that the assert statement is removed from compiled JS.

Let me know if either doesn’t make sense in its implementation; I tried to stick to what made sense and made sure the test suites ran successfully.

Closed with https://github.com/yoshuawuyts/choo/pull/173 and https://github.com/yoshuawuyts/nanoraf/pull/2.


SupplementaryItem does not anchor correctly on items with estimatedHeight

I've found that when trying to add a separator as a supplementary item it doesn't update it's position from the original estimated size. If I specify an estimated height of an item as 200 and then the cell lays out as 150 the supplementary item is still anchored to 200. Works fine on iOS13, just breaks on older versions of the OS.
Below is the layout I am using:
let separatorAnchor = NSCollectionLayoutAnchor(edges: .bottom, absoluteOffset: CGPoint(x: 0, y: 1))
let separatorSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1), heightDimension: .absolute(1))
let separator = NSCollectionLayoutSupplementaryItem(layoutSize: separatorSize, elementKind: SeparatorSupplementaryView.kind, containerAnchor: separatorAnchor)

let itemSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1), heightDimension: .estimated(201))
let item = NSCollectionLayoutItem(layoutSize: itemSize, supplementaryItems: [separator])

let groupSize = NSCollectionLayoutSize(widthDimension: .fractionalWidth(1), heightDimension: .fractionalHeight(1))
let group = NSCollectionLayoutGroup.vertical(layoutSize: groupSize, subitems: [item])

let section = NSCollectionLayoutSection(group: group)
section.contentInsets = NSDirectionalEdgeInsets(top: 16, leading: 16, bottom: 16, trailing: 16)

let layout = UICollectionViewCompositionalLayout(section: section)

On a related note, the position of  a boundary supplementary item is not updated accordingly when an estimated item preceding it is resolved into its actual size.

@JobsIsMyHomeboy @andersio Partially fixed by https://github.com/kishikawakatsumi/IBPCollectionViewCompositionalLayout/pull/102. Please open new issue if you find related to this issue.


[v1.6] Pull latest from upstream

What type of PR is this?

/kind enhancement

What does this PR do / why we need it:
Pulls https://github.com/argoproj-labs/argocd-operator/commit/8a80d94ba5b4282f14e7922fb79f1c9c4f9f447f and https://github.com/argoproj-labs/argocd-operator/commit/5501a7963b91468c25fde95668b7ade49ea2f346
Have you updated the necessary documentation?
NA

/lgtm


list arbitrum

when its on mainnet
https://developer.offchainlabs.com/docs/developer_quickstart

https://offchainlabs.com/
https://twitter.com/OffchainLabs
https://github.com/OffchainLabs/arbitrum
#fe8605

https://offchain.medium.com/introducing-arbitrum-one-our-mainet-beta-ed0e9b63b435


Respect FieldNamingPolicy when set on GsonBuilder

Closes #18.
Unfortunately this won't support arbitrary FieldNamingStrategys, but handles all of Gson's built in FieldNamingPolicys.
The code generated by the createFieldNamingMethods() method is taken from the Gson project, so not sure how to attribute this to them; it was derived from their code but is now generated with JavaPoet. I left their license header on FieldNamingTest.java because that only has slight modifications from the code taken from their project.
This will require projects using auto-value-gson to have a runtime dependency on Gson 2.7+ going forward.

Added notes to correct a couple of minor issues I just noticed. I'll fix them when incorporating any feedback people have.

Finally getting around to finishing this off. I haven't pushed my changes yet, but I've rebased on master and also I've addressed the feedback with the exception of a couple of things that I've mentioned in replies to the original review feedback. Once those are fixed up I'll push a new update for review.

Updated with feedback taken into account; let me know if there's anything further that needs addressing.

@rharter just noticed you released a new version a few days ago without merging this PR - any feedback you'd like me to address?

@rharter sorry to bother you - just wondering if you have further thoughts or feedback on this PR? If I have to rebase again I probably wouldn't go through the trouble, so if you think there's value here it'd be best to merge before other changes go in.
If not feel free to close, cheers.

Sorry for letting this drop off my radar, @3flex.  Thanks for the contribution!


Exception thrown when date attribute is empty string

Laravel Version: 5.5.21
PHP Version: 7.1.6
Database Driver & Version: MySQL 5.7

Description:
When we have an Eloquent model with a date field and we specify the attribute under the $dates property, when saving a record with the date field empty it throws the below error. since internally it checks for the field to be not null but in some cases the field can be empty string.
Steps To Reproduce:

Have an eloquent model with a date column called 'start'
set $dates = ['start']; in the model
Run $model->save(['start' => '']);

the PR submitted fixes by checking if the date is not an empty string in addition to the not null check.
[2017-11-15 16:33:26] production.ERROR: Data missing {"exception":"[object] (InvalidArgumentException(code: 0): Data missing at /var/www/xxx/vendor/nesbot/carbon/src/Carbon/Carbon.php:582)
[stacktrace]
#0 /var/www/xxx/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(715): Carbon\\Carbon::createFromFormat('Y-m-d H:i:s', '')
#1 /var/www/xxx/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(738): Illuminate\\Database\\Eloquent\\Model->asDateTime('')
#2 /var/www/xxx/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(1061): Illuminate\\Database\\Eloquent\\Model->fromDateTime('')
#3 /var/www/xxx/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(1023): Illuminate\\Database\\Eloquent\\Model->originalIsEquivalent('start', '')
#4 /var/www/xxx/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/HasAttributes.php(957): Illuminate\\Database\\Eloquent\\Model->getDirty()

Isn't this a wrong usage? How can an empty string be a date?!


Sync 2 Clients with amplify-ios DataStore

Describe the bug
When triggering many saves via 'Amplify.DataStore.save' in a short time (like 5 per second) every entry is written to the remote backend which I can see in the AWS console. But not all changes are getting published by 'Amplify.DataStore.publisher' to sync a second client. Also when the second device which should fetch the changes is in FlightMode only the newest added entry is getting fetched by the 'Amplify.DataStore.publisher'. When triggering 'Amplify.DataStore.query' all entries are there.
To Reproduce
Steps to reproduce the behavior:
Schema used:
enum PostStatus {
  ACTIVE
  INACTIVE
}

type Post @model {
  id: ID!
  title: String!
  rating: Int!
  status: PostStatus!
}

AppDelegate:
import UIKit
import Amplify
import AmplifyPlugins

@UIApplicationMain
class AppDelegate: UIResponder, UIApplicationDelegate {

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
        // Override point for customization after application launch.

//        Amplify.Logging.logLevel = .verbose

        do {
            // AmplifyModels is generated in the previous step
            let apiPlugin = AWSAPIPlugin(modelRegistration: AmplifyModels())
            let dataStorePlugin = AWSDataStorePlugin(modelRegistration: AmplifyModels())
            try Amplify.add(plugin: apiPlugin)
            try Amplify.add(plugin: dataStorePlugin)
            try Amplify.configure()

            print("Amplify configured with DataStore plugin")
        } catch {
            print("Failed to initialize Amplify with \(error)")
            return false
        }
//
        return true
    }

    // MARK: UISceneSession Lifecycle

    func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration {
        // Called when a new scene session is being created.
        // Use this method to select a configuration to create the new scene with.
        return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
    }

    func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>) {
        // Called when the user discards a scene session.
        // If any sessions were discarded while the application was not running, this will be called shortly after application:didFinishLaunchingWithOptions.
        // Use this method to release any resources that were specific to the discarded scenes, as they will not return.
    }

}

ObservableObject used:
 import Foundation
import Combine
import SwiftUI
import Amplify

class PostStore: ObservableObject {

    @Published private(set) var posts: [Post] = []

    var postSubscription: AnyCancellable?

    init() {
        self.getAllPostsFromDataStore()
    }

    deinit {
        self.unsubscribeFromDataStore()
    }

    func getAllPostsFromDataStore() {

        Amplify.DataStore.query(Post.self) { (result) in
            switch result {
            case .success(let posts):
                DispatchQueue.main.async {
                    print("Got \(posts.count) Posts from DataStore initially")
                    self.posts = posts
                }
            case .failure(let error):
                print("Error getting Posts from DataStore: \(error.localizedDescription)")
            }
        }
    }

    func deleteAllPostsFromDataStore() {

        for post in self.posts {
            Amplify.DataStore.delete(post) { (result) in
                switch result {
                case .success():
                    print("Deleted Post from DataStore")
                case .failure(let error):
                    print("Error deleting Post From DataStore: \(error)")
                }
            }
        }
    }

    func addRandomPostToDataStore() {

        let post = Post.getRandomPost()
        self.addPostToArray(post)

        print("Fire: \(post.id)")

        Amplify.DataStore.save(post) {

            switch $0 {
            case .success(let post):
                print("Added post with id: \(post.id)")
            case .failure(let error):
                print("Error adding post with title: \(post.title) Error: \(error.localizedDescription)")
            }
        }
    }

    func deletePostFromDataStore(for indexSet: IndexSet) {

        let postsToDelete = indexSet.map { self.posts[$0] }

        self.posts.remove(atOffsets: indexSet)

        for post in postsToDelete {

            Amplify.DataStore.delete(post) { (result) in
                switch result {
                case .success():
                    print("Deleted Post from DataStore")
                case .failure(let error):
                    print("Error deleting Post From DataStore: \(error)")
                }
            }
        }
    }

    func subscribeToDataStore() {

        postSubscription = Amplify.DataStore.publisher(for: Post.self)
            .sink(receiveCompletion: { (completion) in

                print("Completion!")

                if case .failure(let error) = completion {
                    print("Subscription received Error: \(error.localizedDescription)")
                }

            }, receiveValue: { (changes) in

                //print("Subscription received mutation: \(changes)")
                print("\n\n\n")
                print("\(try! changes.toJSON())")
                print("\n\n\n")
                //                print("Changes!")
                let newPost = try! changes.decodeModel(as: Post.self)

                DispatchQueue.main.async {

                    switch changes.mutationType {
                    case "create":
                        //                        print("Create Subscription")
                        self.addPostToArray(newPost)
                        break
                    case "update":
                        print("Update Subscription")
                        self.updatePostInArray(newPost)
                        break
                    case "delete":
                        print("Delete Subscription")
                        self.deletePostFromArray(newPost)
                        break
                    default:
                        print("AnotherType?")
                        print(changes.mutationType)
                        break
                    }
                }
                print("\n")
            })
    }

    func unsubscribeFromDataStore() {
        postSubscription?.cancel()
    }

    private func addPostToArray(_ post: Post) {

        if !self.posts.contains(post) {
            self.posts.append(post)
        }
    }

    private func deletePostFromArray(_ post: Post) {

        if let index = self.posts.firstIndex(of: post) {
            self.posts.remove(at: index)
        }
    }

    private func updatePostInArray(_ post: Post) {
        print("update?")
    }
}

ContentView used:
import SwiftUI
import Amplify

struct ContentView: View {

    @EnvironmentObject var postStore: PostStore

    var body: some View {

        NavigationView() {

            VStack(spacing: 20) {

                List {
                    Section(header: Text("\(self.postStore.posts.count) Posts")) {
                        ForEach(self.postStore.posts) { post in
                            Text("\(post.title)")
                        }
                        .onDelete(perform: deletePost)
                    }
                }

                Button(action: {
                    self.addRandomPost()
                }) {
                    Text("Press to add Random Post")
                }.padding()
            }
            .navigationBarItems(leading: Button(action: {
                self.postStore.deleteAllPostsFromDataStore()
            }, label: {
                Text("DELETE ALL!")
            })
                ,trailing: Button(action: {
                    self.postStore.getAllPostsFromDataStore()
                }, label: {
                    Text("Refresh")
                }))
                .navigationBarTitle("Posts")

        }.onAppear(perform: subscribeToPostStore)
    }

    private func subscribeToPostStore() {
        self.postStore.subscribeToDataStore()
    }

    private func addRandomPost() {
        self.postStore.addRandomPostToDataStore()
    }

    private func deletePost(at offsets: IndexSet) {
        self.postStore.deletePostFromDataStore(for: offsets)
    }
}

Full CocoaPods versions:
  - Amplify (1.0.3):
    - Amplify/Default (= 1.0.3)
  - Amplify/Default (1.0.3)
  - Amplify/Tools (1.0.3)
  - AmplifyPlugins/AWSAPIPlugin (1.0.3):
    - AppSyncRealTimeClient (~> 1.1.0)
    - AWSAuthCore (~> 2.13.6)
    - AWSCore (~> 2.13.6)
    - AWSPluginsCore (= 1.0.3)
    - ReachabilitySwift (~> 5.0.0)
  - AmplifyPlugins/AWSDataStorePlugin (1.0.3):
    - AWSAuthCore (~> 2.13.6)
    - AWSCore (~> 2.13.6)
    - AWSPluginsCore (= 1.0.3)
    - SQLite.swift (~> 0.12.0)
  - AppSyncRealTimeClient (1.1.6):
    - Starscream (= 3.0.6)
  - AWSAuthCore (2.13.6):
    - AWSCore (= 2.13.6)
  - AWSCognitoIdentityProvider (2.13.6):
    - AWSCognitoIdentityProviderASF (= 1.0.1)
    - AWSCore (= 2.13.6)
  - AWSCognitoIdentityProviderASF (1.0.1)
  - AWSCore (2.13.6)
  - AWSMobileClient (2.13.6):
    - AWSAuthCore (= 2.13.6)
    - AWSCognitoIdentityProvider (= 2.13.6)
  - AWSPluginsCore (1.0.3):
    - Amplify (= 1.0.3)
    - AWSCore (~> 2.13.6)
    - AWSMobileClient (~> 2.13.6)
  - ReachabilitySwift (5.0.0)
  - SQLite.swift (0.12.2):
    - SQLite.swift/standard (= 0.12.2)
  - SQLite.swift/standard (0.12.2)
  - Starscream (3.0.6)

Expected behavior
Every 'save' from Client A should be automatically getting published to Client B by the 'Amplify.DataStore.publisher' but some are missing.
Environment(please complete the following information):

Amplify Framework Version: 1.0.3
Dependency Manager: Cocoapods
Swift Version: 5.0

Device Information (please complete the following information):

Device: Simulator, iPad Mini
iOS Version: iOS 13

Additional context
I can see the WebSocketDidReceiveMessage - log but the 'receiveValue' closure for the publisher is not getting triggered. (is only getting triggered for the last added object but not for all) - this problem doesn't occure always but it is happening quite often when adding entries fast to the DataStore.
Also, when Client B in this example is in Flight Mode and comes back online, it doesn't automatically fetch all entries added to the DataStore. Only the latest entry is fetched all others are not getting published by the 'Amplify.DataStore.publisher'. But when calling 'Amplify.DataStore.query' all entries are getting fetched we are good to go again.
For additional info see this question: https://stackoverflow.com/questions/62639120/aws-amplify-sync-datastore
If you need additional logs let me know.
Best Regards.

Hi @Titzian thanks for the detailed report. The problem code was identified here https://github.com/aws-amplify/amplify-ios/issues/755 and has been fixed in 1.3.1. PR with fix: https://github.com/aws-amplify/amplify-ios/pull/756


Cannot find a Resource with the Name/Key TabViewButtonBackground

In my Xaml Islands Win32 C++ project, I can use controls from UWP project, but can't create any WinUI control.
Any WinUI control will throw  below exceptions:
WinRT originate error - 0x80004005 : 'Cannot find a Resource with the Name/Key TabViewButtonBackground'.
WinRT originate error - 0x802B000A : 'Cannot find a Resource with the Name/Key TabViewScrollButtonBackground [Line: 2570 Position: 35]'.
WinRT originate error - 0x802B000A : 'Cannot find a Resource with the Name/Key TabViewButtonBackground [Line: 33 Position: 10]'.
I found a similar issue: https://github.com/microsoft/microsoft-ui-xaml/issues/2957. I added this to the project:
<PropertyGroup>
   <DisableEmbeddedXbf>true</DisableEmbeddedXbf>
</PropertyGroup>

but the fix did not work.
Version Info

Nuget WinUI: 2.6.1

Microsoft.Windows.CppWinRT 2.0.210707.1

Windows: Win11 Insider  210629

This is the issue that you get when you don't include  in your App.xaml.  This just happens to be the first key that it looks for and doesn't find.  When you add the Winui nuget package you should have gotten a readme opened which instructed you to add the XCR.  that readme is here: https://github.com/microsoft/microsoft-ui-xaml/blob/main/build/NuSpecs/readme.txt. Let us know if that fixes your issue.

I added XamlControlsResources in my App.xaml, it does not work.

I set up my project strictly according to this document： , and at first everything else worked fine, except the user control. Customized user control threw the exception:
Cannot locate resource from 'ms-appx:///MyUserControl.xaml'
I fixed this by removing package.appxmanifest from the UWP project, it worked and MyUserControl was displayed normally,
But when I added a WinUI control, it failed with Cannot find a Resource with the Name/Key

@marb2000 Can you help out here? I'm not sure exactly how the xaml islands project is supposed to be set up


feat: v3 write API and line protocol validation

Closes #25033
Summary
This PR leverages a set of changes introduced experimentally into influxdb3_core to enable the v3 line protocol write API proposed in https://github.com/influxdata/influxdb/issues/24979.
You can see the result in an end-to-end test here, that performs a write to the /api/v3/write API, and then performs a set of queries to verify that the data can be queried, and that the new line protocol is validated for correctness in the written series key.
Detailed Changes
Extend the Catalog to support tables with series key
After https://github.com/influxdata/influxdb/issues/25031, the TableDefinition in the catalog is just a wrapper around the Schema type from the core schema crate. Therefore, a lot of the following functionality stems from the changes made to that type to support the series key in influxdb3_core.

The catalog can support v1/v2 and `v3 tables simultaneously; the difference between them is:

v3 has a schema-level metadata entry that stores the series key members
v3 can contain Key columns, but not Tag columns, while v1/v2 is the inverse

A new order is enforced for columns in a schema. For v1/v2:tags (in lexicographical order) -> fields -> time

For v3:series keys (in user-defined order) -> fields -> time

Split the write path to enable validation and buffering of v1 and v3 writes
The code that parsed and validated incoming writes was previously written as a series of nested function calls. This PR refactored that code by:

Moving the logic into a new module: https://github.com/influxdata/influxdb/pull/25048/files#diff-3417447e57594cd7ce4ed7e2ff407aa97e138e1c338d205f44bb6c382305450c
Using a state machine WriteValidator to store the state that is re-used throughout the process. There are three steps to validation:

Load up the catalog, and create the database if it does not exist (fallible)
Validate the incoming line protocol, and update the relevant table schema (fallible)
Buffer the data (infallible)

Write separate methods on the WriteValidator implementation to do (i.) and (ii.) for v3

Add a new /api/v3/write API
This is the API that leverages the new write path, and can be used to perform writes using the new write protocol. It accepts the same parameters as the existing /api/v3/write_lp API.

Closed, see #25066


[YUNIKORN-496] Add port-forward loop and remove unnecessary test output

The UT failure is not from this PR, created https://issues.apache.org/jira/browse/YUNIKORN-499 to check.

The UT failure is not from this PR, created https://issues.apache.org/jira/browse/YUNIKORN-499 to check.

@yangwwei  The build seems to be failing. Is this due to an existing issue?

@yangwwei The build seems to be failing. Is this due to an existing issue?

Correct. There is a data race tracked in https://issues.apache.org/jira/browse/YUNIKORN-499. I am working on a fix for this. We can retrigger the build once that is fixed. In the meantime, can you help to review the changes in this PR?

hi @ronazhan , https://issues.apache.org/jira/browse/YUNIKORN-499 now has been fixed, could you please update the dependency by using
go get github.com/apache/incubator-yunikorn-core@master

and update this PR? The UT failure should be gone in the next run. Thanks

hi @ronazhan , https://issues.apache.org/jira/browse/YUNIKORN-499 now has been fixed, could you please update the dependency by using
go get github.com/apache/incubator-yunikorn-core@master

and update this PR? The UT failure should be gone in the next run. Thanks

LGTM.
@yangwwei  Could you please help merge this one?

LGTM.
@yangwwei  Could you please help merge this one?


ES module 'import': tsc complains it could not find JavaScript module when using "paths" in jsconfig.js

VSCode Version: 1.40.0
OS Version: Linux (Debian-based, corp-customized)

Steps to Reproduce:

Set jsconfig.js (at project root) fields:

"compilerOptions": {
        "module": "esnext",
        "target": "es2020",
        "strict": true,
        "checkJs": true,
        "noImplicitAny": false, // see, I specifically set it to 'false'
        "moduleResolution": "node",
       "baseUrl": ".",
        "paths": {
            "@src/*": [ "src/*" ],
        }
    }
    "include": [ "src/**/*" ]
}

Create file src/utils/index.js

export class Debug = {}
export class Dom = {}

Create file src/foo/bar.js:

import { Debug, Dom } from '@src/utils'; // ts(7016)

What happened: Error squiggle with message:
module "...[redacted].../src/utils/index"
Could not find a declaration file for module '@src/utils'.
'...[redacted].../src/utils/index.js' implicitly has an 'any' type.ts(7016)

What's expected: no error messages.
However, in step 3, import like this is fine:
import { Debug, Dom } from '../utils'; // ok

Both variations in step 3 are valid JavaScript code (so it's not that I messed up the path), because I can use these imported symbols in bar.js, and IntelliSense can display jsdoc popovers on the symbols.

Does this issue occur when all extensions are disabled?: Yes

Possibly https://github.com/microsoft/TypeScript/issues/26859. Does it work if you add  "module": "commonjs" to your jsconfig?

Thanks for triaging. I made these tweaks:

Simply changing the module value to commonjs in jsconfig: the error message is still there
action in 1 above + replace ES Module's "import"-syntax with CommonJS's "require"-syntax: the error message is there, too


Async tasks are not properly shutting down

Hey my server log said I should tell you about this:
Nag author: 'Luck' of 'LuckPerms' about the following: This plugin is not properly shutting down its async tasks when it is being reloaded.  This may cause conflicts with the newly loaded version of the plugin

Version v3.0.0

They do get shutdown, just not instantly. You can ignore the error, or stop using the reload command. :)


[rt.openssl.org #4077] Add support for EdDSA and Ed25519

Migrated from rt.openssl.org#4077 (status was 'new')
Requestors:

<EMAIL_ADDRESS>
Attachments:

signature.asc

From<EMAIL_ADDRESS>on 2015-10-08 11:34:48:
I believe it would be useful to have OpenSSL support for Ed25519 signing
and Curve25519 key agreement.  I don't see anything on rt.openssl.org
about this (maybe the proper place to open issue is on github these
days?).  Is there interest in this from the OpenSSL team?  There are
several implementations available, but I would coordinate which one to
use with Peter Schwabe who has been working on proving correctness of
Ed25519 implementations.

/Simon

duplicate of something.. . #487


Multiple data races reported by go test -race

Description
I ran unit tests with Go's race detector. Please find the results here.
It reported data races in code around the following structures:

AddrBook
Set
Hare

Actual Behavior
go test -race reports multiple data races
Expected Behavior
No data races detected

@poszu would you mind if I take over this issue?

@poszu would you mind if I take over this issue?

Go ahead, thanks! :)

The tests are already executed with -race and pass. Closing.


chore: Webpack and npm start

LGTM

Coverage remained the same at 69.364% when pulling fed30ee941446f1e92bf07dfd4557c1e10b74282 on DES-505 into 91c4fd397da8457b382eb35ecd05b437b4669f45 on master.

Coverage remained the same at 69.364% when pulling fed30ee941446f1e92bf07dfd4557c1e10b74282 on DES-505 into 91c4fd397da8457b382eb35ecd05b437b4669f45 on master.


Add detection for F2Fs and JFS

Added in the magic bits for the F2Fs and JFS filesystem, so docker info will display the Backing Filesystem: info as expected. Fixes #12324
Signed-off-by: Megan Kostick<EMAIL_ADDRESS>

:cake: PR 12345 :tada:

@thaJeztah Yeah I wasn't sure. Didn't seem like any specific order to me either. So I added them to the 'end', but kept Unsupported last.

@kostickm I think it will be easier to read if they are alphabetical, especially now the list is getting longer. But perhaps better wait for others to have a look, I don't know if there's some thought behind it :smile:

@thaJeztah Okay sounds good! Happy to alphabetize it if no one comes forward :)

Order does not matter and it's ok for them not to be alphabetized

Let's re-order by alpha now that the list is getting appreciably long.. after that LGTM!

Argh..just saw @crosbymichael's comment.. it truly doesn't matter code-wise, just a matter if we like it easily scannable by a human for whether a FS is in the list :)

@estesp it's hex codes, it will never be easy for a human to read ;)

heh, yes.. I meant the filesystem names.. for "human" is this FS in here yet?  but I truly don't care.. if it was 50+ long I might care more, but similar to ordering Go imports by alpha, it's just nice to have for ease of scanning

It's a quick fix, so let me alphabetize them. Minds well start now for when the list grows.

I meant the filesystem names.. for "human" is this FS in here yet?

That was my use-case, but I'm not really attached to it, just a bit OCD

Sorry about the double commit. First time through a git commit --amend

LGTM after CI

LGTM

Yay!  :)


ConsoleLite Accessibility Config

ACs:

[ ] #618
[ ] #619
[ ] #620
[ ] #621

Closing as issues are now broken out


Helm to use same subchart and deploy multiple charts

I have requirement of having multiple dependencies and used the same subcharts for multiple times.
Parent chart has 3 dependencies  and using the same chart path.  I have to deploy the subcharts with below alias name but its not working.
I need to create 3 subscharts with this alias-name used as sub-chart name.
dependencies:
- name: applayer
  repository: file://charts/applayer
  condition: applayer-1.enabled
  alias: applayer-1
- name: applayer
  repository: file://charts/applayer
  condition: applayer-2.enabled
  alias: applayer-2
- name: applayer
  repository: file://charts/applayer
  condition: applayer-3.enabled
  alias: applayer-3

@myvelmurugan Require more info, can you show your cmd output? Thank very much.

I have added the version and it worked. Without adding version it's not creating the subchart with alias name.


[PR][CLOSED] Updated nobody checker

 Issue by geunsik-lim
Tuesday Jul 03, 2018 at 07:03 GMT
Originally opened as https://github.sec.samsung.net/STAR/TAOS-CI/pull/85

This PR is to update th existing nobody checker to give developers
the exact hint data.
Changes proposed in this PR:

UPdated nobody checker.
Added log file

Signed-off-by: Geunsik Lim<EMAIL_ADDRESS>
geunsik-lim included the following code: https://github.sec.samsung.net/STAR/TAOS-CI/pull/85/commits

:octocat: cibot: Thank you for posting issue #109. The person in charge will reply soon.

 Comment by git-bot-sec
Tuesday Jul 03, 2018 at 07:03 GMT

Thank you for submitting PR #85. Your PR has to pass all verificiation processes of cibot before getting a review process from reviewers. We recommend that you read instruction manual in . If you want to monitor the progress status of your PR in detail, visit http://aaci.mooo.com/.


*: support CLUSTERED and NONCLUSTERED syntax

What problem does this PR solve?
Support syntax for https://github.com/pingcap/tidb/issues/22346.
What is changed and how it works?
This PR adds 2 keywords to describe the type of primary key, CLUSTERED and NONCLUSTERED.

CLUSTERED means the primary key columns are used as row handle(row id).
NONCLUSTERED means the primary keys are implemented with unique secondary indexes.

Usages:
create table t (a int, b varchar(255), primary key(b, a) clustered);
create table t (a int primary key nonclustered, b varchar(255));
alter table t add primary key (`a`, `b`) nonclustered;

Check List
Tests

Unit test
Integration test

Code changes

Has exported interfaces change

Side effects
N/A
Related changes
N/A

LGTM

LGTM

It's expected that the integration fails.

It's expected that the integration fails.


Where can I find the "Ideal Processor" in version 3.0.4399?

Add the column to the threads tab?

Add the column to the threads tab?
Thank you! I really appreciate it.


When creating a new customer with only defaultBillingAddress and defaultShippingAddress three addresses are being created

PHP Version
8.1.17
Shopware Version
<IP_ADDRESS>
Expected behaviour
Only two addresses should be created over the api.
Actual behaviour
Three addresses are being created over the api.

How to reproduce
Use this endpint: https://<domain>/api/customer/
and this payload:
{
    "id": "ae20eff41b9245829fa4138149ed5849",
    "type": "customer",
    "groupId": "15b40e2fa3a54c3280772a6a04dbb9a0",
    "defaultPaymentMethodId": "674d61788e7244ebbf3f4065c03ec686",
    "salesChannelId": "5babdc6b5db246399e576b82513a02a5",
    "languageId": "7b339ce69e7c45b984b994b3e825c0bb",
    "lastPaymentMethodId": null,
    "customerNumber": "10000",
    "salutationId": "a6d786c6bb284bc4bdbbad5a3a197cc8",
    "firstName": "Firstname",
    "lastName": "lastname",
    "company": "company",
    "email"<EMAIL_ADDRESS>    "title": null,
    "vatIds": [
        null
    ],
    "affiliateCode": null,
    "campaignCode": null,
    "active": true,
    "doubleOptInRegistration": false,
    "doubleOptInEmailSentDate": null,
    "doubleOptInConfirmDate": null,
    "hash": null,
    "guest": false,
    "firstLogin": null,
    "lastLogin": null,
    "newsletter": false,
    "accountType": "business",
    "remoteAddress": null,
    "requestedGroupId": null,
    "boundSalesChannelId": null,
    "phoneNumber": null,
    "customer_pallet_exchange": "true",
    "defaultBillingAddress": {
        "id": "e198d282088d4dbab67ab27e8cf7c3d5",
        "countryId": "28e80540d17a49719827bc28d4b49d44",
        "salutationId": null,
        "firstName": "Firstname",
        "lastName": "lastname",
        "zipcode": "38442",
        "city": "Wolfsburg",
        "company": "company",
        "street": "Street 7-9",
        "phoneNumber": null
    },
    "defaultShippingAddress": {
        "id": "f6574fb4aa1443288b99127ab7e2f55e",
        "countryId": "28e80540d17a49719827bc28d4b49d44",
        "firstName": "firstname",
        "lastName": "lastname",
        "zipcode": "38442",
        "city": "Wolfsburg",
        "company": "company",
        "street": "Street 7-9"
    },
    "b2bCustomerData": {
        "customerId": "ae20eff41b9245829fa4138149ed5849",
        "isDebtor": true,
        "isSalesRepresentative": false,
        "isInEasyMode": true
    }
}

It creates the shipping address as billing address. Is it possible to avoid this?

Checked on current trunk and could not reproduce your issue. Maybe you have a separate plugin installed?


modify Utils.minutes_in_an_hour method

before:
minutes_in_a_day = num_minutes % (24 * 60)
minutes_in_a_day % 60
after:
minutes_in_a_day % 60
before and after is equivalent functionally.
Thus, remove the meaningless part of before.

@nnoco, the before is not functionally equivalent to the after as you submitted:
before:
minutes_in_a_day = num_minutes % (24 * 60)
minutes_in_a_day % 60
after:
minutes_in_a_day % 60
The after will fail since minutes_in_a_day has not been initialized.
I would however see an after of the following being functionally equivalent:
num_minutes % 60

@rboykin, Oh, you're right, my mistake. It was careless of me.
In this case, If I fixed it, shoud I commit again?

@nnoco, That would be good.  But, I cannot accept a pull request from you until you have a CLA on file.  See prior comments for details.
Please open a new Pull Request with the new commit after you have a CLA on file.


Consider 201 a successful response status code for the paystack adapter

While working on the  plugin extension repository for paystack (https://github.com/adelowo/gbowo-paystack) , i noticed some section of the api (specifically the part that interacts with the plan) return 201 all the time, and it is even considered a success in https://developers.paystack.co/v1.0/docs/errors

This is only applicable to paystack, amplifypay api says 200 only (https://amplifypay.com/developers#errors)

Fixed https://github.com/adelowo/gbowo/commit/8bb0181bb159e9438e2dc16b0c02bf523249c2dc


'get-' implied by command line, but not respected in Get-Command

Steps to reproduce
At the PowerShell command prompt enter 'uptime' or 'childitem'.  Not the command will be processed as if it were prepended by 'Get-'.  However, "get-command uptime" returns "not recognized as a name"

Expected behavior
If the command parser recognizes and executes a command, I expect 'get-command' to show me the information about that command.

Actual behavior
Error message such as this "Get-Command: The term 'uptime' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again." is returned.

Environment data

----                           -----
PSVersion                      7.1.0
PSEdition                      Core
GitCommitId                    7.1.0
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Good find, but it has been reported before: #3987

Good find, but it has been reported before: #3987

I can not reproduce. Need more info.

I can not reproduce. Need more info.

The default verb logic allows you to submit ChildItem in order to invoke Get-ChildItem.
However, the Get-Command cmdlet doesn't know about this shortcut, even though it should:
Get-Command ChildItem # FAILS

Generally, relying on the default-verb logic should be avoided, both for conceptual clarity and for performance reasons, as discussed in the aforementioned duplicate, #3987.

The default verb logic allows you to submit ChildItem in order to invoke Get-ChildItem.
However, the Get-Command cmdlet doesn't know about this shortcut, even though it should:
Get-Command ChildItem # FAILS

Generally, relying on the default-verb logic should be avoided, both for conceptual clarity and for performance reasons, as discussed in the aforementioned duplicate, #3987.

Sorry, clearly need to put more time into my issues search skills.  To me this is a question of completeness.  If 'uptime' (for example) produces output, then 'get-command' (or 'command') should resolve it.  I stumbled across this when I typed 'uptime' in the wrong window and then wondered why that worked.  My first response was to type get-command to figure out what just ran ... down (the shallow) rabbit hole.  I don't work with PS all the time and a lot of that is PS v5.0.  Knowing what is running and from where is rather useful.  Keeping up with all the changes to PS, .NET, C#, ... is for me a bit overwhelming since it isn't where I primarily work.  Anyway, sorry to cause work by posting a known issue.  Thank you for your reply and to everyone for the hard work they puts into these projects

Sorry, clearly need to put more time into my issues search skills.  To me this is a question of completeness.  If 'uptime' (for example) produces output, then 'get-command' (or 'command') should resolve it.  I stumbled across this when I typed 'uptime' in the wrong window and then wondered why that worked.  My first response was to type get-command to figure out what just ran ... down (the shallow) rabbit hole.  I don't work with PS all the time and a lot of that is PS v5.0.  Knowing what is running and from where is rather useful.  Keeping up with all the changes to PS, .NET, C#, ... is for me a bit overwhelming since it isn't where I primarily work.  Anyway, sorry to cause work by posting a known issue.  Thank you for your reply and to everyone for the hard work they puts into these projects


Update docs: explain allow_download setting

This fixes one possible source of confusion seen in #502 and clarifies
when database downloads will be shown and allowed.

This is great, thank you.


Filter app wide based on tenant

I'm trying to filter my results based on the selected tenant/client.  This means that in my layout I've added a  select drop-down that lists all the clients...when it's selected...that applies the filter to the repository.  We're shown with the multi-tenancy demo how to do ApplyFilters but I'm struggling with the best way to get that jquery selection back to the repository.cs code so I can filter on it.
Right now I'm doing it via cookie but that just seems wrong.  Session storage gets challenging going from jquery back to my C# model.  In the past I've used ViewBag/ViewData but then I'd pass that result as a parameter to my model functions but I don't want to change all those methods from the base Serenity code.  I think this is easy but I'm struggling to figure it out so I thought I'd ask for guidance.
If I want to have a "tenant selector" that's part of the navigation that allows you to filter based on that selection, what's the best way?
Thanks,
John

my guess: just stick it to UserDefinition...


Fix PolygonLayer issue with Data Accessors

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

@ibgreen @georgios-uber Do we need port it to release branch? Can anyone specify what's the issue and how to test it in LayerBrowser? When I debug it in LayerBrowser, didn't see any color or width property in paths

@jianhuang01 It's a bug fix. Do you usually port them to release branch?

@georgios-uber yeah, we need port bug fixes to release branch and publish patch release if they are existing there. But I don't know how to test and verify this on our release branch. Need more details.


[test] Add gperftools test

https://github.com/eth-cscs/production/tree/master/easybuild/easyconfigs/g/gperftools

Hello @jgphpc, Thank you for submitting the Pull Request!

In the file cscs-checks/tools/profiling_and_debugging/gperftools.py, following are the PEP8 issues :

Line 60:80: E501 line too long (82 > 79 characters)

Do see the ReFrame Coding Style Guide

install was missing on dom
retest this please

@jenkins-cscs retry all

There is an issue on dom with the installpath.

https://github.com/eth-cscs/production/pull/976

Codecov Report

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

@@            Coverage Diff             @@
##           master     #670      +/-   ##
==========================================
+ Coverage   91.82%   91.84%   +0.02%
==========================================
  Files          77       77
  Lines        9366     9370       +4
==========================================
+ Hits         8600     8606       +6
+ Misses        766      764       -2

Impacted Files
Coverage Δ

unittests/test_pipeline.py
97.36% <0%> (ø)
:arrow_up:

reframe/core/pipeline.py
91.81% <0%> (+0.08%)
:arrow_up:

reframe/core/config.py
84.34% <0%> (+1.73%)
:arrow_up:

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 2b4c2d5...70bb7ad. Read the comment docs.


replaced incorrect info

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/6892

Dear @JohanFreelancer9,
kindly do the copy editor review for this PR.
Dear @e0i, for your information
Thank you

Changes reviewed and approved by the policy owner; hence, merging this PR. Thanks!


Sensor adaption for Deye SUN-12K-SG04LP3-EU 3-phase inverter

Hello,
I have a 3-phase inverter from Deye and tried to modify your scripts to read out what I think are the relevant modbus registers for it. Unfortunately I have absolutely no idea of modbus, I don't know docker and I simply don't get it done :-/.
I have attached how I modified your deye_sensors.py in the docker image:
deye_sensors.py.txt
When running the modified docker image, it still says
2022-12-06 19:28:20,260 - DeyeDaemon - INFO - Reading start
2022-12-06 19:28:20,603 - DeyeDaemon - INFO - Reading completed

and it also produces no error messages but it doesn't publish anything to MQTT.
Hence I think it's also not successfully reading anything.
I have no idea how to debug it further.
Are you able to help maybe ?
Thank you in advance and best regards.

And maybe to add,  because I think this is part of the issue: When writing 0x256 as address into the deye_sensors.py, I mean the decimal address 598.
grid_outside_voltage_L1_sensor = SingleRegisterSensor("Grid outside voltage L1", 0x256, 0.1, mqtt_topic_suffix='grid/outside/voltage/L1')
When running
root@broker ~# docker run --env-file deye-inverter-mqtt/config.env ghcr.io/kbialek/deye-inverter-mqtt r 598
int: 2373, l: 69, h: 9

it gives the right output of 237,3V also. So in general, the inverter is reachable, answering, etc. but I guess, my dec/hex conversion is wrong or something alike.

hi @thing4711
First of all, I'm impressed by the list of registers you want to read from the device. Do you really need to read them all?
Now, why are they not read? Simply because the bridge is optimized to query only a subset of registers from the logger. Why? Because each read request takes time and quite often has to be retried due to a timeout.
Can this be changed? Absolutely yes. Here is how.

Define feature specific register grups, e.g. battery, grid_outside, grid_inside, offgrid, etc.
Add a configuration option to specify the groups to be read, by default only the current, minimal set of registers will be read
Enhance the reading logic to query only configured set of register groups

Hi Krzysztof,
thank you for the quick response. That said, it makes absolutely sense.
And sorry for posting it as an issue while it is more a feature request, I guess.
Wrt the number of registers: I have tried to include everything that I could identify by the relevant documentation from Deye as this is my first setup of the inverter and I would want to log/monitor as much as possible to really understand what it is doing in which situation. After this phase of understanding, I guess, only a few of those parameters would be relevant for daily operations.
I forgot in the list of things I don't know, that I also don't know python ;-).
Could you maybe point me to the right spot where to extend the registers that are read for later evaluation ?
I have the feeling it is somewhere inside deye_modbus.py where all those hex values are somewhere in the functions, but I have to admit, I don't get it :-/.
Don't know, if it helps going forward, but these are the groups of subsequent register numbers that are currently of interest:

130
514-535
540-541
555-558
587-591
590-591
598-655
661-667
672-683

Hi @thing4711
If you are willing to contribute then please open a documentation PR and add new registers in the table (README.md file). Feel free to also add a column and define the groups.
Once this is ready I will implement it in the upcoming weeks.

Can we please reopen this? I was watching this since I've the Deye 12K sitting here, but not running yet, so can't contribute in a meaningful way, yet. However, register lists can be taken from these projects & I'd happily test them once my inverter reads other values than 0 everything ;-)
https://github.com/bagges/deye-esp32-bridge/blob/main/deye-esp32-bridge.yaml Built by a friend of mine, and seems to work well
https://github.com/kellerza/sunsynk/blob/main/sunsynk/definitions3ph.py Someone else & I did gather some registers, but this one is not really tested (and at least the inverter power is read wrong, unless they supplied me with a suprisingly compact 26MW inverter 😆)

Okay. Meanwhile I did some changes that should make it easier to add new metrics. I'm looking forward to your tests @archi

not stale, just waiting for the electrician ;)

Actually sg04lp3 is supported since the latest release https://github.com/kbialek/deye-inverter-mqtt/releases/tag/2023.03.4
So I'm closing this issue as for now. Open another one if you will have a problem with this tool in the future.


Artifact not found in Maven Central

Hi,
I'm trying to inclure the lib as a dependecy using maven coordinates from readme, but getting:
Could not find artifact net.placemarkt:address-formatter-java:jar:0.0.9 in central (https://repo.maven.apache.org/maven2)

Is the artifact supposed to be found in maven central, or should I use some other repo?

Hi! You should use the Github repo. You'll need to add a repository to your settings.xml that looks something like this:
<repository>
     <id>github</id>
     <url>https://maven.pkg.github.com/OWNER/*</url>
</repository>

Check out this Stack Overflow answer and the Github Maven docs for more information.
I'm also happy to mirror the package in Maven Central. I won't be able to get to it before this weekend though.

Mirroring the package to Maven Central would be the best, since pulling the dependency from GitHub Packages requires authentication.

Happy to do that then.

Is this still ongoing?

Hey @chyoungie, just wanted to touch base. I've uploaded to the Sonatype Nexus repository manager and raised a ticket with them to sync to Maven Central. It looks like they have to do it manually, so it might be until Monday when it becomes available there. FWIW it is popping up in my search here already: https://s01.oss.sonatype.org/#nexus-search;quick~placemarkt
Closing this issue. Will update the Readme when Central syncs. Any more questions feel free to raise an issue. Thanks!


PolymerElement

Sometimes, when your init the widget via uibinder and call the setValue() of a input does'nt work. the console shows no errors but the value stays empty.
Calling setValue() via a Function passed in the method ready()  fixes that.
Is there a method to get notified when all the polymer elements of a container are ready ?

Do you use Elements or Widgets in your UiBinder ?

I'm using widgets in uibinder
Le 14 juil. 2015 18:48, "Manuel Carrasco Moñino"<EMAIL_ADDRESS>a écrit :

Do you use Elements or Widgets in your UiBinder ?
—
Reply to this email directly or view it on GitHub
https://github.com/vaadin/gwt-polymer-elements/issues/44#issuecomment-121305410
.

The ways to get notified when the ui is ready are:

To know that all the imports are loaded you can use:

   Polymer.whenReady(Function callback);

To know when a specific widget or element is ready use:

   Polymer.ready(Element el, Function callback);

Note that the whenReady method is available since the <IP_ADDRESS> version of vaadin-gwt-polymer-elements


Intermittent error when verifying tokens ("Public key retrieved from google was not found or could not be parsed")

Hello Nick!
Thanks for writing and sharing ExFirebaseAuth! I'm using it on my project, and when I try to parse a Firebase token with ExFirebaseAuth.Token.verify_token/1, I get the following error:
{:error,
 "Public key retrieved from google was not found or could not be parsed"}

This is an intermittent scenario. It works sometimes, but once in a while I get this error. I'm not sure if it's an issue with my application, my build, or the library itself (I'm doing using anything other than decoding Firebase tokens, and I've properly configured the library as per docs says).
What could I do to fix, debug, or handle this kind of error?

Hi Joel, are you using the latest version? I have recently patched some issues that may be related to this.

Nick,
I believe I am. My mix.lock file shows the following line for ex_firebase_auth:
"ex_firebase_auth": {:hex, :ex_firebase_auth, "0.4.0", "2c855adc5af63910dbe912c260fe896f6bc5c967d32e76a4f9f5d2e3d003ad00", [:mix], [{:finch, "~> 0.6.3", [hex: :finch, repo: "hexpm", optional: false]}, {:jason, "~> 1.2.2", [hex: :jason, repo: "hexpm", optional: false]}, {:jose, "~> 1.10", [hex: :jose, repo: "hexpm", optional: false]}], "hexpm", "5f3a1af2826556f6c9c9456f7ca8a22204a2050a399183b87db653b16b480dd3"},

@Nickforall any clue on why it might be happening? I'm trying to debug your code (mostly the ExFirebaseAuth.KeySource.Google module), but since I'm not much experienced in Elixir I'm kinda lost on if/where could I start.
It seems the keys are being stored on the ETS table. I was able to check it, and it's there. I've checked the fetching and storing logic, and it seems fine.
Any suggestion on how to tackle it will be appreciated.

Ah thanks for looking that up. Version looks good indeed.
If the keys are present it's an error likely in ExFirebaseAuth.Token.get_public_key. Are you able to share the response of looking up the key in ETS.
Running
:ets.lookup(ExFirebaseAuth.KeyStore, "key identifier") |> IO.inspect()

Where key identifier is the kid field set in the header of the failing JWT token. You can find that field by pasting the JWT token on this site https://jwt.io/

I noticed something interesting: the keys returned from the Google API (endpoint<EMAIL_ADDRESS>are two, but there's one one in :ets.
Keys being returned from Google:

1de8067a(...)
2c8e2b29(...)

But then I can see only one of these keys in ETS (the 2c8e2b29 one):
:ets.first(ExFirebaseAuth.KeyStore) ==  :ets.last(ExFirebaseAuth.KeyStore) # => true

I'm not sure if it could be the problem, but it sounds like it's trying to use a key from ETS that hasn't been saved on GenServer properly (I'm checking it right now). Does these two keys need to be persisted on GS?

Both keys appear to be stored for me
iex(1)> :ets.lookup(ExFirebaseAuth.KeyStore, "1de8067a8298a4e3344b4dbded25f2fb4f40f3ce")
[
  {"1de8067a8298a4e3344b4dbded25f2fb4f40f3ce",
   %JOSE.JWK{
     fields: %{},
     keys: :undefined,
     kty: {:jose_jwk_kty_rsa,
      {:RSAPublicKey,
<PHONE_NUMBER>3564474024552777674588971472920440915151214730917034891541643605274620759316528055591468136661137520152594515799266531014792352467051812558759718253701274916961570450051977940078876540866807034755900397893743767729821776034347281804226663347871309953420303138970497142145548103282535712474656170759061616747904818234768797587000431430823479696758424263808719865263113404572079543540174336760263005282594729455496333252868461897332779892096102967768149760946636181515453210181352755808415199796061764682755851736443579504731293496183947727903952024163376295430559216168903882510680225192394422189350042523529,
       65537}}
   }}
]
iex(2)> :ets.lookup(ExFirebaseAuth.KeyStore, "2c8e2b296c6f3284ec30b8865d7293e627fa2b8f")
[
  {"2c8e2b296c6f3284ec30b8865d7293e627fa2b8f",
   %JOSE.JWK{
     fields: %{},
     keys: :undefined,
     kty: {:jose_jwk_kty_rsa,
      {:RSAPublicKey,
<PHONE_NUMBER>4087117862652297303138015744716970221023194014737088335173488623053669445118950777896686375145280397736719801585386103191715603537943277936222540841961380814749652592621245476142671898218399048549247964898530843412888690324221782782333188312388982278764033871484591743614113262601891652921518639600098187889918029300715734069201637798801480542357681640333674591855805519565142407445271198676123850744648196824392359019957123169918414953914088989160670319893455739807902909711974347754244271427745437696805081847397258439433970805476231323309864317884645909958048949905458702056091649093251520793764276120603,
       65537}}
   }}
]
iex(3)>

Sorry, I just checked it again, both keys seem to be in ETS now. Any, I'm afraid don't have the skills to debug it myself.
I'm not sure what else I could provide you to help tackle the issue, but I'm up for providing you more information that could help you solve it. Thank you for writing and sharing it in first place!

I have been having this issue too. It's very rare, I couldn't find a pattern to reproduce it consistently.
And it happens when I'm starting phoenix or mix test, preventing them from starting.
Should it really prevent applications from starting up if it can't get the public keys?
Is it possible to add a retry strategy to it?

I have not seen this error, and we've been running on production for quite some months now, so closing this as stale. Feel free to reopen if it reoccurs.

Getting the same error consistently for last 30 minutes. First time using this library.
Version - {:ex_firebase_auth, "~> 0.5.1"}
ets table contains only one entry with following value -
iex(1)> :ets.first(ExFirebaseAuth.KeyStore)
"6a4f87ff5d93fa6ea03e5c6e88eea0acd2a232a9"
iex(2)> :ets.last(ExFirebaseAuth.KeyStore)
"6a4f87ff5d93fa6ea03e5c6e88eea0acd2a232a9"
iex(3)> :ets.lookup(ExFirebaseAuth.KeyStore, "6a4f87ff5d93fa6ea03e5c6e88eea0acd2a232a9")
[
  {"6a4f87ff5d93fa6ea03e5c6e88eea0acd2a232a9",
   %JOSE.JWK{
     fields: %{},
     keys: :undefined,
     kty: {:jose_jwk_kty_rsa,
      {:RSAPublicKey,
<PHONE_NUMBER>7166000117937282941287368499188964267704350320016815060755186299190334552341359030182847862883650390995706932990206917504303874597159717626156857776530120286608824298039026662712309062585296391513994028930201376912224740158628136408547035523323040966599847393117788904610391693639428199426775371439187431710883575502972086796633627213970033547315970319396410708150818633921757026450722384908347116277890243025314192440036812929920627983552722832658264926504359043778585873454116991087894748041249472749584754467425019137143154494316545575161017698890108258608397227982398909111303817013085192016995952648177,
       65537}}
   }}
]

Verify token returns
{:error, "Public key retrieved from google was not found or could not be parsed"}


ROX-10066: improve label matching with selectors

Description
The aim of ROX-10066 is to improve performance by reducing the number of label comparisons that have to be made, concretely by immediately discarding a match where the selector has more labels than the incoming item to be matched.
Since the labels.selector is not our code, this has been accomplished by writing a selectorWrapper layer around the selector, and this selectorWrapper then does the abovementioned performance improvement by comparing number of labels and only forwarding a Matches() call to the selector if this preliminary check passes.
Checklist

[ ] Investigated and inspected CI test results
[x] Unit test and regression tests added
[ ] ~Evaluated and added CHANGELOG entry if required~
[ ] ~Determined and documented upgrade steps~
[ ] ~Documented user facing changes (create PR based on stackrox/openshift-docs and merge into rhacs-docs)~

Nothing user facing changes, only performance should improve!
Testing Performed
Tests can be found under listener/resources/selectorwrapper_test.go. In each test case it is checked that labels are matched correctly, and that the selector.Matches function is called if and only if selectorWrapper.Matches can't discard this query prematurely.
These tests were used in regression testing as matching behavior should not change and was previously untested.

Looking through my test cases once more I noticed that I forgot to test selectorWrapper disjunctions. I'll add test cases for those next.

Heads up: I am giving it a look, but most probably fill finish first on Friday.

I think, it would be good if some other person would give this a look before merging.
Merging is still blocked by @lvalerom , so if you could have another look when you have time that'd be great

It would be also interesting to re-run the benchmarks included in the network policy store and see whether there is any performance improvement after implementing this.

I'll do this now

Just got around to running benchmarks, actually surprised at the result. It went from 802.457s on master to 677.785s on my feature branch. Although I did use a recent state of master and not what I branched off from so interference from later changes cannot be ruled out. The time save came from Upsert_Update and Upsert_Add using a lot less allocs/op than before going from 5 and 9 allocs/op to 0 and 4 allocs/op respectively as well as lower B/op. (see attached screenshot)

For some reason it doesn't let me respond to your last comment.  I could change expectedInternalSelectorMatchesFunctionCall to expectedMatchUsingNumLabels but that would require flipping my logic, since right now I am checking for the exact opposite case. With disjunctions this would be a little bit annoying to do. I'll think a bit more and see if I can come up with another name.


Clearly state and cite cutting edge optimization approaches to determine phase angles

Summary: Upon review, we realized that one of the cited approaches to compute the phase angles belongs in the "optimization" section. It's an important result and the cutting edge in methods for computing phase angles. For this reason we update the demo to add more emphasis to it.

@Jaybsoni ready to merge?


🐛.NET MAUI Fix iOS

### Tasks
- [ ] Fix iOS Animations

Hey @JackDevAU , can you please elaborate on that? Is it still relevant?

Hey @JackDevAU , can you please elaborate on that? Is it still relevant?

Hey @AntPolkanov
This has been solved :)


Cleanup working with tags tutorial

Tutorial edited for simplification and style guide. Additional changes were needed to reflect the introduction of fast first Target in v91. As this change means there are no longer devel and master branches, much of this tutorial needed to be modified. Information was added pointing to the reference manual page on having the CI follow branches. This is a stop-gap measure until an additional tutorial is added which will focus on adding an additional branch. At that point, this tutorial will be revised again.
QA steps: ran linter, checked output in browser.

Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[x] Review for wordiness
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
See commit message...this tutorial is going to be a bit awkward until we add an additional one, I tried to make it work out as best as possible for the time being, but suggestions are very welcome.

Docs for 49a08912c97f7d76f02218507804056b5638a4ae are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2254/docs/artifacts/html/index.html

Docs for c9b84527ba658181f3c888145cc6fe8466290b7d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2263/docs/artifacts/html/index.html

Docs for 777db48dd9c1c9ca093e6555b88d563a0a0a1905 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2264/docs/artifacts/html/index.html

Docs for 92bb267926c28306b34cab8883f314775390db3d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2267/docs/artifacts/html/index.html

Docs for b301cc1d950d828bb7a9d1eb207f1a4f0d7e472c are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2269/docs/artifacts/html/index.html


Named Entity Search

light refactoring of some of the search functions

added searching by named entities

added start_date, end_date to multi search

@butlern @will-horning @heavi5ide

LGTM


add problem to Convert Roman numeral to Decimal

Add a problem to convert roman numeral to decimal and its c++ solution

@chandrikadeb7 please review and approve this PR


Basic implementation of Jolt's shift transformation

see: https://github.com/bazaarvoice/jolt/blob/master/jolt-core/src/main/java/com/bazaarvoice/jolt/Shiftr.java

Fixed in https://github.com/infinyon/fluvio-jolt/pull/7


Cleanup code formatting and some vet/lint issues

Most of the vet/lint issues are related to Url => URL translations. Where possible these have been updated.

The main branch is far with your pr, so I just do the same thing to the master branch.
But thanks for your work.


Api for check btc balance on omniusdt node ?

Is there any command for check btc balance of omniisudt address on omniusdt node ?. I want to check there is btc balance available to transaction fee .
Please help.

Hello, you could use the "listunspent" RPC  to list unspent outputs of your wallet. There is no more convenient way currently available.

@dexX7 but why?


Contributing page is incomplete

Before the section "push the changes to your new remote" there needs to be a section "git remote set-url USER_NAME https://github.com/grd/harvey.git"

Adding to that, the "It's time to fork the repo!", is that done only once or does that count for every contribution? What I am saying is that "hub" isn't well known and also not well documented. And I am having troubles with synchronizing after contribution. My knowledge of "git" is average.

You will fork only once. Rest of future times you will do only:
git remote add YOUR_USER git://github.com/YOUR_USER/harvey.git
git push YOUR_USER feature
hub pull-request
What kind of troubles with synchronizing are you having?
hub tool is something new to me too, we're all learning everyday new things, which is one of the main goals in Harvey, but in it's github site there's some useful information. Think in it just in a wrapper to git, you could do the same it does through a bunch of usual git commands, hub is there only to make life easier.

Thanks for the clarification! The problem I have with synchronizing is that when I do a "git pull" it says that my branch is x commits ahead of master.

If you're working into a branch and is outdated respect master, just do a git pull --rebase. This will put your changes after the pull. In case there would be conflicts, you will have to solve them manually, but they are marked with something like ">>>>>HEAD" and git will tell you about what files are them.

Thanks! I think btw that documenting this would clarify it a lot. Shall I give it a try?

Yes, of course. Just send a pull-request to CONTRIBUTING.md file completing all you think is missing as a new experience programmer here :-).

I will do that this evening. More input is welcome btw ;-)

Okay, now I am having troubles with hub pull-request itself. My git remote -v states:
grd	https://github.com/grd/harvey.git (fetch)
grd	https://github.com/grd/harvey.git (push)
origin	https://github.com/Harvey-OS/harvey.git (fetch)
origin	https://github.com/Harvey-OS/harvey.git (push)
I pushed branch issue_66 with git push grd issue_66 and after that I did hub pull-request. The answer is:
Error creating pull request: Unprocessable Entity (HTTP 422)
No commits between Harvey-OS:master and grd:issue_66
Help...

Seems like if you have unpushed changes... did you "git commit" all?
If it keeps happening, set the HUB_VERBOSE=1 hub pull-request to see if it says something more useful. All bugs related in hub tool are old.


Project filter just stopped working

Describe the bug
code renders tasks from all different projects and priorities when it should just show p1 tasks for the project specified in the filter
To Reproduce
Go to live preview with code below inserted
If I remove the   "#Account Capture Activities Project & " it shows all p1 tasks correctly.
Expected behavior
show all priority 1 tasks for the project "Account Capture Activities Project" with this code
```todoist
name: Critical This Week (P1) Tasks
filter: "#Account Capture Activities Project & p1"

Screenshots

Desktop (please complete the following information):

Plugin Version v1.11.1
Obsidian Version v1.3.5

Additional context
Same behavior on Windows 10 and Windows 11

Closing as duplicate of #235


tooltip fixes dragonflight

These are some fixes to make tooltips partly working again in dragonflight.
Still missing is backwards compatiblity with prepatch and replacement for the hook scripts

Ok now also fixed it for dragonflight.
Seen some minor bugs like if you item compare on normal items you get empty compare window
And some misalignments but most important stuff is working so i'm done for a bit :)

@MrMime71


[skc] Exit on internal errors

If exceptions escape out of functions run by runWithGc, they are
just printed and ignored. In the case of skc, this results in skargo
not noticing when compilation fails.

they are just printed and ignored

By skc?

By Context.runWithGcIntern really, see here . Note that if the function passed in throws, its exception message is printed and the context is returned, so the skc-specific code has no idea it has failed once runWithGc returns. Maybe I'm confused, but that is my understanding.

I've also run in to skargo not realising that skc failed. A different exit code makes sense to me.

Ok, I'll change the exit code. No preferences I guess? I don't have much experience with distinguishing exit codes, have never gone beyond success, internal failure / uncaught exception, crash, oom.

Changed the exit code on uncaught exception to 2. I surveyed existing uses of skipExit and 0 is success, obviously; 1 is wrong arguments and other things that could be categorized as "user error", as well as failures to run clang or find the expected version of llvm; 2 is often used for skc internal errors, and 4 is used for no input files.

Ship it!


Added lightbox2 functionality complete with an example (project_10)

What is this for?

What is a feature for? Anything you use it for.
I mostly needed it where I put 12 images in a row. With this you can actually see all of them. Also, in general I like if an image pops up when I click on it.
I am not sure about it but I guess imagemagick downscales the embedded images? In that case pop up does not enlarge the image but if you upload HD images...

What is a feature for? Anything you use it for.

With this you assume we know what lightbox is for.

I mostly needed it where I put 12 images in a row. With this you can actually see all of them. Also, in general I like if an image pops up when I click on it.

Do you have a working example or screenshots? In this example the zoomable images pops when you click on them.

I am not sure about it but I guess imagemagick downscales the embedded images?

Not entirely sure, but I believe this is only currently happening on publication images like reported in #2668.

Should I cancel the PR?

just catching up here: what's the advantage of lightbox2 over zoomable images we already have?

Can you answer this @Picsiri?

sorry, I don't usually check my GitHub ...
For example you can group images, there are more mini image setting options.
I made a pretty looking gallery with 6 images in a row that are unrecognizable on that scale but it is clearly indicated that they belong together and you can view them in a carousel.


clean gameview problem

When using lock logo the logo goes over the bar with play and options

Duplicate of #50


python311Packages.xnd: fix python311 build with upstream patch

Fix renamed functions and moved header file. package builds and unit tests pass. Patch submitted and merged upstream as
https://github.com/xnd-project/xnd/pull/48
ZHF #265948
https://hydra.nixos.org/build/239056417
Result of nixpkgs-review pr 268058 run on x86_64-linux 1

8 packages built:

python310Packages.gumath
python310Packages.gumath.dist
python310Packages.xnd
python310Packages.xnd.dist
python311Packages.gumath
python311Packages.gumath.dist
python311Packages.xnd
python311Packages.xnd.dist

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

The package itself seems to build and run fine, but i cannot create a python environment with it. This is my tests in nixpkgs-review:
$ nix-shell -I nixpkgs=nixpkgs/ -p 'python311.withPackages (ps: [ ps.xnd ps.pdoc ])' --run 'pdoc xnd'
error: collision between `/nix/store/zqwgj0cwr7ssi3jqh3jhbbsjv1kadmvf-python3.11-ndtypes-unstable-2019-08-01/include/docstrings.h' and `/nix/store/cvcwci3iplx07ln9k288ddaw7px29r23-python3.11-xnd-unstable-2019-08-01/include/docstrings.h'

I'd like to move the header into the dev output, but creating it will pull with it the propagated inputs, so i am at a loss. It seems this just git merged as i am writing this, so i'll look into it myself

The package itself seems to build and run fine, but i cannot create a python environment with it. This is my tests in nixpkgs-review:
$ nix-shell -I nixpkgs=nixpkgs/ -p 'python311.withPackages (ps: [ ps.xnd ps.pdoc ])' --run 'pdoc xnd'
error: collision between `/nix/store/zqwgj0cwr7ssi3jqh3jhbbsjv1kadmvf-python3.11-ndtypes-unstable-2019-08-01/include/docstrings.h' and `/nix/store/cvcwci3iplx07ln9k288ddaw7px29r23-python3.11-xnd-unstable-2019-08-01/include/docstrings.h'

I'd like to move the header into the dev output, but creating it will pull with it the propagated inputs, so i am at a loss.
It seems this just got merged as i am writing this, so i'll look into it myself

hmm. ndtypes and xnd are part of the same xnd-project ecosystem. this collision seems like it's been an issue since they were added in 2018. i am a little cloudy on the differences of out, lib, dev -- would have to grep around a little to see how to prevent the propogatedBuildInputs from going in dev -- i assume that dev should just contain headers?

Generally libraries goes in lib, and built-time headers go in dev. I'm working on a PR which should fix it


Switch to mypy baseline (#7788)

Pull request opened by the merge tool on behalf of #7788

Merged into branches iso7 in 0f789f40922cd49c43e939b30a4ec8541abfd40e


Two small fixes

Please provide enough information so that others can review your pull request:

Following https://github.com/frappe/helm/pull/69, I found there are a couple of small fixes required

Explain the details for making this change. What existing problem does the pull request solve?

The two fixes are:

This helm chart deploys redis wihout password by default. Bitnami's redis image runs in safe mode by default and requires a password. There is a small indentation issue that wasn't applying right env variable. I saw that in the latest changes of this chart, the command of the redis containers is overriden. Maybe this makes that override redundant too?
With new persistence classes, there was a conditional that would always be false

@revant yes/no are valid yaml boolean values

A Boolean value can be True/False or Yes/No or On/Off.

https://www.javatpoint.com/yaml-data-types

Made it true/false. Docs says it defaults to false.


run docker in Container

can i  install docker in Container with image Centos or ubuntu?

Yes, it's possible to run docker-in-docker (docker running inside a docker container), but you'll likely need;

to run the container with --privileged (be aware that this disables all security that containers provide, so processes can escape the container and take control of the host)
for graph-drivers (copy-on-write) to work, the /var/lib/docker directory should use a volume.

Please keep in mind that the GitHub issue tracker is not intended as a general support forum,
but for reporting bugs and feature requests. For other type of questions, consider using one of;

https://forums.docker.com
the Docker community Slack channel (register here: http://dockr.ly/community)
StackOverflow

I'm going to close this issue because this is not a bug, but feel free to continue the conversation 👍

thanks， i use the offical image docker.i works on my pc.
i want to run it on Bluemix,but Bluemix container doesn't support --privileged.
can i run an image of centos,and install  docker in it?

Without --privileged it won't be able to run (same for a centos image). I can imagine BlueMix doesn't allow setting privilege for the reason I mentioned (i.e., with --privileged, you can take control of the host), which likely not what they want 😇

I see, thank you very much.
it's sad.