allow save images in multiple sizes

Fixes #2431
Usage:
$form->image('photo')
    ->addThumbnailSize('small', 200, 200)
    ->addThumbnailSize('medium', 600, 600);

// To access thumbnail
$model->thumbnail('small', 'photo');

Reference:

https://laravel-admin.org/docs/#/en/model-form-fields?id=image-upload
https://docs.laravelvoyager.com/core-concepts/helper-methods

Hello @zeroiszero, add plz, auto width/height http://image.intervention.io/api/widen
->addThumbnailSize('small', 250, 0);

@uacode, auto resize width/height added

@z-song We need this feature

@zeroiszero @uacode I did some code refactoring to make the usage method shorter.
Now you can use it as follows
$form->image('photo')->thumbnail('small', 200, 200);

// or multiple thumbnails
$form->image('photo')->thumbnail([
    'small'     => [100, 100],
    'medium' => [300, 300],
    'large'      => [600, 600],
]);

Thanks for your work!!


Support msrc types

Closes #381

I see that there is a need to capture KB metadata, but does that need to be done within pkg? That is, adding a new package type and package metadata seems to imply that this is related to a package, when this is really more akin to distro metadata.

The "packages" are really distro information. There aren't any packages here, I'm overloading the package to represent each KB installed in a Windows OS. The metadata is not (in my testing) used, but it represents better what the fields should look like, and opens up the ability to add more metadata later.


Add textCapitalization property for SearchBar and SearchAnchor

This is to add textCapitalization property for SearchBar and SearchAnchor.
Fixes: #131260
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Shouldn't this property also be exposed in  the SearchBarTheme?

It looks like the tests, e.g. 'SearchBar respects textCapitalization property' need to be extended a little to also verify that the theme parameter does the right thing.

It looks like the tests, e.g. 'SearchBar respects textCapitalization property' need to be extended a little to also verify that the theme parameter does the right thing.

Ah I added this check in search_bar_theme_test.dart. The tests in this file are checking textCapitalization can be overridden by searchBar's textCapitalization, then SearchBarThemeData.textCapitalization, and then overall theme's searchBarTheme.textCapitalization.

Hi, shouldn't the services.dart be an absolute reference? This is the pattern across the whole of Material. I just spotted this, because I have a script that relies on these dependencies while copying Material classes into a custom folder.

Hi, shouldn't the services.dart be an absolute reference? This is the pattern across the whole of Material. I just spotted this, because I have a script that relies on these dependencies while copying Material classes into a custom folder.

Thanks for catching this! Created a fix PR(#140425)!


Unhappy jobs cannot fail only alarm.

When an unhappy job fails, it always reports 'svdc_job_alarm'.
This is not correct.
An unhappy job can fail in all of the same ways that a happy job can fail.  Alarm is a special case (critical event seen).
We need to alarm only when a critical event was seen and allow for 'svdc_job_failed' in the "normal" failure cases.

This has remained undetected, partly because the only error injection testing that has been done on Critical jobs is the injection of unhappy events in the context of critical events.

Resolved with PR #230


Remove enable_bonding from config-example.toml.

Remove the commented configuration option enable_bonding (these lines) from resources/production/config-example.toml.
If an operator tries uncomment the line, the node will crash on startup.

Should a change in example file impact the node, had the change been in config.toml i can see but how in config-example.toml


Finnish translation

Left Bootstrap class names (Default, Danger, Info…) as they were.
Reasoning behind was to allow developers use classes they already
know and keep mental model.

Great first PR to the repo and good idea about the bootstrap classes. Will merge and update the site. Need to change contributors list to include contributions from this repo now.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


BLANK WHITE PAGE

All I get is a BLANK WHITE PAGE.  Since there is absolutely NO documentation, I had to wing it.
I cloned the repo, then tried to run public/index.html from my Apache server and got a blank white screen.  I then saw that is was all built in React, so I ran npm install to install all of the dependencies.  I then hit the page again and got the SAME blank white screen.  So I tried using npm start and that simply generated a BUNCH of ERRORS.
HOW is one actually supposed to actually USE this repo???
Thanks.

Tailwind INstallation
^ first make sure tailwind is properly working, (checkout post cdn for development)
then retry!


TensorflowHub Citation

Hello,
I would like to know if TF Hub has its own paper to cite or preferred citation (preferably in BibTex format). If not, then should we cite TF using the guidlines given here?
Thank you.

There is no stand-alone paper covering TF Hub. Citing TF should be ok in
this case.
On Fri, Nov 19, 2021 at 9:36 AM MarkKocherovsky @.***>
wrote:

Hello,
I would like to know if TF Hub has its own paper to cite or preferred
citation (preferably in BibTex format). If not, then should we cite TF
using the guidlines given here https://www.tensorflow.org/about/bib?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/hub/issues/825, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AG52OTA7J3242RIML4DSRW3UM2DJ5ANCNFSM5IMVAMNQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Alright, thank you!


Support multicolumn primary keys in postgres

I would like to create a composite primary key.

Do you have any example ? I can't find a way to create a multiple columns primary key.

Hi All,
Just improved composite primary key support for gorm, please checkout https://github.com/jinzhu/gorm#composite-primary-key

Thanks ! That's appreciated :)

How do I make a many-to one connection to the entity with a composite id? For example, in the documentation, you have,
type Product struct {
    ID           string `gorm:"primary_key"`
    LanguageCode string `gorm:"primary_key"`
}

So how can I make it work on the following case:
type Campaign struct {
    AssociatedProduct Product
}

Would this work? I'd appreciate any pointers. Thanks.


⚠ Bofrost.fr has degraded performance

In a46a2d8, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1793 ms

Resolved: Bofrost.fr performance has improved in a457fb9 after 6 minutes.


Lab11

Lab 11 Canvas Assignment
Functional requirements:

[ ] Constructor function which creates a product object

[ ] Name property
[ ] Votes property
[ ] Views property
[ ] Image Source property

[ ] Algorithm to generate random side-by-side displays of 3 different product images
[ ] View property is incremented when a product is shown
[ ] An event listener to check for votes via click
[ ] Click event triggers another round of voting with 3 new products
[ ] Number of voting rounds should be defined in a variable
[ ] Remove event listeners from all products when voting rounds are spent
[ ] View results button which shows a list of all products, their views, and their votes

Style Guide

[ ] Repo has a filled out README (the 201 template filled in with a copy of submission comments is ok)
[ ] Proper file structure

[ ] js folder containing app.js
[ ] img or assets folder
[ ] css folder contiaining css files
[ ] .gitignore to hide node_modules folder from git
[ ] .eslintrc.json file

[ ] Assets have been placed in "img" folder
[ ] Work was done in a new feature branch


Update the list of stopwords

Due to the issue reported in #213, I updated the list of stopwords (I used the scikit-learn list of stopwords). Also, I take the opportunity to update the specs.

gonna close this for now for sanity @acmh please reopen if you get the list of words added to the commit


ci(sdk): skip pushing to container registry for snapshot builds

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (57e1ccf) 89.28% compared to head (9b5a2f6) 89.33%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #710      +/-   ##
==========================================
+ Coverage   89.28%   89.33%   +0.04%
==========================================
  Files         108      108
  Lines        4425     4425
==========================================
+ Hits         3951     3953       +2
+ Misses        319      317       -2
  Partials      155      155

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


Add clarification to NRT timeline

Have slightly updated the words of the NRT dataset maturity guide to make it clear that we often produce NRT much faster than 48 hours.
Happy for any wording suggestions here! I just think that if we're often producing data less than 24 hours after capture, we might as well advertise this (in a way that doesn't hold us to any firm deadline).

The currency dashboard suggests that the processing is usually closer to 24 hours, but almost never less than. Can we say that instead?
"and often closer to 24 hours"?

Updated!


Add a generic JSON parser

I think this is at least a good start, depending on what else you want to see there.


[qtinterfaceframework] Build error on x64-linux

Package<EMAIL_ADDRESS>Host Environment

Host: x64-linux
Compiler: GNU 11.4.0
vcpkg-tool version: 2024-04-23-d6945642ee5c3076addd1a42c331bbf4cfc97457
vcpkg-scripts version: cbf4a6641 2024-05-09 (22 hours ago)

To Reproduce
vcpkg install
Failure logs
-- Using cached /home/wfk/vcpkg/vcpkg/downloads/qtinterfaceframework-062662be9975e186a64c19a43b04f13c3e2aebfc.tar.gz
-- Cleaning sources at /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/src/3c3e2aebfc-243481cf92.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/wfk/vcpkg/vcpkg/downloads/qtinterfaceframework-062662be9975e186a64c19a43b04f13c3e2aebfc.tar.gz
-- Applying patch fix-taglib-search.patch
-- Using source at /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/src/3c3e2aebfc-243481cf92.clean
-- Setting up python virtual environmnent...
-- Installing requirements from: /home/wfk/vcpkg/vcpkg/buildtrees/versioning_/versions/qtinterfaceframework/3c0fac0141ef882b26d1904189a1aafd4dc4540f/requirements_minimal.txt
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:112 (message):
    Command failed: /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/x64-linux-venv/bin/python -m pip install -r /home/wfk/vcpkg/vcpkg/buildtrees/versioning_/versions/qtinterfaceframework/3c0fac0141ef882b26d1904189a1aafd4dc4540f/requirements_minimal.txt
    Working Directory: /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework
    Error code: 1
    See logs for more information:
      /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/pip-install-requirements-file-x64-linux-out.log
      /home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/pip-install-requirements-file-x64-linux-err.log

Call Stack (most recent call first):
  /home/wfk/project/hydro_3d_navi/src/build/vcpkg_installed/x64-linux/share/vcpkg-get-python-packages/x_vcpkg_get_python_packages.cmake:103 (vcpkg_execute_required_process)
  buildtrees/versioning_/versions/qtinterfaceframework/3c0fac0141ef882b26d1904189a1aafd4dc4540f/portfile.cmake:22 (x_vcpkg_get_python_packages)
  scripts/ports.cmake:175 (include)

