How to solve the problem that the app is connected before Roudi is terminated, causing the app to fail to access the socket after Roudi is terminated ("Transport endpoint is not connected")

Required information
Operating system:
E.g. Ubuntu 22.04 LTS
Compiler version:
E.g. GCC 11.4.0
Eclipse iceoryx version:
v2.0.3
Observed result or behaviour:
（Multiple programs register apps to connect to Roudi. When a program is terminated, the systemd restarts the service.）
When roudi terminates, since multiple app processes are connected to roudi, after roudi kills the app, the app connects to roudi again, and after connecting, roudi terminates. At this time, the roudi socket file is still in the "/tmp" directory. (Multiple processes of the app are automatically restarted through the system) At this time, the app reports an error (always):
/tmp/iceoryx-2.0.3/iceoryx_hoofs/source/posix_wrapper/unix_domain_socket.cpp:249 { iox::cxx::expected<iox::posix ::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const -> iox_sendto } ::: [ 107 ] Transport endpoint is not connected
internal logic error in unix domain socket "/tmp/roudi" occurred
2024-02-04 12:10:13.794 [Warning]: Error in sending keep alive
roudi's logs:
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: Log level set to: [ Debug ]
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: Reserving 66761736 bytes in the shared memory [iceoryx_mgmt]
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: [ Reserving shared memory successful ]
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.756 [ Debug ]: Registered memory segment 0x7f566d854000 with size 66761736 to id 1
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: Reserving 149264720 bytes in the shared memory [root]
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: [ Reserving shared memory successful ]
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.805 [ Debug ]: Roudi registered payload data segment 0x7f56649fa000 with size 149264720 to id 2
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: RouDi is ready for clients
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.943 [ Debug ]: Registered new application WUdOKBTUjfLdAA
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.944 [ Debug ]: Created new PublisherPort for application 'WUdOKBTUjfLdAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.944 [ Debug ]: Created new SubscriberPort for application 'WUdOKBTUjfLdAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.944 [ Debug ]: Created new ConditionVariable for application WUdOKBTUjfLdAA
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.966 [ Debug ]: Registered new application lWwTkadkAgVCAA
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.967 [ Debug ]: Created new PublisherPort for application 'lWwTkadkAgVCAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.967 [ Debug ]: Created new SubscriberPort for application 'lWwTkadkAgVCAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.967 [ Debug ]: Created new ConditionVariable for application lWwTkadkAgVCAA
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.994 [ Debug ]: Registered new application lFzAeaABrnCCAA
04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.995 [ Debug ]: Created new PublisherPort for application 'lFzAeaABrnCCAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.995 [ Debug ]: Created new SubscriberPort for application 'lFzAeaABrnCCAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:24:55 ubuntu22 iox-roudi[350832]: 2024-02-04 11:24:55.995 [ Debug ]: Created new ConditionVariable for application lFzAeaABrnCCAA
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.721 [ Debug ]: Joining 'Mon+Discover' thread...
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.814 [ Debug ]: ...'Mon+Discover' thread joined.
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.986 [ Debug ]: Registered new application lfDmfeYTSGTaAA
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.986 [ Debug ]: Created new PublisherPort for application 'lfDmfeYTSGTaAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.986 [ Debug ]: Created new SubscriberPort for application 'lfDmfeYTSGTaAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:25:03 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:03.986 [ Debug ]: Created new ConditionVariable for application lfDmfeYTSGTaAA
2月 04 11:25:04 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:04.009 [ Debug ]: Registered new application JOggKaNCqILEAA
2月 04 11:25:04 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:04.010 [ Debug ]: Created new PublisherPort for application 'JOggKaNCqILEAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:25:04 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:04.010 [ Debug ]: Created new SubscriberPort for application 'JOggKaNCqILEAA' with service description 'Service: ***, Instance: ***, Event: ***'
2月 04 11:25:04 ubuntu22 iox-roudi[350832]: 2024-02-04 11:25:04.010 [ Debug ]: Created new ConditionVariable for application JOggKaNCqILEAA
2月 04 11:25:13 ubuntu22 systemd[1]: ***.service: State 'stop-sigterm' timed out. Killing.
2月 04 11:25:13 ubuntu22 systemd[1]: ***.service: Killing process 350832 (iox-roudi) with signal SIGKILL.
2月 04 11:25:13 ubuntu22 systemd[1]: .service: Killing process 350835 (MemPoolIntr) with signal SIGKILL.
2月 04 11:25:13 ubuntu22 systemd[1]:.service: Main process exited, code=killed, status=9/KILL
2月 04 11:25:13 ubuntu22 systemd[1]: ***.service: Failed with result 'timeout'.
2月 04 11:25:13 ubuntu22 systemd[1]: Stopped iceoryx roudi daemon.
Expected result or behaviour:
How to prevent the app process from reconnecting during Roudi termination (or how to detect that Roudi is unavailable at this time)?
Conditions where it occurred / Performed steps:

Before roudi terminates, delete roudi socket file?

@zhang-ke-liang the socket file is already deleted when RouDi is terminated gracefully, e.g. sending SIGTERM. A SIGKILL will terminate the process without giving it a chance to clean up its resources. Please ensure that RouDi is terminated gracefully and the socket will be removed.
You still might have the problem that applications open the socket and try to register while RouDi is shutting down but they will eventually run into a timeout. Unfortunately, there is nothing we can do about this.

Hi, its possible to detect error like this in my application?
/tmp/iceoryx-2.0.3/iceoryx_hoofs/source/posix_wrapper/unix_domain_socket.cpp:249 { iox::cxx::expected<iox::posix ::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const -> iox_sendto } ::: [ 107 ] Transport endpoint is not connected

i assume something is failing where I can check if this is happening?

@ceccocats that depends where it occurs. If you use the socket directly then the return value of the socket call will inform you. If it is deep inside iceoryx we either propagate the error up in the stack or handle it locally but the message is printed nevertheless.
In case this happens during the startup of the application, there is a work in progress experimental API where you could catch this during startup and handle it yourself. Currently only the publisher, subscriber and waitset are available with the experimental API.

I also come across this problem.
/tmp/binarydeb/ros-galactic-iceoryx-utils-1.0.0/source/posix_wrapper/unix_domain_socket.cpp:245 { iox::cxx::expected<iox::posix::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const }  :::  [ 107 ]  Transport endpoint is not connected
/tmp/binarydeb/ros-galactic-iceoryx-utils-1.0.0/source/posix_wrapper/unix_domain_socket.cpp:245 { iox::cxx::expected<iox::posix::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const }  :::  [ 107 ]  Transport endpoint is not connected
internal logic error in unix domain socket "/tmp/roudi" occurred
2024-07-24 02:07:03.524 [Warning]: Error in sending keep alive
/tmp/binarydeb/ros-galactic-iceoryx-utils-1.0.0/source/posix_wrapper/unix_domain_socket.cpp:245 { iox::cxx::expected<iox::posix::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const }  :::  [ 107 ]  Transport endpoint is not connected
/tmp/binarydeb/ros-galactic-iceoryx-utils-1.0.0/source/posix_wrapper/unix_domain_socket.cpp:245 { iox::cxx::expected<iox::posix::IpcChannelError> iox::posix::UnixDomainSocket::timedSend(const string&, const iox::units::Duration&) const }  :::  [ 107 ]  Transport endpoint is not connected
internal logic error in unix domain socket "/tmp/roudi" occurred

The experimental API is released ?  @elBoberido

The experimental API is released ?  @elBoberido

@lix19937 the experimental API is not released but in the main branch and hidden behind a cmake flag

@elBoberido  thanks.


[Demon Gate] merge key attributes

Changes / Comments
The sheet currently has an incorrect setup in that instead of a single attribute with current and max values, key fields like hit points are represented by separate attributes for the current and the max value. This means that they can't easily be used for tokens.
This release swaps the sheet to use single attributes in the normal fashion and will automatically migrate old values if required. The old values are left unchanged for reference.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[x] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[x] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.


Fix .NET and .NET Standard file version

This addresses issue #1945
The changes also allow us to pass a build number to the build script in the CI to properly version CI artifacts.

/azp run CI-SqlClient

How do I make sure I get this corrected? I am using .net8 and trying to run my app in a Docker Container and getting the error:
Process Run Exception: Could not load file or assembly 'Microsoft.Data.SqlClient, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=23ec7fc2d6eaa4a5'. The system cannot find the file specified.
We are using Dev Azure pipeline to build the application and then deploy from there to our Docker Container.


add alpine image

I've added alpine build. Alpine is used in rabbitmq-ha Helm chart.
Published alpine image will help to integrate the plugin into this Helm chart.

Oh, very cool, could you please add a line to the README?

I've mentioned Alpine-based image

Thank you!


Make every possible overflow (that I can see) checked

This is still in draft because I need to

actually verify that all of these are reachable (As in, panic on the current version)
write tests to make sure all of the changes worked

These bugs weren't found by fuzzing since some of them are a pretty tight margin, and is basically "guess until you're correct". Which explains why the fuzzer couldn't really find em.
Going to say Fixes: #439 since that is indeed one of the issues that will be fixed by this.

Okay, what I currently have is as much as I can really do. I did try writing tests for the x86 version, but just couldn't get it to fail, even when I undid the if i > 0 change.
Tried both translating the amd64 test, and also tried modifying an existing x86 test, setting the stack pointer to 0 and trying to get it to underflow. No dice.
But I've kinda left this PR long enough (sorry!) so I'm going to just say it's ready for review now and call it good enough.


Outdated commons-lang3 version

While using Enforcer plugin and DependencyCheck plugin together in the same build, I found an issue with transitive dependencies, specifically the "commons-lang3" version used by Enforcer is older, and breaks DependencyCheck.
See https://github.com/kordamp/enforcer-gradle-plugin/issues/17#issuecomment-2271201919 and following comments for more details.
To address, I forced the Enforcer plugin to use an updated commons-lang3 version, 3.15.0.
The example used may the the root of this issue: pulling in "enforcer" rather than "build-enforcer" plugin in settings.gradle changes the classpath for other plugins, so the conflicting versions of commons-lang3 becomes apparent.

🎉 This issue has been resolved in v0.14.0 (Release Notes)


Add non persistence support to remote image.

We don't want the course catalog to persist all the course images.
Factor CourseCardViewModel to better break apart the different cases.
This also makes the environment part of the model setup instead of the view,
which seems like a more natural separation of concerns and should make
it harder to forget, which we've had a couple bugs about.

