Querying a column of Guid type

Which service(blob, file, queue, table) does this issue concern?
Table
Which version of the Azurite was used?
3.17.1
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
14.4.0
What problem was encountered?
When querying for a record with a column of Guid type w/o specifying the keyword guid in front of the value, Azurite returns the record where the real Storage Table would not.
Steps to reproduce the issue?
Step 1
Create a table with a custom column named InstructionId with Guid values in it.

Step 2
Write a value of a Guid type into the table

Step 3
Query for the item using the PartitionKey and the column value w/o using the guid keyword.
Guid instructionId = someGuidValue;
var pages = client.QueryAsync<TableEntity>($"PartitionKey eq '{userIdDeviceIdCompositeKey}' and InstructionId eq '{instructionId}'", maxPerPage: 1);

Assuming the table contains the record, Azurite will return it.
The real storage account will not. To make it work with the real storage account, the following query must be used:
Guid instructionId = someGuidValue;
var pages = client.QueryAsync<TableEntity>($"PartitionKey eq '{userIdDeviceIdCompositeKey}' and InstructionId eq guid'{instructionId}'", maxPerPage: 1);

Note the InstructionId eq guid'{instructionId}'
Have you found a mitigation/solution?
No

This is a bug. cc @blueww

TableClient.CreateQueryFilter will convert a string based query filter to its escaped format. We have a sample to illustrate this. However, we might be able to have this happen automatically if a FormattableString is passed to the Query method.
BTW, here's the sample for TableClient.CreateQueryFilter https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/tables/Azure.Data.Tables/samples/Sample4QueryEntities.md#odata-formatted-string

@christothes appreciate the info but Azurite behavior is not related to how the query is formatted. Azurite should adhere to what the real service does.

Thanks for raising this.
Agreed, we are aiming for service behaviors rather than documented behavior.
I am working on several related issues to entity types and querying.
I shall roll this up into that work.

@edwin-huber, could you assign this issue to the appropriate milestone to know when this fix goes out? Thank you.

@blueww & @XiaoningLiu approved changes are checked into main, can you help with flagging this for a milestone / release?
Thanks.

@SeanFeldman , @edwin-huber , @XiaoningLiu
We should have a planned release in the middle of Jan,2023.

The release is already out: https://github.com/Azure/Azurite/releases/tag/v3.21.0


map-symbolic-tests: updated lookup, inkeys and remove specs to have an explicit RHS

This needs to be updated.


Feature GUI simplification

In recent days I saw 7-9 SD GUI variations. Also, there are discussions about «right» prompts, styles, and differences from Dall-E2.
Dall-E to me is a one-button thing: overall quality is poor (on July at least), no settings, but it is better «understands» what you mean.
On the other hand is SD: too many options, samplers, better quality (to me) and variety, but  it needs to set it up for better results. Poor results with too many objects in prompt though. SD’ learning curve is way too long. This is a problem with many opensource products.

I think some of the samplers available for SD are better for some purposes. Like Keuler-A is better for paintings, results are very similar to Dall-E’s with «oil painting» and artists' names tags. Some of them really don't need to be generated at a steps greater than 30-50, so it will optimize render time. Maybe you already know what is the best results with different art styles for each sampler? So in near future we can use it automatically or just propose the best sampler and options depending on tags used?
Users don’t need a large number of options in GUI, just good results. We already know (a little, for example) which tags affect images and in what way (more here). Maybe in future realeses we can add popular tags in categories and propose tags as user type in?
Relationship between prompt and image is very random. As a designer, I want the result to be predictable. To simplify this right now, we can add links to some researches available, and in future add examples for some tags and art styles (like promptomania and others). Maybe even edit prompts for better suiting tags, similar to user ones (like, «anime art» doesn’t work well, so use «by studo ghibli» instead). Is it possible?
I think of «advanced options» button for all of them, but in most cases I need prompt like «something in some place, with some additions, in that style». So maybe it is possible to make a few prompt templates for arts, landscapes, portraits, 3d, concept-arts, etc.

All of this will allow us to keep GUI clean and simple, and it will save users' time. I'm not urging you to drop everything and do it, there are more important things right now, of course.

@psychedelicious, some ideas for the future gui. Otherwise, I’m afraid, the interface will drown in buttons and options.


👷 Support Snake function & Replace Model with Helper

Codecov Report

Merging #4 (068a5d9) into main (0857fd3) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@           Coverage Diff            @@
##            main      #4      +/-   ##
========================================
- Coverage   1.08%   1.02%   -0.06%
========================================
  Files         11      12       +1
  Lines        370     390      +20
========================================
  Hits           4       4
- Misses       366     386      +20

Impacted Files
Coverage Δ

pydanticORM/generator/_crud.py
0.00% <0.00%> (ø)

pydanticORM/handler/__init__.py
0.00% <0.00%> (ø)

pydanticORM/handler/helper.py
0.00% <ø> (ø)

pydanticORM/handler/snake.py
0.00% <0.00%> (ø)

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 0857fd3...068a5d9. Read the comment docs.


No template for running query

Hello,
first try with 2.0 alpha. I just do a lpless "my file.linq"  an get a "No template for running query"
What does it mean ?
thanks

Have a look at #27.

Closing as duplicate of #27.


Allow for speed less than 5 ms

