Teams and Projects Mismatched, "Requested resource does not exist" error in logs

Describe the bug
I set up a fairly simple configuration of teams, projects, and projectkeys to test out the operator. Given a list of different project names, I have created teams containing a single project of the same name, along with a projectkey:
apiVersion: sentry.kubernetes.jaceys.me/v1alpha1
kind: Team
metadata:
  name: team-aaaa
  namespace: sentry-operator-system
spec:
  name: aaaa
  slug: aaaa
---
apiVersion: sentry.kubernetes.jaceys.me/v1alpha1
kind: Project
metadata:
  name: project-aaaa
  namespace: sentry-operator-system
spec:
  name: aaaa
  slug: aaaa
  team: aaaa
---
apiVersion: sentry.kubernetes.jaceys.me/v1alpha1
kind: ProjectKey
metadata:
  name: production-aaaa
  namespace: sentry-operator-system
spec:
  name: production
  project: aaaa

This configuration is repeated with bbbb, cccc, etc.
After some amount of time, in Sentry these projects started being affiliated with the wrong team. There were no manual changes to the configuration of projects or teams in Sentry, so I presume the operator did this accidentally on its own. The only other actions that occurred were occasional redeploys of the operator along with my custom Team, Project, and ProjectKey definitions to Kubernetes.
Steps to reproduce

Create Team, Project, and ProjectKey's affiliated with each other, all with the same name (see example above). For example, the "aaaa" team has a project named "aaaa".
After some amount of time, projects and teams get out of alignment. E.g., team "cccc" now has no projects, and instead team "bbbb" contains projects "bbbb" and "cccc". Since I have kept a one-to-one mapping of projects to teams in my setup, this is easy to observe.
Either due to or because of this, many reconciler errors are shown in the logs. (see below)

My completely uneducated guess is that there is maybe some race condition in either the checking of if project-team pairs are valid or the updating of them, which causes the wrong team to be matched with the wrong project.
Expected behavior

Projects should stay as part of the correct team and not move unexpectedly