@mikekatz please review

nice bit of refactor :+1:


Load contact-store data

Describe the feature you'd like
We need to load contact store into local storage and provide a simple metadata lookup function.

https://github.com/holium/campfire/issues/6


Fasta does not instantiate type parameters in mixin applications

Prior to CL 71781 override checks for methods obtained from mixin were disabled. The CL only enables the arity check which is sufficient to resolve the issue described in #34235. We should enable the return type check and parameter type check too. But enabling them for mixins causes false-positives to be produced which in turn prevents the SDK from compiling (libraries such as collections make extensive use of mixins with generic type parameters).
As the following example illustrates, the problem seems to be that generic type parameters are not properly instantiated in mixin applications.
abstract class A<T> {
  T id(T a);
}

class B<T> {
  T id(T a) => a;
}

class C = A<int> with B<int>;

void main() {
  C c = new C();
}

Enabling the return type check causes the following (wrong) error:
Error: The return type of the method 'C::id' is #lib1::B::T, which does not match the return type of the overridden method (dart.core::int).
Change to a subtype of dart.core::int.
  T id(T a) => a;

The type checker complains that the inherited method id in C has a generic return type T, but its interface requires the return type to be a subtype of int. In the mixin application we explicitly instantiate B with int. It seems that this information is lost somewhere internally in Fasta.

This is probably an internal code issue only. Hence the removal of front-end-missing-error.


Cannot send SPL token to SPL address (not created)

I noticed this when trying to send pasting a SPL address (not initialized, 7LivtbXjY4kdmuo5smGFQGG9PioB4zDqS83FN8yJtJ3H ) I get an error on JS console:

Received error validating address TypeError: Cannot read property 'owner' of null

and error Cannot send to address with zero SOL balances.
I do believe this is expected. But also I wanted to ask: How do you decide which SPL address to choose when a user provides a SOL address?
https://github.com/project-serum/spl-token-wallet/blob/ec035a00612d20b2027464e7e74beaf7d72e0732/src/utils/tokens/index.js#L27
why getProgramAccounts instead of getTokenAccountsByOwner?
How do you pick it if the SOL address never received any SPL token before? because It looks like you're not getting the address you'd get using this code snippet for example https://spl.solana.com/associated-token-account#finding-the-associated-token-account-address

How do you decide which SPL address to choose when a user provides a SOL address?
This breaks into two cases (1) the destination user does not have an SPL token account for the token being sent and (2) a user already has at least one SPL token account for the chosen mint. In case (1) an SPL token account for the mint is created and ownernship is assigned to the specified SOL address. In case (2) all SPL token accounts for the (mint, owner) pair are fetched and the token account with the highest balances is chosen as the destination.

Why getProgramAccounts instead of getTokenAccountsByOwner?
They are equivalent in this case. I think the reason getProgramAccounts here is purely historical.

How do you pick it if the SOL address never received any SPL token before?
This is the same as case (2) above where a new SPL token accounts is created and ownership is assigned to the SOL address: https://github.com/project-serum/spl-token-wallet/blob/master/src/utils/tokens/index.js#L164

But when sending to a new SOL address account, do you use https://spl.solana.com/associated-token-account#finding-the-associated-token-account-address program?

How do you know if the user provided a SOL or a SPL token address? assuming both have 0 balance

But when sending to a new SOL address, do you use the https://spl.solana.com/associated-token-account#finding-the-associated-token-account-address program?

Currently no, but it would be good to switch over. The current functionality pre-dates the create_associated_token_account function. Feel free to file an issue addressing this specifically!

How do you know if the user provided a SOL or a SPL token address?

Looking at the owner account of a supplied account. An SPL token account's owner is the SPL token program. Note the terminology here is somewhat mixed and on the explorer it will show the SOL account as the owner, when strictly that is not true. See https://docs.solana.com/developing/programming-model/accounts#ownership-and-assignment-to-programs for more info on account ownership


The highlighted element is not clickable

My project is based on the VUE + Element UI, and I found that using DriverJS in modal frames would cause highlighted elements to be unclickable. Examples are as follows

<el-button class="discernBtn" type="primary"
@click="doCropper">识别二维码

let driver = new Driver({
allowClose: false,
doneBtnText: '完成',
closeBtnText: '关闭',
nextBtnText: '下一步',
prevBtnText: '上一步',
opacity:0.5,
animate:false
})
let items = {
element: '.discernBtn',
popover: {
title: '温馨提示',
description: '请选择',
position: "bottom"
}
}
driver.highlight(items)

I am having the same problem. The buttons/elements inside Highlighted parts not clickable

maybe related: #293

I want to contribute to this issue.

We just released v1.0 of driver.js which has been rewritten from the ground up. This issue should no longer exist. Please have a look at the docs and do let me know if you face any issues.


Use flowParameters.executionMaxRetries to control flow retry

Why we need this
Previously Azkaban use only isExecutionRetried boolean flag to record and control flow/execution retry info, we now want to allow retrying for a number of times defined by the user.
What's done

isExecutionRetried only means whether an execution is retried
At flow submit time, if the flow.retry.statuses is set, then flow.max.retries fallback value is 1 if not set
use flow.max.retries to determine how many times can this execution retry at restartFlow method

Tests done

unit tests
deploy the change to test cluster, launched an execution with flow.max.retries=2 and trigger EXECUTION_STOPPED by killing the k8s pod:

The old execution got into EXECUTION_STOPPED and an new execution is being restarted:

The old execution with "flow.max.retries=2" while the retried new execution has "flow.max.retries=1"

LGTM ! Thanks for incorporating the reordering of the functions so its easied to read.


Automatically encode all email links using as hex HTML entities

