Reimagine Development Settings in Composer

Describe the solution you'd like

Describe alternatives you've considered

Additional context

The following tickets are all part of this:
#7793
#6162
#6446


[Bug] run start_cli_testnet.sh failed on CentOS 7

🐛 Bug

To reproduce
** Code snippet to reproduce **
./scripts/cli/start_cli_testnet.sh
** Stack trace/error message **
-- Build files have been written to: /root/packages/libra/target/debug/build/grpcio-sys-c998cb3e25589d95/out/build

--- stderr
CMake Warning at cmake/protobuf.cmake:48 (message):
  gRPC_PROTOBUF_PROVIDER is "module" but PROTOBUF_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:140 (include)

CMake Warning at cmake/gflags.cmake:26 (message):
  gRPC_GFLAGS_PROVIDER is "module" but GFLAGS_ROOT_DIR is wrong
Call Stack (most recent call first):
  CMakeLists.txt:142 (include)

CMake Error at CMakeLists.txt:738 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:6171 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:871 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:1329 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:1329 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:7803 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:1715 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:1715 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:8012 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:2694 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:2694 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

CMake Error at CMakeLists.txt:8114 (target_compile_options):
  Error evaluating generator expression:

    $<COMPILE_LANGUAGE:CXX>

  Expression did not evaluate to a known generator expression

thread 'main' panicked at '
command did not execute successfully, got: exit code: 1

build script failed, must exit now', /root/.cargo/registry/src/github.com-1ecc6299db9ec823/cmake-0.1.40/src/lib.rs:832:5
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.

warning: build failed, waiting for other jobs to finish...
error: build failed

Expected Behavior

cli started
System information
Please complete the following information:

git cloned

automatically installed by installer

$uname -a
Linux localhost.localdomain 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
$cat /etc/redhat-release
CentOS Linux release 7.6.1810 (Core)
Additional context
Add any other context about the problem here.

Your distribution may have an older CMake package. The COMPILE_LANGUAGE:CXX expression requires version >= 3.3
I ran into this on Amazon Linux 2, and was able to solve it by uninstalling the cmake package, installing cmake3, and creating a symlink /usr/bin/cmake pointing to /usr/bin/cmake3
More details: https://blog.cotten.io/deploying-the-libra-core-blockchain-currency-on-amazon-ec2-f832d4bfadc8

thanks. @tim-cotten
I also find a closed issue about this #76.


Fixed scalar-matrix multiplication in iv module

Seems ok.

Reverted because of failing tests. I don't get why -- this PR was green before the merge.

I will have to look at that when I have more time
On Sun, Feb 3, 2019 at 4:05 AM Fredrik Johansson<EMAIL_ADDRESS>wrote:

Reverted because of failing tests. I don't get why -- this PR was green
before the merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/fredrik-johansson/mpmath/pull/425#issuecomment-460042177,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Adz8FFBr5bOqqwJl7r-LrWLgc42UmQWTks5vJsJkgaJpZM4Z337H
.


Updating release nr

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/relnotes/index.md
76
41
16
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 363e135:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/relnotes/index.md
:white_check_mark:Succeeded
View

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


Raise an exception on geometries of GeometryCollection type

Would be good if it could raise an exception to tell users that it doesn't support encoding GeometryCollection.
Otherwise protobuf will complain like this
collection = shapely.wkt.loads('GEOMETRYCOLLECTION (GEOMETRYCOLLECTION (POINT (4095 3664), LINESTRING (2889 0, 2889 0)), POINT (4095 3664), LINESTRING (2889 0, 2912
158, 3757 1700, 3732 1999, 4095 3277))')
mvt.encode({'name': 'streets', 'features': [{'geometry': collection}]})

# TypeError: None has type <type 'NoneType'>, but expected one of: (<type 'int'>, <type 'long'>)

which doesn't make sense

Thanks for the report! This should be fixed on master now.


Update package version

you forget to update the version

Yooo I have an idea can you make same like for quotes it will be awesome.
On Wed, Nov 4, 2020, 8:11 PM Saurabh Shubham<EMAIL_ADDRESS>wrote:

Merged #12 https://github.com/Saurabh3333/give-me-a-joke/pull/12 into
master.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Saurabh3333/give-me-a-joke/pull/12#event-3958058951,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMXTCNCVXXYPYRLX4VBPZZDSOFVKLANCNFSM4TKFHN5A
.

Yeah. It's a nice idea. Do you know some source which we may use for fetching quotes? If you get time, please do research regarding it.

Sure dude


Font size

Ensure that the fonts of the site are appropriate and match their heading style

Adjusted font of site for each specific heading style


Phaser.Time.Timeline Errors on calling destroy

Version

Phaser Version: 3.80.1-3.85.0-beta.1
Operating system: W10

Description
An issue happens on both versions when trying to destroy a timeline like this, even while it is playing. The error is different for each phaser version though.
Example Test Code
                const follower = this.scene.add.follower(curve, 0, 0, "img", "id/ranks/star");
                follower.setVisible(false)
                follower.startFollow({
                    from: pathProgress - 0.5 < 0 ? 0 : pathProgress - 0.5,
                    to: pathProgress,
                    duration: singleDuration,
                    delay: fullDuration-i*singleDuration*mp
                });
                const bloom = follower.postFX.addGlow(0xffffff,3,2)
                const timeline = this.scene.add.timeline([
                    {
                        at: fullDuration-i*singleDuration*mp,
                        run: () => follower.setVisible(true)
                    },
                    {
                        at: fullDuration-i*singleDuration*mp,
                        tween: {
                            targets: follower,
                            angle: this.getStarAngle(starCount, i)-(360*2),
                            duration: singleDuration,
                        }
                    },
                    {
                        at: fullDuration-i*singleDuration*mp+600,
                        tween: {
                            targets: bloom,
                            innerStrength: 0,
                            outerStrength: 0,
                            duration: 500,
                        }
                    }
                ]).on("complete", () => {
                    if(this?.visible){
                        follower?.destroy();
                        this?.addDivisionStarInFinalPosition(curve, pathProgress, starCount, i);
                    }
                }).play()
if(timeline?.isPlaying())  timeline.destroy();

on 3.85.0-beta.1 the error is as follows:
Uncaught ReferenceError: i is not defined
at Timeline2.clear (phaser.js:233673:14)
at Timeline2.destroy (phaser.js:233752:14)

on 3.80.1 the error is as follows:
TypeError: Cannot read properties of null (reading 'events')
at Timeline2.destroy (phaser.js:233464:41)

https://phaser.io/sandbox/DPz6DKZC
here is a minimal case

Hi @saintflow47. It seems there's a missing var in the for loop in the Phaser.Time.Timeline#clear method. We have fixed this and pushed it to the master branch. It will be part of the next release. Do test it out and let us know if you encounter any issues.


The image for the Find-Command box is older than I am

The image for the VS2022 Find-Command box in the documentation is older than I am.
https://learn.microsoft.com/en-us/visualstudio/ide/find-command-box?view=vs-2022
I've included the image here for posterity.

For what it's worth, I was able to find the VS2022 version of this which is in a new location different from where the documentation states; it also looks slightly different, but you can still run finds and commands from it funnily enough.
It is still in the Standard toolbar's Commands, but it is under the Edit category and it has been renamed to Go to Find Combo from Find. The documentation says it is named Find, but that is a different button.

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

ID: d0b30872-8d41-43f9-8ad1-030324efc322
Version Independent ID: 294bf85a-1e76-cb93-bed9-d97fd081e1f7
Content: Find-Command Box - Visual Studio (Windows)
Content Source: docs/ide/find-command-box.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @ghogen
Microsoft Alias: ghogen

@collinstevens
Yes, it looks like the image is pretty old. I'll see about getting this article updated soon.

I have updates ready for this article. Thanks for the detailed instructions on how to find the new version of this toolbar item, it helped me quickly find it and update the article.


”Moțca” is listed in the drop-down menu

Description:
"Moțca" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Moțca" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Moțca, IAȘI".


rename to stolostron

Ref: https://github.com/stolostron/backlog/issues/18746
Signed-off-by: haoqing0110<EMAIL_ADDRESS>

/retest

/assign @elgnay @zhujian7

/lgtm

LGTM


Errors with .Net 8

I installed donet sdk 8.0.201 and to check if it was installed well I typed "dotnet" in the cmd but when I do the same in the visual studio code finish it does not recognize it. My processor architecture is x64 and I installed the extensions you show in the tutorial. how do I fix it?

Can you show the output of dotnet --info from cmd?
Have you previously installed other versions? Maybe there's an issue with PATH.
Check what where.exe dotnet returns as well.

Thanks for your time. I don't know how, but the problem I had was fixed
just by closing and reopening the visual studio code
El mar, 20 feb 2024, 16:36, Maira Wenzel @.***>
escribió:

Can you show the output of dotnet --info from cmd?
Have you previously installed other versions? Maybe there's an issue with
PATH.
Check what where.exe dotnet returns as well.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/website-feedback/issues/42#issuecomment-1955234792,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BGHULPKPB5OWIBJNNROAYH3YUUQOZAVCNFSM6AAAAABDN6DC46VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJVGIZTINZZGI
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for letting us know. Yeah, sometimes it just needs a restart for the changes to be picked up by the tool.


Add home button in login signup page

There is no way to navigate to home page after visiting login signup page.Hence I want to add home icon to it. Please assign this issue to me under JWOC.

Page will look like this after changes and home button will redirect to homepage

Page will look like this after changes and home button will redirect to homepage

@S-ishita go on


Issue front end infra - bug fix

