Maze solver example throws an error

Running the maze.jl file in the docs/examples directory gives the following error:
ERROR: LoadError: promotion of types Int64 and FixedPointNumbers.N0f8 failed to change any arguments
Stacktrace:
  [1] error(::String, ::String, ::String)
    @ Base ./error.jl:42
  [2] sametype_error(input::Tuple{Int64, FixedPointNumbers.N0f8})
    @ Base ./promotion.jl:374
  [3] not_sametype(x::Tuple{Int64, FixedPointNumbers.N0f8}, y::Tuple{Int64, FixedPointNumbers.N0f8})
    @ Base ./promotion.jl:368
  [4] promote
    @ ./promotion.jl:351 [inlined]
  [5] <(x::Int64, y::FixedPointNumbers.N0f8)
    @ Base ./promotion.jl:419
  [6] >(x::FixedPointNumbers.N0f8, y::Int64)
    @ Base ./operators.jl:378
  [7] (::var"#1#2")(x::ColorTypes.RGBX{FixedPointNumbers.N0f8})
    @ Main ~/Downloads/AgentsExampleZoo.jl-main/docs/examples/maze.jl:22
  [8] iterate
    @ ./generator.jl:47 [inlined]
  [9] _collect
    @ ./array.jl:744 [inlined]
 [10] collect_similar(cont::Matrix{ColorTypes.RGBX{FixedPointNumbers.N0f8}}, itr::Base.Generator{Matrix{ColorTypes.RGBX{FixedPointNumbers.N0f8}}, var"#1#2"})
    @ Base ./array.jl:653
 [11] map(f::Function, A::Matrix{ColorTypes.RGBX{FixedPointNumbers.N0f8}})
    @ Base ./abstractarray.jl:2867
 [12] initalize_model(map_url::String)
    @ Main ~/Downloads/AgentsExampleZoo.jl-main/docs/examples/maze.jl:22
 [13] top-level scope
    @ ~/Downloads/AgentsExampleZoo.jl-main/docs/examples/maze.jl:46
in expression starting at /Users/weili/Downloads/AgentsExampleZoo.jl-main/docs/examples/maze.jl:46

what's the full versions of packages you used? try updating and running again.

try updating and running again. AgentsExampleZoo always operates on latest stable Agents.jl version.

If updating all packages doesn't fix this, I have an idea for why it might be erroring, but it will take some investigation. Also might want to try changing the function in the map to x -> x.r > 0.0.
I'd also suggest using different environments for different projects with ]activate . and not adding everything to the global environment. It's one of the reasons Julia's package manager is so amazing!

Tried both. But it still didn't work. Thank you anyway. Appreciated it!

Does x -> Float64(x.r) > 0.0 work?

If updating all packages doesn't fix this, I have an idea for why it might be erroring, but it will take some investigation. Also might want to try changing the function in the map to x -> x.r > 0.0.
I'd also suggest using different environments for different projects with ]activate . and not adding everything to the global environment. It's one of the reasons Julia's package manager is so amazing, and often prevents headaches.

Tried both. Still didn't work. Thank you both anyway. Appreciated it.

Does x -> Float64(x.r) > 0.0 work?

I don't think so. See below:
ERROR: LoadError: MethodError: no method matching Float64(::FixedPointNumbers.N0f8)

What version of FixedPointNumbers do you have?

What version of FixedPointNumbers do you have?

Like this?
(AgentsExampleZoo) pkg> st FixedPointNumbers
     Project AgentsExampleZoo v0.1.0
      Status `~/Downloads/AgentsExampleZoo.jl-main/Project.toml` (empty project)

Use -m to get the version, st -m FixedPointNumbers. It will also help you to have a look at the docs of Julias package manager (it is really amazing, will make your workflow so much faster) https://pkgdocs.julialang.org/v1/  and DrWatson for making managing projects easier https://juliadynamics.github.io/DrWatson.jl/dev/

Use -m to get the version, st -m FixedPointNumbers. It will also help you to have a look at the docs of Julias package manager (it is really amazing, will make your workflow so much faster) https://pkgdocs.julialang.org/v1/ and DrWatson for making managing projects easier https://juliadynamics.github.io/DrWatson.jl/dev/

The FixedPointNumbers is not installed by calling instantiate in the project. So I manually added the following version:
(AgentsExampleZoo) pkg> st -m FixedPointNumbers
     Project AgentsExampleZoo v0.1.0
      Status `~/Downloads/AgentsExampleZoo.jl-main/Manifest.toml`
  [53c48c17] FixedPointNumbers v0.8.4

The problem still persists. The following variations are tried with no good result:
x -> Float64(x.r) > 0.0 ,x -> float64(x.r) > 0.0, x -> x.r > 0.0


[UPGRADE] Upgrade HAProxy to the latest version (2.4)

Is your feature request related to a problem? Please describe.
Our current HAProxy 2.2.2 has the following vulnerabilities:

CVE-2021-39240
CVE-2021-39242
CVE-2021-39241

Describe the solution you'd like
Update to the latest version. 2.4 is the latest right now.

DoD checklist

[ ] Changelog updated
[ ] COMPONENTS.md updated / doesn't need to be updated
[ ] Schema updated / doesn't need to be updated
[ ] Feature has automated tests
[ ] Automated tests passed (QA pipelines)

[ ] apply
[ ] upgrade

[ ] Idempotency tested
[ ] Documentation added / updated / doesn't need to be updated
[ ] All conversations in PR resolved
[ ] Solution meets requirements and is done according to design doc
[ ] Usage compliant with license
[ ] Backport tasks created / doesn't need to be backported

To track the latest version: https://github.com/haproxy/haproxy/tags


docs: update gitpod and codespaces for working with vite

The Issue
Gitpod had no example yet, Codespaces was a bit too detailed (and I updated my repos)
How This PR Solves The Issue
Add Gitpod, shorten Codespaces
Manual Testing Instructions
Automated Testing Overview

Related Issue Link(s)
Release/Deployment Notes

Ready to pull, thanks 👍


STO Sysdig integration DOC-2747

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/DOC-2747

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Sysdig integration isn't going out until the Step Palette work is done. Will write another draft when this work is done.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

@douglas-j-bothwell do you still need this? Branch flagged as stale.

Closing this. The Sysdig integration hasn't happened yet due to license negotiations...


Installing Unticked Options

I have options such as the box play button and vertical navbar unticked as I want to use Old Glory mainly to rid of the whats new section, but Old Glory installs these options anyways.

Check to see if the options are working as intended in the newest release: https://github.com/Jonius7/SteamUI-OldGlory/releases/tag/Release_<IP_ADDRESS>

Newest release fixed the box play button and vertical navbar being applied even though unticked, but the changes on the left side games list still apply even though I have 0 of those options applied.

Can you be more specific? There are additional options on the CSS Options -> Quick CSS page
Individual parts of the CSS tweaks can be enabled/disabled like this: http://imgur.com/a/PocNfPE

Thank you so much!
Editing the SCSS file like pictured works just as I want.
Sorry for the troubles!


Handle HTTP errors

[ ] Handle HTTP errors like 4xx or 5xx
[ ] Add content stubs for this purpose
[ ] Modules to adapt:

[ ] Debug
[ ] Gii
[ ] Inspector

It has been done


Oc 445 resolve too many parameters issues

Refactored methods and constructors in Platform with 6+ parameters.

SonarQube analysis reported 23 issues

 8 critical
 13 major
 2 minor

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L158: Make "authorizations" transient or serializable.
 Device.java#L165: Make "protocolInfo" transient or serializable.
 Device.java#L188: Make "deviceModel" transient or serializable.
 Device.java#L205: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

SonarQube analysis reported 28 issues

 8 critical
 14 major
 6 minor

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L158: Make "authorizations" transient or serializable.
 Device.java#L165: Make "protocolInfo" transient or serializable.
 Device.java#L188: Make "deviceModel" transient or serializable.
 Device.java#L205: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

SonarQube analysis reported 28 issues

 8 critical
 14 major
 6 minor

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L160: Make "authorizations" transient or serializable.
 Device.java#L167: Make "protocolInfo" transient or serializable.
 Device.java#L190: Make "deviceModel" transient or serializable.
 Device.java#L207: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

SonarQube analysis reported 24 issues

 4 critical
 14 major
 6 minor

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L165: Make "authorizations" transient or serializable.
 Device.java#L172: Make "protocolInfo" transient or serializable.
 Device.java#L195: Make "deviceModel" transient or serializable.
 Device.java#L212: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

SonarQube analysis reported 14 issues

 13 major
 1 minor

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 AbstractDomainResponseMessageProcessor.java#L86: Rename "messageType" which hides the field declared at line 55.
 AbstractDomainResponseMessageProcessor.java#L89: Rename "messageType" which hides the field declared at line 62.
 WebServiceMonitorInterceptor.java#L172: This block of commented-out lines of code should be removed.
 DomainResponseMessageProcessor.java#L89: Rename "messageType" which hides the field declared at line 62.

