Getting Timeout error in Rasa 2.6.0

Rasa version:
2.6.0
Rasa SDK version:
2.6.0
Python version:
Python 3.8
Operating system (windows, osx, ...):
Windows 10
Error (including full traceback):
I am getting this error with rasa 2.6.0 version and Python 3.8
2021-05-12 08:10:12 ERROR    asyncio  - Task exception was never retrieved
future: <Task finished name='Task-2' coro=<configure_app.<locals>.run_cmdline_io() done, defined at c:\users\sures\rasa-for-beginners\env\lib\site-packages\rasa\core\run.py:131> exception=TimeoutError()>
Traceback (most recent call last):
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\rasa\core\run.py", line 135, in run_cmdline_io
    await console.record_messages(
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\rasa\core\channels\console.py", line 182, in record_messages
    async for response in bot_responses:
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\rasa\core\channels\console.py", line 137, in send_message_receive_stream
    async for line in resp.content:
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\aiohttp\streams.py", line 39, in __anext__
    rv = await self.read_func()
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\aiohttp\streams.py", line 338, in readline
    await self._wait("readline")
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\aiohttp\streams.py", line 306, in _wait
    await waiter
  File "c:\users\sures\rasa-for-beginners\env\lib\site-packages\aiohttp\helpers.py", line 656, in __exit__
    raise asyncio.TimeoutError from None
asyncio.exceptions.TimeoutError

Command or request that led to error:
when i do sent a message to bot like "hi"
rasa shell

Thanks for raising this issue, @samsucik will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

@samsucik  @sara-tagger  I have solved the error thank you.

how to solve this problem?https://github.com/sudhir512kj

@ailungoal could you, please, create a new issue where you precisely describe your situation? Thanks a lot!


More examples around Publishing your own CloudEvents

What content needs to be created or modified?

So - the json payload in the CLI example above is not a CloudEvent payload.
What do you mean with the text

If you want to use your own CloudEvent, make sure to specify the datacontenttype as application/cloudevents+json

Let's say I want to boil the ocean to maintain DAPR compat and bin ApplicationProperties in Azure ServiceBus and instead start publishing CloudEvents with Extensionattributes so that I can consume those in DAPR instead.
How/what do I do then?
Describe the solution you'd like

I would like a paragraph on how you publish a CloudEvents payload that can be consumed by a subscriber including ExtensionAttributes so that I can know how to publish cloudevents properly using DAPR.
Where should the new material be placed?

It could replace the bit I screenshotted.
The associated pull request from dapr/dapr, dapr/components-contrib, or other Dapr code repos

Additional context

/assign

This has been resolved. If you feel this needs more work, feel free to reopen or open a new issue.


add Chinese version of Example_Delay.md

Make sure set the target branch to develop
What is the purpose of the change
XXXXX
Brief changelog
XX
Verifying this change
XXXX
Follow this checklist to help us incorporate your contribution quickly and easily. Notice, it would be helpful if you could finish the following 5 checklist(the last one is not necessary)before request the community to review your PR.

[x] Make sure there is a Github issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a Github issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[x] Format the pull request title like [ISSUE #123] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[x] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[x] Write necessary unit-test(over 80% coverage) to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[x] Run mvn -B clean apache-rat:check findbugs:findbugs checkstyle:checkstyle to make sure basic checks pass. Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Coverage decreased (-0.1%) to 53.944% when pulling 278d3285bd7c5d2563a98533a0bac593504a8576 on Cu-Cu:master into df1d93fc8859377b92ba87c6947911281656f355 on apache:master.

Codecov Report

Merging #3036 (278d328) into master (df1d93f) will decrease coverage by 0.29%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #3036      +/-   ##
============================================
- Coverage     47.97%   47.67%   -0.30%
+ Complexity     4569     4539      -30
============================================
  Files           552      552
  Lines         36628    36628
  Branches       4844     4844
============================================
- Hits          17572    17463     -109
- Misses        16832    16933     +101
- Partials       2224     2232       +8

Impacted Files
Coverage Δ

.../broker/subscription/SubscriptionGroupManager.java
54.11% <0.00%> (-16.48%)
:arrow_down:

...rg/apache/rocketmq/common/stats/StatsSnapshot.java
84.61% <0.00%> (-15.39%)
:arrow_down:

.../apache/rocketmq/common/stats/MomentStatsItem.java
38.09% <0.00%> (-9.53%)
:arrow_down:

...ache/rocketmq/common/stats/MomentStatsItemSet.java
43.47% <0.00%> (-8.70%)
:arrow_down:

...org/apache/rocketmq/store/ha/WaitNotifyObject.java
71.15% <0.00%> (-7.70%)
:arrow_down:

...a/org/apache/rocketmq/logging/inner/SysLogger.java
28.57% <0.00%> (-5.72%)
:arrow_down:

...apache/rocketmq/remoting/netty/ResponseFuture.java
85.00% <0.00%> (-5.00%)
:arrow_down:

...ketmq/client/impl/consumer/PullMessageService.java
75.55% <0.00%> (-4.45%)
:arrow_down:

...java/org/apache/rocketmq/logging/inner/Logger.java
51.67% <0.00%> (-4.31%)
:arrow_down:

...va/org/apache/rocketmq/common/stats/StatsItem.java
50.00% <0.00%> (-4.17%)
:arrow_down:

... and 22 more

Continue to review full report at Codecov.

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


Organise documentation

I think it would be better to make README shorter, demonstrating only basic usage of Dip and list of available features, moving their description to separate md files (or wiki pages?)

:+1:
That's what I did on OHHTTPStubs, moving away all the usage examples in a dedicated wiki page as the README was starting to get too big.
You can inspire you from the same idea.

Just be sure the pod doesn't lower its README score too much on CocoaPods (see Dip's quality index page here)
CocoaPods's quality index is explained here but long story short, to have those extra points and be considered a "great README" is is expected to have a score > 75 on http://scoreme.report/ (we're at 100 right now so I we're really :+1: on that front :simple_smile: but reducing the file too much lower it)


Support switching database cluster between MongoDB and CockroachDB (via R2DBC)

In fact, turms used CockroachDB as the database of turms servers at the stage of internal development, but CockroachDB is abandoned due to the JDBC driver (blocking calls) in Java.
Although R2DBC project is still experimental, it's worthwhile to take it with CockroachDB as an alternative database of turms servers in the future.

Hi PM at Cockroach Labs here. What problems are you having with CockroachDB and the JDBC driver?

Thanks for your assistance and the good job Cockroach Labs has done, which makes my life much more easier compared to the traditional architecture for DB servers (relational database servers + middleware).
Expected:
(This is not the reason we didn't use CockroachDB, but may help make the ecosystem of CockroachDB better and more appealing)
CockroachDB better have some examples or posts that demonstrate how to connect to CockroachDB servers via the non-blocking driver https://github.com/r2dbc/r2dbc-postgresql (which supported by Spring framework) and its functionality and stability for Java developers.
Actual:
we didn't use CockroachDB + JDBC because of JDBC has a worse performance and R2DBC is a good alternative but not mature enough to push us to integrate it with CockroachDB for now, and there is no a post demonstrating whether CockroachDB works well via R2DBC (but we will try to integrate them into this project with the developentment of R2DBC).
Motivation:
For this project, CockroachDB + JDBC driver is hard to accept.
Because this project always try to improve throughputs of user requests as more as possible, while JDBC is a blocking driver which makes the calls to DB blocking and reduces throughputs significantly (bucket effect), and that's why we don't adopt JDBC.
And, CockroachDB doesn't has its own driver (BTW MongoDB has its own non-blocking drivers, this's why we are using it now though its use cases, in fact, are not that suitable for this project as CockroachDB does) and supports the drivers for Postgres, but most of them are blocking drivers (backed by JDBC) and I know there are two existing projects (r2dbc-postgresql, vertx-sql-client) supporting non-blocking drivers for Java developers which can be used for CockroachDB, but R2DBC is not ready for production for now but grows fast (that's why I tagged this issue "experimental").
If CockroachDB has its own example for connecting DB via R2DBC, it is much appreciating and exciting for Java developers.
And I will try to integrate CockroachDB via R2DBC into this project later.

@rafi curious what you think about the above?


cut new @xstate/react release?

PR #769 fixed a nasty bug in my games, but the latest 0.8.0 doesn't have it. I'd love to use an official release. Thx!

<EMAIL_ADDRESS>is all yours!

YES! There she is! Thx @davidkpiano


Remove newline between fields in log

This PR removes a newline in a log that outputs the request ID and offset. Logging on the same line makes it easier to search for an offset or a request ID in the logs to correlate the lifecycle of a request (when received, when received on the consumer side, final response sent etc.)
So, instead of:
[2022-02-28T16:36:57.787Z]  INFO <-- POST /gateways/simplestorage [202]:
{"sent":true,"id":"942308fe-2fc9-435c-6690-6d249c563fb2","msg":"zzaaaaaaa-zzbbbbbbb-requests:0:71338"}

we will log:
[2022-02-28T16:36:57.787Z]  INFO <-- POST /gateways/simplestorage [202]: {"sent":true,"id":"942308fe-2fc9-435c-6690-6d249c563fb2","msg":"zzaaaaaaa-zzbbbbbbb-requests:0:71338"}

Signed-off-by: Vinod Damle<EMAIL_ADDRESS>

Codecov Report

Merging #204 (3a54728) into main (e5428b4) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 3a54728 differs from pull request most recent head a7615c5. Consider uploading reports for the commit a7615c5 to get more accurate results

@@           Coverage Diff           @@
##             main     #204   +/-   ##
=======================================
  Coverage   97.20%   97.20%
=======================================
  Files          58       58
  Lines        6902     6902
=======================================
  Hits         6709     6709
  Misses        147      147
  Partials       46       46

Continue to review full report at Codecov.

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


Using Thread.setDefaultUncaughtExceptionHandler is not thread safe

The ConditionAwaiter class registers itself as a Java process global uncaught exception to catch possible unhandled exceptions. This introduces an thread safity issue when Awaitility methods are running in parallel on multiple threads.
Since version 4.0.2 it causes a memory leak through the ConditionAwaiter.originalUncaughtExceptionHandler field when saving the original handler that has just been updated to an ConditionAwaiter instance set by another thread. This is how we have noticed the problem.
A quick fix for pollInSameThread mode could be to use a thread specific uncaught exception handler, that is Thread.currentThread().setUncaughtExceptionHandler,  instead of the global one.

@agavrilov76 Can you check the following commit, please? Do these changes fix this issue? https://github.com/grofoli/awaitility/commit/805cd6d7e1787dc20986cf0849cd59f78927e87a
If yes, I would create a pull request, so it can be included in the next release.

@johanhaleby What do you think about this topic and about the changes in the commit I linked?


Flaky Tests: Suite 'Resolving Environment Variables when Debugging'

Tests have been disabled and need investigation and correction:
Hypothesis is that the path separator char being compared is incorrect due to the Windows \\ vs Bash /.

Confirm paths get appended correctly when using json variables and launched in external terminal
https://github.com/Microsoft/vscode-python/blob/8581d77b07d1854ce4a390ec61ccf2081cf13d09/src/test/debugger/envVars.test.ts#L196
Confirm paths get appended correctly when using json variables and launched in integrated terminal
https://github.com/Microsoft/vscode-python/blob/8581d77b07d1854ce4a390ec61ccf2081cf13d09/src/test/debugger/envVars.test.ts#L205
Confirm paths get appended correctly when using json variables and launched in debug console
https://github.com/Microsoft/vscode-python/blob/8581d77b07d1854ce4a390ec61ccf2081cf13d09/src/test/debugger/envVars.test.ts#L205

Closing as stale.


DHCP timeout will cause software interface deleted in libnmstate.show().

The NM will delete the device if DHCP timeout on software interface(like bond).
nmstate is using NM.Client.get_devices() for the interface list.

https://bugzilla.redhat.com/show_bug.cgi?id=1783891

@ffmancera @tyll @EdDev I recall you guys talk about this issue in a meeting. Can anyone of you input anything valuable here before I consult with NM guys?

This is what we do in VDSM to make sure the devices are not deleted:
https://github.com/oVirt/vdsm/blob/2ce23206ab39f2a6a8f6d236fb44200fd950268d/static/etc/NetworkManager/conf.d/vdsm.conf#L12
We need to add this in nmstate as this seems to make more sense as the default.
There is however another issue with RA infinite timeout, which NM does not support yet and we need to probably use sysfs to set.

Could we closed this? @cathay4t

Fix has been included in master and v0.2.6.


BUG: documentation of scipy.stats.truncnorm could be clearer

Describe your issue.
In the notes of the distribution, it states:

The standard form of this distribution is a standard normal truncated to the range [a, b], where a and b are user-provided shape parameters. The parameter loc shifts the mean of the underlying normal distribution, and scale controls the standard deviation of the underlying normal, but a and b are still defined with respect to the standard normal. If myclip_a and myclip_b are clip values defined with respect to a shifted and scaled normal, they can be converted the required form according to:

I think the phrasing 'underlying normal' (particularly with respect to the standard deviation) may be confusing for some because it implies that the parameter has no impact on the truncation of the normal - that is, it happens "before the normal distribution is truncated". However, the scale parameter does effect where the truncation limits are - that is, changing the parameter from 1 to 2 will double the width of the truncated normal. For the same reason, how to define a and b seems a little unclear.
I'd like to suggest this alternative phrasing, as a drop-in replacement for the above:

This distribution is the normal distribution centred on loc, with standard deviation scale, and clipped at a, b standard deviations to the left, right (respectively) from loc, with the height calculated such that probability summed over the sample space is 1. Note that the standard deviation of the standard normal distribution is 1.0, the default. If myclip_a and myclip_b are clip values in the sample space (as opposed to the number of standard deviations) then they can be converted to the required form according to:

Reproducing Code Example
import scipy.stats
import numpy as np
import matplotlib.pyplot as put

x = np.linspace(-5, 5, num=201)

tn = scipy.stats.truncnorm.pdf(x, -2, 2)
plt.plot(x, tn)

tn2 = scipy.stats.truncnorm.pdf(x, -2, 2, scale=2)
plt.plot(x, tn2)

tn3 = scipy.stats.truncnorm.pdf(x, -1, 1, scale=2)
plt.plot(x, tn3)

Error message
N/A

SciPy/NumPy/Python version information
1.5.1 1.18.5 sys.version_info(major=3, minor=7, micro=7, releaselevel='final', serial=0)

We did some work on that message, but I agree - we still didn't get it right.
I think your phrasing is great - I really like that it's put in terms of standard deviations, since I think is something newcomers will understand better than "scale". I'd just trim some of the parts I think can be left unstated.

This distribution is the normal distribution centered on loc (default 0), with standard deviation scale (default 1), and clipped at a, b standard deviations to the left, right (respectively) from loc. with the height calculated such that probability summed over the sample space is 1. Note that the standard deviation of the standard normal distribution is 1.0, the default. If myclip_a and myclip_b are clip values in the sample space (as opposed to the number of standard deviations) then they can be converted to the required form according to:

I think the bit about height/probability is to be assumed. The same can be said of any probability distribution.
Also, the default values of loc and scale do appear at the bottom of the page in the method definitions. If we're going to include them up here, I think that it makes to include both (rather than just scale). For concision, I'd suggest doing it in the first sentence, where the quantities are first mentioned.
Would you like to submit a PR?
Just thought I'd include the plots suggested above for reviewer convenience:
import scipy.stats
import numpy as np
import matplotlib.pyplot as plt

x = np.linspace(-5, 5, num=201)

tn = scipy.stats.truncnorm.pdf(x, -1, 1)
plt.plot(x, tn)

tn2 = scipy.stats.truncnorm.pdf(x, -1, 1, scale=2)
plt.plot(x, tn2)

tn3 = scipy.stats.truncnorm.pdf(x, -1, 1, loc=2, scale=2)
plt.plot(x, tn3)

Yes, will do.


I've implemented some features that might be helpful

I did a bit of tinkering on this crate for my project. The implementation is janky, but I've added some features that make it a lot more convenient.
Maybe you can take these ideas and implement them in a better way.
https://github.com/KPidS/tonbun/tree/main/src-tauri/crates/discord-rich-presence

clear_activity method on DiscordIpc trait. Basically I implemented solution from #13 into the crate.

https://github.com/KPidS/tonbun/blob/main/src-tauri/crates/discord-rich-presence/src/discord_ipc.rs#L212

#14 connected field on the DiscordIpcClient now actually works. Not sure if it's the right way to implement it though.

set_activity_safe and clear_activity_safe.

https://github.com/KPidS/tonbun/blob/main/src-tauri/crates/discord-rich-presence/src/discord_ipc.rs#L212
Returns Ok If connectedis set to false, meaning the client isn't supposed to be connected.
If it's true, then tries to set the activity. If set_activity returns Err it will try to reconnect the client, and returns Err only if it failed to reconnect or failed to set_activity after reconnecting.

DiscordIpcClientMutex struct. Wraps around DiscordIpcClient and has enable and disable functions.

https://github.com/KPidS/tonbun/blob/main/src-tauri/crates/discord-rich-presence/src/discord_ipc_mutex.rs
enable will start an interval that is constantly going to try to connect to the client, so you don't have to worry about manually connecting it ever.
This is definitely WIP at the moment, since I need to implement a proper way to stop the interval thread when you disable it.
Right now if you spam enable disable you can launch multiple threads at the same time.

Thank you for these, please make a PR so @sardonicism-04 can merge it into the main branch

Thank you for these, please make a PR so @sardonicism-04 can merge it into the main branch

Basically, I wanted to ask if these features are wanted, and if they are ready to be made into the PR.
Features 1 and 2 are likely are, so yeah, I'll try to polish them, add documentation, and make them into the PR.

1 and 2 look great, will happily merge that PR :)
3 looks like a bit of an unnecessary abstraction IMO
4 sounds interesting. I'll have to think about if something like that is in scope of the project, but would probably not merge it at the moment

Yeah, I agree. 3 is a bit too specific for my desires and 4 is definitely not ready to be merged.
I'll make a PR with 1 and 2 in couple of days. Thanks for the reply.


Confluent-kafka-dotnet - Consumer occasionally dies

Description
We are using Confluent.Kafka 1.7.0. Attached is our code.
We are listening to topic; which is not very chatty. Sometimes for days we don't get any messages on that topic. So we are not processing million of messages.
Very occasionally our consumer just dies with ConsumeException; as practice we are also forfeiting consuming messages and we throw exception as well.
As we understand from documentation this line will be blocking call and it will keep polling internally; and it will return ConsumerResult as message is available.  - _consumer.Value.Consume(stoppingToken);
Code :
```
public async Task<IEsmeEvent<T>> ConsumeAsync<T>(CancellationToken stoppingToken = default)
        where T : class
    {
        ConsumeResult<string, string> consumerResult = null;

        try
        {
            consumerResult = await Task.FromResult(_consumer.Value.Consume(stoppingToken)).ConfigureAwait(false);
            _logger.Debug(
                $"Consumed message '{consumerResult.Message.Value}' from topic {consumerResult.Topic}, partition {consumerResult.Partition}, offset {consumerResult.Offset}");
            var @event = _eventFactory.Create<T>(consumerResult.Topic, consumerResult.Message.Value, consumerResult.Message.Key, consumerResult.Offset.Value);
            _consumer.Value.StoreOffset(consumerResult);
            return @event;
        }
        catch (ConsumeException ex) //This exception get's thrown.
        {
            _logger.Error(
                $"Consume failed with [ErrorCode={ex.Error.Code}] [Reason={ex.Error.Reason} [OffSet={ex.Error.Code}]] {ex.ConsumerRecord.Message.}");
            throw new EsmeConsumeException($"Error consuming on topic [{_consumerOptions.Topic}].", ex);
        }
    }

    private IConsumer<string, string> CreateConsumer(string topic)
    {
        var clientConfig = _clientOptions.Value.ToClientConfig();
        var config = new ConsumerConfig(clientConfig)
        {
            ClientId = _clientOptions.Value.ClientId,
            GroupId = _consumerOptions.GroupId,
            SessionTimeoutMs = _clientOptions.Value.BrokerSessionTimeoutMs == 0
                ? EsmeConsumerClientOptions.DefaultBrokerSessionTimeoutMs
                : _clientOptions.Value.BrokerSessionTimeoutMs,
            EnableAutoCommit = true,
            EnableAutoOffsetStore = false
        };

        ConsumerBuilder<string, string> builder;
        builder = new ConsumerBuilder<string, string>(config);

        var consumer = builder.Build();
        consumer.Subscribe(topic);
        return consumer;
    }

Configuration :

   Client: {
      Server: xxxxx,
      ClientId: Local.Local.Loss,
      ApiKey: xxxxx,
      Secret: xxxx,
      RedundancyStrategy: Full,

      BrokerSessionTimeoutMs: 15000,
      ConsumerDebugSettings: consumer,cgrp,topic,fetch,

    }

Questions :
I do see in Debug Log Consumer leaving at 18:16 in Debug Log; but it seems librdrakafka keeps running internally. And we are throwing exception out.

What would be correct way to catch this and recover from this error.
Also is this regular (may be cleanup) behavior of client  ?

Log from our Application :
2022-10-03 18:19:54,815 ERROR Ag.Esme.Kafka.KafkaConsumer: Consume failed with [ErrorCode=Local_MaxPollExceeded] [Reason=Local: Maximum application poll interval (max.poll.interval.ms) exceeded [OffSet=Local_MaxPollExceeded]]
2022-10-03 18:19:54,894 ERROR Ag.Esme.EventStream.EsmeConsumerProcessor: The client [TreasuryClaimEventHandler] has encountered an unrecoverable failure. Error: Ag.Esme.Abstractions.EventStream.EsmeConsumeException: Error consuming on topic [LossTopic]. ---> Confluent.Kafka.ConsumeException: Local: Maximum application poll interval (max.poll.interval.ms) exceeded
at Confluent.Kafka.Consumer2.Consume(Int32 millisecondsTimeout)    at Confluent.Kafka.Consumer2.Consume(CancellationToken cancellationToken)
at Ag.Esme.Kafka.KafkaConsumer.d__91.MoveNext()    --- End of inner exception stack trace ---    at Ag.Esme.Kafka.KafkaConsumer.<ConsumeAsync>d__91.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Ag.Esme.EventStream.EsmeConsumerProcessor`1.d__12.MoveNext()
Debug Log : https://github.com/confluentinc/confluent-kafka-dotnet/files/9715877/DebugLog.txt
How to reproduce
We are not able to reproduce consistently; it happens very occasionally. We have attached Application Log and Debug Log.
Checklist
Please provide the following information:

[ Attached Code snippet ] A complete (i.e. we can run it), minimal program demonstrating the problem. No need to supply a project file.
[ 1.7.0 ] Confluent.Kafka nuget version.
[ We are using Confluent Cloud ] Apache Kafka version.
[ Attached ] Client configuration.
[Windows ] Operating system.
[ Attached ] Provide logs -
DebugLog.txt

rl) "debug" : "..." as necessary in configuration).