Bug fix resulting from Issue/front-end-deploy (#5) changes
Summary
Set the terraform to deploy on main when previous steps have been skipped (but not failed)

Fixes # (#5)
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How To Test
Validate code deploys on pushes to main
Checklist:

[x] My code follows the style guidelines of this project and has no linting errors
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation, including any applicable ADRs
[x] My changes generate no new warnings
- [ ] I have added tests that fail without these changes
- [ ] New and existing tests (unit, integration, accessibility) pass locally
- [ ] Documentation updated
- [ ] If there are security concerns they are addressed or ticketed after being discussed

Application deployment was skipped because Terraform deployment was skipped. Terraform was skipped because no changes in Terraform were present. These changes should set terraform deploy to always run on main branch, even if no changes occur.


Windows image with ContainerD for public clouds

In public clouds like AWS and Azure, there are Windows Server images with container support that come with Docker installed and configured. As a consumer of such images, I would like to see similar images published to AWS, Azure etc, with ContainerD installed and configured to reduce the burden on the end user.

@aravindhp Can you can explain how you plan to use containerd with Windows Server container images on Azure and AWS? What kind of burden? Any example? What Azure services are you using?  I am curious.

I am curious: 1) Why can't OpenShift infra or the Cloud infra bring in containerd bits vs. the customers? 2) How are you using containerd on Windows today on OpenShift? Is the E2E scenario working?

Why can't OpenShift infra or the Cloud infra bring in containerd bits vs. the customers?

Will MSFT provide it as a supported server add-on? If yes, then we can explore that option.

How are you using containerd on Windows today on OpenShift?

We have not moved to ContainerD yet. We are still using Docker which is pre-installed on Windows images in AWS and Azure. What we are asking for is the same treatment when it comes to ContainerD.

/cc @Anandnatraj

We don't have the plan now. It made sense to have Docker pre-installed on the Windows Server images on Azure because it was the only container run-time when Windows Server started supporting containers a few years back. The ecosystem has evolved a lot. There are a lot more diversified options. We are not seeing the same value or need to pre-install containerd on Windows Server at this time. That can change, and we'll revise our plan as needed.
Thanks for the feedback. If no more questions, I'll close this.

/cc @brasmith-ms


Create a list of required art assets (e.g., textures, models).

First Location
Castle
Inn
Church
grey brick roades
grey brick square tower
grey bricks round tower
Big grey bricks round tower
Big grey brick square tower
grey bricks round tower with roof
grey brick square tower with roof
Big grey brick square tower with roof
Big grey brick round tower with roof


nim: 2.0.8 -> 2.2.0; nim: init updatescript;

changeLog v2.0.8...v2.2.0
Adds an update script to nim.
Fixes: #346530
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

It fails on aarch-64darwin for some reason.

@ofborg eval

patching file compiler/msgs.nim
Hunk #1 FAILED at 659.
1 out of 1 hunk FAILED -- saving rejects to file compiler/msgs.nim.rej
error: builder for '/nix/store/lj7avzq64ivkzwyl6q68wwriw8l1gy9r-nim-unwrapped-2.2.0.drv' failed with exit code 1;
       last 10 log lines:
       > patching file lib/pure/dynlib.nim
       > Hunk #1 succeeded at 45 with fuzz 2 (offset -11 lines).
       > Hunk #2 succeeded at 87 with fuzz 1 (offset -11 lines).
       > applying patch /nix/store/vw1jfdamdy5gd2qm0kk41afjykj653h7-extra-mangling.patch
       > patching file compiler/modulepaths.nim
       > Hunk #1 succeeded at 79 (offset 9 lines).
       > Hunk #2 succeeded at 94 (offset 9 lines).
       > patching file compiler/msgs.nim
       > Hunk #1 FAILED at 659.
       > 1 out of 1 hunk FAILED -- saving rejects to file compiler/msgs.nim.rej
       For full logs, run 'nix-store -l /nix/store/lj7avzq64ivkzwyl6q68wwriw8l1gy9r-nim-unwrapped-2.2.0.drv'.
error: 1 dependencies of derivation '/nix/store/fzmdg1fg8sz33dhjzb7m1padxsjvlbfb-aarch64-apple-darwin-nim-wrapper-2.2.0.drv' failed to build

I'll fix the path mangling patch and push it when I get a chance.
After that, squash the version and hash commits together and put the version update in the commit message.
https://github.com/NixOS/nixpkgs/blob/master/pkgs/README.md#commit-conventions

I pushed a new mangling patch.

Works.

Logs:
error: 2 dependencies of derivation '/nix/store/207ndaa7jd4x2il8hiil2qbd6nbga8df-review-shell.drv' failed to build
┏━ 1 Errors:
┃ error: builder for '/nix/store/ls0mbvx6hdmzmzidp36z86f7ahkxrhvq-nim-unwrapped-1.6.20.drv' failed with exit code 1;
┃        last 10 log lines:
┃        > patching file lib/pure/dynlib.nim
┃        > Hunk #1 succeeded at 45 with fuzz 2 (offset -11 lines).
┃        > Hunk #2 succeeded at 87 with fuzz 1 (offset -11 lines).
┃        > applying patch /nix/store/lhkmiqgxabd2z00kbkh3nfgcf7fwd283-extra-mangling.patch
┃        > patching file compiler/modulepaths.nim
┃        > Hunk #1 succeeded at 73 (offset -6 lines).
┃        > Hunk #2 succeeded at 88 (offset -6 lines).
┃        > patching file compiler/modulegraphs.nim
┃        > Hunk #1 FAILED at 503.
┃        > 1 out of 1 hunk FAILED -- saving rejects to file compiler/modulegraphs.nim.rej
┃        For full logs, run 'nix-store -l /nix/store/ls0mbvx6hdmzmzidp36z86f7ahkxrhvq-nim-unwrapped-1.6.20.drv'.

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

2 packages marked as broken and skipped:

chawan
nrpl

2 packages failed to build:

nim1
vimPlugins.fruzzy

4 packages built:

nim (nim2)
nim_lk
promexplorer
tridactyl-native

Might need to keep distinct versions of the extra-mangling.patch for nim 1.x and 2.2.x respectively.

I just made it seprate.

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

2 packages marked as broken and skipped:

chawan
nrpl

4 packages built:

nim (nim2)
nim_lk
promexplorer
tridactyl-native

I can confirm nim1 is working and vimPlugins.fruzzy in my local enviroment.


Vimeo fails, freezes entire application

Every so often Vimeo will fail to render/fetch a video, resulting in the following error:

You must pass either a valid element or a valid id.

This error causes the rest of our application to break, as react routing no longer works and other functionality freezes.
We've boiled it down to the id differing between the iframe and the vimeo player.js internally. The hash which it creates to fetch the blob does not match with the video id provided.
This error is incredibly sporadic, and we've only been able to replicate a handful of times, but never with a resolution. I'm opening an issue with vimeo player.js shortly but I thought to ask here first to see if anyone else has experience with this error and how to solve it.

Hey @Redmega, are you using ReactPlayer inside a frame? Looks like a similar problem to https://github.com/CookPete/react-player/issues/150#issuecomment-297780947 and https://github.com/vimeo/player.js/issues/16.

@CookPete Nope, we're rendering the <ReactPlayer> directly in the app. I believe Vimeo's player.js is creating an <iframe> for its own player, but it works most of the time, so I don't think it's an iframe related thing.
It also works most of the time for the same id which will fail sometimes. It's not an issue with a specific video, either.
Like I said, very hard to replicate. Once I get it to happen again I'll post details of the video and the DOM.

The error being logged is here in the Vimeo player source, which implies that the first argument passed to new Vimeo.Player() is not a dom element (or an ID of an element). The only place that happens in ReactPlayer is here:
https://github.com/CookPete/react-player/blob/d5ba064a42f3b0abfa4c0d78324305ef20120f54/src/players/Vimeo.js#L40
So this.container is not an element. Could it be that the component is unmounted before the SDK finishes loading, and ref is being called with null which sets this.container = null?
Maybe it's as simple as just bailing before new Vimeo.Player() runs if the component has unmounted.

I am seeing on server-side render we get the following error
ReactPlayer: Vimeo player could not call unload – The player was not ready
However the video still plays properly in most cases. I haven't been able to replicate the id issue as of yet.
Could be that during SSR it's failing to mount, or something like that?

My coworker was able to replicate, strangest thing is that the video itself is still playable and works fine. It's just the rest of our app that breaks.

I am seeing on server-side render we get the following error
ReactPlayer: Vimeo player could not call unload – The player was not ready

This is just a warning that can happen when the component unmounts (and calls stop()) before the player is ready. The same thing that can cause the You must pass either a valid element or a valid id error. Pretty sure the two errors are based on the same problem.

FYI, I've just published v1.0.0-beta.0 under the tag next (it was time). It might be worth upgrading and seeing if that makes any difference:
npm install react-player@next

It's a pretty big refactor so would be great to test it in the wild before release.

I think 979e639 should fix this. Part of 1.0.0-beta.1

Ok thanks we'll give it a try.
On Sat, Oct 28, 2017, 3:13 PM Pete Cook<EMAIL_ADDRESS>wrote:

I think 979e639
https://github.com/CookPete/react-player/commit/979e639b8f8faca50509c692d1688e7eb39fef50
should fix this. Part of 1.0.0-beta.1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CookPete/react-player/issues/259#issuecomment-340213411,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAodp8Uqsfufb8uPIhf0g_0nA-A02mn7ks5sw3zvgaJpZM4QFI4B
.

@CookPete Just wanted to give you an update, it seems after releasing 1.0.0-beta.3 to the wild earlier today, we've seen a drastic reduction in those errors. Safe to say near-zero now...

Thanks!


Add support for bridge interfaces

