Add new strategy tutorial issue

I'm having some trouble with the following piece of AddNewStrategy file:
https://github.com/Layr-Labs/hello-world-avs/blob/f48f498a52d3a2c8c2386e0f1cd9fb47340b49bc/contracts/script/AddNewStrategy.s.sol#L96
there it tries to reinitialize the stakeRegistryProxy what is not permitted as initializer code can run only once, tried to look for alternatives but the only way to add a new quorum by other means involves passing the operators as long, what I'm missing here ?

Hi @Gajesh2007 - let me know if you have time to investigate? Otherwise I can make time this week to review

Hi @claudiovb thank you for raising this issue. I can confirm that there are multiple issues and outdated libraries with the current master branch. We are close to merging in many fixes to the mainline codebase via these PRs:
https://github.com/Layr-Labs/hello-world-avs/pull/57
https://github.com/Layr-Labs/hello-world-avs/pull/58
If you can bear with us for another few days, we'll have it cleaned up for you and we can retest 👍


Inclusion of functionality from an untrusted source

Tracking issue for:

[x] https://github.com/lurkydismal/lurkydismal.github.io/security/code-scanning/11

Closed with commit f21ab62


Cardy updates ii

Adding

FreeSticker
Map
FeaturedText
TabNav

is it now part of it when we create a component, no matter how incomplete or likely to change it is, it goes in cardy?