/home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/pip-install-requirements-file-x64-linux-out.log
Collecting antlr4-python3-runtime==4.7.1
  Using cached antlr4-python3-runtime-4.7.1.tar.gz (111 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting argh==0.26.2
  Using cached argh-0.26.2-py2.py3-none-any.whl (30 kB)
Collecting click==6.7
  Using cached click-6.7-py2.py3-none-any.whl (71 kB)
Collecting coloredlogs==10.0
  Using cached coloredlogs-10.0-py2.py3-none-any.whl (47 kB)
Collecting humanfriendly==4.15.1
  Using cached humanfriendly-4.15.1-py2.py3-none-any.whl (70 kB)
Collecting Jinja2==2.11.3
  Using cached Jinja2-2.11.3-py2.py3-none-any.whl (125 kB)
Collecting MarkupSafe==1.1
  Using cached MarkupSafe-1.1.0.tar.gz (18 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting path.py==11.0.1
  Using cached path.py-11.0.1-py2.py3-none-any.whl (32 kB)
Collecting pathtools==0.1.2
  Using cached pathtools-0.1.2.tar.gz (11 kB)
  Preparing metadata (setup.py): started
  Preparing metadata (setup.py): finished with status 'done'
Collecting PyYAML==5.4
  Using cached PyYAML-5.4.tar.gz (174 kB)
  Installing build dependencies: started
  Installing build dependencies: finished with status 'done'
  Getting requirements to build wheel: started
  Getting requirements to build wheel: finished with status 'error'

/home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/pip-install-requirements-file-x64-linux-err.log
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x702025446a70>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=15)')': /simple/antlr4-python3-runtime/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x702025445f30>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=15)')': /simple/antlr4-python3-runtime/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x702025446530>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=15)')': /simple/antlr4-python3-runtime/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7020254464a0>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=15)')': /simple/antlr4-python3-runtime/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urllib3.connection.HTTPSConnection object at 0x7020254461a0>, 'Connection to <IP_ADDRESS> timed out. (connect timeout=15)')': /simple/antlr4-python3-runtime/
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [48 lines of output]
      running egg_info
      writing lib3/PyYAML.egg-info/PKG-INFO
      writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
      writing top-level names to lib3/PyYAML.egg-info/top_level.txt
      Traceback (most recent call last):
        File "/home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/x64-linux-venv/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 363, in <module>
          main()
        File "/home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/x64-linux-venv/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 345, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/home/wfk/vcpkg/vcpkg/buildtrees/qtinterfaceframework/x64-linux-venv/lib/python3.10/site-packages/pip/_vendor/pep517/in_process/_in_process.py", line 130, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 271, in <module>
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/__init__.py", line 104, in setup
          return distutils.core.setup(**attrs)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 184, in setup
          return run_commands(dist)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 200, in run_commands
          dist.run_commands()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 967, in run_command
          super().run_command(command)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 321, in run
          self.find_sources()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 329, in find_sources
          mm.run()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 550, in run
          self.add_defaults()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 588, in add_defaults
          sdist.add_defaults(self)
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/command/sdist.py", line 102, in add_defaults
          super().add_defaults()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 250, in add_defaults
          self._add_defaults_ext()
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 335, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
        File "<string>", line 201, in get_source_files
        File "/tmp/pip-build-env-ezktn6lx/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build wheel did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

Additional context
vcpkg.json
{
  "name": "manifest",
  "version": "0.1.0",
  "description": "",
  "dependencies": [
    "glib",
    "osg",
    "osgearth",
    "pcl",
    "spdlog",
    "vtk",
    "qt"
  ],
  "builtin-baseline": "40619a55c3e76dc4005c8d1b7395071471bb8b96",
  "overrides": [
    {
      "name": "glib",
      "$note": "version 2.76.2 build failed, trying to use latest version instead",
      "version": "2.78.4#1"
    },
    {
      "name": "osg",
      "version": "3.6.5#18"
    },
    {
      "name": "osgearth",
      "version": "3.3#7"
    },
    {
      "name": "pcl",
      "version": "1.13.0#3"
    },
    {
      "name": "spdlog",
      "version": "1.11.0"
    },
    {
      "name": "vtk",
      "version": "9.2.0-pv5.11.0#6"
    },
    {
      "name": "qt",
      "version": "6.5.0"
    }
  ]
}

#32630


Size of localization in image rendering

It would be helful being able to set size of the radius when rendering the localization at least for the final filtered image. This could be done either based on the calculated localization precision of the image, arbitrarly, or each localization rendered based on its own precision.
For publications, we saw that rendering the images with e.g. 2nm is not feasible (you do not see anything!) and increasing the size to e.g. 20nm is necessary.
Alternatives, are to export the table of localizations generated by PyMINFLUX and use other software for the rendering
Thanks!

Hi, @destelisa, thanks for the suggestion. We have already planned to work on this, and will most likely add it to the upcoming release. In the meanwhile, I would suggest a few workarounds:

In File > Options (Preferences on macOS), reduce the value of Resolution (DPI) for exporting plots: this should make the size of the dots larger (particularly on macOS, the default might indeed be a bit aggressive);
Save the filtered data to a .pmx file (File > Save) and then import the .pmxfile in ParaView, where you will have more flexibility in setting up your 3D renderer. Please follow this instructions to set up the plug-in: https://github.com/bsse-scf/pyMINFLUX/wiki/pyMINFLUX-user-manual#3d-data-viewer
Export the filtered data to a .csvfile (File > Export data) and import it into a tool of your choice. If you are familiar with Python and the Matplotlib library, you can create publication-quality figures with a few lines of code.


Add Edge Language

Adds the edge templating language used by AdonidJS
https://edgejs.dev/
Checklist:

[x] I am adding a new language.

[x] The extension of the new language is used in hundreds of repositories on GitHub.com.

Search results for each extension:

https://github.com/search?q=(path%3A*.edge)+AND+(content%3A%40section+OR+content%3A%40if+OR+content%3A%40end+OR+content%3A<div>)+NOT+is%3Afork&type=code

[x] I have included a real-world usage sample for all extensions added in this PR:

Sample source(s):

https://github.com/edge-js/edge/blob/develop/examples/views/welcome.edge

Sample license(s): https://github.com/edge-js/edge/blob/develop/LICENSE.md

[x] I have included a syntax highlighting grammar: https://github.com/edge-js/edge-vscode

[x] I have added a color

Hex value: #0dffe0
Rationale: Color used in official Edge logo found on https://edgejs.dev

[ ] I have updated the heuristics to distinguish my language from others using the same extension.

One question I have is the grammar includes source.js#expression which is not available in the atom javascript textmate grammar, but is available in the microsoft grammar. I think GitHub uses the treesitter grammar for javascript, but I assume it will use the textmate grammar when being included by another textmate grammar. Can you confirm if my assumption is correct about using the textmate grammar when included by other textmate grammars, and if so which version of the grammar is in use.
@thetutlage If the atom grammar is being used I'd recommend updating the edge grammar to include source.ts#expression instead.

I think GitHub uses the treesitter grammar for javascript,

Correct a denoted by the 🐌 in the list of grammers README.md

but I assume it will use the textmate grammar when being included by another textmate grammar. Can you confirm if my assumption is correct about using the textmate grammar when included by another textmate grammars,

It is.

and if so which version of the grammar is in use.

The latest SHA of the repo the submodule points to.

Thanks for the confirmations @lildude
I've made the required updates to the edge grammar, so everything should be fine from our end now. I've tested the updated grammar with nova lightshow and all seems to be working great :)

Done 🙂


scroll_behavior.dart could be simplified