Issue type
[x] Feature request
[ ] Bug report
[ ] Documentation
Description
On a router I have some bridges with multiple interfaces.
With Netbox it's possible to assign an IP address to the (virtual) bridge interface, but it is not possible to reflect which interface is in which bridge. There should be a possibility similar to the bonding devices.

NetBox doesn't support modeling bridges. This is one of those things that crosses into general configuration management and we have to avoid falling down that rabbit hole.

So how do you recommend to document the IPs on bridges? (virtual interfaces?) And how to reflect interfaces in a bridge?
There is a possibility for LAG interfaces, something similar for bridges would be perfect (like master / child interfaces).

You can create a virtual interface named e.g. BVI1 to represent a bridge group and assign IP addresses to it. NetBox does not model bridge groups, but maybe #150 will help once it's been implemented.

That's possible for LAGs - why not for bridges?
I need to reflect which interface is in which bridge, similar to LAGs & LAG members.

Conceptually, a bridge group is the same as a VLAN. Let's see how #150 plays out and you can ask to reopen this issue if it still does not meet your needs.

#150 is implemented and works great. I'd love to see bridge modeling added. It would work almost identically to LAG modeling, so I expect most of the code would be recycled from that. There are network devices, like Mikrotik routers and switches, that heavily incorporate bridges into the VLAN and port configuration (ports are added to a bridge, VLANs are added to bridge and bridge ports, not the physical interfaces), so I don't see this as any less relevant to include than LAG and VLAN in Netbox. Right now, I'm trying to model a bridge, which contains LAGs and other ports which also manages VLANs for the bridge ports and CPU. I can almost fudge this with LAGs, but LAGs can't have parent LAGs. If I use a virtual interface, I can't track which bridge ports are part of. I would also like to show bridge configuration on hypervisors. Can we please re-open this?


Monitor Query - Move to the new proxy server based recorder

See https://github.com/azure/azure-sdk-for-js/issues/17994 for details

Looks like this one got handled alredy


Changed language to either/or

This changes language from 'production and learning environments' to 'either production or learning environments'. It is a little more concise.

/assign @makoscafee

/lifecycle stale

/close


fix: ensure skipped checks are treated properly

In some circumstances, the Appinspect API skips checks. Currently, those checks are not processed correctly. This ensures that the script does fail once a skipped check is encountered.

closing due to remaking this tool with python


Add superscript and subscript

Will be covered in v2 work: https://github.com/jaredreich/pell/projects/1#card-8535962


How to set  own's COCOAPI

Hello author, thank you for your work. Regarding the experimental results on COCO_lt, I would like to know how to change the evaluation API to get experimental results such as AP1, AP2, AP3, and AP4. My code base is based on mmdet=2.3.0. Look forward to your reply!

Hi, you can check the two files (coco.py and cocoeval.py) for reference, or try replacing them in the cocoapi
coco.zip

Thanks for the author's reply. Is the setting of the coco code you provided the same as the setting of the paper result? Can I directly replace it or need to modify it?

Yes, it is the paper's setting, it should be ok to directly replace it.

I have installed pycocotools, and then try to replace coco.py and cocoeval.py in the pycocotools folder in the environment. But the following error is reported: AttributeError:'COCO' object has no attribute'get_cat_ids'. I don't know if there is a problem with my operation.

the pycocotools you are using may not be compatible with the py file ( the function is named getCatIds in the provided file), please try pycocotools with lower version

For the last question, I found the following code in the coco.py file you provided:
import pickle
pickle.dump(y, open('./y.pkl', 'wb'))
## calculate sample num for each class
y_sample = y.copy()
for i, num in enumerate(y):
if i<20:
y_sample[i] = y[i]
elif i>=20 and i<40:
y_sample[i] = random.randint(800, 8000)
while y_sample[i]>y[i]:
y_sample[i] = random.randint(800, 8000)
# print(y_sample[i])
elif i>=40 and i<60:
y_sample[i] = random.randint(80, 800)
# print(y_sample[i])
elif i>=60 and i<80:
y_sample[i] = random.randint(8, 80)
# print(y_sample[i])
Must this y.pkl file be included?

The problem has been solved, thank you!


Cannot Use a Macro from Macro Manager

Finally able to make a list that appears in the Macro Window. For example, I made Macro Manage 2 only have Mass Roll macro listed see images 1 and 2. But when I try to use it I get the following error shown in image 3. Am I doing something wrong?

I'll fix

fixed


fix: The releaser by GitHub Actions is terminated abnormally.

There was an error due to a configuration mistake, so fix it.

Codecov Report

Merging #7 (1a687c3) into main (1bb2149) will not change coverage.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@           Coverage Diff           @@
##             main       #7   +/-   ##
=======================================
  Coverage   59.87%   59.87%
=======================================
  Files           5        5
  Lines         329      329
=======================================
  Hits          197      197
  Misses         98       98
  Partials       34       34

Flag
Coverage Δ

unittests
59.87% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[feat] Add sanity function equivalents of 'os.path'

Fixes #1634

Codecov Report

Merging #1695 (fa9a403) into master (d56e435) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1695      +/-   ##
==========================================
+ Coverage   87.21%   87.23%   +0.02%
==========================================
  Files          45       45
  Lines        7546     7559      +13
==========================================
+ Hits         6581     6594      +13
  Misses        965      965

Impacted Files
Coverage Δ

reframe/utility/sanity.py
97.55% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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

Codecov Report

Merging #1695 (fa9a403) into master (d56e435) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1695      +/-   ##
==========================================
+ Coverage   87.21%   87.23%   +0.02%
==========================================
  Files          45       45
  Lines        7546     7559      +13
==========================================
+ Hits         6581     6594      +13
  Misses        965      965

Impacted Files
Coverage Δ

reframe/utility/sanity.py
97.55% <100.00%> (+0.10%)
:arrow_up:

Continue to review full report at Codecov.

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

@jenkins-cscs retry dom

@jenkins-cscs retry dom


[improvement] Add an option to preferences to update save location

Currently, users can only change where the data saves by editing config.user.json (which also needs to be documented). There should be an option in the preferences to allow users to handle this graphically.
As usual, I will get to this soon but if someone else wants it first, please go ahead. File dialogs are handled by the electron.remote.dialog module, and one for saving files is used in submit.js, if you want a reference.

Resolved as of  33eaf1a.


Simplify "basic" example - add example with just simple generated geometry.

Related to #453
Such as:
https://jsfiddle.net/c2asgdqu/3/

Added


The lib hangs if processing concurrently

When spawning multiple transcriptions at the same time, the lib hangs and keeps using CPU forever.
It seems something is not thread safe but I'm not sure. What could be causing that?

Probably you reused some WhisperProcessor across multiple threads.
You should be able to run parallel transcoding without any locking and loading the model only once, if creating one WhisperFactory that you're going to reuse, but for each thread / task, use a different WhisperProcessor

That's exactly what I'm doing. The factory is static and each audio input creates a new processor.

Please, check latest version (1.7.0) and the example https://github.com/sandrohanea/whisper.net/tree/main/examples/ParallelExecution
This is the result (where the output is interleaved and the lib is not hanging):


Add a well-known format description for ISO 8601 basic format

In a recent project, I needed to parse date times in the ISO 8601 format (YYYYMMDDTHHMMSSZ). I managed to implement this using a format description, but this was quite hacky and will only work for UTC dates using the Z time zone specifier.
Do you think this would be a worthwhile addition? I can provide a PR if you're willing to consider it.

Unfortunately ISO 8601 costs hundreds of dollars. If there's some way to verify the exact format without having the full specification, that would be great.
While I know that the format you've provided is generally correct, that isn't sufficient. There are certainly nuances that need to be handled when parsing, which is impossible to do without the specification itself. That said, if there's some company that wants to purchase a copy of the specification (ISO 8601-1:2019 and ISO 8601-2:2019), I'd be happy to move further towards spec compliance.

Ask ISO to donate you a copy of the ISO 8601 documents. Seriously. I'm pretty sure they'll say yes: it's in their interests to have the Rust time crate implement this stuff.
I hate to be part of their pay-to-use standards process, but it's probably the right way forward here.

I'd never considered that, to be honest. I'll reach out :+1:

Given the lack of a response, I presume they're not interested.

Frustrating. Now ask the Rust Foundation to buy these and share them with you, I think.

Marking as blocked until I am able to get a copy of the standard.

Would it be adequate to implement the profile of ISO8601 described in RFC 3339?

@nmathewson RFC3339 is already implemented. This issue is a request for the full spec of ISO 8601.

The Wikipedia article contains all info required for the ticket.
This is the relevant part of the 2004 version of the spec:

The following are examples of complete representations of date and time of day representations:

Type     | Format                    | Example
+++++++++|+++++++++++++++++++++++++++|++++++++++++++++++++++++++
Basic    | YYYYMMDDThhmmss           | 19850412T101530
Basic    | YYYYMMDDThhmmssZ          | 19850412T101530Z
Basic    | YYYYMMDDThhmmss±hhmm      | 19850412T101530+0400
Basic    | YYYYMMDDThhmmss±hh        | 19850412T101530+04
Extended | YYYY-MM-DDThh:mm:ss       | 1985-04-12T10:15:30
Extended | YYYY-MM-DDThh:mm:ssZ      | 1985-04-12T10:15:30Z
Extended | YYYY-MM-DDThh:mm:ss±hh:mm | 1985-04-12T10:15:30+04:00
Extended | YYYY-MM-DDThh:mm:ss±hh    | 1985-04-12T10:15:30+04

