Single style for output of examples

See https://github.com/perl6/doc/issues/761#issuecomment-236023547
TL;DR: right now we don't have a single "official" output format for our examples, and everyone who writes documentation uses their own style. It's bad if we want to test our examples result automatically in the future. Our current formatting variants:

#-> result
# result
# OUTPUT: «result␤»
# OUTPUT: result

# OUTPUT:
# result1
# result2
# result3
# result4

Please, if you want to propose your own "style" - do it with a comment or just edit this message.
We need opinions about what style is best.

This issue is marked as `big`, because after selection we also need to rewrite all output results that don't match new "official" format line.

I like using the following, as the this way multi-line output aligns well and it's clear that it's output.
# OUTPUT:
# result

I'm against using # result, because it'd conflict with regular comments, especially when we do automated output check and I'm against OUTPUT: «result␤» because it's hard to type the fancy-pants symbols (I don't even know how to type them on my phone at all).

You don't type the result at all. You copy-pasta them from camelia into the docs because you tested the example against camelia to make sure they hold true.
The OUTPUT: «result␤» form allows easy parsing, I do agree that ¶ would have been a better pick because more ppl will be familiar with that symbol. We could change that automatically for html-output.
I'm sorry but the "I don't know how to ... on my phone"-argument is to selfish to be relevant to hopefully millions of readers of docs.perl6.org.

I agree that multi-line output should normally be on multiple lines. As for the «», these are usually typable on phones (and yeah, I think that the argument that you can't type something does not work so well in Perl 6 world). However, when I look at this:
OUTPUT: «result»
OUTPUT: result

It feels like «» are slightly redundant. It is parseable and it looks great.
So:
say qw{1 2 3 4}; # OUTPUT: (1 2 3 4)

.say for qw{1 2 3 4};
# OUTPUT:
# 1
# 2
# 3
# 4

↑ I see no problem here whatsoever
Comparing that to this:
say qw{1 2 3 4}; # OUTPUT: «(1 2 3 4)»

↑ Meh, «» look a bit weird.

We don't have to type the result itself - it's true, but what if I(hypothetically) am a docs writer and I test my examples against my latest rakudo distribution, not camellia?
I can replace every "write" occurrence with "paste result(and maybe add "OUTPUT:" word or something like this)" in original post if it matters.

You copy-pasta them from camelia [...] I'm sorry but the "I don't know how to ... on my phone"-argument is to selfish to be relevant to hopefully millions of readers of docs.perl6.org.

So you hope for millions of readers but how many contributors do you envision? Your argumentation seems to assume all the docs will be written by a handful of nerds who know all about entering Unicode on any device that falls into their hands and who regularly hang out on IRC.
My comments aren't about selfishness, but about pointing out that the proposed format alienates contributors by raising the knowledge required for making a contribution and reduces the amount of drive-by contributions we will get.

And another point, the ␤ doesn't even display right on my Linux dev box. I'm sure I can't be the only one out of these millions of readers who has this problem.

I have no problem requiring unicode -- we're not going to hand out commit bits to everyone. The core contributors can keep things clean, and people contributing docs can do their best based on our submission guidelines when we have them.
Perl 6 has always encouraged unicode where it makes sense, and we should, IMO, continue that trend in the docs (again, where it makes sense)
@zoffixznet, if you're having trouble with the glyphs on this page (like ␤), I'm sure we can help you get that working (and then include that in a how to guide for getting people up and running with unicode)

and then include that in a how to guide for getting people up and running with unicode

sudo apt-get install ttf-unifont brought in the missing glyphs

If it's going to be added to some guide, throw in fonts-freefont-ttf as well.

See also comments in #51.

https://github.com/perl6/doc/commit/be93ca1816
make extract-examples then find examples/ -iname '*.p6' -exec perl6 '{}' ';'
It's a disaster. :) Most of the errors come from missing ; at the end of statements. I may be able to cast a Makefile spell to generate files depending on source files. The 5to6 pods are a bit of a problem in that regard.

As a prototype I made Signature.pod6 compile. Took only two hours. I had to remove FormattingCodes from examples because the parser adds newlines and spaces at spots where they don't belong. In HTML they are not visible (they may pop up on copypasta tho) because spaces and newlines on inline tags are not rendered by the browser. With that change it works quite nicely. I found 8 bugs in those examples. If that rate hold for all .pod6 we are looking about 300 odd bugs. :)
I'm not happy with having to add EVAL to two examples to catch compile time exceptions. Having EVAL blogs around each code block defies the purpose tho, as we want exit codes > 0 so make can complain properly.

The EVAL problem is solved with:
=begin code :skip-test
=end code

https://github.com/perl6/doc/commit/edbad254e0 this commit adds last bits to the Type/ section work.
Now on
This is Rakudo version 2016.07.1-57-g0419194 built on MoarVM version 2016.07-3-gc01472d
all examples in the type documentation can be executed, infinite examples are skipped.
And, actually, I opened this issue to discuss how exactly we should format our output. There are many words(and I really appreciate everyone opinions), but no certain result, so my final thought is like this:

We can use plain # result and sweet # OUTPUT: «result␤» styles. As for Type directory, I've found that they are the most common cases. Styles like #> or other are extremely rare and thus should be considered as bad-formatting and changed.
There are two styles because, okay, there is more than one way to do it.

Any comments?

I would recommend picking a single style. If we have more than one style, we have to write and maintain more code, and more documentation.
I recommend this style, with 2 variants; one for dealing with output, and one for just the last value, in case the example doesn't deal with stdio.
say 3; # OUTPUT  «3␤»

2+5; # RESULT  «7␤»

With this approach then we can have other comments that aren't being tested.
2+5i; # this is a complex number

I don't have a preference on the actual quotes; I think we can use any valid matching quote pair. (or a smaller whitelisted subset)

Let us(or, rather, just lazy me) reanimate this!
So, basically, judging by
➜  doc git:(master) grep -I -r '# .*' doc/ | wc -l
3975

we have about ~4k of comments that need to be revisited and formatted by a style-guide that @coke suggested. I can do it.
we need to mention our new comments style-guide in CONTRIBUTING.md. It will need someone's writing skills.
we need to write an actual script/test that will execute examples and match its output with things in comments. It is a large task and, perhaps, another issue.

Any opposite thoughts?

No? Just go for it!

Actually, we don't need the third clause, see https://irclog.perlgeek.de/perl6/2017-02-01#i_14023735
The needed thing is just a test, not a whole Cool Compilation Suite.

With https://github.com/perl6/doc/pull/1165 https://github.com/perl6/doc/pull/1176 https://github.com/perl6/doc/pull/1181 the first goal is done.
I'm quite short on time now, anybody willing to do the second or the third goal? Perhaps, I'll write a test by myself though.
Also, I think it will be great to mention such major change to CONTRIBUTE.md(when it will be written) in some global news source for contributors(not everyone re-read contribution guidelines every day and we don't want to ruin our unified style quickly) like perl 6 weekly(?). cast @gfldex.

The test is written and soon will be PR'ed.

The original goal was achieved. Closed.


Added libInformation and readerInformation to the python bindings

That looks nice, could you add tests for it ?
Please review @snoyer @Meakk

That looks nice, could you add tests for it ?

Yes, adding them.

I just check the type in the tests, let me know if I need to check the actual content.

I just check the type in the tests, let me know if I need to check the actual content.

I'd say it's not necessary to check for exact content but I'd check for non-emptiness in addition to type where applicable (assert isinstance(xs, list) and xs instead of just assert isinstance(xs, list) for lists and same for dict and str values)
Also you could rename test_plugins.py to test_engine.py (should have been done way back when we started using pytest, better late than never) and add your tests in there to limit the number of files.

@snoyer please review

looks good


Feat/server/like data integration

The client will no longer send a request to facebook if you're not logged in.
removed "User already exists" error shown on server and client
Date ranking algorithm fixed to include user likes
Date Ideas are correctly stored in SQL
venues are stored in SQL
events are stored in SQL
user preferences are stored in SQL

Great job!!!


💡 [FEATURE] - Making the main page and cards more visually appealing and colourful.

Idea Contribution

[X] I have read all the feature request issues.
[X] I'm interested in working on this issue
[X] I'm part of GSSOC organization

Explain feature request
I saw that the website looked very dull from the point of view of a user as it looked plain and simple.
Explain your solution
So I have come up with a solution to transform the cards and add some background colours and animations.

@jfmartinz Please have a look and assign me this issue. Thank you :)

@jfmartinz Please have a look and assign me this issue. Thank you :)

@jfmartinz Please have a look on my PR and accept it. Thank you :)


move sagemaker notebooks to sagemaker folder

yup @leilacc , this was a change requested by Julia so that she can do exactly that :)


Mode visual bloc editing

Good morning,
I'm trying to use mode visual bloc, i put the shortcut on other keyboard shortcut but it's doesn't work.
Visual bloc mode is used, but i can't use the shortcut I{number} - ESC for multiple edit lines.
Thank's for help

Hello,
I'm not sure to fully understand your question, have you changed the visual bloc keyboard shortcut ?
To edit multiple lines, by default, you can press Ctrl+v to enter visual bloc, use arrow keys or hjkl to move the cursors (pressing 10j will select 10 lines bellow), press I (capital i) to enter insert mode, do your edit and finally press ESC to apply to all lines.
Does this help ?

Hello,
I made 'V' shift+v because i edit it.
But after that, what you say doesn't work, here my part of minivim.rc.
let g:currentmode={     \ 'n'  : 'Normal',     \ 'no' : 'N·Operator Pending',     \ 'v'  : 'Visual',     \ ''  : 'V·Line',     \ 'V' : 'V·Block',     \ 's'  : 'Select',     \ 'S'  : 'S·Line',     \ '^S' : 'S·Block',     \ 'i'  : 'Insert',     \ 'R'  : 'Replace',     \ 'Rv' : 'VReplace',     \ 'c'  : 'Command',     \ 'cv' : 'Vim Ex',     \ 'ce' : 'Ex',     \ 'r'  : 'Prompt',     \ 'rm' : 'More',     \ 'r?' : 'Confirm',     \ '!'  : 'Shell',     \ 't'  : 'Terminal', \}

Hi,
If you only edited that part it shouldn't have changed anything related to key bindings.  What you have done here is destroying the vim status line, those "modes" should not be edited. Are you trying to remap entering V-VBlock Shift+V ?
Let's try other leads :

Have you setup MiniVim as instructed in the README ? Copy-pasting the file does not work.
What is your OS, terminal ?

Hi,
If you only edited that part it shouldn't have changed anything related to key bindings. What you have done here is destroying the vim status line, those "modes" should not be edited. Are you trying to remap entering V-VBlock Shift+V ?
Let's try other leads :

