JAVA-1193: Replica metadata should be refreshed immediately when a DDL statement is executed.

I'm also including a fix for JAVA-1120 in the same PR as the affected code is pretty much the same.
Note that I don't have specific tests for JAVA-1120 but I did benchmark quickly the creation of 50 tables with default debouncer options. Without the fix it takes in avg. 50 secs on my laptop; with the fix, it takes 3 secs in avg.
The 3rd commit brings minor enhancements to SchemaChangesTest: missing assertions and verifications basically.

Added two new commits:

1de87db suppresses recursive call to submitNodeListRefresh()
b7e9635 optimizes token metadata computation during schema resfreshes (and makes it synchronous)

Please review those carefully as they affect sensitive areas, and I might have let slip something important.

Rebased and squashed on top of current 3.0.x.

We can probably limit the usage of TestUtils.nonDebouncingQueryOptions in some cases with JAVA-1120.  I'll work on that, would be a good way of ensuring this fix, as these options should no longer be needed in the schema change case.

Not sure why appveyor triggered a check here..please ignore that.

Looks like CI is happy with the removal of TestUtils.nonDebouncingQueryOptions, and more importantly, the overall build time remained constant.

Rebased and addressed feedback: the TokenMap class now caches all the information required to rebuild itself when only the schema has changed, but not the topology.

Looks good to me. We cache more info than before, but it's O(numTokens) so it should still be reasonable, even for large clusters.
@adutra could you squash the commits as appropriate, and reword the messages? (no "should be" or "consider...", just imperative sentences)


Fix rustc/rustdoc config values to be config-relative.

