chore: release main

:robot: I have created a release beep boop
autonat: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

bootstrap: 11.0.8
11.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

circuit-relay-v2: 2.1.4
2.1.4 (2024-10-09)
Bug Fixes

emit 'listening' when relays change (#2758) (0d326d1)
use keep-alive as a tag prefix (#2757) (29b47ad)

Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/peer-record bumped from ^8.0.7 to ^8.0.8
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

crypto: 5.0.5
5.0.5 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3

dcutr: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devtools-metrics: 1.1.6
1.1.6 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/simple-metrics bumped from ^1.2.3 to ^1.2.4

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5

echo: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1

fetch: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

floodsub: 10.1.6
10.1.6 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/pubsub bumped from ^10.0.7 to ^10.0.8

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

identify: 3.0.8
3.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/peer-record bumped from ^8.0.7 to ^8.0.8
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

interface: 2.1.3
2.1.3 (2024-10-09)
Bug Fixes

emit 'listening' when relays change (#2758) (0d326d1)
use keep-alive as a tag prefix (#2757) (29b47ad)

interface-compliance-tests: 6.1.6
6.1.6 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/multistream-select bumped from ^6.0.5 to ^6.0.6
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

interface-internal: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8

kad-dht: 14.0.1
14.0.1 (2024-10-09)
Bug Fixes

use keep-alive as a tag prefix (#2757) (29b47ad)

Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-store bumped from ^11.0.7 to ^11.0.8

keychain: 5.0.7
5.0.7 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1

logger: 5.1.1
5.1.1 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3

devDependencies

@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

mdns: 11.0.8
11.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

mplex: 11.0.8
11.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

multistream-select: 6.0.6
6.0.6 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1

peer-collections: 6.0.8
6.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5

peer-id: 5.0.5
5.0.5 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3

peer-record: 8.0.8
8.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

peer-store: 11.0.8
11.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/peer-record bumped from ^8.0.7 to ^8.0.8

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1

perf: 4.0.8
4.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

ping: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

plaintext: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

pnet: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

prometheus-metrics: 4.2.2
4.2.2 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

pubsub: 10.0.8
10.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/logger bumped from ^5.1.0 to ^5.1.1

simple-metrics: 1.2.4
1.2.4 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

tcp: 10.0.9
10.0.9 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

tls: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

upnp-nat: 2.0.8
2.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

utils: 6.1.1
6.1.1 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

devDependencies

@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5

webrtc: 5.0.12
5.0.12 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/circuit-relay-v2 bumped from ^2.1.3 to ^2.1.4
@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/identify bumped from ^3.0.7 to ^3.0.8
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/websockets bumped from ^9.0.7 to ^9.0.8
libp2p bumped from ^2.1.7 to ^2.1.8

websockets: 9.0.8
9.0.8 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/logger bumped from ^5.1.0 to ^5.1.1

webtransport: 5.0.12
5.0.12 (2024-10-09)
Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/ping bumped from ^2.0.7 to ^2.0.8
libp2p bumped from ^2.1.7 to ^2.1.8

libp2p: 2.1.8
2.1.8 (2024-10-09)
Bug Fixes

emit 'listening' when relays change (#2758) (0d326d1)
use keep-alive as a tag prefix (#2757) (29b47ad)

Dependencies

The following workspace dependencies were updated

dependencies

@libp2p/crypto bumped from ^5.0.4 to ^5.0.5
@libp2p/interface bumped from ^2.1.2 to ^2.1.3
@libp2p/interface-internal bumped from ^2.0.7 to ^2.0.8
@libp2p/logger bumped from ^5.1.0 to ^5.1.1
@libp2p/multistream-select bumped from ^6.0.5 to ^6.0.6
@libp2p/peer-collections bumped from ^6.0.7 to ^6.0.8
@libp2p/peer-id bumped from ^5.0.4 to ^5.0.5
@libp2p/peer-store bumped from ^11.0.7 to ^11.0.8
@libp2p/utils bumped from ^6.1.0 to ^6.1.1

devDependencies

@libp2p/circuit-relay-v2 bumped from ^2.1.3 to ^2.1.4
@libp2p/identify bumped from ^3.0.7 to ^3.0.8
@libp2p/interface-compliance-tests bumped from ^6.1.5 to ^6.1.6
@libp2p/mplex bumped from ^11.0.7 to ^11.0.8
@libp2p/plaintext bumped from ^2.0.7 to ^2.0.8
@libp2p/tcp bumped from ^10.0.8 to ^10.0.9
@libp2p/websockets bumped from ^9.0.7 to ^9.0.8

This PR was generated with Release Please. See documentation.

:robot: Created releases:

plaintext-v2.0.8
tls-v2.0.8
crypto-v5.0.5
interface-v2.1.3
interface-compliance-tests-v6.1.6
interface-internal-v2.0.8
kad-dht-v14.0.1
keychain-v5.0.7
libp2p-v2.1.8
logger-v5.1.1
devtools-metrics-v1.1.6
prometheus-metrics-v4.2.2
simple-metrics-v1.2.4
multistream-select-v6.0.6
peer-collections-v6.0.8
bootstrap-v11.0.8
mdns-v11.0.8
peer-id-v5.0.5
peer-record-v8.0.8
peer-store-v11.0.8
pnet-v2.0.8
autonat-v2.0.8
dcutr-v2.0.8
echo-v2.0.8
fetch-v2.0.8
identify-v3.0.8
perf-v4.0.8
ping-v2.0.8
pubsub-v10.0.8
floodsub-v10.1.6
mplex-v11.0.8
circuit-relay-v2-v2.1.4
tcp-v10.0.9
webrtc-v5.0.12
websockets-v9.0.8
webtransport-v5.0.12
upnp-nat-v2.0.8
utils-v6.1.1
:sunflower:


Increasing __C.TRAIN.MAX_SIZE results in Tensorflow size check error

Hi all,
Attempting to increase the __C.TRAIN.MAX_SIZE to anything above 1280 results in a Tensorflow error:
tensorflow/core/framework/tensor_shape.cc:172] Check failed: size >= 0 (-8105164288 vs. 0)
Some dimension becomes less than zero at some point?
This is the same behaviour when increasing __C.TEST.MAX_SIZE.
Increasing __C.TRAIN.SCALES or __C.TEST.SCALES does not result in any error. Is there a maximum image size that can be taken?

Actually increasing __C.TEST.MAX_SIZE to anything above 1000 results in the same error.


vim-tiny fails on CTRL-X/CTRl-A

Problem:  vim-tiny fails on CTRL-X/CTRl-A
(Rob Foehl, after 9.1.0172)
Solution: After changing the line in del_bytes, invalidate
the cached textlen value

@zeertzjq for approval please

How about just moving the two #ifdefs below? (ml_line_length does seem to need change as well)
diff --git a/src/change.c b/src/change.c
index dacc06fd4..72d01c51a 100644
--- a/src/change.c
+++ b/src/change.c
@@ -1355,17 +1355,17 @@ del_bytes(
     mch_memmove(newp + col, oldp + col + count, (size_t)movelen);
     if (alloc_newp)
 	ml_replace(lnum, newp, FALSE);
-#ifdef FEAT_PROP_POPUP
     else
     {
+#ifdef FEAT_PROP_POPUP
 	// Also move any following text properties.
 	if (oldlen + 1 < curbuf->b_ml.ml_line_len)
 	    mch_memmove(newp + newlen + 1, oldp + oldlen + 1,
 			       (size_t)curbuf->b_ml.ml_line_len - oldlen - 1);
+#endif
 	curbuf->b_ml.ml_line_len -= count;
 	curbuf->b_ml.ml_line_textlen = 0;
     }
-#endif

     // mark the buffer as changed and prepare for displaying
     inserted_bytes(lnum, col, -count);

thanks, makes sense.


Add optional --env or -e parameter to gulp watch

This will trigger the jigsaw build with the correct environment variable and also the browserSync to serve from the correct source dir.

Thanks Pete!

This PR reverts the changes from #28. Was this intended?

@driesvints Ah nope, I messed that up in the merge :( Sorry, will fix now.

No worries! :)


Wazuh Indexer's plugins / extensions development research

Description
Having finished the set-up phase of the wazuh-indexer fork (#1 and #54), we are now beginning a new phase in which we would like to extend the Indexer's capabilities and functionalities by generating our own code in the form of plugins and/or extensions.
However, we are not familiar with the plugins' ecosystem, lifecycle nor have a proper environment to get started. We need to gather this information and elaborate guides, environments and tests that can get us on the right track to start building traction and value, specially in view of the next major version of Wazuh.
Tasks

[x] Study how extensions work and elaborate a brief developer guide
[ ] Research about plugin's set up, folder and project structure. Check these repos:

https://github.com/opensearch-project/opensearch-plugin-template-java
https://github.com/opensearch-project/opensearch-plugins

[ ] Research about testing on plugins.
[ ] Research about plugin's compilation (Gradle build projects)
[ ] Research about plugin's building (generation of packages) (maven)
[ ] Create a development environment based on Docker (check if our existing environments can be reused or extended)
[ ] Create a plugin that exposes a CRUD API as a Proof of Concept

Notes

Plugins are installed and loaded when OpenSearch starts.
As the plugins are class-loaded during the node bootstrap, the extension points (defined by the plugin interface) initialize the data structures. This design of loading plugins during the node bootstrap prevents them being loaded on the fly and cannot be hot-swapped. Each node within the cluster has to be restarted to reload a new plugin.
Extension points enable plugins to hook into various events within the cluster and data lifecycles in OpenSearch. The default extension points are defined by Plugin.java abstract class.
Extensions are registered through the below REST request within OpenSearch.curl -XPOST "localhost:9200/_extensions/initialize" -H "Content-Type:application/json" --data '{ \
"name":"hello-world", \                 // extension name
"uniqueId":"hello-world", \             // identifier for the extension
"hostAddress":"<IP_ADDRESS>", \            // host address
"port":"4532", \                        // port number
"version":"1.0", \                      // extension version
"opensearchVersion":"3.0.0", \          // the OpenSearch version with which the extension is compiled
"minimumCompatibleVersion":"3.0.0", \   // minimum version of OpenSearch with which the extension is wire compatible
"dependencies":[{"uniqueId":"test1","version":"2.0.0"},{"uniqueId":"test2","version":"3.0.0"}] \  // required extensions for the host extension
}'

Bibliography

https://opensearch-project.github.io/opensearch-sdk-java
https://opensearch.org/blog/plugins-intro/

The basic folder structure of a plugin seems to be as follows:
root@ubuntu2204:~/opensearch/extensions/samples/example-rest# tree
.
├── build.gradle
├── gradle
│   └── wrapper
│       ├── gradle-wrapper.jar
│       └── gradle-wrapper.properties
├── gradlew
├── gradlew.bat
├── LICENSE
├── NOTICE.txt
├── README.md
├── settings.gradle
└── src
    ├── main
    │   └── java
    │       └── org
    │           └── opensearch
    │               └── rest
    │                   └── action
    │                       ├── HelloWorldPlugin.java
    │                       ├── HelloWorldService.java
    │                       └── RestHelloWorldAction.java
    ├── test
    │   └── java
    │       └── org
    │           └── opensearch
    │               └── rest
    │                   └── action
    │                       └── HelloWorldPluginTests.java
    └── yamlRestTest
        ├── java
        │   └── org
        │       └── opensearch
        │           └── rest
        │               └── action
        │                   └── HelloWorldClientYamlTestSuiteIT.java
        └── resources
            └── rest-api-spec
                ├── api
                │   └── _plugins.hello_world.json
                └── test
                    └── _plugins.hello_world
                        ├── 10_basic.yml
                        └── 20_hello_world.yml

I was able to get the tutorial plugin to pass its tests using Intellij IDEA with the following environment:
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 8.5
  OS Info               : Linux 6.1.0-21-amd64 (amd64)
  JDK Version           : 21 (Amazon Corretto JDK)
  JAVA_HOME             : /home/fede/.jdks/corretto-21.0.3
  Random Testing Seed   : 60F01E67EE6D8FC
  In FIPS 140 mode      : false
=======================================

The tests do throw lots of warnings at the moment, though:
> Task :yamlRestTest
May 21, 2024 3:45:11 PM sun.util.locale.provider.LocaleProviderAdapter <clinit>
WARNING: COMPAT locale provider will be removed in a future release
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.opensearch.bootstrap.BootstrapForTesting (file:/home/fede/.gradle/caches/modules-2/files-2.1/org.opensearch.test/framework/2.14.0-SNAPSHOT/a4475265569f8ccef4a62a9e31fef43772d3d506/framework-2.14.0-SNAPSHOT.jar)
WARNING: Please consider reporting this to the maintainers of org.opensearch.bootstrap.BootstrapForTesting
WARNING: System::setSecurityManager will be removed in a future release
[2024-05-21T14:45:13,389][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/20_hello_world/With name] before test
[2024-05-21T14:45:13,483][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] initializing REST clients against [http://<IP_ADDRESS>:39337]
[2024-05-21T14:45:13,864][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] initializing client, minimum OpenSearch version [2.14.0], cluster-manager version, [2.14.0], hosts [http://<IP_ADDRESS>:39337]
[2024-05-21T14:45:13,994][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/20_hello_world/With name] after test
[2024-05-21T14:45:14,009][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/20_hello_world/Default with no name] before test
[2024-05-21T14:45:14,046][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/20_hello_world/Default with no name] after test
[2024-05-21T14:45:14,051][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/10_basic/Test that the plugin is loaded in OpenSearch] before test
[2024-05-21T14:45:14,091][INFO ][o.o.r.a.HelloWorldClientYamlTestSuiteIT] [test] [yaml=_plugins.hello_world/10_basic/Test that the plugin is loaded in OpenSearch] after test
WARNING: A terminally deprecated method in java.lang.System has been called
WARNING: System::setSecurityManager has been called by org.gradle.api.internal.tasks.testing.worker.TestWorker (file:/home/fede/.gradle/wrapper/dists/gradle-8.5-bin/5t9huq95ubn472n8rpzujfbqh/gradle-8.5/lib/plugins/gradle-testing-base-8.5.jar)
WARNING: Please consider reporting this to the maintainers of org.gradle.api.internal.tasks.testing.worker.TestWorker
WARNING: System::setSecurityManager will be removed in a future release
> Task :check
BUILD SUCCESSFUL in 25s
26 actionable tasks: 25 executed, 1 up-to-date
3:45:14 PM: Execution finished 'check'.

My next steps will be trying to get the plugin from the tutorial into opensearch's plugin template.

After some fiddling with Intellij's IDEA, I got the blog's example to build and bring up a test environment:

I've managed to migrate the opensearch-plugin-template-java to Kotlin, and made it work with the latest OpenSearch version to date (2.14.0) and Java 21, using IntelliJ IDEA.
During the last two days, I've been reading about Kotlin, Gradle and OpenSearch plugins, taking notes that will be the backbone of our documentation to develop plugins for the wazuh-indexer.
In order to better understand how plugins work, and their ecosystem, I'm going to develop a simple plugin to manage ToDos, using an index.

Re: Create a development environment based on Docker
This is not needed as IntelliJ IDEA bundles a JRE 17, which is able to run the plugins. Gradle takes care of the rest: using a snapshot version of OpenSearch to run the plugin.


logstash: Adding volumes configuration property for Logstash statefulset

What this PR does / why we need it:
This PR allows users of the Logstash chart to specify volumes they wish to define in the Logstash statefulset. This functionality would allow a user to, for example, place custom certificate authorities and configure Logstash to use them.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
None
Special notes for your reviewer:
None

@CharlieC3 I am not completely sure but I think the already existing VolumeMounts variable will do what you need.

To use a volume, a Pod specifies what volumes to provide for the Pod (the .spec.volumes field) and where to mount those into Containers (the .spec.containers.volumeMounts field).

This PR is needed if you want to mount extra volumes in the pod.

@christian-roggia You are correct, my oversight. I've moved the volumes property to be under spec, rather than spec.containers following this doc:
https://kubernetes.io/docs/concepts/storage/volumes/
@rendhalver From what I've been able to find in the Kubernetes docs, the only way to mount a secret or configmap into a pod is to define it in a volume in the pod (or statefulset in this case), then reference it in the volumeMounts property. Is there another way you know of which is possible in the Logstash chart?

Ah good point.
Since the two are linked can we use the same variables to configure each?

@rendhalver Hmm, I'm not sure how I would do that. While volumes can be used in volumeMounts, I wouldn't consider one dependent on the other. They're also populated with different types of data (e.g. the array under the volumeMounts section can't be copied and pasted under the volumes section). Also, as Christian pointed out earlier I think it's worthy to mention volumes does not fall under the same YAML property as volumeMounts.
I think the way the change is now matches the pattern laid out by the other properties and makes sense, but if you have any specific changes you'd like me to make I'd be happy to do so.

@rendhalver @christian-roggia
Are there any other concerns or questions I can address? Hoping we can merge this in by the end of this week if possible.

/ok-to-test

Apologies for the late commit, realized I didn't update the template syntax when I moved the volumes property under the spec property in my 2nd commit.

/lgtm


Subscription processes hangs forever

Hi,
Publish process publishes only 2 messages. Ran subscription process on my local and messaged processed successfully. 2nd time I ran the subscription process once again on my local and there is no messages but the subscription process hangs forever. Can you please explain why?
I am using google pub-sub version 0.21.1-beta.

I think I've been seeing this issue in production as well. Same version as above. However it's only in one of our services. How can I help debug this issue? I've seen similar behaviour? And it happens 1-5 times per day.

Similar issue on 0.22.0-beta. As a test I set up a job to publish messages to a topic every 30 seconds. Subscription will receive messages, every 30 seconds, for a period of time and then suddenly stop receiving messages for hours. Subscriber.Listener does not trigger any callbacks when this occurs. Sometimes it recovers sometimes it does not. Spring Boot app hosted on GKE.

Need to verify if this is a reliability bug or not.

@bisws007 Could you share the code you're using to subscribe? Generally the subscriber won't stop until you call subscriber.stopAsync().
In v0.21, there was a bug that could cause messages to be stuck in the subscriber that prevents termination. That bug has been fixed now. Do you think you can try again with v0.26?

I'll close this for now due to age. Please reopen if required.


remove reader study script

Fix reader study dates
Remove script for fixing reader study dates

@brianhelba double check this is correct before I remove it from the repo (it's already applied).


Setup OneLocBuild in Aspire repo

https://github.com/dotnet/arcade/blob/9a7b1d30fd536da1b71d74b184e857ee96c12a76/Documentation/OneLocBuild.md?plain=1#L14

We are in the process of enabling this now. I have created a test build for OneLocBuild by following these instructions, and we are currently waiting for an LclPackageId from the Localization team in order to put up the PR for enabling it.


Remove Objective-C related code

In few classes I should remove NSObject inheritance.
I left it because some of them requires functionality of NSObject by default, e.g.: Hashable, Equatable, debugDescription and description
I'll remove it in separate PR

Ah, and I think it would also be good to remove references to Objective-C from README.md and CONTRIBUTING.md.

Ah, and I think it would also be good to remove references to Objective-C from README.md and CONTRIBUTING.md.

here 81583a1da7061e2a0daa64fb581cf5c08cbe030d

There seems to be a problem with the assemble GitHub workflow – you haven't removed the Objective-C examples from Scripts/assemble.sh but the workflow is still passing. Looking at the workflow logs, there are definitely things failing inside that script. I think you'll need to investigate why workflow isn't hence failing.

@lukasz-szyszkowski from what I can tell, you've removed the Objective-C build steps, but not made any changes to the rest of the build process. But were you able to investigate why the failure of these build steps didn't cause the CI job to fail? Because it seems like there might be a broader problem. If not something you want to fix here, I think it definitely needs an issue.

There seems to be a problem with the assemble GitHub workflow – you haven't removed the Objective-C examples from Scripts/assemble.sh but the workflow is still passing. Looking at the workflow logs, there are definitely things failing inside that script. I think you'll need to investigate why workflow isn't hence failing.

@lukasz-szyszkowski from what I can tell, you've removed the Objective-C build steps, but not made any changes to the rest of the build process. But were you able to investigate why the failure of these build steps didn't cause the CI job to fail? Because it seems like there might be a broader problem. If not something you want to fix here, I think it definitely needs an issue.

To be honest, I don't know what you mean, there are two commits:
https://github.com/ably/ably-asset-tracking-swift/pull/219/commits/b40d1fa2472a89845d37775e13630befcd0a4118 remove building objc examples
https://github.com/ably/ably-asset-tracking-swift/commit/81583a1da7061e2a0daa64fb581cf5c08cbe030d remove references to objc in README and CONTRIBUTING

To be honest, I don't know what you mean

So, my original comment was this:

There seems to be a problem with the assemble GitHub workflow – you haven't removed the Objective-C examples from Scripts/assemble.sh but the workflow is still passing. Looking at the workflow logs, there are definitely things failing inside that script. I think you'll need to investigate why workflow isn't hence failing.

So what I'm saying is that when I wrote that comment, the following three things were all true:

the Objective-C examples no longer existed;
the assemble GitHub workflow still contained commands to try and build the Objective-C examples;
the CI build was green.

I was saying that we need to understand why the CI build was passing even though the Objective-C examples no longer existed. It suggests that the script might not be correctly checking for the failure of its build steps.

To be honest, I don't know what you mean

So, my original comment was this:

There seems to be a problem with the assemble GitHub workflow – you haven't removed the Objective-C examples from Scripts/assemble.sh but the workflow is still passing. Looking at the workflow logs, there are definitely things failing inside that script. I think you'll need to investigate why workflow isn't hence failing.

So what I'm saying is that when I wrote that comment, the following three things were all true:

the Objective-C examples no longer existed;
the assemble GitHub workflow still contained commands to try and build the Objective-C examples;
the CI build was green.

I was saying that we needed to understand why the CI build was passing even though the Objective-C examples no longer existed. It suggests that the script might not be correctly checking for the failure of its build steps.

Good catch! Thanks.
PR for this https://github.com/ably/ably-asset-tracking-swift/pull/226
POC here https://github.com/ably/ably-asset-tracking-swift/pull/224

Why does it fail?


Feat router completion item provider

Codecov Report

Merging #35 into master will increase coverage by 2.02%.
The diff coverage is 51.66%.

@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
+ Coverage   47.56%   49.59%   +2.02%
==========================================
  Files          23       25       +2
  Lines         679      736      +57
  Branches       89       96       +7
==========================================
+ Hits          323      365      +42
- Misses        342      353      +11
- Partials       14       18       +4

Impacted Files
Coverage Δ

...letionItemProvider/routerCompletionItemProvider.ts
0% <0%> (ø)

src/extension.ts
0% <0%> (ø)
:arrow_up:

src/test/common/document/index.test.ts
100% <100%> (ø)
:arrow_up:

src/common/document.ts
80.76% <100%> (+17.94%)
:arrow_up:

src/common/utils.ts
75.43% <100%> (+6.54%)
:arrow_up:

src/test/common/utils/getAllPages/index.test.ts
100% <100%> (ø)

Continue to review full report at Codecov.

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


Slooooowness

I just started to get into Metadatamenu. It is totally changing my work flow and is amazing. The issue, I'm having is that my system now seems to get very significant lags.  I wondering if there are any ideas on how to speed it up.
I wonder if it has something to do with the queries I set up for selecting fields.  Any pointers would be amazing.
Here is an example.

Those queries look fine.
Even if they return loads of results, they are executed when the corresponding field modal is triggered: so this won't affect the overall performance.
Things that take time (and cpu):
Indexing the "managed fields" fir each single note. Done for all files at start and for a file each time this file is changed.
During this process the whole file is parsed.
If you have long files it will take a lot of time.
If your metadata only live in frontmatter (and not inline with the dataview key::value syntax) you can set scope : frontmatter only in the settings. The plugin will limit the parsing to the frontmatter and this could accelerate the process by a lot

mdelabelle - thank you so much. I already had it set to search frontmatter only but was super slow.
I wound up turning "auto calculation" off and it is much zippier.
Wondering if auto calculation is off, do I need to close obsidian and reopen to have it recalculate the index? Not totally clear yet on what I'm losing from toggling this off.

Great. To refresh on demand, just use the "update all lookups and formulas" command

Moving it to the discussion section in case someone experience the same situation


Suggested edits to DMSN Contribute page

CONTRIBUTE (https://dataoneorg.github.io/Education/CONTRIBUTING)
To address passive voice and an escaping period, CHANGE Intro Statement to:
"This document details our recommended processes and tool to update current content, suggest changes to content, and fork content for your own use, as well as an introduction to how the content is organized.
Thank you for your interest in contributing to these educational materials. This repository was developed by the DataONE Community Engagement and Outreach Working Group and continues to be maintained by members of this team."
In general, I strongly recommend ridding ourselves of the "ings" and extra descriptors to make this page stronger.
For example, the sentence "Forking and editing content through GitHub, rather than downloading and privately editing, enables others to use your edited content and track how these materials are being used." could/should become, "Fork and edit content through GitHub, rather than editing privately, enables others to use your edited content and to track how these materials are used."
We won't get 'em all, but we can sure make it stronger. This is true of all pages, not just CONTRIBUTE.

Suggestions above incorporated. Another review for voice consistency would be valuable.

It looks pretty good to me - nicely done. Not critical, but the only sentences that I would recommend changes to is below - and it is just re-ordering the two sentences:
"Thank you for your interest in contributing to these educational materials. This repository was developed by the DataONE Community Engagement and Outreach Working Group and continues to be maintained by members of this team."
-to-
"This repository was developed by the DataONE Community Engagement and Outreach Working Group and continues to be maintained by members of this team. Thank you for your interest in contributing to these educational materials."

Suggestion incorporated. Leaving the issue open for more eyes.


Feature/#2006 chat changes

This pull request is in response to #2006.
It is trying to use the event bus to modify elements of the chatUserItem and remove calls to the various services from chatUserItemController.
This will hopefully reduce the cpu usage as currently all the services are called for all users whenever the chat user list changes and with this they will not be associated with the specific cell but rather the chat user.

Currently I have it so that everything is initialized fine still need to add events/make sure when changes happen they are reflected properly

Alright this should be fully functional now however still need to do unit tests

Tested this. Now I'm stuck on an endless "Connecting to chat". Doesn't happen on develop.

Recent commit should have fixed the endless connecting. Seemed to be a race condition so added back the user change listener

Yep, works again

Potentially addresses #1892


Use &block as argument for all constructor

Prefer &block rather than block for all constructor
Add custom error if developer didn't specify block to be passed
into constructor.
Use assert_nil for Minitest
Add .gitignore for emacs

Hi @zerosign,
Thanks for contributing with rack-attack!
It seems like the &block changes are mixed with other unrelated changes. I find it better for everyone if different changes are part of different pull requests, which makes code review easier, and can keep discussions focused on one particular concern at a time.
That said, can you please either change this PR or open a new one just with the &block changes?
Thanks again!

hi @grzuy, ok,  I'll try to update this branch soon

Thank you @zerosign. Let me know if you need any help.

Closing for now.
You can re-open on a separate one once you update the branch.
Thank you again!


onPause error

Service edu.rit.se.wifibuddy.WifiDirectHandler has leaked IntentReceiver edu.rit.se.wifibuddy.WifiDirectHandler$WifiDirectBroadcastReceiver@1494eee1 that was originally registered here. Are you missing a call to unregisterReceiver()?

I think I caused that

Should be fixed, will merge soon

Fixed in #164 , closing...


HDDS-3371. Cleanup of old write-path of key in OM

What changes were proposed in this pull request?
When the OM-HA code was added, the tests were not completely updated.  Many of them still call the OzoneManagerProtocol "write-path" methods even though those methods have been superseded by the HA methods.  For this reason the obsolete protocol methods in the OzoneManager class could not be removed.
This PR replaces all those obsolete methods with default methods in OzoneManagerProtocol.java that just throw an UnsupportedOperationException.
It also fixes the tests broken by those changes.
A draft copy of this PR was commented on by @bharatviswa504  and @cxorm but it was too out of date,  so I closed it:
https://github.com/apache/ozone/pull/2629
and created the current one.
Unremoved methods
The following methods are in the OzoneManager class, on the write path.  They were not removed because they are invoked from within the OmRequest subclasses:
OzoneManager::finalizeUpgrade
OzoneManager::getDelegationToken
OzoneManager::renewDelegationToken
OzoneManager::cancelDelegationToken

Other dead code removed
In my testing, I noticed a couple of other methods that are no longer used and removed them as well:
OzoneManager::checkVolumeAccess is unsupported in the VolumeManagerImpl
OzoneManagerRequestHandler::allocateBlock is a private method that is not called from anywhere
Complex Fixes
Most of the broken tests were easy to fix.  Basically any the tests that invoked the removed methods directly from the OzoneManager.class were modified to invoke them from an OzoneManager client.  There were a couple of difficult areas:
TestOmMetrics class
These tests verify that the correct number of metrics are being generated.  Most of them use mocks invoked by the methods removed in this PR.  So they had to be significantly restructured.  In most cases the mocks had to be replaced with a miniCluster, (because there is no other way to generate the metrics.)
My goal was to fix the tests so the number of metrics would not change.  I was able to do that in all cases except one. One of the tests uses the checkVolumeAccess() method, which was removed months ago, (as mentioned above).  The old mocks were incorrectly ignoring the exception it has been generating. So I removed it from the test and corrected the corresponding counts.  The rest of the counts are unchanged.
listStatus() race condition in TestOzoneFileSystem::testListStatusWithIntermediateDir
Under certain circumstances, listStatus() fails to return an intermediate directory if the key containing it hasn't yet been transferred from the cache to the keyTable.  This race did not occur prior to this PR because the test was using the pre-HA version which doesn't use the cache.
Since the test passes when the key is in the table, I fixed it by sleeping/retrying, but it is possible that listStatus() itself should be modified so a read from the cache works the same as a read from the keyTable.  The details of the race are a bit complicated, but explained below.
listStatus() race condition details
In commitKey OmRequest, a key is first written to the keyTableCache and then to the keyTable when the double buffer is flushed.
If OZONE_OM_ENABLE_FILESYSTEM_PATHS is enabled, and the key has a superdirectory, thesuperdirectory's are added to cache during the openKey OmRequest
If OZONE_OM_ENABLE_FILESYSTEM_PATHS is not enabled, the superdirectories are not added in the openkey request.  In addition, the cache search method in listStatus() is written to skip any keys with an embedded "/" here
So, if OZONE_OM_ENABLE_FILESYSTEM_PATHS is disabled, and a key with an embedded "/" is commited, and it is still in the cache, listStatus() won't see it or it's superdirectory.
listStatus() does return the directory when it gets flushed to the table, so sleeping for a bit fixes the problem.
I've only noticed this happening on one test and only 20% of the time.  (I've put a sleep in to handle that case.)  But we should discuss if that is good enough.
Genesis Broken in Master
ozone genesis -b BenchMarkOzoneManager uses the pre-HA code and so should also be updated for these changes.
It is currently broken in the master branch.  It generates this exception when I try to run it in master:
org.apache.hadoop.metrics2.MetricsException: Metrics source DBCheckpointMetrics already exists!

I think that error will need to be fixed before I can update it, so I've left it out of this PR.  Let me know if that's a problem.
Since the CI tests don't run Genesis, the lack of updates don't cause the tests to fail.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3371
How was this patch tested?
All effected tests were updated and all pass without fail.
I timed all the changed tests. Before the changes, they took 12 minutes on average.  Now they take 12.5 minutes on average.
I ran the CI 12 times each on master and on this branch.  Both branches failed 6 times.  While there was some overlap in the failures, some were unique to master and some to this branch.
As best I could tell, none of the failures were related to these changes, but it is hard to be sure.

@bharatviswa504  and @cxorm here is the updated PR.
Please take a look when you get a chance.
Thanks!

In commitKey OmRequest, a key is first written to the keyTableCache and then to the keyTable when the double buffer is flushed.
If OZONE_OM_ENABLE_FILESYSTEM_PATHS is enabled, and the key has a superdirectory, thesuperdirectory's are added to cache during the openKey OmRequest
If OZONE_OM_ENABLE_FILESYSTEM_PATHS is not enabled, the superdirectories are not added in the openkey request. In addition, the cache search method in listStatus() is written to skip any keys with an embedded "/" here
So, if OZONE_OM_ENABLE_FILESYSTEM_PATHS is disabled, and a key with an embedded "/" is commited, and it is still in the cache, listStatus() won't see it or it's superdirectory.

I think if filesystem path is disabled, then it is Object store kind of bucket. On ObjectStore kind of buckets, we donot need to support FS API's like listStatus. And from reading code I think to skip after Stripping "/" at end is as recursive false, We donot need to print 2 level deeper child. As the issue here is for OBS, we donot create intermediate dirs that is the reason this logic of search with the below code is failing to find in cache (As in cache we donot find any intermediate dirs). If we want to fix this for OBS buckets, we should have similar logic getChild like here(https://github.com/apache/ozone/blob/master/hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/KeyManagerImpl.java#L2411)
Or another way to fix the test is listKeys. Which is an Object Store API.
            String remainingKey = StringUtils.stripEnd(cacheKey.substring(
                startCacheKey.length()), OZONE_URI_DELIMITER);
            // For non-recursive, the remaining part of key can't have '/'
            if (remainingKey.contains(OZONE_URI_DELIMITER)) {
              continue;

cc @rakeshadr @smengcl for any comments.

another way to fix the test is listKeys.

@bharatviswa504 I'm ok with using listKeys(), but the name of the test that is failing is: testListStatusWithIntermediateDir
so it seems a bit weird not to use listStatus(). If it is not correct to use listStatus() when enabledFileSystemPaths is false, maybe the test shouldn't run in that case, and only run when enabledFileSystemPaths is true?

Yes, the listStatus makes sense when enabledFileSystemPaths to true. As said, if we want to go ahead and fix it, I am even okay with it. cc @rakeshadr for comments.

@rakeshadr @bharatviswa504 jira ticket here:
https://issues.apache.org/jira/browse/HDDS-5877

I merge from github looks it caused CI issue.
@GeorgeJahad When you get a chance please fix CI. TIA.


Line label URL - correct path and anchor

Found this all the way at the bottom of https://docs.appsignal.com/metrics/custom.html#metric-tags. Just a path and anchor update.

@wesgarrison Thanks for the patch! 👍


lift global variables from protobuf to llvm

lifting and initializing globals, need to add type information into llvm land

Transitioned to mcsema2 and lifting the globals. Closing it.


Ask to save workspace image when closing

Sometimes my R code takes a long time to run so I need to save a workspace image with save.image(). But it is easily forgotten and next time I have to run from the beginning again. I believe it would be great to pop up a warning every time you close an R project. Note that this is a feature in RStudio. Moreover, it would be even better if there is a setting to control whether to show the warning in case one may not want the feature and also a setting to control whether to save an image automatically.

Default settings are
    "r.rterm.option": [
        "--no-save",
        "--no-restore"
    ],

If you want to load the image at the startup of the terminal you may remove --no-restore; and if you remove --no-save, when you try to exit from the terminal, the usual question arises Save workspace image? [y/n/c]:.


Feature request: Stream recording (because SD card in Goggles are not working)

I tried out DigiView on a Samsung Tab A7 (WiFi), and it worked really well. But noticed that I could not record the flight to the SD card in the goggles. Is this expected behavior? It showed "no SD" as soon as I connect the cable to the Android device. I thought it is caused by the hardware interface, which may be the same for external storage and the internal SD card. If that is the case, I would love if the app would (optional) automatically store every stream to a storage location on the Android device. Is that possible?

This feature is already in work (#68 and #79)

Oh. Sorry. I have missed recognizing those PRs. Mostly just checked if there is already an issue with this feature. Sorry for wasting time!

After I tried Diji View out, My googles are unable to recognize the Sd card. Have you had that issue or found a way to reverse it?


Add Python Serialization APIs

Adds API to determine earliest forward compatible version that is able to be targeted by serialization. Currently we offer 1 month forward compatibility.
Closes #1301

Updated this to just be for Serialization APIs and current version. I still think design work is needed for the details of the lookupKnownVersion API.


Tip referendum creation link

Closes https://github.com/paritytech/substrate-tip-bot/issues/150
If the user is not in the privileged GitHub team, the bot will try to produce a tip referendum creation link instead.
To achieve it, I extracted some functionality like preparing an extrinsic to separate functions.
If it works, it looks like this.
If there is an issue with generating the PolkadotJS-Apps link, it will fall back to a message without, like this.

Made sure it continues to work locally: https://github.com/paritytech-stg/playground/pull/24#issuecomment-2074758454


feat(TUP-30081): initial change

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TUP-30081
What is the new behavior?
Decrypt incoming value if it is encrypted
Please check if the PR fulfills these requirements

[x] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[x] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications:
Other information:

Pull request test result: success :star:

Pull request test result: success :star:

Pull request test result: failure :x:


-d option no longer documented in help (plus a typo)

The README in this repo shows that there's a -d option to make a demo page, which is neat. However, when running bookmarklet -h in the terminal, this isn't document. Also there's a spurious ' in the output, after "stdout".
Just found this tool and it looks really helpful, thanks :-).

fixed https://github.com/mrcoles/bookmarklet/commit/47dfa5b7dd79b5082c0f8bd8608112cbba4aa742


Intellimouse

Adding Intellimouse support to the emulator.
For now, this only covers mouse wheel, that is mouse device id 3.

I'll go ahead and merge this is it is now.  If we end up w/ multiple SDL wheel events in the queue causing loss, then we can come back and address it later.


Test TCPIngress behavior when upstream disappears

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
Broken out of #1179
Proposed Solution
No response
Additional information
No response
Acceptance Criteria
Tests confirm that:

[ ]  Long running persistent connections (where the backend server doesn't support reconnect mechanisms) disconnect and fail properly when pods change

Per https://github.com/Kong/kubernetes-ingress-controller/issues/1179#issuecomment-982085102, this is all NGINX-level behavior. AFAIK Kong has no control over the connection once established, and cannot set any NGINX-level configuration that would influence this behavior.

Closing as won't fix per @rainest's comment above.


chore: release 1.0.0-alpha.0

:robot: I have created a release beep boop
1.0.0-alpha.0 (2023-08-02)
Features

initial release (#1) (5eab81b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/blackbaud/angular-tree-component/releases/tag/1.0.0-alpha.0 :sunflower:


Way to limit concurrent executions?

Context
Recovering from rouge script issue and trying to see if there was a mechanism within Zappa deployment to set concurrent executions on a per function basis.
Python 2.7/3.6 -->
2.7
Expected Behavior
A setting variable within the settings_file to able to add/limit concurrent execution limit on the deployed functions.
Actual Behavior

Possible Fix

Your Environment

Zappa version used: 0.45.1
Operating System and Python version:

You can do it through the aws. Have a look at https://aws.amazon.com/blogs/compute/managing-aws-lambda-function-concurrency/

It would be great to be able to control the concurrency limit via the Zappa settings file as well :D

+1 I'm also waiting for this great feature!


What is the origin of the name uv?

When I introduce uv to my colleagues, a surprising number of them ask me "what does uv stand for?" or "where did that name come from?".
Some come up with their own interpretations such as "ultraviolet light = fast", etc.
Is there anything documented about the origin of the name "uv", if only so I can point the extra curious folks at? Was it simply chosen as a short CLI name that didn't conflict with other Linux utilities? Is there a deeper meaning known only to Charlie? 😄

We considered a ton of names — it's really hard to pick a name without collisions this day so every name was a balance of tradeoffs.
uv was given to us on PyPI, is Astral-themed (i.e. ultraviolet or universal), and is short and easy to type.
🤷♀

https://github.com/astral-sh/uv/issues/1349#issuecomment-1986451785

Yeah for me it's short for "ultraviolet" though we liked that there were a few different possible interpretations. We wanted something that was (1) available on PyPI and elsewhere, (2) had minimal conflicts with other software projects, and (3) was easy to type!


Enabling color in piped output (stylish formatter)

What version of textlint are you using?

v11.7.6
What file type (Markdown, plain text, etc.) are you using?
Markdown
What did you do? Please include the actual source code causing the issue.
Piped textlint output to another process.
What did you expect to happen?
Expected that the output is colorized.
What actually happened? Please include the actual, raw output from textlint.

Even without the --no-color option, it seems that the stylish formatter stop colorizing when piped (the 2nd execution in the screenshot below).

I guess this is a bug. If not, is there any way to force-enable color for piped output?
Might be related to #593, if Gradle uses pipes for output of child processes (I'm not sure).

I guess this is a bug. If not, is there any way to force-enable color for piped output?

textlint just use chalk.
FORCE_COLOR=1 env enable color.
FORCE_COLOR is the config of chalk https://github.com/chalk/chalk#chalksupportscolor
FORCE_COLOR=1 ./node_modules/.bin/textlint README.md | cat

Probably related issue?

colors not showing up after spawning child process · Issue #381 · chalk/chalk

I do not know what natural behavior in this case.
For example, I want to disable color in the following case by default.
$ ./node_modules/.bin/textlint README.md > a.txt

I see. Maybe having something like --always-color option would be helpful. But indeed, setting FORCE_COLOR=1 does work for me. Thank you.

textlint --color is the same feature as FORCE_COLOR.
But, it is implicitly and it is not easy to understand.


Hello world 0.0.9

Update docs to thekindkeptn:0.0.9 which fixes https://github.com/keptn/keptn/issues/7112

I hope @oleg-nenashev can get 0.0.9 working as that will be 2/2 known broken environments from 0.0.8 solved with this version and we should be good to go.
This version spins up successfully (for me) on:

Windows w/ WSL2
MacOS 12.2.2
Ubuntu 20.04 on AWS

Thanks!


Design Date Controls

Work on the designs for:
### Tasks
- [ ] #2878
- [ ] #2877
- [ ] #2881

09/01 - Will share the progress and updates with @bhoppers2008. Focusing on the Date Input

17/01 - (WIP) Addressing feedback from leads.

Figma designs complete, dev work started


Log Retention should be 7 days for Public and 30 days for Dedicated.

In the section "Monitoring and logging with Cloud Foundry", the Log Retention states
In Bluemix Cloud Foundry apps, log data is stored for 30 days by default.
It should be replaced by
In Bluemix Cloud Foundry apps, log data is stored by default for 30 days in Bluemix Dedicated/Local and for 7 days in Bluemix Public.
Lionel

Currently CF Apps Dedicated / Local are separated out into topics that do specify the 30 day log retention - https://new-console.ng.bluemix.net/docs/monitoringandlogging/cfapps_ml_logs_dedicated_ov.html#container_ml_logs_dedicated_ov
I will update this topic to clarify log retention for Public - https://new-console.ng.bluemix.net/docs/monitor_log/monitoringandlogging.html#log_retention
Longer term I'm looking at how this section can be more integrated (and how we might integrate w/the container logging and monitoring topics as well).

Verified the logging caps is correctly updated in prod. Closing issue.


Ability to reset

Hi, it will be helpful if there is an ability to reset the scratched image. Thankyou 🙌

Closed in bee151f264f53c3c7cff7f9ee6946f47b460885f.
First upgrade the package version to 1.1.0
Check the readme.usage for usage


[Request]support to Avaritia mod and Extended Crafting mod

https://www.curseforge.com/minecraft/mc-mods/avaritia-1-10
https://www.curseforge.com/minecraft/mc-mods/extended-crafting

I will try to implement

implementation done, now just wait for the 1.4.6 compilation | https://github.com/vindocel/Dark-Everywhere/commit/02a450e4b3a47f1ac7caf48449fa67075ff88e1d


Workload Environment Variable bugs

[x] Source in Environment Variables needs to not have the namespace.  It should only show the source from the namespace that is selected from the Namespace field at top

[x] Prefix or Alias field in Environment Variables loses focus after every character I enter

Tested with master-head build (d1d63b68a)

Create a namespace newns and create secret "secret1" in the namespace
Create a workload and add environment variable using "Add from Resource" .

Source does not contain the namespace

Prefix/Alias field does not have focus issue.

Issue not fixed
Workload creation fails with the error below:

{ "type": "error", "links": {}, "code": "Invalid", "message": "Deployment.apps \"workload\" is invalid: [spec.template.spec.containers[0].image: Required value, spec.template.spec.containers[0].envFrom[0].secretRef.name: Invalid value: \"newns/secret1\": a DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')]", "status": 422 }

Request Payload:
{"type":"apps.deployment","metadata":{"namespace":"default","name":"workload"},"apiVersion":"apps/v1","spec":{"replicas":1,"template":{"spec":{"restartPolicy":"Always","containers":[{"name":"workload","resources":{"requests":{},"limits":{}},"env":[],"envFrom":[{"prefix":"test","secretRef":{"name":"newns/secret1","optional":false}}]}]},"metadata":{"labels":{"workload.user.cattle.io/workloadselector":"deployment-default-workload"}}},"selector":{"matchLabels":{"workload.user.cattle.io/workloadselector":"deployment-default-workload"}}}}

Validated with master-head(1f4a2c388)

Create a namespace newns and create secret "secret1" in the namespace
Create a workload with nginx image and add environment variable using "Add from Resource" . Choose the secret as a resource . Workload creation succeeds.
Exec shell in the workload pod and secret will be present as a env variable as expected.


fix(ndt_scan_matcher): added coping input_source when rebuilding ndt

Description
I found that there was a problem with Driving Log Replayer not working properly, so fix it.
[ndt_scan_matcher-39] [WARN<PHONE_NUMBER>.863786247] [localization.pose_estimator.ndt_scan_matcher]: No InputSource. Please check the input lidar topic (service_ndt_align() at /home/shintarosakoda/autoware/src/universe/autoware.universe/localization/ndt_scan_matcher/src/ndt_scan_matcher_core.cpp:864)
[pose_initializer_node-41] [INFO<PHONE_NUMBER>.864026735] [localization.util.pose_initializer_node]: NDT align server failed. (align_pose() at /home/shintarosakoda/autoware/src/universe/autoware.universe/localization/pose_initializer/src/pose_initializer/ndt_module.cpp:43)
[service_log_checker-4] [ERROR<PHONE_NUMBER>.864308161] [system.service_log_checker]: /localization/initialize: status code 4 'NDT align server failed.' (/localization/util/pose_initializer_node) (set_error() at /home/shintarosakoda/autoware/src/universe/autoware.universe/common/component_interface_tools/src/service_log_checker.cpp:83)
[service_log_checker-4] [ERROR<PHONE_NUMBER>.865189695] [system.service_log_checker]: /localization/initialize: status code 4 'NDT align server failed.' (/default_ad_api/node/localization) (set_error() at /home/shintarosakoda/autoware/src/universe/autoware.universe/common/component_interface_tools/src/service_log_checker.cpp:83)
[service_log_checker-4] [ERROR<PHONE_NUMBER>.865347276] [system.service_log_checker]: /api/localization/initialize: status code 4 'NDT align server failed.' (/default_ad_api/node/localization) (set_error() at /home/shintarosakoda/autoware/src/universe/autoware.universe/common/component_interface_tools/src/service_log_checker.cpp:83)

Related PR

https://github.com/autowarefoundation/autoware.universe/pull/6394

Tests performed
https://tier4.github.io/driving_log_replayer/quick_start/installation/
Driving Log Replayer works fine
driving_log_replayer simulation run -p localization --rate 0.5

Logging Simulator works fine
# terminal 1
ros2 launch autoware_launch logging_simulator.launch.xml \
    map_path:=$HOME/autoware_map/sample-map-rosbag \
    vehicle_model:=sample_vehicle \
    sensor_model:=sample_sensor_kit

# terminal 2
ros2 bag play $HOME/autoware_map/sample-rosbag/sample.db3 -r 0.5 -s sqlite3

Effects on system behavior

There are no effects on system behavior.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@SakodaShintaro The logging simulator is OK. However, I am trying to install Driving Log Replayer but when colcon build the following error occurred
`Starting >>> eagleye_navigation
--- stderr: rosbag2_py_wrapper
lto-wrapper: warning: using serial compilation of 2 LTRANS jobs
Finished <<< rosbag2_py_wrapper [24.2s]
Starting >>> eagleye_geo_pose_fusion
--- stderr: geometry
/home/anh/Work/autoware/src/simulator/scenario_simulator/common/math/geometry/src/bounding_box.cpp:15:10: fatal error: quaternion_operation/quaternion_operation.h: No such file or directory
15 | #include <quaternion_operation/quaternion_operation.h>
|          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
gmake[2]: *** [CMakeFiles/geometry.dir/build.make:76: CMakeFiles/geometry.dir/src/bounding_box.cpp.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:211: CMakeFiles/geometry.dir/all] Error 2
gmake: *** [Makefile:146: all] Error 2
`
But I could not find that quaternion_operation.h file anywhere in the system. How can I fix it?

@SakodaShintaro The logging simulator is OK, but the Driving Log Replayer is not. I tried to install the Driving Log Replayer but when colcon build, the below error showed up
/home/anh/Work/autoware/src/simulator/scenario_simulator/common/math/geometry/src/bounding_box.cpp:15:10: fatal error: quaternion_operation/quaternion_operation.h: No such file or directory    15 | #include <quaternion_operation/quaternion_operation.h>
I could not find that header anywhere in the system. Do you know how to fix it? This error belongs to the scenario_simulator_v2.

@anhnv3991
In my environment, ros-humble-quaternion-operation has been installed.
$ sudo apt list | grep quaternion-operation

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

ros-humble-quaternion-operation-dbgsym/jammy 0.0.11-1jammy.20240126.001735 amd64
ros-humble-quaternion-operation/jammy,now 0.0.11-1jammy.20240126.001735 amd64 [インストール済み]
ros-iron-quaternion-operation-dbgsym/jammy 0.0.7-4jammy.20240207.210444 amd64
ros-iron-quaternion-operation/jammy 0.0.7-4jammy.20240207.210444 amd64

This dependency is described in common/math/geometry/package.xml.
https://github.com/tier4/scenario_simulator_v2/blob/master/common/math/geometry/package.xml#L15
So, I think the commands below seem to work.
rosdep update
rosdep install -y --from-paths src --ignore-src --rosdistro $ROS_DISTRO

@SakodaShintaro This is the terminal output of my Driving Log Replayer.
terminal_output.txt
This looks OK to me.

@SakodaShintaro This is the output of the logging simulator.
logging_simulator_output.txt
The 'NoInputSource' error is not found here, so I think it should be OK.
The run looks OK to me.
Screencast from 22-02-2024 11:35:15.webm

@anhnv3991
This is normal behavior.
Thank you for confirming!


WIP: Introduce rewrite tools on Rel.

Add GetInputs, Copy, CopyWithExpressionRewrite to Rel

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

This is very promising! We have something similar to this in substrait-java in the RelCopyOnWriteVisitor and ExpressionCopyOnWriteVisitor which allows us to implement arbitrary tree rewrites quite easily.

...something similar to this in substrait-java...

Lol, why invent when you can just copy useful patterns, right? :D


Manual Installation

CocoaPods and Carthage are awesome tools and make our life really easier, but there are some devs who still don't know how to use them.
It would be cool to add the Manual installation guide in your README.md. You can take a look at my iOS Readme Template to see how you can do it.

I'm not sure I would want to make manual installation an "officially endorsed" install method.
Manual installation is hardly ever the best (or even just a good) choice when it comes to dependency managing beyond the scope of quick 'n' dirty scripting/prototyping.
If you don't know how to use SPM/Carthage/CocoaPods, then the proper way to integrate "Version" is to first learn about dependency managing and then come back and use one of the officially supported methods. :wink:


Issue #27: Add a hough transform implementation ported from opencv

I took a stab at this and it's working for me.

Great thanx for this.
can you also add a demo/example so that people can try it with webcam for example (see jsfeat docs/examples)?


Reshaping error when solving problem

This is on a Ubuntu 16.04 computer on Python 3.6.5 with
cvxpy==1.0.6
cvxopt==1.2.0
numpy==1.14.5

the following script:
import cvxpy
import numpy as np

common = cvxpy.Variable([16, 16], PSD=True)

x, y = np.random.rand(16, 16), np.random.rand(16, 16)
x = x @ x.T   # make PSD
y = y @ y.T

diff_x, diff_y = x - common, y - common

constraints = [diff_x >> 0, diff_y >> 0]
loss = cvxpy.sum_squares(diff_x) + cvxpy.sum_squares(diff_y)

cvxpy.Problem(cvxpy.Minimize(loss), constraints).solve(solver=cvxpy.CVXOPT)

I often get an reshaping error in cvxpy:
Traceback (most recent call last):
  File "test.py", line 15, in <module>
    cvxpy.Problem(cvxpy.Minimize(loss), constraints).solve(solver=cvxpy.CVXOPT)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/cvxpy/problems/problem.py", line 246, in solve
    return solve_func(self, *args, **kwargs)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/cvxpy/problems/problem.py", line 361, in _solve
    self.unpack_results(solution, self._solving_chain, inverse_data)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/cvxpy/problems/problem.py", line 453, in unpack_results
    solution = chain.invert(solution, inverse_data)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/cvxpy/reductions/chain.py", line 66, in invert
    solution = r.invert(solution, inv)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/cvxpy/reductions/matrix_stuffing.py", line 114, in invert
    order='F'
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 257, in reshape
    return _wrapfunc(a, 'reshape', newshape, order=order)
  File "/home/alan/workspace/ctrl-labs/py3.venv/lib/python3.6/site-packages/numpy/core/fromnumeric.py", line 52, in _wrapfunc
    return getattr(obj, method)(*args, **kwds)
ValueError: cannot reshape array of size 255 into shape (16,16)

This seems to be a something introduced between cvxpy==1.0.4 (which runs fine) and cvxpy==1.0.5 (which crashes).

This error seems similar to #510, which uses CVXOPT and cvxpy 1.0.3. Can you try the same problem with SCS and cvxpy 1.0.5?

Sorry for the delay! I re-ran this script (swapping out solver=cvxpy.CVXOPT with solver=cvxpy.SCS) using cvxpy==1.0.5 and scs==2.0.2 and this seems to have run without errors (although it was a little slow on my laptop).

I just ran the script on a modified version of cvxpy (containing a fix for #510), and CVXOPT worked without error. I also checked optimality conditions for the dual variables, and they seemed to work out fine. I'm marking this as "will be fixed soon".


Add image stream for JDK8 + RHEL8

Issue: https://issues.redhat.com/browse/JBEAP-24491
Signed-off-by: Ruben Dario Novelli<EMAIL_ADDRESS>I created a new file "eap74-openjdk8-rhel8-image-stream.json" using "eap74-openjdk8-image-stream.json" as source and change only the references from rhel7 to rhel8
diff eap74-openjdk8-rhel8-image-stream.json as rhel8-file eap74-openjdk8-image-stream.json as rhel7-file
rhel8-file= "name": "jboss-eap74-openjdk8-rhel8-openshift-image-streams",
rhel7-file= "name": "jjboss-eap74-openjdk8-openshift-image-streams",
rhel8-file= "description": "ImageStream definition for JBoss Enterprise Application Platform 7.4.0 with OpenJDK 8 and RHEL 8",
rhel7-file= "description": "ImageStream definition for JBoss Enterprise Application Platform 7.4.0 with OpenJDK 8",
rhel8-file= "name": "jboss-eap74-openjdk8-rhel8-openshift",
rhel7-file= "name": "jboss-eap74-openjdk8-openshift",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK 8 and RHEL 8",
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK 8",
rhel8-file= "description": "The latest available build of JBoss EAP 7.4 builder image with OpenJDK 8 and RHEL8.",
rhel7-file= "description": "The latest available build of JBoss EAP 7.4 builder image with OpenJDK 8.",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4 with OpenJDK8 and RHEL 8"
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4 with OpenJDK8"
rhel8-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel8:latest"
rhel7-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel7:latest"
rhel8-file= "description": "The latest available build of JBoss EAP 7.4.0 builder image with OpenJDK 8 and RHEL8.",
rhel7-file= "description": "The latest available build of JBoss EAP 7.4.0 builder image with OpenJDK 8.",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK8 and RHEL8"
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK8"
rhel8-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel8:latest"
rhel7-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-openshift-rhel7:latest"
rhel8-file= "name": "jboss-eap74-openjdk8-rhel8-runtime-openshift",
rhel7-file= "name": "jboss-eap74-openjdk8-runtime-openshift",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4.0 Runtime Image with OpenJDK 8 and RHEL8",
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4.0 Runtime Image with OpenJDK 8",
rhel8-file= "description": "The latest available build of JBoss EAP 7.4 runtime image with OpenJDK 8 and RHEL8",
rhel7-file= "description": "The latest available build of JBoss EAP 7.4 runtime image with OpenJDK 8",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4 with OpenJDK 8 (Runtime Image) and RHEL8"
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4 with OpenJDK 8 (Runtime Image)"
rhel8-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-runtime-openshift-rhel8:latest"
rhel7-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-runtime-openshift-rhel7:latest"
rhel8-file= "description": "The latest available build of JBoss EAP 7.4.0 runtime image with OpenJDK 8 and RHEL8",
rhel7-file= "description": "The latest available build of JBoss EAP 7.4.0 runtime image with OpenJDK 8",
rhel8-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK 8 (Runtime Image) and RHEL8"
rhel7-file= "openshift.io/display-name": "JBoss EAP 7.4.0 with OpenJDK 8 (Runtime Image)"
rhel8-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-runtime-openshift-rhel8:latest"
rhel7-file= "name": "registry.redhat.io/jboss-eap-7/eap74-openjdk8-runtime-openshift-rhel7:latest"

@jmesnil FYI

I edit descriptions and display-name. Now we have only the reference to rhel8 or ubi8 in the "List".metadata.name /             "ImageStream".metadata.name and "List".metadata.annotations.description


Move seeding outside of /api/graphql

Describe the bug
Seed logic doesn't belong to any endpoint. In a serverless approach, seeding should hapeen in a "predev" or "prestart" script that is run globally at application startup .
To Reproduce
On a fresh, empty database, try running /api/login before /api/graphql => admin user won't be seeded. This is because the seed happens only in /api/graphql.
Expected behavior
Seeding should happen before "yarn dev", not inside API routes.
To fix:

move seed code outside of "/api/graphql", into it's own independent script, in a "scripts" folder
setup an environment that stills allows to use TS in this script (eg running the script with node-ts or whatever)
run this script on "predev" in package.json (and maybe "prestart" for prod? we don't seed yet in production)

In progress, thanks to the new ability to build TypeScript files as independant scripts. We already have introduced db:seed and db:reset. We could document them as scripts to run after app creation.


restrict maximum row height in file manager to match thumbnail height

I had a quick look at how we could restrict the row height in the file manager.

I tried to set the height attribute of the img tag, but that's a bit tricky since we create the markup in JavaScript file.resultsThumbnailImg in https://github.com/ortic/concrete5-5.7.0/blob/b0f9f083e814e74080a116a4bd9efc0f3a4034a6/web/concrete/elements/files/search.php#L118
I was also a bit confused that Config::get('concrete.icons.file_manager_listing.height') would return 60 despite that I've set the thumbnail height to 100 and also cleared the cache.
I ended up with this tad bit ugly long line of inline CSS

Might replace https://github.com/concrete5/concrete5/pull/3438

I think this should do it:
https://github.com/concrete5/concrete5/commit/8102697179c147e0c43b55cc35391d3c68f06e18


Add Corebot set up to execute as an Azure Function.

Fixes #6102
Description
This is a test bot that is configured to run as an Azure Function.
Specific Changes
CoreBot was used as a base and then the required additional classes were added to allow CoreBot to run as an Azure Function. The required changes are that we need to register a HttpTrigger to map to the /messages incoming URI. This is done in the Triggers/MessagesTrigger.cs source file. This class get a reference to the registered IBotFrameworkHttpHandler in the constructor and then uses this handler in the RunAsync method to route the incoming request to the adapter by calling the ProcessAsync method on the adapter with the incoming request.
This test bot can also be used with AddBotRuntime, but that code isn't checked into the branch yet, so this version can be run with a traditional startup sequence for now. When AddBotRuntime is complete we can update this to use that startup process.
Testing
Test bot was run locally and deployed to Azure and run.

This was great, I'm sad to close it but that's the way life goes sometimes.


[BUG] <IP_ADDRESS> - "The system cannot find the file specified." while dismounting.

Describe the bug
Error "The system cannot find the file specified." while attempting to dismount after applying optimizations.
Desktop (please complete the following information):

OS being optimized: Windows 10 LTSC
OS build: 17763

Additional context
Thought it could be an error with a space in my username, so I attempted it with the Image Dir and Optimize-Offline at C:. But still got the error.
Previous version, <IP_ADDRESS>, completes without error.
Log files
Optimize-Offline.log

Thank you for showing me this. It is not an issue on your part. Basically when I transferred all variables to the function, that included the variable the path where the boot image mounts so, to make this short, the primary script able to return a value for a mounted boot image despite a boot image not even being available to mount. The error you're receiving is occurring when it tries to dismount a non-existent boot image.
I will issue a code correction for this right now and you will be good to go.

This has been corrected in the latest build.


[SPARK-18188][DOC][FOLLOW-UP]Add spark.broadcast.checksum to configuration

What changes were proposed in this pull request?
This pr add spark.broadcast.checksum to configuration.
How was this patch tested?
manually tested

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1161/
Test PASSed.

Test build #93329 has started for PR 21825 at commit 6a85aad.

Test build #93329 has finished for PR 21825 at commit 6a85aad.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93329/
Test PASSed.

Are you sure this is supposed to be documented for end users?

I think it's necessary to let the end users know:
1.this feature is already stable
2.People can disable it if their network is stable, doing this is good for performance

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1515/
Test PASSed.

Test build #93823 has started for PR 21825 at commit cf27272.

Test build #93823 has finished for PR 21825 at commit cf27272.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93823/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1556/
Test PASSed.

Test build #93876 has started for PR 21825 at commit d18d1b2.

Test build #93876 has finished for PR 21825 at commit d18d1b2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93876/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/1592/
Test PASSed.

Test build #93919 has started for PR 21825 at commit 09cbe26.

Test build #93919 has finished for PR 21825 at commit 09cbe26.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/93919/
Test PASSed.

Thanks @srowen