Have you setup MiniVim as instructed in the README ? Copy-pasting the file does not work.
What is your OS, terminal ?


add tags to pdnsresolver

Add tags to pdnsresolver

Environment: dev. Pipeline Stage: dev
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # azurerm_private_dns_resolver.pdnsresolver will be updated in-place
  ~ resource "azurerm_private_dns_resolver" "pdnsresolver" {
        id                  = "/subscriptions/779c236c-a27b-405d-b0b8-0bbb5f7b5c67/resourceGroups/rg-xwc-dnsresolve-001/providers/Microsoft.Network/dnsResolvers/pdnsresolver"
        name                = "pdnsresolver"
      ~ tags                = {
          + "ApplicationName"  = "VelocityLandingZone"
          + "BusinessUnit"     = "MOJ"
          + "CostCentre"       = "MOJ"
          + "OwnerName"        =<EMAIL_ADDRESS>          + "ProjectStartDate" = "05102020"
          + "RequesterName"    =<EMAIL_ADDRESS>          + "ServiceLevel"     = "Gold"
          - "businessunit"     = "MOJ" -> null
        }
        # (3 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Environment: dev. Security Scan of Stage: dev has failed a IaC security scan, Please look at https://dev.azure.com/MoJ-OFFICIAL/Velocity-Landing-Zone/_build/results?buildId=48449&view=ms.vss-test-web.build-test-results-tab

Environment: prod. Pipeline Stage: prod
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # azurerm_private_dns_resolver.pdnsresolver will be updated in-place
  ~ resource "azurerm_private_dns_resolver" "pdnsresolver" {
        id                  = "/subscriptions/876eef88-ec3d-47db-b101-ec6f9daefb65/resourceGroups/rg-xwc-dnsresolve-001/providers/Microsoft.Network/dnsResolvers/pdnsresolver"
        name                = "pdnsresolver"
      ~ tags                = {
          + "ApplicationName"  = "VelocityLandingZone"
          + "BusinessUnit"     = "MOJ"
          + "CostCentre"       = "MOJ"
          + "OwnerName"        =<EMAIL_ADDRESS>          + "ProjectStartDate" = "05102020"
          + "RequesterName"    =<EMAIL_ADDRESS>          + "ServiceLevel"     = "Gold"
          - "businessunit"     = "MOJ" -> null
        }
        # (3 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Environment: prod. Security Scan of Stage: prod has failed a IaC security scan, Please look at https://dev.azure.com/MoJ-OFFICIAL/Velocity-Landing-Zone/_build/results?buildId=48449&view=ms.vss-test-web.build-test-results-tab


Example code manifest version is incorrect.

"The source code has been updated from Manifest V2 to Manifest V3"
No it hasn't.

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

ID: ec889040-6707-74fd-9086-d838c15a9172
Version Independent ID: 73d6355a-b256-c8ab-9889-c51603d3052b
Content: Create an extension tutorial, part 2 - Microsoft Edge Development
Content Source: microsoft-edge/extensions-chromium/getting-started/part2-content-scripts.md
Product: microsoft-edge
Technology: extensions
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for reaching out. However, I need a bit more information from you, if you can provide it, to investigate this issue.
I've got two questions in particular:

Which code snippet(s) do you think hasn't(haven't) been migrated?
Did you notice that code snippets have a v2 / v3 tab at the top, to allow you to switch between the 2 versions.

It's not the snippets, it's the code in the Github repo that the comment about being updated to version 3 refers to, and that hasn't been updated.

Oh ok, thanks for replying. In this case, I'll move this issue to that GitHub repo instead, and close this one.
Thanks again!


⚠ Bofrost.be has degraded performance

In 2dfb43a, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1544 ms

Resolved: Bofrost.be performance has improved in 4a260a4.


Poisson Regression

implement Poisson regression (i.e. the pplmhdfe) estimator

Must have:

[ ] - Poisson implementation in the dev branch works fine, except for minor differences in the estimated residuals self.uhat. This obviously affects standard errors, confidence intervals etc. Debug.
[ ] - Implement at least one method to check for separation

Nice to have:

[ ] log likelihood evaluation


Run Analysis Does Not Start

Hi,
-If it is- bug can be reproduced by running Example 7 - 6c. Example's current false for end session and true for closeopenwindows does not work for me. The window is closed and never re-opens. However, it opens a new window and analyses when false-false is used.
Can you check if you can reproduce this issue I have?

Hi,
I confirm that clicking twice to the button works actually. Maybe add as a non-urgent to do? I am closing this in any case. Thanks for clarification.
Here it is my trial:


[Settings] Do not try to launch non-elevated settings process when it…

Summary of the Pull Request
…'s impossible, since elevated WinAppSDK 1.0 apps crash
What is this about:

For v0.58, we've ported Settings app to Win UI 3.0 which is a part of Windows App SDK.
SDK v1.0 doesn't support running elevated applications.
When we launch Settings app from an elevated runner, we try to launch it non-elevated using a common technique involving shell/explorer.exe process.
however, that method (as well as all others) will fail if UAC is completely disabled via a local policy.
unless UAC is disabled, explorer.exe will detect that it was launched elevated and restart itself without elevation, so that shouldn't be a common scenario.

We will change the current code to a warning once WinAppSDK 1.1 is released, which should support running from an elevated context.
What is included in the PR:
Instead of crashing Settings on start, we display a message box explaining the situation.
How does someone test / validate:

launch explorer.exe /nouaccheck elevated to prevent it drop elevated status. the effect is the same as disabling UAC but doesn't require reboots

Quality Checklist

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

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

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

Linked issue here should be https://github.com/microsoft/PowerToys/issues/18015 . Although we should only consider this really fixed after we're able to ship with 1.1 later.
Having a window with the error is really just so users know what's going on.

We do not share the output of CI builds currently.


Implement the embedded-hal-async Traits once stabilized

I believe it's still too early to begin work on this, but once a stable release (or at the very least a more stable alpha release) is available we can revisit this topic.

In<EMAIL_ADDRESS>the traits to implement are:

[x] embedded_hal_async::delay::DelayUs
[x] embedded_hal_async::digital::Wait
[x] embedded_hal_async::i2c::I2c
[x] embedded_hal_async::spi::SpiBus
[x] embedded_hal_async::spi::SpiBusFlush
[x] embedded_hal_async::spi::SpiBusRead
[x] embedded_hal_async::spi::SpiBusWrite
[ ] embedded_hal_async::spi::SpiDevice
[ ] embedded_hal_async::spi::SpiDeviceRead
[ ] embedded_hal_async::spi::SpiDeviceWrite
[x] embedded_hal_async::serial::Write

I think we could and should do this in a separate crate which will use esp-hal under the hood.
That way

we don't "destabilize" the HAL in case of (foreseeable) breaking changes
we need interrupt handling for the wakers ... I think we would mixup things here if we implement it here
we can experiment with it without breaking anything in HAL

For I2C and SPI we will need interrupt support which we don't have yet. But probably we could implement delay and wait for digital inputs any time since we have support for it

I tried something here: https://github.com/bjoernQ/esp32c3-async-rs-experiment
Really just only async gpio input but at least it seems that implementing async HAL in a separate crate is possible and makes sense. The code is terrible but it proves what I wanted to check

Cool, thanks for sharing!
Should we just add an esp-hal-async package or something to this repo, or how did you want to go about doing this?

Didn't even think about that - probably a good idea. I'm just not sure if we want one Async-HAL with features for each chip or one Async-HAL for each chip (similar to what we have for esp-hal). The later would be more consistent with esp-hal - really not sure what the best way would be. Also interesting what the progress for #57 and #80 is

Working on embedded_hal_async::digital::Wait.

digital::Wait implemented in #333.

Working on embedded_hal_async::spi::*

Async SPI (except spi device) implemented in #385

I'm planning to start working on embedded_hal_async::i2c::I2c soon.

@JurajSadel Any progress here?  I'm looking into working on this and would be happy to pick up any work in progress and/or hear any insight.

@konkers Do you have any update regarding async i2c?

Marking DelayUs as complete, it's implemented for embassy-time via the time driver modules.

@JurajSadel I didn't make too much progress before getting sidetracked.   I did some initial digging into the code.  The i2c driver doesn't have interrupt support and the current code relies on busy waiting to feed/drain the fifo.  The i2c peripheral does not support DMA so the code would need to be refactored into something a bit more state machine like in order to feed/drain the fifo in response the the appropriate fifo interrupts.   That's all before adding any of the async support.   I'm heading out on vacation next week and may take my esp32 c3 rust board with me to hack on this.

Working on SpiDevice with the new eha async release. Added serial::Write to the list too.

Marking DelayUs as complete, it's implemented for embassy-time via the time driver modules.

Is there a way to use this with esp-hal-common at the moment? I would like to pass something that implements embedded_hal_async::delay::DelayUs from esp32c3 hal to an async library function.
From what I see, this requires embaddy-time version 0.1.1, which requires embedded-hal 1.0.0-alpha.10, which is incompatible with esp-hal-common 0.8.
I presume that using both, alpha.9 and alpha.10 at the same time is not an option. But maybe someone know a workaround?
Details

error: failed to select a version for `embedded-hal`.
    ... required by package `esp-hal-common v0.8.0`
    ... which satisfies dependency `esp-hal-common = "^0.8"` of package `sk6812-esp32c3-example v0.1.0 (/Users/jdickert/Documents/Git/SK6812/examples/esp32c3)`
versions that meet the requirements `=1.0.0-alpha.9` are: 1.0.0-alpha.9

all possible versions conflict with previously selected packages.

  previously selected package `embedded-hal v1.0.0-alpha.10`
    ... which satisfies dependency `embedded-hal-1 = "=1.0.0-alpha.10"` of package `sk6812-esp32c3-example v0.1.0 (/Users/jdickert/Documents/Git/SK6812/examples/esp32c3)`

failed to select a version for `embedded-hal` which could resolve this conflict

@MabezDev did you ever make any progress with SpiDevice, or did that work get back-burnered?

@jessebraham back-burnered, I didn't really make a start so feel free to take over :)

@jessebraham back-burnered, I didn't really make a start so feel free to take over :)

sad noises :(

I'm working on embedded_hal_async::serial::Write

Hello,
I want to raise another issue of the async traits. They've decided not to include an async read crate for UART.
This means that there should be some other impl in the hal crates that supports async reads.
Another point that they've mentioned is using embedded-io Read & Write for UART instead.
See this comment for more details: https://github.com/rust-embedded/embedded-hal/pull/349#issuecomment-1499465364

Thanks for adding that, we do have a separate tracking issue already for other peripherals:
https://github.com/esp-rs/esp-hal/issues/361
I suppose we should identify which peripherals should/can have async drivers and list them there, though. Haven't updated it in awhile 😁

Just as a small update, there is talk of removing the SpiDeviceRead and SpiDeviceWrite traits from embedded-hal-async. For this reason, we're holding off on implementing these final traits until a new release is available.


feat: Add pypi pip requirements export

This is a follow-up to #1873 that adds a new pixi project export pypi-requirements to export a pip requirements.txt from a pixi lock file. For pixi environments that specify both conda and pypi dependencies, this would allow users to pixi project export conda-explicit-spec output --ignore-pypi-errors together with the new command to create a series of files that could then be installed into a conda env using a combination of conda/mamba and pip/uv.
Since the pip requirements file has many valid ways of representing a package as well as flags, I think we side step those complexities by specifying the full url path from the pixi.lock. I'd definitely like feedback from people who work with pip more since typically live fully in conda-land.
One known complexity is that a requirements.txt that contains any package with a hash specified is treated as if the --require-hashes flag has been used for the whole file. This means that you can't mix packages with hashes and without in the same pip install -r .... It does appear that uv will handle mixed files. To deal with this, I followed the currently recommended workaround and split requirements into two files. There is fix PR in https://github.com/pypa/pip/pull/11968, at least for packages specified from VCS urls, but that's been sitting for a while. As seen for the output of running this on the pypi-source-deps example, this produces:
$ eza --tree test_output
test_output
├── default_linux-64_requirements.txt
├── default_linux-64_requirements_nohash.txt
├── default_osx-64_requirements.txt
├── default_osx-64_requirements_nohash.txt
├── default_osx-arm64_requirements.txt
├── default_osx-arm64_requirements_nohash.txt
├── default_win-64_requirements.txt
└── default_win-64_requirements_nohash.txt

and the outputs look like:
$cat default_linux-64_requirements.txt
https://files.pythonhosted.org/packages/bb/2a/10164ed1f31196a2f7f3799368a821765c62851ead0e630ab52b8e14b4d0/blinker-1.8.2-py3-none-any.whl --hash=sha256:1779309f71bf239144b9399d06ae925637cf6634cf6bd131104184531bf67c01
https://files.pythonhosted.org/packages/1c/d5/c84e1a17bf61d4df64ca866a1c9a913874b4e9bdc131ec689a0ad013fb36/certifi-2024.7.4-py3-none-any.whl --hash=sha256:c198e21b1289c2ab85ee4e67bb4b4ef3ead0892059901a8d5b622f24a1101e90
https://files.pythonhosted.org/packages/ee/fb/14d30eb4956408ee3ae09ad34299131fb383c47df355ddb428a7331cfa1e/charset_normalizer-3.3.2-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl --hash=sha256:90d558489962fd4918143277a773316e56c72da56ec7aa3dc3dbbe20fdfed15b
https://files.pythonhosted.org/packages/22/7e/d71db821f177828df9dea8c42ac46473366f191be53080e552e628aad991/idna-3.8-py3-none-any.whl --hash=sha256:050b4e5baadcd44d760cedbd2b8e639f2ff89bbc7a5730fcc662954303377aac
https://files.pythonhosted.org/packages/ef/a6/62565a6e1cf69e10f5727360368e451d4b7f58beeac6173dc9db836a5b46/iniconfig-2.0.0-py3-none-any.whl --hash=sha256:b6a85871a79d2e3b22d2d1b94ac2824226a63c6b741c88f7ae975f18b6778374
https://files.pythonhosted.org/packages/04/96/92447566d16df59b2a776c0fb82dbc4d9e07cd95062562af01e408583fc4/itsdangerous-2.2.0-py3-none-any.whl --hash=sha256:c6242fc49e35958c8b15141343aa660db5fc54d4f13a1db01a3f5891b98700ef
https://files.pythonhosted.org/packages/31/80/3a54838c3fb461f6fec263ebf3a3a41771bd05190238de3486aae8540c36/jinja2-3.1.4-py3-none-any.whl --hash=sha256:bc5dd2abb727a5319567b7a813e6a2e7318c39f4f487cfe6c89c6f9c7d25197d
https://files.pythonhosted.org/packages/42/d7/1ec15b46af6af88f19b8e5ffea08fa375d433c998b8a7639e76935c14f1f/markdown_it_py-3.0.0-py3-none-any.whl --hash=sha256:355216845c60bd96232cd8d8c40e8f9765cc86f46880e43a8fd22dc1a1a8cab1
https://files.pythonhosted.org/packages/0a/0d/2454f072fae3b5a137c119abf15465d1771319dfe9e4acbb31722a0fff91/MarkupSafe-2.1.5-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl --hash=sha256:f5dfb42c4604dddc8e4305050aa6deb084540643ed5804d7455b5df8fe16f5e5
https://files.pythonhosted.org/packages/b3/38/89ba8ad64ae25be8de66a6d463314cf1eb366222074cfda9ee839c56a4b4/mdurl-0.1.2-py3-none-any.whl --hash=sha256:84008a41e51615a49fc9966191ff91509e3c40b939176e643fd50a5c2196b8f8
https://files.pythonhosted.org/packages/08/aa/cc0199a5f0ad350994d660967a8efb233fe0416e4639146c089643407ce6/packaging-24.1-py3-none-any.whl --hash=sha256:5b8f2217dbdbd2f7f384c41c628544e6d52f2d0f53c6d0c3ea61aa5d1d7ff124
https://files.pythonhosted.org/packages/88/5f/e351af9a41f866ac3f1fac4ca0613908d9a41741cfcf2228f4ad853b697d/pluggy-1.5.0-py3-none-any.whl --hash=sha256:44e1ad92c8ca002de6377e165f3e0f1be63266ab4d554740532335b9d75ea669
https://files.pythonhosted.org/packages/f7/3f/01c8b82017c199075f8f788d0d906b9ffbbc5a47dc9918a945e13d5a2bda/pygments-2.18.0-py3-none-any.whl --hash=sha256:b8e6aca0523f3ab76fee51799c488e38782ac06eafcf95e7ba832985c8e7b13a
https://files.pythonhosted.org/packages/c7/d9/c2a126eeae791e90ea099d05cb0515feea3688474b978343f3cdcfe04523/rich-13.8.0-py3-none-any.whl --hash=sha256:2e85306a063b9492dffc86278197a60cbece75bcb766022f3436f567cae11bdc
https://files.pythonhosted.org/packages/ca/1c/89ffc63a9605b583d5df2be791a27bc1a42b7c32bab68d3c8f2f73a98cd4/urllib3-2.2.2-py3-none-any.whl --hash=sha256:a448b2f64d686155468037e1ace9f2d2199776e17f0a46610480d311f73e3472
https://files.pythonhosted.org/packages/4b/84/997bbf7c2bf2dc3f09565c6d0b4959fefe5355c18c4096cfd26d83e0785b/werkzeug-3.0.4-py3-none-any.whl --hash=sha256:02c9eb92b7d6c06f31a782811505d2157837cea66aaede3e217c7c27c039476c
-e ./minimal-project

and:
$ cat default_linux-64_requirements_nohash.txt
https://github.com/pallets/click/releases/download/8.1.7/click-8.1.7-py3-none-any.whl
git+https://github.com/pallets/flask@f93dd6e826a9bf00bf9e08d9bb3a03abcb1e974c
git+https://github.com/pytest-dev/pytest.git@c947145fbb4aeec810a259b19f70fcb52fd53ad4
git+https://github.com/psf/requests.git@0106aced5faa299e6ede89d1230bd6784f2c3660

I'll add tests and docs once I get some feedback on the design.

@ruben-arts -- I just pushed changes that add the in-module insta tests, updated the docs and removed the flag having to do with conda packages. I also added a flag --split-reqs-no-hashes that controls whether to split the requirements if there are mix of requirements with and without hashes. I defaulted it to true since that's what needed for pip compatibility, but maybe it's better to opt-in. Also I'm not sure if I love the name.
As far as the tests that @abkfenris added in tests/test_export.sh, the one complication that I'm not sure about how best to deal with is that the export files for this (and the conda explicit spec) are platform dependent. Is it safe to assume that all tests will be run on linux-64? It's slightly problematic if you're running locally on osx-64 or osx-arm64. Or is there a robust way to get the platform from within a bash script?

(Just dropping in to say thank you in advance @synapticarbors for working on this, as this will be super helpful for me getting pixi used more in my field!)

@matthewfeickert I hope to pick up this PR again at some point, but I'm still not 100% happy with the design. The requirements.txt is sort of complicated in terms of all of the different specifications it supports (including integrating cli flags), issues with how hashes interact with pip, etc. Since I don't tend to use pypi packages, I'm also not sure what most users might want, and how to support most or typical use cases.


Type regression scrollMarginLeft and scrollMarginRight

Bug report
Describe the bug
As of canary.8 there is a type regression on the scrollMarginLeft and scrollMarginRight css properties.
To Reproduce

working?
sandbox

✅
canary.7

❌
canary.8

❌
canary.15

Additional context
Interestingly, scrollMargin has correct typing.

Fixed in 6f5c03bd8c054386503cb9dabf6ffb0aaf071817

@jonathantneal still an issue in canary.18

This is not the same issue. It is a different issue. We do not currently offer suggestions for nested tokens like $space$1. However, we previously allowed any string as a value, which would prevent $space$1 from throwing a type error. However, permitting any string means TS will not throw a type error when a missing or invalid token is used. This puts us at an impasse.

Do we explicitly allow nested tokens? This preserves strict typing, but may conflate suggestions beyond usefulness.
Do we allow any string? This preserves suggestions, but drops strict typing.
Do we disable string tokens like $space$1 entirely and only permit explicit usage like theme.space[1]? This somewhat preserves suggestions and definitely preserves strict typing, but drops a major feature.

Can it behave just like marginLeft?

Can it behave just like marginLeft?

Yes. This is option #2, where invalid tokens work.

All CSS Properties should work the same, where they accept a string, tokens (strings), and for some of them, numbers.

Fixed in V1. Please refer to migration guide and changelog


Update README.md

take a look the new read.me, we can adjust it if you want

awesome work, thank you for taking the time to update the README

awesome work, thank you for taking the time to update the README


Propagate responses from stage_block().

When calling BlockBlobOperations.stage_block(), an optional callable can
be passed to handle the response and its return value is returned to the
caller of stage_block(). The patch modifies BlobClient to pass this
value back from its stage_block() method, as currently it is swallowed.
Fixes: #8565

Can one of the admins verify this patch?

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: timuralp sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

I modified the existing test to add verification of the return value. Let me know if adding a new test (with a corresponding VCR .yaml file) is preferred.

https://github.com/Azure/azure-sdk-for-python/issues/8565#issuecomment-557336124
For reference

@rakshith91 have you had a chance to look at the changes from December 9th?

Hi @timuralp ; i really apologize for this huge delay. I was on a vacation and couldnt get back in time. The change looks good to me. Feel free to resolve the small conflict and merge it.

@rakshith91 @xiafu-msft updated the PR to resolve the conflict and added the documentation/typing comments.


Support conventional var escaping

Such as: single quotation, and backlsash behind dollar sign
i.e. '${VAR}' or \${VAR} sould not be substituted

Hi @alexey-vostrikov,

Such as: single quotation, and backlsash behind dollar sign i.e. '${VAR}' or ${VAR} sould not be substituted

Thanks for your suggestion. This feature requires to look into the context of the variable, that means to have some custom lexer/parser like this https://github.com/a8m/envsubst/tree/master/parse . When some escape form is supported, it would need more than that, e.g., $$${VAR}, $$$${VAR},..
Though this is quite possible to have new feature, I'd rather keep my tool simple (without a huge refactoring):  It simply deals with normal regular expression search-replace task. One simple thing I can do is to add a limited-context form, ie, ${{VAR}}, but this would make the use a tool lock-in.
If you know how this is done with a minimal effort, I'm more than happy to hear from you.
I have a few todos relevant to your request

[ ] Update README with new section How it works
[ ] Consider to add new form ${{VAR}} (which becomes ${VAR}) or similar simple form.

Thanks a lot.


How to create a stacked bar where all bars start at zero?

Feature Proposal
When a stacked bar graph is made, it adds the other graph on top of the other. I want both to start from 0. beginStartZero doesn't work.
Possible Implementation
No response

So a stacked bar graph without stacking? Do you mean you want the bars to overlap?

Closing as unresponsive


docs: changelog for 0.23.0

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
/milestone 0.23.0
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign mstemm
You can assign the PR to them by writing /assign @mstemm in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 3e2550407a7851ecfd05937562a3748a82f335fd

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, leodido
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,leodido]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


refactor(motion_utils): delete wall marker explicitly

Description
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
I've confirmed the contribution guidelines.
The PR follows the pull request guidelines.
In-review checklist for the PR reviewers

[ ]  The PR reviewers must check the checkboxes below before approval.
[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
After all checkboxes are checked, anyone who has write access can merge the PR.

@kyoichi-sugahara Please write description


Login endpoint gives 404

Robinhood seems to have removed the login endpoint -- https://api.robinhood.com/api-token-auth/ now returns 404 not found. Anybody have a workaround?
edit: see here for workaround: https://github.com/Jamonek/Robinhood/issues/135#issuecomment-420699999

not yet.. opened a support ticket to ask but I don't expect an answer there necessarily

Here's a way to get an 'access_token' from username/pwd: https://github.com/westonplatter/fast_arrow/issues/13#issuecomment-414080185
But that seems to be different than the 'token' we used to get? Robinhood class has auth_token and oauth_token -- I assume the above returns oath)token, not sure how to get auth_token.

someone gave this info- seems interesting
https://github.com/sanko/Robinhood/issues/87

Ok I think I got it working. Basically you use what I linked to here:

Here's a way to get an 'access_token' from username/pwd: westonplatter/fast_arrow#13 (comment)
But that seems to be different than the 'token' we used to get? Robinhood class has auth_token and oauth_token -- I assume the above returns oath_token, not sure how to get auth_token.

Then when you set token in authorization header, change from
self.headers['Authorization'] = 'Token ' + self.auth_token
to
self.headers['Authorization'] = 'Bearer ' + self.oauth_token
(make sure you set oath_token from 'access_token' first)

Great info- what file do you change this in for this library?

Thanks Justin-pierce

When I add your changes, I get a 405 error:
Traceback (most recent call last):   File "/var/www/robinhood/Robinhood/Robinhood.py", line 119, in login     res.raise_for_status()   File "/home/user/.local/lib/python3.5/site-packages/requests/models.py", line 935, in raise_for_status     raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 405 Client Error: Method Not Allowed for url: https://api.robinhood.com/oauth2/token/

Ok I think I got it working. Basically you use what I linked to here:

Here's a way to get an 'access_token' from username/pwd: westonplatter/fast_arrow#13 (comment)
But that seems to be different than the 'token' we used to get? Robinhood class has auth_token and oauth_token -- I assume the above returns oath_token, not sure how to get auth_token.

Then when you set token in authorization header, change from
self.headers['Authorization'] = 'Token ' + self.auth_token
to
self.headers['Authorization'] = 'Bearer ' + self.oauth_token
(make sure you set oath_token from 'access_token' first)
edit: my new login call is
` def login(self,
username,
password,
mfa_code=None):
"""Save and test login info for Robinhood accounts
    Args:
        username (str): username
        password (str): password

    Returns:
        (bool): received valid auth token

    """

    self.username = username
    self.password = password
    payload = {
        'client_id': 'c82SH0WZOsabOXGP2sxqcj34FxkvfnWRZBKlBjFS',
        'expires_in': 86400,
        'grant_type': 'password',
        'password': self.password,
        'scope': 'internal',
        'username': self.username
    }

    if mfa_code:
        payload['mfa_code'] = mfa_code

    try:
        res = self.session.post('https://api.robinhood.com/oauth2/token/', data=payload, timeout=15)
        res.raise_for_status()
        data = res.json()
        print(data)
    except requests.exceptions.HTTPError:
        raise RH_exception.LoginFailed()

    if 'mfa_required' in data.keys():           # pragma: no cover
        raise RH_exception.TwoFactorRequired()  # requires a second call to enable 2FA

    if 'access_token' in data.keys():
        self.oauth_token = data['access_token']
        self.headers['Authorization'] = 'Bearer ' + self.oauth_token
        return True

    return False`

Not sure if this token has limitations or not. I was able to get my positions and sell a stock using it but that's basically all I've tested.
I'll try to do proper pull request later.

Thanks Justin... I was able to use this and I updated the Robinhood.py script as such and was able to resolve my authentication error reported as  "No JSON object could be decoded" earlier.
The code was updated as per below (I've commented the older code out for reference)
    #"login":  "https://api.robinhood.com/api-token-auth/",
    "login":  "https://api.robinhood.com/oauth2/token/",
    "margin_upgrades": "https://api.robinhood.com/margin/upgrades/",
    "markets": "https://api.robinhood.com/markets/",
    "notification_settings": "https://api.robinhood.com/settings/notifications/",
    "notifications": "https://api.robinhood.com/notifications/",
    "orders": "https://api.robinhood.com/orders/",
    "password_reset": "https://api.robinhood.com/password_reset/request/",
    "portfolios": "https://api.robinhood.com/portfolios/",
    "positions": "https://api.robinhood.com/positions/",
    "quotes": "https://api.robinhood.com/quotes/",
    "user": "https://api.robinhood.com/user/",
    "watchlists": "https://api.robinhood.com/watchlists/",
    "optionsOrders":"https://api.robinhood.com/options/orders/",
    "optionsPositions":"https://api.robinhood.com/options/positions/"
}

session = None
username = None
password = None
headers = None
auth_token = None
positions = None

##############################
#Logging in and initializing
##############################

def __init__(self):
    self.session = requests.session()
    try:
        self.session.proxies = urllib.getproxies() #py2
    except:
        self.session.proxies = urllib.request.getproxies() #py3
    self.headers = {
        "Accept": "*/*",
        "Accept-Encoding": "gzip, deflate",
        "Accept-Language": "en;q=1, fr;q=0.9, de;q=0.8, ja;q=0.7, nl;q=0.6, it;q=0.5",
        "Content-Type": "application/x-www-form-urlencoded; charset=utf-8",
        "X-Robinhood-API-Version": "1.0.0",
        "Connection": "keep-alive",
        "User-Agent": "Robinhood/823 (iPhone; iOS 7.1.2; Scale/2.00)"
    }
    self.session.headers = self.headers

def login(self, username, password, mfa_code=None):
    self.username = username
    self.password = password
    self.mfa_code = mfa_code
    #fields = { 'password' : self.password, 'username' : self.username, 'mfa_code': self.mfa_code }
    #fields = { 'password' : self.password, 'username' : self.username }

    if mfa_code:
        fields = { 'client_id' : 'c82SH0WZOsabOXGP2sxqcj34FxkvfnWRZBKlBjFS',
                    'expires_in' : 86400,
                    'grant_type': 'password',
                    'password' : self.password,
                    'scope' : 'internal',
                    'username' : self.username,
                    'mfa_code': self.mfa_code }
    else:
        fields = { 'client_id' : 'c82SH0WZOsabOXGP2sxqcj34FxkvfnWRZBKlBjFS',
                    'expires_in' : 86400,
                    'grant_type': 'password',
                    'password' : self.password,
                    'scope': 'internal',
                    'username' : self.username }
    try:
        data = urllib.urlencode(fields) #py2
    except:
        data = urllib.parse.urlencode(fields) #py3
    res = self.session.post(self.endpoints['login'], data=data)
    #res.raise_for_status()
    res = res.json()
    #print(data)
    try:
        #self.auth_token = res['token']
        self.oauth_token = res['access_token']
    except KeyError:
        return res
    #self.headers['Authorization'] = 'Token '+self.auth_token
    self.headers['Authorization'] = 'Bearer ' + self.oauth_token
    return True

noticed this issue as well and opened a PR for the robinhood-node package over at https://github.com/aurbano/robinhood-node/pull/78 to use the oauth2 endpoints in case this is helpful though it looks like its all good.

Thank you for solving this so quick!

With this new authentication it appears to only allow one API connection per IP address.
If anyone knows the call to logout that would be appreciated.
I implemented the above changes on my laptop and then when i went to throw it on my server it wouldnt allow another login from the same IP.
I narrowed this down via VPN and it let me log in under a different IP.
Not sure if this will expire at some point. We shall see.

With this new authentication it appears to only allow one API connection per IP address.
If anyone knows the call to logout that would be appreciated.
I implemented the above changes on my laptop and then when i went to throw it on my server it wouldnt allow another login from the same IP.
I narrowed this down via VPN and it let me log in under a different IP.
Not sure if this will expire at some point. We shall see.

If the 'expires in' field is accurate, it'll expire in 24h -- though certain activity might keep it alive. Definitely something to look into as we may need to occasionally refresh our tokens.

derekshreds on reddit filled in info for refreshing token:

The json returned when you get the access_token also returns refresh_token.

post to https://api.robinhood.com/oauth2/token/ with:
"refresh_token": [the string from refresh_token]
"grant_type":"refresh_token"
"client_id":"c82SH0WZOsabOXGP2sxqcj34FxkvfnWRZBKlBjFS"

This will return a new access_token and refresh_token in json. Not sure if you can manually expire the token / logout. The tokens expire after 86400 seconds, just for everyone's information.

Anyone seeing the following error even with the above changes?

requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.robinhood.com/portfolios/

works great!! Thank you so much!

Anyone seeing the following error even with the above changes?

requests.exceptions.HTTPError: 401 Client Error: Unauthorized for url: https://api.robinhood.com/portfolios/

Yes seeing the same issue. Anybody knows why? Thanks

@gautammatta
The file probably not been corrected properly, I uploaded my version here:
https://github.com/tedchou12/Robinhood/blob/master/Robinhood/Robinhood.py
feel free to try it out.

Can someone create a PR for this is they've actually got it working? @desicruizer @justin-pierce

@tedchou12 do you have this working still?

@batcavenet did you just copy past the code he posted? I tried that and still had issues. If you have a working version, can you please create a PR?

@edPratt
I think you don't have the endpoint.py file editted.
    return "https://api.robinhood.com/oauth2/token/"```
If you have issue trying reinstalling with the package I uploaded, I have it working quite well still.

Update: I got it working! @tedchou12 . I now need to open a pr, but need to request access from @Jamonek I believe. Thanks all

good good. I am not sure if this is still alive. But feel free to ask me if you need.

I'm still having a problem logging in.  I updated the Robinhood.py in the Robinhood folder with the one created by @tedchou12.  Still getting the simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0) error.

My bad.  I hadn't updated the endpoint.py file that @tedchou12 mentioned above.  As soon as I edited that, I was able to login without error.  Thanks!

is anyone able to get this to work with MFA

@tedchou12 @desicruizer @justin-pierce can you guys take a look at my most recent issue? "get_options_data 404". Since you guys seemed to solve this I figured you might be able to dig into the get_options_data function. There are a few changes I had to make to get to the 404 error (bugs in the function unrelated to auth), so check out this branch https://github.com/edPratt/Robinhood/tree/fix-options. Thank you in advance to whoever takes a look!

Does anyone have a curl command approach to

Ok I think I got it working. Basically you use what I linked to here:

Here's a way to get an 'access_token' from username/pwd: westonplatter/fast_arrow#13 (comment)
But that seems to be different than the 'token' we used to get? Robinhood class has auth_token and oauth_token -- I assume the above returns oath_token, not sure how to get auth_token.

Then when you set token in authorization header, change from
self.headers['Authorization'] = 'Token ' + self.auth_token
to
self.headers['Authorization'] = 'Bearer ' + self.oauth_token
(make sure you set oath_token from 'access_token' first)
edit: my new login call is
` def login(self,
username,
password,
mfa_code=None):

Does anyone have a curl command approach to doing this. I have written all my scripts in R and run them using system commands in linux.

Just figured out the linux curl command way
https://github.com/Jamonek/Robinhood/issues/176#issuecomment-504604729


[ENH] Update Syncmeta dependencies

There is a dependency in Syncmeta which is limited to node version less than 11.
We should see if this dependency can be updated, removed or replaced

https://github.com/rwth-acis/Social-Bot-Framework/issues/46


First pass at NukeOps creation cleanup

About the PR
Breaks up the logic for starting Nuclear Ops mode into smaller, reusable pieces. This PR does NOT include the actual code to start up NukeOps midround.  Addresses #9899
Screenshots

N/A
Changelog

#10005 was created a few minutes after this, That's probably a better candidate to pull at a glance. I will leave the confirmation of that to the maintainers.

Conflict should be an easy resolve, I just added a check after shuttle spawn to check outpost wasn't deleted and if it was then abort.


Performance problems: Too many requests causing very slow loading

I have an archetype list with 6 data types including one media picker and two rich text fields. The list is around 100 items long and the back-office page takes over 3 minutes to load. Initially the page was making over a 1200 requests but disabling  Deep Datatype Requests brought that down to 452 as seen below.

While it has made an improvement it's still unacceptably slow, 30 seconds minimum with  caching just for the list to appear and another 1.7 minutes before the last rich text box loads and you can start editing. The publishing takes several minutes as well.
I'm sure a lot of you have much bigger lists that a 100 items. Am I missing something?

Hello and thank you for using Archetype.
First off, I would agree that the time you are waiting are excruciatingly long.
However, Archetype was never meant to store massive amounts of data in the way you are using it.
Loading 600 datatypes will inevitably take a long time.  Archetype is a simple wrapper that loads each datatype that is configured and knows nothing about the implementation of any of the child properties.  So if a child datatype loads external files or makes service/DB calls, it's nothing Archetype can optimize.
The best way to use Archetype is to use it sparingly per Umbraco node (list of 10 things or so).  With respect, storing so much data in a single list and expecting the UI to load 600 controls (and then run the AngularJS digest) should take a long time (unfortunately).
My suggestion would be to break up your data into a simpler design that leverages several Umbraco nodes (distribute the load) using the MNTP mixed with Archetype.
Again thank you for the feedback.

Thanks Kevin for the quick response. I guess there is nothing to do but use a different approach.


Double autocompletebox dropdown

Describe the bug
When typing in autocompletebox it sometimes creates two dropdowns
To Reproduce
Create autocompletebox with a lot of items
Expected behavior
just one dropdown
Avalonia version
11.0.10
OS
Windows
Additional context

Never seen it. Looks like a custom style. Can you wire a minimum sample together and file it here?

This is the only styling i have applied to the AutoCompleteBox i dont have any behaviours linked
<Style Selector="AutoCompleteBox">
	<!-- Default font size of the Application -->
	<Setter Property="IsTextCompletionEnabled" Value="True"/>
	<Setter Property="MinimumPrefixLength" Value="0"/>
</Style>
<Style Selector="AutoCompleteBox">
        <Setter Property="CornerRadius" Value="{DynamicResource CornerRadius}"/>
</Style>
<Style Selector="AutoCompleteBox.Expr">
        <Setter Property="Background" Value="{DynamicResource ExprColor}"/>
</Style>
<Style Selector="AutoCompleteBox.Director">
       <Setter Property="Background" Value="{DynamicResource DirectorColor}"/>
</Style>
<Style Selector="AutoCompleteBox.Mandatory">
       <Setter Property="Background" Value="{DynamicResource MandatoryColor}"/>
</Style>

Can't reproduce. Please file a sample App


Remove divider

Please remove the divider of the last proposal

Please add your planning poker estimate with ZenHub @rachelhox


Fix some PR comment

Issue

none

Overview (Required)

Fix some PR comment from @jmatsu #359

112fd7b : Swap if statement condition orde https://github.com/DroidKaigi/conference-app-2017/pull/359#pullrequestreview-22684993
915a451 : Rename constant value https://github.com/DroidKaigi/conference-app-2017/pull/359#pullrequestreview-22685493
33614bb : Use Rect instead of Point and primitive integer https://github.com/DroidKaigi/conference-app-2017/pull/359#pullrequestreview-22685234
2ad1552 : Simplify AppBarLayout expanded/collapsed check https://github.com/DroidKaigi/conference-app-2017/pull/359#pullrequestreview-22686021
fca3292 : Check callback is null or not https://github.com/DroidKaigi/conference-app-2017/pull/359#pullrequestreview-22685520
0d77f42 : Fix duplicate view translation when AppBar is null

Links

https://github.com/DroidKaigi/conference-app-2017/pull/359

Screenshot

Before
After

Mmm, why do tests fail... 🤔
@chibatching
So sorry, could you please merge or rebase master?

I run ./gradlew lint on local machine on this and master branch, and I got some lint error.
I think we should fix this lint error.

@chibatching
Got it. Thank you for reporting! We are investigating it...

@chibatching
Finally, fixed. 🎉
It was caused by a connection between circleci and github 😞
Anyway, your changes LGTM!
Thank you for tackling!

Thanks for review and merge!!


Fix docstrings of a_initiate_chat

Why are these changes needed?
Fix a docstring error in a_initiate_chat
Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5b217c9) 34.24% compared to head (0f02c17) 33.00%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1539      +/-   ##
==========================================
- Coverage   34.24%   33.00%   -1.25%
==========================================
  Files          42       40       -2
  Lines        5098     5090       -8
  Branches     1165     1165
