Double-freeing context from OSSL_LIB_CTX_new_child in teardown of an encoder/decoder provider

I have a provider and call OSSL_LIB_CTX_new_child in the init and corresponding OSSL_LIB_CTX_free on teardown, just like the legacyprov.c
Without ASan the openssl app with my provider hangs in an infinite loop during teardown inside the OSSL_LIB_CTX_free. With ASan, a heap-use-after-free is reported. I found that this happens only when OSSL_OP_ENCODER or OSSL_OP_DECODER is provided (that's why the legacyprov.c doesn't fail).
I suspect the error might be in openssl because the legacyprov fails too when I add a dummy decoder to it. To reproduce this, simply add:
diff --git a/providers/legacyprov.c b/providers/legacyprov.c
index b5fc5f523f..bc865eda14 100644
--- a/providers/legacyprov.c
+++ b/providers/legacyprov.c
@@ -148,6 +148,24 @@ static const OSSL_ALGORITHM legacy_kdfs[] = {
     { NULL, NULL, NULL }
 };

+static int
+dummy_decoder_decode(void *ctx, OSSL_CORE_BIO *cin, int selection,
+                        OSSL_CALLBACK *object_cb, void *object_cbarg,
+                        OSSL_PASSPHRASE_CALLBACK *pw_cb, void *pw_cbarg)
+{
+    return 0;
+}
+
+const OSSL_DISPATCH dummy_decoder_functions[] = {
+    { OSSL_FUNC_DECODER_DECODE, (void (*)(void))dummy_decoder_decode },
+    { 0, NULL }
+};
+
+static const OSSL_ALGORITHM dummy_decoders[] = {
+    { "DER", "provider=legacy,input=pem", dummy_decoder_functions },
+    { NULL, NULL, NULL }
+};
+
 static const OSSL_ALGORITHM *legacy_query(void *provctx, int operation_id,
                                           int *no_cache)
 {
@@ -159,6 +177,8 @@ static const OSSL_ALGORITHM *legacy_query(void *provctx, int operation_id,
         return legacy_ciphers;
     case OSSL_OP_KDF:
         return legacy_kdfs;
+    case OSSL_OP_DECODER:
+        return dummy_decoders;
     }
     return NULL;
 }

And then call openssl list -decoders -provider legacy. This should hang or (with ASan) generate a report like this:
==36313==ERROR: AddressSanitizer: heap-use-after-free on address 0x606000000d00 at pc 0x7ff470e4c9d3 bp 0x7ffdc2c06aa0 sp 0x7ffdc2c06a90
READ of size 8 at 0x606000000d00 thread T0
    #0 0x7ff470e4c9d2 in ossl_provider_deregister_child_cb crypto/provider_core.c:1491
    #1 0x7ff470e4b44f in child_prov_ossl_ctx_free crypto/provider_child.c:46
    #2 0x7ff470e36983 in CRYPTO_free_ex_data crypto/ex_data.c:402
    #3 0x7ff470e2e45d in context_deinit crypto/context.c:132
    #4 0x7ff470e2ea7f in OSSL_LIB_CTX_free crypto/context.c:243
    #5 0x7ff470e2ea7f in OSSL_LIB_CTX_free crypto/context.c:238
    #6 0x7ff46d9c433d in legacy_teardown providers/legacyprov.c:188
    #7 0x7ff470e4f454 in ossl_provider_free crypto/provider_core.c:439
    #8 0x7ff470e4f454 in ossl_provider_free crypto/provider_core.c:422
    #9 0x7ff470d71cf3 in OSSL_DECODER_free crypto/encode_decode/decoder_meth.c:63
    #10 0x7ff470ea4b7b in ossl_method_free crypto/property/property.c:150
    #11 0x7ff470ea4b7b in impl_free crypto/property/property.c:181
    #12 0x7ff470ef7895 in OPENSSL_sk_pop_free crypto/stack/stack.c:406
    #13 0x7ff470ea4e48 in sk_IMPLEMENTATION_pop_free crypto/property/property.c:45
    #14 0x7ff470ea4e48 in alg_cleanup crypto/property/property.c:197
    #15 0x7ff470ea4e48 in alg_cleanup crypto/property/property.c:194
    #16 0x7ff470e5476c in trampoline crypto/sparse_array.c:134
    #17 0x7ff470e5476c in sa_doall crypto/sparse_array.c:98
    #18 0x7ff470e5476c in ossl_sa_doall crypto/sparse_array.c:143
    #19 0x7ff470ea51c0 in ossl_sa_ALGORITHM_doall crypto/property/property.c:75
    #20 0x7ff470ea51c0 in ossl_method_store_free crypto/property/property.c:231
    #21 0x7ff470e36983 in CRYPTO_free_ex_data crypto/ex_data.c:402
    #22 0x7ff470e2e45d in context_deinit crypto/context.c:132
    #23 0x7ff470e371e7 in OPENSSL_cleanup crypto/init.c:417
    #24 0x7ff470e371e7 in OPENSSL_cleanup crypto/init.c:333
    #25 0x7ff47088da26  (/lib/x86_64-linux-gnu/libc.so.6+0x49a26)
    #26 0x7ff47088dbdf in exit (/lib/x86_64-linux-gnu/libc.so.6+0x49bdf)
    #27 0x5615992b40a0 in main apps/openssl.c:308
    #28 0x7ff47086b0b2 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x270b2)
    #29 0x5615992b4b8d in _start (/home/petr/projects/openssl/apps/openssl+0xb2b8d)

0x606000000d00 is located 32 bytes inside of 56-byte region [0x606000000ce0,0x606000000d18)
freed by thread T0 here:
    #0 0x7ff4714d67cf in __interceptor_free (/lib/x86_64-linux-gnu/libasan.so.5+0x10d7cf)
    #1 0x7ff470e36983 in CRYPTO_free_ex_data crypto/ex_data.c:402
    #2 0x7ff470e2e45d in context_deinit crypto/context.c:132
    #3 0x7ff470e371e7 in OPENSSL_cleanup crypto/init.c:417
    #4 0x7ff470e371e7 in OPENSSL_cleanup crypto/init.c:333
    #5 0x7ff47088da26  (/lib/x86_64-linux-gnu/libc.so.6+0x49a26)

previously allocated by thread T0 here:
    #0 0x7ff4714d6bc8 in malloc (/lib/x86_64-linux-gnu/libasan.so.5+0x10dbc8)
    #1 0x7ff470e388a5 in CRYPTO_zalloc crypto/mem.c:191
    #2 0x7ff470e4f80a in provider_store_new crypto/provider_core.c:186
    #3 0x7ff470e2e322 in ossl_lib_ctx_generic_new crypto/context.c:303
    #4 0x7ff470e356c2 in ossl_crypto_alloc_ex_data_intern crypto/ex_data.c:456
    #5 0x7ff470e2efb0 in ossl_lib_ctx_get_data crypto/context.c:407
    #6 0x7ff470e4fec8 in get_provider_store crypto/provider_core.c:241
    #7 0x7ff470e4fec8 in ossl_provider_find crypto/provider_core.c:268
    #8 0x7ff470e4c130 in provider_conf_load crypto/provider_conf.c:152
    #9 0x7ff470e4c130 in provider_conf_init crypto/provider_conf.c:202
    #10 0x7ff470ca7b6f in module_init crypto/conf/conf_mod.c:375
    #11 0x7ff470ca7b6f in module_run crypto/conf/conf_mod.c:239
    #12 0x7ff470ca7b6f in CONF_modules_load crypto/conf/conf_mod.c:138
    #13 0x7ff470ca7b6f in CONF_modules_load crypto/conf/conf_mod.c:90
    #14 0x7ff470ca8876 in CONF_modules_load_file_ex crypto/conf/conf_mod.c:181
    #15 0x7ff470ca8d41 in ossl_config_int crypto/conf/conf_sap.c:64
    #16 0x7ff470e36fde in ossl_init_config crypto/init.c:238
    #17 0x7ff470e36fde in ossl_init_config_ossl_ crypto/init.c:236
    #18 0x7ff470a4847e in __pthread_once_slow /build/glibc-eX1tMB/glibc-2.31/nptl/pthread_once.c:116

Fix in #15741


self host instance: How to check version or release?

I am running a self host instance of excalidraw. I do regular pull to make the docker image and subsequently deploy it in my cloud. Is there a knob that I verify or check the version of excalidraw that I am currently deploying?

You can get the version from build/version.json. However this seems to be just be time-based on the build and not semver.
See: https://github.com/excalidraw/excalidraw/blob/master/scripts/build-version.js#L30

tangentially related: https://github.com/excalidraw/excalidraw/issues/1665

@sbng we include a tag with GIT SHA of the deployed commit on the Docker image, unfortunately that's the only thing we have now.

Will close that due to inactivity. @sbng let us know of your thoughts.


Smart use of CAI vs GCP resource APIs for Inventory data collection

CAI vs API Smart Behavior - Default behavior should be to use CAI for all resources and disable getting data from APIs if the data supported through CAI

Adjusting to P2 - other performance improvements have had the intended benefits. No seeing large material value to do this. This can be an optimization at some point in the future.


tests: move test lnd logs to a more permanent location

Here's a first stab at drafting a solution for storing logs, as discussed with @carlaKC  in #58 . The code changes are pretty small, but a couple notes below on implementation, including a change to LDK that we need to do to get this fully working.
A couple of notes on implementation:

I went with storing the LND logs in a custom /tmp directory for each test. The motivation being that this keeps the logs around after the test so developers can use it for debugging, but since the logs likely won't be needed for long, it's nice to have them stored in the /tmp file so that they're automatically deleted by the OS after a certain amount of time/when the device restarts.
It's possible to specify a custom path for LND logs. But this is not supported by LDK quite yet. Should be easy to add support, I'm pinging Elias from LDK about doing a quick PR for this, if that sounds good. Then we can finish up the LDK side of things.

@carlaKC ok I added the github action for uploading the logs :) I also now included the ldk logs since this PR for setting the ldk logs elsewhere is now merged https://github.com/lightningdevkit/ldk-node/pull/129

Replaced by #70


Introduce support to boot up Firecracker with initrd

Add initial support for booting unikernels over Firecracker with urunc. For the time being, we do not have support for virtio-blk, but only for initrd. THerefore, the guest can only read data from the initrd. Regarding networking, we use virtio-net  over the tap interface  that we create with urunc. Currently there is support for only one network device per guest. Moreover, in the case of Firecracker the guest's network interface has the same MAC address as the tap interface in the network namespace of the container.
Overall, things we need to consider in the future:

Support for virtio-blk
VM memory
Generate Firecracker's configuration, based on a specific config
Use Firecracker's API to spawn, instead of creating a JSON file

Fixes #8