It currently only encodes the href, not any content of the node.
So something like
[mail<EMAIL_ADDRESS>will only encode the link.
The same goes for<EMAIL_ADDRESS>
Although in the latter case one could actually argue to also encode the text.
Thoughts?
Fixes #193

I think this is out of scope for now since it isn't part of CommonMark or the GitHub Flavoured extension.
Just to comment about email obfuscation in general: IMO it is better to display the email in plaintext without obfuscation so that users can see that the email is given out in plaintext. It's trivial to write a decoder for email addresses obfuscated in this way, and I think the worst thing of all would be for a user to believe that they somehow had not given their email address out publicly because of obfuscation.
 I think we shouldn't hide this fact.
The appearance of safety or security where there is none is likely to be worse than none on its own, because it will likely encourage the user to behave as if there were some in place.


INSTALLATION IS WRONG!!!! PLEASE HELP!!!

Use npm or yarn ，it always shows error “ fatal: unable to access 'https://github.com/ethereumjs/ethereumjs-abi.git/': Failed to connect to github.com port 443”
I guess the reason is that "ethereumjs-abi" is depressed ?
Please HELP !!!

This is a proxy error, it happens sometimes in windows machines
can you please try this solution:
https://stackoverflow.com/a/18356572
and I also recommend you to use bash on windows, it eliminates a lot of those issues

Your way doesn't work。
I suggest you do not use the depressed  "ethereumjs-abi" any more .
I recommend to use the [Ethers.js v5 ABI Encoder](https://docs.ethers.io/v5/api/utils/abi/) as a replacement which supports the new ABI Coder v2 types and is under active development.

hey @john000612 thanks for reaching out and using the kit.
Unfortunately this is not an issue with the kit, its a dependancy of a dependancy so not something we can fix for you. the good news is that the new version with use a mono repo so issues like this will be much fewer and the new Moralis SDK2 and new Moralis-React will be used soon also so i am sure this will be updated on their end.
Please bare with us in this beta period. TY for your support


AttributeError: 'NoneType' object has no attribute 'info'

Just getting familiar with Academic and academic-admin to consider using to update my academic website.  It all looks great!
But I'm having some issues importing my publications from a bib file.  For my current website I do this using bib2html, with some bespoke scripts.  academic-admin looks like a much better way to do this so I'm keen to switch, but it doesn't seem to be working for me at present.  Not sure if I have installed correctly(?), although I did follow the instructions on the website.
Here is the traceback when running inside a cloned version of academic:
> academic import --bibtex mybibs.bib -v
08:32:38PM DEBUG: Found Entry: ['article', 'id', {'YEAR': '2019', 'JOURNAL': 'Journal', 'TITLE': 'Title here', 'AUTHOR': 'A. N. Other'}]
08:32:38PM DEBUG: Apply customizations and return dict
Traceback (most recent call last):
  File "/usr/local/bin/academic", line 10, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/site-packages/academic/cli.py", line 94, in main
    import_bibtex(args.bibtex, pub_dir=args.publication_dir, featured=args.featured, overwrite=args.overwrite, normalize=args.normalize)
  File "/usr/local/lib/python3.7/site-packages/academic/cli.py", line 111, in import_bibtex
    parse_bibtex_entry(entry, pub_dir=pub_dir, featured=featured, overwrite=overwrite, normalize=normalize)
  File "/usr/local/lib/python3.7/site-packages/academic/cli.py", line 116, in parse_bibtex_entry
    log.info(f"Parsing entry {entry['ID']}")
AttributeError: 'NoneType' object has no attribute 'info'

The test bib files simply contains
@article{id,
    AUTHOR      = "A. N. Other",
    TITLE       = "Title here",
    JOURNAL     = "Journal",
    YEAR        = "2019"
}

I'm running Python 3.7 (installed via anaconda) on Mac OS X Mojave.

@gcushen Thanks for the rapid fix!  Just picked up your recent changes and all working well on my side now.  I'm loving hugo-academic already!  Finally gave me the push I needed to refresh my academic website for the first time in about 10 years!


Refactor sweeps interface

This work-in-progress PR implements a more flexible sweeps interface for alternating_update based algorithms.
Currently, a proof-of-principle is implemented for tdvp, while other algorithms are broken. The purpose of this draft is to discuss the overall structure of the code, not the details of the implementation of specific functions.
The interface is based around passing a list of length nsweeps, each of which contains four NamedTuples: extracter_kwargs, updater_kwargs, inserter_kwargs, internal_kwargs. The latter hold the epynomous functions as well as their specified keyword args and  are passed as kwargs to tdvp, with the exception of internal_kwargs. Any other kwargs passed to tdvp will be moved into inserter_kwargs for convenience and continuity with prior interfaces. internal_kwargs is not supposed to be passed to tdvp, but instead generated inside tdvp, and in this case contains for example the time_step argument. internal_kwargs is also the only NamedTuple which is not strictly checked for passing unexpected keyword arguments.
The use of internal_kwargs allows to make the coupling between sweep_plan generation and the updater signature looser. Note that the interface is still somewhat verbose: If we wish to pass a kwarg to both inserter and updater, we need to list it twice in the call to tdvp.
A more complicated design would be to group the function (e.g. updater) and a collection of symbols (i.e. keys of kwargs) it can digest. For example for the default TDVP behaviour, we would use something like (exponentiate,[:time_step]). tdvp_sweeps_plan could then be made aware of this signature, in order to not add substep to the updater_kwargs. Matt and I discussed this extensively already, discarding this idea as to complicated.
Other changes:

[ ] Rename extracter to extract, updater to update, inserter to insert. (Maybe, let's think about this.)
[x] Removed sweeps_param from alternating_update.
[x] Move sweep_plan related functionality to tree_sweeping.jl.
[x] Compute observables with sweep_observer instead of region_observer in tests.
[x] Move treetensornetworks/solvers/* to solvers, move solvers/* to solvers/local_solvers.
[x] Rename tree_sweeping.jl to sweep_plans.jl.
[x] Instead of processing inserter, updater, etc. into NamedTuple, use a Tuple instead.
[x] Define a function extend or fill_or_pad.
[x] Put more logic into sweep_plan functions vs. inside particular solvers like tdvp.
[x] Extend kwargs like nsites so they can be functions of the sweep.
[x] Rename and refactor process_kwargs_for_sweeps.
[x] New directory structure: sweep_plans/, alternating_update/, region_update/.
[x] Inside region_update, make a single named tuple for keyword arguments being passed to update! and region_printer.
[x] Update how region_printer, sweep_printer, region_observer!, sweep_observer! are passed.
[x] Refactor make_regions, define forward_regions(nsite, graph) such that forward_regions(2, path_graph(10)) = [(1, 2), (2, 3), (3, 4), ..., (9, 10)] and insert_region_intersections(forward_regions(2, path_graph(10))) = [(1, 2), (2,), (2, 3), (3,), (3, 4), ...(9,), (9, 10)].
[ ] Make tdvp compatible with various signatures for specifying timestep, including list of timesteps, which gets expanded. Implemented, but functionality tests need to be added.
[ ] define defaults, in separate, package-wide file?
[x] Make insert/extract independent of directionality of edges, ordering of vertices in region.

ToDo (once design question is settled):

[ ] adapt other solvers/default_sweep_plan
[ ] handle passing of args to observer (and to lesser extent printer) in a similar manner, or just pass all *_kwargs to observer?
[x] refactor cumbersome functions in tree_sweeping

@b-kloss here's a design idea for process_kwargs_for_sweeps (or whatever it will be called) for dealing with nested named tuples:
kwargs = (;
  update=expand_and_eigsolve_update,
  update_kwargs=(; eigsolve_kwargs=(; krylovdim=20), expand_kwargs=(; maxdim=30)),
  insert_kwargs=(; cutoff=1e-4),
)

can get processed recursively to:
(;
  update=[expand_and_eigsolve_update, expand_and_eigsolve_update, expand_and_eigsolve_update],
  update_kwargs=(; eigsolve_kwargs=(; krylovdim=[20, 20, 20]), expand_kwargs=(; maxdim=[30, 30, 30])),
  insert_kwargs=(; cutoff=[1e-4, 1e-4, 1e-4]),
)

for example for nsweeps=3. This then gets split to:
[kwargs, kwargs, kwargs]

which could again be done recursively. From what I can tell this doesn't lead to any ambiguity, since if you want a keyword argument to be a NamedTuple, you can wrap it in a Vector, but maybe I'm missing something there.

By the way, it may be helpful to use a package like StructWalk.jl for recursively calling into the nested NamedTuples.
Also, I guess we want to think about a more generic interface for adding on subspace expansion to any local solver. An interface I could imagine is:
kwargs = (;
  updater=compose_updaters(; solver=eigsolve_updater, expander=local_subspace_expansion),
  updater_kwargs=(; solver_kwargs=(; krylovdim=20), expander_kwargs=(; maxdim=30)),
  inserter_kwargs=(; cutoff=1e-4),
)

Then, compose_updaters(...) can be a function that builds a nested function that includes the subspace expansion and the solver. It could be quite general, i.e. not be hardcoded to assume it accepts keyword arguments solver and expander, and for each updater * passed to compose_updaters it will look for the corresponding keyword arguments *_kwargs.

Refactor make_regions, define forward_regions(nsite, graph) such that forward_regions(2, path_graph(10)) = [(1, 2), (2, 3), (3, 4), ..., (9, 10)] and insert_region_intersections(forward_regions(2, path_graph(10))) = [(1, 2), (2,), (2, 3), (3,), (3, 4), ...(9,), (9, 10)].
There's a problem with this on trees, at least for nsites=1, and to a lesser extent also nsites=2. It seems impossible to recover for nsites=1 what the reverse edge is supposed to be when two regions are not contiguous, as happen's on general trees. For nsites=2, this also happens but it can be recovered by looking at the past/future regions.
Currently, there's an implementation of reverse_region that's working and similar to the logic in forward_region --- both of them are specialized to nsites=1,2. I suggest we stick with that for now and leave a more general insert_region_intersections logic for the future?

There's a problem with this on trees, at least for nsites=1, and to a lesser extent also nsites=2. It seems impossible to recover for nsites=1 what the reverse edge is supposed to be when two regions are not contiguous, as happen's on general trees. For nsites=2, this also happens but it can be recovered by looking at the past/future regions. Currently, there's an implementation of reverse_region that's working and similar to the logic in forward_region --- both of them are specialized to nsites=1,2. I suggest we stick with that for now and leave a more general insert_region_intersections logic for the future?

It seems like it is easy to extend to the the case of nsites == 1 by including edges incident to the vertex when considering region intersections.
For nsites >= 2, I was picturing that at first you would compute the list of intersections of any region with any other region, independent of the update order. Then you could order the resulting region intersections based on the order of the original region updates.
Anyway, I see that it is a bit of an involved sub-project to get all of that logic correct and make sure it really works for many different types of graphs and update choices, so it sounds reasonable to use the existing code for now.

Codecov Report
Attention: Patch coverage is 81.86398% with 72 lines in your changes are missing coverage. Please review.

Project coverage is 73.56%. Comparing base (65ca518) to head (8833174).

Files
Patch %
Lines

src/solvers/defaults.jl
15.15%
28 Missing :warning:

src/solvers/tdvp.jl
74.00%
13 Missing :warning:

...c/solvers/alternating_update/alternating_update.jl
82.60%
8 Missing :warning:

src/solvers/contract.jl
80.95%
8 Missing :warning:

src/solvers/local_solvers/linsolve.jl
0.00%
5 Missing :warning:

src/utils.jl
86.66%
4 Missing :warning:

src/solvers/linsolve.jl
60.00%
2 Missing :warning:

src/solvers/local_solvers/eigsolve.jl
66.66%
2 Missing :warning:

src/solvers/region_update/update_step.jl
95.12%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #143      +/-   ##
==========================================
- Coverage   73.61%   73.56%   -0.05%
==========================================
  Files          71       74       +3
  Lines        4146     4241      +95
==========================================
+ Hits         3052     3120      +68
- Misses       1094     1121      +27

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks again @b-kloss, this is a big improvement for making the code both simpler and more flexible and customizable!

Huge PR! And a lot of work. The code looks so much cleaner now and I'm enthused about the direction this is going.


Upgrade com.uber.nullaway:nullaway 0.10.5 -> 0.10.6

This PR contains the following updates:

Package
Type
Update
Change

com.uber.nullaway:nullaway

patch
0.10.5 -> 0.10.6

com.uber.nullaway:nullaway
compile
patch
0.10.5 -> 0.10.6

Release Notes

uber/NullAway
v0.10.6
Compare Source

Handle BITWISE_COMPLEMENT operator (#696)
Add support for AssertJ (#698)
Fix logic for @Nullable annotation on type parameter (#702)
Preserve nullness checks in final fields when propagating nullness into inner contexts (#703)
NullAwayInfer/Annotator data serialization support [experimental]

Add source offset and path to reported errors in error serialization. (#704)

Build / CI tooling for NullAway itself:

[Jspecify] Update test dep to final JSpecify 0.3.0 release (#700)
= Intermediate PRs: 0.3.0-alpha-3 (#692), 0.3-alpha2 (#691)
Update to Gradle 7.6 (#690)

[ ] If you want to rebase/retry this PR, check this box

The Java Platform team wishes you a happy festive period. Here is the suggested commit message:
Upgrade NullAway 0.10.5 -> 0.10.6

See:
- https://github.com/uber/NullAway/blob/master/CHANGELOG.md
- https://github.com/uber/NullAway/compare/v0.10.5...v0.10.6

Renovate be like

Header generated and modified from Sweaterify.


Bug: LogFormatter Timezone

Expected Behavior
this.envVarsService?.getTimezone() should return a valid timezone if it is configured.
Current Behavior
this.envVarsService?.getTimezone() is returning the path to the timezone on my machine (:/etc/localtime).
Code snippet
formatTimestamp(now) {
        const defaultTimezone = 'UTC';
        /**
         * If a specific timezone is configured and it's not the default `UTC`,
         * format the timestamp with the appropriate timezone offset.
         **/
        const configuredTimezone = this.envVarsService?.getTimezone(); //this returns ":/etc/localtime"
        if (configuredTimezone && !configuredTimezone.includes(defaultTimezone))
            return this.#generateISOTimestampWithOffset(now, configuredTimezone);
        return now.toISOString();
    }

Steps to Reproduce
Use @aws-lambda-powertools/logger locally
Possible Solution
No response
Powertools for AWS Lambda (TypeScript) version
2.5.0
AWS Lambda function runtime
20.x
Packaging format used
npm
Execution logs
No response

Hi @springer5296, thank you for opening this issue.
Without using Powertools, what's the value of the TZ environment variable?
For example, if you run this code below, what's the output?
console.log(process.env.TZ);

We support only values that appear in the TZ column of the IANA time zone database because that's the convention that the AWS Lambda service uses.

Thanks for the quick response @dreamorosi! It does seem like TZ is being set to that value for some reason. I will do some digging to determine how we can get this set to a proper value in our repo.

From what I read online, it seems that this should be the system-wide setting which is a symlink.  I am not sure Node.js is able to or can be configured to follow the link and convert it to the expected format.
If this is a test environment (but likely even if it isn't) I think the easiest way would be to set the desired timezone as environment variable in your code/entry points (process.env.TZ = 'Europe/Madrid') or when you launch your code (i.e. TZ=Europe/Madrid node foo.js).
I hope it helps!


kopt works with local+grouped reduce and tests

Made kopt to work with local+grouped reduce and a bit change limits of kopt to make search space smaller.
Added test for local+grouped reduce and some other transformations

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/codegen/optimizer.py              5               5
tinygrad/codegen/search.py                 4               5
------------------------------------------------------------
total                                      9              10
------------------------------------------------------------
lines added in the tinygrad folder: -1

I think an idea here is to rewrite the hand coded optimizations in terms of the actions taken by the optimizer.


Add accordions to content in WordPress

After final content is imported into WordPress, add accordions to all pages that need it. These are noted in Airtable.

Accordions added to all posts in WordPress. One outstanding page (Application resources) will need accordions when it gets loaded into WordPress. I've put this ticket in Blocked to reflect that there's a page that still needs the accordion.

Closing this issue as accordions have been added to Application resources. If accordions are needed on State cannabis consolidation I will add it when putting the content into WordPress manually.


redex-break error when execution

gradle run debug log :
14:55:47.197 [INFO] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] :app:assembleDebug (Thread[main,5,main]) completed. Took 0.001 secs.
14:55:47.197 [INFO] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] :app:redexDebug (Thread[main,5,main]) started.
14:55:47.197 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :app:redexDebug
14:55:47.197 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Starting to execute task ':app:redexDebug'
14:55:47.197 [DEBUG] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Determining if task ':app:redexDebug' is up-to-date
14:55:47.197 [INFO] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Executing task ':app:redexDebug' (up-to-date check took 0.0 secs) due to:
Task has not declared any outputs.
14:55:47.198 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter] Executing actions for task ':app:redexDebug'.
14:55:47.247 [INFO] [org.gradle.process.internal.DefaultExecHandle] Starting process 'command 'redex-break''. Working directory: /home/andy/AndroidStudioProjects/ComApp/app Command: redex-break -c /home/andy/AndroidStudioProjects/ComApp/app/build/redex.config --sign --keystore /home/andy/.android/debug.keystore --keyalias AndroidDebugKey --keypass android /home/andy/AndroidStudioProjects/ComApp/app/build/outputs/apk/app-debug.apk -o /home/andy/AndroidStudioProjects/ComApp/app/build/outputs/apk/app-debug-redex.apk
14:55:47.247 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Environment for process 'command 'redex-break'': {PATH=/home/andy/github/redex/usr/lib/jvm/jdk1.8.0_92/bin:/home/andy/Android/Sdk/platform-tools:/home/andy/Android/Sdk/platforms:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games, ......................................
14:55:47.248 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: STARTING
14:55:47.249 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Waiting until process started: command 'redex-break'.
14:55:47.251 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Changing state to: FAILED
14:55:47.252 [DEBUG] [org.gradle.process.internal.DefaultExecHandle] Process 'command 'redex-break'' finished with exit value -1 (state: FAILED)
14:55:47.253 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Finished executing task ':app:redexDebug'
14:55:47.254 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :app:redexDebug FAILED
14:55:47.254 [INFO] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] :app:redexDebug (Thread[main,5,main]) completed. Took 0.057 secs.
14:55:47.255 [DEBUG] [org.gradle.execution.taskgraph.AbstractTaskPlanExecutor] Task worker [Thread[main,5,main]] finished, busy: 0.397 secs, idle: 0.01 secs
14:55:47.263 [ERROR] [org.gradle.BuildExceptionReporter]
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter] FAILURE: Build failed with an exception.
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter]
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter] * What went wrong:
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter] Execution failed for task ':app:redexDebug'.
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter] > A problem occurred starting Redex. Ensure you have installed Redex using the instructions at https://github.com/facebook/redex
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter]
14:55:47.264 [ERROR] [org.gradle.BuildExceptionReporter] * Try:
14:55:47.265 [ERROR] [org.gradle.BuildExceptionReporter] Run with --stacktrace option to get the stack trace.
14:55:47.265 [LIFECYCLE] [org.gradle.BuildResultLogger]
14:55:47.265 [LIFECYCLE] [org.gradle.BuildResultLogger] BUILD FAILED
14:55:47.265 [LIFECYCLE] [org.gradle.BuildResultLogger]
14:55:47.266 [LIFECYCLE] [org.gradle.BuildResultLogger] Total time: 4.491 secs
I have put redex executable to the PATH,(as you can see in the log), why exec command is 'redex-break' instead of 'redex' ?

