[Bug] Producer experienced TimeoutError with direct memory increased

Search before asking

[X] I searched in the issues and found nothing similar.

Version
Pulsar broker (and other components): v3.1.2
Pulsar client: go sdk v0.8.1 / v0.9.0
Minimal reproduce step
As the incident happened in production environment, I've tried to simulate the conditions with the ideas of:

bookie slow response
broker pending requests high

But unfortunately the increasing direct memory cannot be reproduced:

set broker config of maxPendingPublishRequestsPerConnection to 1
set client OperationTimeout and other timeout related parameters to a low value (like 100ms)
create a producer with high load and produce messages to persistent://public/default/t1
to simulate bookie slow response, either:
unload the topic
kill the bookie in charge of topic

Then the two kinds of error occurred:

send operation: 2024/03/06 08:12:33 sendMessage failed: producer.Send: message send timeout: TimeoutError
create new producer operation using the same connection: ERRO[0012] Failed to create producer at send PRODUCER request  error="request timed out" topic="persistent://public/default/t1-partition-0"

What did you expect to see?

DirectMemory should not have peak increasing
Producer should not encounter TimeoutError

What did you see instead?

DirectMemory kept increasing
Producer send Timeout and new connection failed

Anything else?
This issue is rather rare as we have used Pulsar for years and always kept the version fresh (from v2.2.x -> v3.2.0) and never have encountered such problem.
I have digged into the source code, and for me, the possible DirectMemory reason may be that the ledger.asyncAddEntry did not complete (the async executor callback), so as code comment below, the buffer was not released.

Here are also some other findings that may help identify the root cause.

Throttled connection

The code that in charge of toggling pulsar_broker_throttled_connections is org.apache.pulsar.broker.service.ServerCnx#startSendOperation and org.apache.pulsar.broker.service.ServerCnx#enableCnxAutoRead
That means during that period of time, ServerCnx's pendingSendRequest should have reached the maxPendingSendRequests which is 1000 for our configuration.
Also I can confirm that no publish rate limit set on any of the topics.

Metadata store executor queue

While the disableCnxAutoRead called, the command Producer on the connection will not be able to succeed so we can see many of below log:
2024-03-04T09:29:56,302+0000 [pulsar-io-3-1] INFO  org.apache.pulsar.broker.service.ServerCnx - [/<IP_ADDRESS>:59748] Closed producer before its creation was completed. producerId=61

Then the producer will try to reconnect, which results to tons of metadata store operations in org.apache.pulsar.broker.service.BrokerService#getOrCreateTopic.

For what it's worth, the broker / bookie / zookeeper logs show no Exception or error and their CPU/Memory/JVM (except broker DirectMemory) seems fine.

the peaks around 17:40 is the time that I've restarted the brokers on question.

As we have deployed our Pulsar clusters on AWS, my first guess was the networking issue, but after confirming with AWS Technical support and looking into the Cloudwatch metrics, both networking and disk metrics seem fine:

No packet drop or high networking usage
Disk queue is reasonable and read / write metrics too.

Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

just guessing:
Is it possible that the ServerCnx EventLoop  is blocked?
If you have the thread dump, you can check it

Good guess, I do have same doubts.
As you can see in the image of metadata store executor queue, it is quite high.
Unfortunately, it occurs on the production and the incident is quite impacting, I have to do a quick reboot without having time to do the dump.
Yet I will look into the code and maybe related metrics to see the relevance.

Could you share the dump?

@Technoboy- I'm sorry, as explained, there is no dump for now.
I've planned to automatically do thread dump when abnormal behavior occurs, and I fully understand the difficulty of solving (identifying) this issue without the thread dump.
I've posted this to see if anyone have encountered the same problem and could share an insight.

Good guess, I do have same doubts.
As you can see in the image of metadata store executor queue, it is quite high.
Unfortunately, it occurs on the production and the incident is quite impacting, I have to do a quick reboot without having time to do the dump.
Yet I will look into the code and maybe related metrics to see the relevance.


Fix bulk of Mithral Waffle Iron

https://2e.aonprd.com/Equipment.aspx?ID=275 Mithral Objects have their bulk reduced by 1 and go to Light bulk from 1 Bulk

Thank you for this crucial update.


Use of a configmap for k8s deployment

Is the goal of this to not only use a ConfigMap for non-secret configurations but also to hot-reload when ever said ConfigMap changes?

That's a good idea. For now, ConfigMap is not my top prio, but feel free to create an issue linked to this one for asking hot reloading.

@Issif 1 Question.
What is best practice to install sidekick?
As a sidecar container in Falco Pod or as a separate Chart Altogether?

@Issif 1 Question.
What is best practice to install sidekick?
As a sidecar container in Falco Pod or as a separate Chart Altogether?

That's a good question. For now, the only method for deployment is a separated helm chart. I hope to add falcosidekick as a sidecar in official falco helm chart. It will be useful for different reasons :