All is well.

SonarQube analysis reported 18 issues

 4 critical
 14 major

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L163: Make "authorizations" transient or serializable.
 Device.java#L170: Make "protocolInfo" transient or serializable.
 Device.java#L193: Make "deviceModel" transient or serializable.
 Device.java#L210: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

All is well.

SonarQube analysis reported 18 issues

 4 critical
 14 major

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 Device.java#L163: Make "authorizations" transient or serializable.
 Device.java#L170: Make "protocolInfo" transient or serializable.
 Device.java#L193: Make "deviceModel" transient or serializable.
 Device.java#L210: Make "deviceFirmwareFiles" transient or serializable.
 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.

All is well.

SonarQube analysis reported 13 issues

 13 major

Watch the comments in this conversation to review them.
Top 10 extra issues
Note: The following issues were found on lines that were not modified in the pull request. Because these issues can't be reported as line comments, they are summarized here:

 DeviceManagementService.java#L73: Remove this unused method parameter "messageType".
 DeviceManagementService.java#L134: Remove this unused method parameter "messageType".
 ConfigurationManagementService.java#L154: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 ScheduleManagementService.java#L67: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 DeviceManagementService.java#L351: The Cyclomatic Complexity of this method "applyFilter" is 28 which is greater than 10 authorized.
 DeviceManagementService.java#L370: Refactor this code to not nest more than 3 if/for/while/switch/try statements.
 AbstractDomainResponseMessageProcessor.java#L86: Rename "messageType" which hides the field declared at line 55.
 AbstractDomainResponseMessageProcessor.java#L89: Rename "messageType" which hides the field declared at line 62.
 WebServiceMonitorInterceptor.java#L172: This block of commented-out lines of code should be removed.
 DomainResponseMessageProcessor.java#L89: Rename "messageType" which hides the field declared at line 62.

All is well.


BUGFIX: Fix typo in configuration

The classname of the middleware in the configuration was a single character off. Sorry for that.

Thanks for fixing -> tagged with 4.0.1


Rework of pipeline

To check / do:

[x] -1 for IUs that don't reach threshold
[x] year_of_ius_passing_50pct_under_threshold seems wrong - I get a year if only one IU passes under the threshold - because it takes the max year that isn't NA rather than giving a na result for any na found.
[ ] Add a LKG test for oncho
[x] ~Remove age start and age end columns~
[ ] Make sure LKG  test includes a country that reaches the threshold at some point in at least 50% of runs
[ ] Delete the lock file for now (didn't fix issue it was trying to fix)

Going to address the following in follow up PR as this has got too big to sensibly review:

[ ]  Reading in population data (currently assumine 100 IUs per conutry, and each has a population of 10000)
[ ] disease specific thresholds (all using 0.01)


hacks for running (and screenshotting) the examples in CI on a github runner

Objective

Enable capturing screenshots of all examples in CI on a GitHub runner

Solution

Shorten duration of a run
Disable desktop_app mode - as there isn't any input in CI, examples using this take way too long to run
Change the default ClusterConfig - the runner are not able to do all the clusters with the default settings
Send extra WindowResized events - this is needed only for the split_screen example, because CI doesn't trigger that event unlike all the other platforms

moved to git patch, thanks for the idea! it makes it a lot clearer than my sed commands

I would like to merge this PR before the 0.12 to write a more complete story for the blog post. It already has the two approvals needed, but the last commit hasn't been reviewed yet. It adds a patch for window creation to ensure its position is always the same on windows, to be able to have a predictable cursor position in the window.
@rparrett or @nicopap (or someone else), could you give this a new approval? thanks!

thanks!


xfce.gigolo: 0.5.1 -> 0.5.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for xfce.gigolo is: "A frontend to easily manage connections to remote filesystems"
meta.homepage for xfce.gigolo is: "https://gitlab.xfce.org/apps/gigolo/about"
meta.changelog for xfce.gigolo is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2/bin/gigolo passed the binary check.

/nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2/bin/.gigolo-wrapped passed the binary check.

2 of 2 passed binary check by having a zero exit code.

2 of 2 passed binary check by having the new version present in output.

found 0.5.2 with grep in /nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2

found 0.5.2 in filename of file in /nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2

directory tree listing: https://gist.github.com/c4642e90eb3bde49866bf3eeeb45cd7c

du listing: https://gist.github.com/04b24e847a26bab8af9e823b36f8c16d

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
xfce.gigolo

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A xfce.gigolo https://github.com/r-ryantm/nixpkgs/archive/bbb8f790cdf29a0f6c90693ad5fef2a6b63565fa.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2
ls -la /nix/store/kbym0ycjwgx0gba87z29hxml8hbjrpd9-gigolo-0.5.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

xfce.gigolo

Maintainer pings

Result of nixpkgs-review pr 117561 at bbb8f790 run on x86_64-linux 1

1 package built successfully:

xfce.gigolo

2 suggestions:

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near lib/attrsets.nix:362:7:
    |
362 |       value = f name (catAttrs name sets);
    |       ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near lib/attrsets.nix:362:7:
    |
362 |       value = f name (catAttrs name sets);
    |       ^


[MINOR][DOC] Fix comments of ConvertToLocalRelation rule

What changes were proposed in this pull request?
There are some comments issues left when ConvertToLocalRelation rule was added (see #22205/SPARK-25212). This PR fixes those comments issues.
How was this patch tested?
N/A

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Test build #99909 has started for PR 23273 at commit dfd0f71.

Test build #99909 has finished for PR 23273 at commit dfd0f71.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please.

Test build #99944 has started for PR 23273 at commit dfd0f71.

Test build #99944 has finished for PR 23273 at commit dfd0f71.

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

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

Merged build finished. Test PASSed.

Test build #100006 has started for PR 23273 at commit 1cca847.

Test build #100006 has finished for PR 23273 at commit 1cca847.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please.

Test build #100032 has started for PR 23273 at commit 1cca847.

Test build #100032 has finished for PR 23273 at commit 1cca847.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

retest this please.

Test build #100054 has started for PR 23273 at commit 1cca847.

@srowen The build failed twice because of the same reason. It seems we ran into SparkR CRAN feasibility check server problem, which blocks PR build.

retest this please.

Test build #100075 has started for PR 23273 at commit 1cca847.

Test build #100075 has finished for PR 23273 at commit 1cca847.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #100082 has started for PR 23273 at commit 1cca847.

Test build #100082 has finished for PR 23273 at commit 1cca847.

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

Merged build finished. Test PASSed.

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

Merged to master

Thank you! @srowen


Convert from CoffeScript to ES6

Converts to ES6 and:

add tests to ensure no regressions
add browser demo to test rendering
use prettier to format code

It's opens the doors to improve png.js to fix bugs like https://github.com/foliojs/pdfkit/issues/926

@devongovett can you look at this?

@devongovett
Can you merge this or give the access rights so i can do myself?


Suppress formation not found error message when installing DV

Error message shown in CP4D status file when deploying DV:
Error from server (NotFound): formations.db2u.databases.ibm.com "ibm-dmc-1667656879339494-redis" not found
Error from server (NotFound): formationlocks.db2u.databases.ibm.com "ibm-dmc-1667656879339494-redis" not found

Suppress this message.

Error was in CPDemo framework, not deployer.


fix(#229): fixed formly-form model changes

Current coverage is 85.49% (diff: 0.00%)

Merging #238 into master will decrease coverage by 0.06%

@@             master       #238   diff @@
==========================================
  Files            18         18
  Lines           907        910     +3
  Methods         204        203     -1
  Messages          0          0
  Branches        281        283     +2
==========================================
+ Hits            776        778     +2
- Misses          131        132     +1
  Partials          0          0

Powered by Codecov. Last update 1e90ed0...b8003a9


feat: solve_by_elim using (attributes)

I found the following example where the attribute functionality doesn't seem to work -- any ideas?
import Mathlib.Tactic.SolveByElim

theorem mul_le_mul_of_nonneg_right [Mul α] [Zero α] [LE α] {a b c : α} (h : b ≤ c) (a0 : 0 ≤ a) :
    b * a ≤ c * a :=
  sorry

attribute [dummy_tag_attr] mul_le_mul_of_nonneg_right

example {x : Int} : 12 * x ^ 2 ≤ x * x ^ 2 := by
  apply_rules using dummy_tag_attr ; sorry -- `apply_rules` does nothing

example {x : Int} : 12 * x ^ 2 ≤ x * x ^ 2 := by
  apply_rules [mul_le_mul_of_nonneg_right] <;> sorry -- `apply_rules` does something

bors r+


Modern gem build and travis configuration

use bundler
minitest instead of test/unit
simplify version to a string
travis ci config
remove jeweler

Hooray for Travis!

@mfazekas How does this look?


Add Sega Mark III icons to the retrosystem icon theme.

This theme has so meny icons that allows me to create diferent playlists for diferent versions of the consoles or arcades genres, decreasing the size of the lists. Would be nice have icons for separate the japaneses games from the master system like the systematic theme has.
Thanks in advance, and nice work.
https://segaretro.org/Sega_Mark_III

It's already there, they are the same thing essentially that is why it has both names...
Sega - Master System - Mark III.png
https://github.com/libretro/retroarch-assets/blob/master/xmb/retrosystem/png/Sega - Master System - Mark III.png

@Wellvergton i have made them, they are on my repo for the time being, i'll make a pr when i finish some other stuff i have pending...

thanks @alfrix, nice job.

Request attended, issue closed.


Fix issue with Get-Process -Module failing to stop when piped to Select-Object

PR Summary
Previously when running Get-Process -Module and piping to Select-Object, you would receive this error:

Where the command succeeds, but the upstream output is not halted and the Get-Process: Cannot enumerate the modules of the "pwsh" process. non-terminating error is included.
To fix this, I added another clause to catch PipelineStoppedException from WriteObject, and rethrow error, which omits the error message completely.

Also added a Pester test to verify this.

PR Context
Fix #15117

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

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

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

Breaking changes

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

[ ] Experimental feature name(s):

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

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

Tooling

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

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

[ ] Issue filed:

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

[ ] Issue filed:

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

[ ] Issue filed:

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

[ ] Issue filed:

Thanks for your contribution @ArmaanMcleod!


Automated cherry pick of #9793: feat(region): server sku os_arch & cpu_arch checking

Cherry pick of #9793 on release/3.6.
#9793: feat(region): server sku os_arch & cpu_arch checking

Codecov Report

Merging #9795 (331d9d2) into release/3.6 (b9d30c0) will increase coverage by 2.20%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.6   #9795       +/-   ##
===============================================
+ Coverage         5.86%   8.06%    +2.20%
===============================================
  Files              828     107      -721
  Lines           129133   12976   -116157
===============================================
- Hits              7577    1047     -6530
+ Misses          120876   11809   -109067
+ Partials           680     120      -560

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.20%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/eval_context.go
37.00% <0.00%> (-1.15%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.86% <0.00%> (-1.03%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.09%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/vnic.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/network.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/notifier.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/prepare.go

pkg/compute/models/usage.go

... and 614 more

Continue to review full report at Codecov.

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

Codecov Report

Merging #9795 (331d9d2) into release/3.6 (b9d30c0) will increase coverage by 2.20%.
The diff coverage is 0.00%.

@@               Coverage Diff               @@
##           release/3.6   #9795       +/-   ##
===============================================
+ Coverage         5.86%   8.06%    +2.20%
===============================================
  Files              828     107      -721
  Lines           129133   12976   -116157
===============================================
- Hits              7577    1047     -6530
+ Misses          120876   11809   -109067
+ Partials           680     120      -560

Flag
Coverage Δ

aFlag
8.06% <0.00%> (+2.20%)
:arrow_up:

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

Impacted Files
Coverage Δ

pkg/apigateway/handler/auth.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/eval_context.go
37.00% <0.00%> (-1.15%)
:arrow_down:

pkg/monitor/alerting/rule.go
1.86% <0.00%> (-1.03%)
:arrow_down:

pkg/multicloud/esxi/manager.go
0.61% <0.00%> (-0.09%)
:arrow_down:

pkg/multicloud/esxi/host.go
0.77% <0.00%> (-0.01%)
:arrow_down:

pkg/multicloud/esxi/vnic.go
0.00% <0.00%> (ø)

pkg/multicloud/esxi/network.go
0.00% <0.00%> (ø)

pkg/monitor/alerting/notifier.go
0.00% <0.00%> (ø)

pkg/baremetal/tasks/prepare.go

pkg/compute/models/usage.go

... and 614 more

Continue to review full report at Codecov.

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


[ts] Cannot find module './<>.module.scss'.

Category - Bug
I have the module.scss file in the same place where it is referred . But I get error [ts] Cannot find module './GraphConsumer.module.scss' in the .tsx file in components folder. The same for AadHttpClient import { AadHttpClient } from "@microsoft/sp-http". Can you please help me in solving

When you reference the scss file like './GraphConsumer.module.scss'; you are actually referencing the GraphConsumer.module.scss.ts file that gets generated when you build it (gulp serve) so it will often show an error in the editor until you do the initial build.
Could you provide more details about the 2nd issue with AadHttpClient. What version of SPFx are you using? Thanks!

Hi,
We actually encountered the same issue, scss module not being recognized. What is strange is that when generating the project from scratch, everything works fine, but checking out the very generated project from repo, installing dependencies and running gulp serve throws this:
[16:47:11] Error - typescript - src/webparts/testProject/components/testProject.tsx(2,20): error TS2307: Cannot find module './testProject.module.scss'.

Modifying and saving the scss file however solves the problem and the error disappears :/


Remove the PNG examples from SBOL Visual Ontology

The PNG examples do not work. The collective decision is to remove the PNG examples and leave the SVG examples.
Closes #188

@jamesscottbrown I thought you were going to run a SVG to PNG converter to get the PNG examples

I'll set up PNG generation instead.


Include location of the memory

Closes #384
Closed the previous PR #431 as it was way behind in terms of commits from main and to avoid any confusions.
To show static map of the coordinates in the app, I've used one of the APIs of Google Maps. It generates a static map with the coordinates. Google Maps gives out $200 credits per month for free. So we shouldn't be incurring any cost till 100,000 calls for a month.
https://developers.google.com/maps/documentation/maps-static/usage-and-billing
https://github.com/user-attachments/assets/edd91a91-4315-401a-8566-53d3549d1b17

@josancamon19 I've tested it and it is ready for review.

Notes

When I click on the app, does this opens maps app?
We should location below plugins, I think it's nice, but not that important for occupying user focus before overview. Maybe even toggled.

It'd be amazing if, we could store in the location object, an address too, and other related data to location from google maps, maybe address and placeId.
https://developers.google.com/maps/documentation/geocoding/overview
The idea of this feature is to later let the user determine locations, and chat with conversations at home, etc... Filter conversations by place too.
So ideally the location object would be in the db as a separate.
And later different memories could match the same location. Seems like a ManyToOne relationship to me, even if rn, will be OneToOne.
@mdmohsin7

When I click on the app, does this opens maps app?

Yes when you click on the map image, it will open the coordinates in Google Maps (on Android) and Apple Maps (on iOS).

We should location below plugins, I think it's nice, but not that important for occupying user focus before overview. Maybe even toggled.

Understood! Will change the image's position to below plugins

The idea of this feature is to later let the user determine locations, and chat with conversations at home, etc... Filter conversations by place too.

Got it! Will update and create a separate location object to include all the necessary fields.

Created a geolocation object with OneToOne relation to Memory
Moved map widget to below plugin responses
Refactor map related widgets
Geocoding API is used to get user's address, place id and location type

https://github.com/user-attachments/assets/b7e41c3a-671a-465f-afdc-ad799e54b01a


[Input] Input and button does not align

If you place an .ui.input element next to a .ui.button element they don't align. The button is slightly smaller than the input (36px compared to 37px for the input) and they don't align vertically.

See this: http://codepen.io/anon/pen/dMPGgO
I am using Chrome 48 on Mac OSX Yosemite

Button draws its border with box-shadow, while input draws it with border, you can vertically align them by specifying vertical-align: top

Of course you can solve it by aligning them yourself. I just didn't see why they don't align as is.
However, I did some more digging and it might just be an issue with Chrome and Safari. It aligns in Firefox and if I add a value or a placeholder to the Semantic UI input it aligns with the button in Chrome and Safari as well.
The only thing now bothering me is that the button is smaller than the input. Both Chrome and Safari shows the input as 37px (including the border) and the button is 36px. Firefox has the input at 38px. The box-shadow on the button seem to be inset with a spread radius of 1px so it is drawn inside the block.
Chrome 48 OSX Yosemite

Firefox 44.0.2 OSX Yosemite

basic button draws its box shadow using inset so that it can overlay the background, allowing for shading with RGBA, unfortunately this does mean it is now shorter than the standard button.

Hi, not sure if this is related or not, but, it appears that when a placeholder attribute is placed in an input that is adjacent to another input, a similar result occurs.
Chrome Version 54.0.2840.71 OSX 10.9.5

https://jsfiddle.net/sgy9g6bg/10/


Issue/nte string index out of bound

Fix for issue: StringIndexOutOfBoundsException is thrown while converting NTE segments with additional dash #512
In HL7ToFHIRConverter class, Method 'getHl7Message' has code for logging HL7 message structure. In order to optimize the content. It takes subset of each line based on first occurrence of "-" and 5 chars more. Issue occurs when there are multiple repeating segments like NTE and HL7Message.printStructure does not follow {Segment} - start prefix on these repeating segments. and these sgement has "-" in content.
For now added fail-safe check if indexof Dash + 5 chars is more then length of line then take line length as input.

create new pull request with proper commit message.


Docs 2

Working on the migration guide and other docs
TODO:

[x] Migration guide
[x] Hardcoded examples should link to example code that is tested (this was already done, AFAICT)
[x] Address #699
[x] Discuss: should we remove references to non-v2, apart from the migration guide and link to the book for v1? (Off-github conclusion: yes)
[x] RTIC {vs,and} Embassy (important: distinction between embassy runtime & HALs)
[x] More descriptive docs on how to implement & PR implementations of Monotonic to rtic-monotonics

@datdenkikniet What you think about similar PR for this repo https://github.com/rust-embedded/book/pull/356/ ?

I think that it's a nice idea, but also that the amount of overhead it adds to the docs is not worth it at this stage.

Just writing the English docs will take more effort.

We add a hefty layer of indirection.
There have are few contributors willing to write/capable of writing docs, making it more difficult is not likely to improve that.

Whenever we do an update to the docs, we need to poke whoever is maintaining the other language(s)

What do we do if the person responsible for maintaining the docs in a different language no longer wants to contribute?

If there is a clearer use-case for docs in different languages that can't be satisfied by using google translate or an AI powered translation service, it would be easier to motivate.
I have no idea how much benefit translations to different languages would actually make, so it's quite difficult to judge either way. I only know that doing this PR was a chore as-is, and it would've taken a while longer if there were more steps to it.

Hey, I saw this linked on rust-embedded/book#356 :smile:

As is, there are few contributors willing to write/capable of writing docs, making it more difficult is not likely to improve that.

It's certainly difficult to find people who like to write documentation. In Comprehensive Rust, we've taken the approach to let the translations trail the English documentation: we're adding/removing stuff from the English documentation without regard for the translations — it's up to them to keep up if they want.
The result has been that the Brazilian Portuguese translation is in a rough shape — every time we change a paragraph of text, the translation of that one paragraph falls back to the English text. So it requires a very dedicated team of volunteer translators to keep things up to date.
However, I don't feel it puts additional work on the people who contribute to the source language.

Thank you for the insight @mgeisler! I seem to have misunderstood and was expecting gettext to error out if it can't translations for a specific sentence. Given that that's not the case, my arguments don't hold as much water :)
Then it's "just" setting up the system and figuring out if we want a threshold for how much un-translated text we're willing to tolerate.

Thank you for the insight @mgeisler! I seem to have misunderstood and was expecting gettext to error out if it can't translations for a specific sentence. Given that that's not the case, my arguments don't hold as much water :)

:smile: You could still argue that it might look weird for the project to have a set of translations in various stages of decay — that's certainly a concern for me with Comprehensive Rust. It's published by Android/Google, so I ultimately want it to look professional.

Then it's "just" setting up the system and figuring out if we want a threshold for how much un-translated text we're willing to tolerate.

Supporting this would be a matter of "a little scripting". That is, one would need to reuse an old translation if the current translation has degraded too far. I haven't yet written this for my own use, but I've at least recorded the need for this here: https://github.com/google/mdbook-i18n-helpers/issues/16.


Question regarding the new APOR links came in via HMDA Help

Could use help from a developer to help answer this: "Is there a FQDN for these? Or what do we need to whitelist in our firewall to get this to work. Whitelisting these specific url's does not work due to
the load balancing behind them. "

HMDA Help Case #180220-2872447

Receiving HMDA Help alerts on aging case. Followed up on Mattermost for assistance.

Received a similar question via another case. Is this related?
[REDACTED] was notified by [REDACTED] that the location of the APOR downloads has changed. The vendor provided URLs for the new locations, however our Firewall rules require IP addresses instead of a URL.
Please provide the respective IP addresses for the new APOR fixed table and adjustable tables ASAP so our Firewall Rules can be changed:
https://s3.amazonaws.com/cfpb-hmda-public/prod/apor/YieldTableFixed.txt
https://s3.amazonaws.com/cfpb-hmda-public/prod/apor/YieldTableAdjustable.txt


python3Packages.pubnub: 5.5.0 -> 6.0.0

Motivation for this change
https://github.com/pubnub/python/releases/tag/v6.0.0
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/)
22.05 Release Notes (or backporting 21.11 Release notes)

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

[x] Fits CONTRIBUTING.md.

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

7 packages built:

home-assistant-component-tests.august
python310Packages.pubnub
python310Packages.pubnubsub-handler
python310Packages.yalexs
python39Packages.pubnub
python39Packages.pubnubsub-handler
python39Packages.yalexs


v2.2 or v2.3 ?

Hi,
I made a git pull
however still display v2.2
Thank you for your help

Strange, the tool is updated, all files are in place.
Maybe try to re-download the tool via git clone?

I recommend you re-download the tool using git clone and you won't have the problem. It's very simple.

Hi,
$ git status
On branch main
Your branch is up to date with 'origin/main'.
Untracked files:
(use "git add ..." to include in what will be committed)
above.egg-info/
build/
dist/
nothing added to commit but untracked files present (use "git add" to track

A new directory then git clone https://github.com/wearecaster/Above  and sudo python3 setup.py install
That's Ok:  Version 2.3
However why the git pull was not a success I don't know
Thanks


Unable to query translation information using list=cxpublishedtranslations

When I use code
from pywikiapi import wikipedia
# Connect to Telugu Wikipedia
site = wikipedia('te')

# Iterate over all query results as they are returned
# from the server, handling continuations automatically.
#
#gets entries of a category
for r in (site.query(list='cxpublishedtranslations',limit=10,format='json',utf8=1,from='en',to='te',)):
   print(r)

The error is
>  File "<ipython-input-12-243fed8fdae5>", line 9
>     for r in (site.query(list='cxpublishedtranslations',limit=10,format='json',utf8=1,from='en',to='te',)):
>                                                                                ^
> SyntaxError: invalid syntax
>

Looks like the parameter from is not being recognized

The working api  for the above  is https://te.wikipedia.org/wiki/ప్రత్యేక:ApiSandbox#action=query&format=json&list=cxpublishedtranslations&utf8=1&from=en&to=te&limit=max&offset=

@arjunaraoc Here is a trick you can use to pass keyword arguments as parameter names:
for r in (site.query(list='cxpublishedtranslations',limit=10,format='json',utf8=1, **{'from': 'en'},to='te',)):
   print(r)

(Note the **{'from': 'en'} part)
I believe the above syntax requires Python 3.5+. In earlier versions the dictionary unpacking needs to be the last part of the call signature.


Add YAML format output

Fixes https://github.com/hugovk/norwegianblue/issues/137.
For example:
$ eol python --format yaml
- cycle: '3.11'
  eol: '2027-10-24'
  latest: 3.11.2
  latest release: '2023-02-07'
  release: '2022-10-24'
- cycle: '3.10'
  eol: '2026-10-04'
  latest: 3.10.10
  latest release: '2023-02-07'
  release: '2021-10-04'
- cycle: '3.9'
  eol: '2025-10-05'
  latest: 3.9.16
  latest release: '2022-12-06'
  release: '2020-10-05'
- cycle: '3.8'
  eol: '2024-10-14'
  latest: 3.8.16
  latest release: '2022-12-06'
  release: '2019-10-14'
- cycle: '3.7'
  eol: '2023-06-27'
  latest: 3.7.16
  latest release: '2022-12-06'
  release: '2018-06-26'
- cycle: '3.6'
  eol: '2021-12-23'
  latest: 3.6.15
  latest release: '2021-09-03'
  release: '2016-12-22'
- cycle: '3.5'
  eol: '2020-09-13'
  latest: 3.5.10
  latest release: '2020-09-05'
  release: '2015-09-12'
- cycle: '3.4'
  eol: '2019-03-18'
  latest: 3.4.10
  latest release: '2019-03-18'
  release: '2014-03-15'
- cycle: '3.3'
  eol: '2017-09-29'
  latest: 3.3.7
  latest release: '2017-09-19'
  release: '2012-09-29'
- cycle: '2.7'
  eol: '2020-01-01'
  latest: 2.7.18
  latest release: '2020-04-19'
  release: '2010-07-03'
- cycle: '2.6'
  eol: '2013-10-29'
  latest: 2.6.9
  latest release: '2013-10-29'
  release: '2008-10-01'

Looks really cool :sunglasses:

:thinking: COuld you share an output example while querying for more than a single product :grey_question: :pray:

Sure:
$ eol python drupal --format yaml
python:
- cycle: '3.11'
  eol: '2027-10-24'
  latest: 3.11.2
  latest release: '2023-02-07'
  release: '2022-10-24'
- cycle: '3.10'
  eol: '2026-10-04'
  latest: 3.10.10
  latest release: '2023-02-07'
  release: '2021-10-04'
- cycle: '3.9'
  eol: '2025-10-05'
  latest: 3.9.16
  latest release: '2022-12-06'
  release: '2020-10-05'
- cycle: '3.8'
  eol: '2024-10-14'
  latest: 3.8.16
  latest release: '2022-12-06'
  release: '2019-10-14'
- cycle: '3.7'
  eol: '2023-06-27'
  latest: 3.7.16
  latest release: '2022-12-06'
  release: '2018-06-26'
- cycle: '3.6'
  eol: '2021-12-23'
  latest: 3.6.15
  latest release: '2021-09-03'
  release: '2016-12-22'
- cycle: '3.5'
  eol: '2020-09-13'
  latest: 3.5.10
  latest release: '2020-09-05'
  release: '2015-09-12'
- cycle: '3.4'
  eol: '2019-03-18'
  latest: 3.4.10
  latest release: '2019-03-18'
  release: '2014-03-15'
- cycle: '3.3'
  eol: '2017-09-29'
  latest: 3.3.7
  latest release: '2017-09-19'
  release: '2012-09-29'
- cycle: '2.7'
  eol: '2020-01-01'
  latest: 2.7.18
  latest release: '2020-04-19'
  release: '2010-07-03'
- cycle: '2.6'
  eol: '2013-10-29'
  latest: 2.6.9
  latest release: '2013-10-29'
  release: '2008-10-01'

drupal:
- cycle: '10.0'
  eol: '2023-12-13'
  latest: 10.0.3
  latest release: '2023-02-01'
  release: '2022-12-15'
  support: '2023-06-21'
- cycle: '9.5'
  eol: '2023-11-01'
  latest: 9.5.3
  latest release: '2023-02-01'
  release: '2022-12-15'
  support: '2023-06-21'
- cycle: '9.4'
  eol: '2023-06-21'
  latest: 9.4.11
  latest release: '2023-02-01'
  release: '2022-06-15'
  support: '2022-12-14'
- cycle: '9.3'
  eol: '2022-12-14'
  latest: 9.3.22
  latest release: '2022-09-28'
  release: '2021-12-08'
  support: '2022-06-15'
- cycle: '9.2'
  eol: '2022-06-15'
  latest: 9.2.21
  latest release: '2022-06-10'
  release: '2021-06-16'
  support: '2021-12-08'
- cycle: '9.1'
  eol: '2021-12-08'
  latest: 9.1.15
  latest release: '2021-11-24'
  release: '2020-12-02'
  support: '2021-06-16'
- cycle: '9.0'
  eol: '2021-06-16'
  latest: 9.0.14
  latest release: '2021-05-25'
  release: '2020-06-03'
  support: '2020-12-02'
- cycle: '8.9'
  eol: '2021-11-02'
  latest: 8.9.20
  latest release: '2021-11-17'
  release: '2020-06-03'
  support: '2020-12-01'
- cycle: '8.8'
  eol: '2020-12-01'
  latest: 8.8.12
  latest release: '2020-11-25'
  release: '2019-12-04'
  support: '2020-06-03'
- cycle: 7 LTS
  eol: '2023-11-01'
  latest: '7.94'
  latest release: '2022-12-14'
  release: '2011-01-05'
  support: '2015-11-19'

Both pass validation at https://www.yamllint.com/

It looks really cool :sunglasses:

:fireworks:
BTW... cooleagues at the office eol really cool... it becomes everyday a bit more a part of our stack at opt-nc

Nice to hear! Also huge thanks for all your work and the rest of the team's at https://endoflife.date!

😘


Component 12: Not dynamic

There is output that watches the input value, but when we touch the input value, that output won't be updated.

It is going to be fixed by considering v-model on output.


Adding Testnet Beta genesis block

The start of a new beginning 😁

For the sake of time sensitivities, I will update the comment myself in a commit and merge this PR.


CASMINST-4471 fix nexus init/setup to work with newer podman version

Summary and Scope
Fixes the nexus init script.  nexus is now nexus3.  This also removed the -d flag in the podman command since it is no longer valid syntax.
Issues and Related PRs

Resolves CASMINST-4471
Merge with https://github.com/Cray-HPE/metal-basecamp/pull/12

Testing
Manually tested these changes and I was able to start nexus.
Tested on:

#redbull

Risks and Mitigations
Low, it's broken now.
Pull Request Checklist

[x] Version number(s) incremented, if applicable
[x] Copyrights updated
[x] License file intact
[x] Target branch correct
[x] Testing is appropriate and complete, if applicable

Reviewed it. Seems like a fine update. I wasn't able to find anything that stood out as incorrect.


🐛 [cloud_firestore] Add sum and average operators

What feature would you like to see?
The native SDKs for Firestore on iOS, Android, and Web support the new sum and average aggregation operations. Can you make these operations available in Flutter too?

It would really beneficial and helpful as counters are a tedious process to achieve this. Apparently sum and average are 2 main queries by which analytics could be maintained.

Thanks @russellwheatley! No idea why I couldn't find that one when I searched for it. 👍


Annotation with both SnpEff and VEP

What it the difference between the "merge" option and the "SnpEff,VEP"? Will I see different results?

I'm guessing the documentation wasn't clear enough.
Sorry about that.
If you specify snpeff,vep, you'll get your VCFs annotated by snpEff, and by VEP, meaning one different annotation for each annotator.
If you specify merge, you'll get your VCFs first annotated by snpEff, then the resulting VCFs will be annotated by VEP, meaning final VCFs annotated by both annotators.
https://github.com/SciLifeLab/Sarek/blob/master/docs/ANNOTATION.md


PHP Version Compatibility

Issue Summary
In your documentation, you don't seem to state anywhere (that I've seen) which version of PHP is required to use this library and, unfortunately, I have a client who is using an old version of PHP (5.3.3) which doesn't support the new PHP Array short form [ 'email' => $this->getEmail() ] (Mail.php:39 in your 5.0.4 release).
Please can you at least either (a) document the minimum required PHP version for the library to work or (b) not use backwards-incompatible code? I'm happy to create a PR if you'd like me to fix these issues.
Steps to Reproduce

Install SendGrid PHP API r5.0.4
Create a simple file which executes $sg = new \SendGrid($apiKey);
Execute the file

This is a bit disappointing on both the documentation front and on the build side: I appreciate that we all want nice, tidy and efficient code but, so far, I'm finding this unusable without a bunch of work and I'd like to use your library but you've explicitly excluded a whole bunch of users.
Technical details:

sendgrid-php Version: 5.0.4
PHP Version: 5.3.3

Turns out the reason for this issue is simply usage of the new Array form and that your composer.json file is incorrect in regard to the version of PHP that is required to use this library.
I will attempt to correct this on 5.0.3 (as your composer.json says it requires PHP >= 5.3) and see if I can get it working and create PR if required/desired.

Hello @ilithium,
Thanks for the feedback and offer to assist!
This library will only support versions that are not end of life. Currently, that means versions 5.6 and above.
That said, I'm sure this community would appreciate a fork that supports older versions and we would be happy to link to it.
I will be adding the version requirement to the README under the dependencies section for better visibility.


feat: add tests to not-earthly and fix ECR upload

I cannot see cargo fmt check in the workflow. It is present in Earthly.


lightgbm parameters by feature? ex: categoricals/high cardinality

Hi! is there any way/guidance available or planned feature to allow per column/feature parameterization, ex: categorical features? (on the possibility that different features can gain from different encoding params)
thanks!

ping @guolinke

very sorry for the late response.
@rquintino which parameters you think is needed for per-column parameterization?

ping @rquintino

Closed in favor of being in #2302. We decided to keep all feature requests in one place.
Welcome to contribute this feature! Please re-open this issue (or post a comment if you are not a topic starter) if you are actively working on implementing this feature.


Reimplement typescriptBuffer::flush to speed up Autocomplete results.

This should resolve issue #1331.
The typescriptBuffer::flush() method now functions similarly to the way it did in atom-typescript v11.0.6, which results in autocomplete results being nearly instantaneous once again.

Tested on atom-1.20-beta5, works like a charm!
Could you please explain the changes? Why was the implementation changed to use emitDidStopChangingEvent in the first place?

@deankevorkian
The root of the issue is that Autocomplete will call into this package as the user types, yet changes are unlikely to have been flushed out of the buffer at that point. The package author may then need a way to flush those changes out in order to provide up-to-date suggestions. Some Autocomplete providers can just get the current line from the buffer and work that way, but atom-typescript cannot.
atom-typescript has used scheduleDidStopChangingEvent, emitDidStopChangingEvent, and debouncedEmitDidStopChangingEvent within the TextBuffer class in order to flush out those changes. As you noticed, these are undocumented methods for that class, so they are subject to change from release to release of text-buffer (and thus Atom). The method used in Atom v1.18 in order to do so was scheduleDidStopChangingEvent. That method was removed in Atom v1.19, with the replacements being emitDidStopChangingEvent and debouncedEmitDidStopChangingEvent.
debouncedEmitDidStopChangingEvent would essentially have the Autocomplete provider wait for up to TextBuffer::stoppedChangingDelay milliseconds in order to flush out the changes and provide suggestions to the user, which is not ideal. In order to support emitDidStopChangingEvent, the changes in this commit were necessary, as otherwise we would be waiting for up to TextBuffer::stoppedChangingDelay regardless.
As a side note, the atom-typescript v11.0.6 implementation would temporarily set stoppedChangingDelay to 0 and flush out the changes that way when used in conjunction with scheduleDidStopChangingEvent. TextBuffer::emitDidStopChangingEvent accomplishes the same thing in a better way.

This needs additional work. I'll reopen this once it's completed.

Apparently we're leaking Disposables in the current release. The debounce prevented it from being a massive issue.

@GlenCFL, thanks for investigating. Can you tell me more about the disposable leak?

@guncha
const {dispose} = this.buffer.onDidStopChanging(() => {
  dispose()
}

That just never actually disposes of itself, so we register a new callback to onDidStopChanging every single time we flush the buffer. Glancing through everything on the release commit again, it's not that big of an issue there.
It was a much bigger deal in this pull request due to its immediate nature, but it's fixed now. You would have thousands of callbacks firing after only a few minutes of editing.

@GlenCFL @guncha Could this PR get merged now? Autocompletion is extremely unhandy to use at the moment

I'll test it today. @GlenCFL, if you can run the prettier on ./lib/main/typescriptBuffer.ts and push the changes, that would be swell.

@guncha Already did.
This was the very first commit:

Reimplement typescriptBuffer::flush to speed up Autocomplete results.

With this being the latest:

Stop leaking Disposables.

The time stamps are wrong for the commits due to the time on my local machine being wrong. I had switched over from Linux to Windows, which results in the clock being wrong if you haven't applied a fix. If you want, then I can squash these down into a single commit, but there's no issue with an incorrect timestamp due to Git using commit hashes anyway.

Oh, gotcha. I didn't know that Github uses the timestamp to order the commits instead of.. you know, the parent-child relationship of the commits. It should work the same once I merge to master.

Sorry I didn't react sooner, but I didn't manage to find time to take a long hard look before now.
Using debouncedEmitDidStopChangingEvent was motivated by the want to avoid unnecessary events when typing, primarily -- I didn't realize it triggers on trailing edge. Personally, I barely notice the difference. I'm not using autocomplete-on-keypress though, so that might be why. Sorry about that.
Disposable leak is bad, but I'd like to point out I didn't touch that code, so we've been leaking disposables long before -- primarily because Disposable.dispose is not a bound method (https://github.com/atom/event-kit/blob/master/src/disposable.coffee#L31), so deconstructing and calling it with no object is an error (so frankly I doubt the dance around await is necessary, but oh well)

@lierdakil
That's true. The issue is just in the destructured assignment. A cleaner way to do this would just be:
async flush() {
  if (this.changedAt > this.changedAtBatch) {
    await new Promise(resolve => {
      let sub = this.buffer.onDidStopChanging(() => {
        sub.dispose()
        resolve()
      })
      this.buffer.emitDidStopChangingEvent()
    })
  }
}

I really just went with the first thing that came to mind whenever I noticed the leak. I'll sneak it into a future PR if it doesn't appear there another way.


key_pattern value is being checked for each iteration

key_pattern can be checked once before the loop and then assigned and reused

#158

Is that ok now?

yes, merged. thanks again


[v1alpha2] Job should be marked completed when worker 0 exits but other workers are still running

I think there was a regression in v1alpha2.
When there is no chief, we want to assume worker 0 is the chief. Thus when worker 0 exits the job should be marked completed. This was the behavior in v1alpha1 when using a terminationPolicy which allowed us to specify which worker to use as the chief.
In v1alpha2 it looks like the behavior is to wait for all workers to exit.
https://github.com/kubeflow/tf-operator/blob/master/pkg/controller.v2/controller_status.go#L87
I think we need to support the case where only worker 0 exits, because I think there are a lot of TF programs that make the assumption that worker 0 is the chief and only worker 0 exits.
Its possible we also need to support the case where we want to wait for all workers to exit.
We had an E2E test for this but it looks like the test failures weren't being reported properly because of #748

Make sense. Then how do we support both cases? We only have one restart policy.

If we need to support both policies we'll need to add a terminationPolicy or similar field as we had in v1alpha1. I'm following up with the TensorFlow folks to see whether we need to support both cases i.e only worker 0 exits or all workers exit.

The correct criterion should be only waiting for worker N=0 to exit. That should be sufficient; we don't need to support the case where we wait for all N workers to exit.
Here's the answer I got from some TensorFlow experts.
We currently have three multi-node strategies that have three corresponding setups:
a) Between-graph replication with ps:
Waiting for the chief looks like the right criterion, especially when they run asynchronously. However,
although some straggler non-chief workers could still run after the chief terminates,
the updates by the stragglers would not be checkpointed.
b) Between-graph replication without ps, such as MPI-based solution:
It doesn't have a chief. Waiting for worker 0 in this case is acceptable. These workers train
synchronously and therefore they should exit at the same time.
If one worker has some error and exits, then the other workers will probably hang.
c) In-graph replication, typically without ps, which runs in-graph all-reduces to aggregate gradients:
In this case, the first worker (or chief) runs the model while the other workers run
standard tensorflow server. So in this case waiting for worker 0 (if there is no chief) is the right solution.
In case c without a separate chief process, only worker 0 would exit; other workers wouldn't exit. So with the current policy we can't support this case.

SGTM, WDYT @ddysher @codeflitting

@codeflitting Any chance you could take this on?

@jlewi I will take this if nobody working on this :)

@ScorpioCPH If you could pick this up that would be awesome.
/assign @ScorpioCPH

@ScorpioCPH How's this coming?

Will submit a PR later today :)