hi @linsea @timmutton : yes i am struggling to get this working. getting the same error, even though i have redex  installed in my machine. Have added this in my PATH variable as well . Still no luck.
Have you found a solution yet?
Thanks!

Same error here.

@deepti1408 @nethergrim the good news is, 1.1.0 fixes this, the bad news is it breaks when using the debug keystore...


Noteskins not loading

Describe your problem here.
Tried to add a custom noteskin to a song, uses an identical xml to my default only different is that the notes are animated
was working till the notes were played and the game crashed
restarted and now noteskins dont load when I type them into the chart editor, they instead just use the default note skin
I'm using 0.6.2
I put the noteskin in assets/shared/images and it worked fine the first time but then stopped working after a restart

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I edited the default note skin XML (which works fine)

found the issue, for starters the reason why the noteskin wouldnt load is because I'm a dumbass and forgot the load notes button existed
as for the crash, the xml didnt match up with the default note skin


Exploding loss in other datasets

Hi Ga Wu,
I'm implementing a CNN VAE very similar to yours, but I'm experiencing exploding loss.
Did you ever experience this during your development?
Thanks,
Franco

Hi Franco,
At some point, yes. But I do not recall what raised that problem anymore (some coding bugs).
I would check if the latent standard derivation is pushed to 0 during training first. :)

Think I fixed it. Too few convolutional layers it seems with silly (1x1) kernel sizes on a dataset with too much noise.
Thanks!


config: shadow-based upgrading/downgrading for versioned messages.

This PR replaces the previous unknown field smuggling style of upgrading
with shadow-based. Ultimately, we want to move away from shadows, but
for 1.13.0 this simplifies by removing smuggling.
In addition, we make two major changes that are backported from the
WiP v3alpha branch:

Rather than make translateOpaqueConfig() smart and version/type
aware, we switch to an iterative loadFromJson() that first attempts
to load as v2 and then falls back to v3. This relies on the property
that any v3 configuration that is ingestible as v2 has the same
semantics in v2/v3, which holds due to the highly structured
vN/v(N+1) mechanical transforms.

Support for downgrading to earlier versions is introduced to make it
easier for tests that are within the v(N-1) subset of vN to continue
to validate v(N-1), while still mostly using vN messages. This is
particularly useful for ensuring that e2e integration tests are using
v2 resources. As new v3 tests are introduced, tests will need to
eschew downgrading, but this should be a viable approach for 1.13.0.

Risk level: Low
Testing: additional unit tests added to cover opaque config conversion, Any unpacking, JSON loading and version conversion.
Part of #8082
Signed-off-by: Harvey Tuch<EMAIL_ADDRESS>

Tests added, ready for review in full.

@mattklein123 @lizan would it be possible to get a review on this one? This is the last substantial non-tooling related PR prior to the mega-upgrade?


[Cider] Systolic "Source" positions

A small PR which adds support for source position generation in the systolic array. The modifications to the systolic frontend are very similar to those made to the relay frontend.

Curious if we're adding any tests for the source-level debugging stuff anywhere?

Not at the moment, the debugger in general needs some more tests. I haven't gotten around to those since I need to tweak some things so that the debugger can take commands from a file and exit gracefully. Once that exists I can probably put together a runt test suite of sorts


Trim test files from npm package

Actually closed by https://github.com/captbaritone/grats/commit/bd110e34da12a990e27362e2ac52699dac7a5db9


screenProps are not available in navigationOptions.tabBar

I'm trying to display some badgeCounts from my redux state in a Tabbbar
I have the following Component structure:
RootComponent (is connected to redux state which contains e.g. badgeCounbts for my Tabbar)
renders:
<Tabs screenProps={{
      badgeCount,
    }}
/>

Tabs component
is just a js file that export:
const Tabs = TabNavigator({
  Home: {
    screen: props => {
      console.log(props)  // {badgeCount: 0, navigation: Object}
      return <TabHome screenProps={{
        badgeCount: props.badgeCount,
      }} />
    },
    path: 'home',
    navigationOptions: {
      tabBar: navigation => {
        console.log(navigation.props) // undefined
        return {
          icon: ({ tintColor, focused }) => {
            return <TabIcon badgeCount={ navigation.props.badgeCount } />
          },
        }
      }
    },
  },
...
}, {
  swipeEnabled: false,
  animationEnabled: true,
  backBehavior: 'none',
  tabBarOptions: {
    style: styles.tabBar,
    activeTintColor: DXColors.secondary,
    inactiveTintColor: DXColors.text_important_light_bg,
    showLabel: false,
  },
})

Is there any way to access the screenPropswithin my navigationsOptions.tabBar function?
I think I could just move the render function to the screen component (?) but I'd like to keep the tabbar stuff centralized in one file.

This is kinda related to #210 and #145 I think.

I've found if you add screenProps to the navigationOptions method arguments, you get them:
navigationOptions: ({ navigation, screenProps }) => ({      tabBarLabel: 'screenProps.foo: '+screenProps.foo });
Unfortunately if these values change, the Tab Bar does not rerender currently.

Closing in favor of linked issues.


Updates pfc css to import only references to the design-system

Shrinks pfc's main.css file by ~37kb with no downsides.
Testing:

Pull & build
All pfc pages should look identical to prod

Can this be closed in favor of https://github.com/cfpb/consumerfinance.gov/pull/7045, which also deletes the brand-palette?

Can this be closed in favor of https://github.com/cfpb/consumerfinance.gov/pull/7045, which also deletes the brand-palette?

Wow! Yeah, I totally forgot I've already done this @_@


chore(main): release 0.0.42

:robot: I have created a release beep boop
0.0.42 (2024-11-16)
Miscellaneous Chores

