Better control over destination of direct assets

It would be lovely if Bower could support arrays for dependency values, such as,
  "devDependencies": {
    "foo": [
        "https://raw.githubusercontent.com/foo/bar/63eacb484a97a17a9dfde07cc7033119b00bd176/public/assets/css/foo.css",
        "https://raw.githubusercontent.com/foo/bar/63eacb484a97a17a9dfde07cc7033119b00bd176/public/assets/js/foo.js"
       ]
  }

This would mean that both assets end up in the same folder. Currently I cannot figure out a way to put both those assets in the same folder. I believe this is a legitimate use-case and would allow for organising assets from unpackaged sources.
Alternatively (or additionally), something along the following lines would also be useful,
  "devDependencies": {
    "foo/css": "https://raw.githubusercontent.com/foo/bar/63eacb484a97a17a9dfde07cc7033119b00bd176/public/assets/css/foo.css",
    "foo/js": "https://raw.githubusercontent.com/foo/bar/63eacb484a97a17a9dfde07cc7033119b00bd176/public/assets/js/foo.js"
  }

You can change directory destination with
"foo=bar": "https://raw.githubusercontent.com/foo/bar/63eacb484a97a17a9dfde07cc7033119b00bd176/public/assets/css/foo.css"

Bower doesn't support sub-directories in bower_components, nor it will be supporting them, sorry.

@sheerun thanks for the tip, I tried that but it doesn't work as proposed. Could you please verify if this is a missing feature or if it is indeed something that I am not doing right:
  "devDependencies": {
    "laravel.com-docs-css": "https://raw.githubusercontent.com/laravel/laravel.com/a4a97a17a63eacb49dfde07cc7033119b00bd176/public/assets/css/laravel.css",
    "laravel.com-docs-js=foo": "https://raw.githubusercontent.com/laravel/laravel.com/a4a97a17a63eacb49dfde07cc7033119b00bd176/public/assets/js/laravel.js"
  }

Error:
bower laravel.com-docs-js#*  ENOTFOUND Package foo=https://raw.githubusercontent.com/laravel/laravel.com/a4a97a17a63eacb49dfde07cc7033119b00bd176/public/assets/js/laravel.js not found

Thanks very much!

@sheerun for clarification, I want both the css and js files to end up in the same folder. This will allow me to grab assets much more easily.
I think it's a very useful feature to have.
Not everyone has published a bower package but the simplicity and easy of bower should not be wasted on them. This just allows me to specify that I want to take all these CSS and JS files and put them in my specified folder.

It would be, but reusing the same folder and nested directories are against whole internal architecture of bower. We simply can't implement it in reasonable time.
You can use postinstall hook to move assets to appropriate places, though.

Makes sense, fair enough. Good idea on the postinstall hook tip, will go that route.


Good admin area example?

I cannot call this an issue, but wondering if you could point me to good tutorial on setting up (admin) area to actually push the messages?
Wanting to use this in school classroom but like to learn more about using first. Hate to have a kid call me out on it:)
Thanks in advance for your input.
Woody

Could you elaborate on what you mean by admin area?

Hi Tyler. Thank you for replying.
Looking for simple way to send the actual push message. Maybe simple form? Since many of the students are in 12-16 year old range, looking to make things very simple.
Totally understand this is out of scope, but just hoping for some more in-depth tutorials and maybe working examples.
Cheers,
Woody

Depending on what you hope to achieve, you could just wire a button to send the message using the onclick() method. So it might look something like:
<button onclick="Push.create('Hello World');">Click me</button>

Hopefully this is along the lines of what you're looking for?

Thanks again Tyler for input.
Yes something like that but, with form so message can be customized.
I tried onclick method very similar to what you show but also ran into problem of not working. Was on server when tried. Will review my code tomorrow at school and see if yours fixes issues.
Just looking for form that message is customized and submit button so very close:)
Cheers!

Oh, okay! You could always just do something like this (untested):
<form onsubmit="func();">
    <input type="text" id="name" />
    <input type="submit" value="Submit" />
</form>
<script type="text/javascript">
     function func() {
          Push.create(document.getElementById("name").value);
     }
</script>

For more information of HTML forms, see here. Hopefully this is a little more helpful.

Hi Tyler. Sorry for no reply, been kind of crazy with end of year, school is out for summer.
Appreciate the input and will be exploring some ways to do an admin area over the summer.
Cheers!

No problem. I closed this issue because I hadn't heard from you and figured you had everything sorted out. If you have any further questions, just feel free to post on this issue and I'll reopen it :)


Making the library thread-safe

I have been using iniparser for a project I am working on, and it is working great. However, I ran into a segmentation fault recently and discovered that the library as written is not thread-safe. The functions strlwc() and strstrip() in iniparser.c are the culprits as they are not re-entrant (as indicated in the comments).
I think that the library documentation should be revised to indicate that it is not currently thread-safe.
However, I have also revised the above functions to take additional arguments that do make them thread-safe. The changes to the rest of the library are transparent to the user. I can send you a patch if you would like.
Best,
Mike Foss

This has not been integrated yet, right?
b.

You should have a look at my branch https://github.com/touilleMan/iniparser4 ;-)

I see, tnx. :)
It's kinda hard to keep track of where the development is actually going on.
Judging by the diagram at the https://github.com/ndevilla/iniparser/network I can assume quite some development is going on in various repositories but many changes are not pulled back to ndevillea's "main" repository.
Maybe someone should step up and encourage merging all the scattered changes. Unless ndevilla is you :)
b.
BTW I saw this on your repo page: "This branch is 27 commits ahead, 22 commits behind ndevilla:master" - being behind, are you intending to merge those 22 commits or are they incompatible with your changes?

Cutting a long story short, at the time I wanted to make iniparser evolve, @ndevilla had no time to work on this project and was willing to keep the repo as it is (for backward compatibility), letting me forking the repo to create new major version.
My major changes:

unittests with travis integration (code coverage around 92% of dictionary.c and 70% of iniparser.c)
constify the api
make it thread safe

I the meantime, @ndevilla go back to work and start integrate PR redundant with my changes (constify and thread safe), hence our two repos have diverged.
Of course it would be better to have my branch merged into the main one (at least the unit test part, everybody love unit tests !), but no one has the courage to do it so far... ^^

Just had a lengthy discussion with touilleMan. He is taking over maintenance of this project in his branch iniparser4. This repository will mostly remain untouched and left for historical purposes. Please address him any further modifications you might want to contribute!
Will update the project page accordingly. Many thanks to all contributors!
Cheers
Nicolas

Thanks for clarification, and thanks for a great library - I am using it for Snoopy (https://github.com/a2o/snoopy ) quite successfully.
b.

@touilleMan: Could you please enable Issues functionality in your iniparser4 project? :)


Layer Cake

Adding "breadcrumbs" to the main modules is helpful in ushering along course participants, but for some of the optional labs with multiple Cryptol modules (Cryptol and SAW Demos, Salsa20, etc.), it seems abrupt to go from enjoying a Caesar demo to rushing along to Salsa20, for example.  The Transposition lab has the opposite problem, where participants have to go through all the different ciphers before getting to the Capstone lab.  Perhaps there should be multiple layers of navigation: one to traverse multiple modules of a lab, and another to traverse the labs, perhaps with additional links to optional labs where applicable.  Navigation is an interesting problem...

I agree we should do this.

I played at integrating navigation links a few weeks back, using the markup
link mechanism. The results were annoying at best: relative links were
interpreted differently in straight browsing and in the GitHub interface.
Cheers,
Zig
On Sat, Oct 3, 2020, 1:24 PM weaversa<EMAIL_ADDRESS>wrote:

I agree we should do this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/weaversa/cryptol-course/issues/143#issuecomment-703153226,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACRABROPWHXY7WS3R7LWR53SI527RANCNFSM4RVKETUQ
.

It's likely that I made some mistakes...feel free to reopen if you find something that needs fixing.

A good start.
In general, the "layer cake" is a nested digraph comprising a layer of labs and a layer of components within each lab, with a critical path over some components of multiple labs and a recommended path over all components within each lab.  Presently, the critical path comprises one component per lab (Salsa20 is the only critical lab with an extra, non-critical component, Salsa20Props).
More specifically,

