Fix ConvertTo-SecureString with key regression due to .NET breaking change

PR Summary
This PR fixes a regression in ConvertTo-SecureString found and reported by this Issue.
PR Context
This regression was caused by the change of behavior in the .NET CryptoStream.Read() method.  Previously, the Read method would synchronously read entire stream contents into the provided buffer, until the buffer was filled or the stream ended.  It was recently changed to read available data and return before the buffer is filled or the stream ended, breaking the existing code which would now read only partial stream contents.
Instead of performing multiple reads to ensure all stream content is obtained, this change uses an alternative common pattern to copy entire stream contents.  It also takes care to dispose all disposable objects and zero out clear-text buffers.
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@rjmholt Thanks for the review!


Full Stack project review

Full Stack project review
Hi @FUKA-INNOVATIONS! Here's a short code review for your Full Stack course project. The comments in this review are just suggestions for improvements, which you can take into account in this or in the future projects, if you want to. You don't have to do any changes in this project based on these comments to get the credits.
User experience
What did I do?

I registered a new user
I created an event
I went through the events on the home view in different locations
I attended events
I created a post
I checked my profile
I logged out

Experience

The application's user interface is very stylish and easy to use. Well done! 🏆
Creating a post without an image seems to fail although the form indicates that the image is optional
The loading time on the home view is very long
Neat loading indicators!

Code

The code is well organized, great work!
Great use of hooks! These hooks simplify the components' code a lot
State management related to async operation require somewhat repetitive boilerplate code. With the React Query library, it is easy to abstract these operations into simple, reusable hooks
Avoid inline styles. Use Stylesheet.create method instead
The UI theme is configured which makes the styling more flexible and maintainable. Good job!
Good idea to use react-hook-form in the form state management and Yup in the form validation
The Expo deployment is automated with a workflow, nicely done!

Summary
A very good-looking application with a nice set of features! There weren't any major bugs or usability issues during this review. Most of the features in the application worked very smoothly and intuitively. The project's code is well organized and the overall code quality is high. Good job!

Hello @Kaltsoon, thank you very much for the review!


deploy prometheus

deploy prometheus

Please merge prometheus and grafana roles into a single one, we can't add so many separate roles.


fix: Update Android SDK XML attribute docs

Description

Documenting XML attribute updates in android sdk v2.0.0

Testing required outside of automated testing?

[x] Not Applicable

Screenshots (if appropriate):

[x] Not Applicable

Rollback / Rollforward Procedure

[x] Roll Forward
[ ] Roll Back

Reviewer Checklist

[ ] Description of Change
[ ] Description of outside testing if applicable.
[ ] Description of Roll Forward / Backward Procedure
[ ] Documentation updated for Change

:tada: This PR is included in version 1.47.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Bump Golang to version 1.21.8

:tada: This PR is included in version 3.13.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_215a9826-ad9a-4384-bd8d-c0d159e37dfe/pull/1 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target_215a9826-ad9a-4384-bd8d-c0d159e37dfe.git

Docs Build status updates of commit 82765fb:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error] Run script failed with no detailed information. Please retry building your content again. If the issue still happens, open a ticket in https://SiteHelp and include the error report for our team to troubleshoot

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


Add a test for the compute method in Foundation.

The compute method in the in Foundation spawns isolates and attempts to run tasks on the same. This exercises the Engine and the VM in unique ways. There are no tests for this method in the framework. Isolate spawning tests in the engine also do not test child and grandchild isolate runs. Tests should be added for the following cases:

Single child isolate spawn and shutdown.
Child isolate spawns its own children.
Child isolates are spawned and the engine (the Flutter view) is torn down.

cc @rmacnak-google who may be able to think of more uses cases of secondary isolates we might not be testing.
I can wire up the tests for the same in the engine. Can anyone do the same in the framework? cc @tvolkert, @Hixie

Wow, I suck, I didn't add a test. My bad.

I'll add a test to the framework once I get my desktop back up.

Since we implemented spawning in https://github.com/flutter/engine/commit/09d05a38912a3c1a906e95099cac9a7e14fae85f without looking at the URI, it's probably also worth testing that Isolate.spawnUri fails in a reasonable way and doesn't just silently behave like Isolate.spawn.

Can we assert that in the engine somehow? Actually support spawnURI in the JIT environment and fail with an error generated in the engine in AOT contexts.

If we don't intend to support spawnUri in an AOT context, we probably should also not support it in a JIT context unless we can provide the JIT context to release builds.
cc @sbaranov @zanderso

Actually, I can't add a test for "Child isolate spawns its own children" because compute is sync, not async.


Cleanup DLQ on errors when creating consumer-group

Coverage increased (+0.1%) to 66.714% when pulling 7ce6a51a02593ca15834cb8e157f976f5b0be1bf on dlq-cleanup into 81b1e0128904df9dfc7bae474e170319bc56700b on master.


💡 [REQUEST] - Two same blog in the blog section of the website.

[x] I am from GSSoC23.
[x] I would like to be assigned this task.

fill [x] to check the boxes.

Section
Description

Concise Description
Two same blogs in the blog section

Solution Proposed
Want to remove one

Screenshots
[

]

Code of Conduct
By submitting this issue, you agree to follow our Code of Conduct.

[x] I follow the Contributing Guidelines of this project.
[x] I have checked the current issues for duplicate problems.
[x] I have read the readme of this repository.

Hi @HimanshuNarware, thanks for reporting the issue and submitting the PR. soon it will be merged.


How to train a model to retain more texture details?

I'm currently trying to train your model, but I found that when encountering leaves, lawns, sand grains, etc., the model recreates these scenes badly, how can I adjust the training loss to make the model support these scenes, or need to add more such scenes dataset?

Hi, thanks for your attention to our work. The restoration of those regions of fine-grained details is challenging, especially when high perceptual quality is required and faces the unknown degradation in a real-world application. In other words, the generation capacity of the model might be limited in those regions if the input image is degraded severely. To enhance the performance, I think adding more training data with similar scenes and introducing local-based losses may be helpful. But most importantly, the degradation process in the training and testing should be carefully controlled if possible (when you apply the model to a specialized task), to keep consistency between training and testing.


Can not co-existence with react-native-keychain

Tested on react-native version 0.63.2
I already use react-native-keychain in our project and we've been really happy with that.
But now I am looking in to the possibility of backing my Apollo (graphql) cache with react-native-mmkv-storage but I get a compilation error on iOS:
duplicate symbol '_accessibleValue' in
> libRNKeychain.a(RNKeychainManager.o)
> libreact-native-mmkv-storage.a(SecureStorage.o)

Something that has come up before or do you have any solution to it?

fixed it in v0.4.3


Fixed Typos and minor issues in CODE_OF_CONDUCT.md

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Docs Update
Why was this change needed? (You can also link to an open issue here)
To improve the readability and understanding of the CODE_OF_CONDUCT.md file for contributors.
Other information:
Added bullets and fixed minor issues.

@dartpain Please merge this pull request.

Thank you for your PR, but it looks like the whole CODE_OF_CONDUCT.md file was just deleted.

@dartpain  Sorry, it happened by mistake. I have made another new pr with  correct changes So ,I am now closing this pr.
I deeply regret for the inconvenience caused.

No worries, thank you!


bug dsvm notebook spark

Description

Bug in unit test notebook spark.
Related Issues

https://github.com/microsoft/recommenders/issues/987
Checklist:

[ ] I have followed the contribution guidelines and code style for this project.
[ ] I have added tests covering my contributions.
[ ] I have updated the documentation accordingly.

I need to investigate this, the job is cancelled after 20min, which is the max time.


Improve JWT Authentication

Changed the massage when the jwt token fails
You don't need more to pass a key when try to generate a token
TokenUtil has more one method, getClaims(String token), pass the token and get all the claims.

Nice!
Now it's easier to validate websockets requests with api rest's jwt


Update machine-learning-data-science-process-sql-walkthrough.md

Fixed reference links to Reader, Project Columns, and Metadata Editor modules

Hi @msolhab, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (mohabib). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


[Bug] Express generator fails with Unrecognized key "whitelabel"

Describe the bug
When I run fern generate --local, it ends up with an error that looks like:
Docker exited with a non-zero exit code. Logs here: /var/folders/_9/7yr2nw5x5jd0bdycp0f5m9nm0000gq/T/tmp-35967-wCeQZTohYcjJ

When I cat the log, it shows:
cat /var/folders/_9/7yr2nw5x5jd0bdycp0f5m9nm0000gq/T/tmp-35967-wCeQZTohYcjJ

/bundle.js:15117
      throw new ParseError(parsed.errors);
            ^

ParseError: whitelabel: Unrecognized key "whitelabel"
    at Object.parseOrThrow (/bundle.js:15117:13)
    at async ExpressGeneratorCli.run (/bundle.js:260108:24)
    at async ExpressGeneratorCli.runCli (/bundle.js:260103:9) {
  errors: [
    {
      path: [ 'whitelabel' ],
      message: 'Unrecognized key "whitelabel"'
    }
  ]
}

To reproduce
Steps to reproduce the behavior:

Add fern generator express:

      - name: fernapi/fern-typescript-express
        version: 0.7.2
        output:
          location: local-file-system
          path: ../api/src/fern

Go to fern directory
Run the command 'fern generate --local'
See error