[We are using Confluent Cloud ] Provide broker log excerpts.
[ Yes ] Critical issue; affecting Production

Maximum application poll interval

this implies the time between calls to Consume was longer than MaxPollTimeoutMs, which is 5 minutes by default. Can your processing of each message take longer than this?

No; it is not taking longer than 5 minutes. When this happened there were no messages to Consume. You can check in Debug Log; it does not show any messages being consumed at all. This has been mystery for us.
Is it possible that when _consumer.Consme() is called which internally uses libdrkafka; that one took longer time or some internal thread got haywire ?

Also messege in debug log says this :

2022-10-03 18:19:54,815 DEBUG Ag.Esme.Kafka.KafkaConsumer: ClientId:Dev.AppBatchDev.LossCalculator#consumer-3 Level:Warning Facility:MAXPOLL Message: [thrd:main]: Application maximum poll interval (300000ms) exceeded by **1996859793ms** (adjust max.poll.interval.ms for long-running message processing): leaving group.
1996859793ms is unusually long time.

If Consumers leaves the group; does libdrakafka client tries to reconnect again or it stops operating further ?

Thanks

I don't mind upgrading; but is it known problem in 1.7 ? I don't have consistent way to reproduce this bug; so not sure even after upgrading it will fix it.

there are significant fixes to the consumer post 1.7 which may be related, though this issue specifically is not familiar to me.

