Decomp round 2

More decomposition of matter.js
(Note - restructuring is complete but leaving as draft because I need another test/fix cycle or two.)
Adds new packages:

packages/types contains the bulk of data definitions from matter.js.  This includes datatypes, TLV, clusters, etc.
packages/fabric contains the bulk of the lower-level Matter logic from matter.js
packages/node contains the higher-level node API including behaviors, endpoints and nodes
packages/app is a new entry point that reexports all of above and automatically loads specialization for the detected platform via export conditions
packages/nodejs-ble is rename of packages/matter-node-ble.js
packages/examples is rename of packages/matter-node.js-examples

The new package structures conform more closely to the export layout as defined by "exports" in package.json.  Previously we had a mix of snake-case and CamelCase for sub-package exports.  I moved to all "snake" for public exports.
The new structures encourages direct import of types (clusters, behaviors, endpoint types) that are expensive either at build time or runtime.  There are index exports for all of these components but they are not in the default package export.  So e.g. you can import OnOff from @project-chip/matter.js-types/clusters or (better) @project-chip/matter.js-types/clusters/on-off.
The original "matter.js" package is mostly for backwards compatibility now except for some of the controller stuff that still needs to move into the "fabric" package.  Ideally the new "app" package would be our "main" package but this will need to wait on either a new package name or a deprecation period sufficient for a (very) major breaking change.
"matter.js" contains a large number of re-exports to maintain backward compatibility.  The "legacy" API we've been threatening to deprecate still lives there as well.  Should make it easier to make a clean break when the time comes.
The sub-package exports of generated code required a huge number of export files both for compatibility and for re-export in the "app" package.  I added custom build logic to "app" and "matter.js" to create these at build time.
Given the large number of import changes I figured it was an opportune time to add package aliasing.  We now alias via package.json "imports" field for most intra- (and some inter-) package imports.  This makes the imports considerably more concise and aids in portability.  A bit fiddly to set up but they work well once in place.
I did various refactoring along the way.  In particular, I removed generic parameters from a number of the components in "fabric" that no longer need to be generic for the "node" API.  This makes the code less verbose and was easy to compensate for in the legacy API where this specialization is necessary.
I also removed the "ContextT" template parameter from many of the APIs in "fabric".  Makes things less wordy and hopefully not controversial.  The controller vs. device branches of the code both only ever deal with a single context type.  I moved a bit of shared functionality into the base SessionContext type and added assertion functions for the few places where specialization is still required.
The default implementation of "time" is now fully functional.  Platform specialization is still available if necessary but I was able to fully implement the API using standard JS so I don't expect it'll ever be necessary.
Includes numerous codegen updates to match the new package layout and make the codegen logic available at build time.

I seems the "File move" was not working that good with ble and react-native package, also matter,js as it seems ... with this I will have a lot of fun with my draft PRs ... But i manage that somehow ... seems last push destroyed that?
I think there is no easy way to fix that ... so we should simply live with it ... unless you have ideas.
Re "testing it out" ... we have the nightlies for that ... so we will merge that and then I play around and we fix the rest if needed

Well it's just heuristics in git but you can boost file match with -M

I seems the "File move" was not working that good with ble and react-native package, also matter,js as it seems ... with this I will have a lot of fun with my draft PRs ... But i manage that somehow ... seems last push destroyed that?
I think there is no easy way to fix that ... so we should simply live with it ... unless you have ideas.
Re "testing it out" ... we have the nightlies for that ... so we will merge that and then I play around and we fix the rest if needed

More changes now so might've pushed over git's 50% change threshold...  Actually a quick scan through "protocol" shows move detection working pretty well but try -M if you have specific files that don't match


capacity directory: Move out nodes which have not been online for 1 week

Issue migrated from https://api.github.com/repos/Jumpscale/lib9/issues/351, opened by @andhartl
Remove node which are down for more than a week for the Nodes capacity view

is this still the case?

is this still the case?

what is still the case ? this issue was a feature request.
And no, currently there is nothing that remove node even if they are down for ever

still the case. not online nodes pollute the directory.

issue still exist , the nodes was still shown on capacity while it has a long time off more than one week

It was show back for the Ibiza event, a new release will be pushed in production today which hide them again.

It's in production


[Bug]: Input Widgets with Auto height enabled when entering longer text, contents are not fully hugged

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
Drag and drop any of the Input widgets (Input, Phone Input, Currency Input)
Select Auto height in "Height" property
In the "Label" property enter a longer text with more than four or five lines
Observe all the contents are not inside the border of the widget
Also when we move the widget downwards, we also observe that the contents are moved inside or the auto height is being increased for the widget. But then when we drag and drop another widget we are facing the same issue.
https://user-images.githubusercontent.com/104895602/188643207-f1323186-72a7-4344-a130-3c88b5fd9d75.mp4

This issue has been resolved in this PR, https://github.com/appsmithorg/appsmith/pull/16943

Working fine. Moving to done.


Relax test for shotgun.

Closes #5805.

Em, coordinate also has an issue: https://xgboost-ci.net/blue/organizations/jenkins/xgboost-win64/detail/PR-5835/1/pipeline/ .  I will leave that for another PR.


Intraword emphasis

See discussion at https://github.com/jgm/djot/discussions/94#discussioncomment-4127713
TL;DR: it's not clear if fan_tas_tic should contain an em. It does now.
Problem with such implicit emphasis inside the words is that they tend to be greedy and worm themselves into text which wasn't intended to be emphasized, like file_nam.es or large numbers 1_000_000 or urls http://use_dashes_in_urls.com.
An "obvious" fix is to require explicit syntax for intraword case: fan{_tas_}tic. The problem is that its unclear what constitutes the word. We don't want to use unicode definition of the word, as it is our general principle that we don't want to bring in unicode tables. If we define word as non-ascii whitespace, some examples stop working, like *_nested_* or (*parens*) or ¡*Hola*!.

I think the fix for nested case is easy: we can require delimiter to be next to whitespace or a delimiter, recognized by djot. So, things like [_link text_](http://...) or "_quoted emph_" would work, and potentialy (*parens*) (potentailly because I don't think djot is recognizing () by itself, but it's natural to say that it does).
The Hola example won't work,  and things like **Really**???, but that seems niche (I'd expect adjacent punctuation to be inside emphasis in practice).
Note that we have precedence for treating punctuation like words in attribute sytnax: ¡Hola!{.emph}

See https://github.com/jgm/djot/discussions/94#discussioncomment-4138785

As @bpj noted in the linked thread, I think it's good practice simply to include identifiers or filenames containing underscores in verbatim backticks, which makes the problem go away.

I think the fix for nested case is easy: we can require delimiter to be next to whitespace or a delimiter, recognized by djot.

That would mean that, for example “_Dog_” would fail to be emphasized (note the curly quotes). I worry that this sort of half-solution is going to be too fragile and lead to too many confused users.

I worry that this sort of half-solution is going to be too fragile and lead to too many confused users.

I think there are two kinds of confusion:

I wanted the emph to work, but it didn't
I wasn't trying to add emph at all, but part of my code is italicaized for some reason

The first confusion seems less perplexing than the second one: you are doing emphasis, so, if it doesn't work for whatever reason, you can use full syntax. In any case, emphasis is explicitly what you are trying to do.

That is, false positives seem worse here than false negatives.
With the current rules in my blog porting exercise I've hit false positives several time and no false negatives (eg, 10 \_ and zero {_) ("grep" results)

You may be right that the first kind of confusion is more common, but I don't know if it's harder to fix.  Figuring out why "_Dog_" is emphasized but “_Dog_” isn't might be very confusing for users.  Explaining to them that djot treats ascii punctuation differently from non-ascii punctuation might be pretty confusing. Adding a backslash escape isn't hard and always works for the first case.

Yeah, I don't think it's harder to fix, I think it might be harder to realize what the fix is needed.
In the first case, you try to create an emphasis, type “_Dog_”, it doesn't work, you try with explicit syntax.
In the second case, you are writing a nice number, like 33_550_336, glance at the output, and see 33550336 which looks subtly wrong, but it's unclear why -- you are just inputting a number, right?
But that's 100% me trying to role-play, don't have a good feeling how it all will play out in practice.

The number case is a good one -- unlike filenames and identifiers, that's probably not something you'd put in verbatim backticks.  (In what contexts are numbers written this way?)

(In what contexts are numbers written this way?)

That’s my idiosyncratic way to say “a lot” basically, don’t think it’s a common convention or anything, an example would be

which gives us 307_200_000 ray-triangle intersection tests

The number case is a good one -- unlike filenames and identifiers, that's probably not something you'd put in verbatim backticks. (In what contexts are numbers written this way?)

In some programming languages (I am familiar with it from Perl) it is allowed to write numbers this way for readability (i.e. underscores inside numbers are ignored). I'd say that being a programming usage I'd expect it to be between backticks, and otherwise it is probably niched enough to expect those who use it to escape the underscores.
Either way I think the best "fix" is to say explicitly in the syntax specification that

Intra-word underscores do count as emphasis delimiters according to the usual rules;
therefore literal intra-word underscores should be typed as \_ (abc\_def\_ghi), but
for clarity authors should use {_..._} (abc{_def_}ghi) for intra-word emphasis.

Conceivably it might, since Lua is unusual among modern programming languages in being Unicode-challenged, be declared to be up to implementations how they wish to treat intra-word underscores, which in practice would mean that both \_ and {_..._} would be de rigeur for source which wishes to be portable between implementations.

Conceivably it might, since Lua is unusual among modern programming languages in being Unicode-challenged,

The way I understand this, our reluctance to rely on unicode character classes is not due to limitations of a particular implementation, but a design decision to better support unicode documents. Saying "[-_*\[\](){} \t\r\n] are the only symbols recognized by djot, and everything else gets pasted into the output verbatim" is a sure-way to make sure we don't mess up user's unicode input, whatever that might be.
In particular, this makes us resilient to future changes in unicode. If, for example, we use unicode's conception of "word", than each version of unicode would formally need to cause a new version of djot, as unicode properties are not fixed in time.
Not sure this is exactly what jgm has in mind, but that's my wishful reading :) I do think that that's a great approach to tackle complexity here, and I'd love this to be a requirement for all impls (I think djot, unlike markdown, should explicitly discourage creation of flavors)

