UserProfile::setLinkedId should allow null value

For decoding of Json-stored user profile data in vertx sessions. I can build a custom json-serializer for UserProfile but really shouldn't have to maintain one.
I can't see any clear reason why prevent this. At the very least if you want to prevent unsetting of a linked id, you should wrap the null check on the provided linked id in code to validate we have already been linked.
I'll submit a PR but until this is done, vertx-pac4j will remain broken (and this is a blocker to fixing it).

I'm working on this and will submit a PR soon

My idea was that it doesn't make any sense to link an account to another account having the null identifier. That said, I did not provide any way to remove the link so there is an issue in my reasoning  here.
You can safely remove the check.

Reverted the master to 2.0.0-RC3-SNAPSHOT...


git deps cause grief for some

For some users (often those with strict corp policies) GIT dependencies cause grief
https://github.com/airportyh/testem/blob/master/package.json#L42
└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>(git://github.com/patocallaghan/socket.io.git#c1182cae6038a2b65eb13779052b0c3793a04938)
    └─┬<EMAIL_ADDRESS>(git://github.com/patocallaghan/engine.io.git#22b6418a55671a085c4ac87708eae24c14228934)
      └──<EMAIL_ADDRESS>(git://github.com/patocallaghan/ws.git#892ea5f4dfc1cd4cb18d36cce446bef0d8039cf

those variants will need to be published to npm, let me propose the -pure suffix.

socket.io-pure
engine.io-pure
ws-pure

cc @patocallaghan

@johanneswuerbach ideally I would love a release with ^ asap. Let me know your schedule, so I can be sure this is fixed quick enough that your schedule still allows a release.

Duplicate of https://github.com/airportyh/testem/issues/659 . I don't have access to push those forks to npm :-( After they are pushed, I can cut a new release until 23 CET.

Yep , will try get these out ASAP

https://www.npmjs.com/package/ws-pure
https://www.npmjs.com/package/engine.io-pure
https://www.npmjs.com/package/socket.io-pure
https://www.npmjs.com/package/socket.io-client-pure
Here's the packages published to npm although each repo will need to be updated to point to one another.
@johanneswuerbach I'll give you access also, just in case you ever need it

Will merge and release https://github.com/airportyh/testem/pull/661 as soon as everything passed, we still need to link all packages to each other. I could do that, but I would need access to your forks @patocallaghan

@patocallaghan mind also adding me to your engine.io-client-pure Apparently this also needs a few changes to use the ws-pure version


Upgraded gradle from 5.5.1 to 5.6.4

Dependencies upgrades
gradle 5.5.1 -> 5.6.4

Releases notes | Source code | Documentation

This pull request was automatically generated by Releases Hub Gradle Plugin

gradle 5.6.4 -> 6.0

Releases notes | Source code | Documentation

gradle 6.0 -> 6.0.1

Releases notes | Source code | Documentation

gradle 6.1.1 -> 6.2

Releases notes | Source code | Documentation | Issue tracker

gradle 6.2 -> 6.2.2

Releases notes | Source code | Documentation | Issue tracker

gradle 6.2.2 -> 6.3

Releases notes | Source code | Documentation | Issue tracker

gradle

Version: 6.2.2 -> 6.5
Releases notes | Source code | Documentation | Issue tracker

gradle

Version: 6.2.2 -> 6.5.1
Releases notes | Source code | Documentation | Issue tracker

gradle

Version: 6.2.2 -> 6.6.1
Releases notes | Source code | Documentation | Issue tracker


Blending broken using RenderTextures & WebGL

Version

Phaser Version: 3.55.2
Operating system: Windows 10
Browser: Chrome

Description
Additive blending is not working when rendering to a RenderTextures when using WebGL.
Example Test Code
Minimal sample with 2 circles that should be blended: https://codepen.io/sjb933/pen/wvPgpWq?editors=1010
You can fix the blending by either:

Changing USE_WEBGL to false will activate canvas rendering which blends as expected.
Use a version of Phaser <3.50. You can uncomment the second script line in the HTML file to import older<EMAIL_ADDRESS>
I'm including the same sample code below
// With webgl disabled (canvas mode), blending works regardless of Phaser version
// With webgl enabled, blending works in Phaser < 3.50, and doesn't work in latest
const USE_WEBGL = true;

let config = {
  type: USE_WEBGL ? Phaser.WEBGL : Phaser.CANVAS,
  width: 600,
  height: 400,
  scene: {
    create: create,
  }
};

let game = new Phaser.Game(config);

function create() {
  rt = this.add.renderTexture(0, 0, 600, 400);

  layer1 = createLayer(this, 200, 200, 0xff0000);
  layer2 = createLayer(this, 400, 200, 0x0000ff);

  // draw the layers with additive blending
  layer1.setBlendMode(Phaser.BlendModes.ADD);
  layer2.setBlendMode(Phaser.BlendModes.ADD);
  rt.draw(layer1);
  rt.draw(layer2);
}

function createLayer(self, x, y, color) {
  let graphics = self.make.graphics();
  graphics.fillStyle(color);
  graphics.fillCircle(x, y, 150);
  return graphics;
}

Thanks for opening this issue, and for submitting a PR to fix it. We have merged your PR into the master branch and attributed the work to you in the Change Log. If you need to tweak the code for whatever reason please submit a new PR.


Sort window impls

Purpose

Purpose of this PR is to add sort window impls to ballerina stream implementations.

forever {
        from inputStream window sortWindow([3, "inputStream.age", "ascending",
            "inputStream.name", "descending"])
        select inputStream.name, inputStream.age
        group by inputStream.school
        => (TeacherOutput [] emp) {
            foreach e in emp {
                outputStream.publish(e);
            }
        }
    }

Assignees
@mohanvive , @gimantha , @grainier

Closing the PR due to refactoring changes in Ballerina core and Streams.


Limiting shortest Path depth

I am currently unable limit the range of ShortestPath to not try beyond a certain depth in order to save processing - please add feature if possible.

We should support a JSON like arguments, where you can specify params easily like this maxDepth.

Is there any way to query the maximum number of hops between any two nodes (and limit the query to stop searching three nodes out) without using the shortest path function? I would like to use orientdb, but cannot wait until 2.2 is out due to time constraints. For reference my data is 4.8 million nodes and 68 million edges.

@Gerenatian which driver are you using? By the way, OrientDB is extensible: you could always write your function in JS that support a limit. Look at: http://orientdb.com/docs/last/Functions.html

I think I've found a work around for the time being, I can run a query like traverse * from #12:50151 while $depth <= 3 and search for my destination vertex in the result set. It seems fairly quick. Thank you for the quick response Ivca!

V 2.2 includes A* (astar()) function, that allows to define a max depth of the path.
Closing
Thanks
Luigi

Thanks for the update luigidellaquila. Thats a great addition.


Adding the latest version of deepstream.io to cask

This change allows users to use cask to download the deepstream.io
pkg. A small limitations are the fact that it currently
uses 777 settings for log directories.
If there’s a checkbox you can’t complete for any reason, that's okay, just explain in detail why you weren’t able to do so.
After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Applied recommended changes, thanks for quick feedback!

Odd with CI, just ran same change locally and got this
brew cask _audit_modified_casks 983124cfe24e29a2a7b47ca08402b328d9de38ad...402a11c2a5fa36b2a964602d4082d0d9408fa50e
==> 1 modified cask: deepstream
==> Downloading https://github.com/deepstreamIO/deepstream.io/releases/download/v2.4.0/deepstream.io-mac-2.4.0.pkg
Already downloaded: /Users/yasserf/Library/Caches/Homebrew/Cask/deepstream--2.4.0.pkg
==> Verifying checksum for Cask deepstream
audit for deepstream: passed

Odd with CI, just ran same change locally and got this

Already downloaded: /Users/yasserf/Library/Caches/Homebrew/Cask/deepstream--2.4.0.pkg

The pkg is still cached.

Also, does mac get stripped out intentionally from the file name?

Yes, Cask saves the downloads as name--version

A small limitations are the fact that it currently uses 777 settings for log directories.

Where are the logs located?

Where are the logs located?

logs are located at /usr/var/logs/deepstream/

Thanks @yasserf

Awesome, thanks!


Allow async load of components templates

The template function in component bindings only allows sync load of a template. If you want async load (for exemple load template from server with ajax) it's not possible

PR sent, template function can now have a callback as parameter. If this parameters is defined, rivets will use it to wait for the template.


autoupdate: pre-commit

Automated changes by create-pull-request GitHub action

Codecov Report

Merging #18 (3179239) into master (98c50b8) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master       #18   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines          458       458
=========================================
  Hits           458       458

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 98c50b8...3179239. Read the comment docs.


Enable user defined port and proto for metrics http listener

Currently port is statically set to :8080. That doesn't work for everyone.
Make it so that in the globals you can specify the the listening port, and the protocol.
If it's http, should be simple. If it's https, then require some tls bits.

Done a few things here.

added the http-proto / http-port / http-tls-cert / http-tls-key [global] configuration options.
tweaked the monitor listener to bind to either non tls or tls ports based upon aforementioned configuration options.
added some tests against that change
updated base docker image to alpine3.8 and golang 1.11.0
shuffled some stuff around (eg: alog/ -> internal/alog/ , stats/ -> internal/stats/). Hoping to do some more cleanup of that soon.
updated it all so building/testing works again.


Avoid unnecessary files in dist / release files

I took the liberty to exclude the LICENSE.md file as it isn't really needed in dist files. Your position may differ on that.

I agree with you. Thanks!


--vlc: command not found

WebTorrent version: 0.95.1
Node.js version: 6.2.1
OS: Ubuntu 16.04

I'm trying to launch this command on my webtorrent CLI:
webtorrent download <magnet_uri> --vlc

to have the stream directly prompted to vlc. But on console I got --vlc: command not found.
Am I doing something wrong? Should I surround the magnet_uri with "quotes"?

The --vlc option only works when streaming, so you shouldn't be using download
Just do webtorrent <magnet_uri> --vlc

Alright thanks, my mistake. Shouldn't be worth capture this kind of silly mistakes?

@roccomuso You need to surround the magnet uri with quotes.
@rom1504 Actually, webtorrent download <magnet_uri> --vlc and webtorrent <magnet_uri> --vlc are the same.


Update documentation: Variable name in Tutorials/Create a Channel

Description
Varible name of TwoOrgsApplicationGenesis has been updated to ChannelUsingRaft in code
Steps to reproduce
No response

@solo-daemon
Thank you for submitting your PR. I have merged the PR you submitted.
At the same time, I found another PR addressing the same issue.
https://github.com/hyperledger/fabric/pull/4528
This PR seems to include a few addtional fixes aside from your contributions, but it has been stagnating for a long time while waiting for additional updates from the original submitter (I suspect the original submitter may have lost interest in this PR).
So, if possible, could you create and submit a separate PR that picks up on the differences your first PR(#4781) and this one(#4528)?


k3s: add multiple versions

Fixes #213943
This PR is a start offering some structure to having multiple versions.
Listing all versions we have available right now. Newer versions require further work.
I'm trying to keep things simple here. (so no fancy abstraction, DRY, etc)

k3s (k3s_1_26)

k3s_1_24 (1.24.4+k3s1) (1.24.10+k3s1 is available at upstream.)
k3s_1_25 (1.25.3+k3s1) (1.25.6+k3s1 is available at upstream.)
k3s_1_26 (1.26.1+k3s1) (in sync with upstream)

NixOS tests and update script are disabled in legacy versions.
k3s_1_26 is now rolling. Update script and tests are working just as were before. (No changes for latest!)
Patches are duplicated on purpose for when time is due directory can be deleted and nothing will be affected.
Due to priorities, I do not plan doing upgrades, back-ports, tests, update script for previous releases. But PRs are welcomed. And would be better someone with genuine interest in this to step up. Hopefully, as we move forward, we can get these things to a better state.
I might improve latest update script to automatically add new major versions in a new folder and pin previous version.
So basically what we have here, is exactly what we had before (latest rolling versions), plus previous releases we had. No changes. (I did copy and paste from history. Changed just a few minor issues that were patched, like cross compilation patch.)

This PR is awaiting review from maintainers: @euank @Mic92

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

3 packages built:

k3s_1_23
k3s_1_24
k3s_1_25

Do you think this could be backported to 22.11? To ease migration from 22.05... Otherwise I can just overlay them, and the problem will be fixed for at least 23.05 onward.

Do you think this could be backported to 22.11? To ease migration from 22.05...

Back-porting is always possible, with fixes - if necessary.
Feel free to make a PR back-porting to 22.11 and 22.05.

Otherwise I can just overlay them, and the problem will be fixed for at least 23.05 onward.

Up to you.
--
Personally, I'd rather spend time moving things forward than backwards.

Do we really need all four versions? Especially, 1.23 with less than a month of support looks pretty pointless to me. How about reducing the set to the actively maintained ones?
[1] https://endoflife.date/kubernetes

Do we really need all four versions?

I have no strong opinion on this.

Especially, 1.23 with less than a month of support looks pretty pointless to me.

Release 22.05 is pinned to 1.23.

How about reducing the set to the actively maintained ones?

I wouldn't mind reducing the set.
Will remove 1.23 then.

[1] https://endoflife.date/kubernetes

Can follow this.

I think that yes, we need 1.23. Quoting from https://github.com/NixOS/nixpkgs/issues/213943:

to have a successful HA cluster upgrade, you need to:
Upgrade your server nodes to the latest patch version available. One node at a time.
[...]
Latest k3s in NixOS 22.05: https://github.com/NixOS/nixpkgs/blob/0874168639713f547c05947c76124f78441ea46c/pkgs/applications/networking/cluster/k3s/default.nix#L49

However, upstream's latest for that minor version is v1.23.16+k3s1.
I can add myself as maintainer to help you after this is merged, and propose the upgrades.

I'm okay keeping 1.23 since it's in "maintenance mode" for a couple weeks yet. If, hypothetically, there were a CVE that were patched for 1.23, and someone were using an older nixpkgs with an insecure 1.23, it would be safest for them to update to the latest patch version of 1.23 to be secure.
I think that's a reasonable enough argument for keeping it around, and then dropping it once it won't see security releases (admittedly, in 3 weeks).
I, personally, expect that going forward it won't be much of a burden to maintain a few extra older versions. Typically, maintenance work comes with upstream packaging changes, and those shouldn't happen for release branches, except in unusual cases.
Once the update script is updated appropriately, we'll be able to just let the update script do it's job for historical supported versions.
I'll leave a separate review comment regarding the actual PR, but figured this discussion about what to keep would be easier to respond to separately.

Hi @euank,
First, sorry for the delay in answering you.
My approach was simplistic indeed. I wouldn't mind if you have a better idea for implementing this. Either I could merge this as it is now (without 1.23 even?) and then you could change anything you would like (you have my green light for sure). Or another option would be to just start a new PR closing this.
Regarding the update script, if I were to do it I'd likely do it much later, so please, feel free to do it.
Just let me know which path forward you prefer.

Just let me know which path forward you prefer.

I was trying to say in that long-winded review comment that I'm in favor of merging this, and then iterating on it!
I think this is an improvement over the current state of things, and I'm not confident I (or someone else) will do a better iteration super soon!

I would appreciate it if you could restore the 1.23 derivation because that's the one I'd need right now and, after all, the job was already done, so why not?
I noticed that most packages are a bit outdated, but I think it would be better to just merge this foundation, so we can do further updates later in smaller PRs, one by one. If we wait too much, 1.23 will disappear before I can fix it! 😢

1 would work in practice, but K8s docs tell you to update to the latest patch version before introducing minor version number skew... again, in reality, it rarely matters.

I also think that the latest patch upgrade probably is not necessary... but TBH k8s is so complex and important that I prefer to be extra cautious here. 😅

I would appreciate it if you could restore the 1.23 derivation because that's the one I'd need right now

You can always use any past versions already, you just need to add a new input to your flake referencing the commit, and inherit package from that. Nix magic.

and, after all, the job was already done, so why not?

I deleted it. -.-
But I'll re-add it. -.-²

I noticed that most packages are a bit outdated, but I think it would be better to just merge this foundational PR, so we can do further updates later in smaller PRs, one by one.

Yes...

 No package really disappears.

1 would work in practice, but K8s docs tell you to update to the latest patch version before introducing minor version number skew... again, in reality, it rarely matters.

I've been meaning to get to this PR for a week already. K3s is a priority for me because I use it in my Pi cluster. But time is limited. I or euank may bump it on and off, but it is not guaranteed. We have other obligations to answer.
For a perfect legacy support in K3s, consider participating and bumping it yourself. It is not that hard.
I am mostly happy with latest and unstable. I wouldn't mind if my cluster self-destructed. I have a process in place to recreate everything from scratch. :-)

I also think that the latest patch upgrade probably is not necessary...

Questions really is to whom... Right? Different needs, expectations, etc.

but TBH k8s is so complex and important that I prefer to be extra cautious here. sweat_smile

No doubt.

Anyone cares to review/approve again? So I can merge this...


Finalise permissions implementation

Finalise the permissions API from #461. Changes:

Async permission resolvers
Unit tests
Type tweaks
New ActionBar.Group
Various other tweaks

See extensive documentation, with the following entry pages:

Toggling Features integration docs
Permissions API reference
actionBar override docs
ActionBar component docs

Closes #582, closes #579, closes #580, closes #584, closes #461

@monospaced have merged, but would appreciate your review of documentation if you have time.

@monospaced have merged, but would appreciate your review of documentation if you have time.

@chrisvxd Docs are great, very clear and easy to grok. No notes!


Connection without password

Hey,
Currently, i'm coding a mobile app with a facebook login, everything is handle on my application, but i don't know what i can do after get user facebook information to register it into my feathers API.
I just want to send personal information with the token and that Feathers return me a JWT to allow users to interact with the API.
But I can't found anythings about that, do you have any idea ? It's my first time with a facebook login with a mobile application so i'm lost haha!
Thanks (And sorry for my english!)

@Clowning, take a look at the feathers-authentication-oauth2 plugin and use the passport-facebook-token strategy from npm.  I think you might even be able to copy over the setup from a new feathers-cli app with Facebook Auth and just swap out the strategy.
Also, maybe @ekryski or @corymsmith knows of an example application.

Hey @marshallswain, thanks a lot, i've tried to install this passport, everything is installed but i've this error : "info: error: authentication - Method: create: Failed to fetch user profile".
I've set my App ID and Secret Key and pass a valid Facebook Token :/
Do you have any idea about that?

Ok my bad ! It's working! Thanks a lot :-) !

I'm glad you got it working.


Other evaluation metrics

Hi,
I like your paper. As for the evaluation metrics, I can see your are using recall@k to track the performance. May I ask have you tried to implement other metrics like NMI and MAP@R? Thanks!

Hi,
Thanks for your interest! I did implement a few more metrics such as mAP@R (but not NMI), although the code is not compatible with the version from this repository for two main reasons:

I updated my personal repository to Tensorflow 2.2+, so I don’t have a code compatible with this one,
I had to rethink how metrics were implemented (especially how to handle custom distances and how to evaluate metrics for larger datasets), hence, the whole computation process is not compatible with this one.

If you're willing to implement it though, I can share some code.


Thumbnails are not generating on mobile ifproduct has more than 4 photos

Bug report

Thumbnails are not generating on mobile ifproduct has more than 4 photos

Scroll arrows is not working if product has more than 4 photos uploaded

On Mobile we can not see thumbnails of product's photo

@irisda
Bug is fixed now.
No response from last 13 days so we are closing this , feel free to reopen if still exist


error occurs when run test_block_mpc.py

After I configured OpEn and the virtual environment, an error occurred when running the code. I don’t know what caused it, and there is very little information on the Internet.

Hi @CreazeD ,
Thank you for your interest.
This problem seems to be related to the OpEn package which is based on RUST. Since I haven't met this issue myself and we cannot provide much support on Windows OS right now, I can only provide some ideas to debug this.
If you go to opengen/builder/optimizer_builder.py, you can find functions called __make_build_command and __build_optimizer. The first one constructs a cargo command for the second one to build a solver. The error message suggests that the cargo build file is missing. This might be due to the misconfiguration of the environment variables. Ensure that any required environment variables are set correctly. The executable might be in a directory that is not included in the system's PATH.
Possible solutions include adding RUST into your system path (check Configuring the PATH environment variable) or reinstalling RUST by carefully checking each step. If you have RUST correctly installed, you should be able to run rustc --version in your shell.
Hope it works :)
Best regards,
Ze


Works with vuex

Hi, this works with vuex?

@cafe4it
I believe it should work, the API is not coupled with Vuex or any other 3rd party library, but you can add some functionality on top of it and make it work.


[FEATURE] Add support for flash attention

🚀 Feature
Add a new config setting to allow using flash attention for models.
Need to explore how straight-forward this is to use for different types of models and how stable a simple switch could be.

Pytorch 2.0 and most models will already do this automatically, i.e. choosing most optimal routine via
torch._scaled_dot_product_attention
So no extra setting needs to be necessary.

Re-opening, might be easy to add via HF
https://twitter.com/younesbelkada/status/1705258148045750343


Improve readability for test parameters

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/Alluxio-PR-Builder/9714/
Test FAILed.

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/Alluxio-PR-Builder/9715/
Test FAILed.

Jenkins, test this please

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/Alluxio-PR-Builder/9719/
Test FAILed.

Jenkins, test this please

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/Alluxio-PR-Builder/9722/
Test PASSed.

LGTM

alluxio-bot, merge this please


[FLINK-29706][build] Remove japicmp dependency bumps

No longer required. In fact they shouldn't have any effect at all because the dependencies have changed to the jakarta namespace :)
https://github.com/siom79/japicmp/blob/master/pom.xml#L188

@flinkbot run azure


Ikea "E1603/E1702/E1708" not supported (anymore) message

Log message:  This plugin does not support zigbee device with model "E1603/E1702/E1708" yet.
(although it has been running for a couple of years)

running a separate domoticz application on a linux machine connected to the MQQT server running at the PI does support this device.

At my Raspberry that runs zigbee2mqtt and domoticz based on domoticz version 2022.1 and
zigbee2mqtt plugin upgraded to  Plugin (v. 3.1.0-beta) this problem remains.
I upgraded the plugin with the latest version. Deleted the "plugin hardware" and created new Zigbee2MQTT "hardware" did not resolved the issue.

Version: 2022.1
Build Hash: c9526851b
Compile Date: 2022-01-31 09:34:32
dzVents Version: 3.1.8
Python Version: 3.7.3 (default, Jan 22 2021, 20:04:44) [GCC 8.3.0]

This plugin does not support zigbee device with model "XYZ" yet there is no such message in the plugin code anymore, probably the upgrade did go wrong, try to completely remove the plugin folder and fetch the latest plugin version

Thank you for the response. Do I have to follow the install or the upgrade procedure ?

Just fully delete the domoticz/plugins/zigbee2mqtt directory and then follow install steps

The issue occured even with the new version: Zigbee2MQTT Plugin (v. 3.2.0-beta) indicated in the UI.
But anyhow, after several attemps issue resolved.
Thanks for advice

Issue can be closed


Negative weights for conformational state expectation in free energy calculation

When taking the expectation of whether a structure is folded (1) or unfolded (0) on an mbar object, often the weights for folded state at high temperature are very small and negative (such as 1E-15 for folded, 1.00000000e+00 for unfolded). This occurs when the temperature range is 50K to 400K. If I adjust the threshold for native contact fraction such that more structures are considered folded, the negative weights shift to the low temperature. The uncertainties also start to become zero at high T (all elements of covariance/theta matrix are equal to the precision used). Sometimes elements in the sigma matrix returned from the expectation calculation are NaN.
When this happens, we get these warnings:
/home/cwalker7/anaconda3/envs/cg_openmm_py37/lib/python3.7/site-packages/pymbar/mbar.py:1145: RuntimeWarning: invalid value encountered in sqrt   result_vals['sigma'] = np.sqrt(covA_ij[0:I,0:I].diagonal()) /home/cwalker7/anaconda3/envs/cg_openmm_py37/lib/python3.7/site-packages/cg_openmm-1.0-py3.7.egg/cg_openmm/parameters/free_energy.py:175: RuntimeWarning: invalid value encountered in log   np.log(results[str(i)][0][s2]))).value_in_unit(F_unit) /home/cwalker7/anaconda3/envs/cg_openmm_py37/lib/python3.7/site-packages/cg_openmm-1.0-py3.7.egg/cg_openmm/parameters/free_energy.py:181: RuntimeWarning: invalid value encountered in sqrt   theta_i[s1,s1] + theta_i[s2,s2] - (theta_i[s2,s1]+theta_i[s1,s2]))).value_in_unit(F_unit) /home/cwalker7/anaconda3/envs/cg_openmm_py37/lib/python3.7/site-packages/cg_openmm-1.0-py3.7.egg/cg_openmm/parameters/free_energy.py:175: RuntimeWarning: divide by zero encountered in log   np.log(results[str(i)][0][s2]))).value_in_unit(F_unit)
As we discussed, this seems like it's a numerical/rounding issue.
I'm attaching .nc files,
output.zip
output_checkpoint.zip
native structure file, stored cgmodel, and analysis script which reproduces the issue.
free_energy_test_files.zip