The rustc, rustdoc, rustc_wrapper, and rustc_workspace_wrapper config values (in the [build] table) were being interpreted literally. This caused a problem if you used a relative path like foo/rustc.  This would be interpreted as a relative path from whatever cwd cargo launches rustc from, which changes for different scenarios, making it essentially unusuable (since crates.io dependencies wouldn't be buildable).
Additionally, due to https://github.com/rust-lang/rust/issues/37868, it is a bad idea to use relative paths.
This changes it so that those paths are config-relative.  Bare names (like "my-rustc-program") still use PATH as before.
This also includes a commit to centralize the rustc-wrapper program used by several tests so that it isn't built multiple times (and to allow several tests to work on windows).
Fixes #8202

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 47a02919cc454ab1653cd2054653befd705a9899 has been approved by alexcrichton

:hourglass: Testing commit 47a02919cc454ab1653cd2054653befd705a9899 with merge 40b674cd1115299034fafa34e7db3a9140b48a49...

:sunny: Test successful - checks-actions
Approved by: alexcrichton
Pushing 40b674cd1115299034fafa34e7db3a9140b48a49 to master...


Documentation

 Issue by Cloudef
Tuesday Aug 18, 2015 at 15:14 GMT
Originally opened as https://github.com/Cloudef/wlc/issues/48

It would be nice to have documentation syntax in code so we can generate for example man pages for wlc API. Doxygen has been used before, but it may be worth to resee what are the options nowadays.

 Comment by Earnestly
Wednesday Sep 30, 2015 at 19:31 GMT

Here is a tentative (i.e. braindump) mockup that demonstrates what this could look like.
Given the function wlc_init, the comment block above it would look something like this:
/* -- NAME
 * initialize the wayland compositor
 *
 * -- DESCRIPTION
 * wlc_init() initializes the `interface` along with passing `argc` and
 * `argv` from main(), so wlc can rename the process it forks to cleanup
 * crashed parent process and do FD passing (non-logind).
 *
 * -- RETURN VALUE
 * Upon successful execution wlc_init() will return true.
 *
 * -- ERRORS
 * All errors encountered in wlc_init() are considered fatal and thus should
 * never really return false.
 *
 * -- NOTES
 * Avoid running unverified code before wlc_init() as wlc compositor may be run
 * with higher privileges on non logind systems where compositor binary needs
 * to be suid.
 *
 * -- ALSO SEE
 * wlc_interface(3)
 */
WLC_NONULLV(1) bool wlc_init(const struct wlc_interface *interface, int argc, char *argv[]);

The converstion to groff_man(7) should yeild something like this:
The backticks are expanded to .I (italics) or \fI...\fR.
Any reference to a function name in the form of foobar() is expanded out to .BR foobar () or \fBfoobar\fR().
Note that the entire SYNOPSIS section should be generated, the point of this format is to be both flexible, very man-pages(7) specific in layout and try to not let the generation get in the way of the author.
.TH WLC_INIT 3 2015-09-30 WLC "WLC API Functions"

.SH NAME
wlc_init \- initialize the wayland compositor

.SH SYNOPSIS
.B #include <wlc/wlc.h>

.BI "bool wlc_init(const struct wlc_interface " *interface ", int " argc ", char " *argv[] ");"

.SH DESCRIPTION
.BR wlc_init ()
initializes the
.I interface
along with passing
.I argc
and
.I argv
from
.BR main ()
, so wlc can rename the process it forks to cleanup crashed parent process and do FD passing (non-logind).

.SH RETURN VALUE
Upon successful execution
.BR wlc_init ()
will return true.

.SH ERRORS
All errors encountered in
.BR wlc_init ()
are considered fatal and thus should never really return false.

.SH NOTES
Avoid running unverified code before
.BR wlc_init ()
as wlc compositor may be run with higher privileges on non logind systems where compositor binary needs to be suid.

.SH ALSO SEE
.BR wlc_interface (3)

Which would should render something like this on the users screen via the normal man command:
WLC_INIT(3)                 WLC API Functions                WLC_INIT(3)

NAME
       wlc_init - initialise the wayland compositor

SYNOPSIS
       #include <wlc/wlc.h>

       bool  wlc_init(const  struct  wlc_interface *interface, int argc,
       char *argv[]);

DESCRIPTION
       wlc_init() initializes the interface along with passing argc  and
       argv  from  main()  ,  so  wlc can rename the process it forks to
       cleanup crashed parent process and do FD passing (non-logind).

RETURN VALUE
       Upon successful execution wlc_init() will return true.

ERRORS
       All errors encountered in wlc_init()  are  considered  fatal  and
       thus should never really return false.

NOTES
       Avoid running unverified code before wlc_init() as wlc compositor
       may be run with higher privileges on  non  logind  systems  where
       compositor binary needs to be suid.

ALSO SEE
       wlc_interface(3)

WLC                            2015-09-30                    WLC_INIT(3)

 Comment by vodik
Wednesday Sep 30, 2015 at 21:21 GMT

I wonder if clang can do it

 Comment by Cloudef
Wednesday Sep 30, 2015 at 21:21 GMT

This is not bad at all, and doesn't look too complicated to write generator for (apart from understanding bit of C for the function prototypes). If escaping is desired, it should be in way that is simplest for the parser. That is, do not provide many ways to escape things.

 Comment by Cloudef
Wednesday Sep 30, 2015 at 21:23 GMT

Clang was bit troubling with python at least. I've never used the C api though. Ragel can parse C nicely, but won't "understand" it. I think most documentation generators don't actually understand C, but I can see that becoming problematic in some scenarios, like having preprocessor definitions (often for symbol visibility, or compiler attributes) front of function declarations, or even worse libpng style macro function declarations.

 Comment by Earnestly
Wednesday Sep 30, 2015 at 22:58 GMT

There are several limitations to this approach.  The main one is you're essentially locking yourself to groff_man(7) as the bugs section of man(7) points out:
Most  of  the  macros  describe  formatting (e.g., font type and spacing)
instead of marking semantic content (e.g., this text is  a  reference  to
another  page),  compared to formats like mdoc and DocBook (even HTML has
more semantic markings).  This situation makes it harder to vary the  man
format for different media, to make the formatting consistent for a given
media, and to automatically insert cross-references.  By sticking to  the
safe  subset described above, it should be easier to automate transition‐
ing to a different reference page format in the future.

When doing parsing of semantic elements like the backticks one has to consider how it could be represented.
For example consider the text:
`foo bar()`

If we define backticks as .I and bar() as .BR bar () then the non-inline solution would be:
.I foo
.BI bar ()

This immediately presents lots of edge cases which would be ugly to parse.  The first is that bar() can no longer simply transform to .BR bar (), you need to know that you're inside italics mode.  This gets worse when you consider trailing punctution:
`foo bar(), baz`

Would become the following groff without inlining the macros:
.I foo
.BR bar () "" ,
.I baz

The use of "" above is to satify the nature of .BR which alternates each word with bold and roman (normal text), the "" is there to absorb the next bold effect.
However there is a rather nice solution to both of these issues but generally produces slightly less than pretty looking manuals.  This is the use of inline macros via the \f escape.
Consider again the first example of bold being used inside italics.  The inline solution (from a parsers perspective) to this would be:
\fIfoo \fBbar\fR\fI()\fR

And for the second example:
\fIfoo \Bbar\fR\fI(), bar\fR

Notice how we can allow unbalanced pairs, the first \fI does not have a corresponding \fR as it is consumed by the \fR which terminates the \fB which preceeded it, \fB itself also consuming the effect of \fI.  This is quite nice for parsers as they wouldn't need to care, each element can be treated in isolated.
That is to say, bar() can be translated to \fBbar\fR() directly without needing to worry about the surrounding context.  Likewise, a pair of backticks can be replaced with \fI and \fR respectively regardless of the contect.
Things to consider would be if you want this format to be more general.  This would almost certainly require the use of an IR, which the prompts the question of why not just use a well supported markup like restructed text or asciidoc directly?  These formats can both generate manuals fairly comfortably, all the tool here would need to do is parse the comment block and C definition below it.
If the manual generation isn't perfectly like man-pages(7) then it probably wouldn't be too difficult to adjust the output too.

 Comment by Earnestly
Thursday Oct 01, 2015 at 00:11 GMT

This is quite nice too https://github.com/numpy/numpy/blob/master/doc/HOWTO_DOCUMENT.rst.txt

 Comment by Earnestly
Thursday Oct 01, 2015 at 01:21 GMT

Heh, regex poorly all the things: (but as proof of concept it seems to work for the simple stuff I've thrown at, including some edge cases.)
# The .TH and SYNOPSIS sections would be generated from elsewhere.
teapot earnest %i master ~ cat foo
.TH WLC_INIT 3 2015-09-30 WLC "WLC API Functions"

-- NAME
initialize the wayland compositor

.SH SYNOPSIS
.B #include <wlc/wlc.h>

.BI "bool wlc_init(const struct wlc_interface " *interface ", int " argc ", char " *argv[] ");"

-- DESCRIPTION
wlc_init() initializes the `interface` along with passing `argc` and
`argv` from main(), so wlc can rename the process it forks to cleanup
crashed parent process and do FD passing (non-logind).

-- RETURN VALUE
Upon successful execution wlc_init() will return true.

-- ERRORS
All errors encountered in wlc_init() are considered fatal and thus should
never really return false.

-- NOTES
Avoid running unverified code before wlc_init() as wlc compositor may be run
with higher privileges on non logind systems where compositor binary needs
to be suid.

-- ALSO SEE
wlc_interface(3), wlc_output(3)

teapot earnest %i master ~ gman < foo
.TH WLC_INIT 3 2015-09-30 WLC "WLC API Functions"

.SH NAME
initialize the wayland compositor

.SH SYNOPSIS
.B #include <wlc/wlc.h>

.BI "bool wlc_init(const struct wlc_interface " *interface ", int " argc ", char " *argv[] ");"

.SH DESCRIPTION
\fBwlc_init\fR() initializes the \fIinterface\fR along with passing \fIargc\fR and
\fIargv\fR from \fBmain\fR(), so wlc can rename the process it forks to cleanup
crashed parent process and do FD passing (non-logind).

.SH RETURN VALUE
Upon successful execution \fBwlc_init\fR() will return true.

.SH ERRORS
All errors encountered in \fBwlc_init\fR() are considered fatal and thus should
never really return false.

.SH NOTES
Avoid running unverified code before \fBwlc_init\fR() as wlc compositor may be run
with higher privileges on non logind systems where compositor binary needs
to be suid.

.SH ALSO SEE
\fBwlc_interface\fR(3), \fBwlc_output\fR(3)

gman() { italic | embold | mkref | mksec }

italic() { sed 's/`\([^`\]*\)`/\\fI\1\\fR/g'; }
embold() { sed 's/\b\([^ ]*\)()/\\fB\1\\fR()/g'; }
mkref() { sed 's/\b\([^ ]*\)(\([0-9]\))/\\fB\1\\fR(\2)/g'; }
mksec() { sed 's/^-- \(.*\)/.SH \1/'; }

 Comment by Cloudef
Thursday Oct 01, 2015 at 08:10 GMT

That's nice proof of concept.

Things to consider would be if you want this format to be more general. This would almost certainly require the use of an IR, which the prompts the question of why not just use a well supported markup like restructed text or asciidoc directly? These formats can both generate manuals fairly comfortably, all the tool here would need to do is parse the comment block and C definition below it.

This is fine too, as long as the output is high quality. The only downside might be that the comment blocks might become more markup heavy. I don't think most documentation derives too much from what you have done with wlc_init here. Though I can't consider other projects here.


Random password Generator using JS

Describe the project you want to add with tech stack
Here Random passwords are generated from if the user clicks on Generate password button , the user can even copy the generated password by clicking copy password button .
Tech stack : HTML,CSS,BOOTSTRAP,JAVA SCRIPT
Expected behavior

The user interface contains 2 buttons one is for generating a password and the other is to copy the generated password , when the user clicks on generate password then a password is generated and displayed to the user the user can then click on copy password button to copy the password to clipboard
Screenshots (optional)

Additional context (optional )

i would like to contribute for ths issue under gssoc'23...please assign this  task to me.

Please assign me this issue so that I can resolve it under GSSOC-23

I have raised the issue first
On Sat, 20 May 2023, 20:14 Aditya Pawar, @.***> wrote:

Please assign me this issue so that I can resolve it under GSSOC-23
—
Reply to this email directly, view it on GitHub
https://github.com/pranjay-poddar/Dev-Geeks/issues/1062#issuecomment-1555927421,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHV6UAVAPWYYLZW4JOTXHDKF3ANCNFSM6AAAAAAYIYHP7M
.
You are receiving this because you authored the thread.Message ID:
@.***>

!assign

i would like to contribute for this issue under gssoc'23...please assign this task to me.

I have raised this issue first
On Sat, May 20, 2023 at 8:46 PM KILL DOLLAR 987 @.***>
wrote:

i would like to contribute for this issue under gssoc'23...please assign
this task to me.
—
Reply to this email directly, view it on GitHub
https://github.com/pranjay-poddar/Dev-Geeks/issues/1062#issuecomment-1555933815,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATCQWHS7UAEBVQ6TXZFYSOLXHDN6DANCNFSM6AAAAAAYIYHP7M
.
You are receiving this because you authored the thread.Message ID:
@.***>

Project already present


fix indentation for extraContainers

Why is this pull request needed and what does it do?
#141 added support for sidecar containers, but the indentation is wrong. This fixes it so the template can render correctly.
Which issues (if any) are related?
Issue caused from #141 if using the extraContainers field.
Checklist:

[X] I have bumped the chart version according to versioning.
[X] I have updated the chart changelog with all the changes that come with this pull request according to changelog.
[X] Any new values are backwards compatible and/or have sensible default.
[X] I have signed off all my commits as required by DCO.

Changes are automatically published when merged to main. They are not published on branches.

Note on DCO
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Nice catch, thanks!


Cleanup my recent !!/watch commands.

Remove watches missing a ?. Remove duplicate watch created by SD taking the original version of the message, not the edited version (not sure why that happened).

!!/approve

Remove duplicate watch created by SD taking the original version of the message, not the edited version (not sure why that happened).

@makyen I think that happens because we grab the original source of the message to avoid accidentally watching <i> and stuff, but it probably doesn’t account for edits.

@j-f1 That might be it/contributing, but I don't think it is. When we changed to using the raw message content (relatively recently), IIRC, it was a simple change and the raw data already was available from CE, or at least that's what I recall being said.
After the change was made to use the raw message, I've, many times, edited SD command messages, most commonly changing !!/watch to !!/watch-force. Every time, SD recognized the edited version. I've also seen multiple other people make similar edits and have the edited version recognized by SD. (all based on the responses SD gives to the edit). So, I know SD gets the edited raw message correctly almost all the time (or at least in a the cases I've observed).
This was the first time I've experienced, or seen, SD using the original version of a message upon an edit. There's probably nothing for us to track down at the moment, given the rarity of this happening. It just made it clear that there's the possibility it happens. As a result, SD commands which we don't want the possibility of being repeated (e.g. already applied watchlist & blacklist additions) shouldn't be edited. That's an easy work-around, as long as we know it's needed/desirable.


Change "handcrafter" to "handcrafted" in README

Jut a little spelling issue

@Ewpratten Thanks for the correction! :)


todo: move replugged client-mod off of hard coded module id

module ids change a lot find a better way to find it in replugged

https://discord.com/channels/1000926524452647132/1000955966520557689/1143520126252089344

resolved


test and develop Excel API modules with Vue3 and Typescript

[ ] Sheet color change
[ ]  Sheet name change
[ ]  Add sheet (listen event from Excel)
[ ]  Remove sheet (listen event from Excel)
[ ]  Sheet filtering by name

deprecated due #144


Expo 51?

Expo 51 came out today. This library is currently untested for Expo 51. If anyone has already upgraded it would be appreciated if someone could let me know if it works/doesn't work.

I'm starting this now. We use expo-font now, I assume this can layer on top of that?

If you're using expo-font then there isn't much point in using this config plugin since expo-font handles bundling the fonts for you and everything.

I think we still need this library because expo-font does not allow setting fontFamily and fontWeight separately on Android.

Yea that's exactly something that fits the use case of this config plugin. It should work with Expo 51 based on some quick rudimentary testing I did but if not feel free to let me know here or open a new issue.


Initial structure of README with some content examples

README with the Contents and initial structure of sections.
Some sections entries migrated from Updated list of implementations as an examples. It is not a complete migration, just an illustration.
Closes #1

What development process is best suitable here?

should I resolve worked out comments by myself
or the comment's author will decide and reslove (or not) his comments when he'll check commited corrections

I added a formatting example in the "SHACL Validators" section

Jena SHACL  Apache-2.0 Java - Supports: SHACL Core, SHACL-SPARQL.
RDF4J SHACL Sail  BSD-3-Clause Java
TopBraid SHACL API  BSD-3-Clause Java - Based on Jena; supports: SHACL Core, SHACL-SPARQL, SHACL rules.
TopBraid SHACL API Extended  BSD-3-Clause Java - Fork of TopBraid SHACL API + added SHACL-JS based on GraalVM Polyglot.
SHACL for Ruby  BSD-3-Clause Ruby - A pure-Ruby library for working with the Shape Constraint Language to validate the shape of RDF graphs.

Or maybe this one is better?

Jena SHACL  - Supports: SHACL Core, SHACL-SPARQL. Apache-2.0 Java
RDF4J SHACL Sail  - BSD-3-Clause Java
TopBraid SHACL API  - Based on Jena; supports: SHACL Core, SHACL-SPARQL, SHACL rules. BSD-3-Clause Java
TopBraid SHACL API Extended  - Fork of TopBraid SHACL API + added SHACL-JS based on GraalVM Polyglot. BSD-3-Clause Java
SHACL for Ruby  - A pure-Ruby library for working with the Shape Constraint Language to validate the shape of RDF graphs. BSD-3-Clause Ruby

Unfortunately, all bages in general are out of line with the text 😞 I could not find any way to align it vertically.

Let's not obsess on details. We can improve gradually

But em-dashes don't pass the awesome-lint linter. So I propose we should go with ordinary dashes.

em-dashes are the correct punctuation where I've put them, where I replaced hyphens, which are not dashes at all.
Previously, there were double-hyphens at these locations which are the ancient typist's stand-in for an em-dash on typewriters which didn't have the extra strikers for en-dash (~1.5 hyphens wide) and em-dash (~2 hyphens wide). Clever software replaces such doubled-hyphens with em-dashes en-route to the viewer. (Some extra-clever software replaces double-hyphens with en-dash, and triple-hyphens with em-dash.) Less clever software requires that we humans do the job.
I'd like to see the error reported by the not-so-awesome linter, so I can raise an appropriate issue against it.

Unfortunately, all [badges] in general are out of line with the text

Well, that's not awesome!

@TallTed, I completely agree that em-dash is way better for the readability and overall.
But there are two problems (numbered below):
The linter error is:
> awesome-lint
✖ Linting
  README.md:1:1
  ✖  32:47  List item link and description must be separated with a dash  remark-lint:awesome-list-item

There is even a special check in linter's code List item link and description separated by invalid en-dash or em-dash, which is not throwing this type of error messages in an output stream for some unknown reason.

We should also take into consideration that we are planning to submit this list to the community-made aggregators from the issue

#6.

So, we could end up with attempts to improve all these aggregators.
What do you think, @VladimirAlexiev, colleagues? What we should do, the right thing or the easy one?

The best what could be done with the activity bage vertical alignment (as-before and as-improved)

Jena SHACL  - Supports SHACL Core, SHACL-SPARQL Apache-2.0 Java.
Jena SHACL  - Supports: SHACL Core, SHACL-SPARQL Apache-2.0 Java.

Is it good enough?

And a bigger list will look like this (the page will be wider)

Jena SHACL  - Supports SHACL Core, SHACL-SPARQL. Apache-2.0 Java.
RDF4J SHACL Sail  - BSD-3-Clause Java.
TopBraid SHACL API  - Based on Jena; supports SHACL Core, SHACL-SPARQL, SHACL rules BSD-3-Clause Java.
TopBraid SHACL API Extended  - Fork of TopBraid SHACL API + added SHACL-JS based on GraalVM Polyglot BSD-3-Clause Java.
SHACL for Ruby  - A pure-Ruby library for working with the Shape Constraint Language to validate the shape of RDF graphs BSD-3-Clause Ruby.

We have two open questions related to this PR:
1. List entry formatting
Is this last variant (single dashes, bages alignment, semicolons) acceptable or not as a starter? Should we dump bages or not?
2. The entry content question
Rised by @VladimirAlexiev: "We want the link to be most specific, into the SHACL documentation of the concrete product".
Should we make a link to the library's documentation a priority compared to a library's repository link? If so, I could replace repo-links with doc-links whenever it's possible.
Current variant (shaperone from "Declarative UIs" category)

Jena SHACL  - Supports SHACL Core, SHACL-SPARQL; Apache-2.0 Java.
RDF4J SHACL Sail  - BSD-3-Clause Java.
TopBraid SHACL API  - Supports SHACL Core, SHACL-SPARQL, SHACL rules; based on Jena; BSD-3-Clause Java.
rdf-validate-shacl  - Supports SHACL Core; pure JavaScript validator on top of the RDFJS stack; playground; MIT JavaScript.
shacl-engine  - Supports SHACL Core, SHACL-SPARQL; A fast engine for data provided as RDF/JS objects; MIT JavaScript.
shaperone  - SHACL Shapes Form generator; playground; MIT Typescript.

Doc-links variant (Jena, RDF4J, shaperone changed, others do not have any documentation)

Jena SHACL  - Supports SHACL Core, SHACL-SPARQL; Apache-2.0 Java.
RDF4J SHACL Sail  - BSD-3-Clause Java.
TopBraid SHACL API  - Supports SHACL Core, SHACL-SPARQL, SHACL rules; based on Jena; BSD-3-Clause Java.
rdf-validate-shacl  - Supports SHACL Core; pure JavaScript validator on top of the RDFJS stack; playground; MIT JavaScript.
shacl-engine  - Supports SHACL Core, SHACL-SPARQL; A fast engine for data provided as RDF/JS objects; MIT JavaScript.
shaperone  - SHACL Shapes Form generator; playground; MIT Typescript.

I have finalized the last version. It will be rendered like this:
https://github.com/w3c-cg/awesome-semantic-shapes/blob/89e8518336025ec1289fdb81141014aa672aedd4/README.md

@amivanoff thanks, you've done a great job!
I think the first link should be to source because the "last commit" shield suggests that, and people will expect it.
And we can add a link "docs" in the description.
I'm ready to merge, but since you've collected both links, could you make this last change?
Thanks!!

Some punctuation is needed between the license and the language. The single space separator is not sufficient.  Java.

I think the first link should be to the source because the "last commit" shield suggests that, and people will expect it.

Awesome Linter checks that all list entries have unique links. Complex software like Jena, implements SHACL and ShEx and appears twice in the SHACL Validators and ShEx Validators sections.
With doc-links approach it was OK. With repo-links we have a problem.
We could use links to the corresponding submodules, but they are not so informative for the reader:

https://github.com/apache/jena/tree/main/jena-shacl
https://github.com/apache/jena/tree/main/jena-shex

We could use the same "parent" link https://github.com/apache/jena in the SHACL Validators and the ShEx Validators sections but the linter returns an error.
Another option, we could use doc-links and clickable badges with URL links to the repositories.

@TallTed, I will add "license" and a semicolon to list entries.

Does the validation work with links like
:https://github.com/apache/jena/tree/main/jena-shacl ? If so, let's go for that.
The third markup above is too complex

Does the validation work with links like :https://github.com/apache/jena/tree/main/jena-shacl ? If so, let's go for that. The third markup above is too complex

Fixed here https://github.com/w3c-cg/awesome-semantic-shapes/blob/22b7da77fb2ec445cd0c0a26bf8465642435b96f/README.md

No separate documentation links in item's description.
List item main link is repository subcomponent link (not doc-link).
Badge  links removed for markdown clarity.
Switched back from markdown emojis to UTF-8 emojis (plain text emoji is not so visible in the editor).
Added "license;" to the license SPDX codes (not "tags-like" markup in the end of description but more of a "text-like").
Added Part 2 SHACL 2017 talk by TopQuadrant.

I fixed all the comments from above. Whenever possible, I used shield.io badges for versions and last activity dates because this eliminated the necessity for manual updates.
https://github.com/w3c-cg/awesome-semantic-shapes/blob/09dce6b09215c2ee9a44c075dbcaa0aebe4a3b5c/README.md

Great job @amivanoff ! I'll merge it but first want to pick up all links mentioned, eg by @bergos.
Then I'll submit a second PR with more tools and goodies.

@VladimirAlexiev, It's added already, under the "rdf-ext" bullet in the "SHACL Validators" section and under the bullet "SHACL-related specifications" in the "Specifications" section.


feat: update instructions for EEG

"We would like this screen to appear before they start the main task and before the screen notifying the experimenter to start the recording/what to name the file. Please change the instructions to say "you may continue to the main task." -- Grace

9933d6d684de6533cbd02613781aad5aba733ecc


Story creation: add gods selection

When creating a "New Story", add ability to select multiple gods from the desired mythology's gods (in the gods table) to include in the story.
This is a bit complicated since a story can contain many gods, so I think you might want a new table and a rails 'has_many' or 'has_many through:'.  Or an easy initial implementation would be to add a text column to the stories table with a comma separated list of the names of the gods to  include.
Also see the simple_form gem for a possible way to display the list easily: https://github.com/heartcombo/simple_form#associations

I partially implemented this in #31, but still more to do.


KONG_KIC added to the flat manifests and Kustomize, and verified in the chart

Is there an existing issue for this?

[X] I have searched the existing issues

Problem Statement
KONG_KIC=true is not in the Kong container environment variables in https://github.com/Kong/kubernetes-ingress-controller/blob/main/deploy/single/all-in-one-dbless.yaml and friends. We want it to be there.
Proposed Solution
Add it: https://github.com/Kong/kubernetes-ingress-controller/blob/6040356d826aed9fc6a64686b9d96c5b899c23b8/config/base/kong-ingress-dbless.yaml#L26-L50
Additional information
No response
Acceptance Criteria

[x] Generated all-in-one manifests include KONG_KIC=true in the Kong container environment variables.
[x] Helm chart always adds KONG_KIC when KIC is running (this is likely the case already - just pending verification to be sure)
[x] Kustomize manifests always add KONG_KIC

duplicate of #2074. Closing that one and copying the ACs from there over to this one.

For reference, in the chart:
https://github.com/Kong/charts/blob/cb1d9388dee0ab58ea501934b66db003e2c2768d/charts/kong/templates/_helpers.tpl#L646-L648


Fix/remove fallthrough

Please use PX4 Discuss or Slack to align on pull requests if necessary. You can then open draft pull requests to get early feedback.
Describe problem solved by the proposed pull request
While browsing source I saw mc_pos_control had a compiler flag with a TODO to modify to remove it. Was an easy enough change
Test data / coverage
Can't find unit tests that cover flight stack modules
Describe your preferred solution
Extract the switch fallthrough statements into function flows
Describe possible alternatives
Countless

Should probably be noted this is just a refactor, there is no external change to the module

whats the target c++ standard for the project? C++17 added a [[fallthrough]] attribute, that might be a better solution

whats the target c++ standard for the project? C++17 added a [[fallthrough]] attribute, that might be a better solution

Nevermind found my own answer, the root CMakeList sets c++11 to be required standard, therefore the attribute shouldn't be considered an option

@thomaswatters I really appreciate that you took the time to look into the TODO you found in the code. I'm assuming you are missing some context on why it is there. The code is not broken and the compiler flag could theoretically just be removed like I tested in https://github.com/PX4/Firmware/pull/13104 BUT it's there because a certain ccache version that is still shipped with Ubuntu 16.04 has a bug and when doing incremental builds based on the ccache cache (all happening in the background even when doing make clean every time) the compiler hangs at the explicit // FALLTHROUGH messages probably because they are considered comments and hence not cached. See:

https://github.com/PX4/Firmware/issues/12813
https://github.com/PX4/Firmware/pull/12820#issuecomment-527415694
https://github.com/PX4/Firmware/pull/12827#issuecomment-527958040

This ccache bug was fixed a long time ago but we are still supporting vanilla Ubuntu 16.04 because there are certain ROS computer vision applications only running on 16.04. The future way will like you already suggested be to switch to C++17 and use the [[fallthrough]]; statement for these cases. See also https://github.com/PX4/Firmware/pull/12825#issue-311844328, https://github.com/PX4/Firmware/pull/13104#issuecomment-538816225. Currently it's not working because of one board that we support and needs a certain compiler.

@thomaswatters I wrote another comment summarizing all the findings in the original issue: https://github.com/PX4/Firmware/issues/12813#issuecomment-539830184
Would you agree if we close this pr?

@thomaswatters I wrote another comment summarizing all the findings in the original issue: #12813 (comment)
Would you agree if we close this pr?

certainly


HTTP Digest Direct Authenticator

-implement RFC 2617 for digest authentication
Create DigestCredentials given Digest Authorization header
This has to be used similar as the Direct Basic Authenticator is used
Create new DigestAuthenticator intervace to validate DigestCredentials retrieved from the authenticator
The realm value is configurable:
DirectDigestAuthClient digestAuthClient = new DirectDigestAuthClient(new SecurityDigestAuthenticator());
digestAuthClient.setRealm("myRealm");
In order to validate that Digest authentication is successful is needed that:
digestCredentials.getResponse().equals(digestCredentials.calculateServerDigest(true, pwd))
where pwd is the user password kept in database.
According to RFC 2617 the user may keep HA1 encoded format
of the password in database: HA1=MD5(username-value + ":" + realm-value + ":" + passwd)
If the user keeps password in clear (not recommended) then the digest validation should be performed like this:
digestCredentials.getResponse().equals(digestCredentials.calculateServerDigest(false, pwd))
digestCredentials.getResponse() represents the client response digest
digestCredentials.calculcateServerDigest represents the server digest. These two must be equal for a successful digest authentication

Please have a look and merge with original pac4j project if you find it useful
I haven't write any tests, but I plan to write tests also and make new pull request. However I tested the new Direct Digest Authenticator with my web app that uses pac4j (play-pac4j) and works fine
Thanks!
Mircea Carasel

@mmoayyed I think we're good on this one. Is it ok for you?
I'd like to merge it before (https://github.com/pac4j/pac4j/pull/497) or it will be a nightmare for @mirceac . I'll make a few adjustements afterwards.

I'll do a final review later this evening. My main viewpoint in reviewing this would bes to ensure we can use this functionality easily in CAS via https://github.com/Jasig/cas/issues/1384

Yeah this looks fine. Still a couple of questions on whether we need that extra authenticator, but it looks good to me. We can always fix things later once we get to an impl.

I will merge, but remove the interface. We'll add it if we need it later on.
Many thanks @mirceac for your patience and tenacity on this!

Thank you so much for merging my changes!
Regarding to removing DigestAuthenticator interface. Let me know if you want me now to remove it and maybe using the existing TokenAuthenticator interface instead. I can give it a try today, just let me know

No problem. I'm currently refactoring your wok with my PR: https://github.com/pac4j/pac4j/pull/497
After its merge, you'll be able to see the changes I made and submit some tests for quality.

ok, great! Thanks again!

It's updated, you can sync with master and work on tests if you want.


Header Propagation Middleware missing from Build-in middleware list.

I thought this page ought to mention something about the Header Propagation Middleware which is somewhat documented here; https://docs.microsoft.com/en-us/aspnet/core/fundamentals/http-requests?view=aspnetcore-3.1#header-propagation-middleware.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9898482c-fa54-7ce2-1716-d14fbe03990d
Version Independent ID: 3926c686-0ccc-f9fe-ca52-0134612a1623
Content: ASP.NET Core Middleware
Content Source: aspnetcore/fundamentals/middleware/index.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @Rick-Anderson
Microsoft Alias: riande

Thanks @hannahchan ... I'll knock that out real quick.


Implement the framework of a genearlized-alpha solver based on TDD

Implements #22.
Framework of the fully nonlinear generalized-alpha solver was implemented in this work following the principles of test-driven development. To this end, a GeneralizedAlphaTimeIntegrator class was introduced to handle the time stepping, integration, and Newton-Raphson iterations.
The implementation is problem agnostic, meaning it is general enough to be used on any structural dynamics problem. We need to implement additional features for this to handle the problem of rigid pendulum consisting of quaternions as generalized coordinates.

Update: At this point, we have the nonlinear solver framework implemented with dummy implementations for iteration matrix and the residual function. I will shift focus on deriving the terms for the rigid pendulum problem.

We should merge this pull request sooner rather than later.  It is getting hard to see what the new changes are with each commit set.  We can then continue development using a new pull request.

We should merge this pull request sooner rather than later. It is getting hard to see what the new changes are with each commit set. We can then continue development using a new pull request.

I agree. This can be considered as a completed feature and we can move on to merge this upon review. Proposed enhancements (such as mapping and quaternion-based residual/iteration matrices) can be performed in separate pull request(s).

I agree. It's good that you are getting some code and tests fleshed out.
Perhaps David and I can ramp up more work on this... Perhaps we can help more with abstractions and restructuring for inserting test inputs vs "real" inputs, etc., while you move on with more formulation/algorithm work?

I would suggest going ahead and merging this one, and we can work in new pull requests.

I would suggest going ahead and merging this one, and we can work in new pull requests.

Could you review this one more time and approve if looks good? Apologies for having to make you do this multiple times.


How to be happy?

How?

https://www.reddit.com/r/AskReddit/comments/29vm0h/happy_people_of_reddit_what_are_you_tips_and/


add on vanished and cannot reinstall

The add on crashed and vanished now when i go to install it again it fails. For some reason it displays specto - ... Fork rather than specto - genesis fork, hangs on 3 percent for a while then fails.

Right now we have problem wit server performance. Try install add-on tomorow

Yeah same issue, the addons uninstalled its self and now its hanging on a 3% install. I guess I'll wait until tomorrow.

thank you

Try install  update manualy
plugin.video.specto.zip

Worked using manual update mrknow :) Could you please sort the TV section download so I can chose where it goes to. TIA

great work, now you should change all the icons and make it yours

Just checking on issues with server. Still not able to download through zip or super repo.

yeah tried to install the Filmkodi repo and trying to get into it , it says Can't connect to repo


Listeners loaded in different class loader are not called.

We have a plugin based system, Mbassador works very well till the event bus and listeners are loaded by same class loader, however when listeners are in different class loader, even if they are subscribed, they will not get called.
Here's our scenario.

Main application holds a singleton instance of event bus

Main application creates a new class loader for each plugin and loads the plugin.

Once the plugin is loaded, plugin manager gives newly loaded plugin, a chance to register its listeners and passes the event bus as parameter. Here plugin subscribes listeners.

When main application receives a message, it will publish it using event bus.

Listeners in plugins (different class loader) will not get called.

Tried @Listener(references=References.Strong) too.

Maybe there should be an option in bus configuration to provide a class loader which should be used for class resolution? Or an option for "unsafe" mode, when classes will be matched just by their canonical names?

Actually, you could return same instance for event classes using classloader. Its a lot more safer way, but there is only one thing: event classes should NOT have static fields - this is due to securitty issues. (But i didn't test it actually, does same Class share static fields or not).
You can simply do this by checking in plugin classloader if its event class then use reflection to return Class from classloader. Because plugin classloader was created in main application, it will use main classloader. And thus it will return same instance of Class, and they will even share code ... And static variables .... So be carefull with this, but, IMHO, this is one of simplest way to do it.
I know, this is pretty old topic, but its still open and i was intested in it. And i know, sharing static variable is pretty bad - but i think it should be okay for messages... They are messages, and they shouldnt have static variables in them. But again, this is fix only for other side. As for MBassodor fix - IMHO, you shouldn't fix this. They are different classes. They are not the same. You cann't check if same class bytecode is used.  It wont work with Oracle java, but can work for other implementations as it should throw exception because you cannot cast object if bytecode is diff., but this may cause security issues


Support for nodes that wish to offer above average storage

What is the problem
Nodes on the network with storage sizes that are significantly larger than the average are semi problematic.
Our FINDCONTENT mechanism is statistically less likely to query any individual node on the network the further away they tey are from the content-id.  A node that stores an above average amount of data will be effectively wasting that storage after a certain distance since very few queries will reach them
How can this be fixed.
Clients should probably approach this problem by operating multiple nodes on the network concurrently.  The exact specifics of how this would be implemented are up to individual client teams but here are some highlights.
Linkable Identities
If a client is operating multiple node-ids on the network, they should probably use this HD Identity scheme so that we can take accurate census data on the network.  Being able to cryptographicaly tie these multiple identities together gives us better visibility into the health of the network.
Dispersed Identities
When operating multiple node-ids on the network, a client should probably mine each node-id to avoid excessive overlap between the different node-ids.
Another approach might be to have a central identity that advertises a large radius and then to mine out additional node-ids that fall within the main zone of interest and advertise a radius that is appropriately small that it doesn't exceed the bounds of it's primary zone of interest.  This approach would ensure that a node could respond to OFFER and FINDCONTENT messages from any of the identities that it operates since all of the secondary identities would be effectively covered by it's primary identity.
Intelligent Dispatch
If a node is operating two node-ids A and B and they receive a FINDCONTENT request under A for content that is technically stored under B, we should explore whether the appropriate response would be to forward them to B or whether they should just serve the content from A even though the content might be outside of their radius.
This same concept applies to things like gossip as well.
Prototyping
This is likely to pose some non-trivial architecture changes in client design and will need to be prototyped by a client team to figure out some of the nuance.

@ScottyPoi and I did some whiteboarding on this yesterday.  Here's some notes.
Maximum Effective Radius

This probably deserves it's own write-up.

There is a measurable mean/median radius size on the network.  As a node's radius grows above this value, the likilihood that it will be targeted by a FINDCONTENT or OFFER decreases.  I don't know the specific curve that this probability function takes, but I believe it is something like an exponential drop off.  Thus, there is some distance that I'll define as the "maximum effective radius" where the increased radius is no longer really providing the network with any additional benefit because the node isn't likely to actually serve any of the content.
I believe that this should be a CLI configuration option --maxiumum-effective-radius in clients and it would be a value akin to the gas limit where the clients themselves ship with a default value.
Healthy Routing Tables
In an environment where some nodes operate multiple node-ids on the network, we want to avoid the situation where a node gets represented multiple times in another node's routing table, albeit under different node ids.
If we proceed with a multi-node-id architecture, client routing table implementations will need to be aware of this and implement logic to avoid this.  A routing table should probably only ever contain a single node-id from the set of nodes operated by a single client.
Laying out multiple node ids

These models will all ignore the subtle nuances of how the xor distance metric doesn't allow for exact overlapping or adjacent radius coverage of the keyspace.

My initial thoughts for how a client might distribute their identities was simplistic.

The black line represents the overall keyspace.
The circles are 5 different node-ids that combined are intended to cover a wide area of the keyspace.
Each circle would be roughly of radius=maximum_effective_radius

However, I think there is potentially a superior model.

In this model we have a master node-id, which is the middle and largest circle.  All of the other smaller circles are child node-ids and they are effectively ephemeral.  This master node-id publishes a radius which is true to it's effective overall storage that it offers the network.  All of the other child node-ids that the client uses are simply there to provide coverage of the keyspace, with each node-id publishing a radius that is derived from the master radius such that it's outermost edge aligns with the edge of the master node-ids keyspace coverage.
Under this model, the master node-id can be used in place of any of the child node-ids since it's radius should always have full overlap of any child node's radius.  The client should also have an easier time managing it's storage under this model since it only has to track a single radius value from it's master identity, and all child identity radius values are just a function of this master value.
We probably need this for state network.
For us to launch state network we need to provide a large amount of base storage for the network.  Something in the 100 TB range depending on how much redundancy we want.  In order to do this we can either:

Deploy a large number of nodes with small storage (Many CPU's , smaller disks)
Deploy a smaller number of nodes with large storage (Fewer CPUs, larger disks)

Disk space is cheaper than CPU time.  The pragmatic choice for us in this situation is going to be to go with fewer nodes, and larger storage.  That probably means nodes that offer 10/50/100GB of storage to the network.  This is fine when we are the ones operating these nodes.  The problem arises, as soon as we start onboarding users who want the promise of small easy to run nodes.  At this point, if we've naively taken the route of deploying a network full of huge nodes, I think we get a weird network distribution between these mega nodes we operate and tiny nodes that our users are operating.  Specifically, there will be huge disparities in the radius values in our network which isn't an optimal network topology.
So for us to get state truly launched and onboard users, I think that we need this ability to keep our network topology happy.


Add speech enhancement feature

It will be very useful if sherpa could enhance speech.
The goal is having open source alternative to Adobe enhance speech
It's possible to use models such as
https://huggingface.co/speechbrain/metricgan-plus-voicebank

Sorry, currently we don't have such a plan.


Fix Link

This will fix a broken link

Thank you for your contribution 👍

You're welcome. Thanks for merging 😉


Feature Request - Circle Transformation Border Percent

Would it be possible to create a bindable float for border of the circle image so that not the entire border is drawn:
Example
Would be very useful for showing a count down of something to users.

You can achieve something similar with SVG files already. You can also create your own custom transformation for this. I'll close this for now.


How to set DataChangeFilter in listener

Problem

(X) bug report => please search github for a similar issue or PR before submitting
( ) unexpected behavior => please visit the Wiki before

Current behavior

I get Square1 data from Prosys simulation server. but get changed data only!
Expected behavior

I want DataChangeFilter=StatusValueTimestamp. How can i set it?
Minimal reproduction of the problem with instructions

1.inject is  { "interval": 1000,   "queueSize": 1}
2. Prosys sim server log is:
ItemsToCreate=MonitoredItemCreateRequest[1]
[0]=MonitoredItemCreateRequest
ItemToMonitor=ReadValueId
NodeId=ns=5;s=Square1
AttributeId=13
IndexRange=null
DataEncoding=null
MonitoringMode=MonitoringMode
name=Reporting
ordinal=2
RequestedParameters=MonitoringParameters
ClientHandle=2
SamplingInterval=1000.0
Filter=null
QueueSize=1
DiscardOldest=true
3.
Your Environment
Please tell us about your environment:

(X) I am using just the Node-RED package and got node-opcua installed with it

( ) I have installed node-opcua global from source (using git clone)

(X) I have installed node-opcua as a global package (using npm i -g)

Device :

( ) macOS: v
( ) Linux: v
( ) Windows: v
(X) Raspbian: v
( ) Other:

Name:
Version:

Description of the connecting OPC UA system:

Name   : prosys opc ua simulation server
Version: v3.0.0-157
Vendor : prosys

node-red-contrib-iiot-opcua version: ``
<EMAIL_ADDRESS>

Node: (min. 8.x)
node = v8.12.0
node-red = V0.19.4

Hi,

was it working in the versions before? (you set bug report, not unexpected behaviour)
is it node-opcua v0.4.6 in the global install?
could you build some example to get it to work with node-opcua 0.4.6?

cya
Klaus

API docs

options.trigger       {DataChangeTrigger} {Status|StatusValue|StatusValueTimestamp}
options.deadbandType  {DeadbandType}      {None|Absolute|Percent}
options.deadbandValue {Double}

Hi, biancode:
I just study OPC UA with node-red.  be prepare for access some PLC device.
I use node-red-contrib-iiot-opcua  for first time now, so i need some help.
sorry set bug report, but i donot known how to set  "DataChangeTrigger ..." options in node-red.
next is my flow in node-red. maybe give me some advice?
thanks.
[
{
"id": "a6f7c370.9501a8",
"type": "tab",
"label": "opc listen",
"disabled": false,
"info": ""
},
{
"id": "b53de21a.c7a54",
"type": "OPCUA-IIoT-Listener",
"z": "a6f7c370.9501a8",
"connector": "70d1df5f.2610f",
"action": "subscribe",
"queueSize": "1",
"name": "",
"justValue": true,
"showStatusActivities": false,
"showErrors": false,
"x": 360,
"y": 120,
"wires": [
[
"e1aa9291.176f7",
"768cc25c.ecc684"
]
]
},
{
"id": "b94f91b8.790088",
"type": "OPCUA-IIoT-Inject",
"z": "a6f7c370.9501a8",
"injectType": "listen",
"payload": "{"interval":1000,"queueSize":1}",
"payloadType": "json",
"topic": "",
"repeat": "",
"crontab": "",
"once": true,
"startDelay": "",
"name": "listen Square1",
"addressSpaceItems": [
{
"name": "",
"nodeId": "ns=5;s=Square1",
"datatypeName": ""
}
],
"x": 160,
"y": 120,
"wires": [
[
"b53de21a.c7a54"
]
]
},
{
"id": "768cc25c.ecc684",
"type": "debug",
"z": "a6f7c370.9501a8",
"name": "",
"active": true,
"tosidebar": true,
"console": false,
"complete": "true",
"x": 850,
"y": 120,
"wires": []
},
{
"id": "e1aa9291.176f7",
"type": "OPCUA-IIoT-Response",
"z": "a6f7c370.9501a8",
"name": "",
"showStatusActivities": false,
"showErrors": true,
"x": 520,
"y": 180,
"wires": [
[
"29963671.fed68a"
]
]
},
{
"id": "29963671.fed68a",
"type": "function",
"z": "a6f7c370.9501a8",
"name": "",
"func": "var msg1 = {};\n\nmsg1.topic = msg.addressSpaceItems[0].nodeId;\nmsg1.payload = msg.payload.value.value;\nmsg1.timestamp = msg.payload.sourceTimestamp;\n\n//{topic:"name", payload:value, timestamp:1520527095000}\nreturn msg1;",
"outputs": 1,
"noerr": 0,
"x": 670,
"y": 180,
"wires": [
[
"768cc25c.ecc684"
]
]
},
{
"id": "70d1df5f.2610f",
"type": "OPCUA-IIoT-Connector",
"z": "",
"discoveryUrl": "",
"endpoint": "opc.tcp://<IP_ADDRESS>:53530/OPCUA/SimulationServer",
"keepSessionAlive": true,
"loginEnabled": true,
"securityPolicy": "None",
"securityMode": "NONE",
"name": "PROSYS SERVER",
"showErrors": true,
"publicCertificateFile": "",
"privateKeyFile": "",
"defaultSecureTokenLifetime": "60000",
"endpointMustExist": false,
"autoSelectRightEndpoint": false,
"strategyMaxRetry": "",
"strategyInitialDelay": "",
"strategyMaxDelay": "",
"strategyRandomisationFactor": "",
"requestedSessionTimeout": ""
}
]

it works as expected via listener parameters
{     "interval": 200,     "queueSize": 10,     "options": {         "requestedPublishingInterval": 1000,         "requestedLifetimeCount": 1000,         "requestedMaxKeepAliveCount": 12,         "maxNotificationsPerPublish": 100,         "publishingEnabled": true,         "priority": 6,         "trigger": "StatusValueTimestamp"     } }

That is to set from your first inject to the listener. It does not change with next option injects without a deploy before.


Infraspecific rank "f." not parsed correctly under certain conditions

Parsing the name
Cymbalaria muralis G.Gaertn, B.Mey. & Schreb. f. toutonii (A.Chev.) Cuf.
appear not to successfully identify "f." as a rank.
However, if "f." is replaced with "var.", the parsing is successful.
Cymbalaria muralis G.Gaertn, B.Mey. & Schreb. var. toutonii (A.Chev.) Cuf.
Examples using the rank form, but without authors, seems to work fine
Picea glauca var. albertiana f. conica
BTW: Great project !!!

It happens because f. in Cymbalaria muralis G.Gaertn, B.Mey. & Schreb. f. toutonii (A.Chev.) Cuf. might mean
forma or filius and there is no way to know which one it is
https://github.com/gnames/gnparser#names-with-filius-icn-code

I am closing this issue, as I do not have a good algorithm to go forward in distinguishing forma and filius in such cases. Gladly,  such occations are pretty rare, and gnparser issues a warning when it happens. So I guess the solution for now to filter results by that warning and adjust results manually.

Thanks for a swift response @dimus and a fair point. The code of nomenclature is certainly flawed in this case.  There might be a statistical argument of favouring forma over filius  in cases like this, but as you say, they are rare.

Hi @dimus, I was just wondering if the principle below might work to identify forma or filius ?
On the basis that all infraspecific names are lower case and not punctuated, we can say:
If an f. is preceded by a lowercase text and the text is not a recognized rank nor precided by a puncuation mark (Accidental lower case authorship), we can assume that the f. represents the forma rank and not filius.
As you say, these cases are rare.

Hi @dimus, I was just wondering if the principle below might work to identify forma or filius ?
On the basis that all infraspecific names are lower case and not punctuated, we can say:
If an f. is preceded by a lowercase text and the text is not a recognized rank nor precided by a puncuation mark (Accidental lower case authorship), we can assume that the f. represents the forma rank and not filius.
As you say, these cases are rare.

@havardo, as I understand we already have this, can you give an example?

Thanks for taking the time looking into this a bit further @dimus.
The examples below are all forma and adhere to the principlces described above.

The preciding text is lowercase and not punctuated (Hence, not author nor rank).

The parser is reporting them all as ambiguous
Sanguinaria canadensis L. f. multiplex (E.H.Wilson) Weath.
Rosa banksiae R.Br. f. lutescens Voss
Prunus cerasifera Ehrh. f. stipitata Bregadze
Cupressus obtusa (Siebold & Zucc.) F.Muell. f. formosana (Hayata) Clinton-Baker

For example, if we look at Sanguinaria canadensis L. f. multiplex (E.H.Wilson) Weath.
Without additional information, how can we conclude, that f. means Sanguinaria canadensis format multiplex and not L. filius?

The text multiplex is written in lowercase and has now punctuation. We can therfore conclude that the text is neither authorship nor a rank. Hence, the text must be an infraspecific name. We can then conclude that the preceding f. Is forma and not filius.
This approach will not work if an authorship is accidently written in lowercase, but then the name is noncompliant anyway.

We cannot be sure, for example  Ficus aspera Forster f.  nota Blanco has Forster f. as an author. However I think you are right that when such pattern happens, the probability that f. means forma is much higher than if f. means filius.
So it is better to parse f. as forma, with the same warning as before.

I created a new issue at https://github.com/gnames/gnparser/issues/154


[BUG] Home shows GeneralMuteSwitch while disabled in config

Describe the bug
My Home app displays the General Mute Switch accessory while I have this field disabled
To Reproduce
Restarted Homebridge, docker, rebooted Raspberry Pi. Still no luck.
Expected behavior
Home app not showing this accessory while field disabled in config.
IOS (please complete the following information):

Version 12.4.1
Device: iPhone 6s and iPad Air 1

Logs
There are no errors or weird things in my logs
Config
{
"platform": "HarmonyHubWebSocket",
"name": "OBFUSCATED",
"hubIP": "OBFUSCATED",
"mainActivity": "Television",
"showTurnOffActivity": "inverted",
"publishGeneralMuteSwitch": "false"
}

Hi, did you activate it before ?

Yes, I activated to see what it was but I don’t need it. Now I can’t get rid of it.

I quickly checked the code and it should be removed at next start . Will try to reproduce ASAP are you on latest version of the plugin.v
Sent with GitHawk

After reboot, Homebridge restart and Docker container restart I keep getting this in the log:
//
[9/11/2019, 9:34:10 PM] [CarloHarmonyHub] DidFinishLaunching
[9/11/2019, 9:34:10 PM] [CarloHarmonyHub] INFO - Loading activities...
----- Some other plugins -----
[9/11/2019, 9:34:12 PM] [CarloHarmonyHub] (CarloHarmonyHub)INFO - configuring Main TV Service
[9/11/2019, 9:34:12 PM] [CarloHarmonyHub] (CarloHarmonyHub)INFO - Configuring Main Activity Televisie
[9/11/2019, 9:34:12 PM] [CarloHarmonyHub] (CarloHarmonyHub)INFO - Discovered Activity : PowerOff
[9/11/2019, 9:34:12 PM] [CarloHarmonyHub] INFO - Loading geeneral mute Switch...
//
Would restarting the hub do anything?

"publishGeneralMuteSwitch": false
and not
"publishGeneralMuteSwitch": "false"
-> will try to handle this better but currently it is a boolean sorry . Or remove the option it should also work !


编译报错

[20:25:38.582] Running build in San Francisco, USA (West) – sfo1
[20:25:38.635] Cloning github.com/h7ml/amis-page (Branch: main, Commit: ad94130)
[20:25:38.756] Previous build cache not available
[20:25:39.724] Cloning completed: 1.089s
[20:25:39.850] Running "vercel build"
[20:25:40.290] Vercel CLI 28.17.0
[20:25:40.869] Installing dependencies...
[20:25:41.165] yarn install v1.22.17
[20:25:41.180] warning package.json: "dependencies" has dependency "@types/node" with range "^16.11.11" that collides with a dependency in "devDependencies" of the same name with version "^11.13.8"
[20:25:41.188] info No lockfile found.
[20:25:41.193] warning<EMAIL_ADDRESS>"dependencies" has dependency "@types/node" with range "^16.11.11" that collides with a dependency in "devDependencies" of the same name with version "^11.13.8"
[20:25:41.195] [1/4] Resolving packages...
[20:25:44.704] warning react-router ><EMAIL_ADDRESS>Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
[20:25:45.150] warning<EMAIL_ADDRESS>This is a stub types definition. history provides its own type definitions, so you do not need this installed.
[20:25:45.359] warning @types/react-router ><EMAIL_ADDRESS>This is a stub types definition. history provides its own type definitions, so you do not need this installed.
[20:25:45.648] warning @vue/compiler-sfc > magic-string ><EMAIL_ADDRESS>Please use @jridgewell/sourcemap-codec instead
[20:25:46.858] [2/4] Fetching packages...
[20:26:05.849] warning<EMAIL_ADDRESS>The engine "pnpm" appears to be invalid.
[20:26:05.858] [3/4] Linking dependencies...
[20:26:05.861] warning "@ant-design/pro-components ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.861] warning "@ant-design/pro-components ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.862] warning "@ant-design/pro-components > @ant-design/pro-utils ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.862] warning "@ant-design/pro-components > @ant-design/pro-utils ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
[20:26:05.862] warning "@ant-design/pro-components > @ant-design/pro-utils ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
[20:26:05.862] warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| 16.9.0-alpha.0".
[20:26:05.863] warning "amis ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.3.0 || ^15.5.4".
[20:26:05.863] warning "amis ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.3.0 || ^15.5.4".
[20:26:05.863] warning "amis ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0 || ^17.0.0".
[20:26:05.863] warning "amis ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0 || ^17.0.0".
[20:26:05.864] warning "amis > amis-ui ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^17.0.0".
[20:26:05.864] warning "amis > react-json-view ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^16.0.0 || ^17.0.0".
[20:26:05.865] warning "amis > mobx-react ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[20:26:05.866] warning " ><EMAIL_ADDRESS>has unmet peer dependency "amis-theme-editor@*".
[20:26:05.866] warning "amis-editor ><EMAIL_ADDRESS>has unmet peer dependency "amis-theme-editor-helper@*".
[20:26:05.868] warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[20:26:05.868] warning "react-router ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^15.0.0 || ^16.0.0 || ^17.0.0".
[20:26:05.869] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.870] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[20:26:05.870] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.870] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.870] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[20:26:05.870] warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[20:26:28.863] [4/4] Building fresh packages...
[20:26:29.472] success Saved lockfile.
[20:26:29.478] Done in 48.32s.
[20:26:29.932] vite v4.2.1 building for production...
[20:26:29.947] ✓ 0 modules transformed.
[20:26:29.947] ✓ built in 14ms
[20:26:29.948] Could not resolve entry module "src/editor/index.html".
[20:26:29.950] error during build:
[20:26:29.950] RollupError: Could not resolve entry module "src/editor/index.html".
[20:26:29.950]     at error (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:2125:30)
[20:26:29.950]     at ModuleLoader.loadEntryModule (file:///vercel/path0/node_modules/rollup/dist/es/shared/node-entry.js:23797:20)
[20:26:29.950]     at async Promise.all (index 1)
[20:26:29.967] Error: Command "vite build" exited with 1
[20:26:30.184] BUILD_UTILS_SPAWN_1: Command "vite build" exited with 1

用的 vite？

是的。

为什么 你这输出的 内容里 有这个？开着代理呢？
[20:25:38.582] Running build in San Francisco, USA (West) – sfo1

还是 在 codespace 里面用的？

试试手工设置下 pnpm 源吧


Unofficial blog posts should not be on the React blog

Hi folks!
I've noticed there are multiple blog posts that were not written by the React team:
https://zh-hans.reactjs.org/blog/2020/08/21/react-hooks-extra-level-of-indirection.html
https://zh-hans.reactjs.org/blog/2020/08/22/react-hooks-state-granularity.html
While I appreciate that someone wanted to share them, we should not post them on the official blog translation because the React team did not vet their content. It is very important for the React blog to be a resource people can trust, so it needs to match 1:1 to what is being published in English. Please take these posts down and move them to a personal blog. Thank you!

I think these unofficial posts & components should also be removed:

https://zh-hans.reactjs.org/blog/2020/05/22/react-hooks.html
External Logo & QR code at the bottom left of  the Home page

@gaearon DONE! It was my mistake.

Thank you for quick action!


IGAPP-813: Upgrade react native to 0.66.1

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.

Not sure why the build is failing though. Maybe flipper?

Did you install pods?

Not sure why the build is failing though. Maybe flipper?

Wrong/incompatible version of RCT-Folly. Updated it, now it works

Did you install pods?

Not sure what you mean?

You did not run pod install before afaics, that was what my comment meant


how to add header,client?.defaultCacheHeaders()?.toBuilder()?.addHeader("key","value") is don‘t work

Please add headers through okhttp interceptor. You pass in an instance ok okhttp.


add gflag to disable sampler thread

What problem does this PR solve?
Issue Number: #1891
Problem Summary: there is currently no gflag to control the switch of the sampler thread
What is changed and the side effects?
Changed: add --bvar_enable_sampling flag to control the switch of the sampler thread. if flag is false, does not create a global singleton SamplerCollector object.
Side effects:

Performance effects(性能影响):  setting the flag to false will reduce the creation of one thread and the usage of CPU and memory

Breaking backward compatibility(向后兼容性):  yes

Check List:

Please make sure your changes are compilable(请确保你的更改可以通过编译).
When providing us with a new feature, it is best to add related tests(如果你向我们增加一个新的功能, 请添加相关测试).
Please follow Contributor Covenant Code of Conduct.(请遵循贡献者准则).

LGTM

LGTM


UI 1264 - Notice

Fixes close button and correct position for NoticeBox

Commenting here for the record: @xGuTeK and I spent some time reversing some logic from this UIF. This PR missing some important pieces here and is currently in progress.
I'll convert this PR to draft to indicate as WIP.


Bug with Navigating to new State w/ Search Bar

Bug Report
To repro:

Open new incognito window
Navigate to any state or county location (not ROW)
Using the search bar, search for a different State than you're currently in
Click on that State in the search bar
Error occurs

Suspected reason:
In MapCountyGeneric.js, the Geographies component takes in config.geoUrl as the geographies prop. This prop is the correct URL for the json corresponding to the newly navigated State.
However, a console log reveals that the array passed to the geographies child of the Geographies component is the array for the old state that the user navigated from. Seems that the component is not re-rendering?
Fix Attempted by #132 (not yet working):
Manually fetch the geographies array from config.geoUrl, then pass this array into the Geographies component.
Console logs (checked in to this PR) reveal that this solution did indeed pass the correct array to the geographies child, but now, nothing is rendering.
Been struggling with this for a while and feel stuck. Any help would be appreciated!

this is indeed a bug. thanks for reporting. I will take a look at your PR after lunch.

Closed by 9a132d6


Incorrect modal example

On page: http://ionicframework.com/docs/v2/components/#modals

Incorrect import
Missing semi colon

Thanks


added images uploading alternative

Given the issues i saw both on open and closed issues users want a way to upload the images their own way. I wanna do that as well because i have some logic to run before submitting.
I have found a way to extend the package to enable users to access their images before uploading. They will then have to add a few lines of code to win it:
// on the component
<upload-image url="" name="" :custom_submit="true" @upload-images="uploadImages" :max_files="5"></upload-image>

//on the methods object
uploadImages(images){
  //where images is the images on the canvas
}

Closing this as my latest update adds a few more features; along with the suggested change in this PR. Thank you again for the interest & work.


meiotic re-replication terms from Jacky's e-mail

So the it would be
"pre meiotic DNA rereplication" term
cells undergo normal pre meiotic DNA replication followed by a further
round of DNA replication in the absence of nuclear division
Would this make sense (it follows the definition pattern for the mitotic
term):
Definition
A regulation phenotype observed in the meiosis I in which negative
regulation of the initiation of DNA-dependent DNA replication is
abnormal during pre meiotic DNA replication, resulting in one or more
complete or partial rounds of re-eplication of the  genome.
If not then I think what you have said is fine.
Jacky

Turns out I added two of these last month:
id: FYPO:0004758
name: abnormal negative regulation of premeiotic DNA replication initiation
id: FYPO:0004759
name: abnormal negative regulation of premeiotic DNA replication initiation resulting in complete rereplication
I've now added one more:
id: FYPO:0004855
name: abnormal negative regulation of premeiotic DNA replication initiation resulting in partial rereplication

edit file: 60400ab363d2deef2a6a0f3c814fc2c7142c5d6b
release: ad1a93ec3a6e446c7aa0632a50e74379931a8778


request help:  panic happen in my cluster

Issue description
apisix_ingress_controller run in my cluster,but there is a panic.

what should i do
Environment
2022-01-23T17:30:26+08:00	info	ingress/ingress.go:112	apisix ingress controller started
2022-01-23T17:30:26+08:00	info	ingress/ingress.go:114	version:
Version: 1.4.0
Git SHA: no-git-module
Go Version: go1.16.12
Building OS/Arch: linux/amd64
Running OS/Arch: linux/amd64
K8S Version: 1.18.10

How did you install it?
And can you run kubectl get ar -A?

Step for it and APISIX of  Version is  1.4.0
1、cd samples/deploy/
2、kubectl apply -f .yaml

The content in this directory only contains the APISIX Ingress controller itself, not the deployment of APISIX.
From the logs it looks like you have made changes to the https://github.com/apache/apisix-ingress-controller/blob/master/samples/deploy/configmap/apisix-ingress-cm.yaml file, but I don't Determine what exactly you modified.
This file is out of sync with the config file we are currently using https://github.com/apache/apisix-ingress-controller/blob/master/conf/config-default.yaml

And the image version of the APISIX Ingress controller in this directory is still 1.0 and needs to be updated.

Hi, Any update?

I unmount webhook-certs and it's fine. I do this because my Dev environment is fine on my MAC laptop。

I'm still on the road to discovery and I'm using ApisixUpstream only. But I found that my app was not registered with Apisix

I'm still on the road to discovery and I'm using ApisixUpstream only. But I found that my app was not registered with Apisix。 I found through debug that the svcLister had obtained service, but did not register Apisix directly。

my ApisixUpstream :
apiVersion: apisix.apache.org/v2bate3
kind: ApisixUpstream
metadata:
name: test-a
spec:
loadbalancer:
type: roundrobin

I'm still on the road to discovery and I'm using ApisixUpstream only

If you only using ApisixUpstream, it will not be sync to APISIX

https://github.com/apache/apisix-ingress-controller/issues/864

This issue has not been updated for too long, I think the above reply should have solved your problem.
I will close this issue, if your problem is solved, please feel free to reopen it, thanks.


Passing artifacts as manifest to resource template

Summary
What change needs making?
I need to pass input artifacts as manifest to resource template
Use Cases
I have a huge k8s manifest that is coming as an artifact from another step and because of size limitations, we can not take that manifest as a parameter, so artifact is an alternative.
When would you use this?
- name: spark-application
    inputs:
      parameters:
      - name: phase
      artifacts:
      - name: spark-manifest-yaml
        path: /tmp/spark-manifest.yaml
    resource:
      action: create
      manifest: "{{inputs.artifacts.spark-manifest-yaml}}"

currently, it throws error:  templates.spark-application.resource.manifest must be a valid yaml
Alternative: Instead of using a resource template, we can use a script template and do a kubectl create, but we don't get other benefits of resource template like successConditions or FailureCondifitos, etc.

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.

This was completed by #8657


Update tool_integration.md

Very cool! Added what I could think of. Btw, is the description field meant to describe the mzmine export or briefly the tool? Shall a brief description of the tool be included? (Maybe also a DOI?)

Thanks for the contribution, looks great! I think the description field is to describe file format (maybe @robinschmid can correct me on that). I don't think that the description of the tool itself is needed, users can refer to the tool's documentation (or linked publication) for that


Fixes auto-discovery by resolving the correct vendorDir in package scenarios.

[ ] Added or updated tests
[ ] Documented user facing changes
[ ] Updated CHANGELOG.md

related: https://github.com/nunomaduro/larastan/issues/1384
Changes
Don't rely on the ClassLoader location but instead the bootstrap.php location.

This even passes "Test Laravel from other working directories"!

which do you prefer? this or https://github.com/nunomaduro/larastan/issues/1384#issuecomment-1265373788 ?
either works for me, although i feel this one is the most simple.

I'm very happy that I must not answer that, as I'm just a janitor here 😌
I have a feeling that __DIR__ will break something in the far future.

@mad-briller my own answer (not! for Larastan) is: wait 2 months and see

yeah relying on filtering a list of custom autoloaders and hoping that the composer one is the first one we find that isn't in the phar: feels brittle aswell, whereas larastan controls the placement of the bootstrap.php file itself.
i suppose the one thing this doesn't handle is a custom vendor-dir configuration as we're assuming vendor is always in the root of the project.

hoping that the composer one is the first one we find

ClassLoader::getRegisteredLoaders could be our primary and __DIR__ our fallback.

i'll wait for @canvural's input before continuing on this

may be superceded by this:
https://github.com/nunomaduro/larastan/pull/1391

Closing because it is fixed in another way with #1392


Update dependency in pom.xml files: parent project to 2.12.2-SNAPSHOT

Fixed misspelled method name in Controllers in Example modules.

thanks, bud!

Thanks for taking the time to put the work into it!


adding millimeter conversion on javascript folder

Hi, I added a millimeter conversion on javascript folder.
Edited the HTML + JS File!

Hi @Chabivz,
Contributions for hacktoberfest will be counted from 1st october.


How to incorporate Java script methods in protractor jasmine tests

Do we need to use browser.executeScript?

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)

