Can we run multiple workers for a delayed queue

Hello,
The delayed queue is a good feature. But It seems there is a issue when a delayed queue consumed by multiple workers.  The implementation on WorkerImpl#pop will return a null when it is processing the same job with the another worker. That will be a big performance issue if there are many collisions like this.

@junwchina Do you have a proposal for how to address this issue?

Yes, I have a thought. The basic idea is all ready jobs should be pushed to regular queue which is implemented by list type.
Let's say each queue will have two internal queues, one is a delayed queue in zset, the another is a regular queue in list. In the main loop, I will handle the queue's delayed queue firstly, and push all ready delayed jobs into it's regular queue. No matter there is any ready delayed jobs, I will handle the queue's regular queue then. Since the regular queue is a list type, we can use lpop or rpop to get a job to run. These operators are atomic, so we don't need to care the multiple thread issue. It ensures every thread should can get a job to run if it's not empty.
Also, there is a rpoplpush operator in redis which is atomic too, maybe we can use it to implement lpoplpush. The current implementation will get collision too on multiple threads environments.
That's all, please let me know how do you think.

hey @junwchina, moving that to the main loop sounds nice, but this issue can crop up again when running jesque on multiple machines.
Another way would be to perform zrange and zrem within a multi/exec, that way it acts like an atomic zpop.
Something like this:
> multi
OK
> zrangebyscore resque:queue:fooSchedule -1<PHONE_NUMBER>000 withscores
QUEUED
> zremrangebyscore resque:queue:fooSchedule -1<PHONE_NUMBER>000
QUEUED
> EXEC
1) 1) "{\"class\":\"fooScheduleJob\",\"args\":[54625],\"vars\":null}"
   2) "1450151700000"
2) (integer) 1

> multi
OK
> zrangebyscore resque:queue:fooSchedule -1<PHONE_NUMBER>000 withscores
QUEUED
> zremrangebyscore resque:queue:fooSchedule -1<PHONE_NUMBER>000
QUEUED
> EXEC
1) (empty list or set)
2) (integer) 0

related: https://groups.google.com/forum/#!msg/redis-db/ur9U8o-Sko0/tgefLK3zrzQJ
cc @gresrun

@argvk @junwchina @zhangliuping
This definitely looks like an issue that needs to be addressed. I'm currently in the process of relocating from Florida to California so, I am currently not able to take a look at this. Pull requests are most welcome!

@argvk Yes, Multi/Exec is a way to fix this issue. Can you clarify why you think my solution will have issue on multiple machines?
I prefer to use two internal queues. The reason is:

zremrangebyscore's time complex is O(log(N)), but lpop or rpop is only O(1). I think it's better to save as few as possible jobs in delayed queue.  So in the main loop, I would like to get all ready jobs from delayed queue by one operator, and push all of them into regular queue.
Since all running jobs are fetching from the internal regular queue. So we can enqueue all kinds of jobs into one queue.
is coming.. :)

@argvk @gresrun Please let me know how do you think.

@junwchina I meant to say jesque instances running on multiple machines, might have concurrency issues, due to multiple main loops running across them all. Totally agree with your points, the MULTI/EXEC is in addition to moving it to the main loop.
thoughts ?
:+1:

@argvk I think that should not be a problem on multiple machines. We just need to ensure every redis operator must be atomic. That would be possible based on current redis version.

@junwchina OK, I'm trying to work on this and I having a little difficulty understanding this part

I would like to get all ready jobs from delayed queue by one operator,

AFAIK, zremrangebyscore only returns the numbers of elements removed. So, is there something else I can use to return and remove the elements atomically ?

@argvk  Just like you said in the previous message. You can use zrangebyscore and zremrangebyscore together within Multi/Exec.

Any implementation which will require 2 extra redis calls will not scale well under load. Even the query to check type is overloading the redis in my case. This is because redis performance in VM environments is not very good. I am getting around 40k-50k ops per second on a VM as opposed to dedicated hardware where i get around 200K

Here's a novel idea: replace the majority of WorkerImpl.pop() with an EVAL of a lua script that returns the next job.
local queueKey = KEYS[1]
local inFlightKey = KEYS[2]
local freqKey = KEYS[3]
local now = ARGV[1]

local payload = nil