Still looking at this, but one thing to note is that you should be able to calculate the expectations at all temperatures simultaneously in:
for i in range(len(full_T_list)):
U_n = unsampled_state_energies[i,:]
    # compute expectations of being in conformational state n
    # Store results in a dictionary
    results[str(i)] = mbarT.computeMultipleExpectations(
        bool_i,U_n,compute_covariance=True)

Rather than looping over the full list.  Not sure it will help the numerical stability, but would reduce the amount of time doing calculations.

So, the errors do all appear to be when the states are all 1 or all 0, so that you can get negative values that are essentially near zero at the floating point limit, but still negative.  I'll have to think a little bit how to handle these sorts of errors in the future.  I'm not sure there's a non-hacky way, since I don't know a way to make sure rounding errors are always positive.
So, anytime the states are essentially 1 and 0, you will have these sorts of errors - I think the current approach will only have a dynamic range down to 1 x 10-15.
For now, I think the best bet is to recognize that when the occupancies get too low, then the free energies will be inaccurate, which means that it can probably only handle the range of +15 to -15 kBT for now.  I think I can probably fiddle around with the code to expand the range by doing things another way, but that will take some playing around with the logic, and possibly finding another code path.

If you use the pymbar branch 'with_0logfactor' (https://github.com/choderalab/pymbar/tree/with_0logfactor) I made a couple of tweaks that should handle the dynamic ranges of free energies a bit better.  Still a few nan's.  Let me know what you find.   However, I'm not certain these tweaks will be that robust in general, so I'll have to think a bit more about whether they make the most sense to put in the main mbar distribution.

Thanks for making the tweaks to pymbar, the negative weights seem to be gone now. The main thing is that we get free energy and uncertainty at all values of T now.
For the record, we can install this version to an existing conda environment using:
pip install git+https://github.com/choderalab/pymbar.git@with_0logfactor --upgrade
Without the --upgrade it was keeping the existing conda version 3.0.5, that's why it wasn't installing before.
There is still some NaN's only in the sigma matrices, due to some negative covariance elements.

I think those negatives in the sigma matrices are going to be hard to get rid of, since if the weights are sufficiently low, the matrix elements are simply too close together to handle.


Include the cover property in the response for a LIST request on the /books endpoint

Describe the feature you'd like
A response for a READ request on the /books/{id} endpoint contains the cover object for the book requested. Using this object, one can acquire the Cover image data for that specific book. A response for a LIST request on the other hand does not contain such object.
If one were to implement a search for for the existing books, they would have to request the cover image for each book seperately. This increases overhead.
Describe the benefits this would bring to existing BookStack users

Reduces overhead
Simplifies usage of the API

Can the goal of this request already be achieved via other means?
Yes. You would have to iterativly request the cover images for each book seperately.
Have you searched for an existing open/closed issue?

[X] I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?
Not using yet, just scoping
Additional context
No response

Duplicate post


Build Livepeer Subgraph

@ishraq8 Link for QA here:
Deployment Status:

[x] Ethereum: https://okgraph.xyz/?q=QmbHKjxkFDvyk5a259AdSRELBRSMk48CLsy6f9F9DBeuKs

@shashwatS22 @'ing you for tracking

We are building anew schema for this will update once I get it

@shashwatS22 We have a PR for a new schema for web3 infra/Depin once that it through LivePeer will be the first on that schema: https://github.com/messari/subgraphs/pull/1741
Also some comments from our data scientist @jacubcub:

For LivePeer the protocol collects revenue in ETH and not in their native LPT. For fields that are RevenueToken denominate in ETH since protocol revenue not in LPT.

Some notes from the already existing LivePeer subgraph, than may be useful to you:

Found the code for that api https://github.com/livepeer/explorer/blob/main/pages/api/usage.tsx
looks like they are querying their subgraph and then doing some transformations (they use time travel queries to get much of the historical data, but there is also a days entity in their subgraph which has historical data for some fields)
This is where the queries are defined https://github.com/livepeer/explorer/blob/main/apollo/subgraph.ts
You can see how they do the minutes calculation in usage.tsx too. It’s based off of fees and a constant pixels per minute that they get from assuming a certain distribution of transcoded frame rates and resolutions. Then they add minutes from livepeer.com usage api which is not public: https://livepeer.com/api/usage

@shashwatS22 We have a PR for a new schema for web3 infra/Depin once that it through LivePeer will be the first on that schema: #1741
Also some comments from our data scientist @jacubcub:

For LivePeer the protocol collects revenue in ETH and not in their native LPT. For fields that are RevenueToken denominate in ETH since protocol revenue not in LPT.
Some notes from the already existing LivePeer subgraph, than may be useful to you:

Found the code for that api https://github.com/livepeer/explorer/blob/main/pages/api/usage.tsx
looks like they are querying their subgraph and then doing some transformations (they use time travel queries to get much of the historical data, but there is also a days entity in their subgraph which has historical data for some fields)
This is where the queries are defined https://github.com/livepeer/explorer/blob/main/apollo/subgraph.ts
You can see how they do the minutes calculation in usage.tsx too. It’s based off of fees and a constant pixels per minute that they get from assuming a certain distribution of transcoded frame rates and resolutions. Then they add minutes from livepeer.com usage api which is not public: https://livepeer.com/api/usage

Thanks @ishraq8 I'll keep a note of this, and start working on the subgraph.

Passed QA, compared to https://explorer.livepeer.org/
the data matches what is on explorer great work @shashwatS22

Passed QA, compared to https://explorer.livepeer.org/
the data matches what is on explorer great work @shashwatS22

Thanks @ishraq8

@dmelotik Just FYI - this has passed QA

I did my code review yesterday. Working through some final things before merge


attempting handshake status

Added functions for handshake status.  Do I need to know the buffer size or can I just check if it is not empty using the eof function in OpenSSL?

I made a mistake in the function name in file javax-net-ssl.cpp, I have it as SSLContext, I'm aware it needs to be SSLEngine.  Not sure if I should cancel the pull request and put in another, or if it can be changed at merge.

@flipontheradio, pull requests may be altered even when they are opened. Just make sure you commit and push up to the branch that the PR is opened in.


[Feature][Manager] Sort-standalone only comsume the MQ cluster with the same cluster tag

Description
No response
Use case
No response
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

fixed in #5088


Added TeamWarden App to website showcase

My update is to the app showcase on the react native website, adding my TeamWarden iOS and Android app (in alphabetical order)

Not yet, but thanks hehe :shipit:


Remove dependency on JCoffeeScript

Hi Edvinas,
I have made a lot of changes. It suited me, but not sure how you feel about it. The changes were mainly prompted by my need to have a newer version of Rhino that was being used by JCoffeeScript.
I have stripped out all the Module stuff as I don't believe it to be required any more - or am I missing something?
Let me know what you think!
Thanks for your time,
Eamonn

I am very sorry for my late response. I had some holidays. But I am really happy for this pull requests.
Thanks a lot!

Thanks for accepting!


Added support for SSR on regions and refactored to remove handlers

Refs #418

it would be useful if we also add tests in frint-react-server, where we renderToString() an App with a Child App.

top notch work, @jcampalo! 💖
many thanks for fixing this :D
please feel free to collaborate with @rbardini regarding the merge and release. he can sort out your npm access too if needed.

Coverage dropped below 97%, that's why the build is failing: https://travis-ci.org/frintjs/frint/builds/402709904#L5487


Cannot change theme

System Details
— OS: Windows 11 23H2
—Thorium Version: 126.0.6478.231 (64-bit)
Problem
In an older version like Thorium 124, I can change theme normally and seem working very well. But since I updated to 126, a table has flipped, I cannot change theme anymore, no matter what I did like choose variant of theme, re-install Thorium, use another profile…
Additional Notes
Here is the screen recording I captured as well, to demonstrate this bug. Thanks!
https://github.com/user-attachments/assets/2c292ecd-340e-4af4-9783-bf3385f5129b

@Fryhey Im seeing issues with Thorium and another project of mine, Codium.
Time to install a Win 11 virtual machine and test lol.

@Fryhey Im seeing issues with Thorium and another project of mine, Codium.
Time to install a Win 11 virtual machine and test lol.

Thanks! I counting on you.

I'm having the same issue. I cannot change the theme. I have installed a theme before, now whenever I try to change to another theme, or even to reset the theme to the default, Thorium crashes.
I was having this issue with 126, and now with version 128.
Windows 11 23H2

I'm having the same issue. I cannot change the theme. I have installed a theme before, now whenever I try to change to another theme, or even to reset the theme to the default, Thorium crashes.
I was having this issue with 126, and now with version 128.
Windows 11 23H2

Same here buddy and version 128 too, seem nothing happen here.

@Fryhey I can recreate this, however it only seems to happen on Windows 11.


Support all kinds of properties file like application(-profile).yaml(or yaml, properties)

Support all kinds of properties file like application(-profile).yaml(or yaml, properties).

Hi, @saragluna .
FYI: I'll merge this PR without your review.


uadk: update file permission on cleanup

Set execution permission on cleanup.sh.
Signed-off-by: Haojian Zhuang<EMAIL_ADDRESS>

The pull request can't be verified by CI. Close and create a new one instead.


add stream block that strips labels

(relabler can do this, but simpler with a dedicated block)

https://github.com/pothosware/PothosBlocks/commit/5436e63f2be7e6e1941645605db257950fe25e7a


Closing persistent alert from inside callback

It would be great to have a way to be able to show a toast an close it inside a callback. It may use when a remote transaction is processing.
Note : According to the material design recomandation, it shouldn't contains an icon.
I'm trying to explain the concept whith a pseudo code.

// here is a sample deferred process
function deferredProcess(params, context) {
	var promise, processor, domInfo;

    context = context || window;
    domInfo = {
    	domId: null
    };

    response = {}; // this should be a response (from remote server for instance)

	// here promise follow the jQuery pattern (done, fail, always) for readability reason
	processor = function(resolve, reject) {
    	// show a presistent notification and
        // set the dialog Id with the id of the DOM element
        // this ID will be use later to close the dialog
    	alertify.delay(0).notify("Loading process", domInfo);

        // do something asynchronously
        doSomethingAsync.done(function(response) {
        	resolve(response);
        }).fail(function(response) {
        	alertify.delay(5).error("An error occurred during processing " + response.message);
        	reject(response);
        }).always(function() {
        	// hiding the persistent dialog
        	alertify.hideMessage(domInfo);
        });
        // hiding the previousDialog.
    }
    promise = new Promise(processor);
    // ...
    return promise;
}

To keep the alertify's chaining, I'll use an object whiches store DOM object information.
The point here is I'm not sure about the relevance of both, the principle and the way of working (as a client like presented above).
I'm also not sure about the way of working with "message stacking". For now, if the "stack" is full, messages are automatically hidden. If the persistent message should be hide, it will be. When the hideMessage is called, the DOM id will give a blank result so nothing happend.
I'll make this soon if a positive feedback is given.

To me it definitely seems useful to be able to close a log message via code, I like that and would like to see it added.
As far as message stacking, that's actually a feature that I've never been 100% thrilled with. To me, it seems that if there's more than one message being displayed at the same time, then something is wrong from a user experience point of view. How many messages is it practical to push to the user as the same time?!
I only bring that up because obviously removing the stacking, or making it non-default at least, would effect the way the manual closing of an element would work, and could potentially make it a lot simpler. So I guess my point is I'm wondering what everybody would think of that?
That's actually the first I've seen the material design spec, and it makes a lot of sense to me. I actually think it would make sense to implement as much of it as we can. As an example of it in action, Angular Material toasts have a global method for hiding an existing message, and that works because there is never more than 1 at a time.

Ok,
I'm inline with that.
I purpose to split the issue in two. The first one is dedicated to never have more than 1 toast at a time, the second one to implement a global method whiches hide the existing message.

That sounds good. Thanks in advance!


always hadoop-master:9000 failed on connection exception: java.net.ConnectException: Connection refused

wordcount output:
cat: Call From hadoop-master/<IP_ADDRESS> to hadoop-master:9000 failed on connection exception: java.net.ConnectException: Connection refused; For more details see:  http://wiki.apache.org/hadoop/ConnectionRefused

@xiaods Not sure you have started hadoop/hdfs. You need start hadoop in the cluster. with
./start-hadoop.sh
Hope this helps

it works. thanks


Enforcing monotonicity within GBLinear

Often we need to enforce monotonicity within a GLM, and currently this can't really be done within GBLinear for XGBoost.
What we could do is include the ability to specify parameters and direction in which we want to enforce monotonicity within each iteration. At the end of an iteration, the coefficients will be set to 0 where monotonicity criteria has failed. The coefficients will then adjust in the next iteration. This will continue until the end of the specified number of iterations.

@melwuong setting failed coefficient to zero would have to be done earlier than the end of iteration.
@mhmoudr I see that you have started working on this. Unless it's just a proof of concept, please try to align the approach to how it was done in gbtree.

Will check what has been done in gbtree, to align the work, mean while my question: is there an already implemented way to pass the parameters other than the one that I am using?

@khotilov, I have returned back to gbtree and cannot find anything related to monotonicity there. unless you mean creating an inline function similar to "BoostNewTrees" and remove illegal trends inside the function.
on the other hand for where we set the coefficients to zero, unless we are doing another round of weights optimization within the same iteration is should be equivalent to setting them to 0 and the end of the iteration and reply on the next iteration to re-optimize weights again.  yes it is adding up to the total number of iterations, but I am assuming that user is giving enough iterations for the model to fit. (please correct me if I am missing something)

See monotone_constraints in https://github.com/dmlc/xgboost/blob/master/src/tree/param.h . It would be useful to make the << and >> overloading reusable.
The constraints would need to be applies before weight update.

@khotilov , I applied some changes to the code keeping the parameter name similar with different structure, mainly to count for handful monotonic factors among thousands of them, as the factor in gbtree relays on passing an array on 0|1|-1 with a length identical to number of factors while in my implementation I am using index with direction assuming the default case that there is not constraint.
on the other hand I have applied weight restriction within the loop, please check and let me know it matches your expectation.


hello, help please

hello chris i want to install monterey on a 6470b probook but none of the efi files i found worked. Can you send me or help me generate one please? I'm on windows

HP probook Elitebook macOS OC page is not sufisant for you ? I can not help more then that


Please make Impossible Domain work for Druid that picks a Domain.

Is your feature request related to a problem? Please describe.
Currently, Impossible Domain isn't pick-able as a Druid, even if you have a Domain. Even adding one via ToyBox doesn't actually add the spells known / domain powers, and adding the feature doesn't give you the level-dependant abilities.
Describe the solution you'd like
Allow a Druid with a Domain picked instead of an Animal Companion to pick Impossible Domain later on to get any other Domain.
Thanks!

Please please please :D

Domain work is coming eventually, just a very complex thing to change so it may be a while.


3dsmax: Refactored publish plugins to use proper implementation of pymxs

Changelog Description
Refactored 3dsmax Publish Plugins
This pull request addresses part of the GitHub issue #4982 by refactoring most of the 3dsmax publish plugins. The primary focus of the refactoring is to replace the usage of rt.execute() with the appropriate implementation using pymxs.
This refactoring improves the overall code quality, performance, and safety of the 3dsmax publish plugins, bringing them in line with best practices and leveraging the full capabilities of the pymxs API.
The reasons for this refactoring are outlined in more detail in the GitHub issue #4982 .
Additional Info:
Some rules of thumb to follow when trying to convert to undocumented pymxs function from MaxScript.

If the function is not encapsulated behind an interface, it likely exists in the pymxs runtime (although possibly undocumented), allowing us to use rt. prefix to access it directly.

In cases where a # symbol is used in the MaxScript function, the equivalent in pymxs can often be achieved using rt.name("foo") to handle the necessary conversion.

Optional arguments are challenging to work with but often follow a very similar pattern to the MaxScript (example:
pymxs = rt.exportFile( path, rt.name("noPrompt"), selectedOnly=True, using=rt.AlembicExport)
MaxScript = exportFile @"{path}" #noPrompt selectedOnly:on using:AlembicExport)

Great. I haven't fully tested it in my side but read the code.
See comment above.


Ensure we keep correct order

Sorting project name should ensure we don't get any random output,
allowing a smoother diff whenever we regenerate the project list.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

/lgtm


Menu bar overlaps image

Here I am again : )
Most pages (or even all?) start with a picture on the top, which is overdrawn a bit by the dark blue menu bar at the top of the webpage.
Since most pictures are just symbol images, it is not so noticeable, but at the Page Bundesvorstand for example the heads of the people in the top row are cut off.
P.S.: if I comment in the wrong place tell me where to report bugs instead.

Hi @alchemiker! Thanks again for reaching out. It's really the menu bar at fault here. Just that the hero images are told to take up a max height of 50vh.  Since I'm reluctant to let hero images display at their natural aspect ratio in order to prevent any from extending beyond the fold, a good compromise might be to just increase the max height to, say, 65vh? Will be part of the next commit.

Hello @janosh, thank you very much for the explanation!
Such things as how to keep pictures at a reasonable size across different devices are what a typical internet user never thinks about... As a noob I would only restrict the horizontal size, but yeah, at certain devices it would cover the whole page and make it obvious that my site were made by a noob ; )
But maybe it could be also an idea to crop the images (or only at pages, which have people in the hero image) from the bottom and not from the top?
In the attachments you can see a screenshot of the page how it is seen on my laptop (Lenovo X201, Windows 8.1, in Mozilla Firefox) so you can estimate the value for max height which is required to avoid such a cropping.