[Modal] destroy should tear down mutation observer

Steps

Show a modal with {observeChanges: true}
Hide the modal (either programmatically or by, e.g. clicking on the dimmer)
Some DOM updates are performed during the hide/destruction phase of the modal

Expected Result
Scroll lock is removed from the dimmer root
Actual Result
Scroll lock is incorrectly reinstated after tear down of the modal
Version
2.4.0
Testcase
The test case is quite tricky to extract as the specific problem I'm facing is caused by the interaction of Angular and the teardown mechanism of the modal. I can make a PR that fixes the behaviour as I have patched my local version to achieve the correct result.

@euangoddard
Would you like to create your PR for https://github.com/fomantic/Fomantic-UI as well ?
It will get merged there much more sooner than here, i guess 😉
Hint: If you do, please base your PR on the develop branch instead of master
If you don't / won't, i love to adopt your fix for Fomantic-UI myself, because it makes sense (same logic is used in dropdown/sticky/popup/visibility already)

@euangoddard  In case you are going to prepare the PR for Fomantic-UI as well, please see my Review comments before.

@lubber-de I've made a PR against Fomantic-UI as well to expedite this. Let me know if there's anything else you need.


Is it SEO friendly?

Hello @luruke ,
Its awesome. Thank you for the all.
I want to know that is it SEO friendly library, like if i use barbajs in my existing website which is based on pure html css js. and i am confused  that if i use barba js is there make impact on my Google search result rank?
Sorry for my bad English.
Thank you