==========================================
- Hits         1746     1680      -66
- Misses       3209     3270      +61
+ Partials      143      140       -3

Flag
Coverage Δ

unittests
33.00% <ø> (-1.25%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[move-prover] Integrating specification language support into ./language/move-prover.

Motivation
This adapts concepts of David's spec language prototype and combines it with Sam's new spec support in the Move parser. It also refactors and cleans up some of the tool level plumbing for the move prover, so we can hopefully more productively iterate on it.
The spec language support is not complete, as indicated the by TODO markers in the source.
Quite a bit work in this PR is about getting a better command line interface and test support for MVP (the Move Prover). I apologize to have not split this out. If you are mostly interested in the actual spec translation (and its open problems), see src/spec_translator.rs, and the related test output at tests/goldenfiles/test-specs.bpl.
Have you read the [Contributing Guidelines on pull requests]
Yes
Test Plan
The test infra has been rewritten based on the new src/driver.rs. All existing tests pass with the new infra (i.e. compile under boogie). Golden files are updated mostly because of cosmetic changes.
A new test has been added as test_mvir/test-specs.mvir -> test/goldenfiles/test-specs.bpl.
Related PRs
NA

@bors-libra r=sblackshear

:pushpin: Commit 3d43adf has been approved by sblackshear

:hourglass: Testing commit 3d43adfbb330b33bcb68e6e7450b9ea456ad694f with merge 7d5ad6852d6981305a28b5a645b451bcfd972363...

:sunny: Test successful - checks-circle_commit_workflow
Approved by: sblackshear
Pushing 7d5ad6852d6981305a28b5a645b451bcfd972363 to master...


[PYTHON] Upgrade to Py4J 0.10.7

What changes were proposed in this pull request?
This PR proposes to upgrade Py4J to 0.10.7.
Notable changes:

From Py4j 0.10.7, Python's 3.6 support is officially added which PySpark currently claims. See https://github.com/bartdag/py4j/issues/301.

How was this patch tested?
Existing tests, and Jenkins tests.

Test build #90185 has started for PR 21233 at commit f29750c.

JIRA was deleted per http://www.apache.org/security/committers.html#vulnerability-handling

Please pend this for now.

cc @vanzin

Test build #90185 has finished for PR 21233 at commit f29750c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/90185/
Test PASSed.


fix(compiler-core): emit TS-compatible function declaration when requested

In our webpack setup, like in vuejs/vue-loader#1915, we're seeing TS7006: Parameter 'n' implicitly has an 'any' type. warnings for all of our <script type="ts" setup> vue modules with a <style lang="less" scoped> block in the same file.
Currently, genHoists is generating the following line:
const _withScopeId = n => (_pushScopeId("data-v-119f721c"),n=n(),_popScopeId(),n)

This patch adds an explicit parameter definition for the n parameter when valid typescript code is requested.
const _withScopeId = (n: () => any) => (_pushScopeId("data-v-119f721c"),n=n(),_popScopeId(),n)

bump :)