But maybe it could be also an idea to crop the images (or only at pages, which have people in the hero image) from the bottom and not from the top?

It's actually from the bottom and the top so that the image remains centered. That usually works best in the majority of cases. Not so much for this image, I agree.

In the attachments you can see a screenshot of the page how it is seen on my laptop (Lenovo X201, Windows 8.1, in Mozilla Firefox) so you can estimate the value for max height which is required to avoid such a cropping.
I cropped it this morning. Should be slightly better next time the site is built. Together with the increased height allowance, hopefully no more cropped heads. :)

I'll go ahead and close this but feel free to open new issues if you encounter more on our site! Thanks for letting us know each time!


[Chore]: Add XML comments for visible types or members

Many Complier Warnings CS1591 are found in the project.
Any assistance with those would be great!
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/compiler-messages/cs1591?f1url=%3FappId%3Droslyn%26k%3Dk(CS1591)

some examples:
src\Appium.Net\Appium\Interfaces\IHidesKeyboard.cs(42,33): Warning CS1584: XML comment has syntactically incorrect cref attribute 'true'VSBuild |   |
-- | -- | --
  | src\Appium.Net\Appium\Interfaces\IHidesKeyboard.cs(42,33): Warning CS1658: Identifier expected; 'true' is a keyword. See also error CS1041.VSBuild |   |
  | src\Appium.Net\Appium\Interfaces\IHidesKeyboard.cs(42,74): Warning CS1584: XML comment has syntactically incorrect cref attribute 'false'VSBuild |   |
  | src\Appium.Net\Appium\Interfaces\IHidesKeyboard.cs(42,74): Warning CS1658: Identifier expected; 'false' is a keyword. See also error CS1041.VSBuild |   |
  | src\Appium.Net\Appium\MobileBy.cs(69,24): Warning CS1584: XML comment has syntactically incorrect cref attribute 'https://developer.android.com/intl/ru/training/accessibility/accessible-app.html'VSBuild |   |
  | src\Appium.Net\Appium\MobileBy.cs(71,24): Warning CS1584: XML comment has syntactically incorrect cref attribute 'https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIAccessibilityIdentification_Protocol/index.html'VSBuild |   |
  | src\Appium.Net\Appium\MobileBy.cs(80,24): Warning CS1584: XML comment has syntactically incorrect cref attribute 'http://developer.android.com/intl/ru/tools/testing-support-library/index.html#uia-apis'VSBuild |   |
  | src\Appium.Net\Appium\AppiumCommand.cs(277,1): Warning CS1570: XML comment has badly formed XML -- 'Expected an end tag for element 'summary'.'VSBuild |   |
  | src\Appium.Net\Appium\MobileBy.cs(80,101): Warning CS1658: Unexpected character '#'. See also error CS1056.VSBuild |   |
  | src\Appium.Net\Appium\MobileBy.cs(89,24): Warning CS1584: XML comment has syntactically incorrect cref attribute 'http://developer.android.com/intl/ru/tools/testing-support-library/index.html#uia-apis'VSBuild