local not_empty = function(x)
  return (type(x) == 'table') and (not x.err) and (#x ~= 0)
end

local ok, queueType = next(redis.call('TYPE', queueKey))
if queueType == 'zset' then
	local i, lPayload = next(redis.call('ZRANGEBYSCORE', queueKey, '-inf', now, 'WITHSCORES'))
	if lPayload then
		payload = lPayload
		local frequency = redis.call('HGET', freqKey, payload)
		if frequency then
			redis.call('ZINCRBY', queueKey, frequency, payload)
		else
			redis.call('ZREM', queueKey, payload)
		end
	end
elseif queueType == 'list' then
	payload = redis.call('LPOP', queueKey)
	if payload then
		redis.call('LPUSH', inFlightKey, payload)
	end
end

return payload

Since the evaluation of scripts are atomic, this is guaranteed to be safe for multiple workers. Thoughts?
cc @junwchina @argvk @abhinavdwivedi

Take a look at 5721a43 (on a new branch lua_pop) for a proof-of-concept. As a side-note, the Lua-based pop() is over twice as fast in my micro-benchmark!
cc @junwchina @argvk @abhinavdwivedi

@gresrun that'd be perfect, debugging WorkerImpl.pop() might not be all that straightforward, but personally it is trade-off I'm OK with.
:christmas_tree:

@gresrun It likes a big MULTI/EXEC operator. I think these three keys will be blocked longer then separated MULTI/EXEC.
Happy Christmas！:christmas_tree:

@junwchina I was concerned about the same thing but my initial testing showed just the opposite; overall job throughput almost doubled(!) for a single worker using the new Lua-based implementation of pop(). Using this mirco-benchmark, which uses standard queues, I got the following results:
Jesque-2.1.0 => ~2500 jobs/sec
10:13:41.287 [main] INFO  n.g.jesque.perftest.PerfTest - Starting test...
10:13:47.806 [main] INFO  n.g.jesque.perftest.PerfTest - Enqueue complete!
10:13:47.807 [Worker-0 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.PerfTest - Started the clock...
10:14:27.757 [Worker-0 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.PerfTest - Completed 100000 jobs in 39950ms - Avg. 2503.1289111389237 jobs/sec
10:14:27.761 [main] INFO  n.g.jesque.perftest.PerfTest - Test complete!

Jesque-2.1.1-SNAPSHOT/lua_pop => ~4200 jobs/sec
10:15:38.862 [main] INFO  n.g.jesque.perftest.PerfTest - Starting test...
10:15:45.436 [main] INFO  n.g.jesque.perftest.PerfTest - Enqueue complete!
10:15:45.437 [Worker-0 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.PerfTest - Started the clock...
10:16:09.293 [Worker-0 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.PerfTest - Completed 100000 jobs in 23855ms - Avg. 4191.993292810732 jobs/sec
10:16:09.294 [main] INFO  n.g.jesque.perftest.PerfTest - Test complete!

@gresrun Maybe it's because you wrapped all of these redis operators into one, and decreased some network requests. If there are only one worker to consume the jobs, I think it should be perfect. I am afraid what if there are many workers to consume and lots of clients are enqueue at the same time. All workers and clients do want to have an operator on these keys, the bottleneck might occur.

@junwchina OK, I wanted to see if that is the case so I modified my test to allow utilize multiple workers and the results indicate the Lua pop is far better under heavy contention!
4 Workers
Jesque-2.1.0 => ~4250 jobs/sec with 4 workers :frowning:
23:54:41.600 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Starting test...
23:54:48.020 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Enqueue complete!
23:54:48.021 [Worker-2 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Started the clock...
23:55:11.662 [Worker-2 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Completed 100000 jobs in 23641ms - Avg. 4229.93951186498 jobs/sec
23:55:11.664 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Test complete!

Jesque-2.1.1-SNAPSHOT/lua_pop => ~10550 jobs/sec with 4 workers :smile:
23:55:57.815 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Starting test...
23:56:04.314 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Enqueue complete!
23:56:04.315 [Worker-2 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Started the clock...
23:56:13.805 [Worker-2 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Completed 100000 jobs in 9489ms - Avg. 10538.518284329224 jobs/sec
23:56:13.807 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Test complete!

8 Workers
Jesque-2.1.0 => ~2800 jobs/sec with 8 workers :frowning: :frowning:
23:58:36.598 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Starting test...
23:58:43.007 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Enqueue complete!
23:58:43.008 [Worker-5 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Started the clock...
23:59:19.015 [Worker-3 Jesque-2.1.0: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Completed 100000 jobs in 36007ms - Avg. 2777.2377593245756 jobs/sec
23:59:19.018 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Test complete!

Jesque-2.1.1-SNAPSHOT/lua_pop => ~12950 jobs/sec with 8 workers :smile: :smile:
23:57:17.676 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Starting test...
23:57:24.218 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Enqueue complete!
23:57:24.220 [Worker-2 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Started the clock...
23:57:31.950 [Worker-4 Jesque-2.1.1-SNAPSHOT: RUNNING] INFO  n.g.jesque.perftest.MultiPerfTest - Completed 100000 jobs in 7730ms - Avg. 12936.6106080207 jobs/sec
23:57:31.953 [main] INFO  n.g.jesque.perftest.MultiPerfTest - Test complete!

@gresrun OK. It seems very good.

Merged.

@gresrun Thanks for your hard work. :+1:

Is there already a release date for 2.1.1? I'd need a release to depend on including the fix for this issue. Thanks for sharing Jesque!

@thammerl I just cut Jesque 2.1.1; it should appear in Maven Central in a few hours.

Just copying my own benchmarks..
Job times: 10, 50, 200, 1000, 5000 (in ms)
Num of Workers: 10, 20, 40, 50, 100, 150
Case 1) Jesque 2.0.2
04-09-2015 20:49:35.873 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 20:49:51.733 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10), Time: (15860ms)
04-09-2015 20:50:01.914 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 20:50:12.576 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50), Time: (10662ms)
04-09-2015 20:50:22.730 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 20:50:48.489 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200), Time: (25759ms)
04-09-2015 20:50:58.795 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 20:52:39.150 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000), Time: (100355ms)
04-09-2015 20:52:49.660 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:01:10.626 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000), Time: (500966ms)
04-09-2015 21:01:20.873 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 21:01:27.009 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10), Time: (6136ms)
04-09-2015 21:01:37.326 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 21:01:43.398 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50), Time: (6072ms)
04-09-2015 21:01:53.895 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 21:02:10.148 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200), Time: (16253ms)
04-09-2015 21:02:20.652 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 21:03:11.742 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000), Time: (51090ms)
04-09-2015 21:03:22.167 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:07:33.406 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000), Time: (251239ms)
04-09-2015 21:07:43.668 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 21:07:50.437 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10), Time: (6769ms)
04-09-2015 21:08:00.853 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 21:08:07.907 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50), Time: (7054ms)
04-09-2015 21:08:18.124 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 21:08:25.022 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200), Time: (6898ms)
04-09-2015 21:08:35.340 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 21:09:02.231 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000), Time: (26891ms)
04-09-2015 21:09:12.544 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:11:19.469 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000), Time: (126925ms)
04-09-2015 21:11:29.844 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 21:11:37.097 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10), Time: (7253ms)
04-09-2015 21:11:47.629 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 21:11:55.427 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50), Time: (7798ms)
04-09-2015 21:12:05.889 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 21:12:13.212 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200), Time: (7323ms)
04-09-2015 21:12:23.582 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 21:12:45.744 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000), Time: (22162ms)
04-09-2015 21:12:56.049 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:14:38.528 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000), Time: (102479ms)
04-09-2015 21:14:49.049 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 21:15:03.813 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10), Time: (14764ms)
04-09-2015 21:15:14.330 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 21:15:29.035 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50), Time: (14705ms)
04-09-2015 21:15:39.589 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 21:15:49.156 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200), Time: (9567ms)
04-09-2015 21:15:59.699 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 21:16:14.611 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000), Time: (14912ms)
04-09-2015 21:16:25.161 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:17:19.808 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000), Time: (54647ms)
04-09-2015 21:17:30.311 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10)
04-09-2015 21:17:52.667 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10), Time: (22356ms)
04-09-2015 21:18:03.241 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50)
04-09-2015 21:18:25.547 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50), Time: (22306ms)
04-09-2015 21:18:35.727 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200)
04-09-2015 21:18:53.128 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200), Time: (17401ms)
04-09-2015 21:19:03.696 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000)
04-09-2015 21:19:21.700 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000), Time: (18004ms)
04-09-2015 21:19:32.271 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000)
04-09-2015 21:20:14.815 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000), Time: (42544ms)
Case 2) Jesque 2.1.1
10-01-2016 18:28:51.603 [main] [ERROR] JesqueTaskExecutionBenchmark - Benchmark Initialized? (true)
10-01-2016 18:28:51.603 [main] [ERROR] JesqueTaskExecutionBenchmark - benchmark started successfully
10-01-2016 18:28:51.776 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:28:57.510 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10), Time: (5734ms)
10-01-2016 18:29:07.735 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (100)
10-01-2016 18:29:22.992 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (100), Time: (15257ms)
10-01-2016 18:29:33.400 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:31:13.645 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000), Time: (100245ms)
10-01-2016 18:32:47.470 [main] [ERROR] JesqueTaskExecutionBenchmark - Benchmark Initialized? (true)
10-01-2016 18:32:47.470 [main] [ERROR] JesqueTaskExecutionBenchmark - benchmark started successfully
10-01-2016 18:32:47.622 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:32:53.541 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10), Time: (5919ms)
10-01-2016 18:33:03.708 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:33:13.960 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50), Time: (10252ms)
10-01-2016 18:33:24.164 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 18:33:49.377 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200), Time: (25213ms)
10-01-2016 18:33:59.658 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:35:39.912 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000), Time: (100254ms)
10-01-2016 18:35:50.359 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 18:44:11.058 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000), Time: (500699ms)
10-01-2016 18:44:21.212 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:44:26.438 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10), Time: (5226ms)
10-01-2016 18:44:36.853 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:44:42.071 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50), Time: (5218ms)
10-01-2016 18:44:52.514 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 18:45:07.690 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200), Time: (15176ms)
10-01-2016 18:45:18.212 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:46:08.404 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000), Time: (50192ms)
10-01-2016 18:46:18.674 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 18:50:28.973 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000), Time: (250299ms)
10-01-2016 18:50:39.210 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:50:44.455 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10), Time: (5245ms)
10-01-2016 18:50:54.666 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:50:59.851 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50), Time: (5185ms)
10-01-2016 18:51:10.349 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 18:51:20.525 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200), Time: (10176ms)
10-01-2016 18:51:30.945 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:51:56.117 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000), Time: (25172ms)
10-01-2016 18:52:06.369 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 18:54:11.633 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000), Time: (125264ms)
10-01-2016 18:54:22.119 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:54:27.381 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10), Time: (5262ms)
10-01-2016 18:54:37.554 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:54:42.724 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50), Time: (5170ms)
10-01-2016 18:54:53.070 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 18:54:58.247 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200), Time: (5177ms)
10-01-2016 18:55:08.627 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:55:28.792 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000), Time: (20165ms)
10-01-2016 18:55:38.922 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 18:57:19.138 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000), Time: (100216ms)
10-01-2016 18:57:29.675 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:57:34.964 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10), Time: (5289ms)
10-01-2016 18:57:45.028 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:57:50.232 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50), Time: (5204ms)
10-01-2016 18:58:00.778 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 18:58:05.948 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200), Time: (5170ms)
10-01-2016 18:58:16.321 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 18:58:26.501 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000), Time: (10180ms)
10-01-2016 18:58:37.041 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 18:59:27.287 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000), Time: (50246ms)
10-01-2016 18:59:37.845 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10)
10-01-2016 18:59:43.095 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10), Time: (5250ms)
10-01-2016 18:59:53.356 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50)
10-01-2016 18:59:58.670 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50), Time: (5314ms)
10-01-2016 19:00:08.891 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200)
10-01-2016 19:00:14.074 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200), Time: (5183ms)
10-01-2016 19:00:24.514 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000)
10-01-2016 19:00:34.689 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000), Time: (10175ms)
10-01-2016 19:00:44.812 [main] [ERROR] JesqueTaskExecutionBenchmark - Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000)
10-01-2016 19:01:20.021 [main] [ERROR] JesqueTaskExecutionBenchmark - End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000), Time: (35209ms)