Thank you both for the review. I have updated the commit with the suggested changes and added the trailers.


Add links to all the new detail edit pages

Trello ticket: https://trello.com/c/x5mzD7bS/49-supplier-add-links-to-all-the-new-change-pages

Looks good from my perspective.

Took me way too long to spot this, but your hidden_text attributes are nested inside the url_for call, so you're generating weird URLs rather than adding the hidden text.
Also I don't think we want to have the verb (e.g. 'change', 'add') included as part of the hidden text, as a screenreader will read the visible text followed by the hidden text, which will end up with e.g. 'Change change registered company name'. This ignores our internationalisation issue for now, but is consistent with other uses of the hidden_text attribute (e.g. as in @katstevens's example).

@samuelhwilliams good spot with the hidden url, I probably should not have added those just before going home 😅 . And good point with the verbs, I will get rid of them.
Also, do you think we need hidden_text attributes on both "Change" and "Answer Required" links?
I am asking as Answer Required link is just next to the row title...

The hidden_text is needed where there's potential ambiguity. So if there are multiple 'Change' links on the page, the screen reader needs to be able to differentiate between them.

@katstevens good idea, I will check with @constancecerf
As to the change from "or" to "and": yes, it's intentional. In earlier iteration of the page we did not have "Answer required" link so it made sense to show any information that is there. Now, all this information will need to be submitted for a supplier to be able to proceed with their framework application, so if any is missing, an "Answer required" link should be shown.

The links have moved out of line:

@TheDoubleK thanks for spotting, fixed :) (somehow I am least cautious when I am introducing changes as a part of code review, I need to work on that 😬 )

@TheDoubleK good suggestion, I changed the copy of these hidden_text attributes now 👍. Merging when Travis is done ☺


Added step in contact-tns-service-desk.md

Closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/8577.

@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


ip package missing

On latest version the ip package should be added to package.json.

https://github.com/davezuko/react-redux-starter-kit/blob/master/package.json#L94 looks like it's there. Are you sure you pulled the latest version?

Weird. Sorry for taking your time, I must have mistaken a branch.

No worries!


esp32 wdt

Can your implementation watchdog.py component be used for esp32?

Well it should work. But there is actually no point in using it with the esp32 because it is a software watchdog implementation using Timers. It was useful on the esp8266 due to a bug in the micropython firmware which has been fixed a long time ago. I don't think I've ever seen an esp8266 be reset by the watchdog since then but I kept it, just to be sure.
The esp32 has a hardware watchdog and I've seen that one resetting my boards occasionally so I don't think there's any benefit in using an additional software watchdog on the esp32.


Add test coverage for submitting form[data-turbo-frame="_top"]

Closes #901
Add test coverage for submitting <form> elements with [data-turbo-frame="_top"]. Coverage includes both <form> elements outside of <turbo-frame> and <form> elements that are descendants of <turbo-frame> elements.

Thanks again, @seanpdoyle


Separate hotkey for opening dialog box to starting conversation

A single hotkey is mapped to both add an NPC to a conversation as well as open the dialog box. A new pair of hotkeys need to be created which split out these features into two. The original "merged" hotkey needs to be kept for the benefit of VR users.

Fixed by https://github.com/art-from-the-machine/Mantella-Spell/commit/c0e8ee81ab17c894734daffb88d396a1dca4e10d


.h5 file

Hello good day. Thank you very much for providing this repository it is really helpful. But I can't run to test it because of some errors. I can't see any mask_rcnn_shapes_0199.h5 in the directory. Where can I get this? Please help me thank you

Hello, the weights file has been uploaded to the release

Oh I see Thank you very much <3


Resurrecting GraphQL PR

This is a revival of #1642 with modifications after rebasing.

@stubailo all the tests pass on this branch now. does it make sense to open this against prettier:master and just keep adding tests until we're satisified? or should we limit the noise upstream and add tests here?

/cc @vjeux just so you know where this is. would you rather us open this against prettier while we're adding tests / functionality?

merged as part of https://github.com/prettier/prettier/pull/1982


Combine map mouseModes and remove toggle

Resolves #196
Resolves #230
Some notes to reviewers:

Regarding this request from issue 230:

tether magnified "popup" versions of the marker to the appropriate edge of the BoundsDriftMarker's bounding box (bounds and/or boundingBox) - so if the popup is popping down, it needs to be attached/tethered to the bottom edge of the grey bounding box rectangle. If it pops left, on the left edge, and so so on.

I actually opted to tether the popup to whichever boundary extends furthest in the orientation desired. In other words, if the popup is popping down and the grey box's bottom edge does not extend below the marker, we tether to the marker's bottom edge. (screenshots below)

The real work for this PR is in BoundsDriftMarker.tsx. I removed the mouse tools components in MapVEuMap.tsx and reduced opacity of the hovered marker in map-styles.css, but otherwise the diffs are simply removing the types, state, and props associated with the old, one-at-a-time mouse mode logic.

Marker is below the grey box, so tether popup to marker:

Grey box is below marker, so tether popup to grey box:

Do we want another ticket and/or UX discussion to allow the user to keep the popup active my mousing over the grey box or the popup itself?  This may not be trivial - hence a new ticket suggestion.

Do we want another ticket and/or UX discussion to allow the user to keep the popup active my mousing over the grey box or the popup itself? This may not be trivial - hence a new ticket suggestion.

A couple thoughts on this:

As far as I know, no additional information is gained by "interacting" with the popup/box. If I'm mistaken, then this proposal makes more sense to me.
A different take is that it's possible that a user may think that the popup/box are interactive, in which case there's some value in letting the user dispel that notion by letting them hover over the popup/box.

Do we want another ticket and/or UX discussion to allow the user to keep the popup active my mousing over the grey box or the popup itself? This may not be trivial - hence a new ticket suggestion.

A couple thoughts on this:
1. As far as I know, no additional information is gained by "interacting" with the popup/box. If I'm mistaken, then this proposal makes more sense to me.

2. A different take is that it's possible that a user _**may think**_ that the popup/box are interactive, in which case there's some value in letting the user dispel that notion by letting them hover over the popup/box.

Good points.
I guess I was thinking ahead to when the popups might be more interactive (potentially with shortcuts to open the marker config menu). It's probably safer to leave them as they are for now!


WIP progress output see #98

The PR is still a WIP (fixes https://github.com/phparkitect/arkitect/issues/98) , though enough to get feedback, comments below
There is a major change about the runner, switching from a callback based approach to a plain old iterative way
The code still needs to be cleaned up

For me, the approach and the code are correct.
I think it could be useful to add a little section or a description of the new option -v inside the README file.

For me, the approach and the code are correct.
I think it could be useful to add a little section or a description of the new option -v inside the README file.

yup, I'll proceed to complete the cleanup and add some info on the README


Add the support of the restore command

It only supports the string type dump value, but the basic flow like checksum verification is ready. What we have done for now:

Port the crc64 and lzf algorithm from Redis
Implement the restore command but only support the string type
Add the support of verifying payload checksum
Add the support of parsing string type payload

Next:

[x] Add the support of the string type
[x] Add the support of the list type
[x] Add the support of the set type
[x] Add the support of the hash type
[x] Add the support of the zset type
[ ] Add test cases for all sort of encoding types
[ ] Add the support of the stream type

This will close #1648 and we won't support the stream type in this PR because it's a bit complex to support all of them in one PR.

Maybe I can do the "Add the support of the set type". Let me try it.

PR is ready to be reviewed, but I need some time to add test cases for all encoding types.

For compatibility testing, I think we can start a redis service in CI and do some mutual en/decoding? e.g. KvrocksDecode(RedisEncode(x)) = x or RedisDecode(KvrocksEncode(y)) = y

For compatibility testing, I think we can start a redis service in CI and do some mutual en/decoding? e.g. KvrocksDecode(RedisEncode(x)) = x or RedisDecode(KvrocksEncode(y)) = y

Aha, my test case values are dumped from the Redis, it should be difficult since those encoding types are located in many Redis versions, for example, the zip map exists in Redis 2.x.

Sorry for the big PR but the good news is it only affects the restore command itself :)

@git-hulk Yeah, a massive PR! But I believe we will handle it :)

@git-hulk Yeah, a massive PR! But I believe we will handle it :)

Thank you! That's a bit hard to review since most of them are Redis encoding-related implementations. All test values are dumped from the Redis from Redis 2.6(dump command was supported from this version), and now test cases can cover all sorts of encoding types to guarantee it works.

I have tested the RedisShake to migrate Redis data into Kvrocks and it works well now.

Thanks all, I will merge this PR and can submit an issue to followup if you found any issues.


[feature request]check whether a data iterator is initialized

System information

TensorFlow version (you are using): r1.13
Are you willing to contribute it (Yes/No): yes

Describe the feature and the current behavior/state.
When a dataset iterator is shared among sessions by "shared_name", non-chief sessions need to wait for its initialization on the chief session. And what is the proper way to check the state of iterators currently？
Ideally, iterators should be initialized by init_ops of monitoredsession, and checked in model_ready function.
Will this change the current api? How?
No changes on current api. add one new api like "is_initialized".
Who will benefit with this feature?
all who use "shared_name" feature.

Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Make sure you also include the exact command if possible to produce the output included in your test case. If you are unclear what to include see the issue template displayed in the Github new issue template.
We ask for this in the issue submission template, because it is really difficult to help without that information. Thanks!

Please provide details about what platform you are using (operating system, architecture). Also include your TensorFlow version. Also, did you compile from source or install a binary?
Make sure you also include the exact command if possible to produce the output included in your test case. If you are unclear what to include see the issue template displayed in the Github new issue template.
We ask for this in the issue submission template, because it is really difficult to help without that information. Thanks!

sorry，added informations.

awaiting tensorflower

TF 1.X style iterators are deprecated in TF 2.0 and the tf.data team will not prioritize this request. I will mark this issue as contributions welcome.

as the style iterators are deprecated , this is no longer a valid feature request, closing this issue. Thank you


[Feature Request] Waterlogging

The ability to waterlog blocks, for those of us building beneath the ocean's surface. (This may have already been added, I haven't updated to 2.4.0 yet.)

just added in 2.5.0 for 1.17


Wrong borders

There is a mistake in your map: Crimea is an ukrainian territory, not a russian

Thanks for reporting. The topic of disputed territories is indeed not well handled by the current style. Feel free to submit a pull request to https://github.com/maplibre/maplibre.github.io to fix this.

@petr-pokorny-1 what is the process for re-generating the pbfs used in the demotiles repo?

Would be nice if you could join the maplibre slack channel. We had a discussion on this topic 7 months ago. I now linked your issue there.

What would be the easiest way to fix this? Maybe an overlay? Or is there a new version of natural earth?

https://github.com/maplibre/demotiles/pull/9

