Define CRD structure for attestation results

put off until 0.7.0

Moved to miltsone 0.7.0, thanks!


Import error

When trying to import the py_nextbus module, I get the following error. I haven't been able to figure out what it means.
Traceback (most recent call last):   File "/home/nick/Documents/Workspaces/BusScheduler/HomeBusSchedule.py", line 1, in <module>     import py_nextbus   File "/home/nick/Documents/Workspaces/BusScheduler/py_nextbus/__init__.py", line 3, in <module>     from .client import NextBusClient   File "/home/nick/Documents/Workspaces/BusScheduler/py_nextbus/client.py", line 3, in <module>     from urllib.error import HTTPError ImportError: No module named error

The issue is with the import statements in client.py.


Ensure Latest Package-Lock on Release

Feature Request
Description
Update danger-file to check for new package-lock if dependencies are added or changed.
OR
Update/Add pre-release script to ensure a new package-lock is generated before releasing.

resolved with v6


Honor krmignore for subpackages for fn commands

This PR makes sure that fn commands honor krmignore files in subpackages.
Fixes https://github.com/GoogleContainerTools/kpt/issues/2506#issuecomment-920364213
cc @zijianjoy

Closing this in favor of https://github.com/GoogleContainerTools/kpt/pull/2514


feat: added Affiliate Marketing advertising banners

Description
Closes: Affiliate Marketing advertising banners

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[X] ran linting
[X] wrote tests where necessary
[X] included the correct type prefix in the PR title
[X] targeted the correct branch
[X] provided a link to the relevant issue or specification
[X] reviewed "Files changed" and left comments if necessary
[X] confirmed all CI checks have passed
[X] added an entry to the CHANGELOG.md file

yarn && yarn workspace web build && yarn workspace web dev

https://pr-gxclagq5m-bigdipper.vercel.app/


Support for Docker Unix socket.

Hello!
It appears that the support for connections to the Docker Unix socket (which is the default socket in plain Docker installs) is not implemented.
Specifically, it crashes on nkdocker_app:start() when trying to read the DOCKER_HOST variable ( nkdocker_app.erl ) if it's something different from tcp://....
I was wondering: why is this not supported? Would it be difficult to add support for it?
Thanks in advance!

Uh, I see: Erlang does not have a built-in support for Unix sockets...
This other project used an external tool to make up for this lack.
In any case, that would be a nice feature to have.

The socat solution is not very elegant but easy. I will probably add it.


109 fix links generation

Coverage increased (+0.1%) to 93.99% when pulling c632ae1099fa61d4bd04b3881ed76fadd8a955a0 on fenekku:109_fix_links_generation into f4c82a17e094792c6480d866bb2ea41076a3c2d0 on inveniosoftware:master.

Merging and releasing to get things rolling.


Feature/cmp 988/i18n and l10n service & structure

Why we create this PR?
We need a translation service to have at least two languages DE and EN
PR Linked to:
https://jira.catena-x.net/browse/CMP-988

I opened an IP issue for the libraries here now we need to wait:

[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>

i updated the version of the library to v9.2.2 and there is no dependecies not approved

Also fixed an axios vulnerability here

Works fine !

With the DPP it shows like this

With the Battery it works:

The translation also works in the battery correctly


python312Packages.earcut: init at 1.1.5

Description of changes
Adding a package for earcut, a Python port of the earcut JS triangulation library.
https://pypi.org/project/earcut/
Things done

Built on platform(s)

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

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

A couple of thing to do yet:

[ ] add unittests and changelog
[ ] replace Pypi by Github source

There should be exactly two commits:

maintainers: add mapperfr
python312Packages.earcut: init at 1.1.5

There should be exactly two commits:
* maintainers: add mapperfr

* python312Packages.earcut: init at 1.1.5

OK thanks! I'll fix it accordingly.

For unittests, this package does not include any, so I'm not sure we can do anything.

No unittest or changelog are provided in the source package.

No changelog is provided in the source package.

But there is https://github.com/mapbox/earcut/releases/tag/v3.0.0.

No unittest or changelog are provided in the source package.

We gotta open an upstream issue asking for tags.

@mapperfr , thank you very much for your contribution to nixpkgs !

Please rebase this PR correctly against master. Currently it contains unrelated changes
If you are interested in geospatial software, please consider joining Nix Geospatial Team

@mapperfr , thank you very much for your contribution to nixpkgs !

Thanks @imincik!

1. Please rebase this PR correctly against master. Currently it contains unrelated changes

Yeah I messed things up this morning but I should be fixed now, apart from unittests and changelog that are missing in the source package. Could you please check now?

2. If you are interested in geospatial software, please consider joining Nix Geospatial Team

I'd gladly join the team, thanks. Will add myself to the list once this initial PR is done :)

There are still more than two commits.

There should be exactly two commits:

maintainers: add mapperfr
python312Packages.earcut: init at 1.1.5

where the first one only modifies maintainer-list.nix.
Also apply nixfmt-rfc-style.

Please move all packaging code from maintainers: add mapperfr commit to 'python312Packages.earcut: init at 1.1.5'

Putting that to "In progress" again: the motivation for this PR is to package py3dtiles, but we are actually questioning this dependency (because it is a fork of mapbox/earcut, which is more active today). It might make more sense to package this latter package if it is satisfactory for py3dtiles.


Cannot connect to Sonarr

About a week or so ago, both HTPC-Manager and Sonarr came out with updates. Since then, neither one will connect. I have tried rebooting both HTPC-Manager and Sonarr as well as reset API key.
LOGS - http://pastebin.com/cTEW3nVS

Try removing the sonar basepath from htpc manager. Don't edit sonars own settings and try again.

Why is this closed? The issue persists?

I recreated the bug, i get the same error if i enter a basepath. If i remove it, it works. (just remove it, seems like sonar api doesnt like it anymore)

Removing the basepath does not fix the issue. It simply causes HTPC not to generate an error with the Sonarr plugin.

logs?

No change in logs

You can also verify with this script
import requests
from json import loads

def fetch(path, banner=None, type=None, data=None):
        try:
            host = '<IP_ADDRESS>'
            port = 8989
            sonarr_basepath = '/' # dont edit me
            ssl = ''

            headers = {'X-Api-Key': '123'} # edit me

            url = 'http%s://%s:%s%sapi/%s' % (ssl, host, port, sonarr_basepath, path)

            if banner:
                #  the path includes the basepath automaticly
                url = 'http%s://%s:%s%s' % (ssl, host, port, path)

            if type == 'post':
                r = requests.post(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            elif type == 'put':
                r = requests.put(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            elif type == 'delete':
                r = requests.delete(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            else:
                try:
                    r = requests.get(url, headers=headers, verify=False)
                    return loads(r.text)
                except:

                    r = requests.get(url, headers=headers, verify=False)

        except Exception as e:

            print 'Failed to fetch url=%s path=%s error %s' % (url, path, e)

print fetch('Series')

import requests
from json import loads

def fetch(path, banner=None, type=None, data=None):
        try:
            host = '<IP_ADDRESS>'
            port = 8989
            sonarr_basepath = '/' # dont edit me
            ssl = ''

            headers = {'X-Api-Key': '123'} # edit me

            url = 'http%s://%s:%s%sapi/%s' % (ssl, host, port, sonarr_basepath, path)

            if banner:
                #  the path includes the basepath automaticly
                url = 'http%s://%s:%s%s' % (ssl, host, port, path)

            if type == 'post':
                r = requests.post(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            elif type == 'put':
                r = requests.put(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            elif type == 'delete':
                r = requests.delete(url, data=dumps(data), headers=headers, verify=False)
                return r.content

            else:
                try:
                    r = requests.get(url, headers=headers, verify=False)
                    return loads(r.text)
                except:

                    r = requests.get(url, headers=headers, verify=False)

        except Exception as e:

            print 'Failed to fetch url=%s path=%s error %s' % (url, path, e)

print fetch('Series')

What kind of script is this? Python? Bash?

thats a python script.  (its the same a used in htpc manager). Just copy it and saved it to a test_sonarr.py
then call the script from your command line: python test_sonarr.py

root@htpc:/usr/local/HTPC-Manager # python sonarrtest.py
Traceback (most recent call last):
File "sonarrtest.py", line 1, in
import requests
ImportError: No module named requests

Had to install p27-requests, but got the following output
root@htpc:/usr/local/HTPC-Manager # python sonarrtest.py
{u'error': u'Unauthorized'}

And you did edit the apikey?

yes

Replaced '123' with the API key in single quotes

I even got the API from Sonarr directly to confirm

Have you made a new apikey without restarting? I cant find any issues here, if sonarr for some reason returns Unauthorized if your using a correct url and correct key there isnt anyhing i can do about it.

@thejrose1984 did you get it working?

No...

and you did restart sonarr after you got a new api key? I would have posted on their forum, it might be some issues since you running mono. Can other programs you there api?

Did it all...

What do you mean by blank instance?

Move userdata out or rename so HTPC thinks nothing is configured

last thing you can check is sonars config.xml to check the api key. If that is correct you need to make issue/forum post on sonarr. Htpc m is working as it should.


Allow users to contact daikoku admin

Maybe with a chat component

[ ] display a popup in every page to discuss with tenant admin
[ ] send message by mail to tenant admin
[ ] configure webhooks to post user message (slack, teams, discord...)
[ ] admin can respond to question to dispay response in popup


Add rollback for aio setup

ROLLBACK AND CHAIN if the checkpoint migrations table is missing.
I observed the current rollback attempt not to work on an uninitialized data source, because the transaction is left in an error state by the aio carry forward of the standard saver.

Do you have a code snippet of how you're using the setup that makes this necessary?

Thanks for the follow up. In looking at the docs more closely to confirm that I hadn't missed something, I realized of course that I had: the checkpointer assumes psycopg is set to autocommit. With autocommit, this is not needed; I'll close the PR.


Update sbt-mdoc to 2.2.16

Updates org.scalameta:sbt-mdoc from 2.2.4 to 2.2.16.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

labels: sbt-plugin-update, semver-patch

Superseded by #90.


Week2

Pull request week 2. Changed the app style and app layout to a navbarpage with drop down menus. Wordcloud now has color. Added the positive self-image tab where user can enter how likely they think that their desired positive self-image is true as well as see in a graph how that perceived likelihood has changed over time. Users can now save the wordcloud or likelihood graph as a png. Made background functions of some of the code

Hey! This is looking very great! Your code is super neat and understandable! :) Don't forget to add your email adress, also maybe add the other functions like "generate_wordcloud" & "dataloading" into the namespace file with the descriptions as well, so it is clear they are part of your package?


create a way to call a regular function as a global function

This doesn't make sense, functions made to be executed as a global function should be executed in that context and if a part of it should be executed outside of the chain of global functions, it should be free from the context and a separate function.


control + plus doesn't work

It's possible to make this combination. For example try this on firefox:
window.addEventListener("keypress",onWindowKeyPress,true);

function onWindowKeyPress(event) {
    if (event.which==43 && event.ctrlKey == true ) {
        alert("control + plus")
    }

    if (event.which==45 && event.ctrlKey == true ) {
        alert("control +  minus")
    }
}

In firefox, to track this combination is important to associate a callback to this event:
character: +
action: keypress
modifiers: control

The problem is in this function:
getKeyInfo()

I think that it's better:
if (typeof action == "undefined") {
    action = _pickBestAction(key, modifiers);
 }

instead of this:
 action = _pickBestAction(key, modifiers, action);

Because otherwise it's useless to make this binding:
 Mousetrap.bind('ctrl+plus', function() { alert("Control+plus") }, "keypress");

because _pickBestAction() always change the action "keypress" to "keydown".
This change doesn't break the tests.
Also the problem is inside this function: _getMatches().
This condition guives the problem:
 if ((action == 'keypress' && !e.metaKey && !e.ctrlKey) || _modifiersMatch(modifiers, callback.modifiers)) {

With this condition the combination control+plus also triggers pressing only plus.
If this condition is changed to this other one:
 if (_modifiersMatch(modifiers, callback.modifiers)) {

the behaviour is as expected and the mentioned binding to trap "control+plus" works but this last change breaks some tests.

Having the same issue with meta+plus.

The original report notes that Firefox can return the keypress event for ctrl and +.  (As always, + actually is key '=' and shift)
The report then wonders why Mousetrap doesn't handle this combination of key and modifiers.  It mentions (correctly) that Mousetrap is deciding whether to use keydown or keypress events based on the keyboard combination, and possibly overriding the action selection by the caller.
While I can agree that the caller ought to be able to request anything (and then test that request will actually work for their purpose) I'd like to bring up an important consideration.
The comments in Mousetrap note "modifier keys don't work as expected with keypress".  This may reflect an important fact about keypress - that event isn't generated on every key combination.

"... this event must be dispatched when a key is pressed down,
if and only if that key normally produces a character value."

A problem is that ctrl+plus does not normally generate "a character value."  It may be a valid key combination, but as a character, what is it?
Firefox is the only browser that generates a keypress event for this key combination.  Even at that, it is rather confused at what it says when doing so:
    keypress: keyCode=0   which=43("+")  code="Equal"   ctrl shift  key="+"

How can it be an 'Equal' if 'shift' is pressed?  How can it be a '+' if 'ctrl' is pressed?  What 'character' is this?
You can ask for key combinations detectable on keydown events, as Mousetrap is suggesting is 'safe'.  Only normal characters should be specified on keypress events.
.
Is there a reason you needed keypress for this combination, rather than just using the better supported keydown on combinations?
Keyboard handling is the Charybdis of browsers, so it is always best to sail carefully around these events :smile:
.
Below are some traces I captured while trying to understand what was going on.  I traced all events coming into _handleKeyEvent and then also whether bound key combinations were detected.  The browsers are Chrome, Firefox, and Edge.  Note the differing ideas about code and key.  (Chrome's keyIdentifier is not shown)  I believe it is keythat is eventually supposed to replace charCode/keyCode/which/code/etc.  By that mark, then Edge is the most 'modern'.  (!)
          Captured from Chrome (48.0.2564.109 Win US):

    =
keydown   keyCode=187   which=187      code="Equal"
keypress  keyCode=61    which=61("=")  code="Equal"
      Mousetrap callback for  type: keypress    "="
keyup     keyCode=187   which=187      code="Equal"

    +   (aka shift+= )
keydown   keyCode=16    which=16       code="ShiftLeft"   shift
keydown   keyCode=187   which=187      code="Equal"       shift
      Mousetrap callback for  type: keydown     "shift+="
keypress  keyCode=43    which=43("+")  code="Equal"       shift
      Mousetrap callback for  type: keypress    "+"
      Mousetrap callback for  type: keypress    "plus"
keyup     keyCode=187   which=187      code="Equal"       shift
keyup     keyCode=16    which=16       code="ShiftLeft"

    ctrl+=
keydown   keyCode=17    which=17       code="ControlLeft" ctrl
keydown   keyCode=187   which=187      code="Equal"       ctrl
      Mousetrap callback for  type: keydown     "ctrl+="
keyup     keyCode=187   which=187      code="Equal"       ctrl
keyup     keyCode=17    which=17       code="ControlLeft"

    ctrl+shift+=
keydown   keyCode=17    which=17       code="ControlLeft" ctrl
keydown   keyCode=16    which=16       code="ShiftLeft"   ctrl shift
keydown   keyCode=187   which=187      code="Equal"       ctrl shift
      Mousetrap callback for  type: keydown     "ctrl+shift+="
keyup     keyCode=187   which=187      code="Equal"       ctrl shift
keyup     keyCode=16    which=16       code="ShiftLeft"   ctrl
keyup     keyCode=17    which=17       code="ControlLeft"

          Captured from FireFox (44.0.1 Win US):

    =
keydown   keyCode=61    which=61("=")  code="Equal"                   key="="
keypress  keyCode=0     which=61("=")  code="Equal"                   key="="
      Mousetrap callback for  type: keypress "="
keyup     keyCode=61    which=61("=")  code="Equal"                   key="="

    +   (aka shift+= )
keydown   keyCode=16    which=16       code="ShiftLeft"   shift       key="Shift"
keydown   keyCode=61    which=61("=")  code="Equal"       shift       key="+"
      Mousetrap callback for  type: keydown  "shift+="
keypress  keyCode=0     which=43("+")  code="Equal"       shift       key="+"
      Mousetrap callback for  type: keypress "+"
      Mousetrap callback for  type: keypress "plus"
keyup     keyCode=61    which=61("=")  code="Equal"       shift       key="+"
keyup     keyCode=16    which=16       code="ShiftLeft"               key="Shift"

   ctrl+=
keydown   keyCode=17    which=17       code="ControlLeft" ctrl        key="Control"
keydown   keyCode=61    which=61("=")  code="Equal"       ctrl        key="="
      Mousetrap callback for  type: keydown  "ctrl+="
keypress  keyCode=0     which=61("=")  code="Equal"                   key="="  ctrl
keyup     keyCode=61    which=61("=")  code="Equal"       ctrl        key="="
keyup     keyCode=17    which=17       code="ControlLeft"             key="Control"

   ctrl+shift+=
keydown   keyCode=17    which=17       code="ControlLeft" ctrl        key="Control"
keydown   keyCode=16    which=16       code="ShiftLeft"   ctrl shift  key="Shift"
keydown   keyCode=61    which=61("=")  code="Equal"       ctrl shift  key="+"
      Mousetrap callback for  type: keydown  "ctrl+shift+="
keypress  keyCode=0     which=43("+")  code="Equal"       ctrl shift  key="+"
keyup     keyCode=61    which=61("=")  code="Equal"       ctrl shift  key="+"
keyup     keyCode=16    which=16       code="ShiftLeft"   ctrl        key="Shift"
keyup     keyCode=17    which=17       code="ControlLeft"             key="Control"

          Captured from Microsoft Edge 25.10586.0.0

    =
keydown   keyCode=187   which=187                                     key="="
keypress  keyCode=61    which=61("=")                                 key="="
      Mousetrap callback for  type: keypress    "="
keyup     keyCode=187   which=187                                     key="="

    +   (aka shift+= )
keydown   keyCode=16    which=16                          shift       key="Shift"
keydown   keyCode=187   which=187                         shift       key="+"
      Mousetrap callback for  type: keydown     "shift+="
keypress  keyCode=43    which=43("+")                     shift       key="+"
      Mousetrap callback for  type: keypress    "+"
      Mousetrap callback for  type: keypress    "plus"
keyup     keyCode=187   which=187                         shift       key="+"
keyup     keyCode=16    which=16                                      key="Shift"

    ctrl+=
keydown   keyCode=17    which=17                          ctrl        key="Control"
keydown   keyCode=187   which=187                         ctrl        key="Unidentified"
      Mousetrap callback for  type: keydown     "ctrl+="
keyup     keyCode=187   which=187                         ctrl        key="Unidentified"
keyup     keyCode=17    which=17                                      key="Control"

    ctrl+shift+=
keydown   keyCode=16    which=16                          shift       key="Shift"
keydown   keyCode=17    which=17                          ctrl shift  key="Control"
keydown   keyCode=187   which=187                         ctrl shift  key="Unidentified"
      Mousetrap callback for  type: keydown     "ctrl+shift+="
keyup     keyCode=187   which=187                         ctrl shift  key="Unidentified"
keyup     keyCode=17    which=17                          shift       key="Control"
keyup     keyCode=16    which=16                                      key="Shift"


Color emoji not rendered

Are you using the latest version? Is the version currently in use as reported by npm ls sharp the same as the latest version as reported by npm view sharp dist-tags.latest?
Yes<EMAIL_ADDRESS>What are the steps to reproduce?
i tried this code to convert svg to text
<svg height="117" width="512">
 <rect x="0" y="0" width="512" height="117" stroke-width="3px" stroke="white" fill="black" rx="30"/>
 <text x="50%" y="50%" fill="white" font-size="5em" baseline-shift="-25%" lengthAdjust="spacing" textLength="90%" text-anchor="middle">😂</text>
</svg>

i tested it on w3schools.com it shows this

but using sharp i got this

and i installed noto-color-emoji

Hi, this is probably due to an issue with rendering coloured fonts, most likely in cairo as there are a few possible candidates here - https://gitlab.freedesktop.org/cairo/cairo/-/issues?scope=all&utf8=✓&state=opened&search=emoji

Will this issue ever get fixed 🤔 the upstream issue has been open from 2 years now 🤷♂

This is likely to be due to https://gitlab.freedesktop.org/cairo/cairo/-/issues/326

I'm having the same issue and I haven't been able to solve it. I would like to use Twitter Color Emoji rather than noto though. Creating a font.conf with hinting enabled did nothing, and FC_DEBUG=1024 does say the file is being loaded. FC_DEBUG=1 shows a bunch of fonts from the  path, but all of them have hinting set to false.
pango-view doesn't seem to help either. while sharp can render emojis with outline (but no color), pango-view shows no emojis at all.

Any solution to this @lovell ?

I am getting the same issue on sharp. I have tested with noto-color-emoji and with emoji-one on ubuntu 22, but without success.
I have already tried

This is likely to be due to https://gitlab.freedesktop.org/cairo/cairo/-/issues/326

Same issue, in my case pango-view does render color emoji but sharp does not. Have spent multiple hours playing with fontconfig configs and debug vars, as well as different fonts.
The fact that I can get pango-view to render what I want perfectly but not sharp seems to suggest there's a possible bug in the way sharp or perhaps libvips is using pango, right? I don't understand how these components connect well enough to figure out how it's possible that only sharp isn't working...

This is due to that librsvg renders all text as paths to workaround a Pango bug, see for details:
https://gnome.pages.gitlab.gnome.org/librsvg/devel-docs/text_layout.html#emoji-is-broken
So, this issue is currently blocked on https://gitlab.gnome.org/GNOME/librsvg/-/issues/911.
Note that the text operation can be used as an alternative, which should work with colored emoji glyphs after PR https://github.com/lovell/sharp-libvips/pull/228 (sharp v0.33.5).


Add implicit route binding for Model

This PR aims to add implicit route binding for Model.

I like it! The biggest reason I have for liking your approach is the fact that you never have to think about it. You can create a class and instantly bind it in your routing.
I do have a question and it's because I'm curious about your answer and not that I'm saying we should do it my way:
Why do you use this implementation rather than Explicit binding?
The reason I ask is this: Not all models that you create are meant to be full pages. For example, the MetaTag model only exists to set the meta title and description etc. I never want to resolve these in routing or through dependency injection in controllers and methods.

Why do you use this implementation rather than Explicit binding?

The thing with explicit binding is you still have to register it and it can get tedious when you have many models you want to be route bindable.

Not all models that you create are meant to be full pages. For example, the MetaTag model only exists to set the meta title and description etc. I never want to resolve these in routing or through dependency injection in controllers and methods.

Yeah true, but you may also have an admin panel that list,show,create,updates a MetaTag utilizing a ResourceController.

I never want to resolve these in routing or through dependency injection in controllers and methods.

Then just don't. Its not something that must always be done but its an option when needed.

Good points! Thanks for this! :confetti_ball:


Refactor the actorSystem on the SlackApiClient

Would you mind if I submitted a PR that did the following:

Move the actorSystem implicit to the creation of the client,
Add an implicit for the materializer as well (it is heavy weight and shouldn't be recreated upon each request).

I don't mind at all. PR welcome!


Better Material/Texture Settings

Eiyeron on the itch forum suggested improvements to the material setup. These should be relatively simple to implement.

https://imgur.com/a/tWcLE

In the texture settings, put the Filter Size to its minimum (0.10), it avoids getting weird artifacts around the transparent parts (refer to the first and second image in the linked gallery,

Another idea is toggling the Z-Transparency on, to allow transparent parts to overlap opaque ones without having a visual "hole" in the result (refer to the third and fourth pictures)

https://itch.io/t/70286/here-are-some-suggestions

Implemented this.


CREATE EXTENSION ap_pgutils - /usr/lib/postgresql/ap_pgutils.so: undefined symbol: secure_wipe_memory

Hello, I'm trying to install this extension on my Arch Linux x86_64 machine, and after installing some dependencies:

clang15
llvm15

And updating the file GNUmakefile to point to the right PG_HOME, I've finally managed to run the commands make, and make install, successfully.
After that I tried to run CREATE EXTENSION ap_pgutils, and got this error message:
/usr/lib/postgresql/ap_pgutils.so: undefined symbol: secure_wipe_memory
Is it because this extension might not be compatible with my version of Postgres?
Some logs to help:
$ ldd ap_pgutils.so
        linux-vdso.so.1 (0x00007ffe99786000)
        libargon2.so.1 => /usr/lib/libargon2.so.1 (0x00007ff2e37f0000)
        libcrypto.so.3 => /usr/lib/libcrypto.so.3 (0x00007ff2e3200000)
        libc.so.6 => /usr/lib/libc.so.6 (0x00007ff2e301e000)
        /usr/lib64/ld-linux-x86-64.so.2 (0x00007ff2e3834000)

SELECT version();
                                        version
---------------------------------------------------------------------------------------
 PostgreSQL 15.4 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 13.2.1 20230801, 64-bit
(1 row)

Did it dump core? You could run gdb /usr/bin/postgres core then type bt to get a backtrace.
I'm currently on PG 16, the extension fails to build with a different error so I can't reproduce until I fix the issue.

It didn't generate the dump core, but I followed the instructions described here: https://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Linux/BSD#Attaching_gdb_to_the_backend
And I was able to log the error:
$ cat debuglog.txt
Breakpoint 1 at 0x563cdf72a4b0
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00007fa527378edd in ?? () from target:/usr/lib/libc.so.6
Detaching from program: target:/usr/bin/postgres, process 15186
[Inferior 1 (process 15186) detached]

It seems the problem is related to the libc.so.6 lib

I forgot to log the bt command, here is what I got:
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0x00007fa527378edd in ?? () from target:/usr/lib/libc.so.6
(gdb) bt
#0  0x00007fa527378edd in ?? () from target:/usr/lib/libc.so.6
#1  0x00007fa52708c16f in argon2_encodedlen () from target:/usr/lib/libargon2.so.1
#2  0x00007fa52715e58e in pg_argon2 (fcinfo=0x563ce0f65738) at /home/carloshmm/ap_pgutils/ap_pgutils.c:112
#3  0x0000563cdf431c53 in ?? ()
#4  0x0000563cdf51bcbc in evaluate_expr ()
#5  0x0000563cdf51bf5e in ?? ()
#6  0x0000563cdf51cf3f in ?? ()
#7  0x0000563cdf4ada24 in expression_tree_mutator ()
#8  0x0000563cdf4ae514 in expression_tree_mutator ()
#9  0x0000563cdf5003f2 in ?? ()
#10 0x0000563cdf505c1b in subquery_planner ()
#11 0x0000563cdf4ff384 in standard_planner ()
#12 0x0000563cdf5d6566 in pg_plan_query ()
#13 0x0000563cdf5d65d4 in pg_plan_queries ()
#14 0x0000563cdf5d9324 in ?? ()
#15 0x0000563cdf5db933 in PostgresMain ()
#16 0x0000563cdf547f8c in ?? ()
#17 0x0000563cdf54919a in PostmasterMain ()
#18 0x0000563cdf251ac2 in main ()

Yes, this extension was originally written for PG 9.2 and last tested on PG 10. The trace you are showing is an error in calculating the size of the argon2 object, probably a null pointer or such. At this point, considering this is really old code and Apsalar was bought and Singular no longer uses this code, I would advise you instead to use something like PL/PythonU to call argon2_cffi instead. If I ever get to fix this, I will let you know in this ticket.

Thank you, just so you know why I'm looking for this extension after all, its because on my company there is a project using argon2 as a hash mechanism, and I'd like to provide to the db team a way for them to easily generate those hashs directly on PostgreSQL.

I figured. That was our use-case as well, but after the acquisition the source of truth moved from our PostgreSQL to their (shudder) MySQL.


Fixed an issue where the SPM package doesn't compile with Xcode 11.4

After updating to Xcode 11.4, my project is showing the following issue with RxBluetoothKit:
xcodebuild: error: Could not resolve package dependencies:
   target at '/Users/xcode/Library/Developer/Xcode/DerivedData/project-btxgpemzyyretjcousmtwoebmywz/SourcePackages/checkouts/RxBluetoothKit' contains mixed language source files; feature not supported

I've been able to track down the error to the Info.plist file in the Sources folder.
For whatever reason, Xcode 11.4 now doesn't like that there's a file that's not a .swift one. (Xcode 11.3.1 still works fine)
I've included that file in the excluded section in the package description, which solves the issue.

@akmarinov are you sure it's only Info.plist? The Sources folder does also contain RxBluetoothKit.h. I'd say SPM would still consider this as mixed languages. We should exclude this file as well, just in case.

Well, Xcode works in mysterious ways, as the ObjC compatibility header doesn't seem to be an issue in my case.
// swift-tools-version:5.1
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
    name: "TestProject",
    platforms: [
        .iOS("12.4")
    ],
    products: [
        // Products define the executables and libraries produced by a package, and make them visible to other packages.
        .library(
            name: "TestProject",
            targets: ["TestProject"]),
    ],
    dependencies: [
        .package(url: "https://github.com/akmarinov/RxBluetoothKit.git", from: "5.3.1"),
        .package(url: "https://github.com/ReactiveX/RxSwift.git", from: "5.1.0")
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages which this package depends on.
        .target(
            name: "TestProject",
            dependencies: ["RxBluetoothKit", "RxSwift"],
            path: "Sources")
    ]
)

These package dependencies in a test project work without Xcode showing the issue for me, with the RxBluetoothKit.h included.
I'm not sure what the impact of turning off the compatibility header would be for ObjC projects.

excluding it in the SPM package shouldn't be an issue
That's my whole point. :)

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

@DevAndArtist can you approve this pull request? Or who should we ping?
This is a blocker for all of us who use SPM.

@tomovicn I'm just a contributor to the framework (I added some changes to the logging stuff in the past), but not part of Polidea so I can't really approve the PR. Personally I consider this framework as dead and will try to get rid of its dependency in our projects.

It's a shame since it is a very good library. I dropped them a message to see if they still support this project.
Thanks for your response @DevAndArtist


[2.6.2] Incorrect comparison of null values of nullable structures when == is overridden

The compiler does not compares correctly null values of nullable structures when the == operator is overridden.
Demo code below. When the structure overrides the == operator for non-nullable values only then the compiler fails to correctly compare two null values. If the == operator is overridden for both non-nullable and nullable values when the result is correct.
The output of the code below is:
b1 != b2
c1 == c2

Code:
[StructLayout(LayoutKind.Sequential, Size = 1)]
public struct B
{
    readonly int _value;

    public B(int value)
    {
        this._value = value;
    }

    public static bool operator ==(B a, B b)
    {
        return a._value == b._value;
    }

    public static bool operator !=(B a, B b)
    {
        return a._value != b._value;
    }

    public override bool Equals(object o)
    {
        return o is B && (B)o == this;
    }

    public override int GetHashCode()
    {
        return _value.GetHashCode();
    }
}

[StructLayout(LayoutKind.Sequential, Size = 1)]
public struct C
{
    readonly int _value;

    public C(int value)
    {
        this._value = value;
    }

    public static bool operator ==(C a, C b)
    {
        return a._value == b._value;
    }

    public static bool operator !=(C a, C b)
    {
        return a._value != b._value;
    }

    public static bool operator ==(C? a, C? b)
    {
        if (object.ReferenceEquals(a, b))
        {
            return true;
        }
        else if (object.ReferenceEquals(a, null) || object.ReferenceEquals(b, null))
        {
            return false;
        }
        else
        {
            return a.Value._value == b.Value._value;
        }
    }

    public static bool operator !=(C? a, C? b)
    {
        return false == (a == b);
    }

    public override bool Equals(object o)
    {
        return o is C && (C)o == this;
    }

    public override int GetHashCode()
    {
        return _value.GetHashCode();
    }
}

public static class Application
{
    public static void Main()
    {
        Console.WriteLine("Application started.");

        {
            B? b1 = null;
            B? b2 = null;

            if (b1 == b2)
            {
                Console.WriteLine("b1 == b2");
            }
            else
            {
                Console.WriteLine("b1 != b2");
            }
        }

        {
            C? c1 = null;
            C? c2 = null;

            if (c1 == c2)
            {
                Console.WriteLine("c1 == c2");
            }
            else
            {
                Console.WriteLine("c1 != c2");
            }
        }
    }
}

The code compiles to the following:
{
    var b1 = null;
    var b2 = null;
    if (ss.Nullable$1.lift($Test_App_B.op_Equality, b1, b2)) {
	    console.log('b1 == b2');
    }
    else {
	    console.log('b1 != b2');
    }
}
{
    var c1 = null;
    var c2 = null;
    if ($Test_App_C.op_Equality$1(c1, c2)) {
	    console.log('c1 == c2');
    }
    else {
	    console.log('c1 != c2');
    }
}

The issue is the ss.Nullable$1.lift method which returns "null" when any of the arguments is null. It seems its usage is inappropriate in this case.
ss_Nullable$1.lift = function Nullable$lift() {
    for (var i = 0; i < arguments.length; i++) {
	    if (!ss.isValue(arguments[i]))
		    return null;
    }
    return arguments[0].apply(null, Array.prototype.slice.call(arguments, 1));
};

I guess it should return false instead of null for comparison operators, is that what you mean?

This depends on the purpose of the function. If it is used only in the case described then it should check if all arguments are null and return "true" if so. Otherwise, if at least one argument is null then it should return "false". Otherwise, it should call the operator.
In my opinion it should also fail with an exception if the first argument is null (at least in the case described) since it is a function pointer. If compilation is correct though this should never happen so perhaps such a check is not required.
I can create a pull request if you confirm that this function is not used for anything else. It is not invoked anywhere in mscorlib so I assume it is used only by compiled code.

The function is used to lift operators. It currently works as intended for non-comparison operators; any change would need to be made for comparison operators only, and for those I guess different operators have different rules for what should happen if one or both arguments is null.

For comparison operators the rule is that if only one of the operands is null then the result is always false with the exception of the "!=" operator. If both operands are null then the result is always false with the exception of the "==" operator (note that >= and <= also return false when both values are null).
I assume that a different function should be used for comparison operators since it is not possible to detect the type of the operator in the current implementation.


Sentry not working on specific domain

Hi,
I have two different servers running the same Symfony application, one is my developement/testing server, the second is the production server.
I installed sentry using the bundle following the instructions given in the documentation, but i'm only receiving errors from the test server, no errors seems to be sent from the production server.
Months ago, sentry worked fine on the two domains, and we didn't change anything.
I tried to install Sentry via monolog too, but the problem persists : we only get errors from the testing server.
Does anyone have an idea what could be wrong ?
Thanks

Have you inspected the configuration for differences? Maybe you have different error_reporting settings?

I only configured the bundle adding my dsn to the config.yml file on my two projects, not setting anything else should use default configuration, right ?

Yes, but you would have to check the server configuration. Also, do you have a reproducible way to trigger an error on both systems? Are you sure that both server can talk to the Sentry one without issues?

Yes we have a kind of "hidden" error on the project, on the two servers, when I trigger it on my testing server i get the error on sentry, but not when I do it on the production server.
I though sentry was code based and no server configuration could change it, what part of my server configuration do you recommend me to check ?
thanks for your responses

I just checked, php.ini error_reporting settings are the same on the two server, this isn't the source of my problem.
Isn't calling the Sentry reporting manually in a controller like you recommend send only the error implemented in this controller ? I would like all my errors by Sentry, without having to define every possible error manually..

Nope, I was just suggesting a way to reproduce the issue in a controlled way: write a controller that sends something to Sentry, to rule out any possible misconfiguration or issue on the Sentry's side.

Okay, thanks for the hint.
As you said, I writed a controller to send a custom msg to Sentry : I tested it in local mode, it worked. I tested it on my development server, it worked. But, when I tested it on my production server it didn't work..

It seems clear to me that, apart from possible mistakes while deploying to your prod server, it's the server's (configuration) fault.
I'll close this since it's not a bug of this bundle, but feel free to reply further.

Okay thanks ! So now it's clear that the problem is on my side and not Sentry/Raven's side ?
The deployment is OK, so it should be server's fault.
I'm using nginx, i'm going to check the differences between my configuration and the recommended configuration for nginx provided by the documentation ( https://docs.sentry.io/server/nginx/ )
I'll keep you tuned.
Thanks you !

the only thing i can't understand is that my nginx config is the same on my development server and production server..

Do you think installing the sentry server on my server via Docker could solve the problem or the problem will still persist ?


Issue reference to commands as gi connected with lsp

After installation I found issue, I don't find any solution for is. Maybe this is appearing for some one else.

This shows in all languages.
My lsp settings
https://gist.github.com/mkubasz/108e78010607d18d5072f1e362347d78
Logs:
gh.log

The setup is not correct
should be
require'navigator'.setup({
    lsp={
        disable_lsp = {'tsserver','pyright'},
    }
    debug = false
})

You can double check that you have multiple LSP enabled by run LspInfo

@ray-x Thanks!!! And this mean that navigator will be disabled for this two lsps? Or there is a possibility to use navigator with own settings? Like with vim.cmd("autocmd FileType guihua tsserver require('cmp').setup.buffer { enabled = false }") ?

{lsp={ disable_lsp = {'tsserver','pyright'}} }

This will disable tsserver and pyright
You can have your own settings, e.g
{
lsp = {
  gopls = {
    on_attach = function(client)
      print("gopls attached")
      client.resolved_capabilities.document_formatting = false -- efm
    end,
   cmd = {
     "gopls", -- share the gopls instance if there is one already
     "-remote=auto",
     "-logfile=auto",
     "-rpc.trace",
   },

   settings = {
     gopls = {gofumpt = true} -- enable gofumpt etc,
   }
  },
}
}

Thanks :)


Update messages.json

I did some revisions. More to come

Gets a 👍 from me. Thanks @annieleblond!


feature required: support heic image

This package is dependent on image,Too bad it doesn't support HEIC.
https://github.com/brendan-duncan/image/issues/407


Add Replicate demo

Hey @dome272 ! 👋
Thank for this cool model. It's the fastest diffusion model I encountered and can be very usefull!
This pull request makes it possible to run your model inside a Docker environment, which makes it easier for other people to run it.  We're using an open source tool called Cog to make this process easier.
This also means we can make a web page where other people can run your model! View the models for each capability here:

https://replicate.com/arielreplicate/paella_fast_text2image
https://replicate.com/arielreplicate/paella_fast_outpainting
https://replicate.com/arielreplicate/paella_fast_image_variation
https://replicate.com/arielreplicate/paella_fast_image_interpolation

Replicate also have an API, so people can easily run your model from their code:
import replicate
model = replicate.models.get("[arielreplicate/paella_fast_text2image]")
model.predict(...)

If you'd like to modify the Replicate page, let me know and I can transfer ownership to your account.
In case you're wondering who I am, I'm from Replicate, where we're trying to make machine learning reproducible. We got frustrated that we couldn't run all the really interesting ML work being done. So, we're going round implementing models we like. 😊

That is so cool. Sorry for replying so late, but I really like it. Hopefully, we can hook up some more powerful models soon.


Add data-top attribute to modals

Last opened modal has data attr data-top="true", rest has data-top="false". When the top modal is closed, the previous one receive attr data-top="true".
It is helpfull for nested modals, you can select the top modal and the rest modals by CSS clasess.
.modal.show[data-top="true"] {}
.modal.show[data-top="false"] {}

I really appreciate, if you approve these changes, or modify with the same result. Thank you!

It is possible to do by override methods like is it mention here https://github.com/react-bootstrap/react-bootstrap/issues/6472


[BUG] Line chart renders incorrectly with fixed scales and data points that fall outside of the specified range

Current Behavior
If the scale is fixed, e.g:
yAxes: [{ticks: {
    min: 0,
    max: 25
}}];

data points that fall outside of this range cause a line to be drawn outside of the chart (interactive example). This obstructs axes labels and the chart title.

I have also tried this without the angular wrapper and the same behaviour occurs.
Expected Behavior
Ensure lines cannot be drawn beyond the chart area, so that the title and axes labels are not obstructed.
Environment

Chart.js version: 2.3.0
Angular Chart.js 1.0.3
Browser name and version: Chrome Version 54.0.2840.71 (64-bit)

This is the same issue as #2873
For some context, we initially had clipping to make this work nicely, but it caused problems with points getting cut off. We need to find a more advanced way of doing this and filtering out the points to not draw.
One challenge is what the behaviour should be with lines to points outside the chart area. Should we simply cut the line or find the intersection point with the edge of the chart area and draw the line to there.

Thanks @etimberg - i'll check out the zoom plugin. It would be useful to have this out the box, but I guess you want to keep the main library as lightweight as possible. I noticed you added the 2.5 milestone - I'll re visit when this is released.

Sounds good. The zoom plugin does have the original clipping (the one we removed due to other problems).
We are very close to releasing 2.4 and I hope to get the clipping implemented better for 2.5 :)


Update azure-netapp-files-configure-export-policy.md

Allowed clients field supports comma separated IP or Subnet, I am requesting to update document with example I have entered . This is important for customer to know, since export policy supports only 5 rules.

@bhaktajb : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@bhaktajb - Thanks for the input.  I'm running the change by our technical owner will get back as soon as I hear.

@bhaktajb - Apologies for the extended delay.  I'm still waiting for our technical experts to confirm/approve this change.

Hi Julie,
No worries. I have one more suggestion and will submit change later this week.
Thanks,
Jayesh Bhakta
Cloud Solutions Architect - West Majors
Azure Netapp Filesmailto:https://azure.microsoft.com/en-us/services/netapp/
t:<PHONE_NUMBER>
e: jayesh.bhakta<EMAIL_ADDRESS>From: Julie Chen<EMAIL_ADDRESS>Sent: Tuesday, November 10, 2020 2:18 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Bhakta, Jayesh<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] Update azure-netapp-files-configure-export-policy.md (#65303)
NetApp Security WARNING: This is an external email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
@bhaktajbhttps://github.com/bhaktajb - Apologies for the extended delay. I'm still waiting for our technical experts to confirm/approve this change.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/pull/65303#issuecomment-725001054, or unsubscribehttps://github.com/notifications/unsubscribe-auth/APJBCRI6LZSXMWZA75Z4GITSPG3ZFANCNFSM4TFHQPLA.

#sign-off

@bhaktajb, @ktoliver - Not sure if I'm able to trigger the sign-off on this PR.  If not, please go ahead and note "#sign-off" for the merge.  Thanks.

@b-juche Got it. I made a few edits for Microsoft style while I edited the update that is submitted in the PR.
@bhaktajb - Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, we'll merge your pull request. Thanks!

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add dependency cruiser with initial rules

[x] Use recommended settings, no orphans, no circular deps
[x] Prevent packages from importing from apps
[x] Run on CI

Completed in https://github.com/leather-wallet/mono/issues/15


sb3_procgen_model

I print out the 'self.metric_values' in 'update_on_episode function', each value of 'my_custom_function_2' is exactly the same as the value when the 'end_status' is <StepStatus.DEATH: 1> in 'test_output.log'. I think this shows custom_metric can track the value during traning.


MGDOBR-1004 : Maintain single Kubernetes profile

https://issues.redhat.com/browse/MGDOBR-1004
PR owner checklist
Please make sure that your PR meets the following requirements:

[ ] Your code is properly formatted according to this configuration.
Run mvn clean verify -DskipTests so that imports are correctly set.
[ ] Your commit messages are clear and reference the JIRA issue e.g: "[MGDOBR-1] - $clear_explanation_of_what_you_did"
[ ] The layers in the kustomize folder have been updated accordingly.
[ ] All new functionality is tested
[ ] Pull Request title is properly formatted: MGDOBR-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

PR reviewer(s) checklist

[ ] Check if code and Github action workflows have been modified and if the modification is safe
[ ] If the modification is safe, add the safe to test label

How to trigger pipelines and use the bots:

Run the end to end pipeline
Annotate the pull request with the label: safe to test. If you want to run the pipeline again, remove and add it again.

Rebase the pull request
Comment with: /rebase.

Deploy BOT
Comment with `/deploy <dev,stable> when the PR has been merged to deploy to a target environment.

I guess you need to update shard-run.sh to specify the properties you removed from application.properties like the webhook account id

done

depends on https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/1072

closing in favour of https://github.com/5733d9e2be6485d52ffa08870cabdee0/sandbox/pull/1079


Can't create custom injector

Hi, I'm trying to test creating a custom injector but can't seem to get it working.  I created a file dlf-injector.js and placed it in the root of my project's directory.
Issue
handle method is not called.
Expected Behavior
Response to proxied API is the object with the "Hello World" text in the handle method below.
.krasrc
{
  "injectors": {
    "dlf": {
      "active": true
    },
    "script": {
      "active": true,
      "directory": "db/"
    },
    "har": {
      "active": true,
      "directory": "db/",
      "delay": false
    },
    "json": {
      "active": true,
      "directory": "db/"
    },
    "proxy": {
      "active": true
    },
    "store": {
      "active": false,
      "directory": "db/"
    }
  }
}

This is the code for dlf-injector.js.
class DLFInjector {
    constructor(options, config, server) {

    }

    get name() {
        return 'dlf-injector';
    }
    get active() {
        return true
    }

    getOptions() {
        return {};
    }
    setOptions(options) {
    }

    handle(req) {
        return {
          test: "Hello World"
       }
    }
}

exports.default = DLFInjector

The code and everything in it looks fine. I'll investigate. Gimme some minutes.

Hmm weird it's working for me now. Not sure what I changed. I'll close the issue for now and I'll reopen if it comes up again.

So the resolution is in general working fine, but we potentially need a target (or improve that resolution on the piral-injector / pilet-injector in the context of Piral).
Reason: The piral-injector assumes full SPA mode. As such any URL that cannot be resolved will be redirected to index.html. Since injectors are usually isolated they make that decision without knowing that another injector may have a proper response here (this gets, however, tricky with a proxy injector - it will try to proxy all URLs and even if the response is 404 that 404 may be a 404 that should be returned; not a 404 that indicates "wrong URL keep trying", but rather "resource not found, please report back").
I changed my config to be:
{
  "injectors": {
    "dlf": {
      "active": true
    },
    "script": {
      "active": true,
      "directory": "db/"
    },
    "har": {
      "active": true,
      "directory": "db/",
      "delay": false
    },
    "json": {
      "active": true,
      "directory": "db/"
    },
    "proxy": {
      "active": false
    },
    "store": {
      "active": false,
      "directory": "db/"
    }
  },
  "map": {
      "/api": "http://foo"
  }
}

Now that target (/api) is quite arbitrary. I just made it to proof that now requests to /api/foo are really seen by the custom injector. The URL is irrelevant as it would be only used by the proxy injector.
I guess there is room for improvement in the piral custom injectors.


Reduction example

Initial (not complete) reduction example implementation. I have modified validation such that the number of compared elements can be restricted.

Looks good,
one thing which I would perhaps change is to offer both versions of setValidationMethod() in API. Ie. both:
setValidationMethod(const ValidationMethod&, const double)
and
setValidationMethod(const ValidationMethod&, const double, const size_t)
so that it will be easy to create future extensions without changing the API.

I think we now can move reduction example into development branch, it seems stable.


reverve-list->vector in (liii vector) and (srfi srfi-133)

(reverse-list->vector proper-list) -> vector
Like list->vector, but the resulting vector contains the elements in reverse of proper-list.
see also proper-list? in (liii list)

closed by #122


Ensure that Dash for R properly supports arbitary file extensions within components

As provided by plotly/dash#481 for the Python version of the backend, Dash for R should support a range of mimetypes for component library assets, such as fonts (for example).

Resolved by #186; closing.


Created a template for the user streams page

Ported the user streams page to use our template, + little syling to look nice

Hey @alonweissfeld , No it probably fails the tests. But once this PR will be approved I'll create a new one for the updated tests.
About the pictures, sure, you're right, ill post them here


Support for stored procedurees

Do you support stored procedures? If yes, which test should i see.

There is no direct support for stored procedures.
The best you can do is use custom queries or the verbatim function, see
tests/CustomQuery.cpp
tests/Update.cpp
for instance.

Thanks, i am trying something cool using your framework to cache data to redis for buchbinder.de as test proof of concept.

What i miss is how can i avoid injection.
if i use sql::verbatim i can use string format with std::format or boost::format, it might work but it doesnt enforce types. What i would like to see is a parameter query, is it possible something like,
std::string param1 = "1";
int param2 = 2;
auto query = custom_query(sqlpp::verbatim<std::string, std::int>( "CALL SupplierQuote(@param1,@param2)" , param1, param2);
db(query);
Or something similar?

For the moment i solved with boost::format.


fix(deps): update rust crate clap to v4

This PR contains the following updates:

Package
Type
Update
Change

clap
dependencies
major
3.2.22 -> 4.0.8

Release Notes

clap-rs/clap
v4.0.8
Compare Source
Fixes

(derive) Remove a low-value assert preventing defaulting Help and Version actions

v4.0.7
Compare Source
Features

(derive) Populate implicit ArgGroup (#3165)

Fixes

(derive) Support #[group(skip)] on Parser derive
(derive) Tell users about implicit arg groups when running into group name conflicts
(error) Don't report unrelated groups in conflict or requires errors

v4.0.6
Compare Source
Features

(derive) Support `#[group(skip)] (#4279, #4301)

v4.0.5
Compare Source
v4.0.4
Compare Source
Fixes

(error) Specialize the self-conflict error to look like clap v3

v4.0.3
Compare Source
Fixes

(error) Quote literals consistently
(error) Stylize escape (--) suggestions
(error) Format help flag as a literal

v4.0.2
Compare Source
Fixes

(parser) SetFalse should conflict with itself like SetTrue and Set
(parser) Allow one-off overrides

v4.0.1
Compare Source
Fixes

(derive) Ensure #[clap(...)] attribute still works

v4.0.0
Compare Source
Highlights
Arg::num_args(range)
Clap has had several ways for controlling how many values will be captured without always being clear on how they interacted, including

Arg::multiple_values(true)
Arg::number_of_values(4)
Arg::min_values(2)
Arg::max_values(20)
Arg::takes_value(true)

These have now all been collapsed into Arg::num_args which accepts both
single values and ranges of values.  num_args controls how many raw arguments
on the command line will be captured as values per occurrence and independent
of value delimiters.
See Issue 2688 for more background.
Polishing Help
Clap strives to give a polished CLI experience out of the box with little
ceremony.  With some feedback that has accumulated over time, we took this
release as an opportunity to re-evaluate our --help output to make sure it is
meeting that goal.
In doing this evaluation, we wanted to keep in mind:

Whether other CLIs had ideas that make sense to apply
Providing an experience that fits within the rest of applications and works across all shells

Before:
git
A fictional versioning CLI

USAGE:
    git <SUBCOMMAND>

OPTIONS:
    -h, --help    Print help information

SUBCOMMANDS:
    add      adds things
    clone    Clones repos
    help     Print this message or the help of the given subcommand(s)
    push     pushes things
    stash

After:
A fictional versioning CLI

Usage: git <COMMAND>

Commands:
  clone  Clones repos
  push   pushes things
  add    adds things
  stash
  help   Print this message or the help of the given subcommand(s)

Options:
  -h, --help  Print help information

name/version header was removed because we couldn't justify the space it occupied when

Usage already includes the name
--version is available for showing the same thing (if the program has a version set)

Usage was dropped to one line to save space
Focus is put on the subcommands
Headings are now Title case
The more general term "command" is used rather than being explicit about being "subcommands"
The output is more dense with the expectation that it won't affect legibility but will allow more content
We've moved to a more neutral palette for highlighting elements (not highlighted above)

In talking to users, we found some that liked clap's man-like experience.
When deviating from this, we are making the assumption that those are more
power users and that the majority of users wouldn't look as favorably on being
consistent with man.
See Issue 4132 for more background.
More Dynamicism
Clap's API has focused on &str for performance but this can make
dealing with owned data difficult, like #[arg(default_value_t)] generating a
String from the default value.
Additionally, to avoid ArgMatches from borrowing (and for some features we
decided to forgo), clap took the &str argument IDs and hashed them.  This
prevented us from providing a usable API for iterating over existing arguments.
Now clap has switched to a string newtype that gives us the flexibility to
decide whether to use &'static str, Cow<'static, str> for fast dynamic behavior, or
Box<str> for dynamic behavior with small binary size.
As an extension of that work, you can now call ArgMatches::ids to iterate
over the arguments and groups that were found when parsing.  The newtype Id
was used to prevent some classes of bugs and to make it easier to understand
when opaque Ids are used vs user-visible strings.
Clearing Out Deprecations
Instead of doing all development on clap 4.0.0, we implemented a lot of new features during clap 3's development, deprecating the old API while introducing the new API, including:

Replacing the implicit behavior for args when parsing them with ArgAction
Replacing various one-off forms of value validation with the ValueParser API

Allowing derives to automatically do the right thing for PathBuf (allowing invalid UTF-8)

Replacing AppSettings and ArgSettings enums with getters/setters
Clarifying terms and making them more consistent

Migrating
Steps:

Upgrade to v3 if you haven't already
Add CLI tests (including example below), -h and --help output at a minimum (recommendation: trycmd for snapshot testing)
If using Builder API: Explicitly set the arg.action(ArgAction::...) on each argument (StoreValue for options and IncOccurrences for flags)
Run cargo check --features clap/deprecated and resolve all deprecation warnings
Upgrade to v4
Update feature flags

If default-features = false, run cargo add clap -F help,usage,error-context
Run cargo add clap -F wrap_help unless you want to hard code line wraps

Resolve compiler errors
Resolve behavior changes (see "subtle changes" under BREAKING CHANGES)
At your leisure: resolve new deprecation notices

Example test (derive):

#[derive(clap::Parser)]
struct Cli {
    ...
}

#[test]
fn verify_cli() {
    use clap::CommandFactory;
    Cli::command().debug_assert()
}

Example test (builder):
fn cli() -> clap::Command {
    ...
}

#[test]
fn verify_cli() {
    cli().debug_assert();
}

Note: the idiomatic / recommended way of specifying different types of args in the Builder API has changed:
Before
.arg(Arg::new("flag").long("flag"))  # --flag
.arg(Arg::new("option").long("option").takes_value(true))  # --option <option>

After:
.arg(Arg::new("flag").long("flag").action(ArgAction::SetTrue))  # --flag
.arg(Arg::new("option").long("option"))  # --option <option>

In particular, num_args (the replacement for takes_value) will default appropriately
from the ArgAction and generally only needs to be set explicitly for the
other num_args use cases.
Breaking Changes
Subtle changes (i.e. compiler won't catch):

arg! now sets one of (#3795):

ArgAction::SetTrue, requiring ArgMatches::get_flag instead of ArgMatches::is_present
ArgAction::Count, requiring ArgMatches::get_count instead of ArgMatches::occurrences_of
ArgAction::Set, requiring ArgMatches::get_one instead of ArgMatches::value_of
ArgAction::Append, requiring ArgMatches::get_many instead of ArgMatches::values_of

ArgAction::Set, ArgAction::SetTrue, and Arg::Action::SetFalse now
conflict by default to be like ArgAction::StoreValue and
ArgAction::IncOccurrences, requiring cmd.args_override_self(true) to override instead (#4261)
By default, an Args default action is ArgAction::Set, rather than ArgAction::IncOccurrence to reduce confusing magic through consistency (#2687, #4032, see also #3977)
mut_arg can no longer be used to customize help and version arguments, instead disable them (Command::disable_help_flag, Command::disable_version_flag) and provide your own (#4056)
Removed lifetimes from Command, Arg, ArgGroup, and PossibleValue, assuming 'static.  string feature flag will enable support for Strings (#1041, #2150, #4223)
arg!(--flag <value>) is now optional, instead of required.  Add .required(true) at the end to restore the original behavior (#4206)
Added default feature flags, help, usage and error-context, requiring adding them back in if default-features = false (#4236)
(parser) Always fill in "" argument for external subcommands to make it easier to distinguish them from built-in commands (#3263)
(parser) Short flags now have higher precedence than hyphen values with Arg::allow_hyphen_values, to be consistent with Command::allow_hyphen_values (#4187)
(parser) Arg::value_terminator must be its own argument on the CLI rather than being in a delimited list (#4025)
(help) Line wrapping of help is now behind the existing wrap_help feature flag, either enable it or hard code your wraps (#4258)
(help) Make DeriveDisplayOrder the default and removed the setting.  To sort help, set next_display_order(None) (#2808)
(help) Subcommand display order respects Command::next_display_order instead of DeriveDisplayOrder and using its own initial display order value (#2808)
(help) Subcommands are now listed before arguments.  To get the old behavior, see Command::help_template (#4132)
(help) Help headings are now title cased, making any user-provided help headings inconsistent.  To get the old behavior, see Command::help_template, Arg::help_heading, and Command::subcommand_help_heading (#4132)
(help) "Command" is used as the section heading for subcommands and COMMAND for the value name.  To get the old behavior, see  Command::subcommand_help_heading and Arg::subcommand_value_name (#4132, #4155)
(help) Whitespace in help output is now trimmed to ensure consistency regardless of how well a template matches the users needs. (#4132, #4156)
(help) name/version/author are removed by default from help output.  To get the old behavior, see Command::help_template. (#4132, #4160)
(help) Indentation for second-line usage changed. (#4132, #4188)
(env) Parse --help and --version like any ArgAction::SetTrue flag (#3776)
(derive) Leave Arg::id as verbatim casing, requiring updating of string references to other args like in conflicts_with or requires (#3282)
(derive) Doc comments for ValueEnum variants will now show up in --help (#3312)
(derive) When deriving Args, and ArgGroup is created using the type's name, reserving it for future use (#2621, #4209)
(derive) next_help_heading can now leak out of a #[clap(flatten)], like all other command settings (#4222)

Easier to catch changes:

Looking up a group in ArgMatches now returns the arg Ids, rather than the values to reduce overhead and offer more flexibility. (#4072)
Changed Arg::number_of_values (average-across-occurrences) to Arg::num_args (per-occurrence) (raw CLI args, not parsed values) (#2688, #4023)

num_args(0) no longer implies takes_value(true).multiple_values(true) (#4023)
num_args(1) no longer implies multiple_values(true) (#4023)
Does not check default or env values, only what the user explicitly passes in (#4025)
No longer terminates on delimited values (#4025)

Replace Arg::min_values (across all occurrences) with Arg::num_args(N..) (per occurrence) to reduce confusion over different value count APIs (#4023)
Replace Arg::max_values (across all occurrences) with Arg::num_args(1..=M) (per occurrence) to reduce confusion over different value count APIs  (#4023)
Replace Arg::multiple_values(true) with Arg::num_args(1..) and Arg::multiple_values(false) with Arg::num_args(0) to reduce confusion over different value count APIs  (#4023)
Replace Arg::takes_value(true) with Arg::num_args(1) and Arg::takes_value(false) with Arg::num_args(0) to reduce confusion over different value count APIs
Remove Arg::require_value_delimiter, either users could use Arg::value_delimiter or implement a custom parser with TypedValueParser as it was mostly to make multiple_values(true) act like multiple_values(false) and isn't needed anymore (#4026)
Arg::new("help") and Arg::new("version") no longer implicitly disable the
built-in flags and be copied to all subcommands, instead disable
the built-in flags (Command::disable_help_flag,
Command::disable_version_flag) and mark the custom flags as global(true). (#4056)
Arg::short('h') no longer implicitly disables the short flag for help,
instead disable
the built-in flags (Command::disable_help_flag,
Command::disable_version_flag) provide your own Arg::new("help").long("help").action(ArgAction::Help).global(true). (#4056)
ArgAction::SetTrue and ArgAction::SetFalse now prioritize Arg::default_missing_value over their standard behavior (#4000)
Changed Arg::requires_ifs and Arg::default_value*_ifs* to taking an ArgPredicate, removing ambiguity with None when accepting owned and borrowed types (#4084)
Removed PartialEq and Eq from Command so we could change external subcommands to use a ValueParser (#3990)
Various Arg, Command, and ArgGroup calls were switched from accepting &[] to [] via IntoIterator to be more flexible (#4072)
Arg::short_aliases and other builder functions that took &[] need the & dropped (#4081)
ErrorKind and Result moved into the error module
ErrorKind::EmptyValue replaced with ErrorKind::InvalidValue to remove an unnecessary special case (#3676, #3968)
ErrorKind::UnrecognizedSubcommand replaced with ErrorKind::InvalidSubcommand to remove an unnecessary special case (#3676)
Changed the default type of allow_external_subcommands from String to OsString as that is less likely to cause bugs in user applications (#3990)
(help) Command::render_usage now returns a StyledStr (#4248)
(derive) Changed the default for arguments from parse to value_parser, removing parse support (#3827, #3981)

#[clap(value_parser)] and #[clap(action)] are now redundant

(derive) subcommand_required(true).arg_required_else_help(true) is set instead of SubcommandRequiredElseHelp to give more meaningful errors when subcommands are missing and to reduce redundancy (#3280)
(derive) Remove arg_enum attribute in favor of value_enum to match the new name (we didn't have support in v3 to mark it deprecated) (#4127)
(parser) Assert when the CLI looksup an unknown args when external subcommand support is enabled to help catch bugs (#3703)
(assert) Sometimes Arg::default_missing_value didn't require num_args(0..=N), now it does (#4023)
(assert) Leading dashes in Arg::long are no longer allowed (#3691)
(assert) Disallow more value_names than num_args (#2695)
(assert) Always enforce that version is specified when the ArgAction::Version is used
(assert) Add missing #[track_caller]s to make it easier to debug asserts
(assert) Ensure overrides_with IDs are valid
(assert) Ensure no self-overrides_with now that Actions replace it
(assert) Ensure subcommand names are not duplicated
(assert) Assert on mut_arg receiving an invalid arg ID or mut_subcommand receiving an invalid command name

Compatibility
MSRV is now 1.60.0
Deprecated

Arg::use_value_delimiter in favor of Arg::value_delimiter to avoid having multiple ways of doing the same thing
Arg::requires_all in favor of Arg::requires_ifs now that it takes an ArgPredicate to avoid having multiple ways of doing the same thing
Arg::number_of_values in favor of Arg::num_args to clarify semantic differences
default_value_os, default_values_os, default_value_if_os, and default_value_ifs_os as the non _os variants now accept either a str or an OsStr (#4141)
Arg::env_os in favor of Arg::env
Command::dont_collapse_args_in_usage is now the default (#4151)
Command::trailing_var_arg in favor of Arg::trailing_var_arg to make it clearer which arg it is meant to apply to (#4187)
Command::allow_hyphen_values in favor of Arg::allow_hyphen_values to make it clearer which arg it is meant to apply to (#4187)
Command::allow_negative_numbers in favor of Arg::allow_negative_numbers to make it clearer which arg it is meant to apply to (#4187)
(help) Deprecated Command::write_help and Command::write_long_help in favor of Command::render_help and Command::render_long_help (#4248)
(derive) structopt and clap attributes in favor of the more specific command, arg, and value to open the door for more features and clarify relationship to the builder (#1807, #4180)
(derive) #[clap(value_parser)] and #[clap(action)] defaulted attributes (its the default) (#3976)

Behavior Changes

(help) With wrap_help feature, if the terminal size cannot be determined, LINES and COLUMNS variables are used (#4186)

Features

Arg::num_args now accepts ranges, allowing setting both the minimum and maximum number of values per occurrence (#2688, #4023)
Allow non-bool value_parsers for ArgAction::SetTrue / ArgAction::SetFalse (#4092)
Add From<&OsStr>, From<OsString>, From<&str>, and From<String> to value_parser! (#4257)
Allow resetting most builder methods
Can now pass runtime generated data to Command, Arg, ArgGroup, PossibleValue, etc without managing lifetimes with the string feature flag (#2150, #4223)
New default error-context, help and usage feature flags that can be turned off for smaller binaries (#4236)
Added StyledStr::ansi() to Display with ANSI escape codes (#4248)
(error) Error::apply for changing the formatter for dropping binary size (#4111)
(error) Error::renderfor formatting the error into a StyledStr
(help) Show PossibleValue::help in long help (--help) (#3312)
(help) New {tab} variable for Command::help_template (#4161)
(help) Command::render_help and Command::render_long_help for formatting the error into a StyledStr (#3873, #4248)
(help) Command::render_usage now returns a StyledStr (#4248)

Fixes

Verify required is not used with conditional required settings (#3660)
Replaced cmd.allow_invalid_for_utf8_external_subcommands with cmd.external_subcommand_value_parser (#3733)
Arg::default_missing_value now applies per occurrence rather than if a value is missing across all occurrences (#3998)
arg!(--long [value]) to accept 0..=1 per occurrence rather than across all occurrences, making it safe to use with ArgAction::Append (#4001)
Allow OsStrs for Arg::{required_if_eq,required_if_eq_any,required_if_eq_all} (#4084)
(help) With wrap_help feature, if the terminal size cannot be determined, LINES and COLUMNS variables are used (#4186)
(help) Use Command::display_name in the help title rather than Command::bin_name
(help) Show when a flag is ArgAction::Count by adding an ... (#4003)
(help) Use a more neutral palette for coloring (#4132, #4117)
(help) Don't rely on ALL CAPS for help headers (#4132, #4123)
(help) List subcommands first, focusing the emphasis on them (#4132, #4125)
(help) Do not include global args in cmd help help (#4131)
(help) Use [positional] in list when relevant (#4144)
(help) Show all [positional] in usage (#4151)
(help) Polish up subcommands by referring to them as commands (#4132, #4155)
(help) Trim extra whitespace to avoid artifacts from different uses of templates (#4132, #4156)
(help) Hint to the user the difference between -h / --help when applicable (#4132, #4159)
(help) Shorten help by eliding name/version/author (#4132, #4160)
(help) When short help is long enough to activate next_line_help, don't add blank lines (#4132, #4190)
(help) Make help output more dense (reducing horizontal whitespace) (#4132, #4192)
(help) Separate subcommand flags with "," like option flags (#4232, #4235)
(help) Quote the suggested help flag (#4220)
(version) Use Command::display_name rather than Command::bin_name (#3966)
(parser) Always fill in "" argument for external subcommands (#3263)
(parser) Short flags now have higher precedence than hyphen values with Arg::allow_hyphen_values, like Command::allow_hyphen_values (#4187)
(parser) Prefer InvalidSubcommand over UnknownArgument in more cases (#4219)
(derive) Detect escaped external subcommands that look like built-in subcommands (#3703)
(derive) Leave Arg::id as verbatim casing (#3282)
(derive) Default to #[clap(value_parser, action)] instead of #[clap(parse)] (#3827)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

Ignore


strange behavior on group

[ ] Add to an appropriate Epic.

Tester (if different from issue creator):
Site: hcommons-dev.org
URL: https://hcommons-dev.org/groups/shelley-appreciation-group/members/
Test Account: hctester40
Area (CORE, sites, profiles, groups, general): groups
If issue discovered on dev, does it also exist on prod? No
Describe the issue
I created this group using a test user (I believe that user was expunged). Now the admin is a real user who has no access to dev. Not sure how this happened, but we might want to see if we can figure it out. I believe it was either hctester90 or hctester100.
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.
Optional details, if they seem relevant
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.

Weird quirk of syncing from prod to dev.


Can we display container name rather than image name in the visualizer?

@deanmax   Container names in Swarm Mode are not that interesting. However, service name might be more interesting. Is that what you're going for?

@ManoMarks, what I want to see in the visualizer is the service name that I manually specified when creating the service. For now only image name of the service is displayed on the visualizer dashboard.

SGTM

+1 service name. I have multiple services all using the same container and container tag.

Running docker service create --name my-test-service memcached will produce the following:

#38


Add react-static-plugin-typescript to plugin list

Description
I created react-static-plugin-typescript; this PR adds it to the list of plugins.
Note: on Twitter I mentioned wanting to give this a more thorough run-through on my own project, but since I'm stuck on upgrading that I figured I'd submit this anyway, since it otherwise appears to work fine.
Changes/Tasks

[x] Updated plugin list in README

Motivation and Context
It tells people who want to use TypeScript which plugin they can use.
Types of changes

[ ] Refactoring/add tests (refactoring or adding test which isn't a fix or add a feature)
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My change requires a change to the documentation.

[x] I have updated the documentation accordingly.

[ ] My changes have tests around them

@Vinnl how far are you using typescript with react-static?
Im failing use typescript in every aspect:
static.config.ts wont work (babel is not already in place here)
src/index.tsx wont work (file resolutions is weak here)
do you have an example repo where you use typescript completely?

@digitalkaoz I'm only using it for my own app code, so the React Static config is still static.config.ts. I think #978 should make it possible to use a .ts extension for your React Static config if you're running it using ts-node, but I haven't tried that myself.
An example can be seen if you initialise a new React Static application using the TypeScript template. That doesn't enable TypeScript for static.config.js, but does run successfully for all the rest.


Allow multiple TypedHandlers handling the same MessageType

Actual Behavior
Consumers can configure only one Typed Handler to handle the same message type.
For example, the code below would throw an exception:
... Bootstrapper
.AddMiddlewares(middlewares => middlewares.AddTypedHandlers(
                      handlers => handlers
                              .AddHandler<MessageHandler>()
                              .AddHandler<OtherMessageHandler>()))
...
public class MessageHandler : IMessageHandler<TestMessage1>
{
   public Task Handle(IMessageContext context, TestMessage1 message){ return Task.CompletedTask;}
}

public class OtherMessageHandler: IMessageHandler<TestMessage1>
{
   public Task Handle(IMessageContext context, TestMessage1 message){ return Task.CompletedTask;}
}

Expected Behavior
Adapt Kafkaflow to allow consumers to configure more than one TypedHandlers related to the same MessageType.

What is the behavior decision to support multiple TypedHandlers of the same type?
When you have 2 TypedHandlers for the same message type, the behavior to expect should be?

In theses cases both handlers will be executed


Error while trying to run tensoflow2 sorting demo in colab

I am trying to run the new tensoflow2 sorting demo but I'm getting this error while running the "Visualize the sort task"
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-14-5aa1227097fa> in <module>()
      5
      6 inputs_nodes = inputs.nodes.numpy()
----> 7 targets = utils_tf.nest_to_numpy(targets)
      8 sort_indices_nodes = sort_indices.nodes.numpy()
      9 ranks_nodes = ranks.nodes.numpy()

AttributeError: module 'graph_nets.utils_tf' has no attribute 'nest_to_numpy'

That method is new only in the latest version of the library, so I suspect you don't have the correct latest version 1.1 of the library installed.
If you are running on a local kernel, make sure you install the correct versions of the dependencies as per README instructions:
pip install graph_nets "tensorflow>=2.1.0-rc1" "dm-sonnet>=2.0.0b0" tensorflow_probability
Not that if you already had a previous version of the graph_nets library library installed, you will need to force updating:
with either:
pip install "graph_nets>1.1" or pip install --upgrade graph_nets
If you are running in Google Colaboratory, make sure you set Yes in the Install the Graph Nets library on this Colaboratory runtime cell. And run that cell to install the correct dependencies before anything else.
Equivalently you can run at the start:
!pip install "graph_nets>=1.1" "dm-sonnet>=2.0.0b0"

This error occurs only when I am running in Google Colaboratory. And I had set the install cell to "Yes". But I am still getting the error
I found that the only way to make it run locally was to setup the package via pip install . from the cloned Github repository because when I tried to install through pip install graph_nets "tensorflow>=2.1.0-rc1" "dm-sonnet>=2.0.0b0" tensorflow_probability the tf2 sort demo is not even there

I just tried in Google Colaboratory, using the hosted kernels and it seems to run fine in my case, may try the demo again in a fresh hosted kernel, and make sure you run the cell after you select "yes". The logs should include something like this indicating that the 1.1 version of the library is being installed:

Found existing installation: dm-sonnet 1.35
Uninstalling dm-sonnet-1.35:
Successfully uninstalled dm-sonnet-1.35
Found existing installation: graph-nets 1.0.5
Uninstalling graph-nets-1.0.5:
Successfully uninstalled graph-nets-1.0.5
Successfully installed dm-sonnet-2.0.0b0 dm-tree-0.1.2 graph-nets-1.1.0

It is expected that demos are not included in the installation packages installed automatically with the library or uploaded to pypi to reduce package and installation size. Easiest way is to just download the demo colabs from the github. So long as demos_tf/models.py is there they should run find.

I tried in another machine this morning and it is working now for me. I am still not sure about what was happening. Thanks.
PS: Will the other examples also be updated for TensorFlow 2 anytime soon ?

Glad to hear it is working :)
Yes, we will eventually provide more examples, either updated versions of those, or new ones, but hopefully the sort example is sufficient to get users started for now!


Semantic versioning support for stage for upgrade

Is your feature request related to a problem? Please describe
Using stage for upgrade adds significant overhead to deployment times which could be reduced for deployments where it's unnecessary.
Describe the solution you'd like
A solution could be to only use stage for upgrade on solutions where the major version has changed (i.e. breaking changes have been introduced) while using a standard upgrade.
Additional context

https://semver.org/
https://docs.microsoft.com/en-us/powerapps/maker/common-data-service/update-solutions#apply-the-upgrade-or-update-in-the-target-environment

As per my comment on #11, I don't think this is possible.

Closing based on the above.

Closing based on the above.


Exited -127

Hi there,
I started using last week, running it as a daemon, but after a few days (3~4 days) the container exited with (-127) and had to restart it manually.
Can you help?
Thanks

Hey, can you provide some log messages?

Possibly related Docker issue: https://github.com/docker/docker/issues/5684

I close this for now. Please re-open this issue if you still have this problem. Regards


[url_launcher] 'UIApplication' does not conform to protocol 'Launcher' with Xcode16 Version 16.0 (16A242d)

Steps to reproduce
Swift Compiler Error (Xcode): Type 'UIApplication' does not conform to protocol 'Launcher'
/Users/.pub-cache/hosted/pub.flutter-io.cn/url_launcher_ios-6.3.0/ios/url_launcher_ios/Sources/url_launcher_ios/Launcher.swift:21:0
Actual results
url_launcher: ^6.3.0
Logs

Logs

<!-- Paste your logs here -->

Flutter Doctor output

Doctor output

<!-- Paste your output here -->

Hi @virskor, please provide a complete minimal reproducible code sample along with steps to reproduce. I just tested the url_launcher example and it works as expected.  I am using the latest macOS and Xcode versions.
Please also provide the output of flutter doctor -v.
[✓] Flutter (Channel stable, 3.24.3, on macOS 15.0 24A335 darwin-arm64, locale en-US)
.
.
.

[✓] Xcode - develop for iOS and macOS (Xcode 16.0)
    • Xcode at /Applications/Xcode-16.0.0.app/Contents/Developer
    • Build 16A242d
    • CocoaPods version 1.15.2

Thank you

dependency_overrides:
  url_launcher_ios: ^6.3.1

any one have same issue using this methods can fix it

Having the same issue. Any workaround?

Since we're seeing a lot of comments on related issues and PRs: if you are experiencing this issue, please run:
flutter pub upgrade to update your transitive dependencies (including url_launcher_ios which is where this issue and its fix are).

For me i had to do a little extra. Hope this can help someone!
I did the following same as what virskor did:

dependency_overrides:
  url_launcher_ios: ^6.3.1

any one have same issue using this methods can fix it

As well as doing in xcode:
Runner > Build Settings
And setting Allow Non-modular includes in Framework Modules  to true

Xcode's output:
↳
Writing result bundle at path:
/var/folders/gh/_k1gdfl14f38jt1nclg_x1jm0000gn/T/flutter_tools.g4jjWQ/flu
tter_ios_build_temp_dircO6E2S/temporary_xcresult_bundle
/Users/macbook/.pub-cache/hosted/pub.dev/url_launcher_ios-6.2.4/ios/Classe
s/Launcher.swift:20:1: error: type 'UIApplication' does not conform to
protocol 'Launcher'
extension UIApplication: Launcher {}
^
UIKit.UIApplication:24:15: note: candidate has non-matching type '(URL,
[UIApplication.OpenExternalURLOptionsKey : Any], (@MainActor @Sendable
(Bool) -> Void)?) -> Void'
    open func open(_ url: URL, options:
    [UIApplication.OpenExternalURLOptionsKey : Any] = [:],
    completionHandler completion: (@MainActor @Sendable (Bool) -> Void)? =
    nil)
              ^
/Users/macbook/.pub-cache/hosted/pub.dev/url_launcher_ios-6.2.4/ios/Classe
s/Launcher.swift:20:1: note: add stubs for conformance
extension UIApplication: Launcher {}
^
/Users/macbook/.pub-cache/hosted/pub.dev/url_launcher_ios-6.2.4/ios/Classe
s/Launcher.swift:20:1: error: type 'UIApplication' does not conform to
protocol 'Launcher'
extension UIApplication: Launcher {}
^
UIKit.UIApplication:24:15: note: candidate has non-matching type '(URL,
[UIApplication.OpenExternalURLOptionsKey : Any], (@MainActor @Sendable
(Bool) -> Void)?) -> Void'
    open func open(_ url: URL, options:
    [UIApplication.OpenExternalURLOptionsKey : Any] = [:],
    completionHandler completion: (@MainActor @Sendable (Bool) -> Void)? =
    nil)
              ^
/Users/macbook/.pub-cache/hosted/pub.dev/url_launcher_ios-6.2.4/ios/Classe
s/Launcher.swift:20:1: note: add stubs for conformance
extension UIApplication: Launcher {}
^
/Users/macbook/projects/tenh100-ecom/ios/Runner.xcodeproj: warning: The
iOS Simulator deployment target 'IPHONEOS_DEPLOYMENT_TARGET' is set to
11.0, but the range of supported deployment target versions is 12.0 to
18.0.99. (in target 'Runner' from project 'Runner')
note: Run script build phase 'Run Script' will be run during every build
because the option to run the script phase "Based on dependency analysis"
is unchecked. (in target 'Runner' from project 'Runner')
note: Run script build phase 'Thin Binary' will be run during every build
because the option to run the script phase "Based on dependency analysis"
is unchecked. (in target 'Runner' from project 'Runner')

@RothaSoeurn The fix for this issue is was url_launcher_ios 6.3.1. You are using 6.2.4.

Locking to avoid comments being made here instead of on the issue this was closed as a duplicate of.


[#272] fix etherlime compile optional param dir to path

Codecov Report

Merging #289 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master     #289   +/-   ##
=======================================
  Coverage   96.96%   96.96%
=======================================
  Files          80       80
  Lines        3131     3131
  Branches       24       24
=======================================
  Hits         3036     3036
  Misses         92       92
  Partials        3        3

Impacted Files
Coverage Δ

packages/etherlime/cli-commands/commands.js
97.72% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


0003 - Longest Substring Without Repeating Characters

Given a string, find the length of the longest substring without repeating characters.
Example 1:
Input: "abcabcbb"
Output: 3
Explanation: The answer is "abc", with the length of 3.

Example 2:
Input: "bbbbb"
Output: 1
Explanation: The answer is "b", with the length of 1.

Example 3:
Input: "pwwkew"
Output: 3
Explanation: The answer is "wke", with the length of 3.

Note that the answer must be a **substring**, "pwke" is a subsequence and not a substring.

Hi, can I work on this issue?