If it helps - many times we don't get messages for days on this topic. If topic is not getting messages for long period of time (sometimes several days consecutively); is there any logic in broker or in client where it will force to leave the group and it will generate ConsumeException ?

a possible work around would be to dispose and re-create the consumer periodically (say every hour).

you could also assign to the topic partition(s) directly - since your throughput is so low you don't have any need for a consumer group.

Hello, @mhowlett.
We're facing exactly the same error mentioned in this issue & also in https://github.com/confluentinc/confluent-kafka-dotnet/issues/1228. We are using latest confluent kafka (1.9.3) and our apps in production just randomly stuck from time to time. We have N pods of a service deployed to k8s and working with same consumerGroup. After some period of time, suddenly one of the pods gets stuck in .Consume(cancellationToken) method.

From this picture we can see that we have a log right before .Consume(cancellationToken) logged at 19:04:40.
After 12s we got following error:
2022-11-17T21:04:52+02:00 %4|1668711892.043|MAXPOLL|rdkafka#consumer-6| [thrd:main]: Application maximum poll interval (10000ms) exceeded by 247ms (adjust max.poll.interval.ms for long-running message processing): leaving group
Our max.poll.interval.ms is set to 10s. So after that time we suddenly got the poll error.
Here is a look at our code including the attached log.

So, we do reach that point, our cancellationToken has no cancellation requested, but the consumer for some reason doesn't poll at all. According to the summary of the consume method, it's supposed to poll until it receives a message:

Could you please advice on how to fix this? The worst part is this error from above cannot be caught in try/catch, therefore, we cannot just rebuild & re-subscribe our consumer.

@mshahins This should not be considered as a fatal error. One the subsequent Consume() call the consumer will join the group and will resume the consumption.
@Plotso Can you provide debug logs and your consumer config?

@anchitj - Hi I want to delete this issue permanently. I don't have the ability to delete this issue. As an owner of this repo can you please delete this issue? Thanks

Hi @mshahins, Did your issue for resolved? If yes it will help others the solution


Cannot read property 'APPLICATION_PASSWORD' of undefined

After using this package, my jest test is failing with the above error. I did mock for react-native-keychain as well as added @haskkor to transformIgnorePatterns which solves other errors occurred but I can't solve the above problem.
Edit:
My react-native-keychain mock:
export default {
  setGenericPassword: jest.fn(),
  getGenericPassword: jest.fn(),
  resetGenericPassword: jest.fn(),
}

Fixed. Turns out I should create mock for this library instead of react-native-keychain.
For those who might find this useful in the future:

Create @haskkor folder under __mocks__
Create react-native-pincode.js in @haskkor folder
Use my below mock

My final mock:
const keychainMock = {
  APPLICATION_PASSWORD: 'MOCK_APPLICATION_PASSWORD',
}
export default keychainMock


Allow pages to be written in other languages and translate using some translation service.

How about this: interface itself would be generated via sinatra-r18n (i18n) and each hike would have a "language" property. When viewing the site in language X, that language hikes would show in search and discover.

