[DOCS-1571] Add CNI type patch with 'Calico' for Helm install on EKS

When following the EKS installation docs https://docs.tigera.io/calico/latest/getting-started/kubernetes/managed-public-cloud/eks for Helm, and after executing step 3, we need to patch the spec/cni/type value of the default Installation resource with the Calico value. Otherwise, executing step 4 fails with:
Error: failed to create nodegroups for cluster

Product Version(s):

Calico
Issue:

https://tigera.atlassian.net/browse/DOCS-1571
Link to docs preview:

SME review:

[ ] An SME has approved this change.

DOCS review:

[ ] A member of the docs team has approved this change.

Additional information:

Merge checklist:

[ ] Deploy preview inspected wherever changes were made
[ ] Build completed successfully
[ ] Test have passed

@dimitri-nicolo LGTM, the same should be added to >= OSS 3.24 docs


PEX cards?

How many should we get and who should get them?

This is something it would be good for the finance sub-committee to discuss/decide on in terms of policy.

I have one and that seems to be working just fine for now. We can open a new issue if we think someone else should have one.


[gpio] Incorrect register mask values in specification

Hi Eunchan,
Register Mask values for following GPIO registers seem incorrect to me:
(1) gpio.INTR_STATE @ + 0x0
mask 0x1
(2) gpio.INTR_ENABLE @ + 0x4
mask 0x1
(3) gpio.INTR_TEST @ + 0x8
mask 0x1
For all 3 registers above, I think that mask value should be 0xffff_ffff as all 32-bits are defined.
I am not sure whether mask means represents "defined"/"unreserved" bits or "writable bits"?
Also, I see "Register enable =" in all registers. Are we missing some information here?
Best Regards,
Gaurang

@eunchan, ping.

@eunchan what is the status on this old bug?


Removed duplicated entry on Ready-to-run example projects table

This PR fixes #2304 by swapping the duplicated rest-express entry with rest.nestjs.
I also removed the redundant colons on the left of the Example & Language columns, since the default alignment is already to the left.

@feRpicoral Thanks for this PR, and apologies for slow reply! We will go ahead and merge this, but then do some additional editing... the examples that you considered as duplicates are actually not (one is typescript and one is javascript) but the table used the same descriptions and so it was indeed unclear. After we merge your PR to get the new link, we will work to add all of the examples from the examples repo.


Producer gets stuck in an infinite loop and never produces

Description
On some boxes producer fails to produce messages and gets stuck in an infinite loop with the following message:
Debug|2018-08-23 13:06:23.288|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)

Also afterwards I can see high CPU usage caused by librdkafka.
How to reproduce
EDIT: Even using a very basic example it hangs on Windows Server 2012.
It's rather tricky because it works fine on some boxes while does not on others. The code is very simple:
var producer = new Producer<Empty, SomeType>(settings, new ProtoSerializer<Empty>(), new ProtoSerializer<SomeType>());
await producer.ProduceAsync("my.topic", new Message<Empty, SomeType> {Value = new SomeType
            {
              PropertyX =...,
              PropertyY= ...
            }
            });

Checklist
Please provide the following information:

[x] Confluent.Kafka nuget version:1.0.0-experimental-4 (also 1.0.0-experimental-10)
[x] Apache Kafka version: 1.0.0
[x] Client configuration:

    {
	"batch.num.messages":1,
	"socket.nagle.disable":"true",
	"socket.blocking.max.ms":50,
	"queue.buffering.max.ms":1,
	"log.connection.close":"false",
	"group.id":"KafkaProducerTest.exe",
	"client.id":"KafkaProducerTest.exe",
	"enable.auto.commit":"false",
	"acks":1,
	"bootstrap.servers":"192.168.XXX.UUU:9092, 192.168.XXX.ZZZ:9092, 192.168.XXX.YYY:9092",
	"request.required.acks":1,
	"debug":"all"
}

[x] Operating system: clients: Windows Server 2012; brokers: Ubuntu 16.04
[x] Provide logs (with "debug" : "..." as necessary in configuration)

Debug|2018-08-23 13:06:16.200|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/bootstrap: Broker changed state
APIVERSION_QUERY -> UP
Debug|2018-08-23 13:06:16.200|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.UUU:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:16.200|KafkaProducerTest.exe#producer-1|METADATA| [thrd:1
92.168.XXX.UUU:9092/bootstrap]: Skipping metadata refresh of 1 topic(s): connecte
d: already being requested
Debug|2018-08-23 13:06:16.197|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap: ClusterId: x2DnsDHoRUGMd2-kONsKeg, Control
lerId: 1
Debug|2018-08-23 13:06:16.201|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap: 3 brokers, 1 topics
Debug|2018-08-23 13:06:16.196|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Enabling feature
 SaslHandshake
Debug|2018-08-23 13:06:16.201|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap:  Feature LZ4: Gr
oupCoordinator (0..0) supported by broker
Debug|2018-08-23 13:06:16.201|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Enabling feature
 LZ4
Debug|2018-08-23 13:06:16.202|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap:  Feature OffsetT
ime: Offset (1..1) supported by broker
Debug|2018-08-23 13:06:16.202|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Enabling feature
 OffsetTime
Debug|2018-08-23 13:06:16.202|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap:  Feature : Creat
eTopics (0..0) supported by broker
Debug|2018-08-23 13:06:16.202|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap:  Feature : Delet
eTopics (0..0) supported by broker
Debug|2018-08-23 13:06:16.203|KafkaProducerTest.exe#producer-1|APIVERSION| [thrd
:192.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Enabling feature

Debug|2018-08-23 13:06:16.203|KafkaProducerTest.exe#producer-1|FEATURE| [thrd:19
2.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Updated enabled pro
tocol features to MsgVer1,ApiVersion,BrokerBalancedConsumer,ThrottleTime,Sasl,Sa
slHandshake,BrokerGroupCoordinator,LZ4,OffsetTime,MsgVer2
Debug|2018-08-23 13:06:16.203|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: Broker changed state
APIVERSION_QUERY -> UP
Debug|2018-08-23 13:06:16.203|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.YYY:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:16.203|KafkaProducerTest.exe#producer-1|METADATA| [thrd:1
92.168.XXX.YYY:9092/bootstrap]: Skipping metadata refresh of 1 topic(s): connecte
d: already being requested
Debug|2018-08-23 13:06:16.201|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap:   Broker #0/3: 192.168.XXX.UUU:9092 NodeId
2
Debug|2018-08-23 13:06:16.204|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap:   Broker #1/3: 192.168.XXX.YYY:9092 NodeId
1
Debug|2018-08-23 13:06:16.204|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap:   Broker #2/3: 192.168.XXX.ZZZ:9092 NodeId
 3
Debug|2018-08-23 13:06:16.205|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap:   Topic #0/1: my.topicname with 1
partitions
Debug|2018-08-23 13:06:16.205|KafkaProducerTest.exe#producer-1|STATE| [thrd:main
]: Topic my.topicname changed state unknown -> exists
Debug|2018-08-23 13:06:16.205|KafkaProducerTest.exe#producer-1|PARTCNT| [thrd:ma
in]: Topic my.topicname partition count changed from 0 to 1
Debug|2018-08-23 13:06:16.205|KafkaProducerTest.exe#producer-1|TOPPARNEW| [thrd:
main]: NEW my.topicname [0] 00000062A60D3580 (at rd_kafka_topic_partitio
n_cnt_update:587)
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]:   Topic my.topicname partition 0 Leader 3
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:m
ain]: my.topicname [0]: delegate to broker (none) (rktp 00000062A60D3580
, term 0, ref 2, remove 0)
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:m
ain]: my.topicname [0]: broker :0/internal is now leader for partition w
ith 0 messages (0 bytes) queued
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|BRKMIGR| [thrd:ma
in]: Migrating topic my.topicname [0] 00000062A60D3580 from (none) to :0
/internal (sending PARTITION_JOIN to :0/internal)
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|PARTCNT| [thrd:ma
in]: Partitioning 1 unassigned messages in topic my.topicname to 1 parti
tions
Debug|2018-08-23 13:06:16.206|KafkaProducerTest.exe#producer-1|TOPBRK| [thrd::0/
internal]: :0/internal: Topic my.topicname [0]: joining broker (rktp 000
00062A60D3580)
Debug|2018-08-23 13:06:16.207|KafkaProducerTest.exe#producer-1|FETCHADD| [thrd::
0/internal]: :0/internal: Added my.topicname [0] to active list (1 entri
es, opv 0)
Debug|2018-08-23 13:06:16.207|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
:0/internal]: Broadcasting state change
Debug|2018-08-23 13:06:16.207|KafkaProducerTest.exe#producer-1|UAS| [thrd:main]:
 1/1 messages were partitioned in topic my.topicname