only one helm chart to rule them all
I'm planning to add unix pipe as input
for pipe, http, gRPC inputs, a single pod makes communications easier (for example, falcosidekick is already able to replace some custom code in that architecture https://sysdig.com/blog/active-kubernetes-security-falco-nats-kubeless/, no more need custom application for pushing events to NATS)
since falco introduced a gRPC server, we're dealing about how handling multiple falco instances, if we use pods with both falco + falcosidekick, that issue disappears (see : https://github.com/falcosecurity/falco/issues/824)

Hope this answers your interogation.

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

I close this issue, as helm chart is not anymore in this repo. I someone needs this feature, please create a new issue in : https://github.com/falcosecurity/charts


Added OpsMx Spinnaker Operator support for v1.19.9

Signed-off-by: dvropsmx<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.

Flat operator directory structure is obsolete from 23-rd of October 2019, only nested directory structure will be accepted.

New Submissions

[ N ] Does your operator have nested directory structure?
[ Y ] Have you selected the Project Community Operator Submissions in your PR on the right-hand menu bar?
[ Y ] Are you familiar with our contribution guidelines?
[ Y ] Have you packaged and deployed your Operator for Operator Framework?

[ Y ] Is your submission signed?

Updates to existing Operators

[ ] Is your new CSV pointing to the previous version with the replaces property?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

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

Operator Description must contain (in order)

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

Operator Metadata should contain

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

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

@aswath2saru can you please sign it, since you are previous contributor. Thanks

@dvropsmx is this pull request still valid? Since there is #1813 with newer version.

@mvalahtv, Yes these pull requests are still valid as we did separately for
v1.19.9 & v1.20.3.
Regards
Vijayendar Reddy D
On Fri, 29 May 2020 at 13:27, mvalahtv<EMAIL_ADDRESS>wrote:

@dvropsmx https://github.com/dvropsmx is this pull request still valid?
Since there is #1813
https://github.com/operator-framework/community-operators/pull/1813
with newer version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/operator-framework/community-operators/pull/1811#issuecomment-635823178,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL5BDD6ETUHVL7BYZFD2MF3RT5THVANCNFSM4NNMCE6A
.

@dvropsmx is this pull request still valid? Since there is #1813 with newer version.
@mvalahtv, Yes, these pull requests are still valid as we are doing for v1.19.9 & v1.20.3 separately.

@dvropsmx Ok. Which one do you want to merge first? And if this is first, then other has to have replaces current version.

@dvropsmx Ok. Which one do you want to merge first? And if this is first, then other has to have replaces current version.

Sorry, I just want to close the PRs raised for 1.19.9 & 1.20.3  as i had done these one after others without approval. Then i will create another new PR for the latest release v1.20.3 and wait for approval. Thank you.


Adding cdata while parsing

With this edit the parse of this
<node><![CDATA[test]]></node>
will return the object
{node:{dat:"test"}}
This edit will be compatible with the builder once #134 will be merged

Obsoleted by #171 & #187.


fix: remove consensus from naming

Seems we broke the UI repo, mea culpa, I wasn't aware or I would have raised that. https://github.com/fedimint/ui/pull/137


Cannot read properties of null (reading 'packages')

I encountered an error while working on my project. The error message I'm receiving is "TypeError: Cannot read properties of null (reading 'packages'). Not sure which properties are returning null." I'm seeking assistance in understanding and resolving this issue.
Background:
I'm using the madrapps/jacoco-report GitHub Action in my workflow to comment Jacoco code coverage report on PR. The workflow is triggered by a pull event. However, when the workflow runs, I'm faced with the aforementioned error message.
Error Details:
Error Message: "TypeError: Cannot read properties of null (reading 'packages')"
Code:

name: Add coverage to PR
id: jacoco
uses<EMAIL_ADDRESS>with:
paths: ${{ github.workspace }}/code-coverage/target/site/jacoco-aggregate/jacoco.xml
token: ${{ secrets.GITHUB_TOKEN }}
min-coverage-overall: 65
min-coverage-changed-files: 65

Troubleshooting Steps Taken:
I've reviewed my GitHub Actions workflow configuration to ensure that I'm providing the correct inputs and following the expected syntax for the madrapps/jacoco-report action.
I've checked the event that triggers the workflow to ensure that it contains the required information for the Jacoco Report Action to function correctly.
I've examined the workflow run logs for additional error messages or stack traces that could provide more context about the issue.
Request for Assistance:
I kindly request assistance from the community or maintainers in understanding the root cause of this error and finding a resolution. If there are any known issues related to the madrapps/jacoco-report action, or if there have been any updates that might affect its behavior, please let me know. Any insights, suggestions, or guidance would be greatly appreciated.

Could you run the action in debug mode and see what gets printed in the logs?

##[debug]Evaluating condition for step: 'Add coverage to PR'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Add coverage to PR
##[debug]Loading inputs
##[debug]Evaluating: format('{0}/code-coverage/target/site/jacoco-aggregate/jacoco.xml', github.workspace)
##[debug]Evaluating format:
##[debug]..Evaluating String:
##[debug]..=> '{0}/code-coverage/target/site/jacoco-aggregate/jacoco.xml'
##[debug]..Evaluating Index:
##[debug]....Evaluating github:
##[debug]....=> Object
##[debug]....Evaluating String:
##[debug]....=> 'workspace'
##[debug]..=> '/home/runner/work/customer-service/customer-service'
##[debug]=> '/home/runner/work/customer-service/customer-service/code-coverage/target/site/jacoco-aggregate/jacoco.xml'
##[debug]Result: '/home/runner/work/customer-service/customer-service/code-coverage/target/site/jacoco-aggregate/jacoco.xml'
##[debug]Evaluating: secrets.GITHUB_TOKEN
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'GITHUB_TOKEN'
##[debug]=> ''
##[debug]Result: ''
##[debug]Loading env
Run<EMAIL_ADDRESS>Event is pull_request
base sha: ****
head sha: ****
##[debug]followSymbolicLinks 'true'
##[debug]implicitDescendants 'true'
##[debug]matchDirectories 'true'
##[debug]omitBrokenSymbolicLinks 'true'
##[debug]Search path '/home/runner/work/customer-service/customer-service/code-coverage/target/site/jacoco-aggregate/jacoco.xml'
Error: TypeError: Cannot read properties of null (reading 'packages')
##[debug]Node Action run completed with exit code 0
##[debug]Finishing: Add coverage to PR


Expose get_autoload_list to gdscript

Expose get_autoload_list as a typed array to gdscript, since gdscript does not have an ordered array type. It's useful in GDScript too (I'd just tried to find something like this for my own project and saw it wasn't available in GDScript), so it should probably be available.

Although I'm not vehemently against this, could you provide the use case you need this for, and preferably open a Proposal to gather user interest? It is kinda possible to do this already, by opening the raw project.godot as a ConfigFile, but I can understand it's not accessible.

My specific use case for this was as follows: I have a function that loads saved data for some scene. Together with that I need to also load data into some auto-loaded nodes, of which there are several. I'd like it if I could have a list of those. I guess I can open a proposal but there is already one that includes that one function and some others, it turns out https://github.com/godotengine/godot-proposals/issues/4854


YARN-10331. Upgrade node.js to 10.21.0.

JIRA: https://issues.apache.org/jira/browse/YARN-10331
Ran mvn install -DskipTests -Pyarn-ui locally and it passed.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/1/console in case of problems.

(!) A patch to the testing environment has been detected.
Re-executing against the patched versions to perform further tests.
The console is at https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/2/console in case of problems.

I tried to upgrade node.js to 12.18.1 but mvn install -DskipTests -DskipShade -Pyarn-ui failed.
https://gist.github.com/aajisaka/0d40e66a00c50f2bea321de52e33a5e8

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 27s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m 17s
trunk passed

+1 :green_heart:
compile
4m 35s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
compile
4m 25s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
mvnsite
0m 41s
trunk passed

+1 :green_heart:
shadedclient
13m 33s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 25s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javadoc
0m 24s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 15s
the patch passed

+1 :green_heart:
compile
3m 28s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javac
3m 28s
the patch passed

+1 :green_heart:
compile
3m 58s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
3m 58s
the patch passed

+1 :green_heart:
hadolint
0m  4s
There were no new hadolint issues.

+1 :green_heart:
mvnsite
0m 31s
the patch passed

+1 :green_heart:
shellcheck
0m  0s
There were no new shellcheck issues.

+1 :green_heart:
shelldocs
0m 16s
The patch generated 0 new + 104 unchanged - 132 fixed = 104 total (was 236)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 30s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 21s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javadoc
0m 19s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Other Tests _

+1 :green_heart:
unit
3m 37s
hadoop-yarn-ui in the patch passed.

+1 :green_heart:
asflicense
0m 52s
The patch does not generate ASF License warnings.

76m 23s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2106

Optional Tests
dupname asflicense hadolint shellcheck shelldocs compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 15204f4ae7b8 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c71ce7ac337

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/1/testReport/

Max. process+thread count
430 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/1/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6 hadolint=1.11.1-0-g0e692dd

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 37s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
20m  8s
trunk passed

+1 :green_heart:
compile
4m 46s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
compile
4m 30s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
mvnsite
0m 36s
trunk passed

+1 :green_heart:
shadedclient
14m  2s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 25s
trunk passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javadoc
0m 24s
trunk passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 16s
the patch passed

+1 :green_heart:
compile
3m 43s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javac
3m 43s
the patch passed

+1 :green_heart:
compile
3m 55s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

+1 :green_heart:
javac
3m 55s
the patch passed

+1 :green_heart:
hadolint
0m  5s
There were no new hadolint issues.

+1 :green_heart:
mvnsite
0m 36s
the patch passed

+1 :green_heart:
shellcheck
0m  0s
There were no new shellcheck issues.

+1 :green_heart:
shelldocs
0m 17s
The patch generated 0 new + 104 unchanged - 132 fixed = 104 total (was 236)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  2s
The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
13m 49s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed with JDK Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04

+1 :green_heart:
javadoc
0m 19s
the patch passed with JDK Private Build-1.8.0_252-8u252-b09-1~18.04-b09

_ Other Tests _

+1 :green_heart:
unit
3m 21s
hadoop-yarn-ui in the patch passed.

+1 :green_heart:
asflicense
0m 56s
The patch does not generate ASF License warnings.

76m 17s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2106

Optional Tests
dupname asflicense hadolint shellcheck shelldocs compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux b7a53e91841c 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / c71ce7ac337

Default Java
Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.7+10-post-Ubuntu-2ubuntu218.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_252-8u252-b09-1~18.04-b09

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/2/testReport/

Max. process+thread count
415 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-ui

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-2106/2/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6 hadolint=1.11.1-0-g0e692dd

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Update README.md

fixing screenshot in readme file from broken file to screenshot on website homepage

Thank you!


seems interesting

what's this for? seems interesting OwO

Front-end original from Mercurius: https://github.com/NTUOSC/mercurius-union/tree/master/dist
I want to rewrite it with Vue.

Wouldn't vanilla JS be sufficient enough? Serving Vue on card reader might
break due to unstable outbound network connection. o____o)"