That sounds like the right behavior to me when hike.io gets more content (although implementation wise would probably use Angular - https://docs.angularjs.org/guide/i18n)
Currently though, there are only a couple of hikes written in anything other than English. So switching to another language would be completely devoid of content.

I didn't know Angular could i18n. Great!
Just a thought to add: I hike in Japan. Many signs on trails are in Japanese, often pretty complex characters with uncommon pronunciation that even locals can't read. If I see a hike guide in English, I still need the Japanese spelling to find my way, if only to visually recognize them on a sign.
I have some GPX I want to upload, will put Japanese names together with romanized in the text.


Docs » Tutorials » Integrating a third-party application - Improvement Part 1

Description
I am using OSX El Captan operating system and when I entered:
pip install aldryn-newsblog

I get the following error:

How-to-Fix
In the documents webpage, may you please add a pre-requsite text or something explaining that if you are using OSX that you need to run the following commands before running the pip install:
brew install libxml2
xcode-select --install

Once the user enteres those commands and runs the pip install, everything installs smoothly. Of course you don't have to make this improvement, but it's best we provide the users a stressless experience when following the documentation.
Thanks!

On reconsideration, I am not convinced it's appropriate to mention libraries such as libxml2, or give directions on installing them. There are too many such non-Python libraries, and too many ways to install them, and we can't cover them all.
If they are not installed, the user will get be informed by their system, and it will be up to them to deal with.
@yakky @FinalAngel your thoughts?

I agree, listing specific installation steps (in this example osx) opens the question to add the remaining instructions for windows or linux as well. The prerequisite is to have a proper setup on your computer before you begin.
For the case at divio we use https://github.com/divio/osx-bootstrap for the automated setup on osx (which sets up xcode or libxml2) but that might differ from company to company.
so @evildmp :-1: except for adding a note on "please make sure your system is properly configured" if not already so.


Scala Hadoop Shred: support shredding self-describing ND-JSONs

So we have a specific landing area for ND-JSONs, probably output by extra_steps, and Hadoop Shred will read these as well as the Snowplow enriched events.
Obviously it will validate them etc, then write them out to the common path.
TBC: what do we do on an entity clash: e.g. your enriched events contain com.acme/sessions and your extra_jobs' ND-JSON also writes out com.acme/sessions. Referring to part-000 file clashes.

Let's close this


Feature: Trending Products Carousel

Objective
What: Trending Products Carousel on Product Page
Why: To show trending product recommendations inside a product page.
How: Using the Algolia Recommend TrendingItems, making it a configurable feature on the product page.
Usage: shouldHaveTrendingProducts in /config/featuresConfig
Type

[ ] Bug Fix
[x] New Feature
[ ] Performance Tweaks
[ ] Style Tweaks
[ ] Code Refactoring
[ ] Documentation
[ ] Tests

Tested
Outline the approach you've taken to test the change
Tested on localhost to see the feature in the product page when it is set to true and false.
Documented

[x] Have you documented in changed file using comments
[x] Have you added instructions to the README if needed?

@diegolarraz why product details page, why not homepage?

You'll also want to check on this build error @diegolarraz "Error: 'TrendingItems' is not exported by<EMAIL_ADDRESS>imported by src/pages/HomePage.jsx"


bug(language-server): invalid placement of diagnostics when original item is replaced

Bug Report
Cairo version:
2.7.0-rc.3
Current behavior:
When a plugin generate code by replacing the original item with a new rewritten node, the diagnostics are well generated by the compiler, but the language server doesn't show it correctly in the editor panel.

As seen in the image, the invalid statement is correctly seen by the compiler and mappings look correct, but the language server doesn't display it correctly on the editor panel.
Also, clicking on the error in PROBLEMS tag redirects to a file that actually contains the contract code expanded after compiler plugins passe.

Interestingly, the diagnostics generated by the plugin itself are correctly mapped as shown in the image below:

Expected behavior:
The diagnostics generated by the compiler, inside a plugin code, must be shown correctly on the editor panel.
Also, the go to definition is not working in this situation (for any item).
Steps to reproduce:
An MRE is set here: https://github.com/glihm/cairo_plugin_demo
With:

details in the README to setup VSCode and compiled extension.
custom compiler.
custom plugin.
custom language server using the tricks to start it.

Related code:
Not sure of the exact location in the lib.rs where the problem can be. The mappings are correctly shown in the PROBLEMS tab, with correct lines on the file edited by the user.
Also, the starknet plugin only replaced the original item to actually remove it. But most of the time, the original item is not removed and only additional code is added.
Other information:
We've faced this in Dojo, and the current MRE only uses the minimal code to reproduce the problem. Also the custom compiler is here to output the expanded source code for easier debugging.

Thanks for the work on this @Arcticae! However, it seems that the proposed PR is not actually fixing the issue. Currently tested with 2.8.4 as before we had some compiler incompatibility that prevented the testing.
To reproduce:

Clone https://github.com/dojoengine/dojo-core on the branch feat/cairo-2.8.4.
Build the language server: cargo build -r --bin dojo-language-server.
Open lib.cairo inside examples/dojo_simple, and you'll see that the diagnostics are still not showing correctly when using the LS.

Would be happy to help with some pointers as it's crucial for Dojo users to have LS fully functional. 👍

discussed this offline; the fix will land in Cairo 2.9


Adding tests on appveyor

Ping @GreenSuslik have you tested your patch? Does it work for you?

@Nyholm Yep it's work, basename return bad name

Yep it's work, basename return bad name

But so does pathname... I cannot write tests that confirms the bug and that pathname fixes... However, I rewrote your PR into this PR. Does this PR also work for you?

Yes, PR  #20 work for me


Native physical web support in Android

Can anyone provide any information regarding when physical web will be supported natively in android. When I read around people are speculating it might release via Chrome browser, Play store or it can even be released along android M. But after android M launch I didn't find any further update. I also found that  Opera R&D had released a labs build of Opera for Android (APK, 30 MB) with URL beacon detection. But if we need to put out a product in physical web in production how long should the developers need to wait such that physical web would be available in android natively.

As there are changes to Android happening to make the scanning more efficient, it's taking a bit longer than we'd like but it's definitely coming. I'm sorry but we can't give exact dates, just know that we're working very hard on getting this out as fast as we can.


Update executable.md

Fixes tiny spelling mistake.

Changed EnittyFramework to EntityFramework

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@lynxz  can you sign the CLA please?

Sorry missed this message, CLA signed.

Thanks for your help


[PHPStanRules] Adding items to allowedStaticCallClasses in NoStaticCallRule

I'd like to add PHPStan\Type\TypeCombinator as it has static methods.
This does not help.
services:
    -
        class: Symplify\PHPStanRules\Rules\NoStaticCallRule
        tags:
            - phpstan.rules.rule
        arguments:
            allowedStaticCallClasses:
                - 'PHPStan\Reflection\ParametersAcceptorSelector'
                - 'PHPStan\Type\TypeCombinator'

Please advise.

That's weird. We'll need failing test case to NoStaticCallRuleTest
My guess would be contradiction with same definition of this rule in another config.

So NoStaticCallRule cannot be configured currently?

Test case answer that

Should be possible. Test case would answer that question.

All I see is https://github.com/symplify/symplify/blob/master/packages/phpstan-rules/tests/Rules/NoStaticPropertyRule/NoStaticPropertyRuleTest.php#L46
Please help me.

You could also add it

grep -r -l 'public static function' | wc -l in PHPStan's source gives 115. What to do?

Should be possible. Test case would answer that question.

I see! https://github.com/symplify/symplify/blob/master/packages/phpstan-rules/tests/Rules/NoStaticCallRule/config/configured_rule.neon
So should I include the above with config/symplify-rules.neon or copy all neon files and modify them?

The second would be better in this case

Thank you.


Disable incremental compilation

This PR will fix this issue: https://github.com/ArpNetworking/sbt-typescript/issues/36
@BrandonArp please review :)

That's a beautiful change!  I was waiting for this feature to be in the compiler for quite a while.  Thanks for making the change!


tidy requirements and site.cfg

This PR tidies the dependencies of iris now that it is exclusively Python3.

Thanks @bjlittle !


Remove Golang 1.15 and 1.16 versions