Debug|2018-08-23 13:06:16.208|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap: 1/1 requested topic(s) seen in metadata
Debug|2018-08-23 13:06:16.208|KafkaProducerTest.exe#producer-1|CLUSTERID| [thrd:
main]: 192.168.XXX.ZZZ:9092/bootstrap: ClusterId update "" -> "x2DnsDHoRUGMd2-kO
NsKeg"
Debug|2018-08-23 13:06:16.209|KafkaProducerTest.exe#producer-1|CONTROLLERID| [th
rd:main]: 192.168.XXX.ZZZ:9092/bootstrap: ControllerId update -1 -> 1
Debug|2018-08-23 13:06:16.209|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
main]: Broadcasting state change
Debug|2018-08-23 13:06:17.125|KafkaProducerTest.exe#producer-1|QRYLEADER| [thrd:
main]: Topic my.topicname [0]: leader is internal: re-query
Debug|2018-08-23 13:06:17.125|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: Requesting metadata for 1/1 topics: refresh unavailable topics
Debug|2018-08-23 13:06:17.126|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/bootstrap: Request metadata for 1 topic(s): refresh u
navailable topics
Debug|2018-08-23 13:06:17.203|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/bootstrap: NodeId changed from
-1 to 1
Debug|2018-08-23 13:06:17.203|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/1: Name changed from 192.168.12
8.73:9092/bootstrap to 192.168.XXX.YYY:9092/1
Debug|2018-08-23 13:06:17.203|KafkaProducerTest.exe#producer-1|LEADER| [thrd:192
.168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/1: Mapped 0 partition(s) to bro
ker
Debug|2018-08-23 13:06:17.203|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/1: Broker changed state UP -> UP
DATE
Debug|2018-08-23 13:06:17.204|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.YYY:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:17.204|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.YYY:9092/bootstrap]: 192.168.XXX.YYY:9092/1: Broker changed state UPDATE -
> UP
Debug|2018-08-23 13:06:17.204|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.YYY:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:17.290|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/bootstrap: NodeId changed fro
m -1 to 3
Debug|2018-08-23 13:06:17.290|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Name changed from 192.168.
XXX.ZZZ:9092/bootstrap to 192.168.XXX.ZZZ:9092/3
Debug|2018-08-23 13:06:17.290|KafkaProducerTest.exe#producer-1|TOPICUPD| [thrd:1
92.168.XXX.ZZZ:9092/bootstrap]: Topic my.topicname [0] migrated from bro
ker -1 to 3
Debug|2018-08-23 13:06:17.290|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:1
92.168.XXX.ZZZ:9092/bootstrap]: my.topicname [0]: delegate to broker 192
.168.XXX.ZZZ:9092/3 (rktp 00000062A60D3580, term 0, ref 2, remove 0)
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:1
92.168.XXX.ZZZ:9092/bootstrap]: my.topicname [0]: broker :0/internal no
longer leader
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:1
92.168.XXX.ZZZ:9092/bootstrap]: my.topicname [0]: broker 192.168.XXX.ZZZ
:9092/3 is now leader for partition with 1 messages (74 bytes) queued
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|BRKMIGR| [thrd:19
2.168.XXX.ZZZ:9092/bootstrap]: Migrating topic my.topicname [0] 00000062
A60D3580 from :0/internal to 192.168.XXX.ZZZ:9092/3 (sending PARTITION_LEAVE to
:0/internal)
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|LEADER| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Mapped 1 partition(s) to b
roker
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Broker changed state UP ->
UPDATE
Debug|2018-08-23 13:06:17.292|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.ZZZ:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:17.292|KafkaProducerTest.exe#producer-1|SEND| [thrd:192.1
68.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Sent MetadataRequest (v2, 61
 bytes @ 0, CorrId 3)
Debug|2018-08-23 13:06:17.292|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Broker changed state UPDATE
 -> UP
Debug|2018-08-23 13:06:17.292|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.ZZZ:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:17.292|KafkaProducerTest.exe#producer-1|RECV| [thrd:192.1
68.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Received MetadataResponse (v
2, 186 bytes, CorrId 3, rtt 0.60ms)
Debug|2018-08-23 13:06:17.293|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3: ===== Received metadata (for 1 requested topics):
refresh unavailable topics =====
Debug|2018-08-23 13:06:17.293|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3: ClusterId: x2DnsDHoRUGMd2-kONsKeg, ControllerId: 1

Debug|2018-08-23 13:06:17.293|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3: 3 brokers, 1 topics
Debug|2018-08-23 13:06:17.293|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3:   Broker #0/3: 192.168.XXX.UUU:9092 NodeId 2
Debug|2018-08-23 13:06:17.291|KafkaProducerTest.exe#producer-1|TOPBRK| [thrd::0/
internal]: :0/internal: Topic my.topicname [0]: leaving broker (0 messag
es in xmitq, next leader 192.168.XXX.ZZZ:9092/3, rktp 00000062A60D3580)
Debug|2018-08-23 13:06:17.294|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3:   Broker #1/3: 192.168.XXX.YYY:9092 NodeId 1
Debug|2018-08-23 13:06:17.294|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3:   Broker #2/3: 192.168.XXX.ZZZ:9092 NodeId 3
Debug|2018-08-23 13:06:17.294|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3:   Topic #0/1: my.topicname with 1 partitio
ns
Debug|2018-08-23 13:06:17.294|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]:   Topic my.topicname partition 0 Leader 3
Debug|2018-08-23 13:06:17.294|KafkaProducerTest.exe#producer-1|FETCHADD| [thrd::
0/internal]: :0/internal: Removed my.topicname [0] from active list (0 e
ntries, opv 0)
Debug|2018-08-23 13:06:17.295|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
:0/internal]: Broadcasting state change
Debug|2018-08-23 13:06:17.295|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:m
ain]: my.topicname [0]: delegate to broker 192.168.XXX.ZZZ:9092/3 (rktp
00000062A60D3580, term 0, ref 3, remove 0)
Debug|2018-08-23 13:06:17.295|KafkaProducerTest.exe#producer-1|BRKDELGT| [thrd:m
ain]: my.topicname [0]: broker 192.168.XXX.ZZZ:9092/3 is now leader for
partition with 1 messages (74 bytes) queued
Debug|2018-08-23 13:06:17.296|KafkaProducerTest.exe#producer-1|PARTCNT| [thrd:ma
in]: Partitioning 0 unassigned messages in topic my.topicname to 1 parti
tions
Debug|2018-08-23 13:06:17.296|KafkaProducerTest.exe#producer-1|UAS| [thrd:main]:
 0/0 messages were partitioned in topic my.topicname
Debug|2018-08-23 13:06:17.296|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.ZZZ:9092/3: 1/1 requested topic(s) seen in metadata
Debug|2018-08-23 13:06:17.302|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/bootstrap: NodeId changed from
-1 to 2
Debug|2018-08-23 13:06:17.302|KafkaProducerTest.exe#producer-1|UPDATE| [thrd:192
.168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Name changed from 192.168.12
8.72:9092/bootstrap to 192.168.XXX.UUU:9092/2
Debug|2018-08-23 13:06:17.302|KafkaProducerTest.exe#producer-1|LEADER| [thrd:192
.168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Mapped 0 partition(s) to bro
ker
Debug|2018-08-23 13:06:17.302|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Broker changed state UP -> UP
DATE
Debug|2018-08-23 13:06:17.302|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.UUU:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:17.303|KafkaProducerTest.exe#producer-1|STATE| [thrd:192.
168.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Broker changed state UPDATE -
> UP
Debug|2018-08-23 13:06:17.303|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.UUU:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:18.127|KafkaProducerTest.exe#producer-1|QRYLEADER| [thrd:
main]: Topic my.topicname [0]: leader is unavailable: re-query
Debug|2018-08-23 13:06:18.127|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: Requesting metadata for 1/1 topics: refresh unavailable topics
Debug|2018-08-23 13:06:18.127|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2: Request metadata for 1 topic(s): refresh unavailabl
e topics
Debug|2018-08-23 13:06:18.292|KafkaProducerTest.exe#producer-1|TOPBRK| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Topic my.topicname
 [0]: joining broker (rktp 00000062A60D3580)
Debug|2018-08-23 13:06:18.292|KafkaProducerTest.exe#producer-1|FETCHADD| [thrd:1
92.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: Added atech.depositreque
st [0] to active list (1 entries, opv 0)
Debug|2018-08-23 13:06:18.292|KafkaProducerTest.exe#producer-1|BROADCAST| [thrd:
192.168.XXX.ZZZ:9092/bootstrap]: Broadcasting state change
Debug|2018-08-23 13:06:18.302|KafkaProducerTest.exe#producer-1|SEND| [thrd:192.1
68.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Sent MetadataRequest (v2, 61 b
ytes @ 0, CorrId 2)
Debug|2018-08-23 13:06:18.302|KafkaProducerTest.exe#producer-1|RECV| [thrd:192.1
68.XXX.UUU:9092/bootstrap]: 192.168.XXX.UUU:9092/2: Received MetadataResponse (v2,
 186 bytes, CorrId 2, rtt 0.37ms)
Debug|2018-08-23 13:06:18.302|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2: ===== Received metadata (for 1 requested topics): r
efresh unavailable topics =====
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2: ClusterId: x2DnsDHoRUGMd2-kONsKeg, ControllerId: 1
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2: 3 brokers, 1 topics
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2:   Broker #0/3: 192.168.XXX.UUU:9092 NodeId 2
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2:   Broker #1/3: 192.168.XXX.YYY:9092 NodeId 1
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2:   Broker #2/3: 192.168.XXX.ZZZ:9092 NodeId 3
Debug|2018-08-23 13:06:18.303|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2:   Topic #0/1: my.topicname with 1 partition
s
Debug|2018-08-23 13:06:18.304|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]:   Topic my.topicname partition 0 Leader 3
Debug|2018-08-23 13:06:18.304|KafkaProducerTest.exe#producer-1|METADATA| [thrd:m
ain]: 192.168.XXX.UUU:9092/2: 1/1 requested topic(s) seen in metadata
Debug|2018-08-23 13:06:19.291|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (1 added from partition queue)
Debug|2018-08-23 13:06:20.290|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:21.290|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:22.289|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:23.288|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:24.287|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:25.286|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:26.286|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:27.285|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
Debug|2018-08-23 13:06:28.284|KafkaProducerTest.exe#producer-1|TOPPAR| [thrd:192
.168.XXX.ZZZ:9092/bootstrap]: 192.168.XXX.ZZZ:9092/3: my.topicname [0] 1
 message(s) in xmit queue (0 added from partition queue)
^C

[] Provide broker log excerpts
Can provide if needed.
[] Critical issue

Not that much critical but it's a production issue.

please try 1.0-experimental-10. In particular, #545 has been resolved since 1.0-experimental-4.

