feat: Added new colors to the palette file

Description
The palette.dart file contains just five colors, I have added 20 new colors and the colors are in alphabetical order.

Checklist

[x] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[x] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

Breaking Change

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Related Issues

By the way, you don't need to close your old PR and open a new one whenever you are making a change. Just run git push from the command line, and the changes will get submitted into your PR.

By the way, you don't need to close your old PR and open a new one whenever you are making a change. Just run git push from the command line, and the changes will get submitted into your PR.

Got it!


Update composer.json

When upgrading swiss-payment-slip/swiss-payment-slip-fpdf with composer, it will not upgrade dependencies, because of this line. please change and release new version. thanks for your effort on this library!

Would that really solve it?

For pre-1.0 versions it also acts with safety in mind and treats ^0.3 as >=0.3.0 <0.4.0.

https://getcomposer.org/doc/articles/versions.md#caret
I guess, I need to bump the dependency, like for the TCPDF variant:

You're right, I didnt know that composer threats 0.* versions different from SemVer... 😞
So I guess its like you said: Bump it like you did on Tcpdf or what I would suggest: Tag all your releases now with a Version 1.0.0 and use ^1.0.0 on all dependencies then.


[PT Run] [Windows Settings] Add context menu Run as admin

Summary of the Pull Request
What is this about:
Adding a context menu entry to run settings as admin.

What is include in the PR:
Adding a context menu entry to run settings as admin.
This entry is only shown entries that doesn't open the modern settings app.
How does someone test / validate:
⚠Not done yet!
Quality Checklist

[x] Linked issue: #13742
[x] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[x] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

Should we show the context menu entry for all supported entries or only on settings where we need it (new json property)?

I think we should show this for each setting
Pros:

Don't confuse users (why can't I open this via admin?)
No extra maintenance needed for future settings changes (before without admin, later only with admin)
No extra key in the JSON

Should we show the context menu entry for all supported entries or only on settings where we need it (new json property)?

I think we should show this for each setting
Pros:

Don't confuse users (why can't I open this via admin?)
No extra maintenance needed for future settings changes (before without admin, later only with admin)
No extra key in the JSON

Please see discussion in issue too.

As discussed in the issues this won't be implemented because there is no must have reason for this feature.


Chrome drive error

Can i know what's the issue ?
Here the error log
Fatal error: Uncaught Facebook\WebDriver\Exception\UnknownErrorException: unknown error: Chrome failed to start: was killed. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location C:\laragon\www\js\vendor\bhittani\web-driver\drivers\chrome.exe is no longer running, so ChromeDriver is assuming that Chrome has crashed.) in C:\laragon\www\js\vendor\php-webdriver\webdriver\lib\Exception\WebDriverException.php:139 Stack trace: #0 C:\laragon\www\js\vendor\php-webdriver\webdriver\lib\Remote\HttpCommandExecutor.php(371): Facebook\WebDriver\Exception\WebDriverException::throwException('unknown error', 'unknown error: ...', Array) #1 C:\laragon\www\js\vendor\php-webdriver\webdriver\lib\Remote\RemoteWebDriver.php(135): Facebook\WebDriver\Remote\HttpCommandExecutor->execute(Object(Facebook\WebDriver\Remote\WebDriverCommand)) #2 C:\laragon\www\js\vendor\bhittani\web-driver\src\Maker.php(61): Facebook\WebDriver\Remote\RemoteWebDriver::create('http://localhos...', Object(Facebook\WebDriver\R in C:\laragon\www\js\vendor\bhittani\web-driver\src\Maker.php on line 85

Please use the issue template to report issues.
Note: This package is still in development.
As far as your issue with the chrome driver, try using the phantomjs driver and let me know if that works.

Phantomjs working well, only chrome error getting

Do you have a chrome browser installed on your OS? The chrome driver requires a chrome browser installation.

Yes, iam using another framework https://github.com/chrome-php/chrome and
it working well
On Wed, Jun 23, 2021, 6:06 PM Kamal Khan @.***> wrote:

Do you have a chrome browser installed on your OS? The chrome driver
requires a chrome browser installation.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kamalkhan/web-browser/issues/1#issuecomment-866797552,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIXOM4IQHPQNMR4DCARWZ23TUHILZANCNFSM47DHEHKQ
.

Here the bin path of both drivers
Chrome
http://<IP_ADDRESS>/web/vendor/bhittani/web-driver/drivers/chrome.exe
Phantomjs
http://<IP_ADDRESS>/web/vendor/bhittani/web-driver/drivers/phantomjs.exe

This might be an issue with the background process being used.
I will try to debug this when I start working on it.

Ok, thanks.
On Wed, Jun 23, 2021, 6:23 PM Kamal Khan @.***> wrote:

This might be an issue with the background process being used.
I will try to debug this when I start working on it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kamalkhan/web-browser/issues/1#issuecomment-866809018,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIXOM4LAARSXCANWKAGCT7TTUHKMLANCNFSM47DHEHKQ
.


Feature add facebook instagram oembed v11 support

Thanks for contributing to Wagtail! 🎉
Before submitting, please review the contributor guidelines https://docs.wagtail.io/en/latest/contributing/index.html and check the following:

Do the tests still pass? (https://docs.wagtail.io/en/latest/contributing/developing.html#testing)
Yes
Does the code comply with the style guide? (Run make lint from the Wagtail root)
Yes
For Python changes: Have you added tests to cover the new/fixed behaviour?
Yes - I adjust existing tests.
For front-end changes: Did you test on all of Wagtail’s supported environments?

Please list the exact browser and operating system versions you tested.
Please list which assistive technologies you tested.

For new features: Has the documentation been updated accordingly?
I checked the docs and I think the existing documentation in /docs/embeds.rst is sufficient.

For reference: https://developers.facebook.com/docs/graph-api/changelog/version11.0/#oembed
Also, according to https://developers.facebook.com/docs/graph-api/changelog/version9.0 v9 will be supported until the beginning of 2023

For reference: https://developers.facebook.com/docs/graph-api/changelog/version11.0/#oembed
Also, according to https://developers.facebook.com/docs/graph-api/changelog/version9.0 v9 will be supported until the beginning of 2023

@zerolab Thanks for the hint. We started working on this PR because we thought that as of 7. September 2021 one has to use a Facebook app that has been reviewed AND one has to use the v11 api version. After your comment we started to discuss internally on how to interpret the  change log and it seems that one just has to use a reviewed Facebook app, but can continue to use the v9 api version until 2023.
So it is probably not urgent to merge this PR 😅

oEmbed Read

Applies to all versions.

As far as I can tell, the difference after September is that you need to enable "oEmbed Read" in the registered Facebook app (and I suppose complete the app review step).
This PR still makes sense, but as you say, not an urgent one

So, if I'm understanding correctly:

Anyone who set up the old oEmbed product before June 8, 2021 can continue using it for now, but needs to switch to the oEmbed Read feature (which requires app review) before September 7, 2021.
Anyone setting up oEmbed right now is supposed to use the oEmbed Read feature. (The message on https://developers.facebook.com/docs/plugins/oembed implies that the old oEmbed product is unavailable to new apps created after June 8, 2021, although it doesn't say so outright...)
The above is true regardless of whether you're using the v9.0 or v11.0 URL endpoints.

It would be worth double-checking that last point, I think. @cnk - am I right in thinking that you have an existing site set up using the pre-June-2021 oEmbed product, that hasn't gone through Facebook app review? If so, please could you check whether it still works with the URL endpoint changed to v11.0?
If that does work, then it looks like there's no reason not to go ahead and merge this now. If it doesn't work, we should hold off on merging it until after September (by which time Facebook will have forced everyone to switch to the new oEmbed Read feature).
Either way, it sounds like the mention of September 2021 in the docs here should be fixed (=> as of June 2021 for new apps, and September 2021 for existing ones), and it would also be a good idea to add a note about the Facebook policy change in the 2.14 release notes. (While that change isn't tied to any code changes on the Wagtail side or any particular Wagtail upgrade, it's something that developers will need to know about.)

Unfortunately I only had a Facebook/Instagram app for testing the Wagtail embed code. Since I haven't been using it, it expired and now I will need to verify my identity before being able to use it. As part of that verification process, FB is automatically upgrading me to v 11. So sorry. No testing help here.

@gasman We have one "old" Facebook/Instagram app. Unfortunately it has not the old oEmbed product activated, and the old oEmbed product is also not available for selection.
When using the credentials of this app to fetch the embed code, we get the following response:
{
	"error": {
		"message": "(#10) To use 'Oembed Read', your use of this endpoint must be reviewed and approved by Facebook. To submit this 'Oembed Read' feature for review please read our documentation on reviewable features: https://developers.facebook.com/docs/apps/review.",
		"type": 'OAuthException',
		"code": 10,
		'fbtrace_id': 'xxx'
	}
}

The response is the same for the api endpoints v9.0 and v11.0.
So I would say that it is safe to say that for the time being Facebooks oembed permission handling is independent from whether one is using the v9.0 or the v11 api endpoint.
So I think the comment from @zerolab is still true.

As far as I can tell, the difference after September is that you need to enable "oEmbed Read" in the registered Facebook app (and I suppose complete the app review step).
This PR still makes sense, but as you say, not an urgent one

@gasman I updated the docs in this commit.
I hope you are fine with the changes.

the oEmbed Read feature and review their app until September 7, 2021.

@tkremmel do you mean "until"? I think you mean:
Apps that activated the oEmbed Product before June 8, 2021 need to activate the oEmbed Read feature and submit their app for review before September 7, 2021.

@cnk You are absolutely right. English is - as easily detectable - not my mother tongue. Thanks for the correction! Fixed in this commit.

Thanks @tkremmel! Merged in be857cc5e98a73023249198b98fe54838ed9397c , with upgrade consideration note added to the 2.14 release notes.


Wrap with span, not div.

Previously, there was an implicit DIV when using an html or md tagged template literal that returns more than one node. For example:
html`Hello, <i>world</i>!`

This implicit DIV is weird if you’re embedding the HTML inside something else (rather than as a top-level cell value); it’s better to use a container that doesn’t affect the content layout, hence SPAN.
Fixes #73.

Are you saying that DIV with display: block is the right approach? Or is there another element with display: inline that we should use instead?

I'm saying that technically, a <div> is the appropriate semantically meaningless element to wrap "flow content" like paragraphs ... but that in practice, since we don't know whether you intend to render inline content or block content, this change to a <span> is probably the best approach — despite not validating as HTML5.


add abs and sign

I have three small points to discuss.
First, an observation about error messages: one point of difficulty is the use of numerals. For example, in the algebra library, if a theorem with "0" has an error anywhere, it is likely to be blamed on the zero ("type holder in placeholder assigned to ... none of the overloads is applicable").
This is just an instance of the usual problem with overloads and choices. One workaround it to use algebra.zero or something like that. But I thought I would mention it in case you (Leo) can think of another clever workaround.
Second, something funny is happening with numerals and substitution. E.g. here:
https://github.com/avigad/lean/blob/master/library/algebra/ring.lean#L202
we cannot use "(one_mul a)^⁻¹" or even "{(one_mul a)^⁻¹}", and here:
https://github.com/avigad/lean/blob/master/library/algebra/ordered_ring.lean#L366
we cannot get rid of the {}. The workarounds are easy, and I realize that it is a complicated example: it combines higher-order unification, type class inference, and insertion of a coercion.
Finally, the heuristic for "a = b : t" where we try t, t⁻¹, {t}, {t⁻¹} only seems to work when t is a single identifier, not a compound term. Is this intended? Is there any reason not to do it for compound terms as well? For example, it would let us write
sign_of_pos H1
instead of
{(sign_of_pos H1)⁻¹}
here:
https://github.com/avigad/lean/blob/master/library/algebra/ordered_ring.lean#L362
There are lots of examples of this in that file.

First, an observation about error messages: one point of difficulty is the use of numerals. For example, in the algebra library, if a theorem with "0" has an error anywhere, it is likely to be blamed on the zero ("type holder in placeholder assigned to ... none of the overloads is applicable").

I see the problem. The point is that the numerals have a default interpretation (type num).
When we define a notation for a specific numeral, we are overloading it.
We could add an option to disable the default interpretation for numerals.
Then, in the algebra files, 0 would have only one interpretation.
What do you think?

Yes, I think that would help a lot, and it seems like a reasonable thing to
do.
In general (not just for numerals), is there a way to disable a notation?
On Wed, Jan 21, 2015 at 4:57 PM, Leonardo de Moura<EMAIL_ADDRESS>
wrote:

First, an observation about error messages: one point of difficulty is the
use of numerals. For example, in the algebra library, if a theorem with "0"
has an error anywhere, it is likely to be blamed on the zero ("type holder
in placeholder assigned to ... none of the overloads is applicable").
I see the problem. The point is that the numerals have a default
interpretation (type num).
When we define a notation for a specific numeral, we are overloading it.
We could add an option to disable the default interpretation for numerals.
Then, in the algebra files, 0 would have only one interpretation.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-70929977.

we cannot get rid of the {}

I changed how the "calc assistant" works.
When, we write calc lhs = rhs : pr. The "calc assistant" first decides whether a ! needs to be used or not (this is cheap). Then, it tries in sequence the following interpretations: pr, pr⁻¹, {pr}, {pr⁻¹}.
The problem is that in some cases, the right choice is {pr⁻¹}, but it takes a really long time to realize that there is no way to elaborate {pr}. The problem is due to the interaction of computation + higher-order unification (and missing information).
To minimize the problem, the unifier has a "conservative" mode, where only constants marked as reducible are unfolded, other expensive cases are also omitted. Now, the calc assistant uses the conservative mode when processing {pr} and {pr⁻¹}. The idea is that the "calc assistant" covers the simple cases.
When the user writes {pr}, the calc assistant is not being used, and the option "conservative" is not used unless the user have executed
set_option unifier.conservative true

You may ask why this affects an example such as neg_zero. The issue in this example is that neg_zero has an implicit argument (the structure). The argument is filled automatically using class-instance resolution. The automatically generated instances are marked as reducible, but the ones, you defined, are not. Thus, the unification problem cannot be solved because we cannot establish that the 0 in the neg_zero theorem is definitionally equal to the 0 in the theorem you are trying to prove.

In general (not just for numerals), is there a way to disable a notation?

Not really. We don't have names for notation.
So, one option is to provide a command that disables notation containing a user provided token.
Example
notation [disable] +

would disable any notation declaration containing the token +.

Thanks for the explanation of the changes to the calc assistant. They seem perfectly reasonable. The workarounds are easy, and it helps to have a sense of when they are needed.
Just to make sure I understand: in this example,
https://github.com/avigad/lean/blob/master/library/algebra/ring.lean#L202
I just confirmed that we cannot use {(one_mul a)⁻¹}. Is that expected? I thought you said that when you give the substitution explicitly, it is not in conservative mode.

notation [disable] + is a partial solution. Usually, we want to enable one notation when it conflicts with another. A workaround is to disable all of them and then re-declare (either manually or with "open") the one you want.
I think better management for notation should be low priority, something to think about on a rainy day.

I just confirmed that we cannot use {(one_mul a)⁻¹}. Is that expected? I thought you said that when you give the substitution explicitly, it is not in conservative mode.

The conservative mode is not use. Note that {(one_mul a)⁻¹} operationally equivalent to one_mul a ▸ rfl. The latter is executed by the calc assistant. Moreover, the calc assistant is only activated after the equation has been elaborated.

notation [disable] + is a partial solution. Usually, we want to enable one notation when it conflicts with another. A workaround is to disable all of them and then re-declare (either manually or with "open") the one you want.
I think better management for notation should be low priority, something to think about on a rainy day.

Perhaps, we should allow the user to provide names to notations.
Another possibility, we specify a constant symbol. Example
notation [disable] algebra.mul

would disable any notation whose interpretation uses the constant algebra.mul.

Hmm... I tend to favor the second option, I think. It seems easier for you to implement. For the user, it is more work to name notations, and then to remember the name of a notation. It is usually easy to guess the name of a constant.
The only downside I can think of is when we have multiple notations that mention the same symbol, like
notation a ** b := a * b * a
Then notation [disable] algebra.mul would turn that off, too. If it is a problem we can fix it by introducing a definition for a * b * a.
Alternatives are to have variants of the command that disable notation whose head symbol matches "foo", or a command disable notation that exactly matches a term "t", etc.
It probably makes the most sense to start with the simple solution you described, and wait and see if anyone ever wants more than that.
I understand the issue with calculations now.

I added the missing [reducible]s, and the problems were solved.
https://github.com/leanprover/lean/commit/ae7b5a9bc916ea31397e5e7cac1d31815baa5aff
BTW, it would be nice to have a shortcut for
[instance] [coercion] [reducible]

Wonderful!
By the way, should we use the same tags for concrete instance? For example,
in data.int.basic we have
protected definition integral_domain [instance] : algebra.integral_domain
int := ...
Should that have [coercion] and [reducible] too?
How about having an instance command?
instance foo : bar := ...
could be shorthand for
definition foo [instance] [coercion] [reducible] : bar := ...
On Wed, Jan 21, 2015 at 7:27 PM, Leonardo de Moura<EMAIL_ADDRESS>
wrote:

Closed #403 https://github.com/leanprover/lean/pull/403.
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#event-222724559.

Should that have [coercion] and [reducible] too?

I think so. For example, the [reducible] will be needed whenever we try a step such as
          calc    lhs = rhs :  {pr}

where pr is built using a theorem from algebra, and lhs and rhs are terms of the concrete structure.
The unifier will need to establish that constants (*, 0) from the concrete structure are definitionally equal to terms such as has_mul.mul ....

How about having an instance command?
instance foo : bar := ...

I thought about that too. The problem is that we already have a command instance.
instance foo
instance [persistent] foo

Good point. Maybe "structure instance" for the three of them?
definition foo [structure instance] : bar :=
and
structure instance foo
I don't love it, though.
Another thought is that maybe it would be clearer to have a uniform way of
declaring attributes, like
declare foo [instance]
declare foo [coercion]
declare foo [coercion] [instance]
declare foo [reducible]
rather than "instance foo" and "coercion foo". We could use
persistent declaration foo [instance]
for the persistent version. But this would be more work for you, and we
would have to change things all over the library.
On Thu, Jan 22, 2015 at 11:22 AM, Leonardo de Moura <
<EMAIL_ADDRESS>wrote:

How about having an instance command?
instance foo : bar := ...
I thought about that too. The problem is that we already have a command
instance.
instance foo
instance [persistent] foo
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-71047696.

I think [structure instance] looks good.

Another thought is that maybe it would be clearer to have a uniform way of
declaring attributes, like

I think this is a really good idea.
However, the name declaration may give the impression we are declaring something.
What about set_attribute or attribute?
persistent set_attribute looks weird. I think persistent attribute is nice.
What do you think?

I like "attribute" and "persistent attribute". We can get in the habit of
calling the things in brackets "attributes".
On Thu, Jan 22, 2015 at 9:21 PM, Leonardo de Moura<EMAIL_ADDRESS>
wrote:

I think [structure instance] looks good.
Another thought is that maybe it would be clearer to have a uniform way of
declaring attributes, like
I think this is a really good idea.
However, the name declaration may give the impression we are declaring
something.
What about set_attribute or attribute?
persistent set_attribute looks weird. I think persistent attribute is
nice.
What do you think?
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-71137627.

Great!
I will make the changes...

Hmm... I wonder, do we need something like
set attribute foo [coercion]
clear attribute foo [coercion]
?
On Thu, Jan 22, 2015 at 9:34 PM, Leonardo de Moura<EMAIL_ADDRESS>
wrote:

Great!
I will make the changes...
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-71138632.

It would be useful to have a clear_attribute command.
However, there are some issues:

What would be the meaning of clear persistent attribute? I think this would create problems.
Some attributes are not easy to "clear". Coercion is an example. We maintain the transitive closure of the coercion graph.
Some clear commands would affect other attributes. For example: clear attribute inhabited [class], must also "clear" all instance attributes. That is, if a declaration D has an [instance] attribute, and D is an instance of inhabited, then this [instance] attribute must also be cleared.

I think there are more problems, I just list the first problems that came to my mind.

Very good point. It is not worth the effort. These issues are best handled
using namespaces and sections.
On Fri, Jan 23, 2015 at 12:22 PM, Leonardo de Moura <
<EMAIL_ADDRESS>wrote:

It would be useful to have a clear_attribute command.
However, there are some issues:

What would be the meaning of clear persistent attribute? I think
this would create problems.
Some attributes are not easy to "clear". Coercion is an example. We
maintain the transitive closure of the coercion graph.
Some clear commands would affect other attributes. For example: clear
attribute inhabited [class], must also "clear" all instance
attributes. That is, if a declaration D has an [instance] attribute,
and D is an instance of inhabited, then this [instance] attribute must
also be cleared.

I think there are more problems, I just list the first problems that came
to my mind.
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-71229192.

I realized that it makes no sense to declare
protected definition integral_domain [instance] :

algebra.integral_domain int := ...
a [coercion], because it is not a function. But I will make it reducible,
and similarly for the other instances in nat and int.
On Fri, Jan 23, 2015 at 9:38 PM, Jeremy Avigad<EMAIL_ADDRESS>wrote:

Very good point. It is not worth the effort. These issues are best handled
using namespaces and sections.
On Fri, Jan 23, 2015 at 12:22 PM, Leonardo de Moura <
<EMAIL_ADDRESS>wrote:

It would be useful to have a clear_attribute command.
However, there are some issues:

What would be the meaning of clear persistent attribute? I think
this would create problems.
Some attributes are not easy to "clear". Coercion is an example. We
maintain the transitive closure of the coercion graph.
Some clear commands would affect other attributes. For example: clear
attribute inhabited [class], must also "clear" all instance
attributes. That is, if a declaration D has an [instance] attribute,
and D is an instance of inhabited, then this [instance] attribute
must also be cleared.

I think there are more problems, I just list the first problems that came
to my mind.
—
Reply to this email directly or view it on GitHub
https://github.com/leanprover/lean/pull/403#issuecomment-71229192.


WIP: 3-cockpit-11: [no-test] Update translations from Fedora Zanata

Update translations from Fedora Zanata

[ ] po-refresh

po-refresh in progress on centosci-tasks-0mtl2.
Log: https://logs-https-cockpit.apps.ci.centos.org/logs/po-refresh-758-20190809-045858/

po-refresh in progress on 4-ci-srv-03.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-758-20190809-045858/

po-refresh in progress on 4-cockpit-10.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-758-20190809-045858/

po-refresh in progress on 3-cockpit-11.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-758-20190809-045858/


Good framework

I like this framework.
Does it have cdn setup link?

Hey there! I'm glad you like it.
It does not have a CDN setup yet. Even though the framework is somewhat
stable it's still in development, so I haven't gotten to that yet.
If you give me a couple days I will release an early version and publish in
a CDN. I will reply here when I publish it.
But you can still use it by installing the repo as a npm dependency. Then
use cardboard as esm or import the bundle. Either using typescript or js. I
recommend using typescript for better type definitions, but you can use it
directly in js if you prefer.
Take a look at these links for more info on how to get going, and feel free
to ask if you have any troubles:
https://github.com/nombrekeff/cardboard-js/wiki/Getting-Started
Building/bundling:
https://github.com/nombrekeff/cardboard-js/wiki/Building-App
Here is a complete example setup:
https://github.com/nombrekeff/cardboard-js/tree/main/examples/routes
El mié, 8 nov 2023, 23:37, cipriano200 @.***> escribió:

I like this framework.
Does it have cdn setup link?
—
Reply to this email directly, view it on GitHub
https://github.com/nombrekeff/cardboard-js/issues/35, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AECA6PFVBYNJMKQLJYQ3JQLYDQCR5AVCNFSM6AAAAAA7DT5VE2VHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4DINJRGQZTAMY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks


Broken link in samples page note

On samples pages, like this one, the link in the note at the top of the page is broken.
The link currently points to:
https://docs.gradle.org/current/samples/gradle_ides.html#gradle_ides
It should point to:
https://docs.gradle.org/current/userguide/gradle_ides.html#gradle_ides

We discussed it on the community Slack. To confirm, it is a valid issue


Minor fixes to tutorials

Fixed Imports in tutorials, removed extra large outputs in tutorials.

Codecov Report

Merging #46 (da70dce) into master (45a5c4d) will increase coverage by 0.59%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
+ Coverage   49.47%   50.07%   +0.59%
==========================================
  Files          14       14
  Lines        2003     2003
==========================================
+ Hits          991     1003      +12
+ Misses       1012     1000      -12

see 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


[ReleasePrep][2019.01.28]RI of dev into master for NuGetGallery

@skofman1 @joelverhagen @loic-sharma

All my changes are now verified so I'm ready to deploy!

Remember to run migrations within approximately 1 hour of merging this!!!!


Prometheus Tracing

Hi,
I have build a local version of prometheus, that use zipkin or jaeger for tracing the promql and the targets.
As I tried to create a PR, I found the PR-2554.
Which include the information that "the group would't like to have the dependency in the project".
I played a time with the information, and would like to implement a plugin interface.
Then I could develop 2 single shared object, that could be loaded with the golang plugin functions.
Is this a vaild / interessting aproch?
Thanks
Marcel

That's a little out of date now. The release of Prometheus which is in progress includes Jaeger, but only on an experimental stop-gap basis until a OpenTelemetry is settled.
Go plugins would not help here.

Hi,
Thanks for the Info.
Marcel


Describe the bug
Running IntuneCD-startdocumentation results in 'TypeError: can only concatenate str (not "dict") to str'.
Run INTRO="Microsoft Intune backup and documentation generated at $GITHUB_REPOSITORY "
  INTRO="Microsoft Intune backup and documentation generated at $GITHUB_REPOSITORY "
  IntuneCD-startdocumentation \
      --path="$GITHUB_WORKSPACE/prod-backup" \
      --outpath="$GITHUB_WORKSPACE/prod-as-built.md" \
      --tenantname=$TENANT_NAME \
      --intro="$INTRO"
  shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
  env:
    TENANT_NAME: ***
    CLIENT_ID: ***
    CLIENT_SECRET: ***
Traceback (most recent call last):
  File "/home/runner/.local/bin/IntuneCD-startdocumentation", line 8, in <module>
    sys.exit(start())
  File "/home/runner/.local/lib/python3.10/site-packages/IntuneCD/run_documentation.py", line [2](https://github.com/aaronparker/intune-backup/actions/runs/3644379916/jobs/6153567987#step:10:2)18, in start
    run_documentation(args.path, args.outpath, args.tenantname, args.jsondata, args.maxlength, args.split, args.cleanup)
  File "/home/runner/.local/lib/python[3](https://github.com/aaronparker/intune-backup/actions/runs/3644379916/jobs/6153567987#step:10:3).10/site-packages/IntuneCD/run_documentation.py", line 129, in run_documentation
    document_configs(f'{configpath}/Device Configurations', outpath, 'Configuration Profiles', maxlength, split, cleanup)
  File "/home/runner/.local/lib/python3.10/site-packages/IntuneCD/documentation_functions.py", line 2[4](https://github.com/aaronparker/intune-backup/actions/runs/3644379916/jobs/6153567987#step:10:4)4, in document_configs
    for key, value in zip(repo_data.keys(), clean_list(repo_data.values())):
  File "/home/runner/.local/lib/python3.10/site-packages/IntuneCD/documentation_functions.py", line 18[5](https://github.com/aaronparker/intune-backup/actions/runs/3644379916/jobs/6153567987#step:10:5), in clean_list
    values.append(dict_string(item))
  File "/home/runner/.local/lib/python3.10/site-packages/IntuneCD/documentation_functions.py", line 14[7](https://github.com/aaronparker/intune-backup/actions/runs/3644379916/jobs/6153567987#step:10:7), in dict_string
    first = '
     -  ' + v[0]
TypeError: can only concatenate str (not "dict") to str
Error: Process completed with exit code 1.

To Reproduce
See commands used in the log extract above.
Expected behavior
Markdown documentation should complete.
Run type (please complete the following information):

Mode: 1
Client: GitHub Actions
Version: 1.2.7

Can you verify that you are running the latest version? that error looks like it's coming from v 1.2.6

I've re-run it and it's completed OK. Thought the pipeline had run post 1.2.7 being published.


Text uses incorrect style on initial load in P2P

(I'm using mac/firefox)
When loading a document in P2P that already has some text, the initial load does not have the correct text styling. After modifying/adding any object the styling appears to get updated correctly.
Initial load:

After adding a circle:

Thanks for the report. I was fixing this in https://github.com/excalidraw/excalidraw/pull/1197, but apparently didn't account for collab scenes. I'll take a look.

@kyldvs can you check if this is fixed in https://excalidraw-git-fixfontloadingforgood.excalidraw.now.sh/?

Yes, confirmed that it's fixed there! Thanks for the quick turnaround!


ParseUtil#parseTags not updated

ParseUtil#parseTags does not create new Tag object as per implemented in WIFE (implementation is outdated with AB3 version)

Outdated


Refactored middle layers of the SSA stack.

This refactoring should facilitate addressing SmartState issues in the future.
Specifically, this was prompted by the need to address a number of RHEVM SSA issues.
While this PR may address some of those issues, that can't be verified until the
remaining issues have been dealt with.

@Fryguy @chessbyte @jerryk55 please review.

Can we put these into a ..::Scanner class (which gets instantiated with a reference to the VmOrTemplate), instead of including them directly into the class via a concern? It feels like a chunk of functionality that might be more comfortable with a dedicated space for its own instance state.
This is possibly more observation-in-passing, than necessarily something that belongs in this particular PR. Either way, this change looks good... polymorphism++.

@matthewd I was struggling as to where to draw that line. The lower layer of the fleecing code does have its own object/state and is VM type independent. The code that's the subject of this PR is very vmdb and VM type specific - so including it in the VM model class seemed to make sense.


feat!: add sample cdc

Hi,
contributing to https://github.com/openwallet-foundation/agent-framework-javascript/pull/1638 by providing a working postgres CDC sample that publishes changes to redis.
Not sure how you'd want to provide this in the repo, feel free to move it wherever as required.

Very cool @ericvergnaud! I think it would be great if we can add this to the samples directory and integrate it with an actual AFJ mediator setup as example. We currently have a veryyy simple mediator as example, and then this could be part of a more complex one. Or at some point we can move it to another repo (e.g. combine it with https://github.com/animo/animo-mediator and make that a ready to deploy production ready mediator deploy for which we could publish images to docker)

@TimoGlastra I've moved it under examples.
In order to implement a fully working example, I would need to use https://github.com/openwallet-foundation/agent-framework-javascript/pull/1638 as a basis. Not sure about the best strategy, should I wait for it to be merged or should I create a PR on @genaris's work ?

@TimoGlastra not sure why prettier fails, exit code 1 is not very helpful. How do you run this locally ?

It lists the files that are not formatted correclty:
samples/postgres-cdc/docker-compose.yml
samples/postgres-cdc/README.md

You can run yarn format locally to fix it

Sorry for the long delay in getting this addressed @ericvergnaud. We now have https://github.com/sairanjit/credo-ts-examples, which we intend to move over to OWF in the future. Could you add this example to that repository? That would be the perfect place I think. Also I think for this to work you'd also need a custom MessageRepository right? Could you extend the example to be a minimal, but fully working example?


Fix Bash syntax

@mahilleb-msft : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


address #1411

Change Description
Previously, DicomImageRedactorEngine is a child of ImageRedactorEngine; I have removed this dependency.  Then, I allow DicomImageRedactorEngine to be initialized with an instance of ImageAnalyzerEngine as a input parameter.  Then, one could a different recognizer, such as Flair as follows
from flair_recognizer import FlairRecognizer
from presidio_image_redactor import ImageAnalyzerEngine

flair_recognizer = FlairRecognizer()  # This would download a very large (+2GB) model on the first run
registry = RecognizerRegistry()
registry.add_recognizer(flair_recognizer)
my_analyzer_engine = AnalyzerEngine(registry=registry)

my_image_analyzer_engine = ImageAnalyzerEngine(analyzer_engine=my_analyzer_engine)
my_dicom_image_redactor_engine = DicomImageRedactorEngine(image_analyzer_engine=my_image_analyzer_engine)
image, box = my_dicom_image_redactor_engine.redact_and_return_bbox(etc, etc)

Issue reference
This PR fixes issue #1411
Checklist

[ x] I have reviewed the contribution guidelines
[ ] I have signed the CLA (if required)
[ ] My code includes unit tests
[x] All unit tests and lint checks pass locally
[ ] My PR contains documentation updates / additions if required

@microsoft-github-policy-service agree company="University Health Network"

Closing as #1411 is closed


Manage Environment Variables with Azure Key Vault - Add AKV and GKE integration

DEVDOC-287

Description

Pull Request Type

[X] Documentation content changes
[ ] Bugfix / Missing Redirects
[ ] Docusaurus site code changes

PR Checklist

[X] The commit message follows our guidelines included in the CONTRIBUTING.md
[X] All tests of Lint, cspell and check-content pass. (How to launch them?)
[X] No sensitive content has been committed

Other information

Hi guys, any news on that?


base06 only used once in base16.lua

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
base16.lua
Description
The base06 color is only used once in base16.lua. This feels like a waste.
I recommend the feature of using base06 more than once in base16.lua.

Thanks for suggestion!
'mini.base16' tries to follow chriskempson/base16-vim as much as possible. As it doesn't use base06 at all, so is 'mini.base16'.


[gmp] Build error

Host Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:
vcpkg install gmp
Failure logs
Starting package 3/3: gmp:x86-windows
Building package gmp[core]:x86-windows...
-- Downloading https://github.com/ShiftMediaProject/gmp/archive/0018c44e8dfcc3b64b43e0aea4b3f419f0b65fd0.tar.gz -> ShiftMediaProject-gmp-0018c44e8dfcc3b64b43e0aea4b3f419f0b65fd0.tar.gz...
-- Extracting source C:/vcpkg/downloads/ShiftMediaProject-gmp-0018c44e8dfcc3b64b43e0aea4b3f419f0b65fd0.tar.gz
-- Applying patch vs.build.patch
-- Applying patch runtime.patch
-- Applying patch adddef.patch
-- Using source at C:/vcpkg/buildtrees/gmp/src/19f0b65fd0-9b395bc164.clean
-- Building SMP/libgmp.sln for Release
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
Command failed: msbuild C:/vcpkg/buildtrees/gmp/x86-windows-rel/19f0b65fd0-9b395bc164.clean/SMP/libgmp.sln /p:Configuration=ReleaseDLL /p:YasmPath=C:\vcpkg\installed\x64-windows\share\yasm-tool\..\..\tools\yasm-tool\yasm.exe /t:Rebuild /p:Platform=x86 /p:PlatformToolset=v143 /p:VCPkgLocalAppDataDisabled=true /p:UseIntelMKL=No /p:WindowsTargetPlatformVersion=10.0.19041.0 /p:VcpkgTriplet=x86-windows /p:VcpkgInstalledDir=C:/vcpkg/installed /p:VcpkgManifestInstall=false /p:UseMultiToolTask=true /p:MultiProcMaxCount=5 /p:EnforceProcessCountAcrossBuilds=true /m:5 /p:ForceImportBeforeCppTargets=C:/vcpkg/scripts/buildsystems/msbuild/vcpkg.targets /p:VcpkgApplocalDeps=false
Working Directory: C:/vcpkg/buildtrees/gmp/x86-windows-rel/19f0b65fd0-9b395bc164.clean
Error code: 1
See logs for more information:
C:\vcpkg\buildtrees\gmp\build-x86-windows-rel-out.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_install_msbuild.cmake:172 (vcpkg_execute_required_process)
ports/gmp/portfile.cmake:51 (vcpkg_install_msbuild)
scripts/ports.cmake:142 (include)
Additional context
I'm new

Thanks for posting this issue. Please provide the error log file: C:\vcpkg\buildtrees\gmp\build-x86-windows-rel-out.log

build-x86-windows-rel-out.log

build-x64-windows-rel-out.log
for x64 aswell, same thing

i fixed it by installing the windows 10 SDK from vs2022 and uninstalling from vs build tools 2019

This issue has been resolved, so I am closing this issue for now.


Can't build project if LinqPad not installed

DevDeploy.bat should check if LINQPad is installed.

Merge in to own project accidentally closed this issue


Accelerate close but not checkpoints in standalone

What
Accelerate close but not checkpoints in standalone, and skip ahead to ledger 64 in standalone at boot.
Why
In #448 we made standalone accelerated, where both ledger close times are faster and the first checkpoint is set as the 8th ledger. This was done for two reasons.
The first reason was to speed up development and testing use cases that use standalone. Dev and test use cases benefit from shorter ledger close times since tests and developers are waiting for that 5 seconds, and that waiting rarely serves a meaningful purposes outside of a real network.
The second reason was to shorten the time soroban-rpc and horizon (running captive-core) needed to wait to be able to start ingesting data from the standalone network. Both need a checkpoint to be published before they can ingest, and a checkpoint isn't published by default until ledger 64, or when accelerated, ledger 8.
The change in #448 addressed the first issue completely, and reduced the wait time for the first checkpoint from 5 minutes to approximately 8 seconds.
Recently core was released with a new command offline-close that closes a configurable number of ledgers automatically, and published any needed checkpoints. We can use the command to fast forward the standalone network to a ledger that is a checkpoint so that at boot a checkpoint is already available and services can start ingesting immediately.
In dev and testing in quickstart we don't usually need frequent checkpoints either, so we can switch from an accelerated network to a network that has only a faster close time.
By switching to only a faster close time, and skipping ahead to the first checkpoint, both original reasons are still addressed, also the services no longer need to wait the short 8 seconds to ingest but can ingest immediately, and not as many checkpoints are created on disk.
This change in the end isn't critical. What we have already will address the original two problems. But this new command lets us speed it up slightly and makes the logs a little less confusing since soroban-rpc won't have to crash and power cycle during that 8 seconds, but instead will be able to start instantly.
Merging
This change can be merged after the offline-close command is included in released versions of stellar-core that end up in the latest, testing, and soroban-dev images. This will probably mean holding the change until stellar-core v19.11.0 and until stellar-core soroban preview release 10.

cc @graydon @MonsieurNicolas

Closing because of the same reasons outlined in https://github.com/stellar/quickstart/pull/479#issuecomment-1692540323.


Support de-deduping head tags by setting key

Fixes #3169

For reference #668 was my initial implementation. Will work on this sometime soon. Thanks for the PR with tests @liweinan0423 will combine the 2 👌 🙌

@liweinan0423 thanks for using my solution. The test you added fails in appveyor (windows). I'm pretty sure it's related to the test and not the code being broken in this case 👍

@timneutkens tests are good but the de-duping logic was wrong. I have fixed them. Also could you also delete my README texts and add your documentation, I think your docs are better. 👍

@liweinan0423 feel free to copy them over 🙌

@timneutkens any plan on merging this PR into master ?

@liweinan0423 I'll do a new canary release this weekend.


Fonts

Tests Missing don't merge just take a look :)

Hey, this seems to be totally crashing in Squeak-Trunk. Have you taken a look at this? @Sohn123 @TillWenke


How to train models?

#13 Was helpful for using the pre-trained models. However, I would like to train my own models. As a first step, I removed all the existing models:
# cd trained_models/
# ls
conll_2003_en		     i2b2_2014_glove_stanford_bioes  mimic_glove_stanford_bioes
i2b2_2014_glove_spacy_bioes  mimic_glove_spacy_bioes	     performances.md
# rm -rf *

Then I trained a model using data/conll2003/en/ (identical data, default parameters.ini):
# python3 main.py --maximum_number_of_epochs=1 --token_pretrained_embedding_filepath=""

I then see a model in ../output/en_2017-07-26_22-06-40-510129/model. However, I get this error when trying to use the model:
# ls ../output/en_2017-07-26_22-06-40-510129/model/
checkpoint				     model_00001.ckpt.meta
dataset.pickle				     parameters.ini
events.out.tfevents.1501106802.114dd5c0c94c  projector_config.pbtxt
model_00001.ckpt.data-00000-of-00001	     tensorboard_metadata_characters.tsv
model_00001.ckpt.index			     tensorboard_metadata_tokens.tsv
# python3 main.py --train_model=False --use_pretrained_model=True --dataset_text_folder=../data/example_unannotated_texts --pretrained_model_folder=../output/en_2017-07-26_22-06-40-510129/model/
NeuroNER version: 1.0-dev
TensorFlow version: 1.2.1
{'character_embedding_dimension': 25,
 'character_lstm_hidden_state_dimension': 25,
 'check_for_digits_replaced_with_zeros': 1,
 'check_for_lowercase': 1,
 'dataset_text_folder': '../data/example_unannotated_texts',
 'debug': 0,
 'dropout_rate': 0.5,
 'experiment_name': 'test',
 'freeze_token_embeddings': 0,
 'gradient_clipping_value': 5.0,
 'learning_rate': 0.005,
 'load_all_pretrained_token_embeddings': 0,
 'load_only_pretrained_token_embeddings': 0,
 'main_evaluation_mode': 'conll',
 'maximum_number_of_epochs': 100,
 'number_of_cpu_threads': 8,
 'number_of_gpus': 0,
 'optimizer': 'sgd',
 'output_folder': '../output',
 'parameters_filepath': './parameters.ini',
 'patience': 10,
 'plot_format': 'pdf',
 'pretrained_model_folder': '../output/en_2017-07-26_22-06-40-510129/model/',
 'reload_character_embeddings': 1,
 'reload_character_lstm': 1,
 'reload_crf': 1,
 'reload_feedforward': 1,
 'reload_token_embeddings': 1,
 'reload_token_lstm': 1,
 'remap_unknown_tokens_to_unk': 1,
 'spacylanguage': 'en',
 'tagging_format': 'bioes',
 'token_embedding_dimension': 100,
 'token_lstm_hidden_state_dimension': 100,
 'token_pretrained_embedding_filepath': '../data/word_vectors/glove.6B.100d.txt',
 'tokenizer': 'spacy',
 'train_model': 0,
 'use_character_lstm': 1,
 'use_crf': 1,
 'use_pretrained_model': 1,
 'verbose': 0}
Formatting deploy set from BRAT to CONLL... Done.
Converting CONLL from BIO to BIOES format... Done.
Load dataset... done (19.13 seconds)
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 1139, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 1121, in _run_fn
    status, run_metadata)
  File "/usr/lib/python3.4/contextlib.py", line 66, in __exit__
    next(self.gen)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/errors_impl.py", line 466, in raise_exception_on_not_ok_status
    pywrap_tensorflow.TF_GetCode(status))
tensorflow.python.framework.errors_impl.NotFoundError: Unsuccessful TensorSliceReader constructor: Failed to find any matching files for ../output/en_2017-07-26_22-06-40-510129/model/model.ckpt
	 [[Node: save/RestoreV2_23 = RestoreV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_save/Const_0_0, save/RestoreV2_23/tensor_names, save/RestoreV2_23/shape_and_slices)]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "main.py", line 250, in <module>
    main()
  File "main.py", line 245, in main
    nn = NeuroNER(**arguments)
  File "/NeuroNER/src/neuroner.py", line 285, in __init__
    self.transition_params_trained = model.restore_from_pretrained_model(parameters, dataset, sess, token_to_vector=token_to_vector)
  File "/NeuroNER/src/entity_lstm.py", line 337, in restore_from_pretrained_model
    self.saver.restore(sess, pretrained_model_checkpoint_filepath) # Works only when the dimensions of tensor variables are matched.
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 1548, in restore
    {self.saver_def.filename_tensor_name: save_path})
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 789, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 997, in _run
    feed_dict_string, options, run_metadata)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 1132, in _do_run
    target_list, options, run_metadata)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/client/session.py", line 1152, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.NotFoundError: Unsuccessful TensorSliceReader constructor: Failed to find any matching files for ../output/en_2017-07-26_22-06-40-510129/model/model.ckpt
	 [[Node: save/RestoreV2_23 = RestoreV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_save/Const_0_0, save/RestoreV2_23/tensor_names, save/RestoreV2_23/shape_and_slices)]]

Caused by op 'save/RestoreV2_23', defined at:
  File "main.py", line 250, in <module>
    main()
  File "main.py", line 245, in main
    nn = NeuroNER(**arguments)
  File "/NeuroNER/src/neuroner.py", line 278, in __init__
    model = EntityLSTM(dataset, parameters)
  File "/NeuroNER/src/entity_lstm.py", line 216, in __init__
    self.saver = tf.train.Saver(max_to_keep=parameters['maximum_number_of_epochs'])  # defaults to saving all variables
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 1139, in __init__
    self.build()
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 1170, in build
    restore_sequentially=self._restore_sequentially)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 691, in build
    restore_sequentially, reshape)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 407, in _AddRestoreOps
    tensors = self.restore_op(filename_tensor, saveable, preferred_shard)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/training/saver.py", line 247, in restore_op
    [spec.tensor.dtype])[0])
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/ops/gen_io_ops.py", line 640, in restore_v2
    dtypes=dtypes, name=name)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 767, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 2506, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 1269, in __init__
    self._traceback = _extract_stack()