I'm not sure what you mean by incorporate JavaScript methods in protractor jasmine tests. If you want to execute client side JavaScript and evaluate that in your tests then yes, you will need to use browser.executeScript

Thanks @NickTomlin


Decrease size of computed function

Stripped out 14B.   The currentRunId is not really needed for tracking the stale state, since we already have previousArgs and args, which are sufficient.
I also covered staled behavior with test.

Nice! I will check it a few days later, when I will end my travels.

It was added in https://github.com/nanostores/nanostores/pull/229 by @btakita.
@btakita what is use case for currentRunId?

Sure, it would be nice if @btakita has time to validate my PR as well.
I can give my understanding of currentRunId. The problem here is that we can have multiple simultaneously running async tasks with different execution time. Let's say we have task1 (1 sec), task2 (3 sec) and task3 (2 sec) started one after another (the time in parentheses is how long it takes for the task to be resolved). In such case we will see first a result from task1 then the result from task3 and the task2 result will be the latest. But it looks very confusing from user's point of view. And  currentRunId could be used here as a unique id of the latest running task. So the code runId === currentRunId is nothing more than just checking if the current task is the latest one. You can try to remove let runId = ++currentRunId line and run the new test I added in this PR. It will fail.
With all that said above, we can look at my change. For each new task, we are running this line let args = stores.map($store => $store.get()) which creates a new args array (and a unique reference). Also, we already have previousArgs for simple memoization. From semantic point of view, we can rename previousArgs to latestArgs to make it more precise. And now we're ready to make an observation: we have a reference to previousArgs and we also have a reference to args which is unique for each task. We can use that reference as a task id.