[labeled as question as I believe this is most likely an issue that's been resolved in a later build]

@mhowlett Cool, I will try it tomorrow.

Could you try to reproduce when commenting out the following config properties?:
	"batch.num.messages":1,
	"socket.nagle.disable":"true",
	"socket.blocking.max.ms":50,
	"queue.buffering.max.ms":1,
	"log.connection.close":"false",

Also note that the following properties are for the consumer and are ignored for the producer:
	"group.id":"KafkaProducerTest.exe",
	"enable.auto.commit":"false",

@edenhill no success. However, I've noticed that the code (without your proposed config changes) works  on Windows Server 2016 but it does not on Windows Server 2012 (regardless with or without the proposed config changes). The consumer config is OK as I've got both producer and consumer in my test app.

Do any of the producer examples here work?

@edenhill Let me try.

@edenhill I've just tried this one. It hangs too.

@edenhill @mhowlett Ok, my initial hypothesis about the issue being OS related fails. I have found a Windows Server 2012 machine where it works just fine. I am very confused now.

@edenhill For some reason rd_clock() is returning negative values on some of my boxes. I've put the following code in rd_kafka_broker_producer_serve just after now is set:
rd_rkb_dbg(rkb, QUEUE, "CLOCK", "now %"PRId64"", now);

Output from a working box:
Debug|2018-08-29 14:54:25.898|rdkafka#producer-1|CLOCK| [thrd:zzz.zzz.zzz.zzz:9092/bootstrap]: zzz.zzz.zzz.zzz:9092/3:

 now<PHONE_NUMBER>3

Output from not working box:
Debug|2018-08-29 14:53:49.300|rdkafka#producer-1|CLOCK| [thrd:xxx.xxx.xxx.xxx:9092/bootstrap]: xxx.xxx.xxx.xxx:9092/2:

now -102503745224

This issue is also apparent in 0.11.5 but not in 0.11.4 and below. Rebooting the machine did resolve the problem but not sure if I should continue to use 0.11.5.

@edenhill @mhowlett  @ecparra I believe the issue is in the following piece of code from rdtime.h:
static RD_INLINE rd_ts_t rd_clock (void) {
//some other code

        return (now.QuadPart * 1000000) / freq.QuadPart;

//some other code
}

QuadPart is a long long so the max value for that is<PHONE_NUMBER>854775807 which means the max value before it overflows on the multiplication by 1000000 can be<PHONE_NUMBER>854. With a freq of 14318180 (that was on my failing box) it corresponds to slightly more than 7 days:
//counter value / counter freq / seconds in an hour / hours in a day
9223372036854 / 14318180 / 3600 / 24 = about 7.45 days

In 0.11.4 it was implemented using return (rd_ts_t)GetTickCount64() * 1000LLU; that's why it wouldn't have that bug. Does this make sense?

@queil Great analysis! Will look into it, thank you!

@edenhill Thank you very much. It's a real show-stopper for us at the moment.

@edenhill - we also have a number of bug reports the consumer side where restarting the windows server is the only thing that fixes the problem (#610 is this, #584 is this). those issues appear in 0.11.5 and weren't a problem in 0.11.4. could this also be that? superficially, seems a likely to me.
thanks @queil - I think you might have tracked down a really important issue.

For reference, Microsoft QueryPerformanceCounter.

You're right. I edited my comment above.

I believe now.QuadPart / ((double)freq.QuadPart/1000000.0)) will retain precision

or you could stick to integer arithmetic:
clock_coarse = now.QuadPart/freq.QuadPart * 1000000
ticks_fine = ticks - clock_coarse*freq.QuadPart
clock_fine = (ticks_fine * 1000000)/freq.QuadPart
return clock_coarse + clock_fine

quick calc: double has 52 bits of fraction precision -> largest int without any loss of precision =<PHONE_NUMBER>000000000. equivalent to ~10 years using tick value from @queil. after that gradual loss of precision. double calculation would be fine, and probably faster (though there's a couple of casts in there as well which could be costly). i think i prefer sticking to integers though.

where is ticks coming from?

oh sorry ticks is now.QuadPart

The double-version is two instructions, so it should be fine, and is easier to reason about.

0.11.6-RC1 is now on nuget.org which should resolve this.

This problem still seems to be there in 0.11.6-RC1. It hangs at ProduceAsync part. I am using .NET Framework 4.6.1. It works when I use 0.11.2.
`var config = new Dictionary<string, object>
{
{ "bootstrap.servers", "localhost:9092" }
};
        using (var producer = new Producer<Null, string>(config, null, new StringSerializer(Encoding.UTF8)))
        {
            var dr = producer.ProduceAsync("my-topic", null, "test message text").Result;
            Console.WriteLine($"Delivered '{dr.Value}' to: {dr.TopicPartitionOffset}");
            Console.ReadKey();
        }`

@sshaky2 - this sounds like a different issue (unless i'm mistaken, the produce call wasn't blocking in this issue). how long are you waiting? try setting message.timeout.ms to say 10000 and see if the delivery report returns a failure. It defaults to 5 minutes. My guess is message delivery failed for some reason. if the problem persists, please open a different issue and include some debug:all logs.

@mhowlett @edenhill It looks like 0.11.6-RC1 does not have the fix for this issue. Is that intended? I've built qpcfix and it works but the 0.11.6-RC1 nuget does not.

Sorry, that was a mistake on my side, the qpcfix PR is not in RC1.
Will create an RC2 today, this time with the fix in..

@edenhill Cool, thanks!

I've tried 0.11.6-RC2 today - the bug is gone now. Thanks all!

@queil Thank you for all your work on this issue, finding the root cause, suggesting a fix, verifying, all very valuable!

@ravi-sontale - did you use 0.11.6-RC2? that is the only version in which this is currently fixed.

@mhowlett
Yes.
0) supported by broker
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514: Enabling feature SaslHandshake
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514:  Feature LZ4: GroupCoordinator (0..0) supp
orted by broker
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514: Enabling feature LZ4
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514:  Feature OffsetTime: Offset (1..1) support
ed by broker
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514: Enabling feature OffsetTime
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514:  Feature : CreateTopics (0..0) supported b
y broker
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514:  Feature : DeleteTopics (0..0) supported b
y broker
7|2018-09-13 16:26:24.021|rdkafka#producer-1|APIVERSION| [thrd:ssl://broker2:9093/3]: ssl://broker2
:9093/35514: Enabling feature
7|2018-09-13 16:26:24.021|rdkafka#producer-1|FEATURE| [thrd:ssl://broker2:9093/3]: ssl://broker2:9093/35514: Updated enabled protocol features to MsgVer1,
ApiVersion,BrokerBalancedConsumer,ThrottleTime,Sasl,SaslHandshake,BrokerGroupCoo
rdinator,LZ4,OffsetTime,MsgVer2
7|2018-09-13 16:26:24.021|rdkafka#producer-1|STATE| [thrd:ssl://broker2:9093/3]: ssl://broker2:9093/35514: Broker changed state APIVERSION_QUERY -> UP
7|2018-09-13 16:26:24.021|rdkafka#producer-1|BROADCAST| [thrd:ssl://broker2:9093/3]: Broadcasting state change
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:ssl://broker2:9093/3]: ssl://broker2:9093/35514: Request metadata for brokers only: connected
7|2018-09-13 16:26:24.021|rdkafka#producer-1|SEND| [thrd:ssl://broker2:9093/3]: ssl://bbroker2:9093/35514: Sent MetadataRequest (v2, 25 bytes @ 0, CorrId 2
)
7|2018-09-13 16:26:24.021|rdkafka#producer-1|RECV| [thrd:ssl://broker2:9093/3]: ssl://broker2:9093/35514: Received MetadataResponse (v2, 284 bytes, CorrId
2, rtt 4.01ms)
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514: ===== Received metadata
: connected =====
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514: ClusterId: WG7ZA5ZVSra5
apVUIWCa9Q, ControllerId: 37930
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514: 4 brokers, 0 topics
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514:   Broker #0/4: broker2:9093 NodeId 35514
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514:   Broker #1/4: broker2:9093 NodeId 32670
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514:   Broker #2/4: broker2:9093 NodeId 37930
7|2018-09-13 16:26:24.021|rdkafka#producer-1|METADATA| [thrd:main]: ssl://broker2:9093/35514:   Broker #3/4: broker2:9093 NodeId 37547
7|2018-09-13 16:26:24.255|rdkafka#producer-1|TOPIC| [thrd:app]: New local topic:
topic-name
7|2018-09-13 16:26:24.255|rdkafka#producer-1|TOPPARNEW| [thrd:app]: NEW topic-name [-1] 000000B8DAB46AE0 (at rd_kafka_topic_new0:362)
7|2018-09-13 16:26:24.739|rdkafka#producer-1|NOINFO| [thrd:main]: Topic topic-name partition count is zero: should refresh metadata
7|2018-09-13 16:26:24.739|rdkafka#producer-1|METADATA| [thrd:main]: Requesting m
etadata for 1/1 topics: refresh unavailable topics
7|2018-09-13 16:26:24.739|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap: Request metada
ta for 1 topic(s): refresh unavailable topics
7|2018-09-13 16:26:24.817|rdkafka#producer-1|SEND| [thrd:ssl://node1:9]: ssl://node1:9093/bootstrap: Sent MetadataRequest (v2, 51 bytes @ 0,
CorrId 3)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|RECV| [thrd:ssl://node1:9]: ssl://node1:9093/bootstrap: Received MetadataResponse (v2, 401 byte
s, CorrId 3, rtt 4.65ms)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap: ===== Received
metadata (for 1 requested topics): refresh unavailable topics =====
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap: ClusterId: WG7
ZA5ZVSra5apVUIWCa9Q, ControllerId: 37930
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap: 4 brokers, 1 t
opics
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap:   Broker #0/4:
int-evh-broker3-bw-stdev.:9093 NodeId 32670
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap:   Broker #1/4:
broker2:9093 NodeId 35514
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap:   Broker #2/4:
int-evh-broker4-bw-stdev.:9093 NodeId 37930
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap:   Broker #3/4:
int-evh-broker1-bw-stdev.:9093 NodeId 37547
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap:   Topic #0/1:
topic-name with 2 partitions
7|2018-09-13 16:26:24.817|rdkafka#producer-1|STATE| [thrd:main]: Topic topic-name changed state unknown -> exists
7|2018-09-13 16:26:24.817|rdkafka#producer-1|PARTCNT| [thrd:main]: Topic topic-name partition count changed from 0 to 2
7|2018-09-13 16:26:24.817|rdkafka#producer-1|TOPPARNEW| [thrd:main]: NEW topic-name [0] 000000B8DAB47AB0 (at rd_kafka_topic_partition_cnt_update:5
87)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|TOPPARNEW| [thrd:main]: NEW topic-name [1] 000000B8DAB47FB0 (at rd_kafka_topic_partition_cnt_update:5
87)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]:   Topic topic-name partition 0 Leader 32670
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKDELGT| [thrd:main]: topic-name [0]: delegate to broker ssl://broker3:9093/32670 (rktp 000000B8DAB47AB0, term 0, ref 2, remove 0)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKDELGT| [thrd:main]: topic-name [0]: broker ssl://broker3:9093/32670 is now leader for partition with 0 messages (0 bytes) queued
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKMIGR| [thrd:main]: Migrating top
ic topic-name [0] 000000B8DAB47AB0 from (none) to ssl://broker3:9093/32670 (sending PARTITION_JOIN to s
sl://broker3:9093/32670)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]:   Topic topic-name partition 1 Leader 35514
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKDELGT| [thrd:main]: topic-name [1]: delegate to broker ssl://broker2:9093/35514 (rktp 000000B8DAB47FB0, term 0, ref 2, remove 0)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKDELGT| [thrd:main]: topic-name [1]: broker ssl://broker2:9093/35514 is now leader for partition with 0 messages (0 bytes) queued
7|2018-09-13 16:26:24.817|rdkafka#producer-1|BRKMIGR| [thrd:main]: Migrating top
ic topic-name [1] 000000B8DAB47FB0 from (none) to ssl://broker2:9093/35514 (sending PARTITION_JOIN to s
sl://broker2:9093/35514)
7|2018-09-13 16:26:24.817|rdkafka#producer-1|PARTCNT| [thrd:main]: Partitioning
1 unassigned messages in topic topic-name to 2 partitions
7|2018-09-13 16:26:24.817|rdkafka#producer-1|UAS| [thrd:main]: 1/1 messages were
partitioned in topic topic-name
7|2018-09-13 16:26:24.817|rdkafka#producer-1|METADATA| [thrd:main]: ssl://node1:9093/bootstrap: 1/1 requested
topic(s) seen in metadata
7|2018-09-13 16:26:25.004|rdkafka#producer-1|TOPBRK| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: Topic topic-name [0]: joining br
oker (rktp 000000B8DAB47AB0)
7|2018-09-13 16:26:25.004|rdkafka#producer-1|FETCHADD| [thrd:ssl://broker39093/3]: ssl://broker3:9093/32670: Added topic-name [0] to active
list (1 entries, opv 0)
7|2018-09-13 16:26:25.004|rdkafka#producer-1|BROADCAST| [thrd:ssl://broker3:9093/3]: Broadcasting state change
7|2018-09-13 16:26:25.035|rdkafka#producer-1|TOPBRK| [thrd:ssl://broker3:9093/3]: ssl://broker2:9093/35514: Topic topic-name [1]: joining br
oker (rktp 000000B8DAB47FB0)
7|2018-09-13 16:26:25.035|rdkafka#producer-1|FETCHADD| [thrd:ssl://broker2:9093/3]: ssl://broker2:9093/35514: Added topic-name [1] to active
list (1 entries, opv 0)
7|2018-09-13 16:26:25.035|rdkafka#producer-1|BROADCAST| [thrd:ssl://broker2:9093/3]: Broadcasting state change
7|2018-09-13 16:26:26.003|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (1 added from partition queue)
7|2018-09-13 16:26:27.017|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:28.015|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:29.014|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:30.012|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:31.010|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:32.009|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:33.007|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:34.006|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:35.004|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:36.003|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 added from partition queue)
7|2018-09-13 16:26:37.001|rdkafka#producer-1|TOPPAR| [thrd:ssl://broker3:9093/3]: ssl://broker3:9093/32670: topic-name [0] 1 message(s) in x
mit queue (0 add

@ravi-sontale And that's really on v0.11.6-RC2 (not RC1!)? :/

@edenhill
Yes. Today only I have downloaded the 0.11.6-RC2.
And tested using avroseriliser program.

Can you verify that the first line (or thereabout) of output says the version is v0.11.6-RC2?
E.g.:
RDKAFKA-7-INIT: rdkafka#producer-1: [thrd:app]: librdkafka v0.11.6-RC2 (0xb06ff) rdkafka#producer-1 initialized (debug 0xffff)

@edenhill
The output says 0.11.5
7|2018-09-13 18:07:16.283|rdkafka#producer-1|INIT| [thrd:app]: librdkafka **v0.11. 5** (0xb05ff) rdkafka#producer-1 initialized (debug 0xffff)
The problem was I used the AvroSpecific example and copied all the dlls and exe to server. As the bin for this project doesnt have librdkafa folder. I copied it from previous version thinking its the same for 0.11.6-RC2.
I then replaces the librdkafka dlls from 0.11.6-RC2 to AvroSpecific projects bin folder. And then executed on server and it worked :)
I'll try updating my application to 0.11.6-RC2 and see if it works.
Thanks for your prompt response and help.