Rewriting in Vue won't change the protocol between front-end(On tablet)  and back-end (card reader).

I mean "if Vue (or any external library) is used, you'd have to make sure
that they are served locally."
Referencing Vue through CDN would possibly break if the outbound network
connection were not stable. So this is more than an advice.
Squirrel<EMAIL_ADDRESS>於 2017年5月12日 週五 19:30 寫道：

Rewriting in Vue won't change the protocol between front-end(On tablet)
and back-end (card reader).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/NTUOSC/mercurius-panel/issues/1#issuecomment-301053037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcTJ3FWoYKg6cvsfl056ptExr3yR_oDks5r5ELMgaJpZM4NFAJu
.


Bug: esc button is malfunctioning

📜 Description
It bugs out if you open a CD modal and enter esc button for app-1. You will always be redirected to workflow editor of app-1 on pressing esc until you refresh.
Affected areas
Other NON-CRITICAL functionality
Additional affected areas
Other NON-CRITICAL functionality
Prod/Non-prod environments?
Prod
Is User unblocked?
No
How was the user un-blocked?
PERMANENTLY - By giving a workaround (Within Devtron)
Impact on Enterprise
User might lose config changes if by mistakenly esc is pressed.
👟 Steps to replicate the Issue

Open CD pipeline modal in app-1
Enter Escape button
Now if you go to another application (say app-2) and enter Esc you will be redirected back to app-1.

👍 Expected behavior
esc should not switch to different page
👎 Actual Behavior
esc is switching is redirecting back to workflow editor of first application.
☸ Kubernetes version
NA
Cloud provider

NA

🌍 Browser
Chrome
✅ Proposed Solution
NA
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find any similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

AB#9813

Fixed in https://github.com/devtron-labs/dashboard/pull/1760


FinalFormSelect onChange event now returns only value from option.

Just a small change of selects. Not it will return only the actual value of selected option. This should make building forms a bit easier, because you only need values most of the time.
Single select
stateValue: { value: 55, label: 'Option label' } => stateValue: 55
Multi select
stateValue: [{ value: 1, label: 'First option' }, { value: 2, label: 'Second option' }] => stateValue: [1, 2]
Should not break any forms just yet.

@karelhala

It might be useful sometimes but i think that in 90% use case you would rather want an object of values that you can directly send to endpoint. With the current way you would have to parse the form values before sending them. And you have the full options list available anyway.

Okay, sounds good enough, merging.


Add warnings and improve errors

Description:

Add some warning logs
Raise proper error when attempting to load resources with bad requirements

Checklist:

[x] My PR is ready for code review
[x] I have added some tests, if applicable, and run the whole test suite, including linting tests
[ ] I have updated the documentation, if applicable

Codecov Report

Merging #821 into develop will increase coverage by 0.05%.
The diff coverage is 90%.

@@             Coverage Diff             @@
##           develop     #821      +/-   ##
===========================================
+ Coverage    88.53%   88.59%   +0.05%
===========================================
  Files           76       76
  Lines         4615     4621       +6
  Branches       896      900       +4
===========================================
+ Hits          4086     4094       +8
+ Misses         394      392       -2
  Partials       135      135


ci: Install libomp on macos

To resolve nightly / general build issues relating to OpenMP not being found, see https://hud.pytorch.org/pytorch/audio/commit/c6a376cc5679c1940e49fc3e0ba22eaead6c2467
-- Found Torch: /Users/distiller/miniconda3/envs/env3.10/lib/python3.10/site-packages/torch/lib/libtorch.dylib
CMake Error at /Users/distiller/miniconda3/envs/env3.10/lib/python3.10/site-packages/cmake/data/CMake.app/Contents/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:230 (message):
  Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)
Call Stack (most recent call first):
  /Users/distiller/miniconda3/envs/env3.10/lib/python3.10/site-packages/cmake/data/CMake.app/Contents/share/cmake-3.22/Modules/FindPackageHandleStandardArgs.cmake:594 (_FPHSA_FAILURE_MESSAGE)
  /Users/distiller/miniconda3/envs/env3.10/lib/python3.10/site-packages/cmake/data/CMake.app/Contents/share/cmake-3.22/Modules/FindOpenMP.cmake:544 (find_package_handle_standard_args)
  CMakeLists.txt:131 (find_package)

-- Configuring incomplete, errors occurred!

Signed-off-by: Eli Uriegas<EMAIL_ADDRESS>

LGTM! Thanks! please take a look at the failing lint.

lint appears to have already been broken and is unrelated to this PR

Yeah, lint is broken due to the recent change on fbcode side, which I am having trouble resolving on GitHub. You can ignore it.

Thanks for finding the solution. Do you know what introduced this regression?
As far as I know;

We did not change the configuration
CircleCI Support told me that they did not change macOS image recently.
CMake is the same version.


Fix circuits, ipam, tenancy, users apps FKs and related names

See spike https://github.com/nautobot/nautobot/issues/2960#issuecomment-1349809073 for details

Closed via #3090 and #3094


Added new features

Type of change
Elytra switch and ccs help command.

[ ] Bug fix
[x] New feature

Description
title
Related issues
not that im aware of anything
Checklist:

[x] My code follows the style guidelines of ItziSpyder(ImproperIssues).
[x] I have added comments to my code in more complex areas.
[x] I have tested the code in both development and production environments.
[x] I have joined  the ClickCrystals Discord.

@ItziSpyder, Sorry for the ping.
What with this PR?

@ItziSpyder? 😅


Loading please wait problem with console pic

After I login with google account, I got this scene.
The F12 console says this.

I'm sure the API are right and enabled. And the TOS of this account is done.
Just don't know why peewee error and error getting location......
Can Somebody help me, plz....

I have this problem too,pls help

I solve this!!
I figure out that my User names is not english, that is XXXX in the path C:/Users/XXXX  not english.
This situation will result in some problem.
Because modifying it to english word is troublesome and risky,  I create a new HOST users (DO NOT CONNECT TO MICROSOFT) with english word instead, and the live map program works.