I feel like we had a fairly good flow with this back when there was a lot of new and different-from-each-other UI components being built (the good ol' Fractal days). I think you're right – we need to remember to be in the habit of getting stuff into Cardy asap (and we've got a WIP section, so there's not a good reason not to do it that way).

Yea, so maybe it is a start in cardy approach.


Tmds.DBus.DBusException

Hi there,
iam very new to this lib, running on

Linux IR1581 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Distributor ID:	LinuxMint
Description:	Linux Mint 19.3 Tricia
Release:	19.3
Codename:	tricia

dotnet --version gave me:

3.1.101

I've followed thoose instructions. In order to get it working i had to add 2 more things:

curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash -
sudo apt-get install -y nodejs

and:

sudo apt-get install castxml

Once this build was running, i tried to run "ControlCatalog.NetCore", which killed my Cinnamon Session (fallback) and threw the following exception:

Tmds.DBus.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.AppMenu.Registrar was not provided by any .service files
at Tmds.DBus.DBusConnection.CallMethodAsync(Message msg, Boolean checkConnected, Boolean checkReplyType)
at Tmds.DBus.Connection.CallMethodAsync(Message message)
at Tmds.DBus.CodeGen.DBusObjectProxy.SendMethodReturnReaderAsync(String iface, String member, Nullable`1 inSignature, MessageWriter writer)
at Avalonia.FreeDesktop.DBusMenuExporter.DBusMenuExporterImpl.Init() in /daten/dev/csharp/github/Avalonia/src/Avalonia.FreeDesktop/DBusMenuExporter.cs:line 59

I did'nt want to build Avalonia in the first place, but the current nuget-release also doesn't work for me, throwing the following exception:

[Visual] Exception in render loop: "System.InvalidOperationException: Failed to create Skia render target surface
at Avalonia.Skia.SurfaceRenderTarget..ctor(CreateInfo createInfo)
at Avalonia.Skia.DrawingContextImpl.CreateRenderTarget(Size size, Nullable`1 format)
at Avalonia.Skia.DrawingContextImpl.CreateLayer(Size size)
at Avalonia.Rendering.RenderLayers.Update(Scene scene, IDrawingContextImpl context)
at Avalonia.Rendering.DeferredRenderer.UpdateRenderLayersAndConsumeSceneIfNeeded(IDrawingContextImpl& context, Boolean recursiveCall)
at Avalonia.Rendering.DeferredRenderer.Render(Boolean forceComposite)
at Avalonia.Rendering.RenderLoop.TimerTick(TimeSpan time)" (Avalonia.Rendering.RenderLoop #4032828)

Hope you guys can help me a bit.
Thank you!

Tmds.DBus.DBusException

You can ignore that, it means that your DE doesn't support dbusmenu protocol and the app will fall back to in-window menu.

current nuget-release also doesn't work for me

Which version are you using?

Hi,
version is: 0.9.9.

I just figured there is a new version "0.9.10"; same issue.

which killed my Cinnamon Session (fallback) and threw the following exception

You can try removing this line - https://github.com/AvaloniaUI/Avalonia/blob/master/samples/ControlCatalog.NetCore/Program.cs#L61 but I don't think that a missing DBus service is capable of killing the entire session.
Also, show your glxinfo output.

glxinfo: https://pastebin.com/Pi266zuK
Removing the line didn't help either.

Does it crash the entire X server or just the window manager? Are there any window-manager related logs?

Only the window manager is crashing, i will try to find some logs.

https://pastebin.com/8S3sL55i that's at least something...
could this:

ControlCatalog.NetCore: [Binding] Error in binding to 'Avalonia.Controls.NativeMenuItem'.'Command': 'Null value in expression ''.' (NativeMenuItem #5894079)

be the reason?

That's a binding error that can also be ignored. There is still

Jun 26 13:14:48 IR1581 ControlCatalog.NetCore: [Visual] Exception in render loop: 'System.InvalidOperationException: Failed to create Skia render target surface#012   at Avalonia.Skia.SurfaceRenderTarget..ctor(CreateInfo createInfo) in /daten/dev/csharp/github/Avalonia/src/Skia/Avalonia.Skia/SurfaceRenderTarget.cs:line

though. Which is probably caused by 0x0 window size or something like that.
Can't reproduce metacity crash with metacity from Ubuntu 18.04, might be worth reporting that bug to your distro metacity maintainers.

:mips-interest


yet another new bug (as far as i can tell, at least)

crash-2018-11-26_21.15.55-server.txt
it happened when i brokea redwood tree's branches, twice. (using the newest version, the one with the intake overflow already fixed)
(i got no clue on how to tell if this isa problem with DT itself or with the BOP compat, so i'm posting it here, for now)
(modlist included in the crash report)

What do you mean broke it twice?

Fixed same as #168

i mean, the bug happened twice, as in two separate times
sorry for being unclear


EnableMultipleWriteLocations marked internal

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug
This should not be internal.
To Reproduce
Observe the internal-ness
Expected behavior
It should be public
Actual behavior
It is internal
Environment summary
SDK Version: 3.1.1
OS Version (e.g. Windows, Linux, MacOSX) Windows
Additional context
Add any other context about the problem here (for example, complete stack traces or logs).

EnableMultipleWriteLocations is enabled by default. No reason for it to be public.


Passing SRV records (Service DiscoveryInfo) for non-docker tasks

Marathon automatically provides DiscoveryInfo to Mesos when a docker container is launched.
However, the SRV records are incomplete (port information is missing) when the task is a normal CMD action.
It would be nice if we could either post this information manually or have marathon automatically pass this information properly.

@crucidal thanks for creating an issue. Until now Marathon only adds DiscoveryInfo if the app uses IP-per-Task and specifies discovery information.
We merged https://github.com/mesosphere/marathon/pull/3302 yesterday, which makes Marathon always add the DiscoveryInfo and will be included in the next release.
Please re-open this issue if the functionality added in the PR isn't enough.


637 settings view tests

Resolves #
Proposed Changes
-Adding tests for the Setting view and underlying PollingSettings component
How to Test
-Navigate to src/components/Main/components/Settings/index.test.js, remove 'x' before describe.
-Navigate to src/components/Main/components/Settings/index.js and comment out ConfirmationModal
-Run npm test
If the confirmation modal is not commented out, you will see this error "Enzyme Internal Error: unknown node with tag 4" which is due to react-modal using ReactDom.createPortal which is not yet supported in the upgraded version of Enzyme. Here is the PR that fixes the issue but not yet released: https://github.com/airbnb/enzyme/pull/1345
Description of the issue: https://github.com/airbnb/enzyme/issues/1150
Discussed this approach with David and he concurs that we can 'uncomment' that test at some point in the future when Enzyme is released and encompasses the feature that we need.

I think the portal support is in enzyme-adapter-react-16 v1.1.0. I'm going to upgrade and test to see if that's indeed the case.


Django 2.1+ compatibility (tests for 2.2.6)

Previously this Field responded with an attribute error when access directly from the class:
>>> Node.position
Traceback (most recent call last):
  File "<console>", line 1, in <module>
  File "/home/wstott/repos/django-positions/positions/fields.py", line 144, in __get__
    raise AttributeError("%s must be accessed via instance." % self.name)
AttributeError: position must be accessed via instance.

Django admin now relies on the following behaviour:
>>> from examples.nodes.models import *
>>> Node.position
<positions.fields.PositionField: position>
>>> Node.name
<django.db.models.query_utils.DeferredAttribute object at 0x7f6c6b2e9748>

ping: Anything I can do to help get this merged?

Hi @jpwatts do you still maintain this project? I'd love to have @willstott101 features since it's now a more reliable fork IMHO.


load samples from datasets page

on the datasets page it should be possible to load a particular data set in the multi-peptide analysis window
Original issue by @pdawyndt on Sat Oct 06 2012 at 15:54.
Closed by @bmesuere on Tue Oct 09 2012 at 09:39.

Duplicate of #59
Original comment by @bmesuere on Tue Oct 09 2012 at 09:39.


ShowModelResponse is missing several optional properties

On the Ollama API Documentation they show an example payload that includes a details section that isn't present on the C# response model. Additionally, they make note of an optional system property that may contain a modelfile system prompt.
{
  "modelfile": "# Modelfile generated by \"ollama show\"\n# To build a new Modelfile based on this one, replace the FROM line with:\n# FROM llava:latest\n\nFROM /Users/matt/.ollama/models/blobs/sha256:200765e1283640ffbd013184bf496e261032fa75b99498a9613be4e94d63ad52\nTEMPLATE \"\"\"{{ .System }}\nUSER: {{ .Prompt }}\nASSISTANT: \"\"\"\nPARAMETER num_ctx 4096\nPARAMETER stop \"\u003c/s\u003e\"\nPARAMETER stop \"USER:\"\nPARAMETER stop \"ASSISTANT:\"",
  "parameters": "num_ctx                        4096\nstop                           \u003c/s\u003e\nstop                           USER:\nstop                           ASSISTANT:",
  "template": "{{ .System }}\nUSER: {{ .Prompt }}\nASSISTANT: ",
  "details": {
    "format": "gguf",
    "family": "llama",
    "families": ["llama", "clip"],
    "parameter_size": "7B",
    "quantization_level": "Q4_0"
  }
}

These properties are missing from the current ShowModelResponse.

Closed with #35. Once again, thanks for helping out.


tests: Add readonly properties and links to dump tests.

Issue: #985.

I've run into an issue with how readonly interacts with inheritance while writing up this test. From a preliminary discussion with @elprans we decided to restrict the inheritance behavior of readonly which would make the original problematic case illegal. That particular solution is future-compatible and compatible with the current dump test schema. I'll open a separate issue and PR for the readonly problem.

@vpetrovykh  From now on please don't add any tests into dump01.


cabal-install-parsers: update Cabal dependency

Motivation for this change
This also unbreaks haskell-ci.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

Looks reasonable to me.  I've tested that this builds.

Thanks for fixing this!


Add a lower bound to directory

directory <IP_ADDRESS> is a boot library on GHC 7.4, and that version has an incompatible type on getModificationTime. This lower bound precludes those bad build plans.
Please also make hackage metadata revisions to add this bound to older releases as necessary: https://matrix.hackage.haskell.org/package/ghcid#GHC-7.4/ghcid-0.6.9

Thanks! Will go metadata mangling later today.

Metadata now all seems good.

Looks beautiful to me! Thanks a lot.


Fix spelling

The old text doesn't make any sense, I guess it's a typo

The old text is technically correct, if unclear. It refers to the paths specified in ember-cli-build.js, which allow you to change which file will be your 'index.html' and 'tests/index.html'.


delete an 404 url

delete an 404 url:
https://git.k8s.io/minikube/docs/contributors/adding_a_dependency.md
Adding_a_dependency.md has been deleted in this commit:
https://github.com/kubernetes/minikube/commit/f464fa93dbaef63eadc9f54532d62614f6ca1b30#diff-21ec9486a84cff936d6f53e7c77eb0f6
ref:#17649

/assign @zacharysarah

link in document was removed in june in next commit kubernetes/minikube@f464fa93dbaef6

@mhamdisemah not sure that there is a point for that (for korean - perhaps, but for others - no). Dependents content is deleted, what the point to have link to in in localizations?


Add a concurrency example executing a complex graph

@lucteo let's try to move open PRs forward and get them merged, or close them please.


Add quotes via npm script

Now you can easily add a quote to the database with an npm script. Ready for review

There is a problem with the add.ts script. It's not consistent between addQuote requests, It doesn't always go through.

With the latest commit, the script will wait with a callback until the query has finished to process in the backend. This behavior has been tested. Awaiting review

LGTM!


About the training process

Thank you for providing such nice work here. Do you have any plans to release the code of training process recently?

Hi, great to hear that you enjoy our work!
We had released the pretrained models on HQ-YTVIS, however it will take some time to polish the code for training. I'll let you know as soon as we have a more clear idea on the expect time of release.


lpstat -lp not working on MacOS Monterey

Getting
Error: Command failed: lpstat -lp
lpstat: No destinations added.

I think it should be lpstat -l here https://github.com/artiebits/unix-print/blob/d1a652a345afa66078e97548378456b1e1d04d39/src/get-printers/get-printers.ts#L7

Hi @aashutoshrathi did you google Error: Command failed: lpstat -lplpstat: No destinations added? Looks like your system does not recognize local printer.

Hey! @artiebits
I don't have any printers added to my machine. (M1 Pro)
Is there a way to add dummy printers?

that's why it's not working and lpstat -l will not work either.
How to add a dummy printer

Thanks @artiebits


At detectron2 Mask r-cnn Model, outputs of masks are diffrent between onnxruntime and onnxruntime-directml for some type image

The images such coffe bags are diffrent and incorrect.

The images such cartons are same and correct.

The boxes, labels and scores are same and correct, only masks are diffrent and incorrect.
When translated pytorch model to onnx model, there are some TraceWarning as such below.
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/modeling/proposal_generator/proposal_utils.py:106: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if not valid_mask.all():

below is full TraceWarning:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/image_list.py:85: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert t.shape[:-2] == tensors[0].shape[:-2], t.shape
/home2/ros/venv/detectron2/lib/python3.8/site-packages/torch/functional.py:504: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at ../aten/src/ATen/native/TensorShape.cpp:3526.)
return _VF.meshgrid(tensors, **kwargs)  # type: ignore[attr-defined]
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:151: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if tensor.numel() == 0:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:155: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert tensor.dim() == 2 and tensor.size(-1) == 4, tensor.size()
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:151: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if tensor.numel() == 0:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:155: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert tensor.dim() == 2 and tensor.size(-1) == 4, tensor.size()
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/modeling/proposal_generator/proposal_utils.py:106: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if not valid_mask.all():
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:191: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert torch.isfinite(self.tensor).all(), "Box tensor contains infinite or NaN!"
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:192: TracerWarning: Iterating over a tensor might cause the trace to be incorrect. Passing a tensor of different shape won't change the number of iterations executed (and might lead to errors or silently give incorrect results).
h, w = box_size
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/layers/nms.py:15: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert boxes.shape[-1] == 4
/home2/ros/venv/detectron2/lib/python3.8/site-packages/torch/init.py:1404: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert condition, message
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/layers/roi_align.py:55: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert rois.dim() == 2 and rois.size(1) == 5
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/modeling/roi_heads/fast_rcnn.py:138: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if not valid_mask.all():
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:151: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if tensor.numel() == 0:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:155: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert tensor.dim() == 2 and tensor.size(-1) == 4, tensor.size()
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:191: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert torch.isfinite(self.tensor).all(), "Box tensor contains infinite or NaN!"
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/structures/boxes.py:192: TracerWarning: Iterating over a tensor might cause the trace to be incorrect. Passing a tensor of different shape won't change the number of iterations executed (and might lead to errors or silently give incorrect results).
h, w = box_size
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/modeling/roi_heads/fast_rcnn.py:155: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if num_bbox_reg_classes == 1:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/layers/nms.py:15: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert boxes.shape[-1] == 4
/home2/ros/venv/detectron2/lib/python3.8/site-packages/torch/init.py:1404: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert condition, message
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/layers/roi_align.py:55: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
assert rois.dim() == 2 and rois.size(1) == 5
/home2/ros/venv/detectron2/lib/python3.8/site-packages/detectron2/modeling/roi_heads/mask_head.py:139: TracerWarning: Converting a tensor to a Python boolean might cause the trace to be incorrect. We can't record the data flow of Python values, so this value will be treated as a constant in the future. This means that the trace might not generalize to other inputs!
if cls_agnostic_mask:
/home2/ros/venv/detectron2/lib/python3.8/site-packages/torch/onnx/symbolic_opset9.py:5856: UserWarning: Exporting aten::index operator of advanced indexing in opset 17 is achieved by combination of multiple ONNX operators, including Reshape, Transpose, Concat, and Gather. If indices include negative values, the exported graph will produce incorrect results.
warnings.warn(


merge stable

Looks like there's a cache issue on the downloads.dlang.org site for the LATEST file.
$ for i in `seq 0 5`; do curl -s https://downloads.dlang.org/releases/LATEST; echo; done
2.107.0
2.107.0
2.107.1
2.107.1
2.107.1
2.107.1

Whether macos 13 gets the functional version or not is currently luck of the draw.


add byte pricing independent of gas price

closes #262
Add a separate bytePrice field to transaction specs, which allows script execution to be priced separately of bytes.
Open question: Should gas be renamed to something more specific like scriptGas or scriptPrice?

Open question: Should gas be renamed to something more specific like scriptGas or scriptPrice?

Hmmm. We can bikeshed! I feel like coming from Ethereum gas alone is sufficient, but I'm not married to the name.


Unable to display markers

Hey zcreativelabs, thanks for creating react-simple-maps.
I am pretty new to react and front end development so I apologize if I am making some sort of dumb mistake. I have went through my code and compared it to multiple examples that you have up on your page and for the most part everything looks the same/ correct. I've been struggling for a while now to understand why adding markers to my map is breaking my application. Without including Markers and Marker my application works fine, but as soon as I try to add one marker my application no longer renders.
This is all of my code relating to the map:
import React, { Component } from "react";
import { ComposableMap, Geographies, Geography, Markers, Marker, ZoomableGroup, Lines, Line } from "react-simple-maps";
import classes from "./Map.css";
import ReactTooltip from "react-tooltip";

const markers = [
    { markerOffset: -25, name: "Polaris", coordinates: [47.4235, 120.3103] }, //47.4235, 120.3103
    { markerOffset: -25, name: "Titan", coordinates: [32.7767, 96.7970] }, //32.7767, 96.7970
];

class Map extends Component {
    componentDidMount() {
        setTimeout(() => {
            ReactTooltip.rebuild()
        }, 100)
    }

    render() {
        return (
            <div className={classes.Map} >
                <ComposableMap
                    className={classes.Map}
                    width={1000}
                    height={450}
                    projection="albersUsa"
                    projectionConfig={{ scale: 800 }}>
                    <ZoomableGroup disablePanning>
                    <Geographies
                        disableOptimization
                        geography="https://raw.githubusercontent.com/zcreativelabs/react-simple-maps/master/examples/albers-usa/static/states.json" >
                        {(geos, proj) =>
                            geos.map((geo, i) => (
                                <Geography
                                    className={classes.Map}
                                    key={i}
                                    cacheId={geo.properties.ID_1}
                                    geography={geo}
                                    projection={proj}
                                    style={{
                                        default: {
                                            fill: "black",
                                            stroke: "#f73aa9",
                                            strokeWidth: 0.3,
                                            outline: "none",
                                        },
                                        hover: {
                                            fill: "#ec008a",
                                            stroke: "white",
                                            strokeWidth: 1,
                                            outline: "none",
                                        },
                                        pressed: {
                                            fill: "#ef32a1",
                                            stroke: "black",
                                            strokeWidth: 1.2,
                                            outline: "none",
                                        }
                                    }}
                                    data-tip={geo.properties.NAME_1}
                                    onClick={() => {
                                        console.log('This state was clicked:', geo.properties.NAME_1,
                                            "State's Properties:", geo)
                                    }}
                                />
                            ))
                        }
                    </Geographies>
                    {/* <Lines>
                        <Line
                            line={{
                                coordinates: {
                                    start: [0, 0],
                                    end: [-99.1, 19.4]
                                }
                            }}
                        />
                    </Lines> */}
                    <Markers>
                            {markers.map((marker, i) => (
                                <Marker
                                    key={i}
                                    marker={marker}
                                    style={{
                                        default: { fill: "#FF5722" },
                                        hover: { fill: "#FFFFFF" },
                                        pressed: { fill: "#FF5722" },
                                    }}
                                >
                                    <circle
                                        cx={0}
                                        cy={0}
                                        r={10}
                                        style={{
                                            stroke: "#FF5722",
                                            strokeWidth: 3,
                                            opacity: 0.9,
                                        }}
                                    />
                                    <text
                                        textAnchor="middle"
                                        y={marker.markerOffset}
                                        style={{
                                            fontFamily: "Roboto, sans-serif",
                                            fill: "#607D8B",
                                        }}
                                    >
                                        {marker.name}
                                    </text>
                                </Marker>
                            ))}
                        </Markers>
                     </ZoomableGroup>
                </ComposableMap>
                <ReactTooltip />
            </div>
        )
    }
}

export default Map;

When I try to use markers without using ZoomableGroup I get these errors:

When I do include ZoomableGroup I get these errors:

Is using the ZoomableGroup object required for markers? Either way why am I getting these errors?
Any advice or help of any kind would be awesome and thanks again!

Hi @Bog97,
From what I see there could be a problem with your coordinates. The albersUsa projection does not cover the entire globe, so any coordinates outside of the scope of this projection will cause problems. Note that the order of coordinates in react-simple-maps is [lng, lat], it seems your coordinates are specified as [lat, lng] so you might get strange results from that as well.
I copied your code over to codesandbox and switched the coordinates around. I got this:

Hope this is helpful to you.

@zimrick wow thank you so much. Such a small little detail broke my whole application and I just couldn't figure out why that error was being thrown. Thanks again.


Update redhat enforce-victims-rule for CVE tests

Windows Build 5543 outcome was FAILURE using a merge of 5d02c4ff90c3b4efc3f54ba94fc614acda7b785c
Summary: Execution timeout (new); tests passed: 3459, ignored: 192 Build time: 01:41:04


Update docs as per 0.10

It's happening!

Current coverage is 80.03%

Merging #527 into master will increase coverage by +2.20% as of 4782bfd

Powered by Codecov. Updated on successful CI builds.


Update uuid dependency

There's only very few call sites to update and it would remove a deprecated warning from every install.
Changing code this pretty simple as explained here: https://www.npmjs.com/package/uuid#upgrading-from-uuid3
Also it seems at least one call site uses the new syntax: import { v4 as uuidv4 } from 'uuid';, which leads me to believe that just replacing every import with that line allows you to update the uuid dependency to the latest version.

The pr made to resolve this forgot to update the uuid version in package.json

Hi @SamMousa , @kirtan-desai
Thank you for pointing out this issue to us. We will address it in the next testcafe release.


Deprecation warning for date-format

npm WARN deprecated<EMAIL_ADDRESS>0.x is no longer supported. Please upgrade to 4.x.

Seems to come from https://www.npmjs.com/package/junit-report-builder. spellchecker-cli is on version 1.3.3, the latest is 3.0.0.
See https://github.com/tbroadley/spellchecker-cli-action/issues/4

Filed https://github.com/davidparsson/junit-report-builder/issues/42.


Proton: Some text inside message in not visible but present

Is there an existing issue outlining your problem?

[X] I am using the latest version of the provided userstyle.
[X] I have searched the existing issues and they do not solve my problem.

What userstyles are you seeing the problem on?
lbl:proton
Describe your problem.
Some text inside messages is rendered in white colour, and the background is also white, so I cannot see the text.
Attach screenshots.

What browser(s) are you seeing the problem on?
LibreWolf 124.0.1-1
Any additional comments?
When selecting the text as in the screenshot, it is revelaed.

i'm also having the same issue

I find that changing the theme within Proton itself doesn't solve the issue entirely. For example, here's screenshots of a plaintext test email I sent to myself (no styling), and a styled email from a Substack mailing list.
Using Proton's dark theme Carbon with Catppuccin applied via Stylus, the plaintext email is unreadable, whereas the Substack email reads just fine:

Changing Proton's theme to the default light theme Proton, the plaintext email becomes legible, and the substack email loses it's proper styling:

After a bit of fiddling, I've noticed that removing line 61 from the CSS fixes this issue, at least if you're on a dark theme in Catppuccin (Frappé, Macchiato or Mocha) and in Proton (Carbon, Monokai or Ebony):
-    color-scheme: if(@lookup = latte, light, dark);

I'm sure this breaks something if you use another theme combination (particularly Latte), but it works for me on Mocha x Carbon.

@lplawlor commenting out this line still appears to work with dark-mode only for me. Thanks!
Not sure what a good long-term solution is here.
I did notice that it breaks only when first opening a message in Proton Mail (likely because of how the iframe is loaded). After I switch to another message, and then switch back to the previously broken message, it works fine (even without the fix).
Not sure if this helps anyone come to a long-term fix or not, but, I'd say it's still broken as-is since it still requires the work-around to get properly displayed messages on initial load.


[W-10950274] deprecated container v2

ref: W-10950274
This is an alternative version of the deprecated banner (now is actually a "container"). It is at the top of each page of a deprecated version, and the position is not fixed. Otherwise, similar color and feel.
small screen size:

medium screen size:

large screen size:

Thanks for doing this; I assume that Isaac and/or you are going to be using this to share around with stakeholders?  If so, can you make this a draft PR?

add the second canned message listed in https://docs.google.com/document/d/1LTi12VKfHoZUBQleApO4QPo6_dUYep7jREIwT1CJOEg/edit
update the attribute names to olderVersion and noLongerUpdated
fix the "latest version" links:

they now work for beta sites
if a page in an older version doesn't have an equivalent page in the latest version, it will redirect to the latest version's index page instead

See https://www.loom.com/share/a4cff85a28fd417084dc2523c5357003 for detail. @IsaacEldridge to review

@cheungaryk - is there a way to validate this with bundle preview?

I have not found a way for preview to recognize the attributes in ui-model.yml. I only tested using a local build with test-3 UI bundle


feat(elasticbeanstalk): add new check elasticbeanstalk_cloudwatch_enabled

Context
Add a new check that verifies whether an Elastic Beanstalk environment is configured to send logs to CloudWatch Logs. The check fails if the environment is not configured to send logs to CloudWatch Logs.
CloudWatch helps you collect and monitor various metrics for your applications and infrastructure resources. You can also use CloudWatch to configure alarm actions based on specific metrics. We recommend integrating Elastic Beanstalk with CloudWatch to get increased visibility into your Elastic Beanstalk environment. Elastic Beanstalk logs include the eb-activity.log, access logs from the environment nginx or Apache proxy server, and logs that are specific to an environment.
Description
Add new check elasticbeanstalk_cloudwatch_enabled with respective unit tests and metadata.
Checklist

Are there new checks included in this PR? Yes

If so, do we need to update permissions for the provider? No

[x] Review if the code is being covered by tests.
[x] Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings
[x] Review if backport is needed.

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@sergargar Requested changes done 0b8123b


Catalog stuck in refreshing state for several hours

What kind of request is this (question/bug/enhancement/feature request):
This bug was not in v2.5.5. I have checked the logs, the syncing finishes successfully but the state does no change. It only happens with bitnami repo for me. Due to this, my terraform operations keep timing out.
Steps to reproduce (least amount of steps as possible):

Go to global catalogs
Add bitnami repo: https://charts.bitnami.com/bitnami

Result:
The refreshed state should become active after syncing is finished.
Other details that may be helpful:

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.5.6
Installation option (single install/HA): HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
Machine type (cloud/VM/metal) and specifications (CPU/memory):
Kubernetes version (use kubectl version):

(paste the output here)

Docker version (use docker version):

(paste the output here)

I am able to reproduce this issue even on a single node rke node setup running on my localhost.

Was this issue ever resolved for you? Seems to be occurring for my installation now.
https://github.com/rancher/rancher/issues/31940

@jonathon2nd Even after a month, it is still stuck. No matter what I do, it keeps timing out.


CREO2URDF – MVP-2 kick-off

Task description
As preliminary steps of MVP-2 we would like:

[x] Produce the simulation asm of neck+head of iCub and commit to the repo
[x] Get the datums by processing the copy geometries

Definition of done
The above list is completed

Created assembly SIM_ERGOCUB_1-0_HEAD inside repository \\cad-mechanics\projects\simulation_model\ergocub.
@Nicogene @mfussi66

Get the datums by processing the copy geometries

Today w/ @mfussi66 noticed that the features inside the copy geometry can be taken transparently (e.g. as axis or as csys), so we didn't need to do anything in this sense.
We started then modifying creo2urdf in order to handle the new assembly and right now we have to find a way to correctly express the transform prev_link_H_link.
See https://github.com/icub-tech-iit/creo2urdf/commit/4932222537d3368b40fe821728d53a5b3cf2c596
We noticed that the root_H_link is fine, but then composing them we get strange transforms (some w/ nan). Probably we are using the idyntree API in the wrong way. But we will see better in the next days.
cc @pattacini @traversaro

We noticed that the root_H_link is fine, but then composing them we get strange transforms (some w/ nan). Probably we are using the idyntree API in the wrong way. But we will see better in the next days.
cc @pattacini @traversaro

See https://github.com/icub-tech-iit/creo2urdf/commit/4932222537d3368b40fe821728d53a5b3cf2c596#r114447105 .

Right now the priority is to get the prints from idyntree, redirecting the cerr/cout to string/file.

See https://github.com/robotology/idyntree/issues/1064 . As a first test we can try https://stackoverflow.com/questions/10150468/how-to-redirect-cin-and-cout-to-files , even if it is probably not clean as it interferes with the global process state.

said that in the export of the urdf a check is performed on the axis of the joint if it is close enough to the reference frame of the child link (or parent?), probably it is the error we are getting.

See https://github.com/robotology/idyntree/blob/v9.0.0/src/model_io/codecs/src/URDFModelExport.cpp#L365 . See also other [ERROR] messages to get an idea of the error we could be getting.

And indeed we have the error on the exporter, related to the first joint:
[ERROR] URDFModelExport: Impossible to convert joint SIM_ECUB_HEAD_NECK_1--SIM_ECUB_HEAD_NECK_2 to a URDF joint
without moving the link frame of link SIM_ECUB_HEAD_NECK_2 , because its origin is 0.00486151 4.13255e-16 -0.28977

By defining the joint origin as the position of the child coordinate system we were able to fix the error. Initially, we put (0 0 0) assuming that the origin would be taken from the required transform, see here . I'm not 100% sure that it is the intended usage, but the urdf is now valid.
However, we still need to correct the wrong pose of some of the links and joints:

We noticed that we are missing the SCSYS for the first link (NECK_1), this is required for us to correctly define the transforms from links. We are assuming that the first one is an identity but it is not what we actually have. @Mick3Lozzo could you add it to the asm?

Added SCSYS_NECK_1.
@mfussi66 @Nicogene

Joint axes fixed, the (simple) issue was that they are expressed in the root frame:

So in the urdf in the previous post there was a problem in the link transforms. Basically, whenever we retrieved them, they had an unexpected rotation around the Z axis of 180deg, compared to the measurement by hand inside Creo.
So after a lot of checks and verifications, I think we have a potentially working URDF of the head, with all the links and joints in correct order and placement:

BUT
What fixed the problem?
Since we need the transforms as iDynTree structures, we made a deep copy to convert from pfcTransform3D to iDyntree::Transform, assigning each element of the first to the constructor of the second (see https://github.com/icub-tech-iit/creo2urdf/blob/master/src/creo2urdf/src/Creo2Urdf.cpp#L127-L130)
I was afraid that Creo might be crazy enough to index matrix elements as (col, row) instead of (row, col) (basically transposing the matrix).
After applying the switch, we have the correct model 👀
I'm fairly sure that there are no other errors in the code that compensate for this transposition, but it might be useful to make a test in an environment with only two coordinate systems, and see what the transform is when printed from the toolkit in (row, col).

Probably it is not a col/row problem, just a matter of parent_R_child used instead of child_R_parent (or viceversa)

I suspected that too, but what worried me was the fact that a simpl retrieval of a transform would return only the rows and columns of the rotation matrix switched, compared to the program:


Python formatting

Uses black  to strictly format the python code.

Formatting has been done in another branch and the use of the github action is probably not necessary. Closing.


AArch64 Simplied-Provisioner partition type listed as Empty

When using the IoT simplified-provisioning tool on AArch64, the installation is successful but fails to boot and drops to a grub prompt.
Inspecting the included image on the iso ( https://kojipkgs.fedoraproject.org/compose/iot/Fedora-IoT-40-20240604.0/compose/IoT/aarch64/iso/Fedora-IoT-provisioner-40-20240604.0.aarch64.iso )
fdisk -l image.raw
Disk image.raw: 10 GiB,<PHONE_NUMBER>0 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xc1748067

Device     Boot   Start      End  Sectors  Size Id Type
image.raw1 *       2048  1028095  1026048  501M  6 FAT16
image.raw2      1028096  3125247  2097152    1G  0 Empty
image.raw3      3125248 20971519 17846272  8.5G  0 Empty

The partitions are missing the partition type, using fdisk to change it to Linux:
Device     Boot   Start      End  Sectors  Size Id Type
image.raw1 *       2048  1028095  1026048  501M  6 FAT16
image.raw2      1028096  3125247  2097152    1G 83 Linux
image.raw3      3125248 20971519 17846272  8.5G 83 Linux

Boots as expected in a VM.

Thanks @auphof .
Currently AArch64 gets set to dos to support the Raspberry Pi- which isn't a target for simplified-provisioning (yet), so I think it makes sense to change it to gpt as well.

Fixed.


Recommended strategy to split producer code and worker code ?

Hello
It is written on this page that the producer and the workers must share "tasks" code.
This seems counter-intuitive to me for two reasons:

Main Gofer examples show a producer with tasks code, and workers without (tasks are processed at client side!). By reading examples, we can think that tasks are executed by the producer (lambda evaluation).
Worker and producer generally have different library requirements. Ex: if we work on image processing tasks, the worker needs an image processing library but the producer doesn't.

What is the recommended strategy to split producer code and worker code so that the producer remains agnostic about how the worker processes tasks?

Utilizing different sets of libraries in the producers and workers is unlikely to work with Gofer.NET without some clever hacking.
Since the target function location is serialized, and not something more abstract like a string, the producer and worker both need to have access to the target function.
One idea would be to have a sort of virtual assembly in the producer where tasks are defined, but do nothing. In the worker, this assembly would need to be replaced with one of the same Full Name with the task bodies replaced with the real code.
In the general case, this use-case is currently unsupported by Gofer.NET.
If you get it working though, please leave a comment on how you accomplished it and perhaps the docs could get updated.

Thanks for your answer. I guess I can make it work with a global variable (singleton or something like that). However, this is the most basic use case I can think of. For the project I'm working on, I need way more flexibility. I won't be able to test further this library, as it doesn't fulfill my needs

I can understand that there are some use-cases where this type of separation makes sense.
AFAIK this is not generally supported by distributed task libraries that work directly within the language (i.e. python celery) like this one.
A more abstract task system that works on the process/command level may be more inline with what you need.
Currently, we have no plans to support this scenario officially so I'm going to close this issue out.
If you get it working though, I'd still be interested to hear how you did it.

Main Gofer examples show a producer with tasks code, and workers without (tasks are processed at client side!). By reading examples, we can think that tasks are executed by the producer (lambda evaluation).

Can you point out where you are seeing this?
In the guided example, the worker has a project reference to the producer so the producer's assembly is included as a dependency.
https://brthor.github.io/Gofer.NET/example#add-langversion-property
<ItemGroup>
  <ProjectReference Include="..\primary\primary.csproj" />
</ItemGroup>


Add optional evaporation field

This issue represents a feature request to add support for a new optional field in every message for the upcoming SNIP-25.
This feature is similar to the padding field in that it allows clients to tune their message in order to reduce data leaked through the publicly viewable metadata of executions. While padding is used to fill message length, users are still exposed to data leaking through the gas_used field of transaction results.
We've implemented a proof-of-concept using storage writes, but are experimenting with other operations as well.
It's important to note that even if the cost of the underlying operation were to change, this approach remains flexible enough to compensate since the client determines the multiplier.
Rationale
The public gas_used result of a contract execution leaks data about the code path taken.
In its simplest form, attackers can use this information to distinguish between the following execution methods with high confidence: create_viewing_key, set_viewing_key, increase_allowance/decrease_allowance, send/transfer, revoke_permit, and so on.
In some situations, an attacker might even be able to narrow or deduce the values of certain private variables.
While more precise solutions would involve modifications to the compute module, we propose an approach that can be deployed with contracts as-is and in a manner that is guaranteed to take place within the enclave.
Evaporation
We introduce the concept of "evaporation", by which extra gas is deliberately and deterministically consumed during execution in order to pad the gas_used.
Users may include an optional evaporate field in every message. The value of the field should be an integer that specifies an arbitrary multiplier for some fixed-cost operation.
Using evaporation, wallets can compute a precise multiplier to provide as input during execution in order to produce a gas_used value that effectively obscures the nature of the transaction.
Requests

Name
Type
Description
optional

evaporate
number
Number of times to perform the predefined fixed-cost operation in order to consume extra gas.
yes

Example
{
  "transfer": {
    "recipient": "<address>",
    "amount": "100",
    "padding": "-------",
    "evaporate": 620,
  },
}

After much testing we have gone the route of implementing a new gas_evaporate API function. The relevant PRs can be found at:
SecretNetwork: https://github.com/scrtlabs/SecretNetwork/pull/1388
cosmwasm: https://github.com/scrtlabs/cosmwasm/pull/13


♾ API Integration - User Register

I want to connect the user's register to the backend

Guidelines ⚠
I have read the Contributing Guidelines 🔐
I have read the Setup guidelines 🔐

FIXES 🛠
This is the user register page ⤵

I want it so the users can register
⭐ If they register sucessfully alert them with Registration sucessful , please login and redirect them to LOGIN PAGE
⭐If they give invalid credentials alert them with Please input valid credentials and then CLEAR the forn
⭐If user already EXISTS , alert them with User already present , please login and redirect them to LOGIN PAGE
⭐You need to use axios to connect the backend and frontend.
⭐You can checkout the backend routes inside server folder !!
Integrating 🧠
Go the service folder -> Api.js , there you'll need to make functions for calling the API
Here's an EXAMPLE OF API FUNCTION ⤵

As you can see we literally passed the whole useState named credentials to the backend , and we got results from it
With the help of these results you'll need to do alerts as i mentioned earlier

Completed / Doubts ?  🚀
Once you are done with the code , please tag me in #milan with the Screenshot of whatever you made so that we can review that there together.
If you have any doubts, queries please tag me in #milan so that we can discuss the issue there together.
Please Donot DM.
Cheers 🥂

I want to work for this under JWOC.

I want to work for this under JWOC.

Assigning to you , once done tag me in #milan and we can review it together !!


[FLINK-12889] Set FatalExitExceptionHandler for StreamTask#asyncOperationsThreadPool

What is the purpose of the change
In order to avoid the swallowing of uncaught exceptions in asynchronous checkpoint operations,
this commit sets the FatalExitExceptionHandler for the StreamTask#asyncOperationsThreadPool.
For testing purposes the uncaught exception handler was made configurable in the StreamTask.
Verifying this change
Added StreamTaskTest#testUncaughtExceptionInAsynchronousCheckpointingOperation
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (yes)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)
If yes, how is the feature documented? (not applicable)

Thanks for the review @zhijiangW and @pnowojski. I'll address your comments while merging.
@pnowojski, yes I would suggest to follow this pattern everywhere. Task#asyncCallDispatcher seems to set the FatalExitExceptionHandler correctly.


Deprecation warnings for using old arguments in request methods.

Adds a decorator, kwargs_renamed_for_v11, that allows the use of keyword arguments from the 0.8 branch for easier adoption of 1.0. If a kwarg is used with the 0.8.x naming, a DeprecationWarning is raised (specifically a RemovedInPAM11Warning), then the kwarg is mapped to the new name automatically so the operation can continue unimpeded.
Example:
# mws/apis/feeds.py

class Feeds(MWS):
    ...

    @kwargs_renamed_for_v11([("marketplaceids", "marketplace_ids")])
    def submit_feed(
        self,
        feed,
        feed_type,
        feed_options=None,
        marketplace_ids=None,
        amazon_order_id=None,
        document_type=None,
        content_type="text/xml",
        purge=False,
    ):

Here, the 0.8 version of submit_feed uses the argument marketplaceids, which has been renamed in 1.0dev versions to marketplace_ids. It may be unclear to some users that this change was made without combing through documentation or source code, and the operation would fail if the user called the method using submit_feed(..., marketplaceids="foo").
With the decorator in place, the operation will continue as before, simply raising a warning that details the name change. The value "foo" is then passed into the decorated method as marketplace_ids, the kwarg expected by the new function signature.
Testing
Test forthcoming, will update this PR once added.

Is there a lifecycle for this chance? I'd hope that this deprecation warning wouldn't stay in place in perpetuity.

@samamorgan These are meant to create a bridge between 0.8 and 1.0dev versions to aid in upgrading off 0.8. Users that are already on 1.0dev and using param names as defined in the method signatures should not see deprecation warnings at all: while users coming in from master version using incorrect names will see warnings raised only if they use the "old" argument names.
This corrects an issue where users may attempt to use the "old" names in 1.0dev, which previously would just throw an error and prevent the request from going through. With this update, that same code would successfully send a request, while also warning the user to update their code for the future. Particularly for folks who are still using 0.8 from a PyPI install, this should smooth over the transition once we have a 1.0 release up on PyPI and those upgrades start rolling in.
As for lifecycle, the warning raised is RemovedInPAM11Warning, as I expect to remove these deprecated calls in v1.1. No specific timeline on that yet, though.

Note on latest commit today: changes I made to that test prior would make a conflict. The changes I've made now match up with incoming changes from another feature set. Should help avoid a conflict down the line, and still passes either way.
Kinda weird to do it that way, but I can see it being an issue without it.


Missing virtual destructor in dsp class

~DSP();
should be:
virtual ~DSP();

Gotcha; this one?
https://github.com/sdatkinson/NeuralAmpModelerCore/blob/accaa16ef35bea2e3d257e5f15584f4f644f1438/dsp/dsp.h#L22

yessir. Also, it would be good to add namespacing for all classes and methods in nam core. If one would use this in a larger codebase, this could become a problem


Issue #229: setup the song model serializers for the songs endpoint of the music room

Issue #229
worked on the song model serializer to create the set of fields based on the Song Model.
dependent on the views and URLs respectively, the live link below would return the JSON format:
https://music.zuri.chat/songs/

worked on the song model serializer to create the set of fields based on the Song Model.
dependent on the views and URLs respectively, the live link below would return the JSON format:
https://music.zuri.chat/songs/


Quick publish and Manage Publication are wrongly redirected

Quick publish and Manage Publication are wrongly redirected, after publish the configs, the user is redirected to Publish page again. Quick publish and Manage Publication can not be canceled. After clicking on Cancel it is redirecting back to the publish screen. The preview server is enabled in our environment.
Additional information: It is working with AEMaaCS product version 2023.7, but not with the newer versions.
Quick publish - Steps to Reproduce :

Click on Context-aware config.

Add / Update configuration and click on save.

Click on Quick publish.

Manage Publication - Steps to Reproduce :

Click on Context-aware config.

Add / Update configuration and click on save.

Click on Manage Publication

Click on Next

Click on Publish

Actual :: It has to be redirected to the configuration editor or Sites, but instead it is redirected to Publish again.
Expected result:: After successful Quick Publish or after canceling the Quick publish process the user should be redirected to Configuration editor

which version of caconfig editor are you using? please note that we fixed some issues with publication wizard handling in version 1.15.8 (#23).
i tested the publication wizard with 1.15.9-SNAPSHOT and AEMaaCS 2024.4.15787.20240404T134829Z and it looked fine, e.g. canceling manage publication works without problem. which AEMaaCS version did you use?

It is working with version 1.15.8. Thank you!


Cardano: generalise golden example injection using Nary

Fixes #2368.
The new Inject class provides a convenient and uniform way to inject things
into the hard fork combinator, i.e., turn an f blk into an f (HardForkBlock xs).
Use the Inject class to write the inject the golden test examples from an era
into HardForkBlock.
Some golden test results involving HardForkState change because we use the
proper Bounds.

bors merge


Updating success logic

Updating the definition of SUCCESS response code to be 200 OK or 201
Created. Error is anything that is not success. This helps flag
conditions like an unsuccessful update (return code 304) which the
library would have flagged as success earlier

Coverage increased (+0.03%) to 93.27% when pulling 1cea86609bd580150798cf067a504f8328a547aa on sudiptachatterjee:master into 0003e564b19e35386320f13e5efb1dc85cb5b6b8 on google:master.

Coverage increased (+0.03%) to 93.27% when pulling 1cea86609bd580150798cf067a504f8328a547aa on sudiptachatterjee:master into 0003e564b19e35386320f13e5efb1dc85cb5b6b8 on google:master.

Coverage increased (+0.03%) to 93.27% when pulling 1cea86609bd580150798cf067a504f8328a547aa on sudiptachatterjee:master into 0003e564b19e35386320f13e5efb1dc85cb5b6b8 on google:master.

Coverage increased (+0.03%) to 93.27% when pulling 1cea86609bd580150798cf067a504f8328a547aa on sudiptachatterjee:master into 0003e564b19e35386320f13e5efb1dc85cb5b6b8 on google:master.

Coverage increased (+0.03%) to 93.27% when pulling 1cea86609bd580150798cf067a504f8328a547aa on sudiptachatterjee:master into 0003e564b19e35386320f13e5efb1dc85cb5b6b8 on google:master.


update code for upstream notifications plugin

FLPATH-1249
https://issues.redhat.com/browse/FLPATH-1249

Is it intentional to not update MTA because of https://github.com/parodos-dev/serverless-workflows/pull/224?

Is it intentional to not update MTA because of #224?
yes.
see this comment by moti https://github.com/parodos-dev/serverless-workflow-examples/pull/45#discussion_r1594606974

closing this PR since I'd like to push it to staging branch instead.


Minor typo

The numbers have European separators. English US should use commas, not periods.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 98387b95-ce70-594b-b0e1-36ef1b5a6fb6
Version Independent ID: 8a8d3822-49c4-1422-e046-0d7c9726c9b6
Content: Object Ranges - Business Central
Content Source: dev-itpro/developer/devenv-object-ranges.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

Thanks for your feedback, this issue is fixed with the next refresh of the docs.


Connection timeout & no data-file

Hi,
running inventory seems successful on UI, but it creates no data-file:
ConnectTimeoutError: Connect timeout on endpoint URL: "https://ec2.eu-central-1.amazonaws.com/"
ERROR:aws_inventory.invoker:Unknown error while invoking API for service "ec2" in region "eu-central-1".
Traceback (most recent call last):
  File "D:\applications\aws-inventory-master\aws_inventory\invoker.py", line 163, in svc_worker
    response = getattr(params['client'], py_op)()
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\client.py", line 357, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\client.py", line 648, in _make_api_call
    operation_model, request_dict, request_context)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\client.py", line 667, in _make_request
    return self._endpoint.make_request(operation_model, request_dict)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\endpoint.py", line 102, in make_request
    return self._send_request(request_dict, operation_model)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\endpoint.py", line 137, in _send_request
    success_response, exception):
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\endpoint.py", line 231, in _needs_retry
    caught_exception=caught_exception, request_dict=request_dict)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\hooks.py", line 356, in emit
    return self._emitter.emit(aliased_event_name, **kwargs)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\hooks.py", line 228, in emit
    return self._emit(event_name, kwargs)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\hooks.py", line 211, in _emit
    response = handler(**kwargs)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 183, in __call__
    if self._checker(attempts, response, caught_exception):
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 251, in __call__
    caught_exception)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 277, in _should_retry
    return self._checker(attempt_number, response, caught_exception)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 317, in __call__
    caught_exception)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 223, in __call__
    attempt_number, caught_exception)
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\site-packages\botocore\retryhandler.py", line 359, in _check_caught_exception
    raise caught_exception