Resolved the merge conflicts

+1
This is a very much-needed fix for those who depend on newer versions of vue-loader, and who (quite understandably) don't want to disable noImplicityAny or resort to other hacky methods as described in vuejs/vue-loader#1915
It should be a necessity to generating TS code that compiles with strict compiler options enabled in 2024.

/ecosystem-ci run

/ecosystem-ci run


Objects on Nodes and other kubernetes pages disappear after a while

Bug description
On windows, if I have some node available, ie. if I create a kind cluster (there is a node present) and open a node page, kind cluster node is visible. After a while, it disappear. I can bring it back if I switch the kube context to something else and back.

Operating system
Windows 10
Installation Method
Installer from website/GitHub releases
Version
next (development version)
Steps to reproduce
Not easily reproducible. Have kind cluster available and then some other context to switch to and wait a few tens of seconds if kind-cluster context related resources disapper. I have seen it on both windows and linux. After windows went to sleep and was awaken, the problem is gone.
Relevant log output
main ↪ Trying to watch routes on the kubernetes context named "kind-kind-cluster" but got a connection refused, retrying the connection in 75s. HttpError: HTTP request failed)

main ↪ Trying to watch deployments on the kubernetes context named "kind-kind-cluster" but got a connection refused, retrying the connection in 82s. Error: connect ECONNREFUSED <IP_ADDRESS>:44953)