Hello @awsomedesigner ,
barba.js is SEO friendly.
For more info:
https://www.smashingmagazine.com/2016/07/improving-user-flow-through-page-transitions/
http://barbajs.org/how-it-works.html


Slide bar between editor and top level is not handy

It's really hard to adjust the size of the top level on mobile as you can see in this video

Also sometimes the top level just fill the whole screen for no reason


Validator address issues

The call to get a validator that eventually reaches here (https://github.com/jbowen93/ethermint/blob/main/x/evm/keeper/grpc_query.go#L105) doesn't find the validator.
Originally posted by @jbowen93 in https://github.com/celestiaorg/optimint/issues/305#issuecomment-1058767799

This is resolved.

Actual issue was a wrong key used in ethermint.


Bitwise XOR

Compute the bitwise XOR of a numeric expression with another expression. The ^ operator should be enabled on expressions for this to work, see example: https://github.com/Eventual-Inc/Daft/blob/main/daft/expressions/expressions.py#L252
Example:
df = daft.from_pydict({"a": [0b0000, 0b1100], "b": [0b1111, 0b1111]})
df = df.select(df["a"] ^ df["b"]) # result = [0b1111, 0b0011]

or simply with a scalar value
df = df.select(df["a"] ^ 0b1101) # result = [0b1101, 0b0001]

Close with https://github.com/Eventual-Inc/Daft/pull/2365


[bazel/CI] Install bazel in OT CI

Here's the portion of https://github.com/lowRISC/opentitan/pull/10041/
that installs bazel in OpenTitan's Azure containers.
It only updates gcc and installs bazel, it doesn't run anything. On the SW side we already have submitted code that depends on gcc8
Signed-off-by: Drew Macrae<EMAIL_ADDRESS>

Hi @drewmacrae, is this blocking any thing?
Can we please postpone the merger of this until all the contributors can confirm that Bazel is installed on their systems?
It's somewhat of a critical time on the HW side.

Hi @drewmacrae, is this blocking any thing? Can we please postpone the merger of this until all the contributors can confirm that Bazel is installed on their systems? It's somewhat of a critical time on the HW side.

Ah nevermind, this isn't putting these tests in the pipelines yet.  This is fine preparation then.

These installation instructions are somewhat complex.   Is this all documented in the system installation page?

Opened issue #10355 for documentation elsewhere.

Hi @drewmacrae, is this blocking any thing? Can we please postpone the merger of this until all the contributors can confirm that Bazel is installed on their systems? It's somewhat of a critical time on the HW side.

Regarding blocks, this is on the critical path for the mask rom reproducibility at this point. We'll try to have a more organized flag day next time we set it to take effect but for now this just adds the tools to the CI.

I think I can make it a little more robust by making it not throw an error if it runs into trouble here.

I've marked it as a draft so it doesn't get submitted yet.

rebased and pushed to rerun CI

Can you rebase @drewmacrae? I'll then merge once the tests have re-run (the CI pass is a bit out of date now).


Get children async

After we made lazy loading features for the tree view, we realized we actually needed asynchronous GetChildren function. Because of the way Blazor cannot wait on monitor thread, it is not possible to just pass Result of an async method on GetChildren.
I added a new GetChildrenAsync and HasChlidrenAsync parameter to achieve this. This will use a OrderedListByGetChildrenAsync component. Children items are fetch inside the OnParametersSetAsync override, as well has HasChildrenAsync. This changes the Parental parameter to not contains the list of children but the parent's item.
I also added a new demo pages using the new async functions and await Task.Delay to simulate asynchronous calls.
So far, there is no visual feedback on loading async items.
This is a proof of concept more than anything and I am more than inclined to discuss or fixe any points of my code. Thank you for your time

Hi @fhayd,
sorry for the delayed response. Asynchronous loading of a tree view is certainly an interesting problem.
However, at a first glance, this doesn't seem to be the right solution: OnParametersSetAsync will be called many times, if I'm not mistaken, so wouldn't the cost of fetching the necessary information be paid multiple times? What happens if the async operation fails, e.g. when it's a network call that times out?
Visual feedback, as in any kind of spinner, would also be very good. On the other hand, this library should remain unbiased in how things look like, so we can't just drop any spinner in.
My gut feeling says that instead of adding another feature on top of the TreeView component, it might be better to create an AsyncTreeView component, that offers this kind of feature set. There we could easily add e.g. a SpinnerTemplate that gets shown during the async operation.
BR
Stefan

Hi @fhayd,
sorry for the delayed response. Asynchronous loading of a tree view is certainly an interesting problem.
However, at a first glance, this doesn't seem to be the right solution: OnParametersSetAsync will be called many times, if I'm not mistaken, so wouldn't the cost of fetching the necessary information be paid multiple times? What happens if the async operation fails, e.g. when it's a network call that times out?
Visual feedback, as in any kind of spinner, would also be very good. On the other hand, this library should remain unbiased in how things look like, so we can't just drop any spinner in.
My gut feeling says that instead of adding another feature on top of the TreeView component, it might be better to create an AsyncTreeView component, that offers this kind of feature set. There we could easily add e.g. a SpinnerTemplate that gets shown during the async operation.
BR
Stefan

Hello @stefanloerwald ,
Thank you for the reply. I agree with the problematics you pointed out and I will try to work on this.
As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

Hello @stefanloerwald ,
Thank you for the reply. I agree with the problematics you pointed out and I will try to work on this.
As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

I'm not sure about it yet. UI failing isn't ever a great experience. Something should happen. So if GetChildrenAsync fails, it can't return any children, but just returning null doesn't tell the user anything about what happened. Is it something that can be tried again? Is it something that will never work? I feel like there should be a parameter for error callbacks. Maybe just Action<Exception> OnGetChildrenFailure. Then we can wrap the call to GetChildrenAsync in a try-catch and invoke that callback on any issue. The user then has a chance to deal with issues, if required.
Of course if you have a more elegant solution, go ahead! I'm just spitting out thoughts here ;-)

As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

I'm not sure about it yet. UI failing isn't ever a great experience. Something should happen. So if GetChildrenAsync fails, it can't return any children, but just returning null doesn't tell the user anything about what happened. Is it something that can be tried again? Is it something that will never work? I feel like there should be a parameter for error callbacks. Maybe just Action<Exception> OnGetChildrenFailure. Then we can wrap the call to GetChildrenAsync in a try-catch and invoke that callback on any issue. The user then has a chance to deal with issues, if required.
Of course if you have a more elegant solution, go ahead! I'm just spitting out thoughts here ;-)

As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

I'm not sure about it yet. UI failing isn't ever a great experience. Something should happen. So if GetChildrenAsync fails, it can't return any children, but just returning null doesn't tell the user anything about what happened. Is it something that can be tried again? Is it something that will never work? I feel like there should be a parameter for error callbacks. Maybe just Action<Exception> OnGetChildrenFailure. Then we can wrap the call to GetChildrenAsync in a try-catch and invoke that callback on any issue. The user then has a chance to deal with issues, if required.
Of course if you have a more elegant solution, go ahead! I'm just spitting out thoughts here ;-)

The TreeView itself does not define the GetChildrenAsync function but just calls it. I think the responsability for the one providing children to handle these kind of error no? I mean, wrap GetChildren and call back is something they should already do defining the function right?
In the end I should respect your decision of course :)