Figuring out why "Dog" is emphasized but “Dog” isn't might be very confusing for users.

Interestingly, we have a similar problem with attribute attachment:
"good boy"{.ascii}
“good boy”{.unicode}

That's right -- this is another place where we use Lua's pattern-matching to find "the last word" to which to attach an attribute.  We could always drop this convenience altogether and just force people to use explicit spans, to avoid this sort of confusion.

Note that in
"good boy"{.ascii}

you're actually getting the attributes on the double_quoted node:
    double_quoted class="ascii"
      str text="good boy"

So here there is actually a container; it's not a bare word.

We could make the following change to can_open/can_close calculations for inline containers:
diff --git a/djot/inline.lua b/djot/inline.lua
index da9e8cd..8fdc052 100644
--- a/djot/inline.lua
+++ b/djot/inline.lua
@@ -98,8 +98,10 @@ function Tokenizer.between_matched(c, annotation, defaultmatch, opentest)
   return function(self, pos)
     local defaultmatch = defaultmatch or "str"
     local subject = self.subject
-    local can_open = find(subject, "^%S", pos + 1)
-    local can_close = find(subject, "^%S", pos - 1)
+    local can_open = find(subject, "^%S", pos + 1) and
+                       (pos == 0 or find(subject, "^[%s%p]", pos - 1))
+    local can_close = pos > 0 and find(subject, "^%S", pos - 1) and
+                        find(subject, "^[%s%p]", pos + 1)
     local has_open_marker = matches_pattern(self.matches[pos - 1], "^open%_marker")
     local has_close_marker = byte(subject, pos + 1) == 125 -- }
     local endcloser = pos

This has the following effects on tests, some of which are fine and some undesirable:
FAILED at attributes.test line 105
--- INPUT -------------------------------------
{#id .cla*ss*
--- EXPECTED ----------------------------------

{#id .class

--- GOT ---------------------------------------

{#id .cla*ss*

-----------------------------------------------

FAILED at super_subscript.test line 1
--- INPUT -------------------------------------
H~2~O
--- EXPECTED ----------------------------------

H2O

--- GOT ---------------------------------------

H~2~O

-----------------------------------------------

FAILED at super_subscript.test line 7
--- INPUT -------------------------------------
mc^2^
--- EXPECTED ----------------------------------

mc2

--- GOT ---------------------------------------

mc^2^

-----------------------------------------------

FAILED at super_subscript.test line 13
--- INPUT -------------------------------------
test^of superscript ~with subscript~^
--- EXPECTED ----------------------------------

testof superscript with subscript

--- GOT ---------------------------------------

test^of superscript with subscript^

-----------------------------------------------

FAILED at emphasis.test line 29
--- INPUT -------------------------------------
foo*bar*baz
--- EXPECTED ----------------------------------

foobarbaz

--- GOT ---------------------------------------

foo*bar*baz

-----------------------------------------------

FAILED at emphasis.test line 63
--- INPUT -------------------------------------
foo_bar_baz
--- EXPECTED ----------------------------------

foobarbaz

--- GOT ---------------------------------------

foo_bar_baz

-----------------------------------------------

FAILED at emphasis.test line 69
--- INPUT -------------------------------------
aa_"bb"_cc
--- EXPECTED ----------------------------------

aa“bb”cc

--- GOT ---------------------------------------

aa_“bb”_cc

-----------------------------------------------

FAILED at emphasis.test line 107
--- INPUT -------------------------------------
_(_foo_)_
--- EXPECTED ----------------------------------

(foo)

--- GOT ---------------------------------------

(foo)

-----------------------------------------------

238 tests completed in 0.012 s
PASSED:  230
FAILED:    8
ERRORS:    0

Of course, one could decide to treat the _ delimiter specially -- which is what a lot of markdown implementations do.
Or perhaps all emphasis/strong emphasis delimiters, but not delimiters for things like superscript.
But I think there's some value in keeping things uniform and predictable.

One approach could be to just bite the bullet and require H{~2~}O and e=mc{^2^}.
Another possibility would be to give a radically different treatment to super and subscript. Instead of behaving like the other "surround" syntax, it could work this way:
H_2O = subscripted 2 (next single character) (note, with the change to inline emphasis, this wouldn't be confused with emphasis marking)
H{_22}O = subscripted 22
mc^2 = superscripted 2
mc{^the first even prime}

On second thought, the proposal above for subscript would just bring back the problem of intraword underscores creating unwanted markup.  Could do the same, though, with tilde.

Another bad example by @jamii:
_[foo](foo_bar)_

I am migrating my own blog (from lunamark) and hit this issue in URLs (typically Wikipedia URLs).
I am unsure how to fix it, for now I will probably just encode the URLs.

I thought about that a bit more, and I feel like the parser should just ignore all openers and closers except parens when it is processing the location part of a link. That will not fix other instances of this but they can be solved with the curly bracket syntax.
Do you agree? If so I can try to fix it.

@catwell in CommonMark the solution is to add space before the closing parenthesis in the source text. I use it this way for at least 10 years now and never had an issue with URLs any more in any system.

@dumblob In @catwell’s example [link](foo_(bar_qux)), the first closing paren is part of the URL. Spaces don’t help. CommonMark has a balanced parenthesis rule to deal with this. Djot evidently requires the parens to be escaped: [link](foo_\(bar_qux\)) or [link](foo_%28bar_qux%29). In any case, this is a separate issue from intraword emphasis that’s already been filed:

#232

@andersk I do think it's related to intraword emphasis. It only happens due to the interaction of emphasis and parens in the URL.
For instance, your example breaks:
> input = "[Paxos](https://en.wikipedia.org/wiki/Paxos_(computer_science))"
> djot.render_ast_pretty(djot.parse(input))
doc
  para
    link destination="https://en.wikipedia.org/wiki/Paxos_(computer_science"
      str text="Paxos"
    str text=")"

But if you get rid of an underscore it does not:
> input = "[Paxos](https://en.wikipedia.org/wiki/Paxos_(computer-science))"
> djot.render_ast_pretty(djot.parse(input))
doc
  para
    link destination="https://en.wikipedia.org/wiki/Paxos_(computer-science)"
      str text="Paxos"

Still it's good that you filled it separately.

I'm undecided on this, but I don't this is a deal breaker for me, just not ideal. I too like to throw un_der_scores in the middle of a word for fun, or S_P_E_L_L out a word with them. I just wanted to mention that you can encounter similar output mischief writing math using * as multiplication.
C=65*8+1_000_000*8
That said it's fair to expect math to be backticked.
As I ponder it, I think I would prefer intraword emphasis to work and not be emphasized, but I haven't thought through all of the consequences. Personally I'm okay with "_Dog_" working while “Dog” doesn't, but I will admit having the option to differentiate between more types of punctuation and whitespace (making both work) would be ideal.
Some user confusion might be solvable with UX.

Use a different text or background color for characters in the ASCII range versus unicode range, possibly a 3rd color for glyphs that do things (parenthesis, etc).
Syntax highlighting, so at a glance you can see if your blocks were detected

Just thinking out loud.


Issue using zabbix via proxy

Hi and thanks for making this great project, I was quite happy when I found it because I'm currently involved in a project that needs some email notifications.
However, I have some issues getting it to run properly.
We have a working python script that can send email fine, so the variables appears to be good, however the proxy does not work as intended it seems.
Python script that works
eirikz@hostname:~/email-oauth2-proxy$ more /usr/lib/zabbix/alertscripts/send_mail.py_back
#!/usr/bin/python3

import requests
import sys
# import pdb
# pdb.set_trace()

in_to = sys.argv[1]
in_subject =  sys.argv[2]
in_body =  sys.argv[3]
# in_host =  sys.argv[4]
# in_value =  sys.argv[5]
tenant_id = $tenant_id
client_id = $client_id
client_secret = $client_secret
scope = 'https://graph.microsoft.com/.default'
token_url = f'https://login.microsoftonline.com/$tenant_id/oauth2/v2.0/token'

token_data = {
    'grant_type': 'client_credentials',
    'client_id': client_id,
    'client_secret': client_secret,
    'scope': scope
}

token_r = requests.post(token_url, data=token_data)
token = token_r.json().get('access_token')

user_id = $email_address
email_url = f'https://graph.microsoft.com/v1.0/users/{user_id}/sendMail'
headers = {
    'Authorization': f'Bearer {token}',
    'Content-Type': 'application/json'
}
email_data = {
    'message': {
        'subject': in_subject,
        'body': {
            'contentType': 'Text',
            'content': in_body
        },
        'toRecipients': [
            {
                'emailAddress': {
                     'address': $recipient1
                }
            },
            {
                'emailAddress': {
                     'address': $recipient2

However, when doing the following with the emailproxy
[SMTP-1587]
documentation = *** note: this server will work for both Office 365 and personal Outlook/Hotmail accounts ***
server_address = smtp-mail.outlook.com
server_port = 587
server_starttls = True
local_address = $local_ip

<EMAIL_ADDRESS>documentation = *** note: this is an advanced O365 account example; in most cases you want the version above instead ***
token_url = https://login.microsoftonline.com/$tenant_id/oauth2/v2.0/token
oauth2_scope = https://graph.microsoft.com/.default
oauth2_flow = client_credentials
redirect_uri = http://$local_ip
client_id = $client_id
client_secret = $client_secret

And doing the following in zabbix

Yields the following error

2024-11-27 10:05:42: Initialising Email OAuth 2.0 Proxy (version 2024-11-13) from config file /home/eirikz/email-oauth2-proxy/emailproxy.config
2024-11-27 10:05:42: Starting IMAP server at local_ip:1993 (unsecured) proxying outlook.office365.com:993 (SSL/TLS)
2024-11-27 10:05:42: Starting POP server at local_ip:1995 (unsecured) proxying outlook.office365.com:995 (SSL/TLS)
2024-11-27 10:05:42: Starting SMTP server at local_ip:1587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)
2024-11-27 10:05:42: Starting IMAP server at <IP_ADDRESS>:2993 (unsecured) proxying imap.gmail.com:993 (SSL/TLS)
2024-11-27 10:05:42: Starting POP server at <IP_ADDRESS>:2995 (unsecured) proxying pop.gmail.com:995 (SSL/TLS)
2024-11-27 10:05:42: Starting SMTP server at <IP_ADDRESS>:2465 (unsecured) proxying smtp.gmail.com:465 (SSL/TLS)
2024-11-27 10:05:42: Initialised Email OAuth 2.0 Proxy - listening for authentication requests. Connect your email client to begin
2024-11-27 10:05:44: Accepting new connection from local_ip:56084 to SMTP server at local_ip:1587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)
2024-11-27 10:07:05: Accepting new connection from local_ip:46452 to SMTP server at local_ip:1587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)

Your Python script is working because it is using Microsoft Graph rather than SMTP. The zabbix error looks like an issue with your Azure/Entra setup, but it's hard to say any more without the debug log. Either way, it sounds like the proxy is providing value in an important environment, so please do consider sponsoring for commercial or dedicated support.

Aha, I got further with enabling debugging, had to add the email address as username (and random password) in zabbix

2024-11-27 10:43:52: New incoming connection to SMTP server at <IP_ADDRESS>:1587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)
2024-11-27 10:43:52: Accepting new connection from <IP_ADDRESS>:47758 to SMTP server at <IP_ADDRESS>:1587 (unsecured) proxying smtp-mail.outlook.com:587 (STARTTLS)
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) --> [ Client connected ]
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'220 SERVERNAME.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 27 Nov 2024 10:43:51 +0000 [08DD0E9D053B6175]\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-- b'220 SERVERNAME.outlook.office365.com Microsoft ESMTP MAIL Service ready at Wed, 27 Nov 2024 10:43:51 +0000 [08DD0E9D053B6175]\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) --> b'EHLO customer.onmicrosoft.com\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     --> b'EHLO customer.onmicrosoft.com\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-SERVERNAME.outlook.office365.com Hello [<IP_ADDRESS>]\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-SIZE 157286400\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-PIPELINING\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-DSN\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-ENHANCEDSTATUSCODES\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-STARTTLS\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-8BITMIME\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-BINARYMIME\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-CHUNKING\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250 SMTPUTF8\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     --> b'STARTTLS\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'220 2.0.0 SMTP server ready\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-> [ Starting TLS handshake ]
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) [ Successfully negotiated SMTP server STARTTLS connection - re-sending greeting ]
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     --> b'EHLO customer.onmicrosoft.com\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-> [ TLSv1.3 handshake complete ]
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-SERVERNAME.outlook.office365.com Hello [<IP_ADDRESS>]\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-SIZE 157286400\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-PIPELINING\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-DSN\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-ENHANCEDSTATUSCODES\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-AUTH LOGIN XOAUTH2\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-8BITMIME\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-BINARYMIME\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250-CHUNKING\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'250 SMTPUTF8\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-- b'250-SERVERNAME.outlook.office365.com Hello [<IP_ADDRESS>]\r\n250-SIZE 157286400\r\n250-PIPELINING\r\n250-DSN\r\n250-ENHANCEDSTATUSCODES\r\n250-AUTH PLAIN LOGIN\r\n250-8BITMIME\r\n250-BINARYMIME\r\n250-CHUNKING\r\n250 SMTPUTF8\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) --> b'AUTH PLAIN\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-- b'334 \r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) --> b'[[ Credentials removed from proxy log ]]'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     --> b'AUTH XOAUTH2\r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587)     <-- b'334 \r\n'
2024-11-27 10:43:52: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587<EMAIL_ADDRESS>    --> b'[[ Credentials removed from proxy log ]]\r\n'
2024-11-27 10:43:58: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587<EMAIL_ADDRESS>    <-- b'535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [SERVERNAME.NORP279.PROD.OUTLOOK.COM 2024-11-27T10:43:58.434Z 08DD0E9D053B6175]\r\n'
2024-11-27 10:43:58: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587<EMAIL_ADDRESS><-- b'535 5.7.139 Authentication unsuccessful, SmtpClientAuthentication is disabled for the Tenant. Visit https://aka.ms/smtp_auth_disabled for more information. [SERVERNAME.NORP279.PROD.OUTLOOK.COM 2024-11-27T10:43:58.434Z 08DD0E9D053B6175]\r\n'
2024-11-27 10:43:58: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587) <-- [ Server disconnected ]
2024-11-27 10:43:58: SMTP (<IP_ADDRESS>:47758-{<IP_ADDRESS>:1587}-smtp-mail.outlook.com:587<EMAIL_ADDRESS>--> [ Client disconnected ]

Thanks for following up. The error message here points to a simple fix. On a related note, you've also changed the scope value in your configuration entry to a MS Graph one; this will likely lead to another error. I'd recommend reverting this to the value shown in the example configuration.

Thanks Simon, I was under the understanding that this proxy would remove the need to do basic auth, which according to the article
If your authentication policy disables basic authentication for SMTP, clients cannot use the SMTP AUTH protocol even if you enable the settings outlined in this article. For more information, see [Disable Basic authentication in Exchange Online](https://learn.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/disable-basic-authentication-in-exchange-online).
Or am I misunderstanding a difference between basic auth and simple auth ?

Yes, the proxy does remove the need to do basic auth.
Very confusingly, Microsoft refers to both basic- and OAuth-driven authentication, and in effect SMTP as a whole protocol as SMTP AUTH. You do need to enable SMTP AUTH because without it you cannot use SMTP at all as there's no way to authenticate, but you don't need basic auth (which is due to be removed from O365 next year anyway).

Yes, afaik basic auth is already removed from this tenant, which makes the above microsoft statement confusing for me, I read it as
if basic auth == 0
then
snmp auth == n/a
which would mean the only option is graph api usage, which I don't think this proxy can do (nor have I seen any other proxy's that can do it, outside of this simple python script.
My problem with the python script is that it cannot directly integrate into zabbix, as such I can't pass the MACROS from zabbix into the mail body..

No, that's not actually the case. For example, I have an O365 account that does not accept basic auth for SMTP, but does work with OAuth. Have you actually tried this? (Always worth trying, because Microsoft's documentation is confusing at the best of times, and often downright contradictory.)
Re: Graph usage – you're correct that the proxy doesn't support this, but if you're only looking for SMTP, SMTP2Graph may fit your requirements.


Possible to maximize a tiled window directly?

This is not a feature request, just a question - is it possible to maximize a tiled window? Currently, I either float the window, then maximize it, or cycle through the layouts until I get to the "Monocle" layout. Is there a more direct way to switch a tiled window to fullscreen I should be using?
If it's not possible, no worries and I'll close this issue. I know active development has stopped long ago on this, but it's truly a gem of a window manager and I'll continue to use it regardless.

I think I would just bind a key to SetLayout (GetWorkspace) "Maximized".

I know active development has stopped long ago on this, but it's truly a gem of a window manager and I'll continue to use it regardless.

Thanks. :-) And yeah, I still use it daily on all my machines. It is basically "done" from my perspective.