The Z at the end of the datetimes is the UTC designator.
Also see Times section on WP regarding fraction of seconds since both . and , are allowed as separators.
RFC 3339 and ISO 8601 are mostly identical The main difference is that ISO 8601 would like to have Z in case of UTC while +00:00 would also be ok.
What this issue requested was support for the Basic formats in the table above which are only defined in ISO 8601 but not in RFC 3339 because that demands the extended format.
Hope this helps.

What I'm looking for is the 2019 version, not the 2004 version. I have no idea if there are differences as information is hard to come by. I'm not going to rely on Wikipedia regardless; there are frequently nuances that need to be handled that are undoubtedly not shown in a high-level article. That's why I need the actual specification.

There's this interesting discussion about the topic on Twitter, including this nugget.
The thing is that even if we would fund you a copy of ISO 8601-1:2019, you couldn't really use it for anything in an open source project since ISO would like to charge per reader and has a very restrictive license. The situation would just change from me telling you "Yeah, it looks like this. Trust me." to you telling other maintainers "Yeah, it looks like this. Trust me.".
You couldn't reference the standard in a meaningful way since no one would be able to check those references. The situation is indeed kafkaesque.
It all boils down to ISO 8601 implementations always being hearsay and best-effort - as enforced by ISO legalese itself.
For "ISO 8601 datetime (basic)" this hearsay is "RFC 3339 format, but without - and :" and "Z is equivalent to +00:00".
I do have a legal copy of the previous version because a former employer bought a copy for me. Since those copies are per reader, I assume that it's my own personal copy and not the copy of my former employer. I assure you that the information I provided above is all the information provided in the text. The specification contains more formats but this is the part concerned with datetime.
The spec also contains this copyright notice:

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISO's member body in the country of the requester.

IANAL, but this seems to make it illegal to even use the examples provided in the spec in publicly available test code. This also applies to the examples I provided above.
Yes. This is all very, very absurd.
I'm not trying to push you into any direction here. I only wanted to give you the full picture.

My knowledge of copyright is that while the text of the spec can be copyrighted, the format itself cannot be, and thus I would be able to have things like tests public. I'd just have to create my own examples...which is not a big deal. I do understand everything is ultimately hearsay as you've mentioned.
I think what I'm going to do is reach out to both the Free Software Foundation and the Rust Foundation to see if either or both is able to provide legal guidance on this front.

Yeah, creating own examples for tests would be trivial but the opposite of what one would normally do while implementing a spec. One would usually use exactly the examples from the spec because they may contain all kinds of edge-cases.
Most of the spec is just that: patterns with examples. And those patterns are copyrighted, too. 😂
The situation is just extraordinarily absurd. And it has been exactly like that for 20 years.
Every company I ever worked for has suffered in some way because of this.
The problem isn't the price of the spec. The problem is that you can't just send someone a link and say "This is what it should look like. And the authority for this demand is ISO 8601.". It causes unnecessary friction which equals cost. Sometimes lots of it.

That's where I'm hoping some foundation can have an attorney clarify for me what is and is not permissible. If it does turn out that it's largely not possible to do this, then this issue will unfortunately have to be closed for legal reasons. I'll be reaching out either later today or tomorrow most likely.

For transparency I reached out to the Rust Foundation, the Free Software Foundation, and the Electronic Frontier Foundation mid-afternoon (US ET) on January 3. I have not yet received a response. If there is no response by the end of next week (that is, by the end of the day January 14), I will close this issue. with no guidance whatsoever, even from the very foundation that should theoretically help library maintainers in Rust, there won't be anything I can reasonably do.

Seems reasonable. Thanks for looking into it so thoroughly.
One other possible way to proceed would be to implement @huxi's "For 'ISO 8601 datetime (basic)' this hearsay is 'RFC 3339 format, but without - and :' and 'Z is equivalent to +00:00'" as "ISO8601ish format (not known to be True ISO8601™)." I wouldn't be surprised if everyone would be perfectly happy with that…

Closing as no response has been received from any of the three foundations I contacted.

Over the holiday weekend I received the following response (in part) from the Rust Foundation:

Our understanding is that the license text that you have quoted applies to the specification document only, not the standard itself, and that it does not restrict implementation of the standard.
Therefore, you should be able to conduct the activities you suggest.

The Free Software Foundation also responded, but deemed my question to be too close to legal advice, and as such did not provide guidance.
With the response from the Rust Foundation, I'm satisfied that proceeding would not violate the license so long as everything written is my own (including creating my own tests). So at this point it's waiting on a company to provide me with a copy of the specification itself.

@jhpratt is this the right link?  and do you need part 1 and part 2?
We at Slight can definitely support half this (or e.g. one of the parts). We'd love to go half with another company. Let me see if I can find another (@jeffwilcox maybe). To be clear, we can do part 1 unconditionally (or part 2 if you prefer) even if we can't find a partner.

Hey @ColmanHumphrey! Thanks for the offer. Yes, that's the correct link. After quickly reading, part 1 appears to be what I need to satisfy this request. Part 2 could be useful for some other things, but I'm not certain where that would fit in with my vision for this crate.
I know you've got my email as you sent one just a few days ago. No rush or anything — I have some other things I'm working on in the compiler at the moment. Thanks again for offering to cover this.

Sounds good @jhpratt! I've just emailed the ISO org to find out how to buy it in your name, so it'll probably take a bit to sort that out anyway.

Thanks to @ColmanHumphrey & @SlightCode, I am now in possession of ISO 8601-1:2019. It's likely that I will look over the document and begin implementation in the coming weeks.

Finally have a bit of time to dig through the formats in the specification. There is quite a bit of flexibility.
There is the possibility of configuration for some things. Some of these:

whether a format is "basic" or "extended"
the exact components present (date, time, and offset) — can be done in any combination except date-offset
whether the date is the calendar date, week date, or ordinal date

Since it appears as though a number of people are following this issue, I'll ask here. Do users need the ability to configure this at runtime? It should only affect formatting, as the parser should be able to cope with most if not all of the flexibility permitted (I'll know for sure when I start implementation).
If the ability to configure this at runtime isn't needed, I can use const generics to reduce the size of the struct. This'll likely need a bit of creativity to work around current const generics restrictions, but it's doable without too much quirkiness.