As for the failure of the async operation, isn't it the responsability of the GetChildrenAsync function to handle this? I don't think the TreeView should have anything to do with this, event visually, don't you agree?

I'm not sure about it yet. UI failing isn't ever a great experience. Something should happen. So if GetChildrenAsync fails, it can't return any children, but just returning null doesn't tell the user anything about what happened. Is it something that can be tried again? Is it something that will never work? I feel like there should be a parameter for error callbacks. Maybe just Action<Exception> OnGetChildrenFailure. Then we can wrap the call to GetChildrenAsync in a try-catch and invoke that callback on any issue. The user then has a chance to deal with issues, if required.
Of course if you have a more elegant solution, go ahead! I'm just spitting out thoughts here ;-)

The TreeView itself does not define the GetChildrenAsync function but just calls it. I think the responsability for the one providing children to handle these kind of error no? I mean, wrap GetChildren and call back is something they should already do defining the function right?
In the end I should respect your decision of course :)

Fair point. The context withing GetChildrenAsync should be enough for the user to determine how to deal with errors. Good! That helps keeping the API clean.

Fair point. The context withing GetChildrenAsync should be enough for the user to determine how to deal with errors. Good! That helps keeping the API clean.

Hello again.
I made some modifications on my code. Now there is a TreeViewAsync handling asynchronous children fetch and asynchronous HasChildren. To avoid code duplication I made a TreeViewBase whose inherits both TreeView and TreeViewAsync.
Now GetChildrenAsync and HasChildrenAsync are called from OnInitializedAsync which is called only once, but I am still not sure if this is the best way.
I also added a RenderFragement LoadingTemplate to display visual feedback of loading the children that has a deafult value or can be assigned by the user