add rollup plugin to bundle types (0ff9b91)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v0.0.42
:sunflower:


How can I use Invoke-HardeningKitty

Hi,
I'm trying to use this hardening script, but appears this message

I try to see in the issues section but no information about this was found, what am I doing wrong?
Could someone explain please the steps
Here's the folder content of this script downloaded and extracted

Try to import the file using a relative path: Import-Module .\Invoke-HardeningKitty.ps1, then it should work.

Yes it works, thanks


First version of the contextual sidebar component

This is the only sidebar you'll ever need. Its purpose is to capture all the logic for sidebars in a single place so frontend apps become really simple.
This sidebar component is extracted from government-frontend - the corresponding PR that uses this will be up soon.
Note that I've changed as little as possible to make it work. We'll follow this up with a full refactor of the system. I hope to have something like a single class that decides what to show in the sidebar, and then different classes that generate the proper payloads for the HTML. Also, once this is complete we probably won't need the concept of AppHelpers anymore, making everything even simpler.
Todo:

[ ] Super high level integration test with random content

Superseded by https://github.com/alphagov/govuk_publishing_components/pull/228, which also does the sidebar and more.


Allow to use download_url for deployment

This pr is to add download_url configuration back, so that the users are able to keep using the download_url to download specific versions of data model.

If both download_url  and repo keys with valid value present, the workflow will use the repo.

Updates:

The codes used to download data models and generate config.json are merged into one script names config_schema.py.
Although using specific commits is currently not supported for repo, the repo key can now take branch or version as optional values, i.e. Sage-Bionetworks/data-models/v1.1.1 or  Sage-Bionetworks/data-models/develop. The version of schema (in config.json) will be the branch (develop) or version (v1.1.1) if it's provided.

@milen one issue I notice is that the function (get_digraph_by_edge_type('requiresComponent')) we used to auto generate config.json return empty nodes for NF data model. I see there are some values in the dependsOn column. I wonder if you have any ideas what might be the cause?
from schematic.schemas.generator import SchemaGenerator
sg = SchemaGenerator(path_to_json_ld="NF.jsonld")
component_digraph = sg.se.get_digraph_by_edge_type('requiresComponent')
components = component_digraph.nodes()
NodeView(())

@afwillia @milen-sage
Users can now keep using  download_url in schematic_config.yml now. I also added one flag --overwrite, whether to create a config.json from data models, so that users are able to use the existing config.json and set grace time to fill in the DependsOnComponents in data model if they haven't already.
I am going to merge this PR today if there is no further questions.

@allaway
This pr will allow to make the download_url configuration work again and repo configuration can also take branch/version. Once it's merged and I will sync up main as well, so that you could fetch the latest changes from main. However, you might need do two minor modifications for the NF app:

To update the data model configuration in the schematic_config.yml file:

if you would like to use this nf-model, you can set as repo: 'nf-osi/nf-metadata-dictionary/v6.0.0'
if you would like to use specific commit, you could comment out repo and keep usingdownload_ul to define the right downloading version of data model

Note
if both download_url and repo present, the workflow will use the value from repo

Since the workflow will not be able to auto generate the expected config.json from the current NF data model. You would still need to have the nf-config.json in your repo and disable the --overwrite flag in below snippet (remember to remove the \ after 'Sage-Bionetworks/schematic' as well):
https://github.com/Sage-Bionetworks/data_curator/blob/17b0ab2d21690ff9a4056ce387d2d70e2150278f/.github/workflows/shinyapps_deploy.yml#L78-L86

Feel free to let me know if you have any further questions.


operator awx-operator (1.2.0)

Signed-off-by: John Westcott IV<EMAIL_ADDRESS>Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want to use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[ ] Description of the managed Application and where to find more information
[ ] Features and capabilities of your Operator and how to use it
[ ] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[ ] Human readable name and 1-liner description about your Operator
[ ] Valid category name1
[ ] One of the pre-defined capability levels2
[ ] Links to the maintainer, source code and documentation
[ ] Example templates for all Custom Resource Definitions intended to be used
[ ] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@john-westcott-iv please remove operators/awx-operator/1.2.0/manifests/awx-operator.clusterserviceversion.yaml-e and operators/awx-operator/1.2.0/metadata/annotations.yaml-e


Update build infrastructure to CUDA 8.0; openmm 7.1.0 beta

@jchodera When you removed the noarch flag, you should also have remove the build skip section...

@jchodera When you removed the noarch flag, you should also have remove the build skip section...

Good catch! Sorry about that. Will fix.


update the nmt wrapper to the new rsmt2d.Tree interface

Description
This PR updates the nmt wrapper to the new rsmt2d.Tree interface. I'm leaving as a draft as I think there are somethings that still need to be updated before this can be merged.
Closes: #255

Codecov Report

Merging #256 (110d2b4) into master (eff282a) will increase coverage by 1.28%.
The diff coverage is 14.54%.


Recruit participants

@areighar @kstetsyuk @tlageman-epa
03/10/2021- Finalized email to recruit participants for Allowance Holdings Study.

@areighar @tlageman-epa @kstetsyuk
03/11/2021-Finalized participant screener and pre-screener email sent Caiti to begin recruiting Allowance Holdings users.


feat(accessibility-testing): introduce cypress-axe-core

Related Ticket(s)
#8063
Description
Add axe-core with cypress.
Changelog
New

added cypress command checkAxeA11y which calls checkA11y

has optional params context and additionalRules

added to each e2e-storybook test cy.injectAxe() and cy.checkAxeA11y()
added to plugins/index.js for us to use to be able to log as we test and use the table which is being used to print the validations
current setup is we are only checking critical issues and always returning true -> will change in the future as we resovle issues
added to card.e2e.js being able to focus on the card to show focus states
in footer.e2e.js showing how to use optional params in cy.checkAxeA11y()

Looks great @ariellalgilmore !
Looks like some merge conflicts, can you resolve?

The cloud-masthead e2e failures look like what I would expect if the tests are running without the experimental platform feature. @proeung Do you know how to enable that for a specific PR?


WebRTC ANR

When finishing a web-rtc call. One of the two devices will sometime stuck util an ANR message appears instead of exiting normally.

One scenario that it will 100% appear:
1.start a video call from device A
2.when device B receive the call hit hang up key immediately
3.device A hangs!

#3311 Same bug

Close.
A similar issue have been submitted!


[IOTDB-6260] Pipe: Wait for the hardlink/copied tsfile to finish being transfered before deleting

Description
When dropping the pipe, if there is a tsfile being reading or transfering, it will throw an error by calling Pipe Plugin‘s close() method and the file will not be unpinned.
so we add a check before deleting the tsfile, wait until the hardlink/copied file has been transfered.

Thanks for your contribution.
NO NEED TO FIX: the issue is already fixed by PR https://github.com/apache/iotdb/pull/11240


Regression in windows_chrome_dev_mode

The SecondRestartTime benchmark seems to consistently be above the baseline after https://github.com/flutter/flutter/pull/46090.

Reverted to unblock roll.

Benchmark was rebaselined


Error in : dialogs_app.py

When i run this bolt python app  and try to submit - the UI Screen just stuck without closing and it shows error - "We had some trouble connecting . Try Again"
i did a print and the UI accept and print the value in terminal but the dialog never close/submit.

Hi @jambeshmpt! The response you're getting seems to indicate that the view submission isn't being handled by your application.
Is the application one that we have published as an example, or is this one that you created?
In either case, can you confirm that you have a view submission listener that uses the same view callback ID of the modal you're submitting?

@jambeshmpt If I understand correctly, you are trying to run https://github.com/slackapi/bolt-python/blob/v1.14.3/examples/dialogs_app.py, right? I just confirmed the example app is still valid. It worked for me without any issues. Please go to https://api.slack.com/apps/{your app ID}/interactive-messages and make sure whether the Interactivity feature is enabled and a valid Request URL is set as necessary.
Also, as @misscoded mentioned, using modal views is the currently recommended way. You can find an equivalent example using a modal view here.
I hope this was helpful to you.

@jambeshmpt If I understand correctly, you are trying to run https://github.com/slackapi/bolt-python/blob/v1.14.3/examples/dialogs_app.py, right? I just confirmed the example app is still valid. It worked for me without any issues. Please go to https://api.slack.com/apps/{your app ID}/interactive-messages and make sure whether the Interactivity feature is enabled and a valid Request URL is set as necessary.
Also, as @misscoded mentioned, using modal views is the currently recommended way. You can find an equivalent example using a modal view here.
I hope this was helpful to you.

I am using socket mode  from Interactivity & shortcuts and for socket mode the URL is not require as per the options

i using the exact code from the github using socketmode

Hi @jambeshmpt! The response you're getting seems to indicate that the view submission isn't being handled by your application.
Is the application one that we have published as an example, or is this one that you created?
In either case, can you confirm that you have a view submission listener that uses the same view callback ID of the modal you're submitting?

Thank  you @misscoded , Yes i am using the same code from github without any change and running under socket mode .
one positive point is - when i submit  it actually going to the below code
@app.action("dialog-callback-id")
def dialog_submission_or_cancellation(ack: Ack, body: dict):
submission = body["submission"]
print(submission["server_name"])
this does print one of the text I entered in the text input field but the modal dialog stay as-is and shows error when i submit  .

@jambeshmpt Thanks for your reply. Could you share your whole source code to reproduce the issue? I've already confirmed the dialog example code works even with SocketModeHandler. I may be able to detect some difference in your code.

@jambeshmpt Thanks for your reply. Could you share your whole source code to reproduce the issue? I've already confirmed the dialog example code works even with SocketModeHandler. I may be able to detect some difference in your code.

