Failure of exhaustiveness checker when matching on Exception

Prerequisites
Please put an X between the brackets as you perform the following steps:

[X] Check that your issue is not already filed:
https://github.com/leanprover/lean4/issues
[X] Reduce the issue to a minimal, self-contained, reproducible test case.
Avoid dependencies to Mathlib or Batteries.
[X] Test your test case against the latest nightly release, for example on
https://live.lean-lang.org/#project=lean-nightly
(You can also use the settings there to switch to “Lean nightly”)

Description
MWE:
import Lean

open Lean

example (e : Exception) : True :=
  match e with
  | .internal .. => sorry
  | .error .. => sorry

-- missing cases:
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofSyntax _)) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofInt (Int.negSucc _))) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofInt (Int.ofNat _))) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofNat _)) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofName _)) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofBool true)) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofBool false)) _)))
-- (@Exception.internal _ (KVMap.mk (List.cons (Prod.mk _ (DataValue.ofString (String.mk _))) _)))

Versions
"4.10.0-nightly-2024-06-24"
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

The issue here is that Exception.internal has a default argument.
inductive Exception where
  | error (ref : Syntax) (msg : MessageData)
  | internal (id : InternalExceptionId) (extra : KVMap := {})

Thus, .internal .. is equivalent to .internal _ {}. Possible solutions:

A better error message.
Modify the meaning of ...

Workaround.
import Lean

open Lean

example (e : Exception) : True :=
  match e with
  | .internal _ _ => sorry
  | .error .. => sorry

Ah, it's the default argument! I understand .. as "ignore all other arguments", so I would prefer if there was no distinction between arguments with and without a default value.


Acquire 'csse_covid_19_daily_reports_us'

Acquire 'csse_covid_19_daily_reports_us', and merge the USA data with 'daily report' model. The reason for doing such is because currently USA data in a daily report is NOT accurately presented (e.g., recovered, etc.)

https://github.com/CSSEGISandData/COVID-19/tree/master/csse_covid_19_data/csse_covid_19_daily_reports_us

https://github.com/CSSEGISandData/COVID-19/tree/master/csse_covid_19_data/csse_covid_19_daily_reports

There's already a 'recovered' represented in a row for 'US' and 'CANADA'; therefore, acquiring a new file is not necessary.


line 47

Start: 0
Traceback (most recent call last):
File "google.py", line 2, in
response = GoogleSearch().search("something")
File "C:\Users\ageorge\PycharmProjects\google\venv\lib\site-packages\googlesearch\googlesearch.py", line 47, in search
totalText = soup.select(GoogleSearch.TOTAL_SELECTOR)[0].children.next().encode('utf-8').decode('utf-8')
IndexError: list index out of range

line 47
totalText = soup.select(GoogleSearch.TOTAL_SELECTOR)[0].children.next().encode('utf-8').decode('utf-8')

totalText = soup.select(GoogleSearch.TOTAL_SELECTOR)[0].children.next().encode('utf-8').decode('utf-8')
IndexError: list index out of range


Add experiences timeline widget

As discussed in #35 this is a PR to add a widget for a list of experiences containing title, organization, dates, location. Here are some example screenshots of the widget right now.
Widget background is primary in this case.

Widget background is secondary in this case.

Features I could add:

Adding a draft=true/false for each experience, allowing the hugo theme user to write all their experiences in the experiences.md page and selecting whichever they want to show/hide.
Adding a different style where it could just be listed in a plain format without the cards.
Adding an option to show Featured Images for each experiences

I have no idea how to do featured images in the front matter for each entries in front matter of experiences.md
I don't know how to use utils/get-featured.html for featured images typed in an entry of the front matter.

Features that I omitted (for now?):

Maximum number of experiences to show, pagination, etc.

The user will have to manually manage which to experiences to show.

FontAwesome icons for the Organization, Dates, and Location

I think it looks good and clean without the icons.

Direct Questions:

Right now the example experiences widget is at the bottom of the homepage, below the vintage widget. Any preference to the ordering of the widgets on the homepage?
Any feedback on style/look of the widget?
Any feedback on code?
Any tips for the features I might want to add?

@wangchucheng Here's the screenshot where the above card is with the fixed/adjusted style and using mr-4 and the bottom is an altered version.
Top:

{{ .title }}

 {{ .organization | markdownify }}

     {{ .dates | markdownify }}
     {{ .location | markdownify }}

Bottom:

{{ .title }}

     {{ .organization | markdownify }}
     {{ .dates | markdownify }}
     {{ .location | markdownify }}

If you mean to left justify the organization, and right justify the date and location that's also something we can try. Do you know how to do that with HTML/CSS? I'm not quite sure how to do so.

@wangchucheng Here's the screenshot where the above card is with the fixed/adjusted style and using mr-4 and the bottom is an altered version.
Top:

{{ .title }}

 {{ .organization | markdownify }}

     {{ .dates | markdownify }}
     {{ .location | markdownify }}

Bottom:

{{ .title }}

     {{ .organization | markdownify }}
     {{ .dates | markdownify }}
     {{ .location | markdownify }}

If you mean to left justify the organization, and right justify the date and location that's also something we can try. Do you know how to do that with HTML/CSS? I'm not quite sure how to do so.

If you mean to left justify the organization, and right justify the date and location that's also something we can try.

Yes, that's what I mean. You can use flex and justify-between to implement this. See Justify Content for more details.

If you mean to left justify the organization, and right justify the date and location that's also something we can try.

Yes, that's what I mean. You can use flex and justify-between to implement this. See Justify Content for more details.

@wangchucheng Here's how I implemented it and here's the screenshot.
The third code is:

{{ .title }}

         {{ .organization | markdownify }}

 {{ .dates | markdownify }}

 {{ .location | markdownify }}

I personally like the first or the second one.

@wangchucheng Here's how I implemented it and here's the screenshot.
The third code is:

{{ .title }}

         {{ .organization | markdownify }}

 {{ .dates | markdownify }}

 {{ .location | markdownify }}

I personally like the first or the second one.

What I mean is to right justify the date and location together. Maybe like this:

{{ .title }}

         {{ .organization | markdownify }}

 {{ .dates | markdownify }}

 {{ .location | markdownify }}

What I mean is to right justify the date and location together. Maybe like this:

{{ .title }}

         {{ .organization | markdownify }}

 {{ .dates | markdownify }}

 {{ .location | markdownify }}

Thank you for the code! That helped me out understand it better. Here's 3 more styles!
Style 4 - (code you have above)
Style 5 - Location and date right justified.

{{ .title }}

         {{ .organization | markdownify }}

             {{ .dates | markdownify }}
             {{ .location | markdownify }}

Style 6 - Organization and location left justified, dates right justified.

{{ .title }}

             {{ .organization | markdownify }}
             {{ .location | markdownify }}

 {{ .dates | markdownify }}

I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.
If you agree with moving forward with Style 6, then I can probably add this to the code and we can probably do the merge tomorrow. Let me know what your preference is
By the way, do you have a preference to where the experiences.html widget should be on the homepage? I can change the weight to have it move up and down. Right now it's at the very bottom. I can leave it there if that's okay with you. Or I can move it just above vintage.

Thank you for the code! That helped me out understand it better. Here's 3 more styles!
Style 4 - (code you have above)
Style 5 - Location and date right justified.

{{ .title }}

         {{ .organization | markdownify }}

             {{ .dates | markdownify }}
             {{ .location | markdownify }}

Style 6 - Organization and location left justified, dates right justified.

{{ .title }}

             {{ .organization | markdownify }}
             {{ .location | markdownify }}

 {{ .dates | markdownify }}

I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.
If you agree with moving forward with Style 6, then I can probably add this to the code and we can probably do the merge tomorrow. Let me know what your preference is
By the way, do you have a preference to where the experiences.html widget should be on the homepage? I can change the weight to have it move up and down. Right now it's at the very bottom. I can leave it there if that's okay with you. Or I can move it just above vintage.

I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.

Yes, Style 6 is the best I think! And for the org link, how about the following config?
[organization]
  name = "Example Organization"
  url = "https://example.com/"

I can move it just above vintage.

Yes, I agree with that.
And do you mind improve the documentation of this part? The docs is at Hugo Eureka Docs. You can just wirte the English version and I will translate it to Chinese.

I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.

Yes, Style 6 is the best I think! And for the org link, how about the following config?
[organization]
  name = "Example Organization"
  url = "https://example.com/"

I can move it just above vintage.

Yes, I agree with that.
And do you mind improve the documentation of this part? The docs is at Hugo Eureka Docs. You can just wirte the English version and I will translate it to Chinese.

Perfect!! Thank you for all the help. That format for the organization looks good! I'll put that in and let you know once its all good for review. Should be tomorrow.
And about the docs of course, no problem! I'll make sure to add docs for this widget.
Thanks again!
-------- Message d'origine --------
Le 27 janv. 2021 00 h 36, C. Wang <<EMAIL_ADDRESS>> a écrit :
I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.
Yes, Style 6 is the best I think! And for the org link, how about the following config?
[organization] name = "Example Organization" url = "https://example.com/"
I can move it just above vintage.
Yes, I agree with that.
And do you mind improve the documentation of this part? The docs is at Hugo Eureka Docs. You can just wirte the English version and I will translate it to Chinese.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.￼
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "[https://github.com](https://github.com/wangchucheng/hugo-eureka/pull/37#issuecomment-768068480", "url": "[https://github.com](https://github.com/wangchucheng/hugo-eureka/pull/37#issuecomment-768068480", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Perfect!! Thank you for all the help. That format for the organization looks good! I'll put that in and let you know once its all good for review. Should be tomorrow.
And about the docs of course, no problem! I'll make sure to add docs for this widget.
Thanks again!
-------- Message d'origine --------
Le 27 janv. 2021 00 h 36, C. Wang <<EMAIL_ADDRESS>> a écrit :
I really like Style 6 (the bottom one in the above screenshot)! I like the one line look! With the organization and location together since it makes sense for that information to be together.
Yes, Style 6 is the best I think! And for the org link, how about the following config?
[organization] name = "Example Organization" url = "https://example.com/"
I can move it just above vintage.
Yes, I agree with that.
And do you mind improve the documentation of this part? The docs is at Hugo Eureka Docs. You can just wirte the English version and I will translate it to Chinese.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.￼
[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "[https://github.com](https://github.com/wangchucheng/hugo-eureka/pull/37#issuecomment-768068480", "url": "[https://github.com](https://github.com/wangchucheng/hugo-eureka/pull/37#issuecomment-768068480", "name": "View Pull Request" }, "description": "View this Pull Request on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Thank you! How about if we change mr-4 to mr-2 for organization and/or add a separator like · between them?
And we can also remove mr-4 for dates.