Hi @fhayd,
that sounds really good! I'm going to take a look at it tomorrow.
I think calling the async methods only once is very much the right thing to do. If multiple calls were to return different data, that would be a very tough thing to deal with from a library perspective! So if that's required from the user perspective, better handle that kind of stuff fully separate to the library (and then probably just use the sync version).
Thanks already for putting the work in for this pull request!
Stefan

Hi @fhayd,
I had some time to look at the proposed changes in detail now. Overall, it looks like we're on the right track. I made some changes to increase consistency with the rest of the code base. I cleaned up my github profile a while ago, removing access to the ArxOne fork of this library. Could you please grant me access again, so that I can push?
There are two issues I see at the moment:

The introduction of a root item seems unnecessary and in the case of the demo quite confusing, to be honest.

I think we can do without it entirely. Should the user need a root item, they can simply make GetChildrenAsync return that root item immediately. It confused me in the demo, because the item "A" is in code, but nowhere to be seen in the output.

The loading indicator might not be where it should be.

A reasonable LoadingTemplate would be the text "Loading...". This leads to an unpleasing UX, where the entire item is now shifted by quite a bit. It looks roughly like
Loading... [ ] My Item

However, "My Item" isn't loading at all. It's the children! So I think the position of the LoadingTemplate should move to where the children will soon render.
> [ ] My Item
  Loading...