Fix screenshot https://user-images.githubusercontent.com/59284/118267966-117aa100-b4bd-11eb-8824-430cbe674191.png at https://github.com/maplibre/demotiles and all will be good ;)


parseRM_GetNesting.pl - Nested elements are not merged in .Nest.Corr.out

I would like to use your script parseRM_GetNesting.pl to generate a de-nested set of repetitive elements from repeatmasker input. It is critical for my purposes that any given element is reported only once in the output with corrected coordinates spanning all nested elements from a give insertion. This is because I would like to perform feature counting and intersection of sets.
I am struggling a little bit to understand the output of your scripts. Consider the output of the following commands using repeatmasker output from hg19 and mm9 genome builds, and the output generated by your script:
> grep LINE hg19_repeatmasker.4.0.5.txt | wc -l
1569213
> grep LINE hg19_repeatmasker.4.0.5.txt.Nest.Corr.out | wc -l
1791781
> grep LINE hg19_repeatmasker.4.0.5.txt.Nest.Only.out | wc -l
331916
> grep LINE hg19_repeatmasker.4.0.5.txt.Nest.OriginalLines.out | wc -l
646973

> grep LINE mm9_repeatmasker.txt | wc -l
977058
> grep LINE mm9_repeatmasker.txt.Nest.Corr.out | wc -l
1081806
> grep LINE mm9_repeatmasker.txt.Nest.Only.out | wc -l
163184
> grep LINE mm9_repeatmasker.txt.Nest.OriginalLines.out | wc -l
291800

The origional papers on the human and mouse genomes list the total number of LINE elements as ~868,000 for human and ~660,000 for mouse. However the numbers reported by the output of your script do not match at all. In fact, it seems the numbers derived from *.Corr.out are even more greatly inflated than the original data. It appears that insertions disrupted by a nested insertion event are not merged into a single line as described in the documentation.
Consider the following lines of output from mm9_repeatmasker.txt.Nest.Corr.out:
Gname	Gstart	Gend	RealMaskedLen	Strand	Rname	Rclass/fam	Repstart	Rend	Repleft	%Div	%Del	%Ins	If-nest(ed/ing)	ID(blockNumber)

chr1	3000238	3000733	496	-	L1_Mur2	LINE/L1	(4488)	1389	913	21.4	11.4	4.5	na	na
chr1	3000238	3000792	522	-	L1_Mur2	LINE/L1	(4488)	1389	887	21.4946360153257	11.2107279693487	4.84367816091954	nesting	1
chr1	3000734	3000766	33	+	(TTTG)n	Simple_repeat	2	33	(0)	3.1	0.0	3.0	nested	1
chr1	3000767	3000792	26	-	L1_Mur2	LINE/L1	(6816)	912	887	23.3	7.6	11.4	na	na
chr1	3001288	3001583	296	-	Lx9	LINE/L1	(1596)	6048	5742	25.0	6.5	3.7	na	na
chr1	3001723	3002005	283	-	RLTR25A	LTR/ERVK	(0)	1028	625	19.7	33.2	0.7	na	na
chr1	3001723	3002615	847	-	RLTR25A	LTR/ERVK	(0)	1028	1	19.4336481700118	15.6873671782763	4.49551357733176	nesting	2
chr1	3002006	3002051	46	+	(TA)n	Simple_repeat	1	46	(0)	0.0	0.0	0.0	nested	2
chr1	3002052	3002615	564	-	RLTR25A	LTR/ERVK	(404)	624	1	19.3	6.9	6.4	na	na
chr1	3003213	3003261	49	-	L1M2	LINE/L1	(1343)	4800	4769	26.8	14.5	13.8	na	na
chr1	3003213	3003815	419	-	L1M2	LINE/L1	(1343)	4800	4378	26.8	14.5	13.8	nesting	3
chr1	3003262	3003445	184	-	B3	SINE/B2	(2)	214	4	20.1	14.7	0.0	nested	3
chr1	3003446	3003815	370	-	L1M2	LINE/L1	(1375)	4768	4378	26.8	14.5	13.8	na	na

Here there are three insertions that are disrupted by nesting: L1_Mur2 (lines 3, 4, 6); RLTR25A (lines 8, 9, 11); and L1M2 (lines 12, 13, 15), but according to the documentation should be merged into a single line. I would expect the output to look like the following:
name	Gstart	Gend	RealMaskedLen	Strand	Rname	Rclass/fam	Repstart	Rend	Repleft	%Div	%Del	%Ins	If-nest(ed/ing)	ID(blockNumber)

chr1	3000238	3000792	522	-	L1_Mur2	LINE/L1	(4488)	1389	887	21.4946360153257	11.2107279693487	4.84367816091954	nesting	1
chr1	3000734	3000766	33	+	(TTTG)n	Simple_repeat	2	33	(0)	3.1	0.0	3.0	nested	1
chr1	3001288	3001583	296	-	Lx9	LINE/L1	(1596)	6048	5742	25.0	6.5	3.7	na	na
chr1	3001723	3002615	847	-	RLTR25A	LTR/ERVK	(0)	1028	1	19.4336481700118	15.6873671782763	4.49551357733176	nesting	2
chr1	3002006	3002051	46	+	(TA)n	Simple_repeat	1	46	(0)	0.0	0.0	0.0	nested	2
chr1	3003213	3003815	419	-	L1M2	LINE/L1	(1343)	4800	4378	26.8	14.5	13.8	nesting	3
chr1	3003262	3003445	184	-	B3	SINE/B2	(2)	214	4	20.1	14.7	0.0	nested	3

Is the output in *.Corr.out correct?

Hi,
Can you cc your input file corresponding to these lines? The simple repeat should have been filtered out and not considered 'nested' elements.
In the meantime, I am checking this and will address your question shortly (it looks like the original lines are printed in the 'corrected' output but I am not sure that it is the issue).

My input file is the standard repeatmasker out file derived from the mm9 reference sequence obtainable here.
The corresponding lines from my version of this file look like the following:
	SW	perc	perc	perc	query	position	in	query	matching	repeat	position	in	repeat
	score	div.	del.	ins.	sequence	begin	end	(left)	repeat	class/family	begin	end	(left)	ID

	687	17.4	0.0	0.0	chr1	3000002	3000156	(194195276)	C	L1_Mur2	LINE/L1	(4310)	1567	1413	1
	917	21.4	11.4	4.5	chr1	3000238	3000733	(194194699)	C	L1_Mur2	LINE/L1	(4488)	1389	913	1
	215	3.1	0.0	3.0	chr1	3000734	3000766	(194194666)	+	(TTTG)n	Simple_repeat	2	33	(0)	2
	845	23.3	7.6	11.4	chr1	3000767	3000792	(194194640)	C	L1_Mur2	LINE/L1	(6816)	912	887	1
	621	25.0	6.5	3.7	chr1	3001288	3001583	(194193849)	C	Lx9	LINE/L1	(1596)	6048	5742	3
	1320	19.7	33.2	0.7	chr1	3001723	3002005	(194193427)	C	RLTR25A	LTR/ERVK	(0)	1028	625	4
	414	0.0	0.0	0.0	chr1	3002006	3002051	(194193381)	+	(TA)n	Simple_repeat	1	46	(0)	5
	2352	19.3	6.9	6.4	chr1	3002052	3002615	(194192817)	C	RLTR25A	LTR/ERVK	(404)	624	1	4
	386	26.8	14.5	13.8	chr1	3003213	3003261	(194192171)	C	L1M2	LINE/L1	(1343)	4800	4769	6
	797	20.1	14.7	0.0	chr1	3003262	3003445	(194191987)	C	B3	SINE/B2	(2)	214	4	7
	386	26.8	14.5	13.8	chr1	3003446	3003815	(194191617)	C	L1M2	LINE/L1	(1375)	4768	4378	6

For my purposes, elements that are merged should only output the merged element rather than the merged element in addition to the original lines. Maybe you could make this an option if it was your intention to output the original lines in addition to the merged lines?
Also, if I understand correctly, it should not be an issue for the simple repeats to be considered "nestED", but "nestING" could be an issue, however I don't believe that I observe the latter case.

Hi,
So this code is 3y old and super messy - and it was not taking advantage of the block ID numbers generated by RepeatMasker (visually, it is the 'interrupted repeats' track on the UCSC genome browser).
I am writing a new version - which in its current state outputs merged lines, like this:

Score
%Div
%Del
%Ins
Gname
Gstart
Gend
Gleft
Strand
Rname
Rclass/fam
Rstart(left)
Rend
Rend(left)
blockID
RealMaskedLen

10775.66667
11.6
1.3
2.4
chr1
3000001
3004054
nd
-
L1MdFanc_I
LINE/L1
nd
nd
nd
1
3009

3088
20.7
2.866666667
2.966666667
chr1
3004041
3005441
nd
+
L1_Rod
LINE/L1
nd
nd
nd
3
1337

5118
22.6
5.9
3.6
chr1
3005461
3006764
-192465207
+
Lx9
LINE/L1
6309
7644
0
5

253
29
10.9
2.2
chr1
3007005
3007230
-192464741
-
L1M3c
LINE/L1
-4668
1473
1226
7

2922.666667
17.33333333
6.633333333
7.866666667
chr1
3008117
3010670
nd
-
L1_Mur2
LINE/L1
nd
nd
nd
8
1811

2917
20
7.7
1.2
chr1
3008501
3009169
-192462802
+
RLTR26B_MM
LTR/ERVK
1
716
0
9

(slightly different since this is mm10), but similar lines as yours).
For now the -m option that would search again for nested elements is not implemented, but you should already get something much cleaner with the script I just pushed.
You are right, simple repeats cannot be nesting (they are 'added') - but unless you want to count them as well, it is a waste of space. It is easy to keep them if that's something people want, so I will make it an option.

EDIT:
ended up uploading a script that will fit your needs - different than the one to get more details about the nesting/nested blocks structures.

Thank you very much @4ureliek!


[Beta] regression in integration tests w/ async ember-data relationships

@Turbo87 this is the regression I mentioned yesterday on Slack. I finally got a minimal reproduction together: https://github.com/simonihmig/ember-mocha-demo
The failing test is this one: https://github.com/simonihmig/ember-mocha-demo/blob/master/tests/integration/components/my-component-test.js#L39-L42.
In the beforeEach I load a model parent, that has an async relationship to child. The loading of the child happens in the template: https://github.com/simonihmig/ember-mocha-demo/blob/master/app/templates/components/my-component.hbs#L4.
The test itself is passing, but some async callback of ember-data seems to run after the test has finished, causing a set on destroyed object error:

The following screenshot shows the _find function which seems to load the child record. As you can see this happens before the test's assertion:

The other breakpoint is within the then callback, and this happens after the assertion, and apparently after the test has been teared down, as the call to serializerForAdapter is causing the afore mentioned exception (the jsonapi serializer has already been destroyed, when it tries to set the store on it):

Adding await wait() fixes this: https://github.com/simonihmig/ember-mocha-demo/blob/master/tests/integration/components/my-component-test.js#L39-L42. So seems there is still some pending promise or run loop that is not correctly waited for before tearing down the test?
Also, when downgrading to 0.14.4 this error does not show up. As you said already, the root issue might be caused by the larger upstream changes in ember-test-helpers, but I filed this here for now...

@simonihmig - Can you confirm that https://github.com/emberjs/ember-test-helpers/pull/263 (which was released in<EMAIL_ADDRESS>fixes your real app also?

@rwjblue sure, wanted to do that already, but didn't find the time yet. Hopefully tomorrow, will keep you updated!

@rwjblue all tests are ✅  ✅  ✅     👏


Add support for private repos

Thanks for the excellent extension @zeke and @bfred-it!
Took a stab at adding support for private repos, since I use them on a day-to-day basis. I initially was going to make a request to https://github.com/user/repo/raw/master/package.json, but it 301s to a host that isn't allowed by the content security policy on the page.
I needed to move the request from the background page to the content script, because the current session cookie need to be sent with the request for auth w/ private repositories.

The background fetch was added for Firefox but it looks like this works. LGTM. @zeke?

I saw that https://github.com/user/repo/raw/master/package.json redirects to raw.githubusercontent.com anyway, the old url. Does https://raw.githubusercontent.com/user/repo/master/package.json work for private repos? Redirects take longer, it's best if we can avoid them
On a related note, do you know of a path to get the default branch rather than master?

Does https://raw.githubusercontent.com/user/repo/master/package.json work for private repos?

It does technically work, but the content security policy GitHub has in place has a whitelist of domains you can make requests to, and githubusercontent.com isn't in there, so the promise will reject. So it worked before because requests from the background page aren't subject to the CSP, but then you can't send the auth info needed for private repos.

On a related note, do you know of a path to get the default branch rather than master

I don't 😞. Having said that, is the preference to always show deps for the default branch, vs showing  the deps for the branch currently being viewed?

Thanks @DrewML! It would be nice to support this.

content security policy GitHub has in place has a whitelist of domains you can make requests to, and githubusercontent.com isn't in there.

☝  This is probably intentional to keep people from treating that domain as a CDN, but I can ping the GitHub security team and see about it. cc @tmaher

is the preference to always show deps for the default branch, vs showing the deps for the branch currently being viewed?

☝  I would think defaulting to the currently-viewed branch would make the most sense.
If @bfred-it is good with landing this, we should then remove background-fetch.js. Note also that the existing backgroundFetch method is used in two places.
Is there a CI service for browser extensions? Would be nice to get some tests in place for this project.

Sounds good. If GH ends up adding raw.githubusercontent.com to their CSP we can go back

Is there a CI service for browser extensions? Would be nice to get some tests in place for this project.

You can use the ChromeDriver w/ SauceLabs to load up an extension. Can't say I've tried it before, though. Would probably need to make sure we have an example repo that never gets touched or the tests could be flakey.

@zeke I think background-fetch is still still required to access the npm registry

@zeke are we good to merge this?

🚢

🎉 Thanks guys!


Changed rfq.sh to reflect updated interface

Change-type: patch
Signed-off-by: Ryan Cooke<EMAIL_ADDRESS>

ping @rcooke-warwick

ping @rcooke-warwick - can we merge this?

@nazrhom I think this can be merged


Change int to long

Can one of the admins verify this patch?

Hi @chfunk, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.azure.com.

TTYL, AZPRBOT;

Can one of the admins verify this patch?

Hi @chfunk, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, AZPRBOT;

@chfunk was there an accompanying change in hydra-specs-pr this was generated from?

Yes, it can be found here: https://github.com/Azure/hydra-specs-pr/pull/1299

@azuresdkci add to whitelist


traffic management section before telemetry section

moving PR to here:
https://github.com/IBM/istio101/pull/90


Refresh thanosbench

AC:

./benchmark  should be a separate repo in thanos-io org. (TO decide)
thanosbench should be up to date with newest Thanos.

I' m interesting on this. But with some questions.

Rename to thanosbench or remain benchmark?
Do we have any plan for this part? Will it be something like prombench?
Don't have any ideas about this https://github.com/thanos-io/thanos/issues/1180#issuecomment-512626504

Valid questions!
So first of all. The plan is to remove the benchmark directory totally. It's super old and not maintained. Let's stop confusing users: https://github.com/thanos-io/thanos/pull/1423

I think thanosbench makes sense (:
Have some rough ideas, but TBH for recent benchmarks, I used this: https://github.com/thanos-io/thanos/tree/865d5ec710b5651ead08a7dc73864a6f5dbeeaa9/tutorials/kubernetes-demo/blockgen and some infrastracture definitions in Go: https://github.com/bwplotka/mimic/tree/master/examples/prometheus-remote-read-benchmark
Commented.

Overall I am not sure if separate project even makes sense. Benefits of the same repo:

It's easier to synchronize versions of deps, thanos vs benchmarks
Reuse CI, tooling etc.

here are a couple of tools that can help
https://github.com/open-fresh/avalanche
https://github.com/m3db/promremotebench
And here is a bench test setup that I started on the ingestion path.
https://github.com/krasi-georgiev/benchTSDB

Created https://github.com/thanos-io/thanosbench
The initial idea is to have a place that will hold:

CLI / docker tools for benchmarking

Querying
Generating blocks of different size and compactions, downsampling structure - for both object storage as well as filesystem

Kubernetes templates based on Go (mimic) that will generate deployment YAMLs for different cases.
Tooling to build thanos-io/thanos certain commit into docker image for Kubernetes use

That's for start. Feedback welcome, what would you like to see more?

https://github.com/thanos-io/thanosbench exists. Let's create issues on that repo related to benchmarking.


Introduce a command to replace contents of selected html elements

This makes it easier for clients to implement support for updating previously displayed values in response to DisplayedValueUpdated events.

Abandon this PR since we are going to take a different approach.


Token count endpoint

Feature request
I propose adding a new endpoint to the api that only returns the number of tokens in a string, without embedding the text as well.
Motivation
In some applications one wants to know how many tokens a string consists of, without embedding the text as well. For instance, in rag-applications, one first chunks documents into smaller pieces, and then embeds each of these. Recursive chunking strategies does not need embeddings to decide breakpoints, only the token count. While the embedding-endpoint returns the token-count, it is a very inefficient way of getting the count. The benefit of adding this to the embedding server API is that the user does not need to know which embedding model is used, or access to the tokenizer.
Your contribution
NA

Hi @Haakooto,
Thanks for your suggestion!
While a token count API could be nice to have, please note that tokenization schemes can be different between embedding models. Therefore such a so a universal token count API still would need to use the specific tokenizer of the embedding model you want to use down-stream in order to produce accurate counts.
If @michaelfeil sees this within scope of the project this should be not too hard to add.


Auto run start as a service on Windows

Good morning everyone.
To automatically start the Superset service, without starting the Windows session, every time I restart my computer I have to start my Windows session and open the CMD terminal and execute the following lines.
C:> set FLASK_APP=superset
C:> superset run -p 8088
Can someone help me automate starting the service.
Thank you very much for your attention.

Hello, @bumasl
I strongly suggest that you run superset in the IIS.
Please check https://learn.microsoft.com/en-us/iis/extensions/httpplatformhandler/httpplatformhandler-configuration-reference.

This issue has gone stale, but also SUperset officially dues not support Windows. If you want to contribute toward windows support (package management, testing, documentation, etc) please feel free to contribute... lots of folks would be thankful. :)


Result of command: Notifications are not available: Couldn’t communicate with a helper application.

Hi everyone, i am currently seeing this issue inside the jamf logs:
Result of command:
Notifications are not available: Couldn’t communicate with a helper application.
I am pushing the alert.mobileconfig, so it should work. What could be wrong?

Are you running the dialog command as the user? Have you checked this: https://github.com/bartreardon/swiftDialog/wiki/Notifications#alert-mobileconfig

You'll want to run swiftDialog as the logged in user, with a function like this: https://scriptingosx.com/2020/08/running-a-command-as-another-user/
The 2.1.0 RC1 has an updated launcher so you don't have to run swiftDialog as the logged in user, so that will be out of beta soon. https://github.com/bartreardon/swiftDialog/releases

Are you running the dialog command as the user? Have you checked this: https://github.com/bartreardon/swiftDialog/wiki/Notifications#alert-mobileconfig

I am using the Files and Processes -> execute command with Jamf Pro.

You'll want to run swiftDialog as the logged in user, with a function like this: https://scriptingosx.com/2020/08/running-a-command-as-another-user/
The 2.1.0 RC1 has an updated launcher so you don't have to run swiftDialog as the logged in user, so that will be out of beta soon. https://github.com/bartreardon/swiftDialog/releases

Could you please tell me how to do that?

I tried to push the 2.1.0 RC1 but i receive the same error. What could be the issue?

I am using the Files and Processes -> execute command with Jamf Pro.

What's the full command that you're putting in here?

I am using the Files and Processes -> execute command with Jamf Pro.

What's the full command that you're putting in here?

dialog --notification --title "MY TITLE" --message "MY MESSAGE" --icon "/ICONPATH.PNG"

dialog --notification --title "MY TITLE" --message "MY MESSAGE" --icon "/ICONPATH.PNG"

ok, that isn't going to work pre v2.1. the notification needs to run as the user and when you run a command with "Files and Processes" it runs at a system level (root but not really) which does not have the ability to receive system notifications.
can you double check the dialog launcher for me: wc -l $(which dialog)  - if you've installed 2.1 RC1 or RC2 this should have 28 lines

28 yes

dialog --notification --title "MY TITLE" --message "MY MESSAGE" --icon "/ICONPATH.PNG"

ok, that isn't going to work pre v2.1. the notification needs to run as the user and when you run a command with "Files and Processes" it runs at a system level (root but not really) which does not have the ability to receive system notifications.
can you double check the dialog launcher for me: wc -l $(which dialog)  - if you've installed 2.1 RC1 or RC2 this should have 28 lines

28 exactly

Hi.
I'm seeing this error as well (v<IP_ADDRESS>48) but not on all Macs. I have tried launching dialog with /usr/local/bin/dialog --notification --title TITLE --message MESSAGE and /bin/launchctl asuser "${CurrentlyLoggedInUserUID}" "/Library/Application Support/Dialog/Dialog.app/Contents/MacOS/Dialog --notification --title TITLE --message MESSAGE" I've even tried pre-launching Dialog.app /bin/launchctl asuser "${CurrentlyLoggedInUserUID}" "/Library/Application Support/Dialog/Dialog.app as that was something I found when Googling. I have a notifications payload deployed with critical alerts turned off.
Any ideas?
Shannon