Phew, that is good news :)

@ravi-sontale I had to downgrade it to 0.11.2 to make it work. I haven't tested 0.11.6-RC2 yet.

Downgraded to 0.11.4 and its working through my application as well.

This bug was introduced in v0.11.5 and fixed in v0.11.6-RC2

Any idea when the official v0.11.6 release is planned?

soon. there's a last minute issue related to loading interceptor plugins that's blocking this.

Is it fixed in 11.6? I am confused that issue is not closed.

@klesta490  - yes

This issue has popped up again with us in v 11.6.  We are running on Windows Server 2012 are are seeing this log when the issue occurs:
INFO - 2019-02-19 11:41:52,139 [21] Ascend.ATI.VATI.Moodle.Framework.MessagingPublisher - {"Level":2,"Message":"[thrd:sasl_plaintext://xxxx:9093/103]: sasl_plaintext:/xxxx:9093/103: ATI.VATI.EnrollmentChanges.STG [1] 6 message(s) in xmit queue (0 added from partition queue)"}
When publishes successfully we'll see some number before the "added from partition queue"
The steps to reproduce are the same as listed above.  The only difference I can note are we are using SASL.

Same problem here with version 0.11.6.
Is there a workaround to avoid this? The producer stops producing without warning.


feat: Add mongodb v5 support with strict filter types

This PR adds support for mongodb v5.
Together with this we're switching to the StrictFilter types.
Because this is changing the implementation of the internal types and has potential to break existing applications, I think this should be a major version bump. Happy to hear other arguments though.

[x] Upgrade mongodb to 5.0.0
[x] Use StrictFilter types
[x] Use StrictUpdateFilter types
[x] Update MongoDB API docs links

Agreed on the major version bump.

What is the TL;DR on the difference between Filter and StrictFilter?

What is the TL;DR on the difference between Filter and StrictFilter?

Filter is the old pre-4.3.0 Filter type, which does not support dot-notation fields.
StrictFilter is the post-4.3.0 Filter type, which does support dot-notation fields.

Because this is changing the implementation of the internal types and has potential to break existing applications, I think this should be a major version bump. Happy to hear other arguments though.

From looking at the changes, I'm having trouble understanding what this would break in external applications.
However, since this does involve a major version upgrade of the mongodb library, I think that's enough to merit a major version update.

Worth pinning to 5.0.1? https://github.com/mongodb/node-mongodb-native/releases/tag/v5.0.1

I updated our dev dependency to 5.0.1, but given the peer dependency version is more of an indicator of breaking changes which we depend on, I'll keep that version declared as >=5.0.0 and consumers can upgrade at their own pace to subsequent v5 versions.


Ensure files exist for install:broadcasting

Although closed, this addresses Issue #51157. The install:broadcasting has some legacy code which assumes the existence of config/app.php and app/Providers/BroadcastServiceProvider.php. Neither may be true within a Laravel 11 application.
This PR simply checks for the existence of these files before attempting to read a presumably legacy config/app.php to uncomment the legacy reference to BroadcastServiceProvider.
Ideally, the enableBroadcastServiceProvider method would be removed as it is not needed within a modern Laravel 11 application. But I left it to maintain support for older, unslimmed applications which are now running Laravel 11.

Note, there are some other edge-cases which existed for this command, like the assumed namespace, location, and registry of BroadcastServiceProvider. I left those to keep this PR focused. But am glad to address them if the team thinks they are worthwhile.


Suggested as Risky APP in Phone Manager of Realme RMX3686

Steps to reproduce

Install the LNReader v1.1.18 in Realme RMX3686
Use the App as usual.
After the sometime, the Phone Manager (inbuilt virus scanner) in above device, will report it as Risky App.
It says, this is rootkit virus which can create hidden file system and hide the malware.

Expected behavior
App should run as usual, it should not be reported as Risky App.
Actual behavior
After the using some time, the Phone Manager (inbuilt virus scanner) in above device, will report it as Risky App.
It says, this is rootkit virus which can create hidden file system and hide the malware.
LNReader version
1.1.18
Android version
Android 13
Device
Realme RMX3686
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with a source, I should be opening an issue in the sources repository.
[X] I have updated the app to version 1.1.18.
[X] I will fill out all of the requested information in this form.

It's a false positive due to the APK being unsigned.
Duplicate of #724


Create GPz_classifier.py

Currently just a copy of randomPZ

No need to merge, just initialising...

You may want to call it GPz perhaps

Perhaps this distinguishes it from the regressor variant? (Also, we can always fiddle with naming consistency later on.)

Yes, sorry that is slightly confusing calling it classifier, have just changed to GPz.py for the moment...


Remove unused entry from lockfile

When checking out this repo locally and installing the dependencies, I noticed that it causes a yarn.lock mutation to occur. This is probably not desired, so here's a PR to commit the change that yarn wants to make to the lockfile!