I would like to possibly help with this; I spotted some that are obvious to amend but the majority are about Missing XML comment for member.
Ideally, do you envision everything having an adequate comment or do you plan to disable the warning in certain classes / for certain scenarios/members etc. ?

Hi @dragojs.
Thank you for reaching out first of all, any help whould do.
The idea is to add comments whenever possible, rather than just disable the warnings.
You can start with a small PR at first and I assume that with time you will be able to send bigger PR's.

If you're still looking for some help, I'd love to contribute. I'm going to fork the repo and take a look tonight. Let me know how I can best work with you.

There are some plain obvious fixes which I touched right away and knocked out about 100 warnings but really I just scratched the surface.
 I'd probably look at how other clients tackled this; can't really think of a better approach

@sambrandt @dragojs I'm not sure where you guys stand with this, but I came across a relatively easy fix for warnings related to cref.
you can check out this PR for examples:
https://github.com/appium/dotnet-client/pull/752

Went the same route; haven't had as much time as I wished to dedicate to this; there are several few improvements on a branch of mine that refers to this, I can possibly try to PR later this week.
Looked a bit in the java client and there's either barely any comments or I'm looking in the wrong place. The python client however does have some comments to serve as inspiration

Hey! Sorry, I started to work, and then life exploded a bit. I'm hoping that this week I can get some traction on this. Thanks for the reference, I'll take a look at it.