in 2.1+ just run /usr/local/bin/dialog
don't worry about trying to determine the user, fiddling with launchctl asuser etc - the updated dialog launcher handles that.
I have a test notification policy and this works fine for sending the notification:

That's how I have it currently. The script is running as part of a check-in policy in Jamf
#!/bin/sh
sD="/usr/local/bin/dialog"
"${sD}" --notification --title "TITLE" --message "MESSAGE"

On the off-chance the following proves helpful:
https://snelson.us/2023/03/custom-branded-notifications-messages-with-swiftdialog/

Same issue on Mosyle MDM using both a notification profile via Mosyle and the custom profile provided in the wiki. Tried running command as user as well. No dice
28 lines

He can recreate this, noticing it this week. Kandji, swiftDialog <IP_ADDRESS>91, Ventura 13.2.1 and 13.4.1 (c). Using banner or alert config profile, profile installed before swiftDialog is.
Simple command like ```#!/bin/bash
/usr/local/bin/dialog --notification --title "TITLE" --message "MESSAGE"```

This now appears fixed when testing with the 2.3.0 Beta 2!

should be fixed in the release version of 2.3

Notifications are working for me on 2.3.1. MDM Kandji, Alerts config profile in place. I would like to hear input from others.

closing this as fixed - if there's any issues, LMK and I can re-open


initial value via 'selection' does not work

this can be seen in the demo

oh yeah, I must have broken it.  Will get this fixed tonight.

@ssendev fixed as of version 0.0.6

@ssendev you might want to install 0.0.9, that will install the bower dependency properly.

cool that was fast. it is working now. i have made a small enhancement #2 but am not entirely sure it is bulletproof


feat: allow custom max new tokens settings

Any updates? Thanks :)

Any update? I think this is an important feature


Consider implementing RTP MIDI 1.0 pluggable transport

Not currently planned. Could happen in the future. For now, we're focusing on the MIDI 2.0 Network protocol.


Meshery: Unnecessary Kubernetes connection dependency

Description
In more than one example, Meshery is unnecessarily dependent upon having a healthy connection to an active Kubernetes cluster. This issue documents an example with Grafana connections, however, there are other examples of this unnecessary dependency.
Expected Behavior
Users should be able to connect Grafana to Meshery without dependency on Meshery being connected to Kubernetes.
Screen Capture
Video describing issue -

@Aisuko or @vijcheru would you like to look into this?

@Aisuko or @vijcheru would you like to look into this?

I will take a look and  @vijcheru  you can do this first, I have another chart PR and godoc issue of meshery-common-library on my schedule.

I think we have eliminated each of these issues...


Ask for confirmation when canceling notes which has text entered.

When commenting on a note, one might click CANCEL instead of OK, and all the text they've entered would disappear.
That is especially likely as CANCEL and OK buttons are close together.
It would be nice if CANCEL button would ask for confirmation if any text was entered in the comment field (similarly how  CLOSE button asks). Of course if no text was entered, note window could be dismissed without any confirmation, as there is not a danger of data loss.

Okay, but since I promised translators not to add any more strings, I've marked this for 1.x or 2.0.

Done in 2.0.

@mnalis @Zverik I suggest to modify notesCancelMessage and editorCloseMessage to respectively

[Cancel your OSM note? / Close the editor?] You will lose your unsaved changes.

This will make the text consistent and keep it comprehensive for users why -and where- they are being shown this message.
You may choose to add the second part on a new line, or as a seperate translation so it doesn't have to be translated twice.
Otherwise, I would suggest for editorCloseMessage to keep the previous translation or change it to

Discard changes?

Recently, the suggestion was accepted to change it to "Discard changes without saving?". Noteably, "Discard" is the same as "without saving". I would understand this if it was "Discard changes without saving as a draft?", but this takes longer to read.


Improve font loading

Currently, font loading is working via a custom Document with link elements being injected into the head https://github.com/jpmorganchase/mosaic/blob/main/packages/site-components/src/Document.tsx
This affects the initial paint time and slows down the site loading. Ideally, Mosaic should rely on next/font here, e.g. https://github.com/jpmorganchase/salt-ds/pull/1509

https://github.com/jpmorganchase/mosaic/pull/358


Feature: Enhance User Feedback for Web Access Type Favorites

Overview
This PR introduces a user-friendly message that enhances the feedback provided when selecting a favorite with access_type set to web. This message informs the user about the account name, account number, and the AWS IAM role name being accessed, providing a clearer understanding of the federating process.
Changes

Added a fmt.Printf statement to display the federating account's name, account number, and AWS IAM role name before opening the browser for web access type favorites.

Testing

Manual tests were conducted to ensure the message correctly displays the intended information.
Verified that the browser opens as expected and the federating process proceeds without any issues.

This looks like:
Choose a Favorite: bshutter-sandbox
Federating into bshutter-sandbox<PHONE_NUMBER>08) via ctcorp-delivery


chrome_url_fetcher folders in Program Files

Why do I have these folders prefixed with chrome_url_fetcher_ in my C:\Program Files ? Even if I delete them - every time I run Supermium new folders like these are created. How can I prevent these folders - or at least tell Supermium to create them in the %TEMP% folder rather than Program Files ?

I don't have them under Windows 11. What OS are you using?

It is disabled.

Yep, is a brave thing.  NO FIX for it.  Just create a batch file to delete them once you startup PC.

I believe the solution is to remove the first check - IsUserAnAdmin()
base/files/file_util_win.cc::bool CreateNewTempDirectory(...) {
if (::IsUserAnAdmin() && PathService::Get(DIR_PROGRAM_FILES, &parent_dir) &&

It can be patched with a HEX editor:

for chrome.dll 109.0.5414.75 64bit

0725A228: 74 -> EB

for chrome.dll 109.0.4514.5414.120 64bit:

07280058: 74 -> EB

I don't know the locations for other versions of the DLL - but the ultimate solution is to recompile those DLLs without the mentioned check and update the releases on GitHub.

For Supermium 126.0.6478.256 64-bit the offset in chrome.dll is 6753E3B (byte sequence is 74 0E 48 8D 4C 24 40 E8 F9 E9 FF FA 84 C0 75 60) and again 0x74 should be replaced with 0xEB.

How about having it all go to one folder in the folder that it makes in the user's profile instead?


Add Leagues

Primeira Liga league added to conf.
Serie A league added to conf(Italy).
Eredivisie  league added to conf.
Brazil Serie A league added to conf.
Ligue 1 league added to conf.
League One (EFL League One (English Soccer Second League)) added to conf.
Other leagues SBR does not seem to support are:
Kontinental Hockey League,
Turkish Supir Lig (Turkish Soccer Premier League)

Will make small changes to some league abbreviations and add new classes to init.py.

Will make small changes to some league abbreviations and add new classes to init.py.


certbot not recognizing authenticator

Hi, I installed certbot from the Rocky Linux repos, and both it and the plugin are listed in pip but it keeps telling me the authenticator is unknown. All my certbot files are in /usr/lib/python3.9/site-packages and the plugin files are in /usr/local/lib64/python3.9/site-packages. Certbot version is 2.6.0.

This sounds like the same issue as the EPEL9 package: https://community.letsencrypt.org/t/how-do-i-make-certbot-find-use-an-installed-plugin/198647/18
If so, you won't be able to mix the RPM and the pip package. You'll need to use the Certbot pip or snap instructions rather than the EPEL package.

Ah, I see. It may be the same package as I have EPEL repos as well.

@alexzorin I don't really get why there would be any problem created by using an RPM, if it shows up in pip all the same, but I am not an expert. Does it need the python venv for some reason? I used the snap for a good while, but after looking into snap some I removed it since apparently on RHEL-based distros in particular it is not very secure due to the lack of Apparmor for some reason.

It's not really about whether it's RPM or pip.
The maintainers of the Certbot package for EPEL9 decided to use python -s, which prevents Python from loading any "user packages" (i.e. those installed in /usr/local/). If you install a package using pip, that's exactly where it goes.
I don't know why they decided to do this, we didn't suggest it and as far as I know, no other distributions do it either.
If you don't want to use snap, my suggestion is to use https://certbot.eff.org/instructions?ws=other&os=pip&tab=wildcard instead of the EPEL9 Certbot package.


Where is Customer ID used?

Issue in ./help/destinations/catalog/advertising/google-dv360.md
In the list of Prerequisites, it is not clear where the Customer ID will be used. Also, the Account ID information must be fetched from Google Representative. Not sure how Adobe client care or Adobe representative can help.

Thank you for reporting this issue. We will review and update the documentation.
Internal tracking: https://jira.corp.adobe.com/browse/PLAT-102524

We've updated the Google destinations pages with the correct Account and Customer IDs.


ci(monorepo): standardized script naming convention

Signed-off-by: Rifa Achrinza<EMAIL_ADDRESS>

Forcing merge as fixing the CI is not within the scope of the project.


Installer fails without gnome components

The sift-config-tools portion of the install process will fail if certain GNOME components are not present. This has been tested on Ubuntu 16.04. The packages required include 'gnome-shell' and 'gnome-shell-extension-dashtodock'. Ideally if they're required, they may need to be pulled by salt. Otherwise, is there a document showing required core components?
Thanks!
Here's relevant output:
     amazon-ebs: >> Running: /usr/local/etc/foremost.conf
     amazon-ebs: >> Running: sift-config-tools
     amazon-ebs: Update returned exit code not zero
     amazon-ebs: Error: Update returned exit code not zero
     amazon-ebs:     at ChildProcess.<anonymous> (/snapshot/sift-cli/sift-cli.js:545:23)
     amazon-ebs:     at ChildProcess.emit (events.js:315:20)
     amazon-ebs:     at maybeClose (internal/child_process.js:1021:16)
     amazon-ebs:     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
     amazon-ebs:
     amazon-ebs:
     amazon-ebs: ----- PLEASE READ ----------------------
     amazon-ebs:
     amazon-ebs: A lot of failures are caused by the apt system being locked
     amazon-ebs: or unhealthy.
     amazon-ebs:
     amazon-ebs: Before opening an issue in GitHub, please check to see if
     amazon-ebs: your apt system is healthy.
     amazon-ebs:
     amazon-ebs: Try running 'apt-get update' then remove any packages that
     amazon-ebs: aren't used by running 'apt-get autoremove'
     amazon-ebs:

# [ERROR   ] Command 'gsettings set org.gnome.shell favorite-apps "['gnome-terminal.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop']"' failed with return code: 1
# [ERROR   ] stderr: No such schema ?org.gnome.shell?
# [ERROR   ] retcode: 1

16.04 support is being dropped, 18.04 is supported and 20.04 is in the works
Sent from my iPhone

On Aug 26, 2020, at 07:34, Dominik L. Borkowski<EMAIL_ADDRESS>wrote:

The sift-config-tools portion of the install process will fail if certain GNOME components are not present. This has been tested on Ubuntu 16.04. The packages required include 'gnome-shell' and 'gnome-shell-extension-dashtodock'. Ideally if they're required, they may need to be pulled by salt. Otherwise, is there a document showing required core components?
Thanks!
Here's relevant output:
 amazon-ebs: >> Running: /usr/local/etc/foremost.conf
 amazon-ebs: >> Running: sift-config-tools
 amazon-ebs: Update returned exit code not zero
 amazon-ebs: Error: Update returned exit code not zero
 amazon-ebs:     at ChildProcess.<anonymous> (/snapshot/sift-cli/sift-cli.js:545:23)
 amazon-ebs:     at ChildProcess.emit (events.js:315:20)
 amazon-ebs:     at maybeClose (internal/child_process.js:1021:16)
 amazon-ebs:     at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
 amazon-ebs:
 amazon-ebs:
 amazon-ebs: ----- PLEASE READ ----------------------
 amazon-ebs:
 amazon-ebs: A lot of failures are caused by the apt system being locked
 amazon-ebs: or unhealthy.
 amazon-ebs:
 amazon-ebs: Before opening an issue in GitHub, please check to see if
 amazon-ebs: your apt system is healthy.
 amazon-ebs:
 amazon-ebs: Try running 'apt-get update' then remove any packages that
 amazon-ebs: aren't used by running 'apt-get autoremove'
 amazon-ebs:

[ERROR   ] Command 'gsettings set org.gnome.shell favorite-apps "['gnome-terminal.desktop', 'firefox.desktop', 'org.gnome.Nautilus.desktop']"' failed with return code: 1
[ERROR   ] stderr: No such schema ?org.gnome.shell?
[ERROR   ] retcode: 1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Sorry, it was a typo. The system in question is vanilla 18.04 with all the relevant updates.

Interesting. I have not seen this behavior.

Our default approach is to use XFCE with ubuntu, and remove gnome components. That's likely why we've ran into these issues. Removing those two packages in question should reproduce the problem.

Ah. Yeah gnome is the only official supported option. There are just too many variations to support otherwise.
If you don’t care about user and ui preferences you can simple install if using server mode. This just installs all tools and packages and the like with no user customizations.
Erik
Sent from my iPhone

On Sep 1, 2020, at 09:26, Dominik L. Borkowski<EMAIL_ADDRESS>wrote:

Our default approach is to use XFCE with ubuntu, and remove gnome components. That's likely why we've ran into these issues. Removing those two packages in question should reproduce the problem.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

If you'd like to continue talking about this let me know, but for now I'm going to close this.


What is the default target? (please clarify)

This page shows a default target of ES3, and this page shows a default target of ES5 – is this intentional (when a tsconfig file is used, the default changes?) or is this a "bug"?
Also, what is the default for "module", or does that depend on the target?
Thanks. =)

I'm not entirely familiar with what a JSON schema considers as a default. By default, we generate a tsconfig.json that uses ES5 as a target, but if the value is omitted, we will default to ES3.
I think it's probably the latter, so schemastore probably has it wrong.
The default for module is that there is no module system at all; you're just writing script files that don't utilize modules at all.
Also, while schemastore lists moduleResolution's default as classic, it depends on your module option (i.e. using node resolution for commonjs, but not for amd).

Actually, I'm not 100% sure, so @paulvanbrenk and @madskristensen, can you answer what "default" is intended to mean?

That's probably a bug in the schema. I'll update that.

@mhegazy I don't think that this has been fixed yet.

@paulvanbrenk commented on a PR to fix this one: https://github.com/SchemaStore/schemastore/pull/80/files#r48884389

Ah cool, thanks guys. =)

