Show previous/next month's days in current month's view?

Is there a way I can show the previous and next months days in the current month view?
Example:

+1

Had to do this recently and here's what I eneded up with:
const picker = new Litepicker({
  ...
}};
...
picker.on('render:month', (month, date) => {
  const days = month.querySelector('.container__days');
  const pre = days.querySelectorAll(':not([class])') || [];
  const daysInMonth = days.children.length - pre.length;

  const calendars = picker.calendars;
  const isFirst = calendars[0].isSame(date, 'day');
  const isLast = calendars[calendars.length - 1].isSame(date, 'day');

  if(isFirst) {
    const before = date.clone();
    pre.forEach((element) => {
      days.removeChild(element);
      before.subtract(1, 'day');
      const day = picker.renderDay(before);
      day.classList.add('is-pre');
      days.prepend(day);
    });
  }

  if(isLast) {
    const after = date.clone().add(daysInMonth, 'days');
    const maxDays = days.children.length >= 35 ? 42 : 35;
    while(days.children.length < maxDays) {
      const day = picker.renderDay(after);
      day.classList.add('is-post');
      days.appendChild(day);
      after.add(1, 'day');
    }
  }
});

And some css to distinguish those days:
&.is-pre, &.is-post {
  font-weight: 300;
  color: var(--litepicker-is-locked-color);

  &:hover {
    color: var(--litepicker-is-locked-color);
  }
}

This was a pretty easy drop-in for me, it also works with the range plugin!
Hopefully it helps anybody ending up here :)
Cheers!


Added mixin for bordered arrows

So you can get borders that look like this:
http://i.minus.com/ibmuYBGrlkwrTP.png
By using the mixin this way:
.arrow {
  #borderArrow > .below(15px, 1px, @color, #f9f9f9);
}

You can use .below, .above, .left, .right and the parameters are: width of the arrows, border width, color of the border, color of the inside
Given this HTML:

Please note that they're not adding any new features to 1.x (master) anymore. If you want a pull request to be accepted, you make modification on branch 2.0-wip.

Please open a new pull request against 2.0-wip.


Create and edit Datasource

fix #251

* when I try to update a datasource, I can't update the name. I think we can allow this. The slug cannot be, but the name, yes ?

In workspace, we have decided to not allow the modification of its name. I have reproduce it in datasource to be consistent.