If relevant, provide a minimal API definition (OpenAPI or Fern Definition) or Docs configuration (docs.yml) that can be used to reproduce the error.
Expected behavior
I was expecting express boilerplate
Screenshots
If applicable, add screenshots to help explain your problem.
Version
Fern Version: 0.18.1
Additional context
Add any other context about the problem here.

bumped version to
default-group: local
groups:
  local:
    generators:
      - name: fernapi/fern-typescript-express
        version: 0.9.6
        output:
          location: local-file-system
          path: ../api/src/fern
        config:
          noSerdeLayer: true

and its working now!


Added Custom Password Requirements to System Settings

Introduced functionality to allow admin users to set custom password requirements from system settings. All previously stated password requirements still exist as the default.
Within system settings, a new field has been added to set minimum password length, as well as fields to dictate whether numbers, uppercase/lowercase letters, and special characters are required within user passwords.

This functionality has been added to both changing user passwords, as well as setting the password when adding a new user.

When these settings are changed, all help text popups and form validation errors reflect the requirements set within system settings.

One additional thing that would be nice to add would be a max password length. Some vendor risk questions ask about max length because of the "risk" of DoS attacks.
I think a default of 24 characters would be good default.

FWIW, I'd make the max 48 - my password manager is set to 25 - if nothing else, I found out how many sites have a max less than that so we can do better ;-)


inconsistent webpack build

Your Windows build number:  (Type ver at a Windows Command Prompt)
Microsoft Windows [Version 10.0.16278.1000]

What you're doing and what's happening:  (Copy&paste specific commands and their output, or include screen shots)

$ npm run build (getting errors)

getting erros

$ npm run build (running it again magically fixes it!)

magically fixes it

What's wrong / what should be happening instead:
Similar to my issue #2494 ; This build is a hit or miss, sometimes I need to run the same script 3x to 4x just to get it running.  I have my Defender Off.

Seems to me that it can't reach/read the node_modules, looks like another File I/O Issue?

@thisguychris - Thanks for your post. Can you please share the full repro steps? Also, can you try the repro on LxFs ex: ~ (home directory) and share your observation?

I'm just doing a normal webpack production build, so webpack -p.  This code is something internal so I can only share some bits since I'm under NDA.
I'll try to build in the ~/ directory

Hi, just reporting back, building it on ~/home
I've consistently not getting the same error.   I tried building it 4times and all 4 of them gives me consistent result.

I'm just doing a normal webpack production build

Microsoft NT Kernel developers are perhaps not versed on "normal webpack production builds"....
Anyway, there seems to be something to the reports of files/directories disappearing. I haven't seen it myself, but the error from the screencap here is Module not found: Error: Cannot resolve [whatever] in [wherever], which then magically reappears on another run. Which is about the same as #2484, which is unrelated to webpack production builds of the normal or abnormal variety.

I am getting a feeling that this is related to #2448 (funny how it's the last two digits swapped from #2484 :)), also, because of the intermittent nature of the issue. #2448 is a regression between builds 16251 and 16278. It would be interesting to see if this issue also appears on build 16251.

Sounds familiar. Building big things in lxss fails very occasionally, once or twice in a long build. Attempting the build again gets past the problem, usually. Now testing Insider Build 16288.1, and it most definitely fails in the same way on a DrvFs mounted system.

Occasional fails still occur when building exclusively within LxFs within the lxss directory. One or two files vanishing or appearing as directories in building, say, Qt or Gtk+3. This is such a pity, because the system used to be completely reliable both in DrvFs and LxFs.

Thanks for the input @Warblefly. Adding @SvenGroot.

oh yes, I tried using yarn too.  I get about the same results using npm.  So this is definitely in WSL and not on nom or yarn.  I agree its related to #2448


Blackmar-Diemer Gambit Overhaul

The page numbers refer to the extensive book The Blackmar-Diemer Gambit by Christoph Scheerer.
Transpositions

Removed 1. d4 d5 2. e4 dxe4 3. Nc3 called Blackmar-Diemer Gambit. (There is no other sensible sequence of moves reaching 1. d4 d5 2. e4 dxe4 3. Nc3 without reaching 1. d4 d5 2. e4 first.)

Hübsch Gambit

Removed 1. d4 Nf6 2. Nc3 d5 3. e4 Nxe4 called Queen's Pawn Game: Hübsch Gambit.
Renamed 1. d4 Nf6 2. Nc3 d5 3. e4 from Blackmar-Diemer Gambit to Queen's Pawn Game: Hübsch Gambit.
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 called Blackmar-Diemer Gambit.