feat(scale): add ScaleDegree class and methods on Scale

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

51 of 51 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
669

Relevant Lines:
669

💛  - Coveralls


Update Cargo.toml

Fix Version issue when updating probe-run to support defmt 4

@goldenMetteyya sorry I didn't see your PR and opened #393 .
You also have a failing Changelog check. If you're ok with it - let's close your PR as mine is already ready to be merged with the Changelog change.

Thanks for raising the issue.
There is a new probe-run release (version 0.3.8) that should fix the dependency issue. I will close this PR, but please open a new ticket if you still see any issues with the dependencies.


h function -> svg function to generate virtual-dom. Stringifycation issue using h function with new package vdom-to-html

The use of h from virtual-dom loses it's properties when converting to string with vdom-to-html

Would you mind giving a specific example?

@derhuerst I think your example in the README might workout, but the package virtual-dom-stringify  in your example is marked as deprecated.
The suggested replacement is the package vdom-to-html, however the "virtual-hyperscript" generated from the render function in index.js makes use of the h function.
When you perform the convention of those elements, most properties are lost. My fix uses the svg function instead, which can be converted properly, with the new suggested package vdom-to-html, retaining all the properties in the conversion.

I checked all your PRs together and it still doesn't work, sorry.


GEODE-7033: User Guide - Balance lists in left-hand nav panel

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

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

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

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

[x] Does gradlew build run cleanly?

[n/a] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

After this change, the number of <li> and </li> are the same:
$ grep "<li" geode-book/master_middleman/source/subnavs/geode-subnav.erb | wc -l
706
$ grep "</li" geode-book/master_middleman/source/subnavs/geode-subnav.erb | wc -l
706


Make the builder update index.html in gh-pages branch only

This should make things more mergeable across forks. Have index.html in the master branch be just a sample file with one card and just enough placeholder text that BeautifulSoup knows where to add the card text when building. Then, remove the "push to master" step of the GitHub workflow, and just keep the gh-pages subtree split and push.

Done in 96e8c56.


Additions to Weather Underground client to support weather alerts

Updates to the Weather Underground client to support weather alerts, PoP (probability of precipitation), and initialization function to allow setting metric flag other than at instantiation.

@fowlerk -- Your commits have included getForecastText, but I'm having trouble with it.  Is it operable (or is it something on my side)?  I'm trying to use  wunderground.getForecastText() to get the WU text such as: this: Thursday: Steady light rain this morning. Showers continuing this afternoon. High near 60F. Winds light and variable. Chance of rain 60%.

@aliceand -- Yes, it is operational, this was one of the recent additions I added to the Weather Underground library.  You need to pass an integer period to indicate which forecast text you want to request from the function, like wunderground.getForecastText(0) to request the forecast for the current forecast period.  (You may already be aware, but for others, the 10-day forecast API returns (20) forecast periods (numbered 0-19), which include forecast info for each of the 12-hr periods of the 10-days (including the current period)).  Have a look at the code on my distro here https://github.com/fowlerk/ESP8266-Color-Weather-Station-v8, particularly the drawForecastText function as an example.  I call this (3) times passing 0,1,2 to get the next 36-hours of forecast text to display on the bottom panel.
If you're getting an error indicating the function isn't implemented, you likely need to update your library components with the latest from here (or my distro which includes some new features not yet merged into the master for weather alerts also).

@fowlerk --Thank You!  I appreciate your detailed response.  I should be able to make it work now.


#12716 Customise for Azility environments

Changed settigns that are used to populate SQL Server Agent jobs ....
Our production SQL Server instances use E:\databases as convention for backup location
retain for 1 week (168 hours).  We also have AWS Snapshot backups that are kept for longer.

sorry, accident


Use Builtin Gradle Support

... to facilitate https://github.com/robstoll/atrium/issues/126
gives all the nice things that come with Gradle’s support for JUnit, like IDE integration.
Note:

This is a breaking change, because it removes JunitJacocoPluginExtension’s junitPlatform
I am not completely sure that this implementation maps the old behaviour 1:1, mainly because I found it difficult to understand what the intended behavior was in the first place.
tutteli-gradle-junitjacoco is now little less than a thin wrapper. It only sets some defaults. I would recommend to remove it altogether and set the defaults explicitly in projects. I do not think that the plugin is worth its effort anymore.

Okay, so the plugin will stay. I am happy to incorporate changes until this PR is ready to merge. I also have the changes for atrium prepared.

Thank you very much for your contribution :+1:
I'll adjust a few configurations to my need and merge it then into master. I'll let you know when 0.28.0 is released


Provide public API for providing Java toolchains

We currently have rudimentary support for Java toolchains. There is JavaToolChain which can be set on JavaCompile. For Java compilation, we detect the desired toolchain by looking at the fork options.
The Gradle error-prone plugin provides its own Java toolchain which compiles Java by using the error-prone compiler. To be able to do so it needs to resort to the use of quite some amount of internal Gradle APIs. This can lead to breakage when changing internal APIs as seen in #1645.
We should make it possible for plugin authors to provide its own Java toolchain via a public API. The internal API is currently even exposed on the JavaCompile task: setToolChain should only use the Gradle public API.

There are several use cases, so we might split this issue up:

Build logic asks Gradle for a java tool chain given a Java home, and then attaches it to a task that uses a java tool chain, eg compile task, javadoc task, java exec task, test task, task that uses a worker daemon, and so on.
Build logic asks Gradle for a java tool chain given a Java version, and attaches it to a task
Build logic defines a java tool chain by pointing at the relevant executables.
Build logic accepts a java tool chain and uses the tool chain to do something, eg compile source, generate java doc, run a java app, etc.

We should deprecate specifying the Java tool chain as an executable or as a java home on tasks, and instead pass around tool chain instances. We should also ensure that java tool chains and native tool chains are defined in a consistent way.

Actually, I believe there are more use-cases than this (depending on what we call a "tool chain" actually).

For example, if I need to use JavaC 1.8 (because I have annotation processors that require Java 8) but target Java 7, I then need/want to pass a -bootclasspath with the rt.jar for a JDK 7 (if I used Java 9, I could use -release 7 instead). Admittedly this might not fit the definition of "tool chain" though.

The use case that triggered this issue: using a specific compiler. Here, there are 2 subcases:

the compiler is a standalone tool, e.g. ikvmc (not sure if it really qualifies here, as it doesn't produce Java bytecode), or GCJ (now dead); this is undeniably a "tool chain".
the compiler is itself a Java application and/or could be embedded (called with its own API, or javax.tools.JavaCompiler; e.g. Error Prone, ECJ/JDT, Janino, or something like the Android Jack&Jill experiment); in this case you may want to select a Java tool chain to actually run the compiler (e.g. Error Prone requires Java 8, fails with Java 9, so you may want to run your Gradle build with either Java 7 or Java 9, and configure a Java 8 toolchain to run Error Prone – and then you'll possibly want to pass a -bootclasspath to target another platform, see above).

The Error Prone / ECJ / etc. use case might be different from the Java tool chains usecases. The gradle-errorprone-plugin current uses a JavaToolChain because I don't think there's an alternative; but it needs to duplicate a bunch of code from Gradle internals, and does not use a daemon process (IIRC because internal APIs have changed between Gradle versions). Having an API to plug those alternate compilers (resolving their dependencies from the project's configurations) while benefiting from all that Gradle has to offer would be great; but that would likely be a different API than JavaToolChain.
WDYT?

We use gradle for our internal SE experiments and have intensive use of toolchain configurations. It is necessary for us to use very old versions of the Java toolchain and also to configure and access the members of the toolchain and environment. While we currently roll our own this pretty quickly sown and I would love to replace our designs with something that writes to a clean standard API.

Fwiw, Error Prone can be crossed out of the usecases here, as it's converging towards being used through -Xplugin (implementing com.sun.source.util.Plugin). It even works with Java 8 if you fork the compiler and add the Error Prone javac to the bootclasspath (see https://github.com/google/error-prone/issues/535#issuecomment-414165838)

Please have the following use case in mind as well: When using Gradle within Eclipse, it uses the JVM used to run Eclipse itself by default. Eclipse requires JDK 11 for itself since 2020-09, depending on plugins maybe even since 2020-06 already. When one has JDK 8-projects only, those are build by default using JDK 11 now, when Gradle tasks are executed using the Gradle task view in Eclipse. To change that, one needs to configure a JDK for Gradle only within Eclipse.
It would be great if that manual configuration wasn't necessary and instead one could make Gradle aware of different installed JDKs and tell in the project to always use some of those. Regardless what the JDK used to execute a parent process like Eclipse.
This is especially important because when one uses a shell within Eclipse to execute Gradle tasks, the system wide JDK might be used again, which might differ from the one used to run Eclipse itself. In my case I really configured to use JDK 11 for Eclipse only in eclipse.ini:
[...]
openFile
--launcher.appendVmargs

-vm
C:\Program Files\Java\jdk-11\bin\client\jvm.dll

-vmargs
-Dosgi.requiredJavaVersion=1.8
[...]

Toolchains are going to be part of the 6.7 release. Given this issue started to collect multiple distinct use-cases (several of them are already covered), I'm going to close this one for now. If you find a use-case that is not yet covered by the current toolchain feature, please feel free to create specific issues for those. You can also watch the epic #2203 which is going to track the work we plan on doing for 6.8 as well.


fixture: Upgration of 'marked' package

Due to  the vulnerabilities for this package, this is the fixture to update it and pass the test locally.
For details，

                             Manual Review
         Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance

Low             Regular Expression Denial of Service
Package         marked
Patched in      >=0.7.0
Dependency of   metalsmith-markdown
Path            metalsmith-markdown > marked
More info       https://nodesecurity.io/advisories/1076
found 1 low severity vulnerability in 4559 scanned packages
1 vulnerability requires manual review. See the full report for details.

@woodyrew , have a review thanks!

@woodyrew or whoever has push rights. Can you guys please merge the deps PRs?

Thanks for the PR, it has been fixed in 1.3.0 of metalsmith-markdown


handleAllocBoxInst() in InstrKindInfoGetter causes segfault

extension Collection {
  @_inlineable
  public func split() {

    func appendSubsequence() {
      var x = self.count
    }

      _ = appendSubsequence()
  }
}

This is the minimal test case that will crash the compiler. Hope this is helpful.

@Leeleo3x is that now fixed or is it still open?

@mmroz is working on this issue but I'd like to help Mark to solve this issue since he is busy with #22

gotcha! Thanks for chipping in.


Add support multiple valid principals and source ips in requested certificates.

Resolved in https://github.com/Netflix/bless/pull/38


service: fix navigation for associations with many to one relationships and for associations with relationships to same entity

When playing around with the OData API of the SAP Analytics Cloud to retrieve some stories, I have noticed that the nav method did not work with many to one relationships. The SAC API specifies such an relationship between a story and users (createdByUser, a story can be created only by one user, but a user can create many stories): Either you have to specify a key for the nav method or to use the get_entities method which both not works as the target entity is not a list of entities (the entity is returned directly and not in a results array) or as an invalid url is generated (the target entity is being indexed, which does not work as it is not an list).
I have tracked down this issue down to line 886 (and 1362) where the multiplicity for all roles is checked and when the multiplicity for one of the role is "*" the check fails. Here only the multiplicity of the "ToRole" should be checked as this role is the relevant role for the navigation.
Additionally when writing a test for this case I have found another issue: It is not possible to use the nav method with associations where both ends are of the same entity type. The logic for finding the navigation_entity_set in line 877-880 (and 1352-1359) is using the entity set name for finding the role in the association set: This does not work if both roles has the same entity set name. Here the method end_by_role method of the association set can be used to find the correct role (and then the correct navigation_entity_set).

Hi @ Masterchen09
Thank you for not only uncovering more than one problem, but also providing fix for all of them.


Azure App Service Deploy: Can't change which service connection is used

We moved from a PAYG subscription to an EA one, which means I need to update the service connection used for deployments...

The system won't let me update the existing service connection, presumably because it was authorised in a different AD.  I've successfully created a new service connection,  but I can't pick it in the deploy parameters .
If I create a new App Service Deploy task, the new service connection appears there, but that would mean re-creating every deployment task which is error prone.
Is there a better way?

@phatcher , Azure subscription is linked to process parameters.
Click on the Environment name and that will show the process parameters.
Then u can change the Azure subscription.

@vincentdass Thanks for that, I have to re-enter the resource group/slot settings, but that's to be expected.
Might be an idea to put another link on the Azure App Deploy that points you at the Deployment process parameters page, e.g. Update vs Manage - I haven't had to touch this for ~9 months or so which is why I forgot.

Slightly odd, modifying a different pipeline that was created ~2.5 years ago and this one doesn't have any environment process parameters, but the Azure App Service deploy parameters shows refresh circles...

@vincentdass Thanks for the update


Widgets built twice before layout phase in the same frame

This issue is separated from #75308
How does it happens and repro steps please refer to the original issue.
CC @chunhtai

@xu-baolin Hi,
Per the PR discussion, I assume you opened this issue to track https://github.com/flutter/flutter/pull/75308#pullrequestreview-585737136
The original issue / PR talks about fixing 2 issues. Which one among them indicates / replicates the focus manager issue ?
Could you provide steps to replicate ?

https://github.com/flutter/flutter/pull/75308#pullrequestreview-584562834
  // Regression test for https://github.com/flutter/flutter/issues/72257
  testWidgets('NestedScrollView works well when rebuilding during scheduleWarmUpFrame', (WidgetTester tester) async {
    bool? isScrolled;
   int buildCnt = 0;
    final Widget myApp = MaterialApp(
      home: Scaffold(
        body: StatefulBuilder(
          builder: (BuildContext context, StateSetter setState) {
            return Focus(
              onFocusChange: (_) => setState( (){} ),
              child: NestedScrollView(
                headerSliverBuilder: (BuildContext context, bool boxIsScrolled) {
                  buildCnt++;
                  isScrolled = boxIsScrolled;
                  return <Widget>[
                    const SliverAppBar(
                      expandedHeight: 200,
                      title: Text('Test'),
                    )
                  ];
                },
                body: CustomScrollView(
                  slivers: <Widget>[
                    SliverList(
                      delegate: SliverChildBuilderDelegate(
                        (BuildContext context, int index) {
                          return const Text('');
                        },
                        childCount: 10,
                      ),
                    )
                  ],
                ),
              ),
            );
          },
        ),
      ),
    );

    await tester.pumpWidget(myApp, Duration.zero, EnginePhase.build);
    expect(isScrolled, false);
    expect(buildCnt, 2);
    expect(tester.takeException(), isNull);
  });

@xu-baolin
Running above test leads to below:

 test result log
Testing started at 3:45 PM ...
/Users/dhs/Documents/Fluttersdk/flutter/bin/flutter --no-color test --machine --start-paused --plain-name "NestedScrollView works well when rebuilding during scheduleWarmUpFrame" test/widget_test.dart

══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
The following assertion was thrown during a scheduler callback:
'package:flutter/src/widgets/nested_scroll_view.dart': Failed assertion: line 798 pos 14:
'position.hasContentDimensions && position.hasPixels': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      _NestedScrollCoordinator.hasScrolledBody (package:flutter/src/widgets/nested_scroll_view.dart:798:14)
#3      NestedScrollViewState._handleHasScrolledBodyChanged (package:flutter/src/widgets/nested_scroll_view.dart:602:51)
#4      _NestedScrollCoordinator.updateShadow (package:flutter/src/widgets/nested_scroll_view.dart:806:50)
#5      _NestedScrollController._scheduleUpdateShadow.<anonymous closure> (package:flutter/src/widgets/nested_scroll_view.dart:1303:21)
#6      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144:15)
#7      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090:9)
#8      AutomatedTestWidgetsFlutterBinding.pump.<anonymous closure> (package:flutter_test/src/binding.dart:969:9)
#11     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:72:41)
#12     AutomatedTestWidgetsFlutterBinding.pump (package:flutter_test/src/binding.dart:956:27)
#13     WidgetTester.pumpWidget.<anonymous closure> (package:flutter_test/src/widget_tester.dart:522:22)
#16     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:72:41)
#17     WidgetTester.pumpWidget (package:flutter_test/src/widget_tester.dart:519:27)
#18     main.<anonymous closure> (file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart:82:18)
#19     main.<anonymous closure> (file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart:43:89)
#20     testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:144:29)
<asynchronous suspension>
<asynchronous suspension>
(elided 7 frames from class _AssertionError, dart:async, and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════
The following assertion was thrown during a scheduler callback:
'package:flutter/src/widgets/nested_scroll_view.dart': Failed assertion: line 798 pos 14:
'position.hasContentDimensions && position.hasPixels': is not true.

Either the assertion indicates an error in the framework itself, or we should provide substantially
more information in this error message to help you determine and fix the underlying cause.
In either case, please report this assertion by filing a bug on GitHub:
  https://github.com/flutter/flutter/issues/new?template=2_bug.md

When the exception was thrown, this was the stack:
#2      _NestedScrollCoordinator.hasScrolledBody (package:flutter/src/widgets/nested_scroll_view.dart:798:14)
#3      NestedScrollViewState._handleHasScrolledBodyChanged (package:flutter/src/widgets/nested_scroll_view.dart:602:51)
#4      _NestedScrollCoordinator.updateShadow (package:flutter/src/widgets/nested_scroll_view.dart:806:50)
#5      _NestedScrollController._scheduleUpdateShadow.<anonymous closure> (package:flutter/src/widgets/nested_scroll_view.dart:1303:21)
#6      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144:15)
#7      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090:9)
#8      AutomatedTestWidgetsFlutterBinding.pump.<anonymous closure> (package:flutter_test/src/binding.dart:969:9)
#11     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:72:41)
#12     AutomatedTestWidgetsFlutterBinding.pump (package:flutter_test/src/binding.dart:956:27)
#13     WidgetTester.pumpWidget.<anonymous closure> (package:flutter_test/src/widget_tester.dart:522:22)
#16     TestAsyncUtils.guard (package:flutter_test/src/test_async_utils.dart:72:41)
#17     WidgetTester.pumpWidget (package:flutter_test/src/widget_tester.dart:519:27)
#18     main.<anonymous closure> (file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart:82:18)
#19     main.<anonymous closure> (file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart:43:89)
#20     testWidgets.<anonymous closure>.<anonymous closure> (package:flutter_test/src/widget_tester.dart:144:29)
<asynchronous suspension>
<asynchronous suspension>
(elided 7 frames from class _AssertionError, dart:async, and package:stack_trace)
════════════════════════════════════════════════════════════════════════════════════════════════════
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test:
  Expected: <2>
  Actual: <1>

When the exception was thrown, this was the stack:
#4      main.<anonymous closure> (file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart:84:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)
...

This was caught by the test expectation on the following line:
  file:///Users/dhs/Documents/NCFlutter/webtest/test/widget_test.dart line 84
The test description was:
  NestedScrollView works well when rebuilding during scheduleWarmUpFrame
════════════════════════════════════════════════════════════════════════════════════════════════════
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following message was thrown:
Multiple exceptions (3) were detected during the running of the current test, and at least one was
unexpected.
════════════════════════════════════════════════════════════════════════════════════════════════════

Test failed. See exception logs above.
The test description was: NestedScrollView works well when rebuilding during scheduleWarmUpFrame

mainly, throws below exception:
══╡ EXCEPTION CAUGHT BY SCHEDULER LIBRARY ╞═════════════════════════════════════════════════════════ The following assertion was thrown during a scheduler callback: 'package:flutter/src/widgets/nested_scroll_view.dart': Failed assertion: line 798 pos 14: 'position.hasContentDimensions && position.hasPixels': is not true.
Is this the correct interpretation of the the issue logged ?

This will be fixed by the original issue.

After the original issue fixed, it will build twice still.

Just came across this during triage, could https://github.com/flutter/flutter/issues/11599 be related?

Hello @xu-baolin,  I verified this issue on the latest master channel and it seems that this is fixed. the test fails with actualy buildCnt = 1, So I believe that this is fixed.
Logs
mahesh@Maheshs-MacBook-Air-M1 flutter_issue % flutter test
00:01 +0: NestedScrollView works well when rebuilding during scheduleWarmUpFrame
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure was thrown running a test:
Expected: <2>
  Actual: <1>

When the exception was thrown, this was the stack:
#4      main.<anonymous closure> (file:///Users/mahesh/Desktop/flutter_issue/test/widget_test.dart:56:5)
<asynchronous suspension>
<asynchronous suspension>
(elided one frame from package:stack_trace)

This was caught by the test expectation on the following line:
  file:///Users/mahesh/Desktop/flutter_issue/test/widget_test.dart line 56
The test description was:
  NestedScrollView works well when rebuilding during scheduleWarmUpFrame
════════════════════════════════════════════════════════════════════════════════════════════════════
00:01 +0 -1: NestedScrollView works well when rebuilding during scheduleWarmUpFrame [E]
  Test failed. See exception logs above.
  The test description was: NestedScrollView works well when rebuilding during scheduleWarmUpFrame

To run this test again: /Users/mahesh/Development/flutter_master/bin/cache/dart-sdk/bin/dart test /Users/mahesh/Desktop/flutter_issue/test/widget_test.dart -p vm --plain-name 'NestedScrollView works well when rebuilding during scheduleWarmUpFrame'
00:01 +0 -1: Some tests failed.

flutter doctor -v
[!] Flutter (Channel feat-39118, 3.7.0-10.0.pre.68, on macOS 13.1 22C65 darwin-arm64, locale en-IN)
    • Flutter version 3.7.0-10.0.pre.68 on channel feat-39118 at /Users/mahesh/Development/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/mahesh/Development/flutter/bin/flutter, which is not inside your
      current Flutter SDK checkout at /Users/mahesh/Development/flutter_master. Consider adding
      /Users/mahesh/Development/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/mahesh/Development/flutter/bin/dart, which is not inside your current
      Flutter SDK checkout at /Users/mahesh/Development/flutter_master. Consider adding
      /Users/mahesh/Development/flutter_master/bin to the front of your path.
    ! Upstream repository https://github.com/maheshmnj/flutter.git is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to https://github.com/maheshmnj/flutter.git to dismiss this error.
    • Framework revision 34679a7c65 (4 weeks ago), 2022-12-20 14:16:43 -0500
    • Engine revision 3330cce605
    • Dart version 3.0.0 (build 3.0.0-35.0.dev)
    • DevTools version 2.20.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to
      perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
    • Android SDK at /Users/mahesh/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0-rc4
    • ANDROID_HOME = /Users/mahesh/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14A400
    • CocoaPods version 1.11.3

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

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

[✓] IntelliJ IDEA Community Edition (version 2021.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 61.2.4
    • Dart plugin version 212.5080.8

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

[✓] Connected device (3 available)
    • iPhone 12 Pro (mobile) • 026D5789-9E78-4AD5-B1B2-3F8D4E7F65E4 • ios            •
      com.apple.CoreSimulator.SimRuntime.iOS-14-5 (simulator)
    • macOS (desktop)        • macos                                • darwin-arm64   • macOS 13.1 22C65 darwin-arm64
    • Chrome (web)           • chrome                               • web-javascript • Google Chrome 108.0.5359.124

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

! Doctor found issues in 1 category.

Closing as fixed. Incase you still encounter the issue, then please feel free to write in the comments and we will reopen it.


"Unexpected EOF" error

When extracting /System/Library/FeatureFlags/Global.plist from iPhone_4.7_14.5_18E199_Restore.ipsw rootfs (038-44862-252.dmg), I get an "unexpected EOF" error:
$ apfs cp 038-44862-252.dmg /System/Library/FeatureFlags/Global.plist
   ⨯ unexpected EOF

Running with -V gives confusing log messages, like it was traversing an unrelated directory when the error happened...

I just ran it successfully on 19A5261w__iPhone11,8_iPhone12,1/iOS15b2_018-22754-059.dmg
Can you tell me what IPSW that dmg came from?

I'm using iPhone_4.7_14.5_18E199_Restore.ipsw.
(unrelated, this made me realize I should have been using the _P3_ ipsws all along since I'm on iPhone 7 :man_facepalming:)

This should be fixed now


Issue with scrapping transactions from Discount

Details
I got the error: EROFS: read-only file system, open 'transaction.csv'
Log
[2022-07-19 17:48:07.721] [info]  LOGGING_IN
[2022-07-19 17:48:09.606] [info]  LOGIN_SUCCESS
[2022-07-19 17:48:10.666] [info]  TERMINATING
[2022-07-19 17:48:10.740] [info]  END_SCRAPING
[2022-07-19 17:48:10.746] [info]  Importer end
[2022-07-19 17:48:10.758] [info]  EXPORT_PROCESS_START
[2022-07-19 17:48:10.763] [info]  Starting
[2022-07-19 17:48:10.799] [error] EROFS: read-only file system, open 'transaction.csv'
[2022-07-19 17:48:10.805] [error] EROFS: read-only file system, open 'transaction.csv'

System Info

Source Version: 5994cb2d871fae918e9e010943c537d7a67ece61
OS: darwinx64
OS Version: 22.0.0

Hi, thank you for reporting!
It is not the first time I see this error on Mac, I think you should change the CSV file location, just click on the CSV file textbox and choose your desktop, for example.
You're welcome to join our Discord channel to find people that already solved this.

CSV export works for me, if this is still an issue please reopen


update maven repo

Please add 1.18 version to your https://eldonexus.de/ repo :) Big thnx! Great work!

It is https://eldonexus.de/#browse/browse:maven-snapshots:com%2Fgithub%2Fyannicklamprecht%2Fworldborderapi%2F1.18.0--SNAPSHOT
Use the snapshot for now.

Is fixed now. https://eldonexus.de/#browse/browse:maven-releases:com%2Fgithub%2Fyannicklamprecht%2Fworldborderapi%2F1.180.0
Readme is updated as well.


JCore brownfield alerts fixes sep2023

Overview/Summary
Deployment Name too long and Critical Updates Missing failure (V2.1.2)
This PR fixes/adds/changes/removes

c_AVD-HP-VM-MissingCriticalUpdates deployment would fail due to search syntax incorrectly defined
c_AVD-StorAcct-Over-100msLatencyClnt-Stor deployment name was still too long depencing on the name of the storage account appended
Additonal Alert names truncated to avoid deployment name length being over 64 characters
(Trying to avoid logic to use GUIDs for clarity during deployment)
Removed Automation Account Diagnostics log retention which was deprecated (CARML)
Removed Alert - Missing Critical Updates as Table 'Update' is deprecated
Updated logic for host pool name to truncate if over 20 characters long only during deployment
VM Memory and CPU logic changed from checking every 1 min to every 5 min with thresholds based on 15 min vs 5 min average. (5/15 vs 1/5)
This was done to resolve false alerts during VM startup.

Breaking Changes
N/A
Testing Evidence
Redeployed in lab for both commercial and US Gov - successful
As part of this Pull Request I have

[X ] Read the Contribution Guide and ensured this PR is compliant with the guide
[X ] Ensured the resource API versions in .bicep file/s I am adding/editing are using the latest API version possible
[X ] Checked for duplicate Pull Requests
[X ] Associated it with relevant GitHub Issues
[X ] (AVD LZA Team Only) Associated it with relevant ADO Items
[X ] Ensured my code/branch is up-to-date with the latest changes in the main branch
[ X] Performed testing and provided evidence.
[ X] Updated relevant and associated documentation (e.g. Contribution Guide, Module READMEs, Docs etc.)

@JCoreMS thanks for your contribution.


1 Hit kill/death

I'm having issues with killing and being killed with 1 hit regardless of armor/weapons/ETC. I noticed I have "green" attributes on my adventure tab (that was introduced by Apotheosis 6.3.0). I've diagnosed the issue, and the culprit seems to be a default setting of some sort. I've done multiple New Worlds, and config resets with no change. I have 100% Crit Chance, 100% Life Steal, and 100% Current HP Damage. (I'm assuming this effect applies to mobs too, as they kill me in 1 hit) I've attempted to remove and change the versions of my added mods, with no defining results. I'm planning on starting an LP soon, and I really want to show off the most recent update of this mod specifically. Thanks in advance!
**If you'd like a video of this issue, I can provide one on request.
Issue at hand:

Modlist:

Guess it was simply a random error from my configs. I scoured them too, I couldn't find anything that could pose an issue. Thanks for the quick reply, everything seems to be in order now.


Update pyproject.toml

Pull Request Template
Description
Removed pyproject.xyz sections. Trying to see if poetry add tsbootstrap and poetry add tsbootstrap -E all-extras will work, just as pip install tsbootstrap and pip install tsbootstrap[all-extras] does.
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] My changes generate no new warnings

Hmm let me reassess
Intentional.

On Fri, Mar 29, 2024, 6:54 PM Franz Király @.***> wrote:

@.**** requested changes on this pull request.

removal makes sense
do we want to add all that stuff to the dev dep set? Not sure if we
even need it?
are the changes in tests/test_time_series_simulator.py accidental or
intentionally in this PR?

—
Reply to this email directly, view it on GitHub
https://github.com/astrogilda/tsbootstrap/pull/115#pullrequestreview-1969667627,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFTOOHSN5MPTADA5EZXJQTLY2XPHRAVCNFSM6AAAAABFNUPVCCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTSNRZGY3DONRSG4
.
You are receiving this because you were assigned.Message ID:
@.***>

could you delineate the packages you think are not required? @fkiraly

My default guess would be, strictly speaking none, since the CI had worked fine before that?
A slightly more permissive guess would be, only packages that are being mentioned in the contributor guide? E.g., to lint your code, do xyz. Or, those referenced in pre-commit-config?


[MB-11929] remove expired 2017 RDS cert

MB-11929
Summary
This is the final step in updating the RDS certificates. This removes all references to the expired 2017 RDS cert. This includes the dockerfiles as well as the main_test.go file.

Messages

:book:
:link: MB-11929

  Generated by :no_entry_sign: dangerJS against a7e63edcb73ed3c9e693b364d2babc227fa89f13


113 사업분야 코드 목록 API

Closes #113

Codecov Report

Merging #114 (0042838) into main (966325d) will increase coverage by 4.14%.
The diff coverage is 7.69%.

@@             Coverage Diff              @@
##               main     #114      +/-   ##
============================================
+ Coverage     48.80%   52.95%   +4.14%
- Complexity      101      105       +4
============================================
  Files            43       44       +1
  Lines           461      474      +13
  Branches          3        3
============================================
+ Hits            225      251      +26
+ Misses          236      223      -13

Impacted Files
Coverage Δ

...m/benecia/domain/enterprise/domain/Enterprise.java
18.18% <0.00%> (-0.87%)
:arrow_down:

...erprise/presentation/EnterpriseCodeController.java
33.33% <0.00%> (-16.67%)
:arrow_down:

...main/enterprise/service/EnterpriseCodeService.java
9.09% <0.00%> (-7.58%)
:arrow_down:

...n/enterprise/domain/businessarea/BusinessArea.java
16.66% <16.66%> (ø)

...necia/domain/enterprise/code/BusinessAreaCode.java
80.64% <0.00%> (+80.64%)
:arrow_up:

Continue to review full report at Codecov.

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


Allow 3-Digit TIDAL Artist IDs and Bump Dependence Versions

John Williams, the composer for Star Wars and much more, has TIDAL artist ID of 160. Previous to this pull request, only 4-digit to 9-digit IDs were allowed; this is changed.
A few Python package dependencies have bumped minor versions, so those are brought in by this pull request as well.

UPDATE: two-digist artist IDs are valid; the lowest valid value that I have found is 53; that of Neil Diamond!


Ability to view current stack within StackNavigator

Added the ability to view the current stack within StackNavigator. Fixes #427

Well the stack property should only be updating when the route changes because it is whatever the current stack of routes is. So why would it be out of date? If the route changes, then it will get updated accordingly.
Also, I would be happy to add it to other navigators but I have only been working with the StackNavigator and, therefore, that is where most of my familiarity lies.

I believe we can do it with onNavigationStateChange. You can listen to scene changes and use e.g. redux or setState to store its value.

What's missing to get this merged? @grabbou @stief510


Added fromEuler and fromUV to Quat

I've merged it but on thing to notice is that your yaw, pitch, roll is using radians and we usually use angles.

Published as<EMAIL_ADDRESS>


First edits for russian locale

Hello!
Now I would like to learn more about the review and localization process on the project. Therefore, localization is only partial.
Thanks!

hey :)
you don't need to commit the changes to locale/ru.js, there's weekly automation to update these based on the .po files, but since it's a new file, no harm updating it either :)
If you're updating the list of languages in lingui.config.js, remember to also update src/l10n.ts - the availableLanguages array and languageNames - that's what the UI uses to actually display anything.
Other than that, looking good, you can also sanity-check the .po file by running lint-po (from pypi) - npm run lint:po does that.
(And also note that anything coming from the API would still be in English, unless you also add the new language to ansible/galaxy_ng for the backend.)
(repo tests are currently red, fair warning, actually merging things might take a while)

Hello, @himdel !
Me update PR:

fixed one error in ru.po after linting with npm run lint:po;
translated more strings;
commits squashed.

Hello, @himdel !
What I must do for merging this PR into master?

Oh, I'm sorry I didn't realize it was ready..
the code looks good :+1: thanks!,
kicking the linter workflow...

Oh, two things please...

we have a no merge commits policy, can you squash the changes please? (or remove the merge commit)
can you rebase on top of current master please? There were some pipeline fixes that should make the tests go green :)

All my commits are squashed into one.

master branch on my fork is updated. This branch is rebased over him.

Local run npm run lint:po is success:
><EMAIL_ADDRESS>lint:po
> lint-po locale/*.po

How to run additional checks locally for quality improvements?

Thanks, I have to trigger the workflow manually for new contributors,
looks like npm run prettier should fix the pr-checks issue,
maybe also run npm run gettext:extract && npm run gettext:compile, it should auto-run over the weekend but looks like it doesn't match now.
And Cypress is likely to pass, I'll try to restart any random failures :)

Hello, @himdel !
Thanks for your answers!
Me run manually npm run prettier and other commands from your commentary. PR is updated.

Thanks for doing all that!
This is now ready to be merged, don't worry about the screenshots test, that's expected, I'll take it from here :)