Thanks!


please

Sorry, this is not a plugin issue. Can you please create a PerlCooldown plugin please

This is not appropriate.


TCP connect feature

TCP 3-way handshake.

Test cases to include:

[ ] no host
[ ] non existing host
[ ] valid host
[ ] valid host, no service running (connection refused)
[ ] valid host, blocked service (connection timeout)


kernel.org is incorrectly reported as being "insecure"

The only thing preventing Linux from getting "gold" is the odd "Secured delivery against man-in-the-middle (MITM) attacks" issue.  https://www.kernel.org does not have any scripting or frames or ability to really do anything to it, so the "failures" being reported do not make much sense.
For a static site, are all of these "requirements" really sane?

I just finished reading #1346, saw this issue, and thought they might be in a similar vein...

I don't think so as kernel.org does support https properly.
How do you think they are the same?

I was thinking they're similar in that the details text says you should not serve crypto sigs over HTTP but kernel.org's CDN doesn't force a redirect to HTTPS: http://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.3.8.tar.sign.
I am just graping at straws that this is the missing 4% to achieve gold🥇status...
A cryptographic hash (e.g., a sha1sum) MUST NOT be retrieved over http and used without checking for a cryptographic signature.

No, that's not the reason.  Look at the kernel project on the badging site and see that we are failing because:
https://www.kernel.org // X-Content-Type-Options was not set to "nosniff".
And the requirement is:
The project website, repository (if accessible via the web), and download site (if separate) MUST include key hardening headers with nonpermissive values. (URL required)

Bumping this up as kernel.org does now provide X-Content-Type-Options and sets it to nosniff, but the tool still seems to insist that it doesn't.
In checking the .rb code in app/lib/hardened_sites_detective.rb it looks like it is checking this header, however I could not tell if it was maybe a case-sensitive thing or not...

I will need to check, but your case sensitivity suggestion is a likely culprit!

As noted, the website https://www.kernel.org does set "X-Content-Type-Options" to "nosniff", and the security headers website notes this. Off to debug this, thanks for the report.

HTTP header field names are definitely case-insensitive, per RFC 2616 section 4.2. I thought so anyway, but best to check.

@gregkh -
We had two different issues, a bug in the BadgeApp and a legitimate detection on the git.kernel.org site (!).
You were 100% correct that we accidentally did case-sensitive matching on HTTP fields, even though it should be case-insensitive matching. Our fault, thanks for reporting it. Nice job on the hypothesis, you must have seen this before :-). The production site now has that fixed.
However, the badge system is correctly reporting that there are no HTTP hardening values on git.kernel.org. Given the importance of the git.kernel.org site, adding some HTTP hardening settings seems like a reasonable thing to ask for. Here's a more detailed report from securityheaders.com:  https://securityheaders.com/?q=https%3A%2F%2Fgit.kernel.org&followRedirects=on

As git.kernel.org is a static site, having all of those headers don't really do anything, but hey, it doesn't hurt either...  They should now be fixed, let's see if the cii badging site handles it properly...