NotFoundError (see above for traceback): Unsuccessful TensorSliceReader constructor: Failed to find any matching files for ../output/en_2017-07-26_22-06-40-510129/model/model.ckpt
	 [[Node: save/RestoreV2_23 = RestoreV2[dtypes=[DT_FLOAT], _device="/job:localhost/replica:0/task:0/cpu:0"](_arg_save/Const_0_0, save/RestoreV2_23/tensor_names, save/RestoreV2_23/shape_and_slices)]]

Exception ignored in: <bound method NeuroNER.__del__ of <neuroner.NeuroNER object at 0x7f9eb30e7f60>>
Traceback (most recent call last):
  File "/NeuroNER/src/neuroner.py", line 489, in __del__
    self.sess.close()
AttributeError: 'NeuroNER' object has no attribute 'sess'

I'm not sure what to make of this, since I don't see the need for a checkpoint file when using the pretrained models, and there is no model.ckpt in the pre-trained models (although I did see model.ckpt.index, model.ckpt.data-00000-of-00001, and model.ckpt.meta).
Note: I am using python 3.6. I assumed that this would not break compatibility with 3.5 and have yet to test 3.5.

I tried to use the model I had trained similar way using python3.5. I ran into the similar issues. Did you manage to solve it?

In order to load the pretrained model, NeuroNER requires the files parameters.ini, dataset.pickle, model.ckpt.index, model.ckpt.data-00000-of-00001 and model.ckpt.meta to be present in the specified pretrained_model_folder. The latter three files are how tensorflow saves a checkpoint, though the header in the parameters.ini file refers to those files altogether as model.ckpt for simplicity.
Your example should run properly if you simply rename the three files model_00001.ckpt.index, model_00001.ckpt.data-00000-of-00001, and  model_00001.ckpt.meta to model.ckpt.index, model.ckpt.data-00000-of-00001 and model.ckpt.meta by removing '_00001' from the filenames.
In order to export the model more cleanly, please refer to the Sharing a pretrained model section in README.md. The src/prepare_pretrained_model.py script should take care of renaming and copying over the necessary files to a new folder.