LGTM. I recall that currentRunId was used to make the tests pass at some point. If the tests still pass after removing currentRunId. All should be ok.

I rebased it to next, but seems like we already removed currentRunId there. Can you check?

@ai not really. Epoch is something similar, but it's global. So we still need some flag for defining of stale state.
I've rebased everything. My test still will fail if you remove currentRunId or my changes.
BTW, do you always accept changes in next branch? In such case, I propose to add Contributing part into README to make more clear :smiley:

BTW, do you always accept changes in next branch? In such case, I propose to add Contributing part into README to make more clear

In most of cases we accept to main, but now we are preparing next branch.


feat: mt pelerin fiat ramp

Description
on top of https://github.com/shapeshift/lib/pull/986
adds Mt Pelerin fiat ramp under a new feature flag.
Notice

[x] Have you followed the guidelines in our Contributing guide?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Pull Request Type

[ ] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[x] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)
https://app.dework.xyz/shapeshift-dao/product-bounties?taskId=1157933e-3ca4-4e24-a326-17da71d87a6f
Risk
none
Testing
enable MtPelerinFiatRamp flag. there should be a new fiat ramp in the buy/sell modal.
Screenshots (if applicable)

converting to draft until lib package is merged.

@0xdef1cafe is REACT_APP_MTPELERIN_ASSETS_API env var set in fleek?