Do users need the ability to configure this at runtime? It should only affect formatting, as the parser should be able to cope with most if not all of the flexibility permitted (I'll know for sure when I start implementation).

Hello, I'm one of developers in quite big corporation. In our use case being able to parse ISO 8601 is high on nice to have list.
Formatting on the other hand is more like whatever as long as its compilant with the standard.

Like I said, parsing should be able to handle any valid ISO 8601 regardless of configuration, as the format appears to be designed specifically to avoid any ambiguities. Formatting I intend on providing options to the end user. I'm just not certain whether there's a use case for dynamically setting the configuration values (and if it's significant enough to outweigh the benefits of ZST).

As a non-client of this functionality, most likely, my two cents is that it is better to start with the more straightforward runtime-configured struct. I have a hard time imagining the use case for a smaller format struct; I can imagine cases where for example different services accessed by the same client would want different formats; const generics are still in-progress and are harder for newer Rust programmers to understand and work with.

In my applications, I do not see the need to provide runtime configurable formatting at the moment. If it became relevant in the future, I think the existing formatting facilities are sufficiently powerful to handle that as well.
So, no, I don't think that runtime configuration is necessary.

I believe a runtime configuration would be more flexible. For example in a web API, you might retrieve a date-time from a DB and use it with various other APIs that might have different format requirements.

Please re-read my original comment. I am seeking specific real-world use cases where runtime configuration is necessary for formatting. Parsing appears to be workable regardless of configuration, as the format is unambiguous.
Further comments similar to ones already made will be outright deleted, as I've been quite clear in the type of use case I'm looking for.

At this point, I have both parsing and formatting fully implemented. I am writing numerous tests and ensuring 100% code coverage before pushing everything up. But it's happening :tada:

I know there's a number of people following this, so I'll try to provide an update. Testing is going well, and led me to catch 3 errors so far. It gets quite tedious at times, so I'm not putting as much time into it as I theoretically could. With that said, over the coming days, I have family things and will then be taking a lengthy flight. At that point I'll be spending some time in a new country for work. I'm sure I'll do some exploring in my free time, as I am only there for a limited time. That will take priority over this (sorry not sorry). Once I return home I've got a little more going on, but will be back to "normal" by June 6. So I wouldn't plan on having this completed before then. At the absolute earliest, this will be released on June 2. That is when the MSRV can become Rust 1.57 per the crate's six-month policy, and the implementation of ISO 8601 requires const panics to work.
TL;DR get your hopes up, but let's be realistic with a timeframe :slightly_smiling_face: Next release on June 2 at the earliest, realistically June 6 or soon thereafter.

I have just pushed ISO 8601 support to main. It's not as good as it will be in the future, but it fully complies to the standard and the public API is final.
The two major things I'd like to improve on are performance and errors. The errors returned from failed parsing are terrible — technically correct but wildly misleading. Incidentally, the manner in which I will improve performance will also improve the error messages (it's effectively specialization based on the target type).
Please take a look at the implementation and give it a shot! There's a couple unrelated things I want to do before cutting a release, so there'll be a few days at the least before it goes out. I'm 100% abusing const generics, but I think it's ergonomic enough that it shouldn't be an issue.
Thanks again to @ColmanHumphrey and @slightcode for purchasing the standard in my name. This wouldn't have happened otherwise.

Nice one @jhpratt, great to see this!


Add route 53 support

What's this PR do?
Add a route 53 backend that supports posting SRV records to route 53.
This can be used to automatically register docker containers with route
53 SRV records.
Where should the reviewer start?
route53/route53.go
How should this be manually tested?
Modify the dev task in Makefile to look something like
docker run --rm \
		-e "AWS_ACCESS_KEY_ID=mykey" \
		-e "AWS_SECRET_ACCESS_KEY=mysecret" \
		-v /var/run/docker.sock:/tmp/docker.sock \
		$(NAME):dev registrator route53://<zone id>?ec2hostname=false

Then run make dev now you can start and stop separate docker containers and check route53 to ensure your services are (de)registered .
Any background context you want to provide?
This backend was developed to automatically register docker containers with Route 53 so Prometheus can collect metrics from apps hosted in docker.

I had to quote route53://<zone id>?ec2hostname=false to make work from the command line.

So it looks like it takes that name of the docker container and uses that for the base of the DNS name. What happens if you have two docker hosts running, both running registrator and configured to the same zone? Do they conflict, does it add multiple entries?

Yeah it will append new entries in the srv record. You'll end up with something like
1 10 6379 ip-172-xx-xx-11.ec2.internal
1 10 6379 ip-172-xx-xx-22.ec2.internal


GPII-3339: Disable Kubernetes Dashboard

Kubernetes Dashboad has been deprecated on GKE (see
https://cloud.google.com/kubernetes-engine/docs/concepts/dashboards for
details). This disables Kube Dashboard and removes other related bits of
code that are no longer needed.
This depends on gpii-ops/exekube#14, which needs to be merged first.

LGTM
administration-tasks comes from a sample exekube project, so I wonder about deleting the dashboard configuration entirely vs disabling it. However, given that Kubernetes Dashboard is deprecated for GKE and that we have no meaningful migration path for changes from the upstream sample exekube project's administration-tasks to our administration-tasks, deleting is probably best.

Thanks @mrtyler. One more thing to mention and which I've forgotten to add to the description - after applying this, one needs to delete terragrunt docker volume, otherwise the run will fail. This should be ok for CI, as the volumes get deleted after each run, but was causing me trouble on my local machine as I usually just run rake. Not sure if this should be mentioned anywhere, as it's a one-time thing.

LGTM, just throw a heads up in our channel when this PR is merged in order to delete our docker volumes

Thanks, +1 for removing administration-tasks, that is actually the module that's causing the issue mentioned above, and also it has chart directly underneath it, instead of in common/charts. I've created a ticket GPII-3392 to look into this.


Is this 'umbrella' repo needed?

I'm simply looking to have a discussion about this.
Since we have the actual language implementations elsewhere, do we find this repo provides value? Perhaps from an issue-gathering standpoint? Or maybe it does not?
I'm in spring cleaning mode for github.com/adobe so thought I'd throw this out as a question 😄

The history is that originally this was one repository, and was approved by the Open Source all together. Since then, it became more practical to keep them separate. However, from a documentation and customer support standpoint, it is much more convenient to have a single landing page to send customers. Otherwise, you will need to either send a partner multiple links, or ask them exactly which SDK they want. I believe it is more elegant to have a "landing page" for the SDKs rather than rely on lots of links getting separated, especially if a developer finds one SDK and is unaware that others exist.

OK, that's fair. Thanks for the info! I will close this.


bump cranelift version to 0.60.0

Some recent changes are needed for Lucet changes.

(I don't have the bit to actually publish to crates.io, somebody else will have to do that part.)

I can do the publish.

How important are the CI failures?  I see that a number of recent PRs have been getting merged with red CI, but I'm not well versed in what's liable to fail and what's not...

Can you hold this until #1311 is in? It had a failure on nightly only, I just rebased and force-pushed with hope that whatever was wrong with CI is fixed now

Yeah, our CI setup is acting a bit flaky at the moment. I'm not sure what our policy on merging PRs is until we fix it. It seems like it might make sense to delay publishing releases until we know our CI is green...

Can you hold this until #1311 is in? It had a failure on nightly only, I just rebased and force-pushed with hope that whatever was wrong with CI is fixed now

Sure, no problem!

https://github.com/bytecodealliance/wasmtime/pull/1330 should help us make more sense of the CI failures.

btw https://github.com/bytecodealliance/wasmtime/pull/1311 is merged so no more delay required there

I will do the publish and verify that the re-added publish script works.

Published!


enable the use of GP3 volumes

I've not touched the tests, because GP2 is still a valid default

Thanks! Likely it's fine, but have you tested it out on your own GoCD?

Yes I have. The API actually already accepts gp3 as an option, it just needs the UI updating. Otherwise you see an unlabeled option selected in the dropdown:

Yup yup, I had meant to do this a while back as I'd like to change the volumes used on https://build.gocd.org/ shortly as well but forgot about it (build.gocd.org happens to use ECS Elastic Agents).
Will cut a new release shortly.


Selenium Grid, Conference App

Hi Marcel,
I was able to start your containers but unable to get the following:

Selenium Grid	http://${docker-machine ip default}:4444/grid/console
Conference App	http://${docker-machine ip default}:48080/currentSessions

Am I suppose to build something in Jenkins in order to see those links active?
Once I have the containers up -- how should I navigate this demo?
Thanks,
Aliusa

The seleniumhub has to be started separately with "docker-compose -f docker-compose-selenium up". The conferenceApp builds (automagically ;) ) in jenkins and is also deployed from there in a separate docker Container.

docker-compose -f docker-compose-selenium.yml up


Bump pytest to 2.6 and py to 1.10

Codecov Report

Merging #56 (ead51c7) into master (019d1c9) will decrease coverage by 12.76%.
The diff coverage is 84.61%.

@@             Coverage Diff             @@
##           master      #56       +/-   ##
===========================================
- Coverage   75.37%   62.60%   -12.77%
===========================================
  Files           5        1        -4
  Lines         540      361      -179
  Branches        0       49       +49
===========================================
- Hits          407      226      -181
+ Misses        133      128        -5
- Partials        0        7        +7

Codecov Report

Merging #56 (ead51c7) into master (019d1c9) will decrease coverage by 12.76%.
The diff coverage is 84.61%.

@@             Coverage Diff             @@
##           master      #56       +/-   ##
===========================================
- Coverage   75.37%   62.60%   -12.77%
===========================================
  Files           5        1        -4
  Lines         540      361      -179
  Branches        0       49       +49
===========================================
- Hits          407      226      -181
+ Misses        133      128        -5
- Partials        0        7        +7


Support of other calculator

Dear Atsushi Togo,
Currently only VASP is supported out of the box.
A support of other main DFT codes would be great (in particular Quantum Espresso) for force calculations but this needs to be included at various points, e.g. in parsing the forces (QE saves them in the output trajectory) and in setting up the calculation.
Best regards,
Benedikt

I don't have enough resource to work on it now.

Thanks for the quick reply.
I have to discuss with my company if I am free to submit code. If so I would be willing to push some changes to support QE.
So far most of my solution is quite brute-forced  and based on catching exceptions.  Is that fine for you or do you plan on  a more structured interface?
Bests,
Benedikt

Then, we should start with the design of the interface. The parameters etc are not carefully chosen (mostly just pushing into Dict), and they are written just to work for me. I am not a user of QE. So the test is difficult. These are issues for me to improve aiida-phonopy. If you want to change aiida-phonopy, I appreciate if you do it little-by-little so that I can review. In addition, emerging DFT codes is also under the development in AiiDA team. So we have to avoid working duplicated stuffs.

I think supporting other calculators are on the way by the work of @bastonero. So I will close this issue. @BeZie, please discuss with @bastonero if you want to know more details.


erratic behaviour of update button

There's several cases in which the behaviour of the create/update button is kind of weird:

When you import a project the button changes to update but later if you change the name manually or even press the random name generator it won't change back to create
When you type the name of an already existing project it should probably change to update automatically to let you know that the project already exists. This means parsing the fs with every keystroke but i think it should be fine

I think the text field only generates a change event when you leave (ie unfocus it) it but I can take a look making the changes fire when you type....
https://github.com/ofZach/pgElectron/blob/master/app.js#L404-L414
I think this is just a jquery thing.....

Technically it's a little more complicated then that: (and is about your 2nd point)

The "updage/generate" check is done on change of the name field. This way, any change re-activates a check.
BUT if the field is still focused (user is typing), it doesn't do anything because that would make it switch way too often (and maybe erase the addons selection for nothing).
So when the name field is blurred (unfocused), it triggers it's 'change' event.

«but later if you change the name manually»
I can't reproduce this, can you be more specific ?
«or even press the random name generator»
--> true. (As the icon moved into the field, it gets focused while the change event is triggered, thus cancelling the check)
Should be fixed in 6a720eb


Fix incomplete syntaxes in SecAuthN

The Syntax section in some API references contains only a );. This PR trys to complete them using some knowledge from similar API references and Windows header files.

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

Thanks for the contribution, @bdbai ! I've merged your changes and they should be live soon.


Refactor claim school to be has_many with data migration

In preparation for the multiple schools journey we need to change the data model around previous employment.

Pull out the claim school and related employment questions about claimant's time at claim school out to a new Employment model.
Add an employments has_many association on Eligibility and introduce the concept of a selected_employment which is the employment the claimant is answering questions about.
Includes a data migration to migrate relevant claims to use new association. We've left the old columns on the eligibility table for now, a PR to remove them will come later when we're confident the data migration was successful

@pezholio The tricky thing about splitting it up is that it was all necessary to ensure the commit was green.

@pezholio I've split out a couple of commits in a way that should keep the commits green. I can have another go if you think it needs it

 Refactor claim school to be has_many with data migration

My initial review has been a pretty superficial one; I'm going to spend some time getting familiar with the data model and will then take another look!

I think I've resolved all the outstanding comments. Ready for another look when you get a chance 👍

All comments addressed and the seeds file now loads the fixtures, ready for another look 👍


Shipping and billing address from initial order are not used