{{ .title }}

                         {{ .organization | markdownify }}
                         {{ .location | markdownify }}

 {{ .dates | markdownify }}

Thank you! How about if we change mr-4 to mr-2 for organization and/or add a separator like · between them?
And we can also remove mr-4 for dates.

{{ .title }}

                         {{ .organization | markdownify }}
                         {{ .location | markdownify }}

 {{ .dates | markdownify }}

Here are the changes, though there is an issue with smaller screen widths (e.g. mobile). Screenshots below.
Changes/Updates are the following: I added the seperator and spacing. I also added an option in the front matter to hide the specific experience entry if the user specifies (e.g. makes it easier to highlight which employment history is shown). I also added the organization name and url hyperlinking.
I don't know how to fix how the separator sometimes overflowing on smaller screens. There's also some issues with the location text being too close to the dates. I tried playing around with size breakpoints, hidden to deal with the separator issue but I couldn't get it to work. I was thinking maybe it could be
 on mobile, and at the sm: size breakpoint it could become a  like normal.
Normal Width

Smaller Width

Here are the changes, though there is an issue with smaller screen widths (e.g. mobile). Screenshots below.
Changes/Updates are the following: I added the seperator and spacing. I also added an option in the front matter to hide the specific experience entry if the user specifies (e.g. makes it easier to highlight which employment history is shown). I also added the organization name and url hyperlinking.
I don't know how to fix how the separator sometimes overflowing on smaller screens. There's also some issues with the location text being too close to the dates. I tried playing around with size breakpoints, hidden to deal with the separator issue but I couldn't get it to work. I was thinking maybe it could be
 on mobile, and at the sm: size breakpoint it could become a  like normal.
Normal Width

Smaller Width

I have pushed a commit (c159ee9) to make it responsive.
And I think we can remove hide_entry Because people can just comment those experiences.
For the organization, do you think it is a good idea to use:
[organization]
  name = "Example Organization"
  url = "https://example.com/"

instead of:
    organization_name = "Example Organization 2"
    organization_url = ""

The first one is consistent with the form in about widget, but the drawback is that it may only be placed at the bottom to avoid parsing errors.

I have pushed a commit (c159ee9) to make it responsive.
And I think we can remove hide_entry Because people can just comment those experiences.
For the organization, do you think it is a good idea to use:
[organization]
  name = "Example Organization"
  url = "https://example.com/"

instead of:
    organization_name = "Example Organization 2"
    organization_url = ""

The first one is consistent with the form in about widget, but the drawback is that it may only be placed at the bottom to avoid parsing errors.

Thank you for the commit to make it responsive. It looks good!

And I think we can remove hide_entry Because people can just comment those experiences.

Okay, we can remove hide_entry. That's no problem! I removed it.

Btw, I prefer .Params.something instead of $.Param "something". Although they are alomst the same.

Yeah that's fine. I'm new to Hugo so I wasn't sure how that worked. I changed it now.

[organization]
name = "Example Organization"
url = "https://example.com/"

the drawback is that it may only be placed at the bottom to avoid parsing errors

Personally, I would prefer that we stay with organization_name and organization_url. I see a few possible downsides:

Having the organization info "far away" from the rest of entry information (writeup, location, etc.) is cumbersome/non-intuitive to the hugo theme user.
Handling multiple organizations in the widget file might be an issue? I'm not sure how multiple organizations work with `[organization]', where the first entry has Organization A, and second entry has Organization B and so on.

While it's not a same style as the about.md file, I think the organization_name and organization_url is still easy/intuitive for users to understand.
Furthermore I don't want us to make the transition from toml to yaml since thats a change that seems like it should apply to all .md files. It feels too big of change and outside the scope of this PR. I think this widget is pretty much ready now for merging if that's okay with you. (The transition to yaml could be made in the future.)

Thank you for the commit to make it responsive. It looks good!

And I think we can remove hide_entry Because people can just comment those experiences.

Okay, we can remove hide_entry. That's no problem! I removed it.

Btw, I prefer .Params.something instead of $.Param "something". Although they are alomst the same.

Yeah that's fine. I'm new to Hugo so I wasn't sure how that worked. I changed it now.

[organization]
name = "Example Organization"
url = "https://example.com/"

the drawback is that it may only be placed at the bottom to avoid parsing errors

Personally, I would prefer that we stay with organization_name and organization_url. I see a few possible downsides:

Having the organization info "far away" from the rest of entry information (writeup, location, etc.) is cumbersome/non-intuitive to the hugo theme user.
Handling multiple organizations in the widget file might be an issue? I'm not sure how multiple organizations work with `[organization]', where the first entry has Organization A, and second entry has Organization B and so on.

While it's not a same style as the about.md file, I think the organization_name and organization_url is still easy/intuitive for users to understand.
Furthermore I don't want us to make the transition from toml to yaml since thats a change that seems like it should apply to all .md files. It feels too big of change and outside the scope of this PR. I think this widget is pretty much ready now for merging if that's okay with you. (The transition to yaml could be made in the future.)

Furthermore I don't want us to make the transition from toml to yaml since thats a change that seems like it should apply to all .md files. It feels too big of change and outside the scope of this PR.

Yes! I totally agree that this transition is outside the scope of this PR. And what I intended to implement is like:
experiences:
  - title: Example Role 1
    dates: 2019 - Present
    location: Country
    organization:
        name: Example Organization 2
        url:
    writeup: >
      Donec scelerisque egestas augue at tempor. Fusce faucibus magna in.
      - Suspendisse lacinia mauris a laoreet vehicula.
      - Aenean tincidunt enim vitae ante blandit tempor.
      - Nam tincidunt diam quis lorem rutrum ullamcorper.

I think this is intuitive to theme users and can be consistent with the about widget. Sadly, this syntax is only valid in yaml.
As yaml is also a more widely used format, what I am thinking is that I will convert Eureka from toml to yaml format today or tomorrow. This format conversion will not affect existing users, because Hugo can handle both formats. After the conversion is complete, I will perform a simple code refactoring and merge this PR. What do you think of this method?
If you agree, I will merge this PR directly after completing these operations. If you have other ideas, we can continue the discussion here. In addition, I will be very grateful if you can provide the corresponding documentation for the widget when you have time. Thank you for your contribution!

Furthermore I don't want us to make the transition from toml to yaml since thats a change that seems like it should apply to all .md files. It feels too big of change and outside the scope of this PR.

Yes! I totally agree that this transition is outside the scope of this PR. And what I intended to implement is like:
experiences:
  - title: Example Role 1
    dates: 2019 - Present
    location: Country
    organization:
        name: Example Organization 2
        url:
    writeup: >
      Donec scelerisque egestas augue at tempor. Fusce faucibus magna in.
      - Suspendisse lacinia mauris a laoreet vehicula.
      - Aenean tincidunt enim vitae ante blandit tempor.
      - Nam tincidunt diam quis lorem rutrum ullamcorper.

I think this is intuitive to theme users and can be consistent with the about widget. Sadly, this syntax is only valid in yaml.
As yaml is also a more widely used format, what I am thinking is that I will convert Eureka from toml to yaml format today or tomorrow. This format conversion will not affect existing users, because Hugo can handle both formats. After the conversion is complete, I will perform a simple code refactoring and merge this PR. What do you think of this method?
If you agree, I will merge this PR directly after completing these operations. If you have other ideas, we can continue the discussion here. In addition, I will be very grateful if you can provide the corresponding documentation for the widget when you have time. Thank you for your contribution!

I really like that new format in yaml. I think that would be great for users!

After the conversion is complete, I will perform a simple code refactoring and merge this PR. What do you think of this method?

Yeah that plan sounds great to me! Whenever you complete the transition, then feel free to refactor the code for experiences.html. Let me know if you run into any problems.
I'll definitely work on the documentation for the widget! I'm hoping this weekend I can put something together. Thanks again for all the help and for the theme!

I really like that new format in yaml. I think that would be great for users!

After the conversion is complete, I will perform a simple code refactoring and merge this PR. What do you think of this method?

Yeah that plan sounds great to me! Whenever you complete the transition, then feel free to refactor the code for experiences.html. Let me know if you run into any problems.
I'll definitely work on the documentation for the widget! I'm hoping this weekend I can put something together. Thanks again for all the help and for the theme!

I have merged this PR. After we finished the documentation, this feature will be available in the next release.

I have merged this PR. After we finished the documentation, this feature will be available in the next release.


Add Events(Builders Hub, International React Conf, Web3 Conf, Civo Navigate, International JavaScript Conf, React India)

I just want to add these popular events which are going to happen soon. So I would like to work on this issue and please assign this issue under GSSOC'23.