main ↪ Trying to watch pods on the kubernetes context named "kind-kind-cluster" but got a connection refused, retrying the connection in 80s. Error: connect ECONNREFUSED <IP_ADDRESS>:44953)

Additional context
If I do not filter (I view all level) event level in console, I can see verbose level information as seen in above log output.
Output of kubectl seems alright:
kubectl get pods -A
NAMESPACE            NAME                                                 READY   STATUS      RESTARTS   AGE
kube-system          coredns-7db6d8ff4d-9t4rl                             1/1     Running     0          11h
kube-system          coredns-7db6d8ff4d-sqrl5                             1/1     Running     0          11h
kube-system          etcd-kind-cluster-control-plane                      1/1     Running     0          11h
kube-system          kindnet-tn94s                                        1/1     Running     0          11h
kube-system          kube-apiserver-kind-cluster-control-plane            1/1     Running     0          11h
kube-system          kube-controller-manager-kind-cluster-control-plane   1/1     Running     0          11h
kube-system          kube-proxy-dd8b4                                     1/1     Running     0          11h
kube-system          kube-scheduler-kind-cluster-control-plane            1/1     Running     0          11h
local-path-storage   local-path-provisioner-988d74bc-m2grp                1/1     Running     0          11h
projectcontour       contour-7d4b95459-q4vqh                              1/1     Running     0          11h
projectcontour       contour-7d4b95459-tn5dg                              1/1     Running     0          11h
projectcontour       contour-certgen-v1.24.2-9gvmw                        0/1     Completed   0          11h
projectcontour       envoy-8r9fg                                          2/2     Running     0          11h