Until we start creating ScrollBehaviors that need to customize their snap Simulations, it would be simpler to just have a global createSnapScrollSimulation method (perhaps in scrollable.dart, where it's used).

Done.  This is now factored into a couple pieces, including ScrollPhysics.  Hopefully its simpler.


Bug 1745532: FlattenListVisitor now continues traversal on errors and returns an aggregate

This fixes a problem that FlattenListVisitor would always return an error as soon as it hit one in list traversal, even if ContinueOnError is specified
BZ: 4.2: https://bugzilla.redhat.com/show_bug.cgi?id=1745532
Upstream PR: https://github.com/kubernetes/kubernetes/pull/81452

/lgtm

Replaced by https://github.com/openshift/kubernetes-cli-runtime/pull/3


Improve UI in project and model creation workflow

The UI elements are not consistently used in the project and tool model creation workflow.
Some examples:

Here, the elements are aligned on the left side. The button is part of the mat-card. We decided to not have a "Cancel" button (navigation via breadcrumbs already provides this feature), so it should be removed.

This looks weird as it doesn't use the whole available screen space, but the buttons to add users are still on the right side. Also the "skip" should start with an uppercase character and looks weird in the full-width mat-card.

The "Create model" button is on the left side, which is not consistent with the other button locations.
The "Skip model creation [...]" button has a different design again - it's placed in it's own mat-card, which is not full-width. The margins are not the same on the left & right side.

The model sources selection is centered in the middle (other components sticked to the left side).

I'll share some updates with my justifications since I'm making up design choices as I go, in case there's anything anyone wants me to reconsider.
General Information Form Changes

Removed the Cancel button
Left-aligned Create button
Shortened the radio text.
Changed some HTML for accessibility (appropriate fieldsets and legends)

General Information Questions

Can we shorten the radio text to "Public" and "Private" with an info hover (a user will only need to read the explanation once)
Are we settled on "Internal"? (e.g. is it used that way throughout our projects?) I think "Internal" v "Private" doesn't communicate the difference very well
I know the buttons aren't on the mat-card in other forms, but I think it actually needs to stay on the card for accessibility considerations, is that OK as long as I make it consistent throughout?

@MoritzWeber0 I'll share some updates with my justifications since I'm making up design choices as I go, in case there's anything anyone wants me to reconsider.
General Information Form Changes

Removed the Cancel button

👍

Left-aligned Create button

👍

Shortened the radio text.

👍  (The new text is way clearer, I like it)

Changed some HTML for accessibility (appropriate fieldsets and legends)

👍

General Information Questions

Can we shorten the radio text to "Public" and "Private" with an info hover (a user will only need to read the explanation once)

The terminology "Internal" is derived from Gitlab and some other services, which use a similar wording.
"Internal" describes the state that all "logged in" users can see it, while "Public" described the state that all users (also not logged in users) can see the project. Therefore I would keep the name "Internal". We might also add a third visibility "Public" in the future.
I'm also against the info hover - especially when the meaning isn't automatically apparent from the words.

Are we settled on "Internal"? (e.g. is it used that way throughout our projects?) I think "Internal" v "Private" doesn't communicate the difference very well

No, we are not. But Public is not an alternative as mentioned in the comment above. If you have other good ideas, feel free to share them.

I know the buttons aren't on the mat-card in other forms, but I think it actually needs to stay on the card for accessibility considerations, is that OK as long as I make it consistent throughout?

Yes, that's fine.

Project Member Changes

Fixed title margin
Shifted add user and audit logs buttons into mat, added text
Added sections to clarify form actions
Changed skip/continue button into a link-styled button (because it takes the user to the next page, but has no impact on form)

Project Member Questions

I just guessed on the log button text because the hover text was a little long and esoteric, but let me know if that should be more specific
How often is the audit button currently used? I'd move it elsewhere if it's not a critical component (maybe "Project Information" metadata mat?)
How many users does the average project have? The search bar seems unnecessary to me but obviously if projects get huge it must be useful

OK, this is the bulk of the updates, I think I might be missing a few routes for T4C but they should look like the others once I'm finished.
If there aren't any major call outs after sharing these with the team I'll start refactoring. ProjectCreationUpdates.pdf

Looks really nice, love the comparison. Maybe you can put them as images in the PR description (once the PR is open), it's a little more accessible than a PDF that has to be downloaded first.


merge from konsum-frontend-svelte,template-arlac77-github,template-svelte-app

package.json

chore(deps): add ^10.15.1 remove ^10.14.14 (devDependencies.npm-pkgbuild)

.github/workflows/browser_ci.yml

chore: add ubuntu-latest (jobs.test.runs-on)

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

npm package (@latest dist-tag)
v1.34.10
GitHub release

Your semantic-release bot :package::rocket:


Add distribution Categorical

1.Add distribution Categorical;
2.To make test of distribution Categorical, I changed a little for test method assert_tensor_eq--- to make all object to be tested within type f64;
3.I do add code for mean and variance for the distribution, but I don't know how to deal with it when there is Nan, so I commented related code;
4.For sample of distribution Categorical, the result should be conssistent, but just for one example, the resulted 2 objects after as_cell_slice are different, I think it a issue of crate numpy, so I raised an issue there: https://github.com/PyO3/rust-numpy/issues/203.

Weird, why poisson is failed, It is passed on my local machine~

Also works on my machine


Sniffing connection pool with attribute awareness

Hi,
We typically setup multiple VMs each with one instance of our .NET API server, one data node and one coordinating node. Then we replicate this on another server on a separate rack.
The existing sniffing connection pool is interesting but instead of round robin, we would like to always use a preferred node (coordinator) and if this fails switch to the next best and so on.
The failover node will be the one that shares the most attributes with the preferred one.
For example say we configure the nodes with attributes like 'server', 'rack_id' and 'room'.
If the preferred node dies, it will select one on the same host, then one on the same server, then rack, then room and so on.
We will implement something like this but wanted to check if this feature would be desired by the community and if that's the case we will fork the project and do it here rather that in our project.
Any thoughts?
Thanks

Hi @srgclr
We have two things that you could use right now to do this:
StickyConnectionPool
And:
NodeSelector on ConnectionSettings. Look at this test for an example taking node attributes into account.
However the StickyConnectionPool does not support reseeding and NodeSelector and Sniff only runs on IConnectionPools that supports reseeding.
So we'd need a StickySniffingConnectionPool, happy to take a PR for that! We're currently at elasticon so limitted keyboard time is available. If not I can start looking at adding that in in two weeks.

I guess the stickyness decider needs to be pluggable too so CreateView() returns node in the order you want.

Thanks @Mpdreamz,
We can start soonish but can't promise it will be ready in less than two weeks.
Will keep in touch in case you get to it first.
Cheers

Hi @Mpdreamz,
We've started working on this. Should have something to review soon.
Thanks

We're happy with #2789
Thanks

Ty for taking the time to report back @srgclr!


BundleMon GitHub Action keeps listing assets as "added"

Hello @LironEr , I have implemented BundleMon and its corresponding GitHub Action in one of my projects. It's working well (thank you!) and triggered for every PR, however, I cannot figure out a way to make it remember the project. Each time a PR runs, it displays the following:

See the "Files added" label. Even though that it's not the first PR that ran with BundleMon on that repo. The repo is there: https://github.com/aversini/mylogin-ui and the corresponding BundleMon configuration file is here: https://github.com/aversini/mylogin-ui/blob/main/bundlemon.config.cjs
Thanks!

Hey, thanks for reaching out (:
So it looks like you are missing running bundlemon on each commit on your main branch.
for example:
on:
  push:
    branches: [main]
  pull_request:
    types: [synchronize, opened, reopened]

You need to run bundlemon on each commit on your main branch because when you create a PR and you have a target branch, bundlemon checks the file sizes on that branch and compares them to your PR.
Only after you merge something (push to main) bundlemon can save the new file sizes to that branch, and it becomes the new base line.

That did it, thanks for the tip @LironEr 👍


close() method of AzuriteBlob, AzuriteQueue and AzuriteTable won't wait for resolution

Currently, the close() methods for AzuriteBlob, AzuriteQueue and AzuriteTable, although they return a Promise, the code within the promise won't await for the methods called within it:
https://github.com/Azure/Azurite/blob/f3dccf71dae73d1af8bc355e39c215515a322d4f/lib/AzuriteBlob.js#L86-L92
https://github.com/Azure/Azurite/blob/f3dccf71dae73d1af8bc355e39c215515a322d4f/lib/AzuriteQueue.js#L58-L62
https://github.com/Azure/Azurite/blob/f3dccf71dae73d1af8bc355e39c215515a322d4f/lib/AzuriteTable.js#L65-L71
Issues:

this.server.close() expects a callback that will be called on completion. It should be promisified.
Both storageManager.flush() and tableStorageManager.flush() return the promise of db.saveDatabaseAsync(), but is not awaited for.
Both storageManager.close() and tableStorageManager.close() return the results of db.close(), but it should really return the results of db.closeAsync().

Finally, where more than 1 method is called, they should be wrapped with BbPromise.all().
If I'm not missing anything, then I could prepare a PR for you.

Will close this issue as PR solved. And please try with latest Azurite V3.


provide the  affinity character of the sub-deployment-pod  for deployment checker

Describe the feature you would like and why you want it
The sub pod  created by the deployment-checker only  can modify 'NODE_SELECTOR' of deployment khc to be scheduled on specific node.
This is not enough for some specifc situations.
just like this:
environment in (production, qa)
tier notin (frontend, backend)

It's difficult to achieve the specific scheduled rule if we use 'NODE_SELECTOR' of deployment khc.
Maybe we can provice certain ways to achieve affinity by insert container var of deployment khc just like 'NODE_SELECTOR'
// Affinity is a group of affinity scheduling rules.
type Affinity struct {
	// Describes node affinity scheduling rules for the pod.
	// +optional
	NodeAffinity *NodeAffinity `json:"nodeAffinity,omitempty" protobuf:"bytes,1,opt,name=nodeAffinity"`
	// Describes pod affinity scheduling rules (e.g. co-locate this pod in the same node, zone, etc. as some other pod(s)).
	// +optional
	PodAffinity *PodAffinity `json:"podAffinity,omitempty" protobuf:"bytes,2,opt,name=podAffinity"`
	// Describes pod anti-affinity scheduling rules (e.g. avoid putting this pod in the same node, zone, etc. as some other pod(s)).
	// +optional
	PodAntiAffinity *PodAntiAffinity `json:"podAntiAffinity,omitempty" protobuf:"bytes,3,opt,name=podAntiAffinity"`
}

Actually, The easy way is that we  create sub pod by configmap of sub pod configuration, This will  simply the code .
Of course, I prefer to add containter var of deployment khc to achieve this situation.  I don't like deploy our checker by the fussy configuration.
@integrii


Stricter types for nothing and noChange

Description
nothing and noChange sentinels have a type of {} (empty object). This can be confusing and misleading in TypeScript when mixing with other valid lit-html types such as TemplateResult.
function render(value?: string): TemplateResult | {} {
  if (!value) {
    return nothing;
  }

  return html`Value: ${value}`;
}

The return type is not entirely accurate, since any new empty object is not a valid return value for this function. It should only expect a template result or the nothing sentinel.
Acceptance criteria
lit-html can provide a stricter unique type alias for nothing and noChange that ensures the types for those sentinel values are unique and do not conflict with the empty object type.
Example:
export type NothingSentinel = {
  _nothingBrand: never;
};
export const nothing = {} as any as NothingSentinel;

This should be fixed in lit-next by #1470

This should be fixed in lit-next by #1470


Can't put anything in my /keybase

Tried to share a small file with just hello in it, failed with error -36.
my log id: 3a37304731799f7a2ed7151c

The tracking statement for the user whose folder's you're trying to access is broken. We should have popped up a tracker window for you to re-track the person if you trusted their new identity.  But if that didn't work or you ignored the window, you can try keybase track <username>.

No window popped up. Thanks.

Working perfectly now, thanks again!

Great! @cjb: another instance of a tracker popup not showing when we get a "X track components failed" error.


🌱 Update triggers for release-1.4

update triggers on release-1.4 after migration to prow

/test ?

/test metal3-ubuntu-e2e-integration-test-release-1-4

/test metal3-ubuntu-e2e-integration-test-release-1-4

/test metal3-ubuntu-e2e-integration-test-release-1-4

out of support


Fix: graph Axis Label Truncation(fixes #208)

What is the purpose of this pull request? (Check any that's applicable)

[ ] Feature
[x] Bug fix
[ ] Dependency updates
[ ] Documentation updates
[ ] Build related changes
[ ] Changes an existing functionality
[ ] Other, please explain:

Does this introduce a breaking change?

[ ] Yes
[x] No

What changes did you make? (Give an overview)

In all axis, When a label is too long, it will truncate and upon click reveal the entire label. The label when truncated will include an '...' to indicate to user that there is more information that is not shown face up.

Add any screenshots
Before

After

Added new tab called Label Truncation

@AshishMotanamGurunadham Is this going to fix https://github.com/cerner/carbon-graphs/issues/208 ?

@SharathAlur yes it is going to fix issue number 208 and updated PR heading accordingly to let reviewers know the issue number.

A few follow up questions and observations:

How are we handling this different for Gantt charts since the label is oriented horizontally instead of vertically and requires the 12 character limit?
The Line Graph group on the Demo site seems to be where we are putting all kinds of examples if they don't relate to one specific type of graph.  We should consider creating some sort of General group or groups related to Legends, Axes...etc. that impact multiple graph types.

In Gantt chart, label is generated in the place of tick. Whereas in line graph label is generated separately on the axis. That is the reason why label in line graph label is oriented vertically and gantt chart label is oriented horizontally. And based on the space they provided for the label 12 characters would be best to restrict in gantt chart.

@AshishMotanamGurunadham Are we ready to merge the PR?

@Veera81 There are three approvals we can merge it.

@sdadn Can you review and approve the PR? So that we can merge this PR?

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Adds some additional canned atom and bond query definitions

The list:

queryAtomNumRadicalElectrons
queryAtomHasChiralTag
queryBondHasStereo

Any chance for a query(Atom/Bond)HasMissingStereo?

That would be an atom/bond that could have valid stereo but doesn't?

Exactly!

Certainly doable.

I'll add the atom query now. The bond query is going to have to wait until assignStereochemistry is modified to flag double bonds that could have stereo and don't. That should be a separate PR


Add NSDictionary-to-JSON conversion benchmark.

An ideal JSON library will maintain data as an NSDictionary internally rather
than force a conversion to a Swift dictionary during init.
On iPhone 5C, JASON runs in 0.002 sec, SwiftyJSON runs in 0.030 sec on a 10,000 item NSDictionary.
JSON data typically originates as an NSDictionary, and converting
a large NSDictionary to a Swift dictionary is slow (due to mem copy and casting of
every item in the dict).
Type conversions to Swift native types should happen only on key access, thus
amortizing the cost (or avoiding the bulk conversion cost in the case where
there is no consecutive loop access of every key in the JSON data).

In all likelyhood init with NSDictionary is O(n) vs O(1), SwiftyJSON and JASON respectively


fix: override fit in Classifier and Regressor

Summary of Changes
Override fit in Classifier and Regressor, so metrics can be used on the fitted models.

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

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.16.1
GitHub release

Your semantic-release bot :package::rocket:


initial commit

hey take these three files

thanks for your pull request

My pleasure. In future i'll send you more pull request for sure. Keep checking those @DummyCodes 🛩

sure @nayeem990  💴


9407.2 Update dashboard.html to show deprecation notice for TRITON integration

https://github.com/Shippable/pm/issues/9407

rc verified


merge: stage to master

merge: stage to master

:tada: This PR is included in version 0.27.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update dependencies

Update to Django 2.2.10 which fixes CVE-2020-7471.
The changes in #234 closed #232 allowing an update to
django-registration to 3.1.

Pull Request Test Coverage Report for Build 626

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.977%

Totals

Change from base Build 624:
0.0%

Covered Lines:
3662

Relevant Lines:
3662

💛  - Coveralls


check-model-has-properties-file hook fails for versioned model with properties file

Describe the bug
We are running pre-commit check (v2.0.3) in our CI/CD.
Hook check-model-has-properties-file fails for certain models (versioned models) with the following error:
`Check the model has properties file......................................Failed

hook id: check-model-has-properties-file
exit code: 1

project_name/models/example_model.sql: does not have model properties defined in any .yml file.`
Note: real model path and files are replaced with examples to not reveal potentially sensitive information.
To Reproduce
Steps to reproduce the behavior:

Create .pre-commit-config file that includes the check-model-has-properties-file hook
Create version 1 of your model. The file name is: project_name/models/example_model.sql
Note: this model does not have the version suffix as we support the aliases.
Example .sql file:

{{ config( materialized='table' ) }}

select
    field1,
    field2,
    field3,
    field4
from {{ ref('source_name') }}

Define model properties file example_model.yaml

version: 2

models:
  - name: example_model
    description: |
      Example model table
    config:
      contract:
        enforced: true
    latest_version: 1
    columns:
      - name: field1
        description: |
          Field1 description
        data_type: integer
        constraints:
          - type: not_null
        data_tests:
          - unique
      - name: field2
        description: |
          Field2 description
        data_type: string
        constraints:
          - type: not_null
      - name: field3
        description: Field3 description
        data_type: date
      - name: Field4
        description: Field 4 description
        data_type: integer
    versions:
      - v: 2
        columns:
          - include: all
            exclude: [field4]
      - v: 1
        access: public
        config:
            alias: example_model

Create the second version of the model, that will have field4 excluded. Name the file project_name/models/example_model_v2.sql

{{ config( materialized='table' ) }}

select
    field1,
    field2,
    field3
from {{ ref('source_name') }}

Trigger the pre-commit check.

Expected behavior
Pre-commit check should pass with no reported errors as model has defined the properties file.
Version:
v2.0.3
Additional context
We are running pre-commit check in GitHub actions set up.

I see that PR for this issue has been open. Any information when are you planning to release this fix?

Hello @vknezovic1309
v2.0.6 has just been released, please let us know your results


Remove deprecated v1 code

[X] Read the Contributing document.

Summary
This commit removes the deprecated code from the main library and moves the code from the v2 directory into the main library. This commit also removes the duplicated go vendor dirs.
#187603786
Backward Compatibility
Breaking Change? Yes
We are removing deprecated v1 code to switch over entirely to v2 logic. Thankfully, operators can use the old library with the last tag: https://github.com/cloudfoundry/cfhttp/releases/tag/v2.0.2

@jrussett This looks good. It looks there were some updates since the PR that I can't approve and merge. If you can please resolve those, I am going to merge it.


Supporting i18n?

swagger spec doesn't natively support i18n, but is it possible that grape-swagger generate localized documents for different locale? For example, visiting http://localhost:3000/swagger_doc.json will get default language, as well as visiting http://localhost:3000/swagger_doc.json?locale=zh-CN will get another json in Chinese.

It's definitely a useful feature request.


Allow instance IP ordering and filtering

This PR allows users to choose which IP of the bosh instance to use as target and label as requested in #17
How it works

It adds a new parameter filter.cidrs that gives a coma-seperated list of CIDR.
Each instance IP is matched against each CIDR in the order given by the list
The first match gives the IP to use as target and label
Default value for filter.cidrs is <IP_ADDRESS>/0 which matches any IP. Consequently, the default behavior is unchanged: the first available IP is used.
When couldn't match any IPs to any given CIDR, the instance is dropped (which provides a way to filter-out instances by their IP)

Example:

Given two instances with their IPs

A: <IP_ADDRESS> and <IP_ADDRESS>
B: <IP_ADDRESS>

With --filter.cidrs="<IP_ADDRESS>/0" (default flag value)

step A1. <IP_ADDRESS> is checked against <IP_ADDRESS>/0, match

<IP_ADDRESS> is used for A

step B1. <IP_ADDRESS> is checked against <IP_ADDRESS>/0, match

<IP_ADDRESS> is used for B

With --filter.cidrs="<IP_ADDRESS>/16,<IP_ADDRESS>/0"

step A1. <IP_ADDRESS> is checked against <IP_ADDRESS>/16, no match
step A2. <IP_ADDRESS> is checked against <IP_ADDRESS>/16, match

<IP_ADDRESS> is used for A

step B1. <IP_ADDRESS> is checked against <IP_ADDRESS>/16, no match
step B2. <IP_ADDRESS> is checked against <IP_ADDRESS>/0, match

<IP_ADDRESS> is used for B

@frodenas Please can you give me an initial feedback about the approach, implementation and documentation ?
I'll remove the [WIP] flag after pushing some additional unit tests

@frodenas any news on this matter ?

@frodenas any news on this matter ?

Hello @frodenas
Is there any problem with this PR ?

Thanks @psycofdj and apologies for the super late review.


wip on badges refactor

Overall I think your approach makes a lot of sense. I am a little concerned about the average developer following protocol for hashing to get an nftcid. At the same time, how standardized does the nft metadata need to be in order to fulfill the requirements? If metadata does have to strictly follow a specific format, what will we do if people irresponsibly mint tokens? On the brightside, it could be a really cool place to open up an ujo sdk for proper minting. See below for more comments/questions.
Just to be clear on the goal: each token should have a tokenURI that follows: tokenURIBase + tokenId + tokenURISuffix. Your proposal is that:
tokenURIBase is  "https://ipfs.infura.io:5001/api/v0/dag/get?arg=";
tokenId  is the int representation of the hashed bytes of: _mgCid, _nftCid, _beneficiary, _usdCost, badgeNumber
tokenURISuffix is nothing at the moment
The idea is that any exchange will be able to access a single NFT's metadata through a URI instead of a contract.
If that is correct, then I have a few questions:

How are the exchanges supposed to get the tokenUriBase and tokenUriSuffix? Is that something we supply on the side or are:

    string public tokenURIBase;
    string public tokenURISuffix;

standards that other NFT's follow across the board? Or is the expectation that they will get access to tokenId's and be able to call tokenURI for the tokenURI information? Not totally sure of the requirements or how this actually works once its deployed.

Just an opinion, but I feel like the way badgeNums are calculated is extremely specific. For example, what if the MG decides to rotate ethereum address' every X time period. As I type this message I'm starting to get the feeling that the contract shouldn't be responsible for calculating badgeNums. What if this is a service Ujo provides?

I'd be extremely interested in helping out with the JS and even the solidity for the initialise() function https://github.com/UjoTeam/contracts-badges/blob/feat/refactor/contracts/InitBadges.sol#L13. Would be a great learning experience.

Hope those questions/comments are helpful

Thanks for reviewing! I think you have it slightly wrong.
tokenUri is: base + nftCid + suffix.

How are the exchanges supposed to get the tokenUriBase and tokenUriSuffix?

They call tokenUri to get the whole URI. They expect a JSON blob on the other side to digest/scrape it.

Or is the expectation that they will get access to tokenId's and be able to call tokenURI for the tokenURI information?

With your ETH address, you getAllTokens, and do a run over tokenUri to get the URIs for each token. They then use the "ERC721 Metadata JSON Schema" (CTRL+F https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md) to craft the metadata.

Just an opinion, but I feel like the way badgeNums are calculated is extremely specific.

I'm trying to see how else it would be done/possible without the possibility of someone creating fake badges [eg, buying an artist badge, but paying yourself]. You can track provenance and count the badges through changes.

I'd be extremely interested in helping out with the JS and even the solidity for the initialise() function

Yeah, I realised this is going to be a larger lift than expected. I have a ticket for this on the front-end, which ties into this.
We need to create and publish the NFTCIDs related to the badges that have already been bought in order to add it to the initialisation. This will then also be used to publish NFTCIDs to IPFS when MGCID are created or changed.

Codecov Report

Merging #19 into master will decrease coverage by 12.84%.
The diff coverage is 46.83%.

@@             Coverage Diff             @@
##           master      #19       +/-   ##
===========================================
- Coverage   85.64%   72.79%   -12.85%
===========================================
  Files           7        9        +2
  Lines         202      261       +59
  Branches       33       40        +7
===========================================
+ Hits          173      190       +17
- Misses         29       71       +42

Impacted Files
Coverage Δ

contracts/InitBadges.sol
0% <0%> (ø)

contracts/OldUjoPatronageBadges.sol
0% <0%> (ø)

contracts/UjoPatronageBadges.sol
100% <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 3b3f5cf...b89cdbb. Read the comment docs.


Transaction Status should differentiate between InBlock and Finalized.

Currently the RPC stream returns Finalized event, whenever the transaction is included in block, which obviously is not technically correct.
We should rename current Finalized event to InBlock and introduce a new event that is triggered by actual finality.
Requested by @jacogr some time ago, but I didn't have time to look at this yet, happy to mentor though and help with the issue.

We should rename current Finalized event to InBlock and introduce a new event that is triggered by actual finality.

The chain state doesn't know that well about what's actually finalized

Yes I know, but I imagine that it will require another stream of events coming from the consensus protocol about finalised hashes, that can in turn be used by the transaction pool watcher to trigger these events.
It's not going to be trivial, for sure.

I see, or the API code could correlate this a bit higher-up in the stack, by watching for finality notifications.

Huge +1 to this. This was deeply confusing to discover that Finalized here did not mean what you might reasonably intuitively expect it to mean.

CC @jacogr
We now have events for:
inBlock, retracted and later for finalized or finalityTimeout
note that only the latter two will terminate the stream.


WAR/EAR plugins - Add consumable configuration for WAR (aka outgoing variant)

Edit:
Currently, if you want to consume the war produced by the WAR plugin, for example in the EAR plugin, you still have to use the old archives configuration by doing something like this:
dependencies {
    deploy project(path: ':warProject', conf: archives)
}

It should work like this:
dependencies {
    deploy project(':warProject')
}

And this should be implemented by providing a proper outgoing variant (consumable configuration) in the WAR plugin and consuming that in the EAR plugin.
Ideally, the component registered in the WAR plugin for publishing should then also be based on that configuration using an AdhocComponentWithVariants (at the moment it is a custom component implementation). Then local/published consumption would be aligned and easier to customize using existing APIs.
Original Issue Description
Given:
apply plugin: 'ear'
dependencies {
    //following dependencies will become the ear modules and placed in the ear root
    deploy project(':war')
    //following dependencies will become ear libs and placed in a dir configured via libDirName property
    earlib group: 'log4j', name: 'log4j', version: '1.2.15', ext: 'jar'
}

The mywar project uses the war plugin and seems to work fine, creating a war archive.
However, when I try to assemble the ear, Gradle creates a jar archive of the war project and includes the jar as an ejb dependency! Even the application.xml says that it's an ejb.
Expected Behavior
The "war" is placed inside the ear.
Current Behavior
The content of the "war" project is packaged as "jar" and placed into the ear.
Context
Migrated from GRADLE-1912 with 29 votes
Forum discussion
Workaround
dependencies {
    deploy project(path: ':war', configuration: 'archives')
}

Your Environment
This has been broken since 1.0-milestone-5

With the addition of variant aware dependency management in 3.4, we now have the necessary infrastructure in place to solve this transparently. I think this could be a relatively easy win and remove a big head scratcher for newcomers.

With the addition of variant aware dependency management in 3.4, we now have the necessary infrastructure in place to solve this transparently. I think this could be a relatively easy win and remove a big head scratcher for newcomers.

Can anyone link to a description on how to use the variant awareness in 5.*
I will be happy to fix this.

See this discussion on modeling the consumable variants for WAR/EAR correctly:
https://discuss.gradle.org/t/why-do-wars-have-no-dependencies-with-maven-publish/33513
You can already do this manually in your builds/custom plugins.
This should still be improved in the Gradle core plugins to have a working solution out of the box.

Branch is https://github.com/gradle/gradle/tree/cc/dm/issue-1353
It contains some changes to the JVM API which may be worth integrating in 6.7 before it's out.

Bump.

This is also slightly related to #20547. Ideally I could imagine a setup for the war plugin which is closer to what java-library offers.  So instead of only having providedCompile and providedRuntime it could offer:

Consumables - as discussed above
Buckets for defining dependencies - Here one could consider introducing proviedImplementation, providedApi, and providedRuntimeOnly - in symmetry to what java-library offers - and then deprecate providedCompile and providedRuntime (see also #20547)
Resolvables  - right now the war plugin and IDEA resolve  providedCompile and providedRuntime. It would be cleaner to have something like providedCompileClasspath and providedRuntimeClasspath for these cases I think.

With proper Consumables, the war plugin could probably use the AdhocComponentWithVariants for publishing and would then no longer need and custom Component implementation.

Not only the war, but also the ear plugin should provide outgoing variants, so that you for example compose multiple ears properly. If you e. g. currently try to depend on an ear built in an included build, you get a complaint that Gradle could not decide between earlib and deploy variants which have identical attributes and no artifact. See https://discuss.gradle.org/t/composite-builds-and-an-ear-project/46345


Fix sample app coroutines onstop

Description
Fixed an issue where the sample app samples list screen elements were still active even when it was not active in the backstack.
This is because the PermanentChild was actually being called on SamplesContainerNode and not SamplesSelector. This meant that the children existed outside of the backstack and were never paused/stopped.
Also prevented the teaser NavModels from running when stopped.
Check list

[ ] I have updated CHANGELOG.md if required.
[ ] I have updated documentation if required.

We could potentially wait for 1.1.0? This only impacts Samples, but I think the NoOpNavModel class has reason to exist in the core API based on this usecase


Update DO client lib and use DetachByDropletID

This patch updates the Digital Ocean client library to v1.0.0, and uses
the DetachByDropletID function instead of Detach to to detach volumes
from droplets.
Fixes #431

Codecov Report

Merging #496 into master will increase coverage by 0.05%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #496      +/-   ##
==========================================
+ Coverage    30.5%   30.56%   +0.05%
==========================================
  Files          29       29
  Lines        1780     1780
==========================================
+ Hits          543      544       +1
+ Misses       1179     1178       -1
  Partials       58       58

Impacted Files
Coverage Δ

api/types/types_localdevices.go
79.24% <0%> (+1.88%)
: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 7e5e973...d933542. Read the comment docs.

I'm not sure if you should wait for a official response from DO.

Hey folks, the people responsible for this part of the system are out this week, they'll be back on monday and we should have a final decision if this call will go away or not.

https://github.com/digitalocean/godo/pull/136#issuecomment-290736929

@klausenbusk I don't think it really matters. I wanted to switch from Detach to DetachByDropletID anyways. I actually did not see originally that your issue was a PR removing Detach entirely.
Whether it goes away or not, I'd still rather move to the other function, which is what this PR does. But we are in no rush to merge this one, so I'm happy to see what they come back with next week.


Update upgrade script to point to 1.4.1

Purpose
Update upgrade script to point to 1.4.1
Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

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


New name for raffle's

Since we most of the time use multiraffle,
i hate to type multi always.
How about
# old
!multiraffle

#new
!multiraffle
!mraffle

# maybe if multiraffle module active
!raffle

# old
!raffle

#new
!singleraffle
!sraffle

something like this, not sure what exactly about !raffle if only multi or still a single raffle.

For multiraffle
!raffle -m

For single raffle
!raffle

I would prefer this solution

How about just !multi Keepo no ones gonna see you type it anyway(if its in forsens channel)

I'd prefer to leave !multi open for another command
On Mar 15, 2016 03:33, "NotDefendotKappa"<EMAIL_ADDRESS>wrote:

How about just !multi Keepo no ones gonna see you type it anyway(if its in
forsens channel)
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/pajlada/pajbot/issues/234#issuecomment-196621654

I think this can be closed !mraffle and !sraffle is a good solution


Update Composer dependencies (2020-10-28-00-12)

Visual regression test passed!
View the visual regression test report


submanifold sm wedge error (brombo/galgebra#38)

Reconstructed from a google snippet:
opened on Apr 29, 2018 by @lowchlg
from sympy import symbols, sin, pi
from ga import Ga
coords = (r, th, phi) = symbols('r,theta,phi', real=True)
sp3d = Ga('e_r e_th e_ph', g=[1, r2, ...
sph_uv = (u, v) = symbols('u,v', real=True)
sph_map = [1, u, v] # Coordinate map for sphere of r = 1
sph2d = sp3d.sm(sph_map,sph_uv)

Traceback (most recent call last): File "<pyshell#6>"", line 1, in sph2d = sp3d.sm(sph_map,sph_uv)
SM = Sm(*kargs, **kwargs) File "c:\Users\lcl\Downloads\galgebra-master\galgebra-master\galgebra\ga.py", line 1818, in init
self.wedge_print = kwargs['wedge']
KeyError

Fixed in 37e78bae85747752dd7cc0039f89db5f39d43b24


cache dependencies across acbuild invocations

I know this goes against the design goals of acbuild (or at least how I interpret them), but it'd be really nice if acbuild could cache dependencies across contexts.  Every time I do acbuild, acbuild dependency add …, acbuild run, acbuild end, the dependency gets downloaded, which is much slower than I'd like.

https://github.com/appc/acbuild/issues/125

Yep.  Closing.  Thanks!


Bug - Developer Experience: npm link woes

On our Development wiki page, we currently list the following steps:

Clone the repository: git clone --recursive https://github.com/onivim/oni.git

--recursive will also update submodules (which are required to build Oni)

cd oni to navigate to the root folder
yarn install to install the project dependencies (If yarn is not installed, use npm install -g yarn).
npm run build to build the project
npm link to register the oni command in the shell, against the local build.

This worked fine for a while, until we switched to yarn. It seems that yarn and npm don't play well together... And the npm link command at the end is unfortunately not reliable when we use yarn install prior.
A few things:

First, we should standardize on just using yarn version of commands to avoid confusion - so we should change npm run build to yarn build
Second, we should find a replacement for npm link. Unfortunately, the yarn version doesn't seem to work in parity. The only reason we need to the npm link call is to create a global shortcut for the development build of Oni - an alternative here would be to write a shell script for each platform (or in a cross-platform way, if possible), to achieve the same goal. On OSX / Linux, it seems relatively straightforward to create a symlink in /usr/local/bin, but I'm not sure the best way on Windows... perhaps we could write a powershell script to add to the path?

TL:DR - A few things to make the development / set-up experience clearer:

Standardize to use yarn versions of commands vs npm
Replace npm link with something else that we can use with yarn - this might involve writing custom scripts for each platform, worst case.

@texhnolyze re. the wiki pages you can edit those on github once PR is in you don't need to make a PR for the wiki

This can be closed now as it was merged in #2177, forgot to reference the issue in my pull request. I also updated the wiki docs for the dev setup to include yarn as an installation dependency and to run all previous npm run and npm link commands with yarn instead.

Yep, looks like the first bullet point here was covered in #2177 so I'll close this out.
We've got a much more indepth ticket for a link alternative I think over in #1707, so I'll close this out.
Thanks for the contribution @texhnolyze!


Latest version needs to be released on PyPi

dj-paddle version:
Django version:
Python version:
Operating System:

Description
The latest version with the Checkout ID extended to 64 Chars is not on PyPy - it's still installing the old version.
What I Did
pip install dj-paddle

Please could we get an update on when the next version is going to be released?

Hey @sebs-code and @Wolf-Byte, I just released a new version (https://github.com/paddle-python/dj-paddle/releases/tag/v0.1.2) for your convenience. However, the reason I was hesitant to do so before is, that the latest changes are not reflected by the documentation. While I'd love to see docs and releases go hand-in-hand, I'm lacking time to do so on my own right now and appreciate any support.


meltano invoke writes passwords into temporary config files during execution

Meltano encourages you to manage passwords and other sensitive configuration using environment variables (or .env) so they don't end up checked into the repo, but does write these passwords down into the file system when generating the config files for Singer taps/targets, Airflow, or Superset (as of https://github.com/meltano/meltano/pull/6031). They'll also show up in meltano invoke --dump=config <plugin>, as that returns the exact file that's passed to the plugin in question. These files are cleaned up once meltano invoke completes (which is why --daemon flags don't work: https://github.com/meltano/meltano/issues/3440), but are still as long-living as your web UI or scheduler. This has potential security implications.
Since the superset_config.py config file we generate for Superset can contain arbitrary code, we could read the values from the environment variables there instead of hard-coding them into the file. This is not an option with Airflow or Singer, as airflow.cfg and config.json are simple serialized dictionaries.

Logged here, follow up from our discussion on rewinding this for Airflow:

https://github.com/meltano/meltano/issues/6110

It's different for Singer because we are the tool running the connector. But if we detect we are running an SDK tap or target (or another tap/target which supports --config=ENV), then even for those Singer plugins we could completely avoid a stored file with cleartext.


Resolves some more build warnings on Library project

This PR focuses a bit on Lists and some related upstream classes/interfaces.
Any feedback is welcome

I will revisit this after #4244 is approved and merged so adjust it's usage here too and will look at the rest of @bdukes suggestions shortly. I put it on hold to prevent an accidental merge.

@bdukes as discussed in #4242 I have refactored this to use DI for eventLogger in https://github.com/dnnsoftware/Dnn.Platform/pull/4243/commits/639ae56c6eaf0c9879e25c64d6b4f175766fe4bd
Also merged all comments corrections above, I think it's good to re-review now. Thanks for all the feedback

I also have 2 tests to adjust for DI, I'll handle that shortly...

I rebased on latest changes from develop and the tests should now be fixed (once it builds)


Migrate to EventStreams (SSE)

Hi,
Wikimedia is planning to decommission the socket.io based RCStream in July this year.
A new service called EventStreams is available in its place.

https://blog.wikimedia.org/2017/03/20/eventstreams/
https://wikitech.wikimedia.org/wiki/EventStreams
https://phabricator.wikimedia.org/T156919

Hi,
thank you for the news!
We will migrate to EventStream ASAP.
Andrea

Just a reminder that we will be deprecating RCStream in a few weeks.  The deadline for switchover is July 7th!

Hi @ottomata, thank you very much for the reminder!
We have already developed the new connector, and we are goin to push it in the master branch in the next weeks.


PoshSNMP can not file an Issue

Hi!
I found no Email nor I can file an Issue for the PoshSNMP repository.
Is this intended ??

@Kriegel I don't think I've touched that Repo in years, it can probably be considered dead. You can take the existing module and update it though. There's lots of other SNMP modules out there too.

@JustinGrote Thank you for clarification!


Small optimization in hdf5 unpack_data

Use numpy operations to build raw data block.

Current coverage is 100.00%

Merging #309 into master will not affect coverage as of 7d35642

@@            master    #309   diff @@
======================================
  Files           41      41
  Stmts         1876    1881     +5
  Branches         0       0
  Methods
======================================
+ Hit           1876    1881     +5
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of 7d35642

Powered by Codecov. Updated on successful CI builds.


ofMany fails when using only aggregate or when column is null

Laravel Version
10.16.0
PHP Version
8.2.7
Database Driver & Version
No response
Description
The ofMany function in CanBeOneOfMany trait breaks when only providing the aggregate parameter with a closure because it tries to use strtolower with the closure, and if the column is set to null (wich the DocComment says it can) it breaks again trying to use array_key_exists on null.
Both problems can be fixed changin lines 79-82 with:
$columns = is_string($columns = $column) ? [
    $column => $aggregate,
    $keyName => $aggregate,
] : ($column ?? []);

and letting the default values of column and aggregate to null.
Steps To Reproduce
Create a Model with the following relation:
public function books(): HasMany
{
    return $this->hasMany(Book::class);
}

And any of the next relations:
public function book(): HasOne
{
    return $this->books()->one()->ofMany(aggregate: fn ($query) => $query->where('some_field', true));
}

public function book(): HasOne
{
    return $this->books()->one()->ofMany(null, fn ($query) => $query->where('some_field', true));
}

Thanks. Are you willing to send in a PR?

I don't see this way of using ofMany documented anywhere in our documentation. Perhaps the DocBlock should be changed.


Question about the design of QGN

Hello~ Thanks for your great work!
I have some question about the label assignment in QGN. It seems that you follow the design of "End-to-End Object Detection with Fully Convolutional Network". Have you tried the label assignment proposed in OneNet (What Makes for End-to-End Object Detection?), What about the performance?

Hello~ Thanks for your great work! I have some question about the label assignment in QGN. It seems that you follow the design of "End-to-End Object Detection with Fully Convolutional Network". Have you tried the label assignment proposed in OneNet (What Makes for End-to-End Object Detection?), What about the performance?

Thanks for your ask, we temporarily define two label-assignment methods as "sum" and "multi". The two methods are generally similar, ”multi“ has 0.1% AP gain than "sum" at some settings.


[FR] Add "both" option so Inbox folder and note are not mutually exclusive

I think it's great that the latest update added support for an inbox folder. However, I don't want to give up the inbox note I have for quick thoughts that don't necessarily warrant a full note. Therefore, I think inbox folder and inbox note shouldn't be mutually exclusive, e.g., there should be a third “both” option.

Interesting, I hadn't thought of this use case.
Instead of supporting a "both" option, I wonder if it makes more sense to allow configuring multiple inboxes. I was thinking of something similar to how the folder templates feature is implemented for the Templater plugin. You could have two inboxes, one setup for a note and one setup for a folder. This would also support if you wanted to have multiple inbox notes or multiple inbox folders.

That sounds like a good solution!

I'd love to have several Inbox options as I want to physically separate between stuff that I have to do at work from Life stuff. Both inboxes needs to be processed, but at (very) separate times. Reduces my clutter :)

Added in version 3.0.0!
This ended up being a bigger change than I anticipated. Please let me know if your settings don't migrate over smoothly.


Zero time defaults of hour="0" minute="0" do not work

Try using:
<input datetime-picker ng-model="testdate" date-format="MM/dd/yyyy HH:mm" hour="0" minute="0"/>
You will see it does not respect the defaults, but will substitute time with the current time.

Problem is on line 237 and 238.
To fix it replace both the lines with:
var hour = (scope.hour == 0 ? 0 : (scope.hour ? scope.hour : today.getHours())); var minute = (scope.minute == 0 ? 0 : (scope.minute ? scope.minute : today.getMinutes()));
Above code be better written, due to lack of time i have written this to fix my issue.

can this bug please be fixed? there is a pr for it. i do not want to hack up a plugin as it causes confusion for the other devs.

An apparent workaround is to set it to '60' instead of '0'.


change submit button selector to get the right button

Description
Due to the anchor linking of heading elements, the logic was selecting that link and tying the action there instead of the submit button.
I also made url parsing logic support hlx.live and hlx.page urls while I was in there
Related Issue
See: #209
Motivation and Context
a user sent me a screenshot of the previous experience and was having trouble getting the project added to their sidekick. the user is non technical, and was putting in the hlx.page preview url, so it made sense to me to add support for those as well.
How Has This Been Tested?
Tested locally to ensure both GitHub and hlx.page/live urls work.
Screenshots (if appropriate):
Types of changes

[x] 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 change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@shsteimer thanks for the fix! Can you please add a test URL so the PSI check can run?

@rofe I'm struggling to get non-main branches on my fork to render
https://main--helix-website--shsteimer.hlx.page/tools/sidekick/ works
https://sk-gen-fixes--helix-website--shsteimer.hlx.page/tools/sidekick/ gives me a 404. any suggestions here? FYI probably won't get a chance to work on this much more til I'm back in the states next week.

@rofe I had to push a new branch to get it to render as https://sk-gen-fixes--helix-website--shsteimer.hlx.page/tools/sidekick/ just gives a 404
so closing this in favor of https://github.com/adobe/helix-website/pull/211 should be exact same code just with psi check


Add XITY to starters

This PR add XITY starter
Please supply the following information:

http://xity.now.sh
https://github.com/equinusocio/xity-starter

Thanks!

Thank you for this awesome tool!


Add option for overwrite uploaded files

Overwrite existing file uploads by
LABEL_STUDIO_OVERWRITE_FILE_UPLOADS=true

Closed as too outdated.


[REPOSITORY] Egeria Event schema integration connector

Name
egeria-connector-integration-event-schema
Owner
davidradl
Deliverable
Provides an integration connector that extract event schemata from a schema registry (including Confluent schema registry). The connector will be a polling connector and will look in Egeria for new topics that if present in the confluent registry, the associate schema elements will be brought into Egeria.
Build, test and CI-CD process
Answering the questions in order:

as usual
Gradle
Java
yes
same as core Egeria
same as core Egeria
I don't know what this means?

Dependencies
Core Egeria and whatever libraries are required to connect to the schema registry
Justification
This is no natural place for Event schema content to be placed in existing Repositories
Assumptions
Yes all true
Additional Information
Testing may require Karapace an open source schema registry with the same API as Confluent Schema registry
Work Plan
Before creating the repo

[x] review overall request & get clarifications
[x] get approval on developer/TSC call from maintainers

Creating the repo

[x] Create the repo under the odpi organization (default gitignore, license, readme)
[x] Setup branch protection rules
[x] Set pull request options (allow merge, squash, rebase, suggest updating, allow automerge, do not delete head)
[x] Update security settings in repo (policy, advisories, alerts)
[x] set up permissions

First steps

[ ] Initial code-drop (author)

Getting CI/CD started & refining settings

[x] Add initial build script for PR (including gradle wrapper if required)
[x] Add initial build script for merge

Further Refinement

[ ] Add link in egeria docs to new repo describing purpose etc
[x] Add required credentials for publishing to container repos, maven central etc
[x] Add artifact signing if needed
[x] Add dependabot config
[x] Add CodeQL
[ ] Add to LFXSecurity
[ ] Add to LFAnalytics
[x] Add check for stale defects
[x] Add standard issue tags

Release

[ ] Add release pipeline

No additional tags added -- they are inherited from top level odpi. We have too many on egeria, and need to review/consolidate before we push out to all new repos.

@davidradl A few final tasks to do - but perhaps you could take a look.
I've used a template this time with some dummy code - just enough to get a ci/cd job running & be able to configure the appropriate checks and settings

Note: please leave open. still trying to get the LFAnalytics sorted with the LF.
Two more tasks

[ ] Add to connector catalog
[ ] update template in egeria with above

Here are some notes I took as I went through some of the Kafka documentation - please feel free to add/modify/correct..
Confluent Schema Registry Thoughts
Date: 2022-05-06 09:28
Schema Registry Purpose
The purpose of the schema registry is to share message schemas between producers and consumers so that they can be mutually understood as well as to evolve in some careful ways. Schema Registry is community license - but some features require Enterprise license. Schema registry is available within the Confluent Control Center tooling (also community licensed) and via Restful calls.
Design concepts - Schema Registry Schema Linking for Confluent Platform Developers | Confluent Documentation

Producers and consumers can register their schemas automatically
Each registered schema has a globally unique ID (within a cluster)
Kafka is backend of schema registry (within a cluster)
A topic contains messages and each message is a key-value pair

either the key, value or both can be serialized as Avro, JSON or Protobuf
Kafka topic name can be independent of the schema name
Subject is a scope with which a schema can evolve
There are three different subject name strategies
Default subject name strategy is derives subject name from topic name

A registry can contain multiple contexts that act as namespaces to support activities such as lifecycle management between dev, test, staging, prod for example.
Schema linking now available - this supports different scopes within a registry and helps sync schemas to other clusters in the deployment Schema Linking for Confluent Platform Developers | Confluent Documentation - this creates exporters..
Confluent replicator can migrate schemas from one schema registry to another and automatically rename subjects on the target registry

Subject naming strategy - Formats, Serializers, and Deserializers | Confluent Documentation

Topic Name Strategy - default - subject derived purely from topic - all messages in topic must have same schema
Record Name Strategy - multiple schemas in a topic. Topic can have multiple subjects.

Issues being addressed by Schema Registry

Track (and to a limited degree manage) schemas used within a Kafka cluster
Pass schema ID within the message rather than passing the entire schema (at least for Avro and Protobuf) - smaller messages
Some amount of schema evolution
Support for contexts (namespaces) within the registry to support lifecycle
Some schema runtime validation (within constraints)

Limitations of Schema Registry

Schema IDs are only unique within a single cluster
Many of the features of the tooling only support the default subject naming strategy
Seems to be limited value if message schemas are JSON

Egeria integration considerations

Topology matters - schema IDs are unique only within a cluster; replication and more sophisticated use of contexts requires Enterprise features such as replication and Linking.
Lifecycle approach matters - contexts, deployments..
Schema migration is limited
Subject naming strategy really is driven by the message patterns you want to implement
There does not seem to be an architected approach for Topic naming - perhaps Egeria can help here
What else?

Thanks @dwolfson . I thought I would add here the idea we are considering that the Strimzi connector could pick up the subject naming strategy from the CRD, Egeria could store it in the metadata associated with the Kafka Topic, such that when the Event schema integration connector runs, it gets all the relevant topics from Egera and then can use the subject naming strategy information from Egeria to  look for the subjects that correspond to the topic. Exactly what would be stored in Egeria to represent the subject name strategy has not been agreed yet; maybe the subject naming strategy name is enough.

only minor docs remaining


Is it possible to add a button inside the carousel to delete?

I'm creating a form where I want the user to be able to add photos and I'm loading them into a carousel, but I would like to give them the option to delete one of the photos.

You must update adapter with new photo list.


pkg/prometheus/promcfg.go: Only append relabelings if EnforcedNamespaceLabel value is set

Only append relabelings if EnforcedNamespaceLabel value is set.
cc @s-urbaniak @brancz

lgtm on green

Not sure what we could add to our e2e tests to improve them? As our openshift e2e tests caught this. I added a unit test that failed before this change.

We could run promtool checks against all generated configs?

Not sure our e2e tests cover this case, because the pods would not be up and running as prometheus would reject the invalid configuration.

Oops I understand now. https://github.com/coreos/prometheus-operator/blob/be1c7825adbfe0cd6e3bf94dec77060be968f752/pkg/prometheus/promcfg.go#L557
This line needs to be outside of the if statement. We need to enforce no matter if there are relabeling rules defined or not by the user.

@brancz good catch! PTAL, thanks!

lgtm on greene

lgtm :+1:


refactor: Updated trainee-profile endpoints

Naming convention refactored (ContactDetails -> TraineeProfile)
Updated end-points and property types

TISNEW-3946

Add fields for FormR pre-populated data
Add tests

TISNEW-3946

The ignored repository test might need to be deleted later, as we use mockito to do unit tests, no need to set up a db to do repository unit tests. The real database should be used in integration tests. (My own humble opinion)


Error message color is not legible

Feedback received:
" The Error background color is Dark Red/Maroon , not much suitable to read for a person with normal eyesight.(Already reported in previous release)"

This affects light mode only


CORS Error when using GATSBY_MEDUSA_BACKEND_URL env variable

My server deployed to Heroku successfully. Unfortunately, deploying my Admin panel gave continued CORS errors when interacting with the backend despite properly updated environment variables.
The issue appears to be with the environmental variable GATSBY_MEDUSA_BACKEND_URL not taking precedence during loading. I overcame this issue in the Admin project in Chrome and FireFox on a local development with deployed Medusa backend server:

Open Gatsby Admin project
Go to file config.js inside src\services directory -> change line 3 to let medusaUrl = "YOUR DEPLOYED MEDUSA SERVER"

Go to file request.js inside src\services directory -> change line 3 to let baseURL = "YOUR DEPLOYED MEDUSA SERVER"

No more issues after changing those two variables and removing GATSBY_MEDUSA_BACKEND_URL as an environmental variable from the Admin project! Also, to apply this solution, delete the ADMIN_CORS variable from your deployed Medusa server so that it defaults back to the localhost:7000 that it is expecting. I'll be working on getting it all deployed today so stay tuned! 😃

Update: I'm not able to comment in the Discord, but found my solution while reading this chat and this other storefront issue.

@cboydstun Glad to hear it worked out!
Irt. not being able to comment in Discord, can I get you to elaborate? Have not heard of it before.


Changing the desired rocket angle has no effect.

Even if I change the desired rocket angle, the simulation still solves to a desired rocket angle of 0.

Oh sorry, I haven't implemented that yet. I'll try to do it asap (should be pretty easy)!

Hey. I would love to see your solution. I tried going through and changing/adding things to make it work but I did not manage to get the rocket to recognize the desired angle. The graphs did later on show the new desired angle though. At some point I managed to break the entire thing.
Really nice code by the way. It was quite easy to understand going through it. Just my lack of knowledge could not get it working.

Hey. I would love to see your solution. I tried going through and changing/adding things to make it work but I did not manage to get the rocket to recognize the desired angle. The graphs did later on show the new desired angle though. At some point I managed to break the entire thing.
Really nice code by the way. It was quite easy to understand going through it. Just my lack of knowledge could not get it working.
As you can see I am new to github too. Accidentally closed the issue. My bad

Hey. I would love to see your solution. I tried going through and changing/adding things to make it work but I did not manage to get the rocket to recognize the desired angle. The graphs did later on show the new desired angle though. At some point I managed to break the entire thing.
Really nice code by the way. It was quite easy to understand going through it. Just my lack of knowledge could not get it working.
As you can see I am new to github too. Accidentally closed the issue. My bad

Ok, I added it. Now it should work.
If you want to see which modifications I made, you can look at this commit: 6870bc70c61195ea753435acfc6e6f10365852f1

Thanks. That was fast.


feat: simplify CLI usage

This shouldn't break previous valid usages
Sometimes when I want to test some webxdc app real quick I stop and think whether it's worth spending time on trying to recall how to use this tool. This should make things easier for people like me, and new users.

this is a bit problematic, if the command is run without subcommands it should print the help, not try to use run, I think current behavior is fine, and personally, I never run webxdc-dev manually in any of my apps, one will use a script in package.json for that, so I think this is not necessary
closing stale PR

this is a bit problematic, if the command is run without subcommands it should print the help

A list of commands that don't require arguments:

ls
nano, vim
code
vite

For help there is the --help argument, which is pretty much the standard.

I never run webxdc-dev manually in any of my apps, one will use a script in package.json

Then we'd also need to rewrite README, because the global installation method seems to be the recommended one.
Not every app requires a package manager.

closing stale PR

It's not stale anymore, so I'll reopen.

this needs to be rebased


I can't consume kafka messagae at same time.

Thank you for your kafka code.
I want to consume kafka message only when more than 10 messages have accumulated in Kafka. (or many messages)
In kafkajs, consumer do not wait when kafka message piled up in kafka.
Is this something that can be implemented?

@AngPuoSyer Thank you for your comment.  As you mentioned, I will use maxWaitTimeInMs and minBytes, maxBytes. these method looks good.


Fix relative links in alerting tutorial

Links need to go up one more level.
Fixes: https://github.com/prometheus/docs/issues/2173
Signed-off-by: SuperQ<EMAIL_ADDRESS>

Thanks!


fix/update link

"../northstar-installers.md#0negal-viper" redirects to "https://github.com/R2Northstar/NorthstarWiki/blob/main/docs/northstar-installers.md#0negal-viper" but should redirect to https://github.com/R2Northstar/NorthstarWiki/blob/main/docs/installing-northstar/northstar-installers.md#0negal-viper

Thanks for the heads-up. Linking the GitHub page directly is not the best solution as it redirects one back to GitHub when browsing on https://r2northstar.gitbook.io/ ^^
I just fixed the relative link instead now in 036f84dace437a45f3766d291bd73023b5e5da85


提一嘴SSH

ssh<EMAIL_ADDRESS>ssh: connect to host 127.17.0.X port 22: Connection refused
请确保启动了ssh服务器
sudo apt-get install -y openssh-server
service ssh start
关于vscode连接docker：

附加 vscode 选项 需要 安装插件Dev Containers和Remote Containers（好像得有Dev Containers？）才会有
https://stackoverflow.com/questions/68197281/vscode-missing-option-attach-visual-studio-code

@sanbuphy 你zs一下这个问题

在 windows 10 下创建的 docker 容器，在 ssh 连接容器时
ssh<EMAIL_ADDRESS>
如果出现
ssh: connect to host <IP_ADDRESS> port 22: Connection timed out

可以试一下映射一下 22 端口，将容器的 22 端口映射到主机的 5060 端口（端口可以自己选）
docker run -it -p 5060:22 registry.cn-hangzhou.aliyuncs.com/hellofss/kuiperinfer:datawhale /bin/bash

然后使用 5060 端口进行 ssh 连接
ssh<EMAIL_ADDRESS>-p 5060

The authenticity of host '[<IP_ADDRESS>]:5060 ([<IP_ADDRESS>]:5060)' can't be established.
ECDSA key fingerprint is SHA256:dvwO/nKcbfWcoPUwNoGMSoW1Q97CN0kLZfLXUUN6QMY.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '[<IP_ADDRESS>]:5060' (ECDSA) to the list of known hosts.
<EMAIL_ADDRESS>password:
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux <IP_ADDRESS>-microsoft-standard-WSL2 x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management:     https://landscape.canonical.com
 * Support:        https://ubuntu.com/advantage

This system has been minimized by removing packages and content that are
not required on a system that users do not log into.

To restore this content, you can run the 'unminimize' command.

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.


Move Fibre Channel Driver

Moving driver retaining commits.

@msau42 Thanks for the review! I'm still trying to test it out with a fibrechannel backend, also need to look into unmount like you mentioned above.

I didn't realize that a fc driver wasn't already in the kubernetes-csi drivers repo, and that this is a new driver from scratch. In that case, feel free to squash the commits. I think at least splitting out the vendors updates would be useful.

Agreed

In general, this could benefit from unit tests, especially for non-trivial functions where you need to handle/parse input and do error handling.

+1 Will add Unit Tests as well


generated code for composition in subpart and incident

Addresses #9 and #16. This is quite a simple PR, just moving the binary operation out of foldl and foldr from subpart and incident into a generated loop. Happy for comments!
I note that the somewhat aesthetically displeasing if statement in the generated method is because Tuple{Symbol} or even Tuple{Vararg{Symbol,1}} is ambiguous when competing with Tuple{Vararg{Symbol}}.
[NOTE] codecov report seems to have false positives. The new tests include testing for errors when the user provides a tuple of arrows that do not compose.

@jpfairbanks good to merge?

Slick use of comptime @slwu89!!


MAINT: Support Python 3.10 (close #79)

[ ] Change base to develop

Numpy issue
https://github.com/fracdiff/fracdiff/pull/80/checks?check_run_id=3801621621
  Failed to build numpy
  ERROR: Could not build wheels for numpy which use PEP 517 and cannot be installed directly

  at /opt/hostedtoolcache/Python/3.10.0/x64/lib/python3.10/site-packages/poetry/utils/env.py:1183 in _run
      1179│                 output = subprocess.check_output(
      1180│                     cmd, stderr=subprocess.STDOUT, **kwargs
      1181│                 )
      1182│         except CalledProcessError as e:
    → 1183│             raise EnvCommandError(e, input=input_)
      1184│
      1185│         return decode(output)
      1186│
      1187│     def execute(self, bin, *args, **kwargs):

Error: Process completed with exit code 1.


Docker compose image versions

Specify the version numbers for images in the docker-compose.yml file. Prevents versioning issues with these services across production and development environments.

In order to make this work on your system, you will need to rm -r ~/data/db . Without doing this, your mongo will crash. If this doesn't work, then try rm -r ~/data/* .

This seems to have fixed the issue. After removing the previous files like suggested, I was able to bring the system up and down without issue.

Since we are now specifying mongo version 5, does this mean we should be using mongosh instead of mongo in the health check? Afaik, mongo was pre-version 5, and mongosh replaced mongo in version 5.

I did see this before and mongo was replaced in version 5 by mongosh. As far as changing it I am not sure.

Since we are now specifying mongo version 5, does this mean we should be using mongosh instead of mongo in the health check? Afaik, mongo was pre-version 5, and mongosh replaced mongo in version 5.

I just added it and ran it locally and it worked fine I can push it to this branch if we want to go ahead with it.

Hold off on this for now, it looks like the mongo shell version is 5.0.1 and the server version is 4.4.6. If we explicitly specify a version number, it will change one of these.
4.4.6 did not work with mongosh locally for me. I'm investigating and trying to setup a dockerfile that will keep the versions the same.

Great


Format email allowing incorrect email addresses

Hi, I am trying to validate an email address with validate() and FormatChecker, but the validation of some invalid email addresses does not raise an error. See:
>>> import jsonschema
>>> jsonschema.validate('@', {'type': 'string', 'format': 'email'}, format_checker=jsonschema.FormatChecker())
>>> jsonschema.validate('@@', {'type': 'string', 'format': 'email'}, format_checker=jsonschema.FormatChecker())
>>> jsonschema.validate('johny<EMAIL_ADDRESS>{'type': 'string', 'format': 'email'}, format_checker=jsonschema.FormatChecker())
>>>

Am I missing something? I believe these are not valid email addresses - the first one has empty local part and domain part, the third has an unquoted @ char. The second one is also broken ;-)
Thanks!

In basically the only way that jsonschema "deviates" slightly from the spec, the email format validator is intentionally simplistic (it literally only checks for @) which is what you're noticing, because validating email isn't typically a thing that makes sense, and providing it allows people to shoot themselves in the foot. I could have sworn this was documented in a way other than just "format doesn't have to validate things even generally", but I don't see it immediately. If it isn't that's certainly a doc bug.
If you really really really want to do it, there probably are libraries that validate email under the RFC and you can plug them in in lieu of the built-in formatter via FormatChecker().checks.
Lemme know if this makes sense (and thanks for pointing out the lack of docs if that actually is missing :frowning:)

Ok, in that case alright. Thank you!