Thank you Jenny, this advice resolved the issue.

@jennyjylee I have the same error:
Exception ignored in: <bound method NeuroNER.del of <neuroner.NeuroNER object at 0x7fc9b9bab630>>
Traceback (most recent call last):
File "/home/yana/Documents/yana/NeuroNER-master/src/neuroner.py", line 489, in del
self.sess.close()
AttributeError: 'NeuroNER' object has no attribute 'sess'
while simply trying to run the pre-trained model:
python3.5 main.py --train_model=False --use_pretrained_model=True --dataset_text_folder=../data/example_unannotated_texts --pretrained_model_folder=../trained_models/conll_2003_en
I have checked: all the names in con_2003_en folder correspond to the expected ones...
Could you please help?

@jennyjylee
Dear Jenny
I want to fine-tuning the pre-trained model, namely mimic_glove_spacy_bioes, on i2b2 dataset.
But I encountered a problem. It seems the labels in i2b2 dataset are different from the labels in MIMIC dataset.
Do I need to refer to the 'Sharing a pretrained model' section? Do you know how to solve the label difference problem?
I got errors as:
'AssertionError: The label B-BIOID does not exist in the pretraining dataset. Please ensure that only the following labels exist in the dataset: B-AGE, B-COUNTRY, B-DATE, B-DOCTOR, B-HOSPITAL, B-IDNUM, B-LOCATION_OTHER, B-PATIENT, B-PHONE, B-STATE, B-STREET, B-ZIP, E-AGE, E-COUNTRY, E-DATE, E-DOCTOR, E-HOSPITAL, E-IDNUM, E-LOCATION_OTHER, E-PATIENT, E-PHONE, E-STATE, E-STREET, E-ZIP, I-AGE, I-COUNTRY, I-DATE, I-DOCTOR, I-HOSPITAL, I-IDNUM, I-LOCATION_OTHER, I-PATIENT, I-PHONE, I-STATE, I-STREET, I-ZIP, O, S-AGE, S-COUNTRY, S-DATE, S-DOCTOR, S-HOSPITAL, S-IDNUM, S-LOCATION_OTHER, S-PATIENT, S-PHONE, S-STATE, S-STREET, S-ZIP'
Hope for your help.
Best Regards
Steven