Copying my old and latest becnhmarks:
Job times: 10, 50, 200, 1000, 5000 in ms
Num of Workers: 10, 20, 40, 50, 100, 150
Case 1) Jesque 2.0.2
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10), Time: (15860ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50), Time: (10662ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200), Time: (25759ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000), Time: (100355ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000), Time: (500966ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10), Time: (6136ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50), Time: (6072ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200), Time: (16253ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000), Time: (51090ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000), Time: (251239ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10), Time: (6769ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50), Time: (7054ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200), Time: (6898ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000), Time: (26891ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000), Time: (126925ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10), Time: (7253ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50), Time: (7798ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200), Time: (7323ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000), Time: (22162ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000), Time: (102479ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10), Time: (14764ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50), Time: (14705ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200), Time: (9567ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000), Time: (14912ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000), Time: (54647ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10), Time: (22356ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50), Time: (22306ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200), Time: (17401ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000), Time: (18004ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000), Time: (42544ms)
Case 2 - Jesque 2.1.1
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (10), Time: (5919ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (50), Time: (10252ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (200), Time: (25213ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (1000), Time: (100254ms)
Start of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (10), numTask: (1000), jobTimeInMillis: (5000), Time: (500699ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (10), Time: (5226ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (50), Time: (5218ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (200), Time: (15176ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (1000), Time: (50192ms)
Start of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (20), numTask: (1000), jobTimeInMillis: (5000), Time: (250299ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (10), Time: (5245ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (50), Time: (5185ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (200), Time: (10176ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (1000), Time: (25172ms)
Start of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (40), numTask: (1000), jobTimeInMillis: (5000), Time: (125264ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (10), Time: (5262ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (50), Time: (5170ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (200), Time: (5177ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (1000), Time: (20165ms)
Start of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (50), numTask: (1000), jobTimeInMillis: (5000), Time: (100216ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (10), Time: (5289ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (50), Time: (5204ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (200), Time: (5170ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (1000), Time: (10180ms)
Start of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (100), numTask: (1000), jobTimeInMillis: (5000), Time: (50246ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (10), Time: (5250ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (50), Time: (5314ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (200), Time: (5183ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (1000), Time: (10175ms)
Start of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000)
End of Run - maxWorkers: (150), numTask: (1000), jobTimeInMillis: (5000), Time: (35209ms)

@gresrun Thanks a lot!

because this Jesque 2.1.1 must use redis 2.6.x ？


Feature: new account - activity section

To see the preview of the Account details page, go to any account and edit the URL with /beta/ prefix like so:
Before: https://frontend-pr-937-7w1z.onrender.com/accounts/frol.near
After: https://frontend-pr-937-7w1z.onrender.com/beta/accounts/frol.near
More preview links:
https://frontend-pr-937-7w1z.onrender.com/beta/accounts/multisender.app.near
https://frontend-pr-937-7w1z.onrender.com/beta/accounts/qbit.poolv1.near
https://frontend-pr-937-7w1z.onrender.com/beta/accounts/9755042d33e148f87265c3343b69ed902939f166.lockup.near
https://frontend-pr-937-7w1z.onrender.com/beta/accounts/foundation.near
https://frontend-pr-937-7w1z.onrender.com/beta/accounts/82f09db4a072c66f89e8e226234181bb53f5ec24.lockup.near

Closing in favor of #1006


refactor: simplify AST structure for some enum nodes

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[x] N
[ ] Y

refactor: simplify AST structure for some enum nodes

2. What is the scope of this PR (e.g. component or file name):

kclvm/ast/src/ast.rs

3. Provide a description of the PR(e.g. more details, effects, motivations or doc link):

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[x] Other

refactor: simplify AST structure for some enum nodes

4. Are there any breaking changes?(Y/N) and describe the breaking changes(e.g. more details, motivations or doc link):

[x] N
[ ] Y

5. Are there test cases for these changes?(Y/N) select and add more details, references or doc links:

[x] Unit test
[ ] Integration test
[ ] Benchmark (add benchmark stats below)
[ ] Manual test (add detailed scripts or steps below)
[ ] Other

kclvm/parser/src/tests/snapshots/**.snap

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
15.3%

Covered Lines:
2293

Relevant Lines:
2612

💛  - Coveralls


Upgrade to postcss 6.x

This requires a major version bump.
PostCSS Changelog

"dependencies": {
"autoprefixer": "^7.0.0",
"caniuse-api": "^2.0.0",
"chalk": "^1.1.1",

[ ]    "pixrem": "?",
[ ]    "pleeease-filters": "?",
"postcss": "^6.0.0",
[ ]    "postcss-apply": "?",
[x]    "postcss-attribute-case-insensitive": "^2.0.0",
[ ]    "postcss-calc": "?",
[ ]    "postcss-color-function": "?",
[ ]    "postcss-color-gray": "?",
[ ]    "postcss-color-hex-alpha": "?",
[ ]    "postcss-color-hsl": "?",
[ ]    "postcss-color-hwb": "?",
[ ]    "postcss-color-rebeccapurple": "?",
[ ]    "postcss-color-rgb": "?",
[ ]    "postcss-color-rgba-fallback": "?",
[ ]    "postcss-custom-media": "?",
[ ]    "postcss-custom-properties": "?",
[ ]    "postcss-custom-selectors": ""?",
[ ]    "postcss-font-family-system-ui": "?",
[ ]    "postcss-font-variant": "?",
[ ]    "postcss-initial": "?",
[ ]    "postcss-media-minmax": "?",
[ ]    "postcss-nesting": "?",
[ ]    "postcss-pseudo-class-any-link": "?",
[ ]    "postcss-pseudoelements": "?",
[ ]    "postcss-replace-overflow-wrap": "?",
[ ]    "postcss-selector-matches": "?",
[ ]    "postcss-selector-not": "?"
},

Thanks for this issue. Feel free to make PR whenever you can (lot of work, I know).
I just gave you push access to this repo since you contributed a lot already.
I will do the same for all other repo I can as soon as I will see PR on (and if you ask for it).

"postcss-font-family-system-ui": "^2.0.0"

I've released https://github.com/postcss/postcss-calc/releases/tag/v6.0.0.

I think it's related, with latest postcss-loader this package (postcss-cssnext) isn't working.
Config part in webpack:
{
            // PostCSS loader to postprocesses CSS with PostCSS plugins.
            loader: 'postcss-loader',
            options: {
              // Makes it referenceable by other loaders.
              ident: 'postcss',
              plugins: () => [
                // Transforms CSS specs into more compatible CSS so don't need to wait for browser support.
                cssnext({
                  /**
                   * List of browsers query which are supported in project.
                   * Options passed to `cssnext`:
                   *  - `> 1%` -> versions selected by global usage statistics.
                   *  - `last 4 versions` -> the last 4 versions for each major browser.
                   *  - `Firefox ESR` -> the latest [Firefox ESR] version.
                   *  - `not ie < 9` -> exclude IE 8 and below, because React supports only IE 9 and above.
                   */
                  browsers: [
                    '> 1%',
                    'last 4 versions',
                    'Firefox ESR',
                    'not ie < 9'
                  ]
                })
              ]
            }
          }

P.S. Everything is fine with postcss-loader 1.3.3, but not the latest!

I released https://github.com/jonathantneal/postcss-nesting which is now using v6

@Semigradsky, I have PRs for updating postcss-rebeccapurple.
https://github.com/postcss/postcss-color-rebeccapurple/pull/9 — updates PostCSS to v6, updates other dependencies, improves the plugin to not partially update invalid colors like oldrebeccapurple.
https://github.com/postcss/postcss-color-rebeccapurple/pull/8 — just updates PostCSS to v6.
I made them separate PRs incase @MoOx had no interest in the other improvements at this time (or if he found them not to be suitable improvements).

@Semigradsky, https://github.com/jonathantneal/postcss-pseudo-class-any-link is also updated.

@Semigradsky, PR submitted for postcss-replace-overflow-wrap
https://github.com/MattDiMu/postcss-replace-overflow-wrap/pull/5

@jonathantneal @Semigradsky I created a cssnext team in postcss org and you have been added as collab there. Will add you as collab on npm on each repo I have the rights on.

My workflow is: commits + a "x.y.z" commit with changelog notes + package.json version bump + "npm run release" (see scripts ;)). You are the bosses here :)

My recommendation will be to move to a monorepo for the repos we can + remove jscs and all outdated stuff in favor of eslint + eslint-config-i-am-meticulous + prettier + jest (with snapshots) but that might take some time :D

High priority ⚠  ladies and gentlenerds 😛 how can someone help? Any blockers in one of the plugins ?

There's ways of expressing that sentiment that aren't condescending & rude, please show some respect for those of us who work on this stuff in our spare time.

@ben-eb 😟 That wasn't meant to be consdescending or rude, I also asked how to help getting the last bits done 😕

@michael-ciniawsky, @Semigradsky, please review https://github.com/MoOx/postcss-cssnext/pull/384

https://github.com/postcss/gulp-postcss/issues/118

Hi! Seems that last deps is merged https://github.com/MattDiMu/postcss-replace-overflow-wrap/pull/5 and new version have been released (postcss-replace-overflow-wrap@2.0.1-0).
Could you release new cssnext version?

What is missing here? Any plugin still needs update?

For now, I can’t keep up. One of this can be merged and we can work from there, or it will be easier for me to release a different plugin with stages like babel.

Any update on this issue ?

Any sense update to chalk 2? And yes, any :up: ?

@jonathantneal cant we ship a thing until a new solution that include stages is ready?

Closing in favor of #400


Added version tag for docker build and push

This change is

@SchSeba please also add this new variable to devel-guide.md

@phoracek Done

LGTM, let's try it!

https://jenkins.ovirt.org/job/kubevirt_ovs-cni_standard-on-ghpush/17/

@SchSeba it failed with:
14:00:54 [check-merged.el7.x86_64] ./automation/check-merged.sh: line 16: ./hack/get_tag.sh: No such file or directory
14:00:54 [check-merged.el7.x86_64] + export IMAGE_TAG=
14:00:54 [check-merged.el7.x86_64] + IMAGE_TAG=
14:00:54 [check-merged.el7.x86_64] + make docker-build
14:00:54 [check-merged.el7.x86_64] make: *** No rule to make target `docker-build'.  Stop.

Yes can you revert I will update the PR I know the problem

@SchSeba could you revert it or just fix it in the fix PR?


Make selectors available in mindev

Summary
Let's make our life easier when developing profiles by making selectors
available in mindev
Fixes: #3726
Change Type

[ ] Bug fix (resolves an issue without affecting existing features)
[x] Feature (adds new functionality without breaking changes)
[ ] Breaking change (may impact existing functionalities or require documentation updates)
[ ] Documentation (updates or additions to documentation)
[ ] Refactoring or test improvements (no bug fixes or new functionality)

Testing
AUTH_TOKEN=youdliketoknowwouldntyou go run cmd/dev/main.go ruletype test --profile /Users/jakub/devel/playground/ghas-selectors.yaml --rule-type /Users/jakub/devel/minder-rules-and-profiles/rule-types/github/secret_scanning.yaml --entity /Users/jakub/devel/playground/repository.yaml --log-level=debug
Profile valid according to the JSON schema!
{"level":"info","eval_status":"skipped","action":"remediate","Timestamp":1721397355551920000,"message":"action is off, skipping"}
{"level":"info","eval_status":"skipped","action":"alert","Timestamp":1721397355551935000,"message":"action is off, skipping"}
Error: error evaluating rule type: evaluation skipped: entity not selected by selectors
Message: Error on execute
Details: error evaluating rule type: evaluation skipped: entity not selected by selectors
exit status 1

Review Checklist:

[x] Reviewed my own code for quality and clarity.
[ ] Added comments to complex or tricky code sections.
[ ] Updated any affected documentation.
[ ] Included tests that validate the fix or feature.
[ ] Checked that related changes are merged.

coverage: 54.183%. remained the same
when pulling 786af47b19d4b19433d875cc5e3c8dda233ef173 on jhrozek:selectors_mindev
into 8041df27e1a06c680702ecce1ac9c05055a3dc15 on stacklok:main.


Add GCBR logo to GWAS Catalog homepage

Now we have been endorsed as a Global Core Biodata Resource, we need to add the logo to our homepage. The logos can be found here: https://drive.google.com/drive/folders/1qyiHHzf-hSHDJi-a3jc68arFA1F9yger?usp=share_link
(access needs to be requested from GCBR)

If complicated to do in current version, this could be rolled in with the new changes

Open to other suggestions as to where to position logo

Additional info from Matthew Thakur (email fwd from Helen 24 Jan):
Dear GBC resources,
Just checking back in on this thread from late last year - I note that many of you have already updated your resource websites with GCBR badges.
I was thinking about how to make sure we have a bit of consistency in formatting for resources with more than one badge (CoreTrust Seal, GCBR and ELIXIR). After checking in with Geetika and Niki in the web team about this - when they next update the visual fraemwork, they may tweak some of the existing functionality to reflect the proliferation of badges beyond the ELIXIR CDR it was originally designed for. But in the meantime (and as many resources aren't using visual framework modules anyway) - to make sure resources are displaying badges consistently and avoiding any design and accessibility no-no's, please follow Niki's advice below:

Simplest option is to use existing space in the footer - following the example of UniProt. Make sure that the badge is sized large enough to make out the text

We advise against customising and duplicating the Elixir banner (sorry ENA!) as this introduces contrast errors between the text and its background.

To show the badge alongside hypelinked text it's better to use vf-summary--has-image: https://stable.visual-framework.dev/components/vf-summary/#vf-summary--has-image

I'm sure you've all noted this particular string attached, but if your resource is a member of a wider consortium that was granted GCBR status, you may only use the GCBR logo and description in association with the wider consortium.

Accessability - to make sure the badges are legible to users of your pages using screen readers - provide the title of the destination page the badge links to as alt text (i.e. GLOBAL CORE BIODATA RESOURCES instead of "GCBR logo")

Please consider the above in how your resource displays the badges - we can share this guidance with the next round of GCBRs too in about a year's time!
Thanks,
Matt

added to labs


Rails thread safety issues

The documentation regarding thread safety isn't sufficient and this sometimes causes Rails apps to deadlock.

@Stex can you please check https://github.com/socketry/falcon#thread-safety-rails--5x as I don't think your report is the same as this issue.

@ioquatix As far as I see it, threadsafe! is no longer available in Rails 4.2, so I thought it wouldn't be necessary.
If I'm not completely blind, maybe the README should be updated regarding this.

In any case, I will update the README to reflect this, but can you let me know what's going on, on your end?

@ioquatix
Regarding the deadlock in Rails 4.2 (I agree this is different from the issue you opened) - I ran up against this today on a Rails 4.2.10 application - it looks like the code in Rails 4.2 that adds the middleware is a little different than you linked:
https://github.com/rails/rails/blob/4-2-stable/railties/lib/rails/application/configuration.rb#L25 (default nil)
https://github.com/rails/rails/blob/4-2-stable/railties/lib/rails/application/default_middleware_stack.rb#L29
So Rails 4.2 need to specify an explicit config.allow_concurrency = false
config.threadsafe! isn't present and trying to set that will error.

@rjocoleman So, what you are saying, is that in order for Rails 4.2 to break, you must have an explicit config.allow_concurrency = false?

Yikes, sorry I was struggling to send that message due to the Github downtime and it got a little garbled in my attempts.
Just the opposite, rails 4.2 will break by default because the default in that version is essentially config.allow_concurrency = false (it's nil).
Rails 4.2 users need to explicitly set config.allow_concurrency = true.

I was under the impression that nil meant "default". i.e. it should allow concurrency.
nil == false is not true.
I'd like to know for sure exactly what is going on.

In this version of Ruby (`ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]), in a Pry Rails console (4.2.10)
[1] pry(main)> puts 'foo' unless nil
foo
=> nil
[2] pry(main)> puts 'foo' unless false
foo
=> nil
[3] pry(main)> puts 'foo' unless true
=> nil

middleware.use ::Rack::Lock unless allow_concurrency? is the line in this version.

@rjocoleman can you check the proposed changes to the documentation and let me know if you think it's clear enough (and correct!)?

@ioquatix looks great to me, thanks!

Okay, I have updated documentation. If you have any additional things to add to that, any problems or things you could help others, please don't hesitate to add a PR updating the documentation. Thanks so much for your patience and feedback.


[Rendering] HTML Renderer Action.Execute for Input.Toggle puts quotes around result

Target Platforms
Other
SDK Version
2.7
Application Name
HTML
Problem Description
When I have bool true, false values the Action.execute post back has quotes around the value.
Expected:
data.X = true|false
Screenshots

Card JSON
{
    "type": "AdaptiveCard",
    "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
    "version": "1.5",
    "actions": [
        {
            "type": "Action.Execute",
            "title": "Action.Execute"
        }
    ],
    "body": [
        {
            "type": "Input.Toggle",
            "title": "New Input.Toggle",
            "id": "X",
            "valueOn":true,
            "valueOff": false
        }
    ]
}

Sample Code Language
No response
Sample Code
No response

@tomlm that's by design (and you contributed to it ;)) - Input.Toggle's values (value, valueOn, valueOff) are all strings. https://adaptivecards.io/explorer/Input.Toggle.html

Closing as by-design per David...Tom if you want this to be a request to change this, please re-open and I'll change this to a feature request


Clipboard on insecure pages

Describe the bug
Unable to copy text in the clipboard in http (non-secure) web pages.
To Reproduce

Visit an http site
Try to copy text
It'll produce an exception trying to read clipboard from navigator

Expected behavior
It should get the text from the clipboard
Additional context
Likely not a thing that can be overcome without a Chrome flag, since it seems to be a Chrome security thing.

Yep, looks like this is a chrome security feature:

As with many new APIs, the Clipboard API is only supported for pages served over HTTPS.

More can be read here: https://web.dev/async-clipboard/#security-and-permissions


tdlib: 1.8.39 -> 1.8.41

Add vonfry as maintainer

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 361732

x86_64-linux

:fast_forward: 1 package marked as broken and skipped:

pidginPackages.tdlib-purple

:white_check_mark: 8 packages built:

emacsPackages.telega
python311Packages.python-telegram
python311Packages.python-telegram.dist
python312Packages.python-telegram
python312Packages.python-telegram.dist
tdlib
tg
tg.dist

@ofborg eval

It seems that ofborg eval failure is unrelated to this pr.


[WIP] [Identity] TokenCache persistence redesign

This PR is a redesign of the mechanisms provided for persisting the token cache.

Removes the EnablePersistentCache and AllowUnencryptedCache options from the various TokenCredentialOptions classes providing them and replaces them with the TokenCache property.
Adds the classes TokenCache and the derived class PersistentTokenCache to enable applications to persist the token cache either via the built in MSAL extensions mechanisms, or in a completely custom way

Hi @schaabs.  There hasn't been recent engagement on this PR.  Would you please be so kind as to let us know if this is still an active work stream or if the PR should be closed out?

Since there hasn't been recent engagement, I'm going to close this out.  Please feel free to reopen if you'd like to continue working on these changes.


Replace lambda for 'dict' in with dict itself

lambda **kw: kw is not equivalent to the dict constructor. It is much less useful.
In particular it doesn't accept a sequence of pairs.
Why not put dict itself into the DEFAULT_NAMESPACE?
Principle of least surprise, etc.

Seems sensible. Thanks!


⚠ Processors has degraded performance

In 0e7fa80, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 73 ms

Resolved: Processors performance has improved in 58c9130.


Rules not equal

Hi there!
First let me say that you created a nice plugin!
My question: I really would like to detect changes in every folder except a specified on. Is this possible?
So I want the variable to be false if there are no other changes other than, lets say, something in folder 'x', and the variable to be true if anything else is changed.
I do understand that I can add multiple filter rules, but there would be a lot in stead of one simple rule.
Thanks in advance!
Niels

Hello,
I'm not sure it works with our implementation but I think you can do it if you use a single rule:
- task: ChangedFiles@1
  name: CheckChanges
  inputs:
    rules: |
      [SkipFolderX]
      !x/**

Hi SomaticIT,
Thanks! This seems to work.
Keep up the good work!

👍


Add note about mutex unsafety on multi-core systems

See #12.

Thanks, @adamgreig!
bors r+

bors r+


Forward function data to template

Clear and concise description of the problem
Allow to use function arguments as data on the template
Suggested solution
Something like ~
<script setup lang="ts">
import { useTemplatePromise } from 'vue-template-promise'

const ConfirmMessage = useTemplatePromise<'ok' | 'cancel'>()

async function handleSubmit() {
  const result = await ConfirmMessage.start({ message: "please confirm submit" })
}

async function handleDelete() {
  const result = await ConfirmMessage.start({ message: "please confirm delete" })
}
</script>

<template>
  <button @click="open">Open</button>
  <ConfirmMessage v-slot="{ resolve, data }">
    <dialog open>
      <p>{{ data.message }}</p>
      <button @click="resolve('cancel')">Cancel</button>
      <button @click="resolve('ok')">OK</button>
    </dialog>
  </ConfirmMessage>
</template>

Alternative
No response
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

never mind :v

Well, maybe not having to use array indexes will be good indeed.


Page "flashes" when it first loads because

Description

Type: Question

Question
The page seems to "flash" when it first loads because the server-rendered content is unstyled. It seems that main.css is added to <head> via Javascript.
Is there an easy way to remove this flashiness by adding main.css to <head> without JS?

It's related with #289 and only happens in dev environment.

Thanks! Sorry for duplicate. Couldn't find it.


How to use this plugin  in cakephp 3

Can We are use this on cakephp3 ?

This plugin is not compatible Cake 3 yet. There's PR for cake 3 support, but it's still WIP


Symlink files lead to errors

Hello @xeraph
2.6.0 tested on Debian 11 symlinks lead to errors:
Error: File not found. Skipping /etc/sv/ssh/supervise
Tested with and without --no-symlink
Thank you for your work!

@kleinski Hmm.. do you have permission on that file? On my machine:
$ ls -alFh test-symlink
lrwxrwxrwx 1 xeraph regular 4 Dec 22 19:02 test-symlink -> test/

$ ls -alFh test-symlink/
total 1.7M
drwxr-xr-x  2 xeraph regular   26 Dec 22 19:02 ./
drwx------ 22 xeraph regular 8.0K Dec 23 03:27 ../
-rw-r--r--  1 xeraph regular 1.7M Apr 21  2020 test-vuln.jar

$ ./log4j2-scan test-symlink/
Logpresso CVE-2021-44228 Vulnerability Scanner 2.6.0 (2021-12-23)
Scanning directory: test-symlink/ (without /dev, /dev/shm, /run, /sys/fs/cgroup, /proc/sys/fs/binfmt_misc, /run/user/16777216, /run/user/16777220)
[*] Found CVE-2021-44228 (log4j 2.x) vulnerability in /home/xeraph/test-symlink/test-vuln.jar, log4j 2.13.2

Scanned 1 directories and 1 files
Found 1 vulnerable files
Found 0 potentially vulnerable files
Found 0 mitigated files
Completed in 0.06 seconds

Yes, I have been root on the Debian system and tried the same as root on a Raspberry Pi with the jar.
The symlinked files are not existing, so the error output is alright, but as sometimes those symlinks can not be working - thinking of docker - it would be nice to not have that output.
Debian:
root@debcmk:~# /usr/lib/check_mk_agent/bin/log4j2-scan --no-symlink /
Logpresso CVE-2021-44228 Vulnerability Scanner 2.6.0 (2021-12-23)
Scanning directory: / (without /dev, /run, /dev/shm, /run/lock, /proc/sys/fs/binfmt_misc, /run/user/998, /run/user/0)
Error: File not found. Skipping /etc/sv/ssh/supervise
Error: File not found. Skipping /etc/sv/ssh/log/supervise
Error: File not found. Skipping /usr/lib/jvm/java-11-openjdk-amd64/lib/src.zip
Error: File not found. Skipping /usr/share/man/de/man4/console_ioctl.4.gz
Error: File not found. Skipping /usr/share/man/de/man4/tty_ioctl.4.gz
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authad
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/bookcreator
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/syntax.php
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authplain
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/cli.php
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/config
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authpgsql
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/admin.php
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/changes
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/include
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/info
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authpdo
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authmysql
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/popularity
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/styling
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/safefnrecode
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/usermanager
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/pagelist
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/acl
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/remote.php
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/revert
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authldap
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/index.html
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/indexmenu
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/action.php
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/dokuteaser
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/authmultisite
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/extension
Error: File not found. Skipping /opt/omd/sites/niko124/var/dokuwiki/lib/plugins/auth.php
Error: File not found. Skipping /opt/omd/sites/niko124/tmp/run/live-tcp
Error: File not found. Skipping /opt/omd/sites/niko124/local/share/nagios/htdocs/theme/images
Error: File not found. Skipping /opt/omd/sites/niko124/local/share/nagios/htdocs/theme/stylesheets

Scanned 14573 directories and 121389 files
Found 0 vulnerable files
Found 0 potentially vulnerable files
Found 0 mitigated files
Completed in 0.99 seconds
root@debcmk:~#

Raspbian, running some docker containers:
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc2.d/S01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/init.d/unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc0.d/K01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc4.d/S01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc1.d/K01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc6.d/K01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc5.d/S01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/etc/rc3.d/S01unifi
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/usr/lib/unifi/data/data
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/usr/lib/unifi/bin/mongod
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/usr/lib/unifi/run/run
Error: File not found. Skipping /var/lib/docker/overlay2/ce4ae0c3dc21f56eb1a7984566127a540c87967797d0a7540c54bc2afb235211/diff/usr/lib/unifi/logs/logs

@kleinski I got it. This output is due to changes for #196
I want to hear which is better from other users.

Maybe same approach for symlink is good alternative.. (error report for explicitly specified paths)

I think that your scanner should scan primarily existing jar files and not work as a detection tool for broken links as a simple
find . -type l ! -exec test -e {} \; -print would do that job.
So maybe a switch --report-broken-symlinks would be a good solution and as standard behaviour I suggest to drop the error messages.

@kleinski Would you test v2.6.1 release?

For me it is working as it should, many thanks.
And a question: The binaries are now really large - is it possible to get them as non static packages as well?

@kleinski Except some releases, only linux images are doubled.

logpresso-log4j2-scan-1.0.0-win64 (non-static) = 9.4MB (zip is 2.8MB)
logpresso-log4j2-scan-1.0.0-linux (non-static) = 9.1MB (tar.gz is 2.7MB)
logpresso-log4j2-scan-2.6.1-win64 (non-static) = 11.8MB (zip is 3.4MB)
logpresso-log4j2-scan-2.6.1-linux (non-static) = 17MB (tar.gz is 5.1MB)

And JAR file size are really got bigger.

logpresso-log4j2-scan-1.1.0 (6KB)
logpresso-log4j2-scan-2.6.0 (626KB)

Do you mean JAR file or native image file? It cannot be downsized any more.

Hello @xeraph
first I want to wish you a merry xmas!
I meant the native image files. Especially the linux binary, as we need to deploy them on many hosts.
But if it is not possible to shrink them, we will surely live with that.
Thanks again for your work here.


Add methods to create and update admin issued virtual cards

Fixed Issues
Part of https://github.com/Expensify/Expensify/issues/304890
Tests
Tested in https://github.com/Expensify/Web-Expensify/pull/39483
QA
None

I have read the CLA Document and I hereby sign the CLA


new function to write in the relationships index

We need to materialize the relations between strategic indicators and factors when the assessment is stored in the ElasticSearch.

Tasks:

[ ] Create test index
[ ] Add required fields to the mapping
[ ] Add test relations
[ ] Implement qma function

Estimated effort: 15 hours.

Pending integration
Spent effort until now ~= 15 hours


HOWTO

Hello,
After some time trying to figure out how to make this code connect to a running mpd daemon I'm on the edge of giving up.
I've have taken these steps as of now:

installed this via composer.

composer require dcarrith/lxmpd

published the config.

php artisan vendor:publish --provider="Dcarrith\LxMPD\LxMPDServiceProvider"

After this i changed the config to the right info for connecting to the mpd daemon

included the service provider.

Dcarrith\LxMPD\LxMPDServiceProvider::class,

in the app.php provicers array
Also tried to mock around setting up an alias to the facades but no luck figuring that one out either.
'lmpd' => Dcarrith\LxMPD\LxMPDFacade::class,

Can't wrap my brain around how to move on from here. Could you give me any hints?
Thanks in advance!

@rawzone - Have a look at how I use it in my other project dcarrith/mpdtunes.
https://github.com/dcarrith/mpdtunes/blob/master/app/config/app.php
https://github.com/dcarrith/mpdtunes/blob/master/app/config/packages/dcarrith/lxmpd/config.php
https://github.com/dcarrith/mpdtunes/blob/master/app/controllers/MPDTunesController.php
I don't remember if I've pushed all the latest changes to the mpdtunes project to github.  But, I do know that last time I did pushed, everything was working.  However, an issue did come up after I upgraded to Laravel 5.2 (it wasn't able to connect to MPD because it wasn't getting the configs from the Config facade like it did prior to Laravel 5.2).  I just haven't had time to look into it.

The underlying issue probably has something to do with my use of the Config facade inside the LxMPD package @ line 53:
https://github.com/dcarrith/lxmpd/blob/master/src/Dcarrith/LxMPD/LxMPDServiceProvider.php
If I remember correctly, that is the piece that broke with the upgrade to Laravel 5.x.
If you can figure out how to (update my code for the LxMPD package) so it retrieves the config variables for host, port and password in the new Laravel 5.x way, then you should be good to go.

@dcarrith thanks for the snappy answer..!
I will try to look a bit more on the code and see if i can come up with a way to get it working under Laravel 5.x.
The example code helped me understand things a bit better indeed. Ill keep you updated (make a pull request) if things get to a working state.
Thanks again.

@rawzone, I was able to get this working with Laravel 5.2. As @dcarrith mentioned, changes were needed to how the config values were accessed.  I just made a pull request with the change-- https://github.com/dcarrith/lxmpd/pull/2/files
If it still doesn't work after making the change and running php artisan vendor:publish, make sure that you can connect to the MPD through telnet or something (I only mention this because while I was debugging this I ran into an issue where my MPD wasn't starting correctly and I kept seeing 'Connection Refused' in the logs).

@wardcraigj Very nice - Thanks for keeping me informed. Will next week have some time for this project again and I'll test out your pull and see if I can get things going whit that.
Again - Thanks a ton for the info!

@rawzone-- In case you still look for it-- I just closed that PR and created a new one from a separate branch so I can commit to my fork's master without impacting the PR. The link is here: https://github.com/dcarrith/lxmpd/pull/3/files


initial AVM implementation

Description
This PR illustrates what a SQL Managed Instance implementation could (should?) look like.
The code lints & validates, I haven't yet run deployment tests given these take some time to run, but have used the instance level capabilities in this module in a customer environment with success.
Most child resources have been added but I don't have examples covering them yet.  Failover groups is noted tbd.
cc @timchapman
Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[X] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in locals.version.tf.json:

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in locals.version.tf.json.
[ ] Breaking changes and I have bumped the MAJOR version in locals.version.tf.json.
[ ] Update to documentation

Checklist

[X] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[X] I did run all  pre-commit checks

@timchapman any feedback?  I've continue development adding security alert policies and vulnerability assessments, and a fix for AzureRM not supporting both forms of managed identities.

cc @Azure/avm-core-team-technical

Hi, I'm just back from vacations, wondered if this just is not needed any more?  I'll drop my branch if so.


ScrollView component not scrollable within the overlay?

I'm struggling with the same issue - adding a ScrollView inside of the overlay, I cannot get it to scroll

Hello, I'm facing the same issue, any update on that?

Try wrapping the scrollview inside a view and put the following
<View style={{ height: 300, width: "100%", alignItems: "center" }}>
<ScrollView
style={{ marginTop: 20, width: "100%", marginLeft: 0 }}
>
 ...
 </ScrollView>
 </View>

Also having this issue FWIW, @ridwan85's solution didn't work for me


reads some fields of cloudProviderSpec from env variables.

What this PR does / why we need it: reads some fields of cloudProviderSpec from env variables.
the names of variables are hardcoded in the source code and cannot be changed.
there are other mechanisms through which the fields can be set, we only fallback
to reading from env variables when all fails.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #123
Special notes for your reviewer:

TODO: @p0lyn0mial update the documentation

I must say I really like this change, finally we can define a global auth info :)
As for the docs, maybe it would be easiest to just add a comment to the respective fields in the example yamls?

@alvaroaleman thanks for the review, comments addressed. PTAL

That is super awesome! Thank you very much for the very fast implementation!

@p0lyn0mial s/a/b is a short notion of "Please replace a with b, in the case above there is a spelling mitaske, its not varialbe but variable


Update view formatting schema to include tileProps

Added tileProps to the schema
Update description for existing properties
Fixed $ref for formatter to point to relevant version

@VesaJuvonen Could you please help merge this PR?

Will raise another PR.


[packagist] laravel-validation-rules/credit-card

1.0 released

👍🏼👏🏼
Sent from my iPhone

On 24 Sep 2017, at 17:16, Darius Matulionis<EMAIL_ADDRESS>wrote:
1.0 released
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@ssx will you register package in the packagist?

On my todo list for this morning, in around an hour 🙂
Sent from my iPhone

On 27 Sep 2017, at 06:24, Darius Matulionis<EMAIL_ADDRESS>wrote:
@ssx will you register package in the packagist?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Done! https://packagist.org/packages/laravel-validation-rules/credit-card

Had to tidy up composer.json a little and retagged a version to trigger auto push test to packagist. All working well now, and further tags you make will go directly to packagist. 😎


My bug report

email-sample-img-3.pdf

Steps to reproduce

Expected behavior

Actual behavior

Environment data

i have signed it  as of 02/08/2020 with my phone


i can't open cats

Press N in the 3d viewport.

Some of us don't use the Blender defaults, it's on the small context menu (the tiny "<" arrow in the top-right) on the right of the 3D window. For me in 2.81 "Industry Standard" layout "CTRL-]"


v2.ProvisionResponse and provisionSuccessResponseBody should use the same json field names

v2.ProvisionResponse uses json field name operationKey here and provisionSuccessResponseBody uses json field name operation here.
v2.ProvisionResponse could be directly serialized and fed into v2.Client if the json fields b/w client and server match.

yes, you're right. I'm using the client library in a broker implementation.


AURO MIGRATION: Update node to v22

Resolves AlaskaAirlines/auro-templates#6
Summary by Sourcery
Update Node to v22 and configure CI to test against Node 20 and 22.
Enhancements:

Update Node to v22.

CI:

Test against Node 20 and 22.

Tests:

Update test matrix to include Node 22.

:tada: This PR is included in version 4.1.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Material] Fix BottomNavTheme.showSelectedLabels bug

Description
This PR fixes a bug with the BottomNavigationBarThemeData.showSelectedLabels param. Because BottomNavigationBar.showSelectedLables was being set to true, in the constructor, that meant it was not null by default, as the rest of the implementation expected.
Also cleaned up some of the NNBD logic.
Related Issues

https://github.com/flutter/flutter/issues/66738
https://github.com/flutter/flutter/issues/67185

Tests
I added the following tests:

Test that BottomNavTheme.showSelectedLabels: false  and BottomNavTheme.showUnselectedLabels: false works when no widget params provided.
Test that BottomNavTheme.showSelectedLabels: false  and BottomNavTheme.showUnselectedLabels: true works when no widget params provided.
Test that BottomNavTheme.showSelectedLabels: true  and BottomNavTheme.showUnselectedLabels: false works when no widget params provided.

Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

Updating PR to close the related issues automatically.


MPPI

Types of changes

[x] New feature (non-breaking change which adds functionality)

Motivation and Context / Related issue
MPPI implementation with example for HalfCheetah using PETS algorithm structure.

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed and new ones were added.

Thanks for setting this up @freiberg-roman! I'm planning to take a look at this tomorrow (Wednesday), try to run some examples, and give some feedback. I'll keep you posted.


Observation Uncertainty Location

@DhruvaBhagwat23 I've reviewed and merged this to main and deleted the branch.  We generally find that "GitHub flow" pattern of branch->merge->delete works best, where you keep making a new branch from main, adding edits, and then sending the PR (just like you did here).
One advantage of this "feature-branch" approach as opposed to more svn-style branching patterns (e.g. main and dev branches), is that you don't have to always remember to keep resync'ing your branch with other changes made from main quite as often.  Feature-branches are also the dominant pattern these days.


Symbol’s function definition is void: json-serialize

I this error when I try to run copilot-login
Symbol’s function definition is void: json-serialize

M-x version says:
GNU Emacs 28.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.5, cairo version 1.16.0) of 2021-04-04, unofficial emacs-snapshot build: http://emacs.ganneff.de/, git commit dd5ba88afbb63f54603cc632fc55993c04531a85

Your Emacs was built without JSON support. I guess using an official Emacs can solve this problem.
There is a similar problem: https://github.com/org-roam/org-roam-ui/issues/63#issuecomment-899105994

I close the issue since it is not a bug and the thread is not active.


wont compile anymore

`# github.com/gocolly/redisstorage
..\github.com\gocolly\redisstorage\redisstorage.go:43:25: not enough arguments in call to s.Client.cmdable.Ping
have ()
want (context.Context)
..\github.com\gocolly\redisstorage\redisstorage.go:54:20: not enough arguments in call to s.Client.cmdable.Keys
have (string)
want (context.Context, string)
..\github.com\gocolly\redisstorage\redisstorage.go:59:21: not enough arguments in call to s.Client.cmdable.Keys
have (string)
want (context.Context, string)
..\github.com\gocolly\redisstorage\redisstorage.go:66:21: not enough arguments in call to s.Client.cmdable.Del
have ([]string...)
want (context.Context, ...string)
..\github.com\gocolly\redisstorage\redisstorage.go:71:21: not enough arguments in call to s.Client.cmdable.Set
have (string, string, time.Duration)
want (context.Context, string, interface {}, time.Duration)
..\github.com\gocolly\redisstorage\redisstorage.go:76:24: not enough arguments in call to s.Client.cmdable.Get
have (string)
want (context.Context, string)
..\github.com\gocolly\redisstorage\redisstorage.go:96:21: not enough arguments in call to s.Client.cmdable.Set
have (string, string, number)
want (context.Context, string, interface {}, time.Duration)
..\github.com\gocolly\redisstorage\redisstorage.go:109:33: not enough arguments in call to s.Client.cmdable.Get
have (string)
want (context.Context, string)
..\github.com\gocolly\redisstorage\redisstorage.go:123:36: cannot use s.getQueueID() (type string) as type context.Context in argument to s.Client.cmdable.RPush:
string does not implement context.Context (missing Deadline method)
..\github.com\gocolly\redisstorage\redisstorage.go:123:36: cannot use r (type []byte) as type string in argument to s.Client.cmdable.RPush
..\github.com\gocolly\redisstorage\redisstorage.go:123:36: too many errors
Compilation finished with exit code 2
`

Thanks for the report. Seems like redis client has changed over time. Could you work on the fix?

A quick fix could be restore to go-redis in 2018. It works fine for me.
go get github.com/gocolly/redisstorage
cd ~/go/src/github.com/go-redis/redis
git checkout tags/v6.14.2

go run yourcode.go

Reference:
https://stackoverflow.com/questions/24855081/how-do-i-import-a-specific-version-of-a-package-using-go-get
https://github.com/go-redis/redis/releases/tag/v6.14.2


Bug report: only the last "dv.taskList" in the loop shows the corresponding task view

What happened?
With the following dataviewjs code and dataview 0.4.24, only the tasks on the last page are shown, but everything is OK with dataview 0.4.22.
for (let page of dv.pages('"Daily"').sort(p => p.file.name, 'desc')) {
  dv.taskList(page.file.tasks);
}

DQL
No response
JS
for (let page of dv.pages('"Daily"').sort(p => p.file.name, 'desc')) {
  dv.taskList(page.file.tasks);
}

Dataview Version
0.4.24
Obsidian Version
0.13.23
OS
Windows

Fixed for 0.4.25; the task view uses React and was just updating the view each time.


Allow zero values for rolled over benefits

In creating a new membership by rolling over an existing one, when you try to hit submit, it takes you back to the input for "Public instructor training seats rolled from previous."
I'm guessing this is because zero values are not allowed here.  They should be - we will often have memberships where no instructor training seats or workshops are rolled over.  Roll over values will likely be the exception.

Note: this behavior doesn't apply to workshops without admin fee, as their calculations are quite different from training seats.


Update t265_wheel_odometry.py

The configuration should be changed so that the device start streaming the pose data as stated here; then, start the pipeline with new configuration pipe.start(cfg)

Hi,
Thanks for your PR.
The T265 product will be discontinued as of February 2022. Reference .
On the next release the T265 code and exmaples will be removed.
I will close this PR but feel free to use older version of the SDK if you still need it.
Thanks!


Docker Build failure: the url given returns 404

Cannot Build docker image, since the given url in:
docker build -t caffe:cpu https://raw.githubusercontent.com/BVLC/caffe/master/docker/standalone/cpu/Dockerfile
returns 404.
please update a new one to build image on.

Hi,
I am also facing the same issue, Any information on this, please.
Thanks
Mohsin

the following PR seems to be the fix
https://github.com/yahoo/open_nsfw/pull/58/commits/0761435206c9148b97b81eebb31aa8295859d7f2
ho, well, no
after quite a bit of download and setup it fail.
Best regards


export gltf with camera and import it again, camera will split into Camera and Camera_Orientation

Describe the bug
export gltf with camera and import it again, camera will split into Camera and Camera_Orientation
To Reproduce
Steps to reproduce the behavior:

export gltf with option include Cameras
and import the exported gltf to blender again
the camera will split into Camera and Camera_Orientation

Expected behavior
export gltf with camera and import it again, gltf's camera will keep original structure, no matter how many time to export then reimport
Screenshots

Version

OS: Window 10
Blender Version 2.93.5

Hello,
This is a duplicate of #1328
This will be fixed by #1378


Corsair Dark Core not working

Expected Behaviour
The mouse lights should be lighting up
Actual Behaviour
The lights are off
Reproduction steps
Configured the mouse as Corsair M65 and created a light profile. Corsair iCue shows the lights changing the same way Aurora shows, but the actual mouse lights don't turn on.
Frequency
All the time
Aurora Version:
0.7.2
Previously an Issue?
Never used previous versions

Can't fix as per
https://github.com/CorsairOfficial/cue-sdk/issues/8


Option to configure cgroup cleaner path

Description
Changes proposed in this pull request.
Test plan
Outline the test plan used to test this change before merging it.

Fixes #.

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1425",
    "commit-sha": "a39b1d6e98ee996e6788fca80304766a7b3a81b6"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "903",
    "commit-sha": "4b9f6eede18ae35c2fb71e5e732d5d99cc4d0195"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1425",
    "commit-sha": "40a8f4f09823e0168133f64b6321ae5fbee40fbf"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "903",
    "commit-sha": "4b9f6eede18ae35c2fb71e5e732d5d99cc4d0195"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1425",
    "commit-sha": "40a8f4f09823e0168133f64b6321ae5fbee40fbf"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "903",
    "commit-sha": "c0f85d8389393f6ffe56386ed6537fc18a238a23"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1425",
    "commit-sha": "312f4691694b0fab2c8545889902ab04effd742b"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "903",
    "commit-sha": "c0f85d8389393f6ffe56386ed6537fc18a238a23"
  }
]

/build - automatically fired by gogo with following PRs and commit SHAs v1.0.0
[
  {
    "project": "",
    "component": "enforcerd",
    "pr-id": "1425",
    "commit-sha": "2785553b7fea582a171e3832b696e5614b43a76f"
  },
  {
    "project": "",
    "component": "trireme-lib",
    "pr-id": "903",
    "commit-sha": "c0f85d8389393f6ffe56386ed6537fc18a238a23"
  }
]


Clear every frame to black before drawing

AreaManager._tick() is the first function called every frame in Driftwood's drawing process. If there's been a refocusing then AreaManager asks FrameManager to prepare a new frame. This new frame is black. Otherwise, the old frame is used and is not cleared, leaving garbage on-screen if the current draw does not overwrite every pixel.
We need to clear the frame really early in the drawing process, basically before AreaManager.__build_frame() is called since that's where we start copy()ing stuff.
This commit adds a FrameManager tick that is called before AreaManager's tick. All it does is clear the screen.
Fixes #75

I wasn't sure what self.__workspace was used for, specifically, so I just made clear() clear the self.__texture. Clearing either the texture or the workspace had the same effect as right now I think they refer to the same SDL2 texture object.

Just changed it to clear self.__workspace to be consistent with FrameManager.prepare().

Actually this is clearing the screen too often. We need to only clear the screen when we know that AreaManager is going to redraw it again.

Well, I didn't want to have to do this, but looks like AreaManager will be the one to ask for the screen to be cleared. It's the manager that knows when a new frame is going to be drawn for any particular tick. ("par-tick-ular tick?")


How to use the profile

I am trying to use the profile.

I cloned the repository.
Installed in maven local with .\gradlew install

I then run:
grails create-app foo —-profile=me.przepiora.vaadin-grails:web-vaadin8:0.3-SNAPSHOT.
The app seems to be created with default web profile.
Am I missing any step?

Using Grails 3.2.10 in command line

problems where the dashes


RPC   sign_transaction

Use the https://api.eosnewyork.io node. Call the rpc operation of the main network involving the wallet, such as sign_transaction. How to deal with
https://api.eosnewyork.io/v1/wallet/sign_transaction
return
  {
   "message": "PARSE_ERROR",
   "code": 400
}
My own node synchronization is too slow to catch up with the main network

What's your payload? Seems something is wrong with your payload

If I don't sync the main network node. Whether you can complete the transaction using https://api.eosnewyork.io.
The RPC about the wallet seems to have not been accessed.
[
{
"ref_block_num": 7321961,
"ref_block_prefix":<PHONE_NUMBER>,
"expiration": "2018-07-23T09:38:05.000",
"scope": [
"#######",
"#######"
],
"read_scope": [],
"actions": [
{
"account": "@@@@@",
"name": "transfer",
"authorization": [
{
"actor": "#######",
"permission": "active"
}
],
"data": "30209d4637e48c8620209d4637e48c86e8030001111110000446544300000000057366737373"
}
],
"signatures": []
},
[
"EOS8FDdchw68CrrdWCmxxxxxxxxxxxxxx"
],
""
]

I just realize you are calling the wallet API remotely, you should only call the wallet API to a local endpoint.


[NDMII-3058] Add synchronous rDNS lookup to rdnsquerier component

What does this PR do?
This PR modifies the reverse DNS querier component to allow for synchronous calls.
Motivation
While this component was originally written with Netflow in mind, hence the asynchronous implementation, having a reverse DNS lookup with caching is also desired for 2 other use cases:

SNMP integration to enrich devices with hostname
Network Path to enrich private IPs with reverse DNS information

Describe how to test/QA your changes
Ensure that the asynchronous call still works and Netflow reverse DNS data is still being fetched properly. Changes to that were limited to renaming the function call.
Currently there's not a good way to QA the synchronous endpoint as this is just the addition of the synchronous call. Separate PRs will be created that actually use this code and impact the functionality of the agent.
Possible Drawbacks / Trade-offs
This isn't a perfect implementation. With more time, I would investigate refactoring the cache implementation to be more friendly to a synchronous approach. This would allow us to avoid having all of the channels to receive results.
Additional Notes

/merge


gcm: rename Client method receiver to c

At first, Sorry for nit pull request.
Rename Client method receiver to c instead of s.
I saw gcm package, it's forked from alexjlockwood/gcm. That's used Sender type but now mercari/gaurun uses Client type name.
So I think rename to c is more readable.
If mercari have own coding policy, please ignore and close it.
Signed CLA.
Thanks.

Merged. Thanks.

@cubicdaiya You too.


[Workflow] Refresh edit UI

This PR adds UI changes to the edit page (and minor improvements to the homepage) needed for Workflow
Notes:

this includes the changes from #6151 (to avoid duplicating work).
the PR builds on #6084 and so it targets the audit log branch to reduce the cognitive load on review

Screenshots/screencast coming shortly

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing)
Does the code comply with the style guide? (Run make lint from the Wagtail root)
For Python changes: Have you added tests to cover the new/fixed behaviour?
For front-end changes: Did you test on all of Wagtail’s supported browsers? Please list the exact versions you tested.
For new features: Has the documentation been updated accordingly?

Merged into feature/workflow in a4b35dc600d1f0836b5a8b095cf3fa0c4760ef35.


Relative links added to protos causing doc tests to fail

Links inside protos should be absolute URLs, so that they're appropriately linked to in generated reference documents. #825 introduces relative links, which causes doc tests to fail.

This looks like it was fixed in cl/440481666, and shows up as fixed here: https://github.com/googleapis/nodejs-speech/blob/main/protos/google/cloud/speech/v1p1beta1/cloud_speech_adaptation.proto Closing.


Undefined array key "honey_time"

Hi,
I got some error when integrating with livewire.
ErrorException Undefined array key "honey_time" http://<IP_ADDRESS>:8000/
I'm following installation step with default config
<form wire:submit.prevent="store">
    @csrf
    <input type="text" class="block text-sm py-3 px-4" wire:model="text"/>
    <x-honey/>
    <button type="submit" class="py-3 w-64">Submit</button>
</form>

My routes
Route::get('/form', \App\Http\Livewire\Form::class,)->middleware(['honey'])->name('form');
What's wrong here?

Make sure to use the middleware on a POST route and not GET.

Big thanks @kiritokatklian


Report ixmp.Platform.units() in ixmp documentation

Wondering how to obtain a full list of units from MESSAGEix I found that a docstring for the method .units() of ixmp.Platform was missing and therefore not reported in the documentation.

$ git checkout docu-ixmp.Platfrom.units()
bash: syntax error near unexpected token `('

In the future, please just use lower-case characters plus '-' and/or '/' in branch names!