Hiii @tanishqamitra
I have assigned this issue and added labels for GSSoC. I hope you enjoy contributing to the project under GSSoC and waiting for reviewing your pr 🚀


Update RedisClient.cs

add a ScanKeys method, call base Scan method.

Looking at this now, thank you!

As a followup, could you write some unit tests that exercise the functionality that you added?


VM: Implement "Control Flow Collections"

Initially these features are behind the experimental flag control-flow-collections.

[ ] Support new block expression AST node

See:
Language tracking issue: dart-lang/language#165
Feature specification
Implementation plan

PENDING Unified Collections: dart-lang/language#200

Just for proper book-keeping, the following CL provides an initial implementation of block expressions in the Dart VM:
https://dart-review.googlesource.com/c/sdk/+/94441
This should provide a fully functional implementation to continue testing, even though it still has some issues that could be improved (e.g. for now we just disable OSR completely while running control flow collections code for simplicity; this may be unacceptable in the long run).

Current status of control flow collections tests
             control-flow
JIT        +  190 | -   76
AOT        +  190 | -   76

Some CFE CLs for if statements were submitted:
https://dart-review.googlesource.com/c/sdk/+/97200
https://dart-review.googlesource.com/c/sdk/+/97628
for-loops still pending:
https://dart-review.googlesource.com/c/sdk/+/97628

New status
             control-flow
JIT         +  203 | -   63
AOT         +  186 | -   80

Found https://github.com/dart-lang/sdk/issues/36377

Also https://github.com/dart-lang/sdk/issues/36357 and https://github.com/dart-lang/sdk/issues/36356 are blocking fuzz test runs

This morning's status:
             control-flow
JIT       +  251 | -   15
AOT       +  251 | -   15

Probably biggest VM item left to be explored is enabling OSR points inside control flow collection for loops. Alex notes we should ensure that temporaries on the expression stack are preserved when OSR happens.
Consider a more complex expression like
var x = x.bar(42, bazz(), 'abc', [more_bazz(), for (int i = 0; i < n; i++) 2*i ]);
In this case x, 42, bazz() and 'abc' should be on the expression stack unless CFE introduces temporary variables for them. Let's:
(1) test if the above example works;
(2) dump kernel to see how CFE generates this;
(3) print flowgraph of a function compiled for OSR and check that it loads captured values correctly.

If there is no more compiler backend work left to be done on this we can close the issue, a new issue can be opened to track the OSR optimization and it will not be a blocker for the 2.3 release.

Sounds good. I will do that.

Tracking OSR follow up in https://github.com/dart-lang/sdk/issues/36421
Closing this, since there is no known VM work left.


Amend #1268 with a more feasible proposal post-specialization

I took a swing at implementing the original RFC, and it became clear that it made much more sense when described as a modifier to specialization, rather that treating marker traits differently. After writing a proof of concept implementation, I believe this is the easier path forward.
Rendered

Can you repoint this at the numbered RFC, rather than the 0000 file as it is currently?
(Sorry this has been sitting in the queue for so long...)

@sgrif
But the impls do not specialize one another.

@aturon Sorry not quite sure what you're asking, you want me to rename the file? Or you want me to edit the original RFC to include these changes?

@sgrif OK, so looking at this again, I have to agree with @arielb1 that I'm a bit worried about taking this route. In particular, at various points in the implementation we make assumptions about the specialization graph, and this would introduce cycles in that graph which could cause trouble.
I think that fundamentally we're going to need some special-casing here. FWIW, I don't think the original RFC particularly needs updating, since allowing overlap is still essentially what we want (and the rest is implementation detail).
I'd be happy to work with you and @nikomatsakis on an implementation plan and help mentor the actual work; we could set up a call if you're game.
Meantime, I suggest we close this RFC.

Yeah I'd be happy to work on that. Feel free to shoot me an email to set up.


lint(md): consider enforcing asterisk rule in our markdown files

Background
There is a desire to have the asterisk being used for bullet points. We should configure our markdown CI linter to be aware of this rule.
Acceptance Criteria

The rule is applied to our markdown linter
The CI passes for all files with the new rule

Originally posted by @p0mvn in https://github.com/osmosis-labs/osmosis/pull/1983#discussion_r915944653

Closing in favor of cref #2287
In general, I think lints like this are larger time sucks than wins.


Crash on Record::update_sequence_array_count, substraction overflow

In Record::update_sequence_array_count, there is a case where update_sequence is 0 and is subtracted of sizeof<u16> which is 2 and so it overflows to below 0 for an u16.
https://github.com/ColinFinck/ntfs/blob/7dce76c77ca4e1f218e672adbb27b144cf0fb304/src/record.rs#L107-L113
A saturating_sub works here but not sure it is the preferred option 🤔

Fixed in 5cc24169cf510295f53d9969d7bbd75f0b7711b9


Feat : Add geometric distribution

Adds the geometric probability distribution

The p ∈ Ioc 0 1 hypotheses look strange. Why not (hp_pos : 0 < p) (hp_le_one : p <= 1)?
It looks like you have to turn the Ioc hypothesis back into simple inequalities several times to then use positivity, so there is a drawback to using Ioc. Also, to provide a p ∈ Ioc 0 1 term to one of your lemmas, you would basically have to put both inequalities into a constructor, while you could just as easily have provided the inequalities separately.
What made you use Ioc?

No particular reason, I just wanted to reduce the number of hypotheses, so Ioc uses one less hypothesis. however, I agree that it is quite clumsy. Shall I rewrite in terms of your hypotheses?

Yes, please use two separate hypotheses.

I've made the necessary changes. Perhaps measurable_geometricPmfReal (line 65) is redundant now, as the proof is literally by measurability?

@RemyDegenne I've just made a new commit with your suggested changes AND name style changes consistent with the PR #9681 that you also accepted. I just wanted to check in that this was fine before merging?

It looks good! You can merge when CI succeeds.

bors r+

bors r+

bors r+


Iris ❤ Xarray docs page.

🚀 Pull Request
Description

To-do

[x] Do links
[ ] Detail on times and fill values @pp-mo
[x] Consistent styling
[x] What's New entry
[x] Overall summary of the different experience?
[ ] Better location? / Make Technical Papers more visible?

Future additions

Glossary translating Iris & Xarray terms
Comparison - Arithmetic
Comparison - Metadata
Comparison - Subsetting/Slicing

Consult Iris pull request check list

[ ] Detail on times and fill values @pp-mo

@pp-mo this is getting close now I think. Are you able to produce this extra detail that you wanted to?

The guide looks great, thank you. I think Deepak noticed most of the important issues.
I also wanted to say thanks for Iris. It was definitely a big part of the inspiration for Xarray.

Thanks @bjlittle, and everyone for their contributions!


AttackPlan Elaboration

frizb,
Would it be possible for you to post some documentation on custom attack plan creation? I am working to create a "legal" OSCP exam attack plan, but I am running into issues where the custom lines I add to config.ini are not running correctly. Instead of addressing just my issues, I think some elaboration on the attack plan creation as a whole would be super helpful.
Thanks!

Thanks for reaching out regarding attack plan documentation.
I have added 2 more examples that might provide some more guidance on how you might accomplish these custom attack plans.  There is a bit of documentation at the top of the attackplan.ini and config.ini files but I do plan to create a more detailed wiki page in the future.  I am still ironing out some issues and there are some more features I would like to add.


Wallet set up tutorial - Fairground (testnet)

Story
As a user
I want to see a tutorial of how to set up a Vega wallet on Fairground (testnet)
So that I feel supported in doing so, am more likely to get it right first time and have a good experience as a result
Acceptance Criteria

[ ] I can see and link to a video tutorial from the https://vega.xyz/wallet page of the website (perhaps near the 'How to use' section)
[ ] I can see what network this tutorial is relevant for

Tasks

[ ] Decide what details to show and where on the page to link to the tutorial
[ ] Design how this will look on the page (as needed)
[ ] Implement
[ ] Test
[ ] Release

Sketch
Additional details / background info
Slack thread from Edo sharing that a video tutorial has been created and shared on Twitter https://vegaprotocol.slack.com/archives/C02KSKW6Y3F/p1675253167005199
Link to video tutorial on YouTube channel for FAIRGROUND https://www.youtube.com/watch?v=fFmLQeQUa1k

@goslingo @bigfandavid the links above are the target video's for this card.
We will need to create a link or a thumbnail on https://vega.xyz/wallet/ to link to it.


Add some detail around MTU maximums to XDP program type page

For normal XDP programs the expectation is that the full packet is available between ctx->data and ctx->data_end and be linear memory. At the level XDP runs, no consecutive memory pages can be guaranteed, so such a packet + metadata has to fit in exactly 1 memory page (typically 4k). This means that minus stuff like headspace and skb metadata actual max packet size is smaller. Drivers therefor tend to block XDP programs from being attached if the MTU is to high. This seems like an arbitrary limitation for new users and also a poorly documented limitation.
So its would be nice if we could dedicate a section of the XDP program type page to explaining this limit, how and why the numbers change between drivers and perhaps some other factors at play such as the impact of XDP frags and other driver specific settings.

