Bug - Tooltips not aligning correctly in certain elements

I have an issue with mdl tooltips not aligning correctly and I have tracked it down to what I believe is the problem. I have a large web app where elements can either be displayed within the third party library react-grid-layout, or outside of react-grid-layout. If an item is within react-grid-layout, none of the tooltips align correctly, they're always offset by the same offset of the react-grid-layout region from the parent container. This is because the react-grid-layout regions call transform: translate(X, Y) (X and Y being a pixel offset from the region in the top left, the top left region is always set as 0px, 0px, even if it's halfway down a page).
This seems to cause the MDL tooltips to base their position information on the referenced element's position within the overall window, but when it sets the position information on the tooltip itself, it seems to think that the react-grid-layout's top left region is at 0px, 0px of the entire screen, using that as a reference point. This causes the tooltips to display too far right and too far bottom.
I guess my point is that the tooltips are using one set of position information (absolute window pixels) to adjust where they are based on a relative position (pixels within a parent element that has used transform: translate). If someone has seen something like that before and knows of a fix, that would be much appreciated, but I think this may be an underlying, albeit rare, issue built into mdl tooltips?

@brucedlukens can you add a test link to the issue? with css and html.
I had experienced a similar issue recently maybe i can help

Here is a JSFiddle showing the issue. The first row of buttons is displaying the correct tooltips, the second row of buttons is the issue I'm referring to.
https://jsfiddle.net/svan6ntd/7/

@brucedlukens why not use these  components instead ?
They are well maintained and made for react framework and up-to-date with the latest version of mdl

@puranjayjain Our team has decided against Material-UI for a few different reasons. Not to mention, it doesn't seem like Material-UI has support for tooltips yet.
This issue seems like it will present itself outside of react as well.

@brucedlukens i'll try to solve it with mdl then give me some time to cookup a hotfix

@brucedlukens try this setting on the secondGroup it will work like magic (tested in chrome 49)
#secondGroup {
/* transform: translate(0px, 0px); */
display: block;
}

@puranjayjain All you did was take the problem, and comment out the problem.... That's not a solution. Has anyone from the MDL community looked into this issue or have a workaround?

@brucedlukens so that transform property is required by you? I guess if that doesnt solve your problem you can escalate the issue at the gitter chat

sorry my bad @brucedlukens there is another solution however, without removing the transform property if you want, add this property top: 20px !important; to all the tooltips in the second row, it will work (psst) its a dirty fix

@puranjayjain Thank you for the dirty fix, that may be what I'll have to do in the meantime.
I do still think that this is an issue in the mdl tooltips, especially seeing as how you can have other mdl components inside the transform div and they all work correctly, but the tooltips do not. This inconsistency is the main problem.

@brucedlukens there are some problems with how the component calculates its position, hopefully it will be fixed soon.

I had this problem with riot.js too, the solution was to append the tooltip to the document root, since the tooltip css defines a fixed position and the position calculation is based on the absolute position of the element (button). So, on mount I append the tooltip into body and upgrade it, on unmount I remove it. Not sure how this should be done in React though.

Same problem here: if a tooltip is placed inside a parent that has a transform, positioning screws up.
As @RanzQ said, a quick fix is to place the tooltip DOM element outside that parent. It does however makes component-based design somewhat harder because changing the DOM hierarchy isn't always possible.
Any progress on fixing the positioning root problem?

Still having this issue on the latest version (1.3.0) when placing the tooltip inside a dialog.
Either disabling the transform on the dialog with: transform: none !important or placing the dialog outside it worked for me.
Why is the transform property needed for the dialog component? I don't see any visual changes.


Next release

Are we missing a reference to Hermes (#394) in changelog? Suggest that it needs to reference the docs and/or the need to use source map tool.


Use defvar-local to define buffer-local variables

Thanks.

Great - this wasn't possible before, when I was supporting Emacs versions < 24.3.

I only make this PR when I saw you set the minimum Emacs version to 24.4...

That's what I guessed - much appreciated. 😄


How to separate the admin panel like Laravel or other frameworks. Completely different layout and UI or look and feels?

Flexible UI
Suppose we want a different UI and layout for our admin panel. Want to use CSS frameworks like Tailwind or the higher Bootstrap version.

I would like to know how to do this too

Thank you for this suggestion! But why would you really want this...? The admin dashboard is fully integrated with the rest of the software. Everything is consistent. Two different themes for the admin dashboard and the rest isn't possible. Themes are used everywhere as the admin dashboard is part of the rest 🙂
Have a great weekend to you both @mateable @Monarul007! Happy coding and enjoy your social dating web app!
Looking forward to speaking with you on GitHub issues!


Added support for custom skins. Tested with 0 performance impacts.

Unfortunately has to be a janky implementation due to Minecraft.getMinecraft() being null during pre-init, which, Dynamic Resources require the Minecraft instance.
Note: Servers will also need the images in order to register.

Unfortunately has to be a janky implementation due to Minecraft.getMinecraft() being null during pre-init, which, Dynamic Resources require the Minecraft instance.

Minecraft.getMinecraft() is never null during pre-init, Minecraft get initialized first thing in the whole code, without it the game does absolutely nothing.

Then complain to the nullpointer i was getting not to me xD

Then complain to the nullpointer i was getting not to me xD

It is probably because you where using it on the server then, Minecraft is the physical client class

Holy, please only run the actual texture registering, on the client, you are doing it on both sides right now


[stable/newrelic-infrastructure] update to 1.6.0, add psp support

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 #

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

/assign davidkarlsen

@davidkarlsen Should be ok now :-)

bump

/assign  paulczar
/assign  scottrigby

/ok-to-test

/lgtm


docs: add missing CockroachDB docs

Continuing the work to make https://github.com/testcontainers/testcontainers-rs-modules-community/issues/2 happen

Thank you 🙏


Un espace manquant dans la traduction

💡 We improve the calculation and its default valuesevery month!
Problème à cet endroit.
> This ticket was created automatically by our robot from our translation contribution page.

Fixed by https://github.com/datagir/nosgestesclimat-site/commit/92d35f69c32c680bab75b5ab0c05394fa854f261 thanks !


Corrected a few spelling errors

I changed two instances of "assistent" to "assistant".

Thanks :+1:


Rancher-created registry secret is missing the auth field

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a registry secret from the UI
Inspect it via kubectl
Decode the .dockerconfigjson field

Result:
{"auths":{"registry.example.com":{"password":"password","username":"username"}}}

Expected Result:
{"auths":{"registry.example.com":{"username":"username","password":"password","auth":"dXNlcm5hbWU6cGFzc3dvcmQ="}}}

Other details that may be helpful:
If the secret is created via the rancher-supplied kubectl then the secret has the auth field inside. Also, technically speaking the email field should be there as well
Possibly related to:
https://github.com/kubernetes/kubectl/issues/571
This breaks tools like
https://github.com/weaveworks/flux/
That use the secret to list images sha and tags
Environment information

Rancher version: 2.1.7
Kubernetes Version: v1.13.4
Installation option:  Single Node

+1
I have the same Rancher version and I can confirm this issue.
Flux needs the Auth field to work properly.
Also, there is a forum issue reporting this behavior.

@deniseschannon - ping to get this on our radar for consideration

I would vote for this being backported to 2.2.x too.

The fix is based on this upstream kubectl fix, which generates this auth field: https://github.com/kubernetes/kubernetes/pull/72344/files#diff-3bf290ed2a11e649da5afa02a5bbfd3a
When we create a dockerCredential secret from Rancher UI, we post the data via K8s REST API - which does not seem to have this "auth" field generation like kubectl does. Hence we will handle the generation of this field while creating the secret.
We will not be supporting upgrade of existing secrets. Only new secrets created will have the "auth" field generated.

Any thoughts on backporting to 2.2?

I am assuming that since this is still open that this hasn't landed yet in 2.3?

@ekristen not yet, it is scoped for the next rancher patch release 2.3.3

doh! was hoping 2.3.2 ... glad it's scoped though! Thanks! Looking forward to this landing. Appreciate the feedback @prachidamle, much appreciated.

Reproduced the issue on 2.3.2
Steps:

Create a registry secret from the UI
Inspect it via kubectl
Decode the .dockerconfigjson field - echo '<dockerconfigjson-value>' | base64 -d in kubectl in cluster