@jennyjylee
Dear Jenny
I want to fine-tuning the pre-trained model, namely mimic_glove_spacy_bioes, on i2b2 dataset.
But I encountered a problem. It seems the labels in i2b2 dataset are different from the labels in MIMIC dataset.
Do I need to refer to the 'Sharing a pretrained model' section? Do you know how to solve the label difference problem?
I got errors as:
'AssertionError: The label B-BIOID does not exist in the pretraining dataset. Please ensure that only the following labels exist in the dataset: B-AGE, B-COUNTRY, B-DATE, B-DOCTOR, B-HOSPITAL, B-IDNUM, B-LOCATION_OTHER, B-PATIENT, B-PHONE, B-STATE, B-STREET, B-ZIP, E-AGE, E-COUNTRY, E-DATE, E-DOCTOR, E-HOSPITAL, E-IDNUM, E-LOCATION_OTHER, E-PATIENT, E-PHONE, E-STATE, E-STREET, E-ZIP, I-AGE, I-COUNTRY, I-DATE, I-DOCTOR, I-HOSPITAL, I-IDNUM, I-LOCATION_OTHER, I-PATIENT, I-PHONE, I-STATE, I-STREET, I-ZIP, O, S-AGE, S-COUNTRY, S-DATE, S-DOCTOR, S-HOSPITAL, S-IDNUM, S-LOCATION_OTHER, S-PATIENT, S-PHONE, S-STATE, S-STREET, S-ZIP'
Hope for your help.
Best Regards
Steven

Hi Steven,
Have you solved the problem, I have encountered the same problem?
Best wishes,
Tina


Handle missed error codes on TopicMetaDataRequest and GroupCoordinatorRequest

Adds a few missed errors that I've encountered, in particular one https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-TopicMetadataRequest and one https://cwiki.apache.org/confluence/display/KAFKA/A+Guide+To+The+Kafka+Protocol#AGuideToTheKafkaProtocol-GroupCoordinatorRequest
Also adds https://kafka.apache.org/protocol#protocol_error_codes code # 82
The CLA check is failing, but I have previously signed it - if I try to do so again, I get
To sign our CLA 1 field needs to be changed
GitHub username has already signed a CLA

Many thanks!


Mox Mail Server

At first sight, this new integrated mail server seems like a great idea - especially to someone who wants to self-host but finds the usual solution of Postfix/Devecot/SpamAssasin/Roundcube to be very difficult to manage.
But the problem is that installing Mox as it is intended, i.e. with DNSSEC records set up optimally for spam rejection, is just too much work and far too much hassle.
DNSSEC is nominally implemented by my own VPS host (OVH) - yet I find no guide documentation on things like editing TLSA, MTA-STS, etc. Needless to say, the more esoteric records like NSEC3 and NSEC3PARAM are given no mention at all.
So, as I see it, if Mox authors want their new mail server adopted by enough people to enable its testing & debugging, I would advise spending some of the NLNet microfinance grant on a technical author to write the necessary procedures for installation and configuration.
I am sorry to have to say this but it is the simple truth. Just look at the "documentation" on the Unbound package . . . It's more like a list of hacks rather than a user's manual.

I've been through the process of installing this myself, and it can be tricky.
While my tutorial is for a different hoster, it might provide some helpful insights. Check it out here: https://community.hetzner.com/tutorials/install-and-configure-mailserver-mox-on-debian

@RobSlgm
I think you anticipate more expertise in sys admin than most coders may have.
Our Cloud-init configuration installed "unbound" with a minimal configuration and with adaptions for Mox. Prior to enabling the DNSSEC/DANE setup for the mail server, ensure the functionality of the DNS resolver. There are several requirements to DNSSEC.
This is very much a circular answer in that it presumes proficiency in the very things that are causing the hold-ups preventing Mox installation.
Right now, trying to install and configure Unbound has left me with:
$ delv mysite.org ;; broken trust chain resolving 'mysite.org/A/IN': <IP_ADDRESS>#53 ;; resolution failed: broken trust chain
Maybe I need to revert to the Unbound GitHub issues pages before resuming my DNSSEC efforts.
Given the lack of guidance documents on this, I may - to paraphrase Lawrence Oates - be outside for some time.