Currently, we have the following (awkward) sequence of transpositions before reaching the starting position of the Hübsch Gambit after 1. d4 Nf6 2. Nc3 d5 3. e4 Nxe4:
1. d4 { Queen's Pawn Game } 1... Nf6 { Indian Defense } 2. Nc3 d5 { Queen's Pawn Game: Chigorin Variation } 3. e4 { Blackmar-Diemer Gambit } 3... Nxe4 { Queen's Pawn Game: Hübsch Gambit }
We transpose out and into the Queen's Pawn Game a total of two times. Since 3. e4 is gambitting the pawn, the Hübsch Gambit should start after 1. d4 Nf6 2. Nc3 d5 3. e4. The result is the following (tidier) sequence of transpositions, where we only leave and re-enter the Queen's Pawn Game once:
1. d4 { Queen's Pawn Game } 1... Nf6 { Indian Defense } 2. Nc3 d5 { Queen's Pawn Game: Chigorin Variation } 3. e4 { Queen's Pawn Game: Hübsch Gambit } 3... Nxe4
Note that taking the pawn on e5 with 3... dxe4 transposes into the main line of the Blackmar-Diemer Gambit after 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6:
1. d4 { Queen's Pawn Game } 1... Nf6 { Indian Defense } 2. Nc3 d5 { Queen's Pawn Game: Chigorin Variation } 3. e4 { Queen's Pawn Game: Hübsch Gambit } 3... dxe4 { Blackmar-Diemer Gambit }
Transpositions into other openings

Added 1. e4 c6 2. d4 d5 3. Nc3 dxe4 called Caro-Kann Defense [p.51]. (Transposing from 1. d4 d5 2. e4 dxe4 3. Nc3 c6.)
Added 1. e4 Nc6 2. d4 d5 3. Nc3 dxe4 called Nimzowitsch Defense: Scandinavian Variation, Bogoljubov Variation [p.54]. (Transposing from 1. d4 d5 2. e4 dxe4 3. Nc3 Nc6.)

BDG Variations
I shortened the opening names for readability.

Renamed 1. d4 d5 2. e4 dxe4 3. f3 from Gedult Gambit to Blackmar Gambit [p.13].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 e5 4. Be3 from Diemer Attack to Soller Attack [p.15].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 e5 4. Nge2 from Rassmussen Attack to Rasmussen Attack [p.17].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 e5 4. Nxe4 from Simple Variation to Lange Gambit [p.36].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 c5 called Reversed Albin Countergambit [p.52].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 e6 from Weinsbach Declination to Weinsbach Defense [p.71].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 e3 from Langeheinecke Defense to Langeheinicke Defense [p.84].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 Bf5 from Vienna Variation to Vienna Defense [p.103].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Qd6 called Holwell Defense [p.131].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 a6 called Gedult Defense [p.134].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bf5 from Tartakower Variation to Gunderam Defense [p.206].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bf5 6. Ne5 e5 7. Be4 called Gunderam Defense, Stader Variation [p.213].
Renamed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bg4 from Teichmann Variation to Teichmann Defense [p.233].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bg4 6. h3 Bxf3 7. Qxf3 c6 8. Qf2 called Teichmann Defense, Ciesielski Variation [p.256].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bg4 6. h3 Bxf3 7. Qxf3 c6 8. g4 called Teichmann Defense, Seidel-Hall Attack [p.260].
Added 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 Bg4 6. h3 Bxf3 7. Qxf3 c6 8. Be3 called Teichmann Defense, Classical Variation [p.266].

Zero Value Lines
The following lines have no practical / theoretical / historical value and are pretty much never played:

Removed 1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 h5 called Blackmar-Diemer Gambit Accepted: Rook Pawn Defense.
Removed 1. d4 d5 2. e4 dxe4 3. Nc3 Bd7 called Blackmar-Diemer Gambit: Grosshans Defense.

Obscure Lines
I couldn't find any information about the following lines and they don't seem to have zero value. (Maybe someone else wants to look into this.)

1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. f3 exf3 5. Nxf3 e6 6. Bg5 Be7 7. Bd3 Nc6 8. O-O Nxd4 9. Kh1 called Blackmar-Diemer Gambit Accepted: Euwe Defense, Zilbermints Gambit.
1. d4 d5 2. e4 dxe4 3. Be3 called Blackmar-Diemer Gambit: Diemer-Rosenberg Attack.
1. d4 d5 2. e4 dxe4 3. Bc4 called Blackmar-Diemer Gambit: Fritz Attack.
1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. Be3 called Blackmar-Diemer Gambit: Rasa-Studier Gambit.
1. d4 d5 2. e4 dxe4 3. Nc3 Bf5 4. f3 Nf6 5. Bc4 called Blackmar-Diemer Gambit: Zeller Defense, Soller Attack.
1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. Bg5 called Blackmar-Diemer Gambit: von Popiel Gambit.
1. d4 d5 2. e4 dxe4 3. Nc3 Nf6 4. Bg5 Bf5 5. Bxf6 exf6 6. g4 Bg6 7. Qe2 Bb4 8. Qb5+ called Blackmar-Diemer Gambit: von Popiel Gambit, Zilbermints Variation.

Thanks!


First blog post!

Sorry, still trying to figure out how to make PR's to just our project.

No problem @caleybrock, let me know if you have any questions :)


Counter strike 2 decompile maps brushes converts to static prips after decompile

Describe the bug
Hi
I don't know if it's a bug, problem or even a normal thing but when decompile cs2 maps with vrf every brushes turns to static props and losing their collision i mean players can pass through it or grounds losing their collision and player falling down unless if you fill every walkable space with clip.
Do you guys have any idea about how to fix that?
Btw I'm sorry for my bad English
Relevant log output or exception with stacktrace
No response
What game does this happen in
Counter strike 2
Reference file in a Source 2 game
All compiled map files
Expected behavior
Decompile maps with collided brushes
What version of VRF are you using? On what platform?
Windows

Duplicate of #648


No need to create additional spinner-elements.

There's check for label-span, so why not for the spinner as well?

This has been merged, thanks!


Added skeleton page for memory map, unclickable buttons, favicon

Added favicon, changed buttons to be unclickable when user is on that page, removed error-log page because errors will print directly on homepage, added skeleton html and javascript for memory map feature.

Here's what the favicon will look like.


Refine the retry logic in CPI

CPI has many retries. Are they neccessary?
Some retry timeout is too long (it is recommended by Azure API). Should we reduce the retry timeout?

If a certain VM size is not available in the Azure DC, the logic of the bosh-azure-cpi retries 10 times to create the VM with a retry sleep of 480 seconds  after each failure. Finally, this leads to a returning time of 1h 40 minutes. Is there a way to make the amount of retries configurable?
see also:
response.body: {"startTime":"2019-12-16T20:51:11.9137023+00:00","endTime":"2019-12-16T20:51:51.429896+00:00","status":"Failed","error":
{"code":"ZonalAllocationFailed","message":"Allocation failed. We do not have sufficient capacity for the requested VM size in this zone. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance"}
,"name":"246b7307-0e08-4e60-b2ff-d10c3d1e6af6"}
W, 2019-12-16T20:51:52.212925 #118218 #47386358501200 WARN – [req_id cpi-803040]: check_completion - http_put fails for an AzureAsynInternalError. Will retry after 480 seconds.
I, 2019-12-16T22:33:44.776764 #118218 INFO – [req_id cpi-803040]: Finished create_vm in 6160.84 seconds
Thanks & best, Claudia

We should distinguish between a given VM family not being available generally (which can be known up front) from a capacity issue preventing a nominally provisionable request from being satisfied at the moment (which isn’t).  For the former, we should detect that at request-time and abort without retry, whereas for the latter retries may be ultimately successful (especially in the repave case, where a VM has just been retired).
From: Claudia Baur<EMAIL_ADDRESS>Sent: Tuesday, December 17, 2019 7:16 AM
To: cloudfoundry/bosh-azure-cpi-release<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Subject: Re: [cloudfoundry/bosh-azure-cpi-release] Refine the retry logic in CPI (#443)
If a certain VM size is not available in the Azure DC, the logic of the bosh-azure-cpi retries 10 times to create the VM with a retry sleep of 480 seconds after each failure. Finally, this leads to a returning time of 1h 40 minutes. Is there a way to make the amount of retries configurable?
see also:
response.body: {"startTime":"2019-12-16T20:51:11.9137023+00:00","endTime":"2019-12-16T20:51:51.429896+00:00","status":"Failed","error":
{"code":"ZonalAllocationFailed","message":"Allocation failed. We do not have sufficient capacity for the requested VM size in this zone. Read more about improving likelihood of allocation success at http://aka.ms/allocation-guidance"}http://aka.ms/allocation-guidance"}
,"name":"246b7307-0e08-4e60-b2ff-d10c3d1e6af6"}
W, 2019-12-16T20:51:52.212925 #118218 #47386358501200 WARN – [req_id cpi-803040]: check_completion - http_put fails for an AzureAsynInternalError. Will retry after 480 seconds.
I, 2019-12-16T22:33:44.776764 #118218 INFO – [req_id cpi-803040]: Finished create_vm in 6160.84 seconds
Thanks & best, Claudia
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcloudfoundry%2Fbosh-azure-cpi-release%2Fissues%2F443%3Femail_source%3Dnotifications%26email_token%3DABT6UPLYIMGVQBWU5KYN7BDQZDUKTA5CNFSM4FONKV6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHCWQAY%23issuecomment-566585347&data=02|01|Jason.Stevens%40microsoft.com|785fa74168554a5d5ef808d7830402a7|72f988bf86f141af91ab2d7cd011db47|1|0|637121925563006174&sdata=UD8Gp%2BgKOWOebhC8t%2BXbKQwD0rXRkyscpU1YehiSvx0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABT6UPOTL4BNLSBJVYKAYWDQZDUKTANCNFSM4FONKV6A&data=02|01|Jason.Stevens%40microsoft.com|785fa74168554a5d5ef808d7830402a7|72f988bf86f141af91ab2d7cd011db47|1|0|637121925563016168&sdata=ZjPDip9cZ5q%2FDwRO8oS9RRO4xXSO724I1QHzUhDAU%2BM%3D&reserved=0.

No retry in case of an 'out of capacity' issue would also be fine with us. Currently, the code behaviour of bosh-azure-cpi blocks everything due to the ways too long timeout in that case. If it helps, I can also provide the logs.
Thanks, Claudia


FYI: Error message on exit ('Assertion failed') - did not affect session

FYI:
With the new version 'Node Inspector v0.10.0'
I got an error message after I ran to the end of a script.
'Assertion failed: ((err) == (0)), function Stop, file ../deps/debugger-agent/src/agent.cc, line 164.'
It did not seem to affect the debugging session.
Colin G

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/12015378-fyi-error-message-on-exit-assertion-failed-did-not-affect-session?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F195817&utm_medium=issues&utm_source=github).

—
Reply to this email directly or view it on GitHub
https://github.com/node-inspector/node-inspector/issues/623#issuecomment-96542374.

Thanks. I believe this is a problem in Node itself, see deps/debugger-agent/src/agent.cc#L164. Please upgrade to a newer Node version, e.g. 0.12.2 and open an issue in Node's tracker if the problem persist.


Having a .js file excludes a .jsx with the same name from the project

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.63.2 (Universal)
OS Version: MacOS 12.1 (21C52)

File structure:

jsconfig.json
{
  "compilerOptions": {
    "module": "commonjs",
    "allowSyntheticDefaultImports": false,
    "baseUrl": "./",
    "paths": {
      "@util/*": ["src/util/*"],
    },
  },
  "exclude": ["node_modules"],
  "include": ["src"]
}

When index.js and index.jsx in same folder, path alias are not working at index.jsx but work at index.js.

Looks like when there are two files with the same name but different extensions (.js vs .jsx) the js file is always preferred. Relevant part of TSServer log:
Info 138  [17:09:46.260] 	FileName: /Users/matb/projects/san/vscode-alias-path-not-working-demo/src/util/index.js ProjectRootPath: /Users/matb/projects/san/vscode-alias-path-not-working-demo
Info 138  [17:09:46.260] 		Projects: /Users/matb/projects/san/vscode-alias-path-not-working-demo/jsconfig.json
Info 138  [17:09:46.260] 	FileName: /Users/matb/projects/san/vscode-alias-path-not-working-demo/src/index.jsx ProjectRootPath: /Users/matb/projects/san/vscode-alias-path-not-working-demo
Info 138  [17:09:46.260] 		Projects: /dev/null/inferredProject1*

When we see two files with the same extension during includes processing, we assume one is the built output of the other, thus we shouldn't include them both (lest we cause duplicate definition errors or cause confusing find-all-references results). You'll need to specify both files in the files array, at which point things work as requested:
   "files": ["src/index.js", "src/index.jsx"]


feat: Integrate Camel readiness checks into Integration readiness condition

This PR probes the readiness checks exposed by the Camel runtime (Camel Quarkus / MicroProfile Health / SmallRye Health), to reconcile the Integration phase and readiness condition. It aims at surfacing the response from the Camel readiness checks, and exposing useful information, like error messages, so that the Integration status can serve as a single interface for higher level controllers.
As details from the readiness probe responses are not accessible from the Pod(s) status, the readiness probes are directly called by the operator (via the API server proxy), each time the Integration Pod(s) readiness condition change.
This follows up #2682, so that readiness / error status reconciliation now covers the entire lifecycle of an Integration.
TODO:

[ ]  Decouple liveness and readiness probes in the container trait: #1610
[ ] Create a dedicated health trait
[ ] e2e tests

Release Note
feat: Integrate Camel readiness checks into Integration readiness condition

The new health trait and the fix for #1610 is addressed via #2740.

I think it's ready. We'll be able to iterate as soon as we upgrade to Camel 3.13+, to leverage the new features developed by @davsclaus, add more test cases, and fix bugs 😇.


secure urls - poor man's ipfs

I've recently been working on this thing https://github.com/dominictarr/web-bootloader
Which uses an idea called a secure url. A secure url is just a url with a base64 encoded hash in it.
it just detects {base64}.sha256. This is similar to https://en.wikipedia.org/wiki/Subresource_Integrity except subresource integrity only applies to scripts and stylesheets. :cry:  so you can't use to to have secure XHR for example.
You could also do {alg}-{base64} like in SRI, or enforce that the hash is at the end of the url (right before the ?)
content-addressed data means you have caching that is easy to reason about (finally). If you already have an object with that hash, just don't do the request.
The best part is that it's dead easy to implement.
you can implement a content addressable store in 100 lines in any language.
This makes it very good for bootstrapping other protocols, etc.
what do you think about having first class support for secure urls in beaker?

I agree. This is one of the principle ideas for Beaker's new site protocols. It has a lot of beneficial security and caching benefits.
The dat protocol supports this in current master. Its URL scheme is dat://{name_or_key}/{path...}, where:

name may be a DNS TXT entry that points to a dat-URL that contains a key†
key may be a hex-encoded public key or sha256 hash

Dat's can be either "live" or "static." If they are static, the author "finalizes" the archive at some point, and the key is a hash of that final state. If they are live, the dats remain mutable.
Live-dats may be easier to work with, but it'd also be possible to create a flow around deploying static dats, where you update the DNS entry with each new deployment. (Zeit Now does this, but they aren't able to implement the cryptographic guarantees in the client like we can.)
We can look at additional protocols with secure URLs. Do you have any in mind? I'm just wrapping up Dat support, now.
† This will need DNSSEC to defeat MITM injections, which isnt implemented yet

Oh, I just meant http. It doesn't really matter which protocol, if you know the hash you want. you could even provide a list of possible urls to try, as long as the hash is specified.
If it's mutable, but say, signed with a known key (key is in url) that is still a good security feature, but that is more complex and somewhat less secure. Of course, I'm all for that, but just proposing that we also have access to the simplest possible thing.

Ah, for HTTP we'd need to modify the URL scheme somehow, so that the browser knows what to check against. We could standardize some query parameters, for instance:
http://foo.com/resource.js?hash={hash}

Or, perhaps more appropriately, put it in the hash-segment:
http://foo.com/resource.js#sha256-{hash}

Another solution might be to put the hash into the filename. It's easy to detect the hash, and you could be very loose about it.
http://foo.com/sha256-{hash}
http://foo.com/sha256-{hash}.zip
http://foo.com/mystuff.sha256-{hash}.zip

Maybe have sha256 be default, so the tag is optional
http://foo.com/{hash}

We've talked about have dat archive-files that can be hosted over HTTP. This scheme could be useful for that. cc @mafintosh

sorry, that was what I was trying to suggest initiall.
For sbot i'm serving blobs over https:{host}/blobs/get/&{base64(hash)}.{alg}
I think it's definitely wise to specify a hash. since it's so simple, I don't think it's too much to support multiple syntaxes. {alg}-{base64(hash)} is the SRI syntax, {base64(hash)}.{alg}. camlistore uses {alg}-{hex(hash)}.
stronglink uses /{alg}/{hex(hash)} (and the hash may be truncated)
There are some advantages to base58, but it's much harder to find a base58 implementation.
also, those advantages (easy to copy/paste) arn't so important these days.
(we don't type in a url after seeing an ad on tv, instead links are shared on social media, etc)

@btrask

@dominictarr thanks for pinging me!
I think the end-goal should be content addressing, where hashes can be loaded from arbitrary resolvers. This secure URL proposal and SRI are both good intermediate approaches.
Once your browser has a way of verifying hashes embedded in URLs, there's very little reason to actually use the specified source instead of some other resolver. (One consideration being https://github.com/w3c/webappsec-subresource-integrity/issues/22.)
I think it's worth being very careful about this design, since it's carving out a universal namespace across every web server on the net (similar to /.well-known and ?_escaped_fragment_). Unfortunately that tends to make these proposals very ugly.
My suggestions are:

Keep resolvers in mind as a distinct concept and eventual goal
Choose a format that makes the embedded content address distinct (ideally as its own URI)
Be careful about possible collisions (per above)
Aside from that, the primary design/aesthetic constraint should be making it as appealing as possible to engineers of Chrome and Firefox

If you can come up with a decent proposal, I'd be happy to support it in StrongLink. Current raw file URL example, which doesn't follow my suggestions above :). Normal page URL which is much better but obviously highly vulnerable to namespace problems with the name q).
I suspect a query parameter is the way to go. Something like http://example.com/file?_hash_=[hash-uri-of-some-sort].
As for the hash URI itself, I'd suggest supporting all of them until a winner emerges. This JS code might be a helpful starting point (no npm module yet, sorry!).