I had some time to go over the code for different drivers and make an initial overview by copying relevant max MTU calculation code and running it to get some initial numbers:
| driver          | Max MTU normal   | Max MTU frags |
| --------------- | ---------------- | ------------- |
| Veth            | 3520[1]          | 73152[1]      |
| Tun             | 1500             | x             |
| Virtio          | 3502             | :infinity:    |
| xen-netfront    | 3840             | x             |
| Bond            | [2]              | [2]           |
| ENA             | 3498             | x             |
| AQ              | 2048             | :infinity:    |
| BNXT            | 3500             | :infinity:    |
| Cavium Thunder  | 1508             | x             |
| Englender       | :infinity: :sus: | :infinity:    |
| Freescale FEC   | :infinity: :sus: | :infinity:    |
| Freescale DPAA  | 3578             | x             |
| Freescale DPAA2 | [3]              | x             |
| Freescale ENETC | :infinity: :sus: | :infinity:    |
| FunEth          | 3566             | x             |
| GVE             | 2032             | :infinity:    |
| I40E            | 3046[4]          | 9702[4]       |
| ICE             | 3046[5]          | :infinity:    |
| IGB             | 3046[6]          | x             |
| IGC             | 1500             | x             |
| IXGBE           | 3050[7]          | x             |
| IXGBVE          | 3046[6]          | x             |
| Marvell nvneta  | 3424             | :infinity:    |
| Marvell MVPP2   | 3552             | :infinity:    |
| Marvell OTX2    | 1508             | x             |
| MediaTek        | 1508             | x             |
| Mlx4            | 3498             | x             |
| Mlx5            | 3496             | :infinity:    |
| Lan966x         | :infinity: :sus: | :infinity:    |
| Mana            | 3506             | x             |
| Netronome       | [3]              | [3]           |
| qede            | :infinity: :sus: | :infinity:    |
| SFC             | 3490[8]          | x             |
| Stmicro         | 1500             | x             |
| ti              | :infinity: :sus: | :infinity:    |
| hyperv          | 3520             | x             |
| vmxnet3         | 3492             | x             |

[1]: On x86, ARM64, and PowerPC. Else 3518 / 73150
[2]: Depends on slave devices
[3]: Depends on NIC firmware
[4]: Unless running in legacy ENA mode, then 2006
[5]: Unelss running in legacy RX mode, then 1638
[6]: If using large rings, else if "build skb" 1508, else 2022
[7]: If using 3K buffer, else if "build skb" 1514, else 2026
[8]: If falcon/siara, else if A10 3530, A100 3522

Now, these numbers are based on struct sizes in my particular kernel and constants from linux master. So they can move around over kernel versions. I am going to include these in the docs initially with a warning. After that I want to improve this by converting the MTU calculation code for each driver into something we can more easily run against variables such as different page sizes, struct sizes for the LTS kernels ect. This should produce a more accurate matrix of max MTUs. Then figure out some way to include that in the docs in a readable way.


Repeated fields' name in child form different than non-repeated

Essential example:
class MyForm extends Form {
    public function buildForm() {
        $this->add('foo', 'text');
        $this->add('bar', 'repeated', [ 'type' => 'text', 'first_name' => 'bar', 'second_name' => 'bar_confirm' ]);
   }
}

$child = new MyForm();

$parent = Form::create(...);
$parent->add('child', 'form', [ 'class' => $child ]);

The essential rendered output is:
<input class="form-control" id="foo" name="parent[foo]" type="text">
<input class="form-control" id="bar" name="bar" type="text">
<input class="form-control" id="bar_confirm" name="bar_confirm" type="text">

Expecting all inputs to be named in "parent" space, ie: parent[bar] and parent[bar_confirm].

Yes, the problem exists. I'm just not sure how is this field type helpful as it is now, i added it long time ago, and didn't test it thoroughly. Just noticed that name it is given (in your example bar), is not used at all. That's why the naming is not proper. Same thing can be achieved with a child form.
Can you give me real example where you are using it?
I should update it to use first parameter in add() instead of first_name, and second to be configured from options like it is now.

I use it on a credentials form, for confirmation of username and password.
"Repeated" was definitely a short-cut. I could have just done:
$this->add('username', 'text');
$this->add('username_confirm', 'text');
$this->add('password', 'password');
$this->add('password_confirm', 'password');

My actual use case is more complicated, because the form is flexible: the form consumer decides whether he wants to username to require confirmation, or password to require confirmation.  So "repeated" was convenience to keep the code short, given it had more complexity surrounding it.

Yes that was the first idea to use it for confirmation fields. I'll probably update it as i said, to use passed name as first value, and second one to be passed in options, something like this:
<?php
$this->add('password', 'repeated', [
    'first_options' => [],
    'second_name' => 'password_confirmation' // This would be default
    'second_options' => []
]);

Would that work out in your case?

Yes, I think that would work (provided type field is there).
Of course, I'm of the opinion that something more consistent with the existing API, like this:
<?php
$this->add('username', 'text', [ 'attr' => [ 'class' => 'foo' ]]);
$this->getField('username')->repeat();  // repeats with defaults

To override defaults:
$this->getField('username')->repeat('username_confirm', 'text', [ 'attr' => [ 'class' => 'bar' ]]);

This works a little better in my workflow, because the confirmation field is optional, depending upon form configuration.  So, if confirmation is wanted, it's easy to add it in with a method call.

Honestly, I don't think repeated field type is used that often (probably most of the time only for password confirmation), and especially not to be optional like in your case.
The repeat() method is great idea, but most of these field types are idea from Symfony's form component, and for this type i tried to simulate this.
Since it is pretty impossible to do the same thing (use these two fields to bind value to the 3rd field), i'll probably set up repeated type to be as described in my last comment. That would not work in your case, because it needs to be optional, but the point of the field type would be achieved.
I also got an idea about methods 'addAfter()andaddBefore`, which would allow adding fields at specific locations later.

Works for me, thanks!  I can handle my use case with a branch, making different API calls as needed.

Repeated fields are fixed, and working as described :)

Confirmed, thanks!


Debug message if returned None from get_vm method

!test

Codecov Report

Merging #283 into master will increase coverage by 1.58%.
The diff coverage is 20%.

@@            Coverage Diff             @@
##           master     #283      +/-   ##
==========================================
+ Coverage   57.14%   58.72%   +1.58%
==========================================
  Files          40       40
  Lines        3381     3385       +4
  Branches      395      398       +3
==========================================
+ Hits         1932     1988      +56
+ Misses       1350     1295      -55
- Partials       99      102       +3

Impacted Files
Coverage Δ

vmpool/endpoint.py
87.12% <20%> (-2.73%)
:arrow_down:

vmpool/platforms.py
63.41% <0%> (+1.21%)
:arrow_up:

vmmaster/server.py
69.84% <0%> (+1.58%)
:arrow_up:

vmmaster/http_proxy.py
94.11% <0%> (+62.35%)
:arrow_up:

Continue to review full report at Codecov.

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

!test

@sh0ked merge?


Add stale-if-error header

We sometimes get transitory issues with API backends being unavailable, e.g. here.
We should probably set a stale-if-error header by default that is some relatively short time, just to protect users from seeing short-lived issues.
I guess stale-if-error should always be longer than max-age. But how long? 5 minutes?

Could you please give this a priority and estimate it?

this is not done


Add an extra FAQ for EnsureNuGetPackageBuildImports

Fixes https://github.com/NuGet/docs.microsoft.com-nuget/issues/2073

Docs Build status updates of commit 79b1373:
:clock10: Pending: waiting for processors (36 builds ahead of you)
:warning: Docs Build is busy, currently there are 36 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 79b1373:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit c56b155:
:clock10: Pending: waiting for processors (36 builds ahead of you)
:warning: Docs Build is busy, currently there are 36 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit c56b155:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/consume-packages/Package-restore-troubleshooting.md
:warning:Warning
View
Details

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-restore-troubleshooting.md

Line 44, Column 196: [Warning-file-not-found] Invalid file link: '../../resources/NuGet-FAQ.md'.
Line 5, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'karann' is not a valid Microsoft alias.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit b45481d:
:clock10: Pending: waiting for processors (15 builds ahead of you)
:warning: Docs Build is busy, currently there are 15 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit b45481d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/consume-packages/Package-restore-troubleshooting.md
:bulb:Suggestion
View
Details

docs/resources/NuGet-FAQ.md
:white_check_mark:Succeeded
View

docs/consume-packages/Package-restore-troubleshooting.md

Line 5, Column 12: [Suggestion-ms-author-invalid] Invalid value for 'ms.author', 'karann' is not a valid Microsoft alias.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


boost libraries not found - build error on centos 7

Hello,
I was getting error while building from source:
Using custom FindBoost.cmake
CMake Error at libraries/fc/CMakeModules/FindBoost.cmake:1129 (message):
Unable to find the requested Boost libraries.

Boost version: 1.66.0

Boost include path: /root/opt/boost_1_66_0/include

The following Boost libraries could not be found:

boost_system
boost_chrono

Some (but not all) of the required Boost libraries were found. You may
need to install these additional Boost libraries. Alternatively, set
BOOST_LIBRARYDIR to the directory containing Boost libraries or BOOST_ROOT
to the location of Boost.
Call Stack (most recent call first):
CMakeLists.txt:88 (FIND_PACKAGE)

I couldn't get it to work with few workarounds, so I decided to update the scripts/eosio_build_centos.sh to use the 1.67 version of boost library. After that my build succeeded.
OS info:
CentOS Linux release 7.5.1804 (Core)
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.5.1804 (Core)
CentOS Linux release 7.5.1804 (Core)

@barrage-ivan EOS.IO is tested using boost 1.66. You may experience unexpected results using boost 1.67. It is recommended to compile EOS.IO as an unprivileged user i.e. not as root. If you run into any further installation issues please capture the complete output of the eosio_build.sh script and paste it here.

Yes, for the initial contact I've run it with root. You are right, I've run setup with unprivileged user, it went fine. Thanks!

Hi @pacificcode, what is the reason for compiling EOS.IO as an unprivileged user? can you elaborate on that, thx.

@brightermatter , my understanding is that generally, software should be installed as non-root, thus it can be run later as non-root, thus root-access accidents are avoided.


status_rrd_graph.php loads, but has no graphs

