Doccords on layer one

This second request is more to gauge what people think about the style of the included documentation, before I go through the entire current docs, clean them up and apply them to hoon.hoon. The proposed style is a one line summary for the core overview, followed by any number of paragraphs of details.
In practice, this looks like this from the user's point of view:
> ? +2047
layer one: basic arithmetic, tree addressing and molds

Arms:
  ++ache : Either `a` or `b`, defaulting to `b`.
  ++add  : Unsigned addition.
  ++bloq : Blocksize
  ++cap  : Tree head.
  ++dec  : Unsigned decrement.
  ++div  : Unsigned division.
  ++dvr  : Unsigned division with remainder.
  ++each : Either `a` or `b`, defaulting to `a`.
  ++foo
  ++gate : Generic mold matching any gate.
  ++gte  : Unsigned greater-than/equal.
  ++gth  : Unsigned greater-than.
  ++list : Null terminated list.
  ++lone : One-tuple mold generator.
  ++lte  : Unsigned less-than/equal.
  ++lth  : Unsigned less-than.
  ++mas  : Axis within head/tail?
  ++max  : Unsigned maximum.
  ++min  : Unsigned minimum.
  ++mod  : Unsigned modulus.
  ++mold : A gate which normalizes data.
  ++mul  : Unsigned multiply.
  ++pair : Two-tuple mold generator.
  ++peg  : Axis within axis.
  ++pole : Faceless null terminated list.
  ++qual : Four-tuple mold generator.
  ++quid
  ++quip
  ++sub  : Unsigned subtraction.
  ++trap : Producer generator.
  ++tree : Tree mold generator.
  ++trel : Three-tuple mold generator.
  ++unit : Maybe mold generator.

<33.pdv 2.wxc $149>
> ? tree
Tree mold generator.

A `++tree` can be empty, or contain a node of a type and
left/right sub `++tree` of the same type. Pretty-printed with `{}`.

<1.yat {a/<1|van {* <33.pdv 2.wxc $149>}> <33.pdv 2.wxc $149>}>
>

Suggestions?

This looks great to me.
Will you be able to import the text from the docs in some reproducible way?  Such that, when we update the docs we can run something to update hoon.hoon?
The > ? tree is sample output in :dojo, right?  That formatting seems to work just fine.

This is great.  The only thing I'd change, stylistically, just to match
our overall style feel, is universal lowercasing.  Unless anyone wants to
bikeshed? :-)
On Wed, Feb 8, 2017 at 11:20 PM, Galen Wolfe-Pauly<EMAIL_ADDRESS>
wrote:

This looks great to me.
Will you be able to import the text from the docs in some reproducible
way? Such that, when we update the docs we can run something to update
hoon.hoon?
The > ? tree is sample output in :dojo, right? That formatting seems to
work just fine.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-278565899, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyAfv1B7CMDAkV_8KtdsUPcENlagjSks5rar43gaJpZM4L6Zv0
.

All lowercase would feel kind of forced here.  I'd prefer it to have normal capitalization.

  Uppercase in a Hoon file is generally kind
of jarring, since the code style doesn't use it.
The basic motivation for the style is that it's 2017 and people write
badly.  An all-lowercase style makes bad writing look better.
On Thu, Feb 9, 2017 at 9:28 AM, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

All lowercase would feel kind of forced here. I'd prefer it to have normal
capitalization.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-278712641, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyARs58doOmqIj_y8e63Ex0yLipPmUks5ra0zZgaJpZM4L6Zv0
.

Sure, but I guess I'm curious about the answer to my prior question.  Is the text here the same text that appears in the docs?

Updated everything to be lowercase. Fixed one spelling error and one style inconsistency.
This is mostly the text from the docs repo, minus some copy-editing, rewording, and documenting a few undocumented gates. This copy-editing was done by hand.
May I suggest that the hoon source be the canonical place for documentation? I encountered several gates which didn't have documentation in the docs repo. And why should they? That would require two patches to two different repositories. When the documentation is embedded in the code, either through docstrings or something like javadoc, there's a higher chance of actually having documentation written or updated; it's absence can be remarked on in code reviews.
(And the documentation here remains incomplete. I can't document ++quid or ++quip just from context, and I don't understand why the core has a ++foo arm.)

+1 for having fewer untracked dependencies between repos
On Thursday, 9 February 2017, Elliot Glaysher<EMAIL_ADDRESS>wrote:

Updated everything to be lowercase. Fixed one spelling error and one style
inconsistency.
This is mostly the text from the docs repo, minus some copy-editing,
rewording, and documenting a few undocumented gates. This copy-editing was
done by hand.
May I suggest that the hoon source be the canonical place for
documentation? I encountered several gates which didn't have documentation
in the docs repo. And why should they? That would require two patches to
two different repositories. When the documentation is embedded in the code,
either through docstrings or something like javadoc, there's a higher
chance of actually having documentation written or updated; it's absence
can be remarked on in code reviews.
(And the documentation here remains incomplete. I can't document ++quid
or ++quip just from context, and I don't understand why the core has a
++foo arm.)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-278865223, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhn6F1ZkEEDitbdycKakNHpufRaNSks5ra_3kgaJpZM4L6Zv0
.

I'd be completely fine having the docs generated from the source.  I agree that's the easier place to make edits.  The main thing I'd be concerned with is the tooling.  Like, can we run something that will update the docs?

I mean, the pipe dream version of this is ford parses hoon.hoon into html
On Friday, 10 February 2017, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

I'd be completely fine having the docs generated from the source. I agree
that's the easier place to make edits. The main thing I'd be concerned with
is the tooling. Like, can we run something that will update the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0
.

Yeah, I don't think we're quite there.

So you could just have e.g. libraries/3c.md contain "", plus some yaml if really necessary
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

I mean, the pipe dream version of this is ford parses hoon.hoon into html
On Friday, 10 February 2017, Galen Wolfe-Pauly<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

I'd be completely fine having the docs generated from the source. I agree
that's the easier place to make edits. The main thing I'd be concerned with
is the tooling. Like, can we run something that will update the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0
.

Oh I wasn't really thinking about it that way, that's interesting.

Hm actually if it's in the types you don't need to reparse it, you can just
pull the strings directly out programmatically; and if each core has a
++doc-name or sth, you can even use those to query from the markdown.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

So you could just have e.g. libraries/3c.md contain "", plus some yaml if really necessary
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','antechno777@gmail.com');>> wrote:

I mean, the pipe dream version of this is ford parses hoon.hoon into html
On Friday, 10 February 2017, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

I'd be completely fine having the docs generated from the source. I
agree that's the easier place to make edits. The main thing I'd be
concerned with is the tooling. Like, can we run something that will update
the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0
.

Yeah like the actual structure of the docs contains information that's not
in hoon.hoon / zuse, and possibly shouldn't be; that usually wouldn't be
affected by functionality edits though, which is the difficult thing to
manually keep in sync.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

Hm actually if it's in the types you don't need to reparse it, you can
just pull the strings directly out programmatically; and if each core has a
++doc-name or sth, you can even use those to query from the markdown.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','antechno777@gmail.com');>> wrote:

So you could just have e.g. libraries/3c.md contain "", plus some yaml if really necessary
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

I mean, the pipe dream version of this is ford parses hoon.hoon into html
On Friday, 10 February 2017, Galen Wolfe-Pauly<EMAIL_ADDRESS>wrote:

I'd be completely fine having the docs generated from the source. I
agree that's the easier place to make edits. The main thing I'd be
concerned with is the tooling. Like, can we run something that will update
the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0
.

Like similarly, the text of the eyre spec definitely belongs in eyre, but
the "1. Models. 2. Requests" organization can be a dozen lines in the docs
repo specifying which doccords exactly are getting pulled in, and in what
order.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

Yeah like the actual structure of the docs contains information that's not
in hoon.hoon / zuse, and possibly shouldn't be; that usually wouldn't be
affected by functionality edits though, which is the difficult thing to
manually keep in sync.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','antechno777@gmail.com');>> wrote:

Hm actually if it's in the types you don't need to reparse it, you can
just pull the strings directly out programmatically; and if each core has a
++doc-name or sth, you can even use those to query from the markdown.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

So you could just have e.g. libraries/3c.md contain "", plus some yaml if really necessary
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

I mean, the pipe dream version of this is ford parses hoon.hoon into
html
On Friday, 10 February 2017, Galen Wolfe-Pauly <
<EMAIL_ADDRESS>wrote:

I'd be completely fine having the docs generated from the source. I
agree that's the easier place to make edits. The main thing I'd be
concerned with is the tooling. Like, can we run something that will update
the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0
.

Elliot, any interest in weighing in on these "fat doccords" ideas?
Now that we have some doc in the source and it seems to work, is there a
logical way to extend or complete this idea?
On Fri, Feb 10, 2017 at 5:35 PM, Anton Dyudin<EMAIL_ADDRESS>wrote:

Like similarly, the text of the eyre spec definitely belongs in eyre, but
the "1. Models. 2. Requests" organization can be a dozen lines in the docs
repo specifying which doccords exactly are getting pulled in, and in what
order.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

Yeah like the actual structure of the docs contains information that's
not
in hoon.hoon / zuse, and possibly shouldn't be; that usually wouldn't be
affected by functionality edits though, which is the difficult thing to
manually keep in sync.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','antechno777@gmail.com');>> wrote:

Hm actually if it's in the types you don't need to reparse it, you can
just pull the strings directly out programmatically; and if each core
has a
++doc-name or sth, you can even use those to query from the markdown.
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

So you could just have e.g. libraries/3c.md contain "", plus some yaml if really
necessary
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

I mean, the pipe dream version of this is ford parses hoon.hoon into
html
On Friday, 10 February 2017, Galen Wolfe-Pauly <
<EMAIL_ADDRESS>wrote:

I'd be completely fine having the docs generated from the source. I
agree that's the easier place to make edits. The main thing I'd be
concerned with is the tooling. Like, can we run something that will
update
the docs?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279109126, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ABxXhlFw1MKueRdAPCcjwuy1ifgQCONQks5rbQ16gaJpZM4L6Zv0>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279110208, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AALyAU-l3IhZFyTZWXzVF2WuI0IR-772ks5rbRBugaJpZM4L6Zv0
.

It depends on how fat we're talking about.
Right now, in addition to the text I extracted, each entry in the docs repository has an Accepts, Produces, Source and Examples section. The source could be produced from the actual hoon source, the accepts/produces could be generated if the ++span information was expanded to record the string representation of the molds used. What's left is the Examples section, which could be rolled into the doccord. We could even do some magic to say something like quoted code lines ("> (add 5 5)") get parsed as a twig, with the example result autogenerated. (But that requires a (mini)Markdown parser in hoon.hoon.)
As for Anton's idea of putting the ordering information in a separate repository, I worry that that leads to the documentation not getting definitions for new gates.
(I tried experimenting with switching 1a, 1b, 1c into there own cores, but there was some sort of weird problem in vere and I gave up on that.)

I disagree that you'd need a markdown parser in hoon.hoon, you can keep the
docs as plain markdown and convert them in userspace as required.
I'm generally in favor of having both the example code and results
available, if possibly not using the same doccord mechanism; it'd be almost
like unit tests :D
On Friday, 10 February 2017, Elliot Glaysher<EMAIL_ADDRESS>wrote:

It depends on how fat we're talking about.
Right now, in addition to the text I extracted, each entry in the docs
repository has an Accepts, Produces, Source and Examples section. The
source could be produced from the actual hoon source, the accepts/produces
could be generated if the ++span information was expanded to record the
string representation of the molds used. What's left is the Examples
section, which could be rolled into the doccord. We could even do some
magic to say something like quoted code lines ("> (add 5 5)") get parsed
as a twig, with the example result autogenerated. (But that requires a
(mini)Markdown parser in hoon.hoon.)
As for Anton's idea of putting the ordering information in a separate
repository, I worry that that leads to the documentation not getting
definitions for new gates.
(I tried experimenting with switching 1a, 1b, 1c into there own cores, but
there was some sort of weird problem in vere and I gave up on that.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279113328, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhmlo_eKb68zNZLw9ZfTRK1Q9AVPKks5rbRlegaJpZM4L6Zv0
.

(But in particular, if a documented example e.g. stops compiling, it would
be nice to know what the expected result was without digging around for a
working revision) (and conversely to document gotchas via type-failing
examples, in a manner that is clearly intentional)
On Friday, 10 February 2017, Anton Dyudin<EMAIL_ADDRESS>wrote:

I disagree that you'd need a markdown parser in hoon.hoon, you can keep
the docs as plain markdown and convert them in userspace as required.
I'm generally in favor of having both the example code and results
available, if possibly not using the same doccord mechanism; it'd be almost
like unit tests :D
On Friday, 10 February 2017, Elliot Glaysher<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

It depends on how fat we're talking about.
Right now, in addition to the text I extracted, each entry in the docs
repository has an Accepts, Produces, Source and Examples section. The
source could be produced from the actual hoon source, the accepts/produces
could be generated if the ++span information was expanded to record the
string representation of the molds used. What's left is the Examples
section, which could be rolled into the doccord. We could even do some
magic to say something like quoted code lines ("> (add 5 5)") get parsed
as a twig, with the example result autogenerated. (But that requires a
(mini)Markdown parser in hoon.hoon.)
As for Anton's idea of putting the ordering information in a separate
repository, I worry that that leads to the documentation not getting
definitions for new gates.
(I tried experimenting with switching 1a, 1b, 1c into there own cores,
but there was some sort of weird problem in vere and I gave up on that.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/347#issuecomment-279113328, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhmlo_eKb68zNZLw9ZfTRK1Q9AVPKks5rbRlegaJpZM4L6Zv0
.

I added <pre urb:exec> tags a forever ago, which runs the code inside and says the result. This was definitely a mistake, but you can definitely only run the code in the examples when it's being rendered by the :tree.

Anton, you have a point about expected results. Perhaps a simple <include "++add"> is best after all.

Reminder to whoever merges this: you'll need https://github.com/urbit/arvo/pull/338 (and its jet patch in the urbit repository) merged first to parse the new doccord syntax used in this patch.

"Merging first and then fiddling later" is an extremely dangerous practice. Fortunately, it is not relevant here - there's nothing wrong with doccords as a complete feature, they are good to go.
Final result might end up rebased slightly depending on how the staging goes.

Yep, it's one of them fun time merges...
Sent from my iPhone

On Feb 13, 2017, at 7:02 PM, Elliot Glaysher<EMAIL_ADDRESS>wrote:
Reminder to whoever merges this: you'll need #338 (and its jet patch in the urbit repository) merged first to parse the new doccord syntax used in this patch.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

(Closing old pull request now that the final one has things separated into three patches.)


save parsing or conversion works of last time for next time’s usage

It happens frequently that we need to open a pdf file a second time to finish reading it, in order to make pdf.js load pdf fast when loading the same pdf file a second time, I suggest pdf.js to save those common tasks such as parsing or conversion of last time for next time’s usage.

Given the lack of details, closing as a duplicate of issue #5720.
For future reference: Please make sure than you provide the details requested in ISSUE_TEMPLATE.md, and that you read CONTRIBUTING.md before opening an issue.


Upgrade elasticsearch for logs on integration

We want to test out upgrading to 1.7.x as a precursor to trying this on
staging and eventually production.

Flagged as DNM because we need to disable puppet on the logs machines and roll this change out manually one by one to each server.

Good to merge whenever you want 👍

This should be a rolling upgrade: https://www.elastic.co/guide/en/elasticsearch/reference/1.7/setup-upgrade.html#rolling-upgrades

We've disabled puppet on the 3 machines, so we're ready to merge.


[regression](cluster key) move cluster key case to a new directory

move cluster key case from unique_with_mow_p0 directory to unique_with_mow_p0_c directory, because we will add more case like unique_with_mow_p0, now the directory is nested and confusing.

run buildall

run buildall

run buildall


Warn if AutoPrepare isn't on

The provider can detect with AutoPrepare was specified in the connection string or not, and warn (or even error) if not. This would push more people to do the right thing performance-wise.
Why not backport to 2.0 as well...

Looking at this again, I changed the milestone to 3.0 as this isn't a bugfix.


It seems your results are slightly different from Portfolio Visualizer's. Do you know the reason?

See title.

I'm just using the closing price of each day, not sure if it matters.
Computation is calculating the sample variance of logarithmic returns. I don't have a finance background so someone may correct me - the code is straightforward.

I checked your code, and if I remove the "math.log" the result is the same as Portfolio Visualizer's. Is there any good reason to use the logarithmic return?

I checked your code, and if I remove the "math.log" the result is the same as Portfolio Visualizer's. Is there any good reason to use the logarithmic return?

I mainly referred to https://en.wikipedia.org/wiki/Volatility_(finance), and it tells me to use logarithmic. There are indeed two ways to calculate volatility (https://wiki.mbalib.com/wiki/历史波动率), but seems using logarithmic is the mainstream from what I see. I will add an option to allow users to print results based on price percentage changes.

Yeah I did some research as well after the previous comment. It seems the log return is indeed a better choice. Portfolio Visualizer is too simple.


Information for students

I received some feedback that it can be useful to have information for students as well. Like the GitHub student developers pack and some online resources to get started with git.
This can be an extra expandable panel under:
🔑 I work at Utrecht University and want access!
🔑 I study at Utrecht University and want to use GitHub!

What do you think @jelletreep and @kequach? @kequach would you like to implement?

I think it's good. Doesn't hurt to have more information. I'll look into this when I have time.

It would be great to add such a section. However, a link to the page where students can apply for the student developer pack might be tricky, as one needs to upload a proof. I guess privacy officers will not agree with that unless it becomes very clear how this information is processed.
We should however be able to provide students with student developer packs through our enrollment in the campus program, but not sure how that would work (see benefits).
I will seek contact with the github schools team.

Ah ok, so we can grant them access with their UU email address. Let's try to make that work.
@kequach I think everything else can nevertheless be added. Feel free to submit a PR.

I haven't really looked into what I would add under that dropdown but I don't think there's much else besides what @jelletreep mentioned with the campus program. I'm not even sure if you can be part of the UU organization here as a student since I only went through the process after I was already an employee.
I'd wait for the response from the Github schools team and only add that information. Students also love free stuff so it's very good information to provide.

@kequach @J535D165, after a long wait we have received instructions from github on how to generate activation links for student developer packs (and provided dozens of students already with the pack). We are in the process of creating a self service portal for students to apply for the link in Topdesk, I expect this to be ready in February. For now I would suggest to add the following text:
🔑 I study at Utrecht University and want to use GitHub!

To apply for your Student Developer pack, send an email to<EMAIL_ADDRESS>

Do you have no experience with Git and GitHub? There are lots of resources on the internet to learn working with Git and GitHub. Check our best practices repository as a starting point.

Students are not eligible to become member of github.com/UtrechtUniversity, but can be invited as 'outside collaborators' to repositories to be able to contribute.


How to display the percentage of the loading schedule?

Make your own UIView subclass that shows progress and then showToast.


kube-batchd can not aware of the changes of gpu resources when scale up cluster.

fix the issue: kube-batchd can not aware of the changes of gpu resources when scale up cluster.

LGTM, run ./hack/update-gofmt.sh to make CI happy :)


No way to delete or rename file in database project

Deleting's definitely a P1 for Insider build, renaming maybe P2


Implement SKIP LOCKED

Since POSTGRESQL 9.5, there is an SKIP LOCKED option for SELECT FOR SHARE/FOR UPDATE that is extremely helpful.
It would be useful to support this.
Thanks

Would be really useful

I'll take this one. I have already implemented the functionality for PostgreSQL with some unit + integration tests, but I'll also try to get MySQL/MariaDB support in the PR as well for completeness.


could not find docker : stat docker

Hi @AlexR2D2 ,
Thanks for your work on duckdb plugin for metabase. I wanted to test on my computer but unfortunately I have this error at the right end of the process :
Resolving objects.githubusercontent.com (objects.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to objects.githubusercontent.com (objects.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 56866473 (54M) [application/octet-stream]
Saving to: ‘target/duckdb.metabase-driver.jar.1’

duckdb.metabase-driver.jar.1                               100%[======================================================================================================================================>]  54.23M  3.28MB/s    in 17s

2023-05-01 17:58:48 (3.21 MB/s) - ‘target/duckdb.metabase-driver.jar.1’ saved [56866473/56866473]

[+] Building 0.0s (0/0)
ERROR: could not find docker: stat docker: no such file or directory

Hi! I Updated the instructions in the README.md


How to solve this “DNS response for ipv6.google.com - Error 28: ResponseTimeout”

How to solve response timeout problem?. When I ping the Google public DNS IP address, it's not ping the address. After I give "ipaddr" in cli command it is showing this:
ping 64:ff9b::0808:0808
Done ipaddr
fd11:1111:1122:0:0:ff:fe00:3800
fd11:22:0:0:e683:e5ea:2d2d:648d
fd11:1111:1122:0:3a09:4230:1332:7150
fe80:0:0:0:44d7:6f79:a09d:531d
Done dns resolve ipv6.google.com
DNS response for ipv6.google.com - Error 28: ResponseTimeout

So I need to resolve the native IPv6 address of the given host name.
Thanks & Regards
Senthil-nag

Which dns server are you using.
You can use dns config command to show dns configurations.

@senthil-nag , to ping a NAT64 address, make sure you have a default route configured. On OTBR, you can do this with the following command:
prefix add fd11:22::/64 paros
netdata register

I just tested this and was able to perform the following:
> ping 64:ff9b::0808:0808
16 bytes from 64:ff9b:0:0:0:0:808:808: icmp_seq=1 hlim=113 time=33ms

To resolve ipv6.google.com, the default resolver address is 2001:4860:4860:0:0:0:0:8888, however this assume that OTBR has public IPv6 internet connectivity. If OTBR does not have global IPv6 internet connectivity, then you can leverage DNS64 on OTBR. However, you need to set the DNS resolver address to one of OTBR's IPv6 addresses. You can do this by appending the address to the command:
> dns resolve ipv6.google.com fdc4:b9d4:b56e:6083:0:ff:fe00:ec00
DNS response for ipv6.google.com. - 2607:f8b0:4005:807:0:0:0:200e TTL:299
Done

Where fdc4:b9d4:b56e:6083:0:ff:fe00:ec00 was the IPv6 address of my OTBR.
More documentation on the CLI commands here:

dns
prefix
netdata

Hi
Thanks for our response.
Sorry, I am new for open thread border router, How to setup 'dns config' in cli command.
Could you please tell me that thing?

Which dns server are you using.
dns resolver.

You can use dns config command to show dns configurations.
It's giving command is not found "dns config".

Regards
Senthil-nag

@senthil-nag , I see that you are using wpantund and not the latest main branch of openthread/ot-br-posix. Do you need to use wpantund?
If you haven't already, I suggest following the Thread Border Router Codelab.

Hi
Sorry for the late reply. I am using  nRF Nordic semiconductor software, So I have to use wpantund for NCP device.
And I get the NCP file in "nRF5 SDK for Thread and Zigbee v4.0.0"
https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.thread_zigbee.v1.0.0/thread_border_router.html?cp=8_7_5_1_0_8

@senthil-nag , note that nRF5 SDK for Thread and Zigbee v4.0.0 is relatively old. If possible, you should be looking at using nRF Connect SDK.
When using the Nordic SDKs for Thread devices, you can still leverage the latest OpenThread Border Router. For setting up an OpenThread Border Router, I would recommend following one of the following:

OpenThread Border Router Build and Configuration

Thread Border Router - Bidirectional IPv6 Connectivity and DNS-Based Service Discovery

Closing stale issue.


Support TCA 1.6.0

Support TCA 1.6.0, Please

Thanks @HannibalRoyal - in what way does the library not already support TCA 1.6.0? It seems to work fine as far as I've tested.


Update APKBUILD to enable support of kafka plugin.

add makedepends pkg "bsd-compat-headers", which contains the missing headerfile sys/queue.h, required to build rsyslog-(i|o)mkafka.
verified on Alpine 3.7 andyshinn/alpine-abuild.

ERROR: rsyslog: rsyslog-8.33_pre201804271036.tar.gz is missing in checksums

it looks like you have an old or inconsistent state? In the PR I see that 8.34 is used in both places. Can you elaborate?

args, sry ... somehow I did not see CI in the first place. Will have a a look, something with CI looks wrong...


fix(grammatical): Spelling mistakes

Argilla Community Growers
Thanks for your contribution! As part of our Community Growers initiative 🌱, we're donating Justdiggit bunds in your name to reforest sub-Saharan Africa. To claim your Community Growers certificate, please contact David Berenstein in our Slack community or fill in this form https://tally.so/r/n9XrxK once your PR has been merged.
Pull Request Templates
Please go the the Preview tab and select the appropriate sub-template:

🐞-bug
📚-documentation
🆕-features

Generic Pull Request Template
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Closes #<issue_number>
Type of change
This pull request addresses and corrects several grammatical errors found throughout the codebase.
The changes include fixing typos, punctuation, and ensuring proper sentence structure for improved readability and clarity.

[ ] Improvement (change adding some improvement to an existing functionality)
[ ] Documentation update

How Has This Been Tested
(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

[ ] Test A
[ ] Test B

Checklist

[ ] I added relevant documentation
[ ] follows the style guidelines of this project
[ ] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[ ] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

Hi @AbhineshJha, this is looking great. Thanks for the help 👍 If you ever feel like making another contribution, feel free to look at the #contributor channel in Slack.

@AbhineshJha Thanks again for this PR! Just to double-check, did you fill out our contributor form? https://tally.so/r/n9XrxK


Quizzes translated to Spanish

Added my translations to the quiz-app by adding following ES file: https://github.com/microsoft/Web-Dev-For-Beginners/tree/main/quiz-app/src/assets/translations/es.json
Added my Spanish (ES) language code to the dropdown in the quiz-app's App.vue file
Edited the quiz-app's translations index.js file to add my language

thank you!!! gracias!!!


⚠ Bofrost.de has degraded performance

In 623ab2c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 768 ms

Resolved: Bofrost.de performance has improved in e136eef after 15 minutes.


feat: Add generate binary crate

@Abdulbois please add readme for the tool and reference it from the root README.md

merged in scope of #24


Cannot view or create documents for CosmosDB

Storage Explorer Version: 1.12.0
Build Number: 20200116.10
Platform/OS: macOS Catalina 10.15.3
Architecture: don't know
Regression From:  1.11
Bug Description
Existing documents aren't shown.
When creating a new document, this pop-up appears
The collection cannot be accessed with this SDK version as it was created with newer SDK version..
Please use a different id for the document.

Steps to Reproduce

Expected Experience
With the previous version of Explorer I was able to browse CosmosDB documents
Actual Experience
Cannot use Explorer to browse CosmosDB documents
Additional Context
I can see the do documents in the Portal, so I don't think I'm going mad.

I don't believe anything has changed in CosmosDB support in Storage Explorer between 1.11 and 1.12.  @southpolesteve , can you take a look at this?  Thanks.

Azure Storage Explorer support for Azure Cosmos DB has been discontinued as of v1.24.0. We recommend users to use Azure Cosmos DB’s Data Explorer, which can be found in Azure Portal or as a stand-alone version in http://cosmos.azure.com/ for the best Azure Cosmos DB experience. You can also find additional Azure Cosmos DB tooling here: Azure Cosmos DB Tools


server version numbers reported wrong with 32-bit compiled 4.7.6

the code below produces weird shifted results with 4.7.6 compared to 4.7.3 on a 32-bit compile:
< ocilib 4.7.6 0 9 20 920
---
> ocilib 4.7.3 9 2 0 920

fprintf(stderr, "ocilib %d.%d.%d %i %i %i %i\n",
    OCILIB_MAJOR_VERSION, OCILIB_MINOR_VERSION, OCILIB_REVISION_VERSION,
    OCI_GetServerMajorVersion(cn),
    OCI_GetServerMinorVersion(cn),
    OCI_GetServerRevisionVersion(cn),
    OCI_GetVersionConnection(cn));

Hi,
Found the issue in ocilib code.
In your example, with current versions of OCILIB, OCI_GetVersionConnection() should return 90200 instead of 920 for a Oracle 9.2.0 server version.
In v4.7.5, I changed the version integer values returned by OCI_GetVersionConnection() to be on 6 digits instead of 4 to handle the minor and rev number on more than 1 digits.
When using oracle 18+, ver_maj, ver_min and ver_rev are retrieved from oracle OCI APIs  and then assembled into a single integer value on 6 digits and  OCI_GetVersionConnection() returns a correct integer value.
By for previous Oracle version, the version is computed by parsing the server banner (same as the one shown in SQL*PLUS).
And the extracted ver_maj, ver_min and ver_rev are not assembled using the new 6 digit scheme introduced in v4.7.5 but with the old scheme on 4 digits.
As OCI_GetServerMajorVersion, OCI_GetServerMinorVersion and OCI_GetServerRevisionVersion are extracting their value from the combined 6 digits integer value, in case the server is pre 18, they are parsing a 4 digits integer value and then lead to the erroneous value you've seen.
It will be fixed in the current 4.7.7 dev branch by the end of the day :)
Regards,
Vincent


Rendering issue again

this issue happen, again, the youtube it glitch text, anybody did try to other sites and have issue too?

even new tab have issues too

don't wait, looks like it is not solvable here.

If you are not happy then leave this repo, nobody force you to write there
but don't come looking in 2/3 years when 109 will not work any more for some websites.

this issue happen, again, the youtube it glitch text, anybody did try to other sites and have issue too?    even new tab have issues too

Is this with ANGLE in d3d9 mode (as indicated in chrome://gpu)?

With this argue much better --use-angle=d3d9
Confirm.

I dont know how but after installing new copy of windows with latest updates looks like no issue happens, ocassionally i said that supermium 119 trash but looks like i was wrong, one week no problems with yandex and aliexpress that was broken by black squares. Dev sorry and thanks.

try --use-angle=gl last solution helped me. Thanks to win32ss.


[performance | bug] acquireTokenSilent is always talking to azure

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[x] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Other... Please describe:

Browser:

[x] Chrome version: Version 75.0.3770.90 (Official Build) (64-bit)
[ ] Firefox version XX
[ ] IE version XX
[ ] Edge version XX
[ ] Safari version XX

Library version

Library version: 1.0.0 and 1.0.1

Current behavior

it seems acquireTokenSilent is always trying to get the accessToken from azure, instead of local cache. I can see acquireTokenSilent sends request to https://login.microsoftonline.com/te/... everytime my code calls it.
I can get a solid repro using this azure sample:
https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp
Expected behavior

acquireTokenSilent gets token from azure for first time, and subsequently it gets token from browser cache
Minimal reproduction of the problem with instructions

clone code from offcial sample: https://github.com/Azure-Samples/active-directory-b2c-javascript-msal-singlepageapp
make necessary changes (clientId, authority, etc...)
start web app
click login
click call web api
click call web api
click call web api

@pkanher617  is this related to authority and the cache?

@rick-hayek I will take a look at this today. Thank you for the detailed repro.

I'm seeing this behavior in my application as well.

We also faced this issues. Currently, we developed our own Promise-wrapper that cache promise from acquireTokenSilent.
At the start of out app, we send 4 calls to MS Graph, each calls acquireTokenSilent and app initiate 4 auth processes (almost simultaneously). Some of them fail and leave garbage in local storage (key-values from not-finished authentications). All further calls reload iframe to acquire new token as mentioned in this issues.

I think it's also worth noting that this issue further exacerbates the issue reported in #317.  Every time a token request is made instead of using the one in cache, it also triggers an additional unnecessary request for the OpenID configuration.

more and more users complains about this, especially when MSAL have to request and update two tokens (for Graph and SharePoint Online) in the same time.
https://antongorbikov.wordpress.com/2019/07/01/migrating-from-adal-to-msal/

This is definitely something we are focused on fixing @jasonnutter is helping drive the investigation

I'm no longer seeing this issue after upgrading to v1.1.2.  Anyone else?

Updating to v1.1.2 seems to have corrected the issue for me too.

I'm no longer seeing this issue after upgrading to v1.1.2. Anyone else?

Same here, no issues using 1.1.2

Looks like @pkanher617 's fix for scopes helped improve this. @pkanher617 If you confirm the same, we can tag this issue closed with #875.


Training Error assert (boxes1[:, 2:] >= boxes1[:, :2]).all()

Instructions To Reproduce the 🐛 Bug:

what changes you made (git diff) or what code you wrote

Nothing change

what exact command you run: python -m torch.distributed.launch --nproc_per_node=8 --use_env main.py --coco_path ../data/COCO2017 --output_dir output/conddetr_r50_epoch50
what you observed (including full logs):

| distributed init (rank 2): env://
| distributed init (rank 0): env://
| distributed init (rank 4): env://
| distributed init (rank 3): env://
| distributed init (rank 5): env://
| distributed init (rank 1): env://
| distributed init (rank 7): env://
| distributed init (rank 6): env://
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
git:
  sha: N/A, status: clean, branch: N/A

fatal: Not a git repository (or any parent up to mount point /research/d4)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Namespace(aux_loss=True, backbone='resnet50', batch_size=2, bbox_loss_coef=5, clip_max_norm=0.1, cls_loss_coef=2, coco_panoptic_path=None, coco_path='../data/COCO2017', dataset_file='coco', dec_layers=6, device='cuda', dice_loss_coef=1, dilation=False, dim_feedforward=2048, dist_backend='nccl', dist_url='env://', distributed=True, dropout=0.1, enc_layers=6, epochs=50, eval=False, focal_alpha=0.25, frozen_weights=None, giou_loss_coef=2, gpu=0, hidden_dim=256, lr=0.0001, lr_backbone=1e-05, lr_drop=40, mask_loss_coef=1, masks=False, nheads=8, num_queries=300, num_workers=2, output_dir='output/conddetr_r50_epoch50', position_embedding='sine', pre_norm=False, rank=0, remove_difficult=False, resume='', seed=42, set_cost_bbox=5, set_cost_class=2, set_cost_giou=2, start_epoch=0, weight_decay=0.0001, world_size=8)
number of params: 43196001
loading annotations into memory...
Done (t=20.78s)
creating index...
index created!
loading annotations into memory...
Done (t=0.56s)
creating index...
index created!
Start training
Epoch: [0]  [   0/7393]  eta: 7:05:21  lr: 0.000100  class_error: 85.57  loss: 45.1821 (45.1821)  loss_bbox: 3.7751 (3.7751)  loss_bbox_0: 3.7823 (3.7823)  loss_bbox_1: 3.7808 (3.7808)  loss_bbox_2: 3.7756 (3.7756)  loss_bbox_3: 3.7911 (3.7911)  loss_bbox_4: 3.7856 (3.7856)  loss_ce: 1.9574 (1.9574)  loss_ce_0: 2.0151 (2.0151)  loss_ce_1: 2.0196 (2.0196)  loss_ce_2: 2.1484 (2.1484)  loss_ce_3: 2.0683 (2.0683)  loss_ce_4: 2.0683 (2.0683)  loss_giou: 1.7011 (1.7011)  loss_giou_0: 1.7000 (1.7000)  loss_giou_1: 1.7040 (1.7040)  loss_giou_2: 1.7059 (1.7059)  loss_giou_3: 1.7022 (1.7022)  loss_giou_4: 1.7012 (1.7012)  cardinality_error_unscaled: 293.1250 (293.1250)  cardinality_error_0_unscaled: 293.1250 (293.1250)  cardinality_error_1_unscaled: 293.1250 (293.1250)  cardinality_error_2_unscaled: 281.9375 (281.9375)  cardinality_error_3_unscaled: 293.1250 (293.1250)  cardinality_error_4_unscaled: 293.1250 (293.1250)  class_error_unscaled: 85.5712 (85.5712)  loss_bbox_unscaled: 0.7550 (0.7550)  loss_bbox_0_unscaled: 0.7565 (0.7565)  loss_bbox_1_unscaled: 0.7562 (0.7562)  loss_bbox_2_unscaled: 0.7551 (0.7551)  loss_bbox_3_unscaled: 0.7582 (0.7582)  loss_bbox_4_unscaled: 0.7571 (0.7571)  loss_ce_unscaled: 0.9787 (0.9787)  loss_ce_0_unscaled: 1.0076 (1.0076)  loss_ce_1_unscaled: 1.0098 (1.0098)  loss_ce_2_unscaled: 1.0742 (1.0742)  loss_ce_3_unscaled: 1.0341 (1.0341)  loss_ce_4_unscaled: 1.0342 (1.0342)  loss_giou_unscaled: 0.8506 (0.8506)  loss_giou_0_unscaled: 0.8500 (0.8500)  loss_giou_1_unscaled: 0.8520 (0.8520)  loss_giou_2_unscaled: 0.8530 (0.8530)  loss_giou_3_unscaled: 0.8511 (0.8511)  loss_giou_4_unscaled: 0.8506 (0.8506)  time: 3.4521  data: 0.4687  max mem: 2932
Epoch: [0]  [ 100/7393]  eta: 1:17:39  lr: 0.000100  class_error: 85.74  loss: 28.2629 (33.7855)  loss_bbox: 1.5517 (2.3437)  loss_bbox_0: 1.5566 (2.3695)  loss_bbox_1: 1.5482 (2.3519)  loss_bbox_2: 1.5535 (2.3396)  loss_bbox_3: 1.5641 (2.3476)  loss_bbox_4: 1.5637 (2.3431)  loss_ce: 1.5467 (1.6584)  loss_ce_0: 1.5650 (1.6414)  loss_ce_1: 1.5443 (1.6461)  loss_ce_2: 1.5557 (1.6477)  loss_ce_3: 1.5392 (1.6545)  loss_ce_4: 1.5541 (1.6667)  loss_giou: 1.5534 (1.6289)  loss_giou_0: 1.5514 (1.6296)  loss_giou_1: 1.5541 (1.6292)  loss_giou_2: 1.5695 (1.6291)  loss_giou_3: 1.5526 (1.6289)  loss_giou_4: 1.5519 (1.6296)  cardinality_error_unscaled: 293.1875 (293.2420)  cardinality_error_0_unscaled: 293.1875 (293.2420)  cardinality_error_1_unscaled: 293.1875 (293.2420)  cardinality_error_2_unscaled: 293.1875 (293.1312)  cardinality_error_3_unscaled: 293.1875 (293.2420)  cardinality_error_4_unscaled: 293.1875 (293.1658)  class_error_unscaled: 75.6680 (75.4478)  loss_bbox_unscaled: 0.3103 (0.4687)  loss_bbox_0_unscaled: 0.3113 (0.4739)  loss_bbox_1_unscaled: 0.3096 (0.4704)  loss_bbox_2_unscaled: 0.3107 (0.4679)  loss_bbox_3_unscaled: 0.3128 (0.4695)  loss_bbox_4_unscaled: 0.3127 (0.4686)  loss_ce_unscaled: 0.7733 (0.8292)  loss_ce_0_unscaled: 0.7825 (0.8207)  loss_ce_1_unscaled: 0.7722 (0.8231)  loss_ce_2_unscaled: 0.7779 (0.8239)  loss_ce_3_unscaled: 0.7696 (0.8272)  loss_ce_4_unscaled: 0.7770 (0.8334)  loss_giou_unscaled: 0.7767 (0.8145)  loss_giou_0_unscaled: 0.7757 (0.8148)  loss_giou_1_unscaled: 0.7771 (0.8146)  loss_giou_2_unscaled: 0.7847 (0.8146)  loss_giou_3_unscaled: 0.7763 (0.8144)  loss_giou_4_unscaled: 0.7760 (0.8148)  time: 0.6098  data: 0.0105  max mem: 4353
Traceback (most recent call last):
  File "main.py", line 258, in <module>
    main(args)
  File "main.py", line 206, in main
    train_stats = train_one_epoch(
  File "/research/d4/gds/zwang21/ConditionalDETR/engine.py", line 41, in train_one_epoch
    loss_dict = criterion(outputs, targets)
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/research/d4/gds/zwang21/ConditionalDETR/models/conditional_detr.py", line 254, in forward
    indices = self.matcher(outputs_without_aux, targets)
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "/research/d4/gds/zwang21/ConditionalDETR/models/matcher.py", line 79, in forward
    cost_giou = -generalized_box_iou(box_cxcywh_to_xyxy(out_bbox), box_cxcywh_to_xyxy(tgt_bbox))
  File "/research/d4/gds/zwang21/ConditionalDETR/util/box_ops.py", line 59, in generalized_box_iou
    assert (boxes1[:, 2:] >= boxes1[:, :2]).all()
AssertionError
Traceback (most recent call last):
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/runpy.py", line 194, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 340, in <module>
    main()
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 326, in main
    sigkill_handler(signal.SIGTERM, None)  # not coming back
  File "/research/d4/gds/zwang21/anaconda3/lib/python3.8/site-packages/torch/distributed/launch.py", line 301, in sigkill_handler
    raise subprocess.CalledProcessError(returncode=last_return_code, cmd=cmd)
subprocess.CalledProcessError: Command '['/research/d4/gds/zwang21/anaconda3/bin/python', '-u', 'main.py', '--coco_path', '../data/COCO2017', '--output_dir', 'output/conddetr_r50_epoch50']' returned non-zero exit status 1.
*****************************************
Setting OMP_NUM_THREADS environment variable for each process to be 1 in default, to avoid your system being overloaded, please further tune the variable for optimal performance in your application as needed.
*****************************************
Killing subprocess 29668
Killing subprocess 29669
Killing subprocess 29670
Killing subprocess 29671
Killing subprocess 29672
Killing subprocess 29673
Killing subprocess 29674
Killing subprocess 29675

please simplify the steps as much as possible so they do not require additional resources to
run, such as a private dataset.

Expected behavior:
If there are no obvious error in "what you observed" provided above,
please tell us the expected behavior.
Environment:
Provide your environment information using the following command:
Collecting environment information...
PyTorch version: 1.8.0
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: CentOS Linux release 7.9.2009 (Core) (x86_64)
GCC version: (GCC) 11.2.0
Clang version: Could not collect
CMake version: version <IP_ADDRESS>

Python version: 3.8 (64-bit runtime)
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.22.2
[pip3] numpydoc==1.1.0
[pip3] pytorch-ignite==0.2.0
[pip3] pytorch-metric-learning==0.9.99
[pip3] torch==1.8.0
[pip3] torchaudio==0.8.0a0+a751e1d
[pip3] torchfile==0.1.0
[pip3] torchsampler==0.1.1
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.9.0
[conda] blas                      1.0                         mkl
[conda] cudatoolkit               10.2.89              hfd86e86_1
[conda] ffmpeg                    4.3                  hf484d3e_0    pytorch
[conda] mkl                       2021.2.0           h06a4308_296
[conda] mkl-service               2.3.0            py38h27cfd23_1
[conda] mkl_fft                   1.3.0            py38h42c9631_2
[conda] mkl_random                1.2.1            py38ha9443f7_2
[conda] numpy                     1.22.2                   pypi_0    pypi
[conda] numpydoc                  1.1.0              pyhd3eb1b0_1
[conda] pytorch                   1.8.0           py3.8_cuda10.2_cudnn7.6.5_0    pytorch
[conda] pytorch-ignite            0.2.0                    pypi_0    pypi
[conda] pytorch-metric-learning   0.9.99                   pypi_0    pypi
[conda] pytorch-mutex             1.0                        cuda    pytorch
[conda] torch                     1.10.0                   pypi_0    pypi
[conda] torchaudio                0.8.0                      py38    pytorch
[conda] torchfile                 0.1.0                    pypi_0    pypi
[conda] torchsampler              0.1.1                    pypi_0    pypi
[conda] torchsummary              1.5.1                    pypi_0    pypi
[conda] torchvision               0.9.0                py38_cu102    pytorch

Sorry but we never encountered this error. It indicates that the predicted boxes have a negative width or height. Which should not happen. The predicted (cx, cy, h, w) are fed into a sigmoid, so all h, w should be in range [0, 1].

Sorry but we never encountered this error. It indicates that the predicted boxes have a negative width or height. Which should not happen. The predicted (cx, cy, h, w) are fed into a sigmoid, so all h, w should be in range [0, 1].

Maybe the num_classes is not set correctly.

Encountered the same issue, and solved by only using 4 GPUs. Maybe it's caused by AMP or the internal bug of distributed training.


working fix for dashboard bug

This is a working fix for the dashboard bug. By including Angular's Safe Navigation Operator (?) on several fields in the Dashboard template, the problem seems to be fixed. This is related to fetching data in async operations and the template trying to load before the data is ready, resulting in certain fields being undefined. I don't know why this would occur for certain users and not others consistently... but either way this seems to be a working fix which I've verified using Carrie Paschall's account. We can improve upon this if we find there are more problems later.
This also modifies the Action Required section to remove the requirement for a w9 form.
There is also a modification for the function that fetches co-presenters. This was returning some empty presenters so there is just logic to avoid this now.
Finally, this also adds a change to avoid the mongoose Promise deprecation warning.

Also, note:
I'm pretty sure the problem with the login form becoming disabled was a result of the dashboard errors after a user logged in... meaning that this should also fix that problem. Again, will just have to seem if we see the problem persisting after this is merged.

Yeah I was also looking online and found this suggestion. I was gonna try it but glad to know you did and it's working so far.


Remote control (DPAD) navigation should work

Along with keyboard navigation (#13264), and handling keycodes for remote navigation, we should also support focus navigation with a TV remote control.
(Basically a duplicate of https://github.com/flutter/flutter/issues/31957 but for TV remotes)

Closing as TV remote controls just use LogicalKeyboardKey.arrowUp, etc.


Failed to create release: title is empty

Hello,
my colleagues and I use this plugin to upload generated pdf files compiled with latex in a release build. Since the upgrade of gitea to 1.13.0 we receive the following error: Failed to create release: title is empty.
More details
To release a version of a latex document we use in general the following git commands. For example to release a pdf document in version v0.1.0.
$ git tag -a v0.1.0 -m v0.1.0
$ git push origin v0.1.0

When the tag has been successfully pushed onto the git repository hosted on a gitea instance the following drone step will be started as one of others to push the release.
- name: push-tagged-gitea
  image: plugins/gitea-release
  settings:
    base_url: https://git.cryptic.systems
    api_key:
      from_secret: gitea_token
    files:
    - index.pdf
    checksum:
    - md5
    - sha1
    - sha256
    - sha512
    - adler32
    - crc32
  when:
    repo:
    - fh-trier/klinux_ws2021
    event:
    - tag

The step returns the following error:
Release v0.1.0 not found
time="2021-01-30T13:06:57Z" level=fatal msg="Failed to create the release. Failed to retrieve or create a release: Failed to create release: title is empty"

Now, why this does not work any more to release a compiled pdf document with the new version of gitea 13.0.0?
I tested additionally to release a new version over the web interface of gitea. There I must define a title for the release. I use v0.1.0 as title and the release step runs successfully. I'm kind of surprised that it works through the GUI but not through the CLI via git. Are we doing something wrong or is this the problem with the plugin?

If it worked before it sounds like Gitea has changed the requirements. Maybe it has not required ta title before?

I had this problem too. I found solution for it. You can add title  to .drone.yml file like below:
- name: push-tagged-gitea
  image: plugins/gitea-release
  settings:
    base_url: https://git.cryptic.systems
    api_key:
      from_secret: gitea_token
    files:
    - index.pdf
    title: release
    checksum:
    - md5
    - sha1
    - sha256
    - sha512
    - adler32
    - crc32
  when:
    repo:
    - fh-trier/klinux_ws2021
    event:
    - tag

It works for me.


How to delete a file larger than 1.18Gb

FTP OS:  Windows
FTP Server: ???
Computer OS: Windows
When trying to delete a file lager than 1.18Gb, your DeleteFileAsync returns a permission error.  Pretty sure it's because of the file size.  Do you have a work around/setting that can be made to enable the delete to work?
Thanks....................
David Hopkins
Netacent Inc.
Logs :

<paste logs here but DO NOT delete the lines above and below this line>

Its a server side issue. We do not do any checks. Delete is just one FTP command.


Mine' Page Shows 'Not Authorized' Briefly Before Content Loads

Issue Description

When navigating to the "Mine" page, the text "You are not Authorized" briefly appears for a second before displaying the shimmer loader. This creates a confusing user experience.
Expected Behavior

The "You are not Authorized" message should only appear when the user is confirmed to be unauthenticated.
While the authentication status is being determined, a loader should be displayed to prevent showing misleading messages.

Current Behavior

On initial load, the "You are not Authorized" message is briefly displayed even if the user is getting authenticating.
After this brief moment, the shimmer loader is displayed, and the content is loaded.

Screenshots

https://github.com/user-attachments/assets/9e3f141f-9802-43ea-8eb1-d0f603761114
Reproducibility

[x] This issue is reproducible
[ ] This issue is not reproducible

Steps to Reproduce

Visit the "Mine" page

 Observe the "You are not Authorized" message appearing momentarily before transitioning to the shimmer loader.

Severity/Priority

[ ] Critical
[ ] High
[ ] Medium
[x] Low

Additional Information

Checklist

[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.

Closing this issue as it has been resolved in PR #1296 .


Persistent navigation bar and panelHeader

Hi, thanks for the wonderful package!
My question is how to implement persistent navigation bar and panel header? For example, when I open other screens from the main navigation screens, the bottom navigation bar and the panel header should not disappear, they should remain. For example. in spotify when user opens album or other such screens from main screen the bottom navigation bar and panel remain and stay on album screen, how to implement this feature?
Thank you

Hi @suiebay
If you want to persist the weslide like navigation Bar or appBar, then you need to set your routes inside the body widget
body: IndexedStack(
  index: controller.indexPage,
  children: [
    RouterOutlet(module: ExploreModule()),
    //FavoriteModule(),
    // SearchModule(),
    //LibraryModule(),
    // LibraryModule(),
  ],
),

In the above example I am using the flutter_modular package
https://pub.dev/documentation/flutter_modular/latest/flutter_modular/RouterOutlet-class.html
There is a video about flutter_modular RouterOutlet but it is in portuguese: https://www.youtube.com/watch?v=69TRRRcazqk
I hope to answered your question ;)

Thank you for your response
Till your response I searched for some features that can do it, and found that wrapping the screens of body with CupertinoTabView can do what i want :) I don't know how correct this way of implementation but I would take a look for your answer
I close the issue because the question has been answered 👍


CLI argument for setting max number of viewer threads

Since we started parallelizing the viewer, it can end up hogging too much CPU such that it interferes with other running processes.
Add a CLI argument that sets the max number of threads used by the viewer.

RAYON_NUM_THREADS seems to be picked up since we're using the default rayon configuration

I still think we should expose it as a CLI argument (and ideally an argument to rr.spawn as well) for the purpose of making it easy to find for our users. Users shouldn't need to know we use Rayon

This might be a good time for a re_parallel crate that handles the rayon initialization, so it is only initialized once.
Right now I think we don't initialize the thread pool explicitly when called from Python (meaning rayon threads are unnamed)


Storage account name in Update Access Tier dialog is not surrounded by quotes

Storage Explorer Version: 1.10.0
Build: 20190916.5
Branch: master
Platform/OS: Windows 10/ Centos Linux release_7.6.1810(core)/ macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Right click one StorageV2 account -> Select 'Set Default Access Tier'.
Check the description on the 'Update Access Tier' dialog.

Expect Experience:
Indicate the storage account in the description on 'Update Access Tier' dialog.
Like 'Which access tier would you like the account 'myadlsxuanacc' to have?'
Actual Experience:
It doesn't indicate the storage account in the description on 'Update Access Tier' dialog.
Display 'Which access tier would you like myadlsxuanacc to have?'

More Info:

This issue also reproduces for one BlobStorage account.
This issue also reproduces for one blob.

@craxal Please remove localization label. If source string get updated with quotes localization will update target strings as well

Verified as fixed.


Add raw queries for sql server

When trying to run _query_raw on sql server I am getting an error saying "thread 'tokio-runtime-worker' panicked at 'Raw queries are not supported with database 'sqlserver''".  Is there a way to do raw queries for sql server?

Hmm, this should work fine. If you're using default-features = false, make sure the mssql feature is enabled.

Closing due to inactivity


[BUG] Resulting pruned FeatureData truncated due to max JSON depth set to 20

I have run into an issue using the RemoveSkippedScenarios.ps1 script when resulting pruned FeatureData has been truncated in depth due to max JSON depth set to 20 in the script:
❯ .\RemoveSkippedScenarios.ps1 .\TestExecution_combined.json .\FeatureData.json .\FeatureData_pruned.json
Reading '.\FeatureData.json'
Reading '.\TestExecution_combined.json'
Hashing each Test Execution scenario from '.\TestExecution_combined.json'
106 Test Execution scenario(s) found
Pruning unexecuted scenarios from Feature Data
Saving the pruned Feature Data to '.\FeatureData_pruned.json'
WARNING: Resulting JSON is truncated as serialization has exceeded the set depth of 20.

This happened in a project with feature files living in a deep directory structure, which seems to be the reason for maxing-out the JSON depth ("Folders" under "Folders" under "Folders" etc.)
As a result some data in the resulting FeatureData.json was not serialized correctly, eg.
"TableRows": [
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

Proposed trivial fix in PR #5

@AutomationPanda pinging you here as I am not sure if you receive notifications on the @AndyLPK247 account

Thanks for the pull request! I approved and merged it.


[Bug]: Viewport Discrepancies in the repo

Describe the bug
The viewports that have been set are not correct and the styles are not getting applied properly .
To Reproduce
Buggy ViewPort

Expected Behavior
Expected

Screenshot/ Video
No response
Desktop (please complete the following information)
No response
Additional context
No response

I would like to take this issue

Hi, please i would like to work on this issue

resolved

@pawas108ram  this view port that u used in the issue

is virtually impossible to achieve IRL
it can only be achieved by shrinking the tab in windows
also

this image has different viewport from the one above


JNI emitSignal is broken

Godot version:
3.2, as of 7ccb146a55edc41a9dd14c10efb8dc8f4b87f14e
Code is the same as on current master, so I assume it's broken on master, too.
OS/device including version:
Android 9 with tools running on Linux
Issue description:
This issue is a bit weird and is beyond my understanding of C++.
The method that's broken is this the JNI binding of nativeEmitSignal: https://github.com/godotengine/godot/blob/f69760b4befd7348c443960b84dd5f4e1d372e17/platform/android/plugin/godot_plugin_jni.cpp#L112-L133
As stated in the title, calling emitSignal in Android Java code (and thus calling the linked method above` causes the following crash:
05-24 22:23:20.404 22610 22642 E godot   : **ERROR**: Method failed. Returning: ERR_BUG
05-24 22:23:20.404 22610 22642 E godot   :    At: core/io/marshalls.cpp:1384:encode_variant() - Method failed. Returning: ERR_BUG
05-24 22:23:20.404 22610 22642 E godot   : **ERROR**: Failed to encode variant.
05-24 22:23:20.404 22610 22642 E godot   :    At: scene/debugger/script_debugger_remote.cpp:116:_put_variable() - Failed to encode variant.
05-24 22:23:20.404 22610 22642 E godot   : **ERROR**: Method failed. Returning: ERR_BUG
05-24 22:23:20.404 22610 22642 E godot   :    At: core/io/marshalls.cpp:1384:encode_variant() - Method failed. Returning: ERR_BUG

It may be obvious why this doesn't work, but for me it isn't. The only thing I remembered was that GodotLib.calldeferred does work and that the JNI C++ method for GodotLib.calldeferred looks very similar to the one for emitSignal. So I hacked something together for the emitSignal C++ code that works similarly to the calldeferred one functionally:
JNIEXPORT void JNICALL Java_org_godotengine_godot_plugin_GodotPlugin_nativeEmitSignal(JNIEnv *env, jobject obj, jstring j_plugin_name, jstring j_signal_name, jobjectArray j_signal_params) {

	String singleton_name = jstring_to_string(j_plugin_name, env);

	ERR_FAIL_COND(!jni_singletons.has(singleton_name));

	JNISingleton *singleton = jni_singletons.get(singleton_name);

	String signal_name = jstring_to_string(j_signal_name, env);

	int count = env->GetArrayLength(j_signal_params);
	Variant args[count];

	for (int i = 0; i < count; i++) {

		jobject j_param = env->GetObjectArrayElement(j_signal_params, i);
		if (j_param)
		  args[i] = _jobject_to_variant(env, j_param);

		env->DeleteLocalRef(j_param);
	};

	if (count == 1) singleton->emit_signal(signal_name, args[0]);
	if (count == 2) singleton->emit_signal(signal_name, args[0], args[1]);
}

I don't know why, but that one works but there has to be a better solution. 😅
CC: @m4gr3d who wrote the original code
Steps to reproduce:
Call emitSignal from Java with at least one signal parameter.
Minimal reproduction project:
N/A

@timoschwarzer Can you provide the arguments you were passing to the emitSignal call that caused the crash.

Just a simple String is enough. e.g. emitSignal("my Signal", "Hello World")

I don't know if it makes a difference, but I am running the app in debug mode (launched directly from the editor by clicking the Android run button in the top right corner) and in my signal handler GDScript function I just print the string.
func on_my_event(arg):
    print(arg)

I also tried some other types supported by _jobject_to_variant (Dictionary etc.) and they result in the same crash.


No login (Member of role {self.name}, so cannot login)

Describe the bug
The error
"Error Members" report -> No login (Member of role {self.name}, so cannot login)"
incorrectly shows  {self.name} rather than the members name
To Reproduce
Run the members report, with a member of a role, that has no login.
Expected behavior
Should show the members name
Additional context
Add any other context about the problem here.

Fixed in version 1.1


[Hub Generated] Review request for Microsoft.Security to add version preview/2023-02-01-preview

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[x] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Semantic validations passed locally:
PS C:\Repos\azure-rest-api-specs> oav validate-spec C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsBaselineRuleOperations.json
Semantically validating C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsBaselineRuleOperations.json without error
PS C:\Repos\azure-rest-api-specs> oav validate-spec C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanOperations.json
Semantically validating C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanOperations.json without error
PS C:\Repos\azure-rest-api-specs> oav validate-spec C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanResultsOperations.json
Semantically validating C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanResultsOperations.json without error

Model validations passed locally:
PS C:\Repos\azure-rest-api-specs> oav validate-example C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsBaselineRuleOperations.json
{
message: 'Validating "examples" and "x-ms-examples" in  C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsBaselineRuleOperations.json:\n',
level: '\x1B[32minfo\x1B[39m'
}
Validation completes without errors.
PS C:\Repos\azure-rest-api-specs> oav validate-example C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanOperations.json
{
message: 'Validating "examples" and "x-ms-examples" in  C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanOperations.json:\n',
level: '\x1B[32minfo\x1B[39m'
}
Validation completes without errors.
PS C:\Repos\azure-rest-api-specs> oav validate-example C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanResultsOperations.json
{
message: 'Validating "examples" and "x-ms-examples" in  C:\Repos\azure-rest-api-specs\specification\security\resource-manager\Microsoft.Security\preview\2023-02-01-preview\sqlVulnerabilityAssessmentsScanResultsOperations.json:\n',
level: '\x1B[32minfo\x1B[39m'
}
Validation completes without errors.

Avocado swagger -  API not in default tags are deprecated - not in any tab in master as well.

@tadelesh could you help to take a look at go sdk generation failure?

@tadelesh could you help to take a look at go sdk generation failure?

There are many duplicated operations.

@tadelesh could you help to take a look at go sdk generation failure?

There are many duplicated operations.

How can I resolve this?

@tadelesh could you help to take a look at go sdk generation failure?

There are many duplicated operations.

How can I resolve this? Updating the operations names should fix this? Should I update the tags as well?

I think you should remove the duplicated swagger file from tag.


Create the config directory in case it's missing

Always try to create the config directory when saving the client config
in case it doesn't exist.
Signed-off-by: Andy Goldstein<EMAIL_ADDRESS>

LGTM.


How to add http query parameter

@digitalbuddha
For some reason, we need to add special HTTP query parameters for each query/mutation.
for example https://example/graphql?type=SpeicalType, here SpecialType is the parameter, and different query/mutation has different parameters.
I knew that We might be able to do this by Okhttp interceptor, but is there better approach?

Interceptor is the preferred approach. We have leaned away from reimplementing http spec. For example you want to add query param while someone wants to add header and someone else a post body


KenLM as optional dependency

Either use this PR as a reference for how this could be implemented or just merge.
Changes:

KenLM as optional dependency
Removed Sentencepiece tokenizer stuff from the KenLM class, that functionality seemed totally orthogonal
Renamed to KenLMScorer. I am happy to reverse this as well, since KenLM supports any ARPA LM probably? But I think this name is the clearest.

@Gastron, thanks for this PR.

I'm okay with KenLMScorer, note that we also need to change yaml files involves ngram scorer. Also, tokenizer_path should be removed from the args.
Any example of function to parse the token_list given a sentencepiece model path?

* Any example of function to parse the token_list given a sentencepiece model path?

I added an implementation. In YAML it could be used like:
spm_vocab: !apply:speechbrain.tokenizers.SentencePiece.get_spm_tokens
    model_path: !ref <spm_file_path>

Thanks @Gastron, LGTM.


Add GSM0710 AT multiplexer implementation

I have been testing this out for a while now, and it seems to work most of the time, with a few hick-ups here and there.
I still have a few TODO comments, especially around hangup handling / V.24 signalling that I cannot seem to figure out how to get an ergonomic UX on, without it blowing up. Suggestions very much appreciated
Apart from that, I have cases where it feels like my application just stops receiving RX packets all together, resulting in infinite retransmissions until timeout. So far, my suspicion would be, that the underlying issue is the signalling handling above.
If you want to test it out, that would be nice
CC @Dirbaio

@Dirbaio I am back from summer vacation, and ready to see if I can drive this over the finish line, if you can find the time to test it out at your convenience sometime.


WKWebView KVO crash

When using KVO with WKWebView like this:
class SomeView {
   private let webView: WKWebView

   // KVO properties
    private let urlKVO: DynamicSubject<NSObject, URL?>
    private let titleKVO: DynamicSubject<NSObject, String?>
    private let canGoBackKVO: DynamicSubject<NSObject, NSNumber>
    private let canGoForwardKVO: DynamicSubject<NSObject, NSNumber>
    private let loadingKVO: DynamicSubject<NSObject, NSNumber>
    private let estimatedProgressKVO: DynamicSubject<NSObject, NSNumber>
    private let hasOnlySecureContentKVO: DynamicSubject<NSObject, NSNumber>

    // MARK: - Initializers

    init(frame: CGRect, configuration: WKWebViewConfiguration) {
        webView = WKWebView(frame: CGRect.zero, configuration: configuration)
        urlKVO = webView.dynamic(keyPath: "URL", ofType: Optional<URL>.self)
        titleKVO = webView.dynamic(keyPath: "title", ofType: Optional<String>.self)
        canGoBackKVO = webView.dynamic(keyPath: "canGoBack", ofType: NSNumber.self)
        canGoForwardKVO = webView.dynamic(keyPath: "canGoForward", ofType: NSNumber.self)
        loadingKVO = webView.dynamic(keyPath: "loading", ofType: NSNumber.self)
        estimatedProgressKVO = webView.dynamic(keyPath: "estimatedProgress", ofType: NSNumber.self)
        hasOnlySecureContentKVO = webView.dynamic(keyPath: "hasOnlySecureContent", ofType: NSNumber.self)

        super.init(frame: frame)
}

It will crash on dealloc with various unrecognized selectors sent to it :(

I've tried the code you posted and it does not seem to cause issues. Can you provide more details like to error messages?

its thworing

'-[WKWebView _stopScrollingAndZoomingAnimationsPinningToContentViewport:]: unrecognized selector sent to instance 0x10283da00'

I will try to figure it out tomorrow, probably I am doing something wrong then. Am I supposed to retain result of webView.dynamic method at all?

Yes, that's allowed, although you probably want them as signals:
private let urlKVO: Signal<URL?, NoError>
...
urlKVO = webView.dynamic(keyPath: "URL", ofType: Optional<URL>.self).toSignal()

Thanks.
The issue seems to be that WKWebView suddenly receives method calls for UIScrollView. It tries to call setDelegate and _stopScrollingAndZoomingAnimationsPinningToContentViewport which are both methods of UIScrollView, the later one is internal.

Figured out what is causing the issue. I have computed property scrollView:
class SomeView {
   private let webView: WKWebView
   var scrollView: UIScrollView {
     return webView.scrollView
   }

   // KVO properties
    private let urlKVO: DynamicSubject<NSObject, URL?>
    private let titleKVO: DynamicSubject<NSObject, String?>
    private let canGoBackKVO: DynamicSubject<NSObject, NSNumber>
    private let canGoForwardKVO: DynamicSubject<NSObject, NSNumber>
    private let loadingKVO: DynamicSubject<NSObject, NSNumber>
    private let estimatedProgressKVO: DynamicSubject<NSObject, NSNumber>
    private let hasOnlySecureContentKVO: DynamicSubject<NSObject, NSNumber>

    // MARK: - Initializers

    init(frame: CGRect, configuration: WKWebViewConfiguration) {
        webView = WKWebView(frame: CGRect.zero, configuration: configuration)
        urlKVO = webView.dynamic(keyPath: "URL", ofType: Optional<URL>.self)
        titleKVO = webView.dynamic(keyPath: "title", ofType: Optional<String>.self)
        canGoBackKVO = webView.dynamic(keyPath: "canGoBack", ofType: NSNumber.self)
        canGoForwardKVO = webView.dynamic(keyPath: "canGoForward", ofType: NSNumber.self)
        loadingKVO = webView.dynamic(keyPath: "loading", ofType: NSNumber.self)
        estimatedProgressKVO = webView.dynamic(keyPath: "estimatedProgress", ofType: NSNumber.self)
        hasOnlySecureContentKVO = webView.dynamic(keyPath: "hasOnlySecureContent", ofType: NSNumber.self)

        super.init(frame: frame)
}

which i access outside SomeView and when it calls something on it while deallocating it gets somehow redirected to WKWebView or something like that.
I believe its caused by method swizzling in Bonds KVO.

I still don't see how that can be related to KVO. Not saying it isn't, but I don't see a connection.
Maybe something outside SomeView retains scrollView after SomeView and its WebView are deallocated, so ScrollView outlives its parent WebView and causes problems.
Additionally, maybe you should reset all delegates to nil in dealloc if you've set up any.

I dont see the connection either, however it just doesnt happen when I do KVO manually by addObserver and observeValue method. Happens just with Bonds dynamic method.

I'll try to research this more in following days.


Compose / Combine imported queries or mutations

I want to compose / combine queries or mutations.
Example:
  import getUserQuery from '~/apollo/queries/User'
  import allPermissionsQuery from '~/apollo/queries/AllPermissions'

Normally I know how to use e.g. getUserQuery with apollo.
But how can I combine both imported graphQL queries?

use fragments: http://graphql.org/learn/queries/#fragments


nextcloud-client-bin: init at 3.13.0

Description of changes
Adds separate package since it is not built from source like nextcloud-client. Allows room in the future to add linux capability.

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[X] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Please move your package to pkgs/by-name/ne/nextcloud-client-bin.
Also, please follow Commit Conventions. In your case, rebase, squash your commits, and reword the final commit to be nextcloud-client-bin: init at 3.13.0

No need to leave comments about changes in the init commit. Also, please move all the 3 files into a single package.nix file

It would also be nice if you could use your GitHub name and email for this PR. If you're worried about the privacy of your email, you can use the users.noreply.github.com email provided by GitHub. You can see it here https://github.com/settings/emails

I would recommend you to do a "soft reset" by using git reset --soft HEAD~1 to remove your old name and email from the commit. It will delete the commit from the history and move any changes back into the staging area. However, make sure to commit any changes first before doing this.

Please reword the commit to nextcloud-client-bin: init at 3.13.0 and change the pr title as well

I would recommend you run nixpkgs-fmt on your package.nix next time to automatically comply with formatting code conventions

Installed nixpkgs-fmt and reformatted package.nix. Hopefully that works as intended

Result of nixpkgs-review pr 308426 run on aarch64-darwin 1

1 package built:

nextcloud-client-bin

I didn't want to be so forward on that. I am more than willing to be a maintainer for this. I pushed a commit adding me as a maintainer.

You will need to add yourself to the maintainer list in that case. Please take a look at https://github.com/NixOS/nixpkgs/tree/master/maintainers

Adding yourself to the maintainer list should be a separate commit and should be worded as such maintainers: add ArkieSoft

Awaiting being added to maintainers

Please rebase, delete 353738427f22c09b132954b81ff408f5750b18e6 and move<PHONE_NUMBER>9720f6d25e734454801953de55fcb4 to be before 78d7178372dfbd42ce21f1e4633bab3179c7b0e0

Did you try building the source package on darwin? What made you decide that it is not feasible?

Closing because of no answer from author.


UIApplication.shared unavailable in application extensions on Xcode 13 beta 4

Describe the bug
Looks like since Xcode 13 beta 3, UIApplication.shared can not be referenced directly without marking the referencing code as unavailable in application extensions.
I'm getting the following error when I build:
'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead.
Relevant link:
https://forums.swift.org/t/set-application-extension-api-only-on-a-spm-package/39333/11
Steps To Reproduce
Steps to reproduce the behavior:
1. Create new project in Xcode 13 beta 4
2. Add Amplify packages using SPM
3. Add Amplify to project using `amplify init`
4. Build the project

Expected behavior
Project should build.
Amplify Framework Version
1.13.0
Amplify Categories
API
Dependency manager
Swift PM
Swift version
5.5
CLI version
5.2.1
Xcode version
13.0 beta 4 (13A5201i)
Relevant log output
No response
Is this a regression? (i.e. was this working before a version upgrade)
No response
Device
iPhone12-simulator
iOS Version
15.0
Specific to simulators
No response
Additional context
No response

the solution is to add @available(iOSApplicationExtension, unavailable). If anyone from @aws-amplify-ops can resolve this issue so we can continue testing with Xcode 13, that would be fantastic...

I'd like to add that this is not a beta issue but will stay an issue for everyone updating to Xcode 13 in September.

To work around this issue, we check out a local copy of amplify-ios, override the SPM package dependency by adding that local directory, and apply this patch. You may have to do this for many of your dependencies, but fortunately for us in the weeks since Xcode 13.0b3 introduced this issue, our upstream vendors (except AWS) have already fixed their packages.
One gotcha: it's not possible to add a one-liner available when the relevant code is deeper inside a function. Wrapping the logging plugin with PersistentLoggingPlugin when isDevMenuEnabled in DEBUG is an example of this. We don't use the dev menu functionality, so the patch above comments it out rather than restructuring the code so only the relevant bits can be marked unavailable.

So for now I'm using https://github.com/maianhvu/amplify-ios/tree/patch-uiapp-shared, thanks to @maianhvu :)

So for now I'm using https://github.com/maianhvu/amplify-ios/tree/patch-uiapp-shared, thanks to @maianhvu :)

Thanks for the mention! It was a quick and dirty fix I made in stealth mode to get my app up and running. Sorry for the insane amount of prop-drilling, I guess I can patch it up a little with environment variables and see if the folks over at AWS appreciate this solution.

So Xcode 13 beta 5 seemed to have fixed this issue:
You don’t need to annotate code as unavailable for use in application extensions if it references APIs annotated as unavailable for use in application extensions. This reverts a requirement that Xcode 13 Beta 3 introduced. (80615922) (FB9332020)

Not sure if this is going to be a permanent solution to whatever this thread was addressing, or if we should continue to be on the look out for issues around this

This appears to still be an issue if you are making Swift Packages.  My Swift Package project which relies on Amplify compiles under under Xcode 12.  Under Xcode 13 beta 5, Amplify fails to build its Issue Reporter class with: 'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead.  This happens in 2 places where UIApplication.shared is referenced.
Do I need to rewrite the app using manual API calls and avoid Amplify?  I'm not sure what this error really means.

Do I need to rewrite the app using manual API calls and avoid Amplify? I'm not sure what this error really means.

That seems like throwing the baby out with the bath water, but tbh Amplify is giving me way too much trouble than it solves my problems as well.
The issue comes from Xcode thinking that we're building the app for App Extensions (e.g. notification handlers, share) where calls to UIApplication.shared are prohibited.
Admittedly, this is a code smell in my opinion and most packages should ideally not call UIApplication.shared internally, and instead use dependency injection to let the host app decide what to do in situations requiring such a global singleton access. What I've done in my fork above was to do just that--abstracting the calls to UIApplication.shared to an protocol that the host app can implement.
I haven't submitted a PR yet because this seems like an Xcode issue and likely to be resolved in the future. Per @mangoCARE 's suggestion I have downloaded Xcode 13 beta 5 but the issue still persists on my M1 MacBook Pro using Swift Package Manager.

Yes I would agree that it's odd that Amplify does things like using the Application singleton, which you'd expect to be handled by the host app.

This appears to still be an issue if you are making Swift Packages. My Swift Package project which relies on Amplify compiles under under Xcode 12. Under Xcode 13 beta 5, Amplify fails to build its Issue Reporter class with: 'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead. This happens in 2 places where UIApplication.shared is referenced.
Do I need to rewrite the app using manual API calls and avoid Amplify? I'm not sure what this error really means.

It would be nice if you could provide a demo app showcasing the issue when building it in a package. I have tried a couple of times, and it seems to be working fine.

It looks like this change was reverted in Xcode 13 beta 5 according to the release notes:

You don’t need to annotate code as unavailable for use in application extensions if it references APIs annotated as unavailable for use in application extensions. This reverts a requirement that Xcode 13 Beta 3 introduced. (80615922) (FB9332020)

I was able to pull the most recent version of amplify in my project and it compiled/ran without any issues on Xcode 13 beta 5.
I'll leave the ticket open until we get the GM of Xcode 13 in case they change their minds again.

I am trying to run tthe IOS Amplify tutorial in Xcode13beta4 and getting a number of amplify package related errors - ex. errror1 .../ios/Amplify/DevMenu/View/IssueReporter.swift:110:23: 'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead.  error2 -...ios/Amplify/DevMenu/View/IssueReporter.swift:110:30: 'open(_:options:completionHandler:)' is unavailable in application extensions for iOS..

I am trying to run tthe IOS Amplify tutorial in Xcode13beta4 and getting a number of amplify package related errors - ex. errror1 .../ios/Amplify/DevMenu/View/IssueReporter.swift:110:23: 'shared' is unavailable in application extensions for iOS: Use view controller based solutions where appropriate instead. error2 -...ios/Amplify/DevMenu/View/IssueReporter.swift:110:30: 'open(_:options:completionHandler:)' is unavailable in application extensions for iOS..

Please use the latest beta. It seems that the recent version have reverted the cause of the issue.


Create SPI for configuring WF instance launched by the EmbeddedWildFl…

…yLauncher.
related issue https://issues.jboss.org/browse/AF-1029
Enable to turn off jboss logging to not get ClassCastException betweek JDK logging and JBoss logging

@tiagobento Would you mind reviewing this?


[Docs] Fix the controlled RadioGroup example

Closes https://github.com/adobe/react-spectrum/issues/6056
Hey guys I have one question.
Would it be better to just add the empty string ('') check over here?
https://github.com/adobe/react-spectrum/blob/9390151edf56eefcec0aa5635f34643affe10640/packages/%40react-aria/radio/src/useRadio.ts#L82-L92
to something like this?
let tabIndex: number | undefined = -1;
- if (state.selectedValue != null) {
+ if (state.selectedValue != null && state.selectedValue !== '') {
  if (state.selectedValue === value) {
    tabIndex = 0;
  }
} else if (state.lastFocusedValue === value || state.lastFocusedValue == null) {
  tabIndex = 0;
}
if (isDisabled) {
  tabIndex = undefined;
}

✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[x] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:
Docs
http://localhost:1234/react-aria/useRadioGroup.html#controlled-value
https://github.com/adobe/react-spectrum/assets/71210554/74f3d7c9-4e63-464b-b1d1-a184919930ce
🧢 Your Project:

GET_BUILD

Thanks @sookmax this is the correct fix, we allow falsy id's such as empty strings. So you could do something like this https://stackblitz.com/edit/vitejs-vite-28q1zf?file=src%2FApp.tsx,package.json

@snowystinger Ah that's interesting! Never imagined there would be a case where a radio value actually is "" haha. Thanks for sharing the sandbox!


[shiva] add a port of shiva c++ engine

Thanks! We really do need to update the documentation to be closer to the modernized version.