text:
Lack of cross-validation testing between C++, Java

Issue #149 would have been easily discovered if we had cross-validation testing between Java and C++.   This is a critical bug against the release process.   To clear this bug I am suggesting that we can demonstrate:

An automated or semi-automated cron job that can be easily extended.  This job would run tests in java and C++, that produce binary results that can be directly compared without having to resort to static stored binaries.

This job should be run at least nightly, and run against any Release Candidate.

The qualifications required to clear this bug are certainly open for discussion.

We either need to perform such tests out of characterization or create a dedicated repo to handle that. Please either create the issue against a more appropriate repository or as a JIRA ticket. IT is also an enhancement rather than a bug.

authors: jmalkin leerho

repo: apache/incubator-datasketches-cpp


text:
[Feature][Plugin] add a new data sync mode to allow setup a "start_from" or "since" time for data scope to reduce volume of data-syncing

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
when setup a data scope for collecting data, I want to a "sync start from" or "sync since" field, so I don't spend time to collect legacy data which I don't care.
Use case
I have a 5-year project which uses Jira to manage requirements and incidents from very beginning. So my project has more than 30k issues, and my scrum board has more than 100 sprints. I don't care issues completed or created more than 2 years ago. To sync all 30k issues is time consuming and unnecessary.
However, existing jira plugin just provide two sync mode:
full sync mode, which support incremental syncing after first data sync;
date range sync mode, which support syncing data from an exact date, but this mode doesn't support incremental syncing in subsequent syncing process.
Both mode can't support my idea sufficiently.
I want to only collect my recent 1-2 years issues in the beginning and keep incremental syncing subsequently.
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This ought to be cherry-picked to v0.14.

I'll look at this these days.

This issue will be implemented in #3492 (for Jira) and #3688 (for GitHub)

source: gharchive/issue

authors: Startrekzky klesh leglars likyh

repo: apache/incubator-devlake

license_type: permissive

license_source: github-api


text:
运行一段时间后,worker服务无端停止运行,造成任务累积到待执行命令那里，但重启worker就好了。

ds调度正常运行一段时间后，启动工作流之后，任务不执行（简单shell  jps都不行），实例也没有，但是在统计管理待执行命令数那里会显示积压几个任务，而且重启一下worker服务之后，之前没有启动成功的工作流就全部正常显示运行，待执行命令数也归零了。相关属性：
3台机器的启动参数一致如下：
export DOLPHINSCHEDULER_OPTS="-server -Xmx5g -Xms5g -Xss512k -XX:+DisableExplicitGC -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:LargePageSizeInBytes=128m -XX:+UseFastAccessorMethods -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=70"

is three worker server all stop work?
By the way, English is needed, you can update/add title/desc in English, thx