I've never used the changeset tool before and the documentation doesn't mention what type of changes need one of those. If this feels like a change that doesn't require a changelog entry, I'm happy to remove that from the commit!

I would say that changeset are more for Houdini users, not really for developers.
Therefore I would remove the changeset entry.
I triggered the CI, but I will let @AlecAivazis have a look 👍
//Thanks for contributing//

I went ahead and removed the changeset from this PR! I think that means CI will need to be kicked off again 🙃


Some enable implicit dynamic fixes

They can't be dynamic.
Add test for enable-implicit-dynamic flag.

@swift-ci Please smoke test and merge


Upgrade toastr asset files 2.0.1 to 2.1.2

Sorry, Local Test Return invalid

I removed
add_dependency, add_development_depency
if I ircorrect modify file plz :)


Add rest param to trackEvent typing

Shouldn't this parameter be optional?

Support! +1

Any main contributor for checking this PR please?


Move 5A-75E descriptions into a separate directory, add board images

I was wrong thinking that 5A-75E V7.1 is the newer version compared to 5A-75B V7.0. It's a separate board with separate versioning, so I moved it into a separate directory to prevent confusion.

Thanks!


Add JENKINS_OVERWRITE option to allow upgrading from images

Currently you can't upgrade plugins by using a newer image, as the ones included in the image will not overwrite existing ones in JENKINS_HOME

When Jenkins container starts, it will check JENKINS_HOME has this reference content, and copy it there if required. It will not override such files by default, so if you upgraded some plugins from UI they won't be reverted on next start. You can change this behaviour by setting JENKINS_OVERWRITE environment variable to true. This is useful for upgrading from Docker images but can cause Jenkins customizations to be lost on upgrade. Note that JENKINS_OVERWRITE will not affect resources and plugins included in the war file as they are extracted by Jenkins server on startup.

@ndeloof WDYT?
@reviewbybees

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

I'm not sure if having a global var is going to help or would be better to have two ref dirs, one that has content to be intaslled only the first time, and another to overwrite each run

I understand you intent but this is not the way to go imho. Plugin get only overridden on a standard jenkins install if they're bundled in jenkins.war. The "ref" hack is there just to workaround limitation for persistent jenkins_home, it's designed to handle initial setup, but I don't see any interest in preventing user to upgrade those ref-plugins from UI.
Better than an env variable, I would suggest to automatically create plugin.jpi.pinned files, so user can still upgrade from UI and docker image won't override by default, but if user explicitly unpin then override will occur. Wdyt ?

Not so much about preventing user from upgrading from the UI but to get plugin updates as images get updated
Let's say I bundle a jenkins image with extra plugins, and as I update them, I create new images. If the user updates the version of the image he never gets the new plugins, because they never get overwritten.

I can't find a better way to handle this from a Docker point of view, such thing should be addressed by jenkins itself, for sample with support for "bundled" plugins that may not reside inside the war.

better than using some env var, what about using a specific command line argument to docker run, which  jenkins.sh will use to force override ? For sample : docker run jenkins --force-ref

support for "bundled" plugins that may not reside inside the war

Someone was working on such a PR, I recall. You could dig it up.

ok, so I don't think this is a good option.
I'm just deleting the plugin I want to upgrade before the start of the image


Broken after the new update of discord

Can confirm that #3 fixed the issue by manually implementing the updates into the plugin.
Will just have to wait until the author makes the changes on their page.

@TheKodeToad's fix was merged and should be available via BD's plugin update mechanisms soon-ish.


Storage targets dynamic prefix

With the snapshot feature, is it possible to have a dynamic prefix for the storage targets that support a prefix. For example, with the S3 storage target, you can define the spec like this:
s3:
    endpoint: 's3.amazonaws.com'
    bucket: kubedb-qa
    prefix: demo

So instead of having a fixed prefix like demo above, the prefix will be based on the date that the snapshot is being taken, maybe using a customisable prefix template or fixed prefix template options e.g.:
s3:
    endpoint: 's3.amazonaws.com'
    bucket: kubedb-qa
    prefixType: date
    prefix: YYYY/MM/dd

OR
s3:
    endpoint: 's3.amazonaws.com'
    bucket: kubedb-qa
    prefix: template_date

What are your thoughts on the above?

Currently the uploaded snapshot file will be stored on a path like below:
s3://{prefix}/kubedb/{namespace}/{database-name}/{snapshot-name}

If you use the scheduled backup approach, it the snapshot-name will have timestamp suffixed to it. Does that achieve your desired result?
We are also planning to move to restic as uploader. So, this will mean there will be a single archive and no timestamp-ed files.

If you use the scheduled backup approach, it the snapshot-name will have timestamp suffixed to it. Does that achieve your desired result?

Not quite, as the ability to upload to a timestamped object key will allow some degree of organisation of the snapshot files.
In addition, historically AWS did not have a good way of navigating S3 buckets that had 100's of objects contained within, whether manually through the console or programmatically. That has since been improved, but I am an advocate of fewer files in an object key path when it comes to S3.

Insightful observation @boxedcode ! What do you think about using something like restic to store the backups?

I've had a brief look at restic and from what I've seen, it certainly ticks the right boxes from an efficiency and security perspective, and appears to be quite a powerful tool. It is certainly a good next step for kubedb.

This will be addressed by #168 .


Support sending input_request and receiving input_reply messages via the stdin channel

Make updates to support sending input_request and receiving input_reply messages via the stdin channel.
Major changes:

Add string Send(InputRequest message); to IJupyterMessageSender to send message on the stdin socket.
Add InputRequested and PasswordRequested types that derives from KernelEventBase, and handle them in ExecuteRequestHandler, since InputRequested should only be requested when handling an execute_request.
Add StdInChannel and MessageReceiver. StdInChannel accepts a MessageSender and a MessageReceiver.
Add the static method input(string prompt = "") for requesting non-password user input in C#.
Add the static method password(string prompt = "") for requesting password user input in C# (thanks @colombod for the help!)
Update JupyterMessageSender and JupyterRequestContext to take a StdInChannel object.
Very minor refactoring:

rename _shellSender and _ioPubSender to _shellChannel and _ioPubChannel
fix the parameter indentation in JupyterRequestContext.cs

It would be very helpful to include tests at the Microsoft.DotNet.Interactive level early on so we can discuss the design. What is the command and event flow that makes sense at this layer and would make sense as well, for example, in kernel-server mode or via a command-line REPL?
Additional things worth discussing:

Should we create helpers like input, getpass, and so on?
What would requests for other types of input look like and how might we create custom elements to receive that input at the client, e.g. ipywidgets?
Should we intercept Console.ReadLine so that it requests text input?

An important test will be to make sure that passwords don't appear in diagnostic logs, something like this:
var log = new StringBuilder();

using var _ => Pocket.LogEvents.Subscribe(e => log.Append(e.ToLogString()));

// send password input request

log.ToString().Should().NotContain(password);

@jonsequitur I will add a test to validate the password scenario. Thanks!

@colombod Thanks for wiring up the password part!
I pushed a commit to update the var names and exception message in the password gesture. All rest look good to me!

🎉 🎉 🎉 🎉 🎉
@colombod @jonsequitur  Thank you for all the help!

Will this feature be included in the released extension any time soon? It appears that although there have been recent preview releases, they still don't include support for prompting via stdin.

@mattmcnabb Are you asking about our VS Code extension? This issue refers specifically to the Jupyter integration.
We have a separate issue for VS Code support: #436.

@jonsequitur Yes 😃
I'm finding it difficult to distinguish between the two here and in documentation I find on the web. Thanks!


Re-train the openpose ControlNet model with DWPose annotated data

Hi, Thanks for your great work!
One thing I noticed previously in ControlNet is that the openpose model is not performing well on Controlling hands. Even very accuate pose is provided (Through manual editing). I was suspecting that was caused by training set of the ControlNet model containing large amount of mis-annotated data.
Is there a existing work/plan to re-train the openpose ControlNet model with DWPose annotaed data?
Thanks for your work again!

Yes, we also notice the situation. Later we will consider training a new ControlNet model for  DWPose.