And a better PR: https://github.com/SchemaStore/schemastore/pull/136


有个bug，已经录像，如何提交给你呢？

@sunnyhigher you can provide demo project, gif, video link whatever easy for you to describe the issue


opm update with version 1.27.1 and regenerated catalog with snapshot ols-bnxm2

Description
Updated OPM version to 1.27.1
Matched konflux snapshot [ols-bnxm2] with bundle CSV references - with that created new set of catalog images .
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[X ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

/test bundle-e2e-4-15

/lgtm

/approve

/override "Red Hat Konflux / ols-e2e-tests-rosa / bundle"

/override "Red Hat Konflux / ols-enterprise-contract / bundle"


[TextField] the func clearValue is not valid when the props multiLine={true}

when the Component props multiLine={true},then clearValue() is not effect.Neither is setValue()

This is a duplicate of #1001.
@hai-cea I think you can close it.

yes,same problem.I close this issue


Adapt find_unused_parameters warning

🚀 Feature
Latter PyTorch versions introduced the following warning
https://github.com/pytorch/pytorch/blob/d0adb5ff264df8e0e057ce1178feb30198c601d2/torch/csrc/distributed/c10d/reducer.cpp#L1256-L1264
which appears when find_unused_parameters=True but it's not necessary.
Motivation
We set find_unused_parameters=True by default, so this warning will appear for a large percentage of users.
Pitch
Catch this warning and produce another one that explicitly mentions how to modify the strategy passed.

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @borda @akihironitta

This is blocked by https://github.com/pytorch/pytorch/issues/75725


As a developer I want to have automatic publishing and testing when code is pushed to the main branch

1.a) Automate build, test, and publishing with GitHub Workflows
Acceptance:

The test get run when code is pushed to main branch
The code gets published to all three platform types (Windows, Linux, MacOs)

It is done


RFC: roots/wordpress package switching the "no-content" WordPress release

Existing issue: https://github.com/roots/wordpress/issues/3
This is an RFC, and proposal, to change the roots/wordpress Composer package (defined by this repository) to contain the "no-content" WordPress release which means none of the default themes will be included.
Currently, roots/wordpress uses the releases from https://github.com/WordPress/WordPress which includes all default themes. There's a few downsides to this:

WordPress' site health flags  - "Have a default theme available" is marked as critical
it's wasteful and inefficient to include all the default themes when they almost always won't be used

However, making this change is a breaking change as consumers of roots/wordpress might be relying on a default theme being included.
Release plan
We plan to use the release of WordPress 6.0 as a natural point to make this breaking change. The published version of roots/wordpress for 6.0 will use the "no-content" WordPress release without any default themes included.
In the spirit of Bedrock, any default theme can be included by adding it as an explicit dependency via WordPress Packagist packages:
"require": {
   "roots/wordpress": "6.0",
   "wpackagist-theme/twentytwentytwo":"*"
},

Implementation
Right now roots/wordpress is built from GitHub workflows in this repo. We're going to (finally) be switching to https://github.com/roots/wordpress-packager and using @LeoColomb's improvements to let us build multiple versions of the package, including switching roots/wordpress to the no-content version.
As an added bonus, we can remove Bedrock's register theme directory mu-plugin
cc @LeoColomb @roots/everyone

I can only support the switch to the "no-content" variant, which is a really good idea. 👍
That said I'd like to express few concerns on the plan:

The breaking change at roots/wordpress level will not be easy to manage, and might be quite unexpected.

It removes all bundled themes (as well as Hello Dolly plugin but this one is safe to remove I guess).

Keeping a single repo for this change can be confusing:

6.0 might not even be a "major" version from WordPress POV, I mean more major than 5.9 for example.
Even if 6.0 is considered as semver-major for WordPress, there is no way to express the breaking change from roots/wordpress perspective.
Package consumers might quite hardly understand why it happens, and if and how it is possible to keep coherent deployment.