@dominictarr fwiw, there was an earlier Sub-Resource Integrity draft that provided the integrity attribute on pretty much any element with an href or  src: https://www.w3.org/TR/2014/WD-SRI-20140318/
It also used RFC 6920 URI's for the hashes.
Mostly, that seems to have all been taken out due to how it might effect user experience during navigation--i.e. what happens when I click a link with an invalid integrity match.
There's some fresh consideration of putting integrity on <a> if it has download, but again, navigation UX is the "blocker": https://github.com/w3c/webappsec-subresource-integrity/issues/68

I think the problem here is that it's still the link that identifies the resource, not the hash. I think with subresource integrity the server doesn't actually know what hash you were looking for (is this correct?) hence I think it should just be a url convention.


Bug in parsing?

I have the following code:
std::string filename = "";

    std::fstream fs(filename, std::ios::in);
    if (!fs) {
        std::cerr << "Could not open file \'" << filename << "'\n";
        return EXIT_FAILURE;
    }

    // Setting precision of the times to fixed points and 4 decimal places
    std::cout << std::fixed << std::setprecision(4);

    Mata::Parser::Parsed parsed;
    Nfa aut;
    Mata::StringToSymbolMap stsm;
    const std::string nfa_str = "NFA";
    try {
        parsed = Mata::Parser::parse_mf(fs, true);
        fs.close();

        if (parsed.size() != 1) {
            throw std::runtime_error(
                "The number of sections in the input file is not 1\n");
        }
        if (parsed[0].type.compare(0, nfa_str.length(), nfa_str) != 0) {
            throw std::runtime_error("The type of input automaton is not NFA\n");
        }

        std::vector<Mata::IntermediateAut> inter_auts = Mata::IntermediateAut::parse_from_mf(parsed);
        Mata::Mintermization mintermization;
        auto mintermized = mintermization.mintermize(inter_auts);
        assert(mintermized.size() == 1);
        aut = Mata::Nfa::Builder::construct(mintermized[0], &stsm);
    }
    catch (const std::exception& ex) {
        fs.close();
        std::cerr << "libMATA error: " << ex.what() << "\n";
        return EXIT_FAILURE;
    }

where filename contains a path to the NFA tests-performace/automata/b-param-medium-hard/aut0.mata. The code fails on the assertion (false && "Unknown type of node"), function postfix_to_graph, file inter-aut.cc, line 295.

The Parser Problem
The problem is caused by an incorrect format in the input NFA-bits automaton, which conatins a transition in the form q0 \true (q1 | q2). This transition format is not currently supported. Each transition must have exactly one target state, as the parser expects the last symbol on the line to be a target state.
https://github.com/VeriFIT/mata/blob/84ecd6a60caf3bb112af04f1e0cb5119a34caa1e/src/inter-aut.cc#L455-L458
Therefore, instead of a single transition q0 \true (q1 | q2), we need to use two separate transitions: q0 \true q1 and q0 \true q2.
It's no longer an issue
Automata with this unsupported format were removed in commit 3df7ff1, so this issue no longer occurs. The following automata with invalid formats were removed: atm0, atm1, atm2, atm3
Extending the NFA-bits Format for Multiple Targets?
Although this issue was caused by a violation of the current NFA-bits format, we may want to consider extending this format in the future to support transitions with target states specified by a formula.


emulation: training runs out of memory and crashes after epochs

The ML training for the conservative ML model (and maybe others) keeps crashing after running for 8 hours but before saving the ML model! See this: https://wandb.ai/ai2cm/microphysics-emulation/runs/7rgrn7jp?workspace=user-nbren12
The memory usage spikes at the end and eventually exceeds the k8s imposed limits.

See the memory usage profile at the end of these logs. This suggests the score_model functions incur extra memory.

This is likely resolved by #1548 updates to the Argo memory limits and separates the scoring to ease retries.  Runs successfully with an RNN which has quite memory hungry scoring.


Feature/add database versioning GDEV-368

Title for squash and merge:
Add database Versioning GDEV-368

Description for squash and merge:
Enabled Database Versioning, created first migration script

Decided against using alembic inside the db_init function for tests.
Feature to test alembic will be created later

Codecov Report

Merging #3 (ba8b09d) into dev (a831305) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev       #3   +/-   ##
=======================================
  Coverage   89.71%   89.71%
=======================================
  Files          10       10
  Lines         107      107
=======================================
  Hits           96       96
  Misses         11       11

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 a831305...ba8b09d. Read the comment docs.


Add coverage to tests

We don’t quite have anything that tells us how much of the code we test (such as, in the above subtask, how many of the scheduler options we exercise). We should, in both github tests and the userland ones, with proper reporting to the server.

Perhaps use codecov.io

Moving to 1.0.0


Persian translation

Hi :)
I Think I Fixed It Can You Check It For Sure?

There is still a bit more work that needs to be done.
I see the images are not loading correctly. This might be because the relative urls for images are wrong. You can check other translations for getting correct relative urls for images.
https://github.com/ThirdScript/first-contributions/blob/00ab88538907167c63c7a9883dc05f213940bfa6/translations/README.fa.md
https://github.com/ThirdScript/first-contributions/blob/00ab88538907167c63c7a9883dc05f213940bfa6/translations/README.fa.en.md
You can check how translations are rendering in links above.