kubectl get services -A
NAMESPACE        NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)                      AGE
default          kubernetes   ClusterIP      <IP_ADDRESS>       <none>        443/TCP                      11h
kube-system      kube-dns     ClusterIP      <IP_ADDRESS>      <none>        53/UDP,53/TCP,9153/TCP       11h
projectcontour   contour      ClusterIP      <IP_ADDRESS>   <none>        8001/TCP                     11h
projectcontour   envoy        LoadBalancer   <IP_ADDRESS>    <pending>     80:32314/TCP,443:31344/TCP   11h

kubectl get deployments -A
NAMESPACE            NAME                     READY   UP-TO-DATE   AVAILABLE   AGE
kube-system          coredns                  2/2     2            2           11h
local-path-storage   local-path-provisioner   1/1     1            1           11h
projectcontour       contour                  2/2     2            2           11h

Tried several times to reproduce without success

If no reproducing during next week, I will close issue.

Happened during testing of 1.12.0 on Mac:
https://github.com/user-attachments/assets/64053e4f-7d5e-447d-98b2-a06a4654614f

I think it's related to devsandbox not allowing access to Nodes object, will check

Blocked by #8590

It seems you have deployed something on your Kind/Minikube cluster. Can you describe what have been deployed to ?

I managed to get it reproduce: created 2 Kubernetes contexts (minikube and DevSandbox) and wrote a script that switches context every second. After a while (about 1000s), Nodes pages is always empty but this is caused by Podman machine not responding anymore. As it was on WSL, I will try to reproduce on MacOS/Applehv as well

Great that you have reproduced it. It never occurred on purpose. Just while playing with kubernetes cluster/resources during testing.

@jeffmaury I am trying to reproduce the issue now, but no success so far. At least not on my Linux machine. I will see if I can reproduce on some machine in the labs so it can be examined.

@odockal ok to close this one


python3Packages.angr: 9.1.11752 -> 9.1.12332

Description of changes

Things done
Update  angr stack.

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 164888 run on x86_64-linux 1

16 packages built:

python310Packages.ailment
python310Packages.angr
python310Packages.angrcli
python310Packages.angrop
python310Packages.archinfo
python310Packages.claripy
python310Packages.cle
python310Packages.pyvex
python39Packages.ailment
python39Packages.angr
python39Packages.angrcli
python39Packages.angrop
python39Packages.archinfo
python39Packages.claripy
python39Packages.cle
python39Packages.pyvex

@ofborg build python39Packages.angr python310Packages.angr


Issue with building Atom with node 5.1 and npm 3.4.1

I am getting an error everytime I try and build Atom with node.js 5.1 and npm 3.4.1. It can't find the "npm-registry client". The issue persists even after a reinstall of npm and node. I'm running Arch Linux.
The error is below.

Error: Cannot find module 'npm-registry-client'
at Function.Module._resolveFilename (module.js:338:15)
at Function.Module._load (module.js:289:25)
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Object. (/run/media/kamran/External/Projects/atom/build/node_modules/npm/lib/cache/caching-client.js:9:22)
at Module._compile (module.js:425:26)
at Object.Module._extensions..js (module.js:432:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:313:12)
at Module.require (module.js:366:17)

I think it's a problem with npm v3.4.1. Take a look: npm/npm#10394

I have not tried building Atom with npm 3.4. Can you try with an older version of node/npm?

<EMAIL_ADDRESS>works (that's npm@next at the time of writing)

@maxbrunsfeld seems to be building fine with npm 3.5.0.

Ok I'm going to close this out as it seems like it was an npm issue that's been resolved.


[HUDI-5642] Enable schema reconciliation by default

Change Logs
Enable schema reconciliation by default as commit should go through with the wider schema in case of conflict.
Impact
Schema will be reconciled by default.
Risk level (write none, low medium or high below)
low
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@codope I think we should create a JIRA issue for it.

The test failures are due to SchemaCompatibiltyException. One thing to note is that for an incoming schema with compatible projection of the latest table schema, the table schema is chosen but it may lose any data type promotion. See https://github.com/apache/hudi/blob/3979848a499131db594bbb49eb9ab160531a729d/hudi-spark-datasource/hudi-spark-common/src/main/scala/org/apache/hudi/HoodieSparkSqlWriter.scala#L566-L574

@codope please help me understand why this is critical priority?

please help me understand why this is critical priority?

this was planned to be done in one of the prev releases but there are some issues. I've lowered the priority for now, but we should take it up for 0.14.0. Updated the fix version on JIRA appropriately.

this was planned to be done in one of the prev releases but there are some issues. I've lowered the priority for now, but we should take it up for 0.14.0. Updated the fix version on JIRA appropriately.

That's cool, but we are not expecting to introduce any schema data type related regressions.


TS: Support for url encoded requests

Allows the TypeScript client to generate application/x-www-form-urlencode requests.
Also requires that the ConsumesAttribute is taken into account on controller actions #1849.

Info: Consumes is probably not available in openapi 3 and thus we need to get this info from somewhere else

Maybe add
        public bool ConsumesFormUrlEncoded =>
            _operation.ActualConsumes?.Any(c => c == "application/x-www-form-urlencoded") == true ||
            _operation.ActualResponses.Any(r => r.Value.Content.Any(c => c.Key == "application/x-www-form-urlencoded"));

for OpenApi3 support

I'll check up on this when I get home.
Why are we using _operation.ActualResponses for checking if the operation should do a url encoded request? Instead checking something like _operation.RequestBody would make more sense and follow the OpenApi 3 specification, although my brief inspection on SwaggerOperation shows that will not be possible at the moment.

Ah shit, thats completely wrong what i posted - you are right :-)

ConsumesFormUrlEncoded is now checking the _operation.RequestBody for a url encoded media type. Although currently SwaggerOperation.RequestBody doesn't seem to be populated correctly when a document is being generated, though that is probably a separate issue.

Although currently SwaggerOperation.RequestBody doesn't seem to be populated correctly when a document is being generated, though that is probably a separate issue.

If the schema type is OpenApi3 it should be populated as expected, is that not the case?

Is this PR ready?

It is populated if the parameter has a [FromBody] attribute on it, but in OpenApi3 formData is not a valid parameter in-type, therefore these also have to generate in the SwaggerOperation.RequestBody, is that not so?
This PR should be good to go.

It is populated if the parameter has a [FromBody] attribute on it, but in OpenApi3 formData is not a valid parameter in-type, therefore these also have to generate in the SwaggerOperation.RequestBody, is that not so?

Ok, is there already an issue for that?

This PR should be good to go after the ConsumesAttribute is taken into account.

Just looking into this other PR

I did notice that the other PR #1849 does only take care of the ConsumesAttribute with the AspNetCoreToSwaggerGenerator I guess without testing, The WebApiToSwaggerGenerator used in for example the tests is not covered by this.
For my testing needs I have added a simple OperationConsumesProcessor in the WebApiToSwaggerGeneratorSettings, I can include this as well since #1849 seems to be only about the ASP.NET core generation specifically.

So we need the same for web api as in the other PR? That would be the "right" way, correct?

That would be correct, I have added a OperationConsumesProcessor that should take care of this with the WebApi generator.

Can you fix the conflicts? But then i think it looks good...

The conflicts are now resolved.


Expanded seqJSON should include metadata to trace back to source activity

Add metadata fields to seqJSON header to indicate planID, simulation data set ID
Add metadata per command to indicate simulated activity instance ID