<IP_ADDRESS>-32aeeab6b (amd64)
the log is full of enries like this:
opnsense: /status_rrd_graph_img.php: Failed to create graph with error code 1, the error is: ERROR: Could not make sense out of '--start'/usr/local/bin/rrdtool graph /tmp/system-mbuf.rrd-fouryear?refresh_date=20150326221858.png --start<PHONE_NUMBER> --end<PHONE_NUMBER> --step 86400 --vertical-label "utilization, percent" --color SHADEA#eeeeee --color SHADEB#eeeeee --title "OPNsense.localdomain - System :: Mbuf clusters - 4 years - 1 day average" --height 200 --width 620 DEF:"current=/var/db/rrd/system-mbuf.rrd:current:AVERAGE:step=86400" DEF:"cache=/var/db/rrd/system-mbuf.rrd:cache:AVERAGE:step=86400" DEF:"total=/var/db/rrd/system-mbuf.rrd:total:AVERAGE:step=86400" DEF:"max=/var/db/rrd/system-mbuf.rrd:max:AVERAGE:step=86400" LINE2:"current#0080FF:current" LINE2:"cache#00E344:cache" LINE2:"total#FF0000:total" LINE2:"max#000000:max" COMMENT:"\n" COMMENT:" minimum average maximum current\n" COMMENT:"Current. " GPRINT:"current:MIN:%7.2lf %s " GPRINT:"current:AVERA

the situation above was observed after update from <IP_ADDRESS> to <IP_ADDRESS>.  After reboot graphs are back there.

I checked this yesterday and <IP_ADDRESS> seemed fine from here too. Can I close this issue?

Lets assume, that we want to have updates, that do not require reboots.  In this case this is a bug, that needs to be fixed in the context of rebootless updates.
I do agree that it is a minor inconvenience, but I can imagine, that there are cases, when router cannot be rebooted as it would cause a few (unacceptable) downtime minutes.
In my case it does not matter, I do turn off network infrastructure as soon as do not need it (so a few powerdowns a day), but if we target industrial 24/7 uptime and quality, the we need to get it fixed too...

Before assuming, let's say this actually happened despite the fact that it shouldn't. It happens.  It still happens. We are human. We don't get paid. The BSD license makes no promises with regard to quality, liability, damage, etc. Best part is this is a free project. :)
Assuming does, however, not help to trace down this bug, which is also on the low side of the priority item list due to the fact that RDD graphs are not a mission critical system. Compare that to the last two days of work we spent on amending the aliases situation.
We are far from industry standards here with a legacy code base with missing transparency that we had to bring back to the public, not a single unit test, lack of coding style, at least 5 years worth of missing drive to innovate and clean ups. We as OPNsense have worked on fixing this since November 2014, we've been around since January 2015. If that is not enough that's not good, because that's what we can offer. Not more, not less.
May I close this issue or will you help to trace this down?

@fichtner please do not get into attack/defence mode, If would not care about FOSS I would not be here reporting bugs in the first place. At the moment I am positively surprised with the speed the project reacts and fixes minor bugs :)  As long as I stay using the software I will report ALL bugs I come across.
As already stated for me this bug was a minor inconvenience.  The issue stays here for further reference. Fort the time being we can agree to close the issue with status WONTFIX.

@ortylp I am sorry if it came across this way. To some degree I have to draw the line and keep the balance for the few resources that we have. We've come a long way in just a few months and I know that some decisions need to be made to keep this progress up. I love the project and the people and their feedback. Without the community we wouldn't be this far. Thank you. :)

Reopening due to https://forum.opnsense.org/index.php?topic=329.0
The code is correct and works in the test setups. rrdtool complains about '--start' which is a viable command as far as the appended command line afterwards shows. No idea what is going on...

closing this once more, hopefully never to return after the two patches went in.


fix: handle most recently created containers first

This is a proposed fix for #1049. It orders the containers being iterated over by descending creation timestamp (most recent first) instead of by ascending certificate domain name.
Closes #1049

@cpontvieux-systra I know this is ~ 4 months old but your help in validating that this fix #1049 would be welcome.
I've pushed and image that include the fix : nginxproxy/acme-companion:1049


detect_python.sh fails to detect correct Python binary (IDFGH-8831)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v5.1-dev-1908-g439a709c42
Operating System used.
Linux
How did you build your project?
Other (please specify in More Information)
If you are using Windows, please specify command line type.
No response
What is the expected behavior?
detect_python.sh should detect Python version 3.7
What is the actual behavior?
detect_python.sh returns version 3.6.9
Steps to reproduce.
On a Linux system with Python version with both 3.6.9 and 3.7 installed, attempt to install the idf.
Build or installation Logs.
Detecting the Python interpreter
Checking "python3" ...
Checking "python" ...
Python 3.6.9
"python" has been detected
Checking Python compatibility
Traceback (most recent call last):
  File "/home/appveyor/projects/simpleson-l4m5a/esp-idf/tools/python_version_checker.py", line 45, in <module>
    check()
  File "/home/appveyor/projects/simpleson-l4m5a/esp-idf/tools/python_version_checker.py", line 39, in check
    _ver_to_str(OLDEST_PYTHON_SUPPORTED), _ver_to_str(sys.version_info[:3])
RuntimeError: ESP-IDF supports Python 3.7 or newer but you are using Python 3.6.9. Please upgrade your installation as described in the documentation.
Setting IDF_PATH to '/home/appveyor/projects/simpleson-l4m5a/esp-idf'
Detecting the Python interpreter
Checking "python3" ...
Checking "python" ...
Python 3.6.9
"python" has been detected
Checking Python compatibility
Traceback (most recent call last):
  File "/home/appveyor/projects/simpleson-l4m5a/esp-idf/tools/python_version_checker.py", line 45, in <module>
    check()
  File "/home/appveyor/projects/simpleson-l4m5a/esp-idf/tools/python_version_checker.py", line 39, in check
    _ver_to_str(OLDEST_PYTHON_SUPPORTED), _ver_to_str(sys.version_info[:3])
RuntimeError: ESP-IDF supports Python 3.7 or newer but you are using Python 3.6.9. Please upgrade your installation

More Information.
Full log can be found here on Appveyor
The Appveyor Linux build environment has multiple versions of Python installed. Looking at detect_python.sh, the script should iterate through the versions until it finds a suitable version; however, the script is exiting with an unsupported version, as shown here in the logs:
Python 3.6.9
"python" has been detected

I suspect the problem is here:
https://github.com/espressif/esp-idf/blob/439a709c4298b0f613d09b47fc0b7b9728fc5733/tools/detect_python.sh#L20

Root cause: by initializing ESP_PYTHON with python, the script will successfully return an unsupported version of Python if python is an unsupported version but no other supported versions are found.

Hi @gregjesl. Thank you for your investigation.
Returning "python" is desired so even when there is no suitable version, the issue wouldn't be transformed to something else: "python script.py" would be attempted to run instead of "script.py" which could result in another issue - eg. script is not executable, not linked to the right Python.
Lets focus on why hasn't Python 3.7 being detected on your machine. python3.7 is not accessible in the PATH?
These are the Pythons checked (in this order):
for p_cmd in python3 python python3.7 python3.8 python3.9 python3.10 python3.11 python3.12; do

Hello @dobairoland, thank you for your review.
Based on your comment detect_python.sh is working as intended and that python_version_checker.py should be the script that determines if the installed version of python is a supported version.
If that is the case, then I would assert that detect_python.sh and python_version_checker.py are largely redundant. I've submitted pull request #10260 that implements the desired behavior in python_version_checker.py in detect_python.sh and detect_python.fish.

Returning "python" is desired so even when there is no suitable version, the issue wouldn't be transformed to something else: "python script.py" would be attempted to run instead of "script.py" which could result in another issue - eg. script is not executable, not linked to the right Python.

The install script will eventually fail if the only version of Python installed is not a supported version. As implemented in #10260, python_version_checker.py becomes unnecessary and the install script will exit if no supported version of Python is found in detect_python.sh or detect_python.fish.
The other approach I could see is keeping python_version_checker.py and removing the following:
https://github.com/espressif/esp-idf/blob/175e5fc260bedaa17d0e55788fa5c36ba3076a72/tools/detect_python.sh#L17-L20
https://github.com/espressif/esp-idf/blob/175e5fc260bedaa17d0e55788fa5c36ba3076a72/tools/detect_python.fish#L12-L15

Lets focus on why hasn't Python 3.7 being detected on your machine. python3.7 is not accessible in the PATH?

I can't find specific documentation on where the different Python binaries are installed on the Appveyor image. They provide the location of the virtual environments, but the IDF creates an virtual environment and Python does not support creating a virtual environment from a virtual environment. Virtual environment support for this IDF is probably a separate enhancement.
My current work-around is to have my CI install script download and install Python 3.7.15.

If that is the case, then I would assert that detect_python.sh and python_version_checker.py are largely redundant. I've submitted pull request https://github.com/espressif/esp-idf/pull/10260 that implements the desired behavior