I am working on porting the preprocessor to ControlNet extension here: https://github.com/Mikubill/sd-webui-controlnet/pull/1856
Somehow if I run the test I get following error:
  File "D:\stable-diffusion-webui\extensions\sd-webui-controlnet\tests\annotator_tests\openpose_tests\openpose_e2e_test.py", line 17, in setUp
    self.detector.load_model()
  File "D:\stable-diffusion-webui\extensions\sd-webui-controlnet\annotator\openpose\__init__.py", line 207, in load_model
    self.dw_pose_estimation = Wholebody(dw_modelpath, device=self.device)
  File "D:\stable-diffusion-webui\extensions\sd-webui-controlnet\annotator\openpose\wholebody.py", line 37, in __init__
    self.pose_estimator = init_pose_estimator(pose_config, pose_ckpt, device=device)
  File "D:\stable-diffusion-webui\venv\lib\site-packages\mmpose\apis\inference.py", line 109, in init_model
    ckpt = load_checkpoint(model, checkpoint, map_location='cpu')
  File "D:\stable-diffusion-webui\venv\lib\site-packages\mmengine\runner\checkpoint.py", line 639, in load_checkpoint
    raise RuntimeError(
RuntimeError: No state_dict found in checkpoint file annotator/ckpts/dw-ll_ucoco_384.pth

The same pth file works fine if I run it in the Gradio demo code, or just run the constructor alone. I am not very familiar with torch. Did I set anything wrong that could cause this?

I follow your code and try openpose_e2e_test.py. But I do not meet the problem. The problem is here when the point is None. After I fix this, I get the final output as this:

Maybe the pth is broken? Or there are some problems with the file dir?

Ok I found the cause. I was A1111 banning loading unsafe .pth file:
class RestrictedUnpickler(pickle.Unpickler):
    extra_handler = None

    def persistent_load(self, saved_id):
        assert saved_id[0] == 'storage'

        try:
            return TypedStorage(_internal=True)
        except TypeError:
            return TypedStorage()  # PyTorch before 2.0 does not have the _internal argument

    def find_class(self, module, name):
        if self.extra_handler is not None:
            res = self.extra_handler(module, name)
            if res is not None:
                return res

        if module == 'collections' and name == 'OrderedDict':
            return getattr(collections, name)
        if module == 'torch._utils' and name in ['_rebuild_tensor_v2', '_rebuild_parameter', '_rebuild_device_tensor_from_numpy']:
            return getattr(torch._utils, name)
        if module == 'torch' and name in ['FloatStorage', 'HalfStorage', 'IntStorage', 'LongStorage', 'DoubleStorage', 'ByteStorage', 'float32', 'BFloat16Storage']:
            return getattr(torch, name)
        if module == 'torch.nn.modules.container' and name in ['ParameterDict']:
            return getattr(torch.nn.modules.container, name)
        if module == 'numpy.core.multiarray' and name in ['scalar', '_reconstruct']:
            return getattr(numpy.core.multiarray, name)
        if module == 'numpy' and name in ['dtype', 'ndarray']:
            return getattr(numpy, name)
        if module == '_codecs' and name == 'encode':
            return encode
        if module == "pytorch_lightning.callbacks" and name == 'model_checkpoint':
            import pytorch_lightning.callbacks
            return pytorch_lightning.callbacks.model_checkpoint
        if module == "pytorch_lightning.callbacks.model_checkpoint" and name == 'ModelCheckpoint':
            import pytorch_lightning.callbacks.model_checkpoint
            return pytorch_lightning.callbacks.model_checkpoint.ModelCheckpoint
        if module == "__builtin__" and name == 'set':
            return set

        # Forbid everything else.
        raise Exception(f"global '{module}/{name}' is forbidden")

Currently the workaround seems to be pass --disable-safe-unpickle to A1111, but is there a way to workaround this? I saw existing ControlNet models all have statedict defined in python file.

@huchenlei use this https://github.com/continue-revolution/sd-webui-segment-anything/blob/master/scripts/sam.py#L79-L83

@huchenlei use this https://github.com/continue-revolution/sd-webui-segment-anything/blob/master/scripts/sam.py#L79-L83

Thanks for pointer! I discussed with AUTO on discord. Issue already resolved.

@huchenlei We will release a new version with onnx. It will not rely on any mmxx.

@huchenlei @yzd-v @continue-revolution
Can you guys please guide me through installing or using this in controlnet iniside A1111?
I'm not using controlnet-nighty as recommanded here
I have controlnet installaed inside A1111 and i just downloaded the pth model  and put it inside
extensions/sd-webui-controlnet/models
and it does not included the yaml file!
can i use the model now? should i set the resolution to 384x288	as model trainde on it?
Thanks
Best regards

@p0mad
This repo is not an A1111 extension. The .pth file is also not an ControlNet model so should not be placed in extensions/sd-webui-controlnet/models.
See https://github.com/Mikubill/sd-webui-controlnet/discussions/1863 for more details on how to use it in A1111 extension. The main branch is rolled back as lvmin does not want to introduce cpp dependency.
Also please submit a new issue instead of continuing the thread here, as this issue is tracking the re-train ControlNet openpose model task.

@huchenlei Now we can avoid installing mmcv through onnxruntime. Could it be available for A1111?

Yes, we also notice the situation. Later we will consider training a new ControlNet model for DWPose.

what happened to this? any updates? Thanks! I realized we have the same problem. (me and thread OP)

@huchenlei use this https://github.com/continue-revolution/sd-webui-segment-anything/blob/master/scripts/sam.py#L79-L83

Thanks for pointer! I discussed with AUTO on discord. Issue already resolved

How was it resolved?  I want to know since aI am having the same problem. Thank you! 🙏🏻

Yes, we also notice the situation. Later we will consider training a new ControlNet model for DWPose.

looking forward to seeing the model soon

where is the new model? thanks

will the loss only care about the image's pose  rather not the original full  image pixel info?


VoxelSniper 7 logging

Is it possible to support logging VoxelSniper 7?

Previous versions of VoxelSniper had no API, but if they're supporting Sponge, Prism will be aware of the block changes automatically.


Flavio Changes and added contribs to data

@kutyel

https://graphql-portfolio-szfqfsrgvv.now.sh/

Apparently everything works 👏🏼 Nice branch name btw 🤣

It shall be merged and the website shall look way cleaner ! Thank you again 🎉

DEPLOYED 🚀

Nice! Although with your branch strategy I think github didn’t recognize any commit as mine and I don’t appear as a contributor to the project 😭🤣😅


'str" object has no attribute 'decode' using sct_deepseg_sc

Description
When running sct_deepseg_sc -i anat/sub-1000032_T2w.nii.gz -c t2
This error appears:

The same thing happens when using t1w image. This was not an issue when using SCT 4.3. Now using SCT master's version.
Steps to Reproduce

Install SCT git-master-c6e489e764ff54244bb5c6abc3a010c6412d520e*

Go into duke/mri/uk_biobank/1000032

Unzip the file, change to BIDS

Run sct_deepseg_sc -i anat/sub-1000032_T2w.nii.gz -c t2

Expected behavior: I was able to succesfully segment this same image before.
Actual behavior: (see screenshot above)

Hi @sandrinebedard. Thank you for reporting this issue. I believe this issue was caused by #2987 and has been fixed recently by #2988.
Could you please try installing the newest version of SCT, v5.0.0? :slightly_smiling_face:

Hi @joshuacwnewton, thanks for the info! I installed the newest version of SCT v5.0.0, and it worked, thanks again :)


0 ^ 0 returns 0

component
forge, chisel
have you ensured that all of these are up to date?

[x] foundry
[x] foundryup

what version of Foundry are you on?
forge 0.2.0 (467aff3 2024-05-19T00:18:50.827112000Z)
describe the bug
0 ^ 0 returns 0 rather than 1 when running forge tests and also when using chisel. this also happens on remix so i'm not sure its a foundry specific bug.

This behavior is determined by Solidity and it is correct behavior of XOR operator

so sorry, yes you are right i mixed it up. i was using yul exp and mistakenly assumed the equivalent to be ^ not **


Error trying to install Ogone version 0.16.0-rc.7 from nest.land

I am part of the Trex development team and we are adding nest.land as our official package registry and testing using Ogone this installation fails.

https://github.com/SRNV/Ogone/blob/8cf79e0d4c180ec6bef86079df68b821e8ac7f3d/src/ogone/compilation/inspection/styles.ts#L2
that part is causing the problem

@buttercubz This looks like an issue with deno-sass or the import done by Ogone.

the error says that you could not import from the src /ogone/compilation/inspection/styles.ts file and that the error occurs on line 2

@buttercubz Created a PR that imports Sass from deno.land/x. Please do check if it works after merging.

@buttercubz 0.16.0-rc.8 should fix this issue.


Seqr es version bump

Does Hail work with ES 7? It uses ES-Hadoop 6.2.4, which does not claim to support ES7.
https://github.com/hail-is/hail/search?q=elasticsearch+spark
https://www.elastic.co/support/matrix#matrix_compatibility

🤞 since we are only using basic export functionality and at the lowest level what that entails is hitting api endpoints that didn't change from version 6 to 7, it should work


question on installation for AWS S3 connector

i am using aws Control tower but want to also integrate into Sentinel since this is our SIEM
is there anything special i should do since all logs already go to a central bucket for the multi account set up
its asking for bucket names
s3 bucket name
kms key name etc
i was trying to use the script i am thinking manual would be better since its setup with control tower basically

2 other things
1 if i want to look at guard duty vpc etc do i need to add them to the connector
2 it looks like its only looking at the s3 bucket but only 1 of the foldes for a specific account not all the individual accounts

Hi @frankscalzo I have a list of steps that can be used in relation to your issue, please go through the following: -

Create an S3 bucket to store your CloudTrail logs if you haven't already done so. You can create this bucket manually or use an existing bucket that you have access to.
Create a KMS key to encrypt the CloudTrail logs if you haven't already done so. You can create this key manually or use an existing key that you have access to.
Configure CloudTrail to send logs to the S3 bucket you created in step 1. You can do this through the AWS Management Console or with the AWS CLI. You will need to specify the bucket name and KMS key name in the CloudTrail configuration.
Configure Sentinel to read CloudTrail logs from the S3 bucket. You will need to specify the bucket name and optionally the KMS key name if you encrypted the logs.
Once you have completed these steps, Sentinel should be able to read the CloudTrail logs from the S3 bucket and you should be able to monitor your AWS Control Tower environment.
Also to answer your other question, Yes, to monitor AWS GuardDuty or VPC flow logs with Sentinel, you will need to add those services to the connector configuration. You can do this by editing the connector configuration file to include the necessary AWS service types, regions, and resources that you want to monitor.
By default, Sentinel will read CloudTrail logs from all the accounts that are associated with the Control Tower landing zone. However, it will only look for logs in the specific S3 bucket and folder that you specify in the connector configuration. If you want to monitor all the individual accounts in your organization, you will need to configure the connector to read CloudTrail logs from each account's S3 bucket and folder. You can do this by adding each account's S3 bucket and folder to the connector configuration using the sources field. I hope this helps in resolving your query, if there is something else please let me know, thanks!

Hi @frankscalzo are you still facing this issue?

Hi @frankscalzo please provide update on this, thanks!

Hi @frankscalzo, Since we have not received a response in the last 5 days, we are closing your issue #7562 as per our standard operating procedures. If you still need support for this issue, feel free to re-open at any time. Thank you for your co-operation.

@v-vdixit Hello , can we reopen this issue please ? I am experiencing a similar issue with ingesting guard duty findings from a guard duty bucket (aggregated findings due to aws orgs etc) , We have noticed that our sqs queues messages are being received and deleted ,but the log data has not been received in the sentinel .
Also , how do you find the ''connector configuration file'' ? we could not find it in the portal


remove chart version in pod labels.