REACT_APP_MTPELERIN_ASSETS_API=https://api.mtpelerin.com/currencies/tokens
REACT_APP_MTPELERIN_BUY_URL=https://buy.mtpelerin.com/
REACT_APP_MTPELERIN_SELL_URL=https://sell.mtpelerin.com/


Upgrade Linux Kernel for flatcar-3815 from 6.1.85 to 6.1.86

Subject says it all.

See instead https://github.com/flatcar/scripts/pull/1933


Err

[ERR] [SteamAutoCrack.Core.Utils.EMUGameInfo] Failed to get game info, skipping generate supported languages...(AppID: 2361680)
[ERR] [SteamAutoCrack.Core.Utils.EMUGameInfo] Failed to get game info, skipping generate depots...(AppID: 2361680)
[ERR] [SteamAutoCrack.Core.Utils.EMUGameInfo] Failed to get game info, skipping generate DLCs...(AppID: 2361680)

Can you retry it?
Aso send me a scrrenshot.

Cannot unpack file is normal as file is not packed.
For AccessDenied error you need to use steam web api method.


Add rake spec and make it the default Rake task

A good practice when it comes to Ruby project is to enable the default workflow:

clone the code
run bundle to install dependencies
run rake to run tests

This PR makes the last step possible by adding a rake spec task and making it the default.

