xfsprogs: 4.19 -> 5.10

Motivation for this change
xfsprogs was outdated by several years and does not appear to have an (active) maintainer.
Closes #107010
cc @TredwellGit @Mic92
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[x] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Seems like this should target staging?

ofborg says <500 rebuilds, so I guess it should be fine?

@TredwellGit we can also merge #107010 and I can rebase on that, but it should have a maintainer.

Let me add myself as a maintainer.

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

5 packages marked as broken and skipped:

bareos
gnome3.gnome-books
gnome3.gnome-documents
xmonad_log_applet
xmonad_log_applet_gnome3

2 packages failed to build:

samba4Full
scylladb

122 packages built:

adapta-gtk-theme
almanah
atom
atom-beta
bubblemail
calls
cantata
ceph
ceph-client
charliecloud
chrome-gnome-shell
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
clementine
clementineUnfree
disnix
disnixos
docker
docker-gc
docker_18_09
dropbox-cli
dydisnix
dysnomia
elementary-planner
empathy
enlightenment.enlightenment
evolution-data-server (evolution_data_server)
evolution-ews
far2l
feedreader
folks
gfbgraph
glusterfs
gnome-multi-writer
gnome-online-accounts
gnome-photos
gnome-recipes
gnome2.gvfs
gnome3.bijiben
gnome3.cheese
gnome3.evolution
gnome3.file-roller
gnome3.geary
gnome3.gnome-applets
gnome3.gnome-boxes
gnome3.gnome-calendar
gnome3.gnome-contacts
gnome3.gnome-control-center
gnome3.gnome-disk-utility
gnome3.gnome-flashback
gnome3.gnome-initial-setup
gnome3.gnome-maps
gnome3.gnome-music
gnome3.gnome-online-miners
gnome3.gnome-panel
gnome3.gnome-session
gnome3.gnome-shell
gnome3.gnome-software
gnome3.gnome-terminal
gnome3.gnome-todo
gnome3.gnome-tweak-tool
gnome3.gnome-user-share
gnome3.grilo-plugins
gnome3.gvfs
gnome3.libgdata
gnome3.libzapojit
gnome3.nautilus
gnome3.nautilus-python
gnome3.pomodoro
gnome3.shotwell
gnome3.totem
gnome3.tracker-miners
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
hal-flash
libceph
libguestfs
libguestfs-with-appliance
libinih
libvmi
libxfs
mailnagWithPlugins
mate.mate-utils
nfs-ganesha
out-of-tree
pantheon.elementary-calendar
pantheon.elementary-greeter
pantheon.elementary-session-settings
pantheon.extra-elementary-contracts
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-with-indicators
pipework
psensor
python37Packages.guestfs
python37Packages.jupyter-repo2docker
python38Packages.guestfs
python38Packages.jupyter-repo2docker
python39Packages.guestfs
python39Packages.jupyter-repo2docker
qemu_xen (qemu_xen_4_10)
qubes-core-vchan-xen
rabbitvcs
rapid-photo-downloader
spaceFM
udiskie
udisks
usermount
vagrant
vifm-full
xen
xen-slim
xfce.gigolo
xfce.gvfs
xfce.thunar (xfce.thunar-bare)
xfce.thunar-archive-plugin
xfce.thunar-dropbox-plugin
xfce.xfdesktop
xfsprogs
xfstests

Okay, please merge https://github.com/NixOS/nixpkgs/pull/107010 then rebase.

@TredwellGit  done
@lovesegfault I'll see if I can figure out what's happening with samba4Full (and scylladb). Are they actually working on master?

@TredwellGit done
@lovesegfault I'll see if I can figure out what's happening with samba4Full (and scylladb). Are they actually working on master?

Let me check

@TredwellGit done
@lovesegfault I'll see if I can figure out what's happening with samba4Full (and scylladb). Are they actually working on master?

Let me check

Both are broken in master.

@TredwellGit done
@lovesegfault I'll see if I can figure out what's happening with samba4Full (and scylladb). Are they actually working on master?

Let me check

Both are broken in master.

That's good. I mean, it isn't, but that means that this PR is not at fault.
I'll leave this open, in case anyone wants to review it or has any objections, e.g. if we should ship a newer xfsprogs than our current default kernel release or something like that.
In case no-one requests any changes, I'll merge this in 7 days (in my timezone), so on 2021-01-02. Feel free to merge it before that, but seeing as this hasn't been updated since December of 2018, there's probably no need to rush.

After asking upstream, I think we should add a release notes entry to this, which I will write and push shortly.

After asking upstream, I think we should add a release notes entry to this, which I will write and push shortly.

@ofborg eval

@ofborg eval

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107597 run on x86_64-linux 1

3 packages marked as broken and skipped:

gnome3.gnome-books
gnome3.gnome-documents
xmonad_log_applet

2 packages blacklisted:

tests.nixos-functions.nixos-test
tests.nixos-functions.nixosTest-test

117 packages built:

adapta-gtk-theme
almanah
atom
atom-beta
bubblemail
calls
cantata
charliecloud
chrome-gnome-shell
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
clementine
clementineUnfree
disnix
disnixos
docker (docker-edge ,docker_19_03)
docker-gc
docker_18_09
dropbox-cli
dydisnix
dysnomia
elementary-planner
empathy (gnome3.empathy)
enlightenment.enlightenment
evolution-data-server (gnome3.evolution-data-server ,gnome3.evolution_data_server)
evolution-ews
far2l
feedreader
folks (gnome3.folks)
gfbgraph (gnome3.gfbgraph)
glusterfs
gnome-multi-writer
gnome-online-accounts (gnome3.gnome-online-accounts ,gnome3.gnome_online_accounts)
gnome-photos (gnome3.gnome-photos)
gnome-recipes
gvfs (gnome2.gvfs)
gnome3.bijiben (gnome3.gnome-notes)
gnome3.cheese
gnome3.evolution
gnome3.file-roller
gnome3.geary
gnome3.gnome-applets
gnome3.gnome-boxes
gnome3.gnome-calendar
gnome3.gnome-contacts
gnome3.gnome-control-center (gnome3.gnome_control_center)
gnome3.gnome-disk-utility
gnome3.gnome-flashback
gnome3.gnome-initial-setup
gnome3.gnome-maps
gnome3.gnome-music
gnome3.gnome-online-miners
gnome3.gnome-panel
gnome3.gnome-session (gnome3.gnome_session)
gnome3.gnome-shell (gnome3.gnome_shell)
gnome3.gnome-software
gnome3.gnome-terminal (gnome3.gnome_terminal)
gnome3.gnome-todo
gnome3.gnome-tweaks (gnome3.gnome-tweak-tool)
gnome3.gnome-user-share
grilo-plugins (gnome3.grilo-plugins)
gnome3.gvfs
libgdata (gnome3.libgdata)
libzapojit (gnome3.libzapojit)
gnome3.nautilus
gnome3.nautilus-python
gnome3.pomodoro
shotwell (gnome3.shotwell)
gnome3.totem
tracker-miners (gnome3.tracker-miners)
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
hal-flash
libguestfs
libvmi
libxfs
mailnagWithPlugins
mate.mate-utils
nfs-ganesha
out-of-tree
pantheon.elementary-calendar
pantheon.elementary-greeter
pantheon.elementary-session-settings
pantheon.extra-elementary-contracts
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-with-indicators
pipework
psensor
python37Packages.guestfs
python37Packages.jupyter-repo2docker
python38Packages.guestfs
python38Packages.jupyter-repo2docker
python39Packages.guestfs
python39Packages.jupyter-repo2docker
qemu_xen (qemu_xen_4_10)
qubes-core-vchan-xen
rabbitvcs
rapid-photo-downloader
spaceFM
udiskie
udisks (udisks2)
usermount
vagrant
vifm-full
xen (xenPackages.xen-vanilla ,xenPackages.xen_4_10-vanilla ,xen_4_10)
xen-slim (xenPackages.xen-slim ,xenPackages.xen_4_10-slim ,xen_4_10-slim)
xfce.gigolo
xfce.gvfs
xfce.thunar (xfce.thunar-bare ,xfce.thunar-build ,xfce.thunarx-2-dev)
xfce.thunar-archive-plugin
xfce.thunar-dropbox-plugin
xfce.xfdesktop
xfsprogs
xfstests

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:
bubblemail:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

mailnagWithPlugins:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python37Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python38Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python39Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

This is a semi-automatic executed nixpkgs-review which does not build all packages (e.g. lumo, tensorflow or pytorch)
If you find some bugs or got suggestions for further things to search or run please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 107597 run on x86_64-linux 1

3 packages marked as broken and skipped:

gnome3.gnome-books
gnome3.gnome-documents
xmonad_log_applet

2 packages blacklisted:

tests.nixos-functions.nixos-test
tests.nixos-functions.nixosTest-test

117 packages built:

adapta-gtk-theme
almanah
atom
atom-beta
bubblemail
calls
cantata
charliecloud
chrome-gnome-shell
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
clementine
clementineUnfree
disnix
disnixos
docker (docker-edge ,docker_19_03)
docker-gc
docker_18_09
dropbox-cli
dydisnix
dysnomia
elementary-planner
empathy (gnome3.empathy)
enlightenment.enlightenment
evolution-data-server (gnome3.evolution-data-server ,gnome3.evolution_data_server)
evolution-ews
far2l
feedreader
folks (gnome3.folks)
gfbgraph (gnome3.gfbgraph)
glusterfs
gnome-multi-writer
gnome-online-accounts (gnome3.gnome-online-accounts ,gnome3.gnome_online_accounts)
gnome-photos (gnome3.gnome-photos)
gnome-recipes
gvfs (gnome2.gvfs)
gnome3.bijiben (gnome3.gnome-notes)
gnome3.cheese
gnome3.evolution
gnome3.file-roller
gnome3.geary
gnome3.gnome-applets
gnome3.gnome-boxes
gnome3.gnome-calendar
gnome3.gnome-contacts
gnome3.gnome-control-center (gnome3.gnome_control_center)
gnome3.gnome-disk-utility
gnome3.gnome-flashback
gnome3.gnome-initial-setup
gnome3.gnome-maps
gnome3.gnome-music
gnome3.gnome-online-miners
gnome3.gnome-panel
gnome3.gnome-session (gnome3.gnome_session)
gnome3.gnome-shell (gnome3.gnome_shell)
gnome3.gnome-software
gnome3.gnome-terminal (gnome3.gnome_terminal)
gnome3.gnome-todo
gnome3.gnome-tweaks (gnome3.gnome-tweak-tool)
gnome3.gnome-user-share
grilo-plugins (gnome3.grilo-plugins)
gnome3.gvfs
libgdata (gnome3.libgdata)
libzapojit (gnome3.libzapojit)
gnome3.nautilus
gnome3.nautilus-python
gnome3.pomodoro
shotwell (gnome3.shotwell)
gnome3.totem
tracker-miners (gnome3.tracker-miners)
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
hal-flash
libguestfs
libvmi
libxfs
mailnagWithPlugins
mate.mate-utils
nfs-ganesha
out-of-tree
pantheon.elementary-calendar
pantheon.elementary-greeter
pantheon.elementary-session-settings
pantheon.extra-elementary-contracts
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-with-indicators
pipework
psensor
python37Packages.guestfs
python37Packages.jupyter-repo2docker
python38Packages.guestfs
python38Packages.jupyter-repo2docker
python39Packages.guestfs
python39Packages.jupyter-repo2docker
qemu_xen (qemu_xen_4_10)
qubes-core-vchan-xen
rabbitvcs
rapid-photo-downloader
spaceFM
udiskie
udisks (udisks2)
usermount
vagrant
vifm-full
xen (xenPackages.xen-vanilla ,xenPackages.xen_4_10-vanilla ,xen_4_10)
xen-slim (xenPackages.xen-slim ,xenPackages.xen_4_10-slim ,xen_4_10-slim)
xfce.gigolo
xfce.gvfs
xfce.thunar (xfce.thunar-bare ,xfce.thunar-build ,xfce.thunarx-2-dev)
xfce.thunar-archive-plugin
xfce.thunar-dropbox-plugin
xfce.xfdesktop
xfsprogs
xfstests

The following issues got detected with the above build packages.
Please fix at least the ones listed with your changed packages:
bubblemail:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

mailnagWithPlugins:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python37Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python38Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.

python39Packages.guestfs:

Zero tests run by pytest got detected: 'Ran 0 tests in 0.000s'
You have the following options to fix this:

Tell pytest(CheckHook) where to find the tests included in the package
Check if the GitHub Repo contains tests but they are not shipped with Pypi. If so please switch to fetchFromGitHub.
If the Packages does not contain any tests add 'doCheck = false;'and apythonImportsCheck`.


Add Novelsemperor

Source name
Novelsemperor
Source link
Novelsemperor.net
Language
English
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

Duplicate of #931


Default grouping in ui

Show alert groups from the alertmanager config by default and hide the custom grouping behind the checkbox.

If customGrouping is present in the url, then fetch alerts from the /alerts endpoint and group on the frontend
Otherwise (this is now the default) show alert groups from the /alerts/groups endpoint

closes #868

@stuartnelson3 I'm not sure why the circle ci tests are failing.

Not sure, will take a look at it soon (probably Monday)
thanks for doing this!

@beorn7 does it make you happy? :D

UI-wise, this looks good to me. Thank you very much. I haven't looked at the code.
One feature request (which might or might not already work) is to be able to deep-link one group (with the idea to link back to that group from a notification rather than to all alerts of the receiver, as we do it now). If that's not already possible, it could also be added in a later PR (perhaps backend changes are necessary). Just saying it so that we keep it in mind.

One feature request (which might or might not already work) is to be able to deep-link one group (with the idea to link back to that group from a notification rather than to all alerts of the receiver, as we do it now). If that's not already possible, it could also be added in a later PR (perhaps backend changes are necessary). Just saying it so that we keep it in mind.

Yeah, we should be able to add the alert groups fingerprint to the response and "link" to it that way. There would be a few backend changes, nothing major, but enough to warrant a new pr. thanks for the reminder!


@index doesn't work

While we can use {{@index}} on current Meteor version, but when I use this token with jade, it doesn't work.

I've just discovered exactly the same issue.

Same here.

+1

any info update about this?

This is solved in version 0.5.4 of dalgard:jade. Check out the readme for more info about that package's relationship to this one.


Revert "Fixing referential integrity"

This reverts commit f27d20f48f60b3a4421e3676f32a8686bca8ff9a.
This commit introduced a bug that can be see in in Issue https://github.com/airbnb/airflow/issues/27
The bug happens when the conn_id is not passed to the back-end
database.
I'm not sure of the original reason for the change, so there may be a subsequent fix that needs to happen, but this revert appears to fix functionality with the web interface.

There's a little bit more to this. We have this weird use case where I want a foreign key to a non unique field because we allow for non-unique conn_id as documented here: http://pythonhosted.org/airflow/concepts.html#connections
"""
Many connections with the same conn_id can be defined and when that is the case, and when the hooks uses the get_connection method from BaseHook, Airflow will choose one connection randomly, allowing for some basic load balancing and some fault tolerance when used in conjunction with retries.
"""
And somehow MySQL doesn't like FK to a non-unique field. The reason I set the FK is only to get a free dropdown in the Chart edit form (Flask Admin takes care of that), which I think I can achieve with a widget of sorts.

https://github.com/airbnb/airflow/pull/35 addresses this

Thanks for pointing out the issue!

Nice little hacky load balancing. I love it. I also found it failed with sqlite and pg. What seemed weird to me was that the conn_id was being passed as None and then the integrity check was complaining about a NOT NULL constraint not being met --- so it wasn't a non-unique constraint failure.


Remove sssom dependency

sssom is installed by oaklib and pinning it here is counterproductive.

sssom 0.4.2 breaks tests


Remote Control Options has not been covered

I see in this article which is about "Software Center user guide" remote control option is not covered. Under Options tab, just after Computer Maintenance option, we have Remote Control option as well. Although an end user cannot change any of the options under Remote Control, but it's good if you cover them.
Thanks,
Prajwal Desai
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 67a999a9-9597-9dcf-bd61-c8320b8a1fae
Version Independent ID: d99205df-c3d9-f101-13fc-bf7988848190
Content: Software Center user guide - Configuration Manager
Content Source: sccm/core/understand/software-center.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @PrajwalDesai for the feedback, agreed.

Thanks to @jpcast88 for contributing content for this issue, which is why it closed. The changes will publish live tomorrow around 11:00 Pacific time.


feat(frontend): convert max button update

Motivation
In this PR, I'm updating the max button behavior in the Conversion flow - it is now working similar to the ETH send flow, where it considers the fee and also updates input value automatically if fees got changed after the max button was clicked. Also, according the UX team suggestion, we need to display "Calculating..." label until all fees are known. The tests are updated accordingly.
Total fee is not available:

Total fee is available:

@peterpeterparker I added screenshots to the PR description.


[Event Request] Page 5600 Fixed Asset Card - OnAfterLoadDepreciationBooks

Hi,
Please, add a new event in page 5600 Fixed Asset Card for code intervention after the loading of the global depreciation book.
For us, the customization is needed to set the default visualization of the page as "not simple", but it can be useful also with other parameters of personalization.

Best regards,
Luca Martinengo

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Add InputStream Support for Client Certificate Credential + Fix 403 Edge case response for IMDS

Enables users to pass in InputStream for the client certificate in client cert cred.
Fixes Docker 403 edge case response and throws CUE in that case.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-identity


Replace State module by Link

Motivation
For the user, Ui, application and Link are the relevant Apis for construction. State is never constructed, and only stored in an application as a Url. As any Url is a valid State, we do a type alias.
Link.applyTo : State -> Link -> State

instead of
State.next : Link -> State -> State

Goal
Going with #29, State should not be a module because we don't treat it as a permanent data type. Instead, it is a collection of functions that map to and from the Url.
Situation now (Sept 5, 2023)
What does the Url map to and from?

Link
String
Query
Assignment
Path
Flag
Fragment

Here are all Url-centric functions from the current State module.
I excluded the Link-centric functions.
Create

fromString : String -> Maybe State

Map

next : Link -> State -> State
setPath : Path -> State -> State
setFragment : Fragment -> State -> State

type UrlCmd
= Set Assignment
| Add Assignment
| Clear String
- [integrateAssignment](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#integrateAssignment) :
[UrlCmd](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#UrlCmd) -> State -> State
- [addAssignment](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#addAssignment) : String -> String -> State -> State
- [removeAssignments](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#removeAssignments) : List String -> State -> State
- [toggleFlag](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#toggleFlag) : Flag -> State -> State
- [turnOnFlag](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#turnOnFlag) : Flag -> State -> State

## Query

- [hasFlag](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#hasFlag) : Flag -> State -> Bool

## Deconstruct

- [getLocation](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#getLocation) : State -> ( Maybe Path, Fragment )
- [getFragment](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#getFragment) : State -> Fragment
- [getPath](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#getPath) : State -> Path
- [toString](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#toString) : State -> String
- [queryParseLocation](http://localhost:8000/packages/upsiflu/restrictive/0.5.0/Restrictive-State#queryParseLocation) : String -> ( Maybe Path, Fragment )


Standard java lib can't dependence on "relifecyle"  module

apply plugin: 'java' is used in  "relifecyle"  module  . but my standard java lib module in Android Studio can't dependence on it

I don't understand the problem. Could you elaborate or post some code?

@dlew Sorry for my poor English !  There is a java module which applies plugin: 'java'  in AndroidStudio . When I add compile 'com.trello.rxlifecycle2:rxlifecycle:2.0.1' to it , gradle dependencies go wrong ! I don't know why , because rxlifecycle is also a java module too !

Chances are you're dependencies are misconfigured in some way. I still don't exactly understand what's going on, so I am going to need a reproduction of the issue.

@dlew I forgot 'com.google.code.findbugs:jsr305:3.0.1' . Well , please close this issuse


Env setup + code struct

I create a env.yaml file for easy env setup, and a folder /code for later dev.

Looks good!


[Bug]: checking for invalid date

Version
29.2.1
Steps to reproduce

Clone my repo at https://github.com/demensky/jest-invalid-date-bug
npm install
npm test
You should see 1 failed

Expected behavior
1 passed
Actual behavior
    Expected: Date { NaN }
    Received: serializes to the same string

1 failed
Additional context
No response
Environment
System:
    OS: macOS 12.6
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 18.10.0 - /usr/local/bin/node
    Yarn: 1.22.18 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - /usr/local/bin/npm
  npmPackages:
    jest: ^29.2.1 => 29.2.1

wanna send a PR? 🙂

@SimenB
I checked the equals->eq method under expect-utils->jasmineUtils.ts  it has switch with below case for date,
    case '[object Date]':
      // Coerce dates to numeric primitive values. Dates are compared by their
      // millisecond representations. Note that invalid dates with millisecond representations
      // of `NaN` are not equivalent.
      return +a == +b;

Note that invalid dates with millisecond representations of NaN are not equivalent.
Looking at this isn't the behaviour expected.

wanna send a PR? 🙂

I made this fix, if you allow me, I can send the PR.
The problem was exactly where @Rohitbels mentioned.

This comparison (+a == +b) in file /expect-utils->jasmineUtils.ts .. Will never return true, as the value is always a non-numeric string. This value is converted "toISOString" in the file /pretty-format/src/index.ts


feat: add ValidateFailed error

What type of PR is this?
Add ValidateFailed error

What this PR does / why we need it:
It can provide more user-friendly error prompts when importing workflow from git fails, prompting users to check for syntax errors in their workflow

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Add shapes plugin

~This PR makes use of ign-gazebo#95 so that PR will need to be merged before this one (it doesn't have to be, but I thought a separate PR for that functionality would be better for visibility and documentation purposes.~
There are a few things I made "prototypes" of that I would like to have looked and discussed for improvement:

The unused entity id generation in UniqueId()
How should the hovered mouse position be stored for best scalability and access for future users of the value
Should the code for creating a model from the sdf string be moved to a separate function?
Is the current location of HandleModelPlacement() good/could there be a better way to handle the mouse events here?

~There's currently a bug with this addition messing with the button pressing functionalities - I'll take a closer look at this soon~
Resolves #81

Demo:

I noticed this issue when spawning entities from below the ground. The spawned pose is slightly offset from the preview pose at click time:

Fixed in dd864dd

Ready for another iteration


Docker automatic publish on GH release

This leverage the release event to trigger the publish on dockerhub.
Then  ${{ github.ref_name }} contains the name of the version (the tag name).
Every time we create a new label with a version and we move latest

Can you duplicate the workflow have the one running for main tag a development build on Docker Hub?

Done @mcollina


Add Course Link for Go

Added a link for a basic course in Go programming language.

Hi @S2606, can you check guideline for adding course (Ref: Android)

@rathodchintan this is not an issue, we will improve formatting later on. If this is coming more often from contributors then that's an issue!
@S2606 please follow guidelines/formatting next contributions onwards. Thanks for your current contribution, looking forward for more!

@PareshMayani Ok.. I will deprioritize formatting.

@PareshMayani Thank you and I shall take care of it next time.


CCAP 374 Create transmission table

🔗 Jira ticket
https://codeforamerica.atlassian.net/browse/CCAP-374?atlOrigin=eyJpIjoiOTQwYzg0ZGMxY2Y3NGUxNzhmZWE1MTYyYzJkODhiYTYiLCJwIjoiaiJ9
✍ Description
Adds a transmissions table to track transmission of Application PDFs and Uploaded Documents for a given Submission.
Adds enums for TransmissionStatus and TransmissionType which will be used later when saving new transmissions in a separate ticket.

To test the migration:

Check out main
Remove all user files from your local user_files table
Remove all submissions from your local submissions table
With a clean user_files and submissions table - run through the application a few times. Once with 2 or 3 uploaded documents, once with no uploaded documents, and once without reaching the submission screen.
Check out this branch and restart the app so the migration runs
When the migration runs, refresh your local DB setup and you should now see the transmissions table
You should see one transmission for each completed submissions application PDF and one transmission for each uploaded document related to a submission.
You should not see any transmission for submissions that were not complete (have a null submitted at)

Tried to run the migration and ran into some issues:
SQL State  : 42704
Error Code : 0
Message    : ERROR: language "plpgsql" does not exist
  Hint: Use CREATE EXTENSION to load the language into the database.
Location   : db/migration/V2<IP_ADDRESS>.47.41__Add_transmissions_table.sql<EMAIL_ADDRESS>Line       : 1
Statement  : DO

One thing I just thought of, @spokenbird : if we merge this in now, and it gets deployed to Staging and then Prod... we'll mark all the existing Submissions as having been transmitted, etc. But we'll still have more Submissions over the next N weeks until we're actually writing to the Transmissions table, right?
It seems like we need, in parallel to this/at the same time, new code to also properly write to the Transmissions table for all new Submissions today? Am I missing something obvious here?

One thing I just thought of, @spokenbird : if we merge this in now, and it gets deployed to Staging and then Prod... we'll mark all the existing Submissions as having been transmitted, etc. But we'll still have more Submissions over the next N weeks until we're actually writing to the Transmissions table, right?
It seems like we need, in parallel to this/at the same time, new code to also properly write to the Transmissions table for all new Submissions today? Am I missing something obvious here?

@cram-cfa it's a good point, maybe we do the work for this Jira ticket:
https://github.com/codeforamerica/il-gcc-form-flow/pull/631#issuecomment-2374193362
In this branch and then merge when it's all ready?

Tried to run the migration and ran into some issues:
SQL State  : 42704
Error Code : 0
Message    : ERROR: language "plpgsql" does not exist
  Hint: Use CREATE EXTENSION to load the language into the database.
Location   : db/migration/V2<IP_ADDRESS>.47.41__Add_transmissions_table.sql<EMAIL_ADDRESS>Line       : 1
Statement  : DO

but then running this command set the plpgsql: CREATE EXTENSION IF NOT EXISTS plpgsql;

@analoo @enyia21 confused why Chibuisi had no issues but Ana did. @analoo do you have psql installed locally?


Consider what best to use instead of CF task scheduler in case of standalone deployment

Not urgent, and not strictly necessary because any built-in scheduling system such as cron could be used to just hit the schedule endpoint, like the CF scheduler does. But making an issue for it anyway, to decide if something more complex/integrated is worth the hassle.

Moving this into #10


[WIP] Bump deps

rebar 2 on CI fails with something like:
Pulling syslog from {git,"https://github.com/Vagabond/erlang-syslog.git",

                         {ref,"0e4f0e95c361af298c5d1d17ceccfa831efc036d"}}

Cloning into 'syslog'...

ERROR: 'get-deps' failed while processing /home/travis/build/lucafavatella/lager_syslog: {'EXIT',{badarg,[{io_lib,format,

                         ["git checkout -q ~s",

                          [{ref,"0e4f0e95c361af298c5d1d17ceccfa831efc036d"}]],

                         [{file,"io_lib.erl"},{line,168}]},

                 {rebar_deps,download_source,2,[]},

                 {rebar_deps,use_source,3,[]},

                 {rebar_deps,'-get-deps/2-fun-0-',2,[]},

                 {lists,foldl,3,[{file,"lists.erl"},{line,1263}]},

                 {rebar_deps,'get-deps',2,[]},

                 {rebar_core,run_modules,4,[]},

                 {rebar_core,execute,6,[]}]}}

Not sure syslog dep supports rebar 2 any longer - maybe it is supported on a best effort basis and not tested on CI.

Apparently the problem is not the syslog dep but the way the syslog dep is expressed. As I attempted to refer to specific commit, the syntax is incompatible between rebar3 and 2:
rebar 2 https://github.com/rebar/rebar/wiki/Dependency-management#example
    % {mochiweb, "2.3.2", {git, "https://github.com/mochi/mochiweb.git", "15bc558d8222b011e2588efbd86c01d68ad73e60"},

rebar3 http://www.rebar3.org/docs/dependencies#section-declaring-dependencies
requires {ref, _} tuple around commit string.

I expect CI tests to pass for both rebar 2 and 3 now. Once syslog is tagged (see also https://github.com/basho/lager_syslog/issues/29#issuecomment-292902743) the rebar 2 sed hack in the CI script can be removed.


feat: add syntax style options

This adds some style options, making the use of bold and italic text configurable for code syntax. Though I don't love some of the names I came up with for the additional options; I'm open to alternatives that are shorter and/or more descriptive.
Closes #176

I appreciate your efforts, but I am not willing to merge this. syntax styles are very loose and ever-growing between tree sitter and semantic tokens. Users have the possibility to customise everything at will via the overrides option.

That's understandable. I guess my confusion is, why offer only some configurable style options? My initial impression was that the default style options presented to me were comprehensive, that no other italic or bold styles were applied beyond that. I was  frustrated to learn that wasn't the case. I've since become content with the DIY nature of customizing those styles with overrides, but any folks that don't know how might experience a similar frustration at not being able to customize all of the styled syntax.
I guess my point is that having no style options may set better expectations than having some style options.


Poor performance of <LineChart.Dot hasPulse /> when there are 200+ data points

Description
When there are 200+ data points and a single <LineChart.Dot hasPulse />, there's a very noticeable performance degradation and scrolling becomes laggy. This is the animation causing the performance degradation.
Tested on latest release (2.5.1).
Screen Capture
Here's an example of 289 data points and one LineChart.Dot with and without hasPulse.

hasPulse={false}
hasPulse={true}

Closed by #177


Aggregation not worked?

i have following go-carbon.conf

[common]
user = "monitor"
logfile = "/var/log/go-carbon/go-carbon.log"
log-level = "info"
graph-prefix = "carbon.agents.{host}."
max-cpu = 8
metric-interval = "1m0s"

[whisper]
data-dir = "/opt/graphite/storage/whisper/"
schemas-file = "/opt/graphite/conf/storage-schemas.conf"
aggregation-file = "/opt/graphite/conf/storage-aggregation.conf"
workers = 8
max-updates-per-second = 0
sparse-create = true
enabled = true

[cache]
max-size = 1000000
input-buffer = 1000000

[udp]
listen = "<IP_ADDRESS>:2013"
enabled = true
log-incomplete = false

[tcp]
listen = "<IP_ADDRESS>:2013"
enabled = true
log-incomplete = true

[pickle]
listen = "<IP_ADDRESS>:2014"
max-message-size = 67108864
enabled = true

[carbonlink]
listen = "<IP_ADDRESS>:7002"
enabled = true
read-timeout = "30s"
query-timeout = "100ms"

[pprof]
listen = "localhost:7007"
enabled = false

and following aggregation rules

pinba.total.traffic_per_sec (60) = sum pinba.<host>.<server>.<script>.traffic_per_sec
pinba.total.req_count (60) = sum pinba.<host>.<server>.<script>.req_count

pinba.total.req_50_percentile (60) = max pinba.*.*.*.req_50_percentile
pinba.total.req_90_percentile (60) = max pinba.*.*.*.req_90_percentile
pinba.total.req_95_percentile (60) = max pinba.*.*.*.req_95_percentile
pinba.total.req_98_percentile (60) = max pinba.*.*.*.req_98_percentile

pinba.total.error_count   (60) = sum pinba.*.*.*.error_count
pinba.total.error_percent (60) = avg pinba.*.*.*.error_percent

pinba.total.tag_by_req (60) = sum pinba.*.*.*.*.*.tag_by_req_avg
pinba.total.tag_req_percent (60) = avg pinba.*.*.*.*.*.tag_req_percent

pinba.total.req_less_02s (60) = sum pinba.*.*.*.req_less_02s
pinba.total.req_02s_05s (60) = sum pinba.*.*.*.req_02s_05s
pinba.total.req_05s_1s (60) = sum pinba.*.*.*.req_05s_1s
pinba.total.req_1s_2s (60) = sum pinba.*.*.*.req_1s_2s
pinba.total.req_more_2s (60) = sum pinba.*.*.*.req_more_2s

pinba.total.tag_less_01s (60) = sum pinba.*.*.*.*.*.tag_less_01s
pinba.total.tag_01s_02s (60) = sum pinba.*.*.*.*.*.tag_01s_02s
pinba.total.tag_02s_05s (60) = sum pinba.*.*.*.*.*.tag_02s_05s
pinba.total.tag_05s_1s (60) = sum pinba.*.*.*.*.*.tag_05s_1s
pinba.total.tag_more_1s (60) = sum pinba.*.*.*.*.*.tag_more_1s

pinba.total.tag_50_percentile (60) = max pinba.*.*.*.*.*.tag_50_percentile
pinba.total.tag_90_percentile (60) = max pinba.*.*.*.*.*.tag_90_percentile
pinba.total.tag_95_percentile (60) = max pinba.*.*.*.*.*.tag_95_percentile
pinba.total.tag_98_percentile (60) = max pinba.*.*.*.*.*.tag_98_percentile

pinba.* metrics received on port 2013 and i see this traffic over

tcpdump -i lo -w go-carbon.pcap port 2013 and host <IP_ADDRESS>

see http://take.ms/qS34T
but pinba.total.* metrics in wsp files don't  updates
in go-carbon.log i don't see any errors about incorrect aggregation rules, how i can debug and fix it this problem?

http://graphite.readthedocs.io/en/latest/config-carbon.html#storage-aggregation-conf is not http://graphite.readthedocs.io/en/latest/config-carbon.html#aggregation-rules-conf
"Aggregation rules" not supported. Try external aggregators https://github.com/lomik/go-carbon/issues/42


It's not clear whether this module should work with non-proxied requests or not

Example configuration:
-bash-4.2$ cat /etc/nginx/nginx.conf
load_module modules/ngx_http_cookie_flag_filter_module.so;

user nginx;
worker_processes 1;

error_log /var/log/nginx/error.log notice;
pid /var/run/nginx.pid;

events {}

http {
    access_log off;
    root /usr/share/nginx/html;
    index index.html index.htm;

    upstream u {
        server <IP_ADDRESS>:8080;
    }

    server {
        listen 80 default_server;
        server_name localhost;
        set_cookie_flag * HttpOnly;

        location / {
            add_header Set-Cookie "mycookie=from_static";
        }

        location /proxy {
            proxy_pass http://u/;
        }
    }

    server {
        listen 8080 default_server;
        location / {
            add_header Set-Cookie "mycookie=from_upstream";
        }
    }
}
-bash-4.2$ curl -si http://localhost/ | fgrep Set-Cookie
Set-Cookie: mycookie=from_static
-bash-4.2$ curl -si http://localhost/proxy | fgrep Set-Cookie
Set-Cookie: mycookie=from_upstream; HttpOnly

So obviously the module works fine with upstream responses, and doesn't work with "local" add_header directives (which is somewhat expected for experienced nginx users), but it would be good to either have this clarified in documentation, or improve the code, if this behavior is wrong by the author's vision.
Thanks.

Hi @defanator,
Yes, the key target of this module is set cookie flags for the upstream responses. In real situations we often doesn't know what security settings provides backend software and even we can't affect on it. This module cover this cases.
As for the "local" add_header directives, if we can set a cookie, what prevents us from setting the required flags? For example:
location / {
    add_header Set-Cookie "mycookie=from_static; HttpOnly";
}

But in any case, your idea is clear to me and I'll think about its implementation.
Thank you!

@AirisX maybe this change would be enough for now:
diff --git a/README.md b/README.md
index 93c3f2a..5681786 100644
--- a/README.md
+++ b/README.md
@@ -42,7 +42,7 @@ location / {

Description
-This module for Nginx allows to set the flags "HttpOnly", "secure" and "SameSite" for cookies in the "Set-Cookie" response headers.
+This module for Nginx allows to set the flags "HttpOnly", "secure" and "SameSite" for cookies in the "Set-Cookie" upstream response headers.
The register of letters for the flags doesn't matter as it will be converted to the correct value. The order of cookie declaration among multiple directives doesn't matter too.
It is possible to set a default value using symbol "*". In this case flags will be added to the all cookies if no other value for them is overriden.

@defanator I think, yes.

@defanator done here


'want' of null bug when having multiple feeds

Was able to produce a reproducible test case by running npm test on this branch. Seems to happen when you have two hypercores in the same swarm. https://github.com/mafintosh/hypercore-archiver/pull/27/files#diff-bdf3fde96319b43abcc38201204c47ffR97
/Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:269
  this.stream.want({start: 0}) // TODO: don't just subscribe to *EVERYTHING* hehe
             ^

TypeError: Cannot read property 'want' of null
    at Peer.ready (/Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:269:14)
    at /Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/lib/replicate.js:24:10
    at /Users/karissa/node_modules/hypercore-archiver/node_modules/hypercore/index.js:112:15
    at apply (/Users/karissa/node_modules/hypercore-archiver/node_modules/thunky/index.js:44:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

Fixed by you in #92


feat(client): add attribute method to InputMessage

Next up documentation about what attributes are, why you'd want to use them, and an example.

Thanks.


trace-agent: more permissive trace normalization with metrics & logs

What does this PR do?
The trace agent now lets through a wider variety of traces, automatically correcting some malformed traces instead of dropping them. The quantity of malformed traces is kept track of in a new datadog.trace_agent.receiver.traces_malformed metric (tagged by reason).

The following fields are now replaced with reasonable defaults if invalid or empty and truncated if exceeding max length: span.service, span.name, span.resource, span.type.
span.duration=0 is now allowed.
Missing span start date now defaults to current time.

Traces are now dropped only for the following reasons: empty_trace, foreign_span, with the datadog.trace_agent.receiver.traces_dropped metric tagged accordingly.
Motivation
Goal is to redefine the Agent ingestion so that we ingest as many traces as we can, surfacing malformed traces in the UI instead of dropping them at the agent.

Left some pointers. Happy to review again once you feel it's ready.

Depends on https://github.com/DataDog/datadog-agent/pull/3747

@gbbr could you take another look? I think I've addressed all of the comments.

We forgot to take into account decoding errors, we'll have to add this somewhere above or below this line:
if count, err := strconv.Atoi(req.Header.Get(sampler.TraceCountHeader)); err == nil {
    atomic.AddInt64(&ts.TracesDropped.DecodingError, count)
} else {
    metrics.Count("datadog.trace_agent.receiver.decoding_error", 1, nil, 1)
}

We forgot to take into account decoding errors, we'll have to add this somewhere above or below this line:

Good catch! Totally missed that one. Added https://github.com/DataDog/datadog-agent/pull/3738/commits/8774469ea836509cda073f3d45d38f98fc4b8467

Flaky test fixed in https://github.com/DataDog/datadog-agent/pull/3790


First attempt on using GHSCI on Linux

Dear developers,
Perhaps this issue could be labeled as dependencies for Linux.
...
We (Marc, Xavi and I) wanted to test this software on a workstation with a lot more hardware resources than our PCs, but this machine only has a Linux Ubuntu 22.04 installed (docker v23.0.4, with the compose command). The program is containerized so it should work on Linux too. However we found some small issues that we think are platform related. We tested different versions being the last one global-indicators-4.2.1 and all presented two similar problems in Linux.
First problem
The docker-compose.yml is deployed and pulls the images without problems. However, the first attempt failed because of two permission denied error.
 Docker Desktop includes Docker Compose, which is required to run this software.

This can be solved manually using:
chmod +x ./process/instructions.sh

A temporary patch for Linux could be to add this step in the command specified in the docke-compose.yml file (e.g. command: ["/bin/bash", "-c", "sleep 3 && chmod +x ./process/instructions.sh  && ./instructions.sh && /bin/bash"]). Maybe, a different and more stable approach could be to provide separate scripts for each system (e.g. global-indicators-linux.sh or global-indicators-ios.sh.
Another permission issue came when scaffolding the template files:
# python 1_create_project_configuration_files.py example_ES_Las_Palmas_2023
Creating project configuration files, if not already existing in the configuration folder...
Traceback (most recent call last):
  File "/home/ghsci/work/process/1_create_project_configuration_files.py", line 103, in <module>
    shutil.copyfile(path_file, path_file.replace('templates/', ''))
  File "/env/lib/python3.10/shutil.py", line 256, in copyfile
    with open(dst, 'wb') as fdst:
PermissionError: [Errno 13] Permission denied: './configuration/config.yml'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/ghsci/work/process/1_create_project_configuration_files.py", line 106, in <module>
    raise Exception(f'An error occurred: {e}')
Exception: An error occurred: [Errno 13] Permission denied: './configuration/config.yml'

The problem seems to be related to having different user ids in the container and on the host. Using this approach we made it work.
So we added this line to the ghsci service in the docker-compose.yml
    user: "${UID}:${GID}"

Then, docker compose is called using:
        # if Docker exists and is runnable, launch the Docker compose image
        # docker compose -f docker-compose.yml up -d
        UID=$(id -u) GID=$(id -g) docker compose -f docker-compose.yml up -d

This way the process could continue as expected.
Second problem
# python 2_analyse_region.py example_ES_Las_Palmas_2023

Global Healthy Liveable Cities Indicator Study Collaboration, version 4.2.1

Las Palmas de Gran Canaria (example_ES_Las_Palmas_2023)

Output directory:
  process/data/_study_region_outputs/example_ES_Las_Palmas_2023

A dated copy of project and region parameters has been saved as process/data/_study_region_outputs/example_ES_Las_Palmas_2023/_parameters.yml.

Analysis time zone: Australia/Melbourne (to set time zone for where you are, edit config.yml)

Analysis start:	2023-04-21_0322
Create database:                      0%|                              | (0/13)

Processing _00_create_database.py failed: Command 'python _00_create_database.py example_ES_Las_Palmas_2023' returned non-zero exit status 1.

The log shows an error when trying to connect to the database, the host name (gateway.docker.internal) is not recognized in Linux but apparently on iOS and on Windows it works just fine.
Global Healthy Liveable Cities Indicator Study Collaboration, version 4.2.1

Las Palmas de Gran Canaria (example_ES_Las_Palmas_2023)

Output directory:
  process/data/_study_region_outputs/example_ES_Las_Palmas_2023

Connecting to default database to action queries.
Traceback (most recent call last):
  File "/home/ghsci/work/process/subprocesses/_00_create_database.py", line 130, in <module>
    main()
  File "/home/ghsci/work/process/subprocesses/_00_create_database.py", line 26, in main
    conn = psycopg2.connect(
  File "/env/lib/python3.10/site-packages/psycopg2/__init__.py", line 122, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: could not translate host name "gateway.docker.internal" to address: Name or service not known

This is explained in detail in this post and the author provides a solution that should work by just editing the docker-compose.yml file. Using these suggestions the ghsci service now works (I guess that only the second extra_host is necessary in this case):
The compose now works and looks like this:
#  ...
    volumes:
      - ./:/home/ghsci/work
    user: "${UID}:${GID}"
    extra_hosts:
#      - "host.docker.internal:host-gateway" # From the Tim van Baarsen solution
      - "gateway.docker.internal:host-gateway" # Adjusted to the name in this project

#  ... The rest of the dockerfile

Suggestion
It seems that only these three minor edits are necessary to execute the GHSCI on Linux.
We should try this on different machines to see if:

the behavior is consistent in other Linux.
these edits are compatible with the software working on Windows or iOS.

We hope this help other Linux user's while these issues can be addressed in the main branch.
Please, let us know if we can help with any more testing, logs or a pull request.
Thank you for this interesting project! ;)

Hi @benizar ,
Thanks again for the detailed issue write and sharing code for suggested fix -- I've now implemented and tested this in pull request #257 .   I think because you aren't yet in a team within our organization I couldn't select to add you as a reviewer, but would be great if you could try this out when you get a chance (perhaps on a Mac OS computer too if possible?).
The main bit I changed was moving instructions.sh to the parent folder as ../.env and editing it to make the set of instructions to display a text environment variable, and UID and GID likewise as text environment variables (but empty strings; which avoids a warning that otherwise displayed).   As per the write up in the pull request, in my tests this works on both Linux (Ubuntu) and Windows systems (including WSL).
Keen to hear your thoughts!
Carl

This has been addressed in #257, now merged to the main branch -- I will update a new formal release with this fix later


Unwanted newline char

Hi,
Not sure what option I've missed... Can't figure out how to get rid of the extra char added in between "1" & "2"
TY
fiddle = https://jsfiddle.net/d3mzL0x1/

Edit: I have a workaround = I replace tabs and newline before compiliing... replace(/[\t\n\r]/gm,'') But would rather use the right option

You might want to have a look at whitespace-control.
You could do this. But personally I think this is counter-intuitive, so this is not a suggestion to do it.
I you probably put it into the same line or use CSS to remove the gap.

TY for your answer.
Already checked whitesapce-control which helps me fixing extra chars in loops...
I was wondering if I was doing things the right way which seems to be the case.
Won't use your unassigned property trick nor the css (not even sure I can remove a character using css)...
Same line is fine with 2 items... But I have more ;)
Will keep my workaround: removing tabs & newlines before compilation and/or use a {{~#each _Object~}}{{~/each~}} with a little context for my "static links"

I thought there was a good way, but there seems not to be. I found this: https://davidwalsh.name/remove-whitespace-inline-block which may include some helpful hacks, but there does not seem to be a pretty solution...


@alloy => Upgrade artsy-eigen-web-association

Bumps the version in the lock file to 1.0.7 to include the /gender-equality route!

👍


export/import doesn't include the indexes

all indexes are not copy to new database when i was doing importing. any idea?

Indexes are just rebuilt while importing.

sorry. it was my mistake. indexes are corrupted and so it doesn't work at all when importing to new database.


Add event opcode

This PR adds the Event Opcode
Related to https://github.com/lambdaclass/era-compiler-tester/pull/3
It fixes the following tests (with mode Y+M3B3 0.8.26):
tests/solidity/simple/yul_instructions/codesize.sol
tests/solidity/simple/yul_instructions/codecopy.sol
tests/solidity/simple/yul_instructions/basefee.sol
tests/solidity/simple/yul_instructions/chainid.sol
tests/solidity/simple/yul_instructions/coinbase.sol
tests/solidity/simple/yul_instructions/gaslimit.sol
tests/solidity/simple/yul_instructions/gasprice.sol
tests/solidity/simple/yul_instructions/number.sol
tests/solidity/simple/yul_instructions/origin.sol
tests/solidity/simple/yul_instructions/prevrandao.sol
tests/solidity/simple/yul_instructions/timestamp.sol

Even though it's not in the spec, let's add a check to make sure only the EventWriter can use the event opcode (see here) which underneath uses the event_write verbatim.


condition logic for device_id hash/salt

updated please revise

Looks good for me.

👍

Close this for now :)  lol

Where should I put the
os.path.join(_base_dir, 'data', 'deviceid-%s.txt' % self.config.username)
Why is not on the documetnation and why is not an option to set on the config.json? this is like the most easy way for hiantic to ban users...


Improving naming of functions and variables

Background

Fixes

Change Summary

Additional Notes

Testing Procedure

Related PRs or Issues

@code-review-assist help


Feedback email db migration

Let me know what you think. I'd like to do the migratio i.e. the merge when you're online as well

@eleanorreem have updated the table to be more flexible to other forms of email campaigns - let me know your thoughts

Approved - just one question about config change


Any example form tabNavigation swiper animation?

I see this in https://reactnavigation.org/, is there any example ?

Hi @SnowFlowers ! It looks like this is not a bug of the library nor a feature request, so I'll close it: I suggest next time you use Stack Overflow which is better suited for answering these types of questions. I also encourage you to join the Reactiflux community on Discord. There are React Native and React Navigation channels with helpful people who might be able to answer your question. I would also like to mention that there is a collection of helpful links and tutorials for React Navigation in the README which might be helpful for you.
If you believe that you are experiencing a bug or have a feature request, please open a new Issue following the dedicated template or submit a PR.


NCDA CHW Questionnaire - Child Scoreboard encounter [8h]

Tasks:

Encounter CT
Handle sync
Infrastructure on front end
Encounter pages (Participant, Encounter)
Routing

NCDA is on live for few months. Closing.


Draft API for Database-Only vs Search-Graph mode

This draft is about the common api between both modes, i.e. what should be available regardless of what mode the user is running in.
In preperation for a meeting with @bobvanluijt at June 9

See https://docs.google.com/document/d/1t-79VYh2x_Tl2bwEX9pfU22DbEmujmc8UXYJ6ZQ_KFc/edit


Add support for objects with polygonal footprint

Idea is to generalise the footprint of the robot to make it more customisable.

Planned approach:

Construct a trait called Robot that implements methods step, next, control etc.
Take the footprint of the robot as a vector of (f32, f32) that ordered set of coords.
Make changes in RobotConfig to support circular footprint.

This will also make it easy to add different drive types (unicycle, bicycle, Ackerman) etc.


Add instructions to use Flowbite with Symfony UX Turbo

Hey @ker0x,
Thanks for the PR. Merged!
Cheers,
Zoltan


Saving not Working

Describe your bug here.
So basically I was making events for my chart but when I saved or save anything that you can save it just doesn't save and all of my work is gone I tried doing it like 5 times and it did not even save one single time
Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows
Did you edit anything in this build? If so, mention or summarize your changes.
No

Sounds like the issue are from the openfl backend,
also about your work being lost, have you ever tried the load autosave button in the chart editor?

Is it saving to the right place? I had my psych build located in desktop but it was saving to downloads.


Is there a tooltip duration change function?

When mouse hover, the tooltip is displayed, and I want to close it 5 seconds after the tooltip is displayed.
I customized the tooltip using afterShow and afterHide, but there is a problem.
If you hover your mouse over id=test1 and move your mouse to id=test2 to open the tooltip and mouse over the existing test1 again, there is a bug that closes immediately, not after 5 seconds.
When the id changes, I want to initialize the timeOut of that id when I do mouseLeave.
I'm going to solve this method and set the tooltip duration to 5 seconds, so if there's a good way other than this, please share it.

condeSandBox
https://codesandbox.io/p/sandbox/tooltip-w2q7ll?file=%2Fsrc%2FApp.tsx%3A15%2C14-15%2C19

https://react-tooltip.com/docs/options
Check data-tooltip-delay-show and data-tooltip-delay-hide in Available attributes and delayShow and delayHide in Available props. Quite simple, straight forward and self explanatory.

Sorry, my question is unanswered.
I get a tooltip when I hover my mouse, and I want to set this tooltip to 5 seconds. I'm looking for a feature that immediately disappears when the mouse leaves, and when I move the mouse, the tooltip displays for 5 seconds and then disappears.

@ggnu11 we indeed do not have a solution for this use-case, but I do like the idea. Maybe we could include an autoClose prop (kinda like react-toastify but obviously would need to behave a little differently).
I've updated your code sandbox to fix the issue you're having, so maybe that works for you for now, until we possibly work on the new feature.
https://codesandbox.io/p/sandbox/tooltip-forked-5385t9
Anyway, let's leave this issue open for now.

Thank you for your good feedback, I'll keep the code sandbox open for others to refer to.
I'll look forward to many features in the next update


snakemake vidlet reflections

after a first pass by many --

vidlets are fast and complete. pausing is necessary, but it's nice to be able to skip
some of the output / script was covered by video

I used streamlabs OBS and then recorded locally and uploaded to video.ucdavis.edu, which has good quality video.

the captioning really helped. so we need to figure out editing/correcting the captioning!

turn off recording for the interactive zoom calls! it makes people turn off video and disengage.

add cheatsheets

what jeremy wants: "vidlet + companion lesson + cheat sheet"

what jeremy wants: "vidlet + companion lesson + cheat sheet"
to qualify this, it gives more flavors for a broader learner set... some folks will engage more with the videos, while some will favor the text... if they match up, perfect... then the user can go through the text and if they get stuck the video is there to demo the way through (or just fill in context and details)... the cheat sheet would just be a super nice tool for people to reference with a short-list of handy commands and call-outs that are mostly lesson specific... with these three in place, I think interactive sessions would be a smaller group of people who need/want the extra help...


Stream from vlan interface possible?

Is there a way to get a camera RTP stream via vlan? Analogue to this gst command I would like to use the video-viewer or any other net.
gst-launch-1.0 -v udpsrc multicast-iface=veth10 uri=udp://<IP_ADDRESS>:5100 auto-multicast=true caps="application/x-rtp,encoding-name=H264,payload=96" ! rtpjitterbuffer ! rtph264depay ! h264parse ! video/x-h264,stream-format=byte-stream,alignment=au ! avdec_h264 ! clutterautovideosink sync=false async=false
Using video-viewer.py --input-codec=h264 rtp://<IP_ADDRESS>:5100 rtsp://@:1234/my_output --headless results in timeouts like [gstreamer] gstDecoder::Capture() -- a timeout occurred waiting for the next image buffer

@seb2189 you can modify the gstreamer pipeline that jetson-utils constructs for RTP input here:
https://github.com/dusty-nv/jetson-utils/blob/f0bff5c502f9ac6b10aa2912f1324797df94bc2d/codec/gstDecoder.cpp#LL585C1-L585C1
you can try adding your multicast options there.   Then re-run make && sudo make install


Thresholds remain too large for their DataType after RoundAndClipThresholds

Quick summary
RoundAndClipThresholds behave so thresholds values will be clipped to 1 more or 1 less than the maximum and minimum values defined by the DataType, which may lead to an error during HLS code generation.
Details
After switching to dev branch (commit hash "fd72d48410c040ae8f715919e65ec731580235ce"), I experienced an error during the "step_hls_codegen":
Traceback (most recent call last):
  File "/home/hlebleve/finn/src/finn/builder/build_dataflow.py", line 158, in build_dataflow_cfg
    model = transform_step(model, cfg)
  File "/home/hlebleve/finn/src/finn/builder/build_dataflow_steps.py", line 488, in step_hls_codegen
    model = model.transform(PrepareIP(cfg._resolve_fpga_part(), cfg._resolve_hls_clk_period()))
  File "/home/hlebleve/finn/deps/qonnx/src/qonnx/core/modelwrapper.py", line 140, in transform
    (transformed_model, model_was_changed) = transformation.apply(transformed_model)
  File "/home/hlebleve/finn/src/finn/transformation/fpgadataflow/prepare_ip.py", line 86, in apply
    _codegen_single_node(node, model, self.fpgapart, self.clk)
  File "/home/hlebleve/finn/src/finn/transformation/fpgadataflow/prepare_ip.py", line 53, in _codegen_single_node
    inst.code_generation_ipgen(model, fpgapart, clk)
  File "/home/hlebleve/finn/src/finn/custom_op/fpgadataflow/hlscustomop.py", line 288, in code_generation_ipgen
    self.generate_params(model, path)
  File "/home/hlebleve/finn/src/finn/custom_op/fpgadataflow/thresholding_batch.py", line 445, in generate_params
    self.make_weight_file(thresholds, "hls_header", weight_filename)
  File "/home/hlebleve/finn/src/finn/custom_op/fpgadataflow/thresholding_batch.py", line 350, in make_weight_file
    assert np.vectorize(tdt.allowed)(
AssertionError: Thresholds can't be expressed with type UINT4

So this happens because at this point in the flow I end up with a MultiThreshold layer whose threshold values are set to UINT4, and are ranged between 1 and 16, with 16 being impossible to write on UINT4. I found that this situation was created during streamlining, by the RoundAndClipThresholds transformation. Since the this node has a UINT4 input, the datatype of the threshold values is changed and they are rounded to the nearest larger integer. In the code of the transformation,  at some point the values are clipped to the data type's range plus one:
https://github.com/Xilinx/finn/blob/fd72d48410c040ae8f715919e65ec731580235ce/src/finn/transformation/streamline/round_thresholds.py#L63
For UINT4, this means the values are set to be between -1 and 16, with both extremes being impossible to express on UINT4, since idtype.min() returns 0 and idtype.max() returns 15.
I know this transformation is not new so my guess is something changed recently with the way data type's work, unless I am missing something and there is actually a reason to have values clipped to their data type's range plus one ?
Possible fix
Clipping large thresholds to input range instead of input range plus range corrected the issue in my case.
I can provide ONNX models of different steps if you think it's relevant.

I also don't understand why thresholds are clipped to the input range +/- 1 here.
Maybe this was not noticed earlier because minimize_accumulator_width() was previously part of the convert_to_hls transformations, before it was moved to the new step_minimize_bit_width() builder step 6 months ago. This function clips the thresholds according to the minimized accumulator width for the MVAU, and increases the threshold datatype width beyond the input width in cases like this for the thresholding_batch CustomOp.

Hi @hleblevec ,
Thanks for filing this issue, it is something we look into currently. Until further experiments are done, I would suggest changing the datatype assignment a few lines below to a bigger datatype: model.set_tensor_datatype(n.input[1], idtype).
Like @fpjentzsch mentioned, the minimize_accumulator_width got moved, so this might have led to the error you're observing. When the bug is addressed, I will update this issue.

Hi @auphelia and @fpjentzsch ,
Thanks for your answers. I was not using the step_minimize_bit_width before. I included it in my build and I don't see the error anymore. I guess that solves the problem, but it may still be useful to wonder if this clipping is still relevant as it is.


Invalid url AFError for Valid Url bug?

[Removed due to resolution in Swift]

@grantkemp can you please explain what fixed the issue.

Hi @AliTariqPL - it was down to the way the array was taking the url query parameters for me.  The easiest way is to print out the request url before its called and run it through a browser/ Rest client to surface the problem.


Please move required tap-* modules into this repo

To use node-tap at all you need several other repos including:
https://github.com/isaacs/tap-runner.git
https://github.com/isaacs/tap-producer.git
https://github.com/isaacs/tap-results.git
https://github.com/isaacs/tap-consumer.git
https://github.com/isaacs/tap-global-harness.git
https://github.com/isaacs/tap-assert.git
which seem like they generally belong in this repo.  My suggestion is to move these into this node-tap repo to decrease the number of dependencies.

Note that it should affect this, but I think that nodeunit (for one) is already using some of these modules as independent modules: https://github.com/caolan/nodeunit/tree/master/node_modules

Fixed by @kusor, published as 0.1.0


Myntra Customize - Add active links

In navigation bar, add additional links. On scrolling the page, it should highlight the active nav bar content.

Can you please assign this to me?


Generate SQL for bootstrapping db data

Closes: https://github.com/metarhia/metasql/issues/175

[x] tests and linter show no problems (npm t)
[x] code is properly formatted (npm run fmt)
[x] description of changes is added in CHANGELOG.md

Landed in https://github.com/metarhia/metasql/commit/95da670ed057c9774dbadd9e6be86c7b0ceddd1e, https://github.com/metarhia/metasql/commit/68f34df120bba2aeb457ec1978821991b3de8b4d, and https://github.com/metarhia/metasql/commit/259a6850a48bf4920d5be76e03a90d2103b4b541


[Feature] Create checklist for verifying new or modified UI elements

This checklist will create a streamlined and repeatable process for testing and also prevent things from slipping through the cracks during code review, such as the help text for verifying deployments added in #44.
Things to include:

All required components for a new UI element such as a databound setter, getter, doCheck... method, corresponding help text, i18n compatibility for the title and help text, etc.
Spelling out (in a human readable form) the considered scenarios for user input and expected verification message in that scenario.
Spelling out what it means when the feature is working and what expected outcomes correspond to the user's input. (i.e. will the timeout be accurate? Will it finish early if in a successful or unrecoverable state?)
etc...

While it should be the responsibility of the person submitting a change to verify it through testing, having a basic checklist with the addition of submitter-provided explanations for how to check the change makes it easier for someone else to take a second look and verify in a fresh environment/configuration.

Providing readable unit and integration tests should be sufficient for bullets 2 and 3, but documentation or explanation in the PR summary would be nice to have for more changes that require more context to understand.


add support for rhel

rhel does not provide a bsdcpio package, it will need to build from source.

bsdcpio-3.1.2-7.el7.x86_64.rpm


Fix failing parquet test

This PR removes explicitly setting index=True when calling pandas to_parquet in test_roundtrip_from_pandas. The index= parameter was added to to_parquet in pandas version 0.24.0, leading to test failures on the CI when tested against older (yet still supported) versions of pandas (ref https://travis-ci.org/dask/dask/jobs/554929402#L1107-L1139).
This issue wasn't caught before because the CI had pyarrow 0.13.0 installed and skipped the test. With the new release of pyarrow 0.14.0, this test is no longer skipped and the test failure showed up.
Fixes #5073

[x] Tests added / passed
[x] Passes black dask / flake8 dask

Removing index=True makes to_parquet fall back to the default parquet engine behavior, which is to store the index as a column. So IIUC not specifying a value for index in to_parquet should have the same effect as setting index=True.
cc @rjzamora

@jrbourbeau This looks good to me - Thanks!  You are correct (AFAIK) that not specifying index=True for to_parquet should not matter in this particular case.  I recently added it for clarity/explicitness, but I wasn't thinking of earlier pandas versions :)

Thanks for the review @rjzamora!


RPO & RTO requirements for Full Cluster Replication

Recovery Point Objective(RPO): Maximum targeted period for which data might be lost during Disaster Recovery(i.e. Failover).
Recovery Time Objective(RTO): Maximum time duration it takes for clusters to achieve Failover. During this period, clusters will not accept writes.

Open Questions:

[ ] What are the minimum RPO & RTO guarantees we want to support?
[ ] For cross-region use cases, how do we handle network partitioning during failover?

Ideally we'd want to have minimal RPO & RTO.
To achieve zero RPO(i.e. no data loss) & near-zero RTO, we'd need to move towards a synchronous replication model where writes on primary are not acknowledged unless one of the secondary has also accepted the write operation. This ensures that one of the secondary is always consistent with Primary and can be used for failover ensuring no data loss.
However this approach would affect the availability of the Primary(consistency vs availability in CAP theorem).
We propose relying on an asynchronous replication model where user can define its RPO & RTO requirements.
Let's assume we're using Segment Replication with Remote Store. We can piggyback on local cluster level durability guarantees to ensure minimal RPO.
For example, as soon as segments are written to Primary's remote store(with refresh or commit), these changes are always available to the secondary clusters. Incase of Primary outage, secondary can ensure that all the latest segments have been downloaded. As an additional step during failover, we can even explore fetching primary's translog to ensure no data loss. This would ensure we have near-zero RPO & RTO in happy cases.
In the worst case scenario, let's assume that there is is network partitioning and Secondary can't read the remote store data.

Case 1: Customers okay with acceptable data loss can achieve failover immediately(near-zero RTO).  RPO in this case would directly related to replication lag between Primary & Secondary.
Case 2: Customers not okay with data loss will require higher RTO as they have to wait till the network partitioning s resolved. Just to remind, the primary cluster might still be unavailable here. So technically you can achieve your zero RPOs but  you'll take a hit on your RTO..

One optimisation over this could be to rely on the remote store's capability for cross region replication. With this approach, data from Primary's remote store is replicated directly to the Secondary's remote store and secondary cluster can fetch data directly from its remote store. In this case, if a network partition happens, we can rely on underlying remote store's guarantees(e.g. S3 guarantees 15 mins for 99.99) for ensuring that the data is available to the Secondary clusters.

For other approaches, we can only ensure RPO equals to our SLA for Replication lag.
To ensure that failover can be achieved with our RPO & RTO guarantees, we'd need 2 things:

Have metrics and APIs to ensure that Replication setup is in healthy state(i.e. Replication active and lag within the SLA)
Incase the replication lag is high, we'd also need the necessary tuning parameters which can be leveraged to ensure we meet the Replication lag SLA.

Zero RPO is a must have for any business critical application. It is possible to achieve Zero RPO for OpenSearch but there can be trade-offs, you can use synchronous writes with enough redundancy to ensure you have zero RPO within a domain.  For cross-domains we can use one of the following option

Provide synchronous replication across clusters with consensus replication. i.e. Primary will not acknowledge a write request till all the secondary cluster acknowledge the write request. It could also mean that the common remote data store has acknowledged the write request.
Provide synchronous replication across domains with Quorum based replication i.e. Primary will acknowledge a write request if a majority of the secondary cluster acknowledges the write request.

For users who are okay with some data loss, the in-cluster replication and cross-cluster replication can be treated independently. The lag between domains would be equivalent to the RPO. This also provides the opportunity to use different strategy to determine how you want to achieve replication. Do you do it event based, frequency based, size based etc. The design should provide some level of control for the same.
RTO can be tricky. What would we consider as RTO? At a basic RTO is the time it takes a system to recover from a failure event. A system should try and minimize the RTO. In which case it is important that

the mean time to detect failure is low,
time it takes to start recovery is low,
the time it takes to reconcile the data is low or data reconciliation should be fast.

In each of the above case we need to ensure we have the appropriate events, metrics and process.
Failure Detection - Full cluster failure, node failure, network failure, can all impact the ability to replicate and hence need to be detected fast. It could be a combination of health pings between clusters, latency, replication lag and timeouts.
Recovery - If we look at a fully managed experience, it should include ability to do a failover in case a primary cluster is impacted. While the failover happens, primary cluster may need to recover. This recovery will require that first it is established that the cluster up and running and it catches back to the current state of data in the group of clusters.

Thanks for the great discussion!
I'd like to dig-in a bit on Zero RPO. Totally understand why critical business would require 0 RPO.

Provide synchronous replication across clusters with consensus replication. i.e. Primary will not acknowledge a write request till all the secondary cluster acknowledge the write request. It could also mean that the common remote data store has acknowledged the write request.

Provide synchronous replication across domains with Quorum based replication i.e. Primary will acknowledge a write request if a majority of the secondary cluster acknowledges the write request.

Like pointed, synchronous replication is the only way to implement 0 RPO as one needs to ensure the copies are replicated to other cluster which could be in other region.
Is it fair to assume typical cross-cluster replication deployments for DR usecases are across regions? Picking AWS regions as an example (unofficial), latency between us-east-1 & us-west-2 is about 60 ms while between same regions is about 4 ms. Similarly picking Azure, the latencies are 80 ms across west and east US regions while < 10 ms in same region.
These latencies are dictated by laws of physics and dictate the minimum RPO we can achieve (although realistically it is going to be orders higher for intermediate checksum, metadata updates roundtrips etc). Some existing example services like AWS Aurora enforces minimum RPO of 20 seconds.
Since 0 RPO for cross-region workloads is very challenging to achieve realistically, it is a careful conscious decision to choose sync vs async replication mode.
Few things to keep evaluate

OpenSearch supports wide variety of usecases from ingestion heavy log-analytics workloads of peta-byte scale through search heavy usecases. Are there thoughts on which workloads should CCR support?
Sync replication adds strong coupling on health and performance of remote cluster in addition to network latencies. This might not be desirable for all usecases.
One of the arguably needle moving advances happening in OpenSearch is support for remote store (#1968). The main intent is to achieve high durability via external battle tested object stores. Async approach can support wide variety of configurations including non-remote store as per different usecases.

RTO can be tricky. What would we consider as RTO? At a basic RTO is the time it takes a system to recover from a failure event. A system should try and minimize the RTO. In which case it is important that
1. the mean time to detect failure is low,

2. time it takes to start recovery is low,

3. the time it takes to reconcile the data is low or data reconciliation should be fast.

In each of the above case we need to ensure we have the appropriate events, metrics and process.
Failure Detection - Full cluster failure, node failure, network failure, can all impact the ability to replicate and hence need to be detected fast. It could be a combination of health pings between clusters, latency, replication lag and timeouts.

Totally agree. I'd like to call on attention to the fact that some failure detection will have to be external to detect any cluster level outages. Overall, we need to lay in the requirements/documentation on how one can achieve near 0 RTO based on metrics and APIs exposed by OpenSearch.
From OpenSearch CCR point of view, the APIs to switch role (follower/leader or secondary/primary) and them being reliable and performant would be key.

We propose relying on an asynchronous replication model where user can define its RPO & RTO requirements.
Let's assume we're using Segment Replication with Remote Store. We can piggyback on local cluster level durability guarantees to ensure minimal RPO.
For example, as soon as segments are written to Primary's remote store(with refresh or commit), these changes are always available to the secondary clusters. Incase of Primary outage, secondary can ensure that all the latest segments have been downloaded. As an additional step during failover, we can even explore fetching primary's translog to ensure no data loss. This would ensure we have near-zero RPO & RTO in happy cases.

Nice! Few caveats though

The translog itself may be not accessible if the primary cluster is down. If you are refering to remote translog, then perhaps yes.
In case of whole environment outage (ex region level in cloud provider environment), the remote store itself should be replicated or the RTO guarantees will have to be explicit about this remote store dependency.

One optimisation over this could be to rely on the remote store's capability for cross region replication. With this approach, data from Primary's remote store is replicated directly to the Secondary's remote store and secondary cluster can fetch data directly from its remote store. In this case, if a network partition happens, we can rely on underlying remote store's guarantees(e.g. S3 guarantees 15 mins for 99.99) for ensuring that the data is available to the Secondary clusters.

Ok yes - this speaks to caveat 2 and just that it may also be due to outage of remote store (not just network partition).

As an additional step during failover, we can even explore fetching primary's translog to ensure no data loss. This would ensure we have near-zero RPO & RTO in happy cases.

We should consider replicating remote store translog not just during the failover. As the cluster/remote store might not be avaiable during the failover and this ensures desired RPO is maintained in all the cases.

Incase the replication lag is high, we'd also need the necessary tuning parameters which can be leveraged to ensure we meet the Replication lag SLA.

Any tuning params for replication warrants additional resource consumption on leader(and on follower). In most of the cases, this additional load can eat into the resources used for on-going workloads running on the cluster. At leader cluster side, this involves bookkeeping of follower cluster states (as might be replicating at different rates) and allocation of resources to achieve desired RPO. As we are already exploring remote store(on cloud) as an option, we should consider design of replication component external to the clusters that can perform this job without additional overhead on the participating clusters within the replication group.

the time it takes to reconcile the data is low or data reconciliation should be fast.

Recovery - If we look at a fully managed experience, it should include ability to do a failover in case a primary cluster is impacted. While the failover happens, primary cluster may need to recover. This recovery will require that first it is established that the cluster up and running and it catches back to the current state of data in the group of clusters.

Yes, we will need to optimize on both detection and recovery mechanisms.
For recovery within the replication group, In addtion to data reconcialation across the clusters, this needs additional handling from the plugins side.
Depending on the role of the cluster within the replciation group - PRIMARY / SECONDARY. Plugin behavrior/actions might have to be on PASSIVE mode and without much overhead should shift to ACTIVE mode after SECONDARY cluster is promoted to primary.

I agree on the need to optimise detection & recovery mechanism.

Any tuning params for replication warrants additional resource consumption on leader(and on follower). In most of the cases, this additional load can eat into the resources used for on-going workloads running on the cluster. At leader cluster side, this involves bookkeeping of follower cluster states (as might be replicating at different rates) and allocation of resources to achieve desired RPO. As we are already exploring remote store(on cloud) as an option, we should consider design of replication component external to the clusters that can perform this job without additional overhead on the participating clusters within the replication group.

What resource  are we talking about in this case? CPU or I/O?
Irrespective of whether we go with external replication replication component or not, we'll have to do the bookkeeping as well as segments upload on leader.
Here are the pros/cons of using the remote store level replication. Feel free to add if you've got more.
Pros:

Allows us to achieve better cross-region RPO & RTO guarantees during Failover(incase of region level failures)
We piggyback on the guarantees provided by remote store for cross region copy.

Cons:

Will be additional effort. Unless this is the only supported combination.
We'll be continuously copying leader's remote translog to follower's bucket for failover cases. But this continuous data copy(think cross region) would be redundant and not used during normal operations.
With introduction of additional component in data transfer(i.e. follower's remote store), we can potentially have higher replication lag.


APIApplicationInstallParams documents its properties as always present when they are optional

Issue description
Through testing, I've found that APIApplicationInstallParams can be an empty object if you simply do not have an installation link.
Code sample
No response
Package version
0.37.92
Runtime
Node.js
Runtime version
20.15.1
Priority this issue should have
Medium (should be fixed soon)

This is no longer possible since an unknown update:


improve selecting qt module

It looks like this is currently the best fork in the quamash-asyncqt lineage to push improvements. Thanks for having a go at maintaining this well-needed lib :)
This PR:

Allows setting QT_API to empty string to to let qasync choose a lib. (Ran into this because QT_API was set, and needed to "unset" it).
Prefer a Qt lib if it is already imported.

Thanks for your contribution! This is now live in qasync==0.9.3.


Fix minor bug in kapcsolat.php

The red error message should disappear when you click the submit button.

Reset variables after sending data to database

Fixed in Popup feature update, patch #11


Multiple constant lines are not displayed

When setting multiple constant lines to be displayed on a graph, lines are drawn at 0 instead of the values defined in the collection graphs settings – works when defining only one constant line.

This has already been fixed in 7cb7a9757e07d3ed8610a2e810a3d9e05a7b95b3 but never cherry-picked in the 0.2 branch.


Installing MultiMiner-4.3.1 on Windows 10 try to download/install bfgminer from adsf.com

Installing MultiMiner-4.3.1 on Windows 10 try to download/install bfgminer from adsf.com ...
There is clearly something wrong with the code, because bfgminer has nothing to do with adsf.com !!!

Same here!

Also same here!

So, the conclusion is clear, the current code is compromised !


TypeError: Cannot set properties of undefined (setting 'transport')

Issue:
Local development in VS Code runs without problems or crashes.
However, when I upload the application to a server, it runs until a Socket.io connection is established or the connected web page is refreshed.
I don't know if this relates to the admin UI specifically as in the filepath below or if this is a Socket.io issue in general.
Perhaps this also has to do with the middleware which holds up a request until an action has completed so that non-existent data cannot be accessed.
// middleware is executed on every request
var Map = require('file')

module.exports = (io, socket) => {
    socket.use(async (packet, next) => {
        var key = socket.handshake.auth.key
        var data = Map.get(key)

        while(!data.action) {    // true for finished or false for loading
            await new Promise(resolve => setTimeout(resolve,10))
        }
        socket.data = data
        next()
    })
}

Serverconsole:
/usr/src/app/node_modules/@socket.io/admin-ui/dist/index.js:233
socket.data._admin.transport = transport.name;
^

TypeError: Cannot set properties of undefined (setting 'transport')
at Socket.<anonymous> (/usr/src/app/node_modules/@socket.io/admin-ui/dist/index.js:233:42)
at Socket.emit (node:events:390:28)
at WebSocket.onPacket (/usr/src/app/node_modules/engine.io/build/socket.js:214:22)
at WebSocket.emit (node:events:390:28)
at WebSocket.onPacket (/usr/src/app/node_modules/engine.io/build/transport.js:92:14)
at WebSocket.onData (/usr/src/app/node_modules/engine.io/build/transport.js:101:14)
at WebSocket.<anonymous> (/usr/src/app/node_modules/engine.io/build/transports/websocket.js:20:19)
at WebSocket.emit (node:events:390:28)
at Receiver.receiverOnMessage (/usr/src/app/node_modules/ws/lib/websocket.js:1022:20)
at Receiver.emit (node:events:390:28)

Node.js v17.3.1

Hi!
Yes, we keep track of some internal data in the socket.data._admin object: https://github.com/socketio/socket.io-admin-ui/blob/a8ce5262d51c9db44da048cb71186be322ee4929/lib/index.ts#L342-L347
So this line breaks:
socket.data = data

This might not be the best idea actually, but it is needed to work with multiple Socket.IO servers.


always call lua callback when connection goes to STATE_DISCONNECTED

Currently there are inconsistent behavior in notifying lua side about what happens with connection. If error occurs, after passing state STATE_CONNECTED, lua callback invokes two times(with EVENT_ERROR and EVENT_DISCONNECTED inside). The main problem is there are no way to detect in which state connection was when error occurs, so in there is no clue if callback with EVENT_DISCONNECTED will be invoked after error or not. This PR tries to fix it

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Issue-Adds loading indicator

Automated Review Comments
Issues in src/components/App.tsx:

(2, 'Hardcoded string found')
(5, 'Line exceeds 80 characters')
(17, 'Hardcoded string found')
Issues in src/components/CoinList.tsx:
(2, 'Hardcoded string found')
Issues in src/components/ui/LoadingPanel.tsx:
(2, 'Hardcoded string found')
(9, 'Line exceeds 80 characters')
Issues in src/components/ui/LoadingSpinner.tsx:
(2, 'Hardcoded string found')
Issues in src/styles/loading-spinner.sass:
(8, 'Hardcoded string found')

I got it.


Register package

@JuliaRegistrator register

Registration pull request created: JuliaRegistries/General/43971
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:
git tag -a v0.1.0 -m "<description of version>" 7e7b4cfcb42e32adceef965403f1e6fc1a647260
git push origin v0.1.0


Monthly report email flagged for phishing

I'm not sure why it was flagged, but I grabbed screenshots before clicking "I trust this email".

I got a bunch of other monthly report emails at the same time and they were not flagged.

can you share where the "learn more" links to?

Ah sorry I clicked "trust this message" and the warning disappeared.


Oh no! Build 10 failed to distribute. Error: Internal Server Error: undefined

What App Center service does this affect?
Name of service or sdk with the issue.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Thanks for reaching out. There is an ongoing incident affecting distribution: https://status.appcenter.ms/ .

Resolved.

Resolved.

issue not resolved yet.


Adding a new organization in Hyperledger Fabric operation fails

Describe the bug
Adding a new organization in Hyperledger Fabric operation using the operational guide fails
To Reproduce
Steps to reproduce the behavior:

Setup fabric network using bevel
Follow the adding org operation guide
See error in the ansible output

Expected behavior
The automation should complete without error and the new org is added to the network
Additional context
Missing role:
https://github.com/hyperledger/bevel/blob/bbdf9312c34a9ffece7cadf9480be1de7849f056/platforms/hyperledger-fabric/configuration/add-organization.yaml#L125

I'll take this issue

I'll take this issue