Thank you for these translations @ThirdScript

You're Welcome
I'm So Glad I Did Something For My First Github Contribution
Thanks, A lot For Making This Repository For Newbies Like Me :D


logpush job for firewall_event is not working.

Terraform version
tf_0.12.26 -v
Terraform v0.12.26
+ provider.aws v3.26.0
+ provider.cloudflare v2.17.0

Your version of Terraform is out of date! The latest version
is 0.14.6. You can update by downloading from https://www.terraform.io/downloads.html

Affected resource(s)
cloudflare_logpush_job

Terraform configuration files
resource "cloudflare_logpush_ownership_challenge" "ownership_firewall_challenge" {
  count = var.enable_global_config ? 1 : 0

  zone_id          = data.cloudflare_zones.default.zones[0].id
  destination_conf = "s3://<redacted>-${var.environment}-os-cdn-firewall-logs?region=${var.region}"
}

data "aws_s3_bucket_object" "challenge_firewall_file" {
  count = var.enable_global_config ? 1 : 0

  bucket = "<redacted>-${var.environment}-os-cdn-firewall-logs"
  key    = cloudflare_logpush_ownership_challenge.ownership_firewall_challenge[0].ownership_challenge_filename
}

resource "cloudflare_logpush_job" "firewall_to_s3" {
  count = var.enable_global_config ? 1 : 0

  enabled             = var.enable_cloudflare_firewall_logpush_job
  zone_id             = data.cloudflare_zones.default.zones[0].id
  name                = "os-firewall-logs-to-s3"
  logpull_options     = var.cloudflare_firewall_logpush_options
  destination_conf    = "s3://<redacted>-${var.environment}-os-cdn-firewall-logs?region=${var.region}"
  ownership_challenge = data.aws_s3_bucket_object.challenge_firewall_file[0].body
  dataset             = "firewall_events"
}

Debug output

Panic output

Expected behavior
This should create a working logpush job for firewall event. A job that pushes event to the bucket.
Actual behavior
This actually create the logpush job, everything seems ok, but no event are pushed to S3.
This behaviour only happen when the dataset is set to firewall_event.
Steps to reproduce

terraform apply