The Unbound configuration given in my example is complete (if used with Debian).
It starts from the place where you bought the domain (Domain/DNS provider, e.g. Cloudfare). The next assumption behind this configuration is that you can manage all the DNS entries at this provider within their UI. The provider must allow you to enter TLSA records (I mention this as unfortunately not all provider do that…).
The local Unbound is just a kind of glue to retrieve the DNS entries.
Are you trying to operate your own nameserver? In this much more complex setup you still need to setup at least a DS (delegation) record at your Domain provider. I have not yet found one provider who allows this outside the enterprise world.

The Unbound configuration given in my example is complete (if used with Debian).
_Step 2.3 - DNSSECThe Unbound configuration given in my example is complete (if used with Debian).
Our Cloud-init configuration installed "unbound" with a minimal configuration and with adaptions for Mox._
Your only reference to Unbound seems very scant to me.
This is what I can do on my ISP's control panel for DNS:

The how-to on TLSA records is missing from the user docs.
I'm not trying to operate my own nameservers - I use the hosts default nameservers. By domain provider do you mean the registry of all the .xyz domains ? Or just the ISP that handles the annual fees and associated tasks ? The latter is done by OVH in my case.
As it stands, the DNSSEC records provided by OVH for me include SOA, DS, DSK and ZSK keys.

There are two distinct steps.
Server installation
Step 1 is ensuring that your VPS/server can make DNS queries with DNSSEC.
This is unrelated to the fact whether your own domain has DNSSEC enabled. Step 1 is reached in my tutorial with the basic installation (cloud-init, by installation of dns-root-data, unbound-anchor and unbound and the configuration file at /etc/unbound/unbound.conf). The configuration works on Debian (not on Ubuntu).
Check the result of this first step with devl xmox.nl, the result needs to contain a RRSIG record.
DNS setup
Step 2 is making sure that your own domain has DNSSEC enabled. Googling gave me following link at OVHcloud https://help.ovhcloud.com/csm/en-dns-secure-domain-dnssec?id=kb_article_view&sysparm_article=KB0051637
Make sure that you enable DNSSEC for your domain, which I understood was bought at OVH directly. Don’t go down the “Your domain name doesn’t use OVHCloud DNS Server” route.
As soon as DNSSEC is enabled you can perform the ./mox quickstart which gives you a list of DNS records. Now enter ALL these DNS records in the UI, which you properly identified in a previous post. This is described in https://help.ovhcloud.com/csm/en-ie-dns-zone-records?id=kb_article_view&sysparm_article=KB0063636 (are you referring to this page as user manual).
For the TLSA record the quickstart gives you something like
_25._tcp.mail.example.org.      TLSA 3 1 1 99……………………………13e21131
I don’t have access to OVH, but I assume the screen will look similar to this screenshoot from Cloudfare DNS service:

Your local unbound is not involved in the second step at all.

Thanks for reporting @corinthian13, and thanks for the answers @RobSlgm!
It's true that DNSSEC isn't the easiest aspect to get right in a mox setup. As Robert mentioned, there are two parts to DNSSEC:

DNSSEC-verifying resolving of DNS names on your server (mox needs to see the DNSSEC-results of a DNS lookup). Most linux systems don't come with a (properly functioning) DNSSEC-verifying resolver. Installing unbound takes care of this.
DNSSEC-signing the records of your own domain. So that anyone with a DNSSEC-verifying resolver that looks up your domain can detect forged DNS responses. If you're lucky, enabling DNSSEC for your domain is a matter of checking a checkbox in some UI. If you're unlucky, it's not supported by a DNS operator/registrar at all. I used to have my DNS hosted at AWS (Route 53). They support DNSSEC (though enabling it is tricky and feels designed to make you fail; I always need my notes to guide me through the process), but do not support TLSA records.

The mox quickstart is pointing you in the right direction for setting these things up, but it doesn't explain all steps in full detail. In part because the details are best described elsewhere (e.g. unbound documentation, or guides for each DNS registrar/operator/software). But also because the quickstart isn't interactive and I don't want to make the output too long. I still have plans to make an interactive step-by-step setup that guides you through the process, including asking you to install unbound, then checking it is working properly, and including checking dnssec for your domain (and again after you've made changes). But it's not at the top of the todo-list yet.
Some more comments:

But the problem is that installing Mox as it is intended, i.e. with DNSSEC records set up optimally for spam rejection, is just too much work and far too much hassle.

One correction: DNSSEC isn't needed for spam rejection. Spam analysis is done based on verifying sender addresses with DKIM/SPF and keeping tracking of reputation of verified senders. Having DNSSEC doesn't (currently) play a part.
DNSSEC is needed to protect MX records. It ensures email directed to a domain really makes it to the correct, verified mail servers for that domain. Without DNSSEC, a single forged DNS response to a lookup of MX records (during delivery) can cause email addressed to your domain to be misdirected to another server (and that other server may have TLS set up and look very secure and TLS verified, it's just that it may be someone else's mail server!). This indirection through MX records is not present for most other internet protocols (which typically just connect to a hostname from a user-visible URL and verify the connection has a TLS cert for that host name, i.e. they rely on WebPKI), that's why other protocols don't need DNSSEC as badly as email does.

DNSSEC is nominally implemented by my own VPS host (OVH) - yet I find no guide documentation on things like editing TLSA, MTA-STS, etc. Needless to say, the more esoteric records like NSEC3 and NSEC3PARAM are given no mention at all.