{"auths":{"index.docker.io":{"password":"password","username":"username"}}}> `

Verified on 2.3-head - latest
Steps:

Create a registry secret from the UI
Inspect it via kubectl
Decode the .dockerconfigjson field - echo '<dockerconfigjson-value>' | base64 -d in kubectl in cluster

{"auths":{"index.docker.io":{"auth":"c293bXlhdjI3OnRlc3Q=","password":"password","username":"username"}}}>


[WIP] Bounty: Mazda

There is still work to be done but I think a PR gives more visibility to this port with more potential help from members of the community. I have been working on this port  since late last year with help from a few members in the community (extra thanks to @bugsy924).
Unfortunately, Mazda has the same steer lockout issue as ford. If the hands are off the steering wheel for more than 5 seconds you get a warning and the steer commands eventually get ignored. So far I have not found a solution for that,  maybe we will have better luck with new models next year.   My solution until now is to use a weight on the steering wheel.
Torque is modest but enough to handle most curves on a freeway (up to 8-10 degrees). I've driven 10s of hours so far with no major issues. A few users in the community have been using my port and they reported positive results.
I need to work more on the safety side of things, this will be done in the next few weeks. I have put all of my energy so far to find a programmatic solution for the lock out issue.
The Mazda giraffe is available here:
https://github.com/Jafaral/neo/tree/mazda/giraffe/mazda
I will submit a PR against the neo repo, but I need to move the lateral control to CAN 2, in the current design that is on CAN 1.
Comments are welcome!
Jafar/Jacar

@rbiasini Should I rebase my changes on top of devel and squash most of the changes ?  guess I also have to remove the dbc and panda files since those should go into their own repos. I already upstreamed the dbc file but I made some tweaks to it.

@Jafaral, thanks for opening this PR. Looks like the overall architecture is good. Few preliminary comment:

safety code needs work
the 10s lockout unfortunately would make the port unmergeable :(.
as far as CAN enumeration: yes, you should swap CAN 1 and CAN 2.

would a read-only version be upstreamable with a link to a community maintained openpilot fork?
On Jul 31, 2019 1:05 PM, rbiasini<EMAIL_ADDRESS>wrote:
@Jafaralhttps://github.com/Jafaral, thanks for opening this PR. Looks like the overall architecture is good. Few preliminary comment:

safety code needs work
the 10s lockout unfortunately would make the port unmergeable :(.
as far as CAN enumeration: yes, you should swap CAN 1 and CAN 2.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/commaai/openpilot/pull/762?email_source=notifications&email_token=AHMDMSF2PEUQMGGVXLL6MS3QCD6PDA5CNFSM4IHAAQTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3F5LXI#issuecomment-516675037, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AHMDMSF2G5H2N4U57B7DLQDQCD6PDANCNFSM4IHAAQTA.

@bugsy924 actually yes. Same thing we do with Ford: we just won't upstream carcontroller.py and mazdacan.py.

@bugsy924 great suggestion. @rbiasini thanks for the feedback. I will work on getting a read-only version cleaned up for upstream merge.

https://www.youtube.com/watch?v=qYF_1PSZWdQ

@rbiasini what if I make carcontroller.py and mazdacan.py themselves read-only,  no control packets are sent, and the panda also would be in read-only mode, can we upstream it that way? That way the port would have the complete logic but without any actual control. I have done more than 30 hours driving over the last few days and pretty comfortable moving forward with this. I will post more videos if needed.

Two lanes highway drive:
https://www.youtube.com/watch?v=f0MayhGbmmY

@Jafaral I have a 2019 Mazda 3 Hatchback and I don't believe I have the 5 second auto lockout. I do not get the "Please hold steering wheel" prompt. So is it possible that Mazda has removed that feature?
Is there a way I can contact you privately (so we don't clog up this pull request) to find out if this is actually the case?

@avion540 another Mazda3 user reported the same thing - no warning after 5 seconds. This is really promising news. We need to confirm this by running OP on one of those new cars to confirm. Join the discussion on comma's discord server, we have a Mazda channel and also you can DM me there @Jacar

With the dbc and panda upstreamed I went a head dropped those files from this. I also squashed all commits to two, one for the simple boardd mazda safety addition and the other is the the whole new mazda directory. I also rebased on top of master. Will be testing this more over the next few days.

@rbiasini Thanks for taking the time to review this. I will  drop the unused or otherwise the nice to have features but not necessary for the port. I came to the same conclusion myself. What I drive with now is the simplest code path, no changes to any of the dash msgs, everything is stock. The only thing I send  is the LKAS msg. I don't even drop the stock LKAS and the car is just happy that way. since I send LKAS at a much higher rate than stock the EPS just ignores the stock LKAS msgs and uses what is coming from OP. This allows me to run OP with zero chances of dashboard errors, I haven't seen one in a long time. I can plug the EON anytime even when the car is driving and unplug it any time even when the car is driving in everything works smoothly. The result is zero friction with EON. I don't have to take it off overnight and keep it charged. If it is dead in the morning, but the time I drive a mile or so, it is booted and running as it should without any intervention! I love it!


Add support or GeoJSON-L

GeoJSONL: An optimized format for large geographic datasets

See: https://www.interline.io/blog/geojsonl-extracts/
Seems to be getting more support. It's basically GeoJSON but restructured to make it easy to stream. This is potentially an easy implementation that streamlines vector data in Cesium, and would be a great solution we can use today until vector 3D Tiles are further enough along. A lot of vector datasets I've seen on the forum aren't necessarily very large (a few thousand lines/polygons) but will completely freeze up the main thread in Cesium on load, or worse, crash. (This is something that the oldest open Cesium PR at the time of writing fixes but no consensus was reached https://github.com/AnalyticalGraphicsInc/cesium/pull/3970)

@hpinkos  propbably label "category - data sources" and "type - enhancement" ?

If this is all the rage and lots of users are asking for it, then it's a no-brainer, but unless I'm missing something, that's not currently the case.
I tried to google around for this but found very little info.  Google itself only shows 195 hits for "geojsonl".  I think we'll want to wait until this gains significant traction before implementing it, and while trivial, I am skeptical that this will provide any real improvement in Cesium because it will add a bunch of overhead.
It will certainly fix the lock-up issue caused by lack of incremental parsing, but the amount of time taken to load will be a lot higher and for large geometries, it will just move the problem to the primitive tessellation, which is the real bottleneck for formats like GeoJSON in 3D.
Not trying to be a downer, but I'm extremely skeptical here.


request.default does not return a wrapper

Hi,
in the request implementation, cqlling request.default returns you a wrapper that you'll use to issue your next requests using those defaults.
In web-request, calling default only calls request.default and returns void.

You're right, thanks for pointing this out! Let me think about how we can get that same behavior here.

Fixed in 1.0.6.

oops closed the wrong issue


fix last inconsistencies in generics

... use collections, not arrays

Overall, this looks fine to me. I just need some inputs from the rest of the team on one specific change, for which I have raised a dev list thread<EMAIL_ADDRESS>

The new method is taken from AbstractOSGiResolver where a corresponding method is made public. All resolvers implement only the new method and the fallback for the deprecated method is moved to AbstractResolver. The new method is crucial for the SearchEngine to work properly; leave it out and you may as well leave out everything.

BTW, the old method is still there, the implementation is in the abstract class, AbstractResolver.

The methods in AbstractResolver must be defined the other way around: the default implementation of the method with new signature should call the method with the old signature. May I amend the commit?

The same applies to ChainResolver (which should check resolver type as suggested by @jaikiran); actually, all custom resolvers that do not extend AbstractResolver could be wrapped in chain resolver then as a workaround.

Is this sufficient, or should I add an extra check in ChainResolver
            if (resolver instanceof AbstractResolver || hasGenericMethod(resolver)) {
...
            }
....

   private boolean hasGenericMethod(DependencyResolver resolver) {
        try {
            return resolver.getClass().getDeclaredMethod("listTokenValues", Set.class, Map.class).getReturnType().getSimpleName().equals("Set");
        } catch (NoSuchMethodException e) {
            return false;
        }
    }

Hi Gintas,
To be clear - what I meant/proposed in the dev list was:

It's fine to have all the changes related to introducing that new method with Java generics on the implementation classes, including the AbstractResolver. No objections to it.

However, I think we shouldn't yet introduce it on the DependencyResolver interface in this release.

Finally, as you note in the latest comment, we would need to do a type check in our (internal) classes where we use the DependencyResolver interface's listTokenValues method to see if it's of type AbstractResolver and if it is, then invoke the new generic method. Else invoke the older method. We don't need to do a reflection check to see whether the resolver has the generic listTokenValues method, since the other existing method should just function as normal. So ultimately something like:

    if (resolver instanceof AbstractResolver) {
       Set<Map<String, String>> tokenVals = resolver.listTokenValues(...) // the new generic method
    } else {
       // call the method that's exposed via the DependencyResolver interface - the one which doesn't use generics
      Map<String, String>[] tokenVals = resolver.listTokenValues(...);
    }

In short, in this release, don't expose this as a new API on the interface but expose it on the AbstractResolver with an internal implementation that will trickle down to all external resolvers that extend the AbstractResolver.
Again, I'm being a bit extra cautious on this specific interface unlike some other interface/class changes that we have been doing since this one acts as the central well known contract to the developers who have extended Ivy. Plus the fact that we do have a way to do all the changes being proposed in this PR without having to force the implementations of the DependencyResolver to implement that new method in this specific release.

Thanks for clarifying.
My point was that the use of the method is limited to two classes: SearchEngine and ChainResolver (because it is essentially a proxy).
A quick search seems to indicate that most (if not all) custom resolver implementations out there extend AbstractResolver, and thus providing a default implementation of the method with the new signature as a wrapper in the abstract class will mitigate the problems due to the lack of it.
Therefore I would like insist on adding the method to the interface as well as changing the signature in all resolvers that ship with Ivy. Any public method in the abstract class should be declared in the interface, and going halfway does not make much sense.

@twogee, you have looked into the open sources softwares that use Ivy, but Ivy is under the ASL, not the GPL, it might be used in some closed, commercial products :)
So we cannot know for sure that we won't break softwares by changing that part of the API.
The hierarchy of the classes of the DependencyResolver is not of the best design, it would have been great to have more composition than inheritance. But that's we have. So unless we want to break things, rewrite things and make an Ivy3, I think we should stick with it.
To move forward, I suggest that this PR doesn't break the API at all. And if you still think DependencyResolver deserve a probably-safe API break, you're welcomed to discuss it on ant-dev so we can get a consensus.

@nlalevee, we already broke a few things by going Java 7 (and gained native symlinks 😉). For more examples, look at commons-lang3 breaking off commons-text and introducing escapeHtml3 and escapeHtml4 instead of escapeHtml -- all without changing a major version. Pointing to some hypothetical closed code is a poor excuse -- as if commercial vendors (or their customers) have no QA and expect the dependencies to be drop-ins every time. I will present the argument on ant-dev in a more coherent form later.


Charts get distorted sometimes and I dont know why.

I'm using charts from chart.js with bootstrap carousel. Sometimes the charts go from this pie chart working correctly to pie chart not working correctly. The charts get distorted for some reason, and whenever a chart is distorted and I make the browser window bigger or smaller using the mouse by dragging, the chart goes back to its correct working state which is strange. This only happens sometimes but it is still a problem that needs to be solved. The problems seems to occur more frequently when the browser window isn't fully expanded.
It might be also helpful to know that I have two charts on 5 different carousel pages, and every 5 seconds it moves from one page to the next. Weirdly enough, sometimes only the charts on one slide of the carousel get distorted and the others are fine, but its appears to be random which charts get distorted. Sometimes its charts on one page and other times its charts on many pages.
Check it out here.
http://<IP_ADDRESS>/
I just noticed that the charts width = 792 and height = 792 when working correctly and when its distorted that changes to width = -60 and height = -60, why would that happen?
Steps to Reproduce
Its difficult to reproduce but, open this in your browser (http://<IP_ADDRESS>/), keep it open for a while and you will see pie charts starting to get distorted, also note that changing the browser window size will make the problem go away. I think the problem is more likely to occur when the browser window isn't fully expanded. As far as I know it occurs in Google chrome and safari, I haven't tried any other browsers.
Here is my code:

                <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#nav-pillz">
                    Toggle navigation

                </button>

Page A

Page B

Page C

Page D

Page E

The first item of the carousel with two pie charts inside(the other items are the same):

            <canvas id="pieChartA" ></canvas>

            <canvas id="pieChartB" ></canvas>

Chart js javascript file:
$(document).ready( function() {

var ctx = document.getElementById("pieChartA");
var myPieChart = new Chart(ctx,{
    type: 'pie',
    data: {
        labels: ["Red","Blue","Yellow"],
        datasets: [{
            data: [30, 15, 55],
            backgroundColor: [
                "#FF6384",
                "#36A2EB",
                "#FFCE56"
            ],
            hoverBackgroundColor: [
                "#FF6384",
                "#36A2EB",
                "#FFCE56"
            ]
        }]},
        options: {
            animation : false
        }
    });
});

$(document).ready( function() {
var ctx = document.getElementById("pieChartB");
var myPieChart = new Chart(ctx,{
    type: 'pie',
    data: {
        labels: ["Red","Blue","Yellow"],
        datasets: [{
            data: [30, 15, 55],
            backgroundColor: [
                "#FF6384",
                "#36A2EB",
                "#FFCE56"
            ],
            hoverBackgroundColor: [
                "#FF6384",
                "#36A2EB",
                "#FFCE56"
            ]
        }]},
        options: {
            animation : false
        }
    });
});

Javascript file which controls carousel:
$(document).ready( function() {
    $('#myCarousel').carousel({
        interval: 4000
    });

    $('#playButton').click(function () {
        $('#myCarousel').carousel('cycle');
    });

    $('#pauseButton').click(function () {
        $('#myCarousel').carousel('pause');
    });

    var clickEvent = false;
     $('#myCarousel').on('click', '.nav a', function() {
            clickEvent = true;
            $('.nav li').removeClass('active');
            $(this).parent().addClass('active');
    }).on('slid.bs.carousel', function(e) {
        if(!clickEvent) {
            var count = $('.nav').children().length -1;
            var current = $('.nav li.active');
            current.removeClass('active').next().addClass('active');
            var id = parseInt(current.data('slide-to'));
            if(count == id) {
                $('.nav li').first().addClass('active');
            }
        }
        clickEvent = false;
     });
});

@christopherdurning what version of chrome do you have? I tried with Chrome on a mac and didn't notice this even after keeping your page open for a while. The only thing I can think is that somehow there is a race condition and the size measures before the div is visible and the change is not detected. This would explain why resizing the window (which triggers the resize handlers) fixes this.
@simonbrunel thoughts?

Chrome Version 59.0.3071.104 on mac, I just noticed a better way to reproduce the problem. Have a few tabs in the browser window, open a tab with this address http://<IP_ADDRESS>/, then switch to a different tab and then switch back and it will be distorted, try this a few times.

@etimberg

hmmm, maybe something happens with chrome power saving features 🤔

@etimberg , just to pick your brain one last time about this issue. I noticed that this problem does not occur when you open the web page on a mobile device, not sure why that is, perhaps something to do with the screen size. In the html file (the second code snippet down from the top) is there anything wrong with the way I'm setting the column sizes for different screens (these lines ), I dont have a background in JS and html so this is all fairly new to me.

I think this is a duplicate of #4397 which was fixed in #4406


Genre Failure

Hello,
First off I want to complement you on a very good library however there is one rather serious error.
In a ID3V2 tag you can have any genre, not just the ones you listed in the array.  If you read a file that has a genre that is not in your array then the app crashses.
/id3js/dist/id3.js:231
var bomInt = this.getUint16(offset);
Is there any plans to extract the actual id3v2 genre string instead of converting it to a number?

This is a duplicate. Please refer to https://github.com/43081j/id3/issues/6


The SSH public key doesn't get set on the booted VM.

SSH public key doesn't work unless we copy it to the particular path with the following steps:
mkdir -p bip-orchestrate-vm/ssh-key/
cp ~/.ssh/id_rsa bip-orchestrate-vm/ssh-key/key
cp ~/.ssh/id_rsa.pub bip-orchestrate-vm/ssh-key/key.pub

cc @javipolo


Zooming via trackpad does not work

qt6 version
macOS

Zooming via scroll wheel works as expected, but trying to use the trackpad the image disappears entirely. Only the black background is shown.

Just to check, this is with the "tplay-qt" app?

yes


0.4.0: rename group from images.banzaicloud.io to images.cisco.com

Q
A

Bug fix?
no

New feature?
no

API breaks?
yes

Deprecations?
yes

Related tickets
N/A

License
Apache 2.0

What's in this PR?

This patch changes the group name of ImagePullSecrets from images.banzaicloud.io to images.cisco.com.
This is a breaking change.
Upgrading
To upgrade to v0.4.0 the following procedure should be followed:
Step 1) Scale down the replicaset of IMPS to 0. This prevents IMPS from updating any pull
secrets.
Step 2) Change all Secrets containing ECR login information whose are referenced from any ImagePullSecrets object to
cisco.com/aws-ecr-login-config (from banzaicloud.io/aws-ecr-login-config)
Step 3) Install the new version of the imps helm chart.
Step 4) Recreate all ImagePullSecrets objects with the new group of images.cisco.com (see README.md for examples)
Step 5) Delete the old CustomResourceDefinition
from your cluster as:
kubectl get imps

will display the CRDs with the old group information and not the new group's contents.
To delete the old CRDs please execute:
kubectl delete crd imagepullsecrets.images.banzaicloud.io

Why?

This breaking change renames the imagepullsecrets CRD's group from images.banzaicloud.io to images.cisco.com to reflect that this project  is part of the Cisco ecosystem.
Checklist

[x] Code meets the Developer Guide
[x] User guide and development docs updated (if needed)
[x] Related Helm chart(s) updated (if needed)

Moving back to draft, as we might want to do this when the open source projects are merged into cisco's open source organization.


c2d info now needs to include additional instrs on enabling APIs

Placeholder issue so I don't forget. Turns out that we now need to have people enable two apis in their GCP project prior to running the c2d app, otherwise deployment will fail:
https://console.cloud.google.com/apis/api/iam.googleapis.com/overview
https://console.developers.google.com/apis/api/cloudresourcemanager.googleapis.com/overview
This might be a recent change in how GCP projects are set up.

Thanks @amygdala Do people need to enable these APIs only if using C2D? Also, currently C2D doesn't yet support v0.7. Do you know if the requirement for these APIs will apply when C2D supports v0.7 too?

Related (but different APIs): https://github.com/kubeflow/website/issues/1248

Ah, here's where Kubeflow requests the APIs:
https://github.com/kubeflow/kubeflow/blob/1d811f737d7555782dbeab09eb88795a84aeded9/bootstrap/pkg/kfapp/gcp/gcp.go#L2186
From the above, it looks as if we need the user to enable them for either the CLI deployment or C2D - is that a correct assumption?

I see we do already tell them to enable the IAM API. I'll include a section in the C2D guide asking people to check the requirements. I'll also add the Cloud Resource Manager API to the list.


Payload from Trigger CronJob is not send to event.Data

Hi,
I noticed that event.Data is empty when it is triggered by payload of CronJob.
I create my test function:
kubeless function deploy test -n kbox --runtime go1.14 --from-file test.go --handler test.Handler --dependencies go.mod
source of file test.go
package kubeless

import (
	"fmt"
	"github.com/kubeless/kubeless/pkg/functions"
)

func Handler(event functions.Event, context functions.Context) (string, error) {
	fmt.Println("datais", event.Data)
	return event.Data, nil
}

then I created the Trigger cronjob:
kubeless trigger cronjob create -n kbox test --function test -f test.json --schedule "*/1 * * * *"
source of test.json
{"action":"createpod","data":{"name":"mypodname"}}

the logs from pod test-6747bdf7b6-mz96f show that event.Data is empty
2020/10/20 07:55:16 <IP_ADDRESS>:39188 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+
2020/10/20 07:55:46 <IP_ADDRESS>:39306 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+
datais
2020/10/20 07:56:03 <IP_ADDRESS>:55296 "GET / HTTP/1.1" 200 curl/7.52.1
2020/10/20 07:56:16 <IP_ADDRESS>:39452 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+
2020/10/20 07:56:46 <IP_ADDRESS>:39570 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+
datais
2020/10/20 07:57:03 <IP_ADDRESS>:55768 "GET / HTTP/1.1" 200 curl/7.52.1
2020/10/20 07:57:16 <IP_ADDRESS>:39716 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+
2020/10/20 07:57:46 <IP_ADDRESS>:39834 "GET /healthz HTTP/1.1" 200 kube-probe/1.17+

Can You please give me tip what I am doing wrong here.
Thank you in advance.

Yes, nothing is wrong there. The cronjob trigger, by design, doesn't allow to modify the data to be sent, it's just a GET request sent in the given schedule. Note that since there is no interaction with the cronjob, any logic to obtain some data can be encoded in the function itself.
Let us know if you have some specific use case in mind for having this data.

Hi @andresmgot
Thank you for your answer.
I will put more description of my use case because the purpose of the test example wast only to show missing transfer data from Trigger Cron to Function.
In Kubeless I build a function that communicates with Kubernetes API and on-base what  event.Data contain, it will create two different Pods.
I thought that Trigger Cronjob has implemented such functionality, according to the documentions or I miss something.
Thank you in advance for your reply

ah, sorry @1ricardo, you are correct, it's possible to set some data in the latest version of Kubeless. Are you running Kubeless v1.0.7 in your cluster? Also, is your trigger properly created? You can check it if you execute kubectl get cronjobtrigger -n kbox test -o yaml.

Hi @andresmgot
I checked what you about asked:
so to be sure that I use the latest version I check configmaps of kubeless
❯ kubectl get configmaps -n kubeless -o yaml
apiVersion: v1
items:
- apiVersion: v1
  data:
    builder-image: kubeless/function-image-builder:v1.0.7
   ...

and here is result of kubectl get cronjobtrigger -n kbox test -o yaml
❯ kubectl get cronjobtrigger -n kbox test -o yaml
apiVersion: kubeless.io/v1beta1
kind: CronJobTrigger
metadata:
  creationTimestamp: "2020-10-20T07:52:46Z"
  finalizers:
  - kubeless.io/cronjobtrigger
  generation: 2
  labels:
    created-by: kubeless
  name: test
  namespace: kbox
  resourceVersion: "23919434"
  selfLink: /apis/kubeless.io/v1beta1/namespaces/kbox/cronjobtriggers/test
  uid: b0ee8a64-8b36-47f0-ae92-b21eec5de46d
spec:
  function-name: test
  schedule: '*/1 * * * *'

Got it, I am able to reproduce it. It seems that the problem is that even if the CLI is able to parse the payload you are giving:
▶ kubeless trigger cronjob create foo --function get-python-37 -f f.json --dryrun --schedule '* * * * *' -o yaml
apiVersion: kubeless.io/v1beta1
kind: CronJobTrigger
metadata:
  creationTimestamp: null
  labels:
    created-by: kubeless
  name: foo
  namespace: default
spec:
  function-name: get-python-37
  payload:
    f: b
  schedule: '* * * * *'

When creating it, in the cluster, it loses the payload property:
▶ kubeless trigger cronjob create foo --function get-python-37 -f f.json --schedule '* * * * *'
INFO[0000] Cronjob trigger foo created in namespace default successfully!

▶ kubectl get cronjobtrigger foo -o yaml
apiVersion: kubeless.io/v1beta1
kind: CronJobTrigger
metadata:
  creationTimestamp: "2020-10-22T09:02:57Z"
  finalizers:
  - kubeless.io/cronjobtrigger
  generation: 2
  labels:
    created-by: kubeless
  name: foo
  namespace: default
  resourceVersion: "2643761"
  selfLink: /apis/kubeless.io/v1beta1/namespaces/default/cronjobtriggers/foo
  uid: fbd94c72-73df-4ea5-9b60-7c6a683c0ad9
spec:
  function-name: get-python-37
  schedule: '* * * * *'

Adding @delucca to the thread. You contributed this feature. Are you able to reproduce the issue? Would you mind taking a look?

@andresmgot here is the commit where I've added the payload to the kubeless trigger cronjob create command: kubeless#78d3ce
Since our workflow uses Gitops and we don't create resources directly from the CLI in our cluster, chances are that I forgot to test the deployment from the CLI directly to the cluster, and tested it only with the --dry-run flag. I think that must be an easy fix.
This week I'm deploying a new service, so I'll only be able to take a look at it in the weekend. If this issue is not time-sensitve I'll gladly fix it ;)

Thanks a lot, @delucca @andresm for taking the time and looking at this matter

Hi @delucca  @andresmgot
I would like to ask you if there is any progress on that.
I will really appreciate any information or you can give me a tip on what field I should add to cron job trigger in Kubernetes so I can move forward with my project.
Thank you in advance
BR

@1ricardo as a workaround, you can edit your trigger and add the payload field manually:
kubectl edit cronjobtrigger <name>

...
spec:
  function-name: test
  schedule: '*/1 * * * *'
  payload:
    foo: bar


UMI support in WGTS mode

Description of feature
I have WGS data generated with a library prep that includes UMIs (Claret Biosciences SRSLY for FFPE.
The current pipeline code does not allow for umis in the wgts mode, only in the targeted mode.

Hi @SPPearce thanks for opening the issue. We'll have support for this functionality in an official nf-core release soon - stay tuned!


gather stats from zookeeper mntr command

Zookeeper has a tcp 4 letter command API that reports information worth logging.
Currently only the 'stat' command is being read. This adds 'mntr' command.
I'm trying to follow similar style to the parsing of the 'stat' command. Currently, all the results are reported as gauges with a tag of the given state. (one of 'standalone', 'leader' or 'follower')
I'm having trouble visualizing how this will be displayed in DataDog. I am also concerned with information conflicts between the 'stat' and 'mntr' command.
To test locally:

Make sure you have zookeeper running locally on the default port.
Setup the dd-agent repo as explained in the readme.
Add the following code block to the bottom of the checks.d/zk.py file.

if __name__ == '__main__':
    import json
    check, instances = ZookeeperCheck.from_yaml('/home/vagrant/src/dd-agent/conf.d/zk.yaml.example')
    for instance in instances:
        check.check(instance)
        if check.has_events():
            print(json.dumps(check.get_events(), indent=2, separators=(',',': ')))
        print(json.dumps(check.get_metrics(), indent=2, separators=(',',': ')))

4 . While inside the venv (with . venv/bin/activate) run the file.
PYTHONPATH=. python checks.d/zk.py

@Sirupsen @fw42 maybe have a quick glance at this?

why not PR this upstream?

@fw42 I suggested we review it internally and try it in production first, then PR upstream.

@Sirupsen changed tag to 'mode:', removed some comments and now throw an exception on failed parse.

LGTM
Can you update the file in https://github.com/Shopify/cookbooks/pull/6892 and then we'll ship this tomorrow to all nodes?

Oh remember to update the comment at the top of the file too :)

Note: the mntr command can return "This server is currently not serving requests" if it fails to join the cluster. This is probably the most important thing to monitor.

Good find @wvanbergen. Another thing I'd like to see is what these stats look like for an observer.

The exact string to look for is This ZooKeeper instance is not currently serving requests

This should be tagged with something like mode: disconnected/out-of-quorum/inactive. We should also have a standalone metric like zookeeper.mode.{inactive,leader,standalone,follower,observer} where each node does an increment on every run, so we know how many are in each state and preferably which... maybe there's a better way to visualize it in DD

What I use elsewhere is a set metric, tagged with the different states. E.g. I am using the kafkabridge.instances metric, tagged with the git sha of the version that is running. This allows us to monitor rolling out new versions:

@wvanbergen Related to what you said: The code already checks ruok at the top of the program. How might that relate to an error from mntr? Also, does the stat command respond similarly? The admin docs don't seem very clear on this front.

Ah it seems that both stat and mntr can receive This ZooKeeper instance is not currently serving requests even after an imok.

Looks like the parse_stat already in the code does not handle this form and will just raise an exception in this case. I have a feeling it will require re-writing maybe? @Sirupsen @wvanbergen

Looks to me like stat isn't worth parsing for DataDog. It's a subset of mntr except for a list of connected clients.

Removed stat command entirely. mntr is the only thing being parsed.
As suggested by @wvanbergen zookeeper.instances now reports
mode:{inactive,leader,standalone,follower,observer}

I also updated the header comment which I suggest you read.
I don't know how to test the This ZooKeeper instance is not currently serving requests error.
@Sirupsen

@jpittis use something like smoketest (I don't know if it can do this sort of thing), Docker + iptables (something like iptables -A INPUT -j REJECT), or Toxiproxy.

@Sirupsen It's backwards compat again.
Basically, it:

runs the old stat command
uses that version from that command to check if it can run mntr
Values will be logged twice under different names in some cases:
Example:
stat reports: zookeeper.latency.avg
mntr reports: zookeeper.avg.latency

Why both?
stat naming convention needs to be kept for backwards compat
mntr naming convention is more standardized and should be used over the other one.
If upstream doesn't like that, easy fix to remove the duplicates.
Gonna look into testing for failure with toxi proxy or something.

K sounds fine to me, make sure to write that in the upstream PR.
Does this library have any tests? You don't have to write automated tests for the failure mode IMO., just prove to yourself hardcoding against Willem's string works/.*

@Sirupsen It does have tests. I'll look into making them pass once I confirm Willem's string.

@Sirupsen: I tested willem's suggestion manually and the last commit handles it.
Confident that the code is good to go and would only need possible cleaning before a upstream pull.
Don't have time to fix the tests tonight. I'll get them working tomorrow.
(don't even know if they we're passing to begin with. lots of depreciated code in this repo)

Yeah, I remember getting them to run at some point and it was unpleasant. Can you update the code in the cookbook PR so we can ship that tomorrow morning?

When zookeeper is down, this check would raise an exception, stopping any data being sent to DataDog.
The script will now report a zookeeper.instances mode:down when it cannot reach zookeeper.
Before, the script would not report anything to DataDog if an exception occurred. Instead, now when the script encounters an exception, zookeeper.check.d.exception is incremented and zookeeper.instances is set to mode:unknown.
@Sirupsen I want to pop this into the cookbook asap so we can test it before the end of the day.

@jpittis just make another PR to the cookbooks to update the script

@Sirupsen: This logs the exception and renames the the increment to datadog_client_exception.
Feels ugly. Thinking I'll refactor it tomorrow. Might be worth testing the cookbook before I head out?

@jpittis if you merge your PR and message me on slack I'll kill the node for you.

@camilo, @fw42 @fbogsany: I'm looking to PR this upstream. Don't know Python too well so I'm feeling a little uncomfortable. Would you guys have any last minute reviews, or suggestions regarding the process of sending this upstream.
Keep in mind that 7e632de has been running successfully in production for a good few weeks.
Thanks.
cc @Sirupsen

ping @angelini and @orenmazor for python review please

why not PR this upstream?

I'm with @fw42. I'd love to see this upstream asap.

This was merged upstream from d0478d6dfe62d75b4e5d2c1718b813693668d2a7 through to 68c6debd536c65b1eed690c1d9b414f7d5d7288c.
There's no priority to updating to this code. I can do the update in the beginning of May.


io_uring backend?

Hi there, cool project!
Any plans to support io_uring backends for Async I/O (and event loop)?

Yes it's planned. I'm just trying to understand if I can do it avoiding to use liburing as I would like to keep the library free of dependencies.

The kernel interface seems fairly straightforward if you’ve worked on completion queue related settings like Infiniband (libibverbs) and other userspace networking settings. (NB: In Windows, IOCP is the closest equivalent, and in BSD, it’s kqueue.)
However, assuming you already link against a libc, I don’t see why you couldn’t optionally link against liburing and even libfabric (statically or otherwise), if the user wishes to use those backends. For most users, epoll is probably good enough, but the two approaches (completion queues vs epoll) are leaky enough abstractions that they affect how one writes their event loops in not so subtle ways.

I know about IOCP or kqueue (that's how Async library is implemented on Windows / macOS).
I have no idea however about what libfabric is.
Regarding not wanting to link liburing discussion I think it's a matter of definition.
In this project a dependency is anything that is not included with a standard C++ compiler / SDK / sysroot installation.
A dependency is a library that must be pre-installed by a developer or compiled from its sources.
This project links libc (and pthread) but libc comes with the compiler, so it's not considered dependency (it's always available).
liburing instead must be installed through a package manager or compiled from source, and so by this definition it's a dependency.
I should admit however, that this is a very clear definition on macOS or Windows, that come with properly defined SDKs.
On Linux doing the same is immediately more difficult once we need anything out of the libc because outside of the libc/ pthread and a few more libs you need to use some package manager to install "dev" packages (even just X11 or OpenGL / Vulkan for example) or clone and compile things with your own "build system" that I would like to avoid imposing to users.

Hi @ido ,
I have been starting the io_uring backend.
There is a first video I've been publishing on bootstrapping it
https://www.youtube.com/watch?v=YR935rorb3E
I will publish an additional one during this week getting the backend to fully pass the small test suite.
I will probably cleanup the code a little bit and push it to main branch the same day when next video will be pushed out.


Problem indicated in https://github.com/Andre0512/hon/issues/143 returned

Again no entities apart from the basic ones. I am using 0.13.0:

I'm pretty sure this was fixed in v0.14.0-beta.1, see #185


Remove incomplete http post backgrounding

Straight remove, no other changes.
@tobi

Moving this to the Shopify repo.


[Bug]: codeNation image is not visible

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
code nation company image is not visible in internship page
Expected behavior
gonna put another one
Add ScreenShots
No response
What browsers are you seeing the problem on?
No response
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

can you add screenshot @jahnaviyallamelli


CPU spike rule with metric_agg_script not working

name: Metricbeat Average CPU Spike Rule
type: spike_aggregation
es_host: localhost
es_port: 9200
es_username: <username>
es_password: <password>
index: metricbeat-*
timeframe:
  hours: 15
buffer_time:
  minutes: 15
metric_agg_key: myScriptedMetric

metric_agg_script:
    script: (doc['system.cpu.user.pct'].value + doc['system.cpu.system.pct'].value) / doc['system.cpu.cores'].value

metric_agg_type: avg
query_key: agent.hostname
doc_type: _doc
threshold_cur: 0.001
min_doc_count: 1
spike_height: 1
spike_type: "up"

filter:
- term:
    metricset.name: cpu

alert:
- "debug"

This is the rule configuration used. Data is present which exceeds the threshold.
I'm testing above rule with elastalert-test-rule bu the alerts are not generated
Is there any way to check the output of the script?

Which version of Elasticearch are you using?
If you use ES7.x, doc_type: _doc breaks your query.

Is there any workaround for raising the cpu spike alert?

@sshirode
Removing doc_type: _doc from @sanketshirode 's rule will alert.

Tried but didn't work. Even tried handling empty values by checking doc size still 0 hits and the values exceeding the threshold exist

@sanketshirode
Umm...
Would you please debug generated query like this? Generated query will be logged into trace.log.
/opt/elastalert # python -m elastalert.elastalert --es_debug_trace ./trace.log --rule ./rules/debug.yaml

is there any way to debug it with elastalert-test-rule command because my other alerts are already working

@sanketshirode elastalert.test_rule doesn't have --es_debug_trace option. You can run elastalert as a separate process from main elastalert with above command. Note that, to preventing many duplicate query, please specify only target rule with --rule option.

curl -H 'Content-Type: application/json' -XGET 'http://localhost:9200/metricbeat-/_search?pretty&ignore_unavailable=true&size=0' -d '{
"aggs": {
"bucket_aggs": {
"aggs": {
"metric_myScriptedMetric_avg": {
"avg": {
"script": "(doc[\u0027system.cpu.user.pct\u0027].value + doc[\u0027system.cpu.system.pct\u0027].value) / doc[\u0027system.cpu.cores\u0027].value"
}
}
},
"terms": {
"field": "agent.hostname",
"min_doc_count": 1,
"size": 50
}
}
},
"query": {
"bool": {
"filter": {
"bool": {
"must": [
{
"range": {
"@timestamp": {
"gt": "2020-03-24T08:51:23.415791Z",
"lte": "2020-03-24T09:06:23.415791Z"
}
}
},
{
"term": {
"metricset.name": "cpu"
}
}
]
}
}
}
}
}'
curl -H 'Content-Type: application/json' -XGET 'http://localhost:9200/metricbeat-/_search?pretty&ignore_unavailable=true&size=0' -d '{
"aggs": {
"bucket_aggs": {
"aggs": {
"metric_myScriptedMetric_avg": {
"avg": {
"script": "(doc[\u0027system.cpu.user.pct\u0027].value + doc[\u0027system.cpu.system.pct\u0027].value) / doc[\u0027system.cpu.cores\u0027].value"
}
}
},
"terms": {
"field": "agent.hostname",
"min_doc_count": 1,
"size": 50
}
}
},
"query": {
"bool": {
"filter": {
"bool": {
"must": [
{
"range": {
"@timestamp": {
"gt": "2020-03-24T08:51:23.415791Z",
"lte": "2020-03-24T09:06:23.415791Z"
}
}
},
{
"term": {
"metricset.name": "cpu"
}
}
]
}
}
}
}
}'
curl -XGET 'http://localhost:9200/?pretty' -d ''
curl -XGET 'http://localhost:9200/?pretty' -d ''
curl -H 'Content-Type: application/json' -XPOST 'http://localhost:9200/elastalert_status_status/_doc?pretty' -d '{
"@timestamp": "2020-03-24T09:06:24.612911Z",
"endtime": "2020-03-24T09:06:23.415791Z",
"hits": 269,
"matches": 0,
"rule_name": "Metricbeat Average CPU Spike Rule",
"starttime": "2020-03-24T08:51:23.415791Z",
"time_taken": 1.1970951557159424
}'
curl -H 'Content-Type: application/json' -XPOST 'http://localhost:9200/elastalert_status_status/_doc?pretty' -d '{
"@timestamp": "2020-03-24T09:06:24.612911Z",
"endtime": "2020-03-24T09:06:23.415791Z",
"hits": 269,
"matches": 0,
"rule_name": "Metricbeat Average CPU Spike Rule",
"starttime": "2020-03-24T08:51:23.415791Z",
"time_taken": 1.1970951557159424
}'

@ddaichi703n
Getting this in trace.log
I have set threshold to 0.0001 and there are avg values exceeding the threshold.
I have applied the same script in kibana scripted filed for metric beat index pattern and it works
Just there I need to handle the empty fields

@sanketshirode Your generated query looks good. I tested your query with my testing metricbeat index, and I got the alert!
I think your timeframe is too long. Therefore reference_count has not seems to be calclated yet. About timeframe in spike is discribed in https://elastalert.readthedocs.io/en/latest/ruletypes.html#spike.
Please shorten it and test again.
index: metricbeat-*
timeframe:
  minutes: 1  #change from `hours: 15`
buffer_time:

trace.log
curl -H 'Content-Type: application/json' -XGET 'http://localhost:9200/metricbeat-*/_search?pretty&ignore_unavailable=true&size=0' -d '{
  "aggs": {
    "bucket_aggs": {
      "aggs": {
        "metric_myScriptedMetric_avg": {
          "avg": {
            "script": "(doc[\u0027system.cpu.user.pct\u0027].value + doc[\u0027system.cpu.system.pct\u0027].value) / doc[\u0027system.cpu.cores\u0027].value"
          }
        }
      },
      "terms": {
        "field": "agent.hostname",
        "min_doc_count": 1,
        "size": 50
      }
    }
  },
  "query": {
    "bool": {
      "filter": {
        "bool": {
          "must": [
            {
              "range": {
                "@timestamp": {
                  "gt": "2020-03-24T16:33:16.338657Z",
                  "lte": "2020-03-24T16:48:16.338657Z"
                }
              }
            },
            {
              "term": {
                "metricset.name": "cpu"
              }
            }
          ]
        }
      }
    }
  }
}'
...
curl -H 'Content-Type: application/json' -XPOST 'http://localhost:9200/elastalert_status/_doc?pretty' -d '{
  "@timestamp": "2020-03-24T16:48:16.819592Z",
  "alert_info": {
    "slack_username_override": "Praeco",
    "type": "slack"
  },
  "alert_sent": true,
  "alert_time": "2020-03-24T16:48:16.382398Z",
  "match_body": {
    "@timestamp": "2020-03-24T16:48:06.446797Z",
    "agent.hostname": "3ec22bf16250",
    "num_hits": 90,
    "num_matches": 1,
    "reference_count": 0.03013888888888889,
    "spike_count": 0.05993333333333334
  },
  "match_time": "2020-03-24T16:48:06.446797Z",
  "rule_name": "Metricbeat Average CPU Spike Rule"
}'


Duplicate image on sample-SAP-scenario.md

There is a duplicate image (diagram-example-automation.png) on this page

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


[ci][docs] replace file extensions in docs during Sphinx build

@jameslamb I remember you proposed this change some time ago. But I was against because was not bought of idea to rewrite all docs source files during the build process. Now I know that we can do it via internal Sphinx process which doesn't require rewriting files on a disk. Also, this approach safer than rewriting files because we are sure our regex is applied only to links in docs (self.document.traverse(reference)) not to the whole document.
Live demo: https://lightgbm.readthedocs.io/en/sphinx/

@jameslamb Thanks!

all doing what we'd expect (including in the R package)

Another +1 for this way of replacing extensions because R-package docs will be unaffected as they are outside of the Sphinx build tree. 😉  (We simply pick up their folder after Sphinx is finished.)
https://github.com/microsoft/LightGBM/blob/eb9bbfb327815e843b808f5e2b4d73ee3201b4ac/docs/conf.py#L305-L307

@jameslamb Thanks!

all doing what we'd expect (including in the R package)

Another +1 for this way of replacing extensions because R-package docs will be unaffected as they are outside of the Sphinx build tree. 😉  (We simply pick up their folder after Sphinx is finished.)
https://github.com/microsoft/LightGBM/blob/eb9bbfb327815e843b808f5e2b4d73ee3201b4ac/docs/conf.py#L305-L307


running project error

run:
yarn i
yarn build

node_modules/@pixi/core/index.d.ts:25:24 - error TS2307: Cannot find module '@pixi/runner' or its corresponding type declarations.
25 import { Runner } from '@pixi/runner';
~~~~~~~~~~~~~~
node_modules/@pixi/utils/index.d.ts:4:26 - error TS2307: Cannot find module '@pixi/settings' or its corresponding type declarations.
4 import { isMobile } from '@pixi/settings';
~~~~~~~~~~~~~~~~
Found 2 errors.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: "types" exited with 1.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
and running pnpm ,and same result.

DashLineShader
If alignment is set to 0; Then the width will be calculated across the entire container width, which is not expected. Is there a way to avoid this problem?
 graphics.lineStyle({     width: 4,         color,         cap: PIXI.LINE_CAP.ROUND,         join: PIXI.LINE_JOIN.ROUND,         alignment: 0,  }) const pointCollect = [       [0, 0],       [200, 0],       [200, 200],       [0, 200],     ].flat();     graphics.drawPolygon(...pointCollect);


Find Highest Price region in the future

Hi, I'm trying to iplement battery charge at night and discharge only on few hours a day at the highest price (because of charge/discharge losses it doe'sn make sense to use the battery whole day)
So for this I'm looking for lowest price (1h duration is enough for me):
- trigger:
      - platform: time_pattern
        hours: "15"
    action:
      - service: epex_spot.get_lowest_price_interval
        data:
          earliest_start: "14:00:00"
          latest_end: "13:59:00"
          duration:
            hours: 1
            minutes: 0
        response_variable: resp
    sensor:
      - name: Lowest energy price
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

Then two "highest prices"
- trigger:
      - platform: time_pattern
        hours: "15"
    action:
      - service: epex_spot.get_highest_price_interval
        data:
          earliest_start: "00:00:00"
          latest_end: "11:59:00"
          duration:
            hours: 3
            minutes: 0
        response_variable: resp
    sensor:
      - name: Highest energy price 1
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

  - trigger:
      - platform: time_pattern
        hours: "15"
    action:
      - service: epex_spot.get_highest_price_interval
        data:
          earliest_start: "12:00:00"
          latest_end: "23:59:00"
          duration:
            hours: 3
            minutes: 0
        response_variable: resp
    sensor:
      - name: Highest energy price 2
        device_class: timestamp
        state: "{{ resp.start is defined and resp.start }}"

epex_spot_data_net_price:
state_class: measurement
data:
- start_time: '2023-12-21T23:00:00+00:00'
  end_time: '2023-12-22T00:00:00+00:00'
  price_ct_per_kwh: 15.542589999999999
- start_time: '2023-12-22T00:00:00+00:00'
  end_time: '2023-12-22T01:00:00+00:00'
  price_ct_per_kwh: 15.5295
- start_time: '2023-12-22T01:00:00+00:00'
  end_time: '2023-12-22T02:00:00+00:00'
  price_ct_per_kwh: 15.53307
- start_time: '2023-12-22T02:00:00+00:00'
  end_time: '2023-12-22T03:00:00+00:00'
  price_ct_per_kwh: 15.519979999999999
- start_time: '2023-12-22T03:00:00+00:00'
  end_time: '2023-12-22T04:00:00+00:00'
  price_ct_per_kwh: 15.51165
- start_time: '2023-12-22T04:00:00+00:00'
  end_time: '2023-12-22T05:00:00+00:00'
  price_ct_per_kwh: 15.531880000000001
- start_time: '2023-12-22T05:00:00+00:00'
  end_time: '2023-12-22T06:00:00+00:00'
  price_ct_per_kwh: 15.637789999999999
- start_time: '2023-12-22T06:00:00+00:00'
  end_time: '2023-12-22T07:00:00+00:00'
  price_ct_per_kwh: 19.311320000000002
- start_time: '2023-12-22T07:00:00+00:00'
  end_time: '2023-12-22T08:00:00+00:00'
  price_ct_per_kwh: 20.269270000000002
- start_time: '2023-12-22T08:00:00+00:00'
  end_time: '2023-12-22T09:00:00+00:00'
  price_ct_per_kwh: 19.78256
- start_time: '2023-12-22T09:00:00+00:00'
  end_time: '2023-12-22T10:00:00+00:00'
  price_ct_per_kwh: 18.68895
- start_time: '2023-12-22T10:00:00+00:00'
  end_time: '2023-12-22T11:00:00+00:00'
  price_ct_per_kwh: 18.66277
- start_time: '2023-12-22T11:00:00+00:00'
  end_time: '2023-12-22T12:00:00+00:00'
  price_ct_per_kwh: 18.722269999999998
- start_time: '2023-12-22T12:00:00+00:00'
  end_time: '2023-12-22T13:00:00+00:00'
  price_ct_per_kwh: 18.5521
- start_time: '2023-12-22T13:00:00+00:00'
  end_time: '2023-12-22T14:00:00+00:00'
  price_ct_per_kwh: 18.975740000000002
- start_time: '2023-12-22T14:00:00+00:00'
  end_time: '2023-12-22T15:00:00+00:00'
  price_ct_per_kwh: 19.60763
- start_time: '2023-12-22T15:00:00+00:00'
  end_time: '2023-12-22T16:00:00+00:00'
  price_ct_per_kwh: 20.58819
- start_time: '2023-12-22T16:00:00+00:00'
  end_time: '2023-12-22T17:00:00+00:00'
  price_ct_per_kwh: 20.652449999999998
- start_time: '2023-12-22T17:00:00+00:00'
  end_time: '2023-12-22T18:00:00+00:00'
  price_ct_per_kwh: 21.53424
- start_time: '2023-12-22T18:00:00+00:00'
  end_time: '2023-12-22T19:00:00+00:00'
  price_ct_per_kwh: 20.35971
- start_time: '2023-12-22T19:00:00+00:00'
  end_time: '2023-12-22T20:00:00+00:00'
  price_ct_per_kwh: 18.475939999999998
- start_time: '2023-12-22T20:00:00+00:00'
  end_time: '2023-12-22T21:00:00+00:00'
  price_ct_per_kwh: 18.579469999999997
- start_time: '2023-12-22T21:00:00+00:00'
  end_time: '2023-12-22T22:00:00+00:00'
  price_ct_per_kwh: 19.160189999999997
- start_time: '2023-12-22T22:00:00+00:00'
  end_time: '2023-12-22T23:00:00+00:00'
  price_ct_per_kwh: 16.9694
- start_time: '2023-12-22T23:00:00+00:00'
  end_time: '2023-12-23T00:00:00+00:00'
  price_ct_per_kwh: 15.546159999999999
- start_time: '2023-12-23T00:00:00+00:00'
  end_time: '2023-12-23T01:00:00+00:00'
  price_ct_per_kwh: 15.54021
- start_time: '2023-12-23T01:00:00+00:00'
  end_time: '2023-12-23T02:00:00+00:00'
  price_ct_per_kwh: 15.54021
- start_time: '2023-12-23T02:00:00+00:00'
  end_time: '2023-12-23T03:00:00+00:00'
  price_ct_per_kwh: 15.539019999999999
- start_time: '2023-12-23T03:00:00+00:00'
  end_time: '2023-12-23T04:00:00+00:00'
  price_ct_per_kwh: 15.54021
- start_time: '2023-12-23T04:00:00+00:00'
  end_time: '2023-12-23T05:00:00+00:00'
  price_ct_per_kwh: 15.5414
- start_time: '2023-12-23T05:00:00+00:00'
  end_time: '2023-12-23T06:00:00+00:00'
  price_ct_per_kwh: 15.5533
- start_time: '2023-12-23T06:00:00+00:00'
  end_time: '2023-12-23T07:00:00+00:00'
  price_ct_per_kwh: 16.42557
- start_time: '2023-12-23T07:00:00+00:00'
  end_time: '2023-12-23T08:00:00+00:00'
  price_ct_per_kwh: 17.9214
- start_time: '2023-12-23T08:00:00+00:00'
  end_time: '2023-12-23T09:00:00+00:00'
  price_ct_per_kwh: 20.54892
- start_time: '2023-12-23T09:00:00+00:00'
  end_time: '2023-12-23T10:00:00+00:00'
  price_ct_per_kwh: 20.49656
- start_time: '2023-12-23T10:00:00+00:00'
  end_time: '2023-12-23T11:00:00+00:00'
  price_ct_per_kwh: 21.0035
- start_time: '2023-12-23T11:00:00+00:00'
  end_time: '2023-12-23T12:00:00+00:00'
  price_ct_per_kwh: 21.177239999999998
- start_time: '2023-12-23T12:00:00+00:00'
  end_time: '2023-12-23T13:00:00+00:00'
  price_ct_per_kwh: 21.46879
- start_time: '2023-12-23T13:00:00+00:00'
  end_time: '2023-12-23T14:00:00+00:00'
  price_ct_per_kwh: 21.765099999999997
- start_time: '2023-12-23T14:00:00+00:00'
  end_time: '2023-12-23T15:00:00+00:00'
  price_ct_per_kwh: 21.94003
- start_time: '2023-12-23T15:00:00+00:00'
  end_time: '2023-12-23T16:00:00+00:00'
  price_ct_per_kwh: 22.449350000000003
- start_time: '2023-12-23T16:00:00+00:00'
  end_time: '2023-12-23T17:00:00+00:00'
  price_ct_per_kwh: 23.647679999999998
- start_time: '2023-12-23T17:00:00+00:00'
  end_time: '2023-12-23T18:00:00+00:00'
  price_ct_per_kwh: 23.44895
- start_time: '2023-12-23T18:00:00+00:00'
  end_time: '2023-12-23T19:00:00+00:00'
  price_ct_per_kwh: 22.86585
- start_time: '2023-12-23T19:00:00+00:00'
  end_time: '2023-12-23T20:00:00+00:00'
  price_ct_per_kwh: 21.9317
- start_time: '2023-12-23T20:00:00+00:00'
  end_time: '2023-12-23T21:00:00+00:00'
  price_ct_per_kwh: 20.48704
- start_time: '2023-12-23T21:00:00+00:00'
  end_time: '2023-12-23T22:00:00+00:00'
  price_ct_per_kwh: 17.95591
- start_time: '2023-12-23T22:00:00+00:00'
  end_time: '2023-12-23T23:00:00+00:00'
  price_ct_per_kwh: 16.46246

unit_of_measurement: ct/kWh
icon: mdi:currency-eur
friendly_name: Aktueller Strompreis

Now, my expectain is:
Lowest price in the future:
- start_time: '2023-12-23T02:00:00+00:00'
  end_time: '2023-12-23T03:00:00+00:00'
  price_ct_per_kwh: 15.539019999999999

-> OK

But the first highes Price shows me the time in the past:

Screenshot was made on 22.12 at 15:30
How can I achieve, that my Highest Price 1 will look in the future and will get 3h on 23th?
- start_time: '2023-12-23T09:00:00+00:00'
  end_time: '2023-12-23T10:00:00+00:00'
  price_ct_per_kwh: 20.49656
- start_time: '2023-12-23T10:00:00+00:00'
  end_time: '2023-12-23T11:00:00+00:00'
  price_ct_per_kwh: 21.0035
- start_time: '2023-12-23T11:00:00+00:00'
  end_time: '2023-12-23T12:00:00+00:00'
  price_ct_per_kwh: 21.177239999999998

Not sure if I fully understand your application, but here are some hints:

Don't call the service every 15 minutes, but only once per day. Otherwise you get different results right after midnight.
Set earliest_start_post to get results for tomorrow.

hours: "15" means at 15 o'clock each day, isn't it? 15, bacause we get new prices at 14 with a bit buffer.

Right.
Try:
earliest_start: "00:00:00"
earliest_start_post: 1
latest_end: "11:59:00"
latest_end_post: 1

This will give you values for tomorrow.

Thanks, not it works as expected!


Allow all origins, document endpoints, remove static serving

@zerolab I'm going to go ahead and merge this, hopefully uncontroversial enough! But we might want to support env-specified origins in the future.


Update MetadataTableUtil to use the ample api

From @keith-turner: Code in MetadataTableUtil should probably be restructured, but I am not sure what that structure should be; I thought about this a little bit and decided to keep Ample simple with just the primitive metadata ops for now since I did not have an overall design
There are still some big chunks of code that could be simplified by using Ample.. so I was thinking of working those first.  For now I Am thinking just make existing code use Ample
and consider a larger refactoring after that.

I will work on this.

Also removeUnusedWalEntries(..)


goreman: 0.3.11 -> 0.3.13

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

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

1 package built:

goreman

Result of nixpkgs-review pr 182954 run on aarch64-linux 1

1 package built:

goreman


[EUWE] Cloud Network UI: Task queue, validation, buttons and translation

https://bugzilla.redhat.com/show_bug.cgi?id=1394281
This is an Euwe-only PR to resolve conflicts with:
app/controllers/cloud_network_controller.rb
app/models/manageiq/providers/openstack/network_manager.rb

This PR is equivalent to https://github.com/ManageIQ/manageiq/pull/12071
on master.

@miq-bot add_label bug
@miq-bot add_label blocker

@miq-bot add_label euwe/yes

@martinpovolny @gildub is this good to go?

@simaishi, This good to go! Thanks


Report inconsistency in the command JSON.SET

This issue is all about ensuring we are as close to Redis as possible. The command in focus for this issue is JSON.SET.
Go through the official documentation of the command JSON.SET on Redis and identify the inconsistencies. The inconsistencies could be in

unhandled edge case
unexpected behavior
unsupported option

Because we are trying to be compatible with Redis v7.2.5, I would recommend you try out different variants of the command with different inputs on that specific version. The instructions on running Redis v7.2.5 locally

from source code
use Docker

Once you find the discrepancy, you can either

raise an issue on Dice repository with details, or
try to fix it yourself and raise a PR

If you are raising the issue, make sure you provide the details such as

use the template and provide the following details
steps to reproduce (series of commands)
observed output on DiceDB
observed output on Redis v7.2.5

Also, feel free to update the documentation and raise the PR in the docs repository.

You will need to go deeper into the command make sure you are covering all cases and reporting the inconsistencies or fixing them. The deeper the work, the better our stability will be. Also, it is possible that we do not find any discrepancies, so please mention the same in the comment on this issue. Mention the PR or issue links that you create under this issue.

@arpitbbhayani can i take this up?

@kushal0511-not go for it :)

We have some inconsistency in command due to  how we treat JSONPath in JSON.SET command.
here are few examples.
1 )
dice :

Redis 7.2.5 :

2 )
dice :

Redis 7.2.5 :

cc @JyotinderSingh

I have tried other libraries for jsonpath, but the current library which we are using is the  closest to redis(7.2.5) jsonpath.
As we have inconsistency with the redis (like this library parse some json paths differently than redis 7.2.5) , what should be the next steps for this issue.
Should we fork this library and make changes to it
OR
Should we create our own from scratch.
@JyotinderSingh @soumya-codes

I have tried other libraries for jsonpath, but the current library which we are using is the  closest to redis(7.2.5) jsonpath.
As we have inconsistency with the redis (like this library parse some json paths differently than redis 7.2.5) , what should be the next steps for this issue.
This will affect  almost all JSON related commands.
Should we fork this library and make changes to it
OR
Should we create our own from scratch.
@JyotinderSingh @soumya-codes

Thanks for looking into this @kushal0511-not, let's keep this issue open for now, we can look into fixing it at a later stage.
The partial support for the syntax is enough for the existing use cases.

Hi, I have found another inconsistency for JSON.SET when we try to create a string at the root path.
dice:

redis:

I am working on JSON.STRLEN and found this deviation. Since this is an open issue, I feel reporting it here is better than raising another issue.
Regards,
Apoorv

Hello @kushal0511-not,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hi @arpitbbhayani , i have described root cause and discussed with @JyotinderSingh also in previous comments.

Hello @kushal0511-not,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hello @kushal0511-not,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.

Hi, I have been working on documentation for JSON.SET commands and have found many inconsistencies with it. This issue seems like a parent issue for the documentation. I will not be raising another issue.
Dependent issue: #795

Hello @kushal0511-not,
There has been no activity on this issue for the past 5 days.
It would be awesome if you keep posting updates to this issue so that we know you are actively working on it.
We are really eager to close this issue at the earliest, hence if we continue to see the inactivity, we will have to reassign the issue to someone else. We are doing this to ensure that the project maintains its momentum and others are not blocked on this work.
Just drop a comment with the current status of the work or share any issues you are facing. We can always chip in to help you out.
Thanks again.


Freezing

Hello Bradley,
Thanks for sharing your work,
I have ordered 5x of this card and it is not so easy to find the memory chip,
I replaced them by 2x AS7C164A-15PCN: SRAM SRAM SRAM, 64K, 8k x 8, 5v, 28pin Skinny P-DIP, 15ns
The pin setup seems to be the same,
However the card is not working and freezing when it tries to use the additional 16K.
How can I investigate what is wrong, do you have an idea.
Thanks
Vincent

Hello Bradley, Thanks for sharing your work,
I have ordered 5x of this card and it is not so easy to find the memory chip, I replaced them by 2x AS7C164A-15PCN: SRAM SRAM SRAM, 64K, 8k x 8, 5v, 28pin Skinny P-DIP, 15ns
The pin setup seems to be the same,
However the card is not working and freezing when it tries to use the additional 16K.
How can I investigate what is wrong, do you have an idea.
Thanks
Vincent

I also built some boards for my Apple IIs and I'm having exactly the same problem:  freezing when I try to access the other 16KB of the board in ProDOS, for example. I'm using Cy7C185 on my boards. Have you made any progress in the tests?

Hello,
When I changed the Rom to a single rom chip (27C16) if I am not wrong it started working. I suspect that the legacy roms at too slow
V
From: amazingcobrazil @.>
Reply to: btb/LanguageCard @.>
Date: Friday 16 August 2024 at 00:06
To: btb/LanguageCard @.>
Cc: Vincent BESSON @.>, Author @.***>
Subject: Re: [btb/LanguageCard] Freezing (Issue #2)
Hello Bradley, Thanks for sharing your work,
I have ordered 5x of this card and it is not so easy to find the memory chip, I replaced them by 2x AS7C164A-15PCN: SRAM SRAM SRAM, 64K, 8k x 8, 5v, 28pin Skinny P-DIP, 15ns
The pin setup seems to be the same,
However the card is not working and freezing when it tries to use the additional 16K.
How can I investigate what is wrong, do you have an idea.
Thanks
Vincent
I also built some boards for my Apple IIs and I'm having exactly the same problem: freezing when I try to access the other 16KB of the board in ProDOS, for example. I'm using Cy7C185 on my boards. Have you made any progress in the tests?
—
Reply to this email directly, view it on GitHubhttps://github.com/btb/LanguageCard/issues/2#issuecomment-2292354358, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A4ZT7FMRD4JSO7TEPCT4WTTZRUQ5PAVCNFSM6AAAAABMS7I3IGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJSGM2TIMZVHA.
You are receiving this because you authored the thread.Message ID: @.***>

I still have the issue, I will try with old narrow SRAM to see if it change something of not

I change the SRAM by TC5588 and Cy7C185, it does not help, there is something else not working
Vincent

Based on all the test I have made this card is working without any issue 👍

My Apple II ws having a bad DRAM chip causing freeze and data corruption,
If you struggle to find SRAM for this card, you can use AS7C164A-15PCN it is working like a charm

I think we can close this issue

I'm glad to hear it. My apologies that I didn't get around to helping you with this


Train without --masks flag

Hi,
I tried to train a model without --masks on the default Youtube VIS dataset. I used all parameters as default except for decreasing the num_frames to 18 and num_queries to 180 correspondingly to fit my GPUs. But the loss curves show no model optimization gains as beblow

Thus, I wonder if you have tested training model without --masks flag (namely, box tracking instead of mask tracking) on any datasets? Is the current VisTR class usable (not VisTRsegm)?
thanks!

Hello.I want to ask about that how did you find the dataset annotation file. I counldn't find the corresponding file instance_train_sub.json' or 'instance__val_sub.json' in the Codalab page(https://competitions.codalab.org/competitions/20128#participate-get_data). I only download the image data.But, for annotation file, I just got the test.json or val.json or train.json file. And in those json file, I couldn't fine the annotation information.　Is the website where I downloaded the data set wrong?

Hi @StiphyJay, just use the train.json and val.json file of the 2019 version.

Hi @noahcao I have not tried that.

Hello, please can you help? There is no annotation is the valid.json on the website? How did you evaluate on valid split?
https://competitions.codalab.org/competitions/20128#participate-get_data

@noureldien Please refer to Models section in README.

@noahcao Hi, would you were able to do box tracking?
Kind Regards


Directory flag specifies maxdepth 1

Today, pulling protofiles using the -d flag specifies a max-depth of 1.
https://github.com/namely/docker-protoc/blob/93b2381b888c691e2f4b3c0aac010f551cf361c2/all/entrypoint.sh#L174
Is there a specific reason for this? Can it be configurable?
We have a directory structure that looks like this:
src/main/proto/company_pb
├── billing
│   └── events.proto
├── commons
│   ├── sqs
│   │   ├── sqs_attribute.proto
│   │   ├── sqs_attributes.proto
│   │   └── sqs_message.proto
│   └── timestamp.proto

So the maxdepth flag causes the command to fail out with this error
Missing input file.

because no files are passed to the underlying method.

I just tried it out locally by just removing the -maxdepth option and things worked swimmingly for me! I'm happy to do a PR to this project.
The biggest question I have is whether or not we need to maintain the old behavior by default, or if we're comfortable just removing the maxdepth option. I'm open to doing it either way. Thoughts?

Submit a PR and I can test- should be okay.
On Thu, Apr 19, 2018 at 3:48 PM Ben Limmer<EMAIL_ADDRESS>wrote:

I just tried it out locally by just removing the -maxdepth option and
things worked swimmingly for me! I'm happy to do a PR to this project.
The biggest question I have is whether or not we need to maintain the old
behavior by default, or if we're comfortable just removing the maxdepth
option. I'm open to doing it either way. Thoughts?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/namely/docker-protoc/issues/61#issuecomment-382859081,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFkGgmFK4OqyqHh_bFXmjW77LKepm9bks5tqOoggaJpZM4TcEjv
.

If you like me in 2020+ don't understand why code with blocking max-depth come back - read https://github.com/namely/docker-protoc/pull/112


Chore/return published message reference

Type:

~cicd: helm, docker & cicd adjustments.~
feature: new capabilities.
~fix: bug, hotfix, etc.~
~refactor: enhacements.~
other: docs, tests.

What's the focus of this PR:
Since the possibility to publish scheduled messages is available. We also need now to be able to cancel scheduled messages that has not been consumed yet.
Task list:
:cyclone: Components

[x] cancelScheduledMessages new method available

:heavy_check_mark: Test

[x] Canceled messages should not be consumed.

👍


chore(deps): bump go-kong

Codecov Report

Merging #483 (0d4e0fb) into main (3d06cc2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #483   +/-   ##
=======================================
  Coverage   50.44%   50.44%
=======================================
  Files          72       72
  Lines        7835     7835
=======================================
  Hits         3952     3952
  Misses       3534     3534
  Partials      349      349

Continue to review full report at Codecov.

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


Implemented json_pack() format specifiers 's?', 'o?', and 'O?'.

Hello,
I have implemented the format specifiers discussed in issue #261.

Otherwise looks good!

Merged, thanks!


Facial Recognition in photo albums

A cool idea for (probably) the new backend would be the ability to filter photos by your own face. For example, there could be a section on the account page that shows a link to view all photos you're in.
A library that could be used is ageitgey/face_recognition. You'd ofc. get the best performance with a GPU that supports CUDA, but should be doable on a CPU due to the limited number of images and interval at which new photos are uploaded.
It doesn't seem too advanced, and probably consists of two parts:

User must have a profile picture set in their IA account

User uploads image
Detect face
Store face data (e.g. in a db table, https://github.com/ageitgey/face_recognition/issues/43)

Albums should get analyzed before being shown on the website

New photos get uploaded
The faces in a photo are matched against the db
We store the ids of the users in the picture in the Amelie db (don't know its structure)

This facial recognition stuff should probably be run outside of the Amelie backend service as a microservice or smth. Another way would be to simply match the folder with all IA profile pictures against the newly uploaded album, but you'd be re-analysing profile pictures every time (which gets more expensive with every new user). We'll have to see what the reliability of this recognition is on the photos uploaded.
Will affect our Privacy Statement.

I'm not part of the WWW committee, but I'd be willing to implement this even in the current Amelie version.

@pietervanheijningen

This is not going to be implemented, because we are not allowed to process the pictures in that way according to our privacy policy.


CMake on Mac

Installation instruction mentioned the following, "One important difference about CMake on Mac versus Windows is that there is no GUI application....".
However, there is a UI interface for CMake on Mac found here: https://cmake.org/download/

Does the mac also support something like cmake-gui terminal just like in linux? If that's the case, no need to download anything additionally.  Will update the doc.

Are you referring to the cmake-gui terminal as running cmake commands on the mac terminal ? If so, your instructions that specify running this command "ccmake ." on the terminal works on my mac. The following set of instructions on how to compile it from the terminal through cmake is clear and can be followed through your installation instruction. So long answer short, yes, mac support cmake-gui terminal.


Always replace ANCM in xdt transform.

Fixes https://github.com/aspnet/AspNetCore/issues/7307
Verified this worked too.

@jkotalik Late to the party here, but is this already available in Antares?

Yep!


Accepted Features

This bug tracks the accepted features for the language and libraries.
These are tentatively accepted features. This list is bound to change based on implementation complexities, new feedback, or unexpected corner-cases and interactions.

[ ] Read-only access to initializing formals https://github.com/dart-lang/sdk/issues/26655
[ ] &&= and ||=: https://github.com/dart-lang/sdk/issues/26996
[ ] Assert accepts message. https://github.com/dart-lang/sdk/issues/24213
[ ] Type instance is checks: o is expr. https://github.com/dart-lang/sdk/issues/27680
[ ] resolved part-of. https://github.com/dart-lang/sdk/issues/20792, https://github.com/dart-lang/dart_enhancement_proposals/issues/45
[x] allow incomplete unicode surrogate pairs in string literals. For example "\ud8xx". https://github.com/dart-lang/sdk/issues/26620
[ ] Take advantage of negative is-checks for type propagation. Work with dart2js and Analyzer teams to get proposal.
[ ] asserts should allow assignment expressions: assert(x = true). Most implementations already did this.
[ ] Optional new (see https://gist.github.com/floitschG/0a79d90c7824f3d540163b6ce7623236#file-optional_new-md)

[ ] const context https://github.com/dart-lang/sdk/issues/4046
[ ] constructor tear-offs

[ ] positional and named optional parameters for the same function. https://github.com/dart-lang/dart_enhancement_proposals/issues/26 - next is requesting feedback from implementors.

@floitschG, are you still using this issue to track anything? If not, want to close it?

It is still used.

Closing this because we aren't using this issue to track language work anymore.


Restoring downstream kubernetes cluster

https://github.com/rancher/rancher/issues/17867

@galal-hussein I want to think more about this and where this information should go. Since it's about managing the user clusters (not the cluster running Rancher, I'm not sure where you've put it is the best place). I'll let you know where I think it should go when I've figured out where.

@galal-hussein can you update this PR?

Merging as is as @superseb is going to fix it up and move it to the correct location


Add documentation for updating the kit using the latest release branch

Travis will now keep a branch called "latest-release" up-to-date.
This relates to #259.
This branch should make it easier for users to update older versions of the kit.
We should add documentation for updating older versions to use the latest release.

This was fixed by #271. Thanks @paulmsmith!


Feature Enhancement : QR Generator

Is your feature request related to a problem? Please describe.
The basic QR generator lacks advanced customization and features, limiting its usability and visual appeal.
Describe the solution you'd like
I'd like the QR generator to be enhanced with the following features:

Improved UI:

Allow users to change QR code colors.
Provide options for different QR code shapes (rounded corners, dots, etc.).
Let users add a logo or image to the center of the QR code.

Advanced Features:

Implement error correction level selection (L, M, Q, H).
Add support for generating different types of QR codes (URL, text, WiFi, vCard, etc.).
Include a QR code scanner feature to read and decode QR codes.

Describe alternatives you've considered
An alternative could be using third-party QR code generators, but they often lack the level of customization and advanced features needed for specific use cases.
Additional context
These enhancements will make the QR generator more versatile and user-friendly, catering to a broader audience with diverse needs. Below are some screenshots illustrating the desired features and UI improvements:
Before

This is my final Vsoc24 issue, and it was a pleasure to contribute to your repository.

This is my final Vsoc24 issue, and it was a pleasure to contribute to your repository.

This is my final Vsoc24 issue, and it was a pleasure to contribute to your repository. 🙌

thanku for your contributions @atharva012004


Microsoft Dynamics Lifecycle Services

Proposed name of the new command
lcs.cmd.ms
Description
Microsoft Dynamics Lifecycle Services
Category
Dynamics, D365FO
Url
https://lcs.dynamics.com/v2

Accepted


Improve the UI

Make the UI more beautiful and functional.

@jaibhedia please assign this issue to me I would like to work on it.

@jaibhedia I have made pull request please review it #2 if any changes required please update me.

@NandishM0618 Sure, will review the PR and let you know if any changes are required.

@jaibhedia I have resolved the loading issue please review it #5


Refactor to rearrange logical unit of code into appropriate layers after Workflow route refactoring

Closed by PR #864


"Ctrl+["=Leave insert mode in vi

I came from the redox-os project which uses liner in ion, and I tried to run set -o vi and found this.
Im working on this thing, I forked it and I think I fixed it: :crossed_fingers: . You probably should check my work because I have no idea how this project works.
My fork is here: https://github.com/liamnaddell/liner
Should I pr?
I also "added" two more tests that use ctrl+[ instead of Esc

Go ahead and submit a PR. I left a comment on one of your commits. The maintainer for this project seems to be AWOL at the moment, so I'm not sure this will get merged but go ahead and submit it anyway.

Pr is at https://github.com/MovingtoMars/liner/pull/88

@liamnaddell You might want to close this issue, in order to make it #94 more visible.

Closed


multi_cached function  got multiple values error

python: 3.6.0
aiocache: 0.7.2
    @multi_cached('ids', ttl=10)
    async def get_async(ids):
        return {1: '1', 2: '2'}
    res = await get_async([1, 2])

File "\Python36-32\lib\site-packages\aiocache\decorators.py", line 250, in decorator
result = await f(*new_args, **kwargs)
TypeError: get_async() got multiple values for argument 'ids'
Same as this issue:
https://github.com/argaen/aiocache/issues/270

I'm able to reproduce. Will have a look, thanks for reporting


Works just fine the first time around, SIGABRT for any subsequent launch attempts

I'll be reinstalling it soon after posting. Trying to launch with Steam shows the "Launching Duck Game..." window for a split second followed by nothing.

After having reinstalled a second time, the game just straight up doesn't work anymore. :(


wget: Command not found

I'm trying to train SimCSE in a virtual environment (w/ python 3.7.0) I tried to run the download_wiki.sh file, but I got an error message saying "/Users/davidsun/Downloads/SimCSE/data/download_wiki.sh: line 1: wget: command not found" This error persisted even after I installed wget using pip. What should I do?

wget is a Linux command, you may use “sudo apt-get install wget” （for ubuntu and debian）or "sudo yum -y install wget" (for centos) to install wget for your operation system

I'm sorry, but I don't have access to a Linux computer where I have sudo permissions. Can this repo be run on a non-Linux OS?

Actually, you can just download the wiki dataset by yourself, instead of using wget command. if you don't have linux os, i recommend you to use colab to run the repo, google offers you an simple Linux-os platform and some free gpu computational resources. Hope that will work :)

Hi,
This repo is only tested in a linux environment and it seems that you are using a Mac environment. The downloading command can be executed manually (see download_wiki.sh for the dataset link).


Prolonged register outage can cause unnecessary downtime due to cache expiry

The dependency graph specifies that the maxAge for the data holder brands cache is 4 hours.
https://github.com/Regional-Australia-Bank/ADR-Gateway/blob/717e9a75c1bf010685eb062e63d8c1afb2b3e2da/src/Common/Connectivity/Dependencies.yml#L87
If there is an outage at the register after the cache expires, then subsequent requests /cdr/data-holders will fail in turn. This would have the effect of blocking new consents being established, and this would be a kind of customer impact that appears unnecessary due to the nature of a 500 internal server error, for instance.
The outage itself could be addressed by:

lifting maxAge to a value beyond any expected downtime
removing maxAge - this will entail other design challenges such as how changes will propagate at all
implement some new softFailWithCache mechanism so that we can operate on the expired cache

Moving to a "no fail" or "soft fail" mechanism may run the risk that the failure goes undetected indefinitely which would fail to meet the requirement that changes must eventually propagate. It seems best for the ecosystem as a whole to allow eventual failure here, but to:

acknowledge the possibility for downtime due to various causes
clarify if there are any requirements for data recipients to cease communication with data holders after cache expiry (there do not appear to be any in the standards)
seek DSB guidance for a reasonable recommended cache expiry that accounts for the range of possible duration of outages or critical defects


Refactor two calls loss_batch(..) and grad_loss_batch(..) into a sing…

Changing training loop to use jax.value_and_grad(..). This removes a forward pass from the training loop => 5s faster execution on CPU.
Running python main.py before change:
dummy-bJxS6eyFjtsBr94T3kexFk loss 3.2920437 sample ell-apparell'd April on the heel
WARNING:timer.sample:start
3.2920437 Au|  e  e  e  e e  e  e
WARNING:timer.sample:cost 807 ms
TIME: 50.904489278793335

Running python main.py after change.
dummy-UdYk93YwDmF6bfSecce4Cn loss 3.2920437 sample ks be sour.\n\nSIR STEPHEN SCROOP:
WARNING:timer.sample:start
3.2920437 Au|  e  e  e  e e  e  e
WARNING:timer.sample:cost 858 ms
TIME: 45.6448495388031

OBS:
Chose not to delete the following two lines as they are used other places where we only need grad.
grad_loss_batch_unjit = jax.grad(loss_batch, argnums=1)
grad_loss_batch = jax.jit(grad_loss_batch_unjit, static_argnums=0)

Much nicer, thanks!


Latex error \footref already defined

Just found this error popping up on a system that was previously working fine:
stderr: Error producing PDF.
! LaTeX Error: Command \footref already defined.
Or name \end... illegal, see p.192 of the manual.
See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
...
l.6172 }
The file being converted is just a basic test markdown file, and calling on pandoc (v 2.9) to convert using the eisvogel template:
pandoc test.md --pdf-engine=xelatex --from markdown --template=eisvogel -o test.pdf
(Windows 10 OS, Pandoc 2.9, Miktex)
Any thoughts?

I ran into the same issue (Linux, pdfTeX 3.141592653-2.6-1.40.23 (TeX Live 2021/Arch Linux), pandoc <IP_ADDRESS>).
Without having a deep understanding on how to properly fix this, I was able to get it to work with the help of https://komascript.de/release3.32 (known issues).
Try to add \let\footref\relax before \documentclass[ ... in the template file eisvogel.latex


theano.clone feature

Are there some plans to do extension like a theano.clone ?
Description from a original API:
theano.clone(output, replace=None, strict=True, share_inputs=True)
Function that allows replacing subgraphs of a computational graph.
It returns a copy of the initial subgraph with the corresponding substitutions.
Parameters:

output (Theano Variables (or Theano expressions)) – Theano expression that represents the computational graph.

replace (dict) – Dictionary describing which subgraphs should be replaced by what.

share_inputs (bool) – If True, use the same inputs (and shared variables) as the original graph. If False, clone them. Note that cloned shared variables still use the same underlying storage, so they will always have the same value.

It would be great if we can do similar things in tensorflow with easy.

Closing since this seems to be fixed with pull request #557.


REDDEV-510 Refactor to add form for adding counts

Refactored to support a form for adding report counts.
settings.php no longer persists sample configuration if not present.
Extracted ReportSummaryForm component.
Default view is an empty page with "Create a Report" button. Clicking
the button opens a form for entering a title and a report. Upon save the
report configuration is saved by settings.php. Either saves new
configuration to the database, or appends to the existing config.
Currently the form remains on the screen and multiple summaries can be
added.
Removed sample report config and updated documentation and tests.

@kirenotneb , @lawhead , this PR contains all of the refactor to add a form to create report summaries (a node of the report with a total count)
Since it's a bit large I also broke this work up into separate branches and created 4 pull requests. If you take a look at the pull requests you'll see four additional PRs. The title is prefixed with a number to represent the order. If you prefer to review in steps we can close this one and review the 4 PRs separately. Preference?

Here are some screenshots.

I can sympathize that we want to keep PRs very specific. But when you are adding a significant piece of functionality it may be hard to break it up into small focused PRs. I think my preference would be to have a single branch with multiple commits of each aspect. So in this case you would have 1 PR with 4 commits associated with it.