What do you think?
Stefan

Hello @stefanloerwald
First of all I gave you acces to the repo so you can push your modification.
I agree with you on both points:

I noticed when I pushed that this root item is not only confusing but also wrong, a tree can start with multiple elements
I agree on the loading part, and it should not be too hard to move the loading template. I guess I can find exemple of trees that display loading at the place it is at the moment and this lead me to this, but it doesn't mean it's good :)

I can try to make theses changes quickly. If it is the only points that needs to be fixed for you then it's all right

I'm glad you agree on these points. I pushed the changes I made, so if you could continue with that, that would be great!

Hello again, sorry for the delay, I have been quite busy lately.
I fixed the points we discussed earlier, as well as a major bug I implemented (where children at the same level shared the same HasChildren and LoadingChildren).
Let me know if this is ok for you
Thank you

Thanks @fhayd for continuing to implement this.
The behavior of the component still doesn't feel quite right to me.
From the code, it looks like there should be absolutely no delay to display the two top layer elements ("A"), yet the page clearly takes quite a while until it displays them, without showing a "Loading" indicator until then.
Is this just my computer being super slow or is this happening for you as well?

Right now in the exemple, when the TreeView is rendered, we make a call of HasChildrenAsync for the first items (the first "A" items), which does wait for 1s. Maybe I can change this for the exemple.
Which remind me that I forgot to explain something:
As I remove the RootItem from the TreeViewAsync, the user has the responsability to handle GetChildrenAsync(null) and HasChildrenAsync(null) cases. Do you think it is ok? Or should it have a root list of item?

The example code that I see only waits for a second for all elements except the first:
if (i == null)
{
    return new List<Item> { new Item { Self = "A" }, new Item { Self = "A" } };
}
await Task.Delay(1000);
//...

As I remove the RootItem from the TreeViewAsync, the user has the responsability to handle GetChildrenAsync(null) and HasChildrenAsync(null) cases. Do you think it is ok? Or should it have a root list of item?

I think that's a perfectly valid approach.

The reason for the delay is in the HasChildrenAsync, called for "A" items:
if (i == null) return true;
        await Task.Delay(1000);
        switch (i.Self)

this is called for items "A" (so i != null) before they are rendered.
I pushed modification to avoid this:
if (i == null || i.Self == "A") return true;
        await Task.Delay(1000);
        switch (i.Self)

I think it is fine this way, but maybe HasChildrenAsync should be called after item render ?

The reason for the delay is in the HasChildrenAsync, called for "A" items:

Ah, yes, that explains it.

I think it is fine this way, but maybe HasChildrenAsync should be called after item render ?

That sounds like a better solution. As soon as we have items, we should display them, even if HasChildrenAsync takes forever on them to see whether they in turn have children.

Alright, I made the change and now HasChildrenAsycn is called after render. I set the default value to true, so the user can try to expand the item before HasChildrenAsync finish. It seems like the best way to me, but it can easily be changed :)

That seems like a sensible approach to me. I will push a few minor changes in a moment and then I think it's ready for merging!


Not working in PS plus at thie time

I just installed this, made sure to follow all steps carefully, but it seems to still not work in PS plus right now.

If so, please don't ever buy Sony games again and just download them for free online if you want to play them.

Firstly, so THAT is how people have those overlays, nice, also, will check and report back here.

This is what i can figure out through that program so far.

Have you installed Vigem?

Okay, now i am confused. I checked in VSCview just now, and it once again only shows the SharpDX.XInput.Controller (my physical controller) and not the virtual DS4 that i try to emulate with  this software here... I made sure to start the emulator first, and then the view...
Restarted my pc, repaired my controller with my pc (official wireless dongle-stick)  and tried if a wired configuration would work.
I am bejond confused as to what i am doing wrong here.

https://github.com/xeropresence/remoteplay-version-patcher maybe this will help, I didn't check, if someone can check it would be great

https://www.reddit.com/r/remoteplay/comments/r24n95/tutorial_how_to_fix_ps_remote_play_4508250_and/


[DNM] Attempt to reproduce flaky test in CI

Attempting to reproduce and debug swift-corelibs-foundation's TestFileManager.test_emptyFilename in a swift-foundation PR since I haven't been able to reproduce locally.

@swift-ci please test Windows Platform

Excellent, it reproduces here, will debug.

@swift-ci please test Windows Platform

@swift-ci please test Windows Platform

CreateSymbolicLinkW is failing with error 4392. From the Windows documentation:
ERROR_INVALID_REPARSE_DATA
4392 (0x1128)
The data present in the reparse point buffer is invalid.

@swift-ci please test Windows Platform

@swift-ci please test Windows Platform

@swift-ci please test Windows Platform


Messaging: Decryption Race Condition

In some circumstances, incoming messages are unable to be decrypted due to a race condition where the user's key is not yet available. A refresh solves this. Perhaps messages should be re-retrieved after the key is stored?

This should no longer be relevant thanks to the recent centralization efforts. :ballot_box_with_check:


Recently added "fs" module to read config.json is not defined.

Looks like the fs module needs to be 'require'-ed in server/app.js. Otherwise it fails to read the config and says "fs is not defined"

Thanks, not sure how i missed that, i guess that's what i get for gracefully handling errors during my tests.


I'd like @andrewseguin to take a look at this as well

@andrewseguin - ready for round 2!

Just tried this out on the 6.0.0-beta-0 version. It seems to load the content as expected.
The problem I'm having is that the content is being recreated every time you navigate to the tab. I've seen this exact behavior before when using a ng-template in combination with a *ngIf to toggle it. Seems like a similar situation here.
I would want it to lazy load it when the tab is created, not when navigated to...

I'd prefer to set that behaviour externally: something like a "creationPolicy" param with values like:

CREATE_ALL
CREATE_CURRENT
RECYCLE
...

Best.

@Marfyy and @aalbericio, the original issue was that to get animations to work inside a hidden tab some hacking was needed. IMO, this is fulfilled, as no hacking is necessary anymore.
Maybe starting another issue asking to improve the lazy load feature is the best you can do now. This issue is likely to be closed as soon as 6.0.0 is officially released.

Of course! That's more like a feature request. You're right! ;)

agreed :)

What version is this available in? Any 5.x.x versions or not until 6?

Not until 6.


Test validation

add data for testing validation process with 2 different files

[1] "Run validation on file: 2023-04-16-team1_modela-quantile.gz.parquet, 2023-04-16-team1_modela.gz.parquet"
Columns:
No errors or warnings found on the column names and numbers
Scenarios:
No errors or warnings found on scenario name and scenario id columns
Origin Date Column:
No errors or warnings found on the column 'origin_date'
Value and Type Columns:
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Northern Mariana Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; American Samoa
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Virgin Islands
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Guam
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Delaware
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Wyoming
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; North Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; South Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; South Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: A-2023-04-15; Vermont
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; North Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; South Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Alaska
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; North Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; South Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: F-2023-04-15; Rhode Island
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Alaska
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; North Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; North Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: E-2023-04-15; Rhode Island
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: B-2023-04-15; South Dakota
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Alaska
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: D-2023-04-15; Rhode Island
🟡 Warning 507: Some value(s) are greater than the population size. Please verify: C-2023-04-15; Alaska
Target Columns:
No errors or warnings found in target and associated columns
Locations:
No errors or warnings found on Location
Sample:
No errors or warnings found on Sample
Quantiles:
No errors or warnings found on quantiles values and format


enhanced blacklisting on miner side

following flags are supported on miner side

blacklist.allow_non_registered: allow requests from non-recognized entities
blacklist.force_validator_permit: blacklist requests from non-validator hotkeys

@sakrobinson i think, we can merge this PR.


add file travis.yml and badge build passing

In order for Travis CI to build the project, we  need to tell the system a little bit about it. we'll need to add a file named .travis.yml to the root of our repository.

Good :-)


Rename improvement suggestions

📝 Provide a description of the new feature

Show filename in tooltip on hover, so window doesn't have to be stretched to see entire filenames.
Remember window size for next time it's opened, so if it is stretched to be able to see whole filenames, it will remain that way each time.
Add presets/profiles, e.g. one could be called "Append to End" with "$" in the search for box, regex enabled, item name only checked, and any other desired options checked, allowing the user to just fill in the replace with box and rename, without having to go through and adjust all the settings manually, and another could be "Change extension" with the applicable boxes checked, etc.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@vertigo220 we have a 1 topic per issue rule.  1 and 2 should be handled by #2152  / #888


Visualize Maven / Gradle POM and property file in Java Project Explorer

It would be great if we can add files (property files,etc) in the java projects view. If this is already implemented can you share with me how to do it?
Thanks

Currently it's not supported, but it's in out backlog.

Adding new file will be tracked by #598
Visualize pom/gradle files will be tracked by #145