When a subscription order is created, default shipping and billing addresses are used.
See the following 2 points in the code
https://github.com/mollie/magento2-subscriptions/blob/065ec02ac963aacfbf9b03ef3a52f97dfa50413b/Controller/Api/Webhook.php#L277
https://github.com/mollie/magento2-subscriptions/blob/065ec02ac963aacfbf9b03ef3a52f97dfa50413b/Controller/Api/Webhook.php#L215
When the customer uses multiple addresses, this might produce wrong results.
Because the customer can only configure a subscription when doing a fresh checkout, you should always use the addresses from the initial order.

Hi there @ThomasNegeli Thanks for opening this issue. In our latest release, we have addressed this issue. Newly placed subscriptions will use the address used in the order instead of defaulting to the default shipping & billing addresses. I will be closing this issue, but please don't hesitate to reopen it if necessary.


Meeting duration is missing from the e-mail report

Describe the bug
The meeting duration ("Duration (minutes)" field), which is filled in the engagement report, appears empty in the e-mailed report.
User expects this field present in the report, with value as filled in the engagement report.

Can this be because of the dictionary field engagementsIncludeTimeAndDuration in anet-dictionary.yml?

Can this be because of the dictionary field engagementsIncludeTimeAndDuration in anet-dictionary.yml?

Thank you for quick reply @cemalettin-simsoft!
The anet-dictionary.yml contains the following:
engagementsIncludeTimeAndDuration: true

Does this answer your question?

Can this be because of the dictionary field engagementsIncludeTimeAndDuration in anet-dictionary.yml?

Thank you for quick reply @cemalettin-simsoft!
The anet-dictionary.yml contains the following:
engagementsIncludeTimeAndDuration: true

Does this answer your question?

Yes it does, just wanted to cover the base case.


'Refresh Cache ' button not working on admin dashboard

Describe the bug in current situation
While updating the divisions on admin dashboard, 'Refresh cache' button not working, it shows an error
Link bug to the User Story
Impact of this bug
Describe the impact, i.e. what the impact is, and number of users impacted.
Chance of Occurring (high/medium/low/very low)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Test-Marshal
Steps to Reproduce
Steps to reproduce the behavior:

Go to admin dashboard on Test-Marshal
Update divisions for any ministry
Then click "Refresh cache'
See error

Actual/ observed behaviour/ results
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

Working as expected so closing ticket


yarn start fails

I've tried this both on Windows
Microsoft Windows [Version 10.0.19042.928]

and in a Codespace
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

> yarn start
[BUILD] Watchman:  spawn watchman ENOENT
[BUILD] Error while talking to watchman:  Error: spawn watchman ENOENT
[BUILD]     at Process.ChildProcess._handle.onexit (internal/child_process.js:268:19)
[BUILD]     at onErrorNT (internal/child_process.js:464:16)
[BUILD]     at processTicksAndRejections (internal/process/task_queues.js:80:21) {
[BUILD]   errno: -4058,
[BUILD]   code: 'ENOENT',
[BUILD]   syscall: 'spawn watchman',
[BUILD]   path: 'watchman',
[BUILD]   spawnargs: [ '--no-pretty', 'get-sockname' ]
[BUILD] }
[BUILD] node watcher.js exited with code 0
--> Sending SIGTERM to other processes..
[SITE] yarn workspace typescriptlang-org start exited with code 1

I see, so no watchman set up
I think we can probably make the build watcher optional and give a message what you're not getting by it not launching


Make batched_update DAG resistent to mid-update failures

Fixes

Fixes #2507 by @stacimc
Description

More context in #2507, but briefly:
Because the batched_update DAG is going to be used to perform potentially very long-running (multiple weeks long) updates, it needs to be able to handle the update task failing and retrying due to Catalog deployments. In the current implementation, when the update task retries it would resume from the beginning.
This PR takes the following approach:

In each DagRun, we create an Airflow variable suffixed with the query_id that we use to keep track of the progress of the update, updating it after each batch.
When the update_batches task runs, it checks to see if this variable exists and if so, resumes the update from that point. Otherwise it starts at the beginning.
An additional clean up task is added at the end to delete the Airflow variable.

Now, if the update_batches task fails and retries (or is cleared manually), it will resume from the point it left off.
Notably, I also removed the batch_start DagRun conf option that I had previously, as it should no longer be necessary to manually choose the starting point. If a DAG fails, you can manually find and edit this Airflow variable before retrying the DAG if you want to, but it should never be necessary.
Additional context
I chose this approach over deleting rows from the temp table as we go because it reduces the amount of error handling needed, but more importantly because I am concerned about adding an additional DELETE query to each batch when performance is already a major concern. Details about the cons to the dynamic task mapping alternative are available in the issue #2507.
I did not remove the resume_update DagRun conf option in this PR, because this is still useful in the following scenario:

User starts a DagRun which builds a very large temp table
The DagRun builds the temp table successfully
The update_batches task fails due to a syntax error in the user-provided update_query. Because this is a part of the DagRun conf, you cannot simply clear the task. You have to start a new DagRun with an updated conf, but you don't want to have to rebuild the temp table.

Testing Instructions

Setup:
Run just init to make sure you're starting out with our sample data in your local catalog db.
Test a 'regular' flow
Trigger the batched_update DAG with the following conf:
{
	"query_id": "my_query",
  	"table_name": "audio",
  	"select_query": "WHERE provider='wikimedia_audio'",
  	"update_query": "SET duration=0",
	"batch_size": 100,
	"dry_run": false
}

All tasks should pass (except for notify_failure, which is skipped).

Run just catalog/pgcli to open a pgcli session
Run SELECT COUNT(*) FROM audio WHERE provider='wikimedia_audio' AND duration=0 to verify that you have 3992 such records after running the update

Test clearing a DagRun
For this we need to simulate a DAG failure. I did this by modifying the update_batches task to raise an Error on the 3rd batch, by adding the following code on L118here:
if batch_start == 300:
    raise Exception("Oops")

Now trigger a DagRun with this conf:
{
	"query_id": "my_query",
  	"table_name": "audio",
  	"select_query": "WHERE provider='wikimedia_audio'",
  	"update_query": "SET duration=100",
	"batch_size": 100,
	"dry_run": false
}

The update_batches task should fail and go up_for_retry. In pgcli, run SELECT COUNT(*) FROM audio WHERE provider='wikimedia_audio' AND duration=100 and you should be able to see that 300 records were updated.
You should also be able to go to Admin > Variables in the UI and see an Airflow variable named batch_start_my_query which is set to 300.
Now remove the code you added to raise an Exception and clear the task. This time it should succeed. Verify in the logs that it resumed starting at row 300 and that it only updated 3692 records. (Search for the logs: Starting at 300 and finally, Updated 3692 rows. 0 remaining..)
Run the SELECT COUNT(*) command again in pgcli to verify that all records were updated.
Go to Admin > Variables and verify the Airflow variable is gone.
Test a new DagRun using resume_update
Trigger a new DagRun with this conf (note the typo in update_query):
{
	"query_id": "my_query",
  	"table_name": "audio",
  	"select_query": "WHERE provider='wikimedia_audio'",
  	"update_query": "SET durationn=500",
	"batch_size": 100,
	"dry_run": false
}

When the update_batches task fails and goes up for retry, manually mark the task as failed (to avoid having to wait for the retries). The whole DAG should fail. The temp table should not be dropped.
Now trigger a new DagRun with this updated conf, fixing the typo and enabling resume_update:
{
	"query_id": "my_query",
  	"table_name": "audio",
  	"select_query": "WHERE provider='wikimedia_audio'",
  	"update_query": "SET duration=500",
	"batch_size": 100,
	"dry_run": false,
        "resume_update": true
}

Verify that the select_rows_to_update and create_index tasks are skipped. update_batches should succeed, and the temp table and airflow variable should be dropped.
In pgcli, run SELECT COUNT(*) FROM audio WHERE provider='wikimedia_audio' AND duration=500 to verify that all 3992 records were updated.
Checklist

[ ] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[ ] My pull request targets the default branch of the repository (main) or a parent feature branch.
[ ] My commit messages follow best practices.
[ ] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[ ] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (if applicable).

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

There are a lot of formatting changes to DAGs.md after rebasing and regenerating the dag docs 🤔 Any concerns with that @AetherUnbound?

There are a lot of formatting changes to DAGs.md after rebasing and regenerating the dag docs 🤔  Any concerns with that @AetherUnbound?

Yea that definitely is O_o it looks like linting is no longer being run on the DAGs.md file after it's generated. I'll try to look into why that's happening.


To Do Items Never Checked Off

Three of my "Learn about" to-do items that I was saving to do all at once were never addressed. The screenshot was taken after completing the game. New to-do items and terms were added and successfully completed after, but not these.

I've got the same issue. What was happening was when I was saving them to do at a later time, they didn't show up when I called one of the friends.
This might be an issue with saving as I wasn't in the same session.


Use indexer as rpc

Description
As Carbonable I should be able to use indexer as rpc
because we store some data, we may want to impl starknet_rpc specs to provide an rpc access for whoever wants to deploy an indexer
Additional Information
[very Difficulty  - Go - low Priority]
Acceptance Criteria

[ ] Use indexer as rpc

Contribute to Carbonable during ODHack:
Provable environmental infra

Go to the CarbonableOD Telegram: https://t.me/carbonableOD
Present yourself and tell us which issue you want to pick
Explain shortly how you want to tackle the issue
Ask a question if you need some clarity
When you're selected you will be assigned to the issue

@tekkac Can this be assignd to me?

@fishonamos would you like to start working on this?
If yes, kindly please