Nope, something is wrong, I now see the error of:
http://www.kernel.org/ should now be fine! // One or more of the required security hardening headers is missing.
Any ideas "which" header is missing on what site?

@gregkh -
In this case, both https://www.kernel.org and repo https://git.kernel.org are missing X-XSS-Protection. They just need to add this to their headers:
X-XSS-Protection: 1

I agree that many hardening headers don't help on truly static sites. However, I know of no way to reliably detect static sites (trying to detect a "login" link isn't reliable). And as noted, it can't hurt to require it, especially since some "static" sites later quietly become not-completely-static sites. So if we want to make sure it's there on sites that need it, I don't see any simple way other than just flat requiring it.
I also agree that reporting which header is missing would be useful. This reminds me of a quote from the Unix-Hater's Handbook: "Ken Thompson  has  an  automobile  which  he  helped  design... if the driver makes a mistake, a giant “?” lights up in the center of the dashboard. “The experienced driver... will usually know what’s wrong.” We could do better.
Currently we only check 'x-content-type-options' (for nosniff) and the presence of 'content-security-policy', 'x-frame-options', 'x-xss-protection', and we check those for the project URL https://www.kernel.org and repo https://git.kernel.org.  Easy reports for each page are at https://securityheaders.com/?q=https%3A%2F%2Fwww.kernel.org&followRedirects=on and https://securityheaders.com/?q=https%3A%2F%2Fgit.kernel.org&followRedirects=on However, there's been a recent change; it looks like securityheaders is no longer reporting about x-xss-protection (which is a header that's getting pretty old in the tooth & only really useful for old browsers). We might want to remove the check for x-xss-protection. I'll post that for discussion on the mailng list. But I suggest adding those for now, can't hurt.

I appreciate the work to add the hardening headers, especially the new ones for https://git.kernel.org/.
I've posted discussions on the badge mailing list. In rare show of unanimity, everyone seems to agree that the time for X-XSS-Protection has passed. Basically, the idea of hardening headers is still valid, but X-XSS-Protection shouldn't be part of that set. Issue here: https://github.com/coreinfrastructure/best-practices-badge/issues/1426 and mailing list discussions here: https://lists.coreinfrastructure.org/g/CII-badges/messages?start=6:2020:240
Unless there's a sudden discovery of something soon, I expect we'll drop X-XSS-Protection this week, and given the other changes the Linux kernel has made, the Linux kernel will have this last criterion met. Thank you for all your help and collaboration.

It's really been unanimous; all agree that hardening websites is important, but that X-XSS-Protection is an obsolete way to do it. So pull request #1426 removes that specific HTTP header from the enforced list.
So given the Linux kernel's recent hardening of https://git.kernel.org/, I think you merely have to edit the Linux kernel entry for gold "hardened_site" at https://bestpractices.coreinfrastructure.org/en/projects/34/edit?criteria_level=2#hardened_site and assert that it is "Met" (make sure you edit the rationale).
At that point I think the Linux kernel earns a gold badge, and a big congrats to everyone involved!

@gregkh - go ahead and edit the Linux kernel project badge entry at your convenience - looks like it's earned a gold! Not surprising, but it's a good thing and hopefully a useful example for others.
Once the Linux kernel completes earning its gold badge I intend to close this issue. (I'll keep it open until then in case there's an unexpected problem.)

I thought I edited it, but it didn't seem to "stick".
So I've done it again, and from the page it seems like we have 100%, but the badge still says "silver".  Anything else I am missing that I need to do here?
Thanks!

I also just got an email saying we received the "gold" badge, but the site is not showing that, is there some timeout to refresh things?

Congrats! It shows gold on my end.
Perhaps there is a caching problem. Goodness gracious, that should not happen. I can try to investigate, but no matter what, congratulations!


Feature Request - Dot conveys overall task status for a Day

Great plugin .. thanks for the hard work on this.
I've used Obsidian previously and one very nice feature was that the Calendar dots would indicate the following

presence of a dot meant the journal page existed (your red dot does that now)
a second dot for TODO status

open tasks (TODO) items exist on this journal - the second dot is hollow
no open tasks on this journal - the second dot is filled.

Another approach for Logseq that would not require two dots might be to have 3 different colors for a single dot

white(or black for light mode) - page exists and has NO TODOs or DONE items for the day  (July 4 and 22)
red - page exists and has open TODO items in it (July 17, 18, 23, 26, 28, 29 and 30)
green - page exists and has only DONE items (July 6, 12, 14 and 19)

Good idea, I will think about it and do some tests first. The final release may not be that fast.

Thanks for your consideration.
On Fri, 29 Jul 2022, 6:01 pm Richard Yu, @.***> wrote:

Good idea, I will think about it and do some tests first. The final
release may not be that fast.
—
Reply to this email directly, view it on GitHub
https://github.com/vipzhicheng/logseq-plugin-block-calendar/issues/10#issuecomment-1198992649,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5V4HMPDYJNITQQPJJ6A5LVWOFUPANCNFSM547SDVGA
.
You are receiving this because you authored the thread.Message ID:
@.***>

The feature has been implemented, please take a look.


[Scalebar] Localization

Related #247
Localizes the scalebar
Preview of an Arabic localization (right-to-left language sample):

If this is just for the scalar, why are there so many Sources/ArcGISToolkit/Resources/en.lproj/Localizable.strings strings?

If this is just for the scalar, why are there so many Sources/ArcGISToolkit/Resources/en.lproj/Localizable.strings strings?

Those changes actually came from #334, which was already reviewed and merged into this branch. Sorry for the confusion, I probably should have left that PR in draft until this was merged.

Resolved 1 merge conflict, ready for review again


LUCENE-9302: Grouping to use long to avoid overflows

Description

LGTM. I have some minor questions about the approach here, mostly around how reduce the need for explicit casts to long.
This seems like a fine/desirable change to me, but I was curious why there was some intimation on the Lucene upstream jira issue that this might be a controversial change on the Lucene side and might be better handled in Solr (if I'm reading that correctly)?
In any event I think any such questions/concerns are out of scope for this porting to 9x, so no objections, just wanted to jot down thoughts as I had them!


/brewing cant create Mundane Potions

What is the version of the plugin you''re using?
1.7.10
What is your Spigot version?
Paper version git-Paper-171 (MC: 1.20.1) (Implementing API version 1.20.1-R0.1-SNAPSHOT) (Git: 33bec7f)
Please describe the bug.
Using a normal brewing stand, place water bottle at the bottom and Magma_Cream at the top (or any other ingredient for mundane potion, (Glistering Melon, Spider eyes, Sugar, Blaze Powder, Ghast Tears, or Redstone Dust)) and it creates a Mundane Potion.
But when using /brewing command (or [brew] sign), when you put the ingredients in, nothing occurs.
Also tested with PCI 1.7.8 and 1.7.9 to no avail.
Please list your plugins.
PortableCraftingInv only
Anything else to add?
No response

Thanks for the report. I'll get it fixed asap.


⚠ Bofrost.at has degraded performance

In dcd2329, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1647 ms

Resolved: Bofrost.at performance has improved in 96e266e after 10 minutes.


A simple clock using minimalistic 3x2 pixel numerical digits

This request is to pull an additional app.
The developed app is a simple clock using minimalistic 3x2 pixel numerical digits.
It can be tested here: https://sebi5361.github.io/BangleApps/ choosing 3x2 Pixel Clock.
(I am a newbie so don't hesitate to comment.)

Nice. Is this ready to merge?

Yes it is!


Fix incorrect parameter in LibriTTS hifigan vocoder

This PR addresses an issue introduced by the changes in PR #2044. In that update, while the LJSpeech HiFi-GAN recipe was updated, I forgot to update the LibriTTS HiFi-GAN recipe. This resolves the problem reported in Issue #2241.
@BenoitWang @mravanelli

@BenoitWang are you ok with this change?


Compatibility for 1.2.1

This issue is to track the compatibility requirements for Ceylon 1.2.1. This issue assumes that 1.2.1 will be binary compatible with 1.2.0, so the problem is "just" about making the toolset use the 1.2.1 artifacts, rather than complaining about mismatched versions.
The specific requirements are:

We need to be able to run a "1.2.0 module" (that is, a module compiled using the 1.2.0 toolset) using a 1.2.1 distribution.
 Specifically his requirement seems to relate to the implicit dependency on ceylon.language that gets added to compiled modules.

Presumably we also need to be able to compile a module using 1.2.1 which depends on a 1.2.0 module.

When Ceylon gets support for assemblies we expect them to be able to override declared versions in a similar manner to what's required here. An assembly is expected to be (approximately) a zipped repository, so associating some version overrides with a repository seems like a sensible approach to items 1. and 2. In this case we'd be associating some overrides of the dist modules with the dist repo.

Doing this using overrides.xml seems to work fine, except for a couple of places where before we checked for version equality, but now cannot (because the versions are no longer equal). One place was the AbstractModelLoader which checked that the loaded module had a matching version. The other was the ModuleValidator which actively preventing overriding of direct module imports (i.e. those declared in a module.ceylon).
I don't particularly like the idea of just removing the checks, but there's no obvious alternative. The more up to date module itself doesn't know that it can replace the older module, so a more sophisticated check isn't possible without knowing about repos, and these points in the code no nothing about repos.

An assembly is expected to be (approximately) a zipped repository, so associating some version overrides with a repository seems like a sensible approach to items 1. and 2

I don't think I agree with this, I don't think what defines the needed overrides is "a repository" at all. It's the assembly itself, which in turn is defined by its contents, ie the actual versions of the available modules.
So to me an assembly would be a zipped repository with the overrides stored separately from it, just like a JAR has a META-INF the assembly could have a special folder holding metadata.
I say this because I don't think "a repository" is the correct "level" for handling overrides, repositories are dynamic, things get added and removed, we change repository paths and ordering all the time when using the tools, etc.
What determines the need for an override is your application or the distribution itself, neither one of those are defined by a single repository (remember that often for our distribution we use both system modules from the distribution folder and the ones published to the user repository in ~/.ceylon/repo/)
So to me an override is something global, it's:

part of an assembly
passed on the command line (--system-overrides?)
part of the distribution

The first two points are easy enough to understand, I think, but the last one, "part of the distribution", is somewhat more involved. We could literally make it part of the distribution, let's say $CEYLON_HOME/lib/system-overrides.xml. That would be easy enough to support.
But the problem comes if we ever want to support downloading a distribution from the Herd using only a minimal bootstrap. In that case what "defines" the distribution and its associated overrides file are the components themselves. So a possible solution for the distribution itself could be to store the overrides.xml file directly in the ceylon-module-resolver-X.Y.Z.car module.

I'm not saying that repositories in general should support overrides. But the fact is that there is a dist repository. Putting the information about how the modules in it should override other modules doesn't seem like a bad idea to me. Putting them somewhere else in the dist is of course possible, but I don't really see how that's better. But honestly where this file goes doesn't interest me particularly, I'd just like it to end up being consistent with assemblies if possible (and that's hard because we're not really thinking about them yet).
Saying repositories are dynamic things is a generalization. The dist repository is not dynamic.

In that case what "defines" the distribution and its associated overrides file are the components themselves.

Well to my mind the distribution is an assembly, and would be downloadable as a single thing, not as individual components.

Here's a question: Does the metamodel (specifically  `module`.dependencies and modules.list) show the runtime versions or the compile time versions?

But the fact is that there is a dist repository. Putting the information about how the modules in it should override other modules doesn't seem like a bad idea to me.

Like I said, the system components could be retrieved from some other location, it's not exactly advisable to do so (like using -Xbootclasspath in Java), but we do so for example in the test suite. It's the reason we have ant publish in our build scripts. That wouldn't work unless you copy that overrides file to the user repository as well. But the user repository could easily hold several versions of those system modules, so which version of the overrides file is the correct one?
That's what I mean when I say that the repository is not the identifying feature.
It might seem like a convenient place to put it but IMO it's just not correct.
An assembly is different because it's a snapshot of a repository, there's no way to mess with the versions or the ordering of the module lookup anymore and the overrides file is bound to that specific snapshot.

Btw, it also means that we have to add support for a new overrides.xml artifact in the CMR (not a completely trivial task). And you'd have to find it in a place where nothing gets stored, a non-module folder, the root for example, which also means extending the CMR with new functionality it didn't have before. And all that just to find a single file in a single repository. It just doesn't seem right.
A system to provide an override file from outside the CMR and pass it does already exist and could IMO be extended to include the needed new functionality.

Does the metamodel (specifically module.dependencies and modules.list) show the runtime versions or the compile time versions?

Since the modules pointed to will be the result of the override, and the original imports may not be available, they should point to the result of the override (runtime version). In the future we may add an API to query the original imports, but those will likely point to a Module? in case (most likely) that it's not available.

Last night after I posed that question I found that `module` doesn't work for precisely this reason. I agree we should use the runtime version because that's the only real choice we have. Now I just need to figure out how...


Can't build with xcode 10

Trying to build for both ios 12 device and emulator
While building module 'tflite' imported from GeneratedPluginRegistrant.m:11:
In file included from <module-includes>:1:
In file included from tflite-umbrella.h:13:
ios_image_load.h:1:10: fatal error: 'vector' file not found
#include <vector>
         ^~~~~~~~
1 error generated.
GeneratedPluginRegistrant.m:11:9: fatal error: could not build module 'tflite'
#import <tflite/TflitePlugin.h>

Hi,
you can refer to the instructions here: https://github.com/shaqian/flutter_tflite#ios
vector is only available in Objective-C++.

I'm sorry, my bad. Thank you


Pylint sanity check using docker stays in a hung state.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): NO
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): MacOS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NO
TensorFlow installed from (source or binary):  -
TensorFlow version (use command below): -
Python version: -
Bazel version (if compiling from source): -
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: -
GPU model and memory: -