Additional context
I see the following errors scrolling in the log of the sentry-operator-controller-manager:
2021-02-02T20:36:04.820Z	ERROR	controllers.ProjectKey	failed to recreate ProjectKey	{"projectkey": "sentry-operator-system/production-aaaa", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
github.com/jace-ys/sentry-operator/controllers.(*ProjectKeyReconciler).Reconcile
	/workspace/controllers/projectkey_controller.go:132
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:256
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-02-02T20:36:04.826Z	ERROR	controller-runtime.controller	Reconciler error	{"controller": "projectkey", "request": "sentry-operator-system/production-aaaa", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-02-02T20:36:07.316Z	ERROR	controllers.ProjectKey	failed to recreate ProjectKey	{"projectkey": "sentry-operator-system/production-bbbb", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
github.com/jace-ys/sentry-operator/controllers.(*ProjectKeyReconciler).Reconcile
	/workspace/controllers/projectkey_controller.go:132
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:256
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-02-02T20:36:07.322Z	ERROR	controller-runtime.controller	Reconciler error	{"controller": "projectkey", "request": "sentry-operator-system/production-bbbb", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-02-02T20:36:11.010Z	ERROR	controllers.ProjectKey	failed to recreate ProjectKey	{"projectkey": "sentry-operator-system/production-cccc", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
github.com/jace-ys/sentry-operator/controllers.(*ProjectKeyReconciler).Reconcile
	/workspace/controllers/projectkey_controller.go:132
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:256
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88
2021-02-02T20:36:11.016Z	ERROR	controller-runtime.controller	Reconciler error	{"controller": "projectkey", "request": "sentry-operator-system/production-cccc", "error": "sentry: The requested resource does not exist"}
github.com/go-logr/zapr.(*zapLogger).Error
	/go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:258
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:232
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
	/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.5.0/pkg/internal/controller/controller.go:211
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
	/go/pkg/mod/k8s.io/apimachinery@v0.17.2/pkg/util/wait/wait.go:88

This project seems super promising, thank you for creating it! I just hope this bug can get worked out, as it's stopping me from using it with a self-hosted instance of Sentry.

Hi @jwoglom!
Thanks for raising this issue. This doesn't sound desirable indeed. I will have a look later today and try to resolve it ASAP 🙂

Hi -- the approximate period of time this was up for was about 3-4 days. I deployed and set up sentry-operator on Thursday/Friday, and saw the initial projects + teams get created (scrolling through the Sentry UI, everything appeared to be in order). Then today (on Tuesday) I noticed the mismatches, and that the log scrolling with the messages I posted above had been going on for at least 6 hours or so (could only go so far back with kubectl logs).
I haven't seen it happen immediately after redeploying the operator but I will look further into this tomorrow.

Great thanks for the info! Will let you know what I find, cheers!

Hey @jwoglom!
I just spent some time looking into this, but I can't seem to replicate the issue you're seeing yet (maybe I'm not testing it for long enough). Re-deploying the operator doesn't seem to cause any issues for me. But just some observations / guesses I have in mind:

I noted that you're using a self-hosted version of Sentry. What version do you happening to be running? I have only been testing against the cloud version of Sentry, so it's possible that the API / version used for self-hosted Sentry might be different, causing the API calls to do some unexpected things (doesn't seem likely though).
The API (for Sentry cloud) doesn't actually allow you to change the team of a project through the API (I have noted this earlier in this comment and had to document an explicit of working around this if you wanted to change a project's team. So it's quite strange that the bug you're seeing is the opposite of what the API allows. In this case, what might be happening is that the projects are getting deleted and re-created entirely under a different team rather than moved 🤔 Did you notice this? (ie. Sentry error history/data being lost or similar?)

I will try leaving the operator running in my cluster overnight and see if this issue pops up tomorrow. If I get the time this weekend, I will try spinning up an instance of self-hosted Sentry in my cluster to test against. Are you deploying Sentry via a Helm chart?

Hi @jace-ys, thanks so much for looking into this. I am deploying a modified version of the Sentry Helm chart to a Kubernetes cluster -- long story short I exported the Sentry chart to YAMLs, disabled the built-in clickhouse cluster since it was causing some problems in my environment, and made some other minor configuration tweaks.
Some things I did do, if it helps in testing, is delete the deployment (e.g., kubectl delete'd all of the resources) and then re-apply. I also triggered a rollout restart of the sentry-operator-controller-manager deployment after each apply. Maybe some combination of these inadvertently got everything in a bad state.
When I have time I'll try and see if I can reproduce this again and log what I did.

Yeah it's possible that some series of changes led to corrupt state / data races somewhere.. I'll have another dig into the code to see if I can spot anything obvious.
I'll also try to spin up a Sentry instance in my cluster and test it against that as well. Thanks for your time raising this issue and help investigating! Hopefully we can resolve this soon 🙌


alert.present() should resolve with user action on alert.

Ionic version:  (check one with "x")
[ ] 1.x
[x ] 2.x
I'm submitting a ...  (check one with "x")
[ ] bug report
[x ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When I create and present an alert, it returns a Promise that I guess resolves to true if the alert is correctly displayed
Expected behavior:
I was hoping alert.present() would return a promise that resolves with the value of the users action on the alert.  For instance on a confirm alert it could resolve to true if they hit OK and false if they hit cancel.
This would enable me to chain an action on the result of that alert.  As I have to have it nested within the button options.
Steps to reproduce:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
insert the output from ionic info here

Hello! Thanks for the feature request. I'm going to move this issue over to our internal list of feature requests for evaluation. We are continually prioritizing all requests that we receive with outstanding issues. We are extremely grateful for your feedback, but it may not always be our next priority. I'll copy the issue back to this repository when we have begun implementation. Thanks!

This issue was moved to driftyco/ionic-feature-requests#135


Implement before attribute for EFContainer, EFBlock and their References

Implement before attribute for EFContainer, EFBlock and their References
before="-" => prepends the element
before="{name}" => before name's tag

(+) Keep the original tree elements priority when rendering page.

Done

Have to implement:

After attribute for EFBlock, EFContainer Tags
Remove for EFReferenceContainer and EFReferenceBlock

to let go

After attribute for EFBlock, EFContainer Tags => Done
Remove for EFReferenceContainer and EFReferenceBlock => Replaced with a new EFMove Node


IPV6/AAAA support

I'm currently running my docker installation with ipv6 enabled.
However, I don't seem to be able to resolv AAAA records? do i need to manually enable this on skydock as well?

Don't know if it's related, but I had similar issues a while back when building out a dns server. It might be a bug in the resolver; https://github.com/asbjornenge/rainbow-dns/issues/5


[Backport release-24.05] armagetronad: update 0.4; fix possible problem in installCheckPhase

Description of changes

Manual backport of #316823 due to extra commit necessary due to unstable libxml updates.
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

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Thanks, fixed that!

https://github.com/NixOS/nixpkgs/commit/324f3f75f32faee34d1aaf23c0dd0430c5534792
Looks like we squash merged before so there aren't refs for the relevant commits. Ah well. :-)


CVE-2023-5752 (MEDIUM): detected in Lambda Docker Images.

CVE Details

CVE ID
Severity
Affected Package
Installed Version
Fixed Version
Date Published
Date of Scan

CVE-2023-5752
MEDIUM
pip
23.0.1
23.3
2023-10-25T18:17:44.867Z
2024-09-20T01:25:50.413203652Z

Affected Docker Images

Image Name
SHA

public.ecr.aws/lambda/python:3.10
public.ecr.aws/lambda/python@sha256:2fbab05c93b008b68948e19085729cb767b406a9431694c5322577727ccdd957

public.ecr.aws/lambda/python:3.9
public.ecr.aws/lambda/python@sha256:d6ae68cf17e1379e6b877aad75ac1c0b78ad806a9e48a29322e72594ae97fba0

public.ecr.aws/lambda/python:3.8
public.ecr.aws/lambda/python@sha256:92baa296fcd79d9fb5c3505e5a37646fb2f4850f3a8b13757fbe2d7e51194135

Description

When installing a package from a Mercurial VCS URL  (ie "pip install
hg+...") with pip prior to v23.3, the specified Mercurial revision could
be used to inject arbitrary configuration options to the "hg clone"
call (ie "--config"). Controlling the Mercurial configuration can modify
how and which repository is installed. This vulnerability does not
affect users who aren't installing from Mercurial.

Remediation Steps

Update the affected package pip from version 23.0.1 to 23.3.

About this issue

This issue may not contain all the information about the CVE nor the images it affects.
This issue will not be updated with new information and the list of affected images may have changed since the creation of this issue.
For more, visit Lambda Watchdog.
This issue was created automatically by Lambda Watchdog.

is there a fix coming to the base image for this?


Any plans to implement within HF Transformers?

Hi team, and thanks for publishing!
I've been playing for a few days now to get the model working on Amazon SageMaker endpoints (full disclosure - I work at AWS), and wondered if you had any future plans to try and get the model into the Hugging Face Transformers library itself?

Hi, thanks for your advice! We will try to get the model into the Hugging Face Transformers library.


[Enhancement]: Docker comtainerization

Hello, I am running the bot with docker and I tought that I could be useful for other to share my configuration. I am using a fork made by me, that allows all values in the config file to be set as environement variables, so that you don't need attach the cotainer to modify the file.
Dockerfile:
FROM python:3.10.0

ENV PYTHONUNBUFFERED=1

WORKDIR /app
RUN git clone https://github.com/Paillat-dev/Vulkan.git /app #cloning my fork to allow settings as env variables
RUN pip install -r requirements.txt
RUN apt-get update && apt-get install -y software-properties-common && apt-get install -y ffmpeg
RUN adduser -u 5678 --disabled-password --gecos "" appuser && chown -R appuser /app
USER appuser
CMD ["python", "main.py"]

docker-compose.yaml:
version: '3'
services:
  vulkan:
    build:
      context: .
      dockerfile: Dockerfile
    environment:
      - BOT_PREFIX=v! #you can change the prefix
      - BOT_TOKEN=paste your bot token here!
      - SHOULD_AUTO_DISCONNECT_WHEN_ALONE=True #all settings can be set like this

simply put both files in a nw empty dir and run docker compose up -d or if it dosen't work add a dash between docker and compose.

Hi @Paillat-dev!!
First of all, I really appreciate you coming here with this new feature. With Docker it will be easier to deploy it to some web service and I think everyone would like to use that too.
So you don't want to implement this feature in this repository?
You can create a pull request and bring your changes here

Yes ofc! I just wanted to ask you first. I am going to do some more ajustements as well as adding docs in the readme and will  open one.


nem2-cli transaction mosaic does not validate if the account exists

This issue is related to https://github.com/nemtech/nem2-cli/issues/49
I've used nem2-cli account generate command to create an account. Although the operation said success, the account wasn't really created.
Then I tried to add a mosaic to the "generated" account. The command also said that the operation was a success and showed me the mosaic id.
But it seems like the mosaic operation hasn't done anything. The mosaic hasn't been created in reality

I'm not sure if the problem is the CLI or the server that is returning this false positive.
Expected outcome:
The operation should fail stating that the account doesn't exist in the system.
Note:
Nothing is shown in the nem2-cli monitor unconfirmed or nem2-cli monitor confimed logs when using the invalid account. If I add a new mosaic to an existing account, I can see that transaction in the monitors

Thanks for sending your feedback!
Account generation
The public key is recorded in the network when the account first sends or receives a transaction. The nem2-cli generates a private key without interacting with the blockchain.
Mosaic creation

To create a mosaic, you need cat.currency. Try transferring some cat.currency from one of the nemesis accounts to the account you have created.

Receiving an OK from the REST API does not mean that the transaction is included in the block.

Transaction announced correctly means that the transaction was well-formed and that the network received it.  As you mention in the note, to validate the status of the transaction you have to monitor the transaction status. Once the new account receives the transaction mentioned in 1 with cat.currency, you will be able to monitor it.
@NEMTechCN @evias To enhance the developer experience, we can add the following message after announcing a transaction:

Warning: The network has not confirmed the transaction. Remember to monitor the transaction status.

Thanks @dgarcia360. I'm new in NEM and blockchain in general.
Once I transferred some mosaics from the nemesis account to generated account, the new account is now in the system.
nem2-cli account info --profile seller
Now returns information about the account.
So the steps to give a new mosaic to a generated account are

Create the mosaics in the nemesis-account
Transfer the mosaic from the nemesis account to the new account.

It's not possible to create a new mosaic into the generated account directly right?
I have just tried re-running the command
nem2-cli transaction mosaic --amount 555 --supplymutable  --duration 100 --profile seller
and the mosaic doesn't appear in the existing generated account.
Would it be possible to add a comment to the documentation and/or a warning to the command after checking that the recipient of the nem2-cli transaction mosaic is not a nemesis account?
Thanks!
Fernando

Hi @fboucquez,

It's not possible to create a new mosaic into the generated account directly right?

It is possible. The new account seller needs to have enough  cat.currency - the mosaic to pay the service fees.  By default, creating a mosaic costs 500 cat.currency.
You can transfer cat.currency from a nemesis_account to the new account you have created.
Running the command above you will be transferring 10,000 cat.currency from the nemesis account to the new account seller:
nem2-cli transaction transfer --recipient <seller-address> --mosaics @cat.currency::10000000000 --profile nemesis_account

Note that 10,000 is written<PHONE_NUMBER>0, because the cli use absolute amounts. To get an absolute amount, multiply the amount of assets you want to send by 10^divisibility. In this case, cat.currency has divisibility 6, so 10,000 * 10^6 =<PHONE_NUMBER>0.
After the seller account receives the transfer transaction, try to create a mosaic with your account. You can query the status of the transaction at any time running the following command:
nem2-cli transaction info --hash <transaction-hash>

I close the issue, let me know if you don't manage to create the mosaic from the new account.

HI @dgarcia360. I'm sorry for the late response.
I've managed to create mosaics on the new account. Thanks so much!

The nem2-cli generates a private key without interacting with the blockchain.

Does it seem like  nem2-cli account generate is technically generating a key pair instead of an account? The account is "alive" once is in the blockchain after receiving cat.currency. Maybe the command should be called  nem2-cli key generate or  nem2-cli profile generate?


Is there any documentation?

Under README.md it says to read the documentation, but I don't see any.

Hi,
There are several resources. I will add all of them into README file ASAP.

Basic information + how to build and run: https://github.com/opencv/cvat/blob/master/README.md
User's guide (github cannot render images at the moment, it will be fixed): https://github.com/opencv/cvat/blob/master/cvat/apps/documentation/user_guide.md
XML format for annotations: https://github.com/opencv/cvat/blob/master/cvat/apps/documentation/xml_format.md
Computer Vision Annotation Tool (CVAT): interpolation mode screencast: https://www.youtube.com/watch?v=sc5X5hvxNfA
Computer Vision Annotation Tool (CVAT): attribute mode screencast: https://www.youtube.com/watch?v=5yXaG0V7X0Q
Computer Vision Annotation Tool (CVAT): annotation mode screencast: https://www.youtube.com/watch?v=uSqaQENdyJE

Good day,

"I didn't realize that all the controls were off the screen". Could you provide any screenshots please?
"none of the figure work in the user's guide". Yes, we are working on it.
"i started up a gpu/tf enabled version, but I don't see anything related to tensorflow in the interface and there isn't any documentation about how to use this feature. Seems like a good idea though.". If you did all right, button "Run TF Annotation" should appears in the dashboard for each task. It will run auto annotation for supported labels (if task contain any of such labels). We will include an information about it to documentation.
"I don't see anything on how to use the shared mode. When I select it, it makes me choose files, but points to //icv-cifs/icv_projects/cvat/data.". This path will be removed. Currently, if you want use share source, you need mount it to /home/django/share in the docker container.

I attached to screenshots - partial is what I saw originally, fullscreen after I enlarged the window.  You might be making your layout decisions based on a landscape layout assumption.
I found the tf button later, but got a label error.  It makes more sense now.  Can you give me an example of the labels string I should use, say, if I want to detect person and sports_ball?  I tried:
tag @select=class:person,sports_ball
but that's not right.  The schema is:
label_name input_type=attribute_name:attribute_value1,attribute_value2
When you mention labels, you're referring to label_name in the schema?  Can I include more than 2 of those in the label string when configuring the session?
Re: shared mode, I'll try your suggestion.
Thanks for the quick feedback.

So I figured out the tf thing.  I just used "person sports_ball" and that worked.

Thanks a lot,
Layout looks strange, we will be working on it.
Yes, label is label_name.
If you want detect persons and sport balls, you need type "person sports_ball" only.
Also you may assign some attributes for labels. Attribute examples: age or gender (for person), type or model (for car) etc. I will give some examples of valid strings below:
# number, select, radio, checkbox, text - is input types
# You also need specify each attribute type (mutable [~] or immutable [@]). Mutable attributes may be changed frame by frame (in the case of tracked objects)
# For number input type, attribute values is min, max and step.
# For radio and select - is possible values
# For checkbox and text - is default attribute value (true, false) for checkbox and ("any text") for text
person @number=age:1,100,1 @select=gender:man,woman @radio=hair:long,short,curly,straight
car ~checkbox=parked:true
face @text=description:"default description"

Of course, you may create any number of labels and attributes for task:
person @number=age:1,100,1 @select=gender:man,woman @radio=hair:long,short,curly,straight car ~checkbox=parked:true face @text=description:"default description"

Also you may see help about it if you hover cursor to labels string.
Or you can see it in HTML
Good luck

In order to see the rendered documentation, you need press F1 key in the dashboard (task list).

I tried the shared thing, but may have found a bug.  I copied a small clip into the top level host share directory and can see it when I try to select files from the create task dialog, but if I select it it also selects the enclosing directory, which it also treats as a file, which I think is the reason for the error shown on the screenshot.  For this screenshot, I clicked on select files after I got the error, so you could see that screen.
The test of the error is:
Could not create the task. ffmpy.FFRuntimeError: ffmpeg -i /home/django/data/5/.upload/ -start_number 0 -b:v 10000k -vsync 0 -an -y -q:v 16 /tmp/cvat-0qn3bhs9.data/%d.jpg exited with status 1 STDOUT: STDERR:

Yes,  it known bug.  Actually it already was fixed,  but currently was not released. As temporary solution,  I can suggest you to put any other file (empty text file for example) together with video. In this case video only will be selected.

@headdab we added information about available documentation + screenshot, screencasts. Also fixed a couple of other issues. If you have another issues please open new issues. In any case we will try to address other issues which you found in next release. Don't hesitate to send us MRs. I will close the thread.

Great. Thanks!


Minor documentation errors in execute

I think this too can be fixed:

https://github.com/Qiskit/qiskit-terra/blob/186c807877e4af573f1ad8ae6d77bac7a3688e33/qiskit/execute_function.py#L232
:math:`m \times n`

true @prakharb10 , also m and n could already be written in the same math environment upon definition. wanna open a new issue/PR since this one is already merged?
Originally posted by @johannesgreiner in https://github.com/Qiskit/qiskit-terra/issues/8181#issuecomment-1160522309

Yeah thanks, the intended LaTeX symbol is presumably \times.


Infertrade new rule based ta

Added 2 new rules
Donchain and RSI-Price relation based startegy

@Optimus-Q - thanks Melroy. CI is failing. Are tests passing locally? I think we need to get your environment set up successfully before we do lots of additional development work.
@SaurabhBansalInferstat - can you assist @Optimus-Q with getting the InferTrade unit tests to run locally?

@Optimus-Q - thanks Melroy. CI is failing. Are tests passing locally? I think we need to get your environment set up successfully before we do lots of additional development work.
@SaurabhBansalInferstat - can you assist @Optimus-Q with getting the InferTrade unit tests to run locally?

yes I can assist him . if the tests are passing on the CI then maybe there is a difference in the environment?


llava13b memory access faults on api/chat (firts call fine, fail on second one)

I have 2x7900xtx
if I close ollama after each requests and specify only 1 gpu it's running well.
I tried 8 times to run ollama server and close after a request, at some point it was broken too cause closing wasn't clearing the vram

played with https://github.com/ollama/ollama/pull/2146 keepalive parameter to 0 and had no more success (some vram still not free after shutdow from the keepalive).
tried today with same os, gpu on my desk with only 1 gpu and working like a charm so I suggest search arround the 2 gpu memory management, also noticing the vram going in the 2 gpu but 24gb vram cards and only 4-8 gb models

got it again but on mistral this time, so the issue is related to 2xgpu more than llava

@BruceMacD do you need more informations?

There's a reasonable chance the underlying defect has already been resolved.  Can you retry on the latest release and let us know if you still see the problem?

I have the same issue with the latest version, 6700XT via thunderbolt egpu.

@lpuv eGPU support is tracked via #5411

I'm going to go ahead and close this since it's pretty stale and may already be fixed. As @dhiltgen mentioned we can track the eGPU issue separately.


fix: phishing detector validation to drop invalid configs from detector

Explanation

We need to ensure that only valid configurations are processed by the phishing detector. Currently, if one configuration fails validation, it causes all configurations to fail, preventing the detector from receiving updates.
The validation process needs to be updated so that invalid configurations are filtered out, while valid configurations are still passed to the detector.
Solution:
The processConfigs function has been introduced to:

Filter out invalid configurations using the validateConfig function.
Log any validation errors encountered during this filtering process.

This ensures that any configuration passed to the phishing detector is both valid and properly formatted. Invalid configurations are logged and discarded.
References

Changelog

@metamask/phishing-controller

CHANGED: processConfigs function to filter and validate phishing detector configurations, discarding invalid ones.
CHANGED: Instead of throwing an error and failing to update the detector when validation failed on any one config, invalid configurations are now logged via console.error and skipped.

Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
[x] I've prepared draft pull requests for clients and consumer packages to resolve any breaking changes

I think it might be worth a discussion to see if I should update the validation to be more strict in this PR or not
for example enforcing name to in the config
  if (
    !('name' in config) ||
    typeof config.name !== 'string' ||
    !(config.name in ListNames)
  ) {
    throw new Error(
      "Invalid config parameter: 'name'. Must be a valid string and part of ListNames enum.",
    );
  }


[XR] Implement Hand Tracking feature

Based on this - https://github.com/immersive-web/webxr-hand-input

Close as it is now consolidated as a list item in https://github.com/BabylonJS/Babylon.js/issues/6958


SQL export - SQLite or PostgreSQL

It would be great to be able to export results from 'adjust' to an SQLite database or SQL-dump format for use by other applications

Not sure if the demand for SQLite remains, or how high that demand is.  In looking into options to export adjustment output to a better exchange format for other applications, I am wondering if JSON would be a suitable format.
Thoughts?

This issue has been conflated with issue https://github.com/icsm-au/DynAdjust/issues/22 and repurposed as issue https://github.com/icsm-au/DynAdjust/issues/51


⚠ Fetchers has degraded performance

In 19ea9ce, Fetchers ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 285 ms

Resolved: Fetchers performance has improved in fb715ba.


Issues with dark mode inversions

First of all, thank you for your efforts!
I really like the minimal yet smooth design of this theme!
I want to convert my portfolio site (michaelfischer.at) to a static hugo site. It's a rather simple site but I need a carousel and a gallery with a lightbox. After a little bit of research I wanted to give hugo-shortcode-gallery a try. For the carousel I settled on plain HTML via rawhtml.
This led to 3 issues:

The contrast of the images in the carousel was reduced due to the double inversion in main.scss
The tumbnails from the shortcode-gallery were inverted because they also use the "filter" function for the blur effect
The lightbox of the gallery became white because it was inverted as well

I guess setting proper colors for the dark mode will be doubling the code base. I'm scratching my head but I can't think of another solution 🤔
/* --- Dark mode --- */

:root[data-theme="dark"] {
  background-color: #171717 !important;
  filter: invert(100%) hue-rotate(180deg) brightness(105%) contrast(85%);
  -webkit-filter: invert(100%) hue-rotate(180deg) brightness(105%) contrast(85%);
}
:root[data-theme="dark"] body {
  background-color: #FFF !important;
}
:root[data-theme="dark"] img,
:root[data-theme="dark"] video,
:root[data-theme="dark"] iframe,
:root[data-theme="dark"] body [style*="background-image"] {
  filter: hue-rotate(180deg) contrast(100%) invert(100%);
  -webkit-filter: hue-rotate(180deg) contrast(100%) invert(100%);
}
:root[data-theme="dark"] #dark-mode-toggle::before {
  /* Convert to .bi-sun */
  content: "\f5a2";
}

I was able to workaround the issue with the tweaks below. Certainly still work to be done but suffucient for my homepage. It's already online with your template!
/* --- Dark mode --- */

:root[data-theme="dark"] {
  background-color: #121212 !important;
  color: #e0e0e0 !important;
  --link-color: #bb86fc;
  --border-color: #333333;
  --button-bg-color: #1f1f1f;
  --button-text-color: #e0e0e0;
}
:root[data-theme="dark"] body {
  background-color: #121212 !important;
  color: #e0e0e0;
}

:root[data-theme="dark"] .navbar {
  background-color: #121212 !important;
  box-shadow: 0px 2px 20px 0px rgba(255, 255, 255, 0.08);
  color: #e0e0e0;
}

:root[data-theme="dark"] .nav-link, .navbar-brand {
  background-color: #121212 !important;
  color: #e0e0e0;
}

:root[data-theme="dark"] footer {
  background-color: #1a1a1a;
  border-top: 1px #3f3f3f solid;
}

:root[data-theme="dark"] #dark-mode-toggle::before {
  /* Convert to .bi-sun */
  content: "\f5a2";
}


Feature Suggestions

First of all thanks for making a useful tool for generating batch images for openpose models.
To me this is essential for creating consistent previews for the thousands of open pose files I have collected.
There are a few features I would love to see come to this tool.

Remember Previous settings
When I open the tool, I have to populate fields that never change such as the endpoint address. It would be nice to have these in a config file.

Option to not generate Text Files
I don't need to have txt files next to every generated image, it would be nice to have a checkbox to enable this if its wanted.

Output name format
My main use for this tool is to generate a preview of my open pose models, as such I want to have the filename between my model and my result match other than the ending. So that the files will be located next to each other.  Currently I have been using filename.pose.png and filename.preview.jpg.  It would be nice to have input on the output file name, or at least ability to move the word output to the end of the name.

Output file format
In my tens of thousands of AI generated files, I switched to primarily using JPG as it takes up 10x less space. I especially don't need preview files to be large. It would be nice to have the option to save the files as jpg.

Ability to just type in a prompt
In version 1 of this tool, I could just type in a prompt to output all of the images to.  Now it seems I need to create a folder and a text file to run a prompt. I think its cool that the tool can have a wildcard like feature.  But it would also be nice if there was just an option to type in a prompt.

Those are just my observations, take it or leave it.  Keep up the good work.  I look forward to trying future iterations.

@MrKuenning thanks for the suggestions! I have incorporated most of it in the current release :)

Awesome, it's working great!


Share Directory

Would it be possible to have a share current open directory command (each file in the directory)?

Hi there! How do you mean? You mean a hotkey for starting a new pairing session, or something else?
Currently any new file opened within the window will be synced across, although I'm soon to release changes where all files currently opened will be synced across.
Although are you referring to something different?

I think he means the current project. For example when you open a directory in Atom, you should be able to start a pairing session and sync all files over.
Of course, a huge drawback to this would be

Huge codebase
Library folders with a lot of dependencies like node_modules.

This could be prevented with an ignore file, e.g. .apignore with the same syntax as .gitignore. Which would require the collaborator to install any dependencies locally, without having to sync those dependencies over the wire.

fnky was spot on by what I meant. Right now it syncs all tabs opened, but it would be nice if you could sync every non-ignored file/folder with just one command / menu option (without having to open the file in a new tab).

Ahh I see - so by 'synced' do you mean the other person will have them open as soon as they join the session? Or they'll be able to save the files to disk?

By synced it will sync the open project folder—this could be an option to share either a single file or the whole workspace with all files open in sidebar.
I wonder how it would be able to sync on disk. If the session stopped—either by disconnect or lost connection—they files would be different (if either user changed them) that would mean the one sharing the session would only share his changes, and not keep the changes by the collaborator.
This could be avoided by uploading the files in the cloud, and sync the files from there—like Cloud9. I don't know wether Pusher would be able to handle that.

@fnky atom-pair already overcomes this issue with connection so I'm not sure that would be a big deal. The only issue I saw was an error: ' Uncaught TypeError: Cannot read property 'getTitle' of null
C:\Users\sancarn.atom\packages\atom-pair\lib\modules\session.coffee:151'. However this was only when a user opened a file, disconnected, changed a file, closed the file, reconnected.
The changes were still made though. I'm sure there is a way around the issue.

Hi @kn100,
I assume you are closing the issue because it is now implemented? If so, could you indicate how you share the current open directory?


The link specified on the index page cannot be redirected normally

navbar bug page, here is Stackblitz
index page's link cannot be redirected normally, but links specified on other pages can be accessed normally

At the same time, there is also a wrongly redirected link on the main page.
file is here
---
cta:
  - Record
  - /record
secondary:
  - Travel →
  - /trip
---

site is here

cta  can be accessed normally
secondary cannot be redirected normally


Add additional base layers behind feature flags

Purpose of this PR

Evaluate various base layers to improve labels and markers in rural, sub-urban and urban locations
QA to look at these various layers and decide if one meets our needs (TBD)
Write up an ADR on various solutions, benefits and costs (TBD)

Summary
This PR will compare 3 (of 12 possible) base maps from MapTiler (more on this later) in a sub-urban location around Birmingham, AL. These base maps are called:

streets
bright
voyager

Current
This is the current layer, does anyone know where they are? 😭

'Streets'
This is base map is a tad bit better, but labels are too light...

'Bright'
This one is nice? maybe?

'Voyager'
Again labels are too light...

One immediate issue with these is that the labels are fairly light. I haven't figured out how to control the lightness of non-prioritized CBTs (when in high zoom). I"m sure this is controlled by the front-end, however I'm not sure where it is yet. 🤔 .
Out of these my personal choice is 'Bright', however a more holistic QA is needed. QA can click on the links and it will open the latest staging link from this PR with the appropriate flags set.
There are redundant labels
There's another flag we can use ?flags=mt-bright,remove-label-layer#... to remove the labels layer. This can be seen here. The original labels seem to look more prominent, because they are added above all the other layers.
Details
Why not MapBox?
TBH, it wasn't until now, that I found where in the MapBox documentation this can be done. Need to investigate how to make this happen. The URLs Mikel had shared led me down a separate rabbit hole 🐰 , mostly because I didn't understand how the base maps were really working.
Other solutions

MapTiler
Geoapify (possible)

More on MapTiler
There are 13 possible base maps in MapTiler. Unfortunately, you have to be logged into their dev account to see it. The creds have been shared on the "bat-line". 😉 . Here's a screenshot of the others available:

I picked the 3 (streets, bright and voyager) that seem to look the best, IMO.
Costs of MapTiler
This really deserves a conversation on it's own however here's the screenshot of the plans:

We see the free tier offers about 100k requests per month. A single person zooming around the map and checking various locations can easily use up 20 - 100 requests. Not sure how to figure out if this is a good number, however this free tier seems common across commercial competitors (MapBox).
One advantage here also is that in the free plan we have access to custom maps. In the event that someone provides feedback to the map, we may be able to create a custom map and update it based on user feedback. This still needs to be investigated further on the 'how'.
More on Geoamplify
This service may provide everything MapTiler does. Still needs to be investigated:

Do their basemaps meet our need?
Is their basemaps better than MapBox and/or MapTiler?
Is their cost structure better than MapBox and/or MapTiler?

Next steps:

Understand what's going on with our dev pipeline and why are merges / deployments acting weird (links are delayed in showing actual content)
Have QA look into these base maps, discuss the lightness on high zoom and see if it's something that is good enough for now. Would love to schedule a time to work through each of the base maps in various locations and create a spreadsheet for the ADR.
Understand how to remove the white overlay on non-prioritized CBTs. One idea is to separate prioritized and non-prioritized into their own layers via the filter key. Just a guess!
Add more base maps from MapBox and possibly Geoamplify, behind flags and compare all results and write up ADR.
May need to approach Mikel on how to get similar raster maps from MapBox.

If you made it here, I appreciate you! ❤
Thx!
closes #995

Update
Still waiting to hear back from Mikel on possible MapBox solutions. There one base map doesn't have labels so it's not helping too much.
Here are some updated links to try out comparing the 2 base maps from MapTiler, namely, "streets" and "bright" (voyager is too light). All of these screenshots has the labels layer removed:
Streets
Lower 48
I feel the green mutes the prioritized color. Raising the prioritized opacity with make the labels underneath it harder to read.

Also we see some labels are repeated....
Removing label layer:

Sub-urban Birbingham, AL
Seems good. The one issue here is that the current border color between features is the same color as the rivers and oceans. If we decide to use this one, we may want to update that. Very easy to do now.

Bright
48
Having a white base layer, makes the prioritized color pop more

Sub-urban Birbingham, AL
Seems good

Taking votes!
Moving onto geoAmpify and pricing comparisons.


[core] use RubyDateTime directly to create a string

With Rails 6.1, there's no conversion to a Time anymore for a DateTime
if it's already UTC. So what happens is that we call #to_time where
we dind't before. Since Rails overrides that for DateTime to basically
do #getlocal, the result is off.
Using RubyDateTime directly avoids the problem and is faster anyway.

@dr-itz is this valid with 6.0 as well?  We have not branch 60-stable yet (although we could from this point forward).

@enebo it's valid, it just doesn't trigger with 6.0.0 yet. But the change that broke everything might get back-ported..


Inconsistencies in selection state

The top nav displays a muted gray background when selected. The sub-nav for blog posts displays the muted gray background when available for selection. This makes it difficult to understand the selection state. We need to be consistent here.

I agree that there is some overlap in different styles here.
Likewise, the active schema ToC item is also similarly grey highlight:

The original mocks for the top nav had a darker text for the active item:

I am reluctant to change the top nav item to resemble the subnav because I don't like the way those styles look if used up there:

I am happy to brainstorm further on ways to consolidate and reduce ambiguity however.


Change to use 3 valued bool for LocalDiskFlag

For addressing Tracker 126049889, basically, we want to set true to LocalDiskFlag if it's not specified in the deployment manifest.

@maximilien It's ready for review. Thanks.

@mattcui I think this is the hard way to do this. You can use: LocalDiskFlag     *bool      json:"localDiskFlag, omitempty"and since the default value forboolin Golang is false, the struct will havefalse` as default value.

I must be missing something, but this seems the wrong title and wrong code. Let's discuss. I cannot merge this.

As per our discussion, I will have a try with "String" type for LocalDiskFlag. Closing this PR, I will open a new one.


net: TestListenerClose failures with "Dial to closed TCP listener succeeded"

2020-04-27T15:50:54-70d9b72/linux-386-longtest
--- FAIL: TestListenerClose (0.00s)
    --- FAIL: TestListenerClose/tcp (0.00s)
        net_test.go:277: Dial to closed TCP listener succeeded.
FAIL
FAIL	net	29.631s

See previously #14124.
CC @mikioh @bradfitz @ianlancetaylor

greplogs --dashboard -md -l -e 'FAIL: TestListenerClose' --since=2020-04-28
2021-09-02T16:59:57-2a463a2/linux-amd64-longtest
2021-08-18T15:11:52-0c83e01/linux-s390x-ibm
2021-08-16T18:52:20-d35035f/linux-386-longtest
2021-05-05T01:48:39-caf4c94/openbsd-386-68
2021-04-30T16:17:01-cc02d59/linux-s390x-ibm
2020-12-29T20:35:10-b4a71c9/plan9-amd64-9front
2020-10-19T18:25:30-bb44c90/linux-386-longtest
2020-10-16T16:52:13-dfee333/linux-386-longtest
2020-10-01T21:06:35-507a88c/linux-386-longtest

greplogs --dashboard -md -l -e 'FAIL: TestListenerClose' --since=2021-09-03
2021-11-11T04:54:05-4b27d40/dragonfly-amd64
2021-11-04T02:38:03-747e4af/linux-amd64-longtest
2021-11-02T20:47:30-b246873/linux-386-longtest

greplogs --dashboard -md -l -e 'FAIL: TestListenerClose' --since=2021-11-12
2021-12-09T19:01:08-8ff254e/linux-amd64-staticlockranking
2021-12-07T18:58:57-4300f10/dragonfly-amd64

This test is failing with some regularity on builders for first-class ports (notably linux-386 and linux-amd64). To my mind, that makes it a release-blocker via #11811.
Either we should fix the net package to satisfy the expectations of the test, or we should fix the test to match the realities of the net package. (If nothing else, the failing check could be removed from the test without rendering it useless.)

Notably, this assertion begins with a time.Sleep for an arbitrary duration, and then asserts that a Dial call does not succeed:
https://github.com/golang/go/blob/f229e7031a6efb2f23241b5da000c3b3203081d6/src/net/net_test.go#L273-L279
If I understand correctly, the test does not (and cannot feasibly) ensure that the port is not simultaneously reused by some other test — or even some entirely different process! — on the system, since the TCP TIME_WAIT state only strictly applies to the four-tuple of (source address, source port, destination address, destination port). net.Dial specifies only the destination address and port, so a new listener may immediately be opened on the same address and port as long as it only accepts connections from new source addresses and/or ports. Thus, the Dial may spuriously succeed by connecting to an entirely new listener at the same port.


Switch to actor model

Stream_file interface is no longer capable of managing the complexity
Switch to Lwt
Things to work on

Blocking queue, implement using Lwt's mailbox, OCaml's queue, and a mutex lock

----------------------------------------------------
| MailBox | -> Queue (lock protected) -> | MailBox |
----------------------------------------------------

Concurrent progress text printing using Lwt
Adhere to zero-copy model for more things maybe

Encode module is now using actor-based concurrency using Lwt, and is ~50% slower...
Maybe I should move to Rust or wait a few years for multicore ocaml.

@darrenldl did you use profiling to discover where the bottleneck is?  OCaml can be reasonably fast if tweaked...  (sorry, I haven't read through your seqbox code)

@hannesm All good, the code's really rough atm anyway(still looks much better than the old code tho, albeit slower).
I did some testing with different data structures (flipping between Lwt_mvar and Lwt_queue)
(Lwt_queue is just a ring buffer implemented using array and condition variable)
But I didn't do proper profiling with tools, only relied on the progress text printing which reports the rate.
The current arrangement of the encoder internals
---------------               -----------               ---------------
| File reader | --Lwt_mvar--> | Encoder | --Lwt_mvar--> | File writer |
|             |     (1)       |         |     (2)       |             |
---------------               -----------               ---------------

The Lwt_queue variant is just Lwt_mvar with Lwt_queue swapped
Statistics (using defaults, this means data size = 496 bytes, hash = SHA256)

Implementation
Choice for (1)
Choice for (2)
Avg. encode rate blocks/sec

Sequential
N/A
N/A
105K

Lwt
Lwt_queue, size=100
Lwt_queue, size=100
63K

Lwt
Lwt_mvar
Lwt_queue, size=100
63K

Lwt
Lwt_mvar
Lwt_queue, size=1000
67K

Lwt
Lwt_mvar
Lwt_mvar
65K

Progress reporting text didn't seem to have any impact on the performance, so just I placed a call next to where the block is created in Lwt implementations.
Description
Sequential
The sequential implementation is just a single chain of tail positioned function calls.
Lwt
For Lwt implementation, each internal component in is made from a generating function (returns a function of type : unit -> something Lwt.t, e.g. gen_encoder at encode.ml, gen_file_reader, gen_file_writer at actors.ml).
The generated threads first wait on a waiter thread, then the waiter thread is woken up to kick start the encoding process.

My original intuition was that using Lwt would speed things up since the encoder doesn't have to wait for file IO, but that wasn't entirely right I suppose.
My guess is that since the sequential implementation was better optimized since it's just a statically written chain of tail position function calls, while a lot of anonymous functions are used in Lwt version implementation.
But I have almost zero background on compilers and language and runtimes, so I'm probably very wrong.
Currently I'm still very attached to OCaml rather than Rust mainly due to Coq, and also Rust doesn't support tail call optimization. If only Ada has a much larger FOSS community, hmm...

@hannesm I did more tests today with more useful results, namely disabling some code of encoder
The setup is still the same, with connections (1) and (2) both being Lwt_mvar, may switch back to Lwt_queue later for consistency but doesn't seem to matter
Statistics

Code disabled in encoder
Avg. encode rate blocks/sec

Hash & data packing
257K

Hash
76K

Data packing
112K

I noticed the data packing function(which converts 496 bytes of data to a sbx block) can be optimized, I'll post the results after optimization for both the sequential implementation and Lwt implementation.
The issue with delay in hashing and data packing may still persist since there's no way to run code in parallel yet. The hashing part was previously done in another actor, but it has the same level of performance, probably due to above reason.

After a lot of optimizations, the rate sits at around 90K blocks/sec
I'm gonna leave Reed-Solomon support to a Rust rewrite of osbx, if I am ever going to do that

Development effort now directed towards rsbx.
Osbx is now under maintenance mode.
Closing all issues related to adding features.


Service fails with filter parameter in REST call

When using the filter parameter in the REST calls to the API it very often fails with a 'BAD_REQUEST' error and status code 400 giving the message ’Input invalid’. This results in a very limited result list, where sometimes addresses, cadastres or the like is left out, which we consider a critical problem/blocker using the new version of the API.
It was not a problem in the previous version where filter was only available as a parameter in some of the ressources.

We are having trouble replicating the issue.
Could you provide more information?
How often do you experience the errors?
Can you provide timestamps?

I tried to reproduce the error by using this call several times, but could not reproduce the erorr.
https://api.dataforsyningen.dk/rest/gsearch/v1.0/husnummer?token=fd44f26ab5701c01ca9f570e507fe9ab&q=r&limit=10&filter=kommunekode='0153'
I suspect the error only occurs when calling several services at the same time.
I reproduced the error again on our own test site and this is the timestamp for the error;

We experience the error for approximately 1/4 of the calls

org.postgresql.util.PSQLException: ERROR: syntax error at or near "kommunekode"\n  Where: PL/pgSQL function api.husnummer(text,text,integer,integer) line 137 at RETURN QUERY [statement:"select (api.husnummer(:q, :where, 1, :limit)).*", arguments:{positional:{}, named:{q:7,limit:15,where:kommunekode = '0153'kommunekode = '0153'}, finder:[]}]

Called:
https://api.dataforsyningen.dk/rest/gsearch/v1.0/navngivenvej?q=7&limit=15&token=7030997b12f9e91e9da29f0c6e24a845&filter=kommunekode='0153'
Timestamp:
Thu, 25 May 2023 10:10:51 GMT
Error message:
org.postgresql.util.PSQLException: ERROR: syntax error at or near "ORDER"\n  Where: PL/pgSQL function api.navngivenvej(text,text,integer,integer) line 113 at RETURN QUERY [statement:"select (api.navngivenvej(:q, :where, 1, :limit)).*", arguments:{positional:{}, named:{q:7,limit:15,where:}, finder:[]}]

Called:
https://api.dataforsyningen.dk/rest/gsearch/v1.0/matrikel?q=7&limit=15&token=7030997b12f9e91e9da29f0c6e24a845&filter=kommunekode='0153'
Timestamp:
Thu, 25 May 2023 10:17:10 GMT
Error Message:
org.postgresql.util.PSQLException: ERROR: syntax error at or near "ORDER"\n  Where: PL/pgSQL function api.matrikel(text,text,integer,integer) line 121 at RETURN QUERY [statement:"select (api.matrikel(:q, :where, 1, :limit)).*", arguments:{positional:{}, named:{q:7,limit:15,where:}, finder:[]}]

Called:
https://api.dataforsyningen.dk/rest/gsearch/v1.0/postnummer?q=7&limit=15&token=7030997b12f9e91e9da29f0c6e24a845&filter=kommunekode='0153'
Timestamp:
Thu, 25 May 2023 10:17:10 GMT
Error message:
org.postgresql.util.PSQLException: ERROR: syntax error at or near "kommunekode"
Where: PL/pgSQL function api.postnummer(text,text,integer,integer) line 101 at RETURN QUERY [statement:"select (api.postnummer(:q, :where, 1, :limit)).*", arguments:{positional:{}, named:{q:7,limit:15,where:kommunekode = '0153'kommunekode = '0153'}, finder:[]}]

We have pushed an update.
Can you please test again and provide feedback if it has worked or not?

For you information we are trying to find a way to replicate the unintentional behavior, so we don't need to ask you every time to check if the problem is fixed. And hopefully faster can find what is causing the behavior.

It is really no problem.

I just tried to reduce it to only calling the matrikel resource and i can make several request in a row without causing any errors.
Adding husnummer so that I request results for both matrikel and husnummer at the same time makes it fail in some instances

Could I get you to test again?
We tried increasing the resources available for Gsearch.

We managed to replicate the error and identified where the issue is.
Hopefully we'll have a fix very soon.

I'm looking forward to that.

It should be fixed now. It was an issue with ogr.geotools encodeToString that shares memory between the different threads.
https://github.com/SDFIdk/gsearch/commit/2eb754c94b25646e377eaae65f9783a107ee0b74

It is working in our end now also. Thanks for quick response and fix.


Docker --env-file format not compatible with bash environment file format

Consider the following env variables in a file myvars.env
var1="something else"

var2=another thing

When you run source myvars.env , bash throws a error as it can't export var2 which has a space, and it throws the error (-bash: thing: command not found)
But when you export the same file using --env-file in docker, it is getting exported properly.
docker run --env-file myvars.env -d <image_name>
environment on the docker , shows the below values, which is not consistent with bash behaviour.
var1="something else"
var2=another thing
Whatever is "bash-compatible", is not docker compatible.
For the same example , if contents of myvars.env is
var1="something else"

var2="another thing"

When you source this file using bash, the value of these variables will be
bash-3.2$ echo $var1
something else
bash-3.2$ echo $var2
another thing

Whereas when you pass the same file to docker using --env-file, the value of these variables changes to:
root@2421a1853754:/# echo $var1
"something else"
root@2421a1853754:/# echo $var2
"another thing"

Notice, the double quotes in the latter value, both are NOT same values.
docker version
Client:
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Tue Apr 26 23:44:17 2016
OS/Arch:      darwin/amd64
Server:
Version:      1.11.1
API version:  1.23
Go version:   go1.5.4
Git commit:   5604cbe
Built:        Wed Apr 27 00:34:20 2016
OS/Arch:      linux/amd64

Please don't open multiple issues for the same thing. Discussion can happen on the other issue.
Thanks.

@cpuguy83 what is the other issue?

https://github.com/docker/docker/issues/26009


Create ContactTim

Feel free to contact me at<EMAIL_ADDRESS>

What is this?

Hello! brainartfu,
I wanted to send you my email address so that I could add you to ClickUp which I use for project management tasks. Hope that is ok?

Timothy

On Jan 13, 2023 at 4:44 PM brainartfu/breeze-chain-tipmeacoffee @.***> wrote:

What is this?
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


Excuse me, can I ask you for a data set in the paper?

We are deeply inspired by your paper, so we want to continue to do some work related to your paper and quote your paper. I would appreciate it if you could share your dataset.

Hi, the code that goes with the paper was just pushed. The dataset is available here : https://cloud.mines-paristech.fr/index.php/s/6ezipdmzj1uwPcW

thank you very much


Unit Member Tools

Adds the remaining end points for managing Unit Member Tools.
Adds Pact contract tests to ensure the results from the API are what the React front-end expects.

Involved adding a "State Server" docker container that is now used by both the integration tests and contract tests to reset the database.

Responses have been refactored to use ContentResult for most responses

This was done because contract tests expected certain headers that could not be set with the otherIActionResults we had been using.

Standardized on one set of JSON serializer rules in Models.Json.JsonSerializerSettings.
Adds some attributes to models to make sure the resulting JSON matches what is expected by the front-end.
Adds missing includes.
Improves tests to verify orphans aren't created in the database when relationships are broken/deleted.

@vbhupathi Yeah -- thanks for noticing that. Please add local.settings.json to the .gitignore.


didReceiveRemoteNotification is not being called

I have done all steps mentioned in the documentation (in app delegate), however the remote notifications are not being called back.
I have enabled the remote notifications in background mode and push notifications in general.
Please help
Thanks

Sorry, I didn't realize that it doesn't work in simulator. It works well on device.
Thanks and closing out,


Create a new release package

People are always having problems with the sn-tool, and only you can fix this @main--

https://www.nuget.org/packages/DemoInfo/


[Velox] soft affinity support placing duplicate reading to same executors

What changes were proposed in this pull request?
We add two APIs in Soft Affinity to implement the optimization of handling duplicate data reads by preferentially scheduling them on the same executor. This differs from the hash-based method in that it only sets the prefer location during repeated reads; the initial read is not affected by this. This approach reduces the observed uneven distribution of tasks caused by hash conflicts.
With the new APIs and spark events consumption, we obtain information about the relationships between partitions, RDDs, tasks, and executors. Eventually, we simplify this information into a mapping of partitions to executors. This allows us to determine which partition has been read on which executor. When duplicate partitions arrive, we can then allocate the corresponding tasks to the executor where the partition has been read as much as possible.
Its limitation is in assuming that the cache size will always be sufficient, and all reads will be cached. However, this assumption may not always hold true in practice.
How was this patch tested?
UT.
Velox cache enabled (mem only 8GB) + soft affinity: 9.7%.
Velox cache enabled (mem only 8GB) + soft affinity (duplicate reading detecting): 14.3%.
For details please see, https://github.com/oap-project/gluten/pull/4400#issue-2081288878

@baibaichen and @zhouyuan , could you help to review?
Thanks.

General ping, @zhouyuan and @baibaichen , thanks.

CC: @zzcclp

CC: @zzcclp

I will review later

LGTM

@zhli1142015 could you please also help to create one issue to track this patch?

===== Performance report for TPCH SF2000 with Velox backend, for reference only ====

query
log/native_4407_time.csv
log/native_master_02_23_2024_9ceade94a_time.csv
difference
percentage

q1
33.37
34.69
1.322
103.96%

q2
24.44
24.33
-0.110
99.55%

q3
37.94
38.86
0.920
102.42%

q4
37.52
36.08
-1.439
96.16%

q5
71.78
72.24
0.465
100.65%

q6
5.48
7.31
1.831
133.42%

q7
83.04
84.62
1.577
101.90%

q8
86.63
85.39
-1.237
98.57%

q9
119.36
124.53
5.174
104.33%

q10
43.22
44.23
1.009
102.34%

q11
20.07
19.94
-0.135
99.33%

q12
27.08
26.67
-0.403
98.51%

q13
45.06
44.33
-0.731
98.38%

q14
17.73
20.85
3.119
117.59%

q15
27.93
29.04
1.108
103.97%

q16
13.85
14.19
0.340
102.45%

q17
102.04
102.20
0.164
100.16%

q18
148.42
150.35
1.927
101.30%

q19
12.61
14.06
1.444
111.45%

q20
27.33
26.19
-1.143
95.82%

q21
229.62
226.58
-3.048
98.67%

q22
13.65
13.90
0.252
101.84%

total
1228.17
1240.58
12.405
101.01%


Release/1.0.4

@afmcdonald yes, these need to be merged, and we hadn't forgot about this, but it's just been delayed.  Thanks for calling this out!
Looks like this will need to be hand merged because of a conflict (probably a submodule commit).
Also we'll need to do the same for couchbase-lite-java-core.

We merged release/1.0.4 commit by commit.

https://github.com/couchbase/couchbase-lite-java-core/issues/553
https://github.com/couchbase/couchbase-lite-android/issues/567


Docs: create a content/ path

Prevents this error:
> phenomic start

⚡ Hey! Let's get on with it
✨ Open http://localhost:3333
events.js:160
      throw er; // Unhandled 'error' event
      ^

Error: resolve_projpath: path `/Users/rsc/Projects/phenomic/content` does not exist
    at BunserBuf.<anonymous> (/Users/rsc/Projects/phenomic/node_modules/fb-watchman/index.js:95:23)
    at emitOne (events.js:96:13)
    at BunserBuf.emit (events.js:188:7)
    at BunserBuf.process (/Users/rsc/Projects/phenomic/node_modules/bser/index.js:292:10)
    at /Users/rsc/Projects/phenomic/node_modules/bser/index.js:247:12
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

@rstacruz we actually made this optional at #1068


Need package/description check for UWP exports in can_export()

Godot version: Godot 3.2.1.stable Windows 64 (non-mono)
OS/device including version:
Microsoft Windows [Version 10.0.19041.207] (build 2004) 64bit
Issue description:
When creating a new export configuration for UWP, there are a number of fields that are indicated as required or invalid before you can export. Currently there is a discrepancy between these checks and reality, where you can not install a signed APPX file if the description length is 0. Therefore, there should be an additional check added to platform/uwp/export/export.cpp:can_export() that checks that the "package/description" field length is greater than zero.
Steps to reproduce:

Create a do nothing project with a single node scene. Create an export configuration that satisfies all the settings while keeping the description blank.
Export UWP/APPX
Sign the APPX with signtool as indicated by the Godot documentation
Install the APPX via Powershell: Add-AppxPackage C:\path\project.appx

This description requirement can be seen enforced (via XML schema verification) in the Powershell Add-AppxPackage cmdlet:
Add-AppxPackage : Deployment failed with HRESULT: 0x80080204, The Appx package's manifest is invalid.
error 0xC00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 19, Column 147,
Reason: '' violates minLength constraint of '1'.
The attribute 'Description' with value '' failed to parse.
NOTE: For additional information, look for [ActivityId] 25eed3ef-1376-0005-5d5c-81267613d601 in the Event Log or use
the command line Get-AppPackageLog -ActivityID 25eed3ef-1376-0005-5d5c-81267613d601
At line:1 char:1
+ Add-AppxPackage C:\projects\playground\NullProject\NullProject.appx
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (C:\projects\pla...ullProject.appx:String) [Add-AppxPackage], Exception
    + FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand

@crazychenz @calinou => it will be great to get the latest update the feasibility to export UWP in 3.2.2. Is there a plan? when will that be possible? Is there someone allocated to work on UWP?

@GeorgeS2019 The UWP export barely gets any testing and maintenance due to lack of manpower. As far as I know, there is no dedicated maintainer for it.

@Calinou @akien-mga  This is the impression I have. However, since many new guys who have not followed the story of UWP since e.g. May 2019, they wasted their time.
However, occasionally we have some recent effort in this area (e.g. UWP for ARM, make sense for Hololens 2.0), it is unclear HOW COMMITTED are we into delivering UWP for ARM. We need to have a clear message, because next two to three weeks, it is the best time to update Microsoft that Godot is on track to support hololens eventually  (Especially @NeoSpark314 of Godot Discord) just delivered a PoC on Mixed Reality Capture using Oculus Quest.
A new development that will surely attract further Microsoft commitment to Godot.

@crazychenz  please check if this recent UWP export experience address your issue

I was looking into this, and need some advice on something. Getting the description length check in is easy enough, but it seems that many of the manifest rules are currently not being enforced. Most of the names have min and max length requirements, and there are some that have specifications specific to their individual entry in the manifest (such as only allowing alpha-numeric characters). Do we want to enforce those rules as well, or is the focus specifically to notify users that they need something in their package/description box?

I was looking into this, and need some advice on something. Getting the description length check in is easy enough, but it seems that many of the manifest rules are currently not being enforced. Most of the names have min and max length requirements, and there are some that have specifications specific to their individual entry in the manifest (such as only allowing alpha-numeric characters). Do we want to enforce those rules as well, or is the focus specifically to notify users that they need something in their package/description box?

I think we should try to enforce all rules directly in the Export dialog to avoid mistakes.


HDDS-6145. Include docker-compose output in acceptance test output.log

What changes were proposed in this pull request?
Fix the problem that acceptance test output.log does not include container start/stop messages from Docker Compose.
https://issues.apache.org/jira/browse/HDDS-6145
How was this patch tested?
Verified output.log in acceptance artifacts:
https://github.com/adoroszlai/hadoop-ozone/actions/runs/1638682309

Thanks @sodonnel for the review.


DRILL-8282: Bump Hadoop-Common Version to 3.2.4 (CVE)

Description
There is a CVE fix in hadoop 3.2.4
Documentation
(Please describe user-visible changes similar to what should appear in the Drill documentation.)
Testing
(Please describe how this PR has been tested.)

@jnturton Are we good to merge this?

We also need to update hadoop.dll and winutils.exe.


Moving to uselagoon

We plan to move aergia into the uselagoon organization and deploy as part of the lagoon-remote chart installation.
We're evaluating what needs to be done to make this happen properly

Since there have been no comments on this, I think it's safe to say that the move will happen.

This has moved to the uselagoon organization now.
There will be further work in the future to change the domain used in labels from amazee.io to lagoon.sh but will be called out in release notes etc when the change occurs


Don't map & unmap memory every frame.

This is actually not necessary, especially for the buffers you are updating every frame. It is not cheap to map/unmap, best to map at the start and leave it until shutdown.

Fixed in vkguide 2


ILoggerFactory hard to inject in APS.NET Core

Current implementation of AddDynatraceExporter has ILoggerFactory as input parameter - in sample console app it is easy to use but in ASP.NET Core app having ILoggerFactory in configuration phase is hard to implement. It would be better to get ILogger from container.

Hi Dominik!
In 2022, we introduced an OTLP Metrics ingest endpoint in Dynatrace, which makes this exporter here obsolete, as any OTel SDK and the collector can natively export to it out of the box.
You can find more details here:

https://docs.dynatrace.com/docs/shortlink/send-metrics-via-otlp-exporter
https://docs.dynatrace.com/docs/shortlink/migrating-dynatrace-metrics-exporter-otlp-exporter

This exporter is deprecated in favor of the OTLP metrics ingest and as such no new features will be implemented.


Middleware RFC

Paying special attention to 0d8dbf8, I've added middleware functionality. PTAL @michaelbausor and @dwsupplee

Also see cabc2ac for removing ApiCallable all together 👍  I'm really liking this, I hope you agree!

👏 this is looking awesome. Will have some time to do a full review soon!

Codecov Report

Merging #109 into master will decrease coverage by 2.6%.
The diff coverage is 69.2%.

@@            Coverage Diff             @@
##           master     #109      +/-   ##
==========================================
- Coverage   90.03%   87.42%   -2.61%
==========================================
  Files          32       40       +8
  Lines        2238     2283      +45
==========================================
- Hits         2015     1996      -19
- Misses        223      287      +64

Impacted Files
Coverage Δ

src/LongRunning/OperationsGrpcTransport.php
0% <0%> (ø)

src/Grpc/GrpcUnaryCall.php
0% <0%> (ø)

src/Grpc/GrpcServerStream.php
100% <100%> (ø)

src/Middleware/LongRunningMiddleware.php
100% <100%> (ø)

src/Middleware/PageStreamingMiddleware.php
100% <100%> (ø)

src/Grpc/GrpcBidiStream.php
95.23% <100%> (ø)

src/Testing/MockUnaryCall.php
100% <100%> (ø)
:arrow_up:

src/Page.php
98.14% <100%> (ø)
:arrow_up:

src/Grpc/GrpcClientStream.php
100% <100%> (ø)

src/CallStackTrait.php
100% <100%> (ø)

... and 19 more

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 94c4cf5...1361705. Read the comment docs.

This is now tracked in the branch json-transport and #113


What is the benchmark unit?

Can you refine the test setup of following benchmark wiki:
https://github.com/alibaba/druid/wiki/Benchmark_aliyun

what is the unit?
lower the better?
how did you setup your benchmark?
benchmark codes for proving fairness of the benchmark results?

https://github.com/alibaba/druid/blob/master/src/test/java/com/alibaba/druid/benckmark/pool/Case1.java


chore: add groundwater level property to cpt

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

2 of 2 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 87.256%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
938

Relevant Lines:
1075

💛  - Coveralls


add macros: only_controller and only_proxy

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.009%) to 63.838%

Totals

Change from base Build<PHONE_NUMBER>:
0.009%

Covered Lines:
4567

Relevant Lines:
7154

💛  - Coveralls


Clean up all TODOs in the Module

During PTR coding a lot of TODOs were made as a stopgap until spelldata was added, or just adding PTR flags. Once 8.1 goes live these should all be fixed/removed.

Fixed void torrent hard coded insanity: https://github.com/simulationcraft/simc/commit/8fe2d08da5c7f9f2e95238be34bcc6edef00dbc6


Metrics: path definition fails

I try to read out a Home Automation API. It has about 300 devices connected. Direct access of the api brings back something like:
[
  {
    "id": 1,
    "name": "zwave",
    "roomID": 0,
    "type": "com.fibaro.zwavePrimaryController",
    "baseType": "",
 ...
      "setSipUserID": 1,
      "setSipUserPassword": 1
    },
    "created":<PHONE_NUMBER>,
    "modified":<PHONE_NUMBER>,
    "sortOrder": 2
  },
  {
    "id": 3,
    "name": "Wetter",
    "roomID": 7,
...

With a defined metric
metrics:
- name: temperature_devices
  type: object
  help: Devices of HC2 with temperature mesurement
  path: '{$[0:310]}'
  labels:
    id<EMAIL_ADDRESS>    type<EMAIL_ADDRESS>    name<EMAIL_ADDRESS>  values:
    id<EMAIL_ADDRESS>
the exporter brings back all devices:
# HELP temperature_devices_id Devices of HC2 with temperature mesurement
# TYPE temperature_devices_id untyped
temperature_devices_id{id="1",name="zwave",type="com.fibaro.zwavePrimaryController"} 1
temperature_devices_id{id="100",name="UG Az - Rollanden",type="com.fibaro.FGRM222"} 100
temperature_devices_id{id="101",name="UG Az - Steuerung",type="com.fibaro.remoteController"} 101
temperature_devices_id{id="102",name="UG Az - Heizung",type="com.fibaro.zwaveDevice"} 102
temperature_devices_id{id="103",name="UG Az - Heizung",type="com.fibaro.setPoint"} 103
temperature_devices_id{id="104",name="UG Az - Termometer",type="com.fibaro.temperatureSensor"```

If I change the path to
path: '{$[]}'      the exporter isn't working
path<EMAIL_ADDRESS>== "107")]}' the exporter won't do it too.
So the filtering and unlimited requests seems not to work.
I attached the test data.json to the case.

Based on jsonpath syntax $[] does not match anything.
I think what you want to iterate over all is $[0:] but this is in your case pretty much same as $
$[?(@.id=='107')] would be right syntax for special ID
you can use a evaluator like https://jsonpath.com/

The case is solved.
The error messages aren't meaningful. Labels have to fulfill the task of a primary key for the value: It's not allowed to have two or more values with exactrly the same labels. If that isn't given, the exporter will report an error that a value has the wrong type.
---
metrics:
- name: fibaro_temperature
  type: object
  help: Devices of Fibaro HC2 with temperature mesurement
  path<EMAIL_ADDRESS>== "com.fibaro.temperatureSensor")]}'
  labels:
    id<EMAIL_ADDRESS>    name<EMAIL_ADDRESS>    room<EMAIL_ADDRESS>  values:
    value<EMAIL_ADDRESS>
works fine now.


Assertion failed!
You can cause the issue again any time by clicking the Refresh button

this was in the debug.log:
[1122/192602.591:ERROR:directory_reader_win.cc(43)] FindFirstFile: The system cannot find the path specified. (0x3)

Seems like a native module issue. Could you please provide your Windows version?

Windows 10 Pro 64-bit, version 1909 build 18363.1198


Instagram Hashtag url configuration

Configured the Instagram hashtag url to be - explore/tags/ . For example an instagram tag page can be reached at - https://instagram.com/explore/tags/catsofinstagram/

@dejoe thanks for this!
Could you please add a test to cover this scenario? Currently, the Instagram-related tests only cover linkifying mentions. Let's extend that to hastags too!


[Bug] Cannot navigate with keys in the datasources suggestion for API pane

Can store add multiple datasources and see if you still see this? Mostly it seems to be an issue with highlighted state not being very obvious

Lol yes I have no idea which one is selected.

@aakashDesign Can you re-look at the colour scheme here?


Can't build tensorflow from source with docker image

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Mint 19.3
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): Source
TensorFlow version (use command below): 2.2.0
Python version: 3.6.9
Bazel version (if compiling from source): 3.0.0
GCC/Compiler version (if compiling from source): 7.5.0
CUDA/cuDNN version:
GPU model and memory: Nvidia RTX 2060 (Laptop), 6GB
-Driver Version: 440.59
Exact command to reproduce:
Docker version: 19.03.09
Nvidia Container Toolkit: installed and tested
Commands:
docker pull tensorflow/tensorflow:devel-py3
docker run -it -w /tensorflow_src -v $PWD:/mnt -e HOST_PERMS="$(id -u):$(id -g)"
tensorflow/tensorflow:devel-py3 bash
Within the container:
git pull
./configure
bazel build --config=opt --verbose_failures //tensorflow/tools pip_package:build_pip_package