Go to the CarbonableOD Telegram: https://t.me/carbonableOD
Present yourself
Explain shortly how you want to tackle the issue
Ask a question if you need some clarity
When you're selected you will be assigned to the issue

Hi I will love to start up on this!


Change Archive folder to Games

Change the Archive folder name to Games. Trying to make the language a bit clearer on what the folder do in the workspace.

Replaced Archives with Games folder.


Adding and removing layers from a map causes slowdown

If a layer is removed from a map, and then added, repeatedly, it causes the animations and website to slowdown substantially.
Possible issue with something not being removed each time?

Thanks for bringing this to my attention.  Could certainly be something I missed.  I don't know how soon I can investigate this myself, but the first place I would look is at the onRemove method and compare it to the onAdd method to see if something isn't being removed, as you suggest.
https://github.com/jwasilgeo/Leaflet.Canvas-Flowmap-Layer/blob/master/src/CanvasFlowmapLayer.js#L214-L261
If you have a public sample that reproduces this problem (like on jsfiddle, jsbin, etc.) that you can share, that would be a huge step forward in researching this.
Thanks!

Had a quick look through them, and all looks good to me! Very odd.
Will put up a jsfiddle in a bit. Thanks

Looks like something to do with Composite Layers according to Chrome

I have the same problem~

I have the same problem~

Can you all tell me more about what is in your DOM?  Specifically, what are the DOM elements in your <div class="leaflet-pane leaflet-overlay-pane"> when you first add this layer to the map, what does it look like when you remove it, and then what does it look like when you add it back in again?
Can someone please provide a public sample that reproduces the issue?

@jwasilgeo https://codepen.io/fetest/pen/yzOGpj?editors=0010
click the polygon area more than 3 times, you can find the canvas animation slowdown, meanwhile the start position of canvas animation has changed.
hope to resolve this problem, thank you very much！

@wonyun thank you for creating the sample reproducing this.  Actually, I am beginning to wonder if this and #10 are related to each other.  I'll try to find time over the next week or so to figure this out.  Thanks everyone.  My first thought is that I'll make sure the code resets some internal tracking property values during onAdd to the map.

I think this has been fixed in the recent commit to master f89fc9395c0d85e20f50a7a0c346e15641b3874a.  Can you please verify?  Perhaps soon I'll release a "v1" of this project.

Ok, closing for now.


Improve/feature hidden

This PR adds support for hidesBottomBarWhenPushed on view controllers to easily hide the tab-bar for a specific controller.

I guess we can merge the branch now?

@RamonGilabert year, already done :)


Fix start-stop test index cleanup

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[x] Tests for the changes have been added (for bug fixes/features)
[x] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix

What is the current behavior? (You can also link to an open issue here)
Test fails due to index not cleaned up in loops

What is the new behavior (if this is a feature change)?
Delete index before attempting to create again

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No

Other information:

Wrong repo


ChartjsNodeCanvas depending on node canvas

Hello I have been trying to use chartjs within a lambda function, therefore I used chartjs node canvas to create graphs in a node environment. I also use Amplify to manage my lambdas.
Lambda throws error
/var/task/node_modules/canvas/build/Release/canvas.node: invalid ELF header on execution.
I tried using your lambda layer and it successed with importing canvas to my code and running it, however the moment i import chartjs node canvas the lambda throws invalid ELF header error.
Is it possible that since the chartjs library depends on node-canvas, npm installs it and it overrides your lambda layer which has the correct binaries?

Currently the only way is to remove the duplicated canvas which may need some efforts. Thanks for suggesting to add chartjs.
Would do some more round of works here and target to release in next release. Thank you~

A new maintenance release is available through AWS Serverless Application Repository. Please deploy and try. Thank you.