Important factoids
I have open a ticket with cloudflare support (#2080952) about this.
Using a similar snippet I successfully created a logpush job for http_requests, which works perfectly fine.
According to the support the firewall_event dataset is in beta.
From Terraform point of view, when the dataset is firewall_event, everything is ok, but nothing is sent to S3.
When we look at the resource, it looks fine and similar to logpush job with dataset configured to http_requests:
# cloudflare_logpush_job.firewall_to_s3[0]:
resource "cloudflare_logpush_job" "firewall_to_s3" {
    dataset             = "firewall_events"
    destination_conf    = "s3://<redacted>-dev-os-cdn-firewall-logs?region=eu-west-1"
    enabled             = true
    id                  = "26606"
    logpull_options     = "fields=RayID,ClientIP,ClientRequestHost,ClientRequestPath,ClientRequestUserAgent&timestamps=rfc3339"
    name                = "os-firewall-logs-to-s3"
    ownership_challenge = "<redacted>"
    zone_id             = "<redacted>"
}

But when we query cloudflare API, we can see a difference between the 2 dataset http_requests and firewall_event:
{
      "id": 26559,
      "dataset": "http_requests",
      "logstream": true,
      "enabled": true,
      "name": "os-http-logs-to-s3",
      "logpull_options": "fields=RayID,ClientIP,ClientRequestHost,ClientRequestPath,ClientRequestUserAgent,EdgeStartTimestamp,WAFAction,WAFRuleID&timestamps=rfc3339",
      "destination_conf": "s3://<redacted>-os-cdn-http-logs?region=eu-west-1",
      "last_complete": "2021-02-09T17:17:10Z",
      "last_error": null,
      "error_message": null
    }

{
    "id": 26606,
    "dataset": "firewall_events",
    "enabled": true,
    "name": "os-firewall-logs-to-s3",
    "logpull_options": "fields=RayID,ClientIP,ClientRequestHost,ClientRequestPath,ClientRequestUserAgent&timestamps=rfc3339",
    "destination_conf": "s3://<redacted>-os-cdn-firewall-logs?region=eu-west-1",
    "last_complete": null,
    "last_error": null,
    "error_message": null
}

The logstream field is not set for the firewall_event, I guess the issue is more on the side of the cloudflare SDK but I thought it would be worth to open issue about since the firewall_event seems to be supported by the provider and it's mentionned in the documentation.
References

Community note

Please vote on this issue by adding a 👍 reaction
to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull
request, please leave a comment

I guess the issue is more on the side of the cloudflare SDK

I'm not sure I follow. The response is generated by the Cloudflare API and the SDK only handles parsing it so the SDK shouldn't be at fault here if it is working for another similar request. Can you please provide the full TF_LOG=DEBUG output? I suspect the API isn't exposing this and it's an internal issue to be addressed.

closing due to lack of information follow up. if more information is available, we can revisit.


Windows Terminal workaround by using fifos instead of console device

aims to workaround  #36

There is actually a small bug fixed here https://github.com/imachug/win-sudo/pull/49/commits/c6ac43413c99a0becb0593795b9afd30ac23619a#diff-1fa39d56a58df8d32ee980b4cf0927bc11ac1dd009d7a333080d0844476d4098R103
it does assume fifo mode for all fds at once (no clue why you would want otherwise). The grep line might not be too smart. Maybe there is a better way to detect a windows console device.

I'm honestly no longer really involved with the project, as I don't use Windows often anymore, so I can't really test msys2 at the moment. If you did that for me, I will gladly merge the PR.

checked that it works for me eg. on standard bash for windows and with the legacy and new windows console as well as mintty. Only mintty actually manages to share the tty with the elevated backend for some reason.

Thank you for your PR!


Flaky actions

Given that page (snippet):

and given that test:
test("ai test", async ({ freeSlotCountPage }) => {
  const options = {
    debug: true, // If true, debugging information is returned from the ai() call.
  };

  await ai(
    "Click in table on plus icon button of lowest entry",
    { page: freeSlotCountPage, test },
    options
  );

  await ai(
    "Click in table on plus icon button of displayed location",
    { page: freeSlotCountPage, test },
    options
  );

  await freeSlotCountPage.waitForTimeout(5000);
});

Apart from expecting the first action to click on the plus icon of the bottom entry ('24.12.2023'), unfortunately, the next action is rarely successful.

Log:
 ws send: {"type":"task-start","packageVersion":"v0.1.5","taskId":"018c808d-508a-7a10-99ee-40370c259251","task":"Click in table on plus icon button of entry with next date","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"conte
< ws recv: {"type":"command-request","taskId":"018c808d-508a-7a10-99ee-40370c259251","index":0,"name":"clickElement","arguments":{"id":"616"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c808d-508a-7a10-99ee-40370c259251","index":0,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c808d-508a-7a10-99ee-40370c259251","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}
> ws send: {"type":"task-start","packageVersion":"v0.1.5","taskId":"018c808d-625a-7c54-b445-69984f0f3c5c","task":"click in grid on plus icon button of location alfa","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"contentLangua
< ws recv: {"type":"command-request","taskId":"018c808d-625a-7c54-b445-69984f0f3c5c","index":1,"name":"clickElement","arguments":{"id":"748"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c808d-625a-7c54-b445-69984f0f3c5c","index":1,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c808d-625a-7c54-b445-69984f0f3c5c","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}

Log:
"type":"task-start","packageVersion":"v0.1.5","taskId":"018c808b-2d7b-7f29-a6b7-0a7c464c7c9e","task":"Click in table on plus icon button of entry with last date","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"conte
< ws recv: {"type":"command-request","taskId":"018c808b-2d7b-7f29-a6b7-0a7c464c7c9e","index":0,"name":"clickElement","arguments":{"id":"879"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c808b-2d7b-7f29-a6b7-0a7c464c7c9e","index":0,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c808b-2d7b-7f29-a6b7-0a7c464c7c9e","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}
> ws send: {"type":"task-start","packageVersion":"v0.1.5","taskId":"018c808b-3f87-75fe-b284-ffa6277adda4","task":"click in grid on plus icon button of location alfa","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"contentLangua
< ws recv: {"type":"command-request","taskId":"018c808b-3f87-75fe-b284-ffa6277adda4","index":1,"name":"clickElement","arguments":{"id":"895"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c808b-3f87-75fe-b284-ffa6277adda4","index":1,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c808b-3f87-75fe-b284-ffa6277adda4","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}

Even though it appears that nothing is clicked in the second action, the test is marked as 'passed'.
Unfortunately, I am not receiving any debug output anywhere, even though I have set debug to true in the options.
Edit: Here another run - both commands doing the expected:
...
  await ai(
    "Click in table on plus icon button of entry with next date",
    { page: freeSlotCountPage, test },
    options
  );

  await ai(
    "click in grid on plus icon button of location alfa",
    { page: freeSlotCountPage, test },
    options
  );
...

> ws send: {"type":"task-start","packageVersion":"v0.1.5","taskId":"018c8093-d19b-7f54-afe9-b0b4ccafc0d1","task":"Click in table on plus icon button of entry with next date","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"conte
< ws recv: {"type":"command-request","taskId":"018c8093-d19b-7f54-afe9-b0b4ccafc0d1","index":0,"name":"clickElement","arguments":{"id":"621"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c8093-d19b-7f54-afe9-b0b4ccafc0d1","index":0,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c8093-d19b-7f54-afe9-b0b4ccafc0d1","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}
> ws send: {"type":"task-start","packageVersion":"v0.1.5","taskId":"018c8093-e530-7a74-af74-1323bf018403","task":"click in grid on plus icon button of location alfa","snapshot":{"dom":"{\"documents\":[{\"documentURL\":0,\"title\":1,\"baseURL\":0,\"contentLangua
< ws recv: {"type":"command-request","taskId":"018c8093-e530-7a74-af74-1323bf018403","index":1,"name":"clickElement","arguments":{"id":"638"}}
> ws send: {"type":"command-response","packageVersion":"v0.1.5","taskId":"018c8093-e530-7a74-af74-1323bf018403","index":1,"result":"null"}
< ws recv: {"type":"task-complete","taskId":"018c8093-e530-7a74-af74-1323bf018403","model":"gpt-3.5-turbo","wasSuccessful":true,"result":{"actions":["Click"]}}

Ok. For my date issue, this performs much better and reliable:
"Click in table on plus icon button of entry with last date"

Hey @SmartALB - thanks for opening an issue here.
You can think of the AI here as acting like a skilled manual tester. Consequentlly, a good prompt to ZeroStep is an instruction that you could give to a handful of skilled manual testers, and each of them would take the same action. A few of your prompts don't meet that bar, IMO:

Click in table on plus icon button of lowest entry

Since this is a list of dates, I am unsure of what "lowest entry" means. Does it mean the earliest date? (That's what the AI clicks on). Does it mean the last date in the table? (I assume that's what you expected the AI to click on). I don't think you'd have consensus if you asked a few skilled testers what they were supposed to do with this prompt.

Click in table on plus icon button of displayed location

The AI is likely confused by what "displayed location" means. It seems to infer some specific location on the page. Can you refer to that explicitly like you did in your last example, "click in grid on plus icon button of location alfa". A prompt like "In the table, click the plus icon for the location that's displayed beneath the first date" might yield better results, since it would be clearer to a manual tester what exact action you want performed.

Click in table on plus icon button of entry with next date

The AI doesn't have any context on what previous actions were performed, so referring to the "next date" is likely what's confusing it. I would try to be more explicit here.

click in grid on plus icon button of location alfa

I would expect the AI to know what to do for this one, but again I think the phrasing here could be improved. "In the grid, click on the plus icon for the location 'Alfa'" should yield better results.
Please try incorporating these improvements into your prompts and let us know how it goes!


Load MTD files

MET produces 3 main types of files: STAT, MODE, and MTD. Write code to load MTD files.

Completed the code for MTD in feature_23_load_MTD
Merged the code into develop
Included Issue 20, which added new fields


Problem with bidirectional "hasOne" relationship

Note: If your question is regarding the AWS Amplify Console service, please log it in the
AWS Amplify Console repository

Which Category is your question related to?
AppSync graphql
Amplify CLI Version
7.6.23
What AWS Services are you utilizing?
AppSync, Dynamodb
I have 2 models:
`
type ParkingPlace
@model
@auth(
rules: [
{ allow: public, provider: apiKey }
{ allow: private, operations: [read] }
{ allow: groups, provider: userPools, groups: ["Admin"] }
]
) {
id: ID!
isAvailable: Boolean!
ticket: Ticket @hasOne(fields: ["ticketId"])
ticketId: ID
}
type Ticket
@model
@auth(
rules: [
{ allow: public, provider: apiKey }
{ allow: owner, ownerField: "owner", operations: [read] }
{ allow: groups, provider: userPools, groups: ["Admin"] }
]
) {
id: ID!
parkingPlace: ParkingPlace @belongsTo(fields: ["parkingPlaceId"])
parkingPlaceId: ID
owner: String!
expiresAt: AWSDateTime
}
`
After creating a Ticket with given 'parkingPlaceId'

The 'ticketId' field of 'ParkingPlace'  does not get filled
'ticket' field is always null when I try to query 'listParkingPlaces'

listParkingPlaces(filter: $filter, limit: $limit, nextToken: $nextToken) {       items {         id         ticketId         ticket {           id           expiresAt           owner         }       }       nextToken     }

This is still an issue. Any update on this?
For the below two models, creating a profile for a user does not form the correct relationship. When I query for the user and drill down into the response, profile is null
This works if I change the hasOne to hasMany But that is just incorrect relationship declaration
type FireProfile @model {
id: ID!
targetYear: Int!
fireType: String!
targetYearlyExpense: String
targetPortfolioValue: Float
user: User @belongsTo
}
type User @model {
id: ID!
firstName: String!
lastName: String
accounts: [Account] @hasMany
profile: FireProfile @hasOne
dateOfBirth: AWSDate!
createdAt: AWSDateTime!
updatedAt: AWSDateTime!
}

same here...hasMany works not hasOne with belongsTo.
 Everytime I push my edited schema I spend money!

Hi @caesarisme, We apologize for the delay in our response. After verifying with the latest CLI version, we were able to observe the expected results for the hasone relationship. We kindly request you to upgrade to the latest CLI version and try again.
type Blog @model {
  id: ID!
  name: String!
  posts: Post @hasOne
}

type Post @model {
  id: ID! @primaryKey
  title: String!
  blog: Blog @belongsTo
}

Hi 👋, We are closing this issue as we have not received any response from you. However, if you are still facing the same issue and require our assistance, please don't hesitate to leave a comment and provide us with the information our team had previously asked for. This way, we can reopen the issue and provide you with better assistance.
Thank you!


LinkedResource IEnumerable

If LinkedResource type is IEnumerable then ResourceConfigurationBuilder.WithLinkedResource fails to get linkedType. If I set it to IList then it works.
Error pattern:
public class Post{
public in Id {get; set;}
}
public class Author{
public int Id {get; set;}
public IEnumerable Posts {get; set;}
}
configBuilder
.Resource<Author, AuthorController>()
.WithIdSelector(p => p.Id)
.WithLinkedResource (p => p.Posts);

This is working as designed.
Using IEnumerable is like saying:

I don't really care when you work out what's in the list, just do it eventually.

Now that's cool if you're building a query that's gone to run on a database or you have a big collection in memory that you're working on. However, if data is going outside of a context boundary (I'll come back to that, stay with me!) then you should say "The Data is X".
In this case, you're saying that the Author API model has "a bunch of posts, I don't care what they are until later" but the API model must care right now because it's the last time the data is touched by the API. After that, it's out in the world. That's the context boundary. IEnumerable delays the execution of the building of list of entities but that doesn't make sense for an API because client can't add Where clauses onto it. That's why we enforce IList, we are telling the programmer (you in this case) that IEnumerable doesn't cut it and they need to be dealing with lists, be they arrays or linked lists.
That said, there should be a better error message to explain how to fix it.


feat(workflow): improve workflow log readability for humans

:mega: The PR is initially to provide a basis to discuss the workflow flow output format to make it easier for people to make it easier to see what is going on in a workflow. The initial Rust code was only done to show the desired output (and to validate it). Someone with more Rust experience should take over and provide the required tests etc.
Proposed changes

Improve workflow layout and styling to make it easier and quicker for humans to follow complex workflows. The following changes were implemented:

Display nested workflow states visually
Display state contents in input/output format
Add log header section to display workflow trigger info
Remove duplicated information from each state
Include user friendly hints for exit code and empty stdout/stderr

Types of changes

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
[ ] Documentation Update (if none of the other choices apply)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have signed the CLA (in all commits with git commit -s)
[x] I ran cargo fmt as mentioned in CODING_GUIDELINES
[x] I used cargo clippy as mentioned in CODING_GUIDELINES
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

Attached is a full example log file taken from a custom workflow (trying to mimic a device profile operation). example.log is the full log, but below is just a snippet.
==> /var/log/tedge/agent/workflow-device_profile-robot-123.log <==

==================================================================
Triggered device_profile workflow
==================================================================

topic:     te/device/main///cmd/device_profile/robot-123
operation: device_profile
cmd_id:    robot-123
time:      2024-05-06T12:19:40.883043984Z

==================================================================

----------------------[ device_profile @ init | time=2024-05-06T12:19:40.884932495Z ]----------------------

State:    {"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false},{"operation":"config_update","payload":{"remoteUrl":"http://<IP_ADDRESS>:8001/c8y/inventory/binaries/35861751","type":"tedge-configuration-plugin"},"skip":true}],"status":"init"}

Action:   move to scheduled state

----------------------[ device_profile @ scheduled | time=2024-05-06T12:19:40.887326091Z ]----------------------

State:    {"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false},{"operation":"config_update","payload":{"remoteUrl":"http://<IP_ADDRESS>:8001/c8y/inventory/binaries/35861751","type":"tedge-configuration-plugin"},"skip":true}],"status":"scheduled"}

Action:   /etc/tedge/operations/device_profile.sh scheduled '{"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false},{"operation":"config_update","payload":{"remoteUrl":"http://<IP_ADDRESS>:8001/c8y/inventory/binaries/35861751","type":"tedge-configuration-plugin"},"skip":true}],"status":"scheduled"}'

Exit status: 0 (OK)

stderr <<EOF
Filtering/sorting device profile artifacts
EOF

stdout <<EOF
:::begin-tedge:::
{"currentIndex":-1,"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false}]}
:::end-tedge:::
EOF

----------------------[ device_profile @ next_artifact | time=2024-05-06T12:19:40.913705569Z ]----------------------

State:    {"currentIndex":-1,"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false}],"status":"next_artifact"}

Action:   /etc/tedge/operations/device_profile.sh next_artifact '{"currentIndex":-1,"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false}],"status":"next_artifact"}'

Exit status: 0 (OK)

stderr <<EOF
Checking next artifact
Found next artifiact. status=firmware_update
EOF

stdout <<EOF
:::begin-tedge:::
{"status":"firmware_update","currentIndex":0,"current":{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false}}
:::end-tedge:::
EOF

----------------------[ device_profile @ firmware_update | time=2024-05-06T12:19:40.985850631Z ]----------------------

State:    {"current":{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},"currentIndex":0,"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false}],"status":"firmware_update"}

Action:   execute firmware_update as sub-operation

----------------------[ device_profile @ waiting_for_firmware_update | time=2024-05-06T12:19:40.98839402Z ]----------------------

State:    {"current":{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},"currentIndex":0,"profile":[{"operation":"firmware_update","payload":{"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","version":"20240430.1139"},"skip":false},{"operation":"software_update","payload":{"updateList":[{"modules":[{"name":"c8y-command-plugin","url":"","version":"latest"},{"name":"jq","url":"","version":"latest"}],"type":"apt"}]},"skip":false}],"status":"waiting_for_firmware_update"}

Action:   await sub-operation completion

----------------------[ device_profile > firmware_update @ init | time=2024-05-06T12:19:41.002872349Z ]----------------------

State:    {"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","status":"init","version":"20240430.1139"}

Action:   move to scheduled state

----------------------[ device_profile > firmware_update @ scheduled | time=2024-05-06T12:19:41.004943235Z ]----------------------

State:    {"name":"core-image-tedge-rauc","remoteUrl":"https://t9679.latest.stage.c8y.io/inventory/binaries/82029","status":"scheduled","version":"20240430.1139"}

Action:   /usr/bin/sleep 1

Exit status: 0 (OK)

stderr (EMPTY)
stdout (EMPTY)


Fix: solve the problem that micropython could not be used

Solved the problem that micropython could not be used normally in XIAO RP2350

Ping @ryanplusplus and @mcauser in case they have any thoughts...

Doesn't the Xiao RP2350 work with Micropython? The Seeed Wiki seems to indicate that it does:
https://wiki.seeedstudio.com/getting-started-xiao-rp2350/
Can you provide some more information about why this is necessary and how you determined that it was necessary?
I checked the Xiao RP2040 and it is also using a SPI clock divisor of 2 with what I assume is the same flash chip (the schematic leaves it unlabeled).  If there's a difference, I would guess it's related to the layout. However, I'm not sure why a problem would only present itself for MicroPython and not when using the C/C++ SDK directly.

I just noticed this warning in the Wiki:

MicroPython Firmware Issue
As of November 10, 2024, the stable MicroPython firmware version 1.24.0 available for download at MicroPython.org for RPI_PICO2 is currently incompatible with certain devices due to variations in the flash chip.
The Seeed Team is actively working to resolve this issue in collaboration with the official MicroPython maintainers. In the meantime, you can use a preview version of the MicroPython firmware as a temporary solution: RP2350 MicroPython Firmware Preview

Are you with/for Seeed to solve this issue?

If there's a difference, I would guess it's related to the layout.

RP2040 also has a default clock speed of 125MHz whereas RP2350 has a default clock speed of 150MHz; so I guess if something was already operating at the margins of tolerance it'd be much more likely to not work at the higher frequencies of RP2350?

I just noticed this warning in the Wiki:

MicroPython Firmware Issue
As of November 10, 2024, the stable MicroPython firmware version 1.24.0 available for download at MicroPython.org for RPI_PICO2 is currently incompatible with certain devices due to variations in the flash chip.
The Seeed Team is actively working to resolve this issue in collaboration with the official MicroPython maintainers. In the meantime, you can use a preview version of the MicroPython firmware as a temporary solution: RP2350 MicroPython Firmware Preview

Are you with/for Seeed to solve this issue?

emmm, actually, I work at Seeed

emmm, actually, I work at Seeed

Aha! In that case I'll approve this PR :slightly_smiling_face:

If there's a difference, I would guess it's related to the layout.

RP2040 also has a default clock speed of 125MHz whereas RP2350 has a default clock speed of 150MHz; so I guess if something was already operating at the margins of tolerance it'd be much more likely to not work at the higher frequencies of RP2350?

Yes, the current situation seems to be that the SPI clock frequency is too high to be used properly.

If there's a difference, I would guess it's related to the layout.

RP2040 also has a default clock speed of 125MHz whereas RP2350 has a default clock speed of 150MHz; so I guess if something was already operating at the margins of tolerance it'd be much more likely to not work at the higher frequencies of RP2350?

Yes, the current situation seems to be that the SPI clock frequency is too high to be used properly.

Do we understand why it works properly for the C/C++ SDK? Reducing the SPI clock by half will have a large performance impact.

Just a random guess, but perhaps C applications are "lighter weight" than MicroPython applications, and are therefore able to make better use of the XIP cache? (of course I could easily be 100% wrong)

If there's a difference, I would guess it's related to the layout.

RP2040 also has a default clock speed of 125MHz whereas RP2350 has a default clock speed of 150MHz; so I guess if something was already operating at the margins of tolerance it'd be much more likely to not work at the higher frequencies of RP2350?

Yes, the current situation seems to be that the SPI clock frequency is too high to be used properly.

Do we understand why it works properly for the C/C++ SDK? Reducing the SPI clock by half will have a large performance impact.

It seems that the SPI frequency of the firmware compiled by C/C++ SDK is always 50 MHz, regardless of whether PICO_FLASH_SPI_CLKDIV is modified or not.
I'm not sure how 50 Mhz is configured.

It seems that the SPI frequency of the firmware compiled by C/C++ SDK is always 50 MHz, regardless of whether PICO_FLASH_SPI_CLKDIV is modified or not.
I'm not sure how 50 Mhz is configured.

I think this is related to #1903 - on RP2350 the boot_stage2 isn't run by default when using the C/C++ SDK, so it just uses the flash mode setup by the bootrom. The PICO_FLASH_SPI_CLKDIV and similar defines are only used in boot_stage2, so will have no effect on RP2350 unless using a boot_stage2

I think this is related to #1903 - on RP2350 the boot_stage2 isn't run by default when using the C/C++ SDK, so it just uses the flash mode setup by the bootrom. The PICO_FLASH_SPI_CLKDIV and similar defines are only used in boot_stage2, so will have no effect on RP2350 unless using a boot_stage2

Oh interesting! IMHO this definitely deserves to be better documented, as currently the only mention of this in https://datasheets.raspberrypi.com/pico/raspberry-pi-pico-c-sdk.pdf is "A boot_stage2 is not needed on RP2350, but one can be included via the define PICO_EMBED_XIP_SETUP=1." which is buried in the SDK 2.0.0 release notes all the way down on page 649! (And PICO_FLASH_SPI_CLKDIV doesn't have any documentation in the SDK PDF either.)
FYI @nathan-contino

I've been doing some investigating into this problem for a different board that has the same problem (Waveshare RP2350 1.28 in Round LCD module). It's curious because the Waveshare distributed UF2 is exactly the same as the Seeed distributed one. That seemed to have been compiled back in early August, using the PR before RP2350 support was finally merged. I can reproduce a successful build myself this way, and another guy has done the same for this XIAO board.
An indeed, building MicroPython using current releases does not work on either board. Pico SDK 2.0 was being used back in August through to a few days ago. I tested yesterday with SDK 2.1, no joy. I applied this SDK PR and recompiled, still no joy. Another guy tried this on the XIAO with the same sad results.
Are we sure that this PR, while building correctly and passing the Pico SDK CI tests, actually makes the XIAO board boot up into MicroPython correctly?
Disclaimer: I realize I'm that I'm comparing two completely different RP2350 modules. It's possible that they both worked perfectly in August, and are now failing with the released MicroPython for completely different reasons. While I don't have a XIAO to test with myself, I've asked someone else to test this, with the results noted above.
While there may be a good reason for changing the SPI clock speed per this PR, I think there may be more fixes needed before MicroPython can run on the XIAO (and perhaps Waveshare) modules.
Since the focus here seems to be on the flash memory, I'd like to compare the part numbers, but Seeed hasn't released which chip they're using (and it's underneath a metal shield so not easily discerned by inspection). Knowing the part number might help track down this issue, @Lesords

@thestumbler just build micropython with both PRs picked from @Lesords and it works on XIAO RP2350, so indeed SPI clock needs to be lower for flash chip Seeed chose

@lurch any chance this PR can be merged?

Oh. There's a second PR? I missed that

Where is this second PR? I only see one under @Lesords user, that's here on the Pico SDK, and none on the MicroPython repo. Am I missing something obvious?

Second PR is just a board definition, standard Pico 2 should work. But make sure that you select target, iirc by default rp2 port builds for rp2040

So, I'm still confused about the SPI clock speed. Back in August, when one could build MicroPython successfully for the XIAO, using the stock SDK 2.0, wasn't the SPI running at the same "fast" speed that now doesn't work and needs to be halved?

I already have that PR, it's only one file that cigs the SPI frequency in half. Where is the second PR? And yes, I am correctly selecting the 2350 board. Good point!

Where is this second PR? I only see one under @Lesords user, that's here on the Pico SDK, and none on the MicroPython repo. Am I missing something obvious?

Here: https://github.com/micropython/micropython/pull/16299

So, I'm still confused about the SPI clock speed. Back in August, when one could build MicroPython successfully for the XIAO, using the stock SDK 2.0, wasn't the SPI running at the same "fast" speed that now doesn't work and needs to be halved?

No, the SPI frequency of the firmware compiled at that time was always 50Mhz

@lurch any chance this PR can be merged?

a) I don't have merge permissions on this repo
b) most of the Raspberry Pi engineers (including myself) are currently on Xmas and New Year holidays :christmas_tree: :confetti_ball:

@will-v-pi / @kilograham A thought that I had this morning: if a particular (RP2350-based) board will always need a boot_stage2 to be included (which is what the comments in this PR seem to be implying?), is there a way for that to be done from the board's header-file?


HDDS-2995. Add integration test for Recon's Passive SCM state.

What changes were proposed in this pull request?

Verify Recon gets pipeline, node and container report from Datanode.
Verify SCM metadata state == Recon metadata state (Create pipeline , Close pipeline, create container)
Fix issue in DN StateContext.

What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-2995
How was this patch tested?
Manually tested.

Passed the 20 Test run - https://github.com/avijayanhwx/hadoop-ozone/runs/511649415.

+1 LGTM pending CI

@nandakumar131 can we merge it or would you like to review?

Thanks @adoroszlai for the review, I will take a look and merge it.

Thanks for the review all!


Upcoming Transaction Notifications (a.k.a Reminders)

Closes #476

It seems that reminders dialog is not presented automatically on account opening as I suggested, or did I miss something?

Ah forgot about that...will do!

Ok try latest commit.


Update smp_compute_cortical_magnification.py

I added the conversion into visual angles using code published for R Studio (visAngle() - http://stephenrho.github.io/visual-angle.html).

Hi @carbrock , thanks for this pull request. I have modified your suggestions in a way that the script runs now.
I think we should make sure that the PRF x y coordinate units and the "distance from the viewer" units are in the same. I have interpreted your 198 as cm. Is this correct?


doc: fix link to security.md from README.md

Signed-off-by: Simon Deziel<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"


_.reduce error

If you try to run reduce on an empty array it will cause an error. One would expect the function to just return an empty array, not throw an error.

Did you not provide an initial value for the reduction?

One would expect the function to just return an empty array

No, one wouldn't. At least, no one should. The result of a reduction has nothing to do with the fact that your reducing an array. It is only related to the initial value, the reducing function, and the array elements.

LOL @michaelficarra. @TSteele27 This has been fixed in edge.

@jdalton what do you mean by fixed? It returns an undefined value, no? If reduce on an effort array  without an initial value returns an empty array, I will be very confused.

The function was part of a chain, the previous steps ended up in an empty set, so when reduce ran it threw an error complaining about an empty set, either way I don't think that throwing an error is the best way to deal with this case. This is in version 1.5.2 so it may be fixed in newer version, but I didn't see a bug report for it.

#1858


Error: "WARNING: The following permissions are missing"

Maybe I am doing a rookie mistake but I would appreciate help on this matter. I created the app registration, added the cert, added the required data in the ps script (app id, tenantid, certThumbprint etc..) as well as added the permissions.

But I get this error?

and

What am I missing?
Thank you in advance

Hi @KrpaKrpa,
thats not a rookie mistake. I have not really documented that well enough.
The permissions have to be "Application" and not "Delegated". You also have to grant admin consent for each permission.
Can you test it out and give feedback please?
FYI: I am currently documenting that part and will update the readme accordingly.
Best
Ugur

The updated readme should do a better job on guiding you on the necessary steps. Closing the Issue for now until there is any feedback.


[!*VIRAL@CLIP-!]*Priyanka Sanam Full Sex Video Original Video Link Priyanka Sanam Video Viral On Social Media X Trending Now #3739

44 seconds ago
L𝚎aked Video Priyanka Sanam  Original Video Viral Video L𝚎aked on X Twitter Telegram
[-𝐅𝐔𝐋𝐋-𝐕𝐈𝐑𝐀𝐋-]— Priyanka Sanam  Video Original Video Link Priyanka Sanam  Video Viral On Social Media X Now [1U2M3N]
[-wATCH-]— Priyanka Sanam  Video Original Video Link Priyanka Sanam  Video Viral On Social Media X Trending Now
[-wATCH-]— Priyanka Sanam  Video Original Video Link Priyanka Sanam  Video Viral On Social Media X Trending Now
[-wATCH-]— Priyanka Sanam  ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Priyanka Sanam  ʟᴇᴀᴋᴇᴅ Video ᴠɪʀᴀʟ On Social Media ˣ ᵀʷⁱᵗᵗᵉʳ
[-wATCH-]— Priyanka Sanam  Video Original Video Link Priyanka Sanam  Video Viral On Social Media X Trending Now
Priyanka Sanam  Original Video video took the internet by storm and amazed viewers on various social media platforms. Priyanka Sanam , a young and talented digital creator, recently became famous thanks to this interesting video.
L𝚎aked Video Priyanka Sanam  Original Video Viral Video L𝚎aked on X Twitter
Priyanka Sanam  Original Video video oficial twitter
L𝚎aked Video Priyanka Sanam  Original Video Viral Video L𝚎aked on X Twitter..

wq


MAINT: Cleanup PR #90

followup of #90

Codecov Report

Merging #96 (31f368e) into main (20b8e75) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #96   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            2         2
  Lines          140       135    -5
=========================================
- Hits           140       135    -5

Impacted Files
Coverage Δ

polyagamma/_polyagamma.pyx
100.00% <100.00%> (ø)

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 20b8e75...31f368e. Read the comment docs.


Adds a -Random switch parameter to return a random comic

Adds a -Random switch parameter to Get-Dilbert. When called with -Random it will return a random comic
Description
When called with the -Random parameter, a random date between now and '1989-04-16' is used when fetching the comit
Related Issue
Adds the functionality requested in #2
Motivation and Context
Not required at all, but nice to be able to get a random comic, similar to what can be done with the XKCD plugin
How Has This Been Tested?
Simple usage test performed running PoshBot 0.11.5 in PowerShell 5.1 on Windows 10, hooked up to a Slack channel.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Sorry about the confusion with the other PR. This one should be good. Please approve or reject as you see fit :-)

Looks good @csandfeld. Thanks!


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit 6be22e4:
:clock10: Full build: the average full build time is 6 min(s) 5 sec(s), this is based on the last 322 build(s) for this repository.
:warning: This is a FULL build due to the incremental build being disabled in configuration file (.openpublishing.publish.config.json in 'live' branch). For more detailed info, please click here.

Docs Build status updates of commit 6be22e4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details
Dependent Files

:x:Error

Details

Line 388: [Error] Error happened in build.entrypoint.ps1. Please build your target branch first and then reopen this pull request to do another round of verification. If the issue still happens, open a ticket in http://SiteHelp and include the following error message for our team to troubleshoot: At W:\opco-s.optemp\packages\opbuild.scripts.1.74.0-alpha-20190425164814-ge838b4f\tools\opbuild\docset.postbuild.ps1:205 char:5

else if ($currentTargets.NeedBuild)

~

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


Upgrade Spring Boot dependency

As of 2021-11-05, decaton-spring's spring-boot dependency version is 2.1.7.RELEASE, which is way behind from boot's latest (2.5)
Though decaton-spring only uses core features of boot so should be work even with newer boot version, it's better to upgrade the dependency as much as possible

Hi @ocadaruma. I'd like to work on this issue. Could I get this issue assigned?

@hase1108 Oh, thanks for your interest.
Okay then let me assign you to this issue.

Fixed by #129


Add npm command for release prepartion

This allows
npm version <semver-version>|patch|

to work

Current coverage is 90.05%

Merging #6 into master will not affect coverage as of a2431df

@@            master      #6   diff @@
======================================
  Files            3       3
  Stmts          503     503
  Branches        77      77
  Methods          0       0
======================================
  Hit            453     453
  Partial          0       0
  Missed          50      50

Review entire Coverage Diff as of a2431df

Powered by Codecov. Updated on successful CI builds.

LGTM


useCombobox: add shouldKeepInputValueOnBlur option

Provide a general summary of the feature here
by default, when the combobox input loses focus, the popover closes and the input loses its value. onInputChanged will fire with an empty string.
There's a shouldCloseOnBlur option for useComboboxState that will keep the text when set to false, but it also keeps the popover open when blurred, which I don't want.
Could we add another option, to keep the text, but still close the popover?
🤔 Expected Behavior?
I want to be able to keep the input text when the comobobox loses focus, but have the popover close
😯 Current Behavior
You can only keep the text by keeping the popover open with shouldCloseOnBlur: false
💁 Possible Solution
No response
🔦 Context
I can see why it behaves the way it does, but I've got a bug report from a user wondering why their text disappears
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Would setting allowsCustomValue: true work for you? If your combobox doesn't truly accept any arbitrary value a user inputs then it feels more correct to have the input field be cleared, otherwise the user may expect their value to be included on form submission even though it wasn't a valid value.

I think most of our consumers are using it as a controlled component and getting the value from onSelectionChange so custom text isn't a concern for them and allowsCustomValue: true will work for them. Thanks!