Describe the problem
I tried to build tensorflow from source with docker.
I strictly followed the instructions from the tensorflow website, but the build is never successfull and i get an internal compiler error.
I tried it with and without Cuda support, always fails.
Source code / logs
tf_build_errors.txt

@robkuehl
Please refer to these issues with similar error message.
#23401 #23765 link

@robkuehl
Please refer to these issues with similar error message.
#23401 #23765 link

Issues don't seem related as neither of the others appeared using the docker image or am I wrong?

gcc: internal compiler error: Killed (program cc1plus)
It's very likely that the docker container ran out of RAM during compilation. Limiting Bazel's memory usage  might be able to help, e.g. --local_ram_resources=2048.

gcc: internal compiler error: Killed (program cc1plus)
It's very likely that the docker container ran out of RAM during compilation. [Limiting Bazel's memory usage ]https://www.tensorflow.org/install/source#bazel_build_options) might be able to help, e.g. --local_ram_resources=2048.

Tried it but still fails. I tried to include the whole output of bazel but the filesize was about 50MB. I hope the following reduced version is enough.
bazel_build_bug_report.txt

Any chance I get further help on this issue?

@angerson
Tried to build using docker using a quarter of the total resources. Build failed with the following error:
ERROR: /repo/tensorflow/compiler/mlir/tensorflow/BUILD:411:15: C++ compilation of rule '//tensorflow/compiler/mlir/tensorflow:tensorflow_ops_n_z' failed (Exit 4): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 111 argument(s) skipped)
gcc: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
ERROR: /repo/tensorflow/lite/python/BUILD:55:10 C++ compilation of rule '//tensorflow/compiler/mlir/tensorflow:tensorflow_ops_n_z' failed (Exit 4): gcc failed: error executing command /usr/bin/gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections ... (remaining 111 argument(s) skipped)
INFO: Elapsed time: 2011.170s, Critical Path: 631.06s
INFO: 1083 processes: 155 internal, 928 local.

@robkuehl ,
Can you please try to install the latest tf v2.5 or v2.6 and let us know if the issues still persists.Thanks!

--jobs 1 --local_ram_resources=2048 maximizing available memory during compilation helped in my case.


Change all links to https

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added/updated (for bug fixes/features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Chore
What is the current behavior? (You can also link to an open issue here)
Links to https://sass-guidelin.es/ use http format.
What is the new behavior (if this is a feature change)?
Links to https://sass-guidelin.es/ use https format.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Other information:
None.

Thank you so much. 😊


1:10: UX test plan for  early January

As a user of this form, I would like to have a clear and accessible form (and process) that allows me to submit my compliant.

UX Plan