Fairly certain bullet point 2 is complete already https://github.com/NASA-AMMOS/aerie/blob/develop/sequencing-server/src/defaultSeqBuilder.ts#L17

Happy to take this one. Should be a quick change.


Update for Wagtail 4.2; Remove 2.x support

This PR fully updates wagtail streamforms to 4.2. All the tests are passing, and I've tested the changes locally to make sure there are no errors. I also went ahead and updated the submission listing template to be in line with the new wagtail form submission template, with the filters now on the side. The old listing template was broken with the recent admin look changes, and I'm not sure if there's a clean way to redo that look.
Couple of notes on compatibility - I've maintained compatibility with wagtail 3.x, although I'm not sure that it's needed. This also removes 2.x support, since there were substantial breaking changes in 3.x and 4.x.
Let me know if you have any concerns or questions!

It looks like most of these fixes have been integrated with #211 , but there are still issues with the example project, as it still will not run with the latest version of wagtail. Let me know if you want me to rebase this branch so that those changes can be applies.


Add STM32H7 Series USB Device Support

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.
This request addresses USB device driver support on the STM32H7 series. It is not currently supported by Zephyr.
Describe why you are asking for this support?
I have attempted to bring up USB device support myself (see below), but need help understanding where some of the pieces belong (clock and peripheral config) as well as hoping to get support from people more expert in the STM USB implementation.
I am willing, to the best of my abilities, to support this functionality if it makes it into Zephyr.
Additional context
STM32H7 Overview
USB hardware and PCB guidelines using STM32 MCUs - Application note
My Efforts So Far
I have started work in this development branch. I started with trying to bring up the USB FS peripheral on the NUCLEO-H753. I added it to the stm32h7.dtsi and to nucleo_h753zi.dts. (One area where I need help is in understanding how to populate some of the values in the DTS entry for this peripheral, how to find all of the appropriate register values).
With these changes, the samples/subsys/usb/hid sample would compile, but the peripheral failed to initialize.
[00:00:05.006,000] <dbg> main.main: Enabling usb...
[00:00:05.006,000] <dbg> usb_device.usb_enable: lock usb_enable_lock mutex
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_set_status_callback:
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_attach:
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_stm32_init: Pinctrl signals configuration
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_stm32_init: HAL_PCD_Init
[00:00:05.025,000] <err> usb_dc_stm32: PCD_Init failed, 1
[00:00:05.025,000] <dbg> usb_device.usb_enable: unlock usb_enable_lock mutex
[00:00:05.025,000] <err> main: Failed to enable USB

Comparing the init and config in Zephyr to a working USB STM32H7 project in STM32CubeIDE, I tried adding some USB peripheral config that seemed to be missing for H7.
With these changes, the device will now initialize! There is even different behavior on startup if a USB host is attached. Specifically, the device is suspended.
[00:00:00.006,000] <dbg> main.main: Starting application
[00:00:05.006,000] <dbg> main.main: Enabling usb...
[00:00:05.006,000] <dbg> usb_device.usb_enable: lock usb_enable_lock mutex
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_set_status_callback:
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_attach:
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_stm32_init: Pinctrl signals configuration
[00:00:05.006,000] <dbg> usb_dc_stm32.usb_dc_stm32_init: HAL_PCD_Init
[00:00:05.059,000] <dbg> usb_dc_stm32.usb_dc_stm32_init: HAL_PCD_Start
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_configure: ep 0x00, previous ep_mps 64, ep_mps 64, ep_type 0
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_configure: ep 0x80, previous ep_mps 64, ep_mps 64, ep_type 0
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_set_callback: ep 0x00
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_set_callback: ep 0x80
[00:00:05.062,000] <dbg> usb_device.composite_setup_ep_cb: set cb, ep: 0x81
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_set_callback: ep 0x81
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_enable: ep 0x00
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_enable: HAL_PCD_EP_Open(0x00, 64, 0)
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_enable: ep 0x80
[00:00:05.062,000] <dbg> usb_dc_stm32.usb_dc_ep_enable: HAL_PCD_EP_Open(0x80, 64, 0)
[00:00:05.062,000] <dbg> usb_device.usb_enable: unlock usb_enable_lock mutex
[00:00:05.068,000] <dbg> usb_dc_stm32.HAL_PCD_SuspendCallback:
[00:00:05.068,000] <inf> usb_hid: Device suspended
[00:00:05.068,000] <dbg> main.status_cb: status 5 unhandled

Unsurprisingly, the device does not enumerate.
At this point I'm not sure what's missing. Some fundamental incompatibility of the H7 USB device that's not obvious from looking at their header and example files, or something with the configuration of the Zephyr stack in terms of device registers, interrupts, and pinouts.

I am planning to contribute this next week, but I don't want to promise anything. So here are the steps you need:

In the device tree you should write clocks = <&rcc STM32_CLOCK_BUS_AHB1 0x8000000>; instead of clocks = <&rcc STM32_CLOCK_BUS_AHB2 0x00000080>;.
Enable HSI48 clock: in the line that starts with #if defined(RCC_HSI48_SUPPORT) || defined(CONFIG_SOC_SERIES_STM32WBX) add also the CONFIG_SOC_SERIES_STM32H7X.
Disable ulpi clock using: __HAL_RCC_USB2_OTG_FS_ULPI_CLK_DISABLE.
In the end of the function usb_dc_stm32_init call HAL_PWREx_EnableUSBVoltageDetector