Describe the current behavior
When the following command is executed to perform sanity checks using a docker container, the pylint step just hangs and doesn't complete.
$  tensorflow/tools/ci_build/ci_build.sh CPU tensorflow/tools/ci_build/ci_sanity.sh

== omitted logs ==

=== Sanity check step 2 of 15: do_pylint (Python 3 pylint) ===

ERROR_ALLOWLIST="^tensorflow/python/framework/function_test\.py.*\[E1123.*noinline ^tensorflow/python/platform/default/_gfile\.py.*\[E0301.*non-iterator ^tensorflow/python/platform/default/_googletest\.py.*\[E0102.*function\salready\sdefined ^tensorflow/python/feature_column/feature_column_test\.py.*\[E0110.*abstract-class-instantiated ^tensorflow/contrib/layers/python/layers/feature_column\.py.*\[E0110.*abstract-class-instantiated ^tensorflow/contrib/eager/python/evaluator\.py.*\[E0202.*method-hidden ^tensorflow/contrib/eager/python/metrics_impl\.py.*\[E0202.*method-hidden ^tensorflow/contrib/rate/rate\.py.*\[E0202.*method-hidden ^tensorflow/python/training/tracking/tracking\.py.*\[E0202.*method-hidden ^tensorflow/python/platform/gfile\.py.*\[E0301.*non-iterator ^tensorflow/python/keras/callbacks\.py.*\[E1133.*not-an-iterable ^tensorflow/python/keras/engine/base_layer.py.*\[E0203.*access-member-before-definition ^tensorflow/python/keras/layers/recurrent\.py.*\[E0203.*access-member-before-definition ^tensorflow/python/kernel_tests/constant_op_eager_test.py.*\[E0303.*invalid-length-returned ^tensorflow/python/keras/utils/data_utils.py.*\[E1102.*not-callable ^tensorflow/python/autograph/.*_py3_test\.py.*\[E0001.*syntax-error ^tensorflow/python/keras/preprocessing/image\.py.*\[E0240.*Inconsistent method resolution "
Running pylint on 2805 files with 8 parallel jobs...

It just hangs in this state inside the docker container
Describe the expected behavior
However, when I run the check directly on my system (MAC), the stage passes:
$  ./tensorflow/tools/ci_build/ci_sanity.sh

== omitted logs ==

=== Sanity check step 2 of 15: do_pylint (Python 3 pylint) ===

ERROR_ALLOWLIST="^tensorflow/python/framework/function_test\.py.*\[E1123.*noinline ^tensorflow/python/platform/default/_gfile\.py.*\[E0301.*non-iterator ^tensorflow/python/platform/default/_googletest\.py.*\[E0102.*function\salready\sdefined ^tensorflow/python/feature_column/feature_column_test\.py.*\[E0110.*abstract-class-instantiated ^tensorflow/contrib/layers/python/layers/feature_column\.py.*\[E0110.*abstract-class-instantiated ^tensorflow/contrib/eager/python/evaluator\.py.*\[E0202.*method-hidden ^tensorflow/contrib/eager/python/metrics_impl\.py.*\[E0202.*method-hidden ^tensorflow/contrib/rate/rate\.py.*\[E0202.*method-hidden ^tensorflow/python/training/tracking/tracking\.py.*\[E0202.*method-hidden ^tensorflow/python/platform/gfile\.py.*\[E0301.*non-iterator ^tensorflow/python/keras/callbacks\.py.*\[E1133.*not-an-iterable ^tensorflow/python/keras/engine/base_layer.py.*\[E0203.*access-member-before-definition ^tensorflow/python/keras/layers/recurrent\.py.*\[E0203.*access-member-before-definition ^tensorflow/python/kernel_tests/constant_op_eager_test.py.*\[E0303.*invalid-length-returned ^tensorflow/python/keras/utils/data_utils.py.*\[E1102.*not-callable ^tensorflow/python/autograph/.*_py3_test\.py.*\[E0001.*syntax-error ^tensorflow/python/keras/preprocessing/image\.py.*\[E0240.*Inconsistent method resolution "
Running pylint on     2805 files with 16 parallel jobs...

pylint took 77 s

Standalone code to reproduce the issue
Running the above-mentioned commands should reproduce the issue
** Supporting logs in attachments **

sanity_pass.log -> run on MAC.
sanity_fail.log -> run inside docker as per the above-mentioned command where the process hangs.

sanity_pass.log
sanity_fail.log

Hi, any update on this issue? @ymodak

@angerson , mentioning for notification.

The issue seems to be with the pylint version that was being used.
With pylint==1.6.4 the sanity check step2 hangs, but with the latest version of pylint==2.5.3, it completes successfully.


 That is, emitting DWARF doubles the amount of time it takes for the linker to execute. We don't pay this cost for "go test" or "go run", because we turn DWARF off for those already.
The Mac shows a similar ~2X slowdown. I thought maybe #12259 was related but given that Linux clearly is unaffected by that issue, it appears to be a general DWARF problem.
I've put the proposal to turn off DWARF by default (#26074) on hold pending better understanding of where all the time is going (this issue). If we decide that DWARF really is a 2X cost, then we need to go back to #26074 and decide whether that's worth paying on every build when most people make no use of the DWARF info.
/cc @dr2chase @cherrymui @thanm @ianlancetaylor @randall77 @aclements @RLH

An easy thing to try would be to reduce the compression level to favor speed.

This is pretty promising. Using zlib.BestSpeed wins back about half of the linker slow-down. Comparing no-DWARF ("old") to BestSpeed compressed DWARF ("new"):
name           old time/op         new time/op         delta
BuildCmdGoAll          10.0s ±11%          10.8s ± 5%   +8.03%  (p=0.003 n=9+9)
LinkCmdGo              626ms ± 5%          860ms ± 2%  +37.36%  (p=0.000 n=10+8)

And the impact on binary size is minimal.
             cmd/go bytes
nodwarf      10106953
dwarf        12159049 nodwarf+20%
dwarf-speed  12408905 nodwarf+23%
dwarf-nozlib 17766473 nodwarf+76%

@aclements benchcmd looks really nice. Where does it come from? Some light googling and github searches didn't turn it up.

@cespare: https://godoc.org/github.com/aclements/go-misc/benchcmd