ConnectTimeoutError: Connect timeout on endpoint URL: "https://ec2.eu-central-1.amazonaws.com/"
DEBUG:aws_inventory.store:Building the GUI data model.
Exception in thread Thread-1:
Traceback (most recent call last):
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\threading.py", line 801, in __bootstrap_inner
    self.run()
  File "C:\Users\michael.fritsch\.windows-build-tools\python27\lib\threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "D:\applications\aws-inventory-master\aws_inventory\invoker.py", line 99, in _probe_services
    self.write_results()
  File "D:\applications\aws-inventory-master\aws_inventory\invoker.py", line 130, in write_results
    self.store.generate_data_file(out_fp)
  File "D:\applications\aws-inventory-master\aws_inventory\store.py", line 148, in generate_data_file
    for service in data[0]['children']:
KeyError: 'children'

Is there any solution?
regards,
Michael

Given your report, it's hard to say what the issue is. My guess is you had a very narrow filter set on the commandline that reduced the amount of resources to inspect. All requests made by the tool to inspect those resources failed leaving no actual response data to show in the GUI tool. It doesn't look like the tool handles that error case.

Hi there. Did the feedback from @bitsandsalsa  help resolve this issue?


refact getPublishTopicList method and subscriptions  method redundant code

There are two redundancy statement code