Here is the code i am running -
`
import logging
import os
import re
from dotenv import load_dotenv
from slack_bolt import App, Ack
from slack_bolt.adapter.socket_mode import SocketModeHandler
#load_dotenv()
#SLACK_APP_TOKEN = os.environ["SLACK_APP_TOKEN"]
#SLACK_BOT_TOKEN = os.environ["SLACK_BOT_TOKEN"]
SLACK_APP_TOKEN = "xapp-1-A03UW7H2V35-3967802867255-"
SLACK_BOT_TOKEN = "xoxb-378962989360-3982598991731-"
app = App(token=SLACK_BOT_TOKEN, name="tabslash")
logger = logging.getLogger(name)
#########
@app.command("/tabforslack")
def test_command(body, client, ack, logger):
logger.info(body)
ack("I got it!")
res = client.dialog_open(
trigger_id=body["trigger_id"],
dialog={
"callback_id": "dialog-callback-id",
"title": "Request for New Project",
"submit_label": "Request",
"notify_on_cancel": True,
"state": "Limo",
"elements": [
{"type": "text",
"label": "Server Name",
"name": "server_name"
},
{
"type": "text",
"label": "Site Name",
"name": "site_name",
},
{
"label": "Project Name",
"name": "project_name",
"type": "text",
},
           {
                "label": "Project Owner ID",
                "name": "owner_id",
                "type": "text",
            },

        ],
    },
)
logger.debug(res)

##ack section ##
@app.action("dialog-callback-id")
def dialog_submission_or_cancellation(ack: Ack, body: dict):
if body["type"] == "dialog_cancellation":
# This can be sent only when notify_on_cancel is True
ack()
return
errors = []
submission = body["submission"]
print(submission["server_name"])

if submission["server_name"] != "production":
    errors = [
        {
            "name": "server_name",
            "error": "server , site , project ,owner must be valid ",
        }
    ]
if len(errors) > 0:
    # or ack({"errors": errors})
    ack(errors=errors)
else:
   ack(f"Your Project Request Submitted {submission}")

def main():
handler = SocketModeHandler(app, SLACK_APP_TOKEN)
handler.start()
if name == "main":
main()
`

@jambeshmpt

ack(f"Your Project Request Submitted {submission}")

This ack() method should not have any str argument. Like the original example does, ack() should work for you.

@jambeshmpt

ack(f"Your Project Request Submitted {submission}")

This ack() method should not have any str argument. Like the original example does, ack() should work for you.

Thanks  !! That worked .

Glad to hear that!


No string length check defined in Subset class so intval is used

https://github.com/HylianShield/validator/blob/master/src/HylianShield/Validator/String/Subset.php#L32
Needs:
    /**
     * The callable to return the length of the value.
     *
     * @var callable $lengthCheck
     */
    protected $lengthCheck = 'mb_strlen';

Closed by your pull request. Next time, please add: closes #issue


[feat]: Add an interactive terminal/shell to the UI

goal is to allow the user to run shell commands from the embassy dashboard. additional scoping needed to determine where to put this to limit users accidentally performing unwanted changes.

limit users accidentally performing unwanted changes.