Here's a comparison of building vs just linking jujud between Go 1.10 and tip (including BestSpeed DWARF compression):
name           old time/op         new time/op         delta
BuildJujudAll          43.5s ± 0%          41.6s ± 2%   -4.29%   (p=0.000 n=8+10)
LinkJujud              9.28s ± 1%         11.73s ± 2%  +26.36%   (p=0.000 n=9+10)

So, we're winning on non-incremental builds, probably because of indexed export info, but the link step in isolation is 26% slower. Not great, though certainly better than 2X or the 40% reported in https://github.com/golang/go/issues/26074#issuecomment-400844992.

Looking at the CPU profile when linking cmd/go I see 4.76% of CPU time in dwarfGenerateDebugInfo, 6.35% in dwarfGenerateDebugSyms, and 12.7% of time in compressSyms.  By  way of comparison, runtime.scanObject takes 15.87%.
These numbers seem plausible to me and I think we've answered the question posed by this issue, so closing.


No paper_dataset_list() interface in PapersWithCodeClient?

I cannot find a method to get the datasets used in the paper

Added. Release in paperswithcode-client version 0.2.2


Design Search Component on the Home page

I would like to make changes to this search bar styling

In an attempt to improvise on the styling of the search bar and add effects to it
I would like to work on this issue as a part of GSSOC'21

@nandini2110 This issue has been solved as a sub-issue of some other issue. Please look on other issues.


Droping decimal for dh11

Hi is there some reason to drop decimal part of temerature for DHT11?
I modified the code to include it, and had parallel DHT11 and DHT22 connected,one next to the other, and then the temperature value was same.
https://github.com/danjperron/PicoDHT22/blob/b92d34f2fa9b3168cf32d42107c79a555a974fb6/DHT22.py#L163

The DHT11  returns only integer.  The precision is ±2°C.
The DHT22 returns  one tenth of degree.  The precision is ±0.5°C.
DIsplay  decimal on the DHT11 isn't a true value.

Le 4 juin 2021 à 07:56, jpajzinka @.***> a écrit :
Hi is there some reason to drop decimal part of temerature for DHT11?
I modified the code to include it, and had parallel DHT11 and DHT22 connected,one next to the other, and then the temperature value was same.
https://github.com/danjperron/PicoDHT22/blob/b92d34f2fa9b3168cf32d42107c79a555a974fb6/DHT22.py#L163 https://github.com/danjperron/PicoDHT22/blob/b92d34f2fa9b3168cf32d42107c79a555a974fb6/DHT22.py#L163
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/danjperron/PicoDHT22/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABBF7XHVMEMJAYBW33AG6GDTRC5OBANCNFSM46CVEOXA.


How to use without firebase service

In the China's network environment, there is no firebase and google play, how to use it in this case?

This plugin support Barcode scanning, Image Labeling and much more,
If you want to use Barcode scanning then no need to include firebase service.
You cannot use google play service option while taking build, but you can use bundle option.
Example: you can check for barcode scan bundle option here

Try the latest version.
Also note that google_ml_kit has been split in multiples plugins, to avoid adding unnecessary dependencies to your project. You can start using google_mlkit_barcode_scanning instead.
More details here:

https://github.com/bharat-biradar/Google-Ml-Kit-plugin/tree/master/packages/google_ml_kit
https://github.com/bharat-biradar/Google-Ml-Kit-plugin
https://github.com/bharat-biradar/Google-Ml-Kit-plugin/tree/documentation/packages/google_mlkit_barcode_scanning


HTTP Status 500 when accessing .bob files

Under JRE17 and tomcat 9, I can successfully access localhost:8080/dbwr, but when I try to access my own .bob files using url like 'http://localhost:8080/dbwr/view.jsp?display=file:../../xxx.bob', it suggests 'Internal Server Error' and 'Could not initialize class dbwr.parser.WidgetFactory' in detail.

There are two restrictions to file://.. URLs, see https://github.com/ornl-epics/dbwr#client-urls

The file://... URLs are resolved by tomcat, so they have to be in the file system of the server, not on some client computer that's running the web browser
To prevent access to file://etc/passwd and the like, the file:/.. path must be permitted by using the WHITELIST settings

For first tests, use the example displays which are available via http:... from github:
http://localhost:8080/dbwr/view.jsp?display=https://raw.githubusercontent.com/ControlSystemStudio/phoebus/master/app/display/model/src/main/resources/examples/01_main.bob

For first tests, use the example displays which are available via http:... from github:

this gets the same result as the picture above

OK, so the error seems unrelated to the specific display file.
In fact, Could not initialize class dbwr.... suggests that tomcat failed to load the application at all. You may be able to see the view.jsp web page, the basic HTML, but none of the application code works.
When you start tomcat, and/or when you redeploy the dbwr.war file, you should see something like this in the tomcat log:
17-Apr-2023 13:16:36.719 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [/.../apache-tomcat-9.0.73/webapps/dbwr.war]
...
17-Apr-2023 13:16:36.815 INFO [main] dbwr.WebDisplayRepresentation.<clinit> No WHITELIST1 etc., allowing all display links
17-Apr-2023 13:16:36.815 INFO [main] dbwr.WebDisplayRepresentation.contextInitialized ===========================================
17-Apr-2023 13:16:36.815 INFO [main] dbwr.WebDisplayRepresentation.contextInitialized /dbwr started
17-Apr-2023 13:16:36.815 INFO [main] dbwr.WebDisplayRepresentation.contextInitialized ===========================================
17-Apr-2023 13:16:36.816 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [.../apache-tomcat-9.0.73/webapps/dbwr.war] has finished in [97] ms

Instead of such startup messages, I assume you get more Could not initialize class.. errors as the dbwr.war fails to load.
Those messages suggest a basic incompatibility of the dbwr.war binary with the tomcat and/or jdk that you're using.
Could be trying to use tomcat 10+ instead of Tomcat 9, see #12.
Or using a binary that was compiled with a JDK that's newer than what you're using locally.
To avoid such issues, use Tomcat 9 (which I think you already do) and compile from sources, using the same JDK that you're using to run Tomcat.

Thanks, it's another problem of running env version. I switched to jdk19 and still use tomcat9, then re-deployed the project and it works.


How to turn of zoom increase/decrease when scrolling over map

if I scroll from top to down and mouse pointer hits map zoom event is called.
how to turn of zooming and just continue scrolling over map

<GoogleMap
...
  defaultOptions={{
    scrollwheel: false,
  }}
...
/>

that hepled

Please refer to Getting Help section in the README (or #469).


rancher/kubernetes-agent:v0.6.6 does't work

Describe your issue here
Expected state running but got error: Error response from daemon: connection error: desc = "transport: dial unix:///var/run/docker/containerd/docker-containerd.sock: timeout"

Useful
Info

Versions
Rancher v1.6.14 Cattle: v0.183.37 UI: v1.6.37

Access
Disabled

Orchestration
Kubernetes

Route
stack.index

Can you supply more info on your setup (basically copy paste from this and fill in: https://raw.githubusercontent.com/rancher/rancher/master/.github/ISSUE_TEMPLATE.md)
This does sound like either a problem with the Docker daemon, or possible version mismatch?

Please let us know in a comment if you can still reproduce the issue, and we'll reopen it


tflite::MicroProfiler not timing operations correctly

Description
I am trying to profile my model operations running on the coralmicro dev board.
I am injecting a tflite::MicroProfiler into the tflite::MicroInterpreter:
  tflite::MicroProfiler profiler;
  tflite::MicroErrorReporter error_reporter;
  tflite::MicroMutableOpResolver<3> resolver;
  resolver.AddDequantize();
  resolver.AddDetectionPostprocess();
  resolver.AddCustom(kCustomOp, RegisterCustomOp());

  tflite::MicroInterpreter interpreter(tflite::GetModel(model.data()), resolver,
                                       tensor_arena, kTensorArenaSize,
                                       &error_reporter, nullptr,
                                       &profiler // injecting profiler via constructor
);

Then I run inference and print the profiling results:
std::memcpy(tflite::GetTensorData<uint8_t>(input_tensor), image->data(), image->size());
if (interpreter->Invoke() != kTfLiteOk) return false;
*results = tensorflow::GetDetectionResults(interpreter, 0.5, 1);

// logging profile results
profiler.Log();

See below the profiler output. Notice that latency is always 0 ms.
edgetpu-custom-op took 0 ticks (0 ms).
DEQUANTIZE took 0 ticks (0 ms).
DEQUANTIZE took 0 ticks (0 ms).
TFLite_Detection_PostProcess took 0 ticks (0 ms).

It micro_time.h properly implemented for the dev board micro ?
Is there anything else we need to do ( a specific compile flag ? ) to enable profiling ?
Click to expand!
Issue Type
Documentation Feature Request
Operating System
Linux
Coral Device
Dev Board Micro
Other Devices
No response
Programming Language
C++
Relevant Log Output
No response

I was able to get some measurements after using a micro_time.cc implementation.
See: https://github.com/tensorflow/tflite-micro/issues/2120


Platform flag issue

🐛 Bug Report
🤷♀ What did you do
After installing Strapi via the cli tool, then I used your docker cli tool
⛔ Error log
🕵♀ Stack trace
docker-compose up --build

[+] Building 67.3s (14/14) FINISHED
 => [internal] load build definition from Dockerfile                                                                           0.0s
 => => transferring dockerfile: 483B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 86B                                                                                0.0s
 => [internal] load metadata for docker.io/library/node:16-alpine                                                              1.8s
 => [auth] library/node:pull token for registry-1.docker.io                                                                    0.0s
 => [1/8] FROM docker.io/library/node:16-alpine@sha256:b4a72f83f52bbe3970bb74a15e44ec4cf6e873ad4787473dfc8a26f5b4e29dd2        1.4s
 => => resolve docker.io/library/node:16-alpine@sha256:b4a72f83f52bbe3970bb74a15e44ec4cf6e873ad4787473dfc8a26f5b4e29dd2        0.0s
 => => sha256:b6f9bace56ac362c7806f8deeb90f266845dfec935bcdccac803e5daf2f0ef20 36.49MB / 36.49MB                               0.7s
 => => sha256:babb9645c565e97a1a59e05a5a9be53810876a2c2464d1a54027e634152c8149 2.41MB / 2.41MB                                 0.2s
 => => sha256:b4a72f83f52bbe3970bb74a15e44ec4cf6e873ad4787473dfc8a26f5b4e29dd2 1.43kB / 1.43kB                                 0.0s
 => => sha256:0ac2f8cba4274f3aeeb8dd2cde7714fe746b917df68a79eb9b4d5de053c5aa53 1.16kB / 1.16kB                                 0.0s
 => => sha256:5b6b1b14e0516d9de0a964a1e3022e17d517539b3e37082478f7adcaf1e2af95 6.50kB / 6.50kB                                 0.0s
 => => sha256:c41833b44d910632b415cd89a9cdaa4d62c9725dc56c99a7ddadafd6719960f9 3.26MB / 3.26MB                                 0.3s
 => => sha256:014e873a0e36f8b98976f2e7ba1c884d1655cfef237b9bb9c4916bc9acf1557e 449B / 449B                                     0.7s
 => => extracting sha256:c41833b44d910632b415cd89a9cdaa4d62c9725dc56c99a7ddadafd6719960f9                                      0.1s
 => => extracting sha256:b6f9bace56ac362c7806f8deeb90f266845dfec935bcdccac803e5daf2f0ef20                                      0.5s
 => => extracting sha256:babb9645c565e97a1a59e05a5a9be53810876a2c2464d1a54027e634152c8149                                      0.1s
 => => extracting sha256:014e873a0e36f8b98976f2e7ba1c884d1655cfef237b9bb9c4916bc9acf1557e                                      0.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 455.35kB                                                                                0.0s
 => [2/8] RUN apk update && apk add  build-base gcc autoconf automake zlib-dev libpng-dev nasm bash vips-dev                   5.3s
 => [3/8] WORKDIR /opt/                                                                                0.0s
 => [4/8] COPY ./package.json ./yarn.lock ./                                                                                0.0s
 => [5/8] RUN yarn config set network-timeout 600000 -g && yarn install                                                       39.1s
 => [6/8] WORKDIR /opt/app                                                                                0.0s
 => [7/8] COPY ./ .                                                                                0.0s
 => [8/8] RUN yarn build                                                                                13.3s
 => exporting to image                                                                                6.2s
 => => exporting layers                                                                                6.2s
 => => writing image sha256:56a04d197d2f3543fa9b5a1dbfe3262f6e67039e535a594a987b8a4b06c78f7a                                   0.0s
 => => naming to docker.io/library/mystrapi:latest                                                                             0.0s
[+] Running 0/1
 ⠋ Container strapiDB  Creating                                                                                0.0s
Error response from daemon: image with reference postgres:12.0-alpine was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64

## 🙇♀ Expected behavior/code

I used the
`docker-compose up -d
`
and it gave me the same error, what am I doing wrong? I have not changed anything in the docker compose file, specially the platform data.
Just building the docker file with `docker build --platform linux/amd64  .` created the image
And running the docker file with `docker run 200e7c496425 --platform linux/amd64  .`  gave me the following error: WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8)
## 👩💻 Environment

- 📦 Node version: v18.15.0
- 💻 OS:  macOS 13.3.1 (22E261)
-CPU: Apple M1 Max

## 💡 Possible Solution

<!-- Only if you have suggestions on a fix for the bug -->

## 📺 Additional context/Screenshots

<!-- Add any other context about the problem here. If applicable, add screenshots to help explain. -->

Error response from daemon: image with reference postgres:12.0-alpine was found but does not match the specified platform: wanted linux/amd64, actual: linux/arm64

So might be worth check the compose file
It seems you might need to adjust the compose file ☺

I changed the image to run:

image: postgres:12.0

and that seems to make it work :)