@sdake
Chart.Version should not be in pod labels, as they will break the helm chart upgrade&rollback.
Because if we add Chart.Version to pod labels, the pod can't be selected during upgrade&rollback, as they have different value for Chart.Version.
See:
https://github.com/helm/helm/issues/2494#issuecomment-311691146
https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#selector
@ymesika I know Chart.Version was added to fix https://github.com/istio/istio/issues/8413
Another option is that we add matchedLabel without Chart.Version.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: morvencao
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

install/OWNERS [morvencao]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow//e2e-simpleTests-minProfile.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow//e2e-simpleTests-minProfile.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test e2e-simpleTestsMinProfile

prow/e2e-mixer-no_auth-mcp.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-multicluster-e2e.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/cc @ymesika

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-multicluster-e2e.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test istio-pilot-multicluster-e2e

prow//e2e-simpleTests-minProfile.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-mixer-no_auth-mcp.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test e2e-mixer-no_auth-mcp

prow/istio-pilot-multicluster-e2e.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test istio-pilot-multicluster-e2e

prow//e2e-simpleTests-minProfile.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-simpleTestsMinProfile

prow/e2e-dashboard.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-dashboard

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
5e53c958895f299e010b2e267ccbc88916588bba
link
/test istio-pilot-multicluster-e2e

prow//e2e-simpleTests-minProfile.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-simpleTestsMinProfile

prow/e2e-dashboard.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-dashboard

prow/e2e-mixer-no_auth.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-mixer-no_auth

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao imo we need to remove all these labels related to helm.  Helm will add them during deployment (with tiller iirc) - not sure why we are adding them.  Some have to stay as they were introduced in 1.0.  What I would recommend is diffing 1.0 vs 1.1 and removing all labels that were introcued in the release-1.1 branch, leaving any labels introduced in 1.0 alone.
Labels are expensive in etcd and kubernetes in general.  @costinm had made this request in a different review, but not sure it has made its way to an issue trackier.
I never understood the rationale for adding these labels.  It would be grand if we could get this sorted out prior to 1.1.
Cheers
-steve

As an aside, iirc matchedLabel breaks rollback as @ayj discovered and fixed.  We reverted  a matchedLabel set of changes across the helm charts, so I'm not sure matchedLabel is appropriate either.
I am traveling for the next week (to kubecon) - so I will be fairly unavailable.
Cheers
-steve

@morvencao: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow//e2e-simpleTests-minProfile.sh
0908e26932a46d6a366836fd9b223a38113ad05f
link
/test e2e-simpleTestsMinProfile

prow/e2e-simpleTests-minProfile.sh
477e51121a0178da505513c34f3ba4f8d4be1a36
link
/test e2e-simpleTestsMinProfile

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test istio-pilot-multicluster-e2e

/test e2e-simpleTestsMinProfile


Not working in Android

Hi, I tried exporting to Android but it throws a lot of errors when trying to do that. I assume this addon is not adjusted for android export. Will there be an addition so we can use it for android as well?

@michal-gora I think to use MIDI IN/OUT on Android, maybe the best solution is to use Android's native MIDI API... I think Android 6 and above implemented with midi... I find this information in this articles...
https://midi.org/developing-midi-applications-on-android
https://source.android.com/docs/core/audio/midi


YAML based configuration

PR for #12

Looks great! I added two comments that we should discuss before I accept the PR.

Okay but i don't see your comments 😛

My bad. They were still pending 😄 Now you should be able to see them.

This commit provides more tests for the configuration loader.

Thanks for the contribution! 🥇


Delete artifacts uploaded by actions/upload-artifact@v4

GeekyEggo/delete-artifact@v2 can only delete artifacts uploaded by actions/upload-artifact@v3, not v4.

Till now, two successful ways to delete artifact(s) uploaded by actions/upload-artifact@v4 are demonstrated.
The common part is that an artifact is deleted through
gh api --method DELETE /repos/OWNER/REPO/actions/artifacts/ARTIFACT_ID

see API doc https://docs.github.com/en/rest/actions/artifacts?apiVersion=2022-11-28#delete-an-artifact.
What different is how artifact id is gotten:

Job "Upload artifacts", step "Delete multiple artifacts with gh" uses gh api /repos/OWNER/REPO/actions/runs/RUN_ID/artifacts to get list of first 30 artifacts in a workflow run.
Job "Delete artifacts", step "Delete last artifact" takes an artifact id from upstream job outputs, which comes from a step output.

Other tools

gh extension gh-artifact-purge
Currently works per owner or repository wide, thus slow.
[not checked] other actions to delete artifacts

plugin-rest-endpoint-methods.js provides "one method for each REST API endpoint".
octokit.rest.actions.listWorkflowRunArtifacts({
  owner,
  repo,
  run_id,
});

https://github.com/octokit/plugin-rest-endpoint-methods.js/blob/main/docs/actions/deleteArtifact.md

Supported by GeekyEggo/delete-artifact@v4.
https://github.com/GeekyEggo/delete-artifact/releases/tag/v4.0.0

The ideal solution is that @actions/download-artifact supports a new boolean input to control whether to delete downloaded artifacts in runs.post step.

@actions/checkout uses !!core.getState('isPost') to distinguish main and post states, so it can set main: dist/index.js along with post: dist/index.js. See its action.yml and main.ts.
Compared to GeekyEggo/delete-artifact, actions/download-artifact is much simpler (see download-artifact.ts). It simply  calls methods artifactClient.getArtifact(), artifactClient.listArtifacts(), and artifactClient.downloadArtifact() from @actions/artifact package, which wraps @octokit/core.
Currently @actions/artifact doesn't provide artifactClient.deleteArtifact().


PostgresGrammar@compileColumnExists does not take the connection's schema into account and can return incorrect results.

The current code is:
public function compileColumnExists($table)
{
     return "select column_name from information_schema.columns where table_name = '$table'";
}

The issue is that this function does not take into account the connection's schema so Schema::hasColumn($table, $column) can return incorrect results.
A quick explanation:
Tables:
schema_1.table_name: column_1, column_2
schema_2.table_name: column_1
Connections:
connection_1 -> schema_1
connection_2 -> schema_2
The following call will return an incorrect result:
$hasColumn = Schema::connection('connection_2')->hasColumn('table_name','column_2');
$hasColumn will have an incorrect value of true because compileColumnExists() only checks against the table name when it should check against the table name AND the current connection's schema.

Is fixed in the latest release.

I checked the 5.3 branch and the master branch and the code is still the same, there is no check against the current connection's schema. I'm sure I'm missing something, can you show me where this is addressed?


Filtering Error for User's Company and Department

Company and Department, can have the value of null in a RoleMap. Filtering for such object will crash the app since we can't take the CompanyName attribute from an uninitialized object

record filtering scheme already fixed, search method fixes still ongoing


otherplayer soldier advice

Soldier advice is used for the fortress attacks its the games advice of how many soldiers you should use when performing a fortress attack

Thank you!


Expand all feature and search

I extended the json-formatter-js with a new feature to extend all branches of a displayed tree. And I added possibility to search for a text string in the tree which expands all relevant branches and highlights the searched text portions.

+1 for the search and highlighting feature


Support ASP.NET Core 3.0

You can not define a return type for ConfigureServices in ASP.NET Core 3.0. I got an error on this.
public IServiceProvider ConfigureServices(IServiceCollection services)
{
    ...
}

Can you show me how to use you amazing IoC with ASP.NET Core 3.0 preview 3?

Will try it soon. Thanks for head up.

The docs for the reference:
https://docs.microsoft.com/en-us/aspnet/core/fundamentals/dependency-injection?view=aspnetcore-3.0

@dadhi
Yes, I tried it before, please see the following picture.

.NET Core 3.0.100-preview3-010431
Unhandled Exception: System.NotSupportedException: ConfigureServices returning an System.IServiceProvider isn't supported.
   at Microsoft.AspNetCore.Hosting.Internal.GenericWebHostBuilder.UseStartup(Type startupType, HostBuilderContext context, IServiceCollection services)
   at Microsoft.AspNetCore.Hosting.Internal.GenericWebHostBuilder.<>c__DisplayClass12_0.<UseStartup>b__0(HostBuilderContext context, IServiceCollection services)
   at Microsoft.Extensions.Hosting.HostBuilder.CreateServiceProvider()
   at Microsoft.Extensions.Hosting.HostBuilder.Build()
   at DryIOC.Program.Main(String[] args) in C:\...\DryIOC\Program.cs:line 18

Related link:
Unable to use ConfigureTestServices with StructureMap

Instead of creating the Container in your Startup, you may just move it the host, and make Startup fully IOC agnostic - see deails here: https://github.com/dadhi/DryIoc/issues/94#issuecomment-475605873
In addition, DryIocServiceProviderFactory has couple of optional parameters if you need some customization.

I revert all configs in Startup.cs except AddControllersAsServices

And in Program.cs

Could not load file or assembly 'DryIoc, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=dfbf2bd50fcf7768'. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

This is strange, could you share this sample application with me?

Sure, You can find it here

I tried to build the sample in vs2019 and .NET Core 3 preview 3, and after some quirks got the same error.
Not sure the reason, but it shoud not relate to DryIoc itself. DryIoc is strongly signed now, is it a problem? or is it a binding redirects? Not sure. But won't spend much time on it until RC. If you yave ideas, pleaze help.

I think a possible workaroud would be the use of source code package for DryIoc.MS.DI, which is not existent. Maybe it is time to make it , hmmm...

I have published DryIoc.Microsoft.DependencyInjection.src source package and will try it.

Puzzle solved:

The problem was that the sample project has the same name as the transient dependency (DryIoc).


Logs do not rotate when they hit the max Mb limit

Describe the bug
Since a long time CMS has been experiencing issues with log rotation and disk filling up. Basically logs in log/group_* keeps growing until frontends just fills up the disk.
To Reproduce
Reduce the max_mbytes="10.0" param to a small number and verify logs are not rotated.
Info (please complete the following information):

Priority: high
Stakeholders: CMS
Components: frontend