File system refresh

On 2.0, it's necessary to reload the page to get a fresh list of the filesystem. Ideally, this could be updated via an event, or at least via a refresh button.

Button added as a part of 2.0


safeguard against invalid string supplied to chain.blockHash

How might we error out in cases such as the following?
chain
  .blockHash("a peanut butter chicken jelly tuna sandwich")
  .block()

This rune's signature looks like so:
BlockRune<{
    connection: Connection;
    metadata: FrameMetadata;
}, ConnectionError | ServerError | null>

Should we create a new error type? InvalidBlockHashError and unhandle it such that we get the following in the U track?
- ConnectionError | ServerError | null
+ ConnectionError | InvalidBlockHashError | ServerError | null

Would go with MalformedBlockHashError since Invalid  could imply you provide a hash that was semantically correct but didnt exist on the chain.

Malformed wouldn't imply not existing on chain either. Perhaps BlockHashDneError?

Malformed wouldn't imply not existing on chain either. Perhaps BlockHashDneError?

We are safe guarding against an invalid string (as per the title) so malformed would be correct as it doesnt imply not existing on chain

Could include both error types but if the block hash doesnt exist (although the hash is semantically well formed) the standards seems to be returning undefined just like storage

How would both errors be useful? I don't forsee different handling between invalid and DNE.

Going back to the original issue, my point was MalformedBlockHashError would be better than InvalidBlockHashError, but this is just from semantic POV.


Refactor rating component

This PR is subject to change, based on #50 .

@m0t0r Do you want me to squash everything before merging?

@mxth yes, please. Also, remove demo folder if you can, please


Allow arbitrary prefix for all system properties to resolve potential conflicts

Nah, we need to be able to change the prefix with -Drt.prefix=... passed to maven or ant on command line and this doesn't solve it.


update Pull Request