Issue #, if available:
Description of changes:
After EKS-D started supporting K8 1.27, EKS-D has stopped supporting k8 1.22. All our projects supporting k8 1.23-1.27 are built from  EKS-Go 1.17-1.20. Thus, we are moving forward with deprecating EKS-Go 1.15 and 1.16 (will not update or backport new CVE's). All our Golang artifacts from EKS-Go 1.15 and 1.16 are still will be available in our Public ECR.
As this poses immediate risk to users of EKS-Go 1.15 and 1.16, we advise them it is HIGHLY recommended that users of EKS-GO v1.15 - v1.16 update to a supported version of EKS-Go (v1.17+) as soon as possible.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/hold

Do we need to remove any of the following?

https://github.com/aws/eks-distro-build-tooling/blob/bb66807b9090c64e292bce53262afc184509effd/eks-distro-base/tests/run_tests.sh#L658-L680
https://github.com/aws/eks-distro-build-tooling/blob/bb66807b9090c64e292bce53262afc184509effd/builder-base/versions.yaml#L6
https://github.com/aws/eks-distro-build-tooling/blob/bb66807b9090c64e292bce53262afc184509effd/builder-base/Dockerfile#L211-L225
https://github.com/aws/eks-distro-build-tooling/blob/bb66807b9090c64e292bce53262afc184509effd/builder-base/scripts/install_go_licenses.sh#L35C1-L37
Any of the 1.15 and 1.16 files under here? https://github.com/aws/eks-distro-build-tooling/tree/bb66807b9090c64e292bce53262afc184509effd/eks-distro-base-updates

@kschumy we have to keep all the builder-base 1.16 references for the time being

/approve

/unhold


Document and workaround a double-encoding resulting in broken paginat…

…ion links on the web UI
Pagination links created by Spring MVC/HATEOAS get encoded multiple times, resulting in broken next/previous links when navigating multi-page results.
Document this behavior with a test (so that it will be noticed if it changes).
Workaround by performing multiple decoding on such links before displaying them in the Genie web UI.

Coverage remained the same at 88.518% when pulling 17f0927224fb7bf6399b46f431ed4f845c6c9337 on mprimi:master into 8a240127093c8eb4b99ed1081d83d33775440948 on Netflix:master.

Coverage remained the same at 88.518% when pulling c9a49cfbdba89914752cab1b33c52c9e6c117b89 on mprimi:master into 8a240127093c8eb4b99ed1081d83d33775440948 on Netflix:master.


Facility to create a separate environment for native app

Right now, we have certain settings exclusively for native app. For e.g: locationType: 'hash'.
Is it possible to have a separate environment for native app, which modifies the configuration already present for 'development' or 'production'?

You can either do something like this:
var ENV = {
  locationType: process.env.EMBER_CLI_NW ? 'hash' : 'auto',
  // ...
};

or this:
var ENV = {
  // common config
};

if (process.env.EMBER_CLI_NW) {
  // override settings for NW.js
}

or introduce a new environment altogether in your config/environment.js:
var ENV = {
  // common config
};

if (environment === 'nwjs') {
  // override settings for NW.js
}

But if you do the latter, you'll have to run all the ember nw[:*] commands with --environment=nwjs.

Thanks. It would be nice if the above can be added to the README since this is a fairly common use case.


fix: produce correct secondary package paths

I'm submitting a...
[x] Bug Fix
[ ] Feature
[ ] Other (Refactoring, Added tests, Documentation, ...)

Does this PR introduce a breaking change?
[ ] Yes
[x] No

Tested on windows machine!  Works!


Using length replaced by magnitude.

Does this need a new tag?

I think it does, 'cause it'll let us to avoid annoying deprecation message.


Fix incorrect manifest url in channel example.

Fix incorrect manifest url in channel example.

Applied this change locally, It's surprise to me that running ./prospero install --fpl org.wildfly:wildfly-galleon-pack --channel examples/wildfly-27.0.0.Alpha2-channel.yaml --dir installation-dir successfully provision a server. The wildfly-27.0.0.Alpha2-manifest.yaml contains vendor information which shouldn't be part of manifest file, I actually expect a parsing error during schema validation.

Hi @soul2zimate, can you remove the vendor block from the manifest too then?

Thanks @soul2zimate


Failure renewing certificate

Two months or so ago I had issues with renewing of certificates. This is a server with 6 certificates and 3 of them give a renewal failure.
Running wacs.exe and trying to renew manually did not help.
Attached is the log that was created.
log-20210408.txt

Hi @emilstojanov, I believe this is a bug that was fixed in more recent versions of the software, I suggest you install the latest release and try that.

Hi Wouter,
I update to version <IP_ADDRESS>7 and the renewal still fails for one of the domains.
Attached a new log
log-20210411.txt

Hi @emilstojanov, I noticed this in your log now:
2021-04-11 09:00:01.746 +02:00 [WRN] Another instance of wacs.exe is already running, it is not recommended to run multiple instances simultaneously.
If you want to run multiple instances of the scheduled task (e.g. because you use different ACME endpoints) then I'd recommend scheduling them at different times of the day. If that is not your intention then you should probably clean up the Windows Task Scheduler a bit.

I do NOT want to run multiple instances, I have no idea why it created two tasks. I remove both tasks and let wacs.exe create a new task.
I also had a lot of duplicate renewals. So I remove all renewals except for [IIS] Drakar ICT, (any host). I presume that this one will take care of all 4 bindings on the Drakar ICT website.
Tomorrow I will try to renew the certificates for the LittleRaven website. That is the one that gives me trouble. Then I will have a clean log.

Based on this feedback I plan to disallow running simulaneous copies completely. Going forwards they will nicely wait for eachother to finish in this scenario.

I just tried to create the certificates again and I am still runiing into the same issue. The creation of a certificate for the domain littleraven.ws keeps failing.
log-20210413.txt

You're not running into the same issue, this is a different one. The solution is to allow the service more time to do the validation, by increasing the values for Acme.RetryCount and/or Acme.RetryInterval in settings.json. I think you are probably on the old defaults (4 retries with 2 second interval). The new default is 5 retries with 5 second interval, more than trippeling the time the service has to do its thing.

You are correct. I was indeed running with the old defaults. Changed the defaults to the new settings (5,5) and tried again. It still failed. Then I ran it again with the --verbose flag and now it created all certificates without error..
Could it be that I need a still higher RetryInterval?

That's possible, sometimes the service can be busy/slow. Longer timeouts cannot hurt in any case, they just slows you down when failure is inevitable :)


chore(main): release 1.6.5

:robot: I have created a release beep boop
1.6.5 (2023-10-16)
Bug Fixes

🐛 修复 App NextTick 错误 (79d85eb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/viarotel-org/escrcpy/releases/tag/v1.6.5 :sunflower:


Please allow a shortcut for applying the last used type to the currently active geometry

Sometimes I want to map a bunch of buildings.  It would be very nice to have a keyboard shortcut to apply the last used type to the current geometry.
Currently, I have to draw a building and then click "building" on the sidebar. This isn't a problem if you are just mapping one building, but if you're mapping 50 or 200 buildings, it's incredibly annoying.

Yes, I want this too!  This is captured in #1761 / #590


Windows goes to other monitors after Virtual Desktop switching.

Microsoft PowerToys version
v0.63.0
Installation method
GitHub
Running as admin

[X] Yes

Area(s) with issue?
FancyZones
Steps to reproduce
PowerToysReport_2022-10-22-16-35-11.zip
I was using Word on monitor 1 full screen, I switch to another Virtual Desktop by Ctrl+Win+Left, and switch back, Word go to monitor 2 by itself.
✔ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response

Is this issue still relevant in v0.73? /needinfo


Skip ENOENT for vram_str_path and sdma_str_path if files not created when passing some, but not all, GPUs to a docker image

This PR is intended to resolve these issues where rocm-smi --showpids unexpectedly returns UNKNOWNs:
https://github.com/ROCm/ROCm/issues/3002
When running rocm-smi --showpids  when a process does not have access to all GPUs (eg. in a docker image where some, but not all devices are passed through), GetProcessInfoForPID attempts to enumerate all GPUs on the host and search for vram/sdma/cu_occupancy data. In the VRAM example:
  for (itr = gpu_set->begin(); itr != gpu_set->end(); itr++) {
    uint64_t gpu_id = (*itr);
    std::string vram_str_path = proc_str_path;
    vram_str_path += "/vram_";
    vram_str_path += std::to_string(gpu_id);

    err = ReadSysfsStr(vram_str_path, &tmp); //returns ENOENT
    [...]

So, we attempt to access file proc_str_path/vram_{gpu_id} for each gpu on the host (where rocm-smi is invoked). However, since the host and the monitored process have different perspectives on which GPUs exist, there is an inconsistency:
The monitored process will only create vram_{gpu_id} files for the GPUs it thinks exists, while the host expects to see vram_{gpu_id} files for all GPUs. This results in host attempting to read nonexistent files and return early out of the loop with ENOENT.
This PR will ignore ENOENTs when enumerating vram_ and sdma_ files but still return early if other errors are encountered, instead of prematurely returning from the loop. A previous PR - https://github.com/ROCm/rocm_smi_lib/pull/155 - has handled the case for cu_occupancy which may be absent due to device non-support.

This PR has been merged internally and will be available in a future ROCm release.


Fix fromString

Hi! I wanna close #38

Hmm that totally shouldn't pass bincompat.

Thank you for review. What can I done here? Maybe exists another way for fix this issue?

@d1skort  I think we could use a translate error to work.
Either.catchNonFatal(x)
  .adaptError{
     case ok@IllegalArgumentException => ok
     case other                       => new IllegalArgumentException(other.getMessage)
  }

Honestly that may be the better solution overall.

This may be
ok : IllegalArgumentException => ok.asInstanceOf[IllegalArgumentException]
We will be changing the type explicitly to throwable in next version but I agree we should fix this here initially.

Interesting...
Thank you for support!

One final thing, could we introduce a test to make sure the original concern is addressed and will continue to be addressed moving forward.
Same as this test but with the input - 2630147c-4a18-4866-9bbd-b2d89acef83z

yeah, totally


add stats to haproxy

Enable haproxy stats to collect it on datadog

Pull Request Test Coverage Report for Build 669

0 of 0   changed or added relevant lines in 0 files are covered.
3 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 57.738%

Files with Coverage Reduction
New Missed Lines
%

apps/neoscan_node/lib/neoscan_node/notifications/notifications.ex
1
86.96%

apps/neoscan_sync/lib/neoscan_sync/genstage/producer.ex
2
67.44%

Totals

Change from base Build 667:
0.1%

Covered Lines:
1026

Relevant Lines:
1777

💛  - Coveralls


[Feature] YOLOv6 self-distillation

Describe the feature
YOLOv6 self-distillation
Motivation
Self-distillation is a common practice s to improve performance.
Related resources
https://github.com/meituan/YOLOv6

Sorry for the delayed response and thank you for your advice. Self-distillation is a widely used technique that limits the teacher to be the student itself. It's a great idea, but we haven't been able to support it yet due to manpower shortages. We'll appreciate it if you can open a pull request. And here is an example to use distillation on rtmdet.


Add license boilerplate to .go files and add boilerplate checking scripts from kubernetes projects.

Many of our .go files are missing required Apache 2.0 boilerplate text required by the Kubernetes project standards. Proposed solution:

Add the text.
Look at a kubernetes project like cluster-api and add the boilerplate verification scripts they use to this project to ensure future commits have the required text.

The EMLB openapitools-cli generated SDK files (#476) may stand as an exception to the Apache licenses that would be applied on the files in this project (also relevant for CAPP).
The long-term intent for those files is that they would be imported into this project from an outside repository where the files are licensed under a compatible license (very likely MIT, following the equinix-sdk-go pattern).
https://github.com/equinix/equinix-sdk-go/blob/main/LICENSE

If the files can coexist in both repositories with alternate Copyright holders, a single author should also be fine.


Support for Drupal 11: update package version requirements

Problem:
Currently, installing the package with the latest D11.x dev fails with requirements errors:
$ composer update -W
> DrupalProject\composer\ScriptHandler::checkComposerVersion
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - joachim-n/composer-manifest 1.1.5 requires symfony/yaml ^3.4 || ^4.2 || ^5.4 || ^6.1 -> satisfiable by symfony/yaml[v3.4.0-BETA1, ..., 3.4.x-dev, v4.2.0-BETA1, ..., 4.4.x-dev, v5.4.0-BETA1, ..., 5.4.x-dev, v6.1.0-BETA1, ..., 6.4.x-dev].
    - joachim-n/composer-manifest[1.1.0, ..., 1.1.4] require symfony/yaml ^3.4 || ^4.2 -> satisfiable by symfony/yaml[v3.4.0-BETA1, ..., 3.4.x-dev, v4.2.0-BETA1, ..., 4.4.x-dev].
    - You can only install one version of a package, so only one of these can be installed: symfony/yaml[2.0.5, ..., 2.8.x-dev, v3.0.0-BETA1, ..., 3.4.x-dev, v4.0.0-BETA1, ..., 4.4.x-dev, v5.0.0-BETA1, ..., 5.4.x-dev, v6.0.0-BETA1, ..., 6.4.x-dev, v7.1.0-BETA1, ..., 7.2.x-dev].
    - drupal/core-recommended 11.x-dev requires symfony/yaml ~v7.1.1 -> satisfiable by symfony/yaml[v7.1.1, 7.1.x-dev].
    - symfony/yaml[v4.0.10, ..., v4.4.8] require php ^7.1.3 -> your php version (8.3.8) does not satisfy that requirement.
    - Root composer.json requires drupal/core-recommended ^11.x-dev@dev -> satisfiable by drupal/core-recommended[11.x-dev].
    - Root composer.json requires joachim-n/composer-manifest ^1.1 -> satisfiable by joachim-n/composer-manifest[1.1.0, ..., 1.1.5].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Maybe composer-manifest version requirements should be bumped a bit so they could be compatible with more recent versions of Drupal, in particular, Drupal 11.x.

Thanks for reporting!
Fixed and new release made.

Thanks a lot Joachim!
I've just given it a quick try and it seems to be working fine now  with "drupal/core-recommended": "^11.x-dev@dev"
One thing though, not sure if the "symfony/var-dumper": "^4.2" could cause any issue, or problems with the requirements with D11 core dev....
https://github.com/joachim-n/composer-manifest/blob/master/composer.json#L16C10-L16C28
I haven't had any issue adding the project locally, with "drupal/core-dev": "^11.x-dev@dev", but that's maybe because I have other packages installed as well ...
Just not sure, but wanted to double check with you.
Thanks again for your great help and reactivity Joachim!


Implementation of compression frame patch embedding (Fig. 3b)

Hi,
Thanks for the great work. I have a few questions:

By default which "patch embedding" is used? Fig.3(a) or (b)?
Is there a parameter to switch between (a) and (b) in a config file?
I'd like to take a look at the implementation of (b) -- compression frame patch embedding. I see PatchEmbed several places and they are from different libs: sometimes from diffuser sometimes from timm. Do you have a pointer to the code where Fig.3(b) is implemented?

Hi, Thanks for the great work. I have a few questions:

By default which "patch embedding" is used? Fig.3(a) or (b)?
Is there a parameter to switch between (a) and (b) in a config file?
I'd like to take a look at the implementation of (b) -- compression frame patch embedding. I see PatchEmbed several places and they are from different libs: sometimes from diffuser sometimes from timm. Do you have a pointer to the code where Fig.3(b) is implemented?

Latte uses Fig.3 (a) by default.
This repo does not provide (b).
Please refer to here.

Thanks for the prompt reply and pointers.


Issue while updating github

Hi,
I have noticed an error in console after uptating github when I test a transifex webhook call.
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : Processing request at /hooks/transifex
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : #<Sinatra::Request:0x00559c30fc1cd8 @env={"rack.version"=>[1, 3], "rack.errors"=>#<IO:<STDERR>>, "rack.multithread"=>true, "rack.multiprocess"=>false, "rack.run_once"=>false, "SCRIPT_NAME"=>"/hooks", "QUERY_STRING"=>"", "SERVER_PROTOCOL"=>"HTTP/1.1", "SERVER_SOFTWARE"=>"2.15.3", "GATEWAY_INTERFACE"=>"CGI/1.2", "REQUEST_METHOD"=>"POST", "REQUEST_PATH"=>"/hooks/transifex", "REQUEST_URI"=>"/hooks/transifex", "HTTP_VERSION"=>"HTTP/1.1", "HTTP_HOST"=>"localhost:8080", "HTTP_CONNECTION"=>"keep-alive", "CONTENT_LENGTH"=>"76", "HTTP_AUTHORIZATION"=>"Basic xxxxxxxxx==", "HTTP_CACHE_CONTROL"=>"no-cache", "HTTP_ORIGIN"=>"chrome-extension://fhbjgbiflinjbdggehcddcbncdddomop", "CONTENT_TYPE"=>"application/x-www-form-urlencoded", "HTTP_USER_AGENT"=>"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.111 Safari/537.36", "HTTP_POSTMAN_TOKEN"=>"540316de-9e81-67b8-0cab-500336c6c317", "HTTP_ACCEPT"=>"*/*", "HTTP_ACCEPT_ENCODING"=>"gzip, deflate", "HTTP_ACCEPT_LANGUAGE"=>"fr-FR,fr;q=0.8,en;q=0.6", "SERVER_NAME"=>"localhost", "SERVER_PORT"=>"8080", "PATH_INFO"=>"/transifex", "REMOTE_ADDR"=>"<IP_ADDRESS>", "puma.socket"=>#<TCPSocket:fd 12>, "rack.hijack?"=>true, "rack.hijack"=>#<Puma::Client:0x2ace187e1a88 @ready=true>, "rack.input"=>#<StringIO:0x00559c30fc2ca0>, "rack.url_scheme"=>"http", "rack.after_reply"=>[], "rack.request.query_string"=>"", "rack.request.query_hash"=>{}, "rack.request.form_hash"=>{"project"=>"coorpacademy/mooc-core", "resource"=>"account", "language"=>"it", "translated"=>"100"}, "rack.request.form_vars"=>"project=coorpacademy%2Fmooc-core&resource=account&language=it&translated=100", "rack.request.form_input"=>#<StringIO:0x00559c30fc2ca0>, "sinatra.route"=>"POST /transifex"}, @params={"project"=>"coorpacademy/mooc-core", "resource"=>"account", "language"=>"it", "translated"=>"100"}>
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : account
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : request language matches resource
web_1 | I, [2016-01-26T08:16:10.082753 #1]  INFO -- : get https://www.transifex.com/api/2/project/mooc-core/resource/account/translation/it/
web_1 | D, [2016-01-26T08:16:10.083611 #1] DEBUG -- request: User-Agent: "Faraday v0.9.2"
web_1 | Authorization: "Basic xxxxxxxxxxx"
web_1 | Accept: "application/json"
web_1 | I, [2016-01-26T08:16:10.321601 #1]  INFO -- Status: 200
web_1 | D, [2016-01-26T08:16:10.322363 #1] DEBUG -- response: server: "nginx"
web_1 | vary: "Accept-Encoding, Authorization, Host, Accept-Language, Cookie"
web_1 | cache-control: "max-age=0"
web_1 | content-type: "application/json; charset=utf-8"
web_1 | date: "Tue, 26 Jan 2016 08:16:10 GMT"
web_1 | expires: "Tue, 26 Jan 2016 08:16:10 GMT"
web_1 | transfer-encoding: "chunked"
web_1 | content-language: "en"
web_1 | x-content-type-options: "nosniff"
web_1 | connection: "close"
web_1 | set-cookie: "X-Mapping-fjhppofk=B8558B7BB369B761FC4CE03884ACF0F5; path=/"
web_1 | last-modified: "Tue, 26 Jan 2016 08:16:10 GMT"
web_1 | x-frame-options: "SAMEORIGIN"
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : request language is in lang_map and is in request or is nil
web_1 | I, [Tue 26-01-2016 0816 #1]  INFO -- : make github commit for branch: heads/txgh
web_1 | 2016-01-26 08:16:13 +0000: Read error: #<NoMethodError: undefined method `bytesize' for [:ref, "refs/heads/txgh"]:Array>
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/server.rb:668:in `block in handle_request'
web_1 | /usr/local/bundle/gems/sawyer-0.6.0/lib/sawyer/resource.rb:125:in `each'
web_1 | /usr/local/bundle/gems/sawyer-0.6.0/lib/sawyer/resource.rb:125:in `each'
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/server.rb:666:in `handle_request'
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/server.rb:388:in `process_client'
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/server.rb:270:in `block in run'
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/thread_pool.rb:106:in `call'
web_1 | /usr/local/bundle/gems/puma-2.15.3/lib/puma/thread_pool.rb:106:in `block in spawn_thread'

You can reproduce on this Docker image, https://hub.docker.com/r/coorpacademy/txgh/

Ruby 2.18
Git 2.1.4
Puma 2.15.3

Github seems to have been updated and there is no response from txgh.

Hi @lcalvy I pulled your docker image and ran the project tests...this seemed to work ok.  So my initial feeling is that this issue is the result of some of the config not being setup right. ie 'undefined bytesize' because an expected file is missing or maybe even something wrong with the repo.
I will dig more and see if I can recreate a case where this might happen.
Of course the ultimate best is if you can help identify a specific payload that is missing 'bytesize'...and then we can write a test for it!

I haven't been able to recreate this issue under proper configuration.  Closing issue.


comment on QName no longer needed

The publication of the quickstart files includes an rdfs:comment about the QName.  This was put in to trick widoco into doing something we wanted.  The new FIBO Viewer does this out of the box (provides the qname for copy/paste purposes).  This rdfs:comment is no longer needed, and is distracting and annoying.

I believe "QName" (sic) comments appear in more than the quickstart files.
I've made this comment before (and provided references - see https://jira.edmcouncil.org/browse/INFRA-471) - this is not using "QName" as officially defined - which is a purely XML thing. I think we're talking about standard namespace prefixes which are just as applicable to SPARQL and TTL, not XML.

The Qname appears on every element in every published file in the primary OWL product not just Quickstart. It's redundant and clutter and annoying when using tooling that displays rdfs:comments. Can we please get rid of it ASAP @dallemang and @trypuz .


JRuby support

JRuby support is currently missing from lotus.
Asking @jodosha it seems to be because Module.prepend is missing in the current JRuby release.
FYI Module.prepend seems to be mostly implemented on JRuby master jruby/jruby#751 which is the next major release (JRuby 9k) - unfortunately I dunno when it's gonna land (hoping for start of next year personally).
If I get a lot of time I might look into the code to figure out if prepend could be reasonably replaced.
Cheers!

I created a feature card https://trello.com/c/aRmE8bSF/107-support-jruby

@PragTob Do you use JRuby in production? Supporting multiple VMs is getting harder and harder for us. We're evaluating what to do.

JRuby is used by multiple companies in production - here is a recent slide of companies using JRuby in production/for their applications:

Sadly I don't use it in production right now as I don't have an app that is "mine" deployed - but I'm a frequent JRuby promoter and just wait for a chance to plug it in :). And it is frequently recommended in settings where high performance/scalability is needed. High load companies like SoundCloud and TravisCI use it frequently (in the majority of their apps that use ruby, as far as I am aware). For instance this discussion on Ruby rogues: http://devchat.tv/ruby-rogues/162-rr-scaling-rails-with-steve-corona
Where is the pain with supporting JRuby? Can I help you there? 9k should release this year and be 2.2 compatible - the only stuff that I know is not supported is C extensions, but mostly there is an equivalent Java replacement or a ffi compatible gem :) Supporting 9k+ should be ok I believe.
So JRuby support is vital imo to the success of a web framework in today's ruby landscape.
Sorry time is kind of limited, balancing new job, shoes4, ruby user group berlin and confs - but would love to help with JRuby support in code as well. Always here for at least information support etc. :)
PS: As a full disclosure I'm biased towards JRuby of course, biased enoughso that people convinced me to organize JRubyconf this year :)

@PragTob Thanks for the extensive explanation about the benefits of supporting JRuby.
Our problem time and effort. Our Core Team is made of two people, working on free time on Lotus. We have contributors who are helping a lot to speed things up.
Supporting several VMs with a different set of features is becoming a burden for us. Sadly, Ruby is what MRI is. Other implementations will eventually follow. To add injury to insult, roadmaps for those rubies are never clear.
If we plan a release, we can never tell if we should add workarounds for those VMs, or if they will come out with a new version that brings what we need.
We want to apply an 80/20 rule. For our sanity and to ensure that Lotus will make progress.
I'll give you one example: collectable symbols. This MRI 2.2 feature solves a lot of problems for us. To symbolize params representing untrusted input was a serious security threat. We put in place slow but safe mechanism to make Lotus defended against those attacks.
Again, this required and requires time and attention. This effort can be used to build other features, if we assume that the current VM will collect symbols and move on.
In less than a week we should have JRuby 9k beta released which will be compliant with MRI 2.2.
We don't have a timeline for Rubinius yet.
I'm closing this discussion, by saying that the next minor releases will only target VMs with 2.2+ mode.

Would be nice to add to the README :). Targetting 2.2+ compatible VMS seems good with me :) Thanks!

@PragTob Rubies compat is documented in all the READMEs. You don't see JRuby in lotus/lotus repo because both Model and Controller aren't compatible with it and so Lotus isn't.

I was looking for "MRI 2.2+ compatible rubies" :) README says 2.0+

@PragTob We want to wait a bit, then cleanup the code of the gems and bump a minor version of all of them. It's a decision that we just took. :)


kvm: Use 'ip' instead of 'brctl'

The command 'brctl' is deprecated and should no longer be used.
iproute2 supports all the features we need and therefor we should use
this instead of the old commands.
Feature wise this does not change anything. It just makes the code more
robust towards the future.
Signed-off-by: Wido den Hollander<EMAIL_ADDRESS>

LGTM
tested the commands on ubuntu 16

Seems good to me, except this won't run under CentOS 6 according to the manpages of iproute (running currently iproute 2.6.32).
Backporting this should therefore not be done.

@wido can you also fix scripts/vm/network/vnet/modifyvlan.sh?
With CentOS6 support removed from master/4.14, we should try and move all network related commands to use iproute2 instead of ifconfig/brctl etc.

Done @rhtyd

Nice, thanks.
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✖centos6 ✔centos7 ✔debian. JID-310

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

This one looks ready to merge.
@rhtyd Is there any issue with the blueorangutan test?

Something went wrong at the backend, I'll rekick test.
@blueorangutan package

@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.

Packaging result: ✖centos6 ✔centos7 ✔debian. JID-324

@blueorangutan test

@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-422)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 36375 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr3623-t422-kvm-centos7.zip
Intermittent failure detected: /marvin/tests/smoke/test_privategw_acl.py
Smoke tests completed. 76 look OK, 1 have error(s)
Only failed tests results shown below:

Test
Result
Time (s)
Test File

test_02_vpc_privategw_static_routes
Failure
244.80
test_privategw_acl.py


Dbbackup overwrites all but the latest file

As far as I can see, dbbackup always creates single backup called [databasename].backup and overwrites previous backups, since they're already called the same name.
It looks like the issue might be in save_new_backup() in dbbackup.py. Could this instead use similar logic to get_backup_basename() in mediabackup.py, which adds a timestamp?

Wanted to chime in that this is still an issue and related to https://github.com/mjs7231/django-dbbackup/issues/52 .
The comments / doc mentioned that big chunks of the codebase were going to be refactored / rewritten. Is this still the case? If the codebase is going to be relatively static off whatever is in prod, I'd love to contribute some patches more aggressively.

I don't think there's gonna be refactors, no actions except for some old comments indicate this.

I think this issue is no more relevant with current version. File's name has been refactored.


Redux is spammed with BACKEND_CONNECTION_UP actions

Right now the HeartbeatBackendListener component in OverlayScreen.tsx dispatches an establishedBackendConnection action on every single message the frontend receives from the backend. With the current messaging settings, that means that the frontend is usually having to process an extra (redundant) action up to once every 10 ms. This is probably not the main performance bottleneck in our frontend, but it adds a ton of extra events into the Redux inspector (which makes it harder to catch other actions). The fix should be relatively straightforward to implement: only dispatch the establishedBackendConnection action if the backend is not already connected (as reported by the getBackendConnected selector).
It might be worth getting CPU usage measurements before and after this is fixed, just to get a sense of whether this issue has any measurable impact on CPU usage.

There also seems to be some kind of correctness problem with the triggering of establishedBackendConnection action dispatches. When I modify the backend's frontend send schedule to only send a state to the frontend once every 5 seconds, and I uncomment the backend's print code to print every single event sent by the backend to the frontend, I see that there's a flurry of BACKEND_CONNECTION_UP action triggered after every single event sent by the backend. There should be no more than one such action triggered after every event from the backend. What I see now reminds me of the behavior we saw in #363. @rohanpurohit Can you see if you can reproduce those test conditions and this observation on your end? I first observed this on 2bbd755, but I would expect that it should also be reproducible on the develop branch (e.g. d71f11a).

There also seems to be some kind of correctness problem with the triggering of establishedBackendConnection action dispatches. When I modify the backend's frontend send schedule to only send a state to the frontend once every 5 seconds, and I uncomment the backend's print code to print every single event sent by the backend to the frontend, I see that there's a flood of BACKEND_CONNECTION_UP actions (spaced ~5 ms apart) triggered after every single event sent by the backend. There should be no more than one such action triggered after every event from the backend. What I see now reminds me of the behavior we saw in #363. @rohanpurohit Can you see if you can reproduce those test conditions and this observation on your end? I first observed this on 2bbd755, but I would expect that it should also be reproducible on the develop branch (e.g. d71f11a).
Given the timing of this flood of actions, it seems plausible to me that this could be making the frontend's CPU usage measurably higher than it's supposed to be, so we should definitely measure CPU usage before and after this is fixed. This flooding problem should be fixed before we suppress establishedBackendConnection dispatching when the backend is already connected (as specified in the main issue description for #411), as that suppression will make it harder to verify the correctness of the fix to this flooding problem.

(tested on https://github.com/pez-globo/pufferfish-software/commit/d71f11acfe92357142e66592ae671c153d40aa78 with backend running simulator)
Just to confirm if I'm on the same page, I'll describe what I did and observed, changed FRONTEND_OUTPUT_MIN_INTERVAL in states.py to 5 seconds, uncommented the print code for events sent by the backend to the frontend

opened the redux console in chrome dev tools
after every event sent from the backend to frontend
there is a flood of backend_connection_up events in the redux console

so the code in OverlayScreen.tsx checks for the diff between two dates,
const diff = Math.abs(new Date().valueOf() - new Date(heartbeat).valueOf());
and whether this is greater than 3 seconds, which is true when the backend is disconnected, but obviously not when it's connected. therefore it seems to me that we will be dispatching establishedBackendConnection almost all the time and the 5ms delay is probably due to useEffect or latency in dispatch (I'm not sure)
so I think we should probably edit the logic to remove the if-else and only dispatch establishedBackendConnection  when the backend is disconnected (as reported by the getBackendConnected selector) and maybe dispatch it just once? shouldn't just one dispatch be fine for backend connection established?

therefore it seems to me that we will be dispatching establishedBackendConnection almost all the time when the backend is connected regardless of the (connection timeout)

But what you describe is only a subset of the behavior I see: when the backend is connected, establishedBackendConnection is only dispatched (in a flood) for a finite duration after each message is received from the backend - it's not just one continuous flood, but rather a discrete flood per message. During each flood, somehow the useEffect decides for itself when to end the current flood of action dispatches. This reminded me a lot of how the Rotary Encoder controller would decide for itself when to end its own flood of increment/decrement behaviors, i.e. some sort of circular dependency.

so I think we should probably return early if the backend is connected?

I believe this would be a solution for the problem in the main description of this issue (to quote, "only dispatch the establishedBackendConnection action if the backend is not already connected (as reported by the getBackendConnected selector).").
Perhaps one thing we could do to make the useEffect less wasteful is to compute a boolean timedOut = diff > BACKEND_CONNECTION_TIMEOUT and pass that as a replacement for diff in the useEffect's list of dependencies. I also don't see clock and heartbeat actually being used inside the useEffect, so maybe we can remove them from the list of dependencies?

the 5ms delay is probably due to useEffect or latency in dispatch (I'm not sure).

I looked a bit more closely at the BACKEND_CONNECTION_UP actions in the Redux debugger log, and I saw that the action sometimes caused a diff of store.app.clock. This reminded me that actually the reducer for BACKEND_CONNECTION_UP updates the store.app.clock; but clock is also listed as a dependency in the HeartbeatBackendListener's useEffect! This is probably the source of the circular dependency in our system.

remove clock from the list of dependencies in useEffect (if we never really needed the useEffect to be run whenever store.app.clock changes)
remove the clock-setting behavior of the reducer for BACKEND_CONNECTION_UP (if we never really needed that clock-setting behavior in that reducer in the first place)
or both

@ethanjli It looks like the useEffect was mainly relying on the clock dependency to re-run the useEffect and therefore whenever that changed (and probably one of the other dependencies) it starts listening to whether it needs to dispatch a BACKEND_CONNECTION_DOWN OR BACKEND_CONNECTION_UP action
which is why when I removed the clock dependency in #412, we were not able to detect that backend was disconnected, which also raises concerns about the ambiguity of the useEffect.
so I feel we have two options:

keep clock as a dependency (but then useEffect essentially runs whenever clock changes but we also would want to remove that selector altogether in #415 )
remove it and here we have multiple options we could come up with, this is just one example:
define a local state (which is sort of a timer) that changes state whenever we want (let's say 10 seconds) and that local state is added as a dependency to the useEffect, I'm not sure about the performance improvement or regression from this.
I feel like we should try things that obviously give us the functionality we need and also a performance improvement and ultimately making the behavior of useEffect more deterministic.

one thing is Preact performance profiler is really ambiguous, I tried following the 2nd approach but I'm not sure if the component rendered more or less.

Oh, this is very interesting. It sounds like this useEffect is really awkwardly trying to do things made easy by redux-saga (e.g. checking some selectors and dispatching some actions at a regular time interval). If clock does the job correctly, maybe we can keep it as a dependency in #412 (but add a code comment explaining why it's there), and then for #415 we'll completely refactor HeartbeatBackendListener from a useEffect into a saga?

Oh, this is very interesting. It sounds like this useEffect is really awkwardly trying to do things made easy by redux-saga (e.g. checking some selectors and dispatching some actions at a regular time interval, forever). If clock does the job correctly, maybe we can keep it as a dependency in #412 (but add a code comment explaining why it's there), and then for #415 we'll completely refactor HeartbeatBackendListener from a useEffect into a saga?

oh great, I think we can do that! I'll keep clock as a dependency and update the PR!


Add missing path compression option in A* planner

The mechanism to compress the A* path was missing in the implementation.

Actually, on second thought, I'm gonna be difficult here :)
Can you add unit tests for the A-star planner, including a test that checks whether path compression shortens the overall path length? There already is something you can borrow in the test/navigation/test_rrt.py file.

Haha, sure !
I am all in favour of adding tests these days lol.


Add travis_debug command (WIP)

When enabled, the travis_debug command shows the tmate connection strings
I'm unclear how to test if the feature is enabled or disabled.

LGTM!!


Timer inside an Isolate halts when the tab becomes inactive in Dartium

I was trying to do this method in a Polymer web app using isolates to send a heartbeat even while the tab is inactive, but this seemed to be not working in Dartium. I translated the code to JavaScript using pub build and that was working OK in Chrome.
I made a small app to reproduce this problem.
https://github.com/rillomas/isolate_sample
Steps to reproduce

Get code from https://github.com/rillomas/isolate_sample
Run pub get
Run pub serve
Access localhost:8080 with Dartium
Open developer console and confirm the ticking log like [INFO] : tick at 2016-03-23 11:22:55.251241
Create a new tab in Dartium and switch to that tab (Keep the two tabs attached in a single window)
The ticking log will not appear anymore

It will work as intended if you translate the code to JavaScript by the following steps:

Get code from https://github.com/rillomas/isolate_sample
Run pub get
Run pub build
move to build directory and start a  web server there. I used python -m SimpleHTTPServer.
Access localhost:8000/web/index.html with Chrome
Open developer console and confirm the ticking log like [INFO] : tick at 2016-03-23 11:22:55.251241
Create a new tab in Chrome and switch to that tab (Keep the two tabs attached in a single window)
The ticking log will keep appearing

Environment
OS: Windows 7 x64
Dart SDK/Dartium: 1.15.0
Chrome (used for testing pub build): 49.0.2623.87 m (64-bit)

Please re-try with Dart 1.24.2 Stable (Dartium 50).


Add GraphQL interface with ballerina distinct object type

Purpose
Fixes: #3289
Examples
Checklist

[x] Linked to an issue
[x] Updated the changelog
[x] Added tests
[ ] Updated the spec

PR depends on fixes indroduced in v2201.2.0-stage branch of lang repo.
For the feature to work ballerinaLangVersion should be updated after new release


Exempt Local Packages

Is your feature request related to a problem? Please describe.
We use pip-audit in the Manticore CI to check for security issues in our dependencies. This is fine for most of our development, but when we try to create a new release of Manticore, pip-audit fails. The problem is that the release PR we're trying to check contains an incremented version number, but that version of Manticore hasn't been published on PyPI yet, so pip-audit can't check it for issues.
Example
Describe the solution you'd like
Locally installed packages should be ignored when checking for security issues, since they may not have been published on PyPI.
Describe alternatives you've considered
I looked at removing the --strict flag, but this seems like a poor choice for running in a CI environment. The --local flag seems to make pip-audit only look at local packages.
Additional context
The relevant lines from our ci.yml:
    - name: Run pip-audit
      run: |
        python -m pip install .
        pip-audit --strict --desc

The --local flag seems to make pip-audit only look at local packages.

The --local flag controls whether to only audit packages that have been installed in the current virtual environment (that is, local packages) or to include globally installed packages (often things like virtualenv, wheel, setuptools, etc). So that type of local/global distinction won't help us here.

Describe the solution you'd like
Locally installed packages should be ignored when checking for security issues, since they may not have been published on PyPI.

That'd be straightforward to achieve I think. For local installations, pip-api will fill in a location on the file system. So we can just check whether that is populated.
The only thing is that we'll miss reporting some vulnerabilities for packages that have been published to PyPI and just happen to have been installed by pip install .
We could also solve this issue by allowing projects to supply configuration that whitelists certain packages (more on that at https://github.com/trailofbits/pip-audit/issues/209).
@woodruffw @di What do you think about this?

That'd be straightforward to achieve I think. For local installations, pip-api will fill in a location on the file system. So we can just check whether that is populated.

That makes sense to me, although the edge case you pointed out with pip install . is concerning -- I suspect that pattern is pretty common and that we'll end up skipping much of many audits that way.
I think #209 is looking the most appealing to me: at the most general this issues is a variant of all of the other "I want to skip some packages" issues.

I think we maybe need a little more context here:

We use pip-audit in the Manticore CI to check for security issues in our dependencies.

These are sub-dependencies of manticore, or something else? Dev dependencies in a requirements file?
Assuming they're sub-dependencies of manticore, the effect of skipping an audit of manticore would have the effect of skipping all its potential sub-dependencies as well (since pip-audit would skip resolution for manticore), which I think would make the audit somewhat useless.
Ultimately I think https://github.com/trailofbits/pip-audit/issues/81 is what you actually want here: you don't care about vulnerabilities in the top-level manticore project, because you're working with a version that hasn't been released yet. But you care about the sub-dependencies that may get installed when this source tree is installed.

These are sub-dependencies of manticore, or something else? Dev dependencies in a requirements file?

@ehennenfent can confirm, but I believe it's manticore's sub-dependencies.

This is correct; we want to audit only the packages Manticore depends on, and not Manticore itself. #81 would work for our purposes. I wouldn't mind having an option to ignore packages installed via pip install -e <directory>, but if that's out of scope for pip-audit, we can close in favor of #81.

I'll leave this open to track whether we want to exempt editible packages (and have updated the title accordingly).

Opened #244 to explore implementing this.


Add support for integer and array values to 'sw:plugin:config:set' cli command

Previously it was not possible to set an integer or array value when using the cli command sw:plugin:config:set. However, since it is possible to create plugin config elements e.g. for selecting one or multiple dispatch methods, which are saved as their ID (integer) or an array of their IDs (integers) respectively, it is desirable to be able to set the same config value using the cli tools. This PR adds an extra check on the config value passed to Shopware\Commands\PluginConfigSetCommand::execute(), which matches integers and arrays of e.g. the form [val1,val2,val3] and converts them to PHP arrays. Furthermore, if a value contained in the matched array contains only digits, it is converted to an integer.
This PR does not introduce any breaking changes.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/#/issues/SW-15681.
Please use this issue to track the state of your pull request.

Merged with commit https://github.com/shopware/shopware/commit/1c24445d895862d4636c37c9cc8ec1edb83d024e.
Thanks @svenmuennich :+1:


we are noticing lag in delayed job scheduling

e.g. jobs schedule via Resque.enqueue_in(x.seconds, ...
We are noticing that the schedulers are not able to keep up.   Any suggestions for debugging a lag in when jobs are queued?

What does the resque-scheduler output say?  Turning on VERBOSE and checking what you have configured for RESQUE_SCHEDULER_INTERVAL will help.

We bounced everything and flushed the master lock and restarted all the schedulers... things caught up pretty quickly...  I'll keep an eye out for if this happens again.

Just out of curiosity, how many jobs did you have scheduled or in your delayed queue?
I'm gonna close this and you can re-open if the issue happens again.

we have thousands scheduled any given period of time... normally it's rock solid so i think it might just be a matter of we had not bounced the scheduler in quiet a long time or maybe a network blimp between one of our redis servers and the scheduler... looking good this morning.


fix multiple filter AND condition in same keys

host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:07:50:54 +0900]       req:GET / HTTP/1.1      status:200      size:1  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:07:50:55 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:3  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:51:50 +0900]       req:GET / HTTP/1.1      status:200      size:4  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:51:51 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:5  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:59:54 +0900]       req:GET / HTTP/1.1      status:304      size:7  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:59:54 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:8  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:59:57 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:9  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>     ident:- user:-  time:[02/Nov/2017:10:04:34 +0900]       req:GET / HTTP/1.1      status:200      size:10 referer:-       ua:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:10:30:51 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:6  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:10:50:54 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:2  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

following log, it can't be filtering when it's using same key(e.g. "size" is  7 or more and 3 or less)
[u5surf@lltsv 13:31:27]$./lltsv -f 'size <= 7' -f 'size >= 3' -f 'status == 404' access_ltsv2.log
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:07:50:55 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:3  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:51:51 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:5  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:59:54 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:8  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:59:57 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:9  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:10:30:51 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:6  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

I fix muitiple filtering method to using same key in AND condition.
[u5surf@lltsv 13:31:05]$./lltsv -f 'size <= 7' -f 'size >= 3' -f 'status == 404' access_ltsv2.log
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:07:50:55 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:3  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:09:51:51 +0900]       req:GET /play/hls/index.m3u8 HTTP/1.1   status:404      size:5  referer:http://localhost:8000/  ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
host:<IP_ADDRESS>  ident:- user:-  time:[02/Nov/2017:10:30:51 +0900]       req:GET /favicon.ico HTTP/1.1   status:404      size:6  referer:-       ua:Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

@cubicdaiya could you review?


Update airframe-http, airspec to 21.5.3

Updates

org.wvlet.airframe:airframe-http
org.wvlet.airframe:airspec

from 21.4.1 to 21.5.3.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.wvlet.airframe" } ]

labels: library-update, semver-minor

Superseded by #237.


DSharpPlus 5.0.0 support

Hi, what is the support status for 5.0.0 nightlies? I am unable to use these packages after upgrading to 5.0.0 because of
System.TypeLoadException: Could not load type 'DSharpPlus.EventArgs.ReadyEventArgs' from assembly 'DSharpPlus, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'

That is a very good question; should probably make some releases for them, thanks for reminding!

Hm, so sadly just updating to the nightly packages is not enough; there have been some breaking changes I need to figure out first:

Yeah, there were some API changes, I'll wait on 4.4.2 until this repo gets updated, It's been very useful for me :)

Glad to hear! Shouldn't be a ton of work, just adjusting the source generators to whatever breaking change occurred.

Gonna do a 4.4.3 release in between next.

Published a new NuGet with changes from #188
I couldn't get GitVersion to work the way I envisioned so it's not a pre-release.


bug: running Catchment-CN with constant CO2 value overwritten

This issue affects Catchment-CN simulations that are run with a constant CO2 value (ATM_CO2 option 0).
Description:

User-defined constant CO2 value (variable 'CO2') that is being read from LDAS.rc in GEOS_CatchCNGridComp.F90 is being overwritten by an additional declaration of 'CO2' later in Driver routine in GEOS_CatchCNGridComp.F90
The effect of this is that CO2 is set to 0, which causes variables in subroutine Photosynthesis (compute_rc.F90) to be out of bounds causing the model to exit
additional declaration of 'CO2' appears to be remnant of LDASsa structure where constant CO2 value was hardcoded in this place

Solution:

remove additional declaration of 'CO2' in GEOS_CatchCNGridComp.F90

cc: @gmao-rreichle @biljanaorescanin @weiyuan-jiang @rdkoster

cc: @gmao-rreichle @biljanaorescanin @weiyuan-jiang @rdkoster


Feature Request: Folders in folders

I like organizing my feeds. It would be nice to have recursive folders.

Duplicate of #503

This has been covered via a blog post https://inessential.com/2018/09/09/why_netnewswire_doesnt_support_nested_fo on the issue itself.
It has also been mentioned in a number of past issues:

#503
#563
#1370
#2571
#3336
#3392

So I don't think this will be happening anytime soon.
What I ended up doing myself is just using prefixes, and more descriptive. names:

I need this function too，I have more than 1000 feeds,only one layer folder isn't enough.
I ues thunderbird for replace and keep seeking rssreader that fullfill my requirements