My suggestion would be to create another package for the new variant.
Eventually do the same for all variants to offer the ability to chose to the consumers, especially because some variants can support beta/RC builds effortless, making them perfect for testing.
Detaching these packages into another organisation might be handy to do that, eg. like @composer-wordpress (disclaimer: I'm the maintainer of this org).
This can help to build a proper documentation, to easily (and securely) use the build script, and be more robust for next breaking change. 😎✨
Thoughts? 😊

The proposed plan wasn't using 6.0 because it signified any major version (in terms of semver). It was mainly just an arbitrary big milestone we could point to in the future.

Detaching these packages into another organisation might be handy to do that, eg. like @composer-wordpress (disclaimer: I'm the maintainer of this org).

Disclaimer: there's obviously a bit of selfish bias and motivation for us wanting to keep it under roots/wordpress which we'll admit first.
However, I think moving to another org/package would just increase confusion instead of clarifying the situation. Since roots/wordpress would remain heavily used regardless of us suggesting a new package.
So I think the main decision point is keeping roots/wordpress as is (with content) and introducing a new wordpress-no-content package. Or the plan outlined in this issue originally.
I think we all agree that making this breaking change isn't 100% ideal, but it might be worth the possible breakage because it's the proper long-term solution?
I'm also wondering if there's any other Composer features we could take advantage of to make this plan work better. Maybe we could add a suggest package for wpackagist-theme/twentytwentytwo and leverage the message to include some information about the migration?

I feel that while we should make every effort to ease a transition, at the end of the day if you (the end consumer) bump up a major version on a package and don't have some level of testing to make sure it doesn't explode that's on you--the intent of the ecosystem is that it allows you to specify versions in a very granular way so that you can be safe and careful about managing them. Whether or not WordPress adheres to semver isn't necessarily the point: We do, so a major version bump is a clear signal to the user that they should expect things to change. If you chose not be be careful and take advantage of that system, you're kind of on your own because we can't predict (or be expected to account for) your behavior.
I'd prefer roots/wordpress to be the "canonical" version--the one we approve of--but we might consider setting up additional repos like roots/wordpress-themes or roots/wordpress-full and then using the suggest Composer field to point them out to folks. Those repos would in turn use the provide or replace field to point to roots/wordpress, theme repos, etc.
A potentially extreme solution but one that would potentially have the most visibilty would be to move to different repo entirely, i.e. roots/wp and then set the abandoned field on roots/wordpress, pointing people to roots/wp.

Whether or not WordPress adheres to semver isn't necessarily the point: We do, so a major version bump is a clear signal to the user that they should expect things to change.

The roots/wordpress package versions match the WordPress release versions though so unfortunately we can't follow semver either because they don't.

Fair, although I feel that the larger argument (managing versions and checking that they work is the responsibility of the end user) is still valid. Since suggest allows a message along with the recommended packages, we might consider adding a suggest message along the lines of
"suggest": {
  "roots/wordpress-full": "roots/wordpress will be removing themes starting with version 6; to include themes in your dependency use roots/wordpress-full instead"
}

As for next steps, I think we should publish two new packages now in advance:
roots/wordpress-full
Same as roots/wordpress right now, will continue to exist after if people prefer the full version.
roots/wordpress-no-content
This will become the same as roots/wordpress after the breaking change. This also means we'd have two identical packages with different names long-term so this one is debatable? The package description would make it clear what each one is though.
@LeoColomb what do you think?

This looks to be a good plan! 👍

This also means we'd have two identical packages with different names long-term so this one is debatable?

This is debatable indeed.
One option (my favorite 😄) would be to mark roots/wordpress as obsolete after some time and without switching it to no-content content.
This will force roots/wordpress consumers to select an option without introducing an unexpected policy change.
In bonus that avoid maintaining a duplicated package. 😊

Any timeline on when we can get a first release on this?
With the new packages -full and -no-content there's not really anything tying you to a major upstream milestone anymore. The sooner the better IMO :)

https://packagist.org/packages/roots/wordpress-full is published now 😄
Huge thanks to @LeoColomb for working on roots/wordpress-packager

https://packagist.org/packages/roots/wordpress-no-content is now available to use, fyi!


Fixed an issue with icons being too large

Closes #2951
Description
Changed boxSize to fontSize
Current behavior (updates)

New behavior

Is this a breaking change (Yes/No):
No.

Additional Information

@Haru-0001 @illionillion @zonoryo17 @0xtkey256
This bug should not be solved with fontSize, but rather what to do when the provided fontSize is undefined.
The value provided by the theme must also be taken into consideration and resolved.


Input: Refactor Resizer/Static CSS

Input: Refactor Resizer/Static CSS

This update refactors the (Input) Resizer and Static sub components to use
css.js instead of SCSS. This resolves style rendering issue when a
multiline Input is rendered within a Modal.
The SCSS implementation broke since the styles were no longer in the correct
scope.

https://github.com/helpscout/hsds-react/issues/499

Pull Request Test Coverage Report for Build 1710

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1709:
0.0%

Covered Lines:
6512

Relevant Lines:
6512

💛  - Coveralls

Demo URL
https://deploy-preview-500--hsds-react.netlify.com/?selectedKind=Input&selectedStory=multiline %2B resizable&full=0&addons=1&stories=1&panelRight=0&addonPanel=storybook%2Factions%2Factions-panel


Fix #2872: update rng doc about thread/fork-safety

as titled.

Codecov Report

Merging #2883 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2883      +/-   ##
==========================================
- Coverage   85.98%   85.97%   -0.01%
==========================================
  Files         325      325
  Lines       68110    68110
  Branches     7689     7689
==========================================
- Hits        58561    58558       -3
- Misses       8321     8323       +2
- Partials     1228     1229       +1

Thanks. Looks good. Merging.


affected/package:

What version of Go are you using (go version)?

$ go version
go version go1.19 linux/amd64

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOENV="/root/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/root/go/pkg/mod"
GONOPROXY="*.qianxin-inc.cn"
GONOSUMDB="*.qianxin-inc.cn"
GOOS="linux"
GOPATH="/root/go"
GOPRIVATE="*.qianxin-inc.cn"
GOPROXY="https://goproxy.cn,direct"
GOROOT="/root/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/root/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build273339992=/tmp/go-build -gno-record-gcc-switches"

What did you do?
running my program.
What did you expect to see?
my program can run correctly.
What did you see instead?
my program occur some errors,it has no any response.
my program is write by C, but some function are write by go,so i call go function in my c program.
i use go build -o libtest.so -buildmode=c-shared xxx.go xxx.go;
after execute the command, i get a libtest.so,then i call it by dlopen in c program. my c program run as a plugin in nginx.
after call the go function, the nginx has no any response.i use gdb to debug it,and found below backtrace:
(gdb) bt
#0  runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:520
#1  0x00007fff23c550f6 in runtime.futexsleep (addr=0xfffffffffffffe00, val=0, ns=140733793710979) at /usr/local/go/src/runtime/os_linux.go:44
#2  0x00007fff23c35667 in runtime.notetsleep_internal (n=0x7fff23dc66e8 <runtime.work+232>, ns=-1) at /usr/local/go/src/runtime/lock_futex.go:183
#3  0x00007fff23c35785 in runtime.notetsleepg (n=0x7fff23dc66e8 <runtime.work+232>, ns=-1) at /usr/local/go/src/runtime/lock_futex.go:237
#4  0x00007fff23c41338 in runtime.gcBgMarkStartWorkers () at /usr/local/go/src/runtime/mgc.go:1126
#5  0x00007fff23c3fd92 in runtime.gcStart (trigger=...) at /usr/local/go/src/runtime/mgc.go:637
#6  0x00007fff23c36e3d in runtime.mallocgc (size=565248, typ=0x7fff23cfd160, needzero=true) at /usr/local/go/src/runtime/malloc.go:1174
#7  0x00007fff23c6dfaa in runtime.growslice (et=, old=..., cap=) at /usr/local/go/src/runtime/slice.go:267
#8  0x00007fff23c918ef in regexp/syntax.(*compiler).inst (c=0xc000044bf8, op=) at /usr/local/go/src/regexp/syntax/compile.go:164
#9  regexp/syntax.(*compiler).rune (c=0xc000044bf8, r=[]int32 = {...}, flags=212) at /usr/local/go/src/regexp/syntax/compile.go:273
#10 0x00007fff23c90f1e in regexp/syntax.(*compiler).compile (c=0xc000044bf8, re=0xc000190000) at /usr/local/go/src/regexp/syntax/compile.go:101
#11 0x00007fff23c8f805 in regexp/syntax.Compile (re=0xc000190000) at /usr/local/go/src/regexp/syntax/compile.go:74
#12 0x00007fff23ca4a9a in regexp.compile (expr=,
mode=, longest=false) at /usr/local/go/src/regexp/regexp.go:178
#13 0x00007fff23ca5591 in regexp.Compile (expr="") at /usr/local/go/src/regexp/regexp.go:133
#14 regexp.MustCompile (str="") at /usr/local/go/src/regexp/regexp.go:309
#15 0x00007fff23ca8e0a in main.CheckPostAddress (buf=, bufLen=) at /root/codes/di_rechk/rechk.go:540
#16 0x00007fff23ca9a88 in _cgoexp_67df0785bef2_CheckPostAddress (a=0x7fffffffc740) at _cgo_gotypes.go:162
#17 0x00007fff23c2e21a in runtime.cgocallbackg1 (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at /usr/local/go/src/runtime/cgocall.go:306
#18 0x00007fff23c2dee9 in runtime.cgocallbackg (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at /usr/local/go/src/runtime/cgocall.go:232
#19 0x00007fff23c83791 in runtime.cgocallbackg (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at :1
#20 0x00007fff23c813f3 in runtime.cgocallback () at /usr/local/go/src/runtime/asm_amd64.s:915
#21 0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#22 0x0000000000000000 in ?? ()
(gdb) info goroutines

17 syscall  runtime.notetsleepg
2 waiting  runtime.gopark
3 waiting  runtime.gopark
4 waiting  runtime.gopark
19 runnable runtime.gcBgMarkWorker

(gdb) goroutine 17 bt
#0  runtime.notetsleepg (n=0x7fff23dc66e8 <runtime.work+232>, ns=-1) at /usr/local/go/src/runtime/lock_futex.go:237
#1  0x00007fff23c41338 in runtime.gcBgMarkStartWorkers () at /usr/local/go/src/runtime/mgc.go:1126
#2  0x00007fff23c3fd92 in runtime.gcStart (trigger=...) at /usr/local/go/src/runtime/mgc.go:637
#3  0x00007fff23c36e3d in runtime.mallocgc (size=565248, typ=0x7fff23cfd160, needzero=true) at /usr/local/go/src/runtime/malloc.go:1174
#4  0x00007fff23c6dfaa in runtime.growslice (et=, old=..., cap=) at /usr/local/go/src/runtime/slice.go:267
#5  0x00007fff23c918ef in regexp/syntax.(*compiler).inst (c=0xc000044bf8, op=) at /usr/local/go/src/regexp/syntax/compile.go:164
#6  regexp/syntax.(*compiler).rune (c=0xc000044bf8, r=[]int32 = {...}, flags=212) at /usr/local/go/src/regexp/syntax/compile.go:273
#7  0x00007fff23c90f1e in regexp/syntax.(*compiler).compile (c=0xc000044bf8, re=0xc00022a000) at /usr/local/go/src/regexp/syntax/compile.go:101
#8  0x00007fff23c8f805 in regexp/syntax.Compile (re=0xc00022a000) at /usr/local/go/src/regexp/syntax/compile.go:74
#9  0x00007fff23ca4a9a in regexp.compile (expr=,
mode=, longest=false) at /usr/local/go/src/regexp/regexp.go:178
#10 0x00007fff23ca5591 in regexp.Compile (expr=""") at /usr/local/go/src/regexp/regexp.go:133
#11 regexp.MustCompile (str=""") at /usr/local/go/src/regexp/regexp.go:309
#12 0x00007fff23ca8e0a in main.CheckPostAddress (buf=, bufLen=) at /root/codes/di_rechk/rechk.go:540
#13 0x00007fff23ca9a88 in _cgoexp_67df0785bef2_CheckPostAddress (a=0x7fffffffc740) at _cgo_gotypes.go:162
#14 0x00007fff23c2e21a in runtime.cgocallbackg1 (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at /usr/local/go/src/runtime/cgocall.go:306
#15 0x00007fff23c2dee9 in runtime.cgocallbackg (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at /usr/local/go/src/runtime/cgocall.go:232
#16 0x00007fff23c83791 in runtime.cgocallbackg (fn=0x7fff23ca9a60 <_cgoexp_67df0785bef2_CheckPostAddress>, frame=0x7fffffffc740, ctxt=0)
at :1
#17 0x00007fff23c813f3 in runtime.cgocallback () at /usr/local/go/src/runtime/asm_amd64.s:915
#18 0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#19 0x0000000000000000 in ?? ()
(gdb) goroutine 2 bt
#0  runtime.gopark (unlockf=, lock=, reason=, traceEv=, traceskip=)
at /usr/local/go/src/runtime/proc.go:367
#1  0x00007fff23c5b86d in runtime.goparkunlock (reason=, traceEv=, traceskip=, lock=)
at /usr/local/go/src/runtime/proc.go:372
#2  runtime.forcegchelper () at /usr/local/go/src/runtime/proc.go:306
#3  0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#4  0x0000000000000000 in ?? ()
(gdb) goroutine 3 bt
#0  runtime.gopark (unlockf=, lock=, reason=, traceEv=, traceskip=)
at /usr/local/go/src/runtime/proc.go:367
#1  0x00007fff23c48ee8 in runtime.goparkunlock (reason=, traceEv=, traceskip=, lock=)
at /usr/local/go/src/runtime/proc.go:372
#2  runtime.bgsweep () at /usr/local/go/src/runtime/mgcsweep.go:163
#3  0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#4  0x0000000000000000 in ?? ()
(gdb) goroutine 4 bt
#0  runtime.gopark (unlockf=, lock=, reason=, traceEv=, traceskip=)
at /usr/local/go/src/runtime/proc.go:367
#1  0x00007fff23c46fed in runtime.goparkunlock (reason=, traceEv=, traceskip=, lock=)
at /usr/local/go/src/runtime/proc.go:372
#2  runtime.bgscavenge () at /usr/local/go/src/runtime/mgcscavenge.go:265
#3  0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#4  0x0000000000000000 in ?? ()
(gdb) goroutine 19 bt
#0  runtime.gcBgMarkWorker () at /usr/local/go/src/runtime/mgc.go:1166
#1  0x00007fff23c81601 in runtime.goexit () at /usr/local/go/src/runtime/asm_amd64.s:1581
#2  0x0000000000000000 in ?? ()
(gdb) info threads
Id   Target Id                                          Frame
1    Thread 0x7ffff7966b80 (LWP 2024707) "nginx"        runtime.futex () at /usr/local/go/src/runtime/sys_linux_amd64.s:520