I think what we need is a good explanation of how all these concepts and techniques relate to each other. DANE requires a few TLSA records to be created (and DNSSEC enabled on the domain; mox shows the TLSA records to create and that's enough). MTA-STS needs a few DNS records and a simple policy file served over HTTPS (mox shows the DNS records to create and serves the MTA-STS policy file). NSEC* are DNSSEC concepts that chosen as part of DNSSEC setup (your DNS operator has probably made a decision on them). Then there is SPF, DKIM, DMARC, reporting (mox shows DNS records and creates keys). The quickstart does try to give a bit of context (which helps as a reminder if you already pretty much know how it works), but it's not enough to learn the concepts. You either need to know already, or start looking for more complete explanations. There are probably good resources on the internet about all these concepts. With a step-by-step guided setup in the future, we could give more explanation during the process. But it doesn't fit in the one-shot quickstart.
@RobSlgm

While my tutorial is for a different hoster, it might provide some helpful insights. Check it out here: https://community.hetzner.com/tutorials/install-and-configure-mailserver-mox-on-debian

That's nice, hadn't seen that yet (or I didn't remember). Tiny nit: the "import mailboxes" links to the export command docs.

$ delv mysite.org
;; broken trust chain resolving 'mysite.org/A/IN': <IP_ADDRESS>#53
;; resolution failed: broken trust chain

That IP <IP_ADDRESS> indicates the resolved used is not unbound, but probably systemd-resolved, which may have been disabled/uninstalled when unbound was installed. I've seen this more often, and I don't know why that's considered good default behaviour. It's also a good idea to check DNSSEC lookups with "dig". The "delv" command does its own DNSSEC-verification. But you want to check that unbound is doing DNSSEC verification, and "dig" shows the DNSSEC-result that unbound found. See issue #158 for details.
There has been a commit to the quickstart output (that isn't in a release yet) that would point future users in that direction, see https://github.com/mjl-/mox/commit/83004bb18e3cd2d525fee82ad9a754dde6c77a2f#diff-e7bc0318a31a2b51c6d7393f325e4555f474fb1d72a461f823507703fdd1a4d4
It's probably time for a FAQ entry about this, I'm making a note to add an entry.

@mjl-
Thanks for your response.
I well realize that DNSSEC is awkward to get running on a server and that it's more complex than simply switching on an Enable DNSSEC button on a host's control panel.

Problem #1 is this Unbound package and how its repos on apt can be missing config or key files. It's easy to be left with neither a running systemd-resolved service not a working Unbound resolver.
$ delv mysite.org
;; broken trust chain resolving 'mysite.org/A/IN': <IP_ADDRESS>#53
;; resolution failed: broken trust chain

resulted from not enabling and restarting the systemd-resolved service after throwing out the misfiring Unbound.
One correction: DNSSEC isn't needed for spam rejection. Spam analysis is done based on verifying sender addresses with DKIM/SPF and keeping tracking of reputation of verified senders. Having DNSSEC doesn't (currently) play a part.
Well, DNSSEC protects against hijacked email and mail hijacking - which strictly speaking isn't spam, I admit. But if DNSSEC protects MX records, it can also offer protection to all other DNS records - including the SPF, DKIM and DMARC records that combat spam per se.
Quickstart need not explain SPF, DKIM or DMARC records to us as numerous tutorials exist on how to create and edit these. It is unlikely that anyone unfamiliar with these records would be trialling a new mail server like Mox. (But it's thoughtful of Mox to offer us a nice choice of DKIM keys !)
Look, I don't want to be overly critical of your initiative here. You've done a lot of unpaid private time work on this project. It's towards the goal of secure and manageable self-hosted email. Without the awkwardness of coordinating 4 separate packages like Postfix/Exam, Dovecot, SpamAssassin & Roundcube. And without the likely loss of privacy by using a pre-packaged & pre-configured version of the same agglomerate, e.g. iRedMail, DockerMail, MailCow, etc.
But proper user guidance documents (no dry definitions, please) have an important role to play in the testing and adoption by users of Mox - and, since Mox depends a lot on Unbound, we all need better user guides on the latter package too.

I'm using Ubuntu 22.04 LTS.
But don't worry on providing guidance on Mox for Ubuntu.
My issue is principally with Unbound repos and seeing if my ISP allows DNS querying - something beyond Mox's scope.
I'll report back in due course if I progress this.

if Unbound is challenging to use, using a DNS resolver that supports DNSSEC, such as Cloudflare DNS or Quad9, would be enough for most situations.

If Unbound is challenging to use, . . .
It's actually a problem of getting an Unbound version installed that contains an unbound.conf file !
The discussion with NLNet's Overeinder didn't go well as he refuses to accept that Unbound 1.13.1 lacks any files . . . The fault, he thinks, must lie elsewhere - either with apt, the user's Ubuntu installation, the user themselves, etc.
There is talk that Ubuntu 24.04 LTS will include Unbound 1.19 - I am not sure if it is to be the default resolver or not - we will soon see !
I will look into your alternatives.
WARNING: It looks like the DNS resolvers configured on your system do not
verify DNSSEC, or aren't trusted (by having loopback IPs or through "options
trust-ad" in /etc/resolv.conf).  Without DNSSEC, outbound delivery with SMTP
used unprotected MX records, and SMTP STARTTLS connections cannot verify the TLS
certificate with DANE (based on a public key in DNS), and will fall back to
either MTA-STS for verification, or use "opportunistic TLS" with no certificate
verification.
Recommended action: Install unbound, a DNSSEC-verifying recursive DNS resolver,
ensure it has DNSSEC root keys (see unbound-anchor), and enable support for
"extended dns errors" (EDE, available since unbound v1.16.0). Test with
"dig com. ns" and look for "ad" (authentic data) in response "flags".
cat </etc/unbound/unbound.conf.d/ede.conf
server:
ede: yes
val-log-level: 2
EOF
Looking up IPs for hostname mail.sandbarsoftware.ie...
NOTE: It looks like the DNS records of your domain (zone) are not DNSSEC-signed.
Mail servers that send email to your domain, or receive email from your domain,
cannot verify that the MX/SPF/DKIM/DMARC/MTA-STS records they receive are
authentic. DANE, for authenticated delivery without relying on a pool of
certificate authorities, requires DNSSEC, so will not be configured at this
time.
Recommended action: Continue now, but consider enabling DNSSEC for your domain
later at your DNS operator, and adding DANE records for protecting incoming
messages over SMTP.
Checking if outgoing smtp connections can be made by connecting to gmail.com mx on port 25... OK
Checking whether host name IPs are listed in popular DNS block lists... OK
creating file "config/adminpasswd": open config/adminpasswd: file exists
/home/mox# dig _443._tcp.sandbarsoftware.ie
; <<>> DiG 9.18.24-0ubuntu<IP_ADDRESS>-Ubuntu <<>> _443._tcp.sandbarsoftware.ie
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63884
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;_443._tcp.sandbarsoftware.ie.	IN	A
;; AUTHORITY SECTION:
sandbarsoftware.ie.	60	IN	SOA	dns108.ovh.net. tech.ovh.net.<PHONE_NUMBER> 86400 3600 3600000 60
;; Query time: 20 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>) (UDP)
;; WHEN: Mon Jul 15 11:36:28 IST 2024
;; MSG SIZE  rcvd: 112
`

I have quad9 (<IP_ADDRESS>) as my remote resolver.
I have a TLSA record on my domain name.
Still I get issues:
/home/mox# ./mox quickstart<EMAIL_ADDRESS>Checking if DNS resolvers are DNSSEC-verifying...

WARNING: It looks like the DNS resolvers configured on your system do not
verify DNSSEC, or aren't trusted (by having loopback IPs or through "options
trust-ad" in /etc/resolv.conf).  Without DNSSEC, outbound delivery with SMTP
used unprotected MX records, and SMTP STARTTLS connections cannot verify the TLS
certificate with DANE (based on a public key in DNS), and will fall back to
either MTA-STS for verification, or use "opportunistic TLS" with no certificate
verification.

Recommended action: Install unbound, a DNSSEC-verifying recursive DNS resolver,
ensure it has DNSSEC root keys (see unbound-anchor), and enable support for
"extended dns errors" (EDE, available since unbound v1.16.0). Test with
"dig com. ns" and look for "ad" (authentic data) in response "flags".

cat <<EOF >/etc/unbound/unbound.conf.d/ede.conf
server:
    ede: yes
    val-log-level: 2
EOF

Looking up IPs for hostname mail.sandbarsoftware.ie...

NOTE: It looks like the DNS records of your domain (zone) are not DNSSEC-signed.
Mail servers that send email to your domain, or receive email from your domain,
cannot verify that the MX/SPF/DKIM/DMARC/MTA-STS records they receive are
authentic. DANE, for authenticated delivery without relying on a pool of
certificate authorities, requires DNSSEC, so will not be configured at this
time.
Recommended action: Continue now, but consider enabling DNSSEC for your domain
later at your DNS operator, and adding DANE records for protecting incoming
messages over SMTP.

Checking if outgoing smtp connections can be made by connecting to gmail.com mx on port 25... OK
Checking whether host name IPs are listed in popular DNS block lists...
WARNING: checking your public IP <IP_ADDRESS> in DNS block list sbl.spamhaus.org: fail Error: open resolver; https://check.spamhaus.org/returnc/pub/<IP_ADDRESS>/
Other mail servers are likely to reject email from IPs that are in a blocklist.
If all your IPs are in block lists, you will encounter problems delivering
email. Your IP may be in block lists only temporarily. To see if your IPs are
listed in more DNS block lists, visit:

- https://multirbl.valli.org/lookup/<IP_ADDRESS>.html

creating file "config/adminpasswd": open config/adminpasswd: file exists
root@mail:/home/mox#

@corinthian13 What is in your /etc/resolv.conf? If you're using a non-local resolver (IP), the "ad"-flag isn't trusted. You would need a line with "options edns0 trust-ad" in /etc/resolv.conf.
As for the error about config/adminpasswd: You already ran the quickstart in that directory. Mox is careful not to overwrite previous files (consider what happens if you accidentially ran "mox quickstart" in the directory with your existing mox install). While you're still setting up, you can just remove the previously generated files before running the quickstart again. But this is another reason why having an interactive setup will be helpful.

Another note (also mentioned in other issues about DNS-related problems, and in the already committed diff referenced above): You can check the actual DNSSEC status as mox sees it with "mox dns lookup ...", for example:
$ mox dns lookup mx ueber.net
mx records (1, with dnssec):
- mail.axillis.nl., preference 10

What is in your /etc/resolv.conf? If you're using a non-local resolver (IP), the "ad"-flag isn't trusted. You would need a line with "options edns0 trust-ad" in /etc/resolv.conf.
GNU nano 6.2                                 resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
# <IP_ADDRESS> is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
nameserver <IP_ADDRESS>
search openstacklocal

Another note (also mentioned in other issues about DNS-related problems, and in the already committed diff referenced above): You can check the actual DNSSEC status as mox sees it with "mox dns lookup ...",
/home/mox# sudo mox dns lookup mx sandbarsoftware.ie
sudo: mox: command not found

That /etc/resolv.conf shows you're using 3 nameservers. This doesn't look intentional... It also explains why the AD flag isn't used: There is no trust-ad option. But I wouldn't recommend adding option trust-ad for DNS requests over the public internet (the ad bit isn't protected in transit).
That "mox dns lookup" error should be easy to fix. Give it a try, you can do it. You don't even have to run it as root.

That "mox dns lookup" error should be easy to fix. Give it a try, you can do it. You don't even have to run it as root.
It's clear that you are in the wrong directory or using the wrong title for the command.
I'll let you unravel the puzzles in getting after the folder holding commands in Mox.


README updates for v1

Changes in behavior from the ODBC based sqlcmd

We're still missing :XML [On]|[Off]
The missing switches are listed at https://github.com/microsoft/go-sqlcmd/discussions/292, it might be worthwhile to add a link that list.

Refers to: README.md:113 in 3167070. [](commit_id = 3167070f0dd8028f94d2cd0c5e92cdda5d48150e, deletion_comment = False)

Changes in behavior from the ODBC based sqlcmd

We're still missing :XML [On]|[Off] The missing switches are listed at #292, it might be worthwhile to add a link that list.
Refers to: README.md:113 in 3167070. [](commit_id = 3167070, deletion_comment = False)

Added


[SPARK-43802][SQL] Fix codegen for unhex and unbase64 with failOnError=true

What changes were proposed in this pull request?

Fixes an error with codegen for unhex and unbase64 expression when failOnError is enabled introduced in https://github.com/apache/spark/pull/37483.
Why are the changes needed?

Codegen fails and Spark falls back to interpreted evaluation:
Caused by: org.codehaus.commons.compiler.CompileException: File 'generated.java', Line 47, Column 1: failed to compile: org.codehaus.commons.compiler.CompileException: File 'generated.java', Line 47, Column 1: Unknown variable or type "BASE64"

in the code block:
/* 107 */         if (!org.apache.spark.sql.catalyst.expressions.UnBase64.isValidBase64(project_value_1)) {
/* 108 */           throw QueryExecutionErrors.invalidInputInConversionError(
/* 109 */             ((org.apache.spark.sql.types.BinaryType$) references[1] /* to */),
/* 110 */             project_value_1,
/* 111 */             BASE64,
/* 112 */             "try_to_binary");
/* 113 */         }

Does this PR introduce any user-facing change?

Bug fix.
How was this patch tested?

Added to the existing tests so evaluate an expression with failOnError enabled to test that path of the codegen.

+1, LGTM. Merging to master/3.4.
Thank you, @Kimahriman.

@Kimahriman The changes cause conflicts in branch-3.4. Could you backport your changes to 3.4, please.
Just in case, does branch-3.3 has the same issue? If so, please, backport the changes to 3.3 too.

Just in case, does branch-3.3 has the same issue? If so, please, backport the changes to 3.3 too.

No this was added in 3.4, though there was talks of potentially backporting the original PR with the issue https://github.com/apache/spark/pull/37483. I'll make the 3.4 backport PR.


Compile with WASM

On non-X86 (tested with Web Assembly), this fixes not compiling.  It uses the cfg() attribute, rather than the cfg! macro.  This should also make it easier to add SIMD support for more targets - just add another macro.

Instead of the negative "no-simd" feature, can we change it to "use-simd" (default) to avoid confusing double-negatives?

Done.


Eric devbranch

Added some of the requirements that Ben listed earlier in a text file, and created the boilerplate code for a Tk app with python in pycharm.

Approved.


[SourceKit] Fix flakey completion tests

A previous change updated the checkdep tests to move the sleep before
copying over files. This fixed cases where the modification time would
be the same second as the dependency check. Unfortunately this
introduced a slightly different form of flakiness - if the sleep went
too long, the completion that was meant to re-use the AST would see that
it's time to check dependencies and thus skip the fast completion path.
One fix for that would be to add a smaller sleep before, a longer sleep
after, and increase the dependency check time. That increases the
runtime of the tests even further though, so instead just update the
timestamps manually to be in the past/future in order to invoke the path
we want to test. This also allows a 0 dependency check time (ie. always
check), which makes the tests even faster.
Resolves rdar://71861446

Note: I'm aware this does slightly change what the tests are checking. Given that it's just checking the times against now() though, it is roughly the same - just changing one rather than the other (ie. changing file time rather than current time, if that makes sense).
Another alternative is to keep the sleeps but also add in the touch, ie. move the sleep after the first fast completion and put a touch in there instead.
Let me know which you'd prefer!
@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - e13d800b10cfbc2cf928a0a7da62fbba3f917252

Changed the timestamps to 2100 rather than 3020. Nanoseconds since 1970 stored as a 64 bit signed integer only allows up to 2262.
@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 34ff514ab19cdf9725fa8679e8288daa5f127c86

@swift-ci please test OS X platform


Multimedia Integration in pages

Pages should be able to load multimedia functionality based on information retrieved from the backend in the page_info API call.

We have not been able to actually pull this data from the database. The capability exists but we have not actually used it in any scenario.


<EMAIL_ADDRESS>depends on to-iso-string

When I upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>I fail with

eric@mouni2:/tmp/checkouts/shex.js$ npm test

><EMAIL_ADDRESS>test /tmp/checkouts/shex.js
> mocha -C -R dot

module.js:327
    throw err;
    ^

Error: Cannot find module 'to-iso-string'
    at Function.Module._resolveFilename (module.js:325:15)
    at Function.Module._load (module.js:276:25)
    at Module.require (module.js:353:17)
    at require (internal/module.js:12:17)
    at Object. (/tmp/checkouts/shex.js/node_modules/mocha/lib/utils.js:15:19)
    at Module._compile (module.js:409:26)
    at Object.Module._extensions..js (module.js:416:10)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Module.require (module.js:353:17)
npm ERR! Test failed.  See above for more details.

I see
"to-iso-string": "0.0.2"
in devDependencies but not dependencies.

+1

+1

Here is the error as caught by travis

short term solution is to npm install to-iso-string

The issue is that "to-iso-string" ist a dev dependency instead of dependency.

It will be fixed
https://github.com/mochajs/mocha/commit/bd9450b9e5522cb8d89abc926a754752dc697b39

@aivus How long for build? Can one check progress somewhere?

thx @aivus for pushing a quick fix

btw, is npm slow to you? https://www.npmjs.com/package/mocha at the moment is taking ages to load

@Levino @DinisCruz published https://github.com/mochajs/mocha/releases/tag/v2.5.1

fixed in 2.5.1

sorry!

@boneskull no probs, all fixed now


Default path name is incorrect

Loading Minecraft client shows:
Using default value of /Users/arunguptamachine/machines/default
Make sure proper path name is displayed.

Fixed


[BUG] dependency error with flutter_drive and crypto

Describe the bug
I get an dependency error with google_fonts 2.0.0 and flutter_drive
When I try to get dependencies with google_fonts ^2.0.0 and flutter_drive I get the next unmatch dependency error
Because every version of flutter_driver from sdk depends on crypto 2.1.5 and google_fonts >=2.0.0-nullsafety.0 depends on crypto ^3.0.0, flutter_driver from sdk is incompatible with google_fonts >=2.0.0-nullsafety.0.
So, because rae_test depends on both google_fonts ^2.0.0 and flutter_driver any from sdk, version solving failed.
pub get failed (1; So, because rae_test depends on both google_fonts ^2.0.0 and flutter_driver any from sdk, version solving failed.)

I"m also getting the same error.

So am I.

Since flutter_driver from the current stable release uses 3.0.1, this issue can be closed


New version: Tencent.QQ version <IP_ADDRESS>276

This pull request is automatically generated by 🥟 Dumplings in #2962
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

12/25/2023 1:18:16 PM
Installer Verification Analysis Context Information:
Installer https://dldir1v6.qq.com/qqfile/qq/PCQQ9.7.21/QQ<IP_ADDRESS>276.exe
Scan request id: '0cfc0ea4-aaed-415a-9ab9-c3f8b4c64d06'
Error information: BlockingDetectionFound

Hi @SpecterShell,
Is there a different URL for this package?

12/29/2023 4:14:03 AM
Installer Verification Analysis Context Information:
Installer https://dldir1.qq.com/qqfile/qq/PCQQ9.7.21/QQ<IP_ADDRESS>276.exe
Scan request id: '1ce5294d-cfa3-4fce-9deb-b0a1c632a526'
Error information: BlockingDetectionFound


libp2p peerstore prevents gaining peers fast

Describe the bug
Restarting a Lodestar beacon node after running for a while, it takes extremely long to gain peers to target_peers. We now that this doesn't happen on runs from scratch.
I did a test in two contabo nodes:
contabo-14: rm beacon/peer-id.json
contabo-15: rm -r beacon/peerstore/
contabo-14: 2 min latter: 0 peers, 10 min latter 3 peers
contabo-15: 2 min latter: 15 peers, 10 min latter 44 peers
Expected behavior
Having an existing peerstore should not delay gaining peers
Steps to Reproduce

Run Lodestar in Prater without peerstore and time 0 to target_peers (should be < 5 min)
Restart Lodestar and time 0 to target_peers (could be ~ 30 min)

contabo-14

contabo-15

CC: @tuyennhv should we still go for https://github.com/ChainSafe/lodestar/compare/master...dapplion/ephemeral-peerid

CC: @tuyennhv should we still go for master...dapplion/ephemeral-peerid

yeah I'm fine with creating new peer id upon restart (used to do that manually a lot of times), go ahead unless @wemeetagain has some information regarding discv5

Should be fine

Still observing this. The node appears to try to dial to the same peer over and over

tested with v1.3.0/080b73b on a ctvpss node
1st time:

Remove peerstore, node gets to targetPeers in 22 minutes
Restart node, node gets to targetPeers in 9 minutes
Restart node, node gets to targetPeers in 12 minutes

2nd time:

Remove peerstore, node gets to targetPeers in 25 minutes
Restart node, node gets to targetPeers in 23 minutes
Restart node, node gets to targetPeers in 19 minutes

==> keeping peerstore even helps gaining peers faster

Still observing this. The node appears to try to dial to the same peer over and over

fixed in https://github.com/ChainSafe/lodestar/pull/4969


Word-count example

Example for an easy understanding of SpaRkTA

HierarchyBucket is useful for this example?

HierarchyBucket buckets by tails or by heads: For example for the string "www.stratio.com" will bucket by tails

www.stratio.com
stratio.com
com

I believe we could make a similar Bucketer for the word-count

Finally I make one operator for this issue.


how would I set a click event on bar's label?

One-line summary [问题简述]
Version & Environment [版本及环境]

ECharts version [ECharts 版本]:
Browser version [浏览器类型和版本]:
OS Version [操作系统类型和版本]:

Expected behaviour [期望结果]
ECharts option [ECharts配置项]

option = {

}

Other comments [其他信息]

Currently this is not supported. We are considering to add this feature.
See discussion at<EMAIL_ADDRESS>


Edimax SP-1101 doesn't get displayed

Make sure you run the latest version before reporting an issue. Feature requests should go in the forum: https://community.home-assistant.io/c/feature-requests
Home Assistant release (hass --version):
0.20.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
edimax.py
Description of problem:
Edimax SP-1101 doesn't get displayed in the web interface
Expected:
Get's displayed as a switch
Problem-relevant configuration.yaml entries and steps to reproduce:
switch:
  - platform: edimax
    host: 172.16.###.###
    username: ####
    password: ####
    name: Smart Plug 1

If I comment the lines for today power and current power, it gets displayed as a switch.
If these lines are uncommented, how they should be, the switch is not shown on the web ui.
Traceback (if applicable):
no errors
Additional info:

Problem is solved


The microcontroller module seems not to be in this circuitpython firmware build

I've not managed to get this demo to run yet, but in the process of debugging and checking the library imports I spotted:
>>> import microcontroller
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: no module named 'microcontroller'

All the other imports in game.py worked fine.
I also went through the  format.uf2 and firmware.uf2 troubleshooting steps to re-flash in case there was a new version of CircuitPython but still has the same error (it's still 2.2.0-rc1-9-g2523b559b, Adafruit are currently on 2.3.1).

Ouch, looks like I used a feature that has only been introduced in CircuitPython 3.0, sorry about that. I will need to revert that.


Support python3.6

Resolves #180
I manually attempted build_manylinux_wheels (by commenting out non 3.6 to make it faster).  I needed to run docker pull quay.io/pypa/manylinux1_x86_64:latest beforehand to get the latest docker image.
I made the executive decision to drop testing of python3.3 ;)  we don't provide releases for it and don't have any custom code for it - it will still probably continue to work but we won't actively support it.

I added the python3.6 manylinux wheel to the previous release

Coverage remained the same at 94.454% when pulling 90a492017cece1bb3155119404ee1729413d1798 on python36 into 7a24cc538b050a0fbd55ec0615045bf16719f7ab on master.


Add eslint-plugin-toplevel

This is a cool idea. Do you mind fixing the conflicts? I apologize for taking so long to see this pull request.

Thank you!


Optional mTLS client certificate metadata verification

A short explanation of the proposed change:

We want to add optional mTLS client certificate metadata verification in addition to the issuer CA validity checks.
Given a particular signing CA (identified by its subject) we want to limit the allowed client certificate subjects that are allowed to send requests.
While the underlying issue is better solved with changes to the PKI and trust relationship between CAs, the PKI or its use by other sub-entities is not always under the control of the operator.

An explanation of the use cases your change solves

The use case is an upstream proxy managed by a different entity that uses a widely spread private CA for issuing its certificates.
We want to avoid that every user of that CA is able to issue requests to Gorouter, while still explicitly allowing the upstream proxy and its CA certificates, which are short-lived and need rotation.
In the specific use case, we have a CA that controls, which certificates are issued for specific sub-entities, which are clearly identified in the certificate's subject DN.

Instructions to functionally test the behavior change using operator interfaces (BOSH manifest, logs, curl, and metrics)

e.g. configuration in routing-release:
router:
  verify_client_certificate_metadata:
    - ca_subject:
        common_name: Some Root CA
        country:
          - DE
      valid_subjects:
        - common_name: Awesome Service 1
          organizational_units:
            - sub-entity4
          organizations:
            - Acme, Inc.
          country:
            - US
        - common_name: Awesome Service 2
          organizational_units:
            - sub-entity7
          organizations:
            - Acme, Inc.
          country:
            - US

Send a request using a client certificate that is signed by a CA that is configured in client_ca_certs:
but not in the explicit allowed subjects, configured in verify_client_certificate_metadata::curl --cacert other-department-5.pem https://app.cf.example.com

Send a request using a client certificate that is signed by a CA that is configured in client_ca_certs:
and in the allowed subjects, configured in verify_client_certificate_metadata::curl --cacert awesome-service-2.pem https://app.cf.example.com

Expected result after the change

The request fails with a TLS handshake error. Gorouter logs the certificate subject and the fact that this certificate was not allowed.
succeeds, as desired.

Current result before the change

The request passes through without TLS handshake errors, allows access to a different party that should not have access.
succeeds, as desired.

Links to any other associated PRs

[x] I have viewed signed and have submitted the Contributor License Agreement

[x] I have made this pull request to the main branch

[x] I have run all the unit tests.

[ ] (Optional) I have run Routing Acceptance Tests and Routing Smoke Tests

[ ] (Optional) I have run CF Acceptance Tests

@ameowlia thanks so much for this thoughtful and thorough review. We'll address the points. Fully agree on having a check in the spec ERB template / at template generation time.

@ameowlia Could you have another look?
I've updated this PR addressing all comments and provided the companion PR for routing release: https://github.com/cloudfoundry/routing-release/pull/355