getPublishTopicList()：can replace with hashmap constructor
subscriptions(): can replace with hashmap constructor

Just go ahead~


Please invite me to the community

Name
osaguild
Discord Username (if applicable)
osaguild
Additional Context
I learned about devprotocol on Joi ito's podcast. Then I contact with aggre and vincent on twitter and was introduced to their community.
I want to learn and contribute web3 project and project in Japan is better than others because I'm Japanese. I hope dev protocol will be a great service and bring Japanese culture to the world!

Thank you for joining us and welcome here 🎉 I invited you to collaborator, where u can access some private channels on Discord. If you have questions there, don't hesitate to ask the team.


expose a high-level object for I/O

Now that we can read the files, the next task is to create a I/O object that pulls all the different steps together and exposes the read data (like h5py.File, netcdf4.Dataset, or the zarr store). This involves:

[ ] reading all the metadata (volume directory, sar leader, sar image metadata, sar trailer, summary) on open and organizing the metadata and data into groups, variables, coordinates, and attributes (#17)
[x] optionally create cache files for the image files (#20)
[x] lazy access to the data, including chunked reads (#14)

In particular, lazy data access is necessary to be efficient when reading level 1.1 ScanSAR imagery, and allows the use of dask.

Closing since #17 is much more effective in tracking the progress of the metadata organization, and the other tasks have been achieved already.


versionCatalogs fails when a TOML filename starts with 'libs' and multiple TOML files are used

Summary
When including multiple TOML files in VersionCatalog's (see Groovy code steps to reproduce below) and one of the files is named libs.*.toml, then Gradle fails with:
org.gradle.api.InvalidUserDataException: Invalid catalog definition:
  - Problem: In version catalog libs, you can only import a single external catalog in a given catalog definition.
    Reason: Multiple catalog imports are not yet supported.
    Possible solution: Create a separate catalog for each import you want to use.

Workaround is to rename the TOML file.
Expected Behavior
Should not fail or the documentation should state that libs.*.toml usage is not allowed.  Error message could be better too, as it does not point to the source of the problem.
Current Behavior
Fails with an InvalidUserDataException
Context
Would not compile.  Workaround was just to rename the file.
Steps to Reproduce
setttings.gradle file contents:
pluginManagement {
    dependencyResolutionManagement {
        repositories { mavenCentral() }
        versionCatalogs {
            create("tooling") { from(files("gradle/tooling.versions.toml")) }
            create("libs") { from(files("gradle/libs.versions.toml")) }        # this file needed to be renamed to libraries.versions.toml

Your Environment
Android Studio with small Android project.  1 module.  Gradle 7.4.1

            create("libs") { from(files("gradle/libs.versions.toml")) }        # this file needed to be renamed to libraries.versions.toml is redundant: the libs.versions.toml file is a conventional one, so you are basically recreating the same catalog, hence the error message.

I also stumbled at this error with default libs.version.toml at some point. It was really a confusing error to me, since I had create("libs") { from(files("gradle/libs.versions.toml")) } and libs.versions.toml is mentioned a lot in docs, but Gradle didn't like it. And since I am bad at reading a documentation I needed quite some time to figure this out.
I believe we should either:

Ignore an error if user tries to create a catalog that is the same as default catalog
Or print an error message that makes it obvious that it collides with default catalog

Note that the Groovy DSL doesn't care if it's create or get... which is what I think most users care about.

All in all, the conclusions which I can make from this, and the source code are:

The file libs.version.toml is a convention (as documented, and coded in here)
Creation of a version catalog is not an idempotent operation, hence the error message

The error message indeed is misleading, as it doesn't clearly detail what actually happens.

I agree with @asodja about the range of possible actions.
Personally, I think it's completely acceptable if we don't support this special use case, as it is just yet-another-codepath:tm: to go wrong. Instead, I would opt for number 2, and correct the error message (or create a more specific one).

The issue is on hold until #20383's fate is cleared up, as that issue changes this one's implementation.

I notice this https://github.com/gradle/gradle/issues/20383 has been resolved, what about process of current problem? It still exists when I use libs.version.toml with libs namespace.

Unable to load libs.version.toml when i use this name gradle-version-catalog
In Jfrog it is published as gradle-version-catalog.toml
create("libs"){
from("com.xxx.xxx.mobile:gradle-version-catalog:0.1.1-SNAPSHOT:toml")
}

Is this issue irrelevant now we have the following error?:
Invalid catalog definition:
  - Problem: In version catalog libs, you can only call the 'from' method a single time.


Feature: Account update

Commands:
--account (-a) Update contact information
https://ietf-wg-acme.github.io/acme/#registration
For example, to update the contact information in the above registration, the client could send the following request:
POST /acme/reg/asdf HTTP/1.1
Host: example.com

/* BEGIN JWS-signed request body */
{
  "resource": "reg",
  "contact": [
<EMAIL_ADDRESS>    "tel:+12125551212"
  ],
}
/* END JWS-signed request body */

This feature is now implemented, thanks to @lukavia!


Implement matching inside of the mamut matched tracks reader

@abred Just wanted you too have a look. The signature is pretty different. In experiments, I also added this to the export_to_mamut.py script (which I will commit momentarily) so you should be able to use that right away

https://github.com/funkelab/linajea_experiments/commit/3124ca9d894c443e3e79d512e33cb67967c19317

https://github.com/funkelab/linajea_experiments/blob/6a7a12c17e7eca7c1dc2a71c72709ffdc55ff4aa/visualize/mamut/visualize_matched_tracks.py#L57-L58
there writer.add_data(reader, data) is called, with data being a pair
in writer.add_data reader.read_data(data) is called.
That's the signature I tried follow in my code


Documenting how to integrate the Kubernetes Dashboard with Capsule Proxy

Since it works, why not share it with the community?

@prometherion Maybe it could make sense offering a kubernetes dashboard chart with capsule-proxy, which directly integrates with the proxy :). Or do you think that's a bad idea?

Would you go with a fork of the Kubernetes dashboard chart? May I ask you to elaborate a bit more?

@prometherion this seems fixed by #724


The bot won't send messages

When I start the bot it says on the status to do /help but that doesn't work and neither does @(bot) help. It's the same for all the commands.

Thank you for opening this issue, however, I can not help you with this problem without requiring more information about your bot setup.
If you could please provide a list of information with details about your OS, whether you are using Docker, and runtime logs of the bot.

Closed due to inactivity


Add EVPN ESI Support for Active/Active server connections

Description
Add initial support for EVPN ESI support for port configuration. This PR covers following actions:

Capture inputs from SERVERS.YML
Generate a structured_configuration for LEAF devices.
Generate CLI configuration

Data model update:
EOS L3LS EVPN
Input for eos_l3ls_evpn
servers:
  server01_ESI:
    rack: RackA
    adapters:
      - type: nic
        server_ports: [Eth0, Eth1]
        switch_ports: [Ethernet7, Ethernet7]
        switches: [DC1-LEAF1A, DC1-LEAF1B]
        port_channel:
          state: present
          description: data
          mode: active
          esi: 0000:0000:0001:0411:1111
          lacp_id: '0000.0001.0411'
        profile: ALL

EOS CLI Config GEN
Input for eos_cli_config_gen
### Port-Channel Interfaces ###
port_channel_interfaces:
  Port-Channel7:
    description: server01_ESI_data
    vlans: 1-4093
    mode: trunk
    esi: 00:00:00:00:01:04
    lacp_id: 0000.0001.0411

Generated EOS configuration
interface Port-Channel100
   switchport trunk allowed vlan 10, 20
   switchport mode trunk
   !
    evpn ethernet-segment
      identifier 0000:0000:0001:0411:1111
      route-target import 00:00:00:00:01:04
    lacp system-id 0000.0001.0411

Question in progress

[x] Define a mechanism to generate RT for ESI.
[x] Add support to generate automatically LACP system-id

- Input ESI: `0303:0202:0101`
- Final ESI format: `000:000:0303:0202:0101`
- LACP-ID: `0303.0202.0101`
- RT: `03:03:02:02:01:01`

Todo List

[x] Update eos_l3ls_evpn.
[ ] Update eos_cli_config_gen.
[ ] Update Roles documentation.
[ ] Update CI to add ESI in testing.

Add logics to generate RT and LACP-ID
While ESI needs 3 different IDs to run, this commit implement logic to
generate LACP ID and RT based on ESI
Example:

Input ESI: 0303:0202:0101
Final ESI format: 000:000:0303:0202:0101
LACP-ID: 0303.0202.0101
RT: 03:03:02:02:01:01

Known caveat: ESI configured on MLAG devices seems to not work with vEOS-LAB 4.24.0F
Ready for internal review and testing.

PR Review Todo list:

[ ] Rename input ESI to short_esi (update documentation as well)
[ ] Apply a custom filter to transform short_esi to lacp_id

Problem spotted:

short_esi: 0303:0202:0101
rt: 03:03::0:20:2::01:01


addons version variablize

Variablized the below addons and freezed their version:
vpc-cni "v1.19.0-eksbuild.1"
ebs-csi-driver "v1.36.0-eksbuild.1"
metrics-server "3.12.1"
cluster-autoscaler "9.37.0"
node-termination-handler "0.21.0"
keda "2.14.2"
Karpenter "1.0.6"
external-secret "0.9.19"
cert-manager v1.15.1"
reloader "v1.0.115"
Ingress-nginx "4.11.0"
load-balancer-controller "1.8.1"
kubenetes-dashboard "6.0.8"
argocd "7.3.11"
argoworkflow "0.29.2"
kubeclarity "2.23.0"
kubecost "v2.1.0-eksbuild.1"
falco "4.0.0"

tested by @monachawla17


Gamepad

There's anyway to navigate using a gamepad like a XBox 360 controller?

not that i can find thats one of the few downsides to this app, I pretty much need this feature added


Check usage of aurelia-pal

When installing the bridge in a new skeleton project, the bridge loads aurelia-pal as a dependency which is not installed as a top-level dependency in the current skeleton.
See:
https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/issues/204#issuecomment-244968036
Do we need aurelia-pal at all (apart from testing but then it's in the wrong dep category)?

my bad
https://github.com/aurelia-ui-toolkits/aurelia-materialize-bridge/blob/master/src/input/input.js#L2
It is used to throw blur event.

Actually I guess it's better to use DOM like you did.
But I thought I had understood JSPM and that's obviously not the case. :smile:
Why is pal expected as a top level dependency?

I didn't discover fireEvent before playing with the select. Maybe we could use that function on the input instead?

Sure we could do that. But that doesn't solve the queston for me. :smile:
Actually a lot of packages in the skeleton depend on aurelia-pal (including the framework itself) and it doesn't complain when the bridge isn't called.
Let's do this anyway to get this out of the way. But I'll have a look into it.

For a quick fix try jspm install aurelia-pal but I suppose this should be pulled by Aurelia skeleton already.
Anyway, I wonder why this happens.

I just took a completely new download of the esnext skeleton (from their "releases" tab) and installed materialize and the bridge. I can reproduce this issue.
We may have an unnecessary dependency on aurelia-pal which is missing in the skeleton. I'd like to check this out.
Did my "quick fix" work, btw? :smile:

@Thanood, thanks! I just try jspm install aurelia-pal and work.

great :+1:


Firechat.js without Firechat-ui.js

The the two components; firechat.js and firechat-ui.js separate because its is expected that some users will utilize methods and the API and render the data manually? Or is there a different reason for the separation?
I ask because my use case requires a more wide spread integration of chat into the app.
Thanks, Again.

Yes it's decoupled so that you can write your own ui.


[5.1][ConstraintSystem] Shrink: If root expression is assignment always co…

…nsider it as a candidate
If assignment expression is not considered as a top-level candidate
it would mean that other candidates would be allowed to produce
types inconsistent with destination type of the assignment.
Resolves: rdar://problem/51413254
(cherry picked from commit 93ab669c35344789a8b69ebae3cc71396f4087bb)

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 45b1e5913ef4a499f1aa0a17c6ec49737b777f16

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 45b1e5913ef4a499f1aa0a17c6ec49737b777f16

Build failed
Swift Test Linux Platform
Git Sha - 45b1e5913ef4a499f1aa0a17c6ec49737b777f16


No curation ephys AND kilosort triggering

Fix #34
Fix #40
Fix #37
Fix #39

@kabilar should we close this PR? We can issue PR from the run_kilosort branch?

Thanks @ttngu207.  That sounds good.  Feel free to close and create a new pull request.  Let's ask @sidhulyalkar to review and merge.

Closing this PR - to be replaced by a new PR from the run_kilosort branch


Fixing error adding tv shows to watchlist

TV shows currently have a error adding to watchlist, due to the fact that they don't have a video property and specific properties inside the video object are extracted during this addition.
I changed this so that it it simply assigns response["tvShow"] to the tvShow object and the response["video"] to the video objects. This way one of them can be null (as will always happen) and it will be added without errors to the list.
The second problem is that TV shows aren't even shown in the watchlist, because, again, their Entry don't have a video property and during list it was filtered by video!=null, which fails.
I changed it so that it checks for video!=null || tvShow!=null. This way it prevents completely null entries and it works for both shows and movies.

Is important to pull this fix.
Thank you so much @darkarp

Is important to pull this fix. Thank you so much @darkarp

You're welcome :)


[stable/kube-state-metrics] Solve #13961

Signed-off-by: Login Victor<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #13961

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/chart])

@tariq1890 Fix description on README.md and formatted table
/assign @tariq1890

/lgtm
/approve

/approve cancel

@batazor Can you squash your commit history?

/lgtm cancel

@tariq1890 done

/lgtm
/approve


sysbench: connection error received: detected excessive load generating behavior

Describe the bug
https://buildkite.com/risingwave-test/sysbench/builds/596#018c17bd-2613-465e-9e64-6359cf9e3e3a
https://grafana.test.risingwave-cloud.xyz/d/liz0yRCZz1/log-search-dashboard?orgId=1&from=now-12h&to=now&var-data_source=PE59595AED52CF917&var-namespace=sysbench-daily-test-20231128&var-pod=benchmark-risingwave-frontend-f-6d47fdb6d5-grd9r&var-search=

Same error yesterday: https://buildkite.com/risingwave-test/sysbench/builds/595
But if we look at the successful tests a few days ago: https://buildkite.com/risingwave-test/sysbench/builds/576#018bff4b-2891-4a64-ab7e-12f4b56815ba
the QPS is low.
Error message/log
No response
To Reproduce
No response
Expected behavior
No response
How did you deploy RisingWave?
No response
The version of RisingWave
No response
Additional context
cc: @chenzl25  @liurenjie1024, could you help take a look? Thanks

I will ses see.

After some investigation, this is caused by early stop of grpc stream, and we didn't handle grpc stream cancel correctly. I'll submit a pr to fix it.


lower case project name for docker compose

invalid project name "MagicStuff": must consist only of lowercase alphanumeric characters, hyphens, and underscores as well as start with a letter or number

This project name is only for the docker, the user usually don't have to see it.


test_ackman scenario uses wrong models

test_ackman scenario imports Ambulance as a model, instead of being spawned through traffic map annotation. Consequently, it seems the wrong model ( without slotcar plugin ) is used.
Vaguely related to https://github.com/open-rmf/rmf_traffic_editor/issues/386 involving some issues with the model download pipeline from fuel.

we switched to AmbulanceSlotcar and spawned it as a robot in https://github.com/open-rmf/rmf_demos/pull/86, it should be fixed now


[bug] Rotating the app causes it to crash.

Running iOS 12 PB 5 on my 2017 iPad, with the iOS theme and list view on Slide.
Rotating the screen causes the app to crash, no matter where I am in the app. Please see a gif of it below.
https://gfycat.com/RequiredSafeFinnishspitz

I’m experiencing this occasionally, and I’m pretty sure it’s a problem with iOS 12. We’ll look into it though.

Fixed!

I was forcing the tabbar to align to the top of a view it was not inside of if you had sub tabs disabled


Incorrectly parsing Prometheus 'Duration' in Prometheus Rule Group

2.5.12 back port rancher/dashboard#4851

on 2.5-head (1bb0d06):

install monitoring v2 on a cluster
create a new prometheus rule

edit as yaml and update interval to one of the options for duration (i.e. ms, m, d, y)

observe the rule once created in the UI

result:
durations are working as expected -- i.e. 1 minute is converted to 60 seconds
(tested with ms, m, h, d, y)


CodeGPT plugin support for Pycharm 2024.2.2

The CodeGPT plugin for JetBrains does not support Pycharm CE 242.2 versions and says Not compatible with the version of your running IDE (PyCharm 2024.2.2). Please add support for the latest version of Pycharm CE.

@Pradeep-Singhh  Currently, the plugin is not updated to work with the most recent versions of PyCharm. The current one is compatible with this exact version: 241.15989—241.*, no up

Thanks for the reply, hope the plugin is updated soon to support the latest version of Pycharm.


startActivityForResult depricated

Since startActivityForResult depricated how to target GoogleSignIn for new android versions

May get around to this later, but wanted to post the relevant links that show up for fixing this and the areas I found the problem in.
https://github.com/firebase/snippets-android/blob/7268f816496dac6990b9587874520daeeba46333/auth/app/src/main/java/com/google/firebase/quickstart/auth/GoogleSignInActivity.java#L128
https://github.com/firebase/snippets-android/blob/7268f816496dac6990b9587874520daeeba46333/auth/app/src/main/java/com/google/firebase/quickstart/auth/kotlin/GoogleSignInActivity.kt#L100
Links:
https://developer.android.com/training/basics/intents/result
https://stackoverflow.com/questions/62671106/onactivityresult-method-is-deprecated-what-is-the-alternative

@MatthewFallon Let me know if you still wish to contribute :)

Hey @thatfiredev is it to late to contribute ?


mountPoints should default to readOnly=true

A poor selection of default if following the 'deny all, permit explicitly' mantra which is well-respected in the security world.

While I appreciate the security world very much, the vast majority of
volumes will be mounted read-write, so making that the default makes sense
to me.  Also, since volumes model mount(), the defaults should be similar -
mount() is read-write unless otherwise instructed.
On Wed, May 6, 2015 at 9:48 AM, Walter Stanish<EMAIL_ADDRESS>wrote:

A poor selection of default if following the 'deny all, permit explicitly'
mantra which is well-respected in the security world.
—
Reply to this email directly or view it on GitHub
https://github.com/appc/spec/issues/391.

If you're arguing for optimizing a complex system based upon convenience instead of well known security processes, history shows that you're really asking for false economy and problems down the line. Sure, they might not be your problems, but someone will have them. It'd be best to change sooner rather than later.

Currently because ReadOnly is a *bool (in types.Volume) if you try to json.Unmarshal something that doesn't specify the ReadOnly you get some comical nonsense like this (note the PANIC inside of it):
{0.7.1 PodManifest [{rocketpack-io-flow-stora {<nil> sha512-06959624b668ead2cde5f2de128eee2ff9c0a4c9b84131604afa58838fa92d1e []} 0xc8200bc0e0 [] [{rkt.kubernetes.io/containerhash<PHONE_NUMBER>}]}] [%!v(PANIC=runtime error: invalid memory address or nil pointer dereference) default-token-spuha,kind=host,readOnly=falsesource=/var/lib/kubelet/pods/6cad6a24-a27d-11e5-ae42-42010af00003/volumes/kubernetes.io~secret/default-token-spuha] [] [{rkt.kubernetes.io/managed-by-kubelet true} {rkt.kubernetes.io/uid 6cad6a24-a27d-11e5-ae42-42010af00003} {rkt.kubernetes.io/name rocketpack-io-flow-stora-yru1p} {rkt.kubernetes.io/namespace default} {rkt.kubernetes.io/created<PHONE_NUMBER>} {rkt.kubernetes.io/restartcount 0}] []}

which leads to some confusing bugs.  There hasn't been any discussion on this in quite a while, but should we pick a default so we can depointerify it?  Alternatively I can just manually check this value when it's used (in the String() method), but I figured if I was going to muck around with this we could just give it a default.
btw I do not care what the default is, I just want my json to parse properly.

@runningwild I am pretty sure that was fixed via https://github.com/appc/spec/pull/541 - mind giving 0.7.2 a try?

Yes you're right, I hadn't updated in a while I guess, my mistake.


Retrieving the original index of the samples in subset

Hi Jacob,
Thank you for a very cool library. I have a quick question. Maybe I missed something, but right now there are no way to retrieve the original index of the samples in the subset to identify which samples/row number the algorithm chose? This need comes up in 2 scenarios:

When I want to know whether I have sufficiently covered my data distribution based on UMAP 2D embedding, I need to know the index of the samples in the subset to merge it back with the UMAP representation

When I have features [A, B, C], but only want to perform submodular optimization on features [A, B], and then want to know the values of feature C of all the samples in the subset.

Right now I don't see any way to extract out the index/numpy array row number of the chosen samples.

Howdy
The ranking attribute should return this for you.

Thanks! I felt like I missed something from the docs.


Not delete Keypad on user delete

@jwinzer Should a keypad be deleted, if a user is deleted? If so, I'll close this PR.

The keypad should be deleted if the user gets deleted who owns the keypad.

Ok.

Shouldn't it be
user = models.OneToOneField(User, null=True, blank=True, on_delete=models.CASCADE)
to delete the keypad when user is deleted?

I think this is the default. At least the keypad is deleted, if the user is, so currently it works as expected (except the autoupdate, this is another issue, but I have a solution for it).


Error installing library via nuget

version: 2.0.1
dotnet version: 5.0.207
code: NETSDK1
Error mensage: Severity	Code	Description	Project	File	Line	Suppression State
Error	NETSDK1136	The target platform must be set to Windows (usually by including '-windows' in the TargetFramework property) when using Windows Forms or WPF, or referencing projects or packages that do so.	Playground	C:\Program Files\dotnet\sdk\5.0.207\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.Sdk.DefaultItems.targets	362

I had the standard dotnet library installed, and I'm on the dotnet core.


Added ability to add new keys

IYE is a fantastic little tool, the only missing thing for me was the ability to add new keys from the interface, as I find it a bit cumbersome to edit yml files with my text editor.
This PR adds this functionality:

It's quite simple but seems to work well enough for my basic requirements. I've decided to add a dropdown to choose the file you want to save the translation to, as people might be partitioning translations in different files.
Here is a video that shows the feature in action:  https://www.dropbox.com/s/qwyse1ymulprr5p/iye_new_keys.mov?dl=0
I hope you like it and merge it into the master branch.
Paolo

:+1: very cool!

This is great - thank you so much.

Make sure tests pass (bundle && bundle exec rake)
Let us make a separate page for the new form, instead of toggling with JS (eg. /new)
In our main Rails app we have 260 different locale files. It would be cool if we could use some kind of smart dropdown with search-as-you-type!
What do you think about allowing people to add new locales in the same form? Just have a button that, when clicked, adds a new input field/text area under the existing locales.

Hi Harry, a few updates:

I've moved the new key form to a /new page
I've added a message if a search returns no results with a link to create a new key
In the file dropdown, I'm de-duping file names so you can just select the file radix, and enter all translations at once.
Specs now pass

I think this is a good enough step to be merged in and address any further improvement as a separate PR.
See video here: https://www.dropbox.com/s/kwu8wbhbneegwet/iye_new_key.mov?dl=0

:+1:  looks great!

This is cool, I'd like this merged into iye, would save me great amounts of time. How far are you from finishing/merging this in?

I incorporated these changes in my PR #20, trying to fix the issues mentioned here.

@paolodona Your improvements are cool, and we'd love to have them.
Are you still up for making this happen? If not, @1st8 has expressed interest in taking this over if you want to him to do it :grin:

Sadly I find myself quite busy with my day job so realistically I will not be a good & active maintainer right now. Happy for someone else to take it over and incorporate my changes. Thanks guys!

Sweet! We'll move the discussion to #20. Thanks for the work :grin:


object.props "required" but z.infer returns  "optional" type?

deps:
<EMAIL_ADDRESS><EMAIL_ADDRESS>code:

ps: the "parse" & "safeParse" method works well

what does your tsconfig.json look like?
I noticed my schemas were doing the same if either compilerOptions contains "strict": true or no strict property, or also if "strictNullChecks": false was set.

what does your tsconfig.json look like? I noticed my schemas were doing the same if either compilerOptions contains "strict": true or no strict property, or also if "strictNullChecks": false was set.

ah, you'r right 👍
I didn't realize that
sorry and thank you


Getting 'Method [validateUniqueWith] does not exist.' Error.

Seems like UniqueWithValidatorServiceProvider validator resolver is not doing it's thing.

Yesterday it was working fine now I run composer update then I got this issue
{"error":{"type":"BadMethodCallException","message":"Method [validateUniqueWith] does not exist.","file":"E:\\PROJECT DEPT\\Server\\htdocs\\apps\\onlineworkforce\\laravel\\vendor\\laravel\\framework\\src\\Illuminate\\Validation\\Validator.php","line":2564}}

As per instruction in previous comment I add those two line and run php artisan I got this bellow oputput :
O:\laravel>php artisan
string(31) "Illuminate\Validation\Validator"
string(48) "Felixkiss\UniqueWithValidator\ValidatorExtension"
Laravel Framework version 4.2.17

Hello guys, I have the same error on 5.2
BadMethodCallException in Validator.php line 3265: Method [validateUniqueWith] does not exist.
Here is my composer.json
{
  "name": "laravel/laravel",
  "description": "The Laravel Framework.",
  "keywords": [
    "framework",
    "laravel"
  ],
  "license": "MIT",
  "type": "project",
  "require": {
    "php": ">=5.5.9",
    "laravel/framework": "5.2.*",
    "prettus/l5-repository": "^2.5",
    "league/fractal": "^0.13.0",
    "robclancy/presenter": "^1.3",
    "yajra/laravel-datatables-oracle": "^6.11",
    "predis/predis": "^1.0",
    "barryvdh/laravel-debugbar": "^2.2",
    "darkaonline/l5-swagger": "~3.0",
    "adldap2/adldap2-laravel": "2.0.*",
    "aws/aws-sdk-php": "^3.18",
    "prettus/laravel-validation": "dev-develop as 1.1.4",
    "felixkiss/uniquewith-validator": "2.*"
  },
  "require-dev": {
    "fzaninotto/faker": "~1.4",
    "mockery/mockery": "0.9.*",
    "phpunit/phpunit": "~4.0",
    "symfony/css-selector": "2.8.*|3.0.*",
    "symfony/dom-crawler": "2.8.*|3.0.*",
    "laracasts/generators": "^1.1",
    "codeception/codeception": "^2.2",
    "barryvdh/laravel-ide-helper": "^2.2"
  },
  "autoload": {
    "classmap": [
      "database"
    ],
    "psr-4": {
      "Ehos\\": "app/"
    },
    "files": [
      "app/helpers.php"
    ]
  },
  "autoload-dev": {
    "classmap": [
      "tests/TestCase.php",
      "tests/functional/GeneratorTrait.php"
    ]
  },
  "scripts": {
    "post-root-package-install": [
      "php -r \"copy('.env.example', '.env');\""
    ],
    "post-create-project-cmd": [
      "php artisan key:generate"
    ],
    "post-install-cmd": [
      "Illuminate\\Foundation\\ComposerScripts::postInstall",
      "php artisan optimize"
    ],
    "post-update-cmd": [
      "Illuminate\\Foundation\\ComposerScripts::postUpdate",
      "php artisan optimize"
    ]
  }
}

And how I use it
public function rules()
    {
        return [
            'recorded_at' => 'required|unique_with:timeslips,user_id,type',
        ];
    }

Thanks

I have the same error on larvel 5.3.
The boot method i called since i can dd there

Hey dude, i have followed up the discussion but still getting
BadMethodCallException in Validator.php line 3295:
Method [validateUniqueWith] does not exist.
composer.json file has the package, i have added the provider, here is my validation rule
`$rules = [
'house_id' => 'required|unique_with:caretaker_assign_house,caretaker_id',
'caretaker_id' => 'required',
];
    $validator = Validator::make($request->all(), $rules);

    if($validator->fails()) {
        die();
        return Redirect::back()->withErrors($validator);
    }`

Help pls

What version are you using?

Laravel 5.5 happen to me
this helped:
composer update
artisan config:cache
artisan cache:clear
artisan optimize