Yes, I've seen that PR but I'm sorry but that is not the desired behavior. You are right that the scripts have similarities but used for different purpose. The shell scripts intends to find something in the PATH which can be used (don't opt out if python3 is not present but python is a suitable one; pythonX.Y are there for cases when Python installed additionally to meet ESP-IDF requirements). The PY script is invoked from the build system as well.

They provide the location of the virtual environments, but the IDF creates an virtual environment and Python does not support creating a virtual environment from a virtual environment.

That is the problem. ESP-IDF doesn't directly support connecting to existing virtual environments (would result in error if attempted). The requirement is to have a globally available python installed (not virtual environment).
In your case indeed installing a Python manually and using that with ESP-IDF is the way to go.


rename the connecting operators

don't wanna cause confusing with the hacker32 functions
also i'd like them to be short, maybe +, *, >>, |, &, ^ (just need to figure out a way to skip the | when setting op)
also maybe another way of typing them (in addition) SUM, PRO, PIP, STA, BUS, BRA

574a1a7


Uncaught error: "cd */: No such file or directory"

Reproducer:
bash-4.3$ mkdir git
bash-4.3$ cd git
bash-4.3$ git init
Initialized empty Git repository in /Users/joe/git/.git/
bash-4.3$ mkdir 1
bash-4.3$ cd 1
bash-4.3$ git standup
/usr/local/bin/git-standup: line 120: cd: */: No such file or directory
bash-4.3$

What version are you using?  I'll let you know if I see it happen again. Thanks for looking into it.


[auth][middleware] add jwt auth middleware

Added auth middleware to verify JWT (if added) to incoming requests.
JWT verification will take place by pulling JWK from core-webserver.
JWK would be cached for an hour.

[Dependencies]
authlib - Docs

Discussion notes

Move from Authlib to pyjwt


[gbc c++] Generate extern templates of bond::Apply instead of overloads

Currently code-generated *_apply.h/.cpp files are achieving build time improvements by declaring additional overloads of bond::Apply function for predefined set of transforms and a given user-defined struct(s) which are then selected, thanks to ADL. With C++11 the same can be achieved in a more idiomatic way by using extern templates.

@ara-ayvazyan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

I pushed a copy edit commit, so be sure to fetch before making more changes.


Event list ( show only events that are visible on the calandar at that moment )

id like to show only events in event list that are in calendar at that moment

#638
;)

Sorry... still don't understand how it work. Could you please provide more detail?


ULTIMATE MARVEL VS. CAPCOM 3 [PCSG00011]

App summary

App name: ULTIMATE MARVEL VS. CAPCOM 3
App serial: PCSG00011
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3017
Commit hash: https://github.com/vita3k/vita3k/commit/762ee3bc
CPU backend: Dynarmic
GPU backend: Vulkan

Test environment summary

Tested by: nishinji
OS: Windows 10
CPU: Ryzen 9 3950x
GPU: RTX3060Ti
RAM: 32 GB

Issues
Screenshots

Log
vita3k.log
Recommended labels
-nothing

Vita3K summary

Version: v0.1.8
Build number: 3145
Commit hash: https://github.com/vita3k/vita3k/commit/70201583
CPU backend: Dynarmic

Test environment summary

Tested by: othmanead
OS: Windows 11
CPU: Intel i5-10300H
GPU: RTX 3060 mobile
RAM: 16 GB

Issue:
Game displays a black screen
Screenshots:

Log
vita3k.log
Recommended labels

Bootable

as of https://github.com/Vita3K/Vita3K/commit/1b0e65e66d17202b1ae9f155cfecea802dd58778, the game can go to menu, but couldn't go ingame from my testing.
Screenshots

Log
vita3k.log
Recommended labels
Menu

as of https://github.com/Vita3K/Vita3K/commit/1b0e65e66d17202b1ae9f155cfecea802dd58778, the game can go to menu, but couldn't go ingame from my testing.
Screenshots

Log
vita3k.log
Recommended labels
Menu
graphics bug


xdg-user-dirs: new package at 0.17

Please fill out the template.
Read: https://k1ss.org/style
Read: https://k1ss.org/guidestones

Description of package
xdg-user-dirs is a tool to help manage "well known" user directories like the desktop folder and the music folder. It also handles localization (i.e. translation) of the filenames.

[x] I agree to maintain this package.
[x] I agree to notify @dylanaraps if I can no longer maintain this package.

Existing package

[ ] I am the maintainer of this package.

I'd very much not like for this package to make it into the repositories. We've thus far managed to avoid all xdg- crap and I'd really like to keep it this way. Translation is also something unneeded in the repositories as only English is officially supported.

It is a package that does not pull anything, and I use it because it makes me comfortable to have differentiated base folders. As a starting point it is in English. In any case, it is my personal opinion. But if you don't want to include it, I understand your reasons.

as I said I understand your point of view. I proceed to close


the_type element not set in groups extending historical-act

Exported data should the the_type element set to the group name.
This works for "lista" but not for others, like "carta"

This happens because the method group_to_entity uses the list of columns in the PomSomMapper to fetch the elements of the group and set them in the ORM Model. Since "Carta" does not include "the_type" it is not fetched.
The best way would be to inspect the ORM Model to obtain the columns and then use the PomSomMapper hierarchy to find the element name equivalent to each column and fetch the element from group.

PomSomMapper needs to collect all the class_attributes up in the hierarchy.
KGroup.get_element_for_column() ignores PomSomMapper maybe the method would make more sense in PomSomMapper because KGroup  has no access to the db.

fixed in 1.1.12


Use dynamic programming for better word wrapping

I use the simple greedy algorithm right now, but line lengths could be more even in some circumstances.

Did it!


Supporting for bootstrapping

Hello, I am very interested in elasm compiler project! I noticed that the elasm compiler does not seem to take the bootstrapping step into account in the optimization process. Is adding the bootstrapping step automatically a future feature of the elasm compiler?

Thanks for your reply. I look forward to your update. :)

Hey all, since it's been a while, I wanted to check back in to see what the status of DaCapo/Automated Bootstrapping open sourcing is :)


Citation in Dynamic Stackelberg

There's a comment in the Dynamic Stackelberg lecture:
.. TODO: Is the reference to KydlandPrescott to the correct paper?  When I think Kydland Prescott 1980, this is the paper I think of.  Does Evans Sargent refer to your paper with David Evans on History Dependent Public Policy?  I couldn't find the journal or other information on this paper.

And the citation we currently have is
@article{KydlandPrescott1977,
    author = {Kydland, Finn E., and Edward C. Prescott},
    journal = {Journal of Political Economy},
    pages = {867-896},
    title = {Rules Rather than Discretion: The Inconsistency of Optimal Plans},
    volume = {106},
    number = {5},
    year = {1977}
}

Not super pressing, but would be good to iron out if possible.
cc @jstac

@arnavs  if this is the lecture that was removed from the site, we can close this issue.

No that was the history dependent policies one


improve keybindings

Nikola-j requested configurable keybindings, which was on the roadmap but not logged yet.

All that's left is to add instructions to CHB settings page.

Added a note to look in the right place for module settings.


Website doesn't load when using Firefox private browsing

The symptom is a gray screen and the following messages in JS console:
InvalidStateError app.js:40:0

[App.jsx] ----- App.willTransitionTo error -----> DOMError { name: "InvalidStateError", message: "A mutation operation was attempted …" } app.js:4:7397
Unhandled promise rejection DOMError { name: "InvalidStateError", message: "A mutation operation was attempted …" }
The specific cause is the IndexedDB open() call here throws an exception when Firefox is set to forget history (for example, private browsing / incognito mode sets this, but I think it can also be enabled for non-private browsing in some settings screen).  louism reply to this StackOverflow question helped me track down the issue.
We should catch this exception and tell the user the website is not compatible with their privacy settings.  Related:  #143

That is a FF issue..
You can simply not use incognito mode.  I'm not so sure incognito works in RAM only anyways.  If it does not, it is just as good to clear the Db from the console or setup when you are done.
Run these separately to clear all Wallets:
resolve(WalletManagerStore.onDeleteAllWallets())
iDB.root.deleteDatabase(true)

https://bugzilla.mozilla.org/show_bug.cgi?id=781982

You can simply not use incognito mode

Yeah, that's the obvious workaround for this problem.  The issue is that I got absolutely no information about what was wrong, I just saw a gray screen.  It took me an hour with the debugger to figure out what was going on and that incognito mode might be affecting it.
So the UI should catch the exception and display a message to the user on the actual web page along the lines of, "Couldn't open IndexedDB.  This may be because you are in Private mode, or you have browser history disabled.  Please come back without using Private mode."
It seems like it should be very simple for one of you web devs to make that happen, and it changes the user experience from "it's the developers' fault this buggy website is broken and there's nothing I can do to make it work, I guess I just have to wait for them to fix it" to "it's my fault I'm using unusual browser settings, and I can fix it myself in five seconds by disabling private mode."

Good Point!  I'll have a look, thanks for re-opening.   According to this ticket "there is no reliable or accurate way to detect if someone is browsing in an incognito/private/safe browsing mode" ... I can detect it and put a hint that this could be caused by incognito mode to hold us over in the mean time.
Some research is needed to see how our IndexedDb shim handles older browsers, maybe some other types of errors can be separated out from this general message.