[#282] Improve UG formatting, add details about max integer and chronological ordering of contacts

Fixes #282
Improve UG formatting, add details about max integer and chronological ordering of contacts.

Codecov Report

Merging #283 (3bd8616) into master (3ecf983) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #283   +/-   ##
=========================================
  Coverage     73.91%   73.91%
  Complexity      687      687
=========================================
  Files            98       98
  Lines          2101     2101
  Branches        238      238
=========================================
  Hits           1553     1553
  Misses          481      481
  Partials         67       67

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 3ecf983...3bd8616. Read the comment docs.


bash scripts automation (2/3)

Make it easier for other people to run the source locally.
Second pass: enable testing locally with parcel. Instead of automatically editing the package.json pre-commit script for them.
Do this after #76 and before #78.

Need this so travis ci tests can get past the bash prompts (by removing the prompts altogether).

Need this so travis ci tests can get past the bash prompts (by removing the prompts altogether).


[list page] the load should be able to initiate the criteria

The load action should dispatch the criteria

@durandx

@pierr is it sill needed ?

It will be done with FORM / Stores V2


Don't create a temp directory for requirements cache if users opted out.

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

SKIP_REQUIREMENTS_CACHE: is this internal or public?
We have some secret options, which are really not documented anywhere unless the user read the code. We should avoid this.

Yes, it's documented here: https://beam.apache.org/documentation/sdks/python-pipeline-dependencies/#pypi-dependencies (last line of the paragraph).
I'll close this in favor of https://github.com/apache/beam/pull/31961


Add functionality to exclude examples from VR tests

What is the context of this PR?
Fixes: #3116
Previously the sticky components would be failing the VR tests repeatedly. Looking at the backstop JS artifacts showed that the example was not being fully rendered and no fix was found to prevent this. The decision was made to stop certain examples from being included. I have added a change where you can edit the contents of the exclude list to remove certain examples from the VR tests.
Important note: If you are making a change to Table of Contents or a change to any global CSS. you must also check the ToC stick components separately.
How to review this PR
Check that the VR tests no longer run on example-table-of-contents-sticky and example-table-of-contents-sticky-full-page examples. Also sense check the code and please give suggestions if you have any enhancements.
Checklist
This needs to be completed by the person raising the PR.

[x] I have selected the correct Assignee
[x] I have linked the correct Issue

Isn't there a better way of fixing this? I don't like removing examples from tests. I can see you've added warning comments to the affected files but I can see this still getting forgotten. It will be very easy to forget to check this when changing global css. If we haven't already I think we need to look into why the examples aren't being rendered correctly, is it a race condition?

Alessio had looked into fixing this issue for a week in Feb and tried multiple different solutions with no result. I'll give it a try today, but if I can't, then this will be a temporary fix to prevent other PRs from being blocked while I work on a solution that separates CI tests from local tests so that all local tests run but omits tests in CI.

Isn't there a better way of fixing this? I don't like removing examples from tests. I can see you've added warning comments to the affected files but I can see this still getting forgotten. It will be very easy to forget to check this when changing global css. If we haven't already I think we need to look into why the examples aren't being rendered correctly, is it a race condition?

Alessio had looked into fixing this issue for a week in Feb and tried multiple different solutions with no result. I'll give it a try today, but if I can't, then this will be a temporary fix to prevent other PRs from being blocked while I work on a solution that separates CI tests from local tests so that all local tests run but omits tests in CI.

I still don't think removing test coverage is the answer, which includes removing tests in CI. There must be another way to fix this


Avoid running with django >=3.0<3.1.3

as those package versions allow the installation of incompatible
asgiref versions.

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender


Invalid Command "remove CorporateWerServer* from"

This command:
"remove CorporateWerServer* from Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting"
is garbage, it is not a valid command at all. How did this get missed during proofreading?
Please correct.....

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

ID: cdad1b23-8c75-cd08-41cc-6313fc7016bd
Version Independent ID: f7979a0f-a1be-100f-33b5-01627c45f783
Content: Prepare and customize a master VHD image - Azure
Content Source: articles/virtual-desktop/set-up-customize-master-image.md
Service: virtual-desktop
GitHub Login: @Heidilohr
Microsoft Alias: helohr

@MikhailCompo Thanks for the feedback! I have assigned the issue to content author to check and update the document as appropriate.We will update you accordingly.

@Heidilohr Can you please check and add your comments on this doc update request as applicable


Add back stage 2 slideshow

This PR puts Stage 2 back into the story.
The slideshow runs, but the Stage 2 component state is not being written to the db, so I must be missing something. @Carifio24 or @nmearl, would you mind taking a look at this when you get a chance, please?

@nmearl, @Carifio24, I'm getting a long list of terminal errors that ends with this. I'm wondering if it's complaining because Stage 2 doesn't have any markers. It's just the slideshow. Any ideas of what to look into? I can post what I have if that would be helpful, but I can't check if it's correct until I figure out what's causing these errors.
  File "/Users/Pat/anaconda3/envs/common-solara/lib/python3.11/site-packages/pydantic/_internal/_generate_schema.py", line 405, in _unknown_type_schema
    raise PydanticSchemaGenerationError(
pydantic.errors.PydanticSchemaGenerationError: Unable to generate pydantic-core schema for <enum 'BaseMarker'>. Set `arbitrary_types_allowed=True` in the model_config to ignore this error or implement `__get_pydantic_core_schema__` on your type to fully support it.

If you got this error by calling handler(<some type>) within `__get_pydantic_core_schema__` then you likely need to call `handler.generate_schema(<some type>)` since we do not call `__get_pydantic_core_schema__` on `<some type>` otherwise to avoid infinite recursion.

For further information visit https://errors.pydantic.dev/2.7/u/schema-for-unknown-type

Ok, I think I've gotten around the problem by putting in 1 marker. Making progress now.

This is all working correctly for me now. @Carifio24, would you mind taking a look, please?


the 'value' binding seems to be causing double key strokes in input text boxes on ios devices

When I deploy my meteor application to the ios simulator or my ios device, on input text fields where I have the text bound to the viewmodel via the 'value' binding, keystrokes from my keyboard(simulator) and from the ios keyboard render two characters. However, hitting the delete or backspace key only removes one of them.
Help Please!
Here is some sample code showing the issue:
https://github.com/devinesoftware/testBed

How do I run an ios simulator on Linux or Windows?
On Jul 11, 2015 1:44 PM, "devinesoftware"<EMAIL_ADDRESS>wrote:

When I deploy my meteor application to the ios simulator or my ios device,
on input text fields where I have the text bound to the viewmodel via the
'value' binding, keystrokes from my keyboard(simulator) and from the ios
keyboard render two characters. However, hitting the delete or backspace
key only removes one of them.
Help Please!
Here is some sample code showing the issue:
https://github.com/devinesoftware/testBed
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/78.

You'll need to install X-Code. If you don't have a mac, you'll have to create a VM with OS X on it and install X-Code that way.
Once you have x-code installed, you'll need to run the following commands:
meteor add-platform ios
meteor run ios-device
The last command will package your meteor application up into a deployable bundle. it will then launch X-Code and from there you can run in the ios-simulator or run it on an ios device.

I'll take a look at it when I get in front of a computer. In the meantime,
is there any chance you can save me the time and make me a virtual box?
On Jul 11, 2015 1:52 PM, "devinesoftware"<EMAIL_ADDRESS>wrote:

You'll need to install X-Code. If you don't have a mac, you'll have to
create a VM with OS X on it and install X-Code that way.
Once you have x-code installed, you'll need to run the following commands:
meteor add-platform ios
meteor run ios-device
The last command will package your meteor application up into a deployable
bundle. it will then launch X-Code and from there you can run in the
ios-simulator or run it on an ios device.
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/78#issuecomment-120655121
.

Sure, but can you point me to an online resource where I can build you a mac OS-X VM image?

I don't know, you're the osx user =D
On Jul 11, 2015 2:02 PM, "devinesoftware"<EMAIL_ADDRESS>wrote:

Sure, but can you point me to an online resource where I can build you a
mac OS-X VM image?
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/78#issuecomment-120657335
.

Ha.
Thanks

From my research (stackoverflow), you're not legally allowed to run OS X on anything other than apple hardware. I'm going to use knockout-client instead for my project.  However, if it doesn't work on iOS, well that's going to make it a 'no-go' for many projects.
Good luck!

I'll look into it. Thanks for the heads up.
On Jul 11, 2015 2:16 PM, "devinesoftware"<EMAIL_ADDRESS>wrote:

From my research (stackoverflow), you're not legally allowed to run OS X
on anything other than apple hardware. I'm going to use knockout-client
instead for my project.  However, if it doesn't work on iOS, well that's going to make it
a 'no-go' for many projects.
Good luck!
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/78#issuecomment-120658212
.

I've narrowed it down in the release. It happened during the devs from the 1.8.2 to the 1.8.3.
For the moment, I've blocked the updates on the 1.8.2 (got some customers on iOS).

Good deal man. Thanks for looking into it. I look forward to using it when you've got the issue resolved.

Ahh the joys of fixing something in ie and breaking it on Firefox, fixing
it for Firefox and breaking it for iPhone. All the while your tests running
just fine in Chrome.
Please test it on the input of vmtest.meteor.com (the textarea doesn't do
anything)
Thanks for your patience.
On Jul 21, 2015 9:16 AM, "devinesoftware"<EMAIL_ADDRESS>wrote:

Good deal man. Thanks for looking into it. I look forward to using it when
you've got the issue resolved.
—
Reply to this email directly or view it on GitHub
https://github.com/ManuelDeLeon/viewmodel/issues/78#issuecomment-123366477
.

Please test version 1.8.9
I refactored the value binding and it should work on iPhone too

I share your joy on an everyday basis :confused:
The 1.8.9 fixes the issue :+1: Thanks for your reactivity (well on a package for reactivity, I was quite sure of it :smile: ).


Error when running with FastAPI

ERROR:    Traceback (most recent call last):
  File "/opt/lk/eda-services/verifire_service/.venv/lib/python3.11/site-packages/starlette/routing.py", line 677, in lifespan
    async with self.lifespan_context(app) as maybe_state:
  File "/opt/lk/eda-services/verifire_service/.venv/lib/python3.11/site-packages/starlette/routing.py", line 566, in __aenter__
    await self._router.startup()
  File "/opt/lk/eda-services/verifire_service/.venv/lib/python3.11/site-packages/starlette/routing.py", line 654, in startup
    await handler()
  File "/opt/lk/eda-services/verifire_service/verifire_service/web/lifetime.py", line 35, in _startup
    main("verifire_service.services.s3_upload_poller.s3_upload_task")
  File "/opt/lk/eda-services/verifire_service/.venv/lib/python3.11/site-packages/sqs_polling/main.py", line 46, in main
    _handler(p)
  File "/opt/lk/eda-services/verifire_service/.venv/lib/python3.11/site-packages/sqs_polling/polling.py", line 123, in _handler
    loop.run_forever()
  File "uvloop/loop.pyx", line 1377, in uvloop.loop.Loop.run_forever
  File "uvloop/loop.pyx", line 518, in uvloop.loop.Loop._run
RuntimeError: this event loop is already running.

ERROR:    Application startup failed. Exiting.

code
@polling(
    queue_name="service-s3",
    max_workers=5,
    max_number_of_messages=10,
)
def s3_upload_task(
    self: Polling,
    message_body: str,
    message_attribute: dict[str, Any] | None,
    message_group_id: str | None,
    message_duplication_id: str | None,
):
    import json
    from pprint import pprint

    data: dict[str, Any] = json.loads(message_body)
    data.update(message_attribute or {})
    pprint(data)

Thanks for creating the Issue.
Can you tell us a little more about how it is used in combination with FastAPI?

How about this?
https://github.com/nonchan7720/sqs-polling/pull/24/files#diff-8c7c9c5c527d60e8e48ce37d55cc11ed39f3b4d4cf678e239aeec67ad3bfad45

@grizzly-monkey
How about this?
https://github.com/nonchan7720/sqs-polling/pull/24/files#diff-8c7c9c5c527d60e8e48ce37d55cc11ed39f3b4d4cf678e239aeec67ad3bfad45

Thanks for creating the Issue. Can you tell us a little more about how it is used in combination with FastAPI?

Thanks for your fast response... I am trying to consume messages from SQS in our fast api application.
For this  i am using startup event of fast api to start consuming the SQS messages like this
    @app.on_event("startup")
    async def _startup() -> None:  # noqa: WPS430
        app.middleware_stack = None
        if not broker.is_worker_process:
            await broker.startup()
        app.middleware_stack = app.build_middleware_stack()

        db.connect(path=settings.db["uri"], pem=settings.db["secret_key"])
        main("verifire_service.services.s3_upload_poller.s3_upload_task") # here is the queue consumer start
        pass  # noqa: WPS420

    return _startup

i am using boiler plate code from
https://github.com/s3rius/FastAPI-template
for creating our application if this helps

I am not sure of right fix but i can tell if i comment out
form main.py main()
    # loop.run_forever()
    # loop.close()

it works as needed , may be becuase the fast-api template i am using already is running an event loop ? 🤔
from typing import Any

from gunicorn.app.base import BaseApplication
from gunicorn.util import import_app
from uvicorn.workers import UvicornWorker as BaseUvicornWorker

try:
    import uvloop  # noqa: WPS433 (Found nested import)
except ImportError:
    uvloop = None  # type: ignore  # noqa: WPS440 (variables overlap)

class UvicornWorker(BaseUvicornWorker):
    """
    Configuration for uvicorn workers.

    This class is subclassing UvicornWorker and defines
    some parameters class-wide, because it's impossible,
    to pass these parameters through gunicorn.
    """

    CONFIG_KWARGS = {  # noqa: WPS115 (upper-case constant in a class)
        "loop": "uvloop" if uvloop is not None else "asyncio",
        "http": "httptools",
        "lifespan": "on",
        "factory": True,
        "proxy_headers": False,
    }

class GunicornApplication(BaseApplication):
    """
    Custom gunicorn application.

    This class is used to start guncicorn
    with custom uvicorn workers.
    """

    def __init__(  # noqa: WPS211 (Too many args)
        self,
        app: str,
        host: str,
        port: int,
        workers: int,
        **kwargs: Any,
    ):
        self.options = {
            "bind": f"{host}:{port}",
            "workers": workers,
            "worker_class": "verifire_service.gunicorn_runner.UvicornWorker",
            **kwargs,
        }
        self.app = app
        super().__init__()

    def load_config(self) -> None:
        """
        Load config for web server.

        This function is used to set parameters to gunicorn
        main process. It only sets parameters that
        gunicorn can handle. If you pass unknown
        parameter to it, it crash with error.
        """
        for key, value in self.options.items():
            if key in self.cfg.settings and value is not None:
                self.cfg.set(key.lower(), value)

    def load(self) -> str:
        """
        Load actual application.

        Gunicorn loads application based on this
        function's returns. We return python's path to
        the app's factory.

        :returns: python path to app factory.
        """
        return import_app(self.app)

I was able to confirm that the error occurs when an event has already been started, so I
PRs were merged, as shown in the sample code in the previous comment.
I think it is possible to poll by calling the handler method as in the sample code in the previous comment.

I will change the sample code to use @app.on_event("startup").

ok can you release it to pypi so that i can refresh dep and check...
please excuse my python brevity as i am novice py dev.
Thanks for all your help.

I've confirmed that it works fine as shown here, so I'll merge it and release it: 🙆♂
https://github.com/nonchan7720/sqs-polling/pull/24#issuecomment-1793716535

Released by v0.0.5.