handle mapped_invars correctly in more places

fixes #2822
We didn't handle mapped_invars correctly in all places in #1959. In
particular, in #1959 we:

assumed the mapped_invars parameter of xla_pmap_p was only
populated after partial_eval and set to None otherwise (i.e.
staging out for a jit or a control flow primitive),
didn't update it correctly in JVPTrace.process_map (which adds new
inputs corresponding to nonzero tangents, and hence mapped_invars
must be grown),
didn't update it correctly in JaxprTrace.process_map (which adds
inputs to the staged-out version of the primitive,
didn't forward it correctly in JaxprTrace.process_map anyway (we
were setting it to all-true for the staged out eqn),
removed the leading axes of all pvs in JaxprTrace.process_map
regardless of whether the corresponding entry of mapped_invars
was True or False.

The reason we didn't notice 2 and 3 was that they only arise when doing
control flow (e.g. scan or remat) of pmap involving closed-over tracers
(apparently a rare case), since that's the case where we first form a
jaxpr (populating mapped_invars) and then later have to apply
transformations like AD and further partial eval (thus engaging
JVPTrace.process_map and JaxprTrace.process_map with a populated
mapped_invars parameter). It worked in other cases, e.g. when the pmap
was not inside control flow or a remat, because in those cases we left
mapped_invars set to None, indicating all-true of any length (so it
didn't matter if we add inputs).
This commit fixes those issues by

making mapped_invars non-optional (even though the default value
of None is convenient as long as it lasts, it's not worth the
complexity of handling the two None-or-populated cases everywhere
downstream),
handling mapped_invars correctly in
* JaxprTrace.process_map
* JVPTrace.process_map
* ad.map_transpose (since having symbolic-zero cotangents
effectively prunes inputs, and having undefined-primal args also
prunes inputs)
* ad._eval_subjaxpr_primals (since having undefined-primal args
prunes inputs)
making the separate cases of calls and maps handled more explicity
by adding a new Primitive.map_primitive boolean attribute
(analogous to Primitive.call_primitive).

This is begging for a more coherent cleanup. For example, we reuse the
same Primitive class but tag it with call_primitive or map_primitive
(only one of which can be True); we should instead just have a separate
Primitive class for these cases and track the type tag with built-in
Python mechanisms. Moreover, when call_primitive=True or
map_primitive=True implies things about what params must be present
(call_jaxpr and mapped_invars). I plan to follow up with those
cleanups, but I wanted to get something working first.

Attn @gnecula @jekbradbury for interest!

Cleanup in #2829.

Thanks for the review, @jekbradbury !

I hope that this added test would cover all the newly added code.


Error with jQuery 1.6.4

Got an error in jQuery.js
"a.isResolved is not a function"
With 1.4.2a everything is fine.

I have the same issue - any updates? (using jquery 1.7.1)

No.
But i solved it for my part.
At the top of document i use a newer version of jQuery globally.
Later in the document i switch to the older version like this:
<script src="jquery.142a.js" type="text/javascript"></script>
<script src="jquery.xdomainajax.js" type="text/javascript"></script>
<script>
  //<![CDATA[
    $(document).ready(function() {
      $("#mycontainer").load("http://www.somedomain.de #somecontainer", function(response, status, xhr) {
      if (status == "success") {
         // do the kung fu
        }
      if (status == "error") {
        var msg = "Sorry but there was an error: ";
        $(".page_content").html(msg + xhr.status + " " + xhr.statusText);
      }
      });
    });
  //]]>
</script>

I hope this could work for you too.


struct DisjointMut: unsafe impl Send + Sync

Does this reasoning make sense?
In particular, I'm unsure about the provenanceless thing and data races not leading to memory unsafety.  Is this worth it to say?  Is it worth it to add an unsafe trait Provenanceless to ensure such a thing at a more detailed level?  I do think it's an important point that data races won't lead to memory unsafety, though.

Do we need the T: Send + Sync bounds in the unsafe impl Send + Sync here?  Because as is, Rav1dPictureDataComponent is not Send or Sync (which we need it to be) since it contains a ptr: NonNull<u8>.  This ptr is not Sync, however, as no synchronization is done.

I think we need to require it. If that pointer is indeed safe to share we need to mark it as such.

I think we need to require it. If that pointer is indeed safe to share we need to mark it as such.

It's not safe, though.  That's the problem.

Let me think about it some more.


feat: fix bugs with status command

fix a bug where we pulled the beacon state head even if we have an old checkpoint
fix a bug where we compute the wrong diff if the pod owner queues a withdrawal
still an outstanding bug: i think sumRestakedBalancesGwei also needs to use a prior state if we have an existing checkpoint

Sharing some screenshots displaying bugfix #1.
Running status on our preprod test pod, which has had a checkpoint active since yesterday, the master branch shows:

As you can see, the master branch uses the head state. This branch downloads the correct state:

Bug # 2 explanation:
This bug occurs when the pod owner queues a withdrawal in the DelegationManager. The bug is that queuing a withdrawal results in a decrease of shares - so you had 32 ETH of shares, then you queued a withdrawal, now you have 0 ETH of shares.
When a checkpoint is completed in the pod, the change in shares is applied as a delta - so if you have gained 0.01 ETH, the checkpoint would add 0.01 ETH to your current shares, for a new total share count of 0.01 ETH.
The CLI bug here is that the master branch version computes your new shares as a total share value, rather than a delta. It sees that you have 32.01 ETH total assets, so assumes that completing the checkpoint will result in 32.01 ETH worth of shares. Since we have 0 ETH worth of shares at the moment due to our queued withdrawal, the master branch will assume that completing a checkpoint will result in a diff of 32.01 ETH.
The change in this PR correctly calculates a delta rather than using a total.

Bug # 2 testing:
To test this change, I am manually altering the value returned when the status command fetches currentOwnerShares (on both master and this branch):
https://github.com/layr-labs/eigenpod-proofs-generation/blob/4acc4b03c09df33855c6d97467476f563cc3508c/cli/core/status.go#L157
This effectively simulates running the status command after the user has queued a withdrawal for all their shares. Then, running status command on master yields:

As you can see, master assumes we can get 64 ETH worth of shares from a checkpoint. This PR fixes this:

Noting another buggy thing - if i partially complete a checkpoint, status doesn't show that the checkpoint is partially completed!

Bug # 3 explanation:
If we have partially completed a checkpoint, status will not correctly compute the share diff for finishing the checkpoint. This is because it will base the beacon chain ETH delta portion of the share diff on the current checkpoint state, which has already ingested a few updated validator balances.
Those validators' balance diffs will not be accounted for in the delta the CLI calculates. To fix this I need to consider whether there's a way to use checkpoint.balanceDeltasGwei to correct the diff. Alternatively we can use the ETH rpc to read the pod's state when the checkpoint was started rather than partway through.
Not sure what's better here. TBH I think this is a fairly minor issue and the PR here is already a good improvement, so this might be something we want to earmark for a future fix.


Add support for per workspace member locks

This functionality can be enabled by setting tools.rye.workspace.per_member_lock to true
Added a test for the new functionality as well as one for workspaces on its own (as there didn't seem to be any).
Closes #615

This is my first ever rust pr, so any feedback is welcome and appreciated! If anything needs to be changed, "allow edits by maintainers" is on, or post a comment and I'll change the pr accordingly

The windows test failures are a bit confusing.
Failure 1: (link)
It seems like uv functions differently in linux/macos and windows. Its reinstalling both workspace members even tho only one of them changed.
Failure 2: (link)
Ordering seems to be different in windows, (not only in that failure, but all through the test results). A #[cfg(unix)] block would not work here, as there would be too much duplicate code.
Both issues are mostly uv specific, so an update there might be necessary to make it properly consistent

Managed to fix the first failure (https://github.com/astral-sh/rye/pull/1094/commits/decf6f942953c6682bfefd261bc074d35b875a6b) at the expense of a little bit of overhead that comes from the sorting. I am not sure if its worth it to have reproducible tests in all platforms or not.
The second issue is a lot more weird and I find what is determining whether to re-install the project or not in uv. Ill keep investigating

I have no clue how to debug the last failure. I created a Windows 10 VM to run the tests in and was not even able to reproduce the same failures when running the cargo test or when playing around with uv/rye to attempt to reproduce it installing the editable that was not edited

Decided to disable both tests in windows because I have no clue what is going on (cant even reproduce locally). I kept my project ordering change, because it seems like every other pathlike output in rye is sorted too.

Rye test Windows 10 VM results
PS C:\Users\davfsa\rye> cargo insta test --workspace --all-features
    Finished `test` profile [unoptimized + debuginfo] target(s) in 9.00s
     Running unittests src\main.rs (target\debug\deps\rye-d897b6fbf5b1da1b.exe)

running 26 tests
test config::config_tests::test_default_requires_python ... ok
test config::config_tests::test_default_license ... ok
test config::config_tests::test_default_build_system ... ok
test config::config_tests::test_default_toolchain ... ok
test config::config_tests::test_force_rye_managed ... ok
test config::config_tests::test_global_python ... ok
test config::config_tests::test_http_proxy_url ... ok
test config::config_tests::test_https_proxy_url ... ok
test config::config_tests::test_sources_default_inclusion ... ok
test config::config_tests::test_load_config ... ok
test config::config_tests::test_use_uv ... ok
test lock::test_make_relativec_url ... ok
test platform::test::test_read_python_version ... ok
test sources::py::test_get_download_url ... ok
test utils::test_command_output::test_command_output_defaults ... ok
test utils::test_command_output::test_command_output_from_quiet_and_verbose ... ok
test config::config_tests::test_venv_mark_sync_ignore ... ok
test utils::test_expand_env_vars::test_expand_env_vars_no_expansion ... ok
test utils::test_expand_env_vars::test_expand_env_vars_with_expansion ... ok
test utils::test_format_requirement::test_format_requirement_file_path ... ok
test utils::test_format_requirement::test_format_requirement_simple ... ok
test utils::test_format_requirement::test_format_requirement_complex ... ok
test utils::test_quiet_exit_display ... ok
test config::config_tests::test_default_author ... ok
test utils::test_is_inside_git_work_tree::test_is_inside_git_work_tree_true ... ok
test utils::test_is_inside_git_work_tree::test_is_inside_git_work_tree_false ... ok

test result: ok. 26 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.07s

     Running tests\test-list.rs (target\debug\deps\test_list-8143112581ab1f2f.exe)

running 2 tests
Initializing new virtualenv in C:\Users\davfsa\AppData\Local\Temp\.rye-tests---lDUovd\project\.venv
Python version<EMAIL_ADDRESS>Initializing new virtualenv in C:\Users\davfsa\AppData\Local\Temp\.rye-tests---kYfuZM\project\.venv
Python version<EMAIL_ADDRESS>Added jinja2>=3.1.2 as regular dependency
Added jinja2>=3.1.2 as regular dependency
Reusing already existing virtualenv
Generating production lockfile: \\?\C:\Users\davfsa\AppData\Local\Temp\.rye-tests---lDUovd\project\requirements.lock
Reusing already existing virtualenv
Generating production lockfile: \\?\C:\Users\davfsa\AppData\Local\Temp\.rye-tests---kYfuZM\project\requirements.lock
Generating dev lockfile: \\?\C:\Users\davfsa\AppData\Local\Temp\.rye-tests---lDUovd\project\requirements-dev.lock
Generating dev lockfile: \\?\C:\Users\davfsa\AppData\Local\Temp\.rye-tests---kYfuZM\project\requirements-dev.lock
Installing dependencies
Building file:///C:/Users/davfsa/AppData/Local/Temp/.rye-tests---lDUovd/project
░░░░░░░░░░░░░░░░░░░░ [0/1] Fetching packages...                                                                         Installing dependencies
   Built file:///C:/Users/davfsa/AppData/Local/Temp/.rye-tests---lDUovd/project                                         Built 1 editable in 918ms
Resolved 2 packages in 2ms
Downloaded 2 packages in 32ms
Installed 3 packages in 54ms
 + jinja2==3.1.2
 + markupsafe==2.1.3
 + my-project==0.1.0 (from file:///C:/Users/davfsa/AppData/Local/Temp/.rye-tests---lDUovd/project)
   Built file:///C:/Users/davfsa/AppData/Local/Temp/.rye-tests---kYfuZM/project                                         Built 1 editable in 935ms
Resolved 2 packages in 2ms
Downloaded 2 packages in 25ms
Installed 3 packages in 13ms
 + jinja2==3.1.2
 + markupsafe==2.1.3
 + my-project==0.1.0 (from file:///C:/Users/davfsa/AppData/Local/Temp/.rye-tests---kYfuZM/project)
Done!
test test_basic_list ... ok
test test_list_not_rye_managed ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.45s

     Running tests\test_add.rs (target\debug\deps\test_add-df3afaa621f8a707.exe)

running 5 tests
test test_add_flask ... ok
test test_add_flask_dotenv ... ok
test test_add_flask_wrong_venv_exported ... ok
test test_add_explicit_version_or_url ... ok
test test_add_from_find_links ... ok

test result: ok. 5 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 19.46s

     Running tests\test_cli.rs (target\debug\deps\test_cli-33bf92fbc788a2da.exe)

running 1 test
test test_dotenv ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 2.69s

     Running tests\test_config.rs (target\debug\deps\test_config-fe1176a18e93d2be.exe)

running 6 tests
test test_config_incompatible_format_and_show_path ... ok
test test_config_save_missing_folder ... ok
test test_config_empty ... ok
test test_config_get_set_multiple ... ok
test test_config_show_path_and_any_action ... ok
test test_config_show_path ... ok

test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.15s

     Running tests\test_init.rs (target\debug\deps\test_init-3194eec11e47d65d.exe)

running 4 tests
test test_init_lib_and_script_incompatible ... ok
test test_init_lib ... ok
test test_init_default ... ok
test test_init_script ... ok

test result: ok. 4 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 5.63s

     Running tests\test_publish.rs (target\debug\deps\test_publish-a6621253289184e7.exe)

running 1 test
building my-project
* Creating isolated environment: venv+uv...
* Using external uv from C:\Users\davfsa\rye\target\debug\rye-test-dir\home\uv\0.1.42\uv.EXE
* Installing packages in isolated environment:
  - hatchling
* Getting build dependencies for sdist...
* Building sdist...
* Building wheel from sdist
* Creating isolated environment: venv+uv...
* Using external uv from C:\Users\davfsa\rye\target\debug\rye-test-dir\home\uv\0.1.42\uv.EXE
* Installing packages in isolated environment:
  - hatchling
* Getting build dependencies for wheel...
* Building wheel...
Successfully built my_project-0.1.0.tar.gz and my_project-0.1.0-py3-none-any.whl
test test_publish_outside_project ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 3.57s

     Running tests\test_ruff.rs (target\debug\deps\test_ruff-b66af89dd162de94.exe)

running 1 test
test test_lint_and_format ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.73s

     Running tests\test_self.rs (target\debug\deps\test_self-91aa4c57a6d8c47b.exe)

running 2 tests
test test_self_uninstall ... ignored
test test_version ... ok

test result: ok. 1 passed; 0 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.08s

     Running tests\test_sync.rs (target\debug\deps\test_sync-89e7b53413c4a286.exe)

running 6 tests
test test_add_and_sync_no_auto_sync ... ok
test test_add_autosync ... ok
test test_empty_sync ... ok
test test_autosync_remember ... ok
test test_workspace_sync ... ok
test test_workspace_sync_with_per_member_lock ... ok

test result: ok. 6 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 40.43s

     Running tests\test_test.rs (target\debug\deps\test_test-50d4783574730dc9.exe)

running 1 test
test test_basic_tool_behavior ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 4.91s

     Running tests\test_toolchain.rs (target\debug\deps\test_toolchain-c0651c68b340059a.exe)

running 1 test
Downloading<EMAIL_ADDRESS>Checking checksum
Unpacking
Downloaded<EMAIL_ADDRESS>test test_fetch ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 39.08s

     Running tests\test_tools.rs (target\debug\deps\test_tools-c87e10f39cfec1f0.exe)

running 1 test
test test_basic_tool_behavior ... ok

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 3.09s

     Running tests\test_version.rs (target\debug\deps\test_version-db1a0ce8e43598a2.exe)

running 2 tests
test test_version_show ... ok
test test_version_bump ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.32s

info: no snapshots to review

I like it. It looks exactly like what I need! When is this PR going to be merged?


PR: Simplify custom layout definition

Description of Changes

[x] Code was organized
[x] Additional comments added
[x] Added tests

Not sure how this changes could be tested at the moment

The code for setting the default layouts has been simplified to make use of Qt 5.6 resizeDocks
Issues on linux ubuntu have been solved. Also a message handler for Qt was added to avoid printing messages that might be unnecessary warnings. On dev mode we will still print all warnings but on the internal console.
Issue(s) Resolved

Fixes #8613
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: @goanpeca

I'm not sure if there's something specific you want me to test, but on Windows 8.1 x64 with Qt/PyQt 5.9 and Python 3.7, both with and without safe mode (clean prefs) I checked basic Spyder usage, changing to several different layouts, moving around panes, editing the layout preferences and resetting to the default layout, and didn't experience any visible issues or error messages. I did get the QMainWidget::resizeDocks: all sizes need to be larger than 0 message as you did in the console without debug mode on quite a bit, but there was no apparent ill effect.

On Fedora 28 LXQt in a VM, with Qt/PyQt 5.9 and Python 3.6, on starting up Spyder in clean and non-clean settings mode, the window as maximized was seemingly twice the height of the screen, with only the first set of panes visible. Switching to the Spyder default and Matlab layouts produced the same effect, with the latter also displaying a strange artifact where the window behind Spyder showed through for part of the screen, which went away when I minimized and re-maximized it. Resetting the layout to default didn't change this either; in fact, the confirmation dialog showed up near the bottom of the screen. Even exploring all the options in my window manager, I could not get the window's contents to resize properly, and if I ran the latest master in the same environment with or without clean prefs as well, everything looked normal. I also got the same Console message as on Windows.

Again, let me know what I can do to help isolate this further.

Hello @goanpeca! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/app/mainwindow.py:

Line 1641:13: E122 continuation line missing indentation or outdented
Line 1642:13: E122 continuation line missing indentation or outdented
Line 1644:13: E122 continuation line missing indentation or outdented
Line 1645:13: E122 continuation line missing indentation or outdented
Line 1647:13: E122 continuation line missing indentation or outdented
Line 1648:13: E122 continuation line missing indentation or outdented
Line 1651:9: E122 continuation line missing indentation or outdented
Line 1654:9: E122 continuation line missing indentation or outdented
Line 1657:9: E122 continuation line missing indentation or outdented
Line 1658:9: E122 continuation line missing indentation or outdented
Line 1667:21: E128 continuation line under-indented for visual indent
Line 1668:21: E128 continuation line under-indented for visual indent

@CAM-Gerlach I saw the issue you mentioned on Ubuntu and I think I have fixed it. Could you check again when you have some time?
Thanks :-)

CI is ok, it is just pointing to an old Build 🤷♂

I restarted the build.

Could we add tests for custom layouts? Some people complained that those are not working in Spyder 3.

You mea custom in general or the defaults ones (matlab, rstudio, horizontal/verical spit?)

Could we add tests for custom layouts? Some people complained that those are not working in Spyder 3.

I am no sure what we could test. The only thing I can think of is having the method return the location of widgets and compare if after changing the layout (and firing a sig_layout_set or something) compare the dockwidget positions.

@CAM-Gerlach what do you mean by the window cannot be moved and various graphical glitches result in the "unocuppied" area, ? and
. The apparent size of the window contents appears to be the same regardless of what the previous size was.

the window cannot be moved and various graphical glitches result in the "unocuppied" area,

On Fedora 28 LXQt, setting the window layout to a different layout maximizes the window frame and it behaves accordingly (cannot be moved, etc), but the window contents are set to a much smaller fixed size and a (sometimes artifact-filled) version of whatever is behind it is shown throughout the rest of the window. The above screenshot demonstrates how this looks, without artifacts for clarity. I haven't observed this problem previously without this PR.

The apparent size of the window contents appears to be the same regardless
of what the previous size was.

The size of the window contents (the visible portion of the Spyder UI inside the outer window frame) is set to the same fixed size (much smaller than the full maximized size) when changing the layout, regardless of whether the window was previously maximized or not, or what the dimensions of the unmaximized window were. Upon unmaximizing the resulting window, the window frame is set to this size, same as the contents.

Ok, will look more into it. I think it is safe to assume that changing the layout requires going to maximized mode, right?

I think it is safe to assume that changing the layout requires going to maximized mode, right?

Not sure if that was directly at me as opposed to @ccordoba12 ; (I don't see any real UX reason why it should; the panel layout should presumably be defined relative to the window size, not the screen size either way, but either of you have way more insight on the technical reasons for this ). Just to be clear, the key issue for me is that regardless the window contents should match the size of the window frame, whatever dimensions it needs to be.

Yes i still need to address the issues

I don't see any real UX reason why it should; the panel layout should presumably be defined relative to the window size, not the screen size either way, but either of you have way more insight on the technical reasons for this

I really don't see a problem with maximizing the screen after a layout switch, if that fixes the bug @CAM-Gerlach is experiencing. It's a minor annoyance, but users would have to accept it if that means a reliable switch.

I am no sure what we could test.

You could save a custom layout in spyder.ini (with CONF.set), then load it through the graphical interface (i.e. by calling the appropiate method in app/mainwindow.py) and finally verifying that some of the panes of the loaded layout are in the right place according to the configuration you saved in the first place.

I really don't see a problem with maximizing the screen after a layout switch, if that fixes the bug @CAM-Gerlach is experiencing.

I don't either; the window already is being maximized; the actual drawn content just isn't following suit. To be clear, what I was responding to whether there was a reason to maximize the window from a UX perspective, not whether there was a reason not to.
To be more specific, with the overhead with the VM, I can't record at a high enough frame rate to reliably capture it but what I believe I see when I trigger a layout change on Linux is first the window contents and frame are both maximized (correctly), then the window contents jumps back to the smaller size but not the window frame. On Windows, by contrast, the window and contents first resizes to a smaller size, then both correctly maximize. This happens over the course of a few drawn frames.

Understood. The behavior I want to achieve is that I don't like the jumping back and fort, so I am trying to disable that programmatically, and that is why we need to maximize (to have a reliable widget size that can be fixed during the layout definition.
I have reproduced the error and I am looking at options now. Thanks for the feedback @CAM-Gerlach

@CAM-Gerlach could you please test tis again when you have some time?
Thanks :-)

@ccordoba12 added a simple test.

@goanpeca Everything is as before on Windows, while on Linux, changing layouts now works without graphical glitches, although it very annoyingly unmaximizes itself and sets itself to an arbitrary fixed size and location, ignoring any previous non-maximized window size. If we're going to do that, we may as well just have it maximize if we can't just preserve the previous window size, rather than just putting it at an arbitrary position and size that is almost certain to be less desirable than just maximizing it.

@CAM-Gerlach thanks for testing this.

although it very annoyingly unmaximizes itself and sets itself to an arbitrary fixed size and location, ignoring any previous non-maximized window size.

That is strange and not the behavior I see (or expect, based on what the code "does")

If we're going to do that, we may as well just have it maximize if we can't just preserve the previous window size, rather than just putting it at an arbitrary position and size that is almost certain to be less desirable than just maximizing it.

This is exactly what the code is supposed to do. Maximize, freeze the size, change layouts, unfreeze the size.
Just to try something.
If you start from a fresh spyder (reset), then close it. Then start it again, and try the layouts, do you see the same thing?

@ccordoba12 made the changes.

I'll test this on my end before approving. @CAM-Gerlach, if I don't see any issues I'll merge because the problem you're experiencing is probably related to the window manager used by LXQt (a very minor desktop environment compared to Gnome and KDE).

@goanpeca, thing are working well for me, expect for one thing: if you activate Horizontal split and then activate Spyder default layout, the only plugin shown is the Editor.
To fix that, you have to activate any another layout (e.g. Matlab layout) and then Spyder default layout to get the correct layout.

if you activate Horizontal split and then activate Spyder default layout, the only plugin shown is the Editor.

Hmm that is odd. Will take a look. Thanks for testing!

I can also confirm I see the same effect as @ccordoba12 described, on both Fedora and Windows and in and not in --safe-mode.

@ccordoba12 I think this last commit fixes the issue. Not sure what caused it, but it seems to work as expected now.

🎉

@CAM-Gerlach, please give it a last try so we can merge it.

@ccordoba12 In work now.

Thanks for the thorough testing @CAM-Gerlach :-)


Dynamic kubeconfig support

When running the flux_boostrap_git resource, it appears that the kubeconfig referenced in the config_path parameter is loaded at terraform initialization time (ie. before any resources are applied). For example if you try to bootstrap with:
provider "flux" {
  config_path = "./kubeconfig"
}

resource "flux_bootstrap_git" "this" {
  url = var.flux_repository_url
  path = "kubernetes/clusters/homelab/"
  branch = "flux-test"
  http = {
    username = var.flux_repository_username
    password = var.flux_repository_password
  }
}

and there is no file .kubeconfig  or that file exists, but does not contain valid credentials for the target cluster, you receive an error for "Unconfigured clients".
This causes this module to be unusable in scenarios where the cluster does not exist yet. This defeats the purpose of the module in many cases, since you would want to create the cluster and bootstrap it with the same terraform code.
Ideally kubernetes client creation should be late-binding and only be created when the flux_bootstrap_git resource is actually applied.

I neglected to mention that this is not impacted by the terraform dependsOn property, which is the core of the problem.

I added dependsOn to the flux_bootstrap_git resource for a local_file resource containing the new clusters kubeconfig.
The flux_bootstrap_git resource correctly executed after all the dependencies, but it could not find or did not use the local_file resource that it depended on.

This is what lead me to the conclusion that the kubeconfig is loaded during provider initialization, rather than when the bootstrapping is run. You can confirm this by specifying a pre-existing kubeconfig for an invalid cluster. The module will complain that it cannot connect before any other resources are applied.

You are probably right about this. Automated tests for this are on my todo list so there is something that probably broke during development. I will have a look at if can get a quick test for this going. The issue right now is that the provider init function is called multiple times and it is hard to determine which state we are in.
What should occur is that the client should be initialized as late as possible.

@scottiepippen840 so because I was so unsure about if I broke this because there is no test I setup a test which creates a Kind cluster and boostraps the cluster in the same state.
terraform {
  required_version = ">= 1.1.5"
  required_providers {
    flux = {
      source  = "registry.terraform.io/fluxcd/flux"
      version = "0.0.0-dev"
    }
    kind = {
      source  = "kyma-incubator/kind"
      version = "0.0.11"
    }
  }
}

provider "kind" {}

resource "kind_cluster" "this" {
  name           = "test-cluster"
  wait_for_ready = true
}

provider "flux" {
  host                   = kind_cluster.this.endpoint
  client_certificate     = kind_cluster.this.client_certificate
  client_key             = kind_cluster.this.client_key
  cluster_ca_certificate = kind_cluster.this.cluster_ca_certificate
}

resource "flux_bootstrap_git" "this" {
  url = "https://github.com/${var.username}/fleet-infra"
  http = {
    username = var.username
    password = var.password
  }
}

So my best guess is that the kubeconfig that you are referencing may be different or contains unexpected data. Currently the error message is not that great because it does not expose the underlying error which caused this. Something that I will work on when we can remove the old datasource.
Could you share your Terraform and the error message that you are receiving?

Oh cool! I don't see it documented anywhere that you can use the host/client config pattern for the flux provider? That will definitely help in cases where that's available.
Here's what I'm using currently, but I admit the local_file nonsense is solely to try and figure out how to pass the kubeconfig to flux:
resource "talos_cluster_kubeconfig" "kubeconfig" {
  talos_config = talos_client_configuration.talosconfig.talos_config
  endpoint     = [for k, v in var.node_data.masters: v.ip][0]
  node         = [for k, v in var.node_data.masters: v.ip][0]
  depends_on       = [proxmox_vm_qemu.talos-masters, proxmox_vm_qemu.talos-workers]
}

resource "local_file" "talos_kubeconfig" {
    content  = talos_cluster_kubeconfig.kubeconfig.kube_config
    filename = "./kubeconfig"
    depends_on       = [talos_cluster_kubeconfig.kubeconfig]
}

Then my flux configurationprovider "flux" {
config_path = "./kubeconfig"
}
resource "time_sleep" "wait_for_cluster_init" {
create_duration = "300s"
depends_on = [local_file.talos_kubeconfig, talos_machine_configuration_apply.worker_config_apply, talos_machine_configuration_apply.cp_config_apply, talos_machine_bootstrap.bootstrap]
}
resource "flux_bootstrap_git" "this" {
url = var.flux_repository_url
path = "kubernetes/clusters/homelab/"
branch = "flux-test"
http = {
username = var.flux_repository_username
password = var.flux_repository_password
}
depends_on = [time_sleep.wait_for_cluster_init]
}
I can use the kubeconfig to access the cluster fine and if I re-run terraform the flux bootstrap git applies.. so it's something about the initialization of the local_file.
```

So the provider takes the same input as the Kubernetes and Helm Terraform provider. This is by design because I thought it was good to not reinvent the wheel again. You can checkout the provider docs here for more info.
https://registry.terraform.io/providers/fluxcd/flux/latest/docs
It might help to debug this issue by understanding a bit more how Terraform works. When you run plan Terraform parses the HCL and resolves variable and resource references in each block. With this it creates a DAG representing dependencies between all resources. It also determines if values are known at plan time or known sometime during apply. This is the reason why circular references are not possible in Terraform.
The issue you have is that the provider does not have a reference to the resource which fetches the kubeconfig. So Terraform determines that the provider has no dependencies and will immediately initialize it, which fails because the file is not present. Now the challenge is that as far as I know you can use depends_on in a provider block. So you have two options in this case.
The first solution is to create a reference to the local_file resource in the provider, which should make sure that the file is created before the Flux provider is initiated. That could look something like this.
resource "talos_cluster_kubeconfig" "kubeconfig" {
  talos_config = talos_client_configuration.talosconfig.talos_config
  endpoint     = [for k, v in var.node_data.masters: v.ip][0]
  node         = [for k, v in var.node_data.masters: v.ip][0]
  depends_on       = [proxmox_vm_qemu.talos-masters, proxmox_vm_qemu.talos-workers]
}

resource "local_file" "talos_kubeconfig" {
    content  = talos_cluster_kubeconfig.kubeconfig.kube_config
    filename = "./kubeconfig"
}

provider "flux" {
  config_path = local_file.talos_kubeconfig.filename
}

resource "flux_bootstrap_git" "this" {
  url = var.flux_repository_url
  path = "kubernetes/clusters/homelab/"
  branch = "flux-test"
  http = {
    username = var.flux_repository_username
    password = var.flux_repository_password
  }
}

Now I am not a fan of localfile, escpecially becaasue there is no support for temporary directories. My suggestion for you is that you parse the kubeconfig output from talos, and feed it into the provider. Check this response in this issue for more details of how that should be implemented. Your solution may have to be a bit different depending on the authentication method used in the kubeconfig returned by talos.
https://github.com/hashicorp/terraform-provider-kubernetes/issues/917#issuecomment-737885191

I consider this issue closed as it is a matter of Terraform configuration dependencies, rather than an issue with the provider init.


YARN-11381. Fix hadoop-yarn-common module Java Doc Errors.

JIRA: YARN-11381. Fix hadoop-yarn-common module Java Doc Errors.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 50s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 42s

trunk passed

+1 :green_heart:
compile
1m  7s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
0m 59s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 55s

trunk passed

+1 :green_heart:
mvnsite
1m  5s

trunk passed

+1 :green_heart:
javadoc
1m 13s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m 12s

trunk passed

+1 :green_heart:
shadedclient
25m 24s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 51s

the patch passed

+1 :green_heart:
compile
0m 57s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 58s

the patch passed

+1 :green_heart:
compile
0m 48s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 48s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 32s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common: The patch generated 2 new + 144 unchanged - 21 fixed = 146 total (was 165)

+1 :green_heart:
mvnsite
0m 51s

the patch passed

-1 :x:
javadoc
0m 50s
/results-javadoc-javadoc-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkUbuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04.txt
hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkUbuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 generated 30 new + 69 unchanged - 30 fixed = 99 total (was 99)

+1 :green_heart:
javadoc
0m 47s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 167 unchanged - 101 fixed = 167 total (was 268)

+1 :green_heart:
spotbugs
1m 59s

the patch passed

+1 :green_heart:
shadedclient
24m 24s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
5m 47s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
asflicense
0m 49s

The patch does not generate ASF License warnings.

115m  1s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5153

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 22023f315657 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 0f6e45b56dcfcc2dd88c562cbb09702fa1760524

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/1/testReport/

Max. process+thread count
562 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/1/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 47s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
41m 59s

trunk passed

+1 :green_heart:
compile
1m  4s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
1m  1s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
checkstyle
0m 56s

trunk passed

+1 :green_heart:
mvnsite
1m  5s

trunk passed

+1 :green_heart:
javadoc
1m 15s

trunk passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 58s

trunk passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
spotbugs
2m  9s

trunk passed

+1 :green_heart:
shadedclient
23m  6s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 49s

the patch passed

+1 :green_heart:
compile
0m 52s

the patch passed with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
0m 52s

the patch passed

+1 :green_heart:
compile
0m 43s

the patch passed with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

+1 :green_heart:
javac
0m 43s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
0m 33s
/results-checkstyle-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common.txt
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common: The patch generated 2 new + 576 unchanged - 23 fixed = 578 total (was 599)

+1 :green_heart:
mvnsite
0m 46s

the patch passed

+1 :green_heart:
javadoc
0m 41s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkUbuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 with JDK Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 generated 0 new + 0 unchanged - 99 fixed = 0 total (was 99)

+1 :green_heart:
javadoc
0m 39s

hadoop-yarn-project_hadoop-yarn_hadoop-yarn-common-jdkPrivateBuild-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 with JDK Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07 generated 0 new + 0 unchanged - 268 fixed = 0 total (was 268)

+1 :green_heart:
spotbugs
1m 51s

the patch passed

+1 :green_heart:
shadedclient
24m 16s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
5m 30s

hadoop-yarn-common in the patch passed.

+1 :green_heart:
asflicense
0m 48s

The patch does not generate ASF License warnings.

111m 55s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/5153

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 4f7abc6f676f 4.15.0-191-generic #202-Ubuntu SMP Thu Aug 4 01:49:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / c4b08cb2428e3d8c61a941caa4357892639600ae

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.16+8-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_342-8u342-b07-0ubuntu1~20.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/2/testReport/

Max. process+thread count
679 (vs. ulimit of 5500)

modules
C: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common U: hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-5153/2/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

@ayushtkn Can you help review this PR? Thank you very much! The issue of checkstyle is not caused by this pr, this issue also existed before.

@ayushtkn Can you help to merge this pr into the trunk branch? Thank you very much!

Merged, I wanted you to give it a try. :-)

@ayushtkn Thank you very much for your help in reviewing and merging the code!


Seurat and SpatialExperiment integration

counts, metadata, and coordinates are integrated. Images will take more thought and will come after image package

Can you also add update the authors in the description to match the readme?

Changes have all been added. Working on creating issues


Oncoplot omits samples

Hello!:)
I am making oncoplots for a number of cancer patients, and I encounter the following issue all the time: some samples get automatically removed by the program, even when I set removeNonMutated=F, fill=T. Some of my annovar-annotated files are empty, because no mutations have been detected. Would that be reason or there is something else I am not taking into account? I am aiming for all the samples, even the ones without any mutations to be included in the plot. I would greatly appreciate any advice on this.
Thank you!
Arman

Hello Arman,
The easiest fix would be adding a dummy synonymous variant to the empty annovar files. That should add them to the plot and wont affect much of the analysis.

Hi there,
Thanks for such a great and easy to use tool, with very visually appealing results.
I am also experiencing the issue of non-mutated samples being omitted from oncoplots, despite using removeNonMutated = FALSE, fill = TRUE.  I have noted the use of dummy synonymous mutations as a workaround, however, as my pipeline is clinical grade, this is not professionally acceptable.  I note this issue has been open for nearly 18 months now- do you have any solutions planned for future releases of maftools?
Kind regards,
nuttynutmore


Lazy initialization of device vector.

Fix #5162.

Disable copy constructor of HostDeviceVector.  Prevents implicit copying.

@RAMitchell
this->data_ = HostDeviceVector{1, 2, 3, 4, 5};

Not important, but convenient for writing tests.


ArduinoJSON

Update to use latest ArduinoJSON version. (or at least update instructions to specify)
Anything after 5.13.2 does not support jsonBuffer and throws errors.

From the ArduinoJSON site: “The Arduino Library Manager installs the ArduinoJson version 6 by default.
However, using version 5 is highly recommended because version 6 is still in beta stage. Open the Arduino Library Manager and make sure that ArduinoJson version 5 is installed.”


Updating default ini parameters

Added a ADI ToF service to backup NVM flash and CCB

Looks good but you need to sign-off your commits.
Also, commit https://github.com/analogdevicesinc/ToF/pull/357/commits/5e5cab0ecbb894cb8235ec6ac37c3b4928ca6a82 seems to contains changes that are not related to this PR.


Start using Exceptions named nicely and inheriting from one another

this removes some dead code from vm.

it also makes exceptions classified as runtime only or compile time only (or both)


run linux Quickstart  threw Error

When I execute the following command by https://learn.microsoft.com/en-us/azure/ai-services/speech-service/get-started-text-to-speech?tabs=windows%2Cterminal&pivots=programming-language-java
[root@VM-4-5-centos demo]# javac SpeechSynthesis.java -cp ".;target\dependency*"
SpeechSynthesis.java:1: error: package com.microsoft.cognitiveservices.speech does not exist
import com.microsoft.cognitiveservices.speech.;
^
SpeechSynthesis.java:2: error: package com.microsoft.cognitiveservices.speech.audio does not exist
import com.microsoft.cognitiveservices.speech.audio.;
^
SpeechSynthesis.java:13: error: cannot find symbol
SpeechConfig speechConfig = SpeechConfig.fromSubscription(speechKey, speechRegion);
^
symbol:   class SpeechConfig
location: class SpeechSynthesis
SpeechSynthesis.java:13: error: cannot find symbol
SpeechConfig speechConfig = SpeechConfig.fromSubscription(speechKey, speechRegion);
^
symbol:   variable SpeechConfig
location: class SpeechSynthesis
SpeechSynthesis.java:17: error: cannot find symbol
SpeechSynthesizer speechSynthesizer = new SpeechSynthesizer(speechConfig);
^
symbol:   class SpeechSynthesizer
location: class SpeechSynthesis
SpeechSynthesis.java:17: error: cannot find symbol
SpeechSynthesizer speechSynthesizer = new SpeechSynthesizer(speechConfig);
^
symbol:   class SpeechSynthesizer
location: class SpeechSynthesis
SpeechSynthesis.java:27: error: cannot find symbol
SpeechSynthesisResult speechSynthesisResult = speechSynthesizer.SpeakTextAsync(text).get();
^
symbol:   class SpeechSynthesisResult
location: class SpeechSynthesis
SpeechSynthesis.java:29: error: cannot find symbol
if (speechSynthesisResult.getReason() == ResultReason.SynthesizingAudioCompleted) {
^
symbol:   variable ResultReason
location: class SpeechSynthesis
SpeechSynthesis.java:32: error: cannot find symbol
else if (speechSynthesisResult.getReason() == ResultReason.Canceled) {
^
symbol:   variable ResultReason
location: class SpeechSynthesis
SpeechSynthesis.java:33: error: cannot find symbol
SpeechSynthesisCancellationDetails cancellation = SpeechSynthesisCancellationDetails.fromResult(speechSynthesisResult);
^
symbol:   class SpeechSynthesisCancellationDetails
location: class SpeechSynthesis
SpeechSynthesis.java:33: error: cannot find symbol
SpeechSynthesisCancellationDetails cancellation = SpeechSynthesisCancellationDetails.fromResult(speechSynthesisResult);
^
symbol:   variable SpeechSynthesisCancellationDetails
location: class SpeechSynthesis
SpeechSynthesis.java:36: error: cannot find symbol
if (cancellation.getReason() == CancellationReason.Error) {
^
symbol:   variable CancellationReason
location: class SpeechSynthesis
12 errors
I am a little white .
Can you tell me in detail how to do it?
by the way
This is my directory structure
[root@VM-4-5-centos demo]# pwd
/home/demo
[root@VM-4-5-centos demo]# ll
total 12
-rwxr-xr-x 1 root root 1024 Nov  7 22:02 pom.xml
-rwxr-xr-x 1 root root 2107 Nov  8 01:26 SpeechSynthesis.java
drwxr-xr-x 3 root root 4096 Nov  8 00:45 target
guru：with my best blessing

@mrwangjing Thanks for the report, could you please follow the quickstart in this samples repo: https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/java/jre/text-to-speech and let me know if that helps

@mrwangjing Thanks for the report, could you please follow the quickstart in this samples repo: https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/java/jre/text-to-speech and let me know if that helps

i will try tonight and reply to you   waiting for me

@jhakulin   i will try tonight and reply to you.waiting for me
guru：with my best blessing

@jhakulin
good night!
i was run https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/quickstart/java/jre/text-to-speech
on win10 is fine ，but when I run on Linux （centos 7.9）,it's wrong.
by the way
i has following https://learn.microsoft.com/en-us/azure/ai-services/speech-service/how-to-configure-rhel-centos-7
still wrong....

[root@VM-4-5-centos text-to-speech]# pwd
/www/text-to-speech
[root@VM-4-5-centos text-to-speech]# ll
total 16
-rwxr-xr-x 1 root root 2228 Nov  8 20:11 pom.xml
-rwxr-xr-x 1 root root 3203 Nov  8 20:11 README.md
drwxr-xr-x 3 root root 4096 Nov  8 20:11 src
drwxr-xr-x 5 root root 4096 Nov  8 20:11 target
[root@VM-4-5-centos text-to-speech]# javac src/speechsdk/quickstart/Main.java -d target -encoding utf-8
src/speechsdk/quickstart/Main.java:10: error: package com.microsoft.cognitiveservices.speech does not exist
import com.microsoft.cognitiveservices.speech.*;
^
src/speechsdk/quickstart/Main.java:30: error: cannot find symbol
try (SpeechConfig config = SpeechConfig.fromSubscription(speechSubscriptionKey, serviceRegion)) {
^
symbol:   class SpeechConfig
location: class Main........
Is there anything i need to provide？

I can't even try this

@mrwangjing Could you please use following steps to build and run text-to-speech quickstart  and let me know the outcome.
Clone Speech SDK samples GitHub repository
git clone https://github.com/Azure-Samples/cognitive-services-speech-sdk.git
Go to text-to-speech directory
cd cognitive-services-speech-sdk/quickstart/java/jre/text-to-speech
Build the quickstart
mvn clean package
Run the quickstart
java -jar target/text-to-speech-quickstart-0.0.1-SNAPSHOT-jar-with-dependencies.jar
When running the above command, you should see the following output and then input some text you want to synthesize and press enter.
Type some text that you want to speak...

Closing as answered


Using anchoring together with Positioned.fill

Is it possible to create a PortalEntry that has the following two behaviors at the same time:

full screen GestureDetector to dismiss the current PortalEntry whenever you tap outside of it (like your date picker example)
anchoring the actual overlay Widget to the child (like in the contextual menu example)

I tried various things, even using two PortalEntries at the same time (one full screen for the GestureDetector and another with just the Widget that gets anchored to the child), but couldn't get it to work and am wondering whether this is actually possible with the current design.
Previously, I implemented my Overlays by hand with a Stack, but then I failed to position the overlay correctly, because I don't have the size of the actual overlay when it comes to positioning it relative to the target with CompositedTransformFollower. I hoped your library would be a solution to this, but at the moment I am failing to achieve the points above.

Not for now, but you can use two Portal to achieve the same result

Do you mean two Portals or two PortalEntries? I tried with two entries and then had to use your rework branch (because of #4), but now it looks like everything works fine with the following code.
Is this what you had in mind?
class MyApp extends StatefulWidget {
  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  bool visible = false;

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Portal(
        child: Center(
          child: PortalEntry(
            visible: visible,
            portal: Container(
              child: GestureDetector(
                onTap: () {
                  print('dismissed');
                  setState(() {
                    visible = false;
                  });
                },
              ),
            ),
            child: PortalEntry(
              visible: visible,
              portalAnchor: Alignment.bottomCenter,
              childAnchor: Alignment.topCenter,
              portal: RaisedButton(
                child: Text('Close'),
                onPressed: () {
                  print('closed');
                  setState(() {
                    visible = false;
                  });
                },
              ),
              child: RaisedButton(
                child: Text('Open Overlay'),
                onPressed: () {
                  setState(() {
                    print('toggling overlay');
                    visible = !visible;
                  });
                },
              ),
            ),
          ),
        ),
      ),
    );
  }
}

This is what I was thinking of, yes

@rrousselGit is there any way to get global coordinates of anchor point inside portal field of PortalEntry?
i'm trying to position my popup hint based on the position of a child, so it will be fully drawn on the screen for both appbar and bottomnavbar, while the Alignment is like really cool, is there a way to specify it based on child location?


[react-native-cli] Update docs

cc @mkonicek, @ide, @foghina

Should we keep documented how the old cli worked?

I recommend you adding a different guide that explains CLI commands if you want to document them. Felix and me tried to make sure end used doesn't have to run anything, just normal Xcode/Gradle build.
However, this won't work for projects generated before v0.14. I should document this here.

Sounds good. I'l do that instead :)


Missing resource with path: font/roboto_bold.ttf

Hey, I have the same issue but I believe you won't be able to get a fix in this repo.
You can refer to this one instead: https://github.com/luca992/multiplatform-swiftpackage/issues


verifications running before :before notifications executed cause unnecessary failures

Description
verifiers are being run run before :before notification actions are executed on the target resource, so a resource that would pass verification if the before notification was run before the notifying resource was verified will unnecessarily fail.
Chef Version
12.19.36
Platform Version
CentOS 7.3
Replication Case
in this (contrived) example, systemd has a dependency on the service unit existing before the corresponding socket unit can be created. if the before-notification was executed before the verification, this would work.
systemd_unit 'true.socket' do
  content({
    'Unit' => {
      'Description' => 'Truth Listen Socket'
    },
    'Socket' => {
      'ListenStream' => "<IP_ADDRESS>:9001"
    },
    'Install' => {
      'WantedBy' => 'sockets.target'
    }
  })
  action [:create, :enable, :start]
  notifies :create, 'systemd_unit[true.service]', :before
end

systemd_unit 'true.service' do
  content({
    'Unit' => {
      'Description' => 'Truth Service',
      'After' => 'network.target'
    },
    'Service' => {
      'StandardOutput' => 'null',
      'StandardError' => 'syslog',
      'ExecStart' => "/usr/bin/true",
      'Restart' => 'on-failure'
    },
    'Install' => {
      'WantedBy' => 'multi-user.target'
    }
  })
  action :create
end

Client Output
converge failure
Stacktrace
stacktrace

Why are you using a before notification for creating a unit?

before notifications are pretty much exclusively built for the "I need to stop this service during upgrades or config changes and start it again after" use case, so this would only apply is the service resource had a verifier?

@coderanger oh i'm not. like i said, it's a contrived example... it came up in #5909 and seemed like an oversight to me, so figured i'd raise the issue for discussion separately (there may be cases where you want to run a resource before a resource in a community cookbook where you've got less control of ordering).

before notifications are pretty much exclusively built for the "I need to stop this service during upgrades or config changes and start it again after"

ah. makes sense. obvious answer is "order matters", which is fine, but i wasn't sure if before notification was intended to be more like puppet's before ordering, in which case verifier's triggering first seems like a hindrance.

Yeah, that's why I mentioned it, very much not for more arbitrary ordering tricks :) For that you still need to put them in the order you want them to run.

👍


Automatic meta transformations

Implement a meta transformation, applicable both for static meta and Configuration with a set of rules. For Configuration it should create dynamic meta, mirroring all changes.

implementer in 0.1.6-dev-2


Remove gcc package from environment (gssha currently depends on gcc)

As far as I can tell, the gcc package is deprecated (?around the time of Anaconda Distribution 5; I'm not sure how someone's supposed to be aware of that, but that's a different issue...).
In #97, you can see that installing gcc is clobbering libgcc-ng (which then results in various subsequent problems).
gssha (https://anaconda.org/erdc/gssha) has a runtime dependency on gcc; is it possible to remove that? Or change it to e.g. libgcc-ng? Or if a compiler's required, I think it's now packages with the platform in the name, like gcc_linux-64 etc.

Using conda-build 3, it should be possible to replace
requirements:
  build:
    - vc14  # [win and py>=35]
    - gcc # [unix]
    - ...
  run:
    - vc14  # [win and py>=35]
    - gcc # [unix]
    - ...

with
requirements:
  build:
    - {{ compiler('c') }}
    - ...
  run:
    - ...


Implement support for multiframe image decoding via gdcm

this is mostly done to test https://github.com/pevers/gdcm-rs/pull/7 for now and maybe get some visibility on how to improve it right away.
Does not crash but for the 2 test files I added it either produces black images or images with 'bad' colors.

Thank you for working on this, @ingwinlu!
I must warn you though, as I am working on #122, the crate's code will be subjected to several changes with an upcoming pull request. So we may need to rebase this later.

Just a heads-up, #122 has been merged, so this PR will need to be updated accordingly.
I have scheduled for a v0.5.0 release very soon, but this contribution may become part of DICOM-rs in subsequent versions.

with the relese of gdcm-rs 0.4.0 this should hopefully build now

hot damn, some more support for encoded pixel data ready to go!

Closes #226

Any feedback on this?

Short update mostly for myself so I don't forget.
When looking at the above mentioned code https://github.com/Enet4/dicom-rs/blob/c08c3511b651a47dda452e24dac11c47aeb43eff/pixeldata/src/lib.rs#L1577 I could not really understand what slicing is refered to and looked into finding some way to test the behaviour with the test dicom files.
While doing this I also noticed that the branch at https://github.com/Enet4/dicom-rs/blob/c08c3511b651a47dda452e24dac11c47aeb43eff/pixeldata/src/lib.rs#L1574 apparently is not covered by tests at placing a panic! macro there does not influence test results.

When looking at the above mentioned code
https://github.com/Enet4/dicom-rs/blob/c08c3511b651a47dda452e24dac11c47aeb43eff/pixeldata/src/lib.rs#L1577
I could not really understand what slicing is refered to and looked into finding some way to test the behaviour with the test dicom files.

I suspect that the slicing was originally introduced in order to let the user retrieve the first frame from a multi-frame image. Now that we want multi-frame retrieval to work, any slicing can be deferred to eventual calls in DecodedPixelData.

While doing this I also noticed that the branch at
https://github.com/Enet4/dicom-rs/blob/c08c3511b651a47dda452e24dac11c47aeb43eff/pixeldata/src/lib.rs#L1574
apparently is not covered by tests at placing a panic! macro there does not influence test results.

So yes, the current implementation is not very ideal. It was probably a consequence of the changes in #152 or #212. That part is unreachable because we already check to ensure that the transfer syntax is fully supported.
With that said, this reminds me that we are very close to supporting Encapsulated Uncompressed Explicit VR Little Endian (1.2.840.10<IP_ADDRESS>.98), which is a fairly recent transfer syntax.

@Enet4 my problem is that I don't see where there is any slicing occurring? I also see no behaviour that would just return the first frame.

@Enet4 my problem is that I don't see where there is any slicing occurring?

With the current setup, slicing is expected to be done after the decoding, when turning the DecodedPixelData into something else. Maybe at a later stage the decoding can be deferred to a later stage for efficiency.

I also see no behaviour that would just return the first frame.

Currently, it does when feature-gated on gdcm:
https://github.com/Enet4/dicom-rs/blob/c08c3511b651a47dda452e24dac11c47aeb43eff/pixeldata/src/gdcm.rs#L105-L110
The code above fetches only the first frame by slicing on the first W*H*C*bpp/8 bytes. It is an artifact of the first iteration of dicom-pixeldata and should be removed. Please let me know if you need further assistance, or whether you prefer that I take over the pull request.

For some reason when reading  Can you look into line 105 and remove the unwanted slicing like in lib.rs:1577? I only parsed the second reference and never looked into the first. And apparently was way to confused by this to even notice that lib.rs:1577 has no influence with gdcm anyway.
I pushed the change in cc12a78.


imgp: 2.8 → 2.9

Description of changes
https://github.com/jarun/imgp/releases/tag/v2.9
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

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

2 packages built:

imgp
imgp.dist

Result of nixpkgs-review pr 277412 run on x86_64-darwin 1

2 packages built:

imgp
imgp.dist


Required if bug

When I use form validation rules in array way:
['name' => ['required_if:type,1', 'min:4']]
If type is not 1, it still validates the min rule and returns error, however when I use:
['name' => 'required_if:type,1|min:4']
If the type is not 1, it skips every other rule for that value.
Not sure why would different type of writing have different outcome.

Hey there,
I'm unable to reproduce this on a fresh Laravel installation.

Can you please create a minimal reproduction for this and we take a closer look?
laravel new bug-report --github="--public"


Working with Gate Hub?

Should this work with the Gate Hub?  I have dumped the device IDs from my Access setup that is running on my UNVR, but every time I try to refresh or poll the device, I am getting the following log in Hubitat.
"Error retrieving door info: The requested item does not exist."
I've actually tried using every device id that was returned from my API query, and they all return the same error.

I used a different curl command to pull the correct door ID and was able to successfully get it added to my Hubitat hub.  Since I am using this as a garage door opener, if there anyway to display the door status (open/closed) as opposed to the lock status?


Allow HttpClientExtensions.ToForm to have nullable forms

I have a use case where a file is submitted together with other form data. The file itself is optional. Updated the test extension method so it can handle null files.

thank you very much!


ptvsd auto reconnect

Hello!
I try to debbug my python app in docker contener. I connect to it by using ptvsd at VS. But after each restart or modification i need to restart docker app, then open Attach to proccess dialog, then each time write ptvsd connection string (some why it doesn't save at connections list), then find the process, then connect, and after all become debuggin. From this I have a question: Is this possible to make VS auto-wait my docker app to become started and after app "wait attach" it automaticaly connect to debug? Because it annoying after each restart app make this list of actions to make debuggin work. It have to be work as easy as regular debuggin work: we are just clicking Debug run button and debuggin is start. Is that possible to make Remote ptvsd debugging, may be after same configuration, to work by one button click? Thank you!

It's not currently possible, and we don't have any control over the existing Attach dialog (otherwise we would have made it save already :) ), but we could certainly add our own way of doing this.
We should probably make this a debug launcher so that it ties into F5 (i.e. press F5 and it waits to attach to a certain endpoint).

Possible solution to automate attach to process repetitive action by using macro:
Imports System
Imports EnvDTE
Imports EnvDTE80

Public Module PythonTools
    Sub AttachToProcess(Optional ByVal strArguments As String = "")
        Dim strarrArguments As String()
        Dim strTransportQualifier As String, strProcessName As String
        Dim dbg As EnvDTE80.Debugger2

        strarrArguments = strArguments.Split(Nothing, 2)

        If strarrArguments.Length > 0 Then
            strTransportQualifier = strarrArguments(0)

            If strarrArguments.Length = 2 Then
                strProcessName = strarrArguments(1)
            End If
        End If

        If strTransportQualifier = "" Then
            strTransportQualifier = "tcp://localhost"
        End If

        If strProcessName Is Nothing Then
            strProcessName = ""
        End If

        dbg = DTE.Debugger

        Try
            dbg.GetProcesses(dbg.Transports.Item("Python remote debugging"), strTransportQualifier).Item(strProcessName).Attach()
        Catch
        End Try
    End Sub
End Module

One can run this macro from the Command window of IDE:
>Macros.MyMacros.PythonTools.AttachToProcess tcp://secret@<IP_ADDRESS>:1234 PythonApp
or just
>Macros.MyMacros.PythonTools.AttachToProcess
to attach to the first process with default transport qualifier (tcp://localhost:5678).
Surely one can extend PythonTools Module with additional macro code to start local or remote process.
:wink:

There should now be a reattach command that appears in the debug menu after you've attached once.


[5.2] Validate Uploaded Image Dimensions

This PR adds a new validation rule:
// Multiple rules
$rules = ['image' => 'image_dimensions:width=100,min_height=30'];

// Single rule
$rules = ['image' => 'image_dimensions:ratio=3/2'];

Available rules are:

min_width
min_height
max_width
max_height
width
height
ratio

Guess we'll also need a new language line and docs entry for this.

Will take care of that in a couple of hours :)


Update README.md

Codecov Report

Merging #100 into master will decrease coverage by 0.63%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #100      +/-   ##
============================================
- Coverage     57.79%   57.16%   -0.64%
  Complexity      620      620
============================================
  Files            90       83       -7
  Lines          3170     3100      -70
  Branches        183      178       -5
============================================
- Hits           1832     1772      -60
+ Misses         1238     1231       -7
+ Partials        100       97       -3

Impacted Files
Coverage Δ
Complexity Δ

...ntend/src/views/teacher/questions/ShowQuestion.vue

frontend/tests/unit/samples/Question.ts

frontend/src/models/management/Option.ts

frontend/src/models/management/Question.ts

frontend/src/models/management/Topic.ts

...src/views/teacher/questions/ShowQuestionDialog.vue

frontend/src/services/ConvertMarkdownService.ts

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 3983bea...f624ffe. Read the comment docs.

Rui, it is not software engineering only. Técnico and Software Engineering?


(chore) Update halp text on Essential Educational Requirements input

Trello card URL:
https://trello.com/c/aWfVK6n1/492-essential-educational-requirements-text-revision
Changes in this PR:
Update the help text in the Essential Educational Requirements input in the job creation form
Screenshots of UI changes:

 Essential educational requirements text revision


Updated username of NERDTree plugin as it as a new name

Describe the details of your PR ...

Thanks!


docs: remove pwa plugin which is responsible of some bug on the documentation

:tada: This PR is included in version 7.13.4 :tada:
The release is available on:

v7.13.4
GitHub release

Your semantic-release bot :package::rocket:


Sprite Region Editor UI Space Bug

Not sure if this is intended, but when using the Sprite Region Editor you can hold down space to move around. But, upon releasing space, it automatically closes (submits the Ok Button)

maybe remove the focus from the button should do?


Node v21 marked as unsupported but it works without any problems

I'm constantly getting this warning about using node v21 with this plugin, but it works perfectly fine for me. Could you add it to the engines list? Or I can create a PR.
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '^16 || ^17 || ^18 || ^19 || ^20' },
npm WARN EBADENGINE   current: { node: 'v21.6.1', npm: '10.2.4' }
npm WARN EBADENGINE }

Hello!
Basically, I was quite cautious about supporting odd versions of Node.js. However, we started to support in a couple of versions ago, so I think we can support 21 as well.
It has to be added to package.json as supported version and to CI matrix because we have to run tests on the new version of Node.js.
PR is wellcome, or I can do it in a week or so.

Done ✅ https://github.com/effector/eslint-plugin/commit/21f4ea68729b9f781b533e963b1370444aca46d1
Will be released with other changes soon 🔜


Feature request: Show Build Minutes

Show build minutes information on netlify status command.
Example:
https://www.npmjs.com/package/netlify-minutes

Closing as stale. Please re-open if needed


without gpu

❓ Questions and Help
Is it possible to train without gpu? If yes what all changes i need to make?

No it isn't. For instance, there is no implementation of ROIAlign_backward_cpu for the moment. I think that there are no plans to enable cpu training for the moment, do you confirm that @fmassa ?

Correct, no plans to enable CPU training in maskrcnn-benchmark.
Note though that all operations have been implemented on CPU in torchvision in https://github.com/pytorch/vision/pull/826 , so you could potentially use those


Ubuntu/WRF/Isosurface problem

Graphics Card: AMD Radeon RX550/550 Series
Raycaster: Curvilinear
Occurs on: Ubuntu18, Ubuntu20 (not Windows or CentOS7)
To reproduce:

Import WRF data
Create an isosurface.

Here's approximately what it should look like:

Note:
Graphics Card: AMD Radeon RX550/550 Series
Raycaster: Curvilinear
Occurs on: Ubuntu18, Ubuntu20 (not Windows or CentOS7)

@sgpearse will try updating drivers on Ubuntu systems

@stasj PPA third party repository driver screenshot below.  It's much better, but there is red speckling around the domain frame.

@sgpearse can we close this after @stasj backs out the changes for #2800?


Release source dataset metadata

When releasing a managed dataset like the CoL different sectors have been synced at different times. They might be years apart. The source datasets existing in the Clearinghouse could have been updated considerably since and contain different metadata than then one used at the time the source was synced.
The metadata for each source dataset bundled with a release should be the one that represents the exact import attempt that the sync was based on. This becomes a bit of a problem in cases where there are many sectors from the same dataset that have been synced at different times against different import attempts. We should use the latest attempt for all syncs per dataset in these cases.
In order to be able to access the metadata for a specific import attempt we should:

[ ] archive all metadata for all attempts, similar to how we store the import metrics
[ ] keep the import attempt with every sync so we know against which version we have synced
[ ] for each source dataset in releases use the metadata from the exact attempt of a sector sync - or the latest one in case there are multiple attempts existing for all sectors of a single source dataset

Storing all versions of metadata is more complex than anticipated. To understand it better I ahve drawn a diagram that uses rectangular boxes for dataset metadata records:

The one thing I am unsure about is whether a (released) project would maybe want to deviate from the source dataset owners metadata. I would bet that is true, especially if we deal with more projects over time. Is it necessary to have yet another copy of a dataset metadata for each source in a released project? Or maybe point to the official version (using the combined key of datasetKey & import attempt) and allow to specify changes stored the project dataset that modify the original metadata? A bit like decisions but simpler? Then we dont need to store dataset copies in their full glory over and over again.

Alternatively we could

keep a datasets current metadata
store a projects source metadata as a separate file. Each time a sector is synced the metadata would also be checked if it has been updated and an editor be forced to merge the 2 versions if they are different. That manual merging would not work though if many sectors were to be synced at the same time

I can explain approach to dates in metadata in CoL production 2010-19.
We use an analog to Sync attempt/date (i.e. synced all sectors together): date stamp in LSID. It was a technical date, which was useful only for me, Luisa and systems manager in our management process. (It was not possible to "sync" different sectors in different dates. Independence of syncs in CoL+ is a positive feature).
GSD Release Date, a date when GSD export was generated for CoL. It is analog to Import attempt/date. That date was used by our data management team and GSD author. One editorial version of GSD may have different release dates.
GSD version (it included month and year), as defined by the GSD author. The version/date was used by our data management team, GSD author and CoL users.
Different projects may have different approaches and needs.
In CoL+, our data management team need to have consolidated log for sector syncs + {GSD import + GSD release} + GSD version, as well as separate logs for each parameter. Metadata with non-recently-synced GSDs in the assembled checklist should not be changed. For example, metadata for IRMNG should remain unchanged in the project despite of how newer version of IRMNG we have in the clearinghouse, UNTIL we do a sync for a new IRMNG. (In the case of automated updates, sync should be kicked off automatically).

Thanks Yuri. This is not just dates though but any of the metadata like authors, description, citation you name it. Or don't you ever change that?

Metadata should stay unchanged unless GSD version remain unchanged.
There were different procedures for automated and manually updated GSDs.
Manually updated GSD: I am checking metadata for each version of GSD. (GSD authors do not necessarily keep metadata consistent from one release to another. Before assembly, I am checking, that (1) GSD names remain stable (as names which we agreed with first entry of GSD), (2) style of versioning is consistent through editions, (3) style of authors, organizations, English name of the group comply with CoL standards.
Automated GSDs: I was not able to check manually metadata in all automated GSDs. Thus, we frozen such fields as GSD names (for all GSDs), authors & organizations (for WoRMS; because these data do not comply with CoL standards). This approach had negative impact: if list of authors was changed in WoRMS, it may stay unchanged in CoL until our editors or GSD authors report a problem.

I think we should not modify the original sources metadata. If multiple projects make use of the same source different styles are likely and not everyone will be happy. Modifying the authors and title is exactly what I was thinking of above - we need to find a way to apply these changes only in the project scope and not outside. How we do that so it is efficient but always up to date is the main question.

Well, in this case, each project should have an option to create own view for metadata of the source.

The problem is that the metadata is often not well maintained by authors, so I like the idea of projects being able to edit a copy of the metadata.

We figured in our call that a metadata update decision on each source of a project would be address the problem. That decision gets applied during a release before copying the metadata into the archive.


explorer exits due to ECONNREFUSED to port 5432

This is due to explorer tries to connect to db before the db starts successfully.

If I run hyperledger explorer using docker compose, I get below error:
error when connecting to db: { Error: connect ECONNREFUSED <IP_ADDRESS>:5432
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)
errno: 'ECONNREFUSED',
code: 'ECONNREFUSED',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 5432 }
But after I restart explorer docker using 'docker restart explorer.example.com' it works. The reason is that when explorer try to connect to db, the db was not ready.

If this docker-compose changes would be applied then we can also remove 'sleep 16' given before starting explorer.


⚠ Bofrost.at has degraded performance

In f5adaf6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1777 ms

Resolved: Bofrost.at performance has improved in ca9f506 after 48 minutes.


Render airport areas at lower zoom levels

Airport areas appear at zoom 10. I noticed that a lower zooms they can leave sizeable gaps in city grids. I propose treating them more like parks by showing their bounds at lower zoom levels, though not necessarily the runways.
Examples under/over the cusp of z10:

Indeed these come in at zoom 10. That airport in Alaska is probably particularly prominent because of its large size.  I'm pretty sure we could apply a logic similar to openmaptiles/openmaptiles#1479 for universities to keep the largest airports in render at lower zooms.  Anyone know what the largest (in pixels) airport is?

Excluding military bases and Antarctica, we're looking at Saudi Arabia, Iceland, and Denver: https://observablehq.com/d/3c7a0ee3e844a3c7


Remove package-management.md file

Remove package management file, it is no longer used.

@jsquire , @CamSoper for notification.

@CamSoper - Good from Azure SDK perspective.  Feel free to merge when ready.  Thank you.


Docker版无法启动：no such column: uploadstreamers.copyright_source

Code of Conduct

[X] 我清楚知道，可以在 Release 检阅最新的 Biliup 版本
[X] 我清楚知道，反馈非最新 Release 版的错误是无意义的
[X] 我清楚知道，日志中并不包含 Cookie 此类的信息，可以直接上传完整日志
[X] 我已经尝试过最新 Release 版，且问题依旧

运行环境
Ubuntu20.04
biliup 版本
v0.4.70
所录制的主播网址
all
错误描述
在从v0.4.57直升v0.4.70出现错误无法开启容器

配置文件

配置文件

# 在这里填写你的配置文件

报错日志以及其他描述（如果有）

日志

新版本不依赖配置文件，请访问 WebUI 修改配置
Uncaught exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute
    cursor.execute(statement, parameters)
sqlite3.OperationalError: no such column: uploadstreamers.copyright_source
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
  File "/usr/local/bin/biliup", line 8, in <module>
    sys.exit(arg_parser())
             ^^^^^^^^^^^^
  File "/biliup/biliup/__main__.py", line 58, in arg_parser
    config.load_from_db(db)
  File "/biliup/biliup/config.py", line 49, in load_from_db
    k: v for k, v in ls.uploadstreamers.as_dict().items() if v and k not in ['id', 'template_name']})
                     ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 566, in __get__
    return self.impl.get(state, dict_)  # type: ignore[no-any-return]
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 1086, in get
    value = self._fire_loader_callables(state, key, passive)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/attributes.py", line 1121, in _fire_loader_callables
    return self.callable_(state, passive)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/strategies.py", line 967, in _load_for_state
    return self._emit_lazyload(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/strategies.py", line 1068, in _emit_lazyload
    return loading.load_on_pk_identity(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/loading.py", line 694, in load_on_pk_identity
    session.execute(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 2351, in execute
    return self._execute_internal(
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/session.py", line 2236, in _execute_internal
    result: Result[Any] = compile_state_cls.orm_execute_statement(
                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/orm/context.py", line 293, in orm_execute_statement
    result = conn.execute(
             ^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1418, in execute
    return meth(
           ^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/sql/elements.py", line 515, in _execute_on_connection
    return connection._execute_clauseelement(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1640, in _execute_clauseelement
    ret = self._execute_context(
          ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1846, in _execute_context
    return self._exec_single_context(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1986, in _exec_single_context
    self._handle_dbapi_exception(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 2353, in _handle_dbapi_exception
    raise sqlalchemy_exception.with_traceback(exc_info[2]) from e
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/base.py", line 1967, in _exec_single_context
    self.dialect.do_execute(
  File "/usr/local/lib/python3.12/site-packages/sqlalchemy/engine/default.py", line 924, in do_execute
    cursor.execute(statement, parameters)
sqlalchemy.exc.OperationalError: (sqlite3.OperationalError) no such column: uploadstreamers.copyright_source
[SQL: SELECT uploadstreamers.id AS uploadstreamers_id, uploadstreamers.template_name AS uploadstreamers_template_name, uploadstreamers.title AS uploadstreamers_title, uploadstreamers.tid AS uploadstreamers_tid, uploadstreamers.copyright AS uploadstreamers_copyright, uploadstreamers.copyright_source AS uploadstreamers_copyright_source, uploadstreamers.cover_path AS uploadstreamers_cover_path, uploadstreamers.description AS uploadstreamers_description, uploadstreamers.dynamic AS uploadstreamers_dynamic, uploadstreamers.dtime AS uploadstreamers_dtime, uploadstreamers.dolby AS uploadstreamers_dolby, uploadstreamers.hires AS uploadstreamers_hires, uploadstreamers.open_elec AS uploadstreamers_open_elec, uploadstreamers.no_reprint AS uploadstreamers_no_reprint, uploadstreamers.uploader AS uploadstreamers_uploader, uploadstreamers.user_cookie AS uploadstreamers_user_cookie, uploadstreamers.tags AS uploadstreamers_tags, uploadstreamers.credits AS uploadstreamers_credits, uploadstreamers.up_selection_reply AS uploadstreamers_up_selection_reply, uploadstreamers.up_close_reply AS uploadstreamers_up_close_reply, uploadstreamers.up_close_danmu AS uploadstreamers_up_close_danmu
FROM uploadstreamers
WHERE uploadstreamers.id = ?]
[parameters: (5,)]
(Background on this error at: https://sqlalche.me/e/20/e3q8)

其他补充描述

麻烦提供 data/data.sqlite3 文件以供开发者复现


Generate final tag and publish draft release for Wazuh 4.8.1

Description
This issue attempts to publish draft release and generate final tag for version 4.8.1 in the wazuh-security-dashboards-plugin repository.
Tasks

[ ] Generate final tag v4.8.1 from branch 4.8.1 on wazuh-security-dashboards-plugin repository.
[ ] Publish GitHub draft release from tag v4.8.1.

I'm closing this issue as the repository will not be used until version 4.9.0


[qt5-declarative] build failure

Host Environment

OS: WSL2 Ubuntu 20.04 on Windows 10
Compiler: g++ (Ubuntu 9.3.0-10ubuntu2) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34
Vcpkg package management program version 2020.06.15-unknownhash

To Reproduce
Steps to reproduce the behavior:
./vcpkg install qt5-declarative:x64-linux
Failure logs

Computing installation plan...
The following packages will be built and installed:
qt5-declarative[core]:x64-linux
Detecting compiler hash for triplet x64-linux...
Starting package 1/1: qt5-declarative:x64-linux
Building package qt5-declarative[core]:x64-linux...
Could not locate cached archive: /home/vgromov/.cache/vcpkg/archives/56/56a3582070ada91546e682e5be82067426639868.zip
-- Using cached /home/vgromov/devenv/vcpkg/downloads/qtdeclarative-everywhere-src-5.15.0.tar.xz
-- Cleaning sources at /home/vgromov/devenv/vcpkg/buildtrees/qt5-declarative/src/5.15.0-ba8b6ef309.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/vgromov/devenv/vcpkg/downloads/qtdeclarative-everywhere-src-5.15.0.tar.xz
-- Using source at /home/vgromov/devenv/vcpkg/buildtrees/qt5-declarative/src/5.15.0-ba8b6ef309.clean
-- Configuring x64-linux-rel
-- Configuring x64-linux-rel done
-- Configuring x64-linux-dbg
-- Configuring x64-linux-dbg done
-- Package build-x64-linux-dbg
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:72 (message):
Command failed: /usr/bin/make -j 17
Working Directory: /home/vgromov/devenv/vcpkg/buildtrees/qt5-declarative/x64-linux-dbg
Error code: 2
See logs for more information:
[/home/vgromov/devenv/vcpkg/buildtrees/qt5-declarative/package-build-x64-linux-dbg-out.log]
/home/vgromov/devenv/vcpkg/buildtrees/qt5-declarative/package-build-x64-linux-dbg-err.log
Call Stack (most recent call first):
scripts/cmake/vcpkg_build_qmake.cmake:31 (vcpkg_execute_required_process)
scripts/cmake/vcpkg_build_qmake.cmake:66 (run_jom)
installed/x64-linux/share/qt5/qt_build_submodule.cmake:12 (vcpkg_build_qmake)
installed/x64-linux/share/qt5/qt_submodule_installation.cmake:8 (qt_build_submodule)
ports/qt5-declarative/portfile.cmake:2 (qt_submodule_installation)
scripts/ports.cmake:79 (include)
Error: Building package qt5-declarative:x64-linux failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: qt5-declarative:x64-linux
Vcpkg version: 2020.06.15-unknownhash
Additionally, attach any relevant sections from the log files above.

package-build-x64-linux-dbg-err.log
package-build-x64-linux-dbg-out.log

@Neumann-A Could you please take a look?
Thanks.

@JackBoosY exhaustedmemory does not look like something I am able to fix

Similar issue with qt5 bug https://bugreports.qt.io/browse/QTBUG-87117, I tried the patch, however it doesn't work.

Cannot open foreign types file /home/vgromov/devenv/vcpkg/installed/x64-linux/debug/lib/metatypes/qt5network_metatypes.json
/usr//binusr//ldbin:/ ld/:home //vgromovhome//devenvvgromov//vcpkgdevenv//installedvcpkg//x64installed-/linuxx64/-debuglinux//libdebug//libQt5Core.alib:/ libQt5Core.aerror:  addingerror  symbolsadding:  symbolsmemory:  exhaustedmemory
 exhausted

Please make sure you have enough memeory and disk.


panic: runtime error: invalid memory address or nil pointer dereference

Trying to run in portainer, getting this error in the logs when accessing the metrics page which kills the container.

Same issue trying to run this directly in a ubuntu vm
2020/01/03 14:57:42 failed to get session: invalid character '<' looking for beginning of value
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7bad29]

I would guess that it is most likely an authentication issues, as the exporter expects JSON to be returned in the response but something else is read from the body.

It shouldn't panic though...

Hmm. I dont have a user / pass for my transmission. Do you think that might do it?

same here
appuser@home-nas:/opt/exporter_transmission$ docker logs exporter_transmission
2020/03/30 15:52:31 starting transmission-exporter
2020/03/30 15:52:31 no .env present
2020/03/30 15:52:32 failed to get session stats: invalid character '<' looking for beginning of value
2020/03/30 15:52:32 failed to get session: invalid character '<' looking for beginning of value
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x7bbc6f]

goroutine 6 [running]:
main.(*SessionStatsCollector).Collect(0xc0000968a0, 0xc000180060)
	/go/src/github.com/metalmatze/transmission-exporter/cmd/transmission-exporter/session_stats_collector.go:118 +0xcf
github.com/prometheus/client_golang/prometheus.(*Registry).Gather.func1()
	/go/pkg/mod/github.com/prometheus/client_golang@v0.9.0-pre1.0.20181010161331-7866eead363e/prometheus/registry.go:430 +0x19d
created by github.com/prometheus/client_golang/prometheus.(*Registry).Gather
	/go/pkg/mod/github.com/prometheus/client_golang@v0.9.0-pre1.0.20181010161331-7866eead363e/prometheus/registry.go:522 +0xe12

I got this error when I was using hostname that was not in rpc-host-whitelist

@metalmatze it happens for me when transmission is moving files from download directory to final destination which causes timeouts of transmission rpc. the whole transmission is stuck at this point because it's single thread app and when it copies files it doesn't do anything else.
when the copying completes it starts to work again though... it looks like bad handling of rpc errors / timeouts but i'm not a golang dev so i don't understand the code much.

I checked the exporter code and from that little I know about golang I would say there should be no problem. You are correctly checking that err is nil but the code seems tk go through that condition and later fails because there is no data in the response.
Do you have any idea what could be the cause of this error?


Fix playwright tests

I think we might have to add something to our GitHub action to make it work. When it fails it says something about running a command.

Please don't merge

Looks good Jonathan. Nice work!


falsy issue on template and templateUrl

this line should check for defined, not falsy.

What is the use case for having falsy templateUrl or template?

Good question, should have specified. For some advanced layout stuff, I want to have a "field" in place just to have a node there with a specific class. So something like:
{template: '', className: 'my-class-name'}

Right now, I have to do:
{template: 'nbsp;', className: 'my-class-name'}

Less fun...

What are the use cases for 0, false and null?


chore: Bump Microsoft.Build.Utilities.Core

GitHub Issue: #

Proposed Changes

Feature

Description
Update Microsoft.Build.Utilities.Core from 17.1.0 to 17.2.0.
Checklist
Please check if your PR fulfills the following requirements:

[ ] Documentation has been added/updated
[ ] Automated Unit / Integration tests for the changes have been added/updated
[ ] Contains NO breaking changes
[ ] Updated the Changelog
[ ] Associated with an issue

Other information

We are still keeping this repo alive? :)


[EventRequest] table 12170 "Payment Lines"  - Function CreatePaymentLinesSales

Can we please get the following event?
STANDARD CODE:
`                until OldDate = PaymentLines."Due Date";
            PaymentLines."Pmt. Discount Date" := CalcDate(PaymentLinesTerms."Discount Date Calculation", SalesHeader."Document Date");

            if PaymentLines."Pmt. Discount Date" < SalesHeader."Document Date" then
                PaymentLines."Pmt. Discount Date" := SalesHeader."Document Date";
            PaymentLines.Insert();
        until PaymentLinesTerms.Next() = 0;`

NEW CODE
`                  until OldDate = PaymentLines."Due Date";
            PaymentLines."Pmt. Discount Date" := CalcDate(PaymentLinesTerms."Discount Date Calculation", SalesHeader."Document Date");

            if PaymentLines."Pmt. Discount Date" < SalesHeader."Document Date" then
                PaymentLines."Pmt. Discount Date" := SalesHeader."Document Date";
            OnBeforeInserPaymentLines(PaymentLines, SalesHeader);
            PaymentLines.Insert();
        until PaymentLinesTerms.Next() = 0;`

NEW EVENT
         [IntegrationEvent(false, false)]          local procedure OnBeforeInserPaymentLines(var PaymentLines: Record "Payment Lines"; SalesHeader: Record "Sales Header")     begin     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.