[x] insert just open and draft PRs
[ ] check for status update (and some other data {just make structure we don't decide about which data} ) in interval

[ ] register webhook for PR ( if it's possible )
[ ] cron job to update PRs without webhook
[ ] delete PR if it's not available anymore


all templates added

closes #62

@Aryainguz though the program ended but it's fine as I am always open to contributing in any which way. Have a look.

Great work @praptisharma28


Implement Event Batching Take2

Summary

Introduces an EventProcessor interface.
Introduces a BatchEventProcessor (maybe should name it BatchingEventProcessor)
Introduces an OptimizelyRule to handle lifecycle management during unit testing.

Buffering events within a queue before dispatching is an optimization that should prevent SDK implementations from exhausting resources while increasing throughput. This implementation relies on a BlockingQueue to buffer events received from one-to-many producers. A single consumer thread continuously polls from this queue to build a batch before emitting the batched LogEvent.
Note that the Optimizely class only knows about the EventProcessor and EventHandler so that it can gracefully close those implementations, so not strictly necessary. The Optimizely class builds UserEvents via the UserEventFactory and passes those events to the EventProcessor. The EventProcessor emits LogEvents to a NotificationManager<LogEvent> which is subscribed to by the EventHandler for eventual dispatching.
Trade-offs / alternatives:

We could have the EventProcessor accept an EventHandler directly, not leverging the NotificationManager
We could go all in on NotificationCenter as a global registry as opposed to one off implementations.

Pull Request Test Coverage Report for Build 1102

128 of 143 (89.51%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 89.725%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-api/src/main/java/com/optimizely/ab/event/BatchEventProcessor.java
73
88
82.95%

Totals

Change from base Build 1101:
0.006%

Covered Lines:
3519

Relevant Lines:
3922

💛  - Coveralls

Pull Request Test Coverage Report for Build 1102

128 of 143 (89.51%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 89.725%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

core-api/src/main/java/com/optimizely/ab/event/BatchEventProcessor.java
73
88
82.95%

Totals

Change from base Build 1101:
0.006%

Covered Lines:
3519

Relevant Lines:
3922

💛  - Coveralls

Big question, but does Optimizely need to know about the event handler? Can we consider the event dispatching itself part of "processing"? If so, I'd say it's the top-level event processor's job to handle the lifecycle of the events, including dispatching them. That way could avoid having to introduce a brand new concept such as the NotificationManager.

Big question, but does Optimizely need to know about the event handler

I think given the current state of the world, yes because we allow customers to implement it.

@mikeng13 It's a valid question and something I added in the PR description. I'm fine not using the NotificationManager as the conduit between components, it was kind of an experiment in leveraging these constructs more internally. I'll have to keep the EventHandler as part of the Optimizely.Builder for backwards compatibility.

Big question, but does Optimizely need to know about the event handler

I think given the current state of the world, yes because we allow customers to implement it.

I think for now, yes, because of backwards compat. But eventually I think we should decouple it from the client and make part of "event processing"

@mikeng13 It's a valid question and something I added in the PR description. I'm fine not using the NotificationManager as the conduit between components, it was kind of an experiment in leveraging these constructs more internally. I'll have to keep the EventHandler as part of the Optimizely.Builder for backwards compatibility.

Yeah makes sense. Just curious what the result/learnings of the experiment is/are and whether it still makes sense to keep these new constructs (even if just internal) as we might see them as a paradigm to work towards to.


Example error on ubuntu 16.04

The readme proposes trying:
install deps
cmake
make
make install
gst-launch-1.0 tcambin ! videoconvert ! autovideosink
which gives
WARNING: erroneous pipeline: no element "tcambin"
no file named tcambin is created by the script
BUILD_TOOLS=ON
makes no difference.

What about
sudo make install

Yeah did that too once irealized install prefix wasnt respected,
He issue is including that and with the default prefix.
On Nov 30, 2017 12:12, "TIS-Stefan"<EMAIL_ADDRESS>wrote:

What about
sudo make install
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TheImagingSource/tiscamera/issues/131#issuecomment-348158400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFMMJYV0wfMLIe2WV9gzA9pSHQzf8tdRks5s7o24gaJpZM4QvTN7
.

Can confirm that all the examples (C, C++, Python) do not work under Ubuntu 16.04 even after performing make install, it seems there is a fundamental problem with GStreamer not being able to access the camera. I have had some success in viewing images via qv4l2 but not via the example code provided.

I must admit, I am lost. I use Ubuntu 16.04. Our modules are working fine on my machine.
If there is no element "tcambin", then something went wrong. Have you been able to compile and link the modules? with the command "make" in the "build" directory?
Stefan

Ok, I think I resolved the issue, I forgot how I did it so I cannot explain here, I now have a different problem which I'll post a new issue.

ok.


Skip unnecessary secret generation

If you use .Values.config.jwtSecretSecretName and .Values.config.encryptionKeySecretName instead of specifying one in your values file, the helm chart will still generate random secrets for you.
This is usually fine because of helm resource policy (no-upgrade-existing), but the terraform helm provider detects this as the provider producing inconsistent terraform plans. So this changes the secrets to not generate when those config values are used. Otherwise the helm provider thinks it is generating new random secrets on every terraform plan and terraform apply and never works.

I'll make sure to release a new version of the Helm chart today


Website is down

Hi,
http://www.angular-meteor.com/ website is down.
Could you fix it ?

should work now.
thanks for the heads up


Cannot complete the install because of a conflicting dependency.

Hi,
Cannot complete the install because of a conflicting dependency.
The error message is:
Software being installed: Julia Development Tools <IP_ADDRESS>602080102 (com.juliacomputing.jldt.eclipse.feature.group <IP_ADDRESS>602080102)
Software currently installed: Eclipse RCP 4.6.0.v20160606-1342 (org.eclipse.rcp.feature.group 4.6.0.v20160606-1342)
Only one of the following can be installed at once:
Declarative Services 1.4.300.v20150423-1356 (org.eclipse.equinox.ds 1.4.300.v20150423-1356)
Declarative Services 1.4.400.v20160226-2036 (org.eclipse.equinox.ds 1.4.400.v20160226-2036)
Cannot satisfy dependency:
From: Julia Development Tools <IP_ADDRESS>602080102 (com.juliacomputing.jldt.eclipse.feature.group <IP_ADDRESS>602080102)
To: org.eclipse.equinox.ds [1.4.300.v20150423-1356]
Cannot satisfy dependency:
From: Eclipse 4 Rich Client Platform 1.5.0.v20160606-1342 (org.eclipse.e4.rcp.feature.group 1.5.0.v20160606-1342)
To: org.eclipse.equinox.ds [1.4.400.v20160226-2036]
Cannot satisfy dependency:
From: Eclipse RCP 4.6.0.v20160606-1342 (org.eclipse.rcp.feature.group 4.6.0.v20160606-1342)
To: org.eclipse.e4.rcp.feature.group [1.5.0.v20160606-1342]

@mdpradeep Can you help here?

I had the same issue with JuliaDT 0.0.2. I just solved it installing Eclipse Mars (4.5).

I face the same issue appearing with eclipse neon and the "parallel tools platform" suite. Even though #31 was mentioned, I think the question is: will someone make JuliaDT compatible with the latest eclipse release?

I believe @snefru fixed this in the latest release. Could you try it out:
https://github.com/JuliaComputing/JuliaDT/releases/tag/v0.0.3

Closed by d98a7bf633e1a4beadc344d77046042963f4b633. Reopen if necessary.


Session restart

@thomcc I think this part can be moved out of cli in the future https://github.com/ockam-network/ockam/pull/2641/commits/57df07b0bd89e49c017d7e6ac3d095435a9297d7
and it's written so that it should be very easy to move it. But I intentionally landed it into cli until we review and prove this approach is the way we want session management to work

it's written so that it should be very easy to move it.

Yeah, that's a big part of why I don't mind landing it :)


Updated apt::source to work with new versions of puppetlabs-apt

There are some tests that need to be updated also.

@alejandrobednarik-olx if you want to save time on this, I think I have done most of what's required in this branch: https://github.com/juniorsysadmin/puppetlabs-nodejs/tree/apt-2x-fixes . I was going to wait for the next release to the Forge (ETA a few weeks) before submitting a PR, but if you like I can submit it now for some feedback before then, or you can take bits and pieces and add it to this PR. Also see #126

we've got pretty much all tests failing, and i have no idea why.

@igalic You're good to go. You forgot to update the spec to account for the new data structure and you haven't re-integrated with master.
Here is your PR + my changes as a diff:
https://github.com/puppet-community/puppet-nodejs/compare/puppet-community:master...jmcclell:apt-2.x-spec-update
And here are the build results from Travis from that branch:
https://travis-ci.org/jmcclell/puppet-nodejs/builds/65754591
@alejandrobednarik-olx Do you plan to update your PR? It seems silly for me to submit another when you can just bring my small changes in.

@jmcclell There's also #133 which I think is ready to go. The main difference between my branch and your branch seems to be the use of ensure_packages. I think ensure_packages is a better option to avoid duplication package declarations. But if anyone has a better way, I'm all ears.

@juniorsysadmin I believe this module already requires stdlib, so I think you're right. ensure_packages is probably the better option. The only thing I see in your PR is you forgot to replace include_src in the test description. Certainly minor.
I'm running this PR currently in my environment, but don't care which one of these two actually makes it into the official repo. Just hoping one does soon!

It seems that the ordering is broken when using puppetlabs-apt 2.x, at least on Ubuntu 14.04. The repo does come before the package, as is defined by the anchor points here, but the apt_update isn't triggering before running Package[nodejs], so I'm getting the old version on first-run. I'm not sure if this module should be responsible for making sure Package[nodejs] waits for Exec[apt_update] or if there's a bug in puppetlabs-apt that should be addressed.

@jmcclell That issue is to do with the setting for $::apt::_update['frequency'] is probably best left up to the user to set in apt, since it may affect performance in subsequent runs.

#133 has been merged, so closing this PR.


Prometheus not abl to send alert request to alert manager.

Why exactly am I getting this. when visiting the api/v1/ links its working and giving the response. But why exactly do we get this error.
 prometheus_1     | level=error ts=2018-02-06T10:36:55.344497837Z caller=notifier.go:454 component=notifier alertmanager=http://X.X.X.X:9093/api/v1/alerts count=0 msg="Error sending alert" err="Post http://X.X.X.X:9093/api/v1/alerts: dial tcp X.X.X.X:9093: getsockopt: no route to host"``
Alert rule is working fine and showing the instance is down when the instance are down.
What I am expecting next is sending the alert message to alertmanager which is not

Your Prometheus instance can't connect to the AlertManager's address and it looks like an IP routing issue.


Plugin Idea - Legends

Similar to tooltips, Chart.js has a simple option for showing a legend:
   //String - A legend template
    legendTemplate : "<ul class=\"<%=name.toLowerCase()%>-legend\"><% for (var i=0; i<datasets.length; i++){%>
<span style=\"background-color:<%=datasets[i].strokeColor%>\"><%if(datasets[i].label){%><%=datasets[i].label%><%}%>
<%}%>
"

Showing in up as seen in the picture in https://github.com/gionkunz/chartist-js/issues/219
Again that is something I would like to implement as soon as I find some time. Any thoughts about it are appreciated.

Generally I do not support library usage for generating labels as this is such a simply and standard task. However, if it's going to be something with more behaviour, like series highlighting on legend hover, this could definitely go into a plugin then.

@Globegitter I'm closing this issue for now. If you have further ideas please comment on #290


Services using mtls are not able to reference a root CA

If the property services.ca_certificates is specified, an error is returned Tag Validation Errors: string indices must be integers, not 'str'.
It should allow the ca_certificates to be set without error.

@ikethecoder wrote (in Jira):

The other consideration too is that the gwa v2 CLI apply should handle GatewayCertificate as well as GatewayService.  So that the certificate can be registered as part of the same sync process.

We also identified the need for GatewayUpstream
and we will also require updates in gwa-cli to properly handle upstreams


TLS/SSL version and cipher grids. It's very much a client compatibility issue, just not for fron...

TLS/SSL version and cipher grids. It's very much a client compatibility issue, just not for front-end engineers. The existing format is perfect. Happy to help collect data.

This issue was imported from Google Moderator
Moderator votes: +10
Issue added by James Socol on 2014-10-15
To vote this issue up or down, simply include +1 or -1 in your comment.

Duplicate of #1144.


Provide remote log read capability

there was a way presented around 2 months ago in the matrix chat iirc ( end of october), where you could siphon the log output and still dont loose the local log.
    use core::ffi::{c_char, c_int};
    use esp_idf_sys::{size_t, va_list};
    use log::info;

    extern "C" {
        #[allow(improper_ctypes)]
        pub fn vsnprintf(_: *mut c_char, _: size_t, _: *const c_char, _: va_list) -> c_int;
    }

    #[allow(improper_ctypes_definitions)]
    unsafe extern "C" fn vprintf_trampoline(arg1: *const c_char, arg2: va_list) -> c_int {
        const MAX_LEN: usize = 128;
        let mut buf = [0u8; MAX_LEN];
        let len = vsnprintf(buf.as_mut_ptr() as _, MAX_LEN as _, arg1, arg2);
        if len < 0 {
            info!("vsnprintf returned an error: {len}");
            return len;
        }
        let s = &buf[0..(len as usize).min(MAX_LEN)]; // the min is just in case
        match core::str::from_utf8(s) {
            Ok(s) => info!("esp log received: {s}"),
            Err(err) => info!("esp log received a non-utf8 string: {err}, {s:?}"),
        }
        len
    }
    unsafe { esp_idf_sys::esp_log_set_vprintf(Some(vprintf_trampoline)) };
    esp_idf_svc::log::EspLogger::initialize_default();

hope this helps


Create ousl.txt

http://www.ou.ac.lk/home/index.php/ousl/2013-12-19-10-44-25/it-supportive
http://www.ou.ac.lk/home/images/Divisions/IT/downloads/OUSL%20EMAIL%20ADDRESSES%20FOR%20STUDENTS.pdf

OUSL Open university Sri lanka

@damiththiwanka Pull request merged. Thank you!


Define seed, randomizeTests and randomTests on Env

That.
The corresponding PR has been merged
Specifically here are the new exposed functions.

@borisyankov @theodorejb @davidparsson - please can one of you listed authors give this a check?
Thanks

Thanks for the contribution. This PR contains merge conflicts and can not be merged at the moment. Please refresh this PR and address the merge conflicts.

Hello and thank you for your contribution!
Due to an excessively long queue of pull requests that have become stale, we are "declaring bankruptcy" and closing all PRs opened before May 1, 2016. If you'd still like to merge this code in, please open a new PR that has been merged and rebased with the master branch.
Going forward, we are committing to review or merge all PRs on a regular basis so this bankruptcy will not occur again. We apologize for the incovenience and hope you will continue to contribute to DefinitelyTyped in the future.
Thanks
The TypeScript and DefinitelyTyped teams


Update index.md

downloading is not from a broker...
Am I pedantic?

+1/agree.  I've applied this fix manually given the merge conflicts.  Content updated.


[k8sprocessor] Owner metadata should have a grace period after deletion

We keep Pod metadata around after the Pod itself is deleted, to account for telemetry data that might be processed after the deletion takes place. However, we do not do this for owner metadata, whereas we should for the same reason. As is, if a Deployment is deleted and we process data from a Pod belonging to that Deployment afterwards, we won't add the deployment attribute.
I believe this was introduced in #710, where we started calculating owner metadata dynamically instead of keeping it alongside Pod metadata.

@swiatekm-sumo  if you don't mind I'd give this a shot.
Reading through, the most apparent solution would be to reapply that same deferred deletion queue pattern from the pod identity cache to the Owner cache. Probably with some twist to account for the multiple cached collections on that structure. Does that all track?

Yeah, I think the same solution will work modulo different types.


unable to extract audio

Hi, I am unable to extract audio from videos (e.g mp3)  In fact it seems that tartube is unable to download any format other than video in mp4 or webm. .
e.g tried this link https://www.youtube.com/watch?v=rLtZKkCIVmI  I don't want the video, I just want the audio. I use the classic interface and choose format mp3 from the box.
Here is the output.
/home/bee/.local/bin/youtube-dl --newline -i --hls-prefer-native -o /home/bee/Music/%(title)s.%(ext)s -f mp3 --ffmpeg-location /usr/bin/ffmpeg https://www.youtube.com/watch?v=rLtZKkCIVmI
[youtube] rLtZKkCIVmI: Downloading webpage
ERROR: requested format not available

However, using youtube-dl with the comand line downloads video, extracts audio and converst to desired format with no problem.
This works flawlessly
$youtube-dl -x --audio-format mp3 https://www.youtube.com/watch?v=rLtZKkCIVmI
[youtube] rLtZKkCIVmI: Downloading webpage
[download] Destination: Tom Waits - 'Downtown Train'-rLtZKkCIVmI.m4a
[download] 100% of 4.66MiB in 00:02
[ffmpeg] Correcting container in "Tom Waits - 'Downtown Train'-rLtZKkCIVmI.m4a"
[ffmpeg] Destination: Tom Waits - 'Downtown Train'-rLtZKkCIVmI.mp3
Deleting original file Tom Waits - 'Downtown Train'-rLtZKkCIVmI.m4a (pass -k to keep)

Tartube v2.1.051 installed with pip3
youtube-dl version 2<IP_ADDRESS>
OS Ubuntu 20.04

Oops sorry, wrong site.


tableActions call also onRowClick

Hi there,
I have a table declared as follows:
{{#light-table table tableActions=(hash delete=(action 'deleteModel')) as |t|}}
 Some code here...
{{#t.body onRowClick=onEdit tableClassNames="list bordered striped" as |body|}}
 Some code here...
  {{/t.body}}
{{/light-table}}

Every row has a button to delete the row. This button is declared as a cellType.
The problem is when I click that button both actions are called edit and delete.

Can you share the cellType code?

Sure, here is the relevant part of the code:
  actions: {
    cellAction() {
      const action = this.get('action');

      if (action && this.get(`tableActions.${action}`)) {
        this.get(`tableActions.${action}`)(this.get('row'));
      }
    },
  },

<a  {{action 'cellAction'}}>
  <i class="material-icons">{{materialIcon}}</i> {{value}}
</a>

I don't see anything wrong with that code, sorry. Would probably need an ember-twiddle with a reproduction case, does const action = this.get('action') return edit (or what you expect?)

In this case this.get('action') return deleteModel what is expected so everything it's ok.
I will try to reproduce the error in an ember-twiddle.

I'm sort of in the same boat? (I think)
Basically if I have:
{{#t.body onRowClick=<anything here>

Then I can't put anything clickable in a cel without the onRowClick also firing.

That's because of the event bubbling. I'm only on my mobile right now, but
you can read up on it in the Ember guides. 😉
On Wed, Nov 30, 2016, 22:18 Roger Studner<EMAIL_ADDRESS>wrote:

I'm sort of in the same boat? (I think)
Basically if I have:
{{#t.body onRowClick=
Then I can't put anything clickable in a cel without the onRowClick also
firing.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/offirgolan/ember-light-table/issues/269#issuecomment-263998470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAy8TP0eyo4LYG8Da1Mfsm9e7oYXCUuVks5rDeg8gaJpZM4K4Azp
.

@rstudner Yes exactly! We are in the same boat :)
I don't catch your solution, which click method are you overriding in the cel component? The specific component action?

Yeah. Basically just;
my-cell-component/component.js has:
click() { return false; }

On Dec 1, 2016 6:13 AM, "Luis"<EMAIL_ADDRESS>wrote:

@rstudner https://github.com/rstudner Yes exactly! We are in the same
boat :)
I don't catch your solution, which click method are you overriding in the
cel component? The specific component action?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/offirgolan/ember-light-table/issues/269#issuecomment-264145086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAM0MlHMh9qYVSn28cTysob90_noa4V1ks5rDqvPgaJpZM4K4Azp
.

Closing as the above solution will work. Just overwrite your custom cell component's click method and prevent bubbling by either using the given event object or returning false.
If you want to prevent the {{action}} from bubbling, a better solution can be found in the event propagation docs.

Thank you guys, @rstudner solution worked perfectly :smile:


Create a subclass of NSBitmapImageRep to fix the GIF frame duration issue on macOS

New Pull Request Checklist

[x] I have read and understood the CONTRIBUTING guide

[x] I have read the Documentation

[x] I have searched for a similar pull request in the project and found none

[x] I have updated this branch with the latest master to avoid conflicts (via merge from master or rebase)

[x] I have added the required tests to prove the fix/feature I am adding

[x] I have updated the documentation (if necessary)

[x] I have run the tests and they pass

[x] I have run the lint and it passes (pod lib lint)

This merge request fixes / reffers to the following issues: ...
Pull Request Description
Well, for macOS, GIF rendering seems contains issue when the frame duration is lower than 50ms because AppKit build-in NSImage and NSBitmapImageRep use the kCGImagePropertyGIFDelayTime when you switch frame, so the duration is always clamped.
However, many GIF relay on the correct frame duration, and there is no options to change this to allow the correct rendering. It's really frustrating and you have to do many extra struff such as write you own view with Core Animation. You can see our demo's first GIF rendering, which is really slow and the duration is wrong.
Previouslly I think there is no way to fix it, however, after some research that I found we can subclass NSBitmapImageRep to override the behavior and provide a correct and consistent behavior with UIKit.
NSBitmapImageRep don't do something really magic. It will grab loop count from Image/IO when you call setProperty: withValue: with NSImageCurrentFrame to change frame. So we just fix this using the correct calculate from our GIF coder.
To see, since this behavior is not like the default behavior with NSImage, we just enable this on SDWebImageGIFCoder(Not default). Our SDWebImageImageIOCoder on macOS also support GIF rendering because it's the default behavior with NSImage.

To see the correct result for GIF rendering, checkout this branch and run macOS demo and see the rendering for the first doggy GIF. Here is the video showing the demo
macOS-GIF-rendering.mov.zip

Codecov Report

Merging #2223 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2223   +/-   ##
=======================================
  Coverage   78.27%   78.27%
=======================================
  Files          36       36
  Lines        3664     3664
  Branches      338      339    +1
=======================================
  Hits         2868     2868
  Misses        773      773
  Partials       23       23

Impacted Files
Coverage Δ

SDWebImage/SDWebImageGIFCoder.m
79.8% <ø> (ø)
:arrow_up:

SDWebImage/SDWebImageCoderHelper.m
61.42% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a54d1d7...7d4b902. Read the comment docs.


engine/api: fix cURL examples for different cURL versions

relates to https://github.com/moby/moby/issues/41598
relates to https://github.com/moby/moby/issues/17960
relates to https://github.com/moby/moby/pull/27640
relates to https://github.com/curl/curl/issues/936

@StefanScherer @usha-mandya ptal


DASH player isn't working for html5 as well as player resolution.

Currently Im using YTC dev build with the latest update. With Dash on, the video is suppose to load in chunks until completion. But currently DASh isn't working for html5.
On the other hand when I switch to flash/aggressive flash,  DASH works fine but the resolution doesn't follow what I set. I set my resolution to 480p because I have a slow internet and often it will auto change my resolution from 360p to 144p.
Any idea why this is happening for me? DOes it have to do with youtube's constant updates breaking the extension?

How is DASH not working for HTML5? Is it not loading up the video?


adding tests for graphene and pydantic latest versions

Codecov Report

Merging #43 (2d2a607) into master (794d141) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #43   +/-   ##
=======================================
  Coverage   94.09%   94.09%
=======================================
  Files           7        7
  Lines         237      237
=======================================
  Hits          223      223
  Misses         14       14

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 794d141...2d2a607. Read the comment docs.


Improve explanation of the coefficients for trend(, method(ols)) vs. trend(, method(gmm))

The explanation on the help file about the different methods to extrapolate the trend is a bit incomplete. It does not explain that the coefficients on the negative event-times will differ between the two methods and have a different interpretation. We should explain this better in the section on trend in the help file.

This discussion will be helpful to improve the explanation:
In the regression approach, when we include the trend we omit the event-time coefficients used to estimate it from the regression. So if event-time -2 is used to fit the trend, at event-time -2, y = fixed effects + controls + trend + error.
Instead, in the GMM aproach, we adjust the coefficients to be trend plus adjusted coefficient, so at event-time -2, y = fixed effects + controls + trend + adjusted coefficient + error. That is, this approach does not force the adjusted coefficient to be 0. In the regression approach, the adjusted coefficient is loaded in the error. Both approaches return the same slope for the trend though.

This issue will be subsumed by #210 . Closing now.


docs(v2): Add wiki-powerto site showcase

Motivation
(Write your motivation here.)
Have you read the Contributing Guidelines on pull requests?
(Write your answer here.)
Test Plan
(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work. Bonus points for screenshots and videos!)
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

Hi,
LGTM, but can you please respect the alphabetical order?

Hi,
LGTM, but can you please respect the alphabetical order?

thanks :)

thanks :)


Update native code to edition 2018

Overview
Edition 2018 brings improved imports system. Also removed some unused dependencies and updated Cargo.lock to a new diff-friendly format (new feature of Rust 1.41)

See: https://jira.bf.local/browse/ECR-XYZ
Definition of Done

[ ] There are no TODOs left in the code
[ ] Change is covered by automated tests
[ ] The coding guidelines are followed
[ ] Public API has Javadoc
[ ] Method preconditions are checked and documented in the Javadoc of the method
[ ] Changelog is updated if needed (in case of notable or breaking changes)
[ ] The continuous integration build passes

Coverage remained the same at 85.114% when pulling e51d270a5c907fcabf81ee9a2b32a30bffe50090 on vitvakatu:edition-2018 into 7b6d2603cc5e1973a2fa74be62517daf6f3387e6 on exonum:master.


schemas: bump version

ref: https://github.com/cern-sis/issues-inspire/issues/465

Supersede by #3181


quisk: init at 4.1.72

Motivation for this change
Quisk is a SDR transceiver for radios that use the Hermes protocol.
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

needs a rebase

can you squash the last 2 commits?

@Lassulus Sure, thanks for reviewing. Is it ok like this?

looking good, but you also need to call this from all-packages.nix


Refactored progress bar

As well as cleaning up any SCSS / JS for the progress component I've also come up with a way for how we can abstract our style inconsistencies away from gather-content-ui.
Style as Config
I forgot that I have done this before (in previous roles) but abstracting CSS prop values into a default config per component is a really useful way to allow us to keep the UI library styles consistent and easy to digest.
For example;
// Notification/styles.scss - in gather-content-ui

$notification-padding: 15px 10px !default;

.notification {
    padding: $notification-padding;
}

// settings/overrides/notification.scss - in app using package

$notification-padding: 13px 8px; // this padding will be used when

Most of the Work
At the moment we're digesting the CSS from gather-content-ui as a complied CSS file. This strategy would require us to expose all SCSS files (like how we're exposing settings).
I kind of feel like we should do this anyways. Our only way to digest the CSS atm is to require it. Not the worst thing in the world but it'd be nice to have the ability to import our main SCSS file in the same way we expect settings to be imported.
Proposal
We don't expose the SCSS right away but use this style as config approach to set things up to be more flexible moving forward.
What do you think?

Like where this is going 👍


Farms Sorting by Ips

Is your feature request related to a problem? Please describe
Please add sort_by=total, used & free ips for farms
Describe the solution you'd like
ability to sort total, used and free ips by ascending and descending order in farms module

Verifications

You can now sort by free_ips, total_ips and used_ips

You can execute https://gridproxy.dev.grid.tf/farms?sort_by=free_ips
You can execute https://gridproxy.dev.grid.tf/farms?sort_by=used_ips
You can execute https://gridproxy.dev.grid.tf/farms?sort_by=total_ips

Note

Can't find free_farm


Please tag releases in source, and avoid including zip with source

It seems "releases" of this project are made by replacing eye.zip in source.
Please tag releases as git tags, to ease tracking releases.
Also, please consider not adding zip to source: Github offers automatically zip and tarballs of both tagged releases and each git commit, and adding zip to source causes the source to unnecessarily consume lots of space.

If you want to drastically save space (i.e. download time for initial cloning), then before tagging you might want to rewrite history to remove eye.zip from all commits (see first entry of the EXAMPLES section in git help filter-branch).
Normally it is bad to rewrite history, but arguably storing binary blobs in a source git is worse.  Just a suggestion.
While at it, you might want to strip reasoning/image/ype.pvm as well: I believe that contains code you did not write (I'll file a separate issue about the legal implications of that).

There is now https://github.com/josd/eye/releases/tag/v18.1111.2230
The minimal eye.zip is still needed in other projects such as e.g. https://github.com/bdevloed/eye/blob/master/Dockerfile


Allow BPMN message name to be hard coded in Sink connector

In some situation records on one Kafka topic should always sent into Zeebe with the same message name. Currently you have to extract the message name itself from the data of the record.
Current config
    "message.path.messageName": "$.variablesAsMap.messageName",
    "message.path.correlationKey": "$.variablesAsMap.key",
    "message.path.variables": "$.variablesAsMap"

I want to do this
    "message.path.messageName": "messageName",
    "message.path.correlationKey": "$.variablesAsMap.key",
    "message.path.variables": "$.variablesAsMap"

Or maybe we need to rename the attribute into e.g.
    "message.path.messageNameExpression": "$.variablesAsMap.messageName",
    "message.path.messageName": "messageName",

Which I think is inline to what we do at other places in Zeebe.
And I actually wondered why the attribute is called "message.path" - what's the "path" in it? @npepinpe - probably you know?

For JSONPath, but admittedly it probably wasn't necessary to add it there. I think we should focus on migrating to SMT support instead of using JSONPath.

I tend to agree (even if this is a quite big refactoring and still will require some thinking around the message name makes total sense to be hardcoded

I would propose that we allow all values to be hardcoded as well, for example for fan out behaviour you might want the correlation key to be hardcoded to an empty string.


Add

This function lets you poll tweets from a specific user.

@ChimeraCoder: This can be closed, it's since been implemented in timeline.go.


Issue with firebase-auth sample

I'm using firebase-auth example and found one error in firebase console log.
Error Description
Error: getaddrinfo ENOTFOUND www.linkedin.com www.linkedin.com:443
at errnoException (dns.js:28:10)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
Steps to reproduce the issue
Login with Linked in from this sample app: https://linkedin-auth-example.firebaseapp.com
After successful authentication, you will get Please wait message and firebase is responding with code ans state but will not go beyond further and provide token
Here is the snap for firebase console log.
https://www.dropbox.com/s/w5v14xuehpjyb6z/Screenshot 2017-07-12 12.04.55.png?dl=0

Hey @tejasrsuthar,
It seems that the issue is that you did not enable billing on your project.
This sample needs you to have billing enabled because projects without billing are only allowed to do requests to Google Services and so since the app needs to do requests to LinkedIn you'll have to enable billing.

Oh ok. I'll enable billing and check again.
Thanks for your update. :+1:

@tejasrsuthar It worked?

@minhdongsss sorry, I didn't get time to check this.

@tejasrsuthar hihi


Add VirtScreen

Virtscreen is a open source application that Make your iPad/tablet/computer as a secondary monitor on Linux.
They have a deb available from their website.
https://github.com/kbumsik/VirtScreen/releases/download/0.3.1/virtscreen.deb

Sorry, we are only accepting software that is actively maintained/released. Please see:

Add guidelines for what packages are acceptable for inclusion


Can't use in Main Process for emit data

Cant emit data from the main process. Throwing below error,
TypeError: Cannot read property 'apply' of undefined
const ipc = require('electron-promise-ipc')

ipc
  .send('getRendererData', {})
  .then((rendererData) => console.log(rendererData))
  .catch((e) => console.error(e));

Can listen from the main process, send from the renderer process.

I notice you’re using require() and not import so I’m guessing that’s the
error. What version are you on? In 2.0.0, we switched to commonJS exports.
I bet that this would be solved by using:
const ipc = require('electron-promise-ipc').default;
On Wed, Nov 6, 2019 at 1:33 AM Pranav Anilkumar Wani <
<EMAIL_ADDRESS>wrote:

TypeError: Cannot read property 'apply' of undefined
const ipc = require('electron-promise-ipc')
ipc
.send('getRendererData', {})
.then((rendererData) => console.log(rendererData))
.catch((e) => console.error(e));
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sibnerian/electron-promise-ipc/issues/19?email_source=notifications&email_token=AAW3BRFOJNDBRG5WUTF2QJLQSJQJZA5CNFSM4JJQKKXKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HXEE6EQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3BRCYRSOM2MDBAYGQL5TQSJQJZANCNFSM4JJQKKXA
.

Sorry for raising an issue without reading the doc properly. Actually I have a query for sending data from the main process to the renderer process. In doc mention that using WebContent, you can send info. from the main process to the renderer will you please guide for it.

Let’s refer to the documentation.
You can also send data from the main process to a renderer, if you pass in
its WebContents http://electron.atom.io/docs/api/web-contents object.
// in main processimport promiseIpc from 'electron-promise-ipc';
promiseIpc
.send('getRendererData', webContentsForRenderer)
.then((rendererData) => console.log(rendererData))
.catch((e) => console.error(e));
// in rendererimport promiseIpc from 'electron-promise-ipc';
promiseIpc.on('getRendererData', (event) => {
return getSomeSuperAwesomeRendererData();
});
How to obtain the webContents is up to you!  It depends on your app and use
case. The electron documentation is good to read.
One suggestion would be to send a message from the renderer as soon as it
loads, and save the value of event.sender.
On Wed, Nov 6, 2019 at 2:21 AM Pranav Anilkumar Wani <
<EMAIL_ADDRESS>wrote:

Sorry for raising an issue without reading the doc properly. Actually I
have a query for sending data from the main process to the renderer
process. In doc mention that using WebContent, you can send info. from the
main process to the renderer will you please guide for it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/sibnerian/electron-promise-ipc/issues/19?email_source=notifications&email_token=AAW3BRCDBLU2XVOJBATA3OTQSJWAZA5CNFSM4JJQKKXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDFRNRY#issuecomment-550180551,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAW3BRHZ4WZ5TKUVLIYDUELQSJWAZANCNFSM4JJQKKXA
.