yes，All three worker servers are down！
------------------ 原始邮件 ------------------
发件人: "dailidong"<notifications@github.com>;
发送时间: 2020年4月7日(星期二) 下午3:18
收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>;
抄送: "秦健"<352202522@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [apache/incubator-dolphinscheduler] 运行一段时间后,worker服务无端停止运行,造成任务累积到待执行命令那里，但重启worker就好了。 (#2372)
is three worker server all stop work?
By the way, English is needed, you can update/add title/desc in English, thx
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

is zk working fine?

ZK should be OK, because I just restart the work server to run normally. and CDH Server is OK。
------------------ 原始邮件 ------------------
发件人: "Rubik-W"<notifications@github.com>;
发送时间: 2020年4月7日(星期二) 下午3:38
收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>;
抄送: "秦健"<352202522@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [apache/incubator-dolphinscheduler] 运行一段时间后,worker服务无端停止运行,造成任务累积到待执行命令那里，但重启worker就好了。 (#2372)
is zk working fine?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

You can see worker log file. Is there an error log.

At that time, I went to read the work log. The log of work just said that the task has been established
------------------ 原始邮件 ------------------
发件人: "Rubik-W"<notifications@github.com>;
发送时间: 2020年4月7日(星期二) 下午3:58
收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>;
抄送: "秦健"<352202522@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [apache/incubator-dolphinscheduler] 运行一段时间后,worker服务无端停止运行,造成任务累积到待执行命令那里，但重启worker就好了。 (#2372)
You can see worker log file. Is there an error log.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

At that time, I went to see worker log file, and no corresponding log was generated in work
------------------ 原始邮件 ------------------
发件人: "Rubik-W"<notifications@github.com>;
发送时间: 2020年4月7日(星期二) 下午3:58
收件人: "apache/incubator-dolphinscheduler"<incubator-dolphinscheduler@noreply.github.com>;
抄送: "秦健"<352202522@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [apache/incubator-dolphinscheduler] 运行一段时间后,worker服务无端停止运行,造成任务累积到待执行命令那里，但重启worker就好了。 (#2372)
You can see worker log file. Is there an error log.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Close the issue since no updates for long time

authors: Rubik-W chengshiwen dailidong knight11111

repo: apache/incubator-dolphinscheduler


text:
Solve the failure to execute non-query sql

What is the purpose of the pull request
Solve the failure to execute non-query sql
Brief change log

move resultSet = stmt.executeQuery() into SqlType.QUERY branch

Verify this pull request

Codecov Report

Merging #2413 into dev will decrease coverage by 0.02%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev    #2413      +/-   ##
============================================
- Coverage     32.89%   32.87%   -0.03%
+ Complexity     2275     2274       -1
============================================
  Files           423      423
  Lines         19839    19839
  Branches       2366     2366
============================================
- Hits           6527     6523       -4
- Misses        12726    12729       +3
- Partials        586      587       +1

Impacted Files
Coverage Δ
Complexity Δ

...lphinscheduler/server/worker/task/sql/SqlTask.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...he/dolphinscheduler/common/thread/ThreadUtils.java
71.66% <0.00%> (-6.67%)
13.00% <0.00%> (-1.00%)

Continue to review full report at Codecov.

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

You should fetch the new code and keep consisdent of current version.Then I merget this.

source: gharchive/pull-request

authors: codecov-io lgcareer zixi0825


text:
svg 渲染模式下 graph Label文字大小异常

One-line summary [问题简述]

Version & Environment [版本及环境]

ECharts version [ECharts 版本]:4.1.0
Browser version [浏览器类型和版本]:chrome
OS Version [操作系统类型和版本]:mac

Expected behaviour [期望结果]
文字大小正常显示
ECharts option [ECharts配置项]

option = {"tooltip":{"show":false},"series":[{"type":"graph","layout":"force","roam":true,"lineStyle":{"normal":{"color":"source","curveness":0.1}},"label":{"normal":{"show":true,"position":"right"}},"force":{"repulsion":180,"layoutAnimation":false,"edgeLength":[200,250]},"edgeSymbol":["circle","arrow"],"edgeSymbolSize":[1,8],"data":[{"name":"DEVDB:11326","count":4,"id":"DEVDB:11326","category":"DEVDB:11326","itemStyle":null,"symbolSize":30,"y":null,"x":null,"draggable":false},{"name":"DEVBTPRO:11326","count":0,"id":"DEVBTPRO:11326","category":"DEVBTPRO:11326","itemStyle":null,"symbolSize":30,"y":null,"x":null,"draggable":false},{"name":"UNKNOWN:0","count":9,"id":"UNKNOWN:0","category":"UNKNOWN:0","itemStyle":null,"symbolSize":60,"y":null,"x":null,"draggable":false}],"categories":[{"name":"DEVDB:11326"},{"name":"DEVBTPRO:11326"},{"name":"UNKNOWN:0"}],"links":[{"source":"DEVBTPRO:11326","target":"DEVDB:11326"},{"source":"DEVDB:11326","target":"UNKNOWN:0"},{"source":"DEVBTPRO:11326","target":"UNKNOWN:0"}],"animation":false}]}

Other comments [其他信息]

@pissang is this bug fiexd?

@pissang  #8399 is the same issue

@100pah  is this bug fiexd? #8399 is the same issue

Hi, I'm facing the same issue. Have you found a fix?

Text scale has already been fixed. Text position is wrong.

authors: Ovilia node-rookie rikunashoujo tinhour

repo: apache/incubator-echarts

license_source: bigquery


text:
[Enhancement] Method invocation may produce 'NullPointerException'[MessageUtils]

Search before asking

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

Enhancement Request

located at:
eventmesh-sdk-java/src/main/java/org/apache/eventmesh/client/tcp/common/MessageUtils.java line 97,102
Describe the solution you'd like
e.g.

Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

created pull request for #3096; I commit changes for this there.

created pull request for #3096; I commit changes for this there.

No changes were found in https://github.com/apache/eventmesh/pull/3135 to fix this issue. This issue is unfixed and open for contribution.

@Pil0tXia
This seems like an easy job, I wonder if I could be assigned it? 🫣

@cnzakii Of course

authors: Alonexc Pil0tXia cnzakii jjbiggins

repo: apache/incubator-eventmesh


text:
[Gearpump 311] refactor state management

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the commit message is formatted like:
[GEARPUMP-<Jira issue #>] Meaningful description of pull request
[ ] Make sure tests pass via sbt clean test.
[ ] Make sure old documentation affected by the pull request has been updated and new documentation added for new functionality.

Hi @yanghua , thanks for your contribution! This is a huge pull request so I think it would take a while to fully review this one, and also, can you give some description of this pull request about it's mainly idea or design, which would be great help, thanks!

hi @huafengw , this PR works for supporting state management.
state api and usage
It provides a suit of state APIs for gearpump such as :

ValueState
SetState
MapState
...

If users want store some useful state to build there business, they need implement a Processor extends StatefulTask and override it's open method to init state access object like this :
stateInternals = getStateInternals(StringUtf8Coder.of, "partitionedKey")
valueState = stateInternals.get.state(StateNamespaces.global, StateTags.value(valueStateTag, VarLongCoder.of)

you must specify a key for your state because the state would be key-partitioned store and access

then you must override core message handle method invoke to process messages. In this method you can use state api to access your state like this :
//read
val state = valueState.read
//write
valueState.write(1L)

design and implement
in general, this PR mostly contains four parts, list below:

state api trait
coders provide encode(serialize) and decode(deserialize) functions for specific state type
state manage and store abstract
a default state manage implementation backed with heap memory

state store data structure
Generally speaking, it's a two-level index structure. The first level index is StateNamespace and the second level index is StateTag, you can simply think it as a table's row and column.
It uses Guava's Table data structure as default storage implementation. StateNamespace as row key, StateTag as column key and State as value.
integration with checkpoint
finally, the state will integrate with gearpump's checkpoint mechanism and provide exactly-once process semantic guarantee!
the StatefulTask will try to recovery when the task onStart and will try to snapshot states when the task onWatermarkProgress
But there are some problems about integrating with checkpoint when recovering.
inspiration
there state api inspired by Apache Beam and compatible with Apache Beam. Now supported state apis is a subset of Apache Beam's state apis. And StateInternals partly inspired by Apache Beam's Apex runner.

authors: huafengw yanghua

repo: apache/incubator-gearpump


text:
[VL] Fix preProjection to rowConstruction in HashAggregateTransformerMetrics

What changes were proposed in this pull request?
Fix preProjection to rowConstruction in HashAggregateTransformerMetrics.
How was this patch tested?
N/A

@PHILO-HE I found a missing modification in the HashAggregate metrics.

repo: apache/incubator-gluten


text:
[GLUTEN-6562][VL]Set BUILD_BENCHMARKS=ON if BUILD_TESTS is enabled

What changes were proposed in this pull request?
Building Gluten tests depends on gluten benchmark , so we need to set BUILD_BENCHMARKS=ON when BUILD_TESTS is enabled.
Fixes: #6562
How was this patch tested?
I successfully built gluten tests with ./compile.sh --build_velox_backend=ON --build_tests=ON --build_examples=ON that BUILD_BENCHMARKS is not enabled

@xumingming, I note you also found this issue, could you take a review?

Is it possible to not mix BUILD_TESTS and BUILD_BENCHMARKS together? I think it is cleaner, what we need to do is do not let tests code depends on benchmark related code.

Is it possible to not mix BUILD_TESTS and BUILD_BENCHMARKS together? I think it is cleaner, what we need to do is do not let tests code depends on benchmark related code.

@xumingming, I agree. @NEUpanning, we may need to extract out the shared code from benchmark module.

@PHILO-HE @xumingming I have updated the code so that the gluten tests no longer depends on the gluten benchmarks.

Looks good to me.

authors: NEUpanning PHILO-HE xumingming


text:
[Feature][Manager] Support Iceberg sink

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Supported with #2583

authors: dockerzhang healchow

repo: apache/incubator-inlong


text:
[IOTDB-239] Add interface for showing devices

Create an interface for showing all the devices.
USAGE: SHOW DEVICES.

Hi @qiaojialin @kr11 ,
Thanks a lot for your detailed review! I have updated codes as you suggested.

repo: apache/incubator-iotdb


text:
Support Dynamic GraphQL query registering in Data Audit

So far registering queries in data audit requires rebuild and redeploy. This address this point to avoid this.

https://github.com/apache/incubator-kie-kogito-apps/pull/1962

repo: apache/incubator-kie-issues