@shlomow Thank you for this—I've applied these changes to my dev branch, and now the device will enumerate on my MacBook! 🎉
Unfortunately, the device gets suspended shortly after enumeration:
[00:00:00.314,000] <inf> usb_hid: Device configured
[00:00:00.314,000] <dbg> main.status_cb: USB_DC_CONFIGURED
[00:00:00.314,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x80, len 0
[00:00:00.314,000] <dbg> usb_dc_stm32.HAL_PCD_DataInStageCallback: epnum 0x00
[00:00:00.314,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x80, status 0x02
[00:00:00.333,000] <dbg> usb_dc_stm32.HAL_PCD_SetupStageCallback:
[00:00:00.333,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x00, status 0x00
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_read_wait: ep 0x00, 8 bytes, 0+8, 0x24002288
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x00, len 64
[00:00:00.333,000] <dbg> usb_device.custom_handler: bRequest 0x06, wIndex 0x0000
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x80, len 32
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x80, len 0
[00:00:00.333,000] <dbg> usb_dc_stm32.HAL_PCD_DataInStageCallback: epnum 0x00
[00:00:00.333,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x80, status 0x02
[00:00:00.333,000] <dbg> usb_dc_stm32.HAL_PCD_DataOutStageCallback: epnum 0x00, rx_count 0
[00:00:00.333,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x00, status 0x01
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_read_wait: ep 0x00, 0 bytes, 0+0, 0x800a0e6
[00:00:00.333,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x00, len 64
[00:00:00.334,000] <dbg> usb_dc_stm32.HAL_PCD_SetupStageCallback:
[00:00:00.334,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x00, status 0x00
[00:00:00.334,000] <dbg> usb_dc_stm32.usb_dc_ep_read_wait: ep 0x00, 8 bytes, 0+8, 0x24002288
[00:00:00.334,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x00, len 64
[00:00:00.334,000] <dbg> usb_device.class_handler: bRequest 0x0b, wIndex 0x0000
[00:00:00.334,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x80, len 0
[00:00:00.334,000] <dbg> usb_dc_stm32.HAL_PCD_DataInStageCallback: epnum 0x00
[00:00:00.334,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x80, status 0x02
[00:00:00.338,000] <dbg> usb_dc_stm32.HAL_PCD_SetupStageCallback:
[00:00:00.338,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x00, status 0x00
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_read_wait: ep 0x00, 8 bytes, 0+8, 0x24002288
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x00, len 64
[00:00:00.338,000] <dbg> usb_device.custom_handler: bRequest 0x06, wIndex 0x0000
[00:00:00.338,000] <dbg> usb_device.usb_handle_std_device_req: REQ_GET_DESCRIPTOR
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x80, len 4
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x80, len 0
[00:00:00.338,000] <dbg> usb_dc_stm32.HAL_PCD_DataInStageCallback: epnum 0x00
[00:00:00.338,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x80, status 0x02
[00:00:00.338,000] <dbg> usb_dc_stm32.HAL_PCD_DataOutStageCallback: epnum 0x00, rx_count 0
[00:00:00.338,000] <dbg> usb_device.usb_handle_control_transfer: ep 0x00, status 0x01
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_read_wait: ep 0x00, 0 bytes, 0+0, 0x24000220
[00:00:00.338,000] <dbg> usb_dc_stm32.usb_dc_ep_start_read: ep 0x00, len 64
[00:00:02.314,000] <dbg> usb_dc_stm32.usb_dc_ep_write: ep 0x81, len 2
[00:00:02.314,000] <dbg> main.send_report: Wrote 2 bytes with ret 0
[00:00:03.320,000] <dbg> usb_dc_stm32.HAL_PCD_SuspendCallback:
[00:00:03.320,000] <inf> usb_hid: Device suspended
[00:00:03.320,000] <dbg> main.status_cb: status 5 unhandled

I made a mistake in what I wrote before. Enable voltage detector in the end of usb_dc_attach instead of usb_dc_stm32_init. I am not sure if it matters but this is what I did. Can you check also the cdc acm class? This is the class I am using.

@shlomow Moved the voltage detector enable to usb_dc_attach, does look like that's a more appropriate place for it. The hid sample still doesn't stay connected, still gets suspended.
However, the cdc_acm example does stay connected!

Continuing testing with the cdc_acm example, I found that it works and stays connected (doesn't get suspended) if the USB cable is connected on power-up or reset. However, hot-plugging the USB cable leaves the STM32H753 disconnected. Is that expected? Since I'm testing with a NUCLEO-H753, power is not provided by the device USB connection.
I tried setting USB_SELF_POWERED, but that didn't make a difference.

Realized that I hadn't tried to send data through the cdc_acm example. Tried doing that—nothing comes through. So, while it will stay connected, it's not fully functional.

@shlomow Did you have more success than this?

Sorry,. I am on holiday now

Thanks to work from my colleague @IvoBCD, we have a solution to this issue. I've just made a pull request with our changes here: https://github.com/zephyrproject-rtos/zephyr/pull/33686
Thanks @shlomow, your suggestions were very helpful in moving this forward!


Kim fmod test branch

test the debug slider functionality

Would be great if someone could double check this all works and merge with main. :)


Build Bacon with Rollup from ES6 modules

Converts the codebase to ES6 modules which are built with Rollup to produce browser/commonjs builds. Rollup gives us clean output (no requires in browser builds!) but also cleaner separation of scopes in source files.
While the end result isn't at all different, it's now easier to use JS tooling for Bacon source. Eslint detects unused non-prototype imports with no-unused-vars (not enabled, there are violations in code). The code can be loaded in node without separate compilation step – assuming "babel-register" is required.
Running individual test files is much faster and failures report line numbers in source files and not some random numbers in dist/Bacon.js. With some effort, it should be possible to even run the individual test file after file is modified since the mapping form source to test files is quite clean.
The benchmarks also run without requiring separate compilation step.
TODO:

[x] easy interface to assemble partial builds
jsnext package

Looked into providing a jsnext main package. Two solutions came up to my mind: including JS source files in npm package or providing a compiled ES6 bundle file.
Source files would be a clean solution, but might cause some grievance in long term. Babel or ES6 can change, potentially breaking our code. We're not even really using the standard ES6 mode but loose mode for some transformation. Thus, it could also be something unexpected in Bacon code that is only exposed on native ES6 mode.
A separate bundle file with mostly ES5 but ES6 imports would solve these issues. However, that wouldn't be very useful since Bacon only provides one export. Essentially it would save the potentially 20 bytes or so, but also mean that we'd need to add yet another bundle file.

@raimohanska, @phadej, do you have any feedback?

Gotta admit I'm not so deep in the world of packaging javascript modules in so-many-different-ways :( The current build works pretty ok, I guess, and is a result of god-knows-how-many iterations of trial and error.
So I can only comment on this on a "project management level". My priotities are

Don't break it. Fortunately we have a great deal of tests that keep the functional things in check. Personally I rely on tests when making changes. The packaging / module system compatibility part is harder to test automatically though, I guess.
I (pretty much) insist that we still need have a trivial way to import the whole Bacon lib using npm and commonjs, as well as importing the lib from cdnjs using a script tag.
Keep/make baconjs a good citizen in all other relevant ecosystems / ways to build javascript software (there are probably ways I've never heard of)
Don't mess with performance
Don't break compatibility with dinosaur browsers (using shims is of course a possibility too)
Make it possible (one way or other) to get a subset of the library if you're into keeping things
lightweight
Future proof / ES6+ compatibility whatever this means in practise

Damn it was hard to prioritize these thingsies. How do you feel about these?

That's a good list. This viikateisku the first rule a bit by introducing code churn but hipeille compensates with more standard roolina and faster test cycle.
For library consumers, not much should change. The bundle is essentially same. Option for es6 module exists at least of you'd use Bacon from git.

@lautis wat? looks like you're using predictive typing with Finnish vocabulary :)

Yep, that's what happened. Fixed :blush:


Adding support for Windows CPU Telemetry

Took a stab at this.
I can't add reviewers :(  @brandonforster can you take a look? #1075
Signed-off-by: Mike Johanson<EMAIL_ADDRESS>

recheck

@rsdmike LGTM. Needs rebase.

@rsdmike Why are there so many other people besides you showing up on the commit stream? Are you rebasing or cherry picking?

I have no clue, i ran git pull --rebase upstream master ? Cherry-basing maybe?

Look like should be good now after squashing?

recheck


Missing command

There is a missing command to setup a suggestion channel

/autosetup fun setup:Suggestions
try this command and let me know if that works on your end!

Okay perfect
Do you have any suggetions for the bot right now?
Because i am able to start coding on the bot

I will fix the propose command!

Propose Command should be fixxed now!
Please Let me know if you are still getting errors


MSn data?

Do we want to be able to upload only MS2 data. Or should MSn or MS1 also be possible?
I have no experience with working with MSn data and matchms is not able to handle this type of data, so implementing this would be a lot more complicated.
I know you did do a study on MSn data @robinschmid, is this your main use case, or could we start with an implementation for MS2 and maybe later add MSn functionality?

I agree, that this is more than a quick fix somewhere in matchms. But it makes sense to consider adding MSn support to matchms I believe (see issue there --> https://github.com/matchms/matchms/issues/550).

This will be further discussed in issues of matchms.


Issue: can't import

After trying to import and updating all things, I still get this error:

Gradle 'material-sheet-fab' project refresh failed
Error:No service of type Factory available in ProjectScopeServices.

How come?

The library hasn't been actively developed for some time so some of the plugins are outdated. Try updating
material-sheet-fab/build.gradle.
A quick google search gave me this https://code.google.com/p/android/issues/detail?id=219692

Can you please update it?

Are you trying to modify the library (by forking it) or are you importing into your project with compile 'com.gordonwong:material-sheet-fab:1.2.1'? The latter should still work.

Just clone, import, build and run

Okay, you'll need to update the gradle file then. My comments above should have all the info you need.

As I wrote, I tried to update everything. It didn't help.
Please fix the project to work on new IDE version and all..

有り難うございます。


chore: removed fields

Description
Removed deprecated fields in KeptnTaskDefinition type
Fixes #3104
How to test

[ ] Manual Test A
[ ] Unit Test B
[ ] Integration Test C

Checklist

[ ] My PR fulfills the Definition of Done of the corresponding issue and not more (or parts if the issue is separated
into multiple PRs)
[ ] I used descriptive commit messages to help reviewers understand my thought process
[ ] I signed off all my commits according to the Developer Certificate of Origin (DCO)
see Contribution Guide
[ ] My PR title is formatted according to the semantic PR conventions described in
the Contribution Guide
[ ] My code follows the style guidelines of this project (golangci-lint passes, YAMLLint passes)
[ ] I regenerated the auto-generated docs for Helm and the CRD documentation (if applicable)
[ ] I have performed a self-review of my code
[ ] I have made corresponding changes to the documentation (if needed)
[ ] My changes result in all-green PR checks (first-time contributors need to ask a maintainer to approve their test runs)
[ ] New and existing unit and integration tests pass locally with my changes

Closing, reasoning here https://github.com/keptn/lifecycle-toolkit/issues/3104#issuecomment-2017391888


Flyout opened below some controls

What steps will reproduce this issue?
Flyout opened below some controls. He turns from the bottom, but must be on top. This happens if you use WindowsFormsHost or infragistics controls.
Video Bug: https://1drv.ms/v/s!Aq6ZQkyoPcuM9ATS8qNqViwO5zHm
Download my program: https://yadi.sk/d/NTrO4sOepjjQq
Expected outcome
I want to Flyout opened on top of all the program interface
--
Environment

MahApps.Metro v1.3
Windows 7 x64
Visual Studio 2015
.NET Framework 4.0

@alexeygritsenko This is not MahApps related but a known issue by WPF and WindowsFormsHost, so please try the AirspaceDecorator from Microsoft.DwayneNeed to avoid this (https://github.com/MahApps/MahApps.Metro/wiki/FAQ#solution-2)

thanks for the reply.
Solution 1 does not work,
error: Unable to find property "AllowsTransparency" in type "BorderlessWindowBehavior".
after i write line: this.AllowsTransparency = true;
display healed now Flyout from the top looks good, but the buttons located on it do not click. It turns out he is the top only in appearance, but in fact there is less control and interact with it is impossible.
Solution 2, I will check and let you know later. they do not have ready-made library, it needs to be compiled (yet I fail)

thanks for the reply.
Solution 1 does not work,
error: Unable to find property "AllowsTransparency" in type "BorderlessWindowBehavior".
after i write line: this.AllowsTransparency = true;
display healed now Flyout from the top looks good, but the buttons located on it do not click. It turns out he is the top only in appearance, but in fact there is less control and interact with it is impossible.
Solution 2, I will check and let you know later. they do not have ready-made library, it needs to be compiled (yet I fail)

@alexeygritsenko Sorry for this, AllowTransparency is old solutiin, I should dekete it. For the second, I can compile it for you...

I was able to compile the library and follow your example (Solution 2). However, I get an error in my project:

Error		The tag 'AirspaceDecorator' does not exist in XML namespace 'clr-namespace:Microsoft.DwayneNeed.Interop;assembly=Microsoft.DwayneNeed'. Line 270 Position 30.

@alexeygritsenko
Microsoft.DwayneNeed.zip

unfortunately your library the same error (
checking them in?

I realized what was happening. Your assembly (Microsoft.DwayneNeed.zip) for Net 4.5, but my project 4.0. I rebuilt under 4.0 and now it works! The program really shows Flyout top and controls on it are clickable. But the downside is that the visual studio fell off a visual interface editor. He is now constantly crash, I can only view the xaml code(

@alexeygritsenko Sorry about the VS designer crashes. I'll close this issue cause this is not MahApps related.


After BUILD & SERVER - Uncaught SyntaxError: Unexpected token

Hi,
On the dev mode, I can run my code and everything work.
After I run the build and server I get the "Uncaught SyntaxError: Unexpected token".
Can you help me with this issue?
Thanks
(congrats on the project.)

I solve the issue by adding this var to the .env file.

PUBLIC_PATH="/"
INLINE_RUNTIME_CHUNK=false


Dispatcher lock reduction (dev)

Codecov Report

Merging #220 (6f38acb) into dev (5485d4e) will decrease coverage by 0.32%.
The diff coverage is 77.34%.

@@            Coverage Diff             @@
##              dev     #220      +/-   ##
==========================================
- Coverage   43.93%   43.61%   -0.33%
==========================================
  Files          32       33       +1
  Lines        4582     4563      -19
==========================================
- Hits         2013     1990      -23
- Misses       2569     2573       +4

Impacted Files
Coverage Δ

assemblyline_core/submission_client.py
56.94% <51.61%> (-11.24%)
:arrow_down:

assemblyline_core/dispatching/dispatcher.py
76.62% <78.07%> (-1.33%)
:arrow_down:

assemblyline_core/dispatching/timeout.py
97.22% <97.22%> (ø)

assemblyline_core/scaler/scaler_server.py
30.45% <0.00%> (-0.71%)
:arrow_down:

assemblyline_core/updater/run_updater.py
27.48% <0.00%> (-0.19%)
:arrow_down:

assemblyline_core/server_base.py
76.77% <0.00%> (-0.15%)
:arrow_down:

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 5485d4e...6f38acb. Read the comment docs.


For Review Exercise

The Files are for the review exercise

Every thing is awesome. Keep the awesome work.  Keep it that way.


Update RELEASING.md

Thank you for contributing to Apache StormCrawler.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a issue associated with this PR? Is it referenced in the commit message?

[ ] Does your PR title start with #XXXX where XXXX is the issue number you are trying to resolve?

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

[ ] Is the code properly formatted with mvn git-code-format:format-code -Dgcf.globPattern="**/*" -Dskip.format.code=false?

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn clean verify?
[ ] Have you written or updated unit tests to verify your changes?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions for build issues and submit an update to your PR as soon as possible.
This fixes #1412 .

I'll leave this as a draft until we complete the release cycle for 3.2.0