Ok, great, thank you!


the location of conversation is not located in exchange anymore its located elsewhere.

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: eb41d287-f954-dc84-782c-de8fa3c1ea0d
Version Independent ID: 0081aa8b-87dd-aef2-aaeb-61caa8f20351
Content: Teams workflow in Advanced eDiscovery - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/teams-workflow-in-advanced-ediscovery.md
Service: o365-seccomp
GitHub Login: @markjjo
Microsoft Alias: markjjo

https://support.microsoft.com/en-us/office/export-or-delete-your-teams-data-1ed6ac68-5fb4-41be-9861-1a4127fecf68
Users and request the export of conversations here.. Where is the data located ?

@Alfredox911 Thank you for your feedback. For channel conversations, messages are journaled to the group mailbox in Exchange Online, where they're available for eDiscovery.
Personal chats including group chats are stored in the mailboxes of the users. However, these are not accessible immediately and are in hidden folders. - https://docs.microsoft.com/en-us/microsoftteams/ediscovery-investigation
Hope this helps!
Thanks
Sri

@msbemba Thank you very much for the contribution and sharing this explanation. @Alfredox911 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


Pep8

This started off as mainly pep-8 fixes, especially for the 2 spaces indentations that messed up with my editor. I found out that the analysis example was not running and I fixed 2 additional issues:

get_standard_brain and get_standard_mask: paths were incorrect
get_frequency_map: images_df function argument was later referred to as combined_df (which was not defined)

Now the example runs (I think there is still a problem in the ICA part), and the analysis.py and analysis_example.py are more pep8 compliant.

Looks good. Thanks for the fixes, Yannick.


[Guide] Activating delegated harvesting (desktop wallet)

The guide should be short and direct, including screenshots if necessary. The wallet approach will be shown as the first alternative to announce a transaction (e.g: Method #1: Using the Wallet).

Guide to adapt: https://nemtech.github.io/guides/accountlink/activating-delegated-harvesting.html

Blocked, requires the module to be active.


Fix for messages coming from the message pool always ends up as non-confirmable

Hello!
While using this lib I discovered that observe requests sometimes wasn't retried properly (here). After a bit of digging I found out that messages coming from the message pool always are set to non-confirmable while new messages not coming from the pool are confirmable by default.
Since the blockwise code copies messages it can end up sending a non-confirmable message when the original message was actually set as confirmable.
I am not very familiar with this code base so I am not sure this fix is good, I have tested it with our server and it seems to solve the issue.
To me it feels wrong to assume what the type should be, so I guess it needs to be set every time a message is acquired? Regardless if it is reused or new? I haven't checked the reset of the code base to see if there are more places like this, just this file. In the meantime I use a message pool with 0 max size as a workaround since most messages should be conformable anyway, but that could cause other issues I suppose, I mean I assume that reset sets a message to non-confirmable for a reason.
Cheers and thanks for a good library!

(Seems OK to me, but I'll wait for Jozef to go over it. He's enjoying his holiday this week, so that'll have to wait for next week.)

Thanks @jkralik! Is on a vacation trip at the moment, will take this up again when I am back home.

@andersroos Pls could you resolve linter issue - https://github.com/plgd-dev/go-coap/actions/runs/3014872294 ? After that I will merge PR.

@andersroos Pls could you resolve linter issue - https://github.com/plgd-dev/go-coap/actions/runs/3014872294 ? After that I will merge PR.

Sure! Done.

Great. Thx for contributing !


drop support for versions before OTP-17 and bump to 3.0.0

@talentdeficit if you find some time to review.
This looks like a lot of changes, but it isn't. It simply removes the macros for maps_support, force_maps and no_binary_to_whatever.
This effectively drops support for OTP 16 and below.

@talentdeficit crap, I don't have permissions to set the default branch for the repo to be master instead of develop.
I've made this PR against an updated master (now the same as develop) but can you either give me more permissions or make the change to master as the default?

to make things easy let's merge this against master and i'll change the default branch once that's done


Fix website

This puts the images inside of the blog folder in the output so we can safely copy them over. And moves the images in /blog/img/ in the source control so it's easier to discover (instead of having to search many levels deep).
Should make the website work!

@facebook-github-bot shipit

Looks great!

Remove console.log and update image.

@facebook-github-bot shipit


[Feature Request] Support for dotnet-script csx files

OmniSharp already seems to work (in vscode anyway) with csharp script files that use dotnet-script. However, loading up a csx file in vim and manually setting filetype=cs results in "Could not find solution file or directory to start server" because csharp scripts don't have a solution file associated with them (using dotnet script init just creates a main.csx, omnisharp.json, and .vscode/launch.json file).
I can get things at least partially working by doing this in my .vimrc file:
autocmd BufNewFile,BufRead *.csx set filetype=cs
let g:OmniSharp_start_server = 0
let g:OmniSharp_port = 59000

Then manually starting up the omnisharp server and just pointing it to the same directory with the script file:
mono /path/to/OmniSharp.exe -p 59000 /path/to/directory/with/csx

With that in place, I get proper syntax highlighting and ALE errors and warnings in the script, and it even seems to support inline loading of nuget dependencies. Autocompletion does not seem to work (maybe something missing from the .vscode/launch.json file, I haven't spent much time investigating that).
I think it would be really nice if dotnet-script support was provided by omnisharp-vim out of the box. It would at the very least mean an alternate path for loading OmniSharp.exe without a solution file, and possibly other tweaks to get completions working again.

Hi @rudism,
I haven't played with dotnet scripting before but just tried dotnet script init and then opening vim with let g:OmniSharp_start_server = 0 as you describe, and setting ft=cs. I then started the server by just passing the current directory to the OmniSharpStartServer command, like this:
:OmniSharpStartServer %:p:h

This successfully started the server with a random port, after which I had ALE support, and in fact completions also worked fine.
Adding an ftdetect script to automatically set .csx files to use ft=cs is simple enough, I'm not sure if we should do more automatically? We could update the code which searches for a .sln file, to automatically just start the server in the current directory if no .sln is found and the current file is a .csx file... it feels a bit error-prone but it might be a safe enough way to go?

@rudism have a look at PR #464 - does that look good to you?

@nickspoons I checked out your branch and it works great (including completions, not sure why I was having issues with them before).


Merge pull request #17 from opencv/asid/v0.1.1

v0.1.1
Before submitting a pull request, please make sure the following is done:

You have merged in the latest changes from develop.
Resolved any conflicts that may have happened from that merge.
Ensure that you have run all tests and linting locally.

@alwan1989  :question:


Test and fix AsyncWorker

Remove MakeCallback() overloads that defaulted to undefined receiver, because node::MakeCallback() requires an object.
Use the async worker persistent object as the receiver of a worker callback
Persist async errors as strings, because an Error object cannot be created outside of a JS context
Remove overridable AsyncWorker::WorkComplete() because it wasn't useful and caused confusion. OnOK() and/or OnError() should be (optionally) overridden instead.
Add tests to validate basic success and error scenarios for AsyncWorker

@digitialinfinity please review, this is somewhat based on your feedback.

T* instance = Unwrap(callbackInfo.This());

While you're touching this file, can you also fix this to convert this to an object since that's what Unwrap expects?

Refers to: napi-inl.h:2001 in 9a0062a. [](commit_id = 9a0062a482e2acbc5547f3e4b89275a2226dc3a1, deletion_comment = False)

I was working on updating this PR, but after adding more tests I ran into a bug https://github.com/nodejs/node-api/issues/31. I'm going to fix that first, then come back to this.

I rebased on top of the error fix, and updated to address review feedback so far. So when reviewing here, please only look at the second commit.
I encountered an interesting problem: how to deal with unhandled JS exceptions during an async callback. See the TODO comment in AsyncWorker::OnWorkComplete(). Apparently this is something that Nan (or node::MakeCallback()) doesn't really address, but ideally this wrapper should do something better to provide consistent error-handling behavior. I think it will require a new function added to N-API. If others agree, I'll open a bug to track that.

Related to the TODO mentioned above, I'm working on a change in the C APIs that will call node::FatalException() (which is a public API, unlike node::FatalError) if a JavaScript exception escapes from a napi_async_complete_callback. Then AsyncWorker::OnWorkComplete() should just rethrow any Napi::Error as a JavaScript exception (just like other function callbacks already do via the NAPI_RETHROW_JS_ERROR macro).

Related node PR: https://github.com/nodejs/node/pull/12838


Add license information

This license declaration is required for passing legal approval.

looks good to me

looks good to me


Script for searching GitHub for Datalad repos

Closes #1.
Note: The script kept triggering GitHub's abuse detection while searching, so I had to add in a bunch of sleep calls.  Running the script thus ended up taking almost 18 minutes.

Awesome! Can we run it on cron GitHub action?

Eg daily

@yarikoptic Scheduled workflow added.

@yarikoptic Note: A GitHub token will need to be added to the repository as a secret named "SEARCH_GITHUB_TOKEN".  I don't believe the presupplied GITHUB_TOKEN has the necessary permissions to perform searches.

I will just merge and provide token and comments of any as issues later. Thank you @jwodder , awesome work

added the secret, let's see if works ;)


gitkraken stuck in an infinite loop on startup

When i startup my gitkraken, it is stuck in an infinite loop while it is opening the repository. I cannot do anything because the opening repo logo keeps popping up, and when the opening repo logo is gone, it comes back up a second later.
This occurs when i open any repository with gitkraken. (i use the latest version of gitkraken)

Does it work, e.g. if you view the repo with git log --all or perhaps gitk --all?
If so, I suggest to report this to gitkraken, because it is probably a bug on their site then.

Yes. Not sure it's a problem of git-tfs.
@GuylianWasHier Are you really sure to know what is git-tfs and that you post your issue in the good project?

To the best of my knowledge GitKraken does not use this project at all. It looks like this would be used for command line git or other GUI's that utilize the system's installed git (which GitKraken does not use)

Same for me. It keeps doing it not matter which repo im trying to open

This is also happening for me also. When will you guys have a fix for this.

@aboone2000 There will probably have a fix when you stop to post in the first forum you see and provide a reproduction case in their slack channel.
And perhaps if you ask them more kindly that what you just did....

@pmiossec whats the problem. is there a fix or not. I am using this globally in my company and personal.

whats the problem. is there a fix or not.

Perhaps you are a little long to understand...
I don't care!

Perhaps you should improve your skills to find the support place of a software and not necessarily dumbly post in the first result provided by Google...
But it seems you are not the only one with this lack of skill if it could console yourself.

For me this happen on Fedora 28. As much a I found is that this reboot problem happen only with git repos which use SSH. With HTTP repos everything works fine. As much as I could see it that the system crashes happen because of OpenSSL. IMHO it could be, because of a new version of OpenSSL.

Same on Fedora 27 ☠

Omg, do you people have basic reading skills? This GitHub repo is not related to GitKraken in any way.


FR: Command to set up github webhook

It would be great to be able to run something like bk setup github webhook --organisation ... --repository ... --pipeline ... and have a correctly-configured github webhook set up against the pipeline.
Since there's already a github and a buildkite auth token somewhere available after setting up bk this sounds quite achieveable.
Would you welcome a PR that adds this, if you don't yourselves do it?

👋 Thanks for this issue! The new version of the CLI doesn't require a GitHub token, and so we can't assume that one is present. We may look in to introducing the functionality in this issue at a later date, however our currently aim is to be agnostic in which VCS is in use.


Modularize it to be published on pypi

Modularized the code to be published as a package on PyPI

Changed the name to more descriptive and similar to what the code does.

Added github action to automatically deploy to both test.pypi.org and pypi.org

The package is deployed to test when it only pushed to the main branch and to pypi when it have a tag.

The package can be installed using pip install coderanker and used as follows:

from coderanker import *

leetcode = Leetcode("username")
data = leetcode.user_info()
print(data)

# or
leetcode = Leetcode()
data = leetcode.user_info("username") # to give more flexibility to the user

All the other classes can be used in the same way
Available classes are:
Leetcode()
Codeforces()
Kattis()

Note:

Make sure to add your email address in pyproject.toml file before publishing the package to pypi.org
Make sure to increment the version number in pyproject.toml file before publishing the package to pypi.org
Get Token from https://test.pypi.org/manage/account/token/ and https://pypi.org/manage/account/token/ for test and pypi respectively
Add TEST_PYPI_API_TOKEN and PYPI_API_TOKEN as secrets in github repo settings

you can add it by going to settings > Secrets and variables > Action > New repository secret

You can change the name of the package by changing the name in pyproject.toml file

Thank you
Chapi Menge

I will publish it on the PyPI. Thanks, chapi for your insight.