@mmascher Changes in a0a3413 are incorrect.
self.rollover_not_before is coming from min_days=... />, not max_days. Did you set min_days in your configuration? Default is 0. Leave min_days blank or set it to 0.
For the timed rotation max_days should be used.
If you did not set min_days or the rotation is not performed after min_days then there is a bug somewhere else.

Alternatively we could just use access time instead of modification time:
[mmascher@vocms0804 gwms-frontend]$ stat /var/log/gwms-frontend/group_local_users/local_users.err.log
  File: /var/log/gwms-frontend/group_local_users/local_users.err.log
  Size: 797592    	Blocks: 1568       IO Block: 4096   regular file
Device: fc10h/64528d	Inode: 18613289    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1001/frontend)   Gid: ( 1006/frontend)
Context: system_u:object_r:var_log_t:s0
Access: 2024-11-11 05:19:14.721352019 +0100
Modify: 2024-11-11 09:48:13.883773817 +0100
Change: 2024-11-11 09:48:13.883773817 +0100
 Birth: 2024-11-11 05:19:14.721352019 +0100
[mmascher@vocms0804 gwms-frontend]$ python3
Python 3.9.18 (main, Oct  4 2024, 00:00:00)
[GCC 11.4.1 20231218 (Red Hat 11.4.1-3)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.stat("/var/log/gwms-frontend/group_local_users/local_users.err.log")
os.stat_result(st_mode=33188, st_ino=18613289, st_dev=64528, st_nlink=1, st_uid=1001, st_gid=1006, st_size=797592, st_atime=1731298754, st_mtime=1731314893, st_ctime=1731314893)
>>>
[mmascher@vocms0804 gwms-frontend]$ date -d @1731298754
Mon Nov 11 05:19:14 AM CET 2024
[mmascher@vocms0804 gwms-frontend]$ date -d @1731314893
Mon Nov 11 09:48:13 AM CET 2024

Apparently we can't cet the birthtime in linux, which I find very strange: https://stackoverflow.com/questions/14842195/how-to-get-file-creation-date-time-in-bash-debian


[GH-13262] Extend QuickInput component with 'x' to clear text

Summary

Extend QuickInput component with 'x' to clear text
Ticket Link

Fixes https://github.com/mattermost/mattermost-server/issues/13262
MM-200068
Related Pull Requests

None
Screenshots

None

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 9fc2b1cbb12e0d960e7111d44d9db2b6bab603c2.
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

@ali-farooq0 I added the e2e test, but not the jest test. I am not able to trigger the change on jest so it shows this behaviour. I tried several ways to update the input element so it has a value and therefore show the x, but I was not able to do this on jest. Any ideas on how to do it?

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Mattermost test server updated with git commit b27f05a344dc957963c0bc74065a2b72ccb3663c.
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

New commit detected. SpinWick will upgrade if the updated docker image is available.

@ali-farooq0 I added the e2e test, but not the jest test. I am not able to trigger the change on jest so it shows this behaviour. I tried several ways to update the input element so it has a value and therefore show the x, but I was not able to do this on jest. Any ideas on how to do it?

@larkox Either one works. if you're able to test using e2e that's great as well 👌. I would've thought i'd be easier with jest. Only thing with e2e is that you're utilizing another component to test QuickInput, so it might be better to write a jest test that only tests QuickInput clear functionality.
with jest you could do something like
        const wrapper = shallow(
            <QuickInput
                {...baseProps}
            />
        );

        const instance = wrapper.instance();
        // set input value on instance
        const p = wrapper.find('.input-clear-x')
        // assert p is not empty/null
        instance.handleClear()
        // assert input value is set to empty string
        // assert .input-clear-x span doesn't exist

Test server creation failed. See the logs for more information.

New commit detected. SpinWick will upgrade if the updated docker image is available.

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Mattermost test server updated with git commit d2b2eff989416e8e2563572bb617be7da7a750e1.
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit 3f44a873dd38c24adf78fa616f6c81270d0c161f.
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

New commit detected. SpinWick will upgrade if the updated docker image is available.

Test server creation failed. See the logs for more information.

Test server destroyed

creating a new test server, the previous one was in a deprecated cluster

Creating a new SpinWick test server using Mattermost Cloud.

Mattermost test server created! :tada:
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

Account Type
Username
Password

Admin
sysadmin
Sys@dmin123

User
user-1
User-1@123

New commit detected. SpinWick will upgrade if the updated docker image is available.

Mattermost test server updated with git commit cf977fab29be72ddaa28685069c5e9c690d45f39.
Access here: https://mattermost-webapp-pr-4389.test.mattermost.cloud

Test server destroyed

Creating a new SpinWick test server using Mattermost Cloud.

Test server creation failed. See the logs for more information.


Hubs as home airports does not show on the registration page

When you select Hubs as home airport, it does not show on the registration form, it shows all airports in the database.
Version: 7.0.0-dev+240327.d774ff
To Reproduce
Steps to reproduce the behavior:

go to admin
Click on settings
Scroll down to pilots
check Hubs as Home airport
click on save

Show only the VA's hubs as home airports in the registration form

Probably this is an issue with your theme or view cache as it works on my install as designed.

I use your theme, and i have not made much changes to it, just changed some background images

I dont use that setting myself so it never came up as an issue until i tried it myself

Then I would suggest checking + updating your theme if it is outdated 'cause it works on different servers with different settings / hardware etc...
I can not fix something already working.
(This applies to both default and my theme)


Change Name

Hello, good time, I wanted to change the name of the project or make changes in different parts, if possible, with your permission!

What's the reason for changing the name?


Initializing Phrase Query

hi,
we can use this to initialize stringquery:
QueryContainer qry1 =new QueryStringQuery { DefaultField = "content", Query = @"b" };
How to initialize Pa query for MatchPhrase() ?
Thanks

It's simply a match query of type phrase, so you would initialize it as:
new MatchQuery
{
    Type = "phrase",
    ...
};

A little counter-intuitive though, we should probably have a MatchPhraseQuery that sets the type for you.  We'll think about adding this in the next release, or perhaps in 2.0.

thank you,


Try it on all the other browsers

Only tried on Safari and IE for now, still gotta try Firefox, Chrome, etc.

Early tests on MacBook Pro 64-bit:
Safari 8.0.3 OK
Firefox 33.1.1 OK
Chrome 41.0.2272 OK


Update ACS GA Java Releases

@tophpalmer , @ankitarorabit , @RezaJooyandeh  please take a look to the Java release notes.

Will this update the blog post for March? I assumed these changes would go to the April so they show up in the next Azure SDK blog post.

Yes it will, Reza. The entry blog will be on April (first week)

@g2vinay  is any update or comment on this? Thank you!

These release notes will be on April


Bug GitReleaseManager.yml should be named GitReleaseManager.yaml

The file was not being detected, causing default labels to be used for issue inclusion

This is an invalid bug report as both .yml and .yaml are detected locally. I think GRM is either logging false positives on the missing yaml/yml check or something else is going wrong.


Update Renovate according to kas-ui, srs-ui and kafka-ui

Ui modules of managed services https://github.com/bf2fc6cc711aee1a0c2a usess slightly different renovate configuration as sandbox-ui is using currently.
Renovate community advice to use property for approving upgrades in dashboard https://github.com/renovatebot/renovate/discussions/17426#discussioncomment-3482988

@kelvah done


Using TreeExplainer with an ensemble

Hi,
I have an ensemble that consists of 2n-1 xgb classifiers. The prediction probability is returned as an average of the probabilities that are returned by all the models. My question is, is there a way to use TreeExplainer instead of KernelExplainer to explain the output of such ensemble?
(the reason I can't use KernelExplainer is because of MemoryError, my dataset in memory is around 30GB and with 128GB RAM available it throws the exception)

You can try using TreeExplainer to explain predictions of each classifier individually, and then just calculate average of those individual explanations to obtain final SHAP values.
See here:
https://github.com/slundberg/shap/issues/457#issuecomment-468857321

Thanks!


App not listed in task managers

Your Rocket.Chat.Android version: 1.0.8
We received a notification from one of our users, that rocket.chat+ is not listed in task manager. Further investigation showed that indeed, when one launch such appllication (i.e. Advanced Task Manager), the rocket.chat+ is not there.

Is this a 3rd party application you're using to try and view running applications?  When Rocket.Chat is in the background it shouldn't be doing anything.  So might not show up as a background application by a 3rd party application.

Weired: currently it seems that my task app. sees Rocket Chat+ corectly - so it might false alarm. Please give me 24hours to confirm this behavior (that everything is fine) with our employee.
After that I'll give more feedback (or just the info to close the issue).

After consulting the user: false alarm. Issue can be safely closed.


Publish tmLanguage as a Sublime Text package?

I can understand if you don't want to ("support my package manager!" bugs suck), but it'd make things easier for some of us.

Any news on this?

Nope. Cleanup is even more necessary now, as I haven't updated the file in a long time, and I still need to actually figure out how to publish it.

@tabatkins the way I set this up is by "Add Repository" pointing to your github. This way I'm getting any upstream fixes/followups to the syntax file. I think it works similarly for "publishing" the package - it still gets tied to your github, and you keep working on improving the syntax There is no downside of registering the package today.

Oh dang, so you're saying i can just register my repo in Sublime's package manager and it works without extra effort on my part?

Yeah, see https://packagecontrol.io/docs/submitting_a_package#Step_4
Registering just requires you to point to this github (although, it might make sense to use a separate repo). Versioning is with tags.


get and post issue

When entering my website's login section via web browsers, it works fine, but in the webview package, it redirects as a GET request instead of a POST request, so I can't log in using the webview package.

Setting custom headers on POST requests
Currently, setting custom headers when making a post request with the WebViewController's loadRequest method is not supported on Android. If you require this functionality, a workaround is to make the request manually, and then load the response data using loadHtmlString instead.
How can I use it?

I found that I couldn't login into https://www.facebook.com/    either,
I fix it, and upload to pub.dev
Please try with the latest version and let me know if it work for you.
dependencies:
  webview_win_floating: ^2.2.3

Problem solved, thank you very much