Glad to hear it works fine :) Will close the issue then.


Update zio, zio-streams, zio-test, ... to 2.0.14

Updates

dev.zio:zio
dev.zio:zio-streams
dev.zio:zio-test
dev.zio:zio-test-sbt

from 2.0.13 to 2.0.14.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #497.


[3.x] Added alignment options to icons on buttons. They can now be centered and right-aligned.

Backport of #37181 to 3.x.
I recreated the image from https://github.com/godotengine/godot/issues/11380#issuecomment-546186548 to test it:

Thanks!

Thanks for taking care of this!  Got busy with a rapidly-approaching deadline. 😅


Self Signed Registry - X509: certificate signed by unknown authority Error

So I just started started using microk8s today, but I have been developing in DCOS and Kubernetes for years now.  We have a development docker registry on our network that is self signed running on https with no proxy.  I cannot figure out how to properly configure microK8s to talk to this registry.   (I have another kubernetes cluster that is working just fine not microk8s)
The machine is an Ubuntu linux server with microk8s installed through snap.  I installed docker through snap also.  On the same machine docker is talking to the registry just fine and can pull an image from the registry.   In docker I do not need the insecure_skip_verify since I have the crt file. But I tried adding it to the containerd config just to see if it would work.
Attached is the microk8s inspect that you asked for.  Below is my containerd-template.toml section for the registry.  Hopefully someone can tell me what I am doing wrong.  I have been reading every article on the internet that I could find to fix this issue but nothing seems to be working.  I have tried both DNS name and IP address for the registry.
[plugins.cri.registry]
  [plugins.cri.registry.mirrors]
    [plugins.cri.registry.mirrors."docker.io"]
      endpoint = ["https://registry-1.docker.io"]
    [plugins.cri.registry.mirrors."localhost:32000"]
      endpoint = ["http://localhost:32000"]
    [plugins.cri.registry.mirrors."bootstrap.day.dbresearch.net:5000"]
      endpoint = ["https://bootstrap.day.dbresearch.net:5000"]

  [plugins.cri.registry.configs."bootstrap.day.dbresearch.net:5000".tls]
    insecure_skip_verify = true
    ca_file = "/var/snap/microk8s/current/certs/bootstrap-registry.crt"

inspection-report-20200617_193458.tar.gz

The insecure_skip_verify was added from containerd 1.3.
The upgrade to containerd 1.3.4 was recently merged.
@ktsakalozos which channel should have the latest containerd, maybe @kstedman9  can give that a try.

@balchua Thank you for the heads up.  I see where you did the merge but SNAP does not show a channel with that yet.  So it sounds like for the short term to get what I need to work is to just create a simple http -> https proxy around my registry unless that channel is going to show up today.

Usually it gets to the latest/stable within a day.  If not, you can try the channel edge.
But edge channel is not for prod use at all.

@balchua  I just just updated to the latest/edge version which was updated with yesterday's date and everything seems to be working now.  Thank you.
This is only for development and test, so at this point I do not care if we are on edge.

@kstedman9 great to hear that. I will be closing this issue. If there are other issues feel free to file a new one.
Thanks!


Dynamic change max and min

Hello, can I change the max and min value after initializing?

I found that can be done just by changing the value of original input.


Formalize fields in client/public/locales/en for translators

Could anyone work on labeling all of the fields in client/public/locales/en in a formalized way? @akilhylton has done some great work to set up .json files and the react module for integrating the translations, but if there is a set format and identifiers for each section of text, it will make it a lot easier for the translations team to give you the corresponding text! I'd say you can message myself, @akilhylton , and/or @AdhamAH  if you have any questions about it!

@salvolpe here's a rough first draft of what I would propose for the format of what would be delivered back to the translation team. Each screen in the wireframe would be titled in all caps then fields would map to the json/react syntax based on @liadove's original work. This is just a draft to make sure it's heading on the correct path. Your feedback, @SomeMoosery, @akilhylton and @AdhamAH feedback and agreement would be needed before I get this started.
translationfieldsdraft.txt

Note: this draft only includes the Log In and Disclaimer screens on https://github.com/COVID-19-electronic-health-system/Corona-tracker/blob/master/design/wireframes/FINAL-V1-03.28/MASTER_WIREFRAME_reduced.png

@johnemurphy1 I think this looks great and would be readable to the translators!

@johnemurphy1 are you working on this?

Yes, I am working on it.
On Fri, Apr 10, 2020, 10:44 PM Carter Klein<EMAIL_ADDRESS>wrote:

@johnemurphy1 https://github.com/johnemurphy1 are you working on this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/COVID-19-electronic-health-system/Corona-tracker/issues/359#issuecomment-612304541,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF72DUZDYFOXJXMCCTQECUDRL7KSPANCNFSM4L2UV4VA
.

Hi all, this is the translation JSON file that I created per this issue. After a discussion with Sal and Austin, the questions center around what questions have to be included in the launch version and/or could be added (or deleted) later based on @ngiangre 's analytics and/or other parties contributing on various components. Please review attached and comment.
translationsFormatted.txt

looks like this closes this https://github.com/COVID-19-electronic-health-system/Corona-tracker/blob/master/Translations/appText.json closes this issue...credit to @BrianHHough

Awesome! I can close this one. Feel free to edit this file in case there are any bugs/needed edits, but all the text is there and organized for the app as of today: https://github.com/COVID-19-electronic-health-system/Corona-tracker/blob/master/Translations/appText.json
Go team! 🎉

Reopening this - we need more active communication for what's going on here.
How does this ticket pertain to #643 - should we close this as another ticket has been made "on top" of it? Or can these be paralellized and John can continue to work on this while Brian continues to work on something else

#643 is very similar/the same as this issue. I think it was a miscommunication - sorry about circumnavigating the PR process - we'll talk to @BrianHHough

No worries at all!

closing in lieu of #643


[bazel/ci] build all sw with bazel

replace the sw/build step with a bazel invocation and a few copy
commands to place the mask rom appropriately in the archive and
preserve the rest of the built artifacts in the archive.
Fixes #12696
Signed-off-by: Drew Macrae<EMAIL_ADDRESS>

I'm moving it to
  pool:
    vmImage: ubuntu-18.04

where I expect better performance


"Unenroll"

Describe the bug
In some courses there is no "Unenroll"-Button making leaving them when u e. g. joined accidentally impossilble
To Reproduce
.
Expected behavior
Being able to leave Courses
Screenshots