sudo rm -rf /*

Haha xD
Seems we could limit this to just embassy-cli commands.
Or at least to the start9 user rather than root.
Depends on what the goal of this feature is. What would we like the user to be able to do from the UI?
Seems this was opened to replace the SSH over Tor feature request - when I opened that I was picturing full SSH access.
If we implement full SSH access, we will want this feature to be very hidden.

The below could be leveraged or looked into as a way to run this.
https://github.com/shellinabox/shellinabox
and
https://blog.desdelinux.net/en/accede-terminal-servidor-navegador-web/
This may not be a desirable solution to use, as the code is a bit dated, but it at least paints a picture of what I have in my head as to what is going on here.
A more recent solution:
https://github.com/foyzulkarim/terminal-in-browser


Program startup failed

PiP-Tool Version: 1.1.1
System: Win 7 64bit
Screenshots:

I see, to fix the issue #3, I used something only available on Windows 10. I will try to know if I can apply it for the previous version of Windows.

Setup failed.

@bdd786 What is your windows 10 version ?

Windows 10 Enterprise version
Bhavin
From: Lionel Jouin<EMAIL_ADDRESS>Sent: Wednesday, March 6, 2019, 3:21 PM
To: LionelJouin/PiP-Tool
Cc: bdd786; Mention
Subject: [LionelJouin/PiP-Tool] Program startup failed (#5)

@bdd786 https://github.com/bdd786 What is your windows 10 version ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LionelJouin/PiP-Tool/issues/5#issuecomment-470261466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFZ7wZ0uWSMg1p63LstnOVzecafCn1lks5vUCNVgaJpZM4YOYxs.

I meant in the version, not the edition. You can find this information in Settings -> System -> About. For example, mine is 1809.

See below

[image: image.png]
On Wed, Mar 6, 2019 at 3:46 PM Lionel Jouin<EMAIL_ADDRESS>wrote:

I meant in the version, not the edition. You can find this information in
Settings -> System -> About. For example, mine is 1809.
[image: alt text]
https://camo.githubusercontent.com/7ad6b46c15e29c1592beeb8ea4281c986614fa72/68747470733a2f2f692e696d6775722e636f6d2f3152364d4369722e706e67
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/LionelJouin/PiP-Tool/issues/5#issuecomment-470269836,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEFZ7zwRIXVefbbm9dVmWk2lJy3fC8_Mks5vUCklgaJpZM4YOYxs
.

Windows 7 x64, .NET 4.7.2, startapp failed
Prev. version (1.1) works just fine.

I fixed the issue with the version 1.1.2 but I had to removed the DPI support on Windows 7 since I haven't found an equivalent of GetDpiForMonitor.
https://github.com/LionelJouin/PiP-Tool/releases/tag/1.1.2


Compress lima-guestagent.Linux-{x86_64,aarch64}

To let Homebrew ignore "Binaries built for a non-native architecture" check.
See https://github.com/Homebrew/homebrew-core/pull/82723#issuecomment-893232417
==> brew audit lima --online --git --skip-style
==> FAILED
Error: 1 problem in 1 formula detected
Error: No such file or directory @ realpath_rec - /home/runner
lima:
  * Binaries built for a non-native architecture were installed into lima's prefix.
    The offending files are:
      /home/linuxbrew/.linuxbrew/Cellar/lima/0.6.0/share/lima/lima-guestagent.Linux-aarch64	(arm64)

DNM.
Let's see whether we can have check_binary_arches_allowlist soon https://github.com/Homebrew/brew/pull/11832

Btw aside from workarounding the homebrew issue, I think we can still consider merging this to save disk space slightly
$ ls -lh
total 26176
-rw-r--r--  1 suda  staff   6.2M  8 11 18:37 lima-guestagent.Linux-aarch64
-rw-r--r--  1 suda  staff   6.6M  8 11 18:37 lima-guestagent.Linux-x86_64
$ gzip -1 *
$ ls -lh
total 11200
-rw-r--r--  1 suda  staff   2.6M  8 11 18:37 lima-guestagent.Linux-aarch64.gz
-rw-r--r--  1 suda  staff   2.9M  8 11 18:37 lima-guestagent.Linux-x86_64.gz


Automatic Installer generation

I think one next step is to have the windows installers (possibly others) automatically generated for the release candidates.  I think we are a good chunk of the way there, but I think we need a few configurations and some testing.  Possibly something we can do with Azure as appveyor seems a little slow.

I'm already doing it on Travis and Appveyor. I can just add an extra step that builds the installer and we can push the final products to the releases page.
https://travis-ci.com/GMLC-TDC/helics-conda
https://ci.appveyor.com/project/kdheepak/helics-conda-0bk88

I think it is mostly a matter of making sure we have the correct configurations generated and making a decision on what those configurations should be, then we can make sure those configurations are used on the CI builds and uploaded as appropriate.
For Windows

MSVC 2017 x64 Release with C++ Shared Lib

MSVC 2017 x86 Release

MSVC 2017 x64 Debug

MSVC 2015 x64 Release

Some build with static system libraries included and just the C shared library and headers

#759 is a step in this direction

Additional tasks related to this for the next minor release:

[ ] macOS installer
[ ] macOS, Linux, and Windows shared library archives for x86 and x64

Possibly set up future nightly builds.


Decouple TemplateProcessorTest from RefasterTemplateProcessor

Ahead of

#57

I'd considered also changing the tests to no longer use files as in and output but text blocks, but figured we can discuss and pick that up separately.

Going to merge this one as I've only changes classes in src/test, such that I can build on this for a hopeful fix for the missing TemplateProcessor classpath entry.


build fails when inaccessible directory exists in $PREFIX_DIR

I encountered the following error when attempting to install ruby on our RHEL 6 server using a prefix directory:
find: `/swadm/lost+found': Permission denied

BUILD FAILED (Red Hat Enterprise LInux Server release 6.7 (Santiago) using ruby-build 20160130)

The /swadm/lost+found directory is owned by root and we are installing ruby using a different user, which is why the find command run by the fix_directory_permissions method is generating the error.  I will be submitting a pull request that addresses this error shortly.

3a10951711e213de2ee1c4e6996590f3a6c62044


Podcast refresh noticeably slow on lower-end devices.

Describe the bug
Refreshing large podcasts can be very slow.
To Reproduce
Steps to reproduce the behavior:

Refresh any podcast that contains a significant number of episodes.

Expected behavior
The refresh to not take so long.
Additional context
The issue is a result of all episodes in the feed being saved during a refresh, regardless of whether they have changed or not. This is causing unnecessary write overhead and is very noticeable on low end devices. This is a big issue when enabling background refresh for podcasts.
When saving an updated Feed, only new or changed episodes should be saved. Also need to check that expired episodes are removed.

Save routine has been improved to cut out unnecessary file writes for episodes that have not changed. Has noticeably improved the refresh time.


Config did not export an object @ 2.2

I am using webpack merge to do a smart dev or production config.
My start script looks like
  },
  "scripts": {
    "start": "webpack --env=production & node start.js",
    "dev": "webpack-dev-server --env=dev",
  },

and my webpack-config looks like this:
const webpack = require('webpack')
const ExtractTextPlugin = require('extract-text-webpack-plugin')
const CompressionPlugin = require('compression-webpack-plugin')
const webpackMerge = require('webpack-merge')

const baseConfig = function(env) {
  return {
    output: {
      path: '/public/',
      filename: 'index.js',
      publicPath: '/public/',
    },
    module: {
      rules: [
        {
          test: /\.js$/,
          exclude: /node_modules/,
          use: ['babel-loader'],
        },
        {
          test: /\.css$/,
          loader: ExtractTextPlugin.extract({
            fallbackLoader: "style-loader",
            loader: "css-loader",
            publicPath: "/public/",
          }),
        },
      ],
    },
    resolve: {
      extensions: ['.js', '.css'],
    },
    plugins: [
      new webpack.DefinePlugin({
        'process.env': { NODE_ENV: JSON.stringify(env) },
      }),
      new ExtractTextPlugin({
        filename: "bundle.css",
        disable: false,
        allChunks: true,
      }),
    ],
  }
}

module.exports = function(env) {
  return webpackMerge(baseConfig(env), env === 'dev' ? {
    devtool: 'cheap-module-source-map',
    entry: [
      'react-hot-loader/patch',
      'webpack-dev-server/client?http://localhost:8080',
      'webpack/hot/only-dev-server',
      './app/index.js',
    ],
    devServer: {
      hot: true,
      publicPath: '/public/',
      proxy: {
        "/api/**": "http://localhost:3333",
        "/auth/**": "http://localhost:3333",
      },
    },
    plugins: [
      new webpack.HotModuleReplacementPlugin(),
      new webpack.NamedModulesPlugin(),
    ],
  } : {
    devtool: 'inline-source-map',
    entry: [
      './app/index.js',
    ],
    plugins: [
      new webpack.optimize.UglifyJsPlugin({
        comments: false,
      }),
      new webpack.LoaderOptionsPlugin({
        minimize: true,
      }),
      new webpack.optimize.AggressiveMergingPlugin(),
      new CompressionPlugin({
        asset: "[path].gz[query]",
        algorithm: "gzip",
        test: /\.js$|\.css$|\.html$/,
        threshold: 10240,
        minRatio: 0.8,
      }),
    ],
  })
}

Webpack successfully compiles locally but when I attempt to deploy it to heroku, the output in papertrail is as seen below:
> webpack --env=production & node start.js
Config did not export an object.

I apologize if posting this here is not appropriate as it might not be an 'issue', but wanted to see if anyone else was experiencing it, and perhaps get some insights. I have already posted it on Stack Overflow @ http://stackoverflow.com/questions/41780259/webpack-config-did-not-export-an-object

Hi,
I wonder what's the difference between your local and Heroku setup. Please add Node/npm version for both too as that will help. Can you add your package.json too?
I think you could get that error if it's trying to run your configuration through webpack 1 at Heroku, but I'm not exactly sure how that could happen just yet without some additional information.

My entire package.json can be found here https://github.com/awitherow/aether/blob/master/package.json
and the whole project can be found https://github.com/awitherow/aether/
@bebraw thanks for pointing out the Node thing.
I just realized I am running node 7.2.1 locally but my engine for heroku is set to 6.2.0! Which is good because I am getting better errors now :)
Jan 21 06:45:14 aethernote app/web.1:  sh: 1: webpack: not found
Jan 21 06:45:14 aethernote app/web.1:  /app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180
Jan 21 06:45:14 aethernote app/web.1:            throw new ReferenceError(messages.get("pluginUnknown", plugin, loc, i, dirname));
Jan 21 06:45:14 aethernote app/web.1:            ^
Jan 21 06:45:14 aethernote app/web.1:  ReferenceError: Unknown plugin "transform-class-properties" specified in "/app/.babelrc" at 0, attempted to resolve relative to "/app"
Jan 21 06:45:14 aethernote app/web.1:      at /app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:180:17
Jan 21 06:45:14 aethernote app/web.1:      at Array.map (native)
Jan 21 06:45:14 aethernote app/web.1:      at Function.normalisePlugins (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:158:20)
Jan 21 06:45:14 aethernote app/web.1:      at OptionManager.mergeOptions (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:233:36)
Jan 21 06:45:14 aethernote app/web.1:      at OptionManager.init (/app/node_modules/babel-core/lib/transformation/file/options/option-manager.js:367:12)
Jan 21 06:45:14 aethernote app/web.1:      at compile (/app/node_modules/babel-register/lib/node.js:103:45)
Jan 21 06:45:14 aethernote app/web.1:      at loader (/app/node_modules/babel-register/lib/node.js:144:14)
Jan 21 06:45:14 aethernote app/web.1:      at Object.require.extensions.(anonymous function) [as .js] (/app/node_modules/babel-register/lib/node.js:154:7)
Jan 21 06:45:14 aethernote app/web.1:      at Module.load (module.js:488:32)
Jan 21 06:45:14 aethernote app/web.1:      at tryModuleLoad (module.js:447:12)

which has nothing to do with webpack, as it seems to more to have to do with the babel transformations :) I guess this can be closed?

@awitherow It's better to stick with Node 6 for now. Esp. webpack-dev-server has issues with 7. I would recommend using babel-core over babel. But yeah, it looks like a Babel issue now.


mini.pick: Cursor disappears when switching files using picker

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.pick
Description
Since this commit, the cursor disappears when switching from file a to file b using mini.pick.
I tested with an older commit, and the cursor does not disappear.
Neovim version
0.10.1
Steps to reproduce
Open neovim and open a file. Cursor is visible.
Now, use pick.files to open another file. Cursor disappears.
Expected behavior
Cursor does not disappear...;)
Actual behavior
Cursor disappears

Thanks for the issue!
I can not reproduce (because I of course tested this prior). I'd need to ask for more details of the setup and actual steps (is just :Pick files and <CR>?). For instance:

What is the value of guicursor option before and after?
What OS, terminal emulator?

Os: Arch linux
Terminal: Alacritty and tmux
The guicursor:
vim.opt.guicursor = ""

The guicursor:
vim.opt.guicursor = ""

This is the problem, as it should probably not be that way (it more or less means "disable cursor"). Is there a reason you use it this way (I presume from vim.cmd('set guicursor=')?

I'll look more closely on the weekend. In the meantime, having vim.o.guicursor = 'a:block' seems to give the same cursor styling effect but without disappearing cursor.

If I remember correctly:

I use zsh vim mode extensively. Somehow, terminal outside vim behaved differently than terminal inside vim.
I vaguely remember a Neovim issue where the terminal cursor was changed when closing Neovim.
I saw that ThePrimeagen uses this setting. It took some time getting used to the cursor always having the same shape. Now I like the consistency.

I'll look more closely on the weekend. In the meantime, having vim.o.guicursor = 'a:block' seems to give the same cursor styling effect but without disappearing cursor.

Thanks!

Regarding the Neovim issue: I think it was this one.

Regarding the Neovim issue: I think it was this one.

I think this was a suggestion to use set guicursor= inside autocommand for VimLeave. The cursor links to a FAQ entry which in fact suggests au VimLeave,VimSuspend * set guicursor=a:block-blinkon0.

With some dirty hack taken from 'folke/noice.nvim', this should now be resolved on latest main. But to reiterate, I don't think using vim.o.guicursor = '' as the main option value is a good idea to begin with.

Thanks!
As per your suggestion, I now use vim.o.guicursor = 'a:block'. I don't see any difference, and vim mode inside terminal is still working as before, so I will keep that setting.


Update awssdk:auth, awssdk:core, ... to 2.17.169

Updates

software.amazon.awssdk:auth
software.amazon.awssdk:core
software.amazon.awssdk:regions

from 2.17.160 to 2.17.169.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "software.amazon.awssdk" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #74.


Adapted make to use in BSD systems

Refs: #1289
FreeBSD
man make
-s	     Do	not echo any commands as they are executed.  Equivalent	to
	     specifying	`@' before each	command	line in	the makefile.

Linux
man make
-s, --silent, --quiet
Silent operation; do not print the commands as they are executed.

@andresgutierrez Could you please review?


Standard and C99 types handling in Pygments

(Original issue 335 created by delroth on 2008-06-09T18:14:40+00:00)
This patch adds two options to handle c99 and stdlib types for the C lexer. These types are colored by default and can be disabled by passing c99highlighting=False or stdlibhighlighting=False to the lexer options.

(Original issue was assigned to gbrandl)
(Original issue 335 last updated on 2008-06-10T20:22:56+00:00)
(Issue automaticaly closed due to status in Bitbucket: resolved)

(Original comment by mitsuhiko on 2008-06-10T20:22:56+00:00)
Patch applied in [c9add4c2f100].


Java -Added Date Guide

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Hi bomerzz,
Thank You for this PR. In the description, you mentioned you're adding a guide for Dates on Java. However, your article seems to be entirely about Strings, and the same article is already present in the guide on Strings. Perhaps you commited the wrong file in the PR?
I'm closing this PR for now, but feel free to create another one with the right article whenever you're ready!


fix: adds pyodbc output converter for DATETIMEOFFSET

Fixes #253
Refs:
https://github.com/mkleehammer/pyodbc/wiki/Using-an-Output-Converter-function
https://github.com/mkleehammer/pyodbc/issues/134#issuecomment-281739794

Updated with this PR - this fixes the failing tests.
https://github.com/baldwicc/dbt-sqlserver/pull/7

Done - saw this has v1.1.1 milestone so updated changelog.md accordingly


Add jpql case serializer

Motivation:

Explain why you're making this change and what problem you're trying to solve.

Modifications:
Implement JpqlCaseSerializer
Commit Convention Rule

Please commit your modification based by conventional commit
This commit convention is referred from angular convention

Commit type
Description

feat
New Feature

fix
Fix bug

docs
Documentation only changed

ci
Change CI configuration

refactor
Not a bug fix or add feature, just refactoring code

test
Add Test case or fix wrong test case

style
Only change the code style(ex. white-space, formatting)

chore
It refers to minor tasks such as library version upgrade, typo correction, etc.

If you want to add some more commit type please describe it on the Pull Request

Result:
Closes #. (If this resolves the issue.)

Describe the consequences that a user will face after this PR is merged.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.3 out of 4 committers have signed the CLA.:white_check_mark: jbl428:white_check_mark: cj848:white_check_mark: shouwn:x: seyoon.kimseyoon.kim seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


All CIS v2.0.0 scans fail on v1.21.3+k3s1

v2.6.0-rc7
Is this related to CIS itself?

Same problem with RC9.

Scan results are slightly different with Rancher 2.6.3-rc1.
Downstream K3s cluster v1.21.5.
CIS Benchmark v2.0.2

Reports are empty:

I am seeing something similar and I manually run the scan commands on RKE2 with good results (passing results) since RKE2 is hardened by default.
Rancher: v2.6.4
RKE2: v1.22.8+rke2r1
CIS Benchmark: v2.0.3

It almost seems like it is not able to scan the "master" nodes because worker only scans seem to pass and report just fine:


[BEAM-2500] Add S3 FileSystem to Java SDK

My first contribution, will submit ICLA later today.
Ran mvn clean verify against sdks/java/io only, because I'm currently in a place with limited power and bandwidth.
There is some technical discussion in the JIRA.
https://issues.apache.org/jira/browse/BEAM-2500
Please notice that there is one persistent thread pool, and that copy operations can create a new thread pool per copy. Happy to hear feedback and discuss.

Retest this please

Great work Jacob, The build did not pass for some simple errors on findbugs, you can validate this locally with mvn clean verify -Prelease.

R: @iemejia (I add myself more from a end-user validation point of view and some Beam IO experience).
R: @lukecwik (Sorry to bother you but since you implemented most of HDFS and know BeamFS really well you seemd to me like a perfect candidate, feel free to minus if you are busy and can't do the review).

I'll take a look.

I should ask, is an ICLA needed for a patch this size?

I believe so since your adding a whole feature.

Submitted ICLA to Apache.

FAILURE
--none--

FAILURE
--none--

FAILURE
--none--

FAILURE
--none--

FAILURE
--none--

FAILURE
--none--

FAILURE
--none--

SUCCESS
--none--

SUCCESS
--none--

FAILURE
--none--

FAILURE
--none--

SUCCESS
--none--

SUCCESS
--none--

FAILURE
--none--

SUCCESS
--none--

Thanks! Luke, could you do the next round of review?

TODO: describe testing as requested by Eugene

FAILURE
--none--

SUCCESS
--none--

SUCCESS
--none--

FAILURE
--none--

FAILURE
--none--

The code structure from GcsFileSystem is quite poor because it has evolved from GcsUtil which was created before Dataflow 1.0 release. During the migration to "file systems", there were plans to remove GcsUtil and clean up the implementation of GcsFileSystem but they were never acted upon.
I'll take another look now that a bunch of stuff has been moved around.

@lukecwik The current build failure is caused by the AWS update in Kinesis, shouldn't be hard to resolve. If you plan to review again in the next 24h then I'll hold off pushing more commits for the moment.

Yeah, I'm reviewing right now. Also long as you don't squash your commits adding changes won't complicate my review.

What you have done here is great, was wondering if you had time to follow up on the review comments?

Hey Luke, I got 90% done with your latest over the long weekend, should have time to wrap up tomorrow after work, so you should see something Wednesday morning.

There are a couple of TODOs remaining. Here are some notes from tonight:

rebased to master and squashed
WordCount works, reading from and writing to S3
need to do some bigger testing
haven't looked at coverage yet
Kinesis tests fail for me both before and after this PR, so I made a fix and we'll see what Jenkins does with it. If that doesn't work, AWS SDK version 1.11.24 is the last version that should pass without any change in Beam.
there are two open questions to @jkff , mentioned inline
tried to do more tonight, but fixing the content encoding bug turned out to be more complex than I anticipated.

Coverage notes:
S3FileSystem - 80% LOC
S3ResourceId - 93% LOC
missing: exception handling, copy(List, List), rename, matchNewResource
copy(List, List) and rename is two LOC: copy, delete
matchNewResource doesn't do a lot

Practical testing notes:
Wrote a TextIO.Read => TextIO.Write pipeline to test lots of files and data.
Used Dataflow runner, Oregon region
GS and S3 regions are both Oregon
Workers are n1-standard-4
Autoscaling enabled, 100 workers max
No compression
Pipeline 1: GS to S3
~3000 files read from GS
3095 files written to S3
1274848854 lines
368107865893 bytes
47 workers at peak
time 11m16s
Pipeline 2: GS to GS
same input as pipeline 1
same lines, same bytes
38 workers at peak
time 5m0s
Pipeline 3: S3 to GS
input is output of pipeline 1
3150 files written to GS
same lines, same bytes
38 workers at peak
time 5m14s

Luke, the AWS credentials solution you proposed, if I understand it correctly, doesn't work on Dataflow. DefaultAWSCredentialsProviderChain wants to get the credentials from one of the following (copy-paste from Slack):

environment variables (don't know how to set these on a Dataflow worker)
Java system properties (I haven't used this)
credentials file at ~/.aws/credentials (pretty sure the Beam SDK doesn't support this)

I'll do one more load test this morning, with gzip compression.

I just tried to run a pipeline that includes this package, but doesn't use it. Looks like the S3FileSystemRegistrar creates an instance of S3FileSystem even if I don't use it, which means the S3FileSystem constructor probably shouldn't create a thread pool or enforce flag requirements. Now the GcsUtil class makes sense.

Have the S3FileSystemRegistrar not return any filesystems to register if the required flags are missing. You can print a debug statement as to why S3 support is not being enabled.
Having GcsUtil created within PipelineOptions by GcsFileSystem has little to do with not starting threads or flag enforcement and has more to do with no one spending the time to get rid of GcsUtil and migrate it into GcsFilesystem.

The DefaultAWSCredentialsProviderChain is the best default to use for Apache Beam.
For Dataflow users wanting to access AWS services, they should really set one of the static credentials providers like:

ClasspathPropertiesFileCredentialsProvider
AWSStaticCredentialsProvider
or use one of the dynamic ones and set the correct properties.

It is important to document that users need to use a credentials provider that is compatible with the remote execution location and we should make sure serializing PipelineOptions with a few common credentials providers works.
Once we are using the portability framework then the user will be able to build a container containing any files (~/.aws/credentials), additional flags to the JVM (system properties), or additional processes AWS credentials provider.

We're probably close to done writing code, just this auth question remains, yes?
Is this what you have in mind when you say "they should really set one of the static credentials providers" ? I tried the following snippet, and it works with the DirectRunner, but fails with the DataflowRunner.
interface ExampleOptions extends PipelineOptions, S3Options {

    String getSourceS3Filename();
    void setSourceS3Filename(String value);

    String getDestinationS3FilenamePrefix();
    void setDestinationS3FilenamePrefix(String value);
  }

  public static void main(String[] args) {
    PipelineOptionsFactory.register(ExampleOptions.class);
    ExampleOptions options =
        PipelineOptionsFactory.fromArgs(args).create().as(ExampleOptions.class);
    AWSCredentials awsCredentials =
        new BasicAWSCredentials("test key", "test secret");
    options.setAwsCredentialsProvider(new AWSStaticCredentialsProvider(awsCredentials));
    Pipeline pipeline = Pipeline.create(options);

    pipeline.apply(TextIO.read().from(options.getSourceS3Filename()))
        .apply(TextIO.write().to(options.getDestinationS3FilenamePrefix()).withSuffix(".txt"));

    pipeline.run().waitUntilFinish();
  }

The Dataflow error:
com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain
        at com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:131)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.getCredentialsFromContext(AmazonHttpClient.java:1163)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.runBeforeRequestHandlers(AmazonHttpClient.java:762)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:724)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667)
        at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649)
        at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513)

You can check out the failing AWS client code here:
https://github.com/aws/aws-sdk-java/blob/7844c64cf248aed889811bf2e871ad6b276a89ca/aws-java-sdk-core/src/main/java/com/amazonaws/auth/AWSCredentialsProviderChain.java#L131
Because of this, I suspect that my snippet doesn't properly "set one of the static credential providers". Clearly the DirectRunner and DataflowRunner handle my example differently.
I'll try to reply promptly to this thread for the rest of the week. Hopefully we can resolve this last issue.

I made a small change to allow building with, but not using, the package. Tested by building with this package as a dependency, then reading and writing GCS without --awsRegion and without any valid AWS credentials present.

The reason why its not working is that the DirectRunner doesn't serialize/deserialize PipelineOptions so the @JsonIgnore doesn't come into effect on the getAwsCredentialsProvider. This is where my comment about being able to serialize PipelineOptions with a few well known CredentialsProviders would allow us to ship this across to the worker on runners with remote execution like Dataflow/Spark/Flink/...
Filed https://issues.apache.org/jira/browse/BEAM-3344 for DirectRunner to serialize/deserialize PipelineOptions before execution.

@jack749 Do you know how writing to multiple buckets in different regions can be configured? Details about the issue I'm running into: https://issues.apache.org/jira/browse/BEAM-11257#
What I'd like to do is something like this:
public void processElement(ProcessContext c) {

AwsOptions options = c.getPipelineOptions().as(AwsOptions.class);

...

options.setAwsCredentialsProvider(<bucket01_auth>);

options.setAwsRegion(<bucket01_region>);

...

ResourceId resourceId = FileSystems.matchNewResource(<bucket01_filename>, false);
try (WritableByteChannel out = FileSystems.create(resourceId, MimeTypes.TEXT))

{ out.write(contents); }
...

options.setAwsCredentialsProvider(<bucket02_auth>);

options.setAwsRegion(<bucket02_region>);

ResourceId resourceId = FileSystems.matchNewResource(<bucket02_filename>, false);
try (WritableByteChannel out = FileSystems.create(resourceId, MimeTypes.TEXT)) { out.write(contents); }

}

Solution seems to be to use
FileSystems.setDefaultPipelineOptions(options);
at runtime before using FileSystems.create(..)


fix ripleys being able to grab everything

About the PR

eugh
Media

i tested this for portals, it works for those.

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

fix: Ripleys can no longer grab walls, doors, and portals.

YEET


Make sure installation documentation mentions configuroing the backend configuration

https://github.com/wagtail/wagtail-vector-index/blob/main/docs/installation.md
I also wonder if numpy is a good default choice given that it's not production-ready. Maybe we should not allow the user to boot the site until this is configured (Django check framework).

I don't think it's unreasonable to default to the NumPyBackend so people can get up and running and experimenting quickly, and there's no reason why it can't be production ready, it's just that it might scale poorly in some situations - we might just need to be clearer about that.


Request to change checkbox of previous note instead of deleting

Hello,
I'm wondering if it would be possible to change the checkbox of a copied over task in the previous note to another symbol? In my implementation I have bullet journal style icons for 'migrated' tasks, which has an image for - [>]. I would like any - [ ] that gets imported from the old note to be changed to - [>]. Is that something you'd be open to?

I think this feature would mesh well with #25
I will mark this as a feature request and get to it next time I'm working on this code.
Thanks for the suggestion.

Thanks so much! I had the same problem with roll-over not working for my needs and am so glad to have found your implementation.


feat: Add jiro4989/ojosama

Added packages:

jiro4989/ojosama

Thank you for your contribution.

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.14.0


minLevel

Dear @johansatge ,
appreciated, very usefull plugin.
Do you plan to add a minLevel option to exclude the (redundant) title of the document, which is generally at the first level?
Best regards.

Hi @Ericno69 and @johansatge,
cool plugin. Such a parameter would really help and extend the current functionality in a very flexible way.
Beste Regards

Done in 1.1.0 thx @ras0q ❤