@valzav this error is happening during the initial application loading in App.willTransitionTo.  Can you recommend a way to report this in the UI?
I'm able to trap it here:
    Apis.instance().init_promise.then(() => {
        return iDB.init_instance(window.openDatabase ? (shimIndexedDB || indexedDB) : indexedDB).init_promise.catch(
            error => {
            console.error('[App.jsx] Unable to initialize IndexedDb Database',error)
        }).then(() => {

I caught the error and did not re-trow it.  Still nothing rendered in the browser window so I don't have a way to report it in the UI (notify for example).

I guess we could transition to an error page and pass that error in as a string...

It would be nice if we could render a <AppFatalErrors/> component during the App.willTransitionTo passing a error string like idb_init_promise and an object error in as parameters.  The component could do something fancy like (if FF and error == idb_init_promise) then say (this could be caused by private browsing) ...

Or window.location.href =  to a static page.

Should we tie this to #143 and display the same message we display for Chrome Incognito? We can always circle back and add something better for developers later.

This can be closed.. valzav added an alert message that basically says this error could be caused by incognito mode.. I can confirm it worked.  If it does not re-open..


Make sure we are not in a virtualenv if aborting

Fixes #2078

Thanks for the fix! The logic looks correct to me, but we probably want to add a comment there so make sure people reading the code in the future know exactly when (and why) we should abort. Would you be able to add this?

Done!

Thanks for the PR! Will merge after CI

hey @techalchemy, is there a release planned for sometime soon that will get this live?

@pegler in the next couple of days, we have some performance enhancements in the pipeline that I really want to get into the release if possible

If i have the time I will release sooner, depends how smoothly these all go

sounds good. thanks!!


Allow error-handing in MacroMirror derivation

My use-case of MacroMirror is to recursively derive a type class instance for case classes, until I hit a primitive type or enum, where I attempt to derive another type class. With current implementation I cannot branch this derivation because errorAndReport gets called.
Not sure if the breaking change is allowed, but I assumed it is since we're on 0.0.x branch.

As of macroMirrorTestImpl - it wasn't used anywhere, so I changed the implementation quite a bit.

That's awesome! Thanks @chuwy!


Error: 'Name' object has no attribute 'ops'

When using ProgramOfThought and code is generated with named conditionals like this:
Previous Code:
from datetime import datetime

data = {
    "ExpenseReport": "002",
    "ExpenseAmount": "USD30.0",
    "AuthorizationLevel": "94",
    "ExpenseDate": "2024-01-17",
    "SubmittedDate": "2024-02-14",
    "WorkLocation": "US",
    "ExpenseCategory": "hotel",
    "ReceiptAttached": "yes"
}

# Convert amounts to float for comparison
expense_amount = float(data["ExpenseAmount"].replace("USD", ""))
authorization_level = int(data["AuthorizationLevel"])

# Convert dates to datetime objects
expense_date = datetime.strptime(data["ExpenseDate"], "%Y-%m-%d")
submitted_date = datetime.strptime(data["SubmittedDate"], "%Y-%m-%d")
days_difference = (submitted_date - expense_date).days

# Check each policy
policy_1_violated = (expense_amount > 100.00 and authorization_level < 100) or (expense_amount > 25000.00)
policy_2_violated = ((submitted_date.weekday() >= 5) or (days_difference > 30 and data["WorkLocation"] == "US") or (days_difference > 60 and data["WorkLocation"] == "Europe"))
policy_3_violated = (data["ExpenseCategory"] == "hotel" and data["ReceiptAttached"].lower() != "yes")

# Determine status_reason
if policy_1_violated:
    status_reason = "Policy 1 Violated"
elif policy_2_violated:
    status_reason = "Policy 2 Violated"
elif policy_3_violated:
    status_reason = "Policy 3 Violated"
else:
    status_reason = "Approved"

status_reason

The following error message is generated.
Error: 'Name' object has no attribute 'ops'
This can be fixed by adding the 'elif isinstance(condition, ast.Name):' statement in python_interpreter.py as shown below.
    def _execute_condition(self, condition):
        if isinstance(condition, ast.BoolOp):
            if isinstance(condition.op, ast.And):
                results = [self._execute_ast(value) for value in condition.values]
                return all(results)
            elif isinstance(condition.op, ast.Or):
                results = [self._execute_ast(value) for value in condition.values]
                return any(results)
            else: #TODO - add any other BoolOps missing
                raise InterpreterError(f"Boolean operator {condition.op} is not supported")
        elif isinstance(condition, ast.Name):
            return self._execute_name(name=condition)

Hey @arthurgreef ! Thanks a lot. Do you want to open a PR with these improvements for the interpreter?

Hey @arthurgreef ! Thanks a lot. Do you want to open a PR with these improvements for the interpreter?

The contributing.md file referenced on the home page cannot be found because it is no longer in the top directory. Please share. Thanks.


feat: add blockage diagnostics

Related Issue(required)
https://github.com/autowarefoundation/autoware.universe/issues/417
Description(required)
To add LiDAR blockage diagnostic feature.
Review Procedure(required)

Run Autoware
Run rqt_robot_monitor:  ros2 run rqt_robot_monitor rqt_robot_monitor
Check rqt_robot_monitor__RobotMonotor-rqt

Related PR(optional)
https://github.com/tier4/aip_launcher/pull/30#issue-1153923174
Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read commit-guidelines
[x] Assign PR to reviewer

If you are adding new package following items are required:

[x] Documentation with description of the package is available
[x] A sample launch file and parameter file are available if the package contains executable nodes

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the [guidelines][clang-tidy-guidelines].
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@badai-nguyen Please check the spell checker results and fix typos.


Print complete certificate

with PEM_write_X509 or similar

Functionality is already available, stir_shaken_get_x509_raw().

Functionality is already available, stir_shaken_get_x509_raw().

Only raw cert can be read with stir_shaken_get_x509_raw(), need a human readable form that is available with: openssl x509 -in x.pem -noout -text


Add higher order component example

To replace mixins.
https://medium.com/@dan_abramov/mixins-are-dead-long-live-higher-order-components-94a0d2f9e750

https://github.com/steida/este/tree/master/src/client/components/common


Remove [Unsupported] annotation from title bar

We now rely on Help > About and issue reporter to call out unsupported builds,
the title bar is just a nuisance to users now.
Fixes #151104
I tested by hardcoding isPure to false and saw it shows before the change and not after.

https://github.com/microsoft/vscode/pull/154209 should get merged in today to ensure it's in report issue/about, marging.


Test script isn't working

When using create-choo-app and running npm test right after creating a project I first get some standard errors and complains that

'test-deps' is not recognized as an internal or external command, operable program or batch file.

It seems to me it might be worth updating the test script to something similar like choojs/choo uses.
We could add dependency-check to our package and use that to test the input file. Turning the test script into:
"test": "standard && dependency-check package.json && dependency-check --unused --no-dev package.json",

I am running on Windows 10 if that makes any difference :)

Yeah, we should be using that. Probably include a --ignore tachyons as it
only ever exposes CSS. A PR for this would be really helpful, thanks! :D
On Thu, Sep 14, 2017 at 2:51 PM Hendrik<EMAIL_ADDRESS>wrote:

When using create-choo-app and running npm test right after creating a
project I first get some standard errors and complains that
'test-deps' is not recognized as an internal or external command, operable
program or batch file.
It seems to me it might be worth updating the test script to something
similar like choojs/choo uses.
We could add dependency-check to our package and use that to test the
input file. Turning the test script into:
"test": "standard && dependency-check package.json && dependency-check --unused --no-dev package.json",
I am running on Windows 10 if that makes any difference :)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/choojs/create-choo-app/issues/22, or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlekL1ZL4sSAVn-JrEO5HTuvw9pca5ks5siSFYgaJpZM4PXiG8
.

Maybe this is rather an issue with something not being published right?
The scripts section that gets created for me is:
"scripts": {
    "build": "bankai build index.js",
    "inspect": "bankai inspect index.js",
    "start": "bankai start index.js",
    "test": "standard && test-deps",
    "test-deps": "dependency-check . && dependency-check . --extra --no-dev -i tachyons"
  },

While here I see it should create:
"scripts": {
      "build": "bankai build index.js",
      "inspect": "bankai inspect index.js",
      "start": "bankai start index.js",
      "test": "standard && npm run test-deps",
      "test-deps": "dependency-check . && dependency-check . --extra --no-dev -i tachyons"
    }

That might fix my troubles.
On the same note I see a lot of \ns around for the standard files which would fix standard complaining about missing new lines.
I have v1.6.1 installed and package.json on GitHub says that is the current version but somehow the published code seems to be different.

re:

On the same note I see a lot of \ns around for the standard files which would fix standard complaining about missing new lines.

we could also lazily run standard --fix after install 🙃

@ungoldman lol sure yeah why not, would just be an extra step in index.js,
added to the end of bin.js - PR? :D
On Sun, Sep 17, 2017, 20:51 Nate Goldman<EMAIL_ADDRESS>wrote:

re:
On the same note I see a lot of \ns around for the standard files which
would fix standard complaining about missing new lines.
we could also lazily run standard --fix after install 🙃
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/choojs/create-choo-app/issues/22#issuecomment-330071265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACWlejDXLzQkxiB1ZBfleFrZJxIBbY4_ks5sjWpAgaJpZM4PXiG8
.

@ungoldman on the other hand that is really lazy and we might as well just provide code in the style we suggest to follow ^^
For that we could add things as their own files here and have those checked against the standard ;)
@yoshuawuyts  I am unsure what is needed here as I feel the version I got from npm is not what is currently in the repo and some concerns might have already been addressed.

test script is working now
><EMAIL_ADDRESS>test /home/ubuntu/workspace/tmp
> standard && npm run test-deps

><EMAIL_ADDRESS>test-deps /home/ubuntu/workspace/tmp
> dependency-check . && dependency-check . --extra --no-dev -i tachyons

Success! All dependencies used in the code are listed in package.json
Success! All dependencies in package.json are used in the code

thanks


Device unresponsive after turning on for about 30 seconds

When the TV is off and then you issue a command to turn it on, the device is unresponsive for about 30 seconds. During this time, the Home app would display "not responding" and if you use Siri she would go "some of your devices are not responding". I thought this was strange because the TV would turn on fine, so I checked the logs:
[2/11/2018, 9:35:33 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:34 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:36 AM] [LG TV] webOS3 error Error: connect EHOSTUNREACH <IP_ADDRESS>:3000
[2/11/2018, 9:35:37 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:39 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:39 AM] [LG TV] webOS3 error Error: connect ECONNREFUSED <IP_ADDRESS>:3000
[2/11/2018, 9:35:39 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:42 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:42 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:42 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:44 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:45 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:45 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:47 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:47 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:48 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:48 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:50 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:51 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:51 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:52 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:53 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:54 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:54 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:56 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:57 AM] [LG TV] webOS3 TV state: Off
[2/11/2018, 9:35:57 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:57 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:35:59 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:36:00 AM] [LG TV] webOS3 connecting to TV
[2/11/2018, 9:36:00 AM] [LG TV] webOS3 connected to TV
[2/11/2018, 9:36:02 AM] [LG TV] webOS3 TV state: On
[2/11/2018, 9:36:07 AM] [LG TV] webOS3 TV state: On

Looks like during the turn on period the TV refuses connection for 30 seconds. I wonder if there's any way to fix this?

That is normal, the TV needs to boot and all the services needs to come up so it may take a while till the connection can be established.
Just as an info for me, what TV and what webOS version are you using?

From the logs I see that it does appear to be normal. I wonder if there'd be a workaround?
I have the EF9500, webOS 4.25.40

Unfortunately there is nothing that can be done since the TV hardware is already outdated and that is why it takes longer for all services to come up.


Only update log for download progress every 500ms

Closes: #1044

That makes it a bit better - instead of a full screen of progress lines I just get 4 so I get a bit faster stop.

I suppose we could make it every second instead of half second.

PR updated


The data type conversion between int32 and float32 in Keras

I want to build a new layer in Keras, so I defined the layer using Lambda layer. And my self-defined layer requires convert the data type of tensor (dtype=float32) to int32, then I need turn the dtype back (from int32 to float32) after some operations. The code is:
# add my self-defined layer
y = Lambda(f)(y1)  # y1 is the output of last layer

def f(x):
    y = tf.to_int32(x)
    # bitwiseXor = tf.bitwise.bitwise_xor(bitwiseXor, kkk)
    z = tf.to_float(y)
    return z

But following errors appears, how to solve it?

Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 490, in apply_op
preferred_dtype=default_dtype)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 675, in internal_convert_to_tensor
ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 121, in _constant_tensor_conversion_function
return constant(v, dtype=dtype, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 102, in constant
tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/tensor_util.py", line 364, in make_tensor_proto
raise ValueError("None values not supported.")
ValueError: None values not supported.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 504, in apply_op
values, as_ref=input_arg.is_ref).dtype.name
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 675, in internal_convert_to_tensor
ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 121, in _constant_tensor_conversion_function
return constant(v, dtype=dtype, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 102, in constant
tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/tensor_util.py", line 364, in make_tensor_proto
raise ValueError("None values not supported.")
ValueError: None values not supported.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/win1/Ubuntu_App/RemotePython/EncNN/My_EncML.py", line 134, in
model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, verbose=1, validation_data=(x_test, y_test))
File "/usr/local/lib/python3.4/dist-packages/keras/engine/training.py", line 1458, in fit
self._make_train_function()
File "/usr/local/lib/python3.4/dist-packages/keras/engine/training.py", line 1002, in _make_train_function
self.total_loss)
File "/usr/local/lib/python3.4/dist-packages/keras/optimizers.py", line 326, in get_updates
new_a = self.rho * a + (1. - self.rho) * K.square(g)
File "/usr/local/lib/python3.4/dist-packages/keras/backend/tensorflow_backend.py", line 1225, in square
return tf.square(x)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/ops/math_ops.py", line 428, in square
return gen_math_ops.square(x, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/ops/gen_math_ops.py", line 2544, in square
result = _op_def_lib.apply_op("Square", x=x, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 508, in apply_op
(input_name, err))
ValueError: Tried to convert 'x' to a tensor and failed. Error: None values not supported.
Process finished with exit code 1

I tried following codes in tensorflow, the result is right.
a = tf.constant(3.2, dtype='float32')
b = tf.to_int32(a)
c = tf.bitwise.bitwise_xor(b, b)
z = tf.to_float(c)
sess = tf.Session()
d = sess.run(z)
print(d)

The problem is not casting but gradient computation.
From the error message:
File "/usr/local/lib/python3.4/dist-packages/keras/optimizers.py", line 326, in get_updates
new_a = self.rho * a + (1. - self.rho) * K.square(g)

...

ValueError: Tried to convert 'x' to a tensor and failed. Error: None values not supported.

The x in the ValueError refers to g in optimizers.py, which is the gradient.
I don't think bitwise XOR is differentiable.
Your TF code works because there's no model fitting in it.

Thank you for your reply. But the error still exist even if I comment the bitwise line.
# bitwiseXor = tf.bitwise.bitwise_xor(bitwiseXor, kkk)
For now the code is:
def f(x):
    y = tf.to_int32(x)
    z = tf.to_float(y)
    return z

And the error is the same:

Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 490, in apply_op
preferred_dtype=default_dtype)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 675, in internal_convert_to_tensor
ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 121, in _constant_tensor_conversion_function
return constant(v, dtype=dtype, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 102, in constant
tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/tensor_util.py", line 364, in make_tensor_proto
raise ValueError("None values not supported.")
ValueError: None values not supported.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 504, in apply_op
values, as_ref=input_arg.is_ref).dtype.name
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/ops.py", line 675, in internal_convert_to_tensor
ret = conversion_func(value, dtype=dtype, name=name, as_ref=as_ref)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 121, in _constant_tensor_conversion_function
return constant(v, dtype=dtype, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/constant_op.py", line 102, in constant
tensor_util.make_tensor_proto(value, dtype=dtype, shape=shape, verify_shape=verify_shape))
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/tensor_util.py", line 364, in make_tensor_proto
raise ValueError("None values not supported.")
ValueError: None values not supported.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/win1/Ubuntu_App/RemotePython/EncNN/My_EncML.py", line 134, in
model.fit(x_train, y_train, batch_size=batch_size, epochs=epochs, verbose=1, validation_data=(x_test, y_test))
File "/usr/local/lib/python3.4/dist-packages/keras/engine/training.py", line 1458, in fit
self._make_train_function()
File "/usr/local/lib/python3.4/dist-packages/keras/engine/training.py", line 1002, in _make_train_function
self.total_loss)
File "/usr/local/lib/python3.4/dist-packages/keras/optimizers.py", line 326, in get_updates
new_a = self.rho * a + (1. - self.rho) * K.square(g)
File "/usr/local/lib/python3.4/dist-packages/keras/backend/tensorflow_backend.py", line 1225, in square
return tf.square(x)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/ops/math_ops.py", line 428, in square
return gen_math_ops.square(x, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/ops/gen_math_ops.py", line 2544, in square
result = _op_def_lib.apply_op("Square", x=x, name=name)
File "/usr/local/lib/python3.4/dist-packages/tensorflow/python/framework/op_def_library.py", line 508, in apply_op
(input_name, err))
ValueError: Tried to convert 'x' to a tensor and failed. Error: None values not supported.
Process finished with exit code 1