Which version of Artemis are you seeing the problem on?
most recent
What browsers are you seeing the problem on?
Safari
Additional context
No response
Relevant log output
No response

This is not a bug. The instructors can specify an unenrolment period, during which unenrollment is possible and the button is shown. If the button is not shown, this means that the Instructor set up the course such that unenrolment is currently not possible.


how to do early stopping while training adanet

When using adanet on my own data,I face a overfitting problem. I have to try to add early stopping strategy while training adanet.My problem is early stopping strategy stop the adanet iteration.So How can I do early stopping in each iteration so that I can solve the overfitting problem.
1.I set 8 iterations,each iteration has 200000 step
2.The whole training stop at 160000 step in first iteration,

@guoqingyu319: We don't yet support early stopping per iteration, though it's something we would like to add. For now, the best thing is to set the max_iteration_steps to the right number to prevent overfitting (though sometime a little overfitting is good for the ensemble performance).

@cweill thanks a lot.In our scenario,we wanna use adanet to do automl.The biggest problem is some hyperparameters in adanet such as max_iteration_steps can not be automated completly.Different datasets have different max_iteration_steps we need.So the right number you said is also a parameter we should try.Thank you so much!

@guoqingyu319 What we generally do is tune the train steps (i.e. number of epochs) to find the best AdaNet model.


Remove static string literals from visitors

This pull request removes all static string literals that would ordinarily be duped for no reason from visitor methods.
I've also added a test case to ensure that no static string literals are ever put in visitor method bodies in future.
cc @fxn

Was about to embark on this journey myself, wondering why it hadn't been done yet, and voila, it has.
Why is it not merged?

@charliesome can you rebase and I'll merge?

Going to close in favor of having the file directive for this.


Async processes with pidfd

See https://github.com/pop-os/pidfd
Enables async process management by providing a unique file descriptor which can be epoll'd for its exit. The libc::waitid` syscall may be used on a pidfd after it has exited to retrieve the exit status. Only supports Linux.

This has been implemented in https://github.com/joshtriplett/async-pidfd


add a new config to a standalone spark master

I am terrible at naming, so please suggest a better name for the config.

@drcrallen could you review this PR?

Launched test: http://aws-mgmt-jenkins-master.metamx-mgmt.com:8080/view/Backend/job/spark-test/35/

Cool, add docs as well please

@drcrallen added the config to the doc. the test took 1 hour 45 minutes 😮

it has failures: http://aws-mgmt-jenkins-master.metamx-mgmt.com:8080/view/Backend/job/spark-test/36/ can you please check and see if those are related to this?
Yes, spark tests take a long time.

@jisookim0513 for example: http://aws-mgmt-jenkins-master.metamx-mgmt.com:8080/view/Backend/job/spark-test/36/org.apache.spark$spark-core_2.11/testReport/org.apache.spark.deploy/StandaloneDynamicAllocationSuite/

http://aws-mgmt-jenkins-master.metamx-mgmt.com:8080/view/Backend/job/spark-test/36/org.apache.spark$spark-core_2.11/testReport/org.apache.spark.deploy/StandaloneDynamicAllocationSuite/dynamic_allocation_with_cores_per_executor/

@drcrallen I changed the sorting from sorting by a number of free cores to sorting by percentage because we use different instance types with a different number of cores. Sorting by a number of free cores will always assign Spark applications to smaller instances first.

Launched a test: http://aws-mgmt-jenkins-master.metamx-mgmt.com:8080/view/Backend/job/spark-test/42/

forgot about this. sorry. will review early next week. please remind me

👍  but can you resubmit this to https://github.com/metamx/spark/tree/branch-2.0-mmx ?

closing this since we no longer use standalone master


doc: native_posix: Add section about subsystems' backends

Add section to describe a bit the currently available subsystems'
backends for native_posix
Signed-off-by: Alberto Escolar Piedras<EMAIL_ADDRESS>

Codecov Report

Merging #13103 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #13103   +/-   ##
=======================================
  Coverage   48.62%   48.62%
=======================================
  Files         313      313
  Lines       46484    46484
  Branches    10728    10728
=======================================
  Hits        22604    22604
  Misses      19413    19413
  Partials     4467     4467

Continue to review full report at Codecov.

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

@dbkinder : Thanks for the review!


Strict differentiation of predefined and custom buildings

This issue emerged after a private discussion with @StingMcRay on discord according to issue #105.
We came to the conclusion that there is a need for a strict(er) differentiation of buildings from the presets file and custom buildings created by the user that are not in the presets file.
The intention of the logic used in issue #105 was to check if a building with the same settings that the user made (icon and size) is found in the presets file and "map" the custom building to a predefined one.
This is somewhat hacky and not very transparent to the user.
So the following idea emerged:
If a building from the presets file is selected (via TreeView) then there will be a green border around the building settings.
If the user "created" a custom building then there will be an orange border.
Maybe a checkbox or something where the user "accepts" the automatic conversion.
The use of different borders would make it more transparent to the user that the building configuration is not in the presets file.
Also to avoid countless "Unknown Building" entries in the statistics the label entered by the user could be used.
This is a quick mockup:

So the next thing is to define which setting should be used to find a building in the presets file.
Continue to use the current logic of same icon and same size (rotation doesn't matter) or use some other logic?
Please share your opinions! It is an open discusison.

This Issue was addressed in Anno Designer version 9 i believe, however it is not mentioned, but will fixed now in PR #356
The only way an "Unknown Object" in statistics screen is showed, if the user make a building at start and not name it on the label text box.
Name change can be done, on known buildings and own creation without selected a preset tree building, as long users fill in the Label, however those buildings will never be translated for others, as they are not part of the preset list.

The root problem for opening this issue might be solved, but the idea of this PR is still not solved.
Currently (and also after PR #356) there is no way for a user to know if a building is from the presets or a custom building.

I know, we need to dive in deeper in this matter... i have some ideas but need to work that out on my mind first


line.interpolate("cardinal") in version 4

In version 3 I have this section of code:
var loopFunction = d3.svg.line ()
.x (function (d) {
return d.x;
})
.y (function (d) {
return d.y
})
.interpolate ("cardinal")
.tension (-1);

In version 4 I modified to:
var loopFunction = d3.line ()
.x (function (d) {
return d.x;
})
.y (function (d) {
return d.y
})
.curve (d3.curveCardinal.tension (-1));

When I call the method loopFunction passed a parameter:
[{"x": 70.31797611050145, "y":<PHONE_NUMBER>27101}, {"index": 88, "x":<PHONE_NUMBER>0110291, "y":<PHONE_NUMBER>855732, "vy": 0.0019068901105323065 , "Vx": - 0.00017607654513037712}, {"x": 57.84059504012937, "y":<PHONE_NUMBER>1082347}]
The results in version 3 are:
"M70.31797611050145,<PHONE_NUMBER>27101Q122.35294204801762,254.3978668964249,114.03468800110291,273.2449708855732Q105.71643395418819,292.0920748747215,57.84059504012937,265.33225751082347"
But the result in version 4 is:
"M70.31797611050145,237.061601527101C70.31797611050145,237.061601527101,118.19381502456027,263.82141889099904,114.03468800110291,273.2449708855732C109.87556097764555,282.66852288014735,57.84059504012937,265.33225751082347,57.84059504012937,265.33225751082347"
I would like to get version 3 in the version of the results of how to write?

Per the Release Notes, the interpretation of Cardinal spline tension was fixed in 4.0:

4.0 fixes the interpretation of the cardinal spline tension parameter, which is now specified as cardinal.tension and defaults to zero for a uniform Catmull–Rom spline; a tension of one produces a linear curve.

Tension should typically specified in the range [0,1], so even with the broken interpretation used by 3.x, a tension of -1 is a bit unusual. It looks like you can approximate your old result using a tension of about -3.5.
https://bl.ocks.org/mbostock/58d4fa2e26c0ec32197c27d4cef837e2
An exact match for the interior segments of the spline would be a new tension value of -5, because the length of the tangents was changed from (1 - tension) / 2 to  (1 - tension) / 6: (1 - -1) / 2 = 1 = (1 - -5) / 6.
However, v4 also fixed the first and last segment of Cardinal splines; in v3 Cardinal splines used a quadratic Bézier for the first and last segment, which… well, which didn’t really make sense, and so there’s no equivalent.

The effect is almost, but the arrow can not follow the change?

@mbostock  The effect is almost, but the arrow can not follow the change?

Sorry, I don’t understand the question.
Please use Stack Overflow tag d3.js to ask for help. Although I make an effort to assist everyone that asks, I am not always available to provide help promptly or directly. Stack Overflow provides a better collaborative forum for self-help: tens of thousands of D3-related questions have already been asked there, and some answered questions may be relevant to you.
If you have a question about D3’s behavior and want to discuss it with other users, also consider the d3-js Google Group or joining the d3-js Slack.
Thank you! 🤗


Mercy DMG Boost

Created by: DpsDoomMain
Mercy’s damage boost should be at 30% currently it’s at 25%

Created by: MaxwellJung
Not sure if this is possible. There's currently no way to check who's getting damage boosted by mercy in workshop.

moved from ow1_emulator_backup#655

moved to ow1_emulator#79

Created by: DpsDoomMain
Question can you see who she has healing beam on?


Add support for mLineIndex, fix ice candidate pair failure terminating entire connection

Fixes https://github.com/shinyoshiaki/werift-webrtc/issues/208
Adds support for ice candidate mLineIndex.

I'm seeing this test timeout failure even without my changes.

I'm seeing this test timeout failure even without my changes.

Is the test that fails "test_connect_close"?
This test should be renamed to "should fail when connecting to a closed connection" for clarity.
With this change, the test no longer passes because it now takes longer for the connection to fail completely.
So, don't worry about the test failing itself.


🔧: add tool config

maybe also install the related deps?

[coverage] and [tool.pytest] have deps already in [dependency-groups].
ruff will be managed by pre-commit, which I've now added to [dependency-group]. We need to make the pre-commit yaml next (new PR).
mypy and the other static checkers we need to figure out. We could do mypy in pre-commit, or as a different step in the CI.

Ok. Style should be much more consistent. I removed the alignments and spacing styles.