2    Thread 0x7ffef1ffb700 (LWP 2024717) "nginx"        0x00007ffff7a483bf in __GI___clock_nanosleep (clock_id=clock_id@entry=0, flags=flags@entry=0,
req=req@entry=0x7ffef1ffae80, rem=rem@entry=0x0) at ../sysdeps/unix/sysv/linux/clock_nanosleep.c:78
3    Thread 0x7ffef27fc700 (LWP 2024718) "ZMQbg/Reaper" 0x00007ffff7a8a5ce in epoll_wait (epfd=42, events=events@entry=0x7ffef27fb200,
maxevents=maxevents@entry=256, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30
4    Thread 0x7ffef2ffd700 (LWP 2024719) "ZMQbg/IO/0"   0x00007ffff7a8a5ce in epoll_wait (epfd=44, events=events@entry=0x7ffef2ffc200,
maxevents=maxevents@entry=256, timeout=timeout@entry=-1) at ../sysdeps/unix/sysv/linux/epoll_wait.c:30

i don't know how to solve the problem.

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions


Best way creating npm library.

I have encountered a problem while creating npm library with Typescript. I have created a few react components. Creating declaration files and then combining all of them in one and declaring the module.
Where to put my .d.ts declarations when distributing npm package?

For an example of something that is built on TypeScript and is distributed on npm, take a look at RxJS.  There are a lot of considerations to distributing your code on npm that are well outside of the scope of just TypeScript.  You need to consider if you will distribute your code as CJS, UMD, ES6 (or even AMD) modules and what types of loaders you expect people to use your code with, etc.

We do not have a clear guidance here. we have some documentation https://github.com/Microsoft/TypeScript/wiki/Typings-for-npm-packages, but clearly this is not nearly sufficient.


If kafka not available, server starts reports error, but still seems to start

#2990 adds a retry loop to the initialisation of the kafka topic connector.
In the 'coco pharmaceuticals' environment our default configuration involves several servers
When an attempt is made to start a server, we try and create the topic connector for the cohort.
This fails (in my case the host isn't resolvable)
However I note the exception is being reported as:
                       error message is: OMAS-ASSET-CONSUMER-400-001 The Asset Consumer Open Metadata Access Service (OMAS) has been passed an invalid connection for publishing events.  The connection was Connection{displayName='null', description='null', connectorType=ConnectorType{displayName='Kafka Open Metadata Topic Connector', description='Kafka Open Metadata Topic Connector supports string based events over an Apache Kafka event bus.', connectorProviderClassName='org.odpi.openmetadata.adapters.eventbus.topic.kafka.KafkaOpenMetadataTopicProvider', recognizedAdditionalProperties=null, recognizedSecuredProperties=null, recognizedConfigurationProperties=[producer, consumer, local.server.id, sleepTime], qualifiedName='Kafka Open Metadata Topic Connector', additionalProperties=null, type=ElementType{elementTypeId='954421eb-33a6-462d-a8ca-b5709a1bd0d4', elementTypeName='ConnectorType', elementSuperTypeNames=null, elementTypeVersion=1, elementTypeDescription='A set of properties describing a type of connector.', elementSourceServer='null', elementOrigin=ElementOrigin{originCode=1, originName='Local to cohort', originDescription='The element is being maintained within one of the local cohort members. The metadata collection id is for one of the repositories in the cohort. This metadata collection id identifies the home repository for this element. '}, elementHomeMetadataCollectionId='null', elementHomeMetadataCollectionName='null', elementLicense='null'}, guid='3851e8d0-e343-400c-82cb-3918fed81da6', url='null', classifications=null}, endpoint=Endpoint{displayName='null', description='null', address='egeria.omag.server.cocoMDS2.omas.assetconsumer.outTopic', protocol='null', encryptionMethod='null', qualifiedName='null', additionalProperties=null, type=null, guid='null', url='null', classifications=null}, userId='null', configurationProperties={producer={bootstrap.servers=banana:9092, bring.up.retries=10}, local.server.id=b51a998c-68b0-4f36-9cd1-5cdb3420bf45, consumer={bootstrap.servers=banana:9092, bring.up.retries=10}}, qualifiedName='null', additionalProperties=null, extendedProperties=null, meanings=null, type=null, GUID='null', URL='null', classifications=null}.  The resulting exception of org.odpi.openmetadata.frameworks.connectors.ffdc.ConnectorCheckedException included the following message: OCF-KAFKA-TOPIC-CONNECTOR-400-002  Egeria was unable to initialize a connection to a Kafka cluster.  The message in the exception was: Failed to create new KafkaAdminClient

The details of this are useful. I can see why it is reported as being from ASSET_CONSUMER as that is the first OMAS initialised that discovers the error.
Secondly, and more importantly, after this initialisation fails, an attempt to query the configuration of the running server returns ok -- so the instance still exists
ie GET http://localhost:8080/open-metadata/admin-services/users/garygeeke/servers/cocoMDS2/instance/configuration
Either the server has started (with warnings if that makes sense), or it does not and reports an error.
Looks like the initialisation failure is not causing the required cleanup
Logs added to https://ibm.box.com/s/v2sq5erb8xujoy3lhy5redm002f856sb

Here's a few more examples of the response from the platform after this supposed failed startup:
jonesn:~/ $ http --pretty format GET http://localhost:8080/open-metadata/platform-services/users/garygeeke/server-platform/servers/cocoMDS2/is-known
HTTP/1.1 200
Connection: keep-alive
Content-Type: application/json
Date: Mon, 04 May 2020 14:40:27 GMT
Keep-Alive: timeout=60
Transfer-Encoding: chunked

{
    "class": "BooleanResponse",
    "flag": true,
    "relatedHTTPCode": 200
}

jonesn:~/ $ http --pretty format GET http://localhost:8080/open-metadata/platform-services/users/garygeeke/server-platform/servers/cocoMDS2/status
HTTP/1.1 200
Connection: keep-alive
Content-Type: application/json
Date: Mon, 04 May 2020 14:40:39 GMT
Keep-Alive: timeout=60
Transfer-Encoding: chunked

{
    "active": true,
    "class": "ServerStatusResponse",
    "relatedHTTPCode": 200,
    "serverName": "cocoMDS2",
    "serverStartTime": "2020-05-04T14:07:03.865+00:00"
}

jonesn:~/ $ http --pretty format GET http://localhost:8080/open-metadata/platform-services/users/garygeeke/server-platform/servers/active
HTTP/1.1 200
Connection: keep-alive
Content-Type: application/json
Date: Mon, 04 May 2020 14:41:07 GMT
Keep-Alive: timeout=60
Transfer-Encoding: chunked

{
    "class": "ServerListResponse",
    "relatedHTTPCode": 200,
    "serverList": [
        "cocoMDS2",
        "cocoMDS3",
        "cocoMDS5",
        "cocoMDS6"
    ]
}

We hit this issue, by defining just the subject area omas, the server started eventually after the retries and then accepts rest calls. I can supply the config call if required.

Just noticed that Subject Area OMAS is throwing exceptions and claiming it is Asset Consumer OMAS.   This is from the Subject Area OMAS initialize() method.
super.throwUnexpectedInitializationException(actionDescription,
                                                    AccessServiceDescription.ASSET_CONSUMER_OMAS.getAccessServiceFullName(),
                                                         error);

Also noticed that it registers a listener with the enterprise topic connector.  The listener creates a publisher which is passed the out topic connection.  However the publisher never creates the out topic connector (which embeds the Kafka connector) so it can never know that kafka is up or down.
@davidradl could you supply me with the configuration doc so I can understand which component is creating a connector to kafka.  Start up audit log would also be helpful

Raised #3070 to create the appropriate topics on start up for the subject area omas.

This issue is no longer current as the metadata servers wait for Kafka to become available as part of their start up processing.

This issue is no longer current as the metadata servers wait for Kafka to become available as part of their start up processing.


Filtering by value instead of text bug

Describe the bug
There are two main bug with the filtering and value attribute.
With the first bug, the combobox filters by value attribute after clicking on the suggested name.
For example, take the code:
<auro-menuoption value="WA" suggest="wa washington">       Washington     </auro-menuoption>
When you type in Washington and click on the filtered option everything works as intended. However, when you click on the combobox one more time, it no longer filters by the text value and instead filters by the value attribute.
With the second bug, when you click on the suggested name twice in a row, the value attribute overrides text value.
For example: in the combo box the text value Washington would be overridden with WA
To Reproduce
Steps to reproduce the behavior:

Go to https://auro.alaskaair.com/components/auro/combobox and under the Airports example
Type in idaho falls and click on idaho falls regional airport
Click on the Combo box again.
At this point, the combo box is now filtering by the value attribute. Click on idaho falls regional airport one more time.
Now the text value idaho falls regional airport turned into ida

Note: The moment you start typing again, it filters by the text value of the combo box.
Expected behavior
When you click on the combo box after having selected your location, I expect the combo box drop-down to filter by the text value instead of the value attribute.
I also expect to have the text value stay the same after clicking on it twice instead of it being replaced with the value attribute.
Screenshots

Desktop (please complete the following information):

Browser Chrome latest Version
Windows

Smartphone (please complete the following information):

Untested

Additional context
None

@jason-capsule42 , could you review this bug report? Thanks!

I just ran through this and validated the error. I should also note that this issue also happens directly if you do the following:

Type Seattle Tacoma International
Click on Seattle Tacoma International menuoption
See sea appear in the input