Casting is not differentiable

So, is there any solution of casting in the intermediate layer????


Enable compiler driven save actions

See commit messages for more information

Review done - looks good, see my comments for some nitpicking.

Thanks for the review, I took care of it.

LGTM then.


Renaming add-ins folder

To be more consistent with other sites

@jasonjoh,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/add-ins/addin-tutorial.md
:white_check_mark:Succeeded

docs/add-ins/concepts.md
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/add-from-file.PNG
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/addin-prompt-configure.PNG
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/addin-settings.PNG
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/addin-taskpane.PNG
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/button-and-pane.PNG
:white_check_mark:Succeeded

docs/add-ins/images/addin-tutorial/yeoman-prompts.PNG
:white_check_mark:Succeeded

docs/add-ins/index.md
:white_check_mark:Succeeded

docs/add-ins/reference.md
:white_check_mark:Succeeded

docs/add-ins/toc.yml
:white_check_mark:Succeeded

docs/breadcrumb/toc.yml
:white_check_mark:Succeeded

docs/index.md
:white_check_mark:Succeeded

docs/toc.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


AI Grader link Correction

Corrected redirection links for AI Graders.

its good, pull it into the system


Add Liferay advisories

See https://liferay.dev/portal/security/known-vulnerabilities

Taking this up!

Could I work on this, I saw it's still open.

Working on it.

@lata-11 I am about to make a pr for this one.


modularize codebase

Created by: MaxwellJung
Split main.opy into multiple .opy files for easier maintenance

mentioned in merge request ow1_emulator_backup!8

mentioned in merge request ow1_emulator_backup!3

moved from ow1_emulator_backup#742

mentioned in merge request ow1_emulator_backup!7


set up IPFS for image storage (M)

Summary:
As a DHO Developer I want to store images (logos, banners, background images) on IPFS.
Acceptance Criteria:

[x] Create IPFS credentials for DHO (@sebastianmontero)
[x] Create upload input component (for images)
[x] Create method to get real files (images) using the ipfs Id
[ ] Include in DHO creation

https://github.com/hypha-dao/dao-contracts/issues/157

HI @leonieherma1, I told with Luke and we think this issue should be closed, the core and base input are done, So the missing point (Include in DHO creation) should be done when we started to work in the creation DHO in other new issue, make sense for you?


form validation capitalize

Hi, i trying live demo of form validation.
When i try<EMAIL_ADDRESS>it gives 'This email is already in use!'
but when using<EMAIL_ADDRESS>it passed.

Hi, @fzone
Thank you for report.
Well, in the case of ajax validation everything depends on how server process the data and it is not Bunny Validation's problem.
In demo I use very simple plain PHP script to compare GET param with direct hardcoded string and because of that it failed since two strings wasn't equal. In real app on backend you will use any framework or ORM and usually won't have this problem.
Anyway I updated that PHP script on demo so it now ignores case.
Thanks again, let me know if you will have any other feedback, ideas or proposals.


Move cancellation ids to end of scopes.

You used to get warnings for moving ID types to the end of scopes after return statements (see https://github.com/apple/swift/issues/56805), but that's not the case anymore. By moving the IDs to the end of the scope we can remove unnecessary details from the top of our reducers.

Gonna close this without merging. While interesting, we have some changes coming that somewhat alleviate the need for this.