Sometimes you just want your code to run as fast as possible. Even at 5 ms computing the Taylor series for atan to 64 terms (don't ask) takes around 2 minutes.

Yep, Esolang Park is a pretty slow experience if you just want to run some code without any frills. The execution interval is currently limited to at or above 5ms because the React render takes quite a lot of time as compared to the execution time. This is also mentioned in the wiki in a bit more detail.
A possibly better solution than the one mentioned in the wiki is to rework how messages from the message queue are processed. If we perform batch processing of messages say every 50 ms (or atleast debounce the visualization rerender), it will allow us a very comfortable window to re-render almost anything we want. This is off the top of my head though - there may be some blockers here regarding how the editor highlights and code output are updated on message processing. But I think this should be feasible.
Let me see if I can take a look at this on the weekend.

Okay, this is trickier than I thought. Removing the sleep() call on the execution controller side will cause the while-loop to block processing of messages from the main thread - meaning pause and stop actions won't work. And keeping a sleep(0) adds too much event-loop overhead - it's not much faster than 5ms.

The execution interval input now allows 0ms as input. @Seggan How long does your program take to execute on this setting?

The execution interval input now allows 0ms as input. @Seggan How long does your program take to execute on this setting?

Around a second for 64 iterations now! Thank you so much! It's so much less painful now!


HelmRelease reconciliation failed: failed to get last release revision

I am getting a HelmRelease reconciliation failed: failed to get last release revision. I followed this command:
gitops create dashboard ww-gitops \
  --password=$PASSWORD \
  --export > ./clusters/my-cluster/weave-gitops-dashboard.yaml

Environment

Weave-Gitops Version: 0.24.0
Flux Version: 2.1.0
Kubernetes version: 1.27

To Reproduce
Steps to reproduce the behavior:

Type:

gitops create dashboard ww-gitops \
  --password=$PASSWORD \
  --export > ./clusters/my-cluster/weave-gitops-dashboard.yaml

Commit it in the repository
Reconcile the git, then the flux-system kustomization, then reconcile the helm release.
See error

Expected behavior
The reconcilation of helm release will be ready.
Actual Behavior
HelmRelease reconciliation failed: failed to get last release revision
Additional Context (screenshots, logs, etc)

Hey @UGS-DanielSoriano thank you for reporting this. Is this still an issue? We had some issues yesterday when we created a new release of Weave GitOps and it's likely that you were affected by that, if you got this error yesterday. However, it should be fine now with v0.31.2, can you confirm if this has been resolved?

Hey @yiannistri, I retried it and there is a new error. Here is what I am getting.
helm-controller  reconciliation failed: Helm install failed: rendered manifests contain a resource that already exists. Unable to continue with install: could not get information about the resource ClusterRole "wego-admin-cluster-role" in namespace "": clusterroles.rbac.authorization.k8s.io "wego-admin-cluster-role" is forbidden: User "system:serviceaccount:flux-system:dashboard" cannot get resource "clusterroles" in API group "rbac.authorization.k8s.io" at the cluster scope

There may still be some resources installed in your cluster, from the previous (failed) attempt to install Weave GitOps. You can try removing the Weave GitOps HelmRelease resource from your Git repo (comment it out so that Flux doesn't interfere), then use kubectl to remove any remaining Weave GitOps resources that may still be present in your cluster. Then try adding the HelmRelease resource back and see if that works.

I tried to remove it and check the cluster if there are weave gitops resources, then add it back again but it still the same error. Btw I followed this to create RBAC for the HelmRelease since we have Multi-Tenancy Lockdown in the kustomization. I am not sure if there are missing rules for the Role of something? since the service account attached to the HelmRelease "system:serviceaccount:flux-system:dashboard" cannot get resource "clusterroles" in API group "rbac.authorization.k8s.io" at the cluster scope based on the error, but it is not included in the documentation so I am not really sure.

Yeah, I think we may be missing some rules. I'll attempt to reproduce this using the Flux RBAC guide you've linked and report back.

Apologies for the slow response, I plan to take a look at this, this evening.

Hi @yiannistri, may we follow up on this please?

Hey @UGS-DanielSoriano I was able to reproduce this error. I'm now tweaking the role rules to see if that fixes the permission error.

Hey @UGS-DanielSoriano, I've managed to get the Weave GitOps Helm release installed with a service account, without errors. Here's what I used (tested installation on a kind cluster bootstrapped with Flux):
apiVersion: v1
kind: Namespace
metadata:
  name: weave-gitops
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: weave-gitops-reconciler
  namespace: weave-gitops
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: weave-gitops-reconciler
rules:
  - apiGroups: [""]
    resources: ["users", "groups"]
    verbs: ["impersonate"]

  - apiGroups: [""]
    resources: ["namespaces"]
    verbs: ["get", "list", "watch"]

  - apiGroups: [""]
    resources: ["secrets"]
    resourceNames: ["cluster-user-auth", "oidc-auth"]
    verbs: ["get", "list"]

  - apiGroups: ["rbac.authorization.k8s.io"]
    resources: ["clusterroles"]
    verbs: ["get", "create"]

  - apiGroups: ["rbac.authorization.k8s.io"]
    resources: ["clusterrolebindings"]
    verbs: ["get", "create"]

  # The following permissions are required by Weave GitOps during runtime - They are defined in ClusterRole "wego-admin-cluster-role"
  - apiGroups: ["*"]
    resources: ["*"]
    verbs: ["get", "list", "watch"]

  - apiGroups: ["source.toolkit.fluxcd.io"]
    resources: ["buckets", "gitrepositories", "helmcharts", "helmrepositories", "ocirepositories"]
    verbs: ["patch"]

  - apiGroups: ["helm.toolkit.fluxcd.io"]
    resources: ["helmreleases"]
    verbs: ["patch"]

  - apiGroups: ["kustomize.toolkit.fluxcd.io"]
    resources: ["kustomizations"]
    verbs: ["patch"]

  - apiGroups: ["infra.contrib.fluxcd.io"]
    resources: ["terraforms"]
    verbs: ["patch"]

  - apiGroups: ["image.toolkit.fluxcd.io"]
    resources: ["imagepolicies", "imagerepositories", "imageupdateautomations"]
    verbs: ["patch"]

  - apiGroups: ["notification.toolkit.fluxcd.io"]
    resources: ["alerts", "providers"]
    verbs: ["patch"]

  - apiGroups: ["apiextensions.k8s.io"]
    resources: ["customresourcedefinitions"]
    verbs: ["list", "watch"]
  # end
---
apiVersion: rbac.authorization.k8s.io/v1
kind: Role
metadata:
  name: weave-gitops-reconciler
  namespace: weave-gitops
rules:
  # last release revision, "cluster-user-auth"
  - apiGroups: [""]
    resources: ["secrets"]
    verbs: ["get", "list", "create"]

  - apiGroups: [""]
    resources: ["services"]
    verbs: ["get", "create"]

  - apiGroups: ["apps"]
    resources: ["deployments"]
    verbs: ["get", "create"]

  - apiGroups: ["networking.k8s.io"]
    resources: ["networkpolicies"]
    verbs: ["get", "create"]

  - apiGroups: [""]
    resources: ["serviceaccounts"]
    verbs: ["get", "create"]

  - apiGroups: ["rbac.authorization.k8s.io"]
    resources: ["roles"]
    verbs: ["get", "create"]

  - apiGroups: ["rbac.authorization.k8s.io"]
    resources: ["rolebindings"]
    verbs: ["get", "create"]

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: weave-gitops-reconciler
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: weave-gitops-reconciler
subjects:
  - kind: ServiceAccount
    name: weave-gitops-reconciler
    namespace: weave-gitops
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  name: weave-gitops-reconciler
  namespace: weave-gitops
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: weave-gitops-reconciler
subjects:
  - kind: ServiceAccount
    name: weave-gitops-reconciler
    namespace: weave-gitops
---
apiVersion: source.toolkit.fluxcd.io/v1beta2
kind: HelmRepository
metadata:
  annotations:
    metadata.weave.works/description: This is the source location for the Weave GitOps
      Dashboard's helm chart.
  labels:
    app.kubernetes.io/component: ui
    app.kubernetes.io/created-by: weave-gitops-cli
    app.kubernetes.io/name: weave-gitops-dashboard
    app.kubernetes.io/part-of: weave-gitops
  name: weave-gitops
  namespace: weave-gitops
spec:
  interval: 1h0m0s
  type: oci
  url: oci://ghcr.io/weaveworks/charts
---
apiVersion: helm.toolkit.fluxcd.io/v2beta1
kind: HelmRelease
metadata:
  annotations:
    metadata.weave.works/description: This is the Weave GitOps Dashboard.  It provides
      a simple way to get insights into your GitOps workloads.
  name: weave-gitops
  namespace: weave-gitops
spec:
  serviceAccountName: weave-gitops-reconciler
  chart:
    spec:
      chart: weave-gitops
      sourceRef:
        kind: HelmRepository
        name: weave-gitops
  interval: 1h0m0s
  values:
    adminUser:
      create: true
      passwordHash: $2a$10$LL.UVzwbSlr7J9W5lTvZvOpgB5zEGepC9djTd69FwTZriANUSHJHO
      username: admin

I have assumed that you want the minimum set of permissions required for the default installation, which includes the need to create cluster roles/cluster role bindings.
Hope this helps, let me know if you have any more questions.

It works! thanks @yiannistri


I'm not able to open database from Google Drive

For some reason, not all the files and folders are listed after I have added my account. I had to restrict permissions to not share the folder to have it appear in the list.

When I try to open a file from the folder it shows me a popup that tells: "Failed to load the specific file!". I'm an owner of both file and folder.

Releases v2.0.0 today.
Please test it with this version. If you problem still appears, please re-open this issue.


2021.1.0b0 error

I know you will be THRILLED to hear this but the latest beta has broken this again. Seems the same error as previously - I wonder if they reverted a PR?
2020-12-31 09:04:59 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Greater Sydney Region for nsw_rural_fire_service_fire_danger
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 236, in async_setup
result = await component.async_setup_entry(hass, self) # type: ignore
File "/config/custom_components/nsw_rural_fire_service_fire_danger/__init__.py", line 82, in async_setup_entry
manager = NswRfsFireDangerFeedEntityManager(hass, config_entry)
File "/config/custom_components/nsw_rural_fire_service_fire_danger/__init__.py", line 118, in __init__
self._rest = RestData(
TypeError: __init__() missing 1 required positional argument: 'verify_ssl'

Quick analysis indicates that this issue was introduced with https://github.com/home-assistant/core/pull/43877 where a new parameter was addded to RestData's constructor.
I'll have a look how to best fix this custom component...

Fixed in v0.6

Fixed in v0.6

Thanks mate...

Thanks mate...


Update Composer dependencies (2021-11-12-00-10)

Visual regression test passed!
View the visual regression test report


Ftrack: rewriting component creation to support multiple thumbnails

Changelog Description
The creation of Ftrack components needs to allow for multiple thumbnails. This is important in situations where there could be several reviewable streams, like in the case of a nuke intermediate files preset. Customers have asked for unique thumbnails for each data stream.
For instance, one stream might contain a baked LUT file along with Display and View. Another stream might only include the baked Display and View. These variations can change the overall look. Thus, we found it necessary to depict these differences via thumbnails.
Additional info

to support required feature the plugin had to be rewritten.
this is only part in the puzzle which is ensembled in this PR https://github.com/ynput/OpenPype/pull/5936

Testing notes:

Thumbnails in all hosts should work as before

Sounds like we can merge.


fix: tuples response parser, for nested tuples, or tuple including Result

Motivation and Resolution
Solve issue #997

If the tuple includes a Result enum, the parse is wrong (because the Result type includes a , : Result<u64, u8>
if it's nested tuples (more than 2 levels), it's not handled by the parser.

Usage related changes
Such Abi outputs are now handled (in Cairo 1):
((u256,(u16,Order2)), u8)
(Result<u64, u8>, u8)
(tupleResponse::tupleResponse::Direction, core::integer::u8) // where Direction type can be a Result type

Development related changes

the tuple parser was splitting the abi output string, using , as splitter, and was not able to handle more than 2 levels of tuples. This code has been completely rewritten.
Tests : a dedicated test contract has been added, and tests have been added in Cairo1v2.test.ts

Checklist:

[x] Performed a self-review of the code
[x] Rebased to the last commit of the target branch (or merged it into my branch)
[x] Linked the issues which this PR resolves
[x] Documented the changes in code (API docs will be generated automatically)
[x] Updated the tests
[x] All tests are passing

I wanted to test a refactoring suggestion and I noticed that some of the tests don't fully check the code.
On this branch you can see that part of the code is commented out but the tests still pass. The code does get passed through when it is not removed, but when it is removed the fallback conditional is sufficient to produce the expected result for the corresponding tests.

It should be better now.
I have already tried a refactor of this part of the code, using .some(), but i had an error message due to variable posStart.


Add option to disable the progress bar

Hi,
unless I missed something, it is currently not possible to disable the progress bar when training a SetFit model using SetFitTrainer. I suggest adding an option for this.
Motivation: I am using SetFit in a Jupyter Notebook (not sure why it seems to print more than in the SetFit example notebook) and the output makes it rather ugly. Moreover, one might want not to display progress bars regardless of the notebook setting.
Problematic calls:
https://github.com/huggingface/setfit/blob/fa1021d2355f0cb3a2c85732ee7ffe44b0cef0d1/src/setfit/trainer.py#L374
https://github.com/huggingface/setfit/blob/fa1021d2355f0cb3a2c85732ee7ffe44b0cef0d1/src/setfit/trainer.py#L388

Perhaps a more appropriate fix is for sentence-transformers to start using tqdm.autonotebook, i.e.
from tqdm.autonotebook import ...

rather than
from tqdm import ...

This will automatically detect whether tqdm, the module responsible for the bars, should display the progress as if it's in a console or as if it's in a Jupyter notebook. In a Jupyter notebook, the bars ought to look along the lines of this if autonotebook is used.

(Source)
This should be as simple as replacing all from tqdm import ... with from tqdm.autonotebook import ... in the sentence-transformers repository.

Tom Aarsen

Thanks for the quick response, @tomaarsen.
Yes, this sounds as sentence-transformers could improve on this as well. I did not know about autonotebook, this is great advice. Thank you (also for the detailed demonstration)!
In this case I feel SetFit could expose this parameter as well (at least as long as it explicitly passes the show_progress_bar parameter itself).

Agreed. I've made a PR to handle the SetFit side of this issue, i.e. with show_progress_bar.

Awesome, thank you!


chore(editorconfig): add .editorconfig

This may help keeping a sane codebase.

Good call, thanks! Back when I made this project I didn't really think anybody else would ever contribute 😁
Would you mind setting up eslint too with the same configuration?


Rename feature to loi in unit tests

Towards alpha cleanup

@scolsen  PTAL?

Codecov Report

Merging #1208 (8e89e56) into master (47b7b11) will decrease coverage by 0.72%.
The diff coverage is n/a.

:exclamation: Current head 8e89e56 differs from pull request most recent head 4ca318a. Consider uploading reports for the commit 4ca318a to get more accurate results

@@             Coverage Diff              @@
##             master    #1208      +/-   ##
============================================
- Coverage     29.73%   29.01%   -0.73%
+ Complexity      785      772      -13
============================================
  Files           291      291
  Lines          7630     7520     -110
  Branches        348      341       -7
============================================
- Hits           2269     2182      -87
+ Misses         5253     5234      -19
+ Partials        108      104       -4

Impacted Files
Coverage Δ

...android/ground/model/locationofinterest/Point.java
66.66% <0.00%> (-33.34%)
:arrow_down:

...ogle/android/ground/repository/SurveyRepository.kt
76.56% <0.00%> (-8.52%)
:arrow_down:

...round/model/submission/MultipleChoiceResponse.java
24.00% <0.00%> (-8.00%)
:arrow_down:

...ence/local/room/converter/ResponseJsonConverter.kt
42.00% <0.00%> (-4.00%)
:arrow_down:

...round/ui/datacollection/DataCollectionViewModel.kt
92.59% <0.00%> (-3.71%)
:arrow_down:

...nce/remote/firestore/schema/SubmissionConverter.kt
68.85% <0.00%> (-1.64%)
:arrow_down:

...nd/ui/home/mapcontainer/PolygonDrawingViewModel.kt
86.46% <0.00%> (-0.11%)
:arrow_down:

...le/android/ground/ui/home/HomeScreenViewModel.java
0.00% <0.00%> (ø)

...oid/ground/ui/common/LocationOfInterestHelper.java
100.00% <0.00%> (ø)

.../ground/system/auth/GoogleAuthenticationManager.kt
0.00% <0.00%> (ø)

... and 29 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


New package: dune3d.dune3d version 1.2.0

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
[x] Resolve #192981

Manifests

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

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

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

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Executable C:\Program Files\Dune 3D\dune3d.exe returned exit code: -1073741819
Executable C:\Program Files\Dune 3D\gspawn-win64-helper-console.exe returned exit code: 3
Executable C:\Program Files\Dune 3D\gspawn-win64-helper.exe returned exit code: 3

Automated error analysis suggests -1073741819 may mean Converted to hexadecimal (C0000005) possibly Access Violation. (This is occasionally seen in PRs despite the install otherwise being successful. Should it be added as an InstallerSuccessCode or similar here?)
(Automated response - build 899.)

Manual Validation ended with:

Fault bucket<PHONE_NUMBER>633979280, type 5 Event Name: BEX64 Response: Not available Cab Id: 0  Problem signature: P1: dune3d.exe P2: <IP_ADDRESS> P3: 671811e3 P4: StackHash_ac46 P5: <IP_ADDRESS> P6: 00000000 P7: PCH_DF_FROM_ntdll+0x000000000009D8C4 P8: c0000005 P9:<PHONE_NUMBER>000008 P10:   Attached files: \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6DD6.tmp.dmp \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E64.tmp.WERInternalMetadata.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E74.tmp.xml \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E72.tmp.csv \?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6E83.tmp.txt  These files may be available here: \?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_dune3d.exe_4d5022d4bbef59f8c24b1d5f3a745aecb956e1b4_349f4197_74fa653d-8943-448a-813d-6894a2db1fec  Analysis symbol:  Rechecking for solution: 0 Report Id: 1f3abf46-54d7-4189-90e4-a08dbfc53e7e Report Status: 268435456 Hashed bucket: f20968d23b0c359808a82399d689b990 Cab Guid: 0
Faulting application name: dune3d.exe, version: <IP_ADDRESS>, time stamp: 0x671811e3
Faulting module name: unknown, version: <IP_ADDRESS>, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000000000000
Faulting process id: 0xa68
Faulting application start time: 0x01db3f9987c1f02e
Faulting application path: C:\Program Files\Dune 3D\dune3d.exe
Faulting module path: unknown Report Id: 1f3abf46-54d7-4189-90e4-a08dbfc53e7e
Faulting package full name:
Faulting package-relative application ID:

(Automated response - build 899.)


Request failed: unacceptable content-type: text/xml

Hi,
I'm not sure what's is going on. I use Amazon S3 bucket to store some plist files but when I want to use them with GroundControl I got the following error message:
NSLocalizedDescription=Request failed: unacceptable content-type: text/xml
if I add this line to GroundControl it works perfectly
requestOperation.responseSerializer.acceptableContentTypes = [NSSet setWithObject:@"text/xml"];
If I add these lines it also works:
 if (![[NSUserDefaults standardUserDefaults] responseSerializer]) {
     [[NSUserDefaults standardUserDefaults] setResponseSerializer:[AFPropertyListResponseSerializer serializer]];
 }

 AFPropertyListResponseSerializer *serializer = (AFPropertyListResponseSerializer *)[[NSUserDefaults standardUserDefaults] responseSerializer];
 [serializer setAcceptableContentTypes:[NSSet setWithObject:@"text/xml"]];

But there must be an easier/more obvious way to fix this issue
Thanks

This is still broken. Seems this repo has been mostly abandoned.


MINOR: Improve JavaDoc for some public classes.

@miguno @ymatsuda for reviews.

LGTM

Merged to trunk.


RedisStore - Using direct Redis commands instead of hash Redis commands

Can we use the direct Redis get, set, del commands instead of hget, hset, hdel?
The reason

On using the hash command the expiration of the particular hash list is set to infinity.
And on accessing the Request Cache it iterates all the keys and deletes only one key if the length exceeds the provided max length
It uses hgetAll to iterate all the keys which are of O(N) time.

Proposed Solution

To avoid iterating all the keys, the max length should not be specified.
Because of the absence of max length, the size of the Redis hash list increases and instill the memory load in the Redis server.
Even if the max length is specified, we can use the scan command to iterate through keys 1000 at a time. It optimizes the flow.
For the namespace, we can prefix the key.
To overcome this, we can use the direct Redis commands with separate TTL for every key. On the expiration of the TTL, the Redis itself deletes the key.
We can provide the developers with two different options to use the RedisStore either by hash commands or by direct commands.

Merged and released in the latest version https://github.com/RasCarlito/axios-cache-adapter/releases/tag/2.7.0


Notifications

Hello Teams,
have you planned to develop a notification that invokes an API ?
Best,
Sal

You mean like a web-hook? We have a feature that is a web-hook.

I've never used a web-hook but it might be fine ... where do I find the documentation?

Please try to make more meaningful summaries/descriptions of you github issues that make it clear what it is that you are requesting.

Hello Teams,
I have seen here https://defectdojo.readthedocs.io/en/latest/features.html?highlight=notifications#notifications that DefectDojo can inform of different events in a variety of ways. We want to integrate DefectDojo with an internal system via API to notify them of different events such as added test or closed engagement.
@damiencarol told me about web-hooks which might be fine but I haven't found any documentation explaining how it works, can you help me ?
Best,
Sal


issues with sqlite driver on the docker image

Hello, I'm trying to use the docker image (with docker-compose) to run the project, when I start it I get the following message:
pastebin_1  | stty: 'standard input': Inappropriate ioctl for device
pastebin_1  | stty: 'standard input': Inappropriate ioctl for device
pastebin_1  |
pastebin_1  | In db.cr line 101:
pastebin_1  |
pastebin_1  |   no driver was registered for the schema "sqlite", did you maybe forget to r
pastebin_1  |   equire the database driver?
pastebin_1  |
pastebin_1  |
pastebin_1  | prune
pastebin_1  |
pastebin_1  | 2024-06-08T21:23:05.921285Z   INFO - athena.framework: Server has started and is listening at http://<IP_ADDRESS>:4633

And it starts correctly, but as soon as I try to use it, the sqlite error bites back:
pastebin_1  | 2024-06-08T21:23:10.626409Z   INFO - athena.framework: Matched route 'paste69_home_controller_index' -- route: "paste69_home_controller_index", route_parameters: {"_route" => "paste69_home_controller_index", "_controller" => "Paste69::HomeController#index"}, request_uri: "/", method: "GET"
pastebin_1  | 2024-06-08T21:24:35.379922Z   INFO - athena.framework: Matched route 'paste69_home_controller_index' -- route: "paste69_home_controller_index", route_parameters: {"_route" => "paste69_home_controller_index", "_controller" => "Paste69::HomeController#index"}, request_uri: "/", method: "GET"
pastebin_1  | 2024-06-08T21:24:52.100878Z   INFO - athena.framework: Matched route 'paste69_paste_controller_create_paste' -- route: "paste69_paste_controller_create_paste", route_parameters: {"_route" => "paste69_paste_controller_create_paste", "_controller" => "Paste69::PasteController#create_paste"}, request_uri: "/", method: "POST"
pastebin_1  | 2024-06-08T21:24:52.363819Z  ERROR - athena.framework: Uncaught exception #<ArgumentError:no driver was registered for the schema "sqlite", did you maybe forget to require the database driver?> at /usr/share/crystal/src/primitives.cr:36:1 in 'get_connection'
pastebin_1  | no driver was registered for the schema "sqlite", did you maybe forget to require the database driver? (ArgumentError)
pastebin_1  |   from /usr/share/crystal/src/primitives.cr:36:1 in 'get_connection'
pastebin_1  |   from lib/crecto/src/crecto/repo.cr:88:30 in 'all'
pastebin_1  |   from /usr/share/crystal/src/indexable.cr:574:11 in 'get_by:sha256'
pastebin_1  |   from src/models/paste.cr:81:18 in 'create_paste'
pastebin_1  |   from lib/athena/src/action.cr:42:13 in 'handle_raw'
pastebin_1  |   from lib/athena/src/route_handler.cr:19:5 in '->'
pastebin_1  |   from /usr/share/crystal/src/http/server/request_processor.cr:51:20 in 'handle_client'
pastebin_1  |   from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
pastebin_1  |   from ???

do I need a specific configuration that I'm missing? the docker-compose is fairly simple:
version: '3.3'
services:
    pastebin:
      image: ghcr.io/watzon/paste69
      ports:
        - <private>
      environment:
        - PORT=<private>
        - SITE_URL=<private>

I think you need to do sqlite3 for the schema. Try that and let me know if it works.

You should be able to do it in the environment variable. DATABASE_URL=sqlite3://./db.sqlite or something to that effect.

ok that actually did something but it's now broken in different ways 😅
I'm doing
echo "hello" | curl -F"file=@-" "http://<host>:4633"

and I get the message:
pastebin_1  | stty: 'standard input': Inappropriate ioctl for device
pastebin_1  | stty: 'standard input': Inappropriate ioctl for device
pastebin_1  | Pruned 0 expired files
pastebin_1  | 2024-06-22T21:17:14.861566Z   INFO - athena.framework: Server has started and is listening at http://<IP_ADDRESS>:4633
pastebin_1  | 2024-06-22T21:17:18.003719Z   INFO - athena.framework: Matched route 'paste69_paste_controller_create_paste' -- route: "paste69_paste_controller_create_paste", route_parameters: {"_route" => "paste69_paste_controller_create_paste", "_controller" => "Paste69::PasteController#create_paste"}, request_uri: "/", method: "POST"
pastebin_1  | 2024-06-22T21:17:18.292685Z  ERROR - athena.framework: Uncaught exception #<NilAssertionError:Nil assertion failed> at /usr/share/crystal/src/nil.cr:113:7 in 'not_nil!'
pastebin_1  | Nil assertion failed (NilAssertionError)
pastebin_1  |   from /usr/share/crystal/src/nil.cr:113:7 in 'not_nil!'
pastebin_1  |   from /usr/share/crystal/src/nil.cr:109:3 in 'not_nil!'
pastebin_1  |   from lib/totem/src/totem/config.cr:179:40 in 'url'
pastebin_1  |   from src/models/paste.cr:10:5 in 'create_paste'
pastebin_1  |   from lib/athena/src/action.cr:42:13 in 'handle_raw'
pastebin_1  |   from lib/athena/src/route_handler.cr:19:5 in '->'
pastebin_1  |   from /usr/share/crystal/src/http/server/request_processor.cr:51:20 in 'handle_client'
pastebin_1  |   from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
pastebin_1  |   from ???
pastebin_1  |


[Snyk] Security upgrade rack-contrib from 2.4.0 to 2.5.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the rubygems dependencies of this project.
Snyk changed the following file(s):

Gemfile
Gemfile.lock

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Allocation of Resources Without Limits or Throttling SNYK-RUBY-RACKCONTRIB-7148535
  236

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling

Already done. Closing.


Allow empty JSON body during web requests [phab:D353]

Created by schroederc at 2015-06-22 20:45:53:

shahms accepted this revision at 2015-06-22 21:14:59

schroederc closed via commit 529a5a98e37376a2a6bb50e9e9c524b6681264e6 at 2015-06-22 21:16:37


update images to latest v1.0.4

Signed-off-by: Vasu Kulkarni<EMAIL_ADDRESS>

@crobby can you take a look?


Run flask server in production mode

The flask server is currently running in develop mode.
It can cause problems when running the pipe for long time

main

There are 2 flask servers:

for pipe manager with UI
for the output component flask display

I tried to change the app.run to using the waitress.serve to run the app, but it only made the video run really slow compare to the flask as usual.
what i did was to import the serve from waitress in both main.py and flask_video_display.py
and changed where the app.run to serve(app, host="<IP_ADDRESS>", port=5000)
is it ok that the video is running slow? what do you think we should do ? @ItayHoresh

The video speed is more important than change flask to be in production mode. Our use of the flask display is for development for now.

What will we do when we'll need to use the pipeline in production mode and will need it to run for a long time?


Process for building support for other F4 boards?

I have an F4 Omnibus flight controller and I’m wondering what modifications I’d need to make for rosflight to run on it. The docs seemed to suggest that it should work on any F4, but other places suggested this firmware is very specific to the revo. If it wouldn’t work out of the box, would building support for my board require modifcations to rosflight, airbourne, or both?

Hey @atyshka,
Yeah, I didn't do a great job of architecting the code so that it was obvious how to extend airbourne.
It's a change to airbourne.  In airbourne/include/revo_f4.h I have defined all the peripheral mappings, and that is the only revo-specific code (or at least it should be) in airbourne.
The include structure of airbourne is currently pretty revo-specific, but that's just because I wasn't very careful.  I think the right thing to do is use a macro set at compile time which directs airbourne to the proper header, whether it be the revo, or the omnibus to the proper peripheral mappings.
If I were implementing a new board, I would start by making sure that all of the header files in the include folder in airbourne only pointed to the system.h header, and add some code to the top of that header which looked something like
#if defined(REVO)
#include "revo_f4.h"
#elif defined(OMNIBUS)
#include "omnibus_f4.h"
#else
#error "No compatible board implementation found"
#endif

That way the right peripheral mappings get included.
The next thing would be to make a copy of revo_f4.h and modify it so that it hooks up everything you need for the omnibus board, and finally, I would build and run each of the examples, to make sure that everything works.
If the examples work, then ROSflight should work, because it uses the API tested by the examples.


Update commons-io dependency

Coverage remained the same at 77.814% when pulling 34138b1531853b977ba78429ae30a5ff0baebe03 on Thihup:patch-1 into c27d4d1ecae76e41579b02892a7a0c27da6e34b0 on apache:master.


[BUG] Too many level 0 categories in SfHeader, which is too narrow

Describe the bug
When I have too many categories (level 0) in SfHeader then Vue Storefront logo on the left hand side is getting too narrow. Also there is no solution for handling many categories on level 0, that would not fit in the maximum width of the header.
Expected behavior
I think we should handle the appearance of the logo. The question to UX Designer is how shall we handle bigger amount of categories in level 0. In case of the decision of not handling that case - we should think about some limitation or information in documentation of Storefront UI on what's the maximum amount of level 0 categories to be added in SfHeader.
Actual behavior

fixed on design side

#1011

solved by #1165


Oracle just announced that Java 11 will have support thru Jan 2032

Link to product page on endoflife.date
https://endoflife.date/oracle-jdk
Details of incorrect and correct details you have found
endoflife.date: 2023-09-30
Product documentation: 2032-01-31 (they don't provide the day-of-month, I'm guessing the 31st?) They also are saying "at least" in this article.
What is the source website for the product and for its version information?
I can't find other announcements beyond this right now: https://blogs.oracle.com/javamagazine/post/java-21-now-available
Additional context
This isn't terribly surprising with JDK 11 being in use by over 55% of Java developers in recent industry surveys.

Good catch :+1: and thank you for opening this issue.
We are using the page https://www.oracle.com/java/technologies/java-se-support-roadmap.html as source for the dates. They have not yet updated the page therefore I would wait with our update too. For me it is also not clear which date (Premier Support or Extended Support) they have extended.

@BiNZGi Looks like the folks I chatted with on r/java were correct, the extension was specifically for Oracle Extended Support (see the Java 11 line in the table on the page you referenced, where Extended support has moved from Sept 2026 to Jan 2032). Hopefully the OpenJDK maintainers will try and get a level of parity with that (because who uses Oracle JDK anyways these days?).

Thanks for the update @hantonr !


chore: Pin version of unittest Dart package used in e2e tests.

There is some problem with the versions of test/unittest that Travis is able to install. I am abandoning this PR and seeing if we can just move to "test" package.


Changes for split arch support through scripts

Fixes for status handling

The way these scripts work.

The setup_infra.sh is the main script. It takes in couple of arguments from the user. Main being mode "-m" that identifies if it's a host install or a split install. Second "-r", that's valid for split only and represents the IP address on the ACC over comms channel. Based on this IP address, host side is allocated +1 ip from the same subnet.
If mode is "host" , script pretty much works like create_interfaces.sh + bug fix + some changes to accommodate recent config changes on infrap4d.
If mode is "split" then scripts looks for "-r ". In this mode, the script executes host functions like creating cdq etc, cert generation on host and then remotely transfers and executes ACC side of script "setup_acc_infra.sh" and certs & artifacts. ACC side of script then takes over configuration on ACC for infrap4d and inframanger and starts them.

Default is with mTLS. In case of internal testing, we would need some changes in the script and config files to start in insecure mode.


build project

can some one teach me how to build project in visual studio pls :V

but i have some bug when run project and I fixed it 5 minutes ago, tks


Why are RELU and BN set before Conv?

https://github.com/tornadomeet/ResNet/blob/master/symbol_resnet.py
In line 28:
    bn1 = mx.sym.BatchNorm(data=data, fix_gamma=False, eps=2e-5, momentum=bn_mom, name=name + '_bn1')
    act1 = mx.sym.Activation(data=bn1, act_type='relu', name=name + '_relu1')
    conv1 = mx.sym.Convolution(data=act1, num_filter=int(num_filter*0.25), kernel=(1,1), stride=(1,1), pad=(0,0),

bn1 and act1 layer is set before conv1, why?

please read the original paper.

THX


make it possible to redirect to another url, than /webapp

Signed-off-by: Felix Bartels<EMAIL_ADDRESS>

Local test run succeeded


Rule: Fix temporary rule filename composition issue

Signed-off-by: Matej Gera<EMAIL_ADDRESS>

[X] I added CHANGELOG entry for this change.
[ ] Change is not relevant to the end user.

Changes
Provides a fix for current issue with rule filenames, which are being written into a .tmp-rules directory for further processing. As was discovered in the linked issue, the current implementation could lead to temporary rule filenames being composed in a way, where trimming of the filename leads to unexpected result, i.e. the TrimLeft function can in some cases trim the filename in a way which results in duplication of temporary rule filenames. This in turn manifests itself as some rules being 'ignored' by the rule component.
Since trimming the filename does not seem to have the desired effect, the fix proposed here is to simply leave the full filename as is, which practically leads to same result but without possible name duplication issue.
Fixes #4232
Verification
Related tests have been updated to assess the fix is working; also tested manually with local run of thanos rule

LGTM, I have fixed the conflicts!

Seems Sonatype Lift is having problems, merging


Bracket Pair Colorization: Consider picking colors with a bit more contrast from syntax higlight

In #129231 there was a discussion about contrast between brackets, however it would be also great to have a bit more contrast between bracket and tokens near it for default themes.

It mostly noticeable with light blue parentheses ( #87cefa) that looks almost same as to parameters and properties (#9cdcfe).
Constants(#4fc1ff) are slightly better.
function and log looks great near (
@hediet do you think it's possible to find blue value that distinct enough from other colors in syntax highlight or this is out of scope?
UPD. For example #179fff is brighter but I guess it's comparable to #ffd700.
Looks good with parameters/properties and constants, however closer to function and false, but still not as close as with parameters and properties now.

You can customize the colors:
"workbench.colorCustomizations": {
    "[Default Light+]": {
        "editorBracketHighlight.foreground1": "#0431FAFF", // #1857D0FF
        "editorBracketHighlight.foreground2": "#319331FF", // #167C4BFF
        "editorBracketHighlight.foreground3": "#7B3814FF", // #8A4F0CFF
    }
},

Please let us know if you find nice colors 😉
We mainly optimized for relative contrast. Though the colors for the dark theme are taken from the original bracket pair colorization extension.

Main idea was to have better defaults for built-in themes if possible (I remember how hard was to find another blue color so it's questionable if there is good color for brackets).
I found #179fff or #33aaffas more preferable for me but it's more brighter so may not fit goal "draw less attention" if there is one.
Something from hue ~205, saturation ~90-100%, and lightness ~50-60%
If this change if out of scope - fell free to close this issue - I'll use local color overrides (as you've mentioned above).

Main idea was to have better defaults for built-in themes if possible

I got that, I wanted to encourage playing with colors and posting better ones 😉

I found #179fff or #33aaffas more preferable for me but it's more brighter so may not fit goal "draw less attention" if there is one.

Thanks, I'll try it out!

I updated the dark colors to use #179fff.

This is what I use for Solarized Dark based off of the settings I had when I was using the bracket pair colorization extension. I just picked some colours that were already in use by the theme.
"[Solarized Dark]": {
    "editorBracketHighlight.foreground1": "#cdcdcdff",
    "editorBracketHighlight.foreground2": "#b58900ff",
    "editorBracketHighlight.foreground3": "#d33682ff",
}

This is what it looks like in practice.

@TabithaLarkin thanks! Feel free to open a PR to the repo that defines this theme! (also include a before screenshot)

The new blue is a complete eyesore and has to be changed; it actively hurts the eyes.

The old extension had these colours:
{
  "bracket-pair-colorizer-2.colors": [
    "Gold",
    "Orchid",
    "LightSkyBlue"
  ]
}

#ffd700
#da70d6
#87cefa

While they were pretty bright, they weren't hurting and they were different enough from the base theme that they didn't cause problems.

It look great with white, and slightly better then initial with variables.
However it's almost identical to constants/read-only values (#4FC1FF), therefore proposition was to pick value distinguishable from both of these colors.


DRD label editing causes shortcut conflict

Select a DRD (activates E shortcut for edit)

Double-click or hit E to actually start editing

if you type e as part of your label, the shortcut is triggered again which results in deletion of the newly typed text.

(tested with 1.16.1 on Windows and Mac)

Fixed in Camunda Modeler v1.16.2.


Files keep on local storage

Hi @thaiphan, I'm using your module, thanks for it.
I have a question, why do files stay in local storage? How do I send just for s3?

@greatwitenorth Did you figure out the issue with this or were able to fix it?


refactor(compartment-mapper): Inline Zip archive library

This change subsumes a variation on the popular JSZip library. See README.md in packages/compartment-mapper/src/zip for details about how the library varies.
The objectives are:

To eliminate the dependency on the Node.js readable streams built-in library.
To convert entirely to ECMAScript modules so the compartment mapper can be embedded in an XS binary.
To work under SES. Notably, to not depend on new Date().

In refactoring, I introduces stricter integrity checks than JSZip, consistent with our security focus, at the possible expense of compatibility with some archives.
The implementation is sufficient for round tripping an archive, and for third-party tools to be able to read that archive, but not sufficient to be able to read archives generated by other tools, notably if they use Zip64 or any kind of compression. While this is sufficient for our needs, these features are recoverable with some work.
Zip64, to the extent of 53 bit addresses, or with a major BigInt refactor for 64 bit addresses, is relatively straightforward. Recovering *FLATE compression just requires converting the pako package to ESM and affords an opportunity to reuse the CRC-32 package, perhaps publishing these as @agoric/crc32, @agoric/inflate, and @agoric/zip (or even just zip since I own that).
I also removed asynchrony. JSZip supports a mode where it will periodically yield to avoid monopolizing the event loop, emitting progress updates. This feature could be recovered with a parallel API that drives the synchronous buffer writer using async functions, and streaming Uint8Array async iterators, which is entirely out-of-scope for our needs.
That said, our needs may eventually include lazy archive reading, which could be done with an async seekable reader, much like the included buffer reader.
I’ve elected to inline the implementation now to defer the higher bar needed to commit to public API’s and to be more generally useful.
(cc JSZip authors @stuk and @aadsm)

cc @erights and @dtribble. This was an unanticipated tangent on the critical path to removing Rollup from our deployment system. It has successfully cut the dependencies on Node.js built-ins down to just a few things Babel asks for. I’ll try integrating this branch next, in hopes this was enough to clear the hurdle of “what subset of JavaScript intersects Rollup and -r ESM”. If it’s not, I will try again to swap the Rollup dependencies for Rollup-standalone.


Support for home_timeline ?

Hey,
Does this library support retrieving tweets from statuses/home_timeline ?
Thanks

No it doesn't. Only the search API and user timelines are supported.
It should be easy to add the home timeline as well, though. Although I think that most people would use a twitter client library for such things.


Consider specifying that Filter search shows up only once you have more than a handful of entries

Nit: consider specifying that Filter search shows up only once you have more than a handful of entries

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7fdcd90e-7d08-39e9-c2e5-888c690c6cbc
Version Independent ID: 525bd933-5da2-29b5-8d7c-dadfa094c9f0
Content: Parameters in Azure Data Explorer dashboards
Content Source: data-explorer/dashboard-parameters.md
Service: data-explorer
GitHub Login: @orspod
Microsoft Alias: orspodek

@mitulmk
Thank you for reaching out. At this time we are reviewing the ask and will provide an update as appropriate

@Gabilehner

@mitulmk - created a WI to make this update. I'm closing now.

@Gabilehner @Mitulmk please review https://github.com/MicrosoftDocs/dataexplorer-docs-pr/pull/906


PRs from forks should not run lang server tests

... because you don't have access to the private variables which allow pulling in the lang server nuget packages, so these tests would fail.

@alexgav This is the one I need reviewed, thanks!


python pose analysis plot shows velocity twice

Instead of showing velocity and velocity standard deviation, the standard deviation plot is populated with velocity, again.

Fixed in #65.


Transpiler: Implement field wildcards

Implement the * functionality and the function(*). This will require a working schema implementation to function.

This is documented now for the how to do: https://github.com/influxdata/influxdb/blob/master/query/influxql/README.md#-generate-the-pivot-table
I'll begin working on this.

This may actually cause an issue. In the trivial case, this can be quite easy such as in the example of SELECT * FROM m0. But, influxql also allows  SELECT * + 2, value FROM cpu and then it starts to  become harder. We would need to apply the + 2 to every field that was selected and have it as a separate column. We would also have to deal with the inevitable field conflict. It is not possible to infer that value is selected by * because value may not be a field or tag. If a field or tag was present  with the key value, then the second value would be value_1 (or maybe value_0). If it wasn't, then it would keep its name and just be an empty column.
So this has a lot of edge cases that are pretty complicated.

if value is not a field or tag what would it be?

Nothing. It gets returned as null. It annoyed me for a very long time, but influxql treats everything as something and does not return errors when you reference nothing because it believes nothing is something.

I am going to treat this issue as "implement field wildcards when a wildcard is the only thing present". We can do that with pivot. We will have to design the more complex stuff.

Good news: This was too complex for influxql at the time too: https://github.com/influxdata/influxdb/blob/728bdd6562858ff7e0793bcf54b619e462f55a1c/query/compile.go#L309


Missing 'getValue(App, KProperty<*>)' method on delegate type 'LazyKodein'

When implementing KodeinAware in Application Class. Before and after binding anything at all. This error appears.

I replaced 'by' with = based on the demo app on the project, error doesn't occur anymore.
Documentation is suggesting to use by instead of '='

I have same issue. Kodein 5.0.

Use =, not by.
Kodein.Lazy is not a property delegate, it is a Kodein implementation that will actually create the binding lambda upon the first retrieval.

Im having the same issue
Type 'KodeinPropertyDelegateProvider' has no method 'getValue(TodayFragment, KProperty<*>)' and thus it cannot serve as a delegate
The application class is being called in the manifest and showing that it was never used.
class WeatherForecast: Application(), KodeinAware {
//Using Kodein.lazy allows you to access the Context at binding time.
override val kodein = Kodein.lazy {
    import(androidXModule(this@WeatherForecast))

//        import(androidModule(this@WeatherForecast))
    bind() from singleton { ForecastDatabase(instance()) }
    bind() from singleton { instance<ForecastDatabase>().currentWeatherDao() }
    bind<ConnectivityInterceptor>() with singleton { ConnectivityInterceptorImpl(instance()) }
    bind() from singleton { ApixuApiWeatherService(instance()) }
    bind<WeatherNetworkDataSource>() with singleton { WeatherNetworkDataSourceImpl(instance()) }
    bind<ForeCastRepository>() with singleton { ForeCastRepositoryImpl(instance(), instance()) }
    bind() from provider { TodayViewModelFactory(instance()) }

//        bind<ViewModelProvider.Factory>() with singleton { TodayViewModelFactory(instance()) }
}

}


Use analyzed data in search ranking

Package health is 5% of the total score.
Using bezier scoring for both popularity and health.

This is the first step of the chicken-and-egg problem of using bezier (relative) scores for package health (where you need to have some synchronization and get to know all the scores). The search index needs all the raw numbers to calculate the relative score, so it will fetch it from analyzer, and stores it in the snapshot.
Later on either the frontend or the analyzer will need to know about the score of a particular package, so most likely they will turn to the search index for the calculation.

@isoos Another timing out test. Maybe we need another increase in timeout for this upload-too-big test.

Pulling it now. Filed https://github.com/dart-lang/pub-dartlang-dart/issues/305 for discussing this artificial bias in the health metric.


Add a humanization random option

How about adding a humanization option to the dialogue box  that could assign subtle random tempos to each note within a user set range based on a section's over all tempo? It would be interesting if Musescore's playback could be made to sound more human by introducing minute note tempo and velocity variations/imperfections. Thanks, Sam

Whilst that would be nice I don't think this plugin would be the correct place for a humanize playback option. Perhaps someone will step up and make a humanize plugin.
In my opinion though, such an implementation would either (A) still sound mechanical if it's easy to write or (B) require something bordering on decent AI to get a good interpretation of a music piece. After all, no human interprets a piece in an identical way.
If you have the time you can always try and use the pianoroll editor as well as give each note a velocity offset value to your hearts desire inside MuseScore (I believe velocity isn't even available to the plugin framework).
But it is out of scope for this plugin.


MaxReaders 1 not working for RTSP(S)

Which version are you using?
v1.0.0
Which operating system are you using?

[ ] Linux amd64 standard
[ ] Linux amd64 Docker
[ ] Linux arm64 standard
[ ] Linux arm64 Docker
[ ] Linux arm7 standard
[ ] Linux arm7 Docker
[ ] Linux arm6 standard
[ ] Linux arm6 Docker
[x] Windows amd64 standard
[ ] Windows amd64 Docker (WSL backend)
[ ] macOS amd64 standard
[ ] macOS amd64 Docker
[ ] Other (please describe)

Describe the issue
MaxReaders config is not enforced properly for RTSP(S). It seems those protocols require 2 readers (even though path.readers only show 1 session). Setting MaxReaders to 1 therefore would not allow any RTSP(S) client connection.
Describe how to replicate the issue

start the server
publish path with maxReaders set to 1
read RTSP with any client

INF [RTSP] [conn <IP_ADDRESS>:62723] closed (maximum reader count reached)

Did you attach the server logs?
no
Did you attach a network dump?
no

Is that with tcp, udp, or both?

I tested with tcp mediamtx output and tcp client.
~ mediamtx.yaml ~
protocols: [tcp]

$ ffplay -rtsp_transport tcp http://localhost:8554/mystream

fixed in v1.0.1


While select Configure-Enable TSLint Builder.

Errors occurred during the build.
Errors running builder 'TSLint Project Builder' on project 'qccweb'.
The following request caused an error to be thrown:
{"method":"lint","arguments":["/Users/shenyaojie/Sites/qccweb/e2e/app.e2e-spec.ts"]}
Error: Could not find the following rules specified in the configuration:
arrow-return-shorthand
callable-types
import-blacklist
import-spacing
interface-over-type-literal
no-duplicate-super
no-empty-interface
no-misused-new
no-non-null-assertion
no-string-throw
no-unnecessary-initializer
prefer-const
typeof-compare
unified-signatures
directive-selector
component-selector
use-input-property-decorator
use-output-property-decorator
use-host-property-decorator
no-input-rename
no-output-rename
use-life-cycle-interface
use-pipe-transform-interface
component-class-suffix
directive-class-suffix
no-access-missing-member
templates-use-public
invoke-injectable
at Object.loadRules (/Applications/Eclipse.app/Contents/Eclipse/plugins/com.palantir.tslint_1.0.1.v20160225-1827/node_modules/tslint/lib/ruleLoader.js:29:15)
at Linter.lint (/Applications/Eclipse.app/Contents/Eclipse/plugins/com.palantir.tslint_1.0.1.v20160225-1827/node_modules/tslint/lib/tslint.js:24:44)
at LinterEndpoint.lint (/Applications/Eclipse.app/Contents/Eclipse/plugins/com.palantir.tslint_1.0.1.v20160225-1827/bin/bridge.js:17:33)
at Main.processRequest (/Applications/Eclipse.app/Contents/Eclipse/plugins/com.palantir.tslint_1.0.1.v20160225-1827/bin/bridge.js:46:37)
at Interface. (/Applications/Eclipse.app/Contents/Eclipse/plugins/com.palantir.tslint_1.0.1.v20160225-1827/bin/bridge.js:36:23)
at emitOne (events.js:115:13)
at Interface.emit (events.js:210:7)
at Interface._onLine (readline.js:278:10)
at Interface._normalWrite (readline.js:419:12)
at Socket.ondata (readline.js:138:10)

I have the same issue. have you found a solution ?

I know this is old but we had this and it was due to the fact that there was a tslint.json file already existing. Delete that one first.

This does not solve the problem at all. tslint.json file needs to exist in the top level directory. If deleted will get an error as well.


Some Youtube music audio files are too big for Telegram bot API (>50 mb)

Some Youtube music audio files are too big for Telegram bot API (>50 mb).
Example:
https://music.youtube.com/watch?v=N1MDxgdPMq0&list=LM
Perhaps I need to add audio file compression if the file is larger than 50 megabytes.

Solved in #32, thanks to Pyrogram!


Support link does not appear in side menu

On latest master-head
Click the hamburger menu in top-left - the side menu no longer shows the support link in the bottom left.

This was fixed with permissions rbac changes and looking for PUT instead of PATCH.

Works fine on master-head (b8a44fa)


modules/nginx: Only send one set of HTTP/3 headers

Description of changes
Currently, enabling http3 in an nginx virtual host results in a config that sends multiple sets of Alt-Svc and QUIC-Status headers for each listening interface. For example, I have a machine has IPv4 and IPv6 enabled, and the configuration looks like this:
        listen <IP_ADDRESS>:443 ssl http2 ;# UDP listener for **QUIC+HTTP/3
        listen <IP_ADDRESS>:443 http3 reuseport;
        # Advertise that HTTP/3 is available
        add_header Alt-Svc 'h3=":443"';
        # Sent when QUIC was used
        add_header QUIC-Status $quic;
        listen [::0]:443 ssl http2 ;# UDP listener for **QUIC+HTTP/3
        listen [::0]:443 http3 reuseport;
        # Advertise that HTTP/3 is available
        add_header Alt-Svc 'h3=":443"';
        # Sent when QUIC was used
        add_header QUIC-Status $quic;

The multiple add_header options cause the same headers to be sent twice.
Things done
This change will cause the configuration to only add these headers once.

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

My variant fix bug - #146917

I think this has been fixed. Please reopen otherwise.


Help setting up

Hi,
I'm trying to set this up from behind a corporate network without a global DNS server available. I'm trying to set up redsocks with dnstc so that DNS queries go over tcp instead of udp. I've augmented the redsocks script with a few new iptables rules, so far I've got:
iptables_rules() {
    # private ip ranges are not intercepted
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/8 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/8 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/16 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/12 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/16 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/4 -j RETURN
    iptables -t nat -$1 PREROUTING -i docker0 -d <IP_ADDRESS>/4 -j RETURN

    iptables -t nat -$1 PREROUTING -p udp --dport 53   -i docker0 -j REDIRECT --to 5300 2>/dev/null
    iptables -t nat -$1 PREROUTING -p tcp --dport 80   -i docker0 -j REDIRECT --to 12345 2>/dev/null
    iptables -t nat -$1 PREROUTING -p tcp --dport 8080 -i docker0 -j REDIRECT --to 12345 2>/dev/null
    iptables -t nat -$1 PREROUTING -p tcp -i docker0 -j REDIRECT --to 12346
}

I try and run redsocks with:
docker build -t willp/forgetproxy .
docker run -it --net=host --privileged -e http_proxy=http://wasp.gbr.iae.net:3128 -e https_proxy=http://wasp.gbr.iae.net:3128 -it willp/forgetproxy
Once up, I then test out the network with
docker run --rm -it ubuntu apt-get update
I've been watching packets on wireshark and the ubuntu box is trying to use google's dns servers which doesn't work. I think I need to use the --dns option to point it towards the redsocks box but haven't had much luck does this yet, I've tried using --dns <IP_ADDRESS> where the ip is that of my docker0 instance but I assume this ends up getting caught by one of the earlier iptables rules and doesn't get redirected to port 5300... any ideas?

I meant to post this on docker-forgetproxy, apologies
(link: https://github.com/k-labs/docker-forgetproxy/issues/2)


VERSION_CATALOGS support for platform (BOM)

Context
I was defining a dependency on software.amazon.awssdk:acmpca and it pulled totally invalid transitive dependencies in. No idea if Maven would have worked correctly here, and it doesn't matter. Fact is that the inclusion of the BOM fixed it.

I couldn't find an issue here nor in Slack, but maybe my search-fu is not good enough and this was already discussed. I'm sorry if that's the case.

Expected Behavior
Dependencies can be defined as platform and are recognized as such automatically, especially to create bundles.
[versions]
aws-sdk = "2.17.89"

[libraries]
aws-sdk-bom = { module = "software.amazon.awssdk:bom", version.ref = "aws-sdk" }
aws-sdk-acmpca = { module = "software.amazon.awssdk:acmpca" }

dependencies {
    implementation(platform(libs.aws.sdk.bom))
    implementation(libs.aws.sdk.acmpca)
}

Current Behavior
It is not possible to define a dependency as platform, but that would be very useful. I don't know what the best way would be to add this functionality to the TOML, but the usage is clear.
[versions]
aws-sdk = "2.17.89"

[platforms]
aws-sdk-bom = { module = "software.amazon.awssdk:bom", version.ref = "aws-sdk" }

[libraries]
aws-sdk-acmpca = { module = "software.amazon.awssdk:acmpca" }

[bundles]
aws-sdk = ["aws-sdk-bom", "aws-sdk-acmpca"]

dependencies {
    implementation(libs.bundles.aws.sdk)
}

The version catalog feature has been designed to only cover the coordinates of dependencies, not how they are used - which configuration, which attributes, which classifier, etc ...
So this information will not be encoded there.


operator infinispan (2.4.8)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description about the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

Hi! Sorry there is an issue one CI task. The error looks a 502 bad gateway.
I'm not sure it is something we can fix on our side.

/merge possible

/merge possible

Thanks!


update to vn0.6.6

simple change to update to vn0.6.6

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

vn0.6.6 includes a change to setup.py so that the main javascript component is in the correct place when installed from conda.


move shrs crate to crates/shrs

Resolves #233.

Probably keep shrs_example in root directory (or crates/) since it acts more as an integration test for all the crates and plugins. shrs_example should also be able to be built and installed by the user so having it under examples/ is a bit weird.

Ah, very good point! I didn't notice that the shrs_example also depended on the plugins. I updated this PR to keep it in the repository root. (I think that's better than having it in crates/ since then crates/ only contains crates that are published, which is nice.)

LGTM


Android Compose library without Material3

About this issue
Markdown() composable has a strong dependency on material components like androidx.compose.material.MaterialTheme.
For Wear these should be avoided and instead use Wear Material versions.
See https://developer.android.com/training/wearables/compose#different
Is it feasible to pull these Color and Typography factories that default to mobile material to a separate dependency?
Details
0.11
Wear (Android)
Checklist

[x] Searched for similar issues
[x] Checked out the sample application
[x] Read the README
[ ] Checked out the CHANGELOG
[ ] Read the FAQ
[ ] Checked out the MIGRATION GUIDE

n.b, FAQ is missing? https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/FAQ.md

Good day @yschimke
Thank you very much for the report. The MaterialTheme is already only used in the default factories, allowing you to replace all of them with alternative variants:

hhttps://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/multiplatform-markdown-renderer/src/commonMain/kotlin/com/mikepenz/markdown/model/MarkdownTypography.kt
https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/multiplatform-markdown-renderer/src/commonMain/kotlin/com/mikepenz/markdown/model/MarkdownColors.kt
https://github.com/mikepenz/multiplatform-markdown-renderer/blob/develop/app/src/main/java/com/mikepenz/markdown/ui/Theme.kt

If you adjust all of these, wouldn't proguard be capable of removing all references for Material classes?

Yep, I'm not blocked. I would feel safer not relying on R8 to drop dependencies. Feel free to close if you feel strongly about it.

And nice library.

@yschimke mostly curious on it. haven't shaped a decision on it yet. Do you have an example of a library which includes compose ui and splits to a wear module and other modules due to material theme?

The whole of Wear Compose is like that :)
It has a Wear Material Text instead of Material Text. Wear MaterialTheme instead of MaterialTheme.
But honestly, I think it's about supporting more than just Material. There are other possible design systems, and I'd personally prefer to be able to import multiplatform-markdown-renderer without any explicit material assumptions. And a markdown-material for mobile, and markdown-wear for Wear.

Moving the MaterialTheme itself is not necessarily the problem. https://github.com/mikepenz/multiplatform-markdown-renderer/commit/9ab4568c770572853901c089f4e3da07219574ff
But how would you advice on going with Text or Surface in general. I have extracted those also by copying over some parts of Text and Surface from Material. However that doesn't seem very maintainable to do that in general? 🤔
https://github.com/mikepenz/multiplatform-markdown-renderer/pull/107

I sort of got the impression you are making most of the decisions upfront, so using BasicText directly might be the right thing.
Wear Material actually doesn't have Surface at all.  So maybe uplifting those to the m2 or m3 impls might be the solution?
Thanks for attempting this, I hope overall it's a clean up and more correct as people switch between m2, m3, wear.

Thank you for the additional input @yschimke
I would highly appreciate if you could review the PR https://github.com/mikepenz/multiplatform-markdown-renderer/pull/107
Decided to have wrappers (basically similar to what you mentioned on uplifting the m2/m3 impls) based on the normal surface/text components: https://github.com/mikepenz/multiplatform-markdown-renderer/pull/107/files#diff-8142270f21ac4367be27d783daec3cdff3fafe3e4e498bf9e046932a901b1dab - allowing the full removal of the Material dependency.

For everyone looking for this. There is a first pre-release available with the individual m2 and m3 artifact.
v0.13.0-a01 - https://github.com/mikepenz/multiplatform-markdown-renderer/tree/v0.13.0-a01


!destroyTown could be smarter/safer

It could use the DB to pull data on what channels/categories etc to remove instead of assuming they have certain names
It could also be used within the control channel with no parameters if we want

After a lot of debate when porting to C# we ended up deciding to not change this drastically; the current setup is what we want


tryUntil error: mcpd status is lacpd down, not required

Environment
Declarative Onboarding Version: 1.31.0
Tenant BIG-IP Version: <IP_ADDRESS> deployed in one partition with one blade
Velos F5OS v1.3.2
No LAG/Trunk configuration on the Velos partition, only one port (40Gb) and one vlan used.
Summary
Got following error, from restnoded.log, during the DO deployment:
tryUntil error: mcpd status is lacpd down, not required, then roolback when Max tries reached
Same DO deployment works on a cBigIP
Steps To Reproduce
Steps to reproduce the behavior:

Submit the following declaration:

{
    "$schema": "https://raw.githubusercontent.com/F5Networks/f5-declarative-onboarding/master/src/schema/latest/base.schema.json",
    "Common": {
        "Default": {
            "class": "RouteDomain",
            "id": 0,
            "strict": true,
            "vlans": [
                "http-tunnel",
                "socks-tunnel"
            ]
        },
        "MyNtp": {
            "class": "NTP",
            "servers": [
                "<IP_ADDRESS>",
                "<IP_ADDRESS>",
                "<IP_ADDRESS>"
            ],
            "timezone": "Europe/Paris"
        },
        "MyProvisioning": {
            "class": "Provision",
            "ltm": "nominal"
        },
        "RD_Gi_Internal": {
            "class": "RouteDomain",
            "id": 11,
            "routingProtocols": [
                "BGP"
            ],
            "strict": false,
            "vlans": [
                "Gi_Internal"
            ]
        },
        "Resolver_Sup": {
            "cacheSize": 10,
            "class": "DNS_Resolver",
            "forwardZones": [
                {
                    "name": "fr.",
                    "nameservers": [
                        "<IP_ADDRESS>:53"
                    ]
                },
                {
                    "name": "com.",
                    "nameservers": [
                        "<IP_ADDRESS>:53"
                    ]
                }
            ],
            "routeDomain": "RD_Gi_Internal"
        },
        "Resolver_WAP2": {
            "cacheSize": 5767168,
            "class": "DNS_Resolver",
            "forwardZones": [
                {
                    "name": "toto.",
                    "nameservers": [
                        "<IP_ADDRESS>:53"
                    ]
                }
            ],
            "routeDomain": "RD_Gi_Internal"
        },
        "class": "Tenant",
        "dbvars": {
            "bigd.reusesocket": "disable",
            "bigpipe.displayservicenames": "false",
            "class": "DbVariables",
            "connection.syncookies.threshold": "50000",
            "tm.tcpabcsslimit": "64",
            "tm.tcpprogressive.autobuffertuning": "enable",
            "tm.tcpprogressive.autonaglerttthresh": "20",
            "tm.tcpprogressive.burstcontrol": "disable",
            "tm.tcpprogressive.proxybufmax": "4194304",
            "tm.tcpprogressive.proxybufmin": "1048576",
            "tm.tcpprogressive.proxybufoffset": "65535",
            "tm.tcpprogressive.rcvbufbdpmultiplier": "4",
            "tm.tcpprogressive.rcvbufincr": "65536",
            "tm.tcpprogressive.rcvbufincrsmall": "4",
            "tm.tcpprogressive.rcvbufmax": "16777216",
            "tm.tcpprogressive.rcvbufmin": "1048576",
            "tm.tcpprogressive.rcvbufmininterval": "50",
            "tm.tcpprogressive.rttthresh": "10",
            "tm.tcpprogressive.sndbufbdpmultiplier": "4",
            "tm.tcpprogressive.sndbufincr": "65536",
            "tm.tcpprogressive.sndbufincrsmall": "2",
            "tm.tcpprogressive.sndbufmax": "16777216",
            "tm.tcpprogressive.sndbufmin": "1048576",
            "tm.tcpprogressive.sndbufmininterval": "50",
            "tm.tcpsegmentationoffload": "disable",
            "tm.tcpudptxchecksum": "software-only",
            "tm.tcpwoodsidefasterrecovery": "enable",
            "tmm.http.passthru.invalid_content_length": "enable",
            "tmm.resolv.timeout": "1"
        },
        "mySystem": {
            "autoPhonehome": false,
            "class": "System",
            "cliInactivityTimeout": 0,
            "consoleInactivityTimeout": 0,
            "hostname": "scvelos"
        }
    },
    "async": true,
    "class": "Device",
    "label": "my BIG-IP declaration for declarative onboarding",
    "schemaVersion": "1.31.0"
}

Observe the following error response:

{
        "id": "5c3f8759-2fd5-401c-924b-c64ca34c9138",
        "selfLink": "https://localhost/mgmt/shared/declarative-onboarding/task/5c3f8759-2fd5-401c-924b-c64ca34c9138",
        "code": 500,
        "status": "ERROR",
        "message": "invalid config - rolled back",
        "errors": [
            "tryUntil: max tries reached: mcpd status is lacpd                 down, not required\n",
            "tryUntil: max tries reached: mcpd status is lacpd                 down, not required\n"
        ],
        "result": {
            "class": "Result",
            "code": 500,
            "status": "ERROR",
            "dryRun": false,
            "message": "invalid config - rolled back",
            "errors": [
                "tryUntil: max tries reached: mcpd status is lacpd                 down, not required\n",
                "tryUntil: max tries reached: mcpd status is lacpd                 down, not required\n"
            ]
        },
        "declaration": {
            "$schema": "https://raw.githubusercontent.com/F5Networks/f5-declarative-onboarding/master/src/schema/latest/base.schema.json",
            "Common": {
                "Default": {
                    "class": "RouteDomain",
                    "id": 0,
                    "strict": true,
                    "vlans": [
                        "http-tunnel",
                        "socks-tunnel"
                    ],
                    "connectionLimit": 0
                },
                "MyNtp": {
                    "class": "NTP",
                    "servers": [
                        "<IP_ADDRESS>",
                        "<IP_ADDRESS>",
                        "<IP_ADDRESS>"
                    ],
                    "timezone": "Europe/Paris"
                },
                "MyProvisioning": {
                    "class": "Provision",
                    "ltm": "nominal"
                },
                "RD_Gi_Internal": {
                    "class": "RouteDomain",
                    "id": 11,
                    "routingProtocols": [
                        "BGP"
                    ],
                    "strict": false,
                    "vlans": [
                        "Gi_Internal"
                    ],
                    "connectionLimit": 0
                },
                "Resolver_Sup": {
                    "cacheSize": 10,
                    "class": "DNS_Resolver",
                    "forwardZones": [
                        {
                            "name": "fr.",
                            "nameservers": [
                                "<IP_ADDRESS>:53"
                            ]
                        },
                        {
                            "name": "com.",
                            "nameservers": [
                                "<IP_ADDRESS>:53"
                            ]
                        }
                    ],
                    "routeDomain": "RD_Gi_Internal",
                    "answerDefaultZones": false,
                    "randomizeQueryNameCase": true,
                    "useIpv4": true,
                    "useIpv6": true,
                    "useTcp": true,
                    "useUdp": true
                },
                "Resolver_WAP2": {
                    "cacheSize": 5767168,
                    "class": "DNS_Resolver",
                    "forwardZones": [
                        {
                            "name": "toto.",
                            "nameservers": [
                                "<IP_ADDRESS>:53"
                            ]
                        }
                    ],
                    "routeDomain": "RD_Gi_Internal",
                    "answerDefaultZones": false,
                    "randomizeQueryNameCase": true,
                    "useIpv4": true,
                    "useIpv6": true,
                    "useTcp": true,
                    "useUdp": true
                },
                "class": "Tenant",
                "dbvars": {
                    "bigd.reusesocket": "disable",
                    "bigpipe.displayservicenames": "false",
                    "class": "DbVariables",
                    "connection.syncookies.threshold": "50000",
                    "tm.tcpabcsslimit": "64",
                    "tm.tcpprogressive.autobuffertuning": "enable",
                    "tm.tcpprogressive.autonaglerttthresh": "20",
                    "tm.tcpprogressive.burstcontrol": "disable",
                    "tm.tcpprogressive.proxybufmax": "4194304",
                    "tm.tcpprogressive.proxybufmin": "1048576",
                    "tm.tcpprogressive.proxybufoffset": "65535",
                    "tm.tcpprogressive.rcvbufbdpmultiplier": "4",
                    "tm.tcpprogressive.rcvbufincr": "65536",
                    "tm.tcpprogressive.rcvbufincrsmall": "4",
                    "tm.tcpprogressive.rcvbufmax": "16777216",
                    "tm.tcpprogressive.rcvbufmin": "1048576",
                    "tm.tcpprogressive.rcvbufmininterval": "50",
                    "tm.tcpprogressive.rttthresh": "10",
                    "tm.tcpprogressive.sndbufbdpmultiplier": "4",
                    "tm.tcpprogressive.sndbufincr": "65536",
                    "tm.tcpprogressive.sndbufincrsmall": "2",
                    "tm.tcpprogressive.sndbufmax": "16777216",
                    "tm.tcpprogressive.sndbufmin": "1048576",
                    "tm.tcpprogressive.sndbufmininterval": "50",
                    "tm.tcpsegmentationoffload": "disable",
                    "tm.tcpudptxchecksum": "software-only",
                    "tm.tcpwoodsidefasterrecovery": "enable",
                    "tmm.http.passthru.invalid_content_length": "enable",
                    "tmm.resolv.timeout": "1"
                },
                "mySystem": {
                    "autoPhonehome": false,
                    "class": "System",
                    "cliInactivityTimeout": 0,
                    "consoleInactivityTimeout": 0,
                    "hostname": "scvelos",
                    "autoCheck": true,
                    "tmshAuditLog": true,
                    "guiAuditLog": false,
                    "mcpAuditLog": "enable",
                    "preserveOrigDhcpRoutes": false
                }
            },
            "async": true,
            "class": "Device",
            "label": "my BIG-IP declaration for declarative onboarding",
            "schemaVersion": "1.31.0",
            "controls": {
                "class": "Controls",
                "userAgent": "vscode-f5/3.8.3",
                "dryRun": false,
                "trace": false,
                "traceResponse": false
            }
        },
        "httpStatus": 200
    }

In the restnoded.log
Fri, 29 Jul 2022 09:09:13 GMT - fine: [f5-declarative-onboarding: restWorker.js] list localhost /tm/sys/service/lacpd/stats
Fri, 29 Jul 2022 09:09:13 GMT - fine: [f5-declarative-onboarding: restWorker.js] {"kind":"tm:sys:service:servicestats","generation":0,"selfLink":"https://localhost/mgmt/tm/sys/service/lacpd/stats?ver=<IP_ADDRESS>","apiRawValues":{"apiAnonymous":"lacpd                 down, not required\n"}}
Fri, 29 Jul 2022 09:09:13 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: got error {}
Fri, 29 Jul 2022 09:09:13 GMT - finest: [f5-declarative-onboarding: restWorker.js] typeof err object
Fri, 29 Jul 2022 09:09:13 GMT - finer: [f5-declarative-onboarding: restWorker.js] tryUntil error: mcpd status is lacpd                 down, not required
tries left: 0
Fri, 29 Jul 2022 09:09:13 GMT - finest: [f5-declarative-onboarding: restWorker.js] tryUntil: retryOrReject: numRemaining: 0 , code: {} , message: mcpd status is lacpd                 down, not required
Fri, 29 Jul 2022 09:09:13 GMT - finer: [f5-declarative-onboarding: restWorker.js] Max tries reached.
Fri, 29 Jul 2022 09:09:13 GMT - severe: [f5-declarative-onboarding: networkHandler.js] Error processing network declaration: tryUntil: max tries reached: mcpd status is lacpd                 down, not required
Fri, 29 Jul 2022 09:09:13 GMT - severe: [f5-declarative-onboarding: declarationHandler.js] Error processing declaration: tryUntil: max tries reached: mcpd status is lacpd                 down, not required
Fri, 29 Jul 2022 09:09:13 GMT - severe: [f5-declarative-onboarding: restWorker.js] Error onboarding: tryUntil: max tries reached: mcpd status is lacpd                 down, not required
Fri, 29 Jul 2022 09:09:13 GMT - info: [f5-declarative-onboarding: restWorker.js] Rolling back configuration
Fri, 29 Jul 2022 09:09:13 GMT - fine: [f5-declarative-onboarding: restWorker.js] list localhost /tm/sys/provision
Expected Behavior
DO deployment succeed
Actual Behavior
DO deployment failed, then rollback.
It seems there is a problem with lacpd daemon:
No LAG/Trunk configured on Velos partition, result is:
[root@localhost:/S1-green-P::Active:Standalone] config # bigstart status | grep lacpd
lacpd                 down, not required
[root@localhost:/S1-green-P::Active:Standalone] config #

@leondelyon3 Do you see this problem when using a Virtual Edition or a different hardware platform?

No, only with VELOS.

Thank you. I have added this issue to our internal product backlog as AUTOTOOL-3438.

@leondelyon3 please contact me at<EMAIL_ADDRESS>so i can prioritize

This issue has been resolved.


While loading plugin compileScssBatch  from package fourseven:scss:   native: %1 is not a valid Win32   application.

I did a meteor update from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>, and the fourseven:scss is acting nasty.
Any fix for this?
While loading plugin compileScssBatch  from package fourseven:scss:   native: %1 is not a valid Win32   application.

Can you try the new version 4.5.0

did not solve my problem :(


Possible race condition between counting requests and reporting additional data

We are using rack-attack and we want to report additional information for well-behaved clients.
In particular we want to inform the client of what the limit is, when it gets reset, and how many requests are remaining.
Consider some middleware that is doing something like this:
(Note: This is very similar to the sample code provided in the X-RateLimit headers for well-behaved clients section of the README, it just provides the data on every request, not just throttled ones)
class FooMiddleware
  def initialize(app)
    @app = app
  end

  def call(env)
    status, headers, body = @app.call(env)
    now = Time.now
    match_data = env['rack.attack.match_data']
    if match_data
      headers.merge!({
        'X-RateLimit-Limit' => match_data[:limit].to_s,
        'X-RateLimit-Remaining' => match_data[:limit] - match_data[:count],
        'X-RateLimit-Reset' => (now + (match_data[:period] - now.to_i % match_data[:period])).to_s
      })
    end
    [status, headers, body]
  end
end

This does the trick, but there is a race condition here.
Rack::Attack::Throttle#[] uses Rack::Attack::Cache#count to count the number of requests it has seen so far. The cache uses the following code to generate which key it is using
      def key_and_expiry(unprefixed_key, period)
        epoch_time = Time.now.to_i
        # Add 1 to expires_in to avoid timing error: http://git.io/i1PHXA
        expires_in = (period - (epoch_time % period) + 1).to_i
        ["#{prefix}:#{(epoch_time / period).to_i}:#{unprefixed_key}", expires_in]
      end

So here is the race condition.

the request enters the cache method at T1 (at the very end of the second)
that increments the counter (as expected)
the middleware that reports the headers uses Time.now but it is now T1+1 second
The X-RateLimit-Remaining has a value of the previous time frame, but the X-RateLimit-Reset has rolled over

To better illustrate this here is a series of headers that could happen
REQUEST 1 - This request processes as I would expect

HTTP/1.1 201 Created
Status: 201 Created
X-RateLimit-Limit: 300
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Remaining: 133

REQUEST #2
This request processes as I would expect. Notice that the Reset date is the same and the RateLimit-Remaining has decreased by one.

HTTP/1.1 201 Created
Status: 201 Created
X-RateLimit-Limit: 300
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Remaining: 132

REQUEST #3
This is where things get weird. You’ll notice that the Reset date has changed which should result in the Remaining value being reset, however, the remaining value did not reset.

HTTP/1.1 200 OK
Status: 200 OK
X-RateLimit-Limit: 300
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Remaining: 131

REQUEST #4
Now things are as they should be. The reset and remaining are now in sync.

HTTP/1.1 201 Created
Status: 201 Created
X-RateLimit-Limit: 300
X-RateLimit-Reset:<PHONE_NUMBER>
X-RateLimit-Remaining: 299

A solution here would be to also expose the time that was used in the match data so that anything that has access to the data can operating in the same timeframe that rack attack believes.
I've written up a possible PR that would provide this behaviour here:
https://github.com/kickstarter/rack-attack/pull/282

Thank you for reporting this.

Closed by #282

For the record, rack-attack 5.4.0 has been released with this included.


SnssFileType.Session isn't functional

Is reading of session files supposed to work at all? ccl_chromium_snss2.py just fails:
ValueError: 131 is not a valid SessionRestoreIdType

Microsoft Edge 131.0.2903.86

Hi there, I haven't tested with the most recent builds of Chrome but it was working with the data I had available when it then the code was published, yes.
The error message is correct, 131 is not a valid SessionRestoreIdType (see Chromium source-code here: https://source.chromium.org/chromium/chromium/src/+/main:components/sessions/core/session_service_commands.cc;l=29), so it might be that something has changed in the format since this was built.
If you are able to share the data I could take a look at it, otherwise I'll try it with version 131 data, but unless it's a fairly trivial change, I won't be able to dig in much before the end of the year due to other comitments, sorry.

It doesn's appear that anything has changed in the core serialization, as far as Chromium is concerned: https://source.chromium.org/chromium/chromium/src/+/main:components/sessions/core/serialized_navigation_entry.cc;bpv=1
The format is based around a pickle, which is prefixed with a length, so it seems less likely that the record buffer is being read incorrectly, so my initial guess is that this might be either: an Edge specific customization; or a corrupt file.

UpdateL I can confirm that I'm getting a similar error with Edge but not Chrome, so it's looking like a Edge customization to the format.

I have confirmed that Edge is using some custom command IDs. I found that 132 is also being used in my data. Fixed in a8a1924665d090836f4325ed4eab9bb549ebb3d4 - let me know if thius resolves your issue please.

I'll look at implementing a "bad record handler" like I have in a few other places so that the calling code gets the full context of the reason and location of the bad data.  I like an exception by default, because people don't generally report issues / I don't notice changes to the underlying format if it doesn't crash.
In the meantime you could add the following to the SnssFile class to work around it:
    def iter_session_commands2(self):
        self.reset()
        while True:
            try:
                command = self._get_next_session_command()
            except ValueError as ex:
                print(ex, file=sys.stderr)
                continue
            yield command

(And then change any calls to the original version of the function to this version, or just overwrite the original function I suppose).

I've renamed the issue to represent the current plan of action to resolve this more long-term. I'll leave the issue open on that basis.


debug print improvements

This PR contains a load of debug printing improvements from several branches I'm working on, in particular latest libfabric changes. Pushing this to see if it causes any compilation problems on dashboards, as I will need it merged before other branches.

Normally we use east-const notation in our code base... I'd appreciate it if you adapted to this. Thanks!

Is this something that clang-format can do fo us? I am not accustomed to writing consts on the right and I don't want to change all this by hand.

Normally we use east-const notation in our code base... I'd appreciate it if you adapted to this. Thanks!

Is this something that clang-format can do fo us? I am not accustomed to writing consts on the right and I don't want to change all this by hand.

The clang-format people  say it's not the job of their tool to do that (clang-format never changes the sequence of tokens). They think this is something clang-tidy could provide. I'm not sure if somebody has actually implemented this there, however.

The clang-format people say it's not the job of their tool to do that (clang-format never changes the sequence of tokens). They think this is something clang-tidy could provide. I'm not sure if somebody has actually implemented this there, however.

There is work on-going in clang-format to add support for an east-west const fixer
https://reviews.llvm.org/D69764
I knocked up a quick regex search to find all the places where we are using west const instead of east const - it's a lot. I am going to push a cleanup patch to fix the cxx-14 variadic print (thanks, I've used your patch, plus some other improvments) and then a separate one with east const fixes for the debug printer.

There is work on-going in clang-format to add support for an east-west const fixer
https://reviews.llvm.org/D69764

Cool, I was not aware of that.

I knocked up a quick regex search to find all the places where we are using west const instead of east const - it's a lot. I am going to push a cleanup patch to fix the cxx-14 variadic print (thanks, I've used your patch, plus some other improvments) and then a separate one with east const fixes for the debug printer.

Thanks, much appreciated.

I made a bunch of cleanups and fixed some old stuff that wasn't updated. @hkaiser was correct in saying that debug arguments that are function returns are evaluated even in debug paths, so I added a lazy eval wrapper (had to use a macro unfortunately) and added a unit test that checks that the functions/features are behaving as tested. Any other tweaks can wait for a new PR or the next release.

Add the environ check as suggested. I actually plan on removing that stuff and replacing it with something that uses the batch environment checks that already exist - but I will leave that until after the mpi branch is finished as I am actually using this in the mpi testing at the moment and it can wait as it is not urgent.

Let's get this is asap.

After several rounds of fixing the windows/mac builds and sorting out some silly warnings etc - this now looks ok on dashboards - the fails being returned from tests are unrelated.