* when I reload a page like `http://localhost:3000/w/pouic/datasource/test`, in the browser, I have a message "An error has occured" (see image). Could you make this work ?
  ![image](https://user-images.githubusercontent.com/2027964/264391051-48e5fb4b-ee23-4e30-ae75-e2a0902aa5bc.png)

yep, it's a issue with the authent token (cf mail)

* for a `local` datasource, the user don't need to set a `connection` as we generate one on the backend side. actually, validator say it's mandatory, I need to upgrade the validator before update this part (this is not blocking, I create the issue [[datasource] Allow create a local datasource without connection property #254](https://github.com/locokit/locokit/issues/254) for that )

Concerning the "non" update of the name property, I create the issue https://github.com/locokit/locokit/issues/255 to track progress and not forget to implement it on the datasource.


Helm automated rollback failure

We are trying to implement helm automated rollback using the --atomic flag, if the helm upgrade fails.
Below is the helm command we use to invoke a helm install/upgrade.
Helm command: helm upgrade --install --namespace myNamespace myReleaseName . -f value.yaml  --debug --timeout=90s --cleanup-on-fail --atomic
When the helm upgrade does not have any issues it will deploy successfully. If the helm upgrade is having issues after timeout is reached it will start rollback and it fails with the error Error: UPGRADE FAILED: release myReleaseName failed, and has been rolled back due to atomic being set: client rate limiter Wait returned an error: context deadline exceeded.
Despite encountering the error below, the previously successful deployment will remain available, while any new deployments created as part of the current operation will be deleted. However, the primary concern lies in the fact that the Helm command generates an error, potentially causing confusion for end users.
Complete error stack details are given below.
history.go:56: [debug] getting history for release myReleaseName
upgrade.go:155: [debug] preparing upgrade for myReleaseName
upgrade.go:163: [debug] performing update for myReleaseName
upgrade.go:356: [debug] creating upgraded release for myReleaseName
client.go:393: [debug] checking 3 resources for changes
client.go:693: [debug] Patch Service "myReleaseName" in namespace myNamespace
client.go:693: [debug] Patch Deployment "myReleaseName" in namespace myNamespace
client.go:693: [debug] Patch VirtualService "myReleaseName" in namespace myNamespace
upgrade.go:428: [debug] waiting for release myReleaseName resources (created: 0 updated: 3  deleted: 0)
wait.go:48: [debug] beginning wait for 3 resources with timeout of 1m30s
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
ready.go:303: [debug] Deployment is not ready: myNamespace/myReleaseName. 0 out of 1 expected pods are ready
upgrade.go:468: [debug] warning: Upgrade "myReleaseName" failed: client rate limiter Wait returned an error: context deadline exceeded
upgrade.go:486: [debug] Upgrade failed and atomic is set, rolling back to last successful release
history.go:56: [debug] getting history for release myReleaseName
rollback.go:65: [debug] preparing rollback of myReleaseName
rollback.go:131: [debug] rolling back myReleaseName (current: v2, target: v1)
rollback.go:72: [debug] creating rolled back release for myReleaseName
rollback.go:78: [debug] performing rollback of myReleaseName
client.go:393: [debug] checking 3 resources for changes
client.go:693: [debug] Patch Service "myReleaseName" in namespace myNamespace
client.go:693: [debug] Patch Deployment "myReleaseName" in namespace myNamespace
client.go:693: [debug] Patch VirtualService "myReleaseName" in namespace myNamespace
wait.go:48: [debug] beginning wait for 3 resources with timeout of 1m30s
rollback.go:257: [debug] superseding previous deployment 1
rollback.go:84: [debug] updating status for rolled back release for myReleaseName

Error: UPGRADE FAILED: release myReleaseName failed, and has been rolled back due to atomic being set: client rate limiter Wait returned an error: context deadline exceeded

helm.go:84: [debug] client rate limiter Wait returned an error: context deadline exceeded
release myReleaseName failed, and has been rolled back due to atomic being set
helm.sh/helm/v3/pkg/action.(*Upgrade).failRelease
  helm.sh/helm/v3/pkg/action/upgrade.go:519
helm.sh/helm/v3/pkg/action.(*Upgrade).reportToPerformUpgrade
  helm.sh/helm/v3/pkg/action/upgrade.go:380
helm.sh/helm/v3/pkg/action.(*Upgrade).releasingUpgrade
  helm.sh/helm/v3/pkg/action/upgrade.go:440
runtime.goexit
  runtime/asm_amd64.s:1650
UPGRADE FAILED
main.newUpgradeCmd.func2
  helm.sh/helm/v3/cmd/helm/upgrade.go:229
github.com/spf13/cobra.(*Command).execute
  github.com/spf13/cobra@v1.8.0/command.go:983
github.com/spf13/cobra.(*Command).ExecuteC
  github.com/spf13/cobra@v1.8.0/command.go:1115
github.com/spf13/cobra.(*Command).Execute
  github.com/spf13/cobra@v1.8.0/command.go:1039
main.main
  helm.sh/helm/v3/cmd/helm/helm.go:83
runtime.main
  runtime/proc.go:267
runtime.goexit

Output of helm version:
version.BuildInfo{Version:"v3.14.0", GitCommit:"3fc9f4b2638e76f26739cd77c7017139be81d0ea", GitTreeState:"clean", GoVersion:"go1.21.6"}
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.1", GitCommit:"e4d4e1ab7cf1bf15273ef97303551b279f0920a9", GitTreeState:"clean", BuildDate:"2022-09-14T19:49:27Z", GoVersion:"go1.19.1", Compiler:"gc", Platform:"darwin/amd64"} Kustomize Version: v4.5.7 Server Version: version.Info{Major:"1", Minor:"25", GitVersion:"v1.25.16", GitCommit:"c5f43560a4f98f2af3743a59299fb79f07924373", GitTreeState:"clean", BuildDate:"2023-11-15T22:28:05Z", GoVersion:"go1.20.10", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.): GKE
Can someone help me here on how to have successfully rollback so that helm command will exit gracefully.
Let me know if any furrther details is needed.

The --atomic upgrade flag just means "rollback-on-failure" (I wish it was called such). As that implies, if Helm determines an error has happened during the upgrade, it will attempt to rollback to the previous version (which effectively means "upgrade" to the previous version).
It is important to note, that all this is driven by Helm client-side. The name atomic is slightly misleading. If Helm e.g. can't contact the cluster correctly e.g. due to being rate limited (like appears to be happening here). Then it won't be able to rollback (upgrade to the previous release).

Any thoughts/PR suggestions to improve the docs / cli help would be appreciated

The --atomic upgrade flag just means "rollback-on-failure" (I wish it was called such). As that implies, if Helm determines an error has happened during the upgrade, it will attempt to rollback to the previous version (which effectively means "upgrade" to the previous version).
It is important to note, that all this is driven by Helm client-side. The name atomic is slightly misleading. If Helm e.g. can't contact the cluster correctly e.g. due to being rate limited (like appears to be happening here). Then it won't be able to roll back (upgrade to the previous release).

@gjenkins8 In my case after upgrade failure, it says rollback due to atomic is set and it fails. But from the functionality point of view, rollback worked as I see pods that are running are off the previous stable deployment, the latest build that failed will be cleaned up(Workloads as been removed). My only concern here is that the helm command didn't exit gracefully.
Not sure if this is the expected behavior to throw the error from the helm side.  Please confirm this.

Any thoughts/PR suggestions to improve the docs / cli help would be appreciated

I feel from a documentation point of view instead of atomic to enable automated rollback, --enableRollback=true should be used which will be more descriptive by argument name itself. A dedicated section on how the automated rollback in Helm works also will be useful as we don't have much documentation on this topic.

Friend, I have the same error, what did you do to solve it?
This is how I have the pipeline:
arguments: '--install --namespace default --values $(Build.SourcesDirectory)/my-charts/values.yaml --debug --timeout 90s --cleanup-on-fail --atomic'


Reference number display update

Added tests for hiding remission register text and showing reference number
Updated optional display/style of confirmation block
only display the right hand guidance on remission register for
evidence_check and part_payments when the reference date has passed
styled the reference number display when completing an application form

Addresses the following tickets
109886940
110402860
110403354
110403438

:+1: looks all good!


Chapter 6 : Example material

This merge request contains the example material for "Chapter 6, Automatically Generating Documentation with CMake".

I don't think it's redundant. I find it more readable this way. It is like
saying "it is a virtual function, and I am overriding it." I am looking
override in the same way as delete or const.
On Fri, 5 Nov 2021, 01:36 Dominik Berner, @.***> wrote:

@.**** commented on this pull request.
In chapter_6/ex01_doxdocgen/include/chapter6/ex01/calculator.hpp
https://github.com/PacktPublishing/CMake-Tips-and-Tricks/pull/18#discussion_r743250229
:

@param [in] augend The number to which @p addend is added

@param [in] addend The number which is added to @p augend

@return double Sum of two numbers, @p lhs and @p rhs

*/
virtual double sum(double augend, double addend) override;

/**

Calculate the difference of @p rhs from @p lhs

@param [in] minuend    The number to which @p subtrahend is subtracted

@param [in] subtrahend The number which is to be subtracted from @p minuend

@return double Difference of two numbers, @p minuend and @p subtrahend

*/
virtual double sub(double minuend, double subtrahend) override;

It's not wrong, it's just redundant ;)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/PacktPublishing/CMake-Tips-and-Tricks/pull/18#discussion_r743250229,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCHY6E4VJRIGRLLPT6LQE3UKMDINANCNFSM5HLUSYKA
.


support fragmented MPEG-2 audio frames

Codecov Report

Merging #259 (d7628f2) into main (84fcc01) will increase coverage by 0.08%.
The diff coverage is 91.66%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #259      +/-   ##
==========================================
+ Coverage   86.23%   86.31%   +0.08%
==========================================
  Files          88       88
  Lines        9107     9192      +85
==========================================
+ Hits         7853     7934      +81
- Misses        975      977       +2
- Partials      279      281       +2

Impacted Files
Coverage Δ

pkg/formats/rtpmpeg2audio/decoder.go
88.05% <85.18%> (-11.95%)
:arrow_down:

pkg/formats/rtpmpeg2audio/encoder.go
86.40% <96.15%> (+12.83%)
:arrow_up:

pkg/formats/rtpmpeg4audio/decoder.go
79.61% <100.00%> (-1.16%)
:arrow_down:

pkg/formats/rtpmpeg4audio/encoder.go
96.61% <100.00%> (-0.04%)
:arrow_down:

... and 1 file with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Update to the latest go rules, which fixes the build on OSX

This change is

Jenkins job mixer/presubmit passed

jenkins rebuild mixer/e2e-smoketest

Ug, Jenkins keeps flaking due to github rate limits.
jenkins rebuild mixer/e2e-smoketest

jenkins rebuild mixer/presubmit
jenkins rebuild mixer/e2e-smoketest

jenkins rebuild mixer/e2e-smoketest

jenkins rebuild mixer/presubmit

Jenkins job mixer/presubmit passed

Jenkins job mixer/e2e-smoketest passed

Jenkins job mixer/pilot-regression passed


Fix env vars regression for targets

fixes regression where target environment vars are ignored;
adds unit tests for regression;
fixes issue where command line --listen-port is ignored for qx serve;
better message when qx serve port is in use already

Urgent bug fix, fast track, assuming @hkollmann' approval. Thank you @johnspackman !


feat: enforce E164 when createNumber

#449

@xquanluu thanks for the PR. I will take a first look at this next week.

@xquanluu Sorry for the delay.
It was a bit difficult to coordinate due to the holidays.
Thanks again for the PR.


Adds trace IDs to dependency links

TODO: make this conditional, as existing dependency linker jobs won't
need IDs and keeping them might make spark jobs move more data than
they currently need.
See #1206

ps not merging intentionally until we get some experience with the
experiment. reason is that this is api breaking

for those wondering.. pausing while we investigate what else is out there (ex haystack has some aggregation tools as well.. not sure if there is any overlap until we ask)

I think we can pick this back up in javascript after #2731

moved most code out in this https://github.com/openzipkin/zipkin/pull/2803

moved to branch archive/links-with-traceIds


Feat/scratch sensor

@xram I don't really like the name as well. I did not call it SwipeSensor because I thought the SwipeSensor could a higher level component that internally uses ScratchSensor and based on dx and dy create swiping events.
I also did not feel like calling it a DragSensor, because I thought there might be other things that will actually deal with "dragging", although maybe DragSensor would be a better name.


How to embed synopsis and description in meta comment?

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I intentionally remove or skip any mandatory* field

Checklist

[X] I'm asking a question and not reporting a bug or requesting a feature
[X] I've looked through the README
[X] I've verified that I have updated yt-dlp to nightly or master (update instructions)
[X] I've searched known issues and the bugtracker for similar questions including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Please make sure the question is worded well enough to be understood
Hi all.
I do need to embed both the URL of the downloaded video and his description into the file Comment description field and I tried a few versions of the following command but unfortunately I can't make the yt-dlp to embed both field. It is always embedding one or the other field.
--parse-metadata 'synopsis:%(webpage_url)s + description:(?s)(?P<meta_comment>.+)' --add-metadata
--parse-metadata 'synopsis:%(webpage_url)s description:(?s)(?P<meta_comment>.+)' --add-metadata
--parse-metadata 'synopsis:%(webpage_url)s' + 'description:(?s)(?P<meta_comment>.+)' --add-metadata
What is the correct syntax to embed both the synopsis and description into the same Comment field?
Best regards.
Provide verbose output that clearly demonstrates the problem

[ ] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] If using API, add 'verbose': True to YoutubeDL params instead
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
No response

--parse-metadata "%(webpage_url)s %(description)s:%(meta_comment)s" --embed-metadata

--parse-metadata "%(webpage_url)s %(description)s:(?s)(?P<meta_comment>.+)" --embed-metadata

Thank you. It is working. It is possible to also insert an empty line between webpage_url and meta_comment?
Like:
webpage_url

meta_comment

you'd have to put an actual newline in the quoted argument, e.g.:
--parse-metadata "%(webpage_url)s

%(description)s:(?s)(?P<meta_comment>.+)" --embed-metadata

not sure if that will work in your shell. if not, you can add it to your config file (or create one if you don't have one already)


[APIM-Analytics-3.2.0] Purging task halted Error on Analytics Node

Description:
When there is an aggregation issue, what we are usually doing is restarting the worker node and simulate events to initiate the aggregation. But even if we ask to do that, for throttling and fault aggregation flows, an event might not trigger.
So the ApiThrottledOutAgg and the Falult aggregations will remain in the previous state and the rest of the aggregations will trigger and the issues of other aggregations will resolve. But after some time when the automatic purging is triggered (default after 60 min) the "Purging task halted!!!" error will continuously printed for throttling and fault flows and the purging will also halt.
[2022-05-16 05:12:17,843] ERROR {io.siddhi.core.aggregation.IncrementalDataPurger} - Purging task halted!!!. Data purging for table: ApiThrottledOutAgg_HOURS with a retention of timestamp :<PHONE_NUMBER>810 didn't executed since parent ApiThrottledOutAgg_DAYS table does not contain values of above period.
Hence we need to fix this at code level.
Affected Product Version:
APIM - Analytics -3.2.0

Public fix added with https://github.com/wso2/carbon-analytics/pull/2002


Relax bundler dependency to allow bundler v2.0

Hi @unagiootoro
Great work!
I find that bundler v2 does not work in your project. Why don't you update a gemspec file?
Style 1
https://github.com/rubocop-hq/rubocop/blob/master/rubocop.gemspec#L45
Style 2
https://github.com/ruby-numo/numo-narray/blob/2d05d8fde74df180ead1e68178f5b5abed7fe386/numo-narray.gemspec#L31-L35

Thank you for pull request.
I will correspond in order.

Thank you!


[UBS/order]The user can enter more than 255 characters in the 'Comment to the address' field on the 'New address' popup.

Environment: Windows 10 Pro Version 22H2 OS 19045.3803 Google Chrome Version 120.0.6099.200 (Official Build) (64-bit)
Reproducible: always
Build found: 03/03/2024
Preconditions:
1.The site https://www.greencity.social/#/ubs is opened.
2.The user is authorized.
3. The 'order' button is clicked.
4. The number of packages entered.
5. The 'Next' button is clicked.
6. 'Add another address' button is clicked.
Steps to reproduce:
1.Type address.
2.Write or paste more than 255 characters in the 'Comment to the address' field.
Actual result
The field is highlighted in blue-red, and the user can continue entering characters.
Expected result
The field is highlighted in red, and the user cannot continue entering characters.
Labels to be added
"Bug", Priority ("pri: "), Severity ("severity:"), Type ("UI, "Functional"), "API" (for back-end bugs).

I will remove the blue highlight in case of an error, but there is no need to limit the input. The user can enter more than 255 characters and then a message will appear that the comment is not valid. If you limit the input to 255 characters, the user will never see a validation message.


[Feature Request] Preconfigure and add documentation for Home Assistant in the UI

With the great new Rhasspy tutorial it is quite easy to setup Rhasspy on a new Pi.
It will react to a wake word and parse intents. But actually doing something useful with the intents is still more complicated for Home Assistant users than it needs to be.
Suggestions:

Enable "Send intents" by default for Home Assistant. It is the intended way to do it now and more importantly:  There are some build in intents (https://developers.home-assistant.io/docs/intent_builtin)
Either change/add the initial default intents of Rhasspy to those builtin intent names or add them to the user configuration the first time the user enables Home Assistant Intent handling.

Those two should should be very easy to do (at least the first option of suggestion 2).
Slots
Those built in intents of Home Assistant need the names of the entities as Slot Value. I see two possibilities to help the user here:

In the Home Assistant intent handling configuration add a help text like (fix my english):
To use the build in intents of Home Assistant together with the preconfigured sentences create a new slot "hassnames" in Rhasspy and paste the output of the following template (link to open text in a dialog) executed in the "Developer Tools/Template" tab in home assistant into it.
hass-names.txt
(another option is a more complex version instructing the user to create multiple slots for different types of entities with more than one template "script)
Provide a simple slot-generation-script that queries Home Assistant for all entities in the different domains (light, switch, cover, scenes, groups) using the configured API data and configure it when the user selects Home Assistant.

Conclusion
Doing some of those things would greatly improve the out of the box experience with Home Assistant and provide the user with a working voice assistant without any configuration in Home Assistants files.

I agree, I've switched to "Send Intents" as the default. Should be in the next release.
I'm working on an example here: https://github.com/rhasspy/rhasspy/tree/master/examples/homeassistant
This uses the built-in intents and automatically downloads entities using a slot program. Let me know what you think.


update exports field documentation

add new node.js features for exports field
add support table for all general features
add rollup, esinstall and wmr to supported tools

@LarsDenBakker @lukastaegert I added rollup to the list of supported tools.
@matthewp @drwpow I added esinstall to the list of supported tools.
@developit I added wmr to the list of supported tools.
Could you review if I listed supported features and conditions for your tools correctly?
Here is a readable preview: https://webpack-js-org-git-content-exports-field.webpack-docs.now.sh/guides/package-exports/

@LarsDenBakker @lukastaegert I added rollup to the list of supported tools.
@matthewp @drwpow I added esinstall to the list of supported tools.
@developit I added wmr to the list of supported tools.
Could you review if I listed supported features and conditions for your tools correctly?
Here is a readable preview: https://webpack-js-org-git-content-exports-field.webpack-docs.now.sh/guides/package-exports/

Hey @sokra - sent you a DM about thoughts on migrating this to somewhere central, but the issues you pointed out for WMR are all accurate. (yay, stuff to fix!)

Hey @sokra - sent you a DM about thoughts on migrating this to somewhere central, but the issues you pointed out for WMR are all accurate. (yay, stuff to fix!)

@sokra rollup supports "." property, normal property and property ending with / as well.
@web/dev-server and @web/test-runner both support the same features as rollup.

@sokra rollup supports "." property, normal property and property ending with / as well.
@web/dev-server and @web/test-runner both support the same features as rollup.

@sokra I think that looks correct for esinstall. We're going to add support for some of this relatively soon, but I'll send a PR here if that happens after you've merged.

@sokra I think that looks correct for esinstall. We're going to add support for some of this relatively soon, but I'll send a PR here if that happens after you've merged.


Fix some small errors on StorageClass NodeSelector.

For ticket #6392

Here's a screen shot from installing the amended Longhorn chart from my branch (note the "whith" changed to "with".  Most of the changes are less visible, but are for agreement with values.yaml.

Discussed with @james-munson, the node selector here is for volume's replica scheduling. The current description We use NodeSelector when we want to bind PVC via StorageClass into desired mountpoint on the nodes tagged with its value is a bit confusing. May be we should change it to mention that this is for replica scheduling logic

Discussed with @james-munson, the node selector here is for volume's replica scheduling. The current description We use NodeSelector when we want to bind PVC via StorageClass into desired mountpoint on the nodes tagged with its value is a bit confusing. May be we should change it to mention that this is for replica scheduling logic

Let's do this in the ticket https://github.com/longhorn/longhorn/issues/4776


[bug] Multidrag select with SHIFT doesn't respect filtered items

Describe the bug
When I am using multidrag, I select an item, hold shift while selecting another item and all the items between these 2 will be selected too.
I have a list with draggable items on it. Some of these items are filtered out by the filter property on the Sortable configuration.
If one of these filtered items are between the 2 selected items (while holding SHIFT), I can select and sort it.
To Reproduce
Steps to reproduce the behavior:

Select an item before a filtered item
Hold SHIFT and select a item after a filtered item
The filtered item will be selected
Drag all the items and the filtered item will be dragged too

Expected behavior
The filtered items shouldn't be selected.
Information
I think the codesandbox will be enough to understand the bug.
Inside it there will be 4 items. Item "three" is filtered out and you can't move it (unless you are using the bug described here).
Versions
sortablejs = 1.10.2
@types/sortablejs = 1.10.4
Additional context
Add any other context about the problem here.
Reproduction
codesandbox: https://codesandbox.io/s/bug-report-on-sortable-9s6wc?file=/src/index.js

Fixed in 1.15.4


Fix install command. Needs name of file in case building in a sandbox.

Building in a sandbox is common in many package systems. Install will often be installing into an empty folder. In this case install would create a file at say /usr/bin if CMD_DESTDIR were set to /usr, new version will create the /usr/bin directory and put the buildg file within the /usr/bin/buildg (the desired effect).

Done


ENH: expose retry status config and handle retry in ES sink

Issue #, if available:
#9
Description of changes:
This PR
(1) Exposes retry status as a list in the RetryConfiguration
(2) Added RetryUtils and test cases to control retry backoff time.
(3) Add retry handling in ElasticsearchSink
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Cannot push new commits. Will open a new PR


import error

error

using
import Ajv from 'ajv';

export const deepClone = (obj) => {
  console.log('深复制');
  return JSON.parse(JSON.stringify(obj));
};

export const checkJSON = (value, schema) => {
  const ajv = new Ajv();
  const validate = ajv.compile(schema);
  const valid = validate(value);
  if (!valid) return validate.errors;
  return true;
};

this is not an Ajv issue - you need to change configuration of your build process.
Possibly the issue is that Ajv is compiled to JS 2018, and you need to recompile typescript to an earlier target to be compatible with your build/environment.

this is not an Ajv issue - you need to change configuration of your build process.
Possibly the issue is that Ajv is compiled to JS 2018, and you need to recompile typescript to an earlier target to be compatible with your build/environment.

@epoberezkin Solved it, it was my fault, thank you


Fix compile issues

Fixes all compilation warnings and changes the CI configuration file to be a bit more forgiving.

I added some more changes to the code based on the complaints thrown by clippy.


batch insert TxOut

Follow up to https://github.com/input-output-hk/cardano-db-sync/pull/937

With the first patch, I am seeing a 10-20% speed improvement. Curious to see if this has a further measurable improvement.


UCP install error

While updating through the module I encountered this error:
Please wait while module actions are performed
Installing ucp
Updating tables ucp_sessions...Done
System : debian
icu, pkg-config or pkgconf is not installed. You need to run: apt-get install icu libicu-devel pkg-config pkgconf
Error(s) installing ucp:
Failed to run installation scripts
Updating Hooks...Done
looks like the tiredofit image experienced the same issue in the past:
https://github.com/tiredofit/docker-freepbx/issues/116

Me too. Running
#apt-get install icu libicu-devel pkg-config pkgconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package icu
E: Unable to locate package libicu-devel
root@615baa524e91:/# apt-get install  pkg-config pkgconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
pkgconf : Breaks: pkg-config (>= 0.29-1)


Prepare 1.9.2-dev.0001

This PR prepares the internal release 1.9.2-dev.0001.
Please note that all commits up to (and including) 39650285cfee2771a2f65ac8d9a7a10357a70e68 are already on main. This PR serves as a way to discuss all recent changes.
Once it's merged, I will rebase the remaining changes onto main.

latest-release was at c6681ed3762fdb3bda63fc9c147a369d3812f7d9.


Drop the support for CRI v1alpha2

https://github.com/Mirantis/cri-dockerd/blob/9a8a9fe300c829ed292d4bb97d8626c3077f6b25/core/service_alpha.go#L25
Kubernetes has dropped the support for CRI v1alpha2 in Kubernetes v1.26:

https://github.com/kubernetes/kubernetes/pull/110618

v1.25, the last release to support v1alpha2, has already reached the EOL: https://kubernetes.io/releases/patch-releases/#non-active-branch-history
So I guess cri-dockerd should be ready to drop it too?

As long as it is documented (and something like 0.4?), I think the feature can be removed also from cri-dockerd...
Previously the versioning of tools like crictl was unclear, and thus many tried to use them with e.g. new containerd and failing. But now the release of cri-tools and cni-plugins has been bundled with the kubeadm installation, so that users need to upgrade their CRI and CNI with their k8s installation. There was already the issue of cri-dockerd not supporting k8s versions before 1.24, where dockershim should be used instead. But I think* 1.24-1.26 should support CRI v1?
* looking at for instance the https://containerd.io/releases/#kubernetes-support table, where it says "1.23+"
https://kubernetes.io/blog/2021/12/07/kubernetes-1-23-release-announcement/#container-runtime-interface-cri-v1-is-default


KWStyle fails in rtk::ComputeAttenuationCorrectionBackProjection

m_ex1 is not an accepted name for ITK members. I would correct it if I knew what is the proper name... If this is the article name, use m_Ex1, that should pass kwstyle (checked at commit time now). @arobert01, can you handle this or let me know where this name comes from?

Yes indeed, I used the notations from the article for naming the variables. Do you want me to rename it to m_Ex1 ?

Thanks, I'll handle it. There are a few other errors that popped up, I'll fix them altogether.


Access to ordered timings data

I see that in all implementations there is a zip-iterator that associates names and timings, but they are subsequently inserted into a hashmap loosing the ordering.
What is the reasoning and would you accept a PR changing it to get out a &[(String, Duration)] and internally just store it as a Vec instead to not loose the ordering?
I guess this is just convenient syntax rather than an intentional summation of same names? I have several blit which now get summed. Could ofc change names
*self.timings.entry(pass_name).or_default() += time;

No strong opinion on this. In fact, the first implementation was doing exactly &[(String, Duration)]. However, when I started running with it, I realized that I have multi-pass stages, and seeing 5-20 entries of the same name is just not practical. That's where I figured that building a hashmap instead would make this nicer.
If one needs detailed timings, one should use the platform-specific tools. Like NVidia Nsight Graphics, or RenderDoc.
The built-in timings are there only for high-level overview.

I use the Radeon GPU Profiler for all profiling, but it's nice to also have the built in overview, and getting them in the order of execution is the way I prefer reading them.
I see the use-case for merging the names, though since that can be done very easily on-top of the slice output I think still not having the API remove the order is better

that can be done very easily on-top of the slice output

Indeed, I'll just do this conversion locally.


How to execute chrome directly from its path?

Hello!
I'm trying to build an AWS Lambda function that shells out to execute a command-line A11Y checker called axe-cli. This checker uses headless chrome, which is expected to be in the PATH.
I've tried to include headless chrome using the serverless-plugin-chrome plugin, but I keep getting an WebDriverError: unknown error: cannot find Chrome binary error.
Here's the code for this function, what am I doing wrong? Thanks!
https://gist.github.com/jaimeiniesta/2c2c42a6487b4a468f64dc9238d41a26

To make the question shorter, what is the path to the Chrome executable installed by serverless-chrome?

Hi @jaimeiniesta. On AWS Lambda, the headless shell should be at /var/task/node_modules/@serverless-chrome/lambda/dist/headless-chromium.

Thanks!

So, I tried adding this to the PATH but still doesn't work in AWS Lambda, it looks like selenium-webdriver can't find it:
2018-07-09 13:39:37.224 (+02:00)	bfd787ed-836c-11e8-b351-eb04a73ff2bb	Path is:/var/lang/bin:/usr/local/bin:/usr/bin/:/bin:/var/task/node_modules/@serverless-chrome/lambda/dist/
START RequestId: bfd787ed-836c-11e8-b351-eb04a73ff2bb Version: $LATEST
2018-07-09 13:39:37.773 (+02:00)	bfd787ed-836c-11e8-b351-eb04a73ff2bb	Command to run: ./node_modules/axe-cli/axe-cli http://jaimeiniesta.com --save pGd6e6m8tzsD250jVxWcbu6t5Cqd3MuthYj2zhHPCOxfWbeHM01531136377771.json -d /tmp
2018-07-09 13:39:39.028 (+02:00)	bfd787ed-836c-11e8-b351-eb04a73ff2bb	{ Error: Command failed: ./node_modules/axe-cli/axe-cli http://jaimeiniesta.com --save pGd6e6m8tzsD250jVxWcbu6t5Cqd3MuthYj2zhHPCOxfWbeHM01531136377771.json -d /tmp
/var/task/node_modules/selenium-webdriver/lib/promise.js:2626
        throw error;
        ^

WebDriverError: unknown error: cannot find Chrome binary
  (Driver info: chromedriver=2.40.565383 (76257d1ab79276b2d53ee976b2c3e3b9f335cde7),platform=Linux 4.9.93-41.60.amzn1.x86_64 x86_64)
    at WebDriverError (/var/task/node_modules/selenium-webdriver/lib/error.js:27:5)
    at Object.checkLegacyResponse (/var/task/node_modules/selenium-webdriver/lib/error.js:546:15)
    at parseHttpResponse (/var/task/node_modules/selenium-webdriver/lib/http.js:509:13)
    at doSend.then.response (/var/task/node_modules/selenium-webdriver/lib/http.js:441:30)
    at process._tickCallback (internal/process/next_tick.js:109:7)
From: Task: WebDriver.createSession()
    at Function.createSession (/var/task/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
    at Function.createSession (/var/task/node_modules/selenium-webdriver/chrome.js:761:15)
    at createDriver (/var/task/node_modules/selenium-webdriver/index.js:170:33)
    at Builder.build (/var/task/node_modules/selenium-webdriver/index.js:642:16)
    at startDriver (/var/task/node_modules/axe-cli/lib/webdriver.js:33:27)
    at testPages (/var/task/node_modules/axe-cli/lib/axe-test-urls.js:11:10)
    at Object.<anonymous> (/var/task/node_modules/axe-cli/index.js:73:1)
    at Module._compile (module.js:570:32)
    at Object.Module._extensions..js (module.js:579:10)
    at Module.load (module.js:487:32)

    at ChildProcess.exithandler (child_process.js:204:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:886:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
  killed: false,
  code: 1,
  signal: null,
  cmd: './node_modules/axe-cli/axe-cli http://jaimeiniesta.com --save pGd6e6m8tzsD250jVxWcbu6t5Cqd3MuthYj2zhHPCOxfWbeHM01531136377771.json -d /tmp' }

Maybe it's the file name, not the PATH? I have /var/task/node_modules/@serverless-chrome/lambda/dist/ in the PATH, but maybe selenium-webdriver doesn't expect the executable to be named headless-chromium?

@jaimeiniesta yes; that's likely true. I think there's an option for selenium/chrome webdriver to specify a path to the chrome executable, but it doesn't seem to be exposed by axe-cli. Perhaps there's an env var that does that same, but I don't know it.

Thanks! @WilcoFiers can you throw some light here? Is there a way in axe-cli to specify the path to the chrome executable?

@jaimeiniesta if you can't get it working with axe-cli, you might be able to hack something together with axe-core directly in combination with puppeteer or chrome-remote-interface.

@jaimeiniesta Axe-cli doesn't support this. If the only alternative is to rewrite Axe-cli, best to just add it as a feature. Didn't think that'd be necessary though. Let me reach out to someone who's a bit more familiar with Lambda's than I am. --> @stephenmathieson

Disclaimer: I have not tried to run axe-cli on Lambda.
axe-cli uses chromedriver, which can be configured to run headlessly. Based on https://github.com/dequelabs/axe-cli/blob/v3.0.0/lib/webdriver.js#L14-L28, telling it to use "chrome-headless" should Just Work™. I haven't verified this, but it's probably worth a shot. If it doesn't work, feel free to reach out (stephen dot mathieson at deque dot com) and we can try to get something figured out :)

Thanks! I can assure you axe-cli runs great on AWS Lambda - I have been running it for months in production, with axe-core 2.5.0 and phantomjs.
It's only that when I try to update to axe-core 3.0, which uses chrome, I can't get it to work in AWS Lambda. But it looks just a matter of letting it find the executable in the path, it seems.
I'll try to prepare an example repo with the code to run axe-cli + phantomjs + serverless so you can see it working, and a branch with the update to axe-core 3.0 + chrome.

Cool, sounds great Jaime! Let me know 😃

Thanks @stephenmathieson, I just pushed some working code, added you and also @WilcoFiers and @adieuadieu as collaborators (the repo is private by now until the code is more polished up). Thanks a lot for your help!

I would love to see this as well - working on getting this working in a Docker container and running in to a similar issue.
Appreciate your work on this.

@nicklemmon relevant conversation is at https://github.com/jaimeiniesta/serverless-axe-cli/pull/1, which has been made public


TypeError: fetch failed

When i try to transform this error show me.

Hi, have you solved it?

Would it be possible to share a .gltf file that reproduces this problem?
Aside, I would strongly recommend NOT applying Draco before passing the model in with the --transform flag. The --transform flag must then decompress the data, and then recompress it, and this will introduce additional compression quality loss unnecessarily. The --transform flag applies Draco automatically. I think normally there would be a warning logged about that, but perhaps it's not getting that far due to the error, of which I'm not sure of the cause.

Hi, I downloaded the 3D model from Sketchfab. It contains 4 files, as shown in the screenshot below. I navigated to the folder containing these files in my terminal and executed the command: "npx gltfsx name.gltf" then got that error; The strangest thing is it worked well for the first time, and it failed when I tried the second model.

Here is the files:
earth.zip
Thanks

Hm, for me this completes quickly on the attached model.
npx gltfjsx --transform ./scene.gltf --transform

I'm using Node.js v20, I would expect this to work on Node.js v18+, is it possible you're using an older version?
I would also caution that this model relies on the old spec/gloss extension, and three.js requires metal/rough PBR. To see the correct appearance in three.js you'll need to convert it as described at https://stackoverflow.com/questions/75886578/three-gltfloader-unknown-extension-khr-materials-pbrspecularglossiness/75889212#75889212. The conversion, optionally packing to .glb, may resolve these issues as well.

I tried, but still failed. Could you explain how you did it?  What dependencies did you use?


DefaultAntBuilder always uses script directory as basedir

DefaultAntBuilder always uses script directory as basedir
See also https://issues.gradle.org/browse/GRADLE-2039
Expected Behavior
basedir value defined in ant script is used
Current Behavior
basedir is always set to script directory
Context
When importing an ant script from gradle
Steps to Reproduce (for bugs)
build.gradle
ant.importBuild 'build.ant'

build.ant
<?xml version="1.0" encoding="UTF-8"?>
<project name="docker" default="images" basedir="../..">
  <echo message="${basedir}"/>
<target name="foo"/>
</project>

gradlew foo
Excpect to see the directory two levels up from the script directory.
Your Environment
MacOSX

I'm new working with Gradle... sorry in advance
Originally I had a java project and I used ANT to compile and build .jar file. In this project we used some Ant Tasks created by our developers to create code dinamically.
These tasks use log4j to log its process and do some other operations with files...

In the .xml used to configure log4j the path to log files is specified as a relative path.
When executed logs are created inside "working directory" using the relative path.

I've created the build.gradle which reproduces the operations done in the old build.xml.
I'm not importing a build.xml but defining the tasks in my build.gradle.
From command line, located in the same directory of build.gradle we invoke gradlew build and everything works fine.
I've imported my Gradle in Eclipse and tried to invoke build task.
Problem is that the Ant Task are executed using as working directory Eclipse root; so my logs get created in an unespected path and tasks don't find configured files...
From Console output:
Working Directory: C:\java\localWork\monorepos.eclipseworkspace\git\project-java
Gradle User Home: C:\Users\mjorive\.gradle
Gradle Distribution: Gradle wrapper from target build
Gradle Version: 4.7
Java Home: C:\java\jdk1.8.0_77
JVM Arguments: None
Program Arguments: None
Build Scans Enabled: false
Offline Mode Enabled: false
Gradle Tasks: build

> Configure project :
Root project:   root project 'project-java'
  rootDir:      C:\java\localWork\monorepos.eclipseworkspace\git\project-java
  projectDir:   C:\java\localWork\monorepos.eclipseworkspace\git\project-java
  user.dir:  C:\java\eclipse-jee-oxygen-3a-win32-x86_64\eclipse

If I'm not undestanding wrong, my problem is the same as the one discussed here.
Any news or workarounds (other than execute those tasks from command line, of course ;) )

I have an idea for fixing this issue. My idea is to extend the org.gradle.api.AntBuilder with 2 new abstract methods, which will be simply overloading the existing importBuild() methods, allowing to explicitly specify the baseDirectory for the imported Ant tasks. This change will also require to add new implementations in org.gradle.api.internal.project.ant.BasicAntBuilder and org.gradle.api.internal.project.DefaultAntBuilder.
I already prepared the necessary code adjustments. They are posted below. Please let me know if you would rather like to review them in a pull request, or if I should create the pull request only after the review of changes.

AntBuilder.java
--- a/subprojects/core-api/src/main/java/org/gradle/api/AntBuilder.java
+++ b/subprojects/core-api/src/main/java/org/gradle/api/AntBuilder.java
@@ -57,7 +57,37 @@ public abstract class AntBuilder extends groovy.util.AntBuilder {
      */
     @Incubating
     public abstract void importBuild(Object antBuildFile, Transformer<? extends String, ? super String> taskNamer);
-
+
+    /**
+     * Imports an Ant build into the associated Gradle project, specifying the base directory for Gradle tasks that correspond to Ant targets.
+     *

+     * By default the base directory is the Ant build file parent directory. The relative paths are relative to {@link Project#getProjectDir()}.
+     *

+     * For each Ant target that is to be converted to a Gradle task, the given {@code taskNamer} receives the Ant target name as input
+     * and is expected to return the desired name for the corresponding Gradle task.
+     * The transformer may be called multiple times with the same input.
+     * Implementations should ensure uniqueness of the return value for a distinct input.
+     * That is, no two inputs should yield the same return value.
+     *
+     * @param antBuildFile The build file. This is resolved as per {@link Project#file(Object)}.
+     * @param baseDirectory The base directory. This is resolved as per {@link Project#file(Object)}.
+     */
+    @Incubating
+    public abstract void importBuild(Object antBuildFile, Object baseDirectory);
+
+   /**
+    * Imports an Ant build into the associated Gradle project, specifying the base directory and potentially providing alternative names
+    * for Gradle tasks that correspond to Ant targets.
+    *

+    * By default the base directory is the Ant build file parent directory. The relative paths are relative to {@link Project#getProjectDir()}.
+    *
+    * @param antBuildFile The build file. This is resolved as per {@link Project#file(Object)}.
+    * @param baseDirectory The base directory. This is resolved as per {@link Project#file(Object)}.
+    * @param taskNamer A transformer that calculates the name of the Gradle task for a corresponding Ant target.
+    */
+    @Incubating
+    public abstract void importBuild(Object antBuildFile, Object baseDirectory, Transformer<? extends String, ? super String> taskNamer);
+
     /**
      * Returns this AntBuilder. Useful when you need to pass this builder to methods from within closures.
      * @return this

BasicAntBuilder.java
--- a/subprojects/core/src/main/java/org/gradle/api/internal/project/ant/BasicAntBuilder.java
+++ b/subprojects/core/src/main/java/org/gradle/api/internal/project/ant/BasicAntBuilder.java
@@ -62,13 +62,25 @@ public class BasicAntBuilder extends org.gradle.api.AntBuilder implements Closea
         throw new UnsupportedOperationException();
     }

+    @Override
     public void importBuild(Object antBuildFile) {
         throw new UnsupportedOperationException();
     }

+    @Override
     public void importBuild(Object antBuildFile, Transformer<? extends String, ? super String> taskNamer) {
         throw new UnsupportedOperationException();
     }
+
+    @Override
+    public void importBuild(Object antBuildFile, Object baseDirectory) {
+        throw new UnsupportedOperationException();
+    }
+
+    @Override
+    public void importBuild(Object antBuildFile, Object baseDirectory, Transformer<? extends String, ? super String> taskNamer) {
+        throw new UnsupportedOperationException();
+    }

     @Override
     protected void nodeCompleted(Object parent, Object node) {

DefaultAntBuilder.java
--- a/subprojects/core/src/main/java/org/gradle/api/internal/project/DefaultAntBuilder.java
+++ b/subprojects/core/src/main/java/org/gradle/api/internal/project/DefaultAntBuilder.java
@@ -89,14 +92,28 @@ public class DefaultAntBuilder extends BasicAntBuilder implements GroovyObject {
         return castMap;
     }

+    @Override
     public void importBuild(Object antBuildFile) {
         importBuild(antBuildFile, Transformers.<String>noOpTransformer());
     }
-
+
+    @Override
+    public void importBuild(Object antBuildFile, Object baseDirectory) {
+       importBuild(antBuildFile, baseDirectory, Transformers.<String>noOpTransformer());
+    }
+
+    @Override
     public void importBuild(Object antBuildFile, Transformer<? extends String, ? super String> taskNamer) {
-        File file = gradleProject.file(antBuildFile);
-        final File baseDir = file.getParentFile();
+       importBuild(antBuildFile, null, taskNamer);
+    }

+    @Override
+    public void importBuild(Object antBuildFile, Object baseDirectory, Transformer<? extends String, ? super String> taskNamer) {
+        File file = gradleProject.file(antBuildFile);
+
+        Optional<Object> baseDirectoryOptional = Optional.ofNullable(baseDirectory);
+        File baseDir = gradleProject.file(baseDirectoryOptional.orElse(file.getParentFile().getAbsolutePath()));
+
         Set<String> existingAntTargets = new HashSet<String>(getAntProject().getTargets().keySet());
         File oldBaseDir = getAntProject().getBaseDir();
         getAntProject().setBaseDir(baseDir);

Hi @oehme, please see my solution proposal above.

Any plans to fix this?

@qrdimir I'll create PR soon, let's see if it is accepted

@kejn Was your PR ever merged and the issue just not referenced here?

text eol=lf

The above will handle all files NOT found below
https://help.github.com/articles/dealing-with-line-endings/
https://github.com/Danimoth/gitattributes
These are explicitly windows files and should use crlf
*.bat           text eol=crlf
These files are text and should be normalized (Convert crlf => lf)
*.bash          text eol=lf
*.css           text diff=css
*.htm           text diff=html
*.html          text diff=html
*.java          text diff=java
*.sh            text eol=lf
These files are binary and should be left untouched
(binary is a macro for -text -diff)
*.a             binary
*.lib           binary
*.icns          binary
*.png           binary
*.jpg           binary
*.jpeg          binary
*.gif           binary
*.ico           binary
*.mov           binary
*.mp4           binary
*.mp3           binary
*.flv           binary
*.fla           binary
*.swf           binary
*.gz            binary
*.zip           binary
*.jar           binary
*.tar           binary
*.tar.gz        binary
*.7z            binary
*.ttf           binary
*.pyc           binary
*.gpg           binary
*.bin           binary


Find the Velocity if Displacement and Time are given

Example Problem: Find the Velocity of an object if it's Displacement is 6 m and Time taken is 2 sec
Example Solution: Velocity is 3 m/sec
Further explanation : Velocity = Displacement/Time

This is good, would you like to be assigned?

I would like to work under hacktoner fest. If possible assign this to me

Hey, I saw that this issue has not been solved yet. Would love to be assigned to this if possible.


RTL Support

Describe the bug
Styling in couple of controls have problem with RTL Contents.

Placeholders in MaterialTextField and MaterialDialog don't go away when I start typing.
Confirm and Dismiss Buttons in MaterialDialog overlay each other.
Confirm Button in MaterialDialog  is always Disable!!!

Screenshots

**Smartphone:

Device: Phone6
OS: iOS
Version: XF.Material <IP_ADDRESS>

Any updates regarding RTL support?

You can use "Xamarin Forms Visual" by Xamarin Team.
Try it and see if it works for you.

https://docs.microsoft.com/en-us/xamarin/xamarin-forms/user-interface/visual/
https://github.com/davidortinau/VisualChallenge


Question about hotrod-store configuration

Hi,
i have a question about the hotrod-store configuration:
https://github.com/thomasdarimont/keycloak-project-example/blob/main/deployments/local/cluster/haproxy-external-ispn/cli/0100-onstart-setup-hotrod-caches.cli
I testet it with RH-SSO 7.5 and Redhat Datagrid 8.1/8.2 and have the following situation.
When a new session is created, it only stores the session in SSO and not in RHDG.
You can see that with the metrics endpoint.
Is it possible that you test the hotrod-store with your setup and see if the remote cache is used at all?
Best Regards!

I think that won't work at all because of: https://github.com/keycloak/keycloak/blob/01a0e11c8f56d265e3ae824221e766b2ac7e215e/model/infinispan/src/main/java/org/keycloak/models/sessions/infinispan/util/InfinispanUtil.java#L44
The implementation only works for RemoteStore.
Or do i overlook something?


Fix mypy error

Fixes MyPy error in main branch:
src/universal_transfer_operator/data_providers/filesystem/sftp.py:120: error: Returning Any from function declared to return "str"
[no-any-return]
            return urlunparse(final_url)
            ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
Found 1 error in 1 file (checked 51 source files)

Not related to this change but look like some genuine issue with CI for airflow 2.2.5

I also noticed some tests failed, @pankajastro , I wonder if it was some intermittent issue - I've triggered them to run again and it looks promising 🤞

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (8e071b8) 60.92% compared to head (688356a) 60.92%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #70   +/-   ##
=======================================
  Coverage   60.92%   60.92%
=======================================
  Files          40       40
  Lines        2380     2380
  Branches      228      228
=======================================
  Hits         1450     1450
  Misses        882      882
  Partials       48       48

Flag
Coverage Δ

UTO
60.92% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ransfer_operator/data_providers/filesystem/sftp.py
87.09% <100.00%> (ø)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


cargo add cannot enable features if version="*" in Cargo.toml

Problem
When trying to run cargo add crate -F feature with crate = "*"  or crate = { version="*" } in Cargo.toml, an error is returned.
Steps

Add time = "*" to Cargo.toml
Run the following command:

$ cargo +nightly add time -F serde
    Updating crates.io index
      Adding time * to dependencies
error: unrecognized feature for crate time: serde
no features available for crate time

Change time = "*" to time = "0.3"
Run the command again:

$ cargo +nightly add time -F serde
    Updating crates.io index
      Adding time v0.3 to dependencies
             Features as of v0.3.0:
             + alloc
             + serde
             + std
             - formatting
             - itoa
             - large-dates
             - local-offset
             - macros
             - parsing
             - quickcheck
             - quickcheck-dep
             - rand
             - serde-human-readable
             - time-macros

List of features changes when using the last concrete version (0.3.36).
Possible Solution(s)
For version="*", I would expect that it uses the feature list of the used root dependency (as in Cargo.lock)  or of the latest version available.
Notes
No response
Version
cargo 1.83.0-nightly (80d82ca22 2024-09-27)
release: 1.83.0-nightly
commit-hash: 80d82ca22abbee5fb7b51fa1abeb1ae34e99e88a
commit-date: 2024-09-27
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Fedora 41.0.0 (FortyOne) [64-bit]

When cargo add looks for available features to display and validate against, it looks to the oldest version compatible with your version requirement, assuming

You set the minimum supported version in your version requirement
The dependency doesn't remove features, making this the lowest common denominator for your version requirement.  Granted, this gets fuzzy with multi-major version requirements.

In your case, its picking time = "0.1.0" and only allowing features from that version.

The issue you're encountering with using cargo add and the version = "" syntax is related to how Cargo resolves features for dependencies. When you specify a version as "", Cargo does not fetch the features for the latest version of the crate, which is why you're seeing the error about the unrecognized feature.
-Check Latest Version: If you want to automatically use the latest version while also ensuring you have the right features, you can check the latest version of the crate and specify that version explicitly:
`

cargo search time

-Using cargo update: If you want to ensure that your dependencies are updated to the latest versions, you can run:

cargo update

-Feature List Retrieval: If you want to see what features are available for a crate without adding it, you can use:

cargo search time

`
This will show you the latest version and its features.
-Using cargo add with Specific Version: If you want to add the crate with a specific version and include features, you can do so directly:
> cargo add<EMAIL_ADDRESS>-F serde

@Kelvin-1013 please don't post LLM responses without reading and reformatting.

The behavior is written down here in code: https://github.com/rust-lang/cargo/blob/d8cb5fb7f8f66fc9b4ba3d80b089474164a8a83d/src/cargo/ops/cargo_add/mod.rs?plain=1#L1040-L1054
It seems pretty like an implementation detail relying on the assumption in the comment. I don't think this should be documented, and picking up the latest version isn't better either. I would propose we close this as the behavior is intended.

Thank you for your detailed report on the issue with cargo add and the version="*" specification. I appreciate the clarity in your steps and the examples provided.
It's clear that the current behavior is tied to how Cargo determines the lowest common denominator for features based on the earliest compatible version. Your observation about it defaulting to time = "0.1.0" and the limitations that come with that is insightful.
While I understand the rationale behind this implementation, I agree that it can lead to confusion, especially when users expect the latest features to be available with a wildcard version. However, since this behavior seems intentional and documented in the code, I support closing this issue as 'not planned.'
It might be worth considering whether we could improve the documentation around this behavior in the future to help users understand the implications of using wildcard versions better. Thanks again for bringing this to our attention!

imo if we did anything, it would likely to be lint against wildcard dependencies, see #5340

It seems odd that cargo, which has a ton of code about resolving versions of crates, doesn't reuse this for determining which version's features are in play here? Especially in this case where the actual version is already known in Cargo.lock?
A diagnostic sounds good to me -- the current behaviour is surprising.

The current version is in Cargo.lock but your dependency specification says any version in existence could be used instead.  We are trying to pick features that work for your dependency specification.  However, as I said earlier

Granted, this gets fuzzy with multi-major version requirements.


Multiple push notification problem

When there are more than one notification in status bar (different notIds), tapping on any of then will open the last received (Android only).

@natanaelmaia Sounds like a bug. Can you give me a more detailed reproduction scenario so when I have time to look at this I can go right to the problem?

@macdonst, I sent two push notifications to the app. The first one with notId=0 and the last one with notId=1. When I tapped the first notification sent (notId=0), the push.on(’notification’) function was called with notId=1. The other notification also had disappeared from status bar.
This only happend in Android.
Thanks!

Seems like this tracks back to this issue where  @sinedied mentions that creating different notIds only makes showing multiple notifications possible, not handling them all accordingly. We need to inform a different requestCode for each notification for them to be able to trigger different actions. This behaviour is described in details here:

If you truly need multiple distinct PendingIntent objects active at the same time (such as to use as two notifications that are both shown at the same time), then you will need to ensure there is something that is different about them to associate them with different PendingIntents. This may be any of the Intent attributes considered by Intent.filterEquals, or different request code integers supplied to getActivity(Context, int, Intent, int), getActivities(Context, int, Intent[], int), getBroadcast(Context, int, Intent, int), or getService(Context, int, Intent, int).

Changing https://github.com/phonegap/phonegap-plugin-push/blob/master/src/android/com/adobe/phonegap/push/GCMIntentService.java#L96 from
PendingIntent contentIntent = PendingIntent.getActivity(this, 0, notificationIntent, PendingIntent.FLAG_UPDATE_CURRENT);

to
int requestCode = new Random().nextInt();
PendingIntent contentIntent = PendingIntent.getActivity(this, requestCode, notificationIntent, PendingIntent.FLAG_UPDATE_CURRENT);

fixes it.
Please take a look into it! Looking forward to 1.1.2 with this!

You guys are the best. I may get a chance to look into this tonight.

@fredgalvao thanks, I tested and merged your change today. It'll show up in the next plugin release officially bug you can clone this repo to get the latest.

I appreciate the quick response, and I'm glad I could help!
Now onto that bigText thing on android...

I am having notifications with different notId and when I select a notification the corresponding actions are executed correctly, But other notifications with different notIds are disappearing from notification tray in android

@VaishaliRavindran Have you tried reading/changing the value of android.clearNotifications on your init options?
https://github.com/phonegap/phonegap-plugin-push/blob/master/docs/API.md#android
Also, if your issue persists, please create a new issue, as your case is not really the same as this issue.


Build failure, XLA, OS/X

Maybe OS/X only.   I have Apple clang 8.0.0 (clang-8<IP_ADDRESS>)
tensorflow/compiler/xla/service/allocation_tracker.cc:178:54: error: non-constant-expression cannot be narrowed from type 'std::vector<se::DeviceMemoryBase>::size_type' (aka 'unsigned long') to 'long long' in initializer list [-Wc++11-narrowing]
        ShapeUtil::GetSubshape(allocation->shape(), {i}),
                                                     ^
tensorflow/compiler/xla/service/allocation_tracker.cc:178:54: note: insert an explicit cast to silence this issue
        ShapeUtil::GetSubshape(allocation->shape(), {i}),
                                                     ^
                                                     static_cast<long long>( )

I see that this has been mentioned before:
https://github.com/tensorflow/tensorflow/issues/8024

related?
ERROR: /Users/davidlaxer/tensorflow/tensorflow/compiler/xla/service/BUILD:412:1: C++ compilation of rule '//tensorflow/compiler/xla/service:allocation_tracker' failed: cc_wrapper.sh failed: error executing command external/local_config_cc/cc_wrapper.sh -U_FORTIFY_SOURCE '-D_FORTIFY_SOURCE=1' -fstack-protector -Wall -Wthread-safety -Wself-assign -fcolor-diagnostics -fno-omit-frame-pointer -g0 -O2 -DNDEBUG ... (remaining 105 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
tensorflow/compiler/xla/service/allocation_tracker.cc:178:54: error: non-constant-expression cannot be narrowed from type 'std::vectorse::DeviceMemoryBase::size_type' (aka 'unsigned long') to 'long long' in initializer list [-Wc++11-narrowing]
ShapeUtil::GetSubshape(allocation->shape(), {i}),
^
tensorflow/compiler/xla/service/allocation_tracker.cc:178:54: note: insert an explicit cast to silence this issue
ShapeUtil::GetSubshape(allocation->shape(), {i}),
^
static_cast( )
1 error generated.


Deprecate clip_lower/clip_upper

As discussed in #318, this PR extends Koalas to treat deprecated pandas functions/properties as special cases of not implemented. More specifically, this PR starts by handling the clip_lower() and clip_upper() methods. In the future, other deprecated methods should be treated the same way.
Resolves #318

Codecov Report

Merging #342 into master will decrease coverage by 0.15%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master     #342      +/-   ##
==========================================
- Coverage   94.34%   94.19%   -0.16%
==========================================
  Files          35       35
  Lines        3486     3514      +28
==========================================
+ Hits         3289     3310      +21
- Misses        197      204       +7

Impacted Files
Coverage Δ

databricks/koalas/missing/frame.py
100% <100%> (ø)
:arrow_up:

databricks/koalas/missing/series.py
100% <100%> (ø)
:arrow_up:

databricks/koalas/tests/test_series.py
98.8% <83.33%> (-1.2%)
:arrow_down:

databricks/koalas/tests/test_dataframe.py
99.31% <83.33%> (-0.69%)
:arrow_down:

databricks/koalas/exceptions.py
77.77% <85.71%> (-0.35%)
:arrow_down:

databricks/koalas/missing/__init__.py
92.3% <87.5%> (-7.7%)
:arrow_down:

databricks/koalas/__init__.py
88.88% <0%> (-3.71%)
:arrow_down:

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 acdadfb...6170e75. Read the comment docs.

The PR decreases the test coverage by introducing compatibility for deprecated properties which is not yet tested as the PR focuses on the clip_lower() and clip_upper() functions only. Would it be okay to accept this for now, knowing that the coverage will increase again once the first deprecated property is added?

@floscha I thought you were testing those? Did I read this wrong?

        deprecated_functions = [name for (name, type_) in missing_functions
                                if type_.__name__ == 'deprecated_function']
        for name in deprecated_functions:
            with self.assertRaisesRegex(PandasNotImplementedError,
                                        "method.*DataFrame.*{}.*is deprecated".format(name)):
                getattr(kdf, name)()

Ah I see what you mean. It's property not method. Yes I think this is fine. But can you do one more thing ...
Update the dev/_make_missing_functions.py and dev/_make_missing_properties.py files to reflect this change. I think you can just search for .. deprecated in the docstring to identify whether a method is deprecated or not.

I've updated the dev/_make_missing_functions.py and dev/_make_missing_properties.py files with  ee2c35d and 687c74a.

Yes, there are many. I was originally creating this PR to fix #318 but I might as well add the other deprecated functions/properties as well.

+1 !

I've added all deprecated functions/properties to dedicated sections in frames.py, grouby.py and series.py.

Merging this in. @ueshin if you find anything else that can be improved please comment here still.
Thanks @floscha!

late LGTM.
Thanks @floscha!


Docs: Clicking on social buttons redirects to the main page

Clicking on social buttons redirects to the main page in the v5 documentation.
This was not the case in the v4 documentation and is not the case in the v5 documentation for other buttons in the same page.

Clicking on social buttons redirects to the main page in the v5 documentation.
This was not the case in the v4 documentation and is not the case in the v5 documentation for other buttons in the same page.

I would like to contribute but cannot seem to gain access to v5 code when cloning.  I am new to contributing but would like to help.  Can you tell me how to access v5 code?

Welcome @ckkeppler!

Can you tell me how to access v5 code?

Our default branch is still v4-dev (version 4). You can checkout the v5-dev to access to the version 5 (current version).


Invalid Error Message

If a user were to try to enroll, as in click on "Pay Now", but then not complete payment, their quote is accepted in the Stripe Api. If they were to come back to the enrollment page, there is an error, but we don't see it until they go to the main page.

To be clear, when coming back to the payment page, a client secret is not generated, and the app crashes as a result.


Fix thread lock detection bug

The effect of the bug was that a deadlock would be reported as long as the
current thread T0 that tries to acquire the ZK path P0 is in the following
situation:

Thread T0 tries to acquire ZK path P0, held by T1.
Thread T1 tries to acquire ZK path P1, held by T2.

Instead, T2 would need to equal T0.  Or,
3. Thread T2 tries to acquire ZK path P2, held by T3 = one of (T0, T1).
etc.

Thanks


Animation to auto-hide the page control

Page control alpha fades to 0 after 2 seconds. Instantly set alpha back to 1 when swiping between images.

Ok couple things overall:

There's new functionality, but no new unit tests. The two should go hand-in-hand.
Assume wild monkeys will get ahold of your code and use it in every wrong way imaginable. Try to constrain usage to the use cases you're designing it for, and make sure you test everything that the monkeys can muck with.

@justinvallely did you see all of my comments? It doesn't look like they've all been addressed. In particular we need:

To handle the background color being set after the imageCollectionView is instantiated.
To add unit tests for new public facing elements.

This should be going into develop, shouldn't it?

 I'm just bad at interpreting github now that we've been using BitBucket a lot.

👍


instanceGroupManagers can not insert a multi-zone instance group

compute.instanceGroupManagers().insert does not accept a region in its zone input parameter, nor accepts a region parameter.
I know it is a new feature in Google Cloud instance groups so it is probably in progress.
Thanks!

Ran into a similar issue with this, putting this here for the next person that comes looking:
You need to use the regionInstanceGroupManagers() resource instead of instanceGroupManagers(). More information available here: https://developers.google.com/resources/api-libraries/documentation/compute/v1/python/latest/compute_v1.regionInstanceGroupManagers.html#insert .

I'm assigning this to @crwilcox provisionally because I don't believe I can use this API without some administrative help from a Googler.

Thank you @antoniomika for your assistance. That is correct. For regionally scoped managers, you need to use regionInstanceGroupManager
@mcdonc , I think this may be something we can fix with better documentation perhaps. By design, instanceGroupManagers are not scoped to regions.
Perhaps if we added a mention of regionInstanceGroupManagers in https://developers.google.com/resources/api-libraries/documentation/compute/v1/python/latest/compute_v1.instanceGroupManagers.html#insert ?


.Net core Compatibility

Is it compatible for .Net Core 3.x and will it be supported for higher versions of .Net core e.g. 5.x or 6.x ?

Yes. Package has .NETStandard 1.6, 20, and 2.1 builds.  .Net Core 3.0 uses .NETStandard 2.1 (https://docs.microsoft.com/en-us/dotnet/standard/net-standard) and as I know it's OK to reference lower versions
Yes. I'm planning to support high versions in the future.


example/send_throughput with compare to plain udp

I took the example/throughput.js and changed it to only send from one direction, in batches, and the receiver returns small acks only to trigger the next batch send.
it can accept arguments using --udp and --size 1000 etc.
see the comparison of throughput - this is with plain UDP:
$ node example/send_throughput.js --udp
Using Arguments { _: [],
  udp: true,
  integrity: false,
  size: 8000,
  batch: 20,
  acktime: 20,
  port: 23395,
  time: 5000 }

Client connected.
Server connected.
..............................................

Sent Packets     : 92620
Received Packets : 92586
Acks             : 4632 (2 timedout)
Size             : 8000 B
Time             : 5000 ms
Throughput       : 144665.625 KB/s

and now with DTLS:
$ node example/send_throughput.js
Using Arguments { _: [],
  integrity: false,
  size: 8000,
  batch: 20,
  acktime: 20,
  udp: false,
  port: 23395,
  time: 5000 }

Server connected.
Client connected.
...

Sent Packets     : 7880
Received Packets : 7590
Acks             : 395 (19 timedout)
Size             : 8000 B
Time             : 5000 ms
Throughput       : 11859.375 KB/s

Did some testing with this:

Encrypting/Decrypting seems to be 80% of processing time for the packets. Commenting out the encrypt(), decrypt() methods in DtlsRecordLayer makes the library 5 times as fast.
A lot of the speed loss was caused by logging messages on the application data handling path (even if they weren't shown because of log level.
There were some easy optimizations to be done in DtlsPlaintext packet constructing.

Currently there is 36% overhead caused by DTLS layering (DTLS envelope, eventing, etc). ie. unencrypted packet with UDP takes 34.3 ns, while DTLS packet (without encryption) takes 46.6 ns. Encrypted packet takes 232.9 ns. So even if we were to get the unencrypted overhead down from 46.6 ns to 34.3 ns (12.3 ns), we'd still have encrypted packets taking 220.6 ns, which is 5% increase in throughput.
When running parallel processes, the throughput scaled linearly up to 4 processes gaining roughtly 30M/s per process. From there to up to 8 processes the scaling dropped to 15M/s per process above 4. From 8 upwards the throughput flattened out. Given this was executed on an octacore CPU, it would seem clear it's a CPU heavy operation, utilizing two threads. The same behavior was visible on the raw UDP sockets.

Blue: DTLS, Green: raw UDP

Based on this, I'm somewhat satisfied with my own code. The bottleneck seems to be the encrypt/decrypt methods, which are a bit out of my hands at the moment. Switching the implementation to pure javascript might gain performance as we'd save the overhead of native calls - but at the same time it might lose performance as OpenSSL itself is pretty optimized for crypto functions. The stuff that would be easy for me to optimize would gain 5% throughput increase, which I don't deem worth it at this point.

if you are using Mac then Instruments Time Profiler gives amazing info.
for example in this run with DTLS:

you can see that there are 4 libuv threads consuming total of 16% (4*4%) doing mostly uv__getaddrinfo_work ... so something about DNS is working very hard there.
for the main thread you can see that:

only 3% of the total time was spent in sendmsg/recvmsg
only 10% of the total time was spent in encrypt and sha1

for comparison with UDP ~ 30% is spent on sendmsg/recvmsg:

this is actually very accurate - since the UDP benchmark pushes 10x more packets than with DTLS and you can see that same 10x ratio in the profiler time spent in sendmsg/recvmsg...


Update control-user-access.md

Suggest removing this entry since security group nesting isn't likely to be made available soon. We can suggest mail-enabled security groups instead (if applicable to this scenario).

@Luspin
Thanks for the update suggestion. Taking this change to live via my branch.


Fix return type of NaN and Infinity values from presto API

Presto returns NaN and Infinity values as strings in the API response.
The python client doesn't do any work to coerece the values, thus their
python types differ from the type intended by presto. This commit fixes
that by detecting when these special values get returned and
transforming them into python's special values for NaN and infinity.
Fixes #55

Naive and inefficient approach here, could be sped up by caching indexes of fields which need to be checked. Also doesn't account for NaN/Infinity values in Maps/Arrays


Access token not supplied by resync-explorer

Was supposed to be fixed in https://github.com/resync/resync/issues/37. In 2.0.0 have verified that --access-token works with resync-sync but does not in resync-explorer

Released in 2.0.1


libconnman-qt5: Drop upstreamed patch for MeeGo prefix removal

MeeGo prefix was made optional by sending the adjusted patch upstream. By defining "no-module-prefix" it will now build without prefix.
Signed-off-by: Herman van Hazendonk<EMAIL_ADDRESS>

@shr-project This can be applied to other branches as well


[DOCFIX] [ALLUXIO-2009] Update "System Configuration" to "Configuration"

https://alluxio.atlassian.net/browse/ALLUXIO-2009
Update "System Configuration" to "Configuration" in docs/cn/Web-Interface.md to be consistent with the Web UI navigation bar

Can one of the admins verify this patch?

ok to test

Thanks for submitting a patch to Alluxio!
We found your commits on GitHub aren't linking to a valid Github account yet. ( See https://github.com/Alluxio/alluxio/pull/3480/commits where your icon is gray)
For us to properly credit your contributions, would you spend a minute or two to set up your Github account by (1) following the Github instructions here, (2) closing this PR, and (3) creating another PR?
Thank you again for your contribution!

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10281/
Test PASSed.

Thanks for proposing this @EMOBO . This issue has already been resolved in our current version. I think we can close this PR now. @apc999

@RongGu I have merged this PR any way :) thanks for the followup


Multiple version of scala detected when building gatling 2.1.7 with maven

I am building a project with gatling as the only dependency
Here is the snippet of the log produced by 'mvn clean install' during the compile phase
[WARNING]  Expected all dependencies to require Scala version: 2.11.7
[WARNING]  io.gatling:gatling-app:2.1.7 requires scala version: 2.11.7
[WARNING]  io.gatling:gatling-core:2.1.7 requires scala version: 2.11.7
[WARNING]  org.scala-lang:scala-reflect:2.11.7 requires scala version: 2.11.7
[WARNING]  com.typesafe.akka:akka-actor_2.11:2.3.12 requires scala version: 2.11.5
[WARNING] Multiple versions of scala libraries detected!

Stupid warnings, minor versions of Scala are now compatible. It should only complain if for example we were mixing librairies compiled against Scala 2.10 and Scala 2.11.
Just forget about them.


Update dependencies

Updating serverless and jest to their latest versions, and updating versions in examples in response to Dependabot. (Local tests work; needs an end-to-end, which I'll do this coming week.
Also, this should probably merge after the policy update in #100

Successful end-to-end test done in eu-west-3.

Successful end-to-end test done in eu-west-3.


Live streaming

Hello! Flutter is developing rapidly, which is very nice, but the needs of users (flutter clients) are growing, for example, after surfing the Internet in the repository, I still don’t understand whether it is possible to transfer video from camera to server using flutter, for example, to play a Live broadcast There is a video_player plugin via the hls protocol, but is there a reverse solution, giving the video stream to the server? There are wonderful webrtc, but I have not yet met streaming services using webrtc.
I think this topic will interest many.

The demand is much, RTMP plugin for flutter to publish and playback. WebRTC might be no go area, I have been dealt with, codec incompatibility.  VP8 vs H.264

We are also waiting for RTMP support ! 👍

i hope it will come to reality eraly..

Doesn't this package do exactly that?
https://pub.dev/packages/flutter_rtmp_publisher

@premy the package is broken and it uses some custom view instead of a normal view.

Any News on that

I have a fork here which works very well with capturing live video: https://github.com/ollydixon/flutter_rtmppublisher

Very necessary an official plugin supporting Live Streaming through RTMP and if possible the new SRT protocol. I have tested a lot of streaming plugins on pub.dev and wasted a lot of time, finally I found this one apivideo_live_stream which seems good enough for RTMPS

Closing, as this is out of scope for the Flutter team. This is something that would be best implemented by the community via plugins using third-party streaming SDKs.


Search yaml files recursively

The path of the yaml file in the Adversary Emulation Library will be changed.
Why don't you try to find the yaml file recursively?
diff --git a/app/emu_svc.py b/app/emu_svc.py
index d52d677..f2f014a 100644
--- a/app/emu_svc.py
+++ b/app/emu_svc.py
@@ -36,12 +36,12 @@ class EmuService(BaseService):
         """

         if not path_yaml:
-            path_yaml = os.path.join(self.repo_dir, '**', '**', '*.yaml')
+            path_yaml = os.path.join(self.repo_dir, '*', '**', '*.yaml')

         at_total = 0
         at_ingested = 0
         errors = 0
-        for filename in glob.iglob(path_yaml):
+        for filename in glob.iglob(path_yaml, recursive=True):
             emulation_plan = self.strip_yml(filename)[0]

             abilities = []

The path the yaml files in the Adversary Emulation Library has been changed.
https://github.com/center-for-threat-informed-defense/adversary_emulation_library/pull/63/commits/7d2b01280e66471e338ae60391889ef680055e6a

Yea the hesitation was with the inclusion of the Archive directories (https://github.com/center-for-threat-informed-defense/adversary_emulation_library/tree/master/apt29/Archive)  and whether there would be a emulation plan graveyard that wouldn't want to be imported. I've add the recursive search in (https://github.com/mitre/emu/pull/7) and recommended a test within their CI pipeline for checking that the emu plugin works (we'll also add a test on the caldera side when we include as a default plugin)


Feat/rtp transport for SIP

Pull Request
Description
I added the RTP transport for the SIP call—it is a transport for processing the raw RTP packet without Webrtc. I also added a server using the ng-control protocol, such as an RTP engine, for request calling from the SIP server.
Checklist

[x] Simple Ng Control Server
[ ] Rtp Transport

[x] Process RPC from Ng Control
[x] Generate Sdp
[ ] Transmit Rtp packet
[ ] Encode audio data
[ ] End Call

[ ] using configuration param for setting. Currently, I'm fixing all settings.

Additional Notes
Some problems I faced:

I generate the answer SDP by fixing the media session and using the public IP of the current node. But I think it is another way to generate a more generic SDP

For the transmitted RTP packet flow, I will convert the UDP data to an RTP packet and send it to the Media Endpoint. Is my way okay?

@marverlous811

I generate the answer SDP by fixing the media session and using the public IP of the current node. But I think it is another way to generate a more generic SDP

You can use local-ip-address lib to get current node IP. May be with sip we only need single default IP

For the transmitted RTP packet flow, I will convert the UDP data to an RTP packet and send it to the Media Endpoint. Is my way okay?

You need transcode it to opus, which is used to send over cluster

NodeJs sample is moved to separated repo:
https://github.com/8xFF/atm0s-media-sip-call-sample


Different alignment in scroll mode

Current way of alignment images in a row in non merged scroll mode work strange
Normal rows are left aligned, but not fully filled rows are center aligned:

Here is the result, that I'm expecting to see:

Left alignment is traditional way of showing results in grid on boorus, so please make it to one standard

I have posted all of bugs that I seen in 5.4.0a. So now I will just sit and wait for 5.4.0 release. Of course I have other suggestions, but they no need fast implementing, so nevermind. Also thank you for you hard work. I wouldn't do all that bugreports/suggestions without your feedback!

And almost forgot, please update translation files before release please/


Ability to exclude some endpoints from being traced

Hello,
I've basically scoured the internet and the source codes, but couldn't find a way to exclude some URL patterns from being traced.
We use Otel bridge and zipkin exporter to get the trace data. Our use case is that there are a lot of traces regarding actuator, for both health and prometheus endpoints.
My question is that is there a way to exclude some URLs trace data being pushed to zipkin?
Thank you.

Yeah we are using spring boot. I will open an issue there. But meanwhile, I think I found a (hacky) workaround.
Since our sole use case is for the actuator endpoints, which don't send any HTTP requests, I created my own CompositeSpanExporter and overriden the export function like that:
public class FilteredZipkinExporter extends CompositeSpanExporter {

    public FilteredZipkinExporter(ZipkinSpanExporter zipkinSpanExporter) {
        super(List.of(zipkinSpanExporter), null, null, null);
    }

    @Override
    public CompletableResultCode export(Collection<SpanData> spans) {
        Set<String> actuatorTraceIds = spans.stream()
                .filter(span -> span.getName().contains("actuator"))
                .map(SpanData::getTraceId)
                .collect(toSet());

        List<SpanData> nonActuatorSpans = spans.stream()
                .filter(span -> !actuatorTraceIds.contains(span.getTraceId()))
                .collect(toList());

        return super.export(nonActuatorSpans);
    }
}

I take ZipkinSpanExporter that spring boot creates, so that I don't need to do any publishing myself. Then find the trace IDs of spans that have the name "actuator" in them, since Micro meter publishes the span name to include the actual URL, then I filter out all the spans that have this trace ID.
But this is not enough. Since ZipkinSpanExporter is also registered as bean, I need to replace the bean with a BeanPostProcessor otherwise two span exporter beans are present so both of them are called.
@Configuration
public class ZipkinSpanExporterPostProcessor implements BeanPostProcessor {

    @Override
    public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
        if(bean instanceof ZipkinSpanExporter zipkinSpanExporter) {
            return new FilteredZipkinExporter(zipkinSpanExporter);
        }
        return bean;
    }
}

Then only my FilteredZipkinExporter is present as a SpanExporter
I know this is hacky but I tried your solution, but that gets the spans one by one, so I can filter out the spans that are actually related to actuator, but all the other spans that are related with this trace gets pushed to zipkin.

Since you are using Boot, the instrumentation there is using the Observation API.
So by creating an ObservationPredicate @Bean you can exclude what you don't want. Here is an example with Spring MVC and Spring Cloud OpenFeign for incoming and outgoing HTTP requests for actuator endpoints:
https://github.com/jonatan-ivanov/teahouse/blob/37e537b276b522f301b987dd88ad621b7a27ff9d/core/src/main/java/org/example/teahouse/core/actuator/config/CommonActuatorConfig.java#L24-L46

As far as I can tell, the details here should answer your question, let me close the issue.
Please feel free to let us know if you want it to be reopened.


Convert Slider to ES6 and resolve lint errors

@ljharb this PR brings in the pieces from https://github.com/airbnb/rheostat/pull/35/commits/191744b9457029fdc80a9ee93fade394863be33b that survives post rebase. It eliminates 6 of the eslint exceptions and tees us up for the react-with-styles commit, which I will repost as a separate PR once this is in.

Note: This would be a patch semver, but i am not sure it warrants a release on its own.

Looks like this maybe broke React 0.13 tests. https://travis-ci.org/airbnb/rheostat/jobs/168961319

Do class-based components work in React 0.12? I know SFCs don't work in 0.13, so we'd need prefer-stateless-function to remain disabled.

@ljharb @lencioni good news: tests are now passing. bad news: i played around in codepen to confirm what we already knew: ES6 classes won't work with React 0.12. The original blog post for 0.13 touches on this https://facebook.github.io/react/blog/2015/01/27/react-v0.13.0-beta-1.html, and I was able to confirm by loading up the old 0.12 code.
So, do we think compatibility with 0.12 is a worthwhile constraint? And, when we get to the next commit, with react-with-styles have any issue with the legacy React.createClass() syntax?
If we think 0.12 is required and that react-with-styles won't have any issues, I can close this PR outright and just work on the latter…

So, do we think compatibility with 0.12 is a worthwhile constraint?

I don't think it is worthwhile to continue support for React 0.12 in this project. 0.13 was released about a year and a half ago and folks who are still on that version can continue to use an older version of Rheostat.

And, when we get to the next commit, with react-with-styles have any issue with the legacy React.createClass() syntax?

I can't think of any reasons why react-with-styles won't work with React 0.12. I guess it is possible that something changed with context, but I'm not aware of anything like that.

I don't mind dropping 0.12 - it would just be semver-major. I strongly feel we should support down to N - 2 - ie, continue to support 0.13 (which means no SFCs).
In general, the true statement "users can just stay on the older version!" doesn't hold up in practice. Any time we drop support, it hurts the migration path for those users. Hopefully nobody is still on 0.12 - and the current version of Rheostat supports 0.12 - 15 - so the migration path should be clear - but it's always worth considering.

Very good. If this is the case, the current state of this PR passes. We are testing on React 13, 14, and 15. It uses ES6 classes but not SFCs. Please confirm this is a reasonable landing place?
As for tagging this semver-major, I would agreed, but I would also suggest waiting until we complete the separate PR for react-with-styles before cutting that release.

That sounds fine with me.

Polite ping. I think i got an informal thumbs up but need an official stamp.

Should this PR thus also drop 0.12 support, in travis.yml and package.json?
I'd also prefer to cut a release before this is merged.

@ljharb done and done. I made that change in a separate commit and rebased to move that commit up front so that we have a more coherent path. let me know if I can adjust further — sorry for the churn!

LGTM


Add new API endpoint: get a live page by its path

This adds a new endpoint with format /api/pages/with-path/<path>/ that returns the same response as the "get page by id one".

Coverage increased (+0.2%) to 96.796% when pulling 83ce0947d3eeff6d1ac848a0bc629682e95eb0ff on page-by-path into 0798a15821e1decf415497a2f5aa801f57f985f7 on master.


Asset compression support

I'm submitting a ...
[X] feature request

Summary
What do you think about adding support for asset-compression (images specifically)?

The total asset size for ADR can get out of hand over time.
We added a basic image compression system to our repo for ADRs using the sharp library with caching in mind. I can work on adding it to this library as well.

Yes, you can try to do it.