"Previous Lab" and "Next Lab" should navigate along the critical path
"More" should link a critical lab component to representative entry components of optional labs
"Up" should link each non-critical component (entry or otherwise) back to the critical component that linked to its representative
"Previous Component" and "Next Component" should navigate a recommended path of all components in the current lab
Each lab component with an `EXERCISE should have a corresponding "Answers" file and link,
Each "Answers" file should have a link back to the "Exercises" it answers
The nested graph of "Answers" should mirror that of the corresponding "Exercises".

If we're up for some...exercise, we could depict recommended paths graphically within each multi-component lab and/or check the consistency of navigation in a CI script using metadata.

Thanks for having another go @WeeknightMVP. If you make a PR I will help out.


Android Basics: Get data from the Internet

name: Android Basics Unit 4 issue
about: Report problems with the Android Basics Unit 4 codelabs
title: 'Android Basics Unit 4 issue:'
labels: ''
assignees: ''

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-training-getting-data-internet?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-kotlin-unit-4-pathway-2%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-training-getting-data-internet#7
In which task and step of the codelab can this issue be found?
Step 8
Describe the problem
interface MarsApiService {
@GET("photo")
fun getPhotos(): List
}
should say @GET("photos") <-- needs the "s"
Steps to reproduce?
Versions
Additional information

@wlagunzad
Thank you for reaching out to us. The issue is fixed and published.


Prevent the user-provided props to override the own props of KeyboardAvoidingView

If the user provides onLayout or ref props to KeyboardAvoidingView, it will override the internal props that will be provided to the internal View. This PR fixes the problem.

Are you sure the behavior where onLayout and ref get overridden isn't what some people want?
A test to make sure this behaves correctly would be good, too.

Closing this one since Kevin commented last about a month ago. If you plan to continue working on this please send a new PR. Closing PRs just helps make sure they don't stay around and get stale, and it's quite easy to reopen new ones. Thanks for understanding!

@mkonicek Sorry, I missed the comment by @lacker.
I think if those get overridden, KeyboardAvoidingView doesn't work as expected. Do you think it's not the case, @lacker?


No obvious way to delete AnimationNodeBlendTree node in AnimationTree editor

Godot version
4.2-mono-rc5
System information
MacOS 12.3
Issue description
When adding a new node to an AnimationNodeBlendTree in the AnimationTree editor, I can't find a way to remove it again other than undo.
Ctrl+Delete removes the AnimationTree node. Right click on the node opens the Add Node menu.

Steps to reproduce

Add an AnimationTree node with an AnimationNodeBlendTree
Open the AnimationTree editor
Add a node
Try to remove it

Minimal reproduction project
Should be easily reproducible without an MRP

Select Node -> Press Delete Key
seems to work!

Select Node -> Press Delete Key seems to work!

That does nothing on my platform (Macbook Pro). Possibly because the Delete key is actually backspace?

Select Node -> Press(出版社) Delete Key seems to work!

That does nothing on my platform (Macbook Pro). Possibly because the Delete key is actually backspace?

Sorry, I didn't realize you meant mac.
Editor -> Editor Setting -> Shortcuts -> ui_graph_delete, change binding to Backspace (or your like)

That does fix my immediate problem, but I'm leaving this bug open because I believe something like the statemachine node editor bin button is required here:

I got same issue when I want delete Node in AnimationTree
without delete button, makes me confused

This is a regression. Close buttons are available in 4.1 versions.


Make text to replace consistent

The two instances of YOUR_COMPANY_NAME_HERE in the DCM were inconsistent.

This PR is out of date and no longer applicable.


[M] fetch and merge into active branch

`/usr/bin/git merge o r i g i n / d e v e l o p` failed with following output:

merge: o r i g i n / d e v e l o p - not something we can merge

Can you make a log with where commands
https://github.com/divmain/GitSavvy/blob/master/docs/debug.md#gitsavvy-start-logging


[Workaround] Value cannot be null, value: text

You probably saw my comment on the other issue.
First it wasn't meant as an attack, sorry if it seemed to be one.
Second, and that's why I am writing this, I have a workaround for the issue.
To avoid frustrated users you could add it to the closed issue (since I can't)
All Charts seem to work if we initialize all Properties inside of a ChartEntry item.
Hope this will help some users!
This can be closed since it's of no real use, just to contact you.

I understand that, it's just I've had people complain about something not being done fast enough so that's why I'm a little defensive, I apologize for that, I locked it just because the ticket is so old and I'm trying to keep things tidy, I think there's a way to autoclose tickets but I need to investigate how to add it to keep issues fresh and know if something is actually a problem still.


Fix dynamic class assembly name

Using the assembly name to hint at the source of the classes was
problematic in multiple ways.
This change stores the actual filename in an attribute on the assembly.
So for a given type, one can get the assembly this way:
[SomeType].Assembly.GetCustomAttributes() |
? { $_ -is [System.Management.Automation.DynamicClassImplementationAssemblyAttribute] } |
% { $_.ScriptFile }

This is great, but the usage seems too complex to remember.  Can we use ETS to just add a ScriptFile property making it more discoverable?

@SteveL-MSFT - I've only seen 1 request for this ability - from the author of ISESteroids - so ease of use doesn't seem too critical. I suppose we could use a NoteProperty on the assembly instance, but that is harder to access from C#.

@lzybkr we can wait for customer request before adding more.  Thanks


linuxPackages.ax99100: fix build with Linux >= 6.2

Description of changes
The device class definition was changed to require a const pointer, so this driver needs to be patched as well.
https://github.com/torvalds/linux/commit/ff62b8e6588fb07bedda7423622c140c4edd66a7
Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

6 packages built:

linuxKernel.packages.linux_6_2.ax99100
linuxPackages_latest.ax99100 (linuxKernel.packages.linux_6_3.ax99100)
linuxPackages_latest-libre.ax99100 (linuxKernel.packages.linux_latest_libre.ax99100)
linuxPackages_lqx.ax99100 (linuxKernel.packages.linux_lqx.ax99100)
linuxPackages_xanmod_latest.ax99100 (linuxKernel.packages.linux_xanmod_latest.ax99100 ,linuxPackages_xanmod_stable.ax99100)
linuxPackages_zen.ax99100 (linuxKernel.packages.linux_zen.ax99100)


inital commit of sherpa_bridge

Here is the notebook demonstrating its use.
Sorry for all the typo's and spelling mistakes by the way I try but a lot slip though.
https://github.com/nocturnalastro/astrosherpa-notebooks/blob/proofofconcept/Sherpa_fitter.ipynb
This has the new way to deal with returning the model as a list if there's multiple models or datasets
https://github.com/nocturnalastro/astrosherpa-notebooks/blob/proofofconcept/Tied_List_Fitter.ipynb

I think your tests look extensive for what is there already; I would have thought that we could have done with one test for each of the types of test you run there at this point of the project, but you are doing even better!

I ran coverage analysis on the current tests: there are parts of the code that are not being tested. I would suggest, if possible, to remove those parts until you add tests for the functionality they implement (or add those tests now, but since such functionality is not in the list of use cases so far that can be done later).
The other part of the code that is not covered is error handling: I have some comments on that which could significanlty reduce the amount of error handling to actually implement.
A general comment on the use of isclass and isinstance: in my opinion they should be avoided as much as possible. Either you embrace duck typing, or you take control of the instances you build through factories. If you choose duck typing, rather than checking the class explicitly, try calling the method you need, then fail graciously if it does not work.
I'll add more specific comments to the diff itself.
[I am well aware that some of my comments may be clashing with current practices in the Sherpa code (e.g. the use of isinstance et al.), but that's something we are trying to improve in Sherpa as well].

Good work @nocturnalastro! With the tests in place, I think we are now in a place where we can do some serious refactoring, so to make the code cleaner and more maintainable. Also, we might want to take a step back and agree on the API for setting the various fit components (optimizer, statistic, error estimator) and for setting their options.


Run mix format, support cowboy 2.x

Hello, @arjan! This is your first Pull Request that will be reviewed by Ebert, an automatic Code Review service. It will leave comments on this diff with potential issues and style violations found in the code as you push new commits. You can also see all the issues found on this Pull Request on its review page. Please check our documentation for more information.

Would you mind merging this so I can stop maintaining my own fork?

Changes included in other PR. Thanks!


Node.js  uvwasi team Meeting 2024-02-14

Time
UTC Wed 14-Feb-2024 19:00 (07:00 PM):

Timezone
Date/Time

US / Pacific
Wed 14-Feb-2024 11:00 (11:00 AM)

US / Mountain
Wed 14-Feb-2024 12:00 (12:00 PM)

US / Central
Wed 14-Feb-2024 13:00 (01:00 PM)

US / Eastern
Wed 14-Feb-2024 14:00 (02:00 PM)

EU / Western
Wed 14-Feb-2024 19:00 (07:00 PM)

EU / Central
Wed 14-Feb-2024 20:00 (08:00 PM)

EU / Eastern
Wed 14-Feb-2024 21:00 (09:00 PM)

Moscow
Wed 14-Feb-2024 22:00 (10:00 PM)

Chennai
Thu 15-Feb-2024 00:30 (12:30 AM)

Hangzhou
Thu 15-Feb-2024 03:00 (03:00 AM)

Tokyo
Thu 15-Feb-2024 04:00 (04:00 AM)

Sydney
Thu 15-Feb-2024 06:00 (06:00 AM)

Or in your local time:

https://www.timeanddate.com/worldclock/fixedtime.html?msg=Node.js+Foundation+uvwasi team+Meeting+2024-02-14&iso=20240214T1900
or https://www.wolframalpha.com/input/?i=07PM+UTC%2C+Feb+14%2C+2024+in+local+time

Links

Minutes Google Doc: https://docs.google.com/document/d/1nhxetzCzZk09HfEyK5pm5-zqJ5bW8YjmjkuDx4hCoSM/edit

Agenda
Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

NodeJS WASI API throwns an exception when both _start and _initialize are exported #51544
WASI preview 1: fd_readdir ignores cookie argument #47193

nodejs/uvwasi

What's new with uvwasi in 2023 #201
Changes to WASI spec in snapshot_preview2 #59

Invited

uvwasi team: @nodejs/wasi

Observers/Guests
Notes
The agenda comes from issues labelled with uvwasi-agenda across all of the repositories in the nodejs org. Please label any additional issues that should be on the agenda before the meeting starts.
Joining the meeting

link for participants: https://zoom.us/j/91612484369
For those who just want to watch:
youtube admin page: https://www.youtube.com/my_live_events?filter=scheduled

Minutes from the meeting today:
Node.js  uvwasi team Meeting 2024-02-14
Links

Recording:  https://www.youtube.com/watch?v=3spOIIOR5dU
GitHub Issue: https://github.com/nodejs/uvwasi/issues/249

Present

Michael Dawson (@mhdawson)
Guy Bedford
Blaine

Agenda
Announcements
*Extracted from uvwasi-agenda labelled issues and pull requests from the nodejs org prior to the meeting.
nodejs/node

NodeJS WASI API throwns an exception when both _start and _initialize are exported #51544

No update

WASI preview 1: fd_readdir ignores cookie argument #47193

GitHub does have the Mac M1 runners, that could be step towards debugging

nodejs/uvwasi

What's new with uvwasi in 2023 #201

Nothing new this week

Changes to WASI spec in snapshot_preview2 #59

About this time last month preview 2 was formalized, now called wasi 020, major update to the APIs that add supports for component model based bindings. Also includes new subsystem wasi http (has fetch like semantics), wasi sockets is also much more complete.
Means we could ship preview 2 if we had the cycles to do it.
https://github.com/bytecodealliance/jco has implemented preview 2 on top of Node.js

running posix on posix in multiple layers
passes all of the preview 2 testsuite
means where you have Node.js you can get WASM. It will be correct, but not necessarily fast

Guy to put together a summary of what the high level integration would look like
Michael, how many implementations

jco
Wasmtime
something vscode related

Blain

anybody who runs in browser will have their own shims as chrom is not going to implement the component model
Wasmtime

Guy, now at the early adoption phase, its now stable, which should drive usage

Q&A, Other
Upcoming Meetings

Node.js Project Calendar: https://nodejs.org/calendar

Click +GoogleCalendar at the bottom right to add to your own Google calendar.


Integrate updated mux into tt07

Merges the dev branch plus some minor changes to make it pass the flow. Works in tandem with updates in tt-support-tools and tinytapeout-07 (to follow soon).

Can you remove 661f705
We never put the temporary "hacks" in master. We keep branches per shuttle with those applied on top.

Also did we run a tapeout job to make sure the result passes all the steps ?


Simplisafe fails to load on 0.80.0 version

Home Assistant release with the issue:

0.80.0
Last working Home Assistant release (if known):
0.79.3
Operating environment (Hass.io/Docker/Windows/etc.):

Virtual Environment installation n Ubuntu 16.04 LTS
Component/platform:

Simplisafe
Description of problem:
Simplisafe throws error and refuses to work. I have had Simplisafe for a couple of years now, and never had any issues with it until the 0.80.0 version. When I downgraded my HA to 0.79.3, the issue went away.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
alarm_control_panel:
  platform: simplisafe
  name: Simplisafe
  username: !secret simplisafe_username
  password: !secret simplisafe_password

Traceback (if applicable):
2018-10-14 09:23:17 ERROR (MainThread) [homeassistant.components.alarm_control_panel] Error while setting up platform simplisafe
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/helpers/entity_platform.py", line 128, in _async_setup_platform
    SLOW_SETUP_MAX_WAIT, loop=hass.loop)
  File "/usr/local/lib/python3.5/asyncio/tasks.py", line 400, in wait_for
    return fut.result()
  File "/usr/local/lib/python3.5/asyncio/futures.py", line 293, in result
    raise self._exception
  File "/usr/local/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/alarm_control_panel/simplisafe.py", line 77, in async_setup_platform
    systems = await simplisafe.get_systems()
  File "/srv/homeassistant/lib/python3.5/site-packages/simplipy/api.py", line 97, in get_systems
    await system.update(refresh_location=False)
  File "/srv/homeassistant/lib/python3.5/site-packages/simplipy/system.py", line 144, in update
    'cached': str(cached).lower()
  File "/srv/homeassistant/lib/python3.5/site-packages/simplipy/api.py", line 148, in request
    endpoint, err)) from None
simplipy.errors.RequestError: Error requesting data from subscriptions/521915/settings: 403, message='Forbidden'

Additional information:
I also enabled simplipy.api: debug in the logs section, and I do not see anything but the above call stack. No additional information that I can share. Please feel free to tag me on Discord if you need me to try out anything. I'll be happy to tryout a few things to help troubleshoot the problem.

@skalavala Sorry for the trouble. I reached out on Discord.

@skalavala Sorry for the trouble. I reached out on Discord.

@bachya  Thank you very much for your outstanding support! I am closing the issue knowing that the fix has been issued, and will be available in either the next release or in the upcoming minor releases.


updating Chef Server to 15.3.2

Signed-off-by: Kallol Roy<EMAIL_ADDRESS>:nut_and_bolt: Description: What code changed, and why?
Update Chef Server to 15.3.2
:chains: Related Resources
:+1: Definition of Done

Chef Server pipelines should be green

:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist
All PRs must tick these:

[x] I have read the CONTRIBUTING document.
[x] All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

[ ] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
[ ] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
[ ] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
[ ] Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
[ ] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

[ ] Tests added/updated? (all new code needs new tests)
[ ] Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable

@kalroy  chef server test cases are passing in the pipeline, Could you please check it once.


Redundant requirement in reset password screen

Environment info

Version: VERSION
Deployment: AZURE | AWS | GCLOUD | ESX | VBOX | DEV
Customer: NAME

Actual behavior

"This field is required" - no need for that.

Expected behavior

Steps to reproduce

Create a new user and login with it/ reset a user password and try login.

Screenshots or Logs or other output that would be helpful

As we are not investing in the UI console, closing


Works for all games?

Just wanna confirm if this is only applicable to csgo or any other games using vac such as tf2, dota2 etc...

Well I use it for other games I pay for games you can see here https://steamcommunity.com/profiles/76561199094345102/ and so far so good


Limiting whose pull requests generate new versions

The problem
We are using this pull request resource to create Bosh releases in our Concourse pipeline, for a deployment of Cloud Foundry. Bosh releases (and potentially other repositories) can contain scripts which are executed when the release is compiled in the pipeline. Executing scripts from a pull request combined with use of an AWS instance profile (for Concourse) presents a massive security problem. Anybody could raise a pull request with malicious code which grabs the instance profile's metadata (AWS keys).
Proposed solution
Add some optional resource parameters which limit the source of the pull request. We still want people to be able to raise pull requests, but only the right people will cause a new version in Concourse to trigger. Two ideas could be:

limit to pull requests from the same repo (forks are not allowed to submit)
limit to GitHub users/groups

We are going to fork this repository and work on a solution. Meanwhile, we would be grateful for any advice you may have on the matter. We would like to be able to merge our solution upstream and close our fork once we are done.

Limiting the users as a config on the PR resource adds a level of authorization. The resource shouldn't be concerned with this. Github already has a mechanism for limiting access to repos and who can make PRs -- make the repo private.
This would duplicate work that Github has already done of good job of. :-/

@jtarchie

Limiting the users as a config on the PR resource adds a level of authorization. The resource shouldn't be concerned with this.

The pull request resource is concerned with detecting valid versions of a resource. For instance, a closed pull request is not valid. Whether the pull request is from a fork, and therefore less trusted, is just another piece of criteria you can use to determine what generates a resource version. An example of this is the Git resource itself, which has code to assert the commit has been signed.

Github already has a mechanism for limiting access to repos and who can make PRs -- make the repo private.

This conflicts with the ability to make code open source, or open to the public. Our organisation has a policy of coding in the open and making things open source whenever possible, so we want people to be able to open pull requests to benefit from the open source community. That said, we cannot have untrusted code being pulled into our Concourse pipeline. Having private repositories with a public counterpart only protects from internally leaking something into the open.

This would duplicate work that Github has already done of good job of. :-/

Kind of true. This functionality would in no way affect actual authorisation over the contents of any repository. It is authorisation on the thing consuming the code from the external repository. It is the automated equivalent of a human saying "Should I really download the contents of this pull request and run any executables on my local machine without checking them first?".

Spent some time refactoring the filtering of pull requests. Please look at the filters. This is the direction I am going in supporting new filters.

Thanks @jtarchie. Does that mean if we refactor our work on https://github.com/alphagov/paas-pullrequest-resource/pull/1 to fit this pattern of filters you will accept the pull request?

Yes.
Happy to help. This was a massive refactoring.

Awesome, thanks. It may be a while as we will have to schedule the work.

Give me some time, I think I can pull in your changes. Assuming your test case pass, right? :-)

Our tests were passing, it was reviewed on our team, and we've already started using our version to in our CI pipeline with no problems. I don't know how it would fit in with your refactoring yet though. Do you need us to raise a pull request, or would you just cherry pick our changes?

@henrytk, please see this commit.
It should be on jtarchie/pr:test docker image for testing. If you works for you I'll release it!
NOTE I changed disallow_forks to disable_forks.

Merged. I will release officially tonight.

Closing on release of v20. Please open up new issues if there are bugs or future feature requests.


ChoiceOutputParser

Feature request
Output parser that returns one of a set of options
Motivation

Many decisions are multiple choice. This makes it easier to elicidate this information from LLMs

Your contribution
Implemented ChoiceOutputParser
Details in PR

https://twitter.com/JacobFValdez


remounting window manager after destroy

Im unmounting whiteboard component, when i remount it destroys old instance of windowmanager and remounting window manager.
windowManager?.destroy()

await WindowManager.mount({
    room,
    container: whiteboardEl,
    cursor: true,
    collectorContainer: collectorEl,
    /* the containerSizeRatio config limit width and height ratio of windowManager
     for make sure windowManager sync in whiteboard. */
    containerSizeRatio: (8.3 / 16),
    collectorStyles: {
        position: "absolute",
        right: "10px",
        bottom: "60px",
    },
    chessboard: false,
    debug: true
})

when component is mounted i have access to toolbars however I'm unable to annotate on the whiteboard and the cursor doesn't show pencil symbol etc etc
i get the following error on the console.
Error: there is another view who's mode is Writable. it should be singleton

Thanks for your report, I will fix it later

fix at<EMAIL_ADDRESS>

"white-web-sdk": "^2.13.20"
"@netless/window-manager": "^0.1.66",
no longer getting window on mount errors but now getting below error
Uncaught (in promise) Error: view did release
at ll.assertNotRelease (webpack-internal:///./node_modules/white-web-sdk/index.js:1)
at ll.release (webpack-internal:///./node_modules/white-web-sdk/index.js:1)
at Te.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20)
at Le.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20)
at yt._destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20)
at yt.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20)
at mountWindowManager (webpack-internal:///./src/components/Whiteboard.tsx:134)
at eval (webpack-internal:///./src/components/Whiteboard.tsx:171)
at commitHookEffectListMount (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:19731)
at commitPassiveHookEffects (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:19769)
at HTMLUnknownElement.callCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:188)
at HTMLUnknownElement.sentryWrapped (webpack-internal:///./node_modules/@sentry/browser/esm/helpers.js:80)
at Object.invokeGuardedCallbackDev (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:237)
at invokeGuardedCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:292)
at flushPassiveEffectsImpl (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22853)
at unstable_runWithPriority (webpack-internal:///./node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:653)
at runWithPriority$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11039)
at flushPassiveEffects (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22820)
at performSyncWorkOnRoot (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:21737)
at eval (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11089)
at unstable_runWithPriority (webpack-internal:///./node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:653)
at runWithPriority$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11039)
at flushSyncCallbackQueueImpl (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11084)
at flushSyncCallbackQueue (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11072)
at discreteUpdates$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:21893)
at discreteUpdates (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:806)
at dispatchDiscreteEvent (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:4168)
at HTMLDocument.sentryWrapped (webpack-internal:///./node_modules/@sentry/browser/esm/helpers.js:80)

"white-web-sdk": "^2.13.20" "@netless/window-manager": "^0.1.66",
no longer getting window on mount errors but now getting below error
Uncaught (in promise) Error: view did release at ll.assertNotRelease (webpack-internal:///./node_modules/white-web-sdk/index.js:1) at ll.release (webpack-internal:///./node_modules/white-web-sdk/index.js:1) at Te.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20) at Le.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20) at yt._destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20) at yt.destroy (webpack-internal:///./node_modules/@netless/window-manager/dist/index.es.js:20) at mountWindowManager (webpack-internal:///./src/components/Whiteboard.tsx:134) at eval (webpack-internal:///./src/components/Whiteboard.tsx:171) at commitHookEffectListMount (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:19731) at commitPassiveHookEffects (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:19769) at HTMLUnknownElement.callCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:188) at HTMLUnknownElement.sentryWrapped (webpack-internal:///./node_modules/@sentry/browser/esm/helpers.js:80) at Object.invokeGuardedCallbackDev (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:237) at invokeGuardedCallback (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:292) at flushPassiveEffectsImpl (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22853) at unstable_runWithPriority (webpack-internal:///./node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:653) at runWithPriority$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11039) at flushPassiveEffects (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:22820) at performSyncWorkOnRoot (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:21737) at eval (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11089) at unstable_runWithPriority (webpack-internal:///./node_modules/react-dom/node_modules/scheduler/cjs/scheduler.development.js:653) at runWithPriority$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11039) at flushSyncCallbackQueueImpl (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11084) at flushSyncCallbackQueue (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:11072) at discreteUpdates$1 (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:21893) at discreteUpdates (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:806) at dispatchDiscreteEvent (webpack-internal:///./node_modules/react-dom/cjs/react-dom.development.js:4168) at HTMLDocument.sentryWrapped (webpack-internal:///./node_modules/@sentry/browser/esm/helpers.js:80)

Is there a reproducible demo?
I can’t reproduce it with the same version

i upgraded to white-web-sdk 2.14.3, enabled mobx on sdk init and its working fine. thanks


animateHeight={true} -> issue with overflow

When the swipeview is initialized with the property animateHeight={true} the the swipeable container behaves as expected: It has the perfect size to fit the content.
But once some list you output withing that container gets highter (e.g. states changes and the map function returns more  elements) the height doesn't change accordingly. You have to swipe to another swipecontainer and then come back again to see the correct height.
Is there an event which I can trigger to recalculate the height once my content changes?

Here is a related issue #144.

Thanks for the quick reply. I would much rather see the height of the container get updated than dealing with a overflow auto scrollbar :/

Having the same problem. I basically load the content of each container in the list of swipable containers, after the swipable views has been rendered the first time. If the animateHeight property is set to true the first views does not render correctly. I tried to hack this and set the animateHeight to false the first time I load the component and then change it to true once I do the first swipe, but this results in weird jumps on the page once I set the property to true. Hope this can be fixed soon. Thx.

I would much rather see the height of the container get updated than dealing with a overflow auto scrollbar

That wasn't working before this change.
Dynamic content height are definitely not supported right now.
You can add an overflow-y: auto; style to the slides that are going to have a greater height.
I have no plan regarding improving this point.
I'm not sure what's the best approach is.

This isn't ideal, but I used a callback for any event affecting the height to call forceUpdate() on the component that renders SwipeableViews. Made even hackier by the fact I had to put it in a setTimeout so it would wait for a child's height transition to complete before re-rendering and recalculating height. Works, but makes me a little sad.

@DaveSpivey Any idea how we could improve this dirty hack? Maybe exposing a callback trigger.

I was pretty happy with this component, but since I discovered this issue, it is a show-stopper and I'll have to find some alternative ;(

@Nopik Or you could help fixing it :)

Yeah, trying to, actually ;) In my case force refreshing the whole container should work. If the container would expose some callback, I can call it to, after my content changes. Not ideal, but will do the job.
heightLatest is already in the state, and there is updateHeight method, though its argument makes it extremely hard to use from client code. It should be easy to expose more convenient method to the client, as you know all the nodes (can remember array of refs, not doing that at the moment) and index of currently selected node. So, argumentless updateHeight should be quite easily possible.
Then, client should call that after content change, and it theoretically should work, if I didn't overlooked something.
Also, having such method available in context would be great, too, so there would be no need to remember refs on client side and pass update callback through possible large number of prop layers.
And indeed, when I did a quick and dirty new function (which would have height as a single argument and setState it to heightLatest), exposed it via context and called from child deep in the hierarchy, the height nicely animated to the correct value. Interestingly, even if I provided too high value, like 2000, the container height updated to the correct value (565 in my test case). I guess, extra update was there.
Adding it in a proper way (not requiring a height as an argument, but having an array of refs & taking the height of the correct one), would solve the problem for me.

So, for now, taking an advantage that there is extra update in meantime, I modified my function to set latest height to zero, and being argumentless. So, it is easy to call from client code, and the resulting effect on screen is exactly what I want.
That should definitely be improved later on to cleaner version & proper algorithm described above, but for now it does the trick. I'll try to fork and issue PR for it - as the change is additive, it wont break any existing code, but for those in need it will be a help.

Issued https://github.com/oliviertassinari/react-swipeable-views/pull/279

Btw. it seems that setting height to 0 will actually animate it from current height to zero, then to the desired height. Setting it to currentHeight + 1 gets rid of that effect.


Implement 1st review changes

This PR:

[ ] Closes #xxxx.
[ ] Adds and passes relevant tests.
[ ] Has well-formatted code and documentation.

Notes:

It is essential that you add a test when making code changes.
This keeps the code coverage level up, and helps ensure the changes work as intended.
When fixing a bug, you must add a test that would produce the bug in the master branch, and then show that it is fixed with the new code.
New code additions must be well formatted. Changes should pass the pre-commit workflow, which you can set up locally using pre-commit.
Docstring additions must render correctly, including escapes and LaTeX.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@6fdbc70). Click here to learn what that means.
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            @@
##             master       #4   +/-   ##
=========================================
  Coverage          ?   98.80%
=========================================
  Files             ?       30
  Lines             ?      750
  Branches          ?        0
=========================================
  Hits              ?      741
  Misses            ?        9
  Partials          ?        0

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


fix(checkbox,radio-group): Increase contrast ratio of checkboxes and radio buttons

Fixes #223

@multiwebinc I made some updates to make it work without bg-white. Let me know what you think.

Yes, that's much better.


[Feature]: is it possible to have several injected wallets displayed?

Is your request related to a problem?
Hi, currently only one injected wallet is displayed when connecting with onboard ->

Is it possible to have several injected wallets displayed instead of one?
Thanks!
Feature Description
No response
Alternative Solutions
No response
Anything else?
No response

@greedythib which injected-wallets package version are you on? Which wallets are you wanting to show?
In the latest version of injected-wallets package, if a user has Coinbase wallet installed both CB and MM will be shown

@Adamj1232 I am using the very last versions for react and injected-wallets modules. OK thanks, indeed coinbase injected wallet is displayed separately from metamask, that's amazing!
However, it seems like await connect() does not trigger the connection when the array connectedWallets is empty. Do you know what it could be?
Thanks

@greedythib hmm Im not too sure, could you share a little more context around the code block causing an issue?
We have this working in our demo project here and I'm not seeing an issue when await connect() is called triggered and connectedWallets is empty

My code is exactly similar to the demo you mentioned. It was working smoothly but with the new updates, the call await connect() does not work anymore. I am not sure whether this is the reason but it is only triggering the connect modal when connectedWallets is not empty.

@greedythib I would need more context around when await connect() is called to help

@greedythib there is a new version of web3-onboard react out that I owuld recommend updating to and then comparing your code to the react demo code. I am going to close this issue as it is unrelated to the title but we can continue this discussion or I can meet you on discord for chat support which would be the easiest way to communicate

Hey @Adamj1232, sorry for bringing this back, but we are facing this issue where users that use Opera GX are only being suggested the Opera Wallet and not MetaMask even though they have MetaMask installed on their browser. Is there any way around that ?

Amazing thanks !


Args with null value fail in story

import Message from "../../templates/components/Message.html.twig";

export default {
    component: Message,
    argTypes: {
        chat: {table: {disable: true}},
    },
    args: {
        chat: null
    }
}

export const Default = {};

@Fred-QS Just checked the code, the issue was fixed when I refactored the actions addon integration, but it was not part of the 0.1.1 release.. If you use the latest version 0.1.2 that I just published, you should not encounter this issue anymore.


Reword prompt for Credential Nickname

https://positpbc.slack.com/archives/C05D7NZD52S/p1726065183528269

The Title Case is awkward here, and the “Credential” concept was not previously introduced. Consider saying something a little more casual like:
Enter a unique nickname for this server and API key combination.

Adding another example of the inputs from VS Code to show that the title case is usually not used


Fix broken text input in the switch node

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
Fixed #4241. In the switch node, the previous type is applied to the added text input. As of now, in the "is type of" rule, I think that only the number type should be copied to the second rule and others are string type. Could you check this handling?
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the forum/slack team.
[ ] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

👍


0.23 : No more emphasize in PowerToys Run list

ℹ Computer information

PowerToys version: 0.23
PowerToy Utility: Run
Running PowerToys as Admin: Yes
Windows build number: [run "winver"] 1903.18362.592

📝 Provide detailed reproduction steps (if any)

Activate PowerToys Run
Type something

✔ Expected result
The first item on the list should be emphasized, and it's not more in 0.23.
❌ Actual result
See the screenshot.
📷 Screenshots

Hi @romu70, i can't repro this bug.  Can you work with us a bit more and help us repro this?
Are you doing a lot before hand?  does this happen on a fresh new launch?

Hi @crutkas, sure, let me know how I can help.
Since the installation of the 0.23, it happens all the time, I never see the blue emphasize anymore. I'll try to restart the computer to check if this fixes the problem.

similar to #6683

@romu70 Can you please share logs at %userprofile%/appdata/local/microsoft/powertoys/PowerToys Run?

Here they are, I zipped the whole folder.
Logs.zip

I didn't see the problem since 0.24, but this morning, with 0.25, it's here again. Logs are here attached.

Logs.zip

do you have this option enabled in your color setting?

@romu70 do you have that setting set i highlighted in the screenshot in Windows?

This setting is not checked on my system.

@romu70 can you do a quick screenshot of what you do have there?

Indeed the emphasis is back. I just restarted the computer this last week-end. But I didn't touch PowerToys.
Here is the screenshot.

We did update the lib. Good to see it is fixed.


Enhancement: Create Good Looking Modal which matches web application's UI

Fix the Color Mismatch and enhance the UI with respect to the application.
Can take help from #47

@devjainofficial please assign me

@n-keerthi-gayathri it's an urgent issue, please resolve it quick.

I made this, tell me if you need anything to be modified

Looks good, please add the pull request.


Broken Example (player doesnt get physics collider)

Version

Phaser Version: 3.16.2

Operating system: Windows

Browser: Chrome, but happens on other as well

Description
The player in this example seems to not be getting it's collider (pressing C to show debug before it falls off screen) Broken Example
Additional Information
Found via yassin#3588 who asked about it in the discord, I was unable to find a reason it was happening through a quick glance and so made this issue.

There seems to be an over-correction (at least for this example) in
https://github.com/photonstorm/phaser/blob/70b500cd2881dddd3a816a504c28ad1c692df96f/src/physics/arcade/World.js#L2168-L2173
It becomes visible when the TILE_BIAS is increased and the player is moved way over the tile during the collision (instead of passing though). Removing the if stabilizes it (although the real solution probably needs to refine it to apply it only to certain cases).

Had a quick look and the player collides happily with the 'ground' layer in the middle, just not the 'kenny' later on the left. Needs further investigation, but to do with varying tile sizes rather than anything else.

Thank you for submitting this issue (5 years ago!). We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.
👴🏻


Using autofill on the web causes a crash in the keyboard binding

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

flutter create semantics_sample
paste the code sample
flutter run -d chrome
fill in the username field
fill in the password field
5a) if now using Tab to go to the next field, an autofill dialog is shown
5b) the dialog is also shown when clicking the repeat password field
5c) the dialog is not shown when the focus leaves the autofill group, probably intended
Press the save button in the dialog
Reload the app (refresh in browser or restart with terminal)
Double click the password field
Select the saved password
A crash happens in the console (see the log)

Expected results
No crashes when using autofill.
Actual results
A crash when using autofill, but the app works anyway. Text field is autofilled.
Code sample
Code sample
import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';
import 'package:flutter/services.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  TextEditingController username = TextEditingController();
  TextEditingController newPassword = TextEditingController();
  TextEditingController repeatNewPassword = TextEditingController();
  TextEditingController password = TextEditingController();

  bool isNewUser = true;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      floatingActionButton: FloatingActionButton(onPressed: () => TextInput.finishAutofillContext()),
      body: AutofillGroup(
        child: Column(
          crossAxisAlignment: CrossAxisAlignment.start,
          children: <Widget>[
            const Text('Username'),
            TextField(controller: username, autofillHints: const [AutofillHints.username]),
            if (isNewUser) ...[
              const Text('Password'),
              TextField(obscureText: true, controller: newPassword, autofillHints: const [AutofillHints.newPassword]),
            ],
            if (isNewUser) ...[
              const Text('repeat password'),
              TextField(controller: repeatNewPassword, autofillHints: const [AutofillHints.newPassword]),
            ],
            if (!isNewUser) TextField(controller: password, autofillHints: const [AutofillHints.password]),
          ],
        ),
      ),
    );
  }
}

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
Error: Unexpected null value.
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49      throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 855:63  nullCheck
lib/_engine/engine/keyboard_binding.dart 372:38                                   [_handleEvent]
lib/_engine/engine/keyboard_binding.dart 582:7                                    handleEvent
lib/_engine/engine/keyboard_binding.dart 98:18                                    <fn>
lib/_engine/engine/keyboard_binding.dart 140:16                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall
Error: Unexpected null value.
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49      throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 855:63  nullCheck
lib/_engine/engine/keyboard_binding.dart 372:38                                   [_handleEvent]
lib/_engine/engine/keyboard_binding.dart 582:7                                    handleEvent
lib/_engine/engine/keyboard_binding.dart 101:18                                   <fn>
lib/_engine/engine/keyboard_binding.dart 140:16                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall
Error: Unexpected null value.
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49      throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 855:63  nullCheck
lib/_engine/engine/keyboard_binding.dart 372:38                                   [_handleEvent]
lib/_engine/engine/keyboard_binding.dart 582:7                                    handleEvent
lib/_engine/engine/keyboard_binding.dart 98:18                                    <fn>
lib/_engine/engine/keyboard_binding.dart 140:16                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall
Error: Unexpected null value.
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/errors.dart 294:49      throw_
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 855:63  nullCheck
lib/_engine/engine/keyboard_binding.dart 372:38                                   [_handleEvent]
lib/_engine/engine/keyboard_binding.dart 582:7                                    handleEvent
lib/_engine/engine/keyboard_binding.dart 101:18                                   <fn>
lib/_engine/engine/keyboard_binding.dart 140:16                                   loggedHandler
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 574:37  _checkAndCall
dart-sdk/lib/_internal/js_dev_runtime/private/ddc_runtime/operations.dart 579:39  dcall

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-x64, locale
    en-BE)
    • Flutter version 3.13.8 on channel stable at
      /Users/navaronbracke/Documents/flutter
    • Upstream repository git@github.com:navaronbracke/flutter.git
    • FLUTTER_GIT_URL = git@github.com:navaronbracke/flutter.git
    • Framework revision 6c4930c4ac (7 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/navaronbracke/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/navaronbracke/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.13.0

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.83.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.74.0

[✓] Connected device (2 available)
    • macOS (desktop) • macos  • darwin-x64     • macOS 14.0 23A344 darwin-x64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 118.0.5993.88

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the detailed report. Was able to replicate the error using stable and master versions.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.13.8, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.13.8 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 6c4930c4ac (5 days ago), 2023-10-18 10:57:55 -0500
    • Engine revision 767d8c75e8
    • Dart version 3.1.4
    • DevTools version 2.25.0
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.16.0-17.0.pre.40, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.16.0-17.0.pre.40 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 2f45754aab (18 minutes ago), 2023-10-26 00:51:43 -0400
    • Engine revision f844ab9333
    • Dart version 3.3.0 (build 3.3.0-56.0.dev)
    • DevTools version 2.28.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Deduplicating into https://github.com/flutter/flutter/issues/137148


Bug when generate regexp from objects [not string]

When regexp is an object the value is undefined.

unit tests... My bad


refactor GoogleCredentialsAccessTokenSupplier

These PR contains two refactorings:

throw exception if file at HELIOS_GOOGLE_CREDENTIALS cannot be read
This changes the behavior when the HELIOS_GOOGLE_CREDENTIALS environment variable is set to a file that does not exist or cannot be read from falling to Application Default Credentials to instead throw an exception.
If the environment variable contains invalid configuration, it seems better to throw an exception rather than silently use a different set of (possibly incorrect) credentials.
We have seen some confusing behavior internally arising from the fact that this class would load an unexpected set of credentials when the file at the environment variable could not be loaded.

introduce a AuthorizationHeaderSupplier interface
This is a refactoring of the GoogleCredentialsAccessTokenSupplier class and its usage in AuthenticationHttpConnector and HeliosClient.Builder to make those classes less tied to the Google Cloud OAuth2 token concepts.
The goal here is to make it much simpler to add non-Google implementations of this interface in the future without having to have other layers of Helios (such as AuthenticatingHttpConnector) aware of those implementation details.

Codecov Report

Merging #1210 into master will decrease coverage by 3.69%.
The diff coverage is 34.04%.

@@             Coverage Diff             @@
##             master    #1210     +/-   ##
===========================================
- Coverage     52.57%   48.87%   -3.7%
+ Complexity     1613      601   -1012
===========================================
  Files           268      103    -165
  Lines         13026     5076   -7950
  Branches       1505      771    -734
===========================================
- Hits           6848     2481   -4367
+ Misses         5658     2366   -3292
+ Partials        520      229    -291

#1210


Anthropic integration

As described in https://github.com/asteroidai/asteroid-python-sdk/issues/10
This pull request includes several changes to improve the functionality and structure of the asteroid-sdk package, particularly in handling different language models and supervision configurations. The most important changes include updates to the import statements, enhancements to the supervision decorators, and modifications to the API logger and supervision manager classes.
Updates to import statements:

README.md: Updated import statements to correctly reference asteroid_init from asteroid_sdk.registration.initialise_project.
run_openai.py: Renamed from run.py and adjusted import statements to correctly reference asteroid_init and asteroid_end from asteroid_sdk.registration.initialise_project.

Enhancements to supervision decorators:

run_anthropic.py: Added new supervision decorators and example functions for booking flights, getting weather, and booking hotels. Introduced tool_supervisor_decorator for more flexible supervision strategies.

Modifications to API logger and supervision manager:

src/asteroid_sdk/api/api_logger.py: Updated APILogger to handle both ChatCompletion and Message types, and introduced ModelProviderHelper for managing model-specific logic. [1] [2]
src/asteroid_sdk/api/asteroid_chat_supervision_manager.py: Enhanced AsteroidChatSupervisionManager to utilize ModelProviderHelper and refactored methods for better handling of tool calls and supervision contexts. [1] [2] [3] [4] [5] [6] [7]

Additional updates:

src/asteroid_sdk/api/supervision_runner.py: Included ModelProviderHelper and refactored the handling of tool calls from language model responses to support various model providers. [1] [2] [3] [4] [5]

With these changes the example examples/chat_supervision.py is not working. chat_supervisors  were removed from from asteroid_init  there seems to be no way to initialise the chat_supervisors that need to be passed to register_tools_and_supervisors

I took the liberty of adding support to chat_supervisors back and fixing one bug (parsing the message from the toolcall)
https://github.com/asteroidai/asteroid-python-sdk/pull/16/commits/b6d0285fc5d48b22dd4e00d850f81fce21944b9c
@tom-diacono if this violates some logic you created or intended to create, feel free to revert/make changes so we support chat_supervisors


🙈 Hidding System Test activities

This exercise is not defined yet. Hide to avoid confusion.
Many students ask about this exercise/activity as the content is empty and no clear actions to execute. It could be better not to show it until there is a clear activity to do.

@ckavili @springdo @eformat Comments? Every time a deliver the TL500 got the same question: "What should we do in System Test?, what is the goal of this step?
Until we don't provide an example/activity, we could skip it. WDYT?

The work is never done. This is a good way to explain that even TL500 is not finished !
and we get to use @springdo name in vein .. since HE PROMISED to do this section .. for over a year now ...

I Vote we keep it IN ... until the work is done ...

https://github.com/rht-labs/tech-exercise/issues/7

Ahaha I like how Mike put an evidence there to prove over a year🙈🙈 like Mike said, I enjoy joking around with @springdo but it's okay for me to comment those out for now as long as we don't forget to update the picture and everything :D

(sorry hit close by mistake 🙈)

I WILL DO THIS!!!
You guys just need to keep faith.... How about I try do it before the NA runs and if it's not done by then, then you can comment it out 🙏

That sound good! (not sure if time pressure ever worked on you though :p)

Team! I don't want to pressure anyone ... not now in Summer :smile:. I was only thinking about the students and facilitating their technical exercises. I am comfortable with the @eformat message about We are working on it, as we are an agile team so as you decide, accept or reject it.

no pressure @springdo

hy @ckavili i wonder if @springdo will bring us a christmas present on #192 ?!?

Ahhhhh @eformat I actually started this a few weeks ago but got side lined with other stuff.... I know the exercise works at least cuz I did a demo of it (by request) at the last run of the course I'm Dublin 😁
Perhaps if yous are nice Santa Spring will bring you a lovely sack of tests

no pressure..right @eformat? 😌

@springdo - pressure ? what pressure @ckavili ?

is this that time of the year? @eformat 🤔

y'all ready for this ....

erm --- toooo late https://github.com/rht-labs/tech-exercise/pull/275

this will be waiting for the PR to be accepted now ....

Great job @springdo !!! Now I can close this PR as you did the job and now the Pet Battle teams can enjoy with more exercises ... 🪅👏🪅👏🪅


[Retest after 4835] Select shipping cost automatically like express checkout does

Environment Details
Spartacus: feature/express-checkout-fr1 branch
Browser: chrome
Device: mac
Happens on: http://dev-com-21.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
Steps to Reproduce

Enable express checkout
Login.
Place an order (with 1 saved address and 1 saved payment)
Go to Myaccount -> Payment Details.
Delete the payment
Add a product to cart, and proceed to checkout -> On Step2 of checkout, the delivery mode is preselected for the user.
Add and save a payment method and place the order
Now go to MyAccount -> Address Book
Delete the address
Add a product to cart, proceed to chckout
Add and save an address

Actual Result
Now the delivery mode is not pre-selected.
Expected Result
It should be consistent.
Either the delivery mode should be preselected or not, for both scenarios:

when I have only 1 address saved, no payment.
when I have only 1 payment saved, no address

Tried to test this on dev10, but still seeing the issue. It will probably be resolved after #4835 is fixed.

Tested on dev10. It's fixed now.


PHOENIX-6273: Add support to handle MR Snapshot restore externally

https://issues.apache.org/jira/browse/PHOENIX-6273

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
14m 39s
4.x passed

+1 :green_heart:
compile
1m  2s
4.x passed

+1 :green_heart:
checkstyle
0m 43s
4.x passed

+1 :green_heart:
javadoc
0m 45s
4.x passed

+0 :ok:
spotbugs
3m  1s
phoenix-core in 4.x has 945 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 49s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

-1 :x:
checkstyle
0m 47s
phoenix-core: The patch generated 27 new + 709 unchanged - 4 fixed = 736 total (was 713)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 44s
the patch passed

+1 :green_heart:
spotbugs
3m 10s
the patch passed

_ Other Tests _

-1 :x:
unit
127m 40s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

163m 27s

Reason
Tests

Failed junit tests
phoenix.end2end.TableSnapshotReadsMapReduceIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1110

JIRA Issue
PHOENIX-6273

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 882e9d0ab522 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 1499989

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/testReport/

Max. process+thread count
5606 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 30s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
14m 39s
4.x passed

+1 :green_heart:
compile
1m  2s
4.x passed

+1 :green_heart:
checkstyle
0m 43s
4.x passed

+1 :green_heart:
javadoc
0m 45s
4.x passed

+0 :ok:
spotbugs
3m  1s
phoenix-core in 4.x has 945 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 49s
the patch passed

+1 :green_heart:
compile
1m  1s
the patch passed

+1 :green_heart:
javac
1m  1s
the patch passed

-1 :x:
checkstyle
0m 47s
phoenix-core: The patch generated 27 new + 709 unchanged - 4 fixed = 736 total (was 713)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 44s
the patch passed

+1 :green_heart:
spotbugs
3m 10s
the patch passed

_ Other Tests _

-1 :x:
unit
127m 40s
phoenix-core in the patch failed.

+1 :green_heart:
asflicense
0m 49s
The patch does not generate ASF License warnings.

163m 27s

Reason
Tests

Failed junit tests
phoenix.end2end.TableSnapshotReadsMapReduceIT

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1110

JIRA Issue
PHOENIX-6273

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux 882e9d0ab522 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 1499989

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/artifact/yetus-general-check/output/patch-unit-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/testReport/

Max. process+thread count
5606 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
14m 26s
4.x passed

+1 :green_heart:
compile
1m  0s
4.x passed

+1 :green_heart:
checkstyle
0m 44s
4.x passed

+1 :green_heart:
javadoc
0m 46s
4.x passed

+0 :ok:
spotbugs
3m  0s
phoenix-core in 4.x has 945 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 50s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

-1 :x:
checkstyle
0m 45s
phoenix-core: The patch generated 26 new + 710 unchanged - 3 fixed = 736 total (was 713)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 44s
the patch passed

+1 :green_heart:
spotbugs
3m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
128m  4s
phoenix-core in the patch passed.

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

161m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1110

JIRA Issue
PHOENIX-6273

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux c2997de1f048 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 1499989

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/testReport/

Max. process+thread count
5596 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 32s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ 4.x Compile Tests _

+1 :green_heart:
mvninstall
14m 26s
4.x passed

+1 :green_heart:
compile
1m  0s
4.x passed

+1 :green_heart:
checkstyle
0m 44s
4.x passed

+1 :green_heart:
javadoc
0m 46s
4.x passed

+0 :ok:
spotbugs
3m  0s
phoenix-core in 4.x has 945 extant spotbugs warnings.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
5m 50s
the patch passed

+1 :green_heart:
compile
1m  2s
the patch passed

+1 :green_heart:
javac
1m  2s
the patch passed

-1 :x:
checkstyle
0m 45s
phoenix-core: The patch generated 26 new + 710 unchanged - 3 fixed = 736 total (was 713)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
javadoc
0m 44s
the patch passed

+1 :green_heart:
spotbugs
3m  6s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
128m  4s
phoenix-core in the patch passed.

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

161m 10s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix/pull/1110

JIRA Issue
PHOENIX-6273

Optional Tests
dupname asflicense javac javadoc unit spotbugs hbaseanti checkstyle compile

uname
Linux c2997de1f048 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-personality.sh

git revision
4.x / 1499989

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/artifact/yetus-general-check/output/diff-checkstyle-phoenix-core.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/testReport/

Max. process+thread count
5596 (vs. ulimit of 30000)

modules
C: phoenix-core U: phoenix-core

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-PreCommit-GitHub-PR/job/PR-1110/2/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Links already created with hash strategy doesn't work with path strategy

Is there any solution to migrate from hash to path?
There are a lot of links of my web created with hash on linkedin, facebook, sent via email, sent via whatsap...
www.myweb.com/#/privacy
www.myweb.com/#/card
www.myweb.com/#/plans
If anybody clicks on one of these links, it wouldn't work on path strategy.
Is there any solution for these "already created" links to work now on path strategy?
Thanks!,

Hi :) Thanks for using the package and creating the issue @ismadev ❤
There is unfortunately no way to address this with Flutter's default path strategy feature (we faced the same issue). However, you should be able to read the URL on app start and set the initialRoute on your MaterialApp accordingly 🙂
import 'dart:html';

window.location.href;

Thanks! I will try it. ❤

Awesome. I will close this as this is not strictly related to the package.

If somebody has the same problem.
Here is a workaround:

If you are using "setPathUrlStrategy();" and the url resolved contains the hash and a path, the page will not load.
Uri.base.fragment contains the path, so you have to replace it in your generated route.
The RouteSettings of the generated route must contain the path.


Create a CTA button that is a link-to

In card builder, I found myself doing things like this:
<LinkTo
  @route="cards.card.edit.fields"
   @class="right-edge--configure-schema-link cs-component-cta secondary responsive cs-dark-cta" >

I stole the classes from the CTA button. We should create a CTA button that is a link-to instead, and replace any Link-Tos that have a class "cs-component-cta."

@burieberry do you have any thoughts on whether we should do this and what the approach should be?

@jenweber Yes, I think it's a good idea. I'm open to whichever approach seems easy and sturdy. To my horror, I saw a CTA component that's wrapping a link-to in Cardhost, and we gotta get rid of that.

@burieberry yeah, that causes problems. I fixed one of those here https://github.com/cardstack/cardstack/pull/1309/files


cms.utils.permissions - get_user_permission_level - AttributeError 'Page' has no attribute 'level'

As the title suggests, the "get_user_permission_level" function in cms.utils.permissions tries to return the level of the page and falls over with an AttributeError.  I don't think this is something that I have messed up (I am adding the CMS to an existing project that was on django 1.5, upgrading to django 1.8.8 in the process so I have to contend with the new migrations).
This is using version 3.2.0 and occurs on line 202.
I think that is is just a case of changing .level to .get_depth() but I don't know what knock on effects this will have.
Furthermore there are two lookups for __level in get_subordinate_users() and get_subordinate_groups() in the same file. (Let me know if you need new tickets raising for these)
def get_user_permission_level(user):
    """
    Returns highest user level from the page/permission hierarchy on which
    user haves can_change_permission. Also takes look into user groups. Higher
    level equals to lover number. Users on top of hierarchy have level 0. Level
    is the same like page.level attribute.

    Example:
                              A,W                    level 0
                            /    \
                          user    B,GroupE           level 1
                        /     \
                      C,X     D,Y,W                  level 2

        Users A, W have user level 0. GroupE and all his users have user level 1
        If user D is a member of GroupE, his user level will be 1, otherwise is
        2.

    """
    if (user.is_superuser or
            GlobalPagePermission.objects.with_can_change_permissions(user).exists()):
        # those
        return 0
    try:
        permission = PagePermission.objects.with_can_change_permissions(user).order_by('page__path')[0]
    except IndexError:
        # user isn't assigned to any node
        raise NoPermissionsException
    return permission.page.level #<----OFFENDING LINE

I just bumped into this.   Treebeard MP_Node has a "depth" attribute, so it looks like the fix is to simply replace level with depth.  What I can't understand is how this has escaped fixing all this time, and I see new code in develop that still references "level."  Am I missing something?
The level attribute is also referenced in some templates, possibly elsewhere.  I can provide a PR if someone can confirm that this hasn't been fixed some other way.

@divio/django-cms-core any feedback?

Confirmed. Will need to be backported to 3.1

I'm currently working on a fix for this on 3.3.x

Fixed by https://github.com/divio/django-cms/pull/5532


Handle new SAS key requiring encryptionScope , when version >= "2020-12-06"

Thanks for contribution! Please go through following checklist before sending PR.
Fix issue : https://github.com/Azure/Azurite/issues/1389
This PR is based on https://github.com/Azure/Azurite/pull/1393, with fix for account sas and test case.
Still pending one change: when Encryption Scope is specified in SAS, and not "-loose" should fail the request.
PR Branch Destination

For Azurite V3, please send PR to main branch.
For legacy Azurite V2, please send PR to legacy-dev branch.

Always Add Test Cases
Make sure test cases are added to cover the code change.
Add Change Log
Add change log for the code change in Upcoming Release section in ChangeLog.md.
Development Guideline
Please go to CONTRIBUTION.md for steps about setting up development environment and recommended Visual Studio Code extensions.

/azp run

/azp run

/azp run


Enhance WebContentLoader to Support Recursive Link Parsing and Custom Headers

Is your feature request related to a problem? Please describe.
I'm always frustrated when the WebContentLoader cannot parse content recursively from all internal links of a given URL. Additionally, it lacks the ability to customize request headers, which can lead to blocks by services like Cloudflare or web application firewalls when using Python HTTP clients.
Describe the solution you'd like
I would like the WebContentLoader to have:

A recursive parsing feature that, when enabled via a parameter, navigates all internal links from the main URL and parses the content of all these pages.
The ability to override default request headers, including user-agent and authentication headers, through optional parameters.

Describe alternatives you've considered
An alternative would be to create separate utilities for recursive link parsing and custom headers, but integrating these features directly into WebContentLoader will provide a more seamless and efficient solution.
Additional context
This enhancement will make the WebContentLoader more robust and versatile, allowing it to handle more complex web scraping scenarios and avoid blocks by various web services.

I need this too

Thanks for the suggestion Leandros. This feature is already on our roadmap, and we planned to make this happen later this month. Please stay tuned!


recommend: spectacle

can't really do much better than this app for tiling window management.
every alternative i've found is not gratis.

I have tried Spectacle and it is quite nice. However BetterTouchTool and this Alfred workflow does everything I need. So there is no need for me to keep another app running in the background. 🙂

asd

asd

asd


Add DDS Stress test pipeline

Description
Adds a pipeline for longer versions of DDS fuzz tests.
To keep costs reasonable but still give us a decent idea of when we introduce regressions, this pipeline is configured to only run each package's tests when there are files modified under affectedPaths. Like the real service stress pipeline, it uses the CI client package build pipeline as a trigger.
Sample run which runs both sequence and tree fuzz tests: here (this was before I set the reporter variable correctly; that can be seen to be working here. It's expected 2 tests fail, that matches what I see locally)
Sample run which runs only sequence fuzz tests: here. Notice that 'tree' job is skipped.
This PR doesn't make an attempt to fine-tune the config for these fuzz tests; that can be done individually later.

I don't have the knowledge to review the pipeline parts of this (thus I won't be the primary reviewer to approve this), but overall, I like the idea and the few code changes look good to me.


anchor links don't work

anchor links don't work using [descr](#link) doesn't work

fixed in https://github.com/threebotserver/publishingtools/commit/db928bfa7fd93e320c7860d3cea8b0246081275c


Avoid using root

https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#user

Thanks, this seems reasonable.  We can revisit this if the usual practise changes.