Release not found

I'm having an issue getting Flux to read Helm charts from a private GitHub repository and apply changes to the cluster. I have Flux and the Helm Operator installed. I've created the deployment key, and Flux can read/write my repository.  My chart is custom, and contains 15 subcharts. Below is my HelmRelease:
---
apiVersion: flux.weave.works/v1beta1
kind: HelmRelease
metadata:
  name: sellout
  namespace: default
  annotations:
    flux.weave.works/automated: "true"
spec:
  releaseName: sellout
  chart:
    git: git@github.com:sellout-tickets/SelloutOps
    ref: master
    path: charts/sellout
    values:
      global:
        # Image Config
        webAdminImageTag: 8adaff1
        webCheckoutImageTag: a9ed95d
        platformImageTag: a9ed95d
        # Environment Variables
        API_URL: https://graphql.sellout.cool
        ADMIN_UI_BASE_URL: https://app.sellout.cool
        # TLS Config
        tls:
          email<EMAIL_ADDRESS>          domains:
            admin: app.sellout.cool
            embed: embed.sellout.cool
            graphql: graphql.sellout.cool

Flux installs the sample applications just fine, but fails when trying to install the sellout chart. Below is the result of kubectl describe hr sellout:
Name:         sellout
Namespace:    default
Labels:       flux.weave.works/sync-gc-mark=sha256.jBy-XI76GHQT5sRtG08Tl4fMWyvooi-dMvBx3gFYstQ
Annotations:  flux.weave.works/automated: true
              flux.weave.works/sync-checksum: 4e62357b5df01e18f3afb71c10e7271e5567ab51
              kubectl.kubernetes.io/last-applied-configuration:
                {"apiVersion":"flux.weave.works/v1beta1","kind":"HelmRelease","metadata":{"annotations":{"flux.weave.works/automated":"true","flux.weave.w...
API Version:  flux.weave.works/v1beta1
Kind:         HelmRelease
Metadata:
  Creation Timestamp:  2019-05-16T21:37:17Z
  Generation:          2
  Resource Version:    1685696
  Self Link:           /apis/flux.weave.works/v1beta1/namespaces/default/helmreleases/sellout
  UID:                 c6ecaad4-7822-11e9-b232-42010a800051
Spec:
  Chart:
    Git:   git@github.com:sellout-tickets/SelloutOps
    Path:  charts/sellout/
    Ref:   master
    Values:
      Global:
        ADMIN UI BASE URL:   https://app.sellout.cool
        API URL:             https://graphql.sellout.cool
        Platform Image Tag:  a9ed95d
        Tls:
          Domains:
            Admin:               app.sellout.cool
            Embed:               embed.sellout.cool
            Graphql:             graphql.sellout.cool
          Email<EMAIL_ADDRESS>        Web Admin Image Tag:     8adaff1
        Web Checkout Image Tag:  a9ed95d
  Release Name:                  sellout
Status:
  Conditions:
    Last Transition Time:  2019-05-16T21:37:41Z
    Message:               successfully cloned git repo
    Reason:                GitRepoCloned
    Status:                True
    Type:                  ChartFetched
    Last Transition Time:  2019-05-16T21:37:41Z
    Message:               rpc error: code = Unknown desc = release: "sellout" not found
    Reason:                HelmInstallFailed
    Status:                False
    Type:                  Released
  Release Name:
  Release Status:
Events:
  Type    Reason       Age              From           Message
  ----    ------       ----             ----           -------
  Normal  ChartSynced  1s (x3 over 9s)  helm-operator  Chart managed by HelmRelease processed

I've been fighting with this all day. Any help is greatly appreciated.

Can you share the logs from the Helm operator from around the time it runs into the installation error?

@samheutmaker Did you resolve this? Otherwise, can you share the logs?
If it's still a problem, could you join the #flux Slack channel channel so that we can pin-point it?

@samheutmaker closing this to get it of our radar, if the problem surfaces again feel free to reopen the issue (or join #flux on Slack as mentioned above).

I had the same issue. The problem was that my chart definition was bad (there was an undefined variable in it, due to which flux-helm-operator logs showed a Chart release failed error). Fixing the chart definition solved the issue.

Can confirm what @johncf said: the error is due to an user error:
kubectl -n tiller logs -f deployments/tiller-deploy

In my case I was having a failure caused by a wrongly typed value. IMHO flux should show a more user-friendly error than rpc error: code = Unknown desc = release: "RELEASE_NAME" not found.
I sugges something along the lines of Deploy failed - Check Tiller logs


Containers should have prepend / append_reversed methods (as well as push_front/back)

Now added and tested.


[DO NOT DEPLOY] Try Dependabot

I would like to try using Dependabot with a frontend repo, as we have been having issues with PyUp recently. This PR is an experiment, I expect that it will either be superseded or reverted at a later date.
This PR adds a Dependabot config file that I think should cause Dependabot to update requirements in requirements.txt weekly. Unfortunately the configuration for Dependabot doesn't seem to be as flexible as PyUp's. I can't see a way to specify filenames using the Dependabot config file format; there might be a way to do so in the GUI, I'm not sure.
On the plus side for Dependabot, we could use it to manage both Python and JavaScript dependencies. Also, Dependabot claims that its Python features include being able to manage Git sources (not sure how).

What do we expect the resulting workflow to be when a PR is raised? I'm assuming a dev would have to manually add to requirements-app and refreeze?

What do we expect the resulting workflow to be when a PR is raised? I'm assuming a dev would have to manually add to requirements-app and refreeze?

I think so, yeah. I'm not sure though, the dependabot docs are pretty sparse. One thing that's interesting is that if we were using pip-tools then Dependabot supposedly would pick that up and work with that; I wonder if changing the names/layout of our requirement files to look like they were generated with pip-compile would make Dependabot do the freezing for us?

I wonder if changing the names/layout of our requirement files to look like they were generated with pip-compile (i.e. name it requirements.in like this blog post mentions) would make Dependabot do the freezing for us?

Looking at the dependabot-core source code it seems that Dependabot uses pip-compile if it detects a requirements.in file, so the above suggestion is probably a bad one.

How annoying would it be for us to swap our filenames? So that requirements.txt becomes requirements-app.txt and vice-versa? That would give us the equivalent of the PyUp PR, wouldn't it?

How annoying would it be for us to swap our filenames? So that requirements.txt becomes requirements-app.txt and vice-versa? That would give us the equivalent of the PyUp PR, wouldn't it?

That might work 🤔 Although I'm reading the source code for Dependabot trying to figure out what it does exactly and I'm starting to worry that actually it looks at all *.txt files...

Okay, so my theory on reading the code is that the config in this PR will cause Dependabot to update both requirements-app.txt and requirements.txt. I've update the comment in the config to reflect this. We could get around this if we changed the file extension of requirements-app.txt (i.e. to something like requirements-app.lst, or just requirements-app). We as developers would  then have to freeze requirements manually for Dependabot PRs, like we do for PyUp PRs.
Alternatively, it might be okay to let Dependabot update both files, depending on whether/how Dependabot looks at version conflicts. I will keep researching.

After a lot of reading, it looks like Dependabot doesn't do conflict resolution of its own (which is the reason why we do make freeze.

I think this would work better if we were using pip-tools; I've put up a PR that implements that if anyone is interested #207


when add route after service，konga  reporter an error like this “Submission failed. schema violation (https_redirect_status_code: unknown field)”,even set default value 426, What could be the problem?

@qiyuxin we were having this issue, but then noticed this in the readme:

When a plugin property is an array, the input is handled by a chip component. You will need to press enter after every value you type in so that the component assigns it to an array index. See issue #48 for reference.

After typing a host, we need to press enter/return to convert the textual entry to a "chip". We were then able to create routes.

@qiyuxin , that is a field introduced in Kong 1.3, if your Kong version is lower than that, you can either update your Kong installation or use an older version of Konga. I would suggest that you upgrade Kong.

@pantsel  as you said ,it is a field in kong1.3, but now I use kong1.1.2 and konga  the latest version on  dcos platform，if i degrade konga version , Which version do you recommend downgrading to?

@pantsel  I upgrade kong to latest version and this problem solved, thank you~

@qiyuxin I have the same problem with konga latest verison and kong 1.0.3
I saw you mentioned you had already updated your kong to 1.3, however I could not install kong 1.3 in k8s, can you share me some scripts?
Thanks a lot.


Fix rendering html tag in markdown

Source Markdown
(I add one space on end of javascript code block(const clause) because without space it rendered as valid code block, so breaks rendering result)
# Some blog title

Just need to show you some code first:

```js
const foo = "bar"
`` `

 this is root red text

* list 1
* list 2
* list blue text
* list 3
   * two depth green text

<Row>
  <Col>Need to tell you something over here</Col>
  <Col>And over here</Col>
</Row>

Before this pr

After this pr

@sjstyle Hi there and so sorry for my late reply! I have been in paternity leave and just got back to work with way too much to do :)
A couple of comments:

The package.json entry has to be lib/index.js... or else it will load up babel-transpiler, the components thing is opt-in

Would you mind writing a test to ensure this works? :)

If not I will look into this later!


waybar displaying wrong timezone

timedatectl outputs the following:
               Local time: Sun 2024-03-17 20:16:08 EDT
           Universal time: Mon 2024-03-18 00:16:08 UTC
                 RTC time: Mon 2024-03-18 00:16:09

System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

However, after the new update, waybar is now saying it is currently midnight.

Don't know if you have a timezone set in your config file, but maybe try to first set your time zone with timedatectl because it looks like your output isn't reporting any.

it is set, I just removed it for privacy, should've said that
also, it worked perfectly before the most recent update. I currently have the timezone force set in waybar as a workaround, but I don't think I should have to set the timezone.

I'd like to chime in an say that I'm also facing this issue. It was working perfectly up until the update and now it only displays UTC instead of my timezone.

Same here, clock displays UTC instead of my local timezone.

same, waybar-clock displays hwclock (utc by default but responds to time/date changes in uefi)

same, waybar-clock displays hwclock (utc by default but responds to time/date changes in uefi)

I didn't know that.
But I have my hwclock synced with my OS clock anyway, both are set to my local timezone.

this is not correct, my hwclock is not displaying UTC and waybar still does not display the correct timezone unless manually set.

I have the opposite challenge using Waybar v.0.9.9 on Ubuntu 22.04.  I only see my timezone's time when I want to see UTC.
I have tried the following timezone settings:

"timezone": "UTC"
"timezone": "Universal"
"timezone": "GMT"
"timezone": "UCT"

Try updating to v0.10

Issue still remains with Waybar v0.10.2. Workaround is manually set the timezone in ~/.config/waybar/config:
    "clock#date": {
        "timezone": "America/Argentina/Buenos_Aires",
        "format": "{:%A %b %d}",
        "format-alt": "{:%Y-%m-%d}",
        "tooltip-format": "<big>{:%Y %B}</big>\n<tt>{calendar}</tt>",
        "interval": 60
    },
    "clock#time": {
        "timezone": "America/Argentina/Buenos_Aires",
        "format": "{:%H:%M:%S}",
        "interval": 1
    },

Yup, this should be marked as a regression IMO.

This issue still persists with 10.4-2

Even with "timezone": "Europe/Amsterdam", I still only see UTC, and not UTC+2.
On waybar 0.10.4-2 (Arch).

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo.
Masked 2024b until fixed.

I'm currently facing the same issue:

Although I'd swear this behavior wasn't there last week and the time displayed my timezone, I'm not sure. Maybe this bug only appears when certain time conditions are met? This issue had been silent for months, but today there are three reports of it. I'll post updates if it resolves itself without any specific updates addressing the issue.

Mine is not working either, the debug log is saying : [2024-09-08 17:55:58.688] [warning] Timezone: Asia/Dhaka. std::chrono::tzdb: cannot locate zone: Asia/Dhaka

I am also facing the same problem. Waybar clock is using Universal time instead of my local time

Same issue here:
Waybar v0.10.4
i tried following configs
"timezone": "Europe/Vienna"
"timezone": "Europe/Vienna (CEST, +0200)"
and i also tried to reconfigure hwclock
no success
timedatectl                 Local time: Sun 2024-09-08 15:47:00 CEST            Universal time: Sun 2024-09-08 13:47:00 UTC                  RTC time: Sun 2024-09-08 13:47:00                 Time zone: Europe/Vienna (CEST, +0200) System clock synchronized: yes               NTP service: active           RTC in local TZ: no

i remember waybar showing the correct time some weeks ago

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo. Masked 2024b until fixed.

I have the same issue on Arch Linux, and I can confirm that downgrading the package tzdata from 2024b-1 to 2024a-2 fixes the problem. I suggest this as a temporary workaround for now.

Here's the changelog from 2024a to 2024b. It seems that something changed in the naming of the timezones, as in the changelog it says

System V names are now obsolescent.
The main data form now uses %z.

Maybe this is useful to debug the issue?

Mine is not working either, the debug log is saying : [2024-09-08 17:55:58.688] [warning] Timezone: Asia/Dhaka. std::chrono::tzdb: cannot locate zone: Asia/Dhaka

I don't even see any log message, not even with --log-level trace. I'm on Arch Linux.

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo. Masked 2024b until fixed.

Yeah, This is it. Arch homies should downgrade too, until there's some more communication on this bug. I don't know which package contains/modifies timezone data on Arch though, as it might be subsumed in a larger package. I just downgraded the package on Gentoo and restarted waybar.

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo. Masked 2024b until fixed.

I have the same issue on Arch Linux, and I can confirm that downgrading the package tzdata from 2024b-1 to 2024a-2 fixes the problem. I suggest this as a temporary workaround for now.

Can confirm, works like a charm after the downgrade!

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo. Masked 2024b until fixed.

I have the same issue on Arch Linux, and I can confirm that downgrading the package tzdata from 2024b-1 to 2024a-2 fixes the problem. I suggest this as a temporary workaround for now.

Same here, downgrading to 2024a-2 fixes the issue.

facing the same issue from today on arch

Same issue on arch, downgrading 2024b to 2024a-2 fixes - Arch Linux

Also confirming that on Arch tzdata is the culprit - downgrade to fix.

Also confirming that downgrading tzdata is the way to fix it on Arch

another workaround is a custom module:
"custom/clock": {
          "exec": "date +\"%F %H:%M\"",
          "interval": 10
},

adding on that downgrading tzdata solves the issue on arch, hope this can be looked into soon

Seeing the same issue this morning. RTC is set to UTC and clock is only displaying UTC.
❯ timedatectl
               Local time: Mon 2024-09-09 13:33:07 PST
               Universal time: Mon 2024-09-09 05:33:07 UTC
               RTC time: Mon 2024-09-09 05:33:07
               Time zone: Asia/Manila (PST, +0800)
System clock synchronized: yes
              NTP service: active
              RTC in local TZ: no

hello, same here.
After downgrading, it works correctly

I was facing the same issue. It seems that the only way to fix it is to downgrade tzdata. I use arch btw.

I don't think downgrading a package is a good idea. But anyway, we aren't discussing Arch Linux here.
In my case I've been having this issues for several months, are we sure this is just tzdata?
Also, I have another machine running Fedora 40 and I experience the same issue, the tzdata version here is 2024a.

I'm not entirely sure about Fedora as i have no experience with it or it's derivatives. In my case the only fix that worked was to downgrade tzdata from 2024b-1 to 2024a-2. I have no clue about why you would be having the issue for several months as i had only experienced the issue after updating a few hours ago.

@itaranto You might have a different issue then? I'm also running Arch, downgraded tzdata, and it's working. Also it stopped working at the same time I upgraded tzdata to 2024b-1.

@itaranto You might have a different issue then? I'm also running Arch, downgraded tzdata, and it's working. Also it stopped working at the same time I upgraded tzdata to 2024b-1.

Yes, it's most likely a different issue.
I'm having this issue since version v0.10, just like the OP.

same for me. I am on waybar 0.10.4.

I am also having the same issue. I am on waybar 0.10.4
My config:
"clock": {
"timezone": "Asia/Dhaka",
"format": "{:%I:%M%p}",
"tooltip-format": "{:%Y %B}\n{calendar}",
// START CLOCK FORMAT
"format-alt": "{:%Y-%m-%d}"
},

Same issue on arch linux, downgrading tzdata fixes it.

Here to confirm downgrading tzdata to 2024a-2 fixes it

In other words time is stuck at GMT. It would be nice if "timzone" supported a plus-minus syntax. So "timezone": -5 would be equivalent to "America/Chicago" etc.

Wait so it's because of the update!!
I spend 2 hours trying to fix it. I was going mad :)

Looks like waybar doesn't work with sys-libs/timezone-data-2024b, at least have same issue with waybar at gentoo. Masked 2024b until fixed.

Can confirm downgrading tzdata resolved the issue for now.

Downgrading tzdata resolved the bug for me also.
I installed downgrade with yay yay -S downgrade.
Then I run sudo downgrade tzdata, and I selected 2024a-2.
After that I run pkill waybar & waybar & to restart it.

https://github.com/chronotope/chrono-tz/releases/tag/v0.10.0
It seems chrono-tz v0.10.0 fixed this.

https://github.com/chronotope/chrono-tz/releases/tag/v0.10.0
It seems chrono-tz v0.10.0 fixed this.
   39       ╎ try {
   40       ╎   tzList_.push_back(locate_zone(zone_name.asString()));
   41       ╎ } catch (const std::exception& e) {
   42       ╎   spdlog::warn("Timezone: {0}. {1}", zone_name.asString(), e.what());
   43       ╎ }

(gdb) p e.what()
$4 = 0x555555a79dd8 "std::chrono::tzdb: cannot locate zone: Asia/Shanghai"

The issue is fixed just by having 'chrono-tz' pkg?
Even if that's the case, there still is a regression from a previous version, which should be reported ideally. Did anyone do that yet?

Same issue
Arch Linux: 6.10.9-arch1-1
waybar: 0.10.4-2
tzdata: 2024b-1
waybar config:
		"clock":	{
			"interval":				1,
			"timezone":				"Europe/Moscow",	// Without manual tz set and with
			"tooltip-format":			"<tt>{calendar}</tt>",
			"format":				"{:%H:%M:%S}",
			"format-alt":				"{:%e %B %Y (%A) [%Y.%m.%d]}",
			"calendar":	{
				"mode":				"month",
				"mode-mon-col":			3,
				"on-scroll":			1,
				"format":	{
					"months":		"{}",
					"days":			"{}",
					"weekdays":		"{}",
					"today":		"{}"
				}
			},
			"actions":	{
				"on-click-right":		"mode",
				"on-scroll-up":			"shift_up",
				"on-scroll-down":		"shift_down",
			},
			"on-click-middle":			"gnome-calendar"
		},

Downgrading tzdata resolved the bug for me also.
I installed downgrade with yay yay -S downgrade. Then I run sudo downgrade tzdata, and I selected 2024a-2. After that I restart it with pkill waybar & waybar &.
Hope this bug will be fixed

Downgrading did help in my case. Thank you!
But, is the bug related to tzdata 2024b or waybar?

[warning] Timezone: Europe/Berlin. std::chrono::tzdb: cannot locate zone: Europe/Berlin
It is related to tzdata

On Arch Linux if I try to list all the timezones contained in tzdb
#include <chrono>
#include <iostream>

int main() {
    const std::vector<std::chrono::time_zone> &zones = std::chrono::get_tzdb().zones;
    for(const std::chrono::time_zone &i : zones) {
        std::cout << i.name() << std::endl;
    }
}

then I get only the following timezones
Etc/GMT
Etc/UTC

and this is the reason tzdb doesn't recognize any other timezone.
Links:
https://en.cppreference.com/w/cpp/chrono/tzdb

Guys I think we could be misleading the devs here, as far as I understand there's 2 issues here:

The original issue about the timezone not being detected automatically since v.0.10
A recent issue related to tzdata that prevents you to have a local timezone even when set manually.

I think this should be split into two different issues.

Agreed

another one confirming downgrading tzdata 2024a-1 or 2024a-2 fix the issue
i literally messed up my hwclock timedatectl bios clock everything lol

About to kms if clock keeps showing wrong in waybar

About to kms if clock keeps showing wrong in waybar

replace the clock module with something similar int the meantime:
  "custom/clock": {
    "exec": "date +\"%I:%M %p\"",
    "format": " {}",
    "interval": 10
  },

Unfortunately tzdata 2024b-2 (now in core-testing for archlinux) doesn't solve the issue...

Just installed vanilla arch, the issue appears to be fixed as my clock in the waybar is correct. Tzdata version is 2024b-2 from core-testing.

It looks like the recent  tzdata issue has been solved by gcc-14.2.1+r134+gab884fffe3fc-1.
https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/commit/2d0f36bcac02e8ebe25f3c187c51285bd1741737

However, the issue in the post is still present, and is unrelated to tzdata, I believe you all are looking for issue https://github.com/Alexays/Waybar/issues/3575

It looks like the recent tzdata issue has been solved by gcc-14.2.1+r134+gab884fffe3fc-1.
https://gitlab.archlinux.org/archlinux/packaging/packages/gcc/-/commit/2d0f36bcac02e8ebe25f3c187c51285bd1741737

Re-building waybar with the latest GCC fixes the issue.

Thanks for the update on the issue.
Update to latest gcc-libs and gcc fixed it on my arch.
Then just do a
pkill waybar && waybar -c /path/to/waybar_config -s /path/to/waybar_style.css &
Cheers

Fix confirmed.  Just doing a regular pacman -Syu pulled in the update to gcc-libs and gcc, and once that completed I ran waybar again, and the timezone issue was fixed. :tada:

thanks.

However, the issue in the post is still present, and is unrelated to tzdata, I believe you all are looking for issue #3575

Yes, this issue still happens to me (it's not related with tzdata at all).

@Kommynct I'd suggest closing this issue and creating a new one, otherwise it will be very confusing for the devs.

i suggest people powt about their issue in the relevant issue trackers instead of taking over an unrelated one

i suggest people post about their issue in the relevant issue trackers instead of taking over an unrelated one

Yes, I was about to say your issue got hi-jacked by another one :man_shrugging:

This ticket is about an issue that has been around since March.
For a similar issue that appeared about two weeks ago, see https://github.com/Alexays/Waybar/issues/3655

❯ timedatectl
               Local time: Sun 2024-12-08 19:10:26 -03
           Universal time: Sun 2024-12-08 22:10:26 UTC
                 RTC time: Sun 2024-12-08 22:10:26
                Time zone: America/Argentina/Buenos_Aires (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

My Waybar incorrectly says the titme is 22:10, which is quite clearly wrong.

Seems like an Argentinian issue at this point lol
Sum myself to the rest
❯ timedatectl
               Local time: Mon 2024-12-09 19:37:54 -03
           Universal time: Mon 2024-12-09 22:37:54 UTC
                 RTC time: Mon 2024-12-09 19:37:53
                Time zone: America/Argentina/Buenos_Aires (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: yes

Fresh install, SUSE Tumbleweed.

i'm not in argentina, definitely not an argentinian issue.

i'm not in argentina, definitely not an argentinian issue.

That would be oddly specific.

The issue went away for me eventually.
These seem to be two different causes for this issue. AFAIK, one of them was a bug in the c++ stdlib.

I travel constantly and have no desire or intention to constantly reset my waybar config for a timezone. That's uh, why I update my system's local timezone.
So does anyone understand what the actual issue is? Downgrading tzdata is not something I'm interested in doing. Nor is C++. But more than my disdain for C++ is my desire for my clock to report the correct time. It's massively confusing and sometimes detrimental for Waybar to just.... be showing the completely wrong time.
Also, I'm a bit shocked that this isn't even more widely noticed. Are the users not in this thread rocking distros with really out of date tzdata, or what?

I travel constantly and have no desire or intention to constantly reset my waybar config for a timezone. That's uh, why I update my system's local timezone.
So does anyone understand what the actual issue is? Downgrading tzdata is not something I'm interested in doing. Nor is C++. But more than my disdain for C++ is my desire for my clock to report the correct time. It's massively confusing and sometimes detrimental for Waybar to just.... be showing the completely wrong time.
Also, I'm a bit shocked that this isn't even more widely noticed. Are the users not in this thread rocking distros with really out of date tzdata, or what?

As far as i understand, the issue was really glibc, which got rebuilt against newest tzdata (which wasn't in the upstream yet) and this way it broke some apps.
I'm not experiencing any issues at the moment on arch linux, though

Downgrading tzdata is not an option for me. I struggle to believe that current, stable glibc + tzdata are so badly broken for 6 months that there isn't a bug in Waybar.

Maybe this is related. My system thinks that the clock is UTC time, but it seems like it's not actually:
❯ timedatectl
               Local time: Fri 2024-12-13 10:37:47 -03
           Universal time: Fri 2024-12-13 13:37:47 UTC
                 RTC time: Fri 2024-12-13 13:37:47
                Time zone: America/Argentina/Buenos_Aires (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

❯ sudo !!
sudo hwclock
2024-12-13 10:38:11.163333-03:00

~
❯ sudo hwclock --utc
2024-12-13 10:38:52.213120-03:00

~
❯ sudo hwclock --localtime
2024-12-13 13:39:05.157181-03:00

I'm sort of out of my depth here.

~Maybe this is related. My system thinks that the hwclock is UTC time, but it seems like it's not actually:~
❯ timedatectl
               Local time: Fri 2024-12-13 10:37:47 -03
           Universal time: Fri 2024-12-13 13:37:47 UTC
                 RTC time: Fri 2024-12-13 13:37:47
                Time zone: America/Argentina/Buenos_Aires (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

❯ sudo !!
sudo hwclock
2024-12-13 10:38:11.163333-03:00

~
❯ sudo hwclock --utc
2024-12-13 10:38:52.213120-03:00

~
❯ sudo hwclock --localtime
2024-12-13 13:39:05.157181-03:00

waybar shows 13:39
~I'm sort of out of my depth here, but I suspect this is related.~
Reading sudo hwclock --debug output indicates this is all as expected. I'm quite sure this is a bug in Waybar. This issue does not affect any other desktop, any other application, any other anything on my system. Only Waybar.

I have a similar output on Arch Linux:
$ timedatectl
               Local time: Sat 2024-12-14 09:52:08 -03
           Universal time: Sat 2024-12-14 12:52:08 UTC
                 RTC time: Sat 2024-12-14 12:52:07
                Time zone: America/Argentina/Cordoba (-03, -0300)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

$ sudo hwclock
2024-12-14 09:52:46.393252-03:00

Waybar displays 12:52.


Test struct methods ending in ?, !

Opal was not allowing members ending in ?, ! to be defined
https://github.com/opal/opal/pull/1165
Was going to add a test to see if Struct prevents invalid method names from being used, but as of 2.2.0 (release, not preview), MRI allows "invalid" method names like :'method-3-' to be used without error, so did not add a test for that.

done

Note that the Struct#[] spec already tests hyphens but indeed this spec if more appropriate.
Yeah, validation of these names seems to be rather limited.

Good spec, thanks!

Also, some implementations (opal bias here) don't use the methods with Struct#[]. opal goes directly to an underlying data structure.


Some logs not displaying Namespace and Podname detaills

Bug Report

General Information

K3s
Kubectl Client Version: v1.25.4
Karmor Logs are here: test2.log
Most likely calico-system in this case

To Reproduce

run the karmor log --logFilter all --json command and dump it into the system
You'll find some logs dont have namespace and podname being logged. Example given below:
{"Timestamp":1670571404, "UpdatedTime":"2022-12-09T07:36:44.353564Z", "ClusterName":"default", "HostName":"aks-agentpool-71604899-vmss000001", "Labels":"k8s-app=calico-typha","ContainerID":"116277e1516f927222eefc2c83fad346e211d080cf64165e9c1a523cffc06e8b", "ContainerName":"calico-typha","ContainerImage":"mcr.microsoft.com/oss/calico/typha:v3.21.6sha256:3ed72779a50d89795f9d7718cd45b6db32bbe5f62fc44935ac939b0cc52d344a","ParentProcessName":"/sbin/tini","ProcessName":"/code/calico-typha","HostPPID":655691,"HostPID":655722,"PPID":1,"PID":7,"UID":999,"Type":"ContainerLog","Source":"/code/calico-typha","Operation":"Network","Resource":"remoteip=<IP_ADDRESS> port=9098 protocol=TCP","Data":"kprobe=tcp_accept domain=AF_INET","Result":"Passed"}

Expected behavior
Each and every log should have namespace and podnames logged
Screenshots

These two logs as shown above do not show namespace or podname.

Empty spaces in some of the processes. This also applies to File and Network Operations as well.

Not seeing this issue with the latest version of kubearmor. Keeping it open and observing it.


⚠ Bofrost.at has degraded performance

In c3883a5, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1824 ms

Resolved: Bofrost.at performance has improved in 8dcb121 after 33 minutes.


Remove previously created form elements

Hello,
I am using this library and works fine , but i am facing a issue when i try to create a form after creating one form, means, if i have already created a form on a page whose state say; http://locahost/example/#/newForm and after this when i go to another state say; http://locahost/example/#/formList and now if again i create a new form by going to http://locahost/example/#/newForm state then the page shows previously created form components.
How can i remove old form components.
I am using

for form building, and,

for preview
Now how can i flush old form data?
i tried
$scope.default = [];
But its not clearing the old form elements
Thanks in advance

i tried this $builder.forms.default; but this is clearing further form data that i am storing into db

Hi @kamleshpawar2006 ,
I'm also facing the same issue. Can you please let me know how you solve this problem.
Thanks,
RJay


Nested HTML not parsed correctly

BEFORE

AFTER

@probablyup I've verified this within a project that I'm working on that is utilizing this library. I traced the issue down to this regex which is only capable of matching nested tags of the same parent tag name one level deep. Any levels deeper and this rendering issue occurs. You can confirm by running the below snippet in any JS REPL
const regex = /^ *(?!<[a-z][^ >/]* ?\/>)<([a-z][^ >/]*) ?([^>]*)\/{0}>\n?(\s*(?:<\1[^>]*?>[\s\S]*?<\/\1>|(?!<\1)[\s\S])*?)<\/\1>\n*/i;
console.log(regex.exec('

')[0])
// outputs unbalanced HTML '

'

I tried modifying the regex to the following
/^ *(?!<[a-z][^ >/]* ?\/>)<([a-z][^ >/]*) ?([^>]*)\/{0}>\n?(\s*((?:<\1[^>]*?>[\s\S]*?<\/\1>|(?!<\1)[\s\S])*?)*)<\/\1>\n*/i

to simulate a recursive match but performance took a steep hit (not surprisingly).
I looked through the codebase and it's using regex parsing heavily but I wanted to ask if there been thoughts of parsing via tokenization instead, at least for slightly better parsing of HTML such as the example in this issue? I feel that parsing HTML via regex will always have its limitations.

We gave up on this library after discovering this issue, and switched to mdx-js. Even though mdx-js is larger, it's more robust and that's what was important for us. Regex is just not reliable enough to parse even slightly more complex HTML. Good luck.

I looked through the codebase and it's using regex parsing heavily but I wanted to ask if there been thoughts of parsing via tokenization instead, at least for slightly better parsing of HTML such as the example in this issue? I feel that parsing HTML via regex will always have its limitations.

It'd vastly inflate the bundle size, which is a big part of the point of this library. All libraries have tradeoffs, and imperfect but serviceable HTML parsing at a tiny bundle size is this one.

It would be good if this were pointed out in the README.


Smoothscroll Flickering Page Elements and too fast on Safari 13.0.5

I have a website in overflow:hidden style, only letting you scroll the entire page.
On Safari 13.0.5 the nav-bar on the right is flickering and when i scroll multiple pages it goes way too fast.

You can look at this behaviour at test.dscoimbra.pt
If you can't reproduce the behaviour, I'll upload a video of it.
Thank you for your help.

I am using React and Next.js and I'm importing the polyfill on __app.jsx and initialising it on componentDidMount()
import '../global.css';

import App from 'next/app';
import LoadingBlocker from '../components/loading-blocker/LoadingBlocker';
import { Provider } from 'react-redux';
import React from 'react';
import smoothscroll from 'smoothscroll-polyfill';
import store from '../redux/store/index';

class MyApp extends App {
  // Only uncomment this method if you have blocking data requirements for
  // every single page in your application. This disables the ability to
  // perform automatic static optimization, causing every page in your app to
  // be server-side rendered.
  //
  // static async getInitialProps(appContext) {
  //   // calls page's `getInitialProps` and fills `appProps.pageProps`
  //   const appProps = await App.getInitialProps(appContext);
  //
  //   return { ...appProps }
  // }

  componentDidMount() {
    smoothscroll.polyfill();
  }

  render() {
    const { Component, pageProps } = this.props;
    return (
      <Provider store={store}>
        <LoadingBlocker />
        <Component {...pageProps} />
      </Provider>
    );
  }
}

export default MyApp;

Hey [deleted-account], I checked out your site briefly and can definitely see the bug. However this does not appear to be related to this polyfill.
I noticed that by disabling the transform: translateY(-50%) style that Safari no longer behaves broken. I would recommend finding a way to solve your UI intent without the transform.


Add != (notequal) operator to expression editor for Rules

This would also be applicable to other places that use the expression builder, but immediate request is to add a != operator for Rules.
This would mean we could simply write:
AND( "X-SSL-Client-Verify" != "SUCCESS")
Instead of:
NOT( AND( "X-SSL-Client-Verify" = "SUCCESS"))
It doesn't look much different on paper, but would help a lot with the ediitng (a good number less mouse clicks required) :)

Rules are now based on StroomQL, which has a != operator


Async Push-Pop example added

@knaman2609 I'm sorry no one responded to you sooner, but we generally don't link to external examples simply because they tend to fall out of date. Examples are generally kept in this repository so the code can be checked. However, I encourage you to share any examples or learning resources you have on the PureScript Discourse.


chore: introduce eslint

> eslint . "--fix"
/node-core-utils/lib/auth.js
  47:10  error  Redundant use of `await` on a return value      no-return-await
  70:5   error  Return statement should not contain assignment  no-return-assign

/node-core-utils/lib/request.js
  38:7  error  'totalCount' is assigned a value but never used  no-unused-vars

We have 3 errors. What do you think?(accept rules, etc...)
But totalCount seems to be used 🤔

I’m merging this since I have fixes for the first ones because I’m trying to do the same thing :)


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target_cbd73929-63d8-4c7a-922c-64c5d5e1d18b/pull/1 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target_cbd73929-63d8-4c7a-922c-64c5d5e1d18b.git

Docs Build status updates of commit 2eb9008:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 2eb9008:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error-UserAccountBuildPermissionInsufficientError] Owner v-alji no longer has Read permission of the repository https://github.com/opstest2/docs-archive-test-source. It might be due to recent GitHub changes on SSO. Please ask the owner v-alji to logon to Docs Portal https://ops.microsoft.com once again. If it is not the case, please ask anyone of Admin permission of the repo to assign a new owner via Docs Portal https://ops.microsoft.com

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


[plplot] Disable all language bindings but C++

What does your PR fix?
Fixes the plplot build enabling bindings based on build-time system inspection, e.g. fortran for https://github.com/microsoft/vcpkg/pull/22124. CC @JackBoosY
C++ is the only language which can be assumed to be buildable without extra dependencies.

Which triplets are supported/not supported? Have you updated the CI baseline?
unchanged, no.

Does your PR follow the maintainer guide?
yes

If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?
yes

Thanks for the fix!

Oh sorry, I forgot this PR.


Config settings not working

It has been reported that the configuration in environment.js is not getting picked up by EDA.  See end of #4.

Cannot reproduce


VIEWWALLET, NAV, DAO, DGD + typos + consistency

Spaces before double punctuation marks in French ( ;:?! )
Names, not verbs, in titles (both were mixed, I prefer names; feel free to change, but keep consistency in mind)

Thank you! French is looking good!


Refactor code coverage support.

This is in case (a) we ever have a second subdirectory like
bigtable/, and (b) because it makes the bigtable/CMakeLists.txt
more readable.

PTAL.


Improve Reverse Accessor Clash feedback

I just spent ages trying to work out what this migration error meant after I added a new app. This very minor addition to the feedback could have saved me a load of time getting my head around what was happening.

Hi Bernd,
Please open a ticket on Trac if there isn't one already (apologies if there is, I haven't spotted it).
I absolutely agree that it would be useful to say what the clashing name was.
It looks like (based on the test failures) the following unit tests will need to be updated to accommodate the change in message:
invalid_models_tests.test_relative_fields.AccessorClashTests.test_clash_between_accessors
invalid_models_tests.test_relative_fields.ComplexClashTests.test_clash_parent_link
invalid_models_tests.test_relative_fields.ComplexClashTests.test_complex_clash
invalid_models_tests.test_relative_fields.SelfReferentialM2MClashTests.test_clash_between_accessors

Please open a ticket on Trac

Voila: https://code.djangoproject.com/ticket/33131#ticket
Will review the patch review checklist soon.

@bernd-wechner Do you have time to keep working on this?

Soon. Life's busy. Priorities. But a good reminder.

Wow, took a quick look. one tiny line tweak and 13 workflow failures? Most of which produce a 404 error when I click on Details. And the only one that doesn't is a New Contributor message with no clear indication as to what is wrong. What am I to do?
I would love to get this cleaned up and learn what's up. I'm more than happy to contribute positively to Django (as I use it a lot) but this experience is less than encouraging so far ... I'd like to establish a workflow that, well, works ...

I would love to get this cleaned up and learn what's up. I'm more than happy to contribute positively to Django (as I use it a lot) but this experience is less than encouraging so far ... I'd like to establish a workflow that, well, works ...

We don't keep the entire history on Jenkins, that's why you're getting 404. You can rebase from the main branch and push again for a fresh build. Failures are related with the changed message (see invalid_models_tests). Please update also fields.E302, related tests, and docs.

(see invalid_models_tests). Please update also fields.E302

Can you interpret that for an inexperienced reader (like yours truly)?

(see invalid_models_tests)

You can run invalid_models_tests locally to check failures before submitting updates, e.g.
./runtests.py invalid_models_tests

Please update also fields.E302

fields.E302 is a similar check:
https://github.com/django/django/blob/d400b08a8baa697905daadd47a6ba12336e93336/django/db/models/fields/related.py#L239-L248
I suggested to update it as well.

Got me with a moment to spare tonight between a few things and my attention and a burning desire to understand Django contribs better and get it right so I got started with:
https://docs.djangoproject.com/en/3.2/internals/contributing/writing-code/unit-tests/
Alas up front I note the instructions could be a tad clearer  ;-).  Only because to work:
python -m pip install -r requirements/py3.txt

won't do .... alas. Loads of noxious red garble on the screen. So first tune my console to use a legible colour for the red (which I though I did a while back) and then reading them I find essentially I needed to:
pip install wheel
sudo apt install libmemcached-dev

Then the requirements installed fine. The second line of course is system dependent and my cited example is apt based some Debia/Ubuntu stream. The first line though is missing from requirements/py3.txt and I reckon I should add it as part of the PR? It's actually a very common problem, and I run into it a lot that docs presume wheel is installed. And in a new venv it never is it seems and having it in the requirements seems often overloooked somehow.
That said am looking at the test failures now ;-)

The first line though is missing from requirements/py3.txt and I reckon I should add it as part of the PR? It's actually a very common problem, and I run into it a lot that docs presume wheel is installed. And in a new venv it never is it seems and having it in the requirements seems often overloooked somehow.

I've just created a new virtual env (Python 3.8, Ubuntu) and all worked fine without wheel:
$ python -m pip install -e ..
Obtaining file:///django
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Collecting asgiref>=3.3.2
  Using cached asgiref-3.4.1-py3-none-any.whl (25 kB)
Collecting sqlparse>=0.2.2
  Using cached sqlparse-0.4.2-py3-none-any.whl (42 kB)
Collecting backports.zoneinfo
  Using cached backports.zoneinfo-0.2.1-cp38-cp38-manylinux1_x86_64.whl (74 kB)
Installing collected packages: sqlparse, backports.zoneinfo, asgiref, Django
  Running setup.py develop for Django
Successfully installed Django-4.1.dev20211001111137 asgiref-3.4.1 backports.zoneinfo-0.2.1 sqlparse-0.4.2

$ python -m pip install -r requirements/py3.txt
...
Successfully installed MarkupSafe-2.0.1 Pillow-8.3.2 PyYAML-5.4.1 aiohttp-3.7.4.post0 argon2-cffi-21.1.0 async-timeout-3.0.1 attrs-21.2.0 bcrypt-3.2.0 certifi-2021.5.30 cffi-1.14.6 chardet-4.0.0 charset-normalizer-2.0.6 docutils-0.17.1 geoip2-4.4.0 idna-3.2 jinja2-3.0.1 maxminddb-2.2.0 multidict-5.2.0 numpy-1.21.2 pycparser-2.20 pylibmc-1.6.1 pymemcache-3.5.0 python-memcached-1.59 pytz-2021.3 pywatchman-1.4.1 redis-3.5.3 requests-2.26.0 selenium-3.141.0 six-1.16.0 tblib-1.7.0 typing-extensions-<IP_ADDRESS> tzdata-2021.2.post0 urllib3-1.26.7 yarl-1.6.3

Bizarre, cannot explain that. Could be the order. I think I overlooked: python -m pip install -e .. on first try, and that may be the difference. Trying to interpret test results now and test definitions.  Fails on 4 assertions.

Ouch, been looking at the code behind these failures and starting to see why no-one wants to go there ;-).
The reports are superbly cryptic and unhelpful. Take a look at this:
FAIL: test_complex_clash (invalid_models_tests.test_relative_fields.ComplexClashTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python3.8/unittest/case.py", line 60, in testPartExecutor
    yield
  File "/usr/lib/python3.8/unittest/case.py", line 676, in run
    self._callTestMethod(testMethod)
  File "/usr/lib/python3.8/unittest/case.py", line 633, in _callTestMethod
    method()
  File "/media/Data/Workspace/Eclipse/Django/django/tests/invalid_models_tests/test_relative_fields.py", line 1414, in test_complex_clash
    self.assertEqual(Model.check(), [
  File "/usr/lib/python3.8/unittest/case.py", line 912, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.8/unittest/case.py", line 1118, in assertListEqual
    self.assertSequenceEqual(list1, list2, msg, seq_type=list)
  File "/usr/lib/python3.8/unittest/case.py", line 1100, in assertSequenceEqual
    self.fail(msg)
  File "/usr/lib/python3.8/unittest/case.py", line 753, in fail
    raise self.failureException(msg)
AssertionError: Lists differ: [<Err[801 chars]ssor ('Target.id') for 'invalid_models_tests.M[3805 chars]05'>] != [<Err[801 chars]ssor for 'invalid_models_tests.Model.foreign_1[3737 chars]05'>]

What the heck is ssor? Still not found where that creeps in.
Getting closer though. Stepping through the code. We're lucky that tonight my wife is stressed preparing stuff for uni tomorrow, the kids are in bed, and I've had enought of my other projects for the moment ;-). Won't last so I better get cracking and try to work out how to fix the test expectations for these failures.  Fixed 2 of 4 already, but ...

The failure report is hard to read, true, but the [801 chars] means the output was truncated. If you look up the failing test test_complex_clash and ctrl-F for "ssor" you'll see it's part of the word "accessor".
Try setting inserting the line self.maxDiff = None into the test case right before the assertion to get a bigger diff from the test failure. This test case should probably have it.

Thanks for that. Appreciate it. I did establish a little workflow for this painful process, and did fix the tests. I then encountered a hell hole of push issues to the branch because I use gitkraken generally and it's spitting errors about lacking worklflow permission so went to the cli and it can't log in and had to generate a new personal access token, and on and on and on ...
and then even though I rebased the branch onto the latest main, when I did push, blam the this PR says 107 files changed. I',m puling hair out. How hard do these guys want to make this? The commit changed one extra file, not 106 extra files.

I cannot fathom what github is doing, except to suppose:
https://github.com/bernd-wechner/django/commits/improve-reverse-accessor-clash-feedback
that what happens here is because the branch was from an old version of main (but hey I rebased it!) this push merged all the main branch changes onto the branch and that was the 106 little surprises. Which is NOT what we wanted. I wonder is this undoable or is it easier to trash the branch and create a new one cherry picking these two commits and them pushing them.

Wow, that was a mess, but the PR looks cleaner, just the two files in question now. Next would the doc.
All I can says is, git is both a blessing and a bane (I wonder if you can count the number of people who can explain and understand rebasing, fast forwarding and such in the world on your fingers or if you'd need your toes as well ;-). I reread that stuff ever few months because I can't remember.

Oh and fields.E302. On the morrow. Past midnight now ... At least I think I have a clean repo again.
Methinks what happened is I rebased the local and not the remote (origin) and so the push at the remote was onto a formk of main 105 commits ago.
Alas gitkraken on this repo and and this repo only bails on pushes with:
Push Failed: improve-reverse-accessor-clash-feedback: Push failed on refs/heads/improve-reverse-accessor-clash-feedback: refusing to allow an OAuth App to create or update workflow .github/workflows/linters.yml without workflow scope
So I had have to use the CLI to push (which uses ssh access and and a personal access token)

Thanks for you support BTW, all good upskilling (albeit IMHO frustrating at some levels) in the PR game. Been PRing a fair bit this last year, but this repo poses some special problems it seems (with gitkraken).

All I can says is, git is both a blessing and a bane (I wonder if you can count the number of people who can explain and understand rebasing, fast forwarding and such in the world on your fingers or if you'd need your toes as well ;-). I reread that stuff ever few months because I can't remember.

Don't worry we can squash & rebase for you with final edits, we do this every day.

Well tests all passed bar one flake. Looking better. Likely I'll finish this off this week between things as it's very close and been a large learning curve.

Well, once in the swing, it's much quicker. Just patched 302 and pushed the branch. All tests pass locally, and we'll see what Jenkins says shortly.

Dang, lots of new failures ;-). Overlooked 302 related issues. Clearly no invoked by the invalid_models_tests run. I shall have to seek and destroy them too ;-). It would be helpful if Jenkins reported the test that broke in the list without without having to open each of 17 items.

It would be helpful if Jenkins reported the test that broke in the list without without having to open each of 17 items.

Here you go https://djangoci.com/job/pull-requests-bionic/13541/#showFailuresLink.

Only one test is broken: model_inheritance.test_abstract_inheritance.AbstractInheritanceTests.test_reverse_foreign_key.

Wow you're quick Felixxm! Looks like all the one line. Fixed and pushed (which works in gitkraken now!) Fingers cross got all the 302s now.

Out of interest, for my learning here, where does Jenkins run? We run it at work on a build server. is it running at the github end as a service, or do you need an instance runnning somwhere else to report to github?

Out of interest, for my learning here, where does Jenkins run? We run it at work on a build server. is it running at the github end as a service, or do you need an instance runnning somwhere else to report to github?

Some details can be found on the wiki page.


Is PRAGMA defer_foreign_keys supported in sqlcipher?

I have a transaction with a couple of INSERT OR REPLACE statements that throws a foreign key error. I tried the statements by turning defer_foreign_keys=ON for the transaction and it worked in sqlcipher console / DBBrowser. But it is not working from my code.
Is PRAGMA defer_foreign_keys supported in sqlcipher or am I missing something?

Is it supported?

I have a transaction with a couple of INSERT OR REPLACE statements that throws a foreign key error. I tried the statements by turning defer_foreign_keys=ON for the transaction and it worked in sqlcipher console / DBBrowser. But it is not working from my code.
Is PRAGMA defer_foreign_keys supported in sqlcipher or am I missing something?
I am also facing the same issue
any update ? Please Fix it.

I think this question is more suited for the sqlcipher team - please ask there 🙂


Remove the need to mirror packages + transition to dotnet.myget.org/dotnet-core

Our repositories currently reference aspnetcore-[dev|release] feeds and NuGet.org while relying on Universe to mirror packages for us from dotnet-core, dotnet-corefxlab, roslyn, vssdk and vsformac feeds.
CoreFxLab will transition to dotnet-core and dotnet-corefxlab will no longer need to be referenced. The remainder are meant to support tooling and are not consumed by runtime packages.
Here's my suggestion, once dotnet-corefxlab goes away,

[ ] Update repos to reference dotnet-core as a source
[ ] Have Razor explicitly reference roslyn, vssdk, and vsformac (Are there other repos that reference packages from an external feed?)
[ ] Tell customers to use dotnet-core to get their ASP.NET Core nightlies. We should be ready to make an announcement to this effect and stop using aspnetcore-dev.

cc @natemcmaster \ @pakrym \ @Eilon

This does look overall correct to me.

+1. I'm in favor of this.

@pakrym could I assign this to you so we can track whenever you're done with the corefxlab changes?

Sure,

How would we handle situations like this? #869  - we need a new version of xunit from yet-another myget feed. Should we update the feeds in each repo? Or continue to mirror?

Not entirely sure. A test-only package is easy to deal with since the repo could reference the package and we'd be done. Packages consumed by runtime would be far more problematic (for instance if Kestrel needs a nightly build of Libuv?). Maybe we'll still need to keep the feature around, just not use it.

Unblocked now.

We decided that for now we should stop mirroring dependencies and we'll see if anything breaks.


Align collector configuration

Collectors get some value against which dependencies are compared, e.g. a regex-pattern in case of the className-collector. The key for this value can be different for each collector. I don't see much of a benefit, instead it makes configuration more difficult, because you need to know what the key is called for the specific collector.
Her is an overview of the current state:

collector
key
expected value type

BoolCollector
must, must_not
array<CollectorInterface>

ClassNameCollector
regex
string

ClassNameRegexCollector
regex
string

DirectoryCollector
regex
string

ExtendsCollector
extends
string

FunctionNameCollector
regex
string

ImplementsCollector
implements
string

InheritanceLevelCollector
level
int

InheritsCollector
inherits
string

LayerCollector
layer
string

MethodCollector
name
string

SuperglobalCollector
names
array<string>

UsesCollector
uses
string

I think it makes sense to streamline the key name for all collectors except BoolCollector to the same name, e.g. value.

Ideally, we would allow both variants at first to prevent a BC-break in the depfile.


Not including 'format' option in schema for an 'inputType: date' fails v2.2.2

Not including the format option in the schema an input with the inputType: date will cause validation to fail. It will reset the input and put the UNIX timestamp into the model. It will then put the following warning in the Chrome console:
The specified value "1286686800000" does not conform to the required format, "yyyy-MM-dd".
This issue does not exist in v2.1.1.
Correct schema:
{
    type: 'input',
    inputType: 'date',
    model: 'date',
    format: 'YYYY-MM-DD',
    validator: VueFormGenerator.validators.date
}

Example: https://jsfiddle.net/evild70/w3e0p2a6/ (see Chrome console for warning)
I couldn't find any mention of this in the documentation.

There's an issue I came across in Chrome recently where in value always has to be set in the format yyyy-mm-dd, regardless of how it's displayed on the screen and the submitted value will also always be in the same format.
https://developers.google.com/web/updates/2012/08/Quick-FAQs-on-input-type-date-in-Google-Chrome

@evild70 is this still an issue in the latest 2.3.x?


nodejs: Fix problem with permissions

Related Issue
(https://github.com/Granulate/gprofiler/issues/592)
How Has This Been Tested?
Run fibonacci application in container with: docker run --user 5555:0, and then run gprofiler as exe.

Yes

Flaky issues; this looks good.


lisa: Add support for new Hwmon node names with 'mainline' driver

The names of the nodes for energy have changed - they are no longer
of the form 'a53_energy' for the CPU clusters, but are now called
'BOARD_LITTLE_ENERGY'. Likewise, all the other sensor names are different
but we don't monitor those in lisa.
In order to support those, add a new device named juno2. Once both types
are no longer in circulation, the names can be changed.
Signed-off-by: Chris Redpath<EMAIL_ADDRESS>

I have reworked this a bit, I'll post a new branch and close this one.


Add instructions for installing opam and core.

It's late but we should mention that we expect opam and core to be installed, unless that's better mentioned elsewhere.
@exercism/ocaml

It might be mentioned in the docs/, but I think it's a good idea to list it here where people will be looking for more information as they're doing the exercises.


Improve resource navigator

This is a lofty request - but I'm currently not entirely happy with the resource navigator for the following reasons:

lots of scrolling up and down to get an overview of what types of resources there are; could we have a minimap of some kind!?
the various indents, spacings and section/subsection headlines create a "confusing" UI (for me...) - could we somehow simplify this!? Perhaps if we...

had no sections - only subsections?  or an accordion for the sections!?
had a "table view" with columns for name, type, namespace - with filtering/sorting on each!?

not urgent - but would be great to create some mockups to show to users and see what they think..

Related - https://github.com/kubeshop/monokle/issues/208


[Creators] Add how to limit the size of Storage provided by Datanode to the Masternode .

MicroByte Title: Hadoop Cluster
Improvement Proposal:

Make an activity of how learners can limit the storage size of Datanode.

Benefits of proposed improvements:
By default when Datanode is connected to the Masternode , Datanode provides its all storage to the Masternode but we can control it , with the help of proposed improvement leaners can provide limited storage or the desired amount of storage to the Masternode.

Hey @Nitesh-thapliyal this issue is for learners right?
If yes, you can rename the [creators] in the title to [learners]


Support building with the upcoming Libav 10 release

Is anyone working on this? I'm kind-of stuck here, on Ubuntu 14.10, I cannot use neither 2.4.10 nor 3.0-beta with ffmpeg, since libavcodec-ffmpeg-dev and the like would prompt uninstallation of  libavcodec-dev and ~70 other packages, and I don't want to break my system...

Currently on Ubutnu 14.10 neither 2.4.10 nor 3.x build with ffmpeg and vtk, since apparently vtk6-dev  depends on libavXXX-dev files. In general, the way I would approach this would be a new cmake drop-down style option, that would enable the user to switch between libav and ffmpeg, which in turn would influence another preprocessor flag that would switch between libav & ffmpeg versions of the code, hence I think the fix proposed here is incomplete. I would not advise to sticking to just one or the other: Ubuntu will default to ffmpeg instead of libav starting from 15.04, so far as I know. I am unaware of any way libav and ffmpeg could peacefully coexist and still be useful on the same system.


Back to lesson overview

Students cannot click back to the "Lesson Introduction" page
Why?
Use Case 1

When I had left my session last time I had just started the concept of a new lesson. I've returned to the site and clicked "Resume" on my dashboard. I'm in concept 1 of that lesson but feel like I want a refresher on what the lesson will entail.

Use Case 2

I've started concept 1 of a lesson but forgot how much time spend would be in the lesson. I'd like to go back to the lesson overview page to see if I want to go down this rabbit hole now or later.

@tcp I think this is done. I see PR is already merged. Please confirm


[Deploy] Twitch Chat

Service
Twitch.tv chat
Link to your repository
https://github.com/colinodell/franz-twitch
Additional Information
Forked from the proposed Franz 4 recipe.
Users who want to add Twitch chat will be getting the team id from URLs like https://go.twitch.tv/sovietwomble.  I've therefore defined https://go.twitch.tv/ as the urlInputPrefix even though that config option is not yet present on the configuration screen.

Deployed, thanks for your contribution.


⚠ ClamAV has degraded performance

In 25af905, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 90 ms

Resolved: ClamAV performance has improved in bac1b31 after 15 minutes.


Failed to deploy gateway-fqdn-proxy

My data :
for ex it data for this case "Deploy Gateway with TLSPassthrough option"

And run :  npx ts-node --project tsconfig-node.json scripts/fqdn_gateway.ts
Act.res :
Error: Error: Failed to deploy gateway-fqdn-proxy with name john on node 1 due to: failed to setup fqdn proxy: failed to verify domain dns record: host doesn't point to the gateway ip
at TwinDeploymentHandler.handle (/root/grid3_client_ts/src/high_level/twinDeploymentHandler.ts:393:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async GWModule.deploy_fqdn (/root/grid3_client_ts/src/modules/gateway.ts:42:27)
at async GWModule.descriptor.value (/root/grid3_client_ts/src/modules/utils.ts:14:16)
at async GWModule.descriptor.value (/root/grid3_client_ts/src/helpers/validator.ts:23:16)
at async main (/root/grid3_client_ts/scripts/fqdn_gateway.ts:18:17)
Cases: TC203,TC204,TC202
Deploying on:
Testnet,
Grid v0.1.32

@VenyaPanou
you need to use your own domain (you may create a new on on godady), so u can have access to it so you can connect.
You don't own the domain farming.threefold.io
https://library.threefold.me/info/manual/#/manual3_iac/grid3_javascript/manual__grid3_javascript_vm_gateways?id=detailed-explanation-1


MINIFICPP-1753 Remove the possibility of multiple initialization

https://issues.apache.org/jira/browse/MINIFICPP-1753

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically main)?

[ ] Is your initial contribution a single, squashed commit?

For code changes:

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file?
[ ] If applicable, have you updated the NOTICE file?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.

LGTM (edit: sorry, I didn't see it was still in draft; will take another look if there are more commits)

No problem, there are no additional commits, I just wanted to wait for the CI jobs to finish to make sure there are no additional problems. The one test that failed is a known issue.


when i use helm deploy cvat have a error

helm upgrade -n default cvat -i --create-namespace ./helm-chart -f ./helm-chart/values.yaml -f ./helm-chart/values.override.yaml
Warning  FailedScheduling    default-scheduler  running "VolumeBinding" filter plugin for pod "cvat-redis-replicas-0": pod has unbound immediate PersistentVolumeClaims
Warning  FailedScheduling    default-scheduler  running "VolumeBinding" filter plugin for pod "cvat-redis-replicas-0": pod has unbound immediate PersistentVolumeClaims

@xs818818 Hi,
we use bitnami's redis subchart and don't manage it, it might need to be updated.
Try to update redis subchart.

success，thank you


Implement methods to generate nodes via NodeParser

Description:
parseExpression(), parseStatements() is implemented with PR #32806 as per shell, debugger requirements.
There is a use-case(bindgen, open api, grpc, etc) if we add parseStatement(), parseModuleMemberDeclaration(), parseModuleMemberDeclarations(), parseTypeDescriptor() etc.
For example, say one wants to generate a statement with a specific name; int foo = 10;
NodeParser.parseStatement(String.format("int %s = 10;", "foo"))
will give the generated node without having to build it from scratch using NodeFactory API.
Also, any changes to ST parsing are instantly reflected through API.

@sameerajayasoma @rdulmina @hasithaa Shall we introduce the following?

parseStatement()
parseActionOrStatement()
parseModuleMemberDeclaration()
parseModuleMemberDeclarations()
parseTypeDescriptor()
parseBindingPattern()

I think this will simplify many places (bindgen, open api, grpc, some choreo folks also generate nodes) where nodes are generated to modify the syntax tree. This will not require knowledge of internal node structure to generate nodes.


Add JSON schema checking functionality for DRep and Gov action metadata

Changelog
- description: |
    Added schema checking functionality for DRep registration, DRep update, and GovAction metadata, based on CIP-0100, CIP-0108, and CIP-0119. Also add functionality to check whether a certificate is for DRep registration or updating.
  type:
  - feature
  - compatible
  - test

Context
The objective is addressing this issue: https://github.com/IntersectMBO/cardano-cli/issues/906
This PR adds 3 functions to the API that should be the only ones needed by the cardano-cli in order to implement this functionality:

isDRepRegOrUpdateCert - Checks whether a certificate is for DRep registration or DRep update.
validateDRepAnchorData - Checks whether a ByteString is valid JSON and conforms to CIP-0119.
validateGovActionAnchorData - Checks whether a ByteString is valid JSON and conforms to CIP-0108

This PR is a requirement from PR #995 that implements the checking in cardano-cli and is based of the version of cardano-api in this PR.
Related PRs in CIPs repo:

PR #950 - Adds @ before type field name
PR #951 - Ensures CIP-0008 is in capital letters

How to trust this PR
Tests should give some assurance. They are taken from the CIPs repo, with some adaptations that I have already created PRs in CIPs repo for (see above).
The main thing to check here is the accuracy of the checks (are they enough, are they too much, are they right).
Could be useful to check the cardano-cli PR together with this one.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[x] New tests are added if needed and existing tests are updated. See Running tests for more details
[x] Self-reviewed the diff

But the CIPs 0119 and 0108 are in proposed state. Shouldn't we wait till they get accepted?


Multiple month view not obeying viewStartDate for February (or current month maybe?)

Hi I am trying this
$('#calendar').kalendae({
                   mode: 'multiple',
                   months: 3,
                   viewStartDate: '2/1/2015'
               });

If viewStartDate is set to a different month it will work. But if it is not set or set to February (current month) then the months shown are January, February, March. I see the same on the demo http://chipersoft.com/Kalendae/

I fixed this by using
$('#calendar').kalendae({
                   mode: 'multiple',
                   months: 3,
                   direction: 'today-future'
               });

Perhaps this is intentional? Although I'm not sure why it would work one way for the current month and different way for other months

Yes, it is intentional. Multi-month views always center on the viewStartDate (or start on it for calendars showing an even number of months).  The reason today-future changes this behavior is because the user would not be able to select a day prior to the current month, so there's no reason to show them that month. It works the opposite for today-past.

Actually viewStartDate isn't centered when it is in the future rather it is the first month, so I'm not 100% sure I  understood.

It centers when there is no direction defined. It aligns against an edge when future or past directions are used.

Hi Chipersoft, maybe I didn't explain 100%. If you use  viewStartDate: '3/1/2015' it will start from May and move forward. If you use  viewStartDate: '2/1/2015' it will put February in the middle. That's what I thought was inconsistent.

it will start from May

May? Not March?
On Feb 18, 2015, at 11:23 AM, yehudahkay<EMAIL_ADDRESS>wrote:

Hi Chipersoft, maybe I didn't explain 100%. If you use viewStartDate: '3/1/2015' it will start from May and move forward. If you use viewStartDate: '2/1/2015' it will put February in the middle. That's what I thought was inconsistent.
—
Reply to this email directly or view it on GitHub.

Sorry, March :-) I don't live in the US anymore

Oh, I see.  I don't remember if that was the intent, but I'm ok with keeping it that way.


Sphinx PVC

What

[X] upgrade procedure tests
[x] Added System Sphinx  PVC
[x] Doc

Promoted System Sphinx to an independent component with its own reconciler, options and option provider modules. For backward compatibility, in the APIManager CRD, sphinx still included in spec.system.sphinxSpec. SphinxSpec new fields:

PVC persistentVolumeClaim

Storage Class Name storageClassName
Resources resources
Volume Name volumeName

---
apiVersion: apps.3scale.net/v1alpha1
kind: APIManager
metadata:
  name: apimanager1
spec:
  wildcardDomain: eguzki.apps.dev-eng-ocp4-8.dev.3sca.net
  resourceRequirementsEnabled: false
  system:
    sphinxSpec:
      persistentVolumeClaim:
        storageClassName: myClass
        volumeName: myVolume
        resources:
          requests: 2Gi

Verification steps

Requires openshift (oc CLI) session
Create new project

oc new-project 3scale-sphinx-pvc

Checkout this branch and run the operator

make install
make run

Deploy 3scale with a custom Sphinx PVC settings

no need to specify S3 credentials
wildcardDomain must be something valid (only if it is going to be used later). Usually ${PROJECT_NAME}.apps.${CLUSTER_DOMAIN}

k apply -f - <<EOF
apiVersion: v1
kind: Secret
metadata:
  creationTimestamp: null
  name: aws-auth
stringData:
  AWS_ACCESS_KEY_ID: testID
  AWS_SECRET_ACCESS_KEY: testkey
  AWS_BUCKET: testbucket
  AWS_REGION: us-east-1
type: Opaque
EOF

k apply -f - <<EOF
---
apiVersion: apps.3scale.net/v1alpha1
kind: APIManager
metadata:
  name: apimanager1
spec:
  wildcardDomain: example.net
  resourceRequirementsEnabled: false
  system:
    sphinxSpec:
      persistentVolumeClaim:
        resources:
          requests: 2Gi
    fileStorage:
      simpleStorageService:
        configurationSecretRef:
          name: aws-auth
EOF

wait for deployment to be ready

oc wait --for=condition=available apimanager/apimanager1 --timeout=-1s
apimanager.apps.3scale.net/apimanager1 condition met

The above "wait" ensures the pods are up and running.

Check the PVC for the system sphinx has indeed 2Gi as requested

❯ k get pvc system-sphinx -o wide
NAME            STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE    VOLUMEMODE
system-sphinx   Bound    pvc-5633f9e8-378e-4095-8214-c54258ba04b1   2Gi        RWO            gp2            5m6s   Filesystem

@akostadinov ready for review

I'm just surprised not to see these in the pod spec. But I also don't see limits in any pod. So I guess something special is needed to get resource limits set during installation?
Yes, you can apply "default" resource requirements or custom per component. This is an example to apply defaults (defined in the operator's code) to all 3scale components.

---
apiVersion: apps.3scale.net/v1alpha1
kind: APIManager
metadata:
  name: apimanager1
spec:
  resourceRequirementsEnabled: true


A little error in the tkinter and Tkinter name import

Issue Type: Bug
So basiclly the Python extention autocomplite and suggest the "tkinter" syntax for import but whenever you complite the code, error "ImportError: No module named tkinter" and thats totaly normal cause the module isn't named "tkinter" but "Tkinter" (the uppercase in the begin), so every time i want to compile the code i have to change the import name, (i can't just write the "Tkinter" with the uppercase when i code cause then i can't take advantage of the auto complite), thanks
Extension version: 2021.3.680753044
VS Code version: Code 1.55.0 (Universal) (c185983a683d14c396952dd432459097bc7f757f, 2021-03-30T16:01:05.981Z)
OS version: Darwin x64 14.5.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz (8 x 2200)

GPU Status
2d_canvas: unavailable_softwaregpu_compositing: disabled_softwaremetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offopengl: disabled_offprotected_video_decode: disabled_offrasterization: disabled_softwareskia_renderer: disabled_off_okvideo_decode: disabled_softwarewebgl: unavailable_softwarewebgl2: unavailable_software

Load (avg)
3, 3, 3

Memory (System)
8.00GB (0.02GB free)

Process Argv
-psn_0_53261 --crash-reporter-id 6465734e-fd91-4d4f-be10-f56e0de4b5c6

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspyt653:30270858
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstry914:30276682
pythonvsdeb440:30248342
pythonvsded773:30248341
vstes627:30244334
pythonvspyt875:30259475
pythonvspyt639:30281910
pythontb:30283811
wslfolderdoc:30282074
vspre833:30267464
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30276952
pythondataviewer:30285071

@Roombabatata What do you have as your language server in your settings? Can you share the logs from output > python  panel

sorry for having taken too long to respond, so is it what you asked me

@Roombabatata Can you try this with either JediLSP or pylance? Also can you share a screenshot of what you are seeing.

well, nothing has changed it still recommend me tkinter with a lowercase, with both JediLSP and Pylance

except that in JediLSP it now shows me errors about Jedi

Ah this is weird now I switched again to Pylance and now it tells me that I need to install in extention, so I installed it and now it's a bit better cause it shows me the errors before compiling, something like this

and with JediLSP it shows me this

and for the close and reopen just a miss click

Hi @Roombabatata,
If you look at the latest Tkinter documentation, the module name is tkinter with a lowercase, so JediLSP and Pylance are correct. Which version of Python is selected as an interpreter?

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on then we will be happy to re-open this issue to pick up where we left off.


autoscroll() not working

I have lcd 16x2 with i2c backpack (PCF8574T). I run this code:
var five = require('johnny-five');
var chipio = require('chip-io');

var board = new five.Board({
  io: new chipio()
});

board.on('ready', function() {
        var lcd = new five.LCD({controller: "PCF8574T", address: 0x27, bus: 2, rows: 2, cols: 16});
        lcd.cursor(0, 0);
        lcd.autoscroll().print("Bloop").print("Bleep");
});

My lcd only display BloopBleep and a blinking cursor.
Thanks

There are a number of issues emerging with I2C LCD devices and CHIP, I will post back here and on the other as soon as I learn more

Thank you

Hi @sumarouno,
Could you please also try this code with PR #19?

Yes sure. I have tried that code. But still same. I got BleepBoop and blinking cursor.
Thanks

Hi @sumarouno,
Could you also provide debug logs? DEBUG=chip-io node <file>.js
I'm interested to see what i2c methods are being called.

DEBUG=chip-io node .js

hi, @sandeepmistry . Nice to meet you again. I will try your suggestion but I'm at my office right now. I will give my report after I try at home.
 What i got is the same thing, "BleepBloop" with blinking cursor at the end.
here my code for m mega:
var five = require('johnny-five');

var boards = new five.Boards([
{
	id: "mega",
	port: "/dev/ttyUSB3"
},
]);

boards.on('ready', function() {
	var lcd = new five.LCD({
		controller: "PCF8574T",
		address: 0x27,
		bus: 2,
		rows: 2,
		cols: 16
	});

        lcd.cursor(0, 0);
        lcd.autoscroll().print("Bloop").print("Bleep");
});

thank you

@sumarouno great idea to test with the Mega2560!
Since it doesn't seem specific to the CHIP + chip-io, I think we can close and move to the issue to the main Johnny-Five repo.


fix fsdp auto wrap policy

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Single script for testing development, production

This is essentially a duplicate of this pull request:
https://github.com/pbarbiero/enhanced-electron-react-boilerplate/pull/4
... adapted for the basic- version of the project.

Thanks!


Analytics

Fixes #115 .
Changes proposed in this pull request:

Google Analytics via ember-metrics library
offline mode support with a lib from Google

cc @HospitalRun/core-maintainers

@jglovier it's surely the former and yes, you're right, it's confusing now which GA account should be used. It also allows everyone to change the config easily, so maybe some encapsulation of GA-ID would be required there.

So, I see 3 solutions there:

If we really say "Oh, no one really edits config/environment on their own!", let's leave it as it is.
We would be able to use Lazy initialization in order to encapsulate a bit the ID and put it in our route.js.
And if we really care that our ID is... well... call it safe or maybe not-so-confusing, then the possible solution could be creating a custom hr-google-analytics metrics adapter and encapsulate the ID there.

@jglovier @tangollama @jkleinsc opinions?

@stukalin thanks for the response. @jkleinsc @tangollama I'd be interested to hear your thoughts on ☝


Is there a way to export a warmed up graph so that it is ready to go from cold boot?

I have not tried straight pickle but did not see any documentation about exporting model.

PyTorch 2.0 has a way to save on disk and reload compiled Triton kernels.
Using their API should save lots of time during the warmup.
We just merged a merge to a recent version of PyTorch 2.0 so I guess it's very doable to just call their API to launch Triton kernels instead of the original Triton one.
However, a CUDA graph can't be exported and reused.
The main reason is that kernels are re-executed with their parameters.
Those parameters include gpu memory addresses.
And it's very likely that your tensor memory address will change from launch to launch (if you quit Python session and the CUDA pool is freed).
It's certainly possible in theory to update the graph parameters, but it seems very hard, so probably better to just rerun the warmup (without recompiling triton kernel ofc).

@amazingvince FYI we have found a way to speedup warmup significantly in #234.


I want to add Kimi Raikkonen. But...

When i add kimi raikkonen... okay i contract him for 4 years. But when i want to advance to race week .... then my game says BOEM. Crashed. How to fix it? I want kimi. I want to give him a good drink.

Kimi Raikkonen already exists in the game as a retired driver.


add link to CrowdIn in README.md

Start with a simple change, and then we can figure out if we want to add something to the i18n docs page or otherwise.

I'm with Kelos, would be good to have a note about supported language and also have a list of what those languages are, prob with the English name, localised name, locale name, and maybe a flag because it's cool.

I added the English name.  Not certain of what the correct localised names would be, and they're not on our Crowdin project either.  I experimented with a couple options for flags but I don't think they're really worth the effort to try to style inline in markdown and emoji-flags don't display as flags when someone's viewing via Windows.


[Samples][Tableandlinkupdate]

Updated the following files:

TOC.yml
conversation-basics.md

Removed the Bots and Messaging extension samples from the TOC.
@Wajeed-msft - please update the following before we approve the PR:

[ ] Verify if the inline code has been updated.
[ ] Does this file require a code snippet?

Docs Build status updates of commit d2afa7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/conversation-basics.md
:bulb:Suggestion
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md

Line 332, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /azure/bot-service/dotnet/bot-builder-dotnet-add-media-attachments?view=azure-bot-service-3.0

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit d2afa7d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/bots/how-to/conversations/conversation-basics.md
:bulb:Suggestion
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md

Line 332, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /azure/bot-service/dotnet/bot-builder-dotnet-add-media-attachments?view=azure-bot-service-3.0

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 41dd9b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 41dd9b1:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 545cd92:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 545cd92:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/bots/how-to/conversations/conversation-basics.md
:white_check_mark:Succeeded
View

msteams-platform/tutorials/code-samples.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@Wajeed-msft - gentle reminder to approve the PR. Thank you.


Docs: omit function name in SnapshotTesting.md

Summary
http://facebook.github.io/jest/blog/2016/10/03/jest-16.html

We removed function names from snapshots.

Test plan
Your clear mind and sharp eyes, friendly reviewer :)

Legit

Just below, there was one step forward and one step back in https://github.com/facebook/jest/pull/2745/files#diff-7aab380059e10ec2a4da3d6adc2d51d7

forward: larger nicer cropped terminal window
back: received in picture is Instagram but change in code is Jest

http://facebook.github.io/jest/docs/snapshot-testing.html#updating-snapshots
If you want me to change the code to match the picture, then I can update this PR.

oh, thanks!


Remove unnecessary code in main

Signed-off-by: Jun Xu<EMAIL_ADDRESS>

Can you explain why this is unnecessary?

sorry，I'm misunderstanding.


npm dependencies

Hi, I've noticed that dependencies in package.json are a bit mixed up: @types are in dependencies and regular libraries that are used are in dev-dependencies.
The thing is that npm won't install dev-dependencies when you install the package, but only dependencies. So if you say that someone needs to install reflect-metadata when they install this package, that's an obvious "smell" you need it in your dependencies.
I'll make a PR soon with a fix 🙂

Hey thanks for your advice :) But there is a reason why these dependencies are listed in the corresponding dependency configuration (dependecies/devDependencies).
reflect-metadata should not be installed by default when using sequelize-typescript.This is to ensure, that never multiple reflect-metadata packages exist in one project. This is because of how reflect-metadata stores the information. For example if there is a version conflict between two reflect-metadata dependencies, you will end up with two reflect-metadata packages. In this case I faced the issue, that arbitrary meta data is stored in one reflect-metadata package and later tried to retrieve from the other, in which of course, the meta data couldn't be found. I agree, that there could be a better way of handling these dependencies: peerDependencies could be a way to go. But I didn't get these to work as I expected (NPM complains about missing peer dependencies despite of there are installed). So I decided not to using peerDependencies. But If you can help me on this I would appreciate it :) The reason why reflect-metadata exists in devDependencies: It is needed for testing.
@types/* dependencies: These dependencies are listed in dependencies because sequelize-typescript provides typings by default. So when using sequelize-typescript with typescript you will need the @types/* dependencies as well. Or did I overseen something?

@Pritilender As you also mentioned sequelize in your pull request: The consumer of sequelize-typescript should be able to choose which sequelize version they want to use. So that also sequelize is a peer dependency :)

@RobinBuschmann Oh, I see. I wasn't thinking about having different versions.
For @types, I think that all type packages are dev dependencies, but if you want to ensure that the user has out of the box support for sequelize in TS, then it makes sense to have it there.
As far as help is concerned, I'm glad to help you. This would be my first open-source contribution, so I'd appreciate if you would give me some advice, or write some contributor guide. I can take a look at this thing with peerDependencies first. I'm currently working on a project that uses this package, so I'll be writing down some issues I find. Also, if you have some kind of a roadmap for v1.0, that would be nice to be somewhere publicly available.

@Pritilender Good to here that you will include sequelize-typescript in your project :)
Regarding contribution: I don't have any guidelines yet. For every newly added feature, tests should be implemented. When writing an issue, questions, advices,..  any help is greatly appreciated.
Since all sequelize features are available with sequelize-typescript (or did I missed one?), there are no features on my list for an update to v1.0. But before I will update this repo to a major version, I would like to use it a little bit more on my own projects, to ensure that it is ready for production. But if you have any features in you mind, feel free to contribute them :)
Anyway I do have some ideas for new features. I will create an issue with a proposal soon. If you like to discuss about it.
If it is ok for you, I will close this issue(?) (Feel free to post any further questions in this issue)

@RobinBuschmann It's cool :)


⚠ PrivateHD has degraded performance

In 2571b4f, PrivateHD ($PHD) experienced degraded performance:

HTTP code: 200
Response time: 2596 ms

Resolved: PrivateHD performance has improved in 67ff619.


Fix TLS certificate for https://ciscobinary.openh264.org

Please use a correct certificate for the site so HTTPS works out of the box. It's currently having Akamai name in subject alternative name. Eg Let's Encrypt can be combined quite well with Akamai CDN to get correct subject alternative name so the site is accepted by TLS libraries.

See #909 :-(

This is a serious issue. No one should be using OpenH264 in current state where

GitHub doesn't have SHA2 for files
Cisco download site is subject to MITM attacks due to lack of proper HTTPS support
No GPG signatures for validating file origin

One of three must be fixed, preferably all.

If anybody is home, this should be closed as a duplicate of #909

infringement of copyright 48 cfr 102 uk 48 cfr 101 japan farmer president international canabis project intellectual property meaning bussines requirements unlawful intrest in a public contract is a violation 2921.15 ohio merchabilty and fitness is a stand alone policy

#3669 Could you please help with this issue?

@BenzhengZhang you can mark this as a duplicate of #909

The only conclusion I've reached here is binaries built by Cisco should not be used. Cisco also hosts binaries build by Mozilla whose hashes are securely distributed.


[SSH Access]add hdfs and ssh check in dockerContainerScript

Coverage increased (+0.4%) to 74.674% when pulling 6aa790ef6bdd028e4349d66f349d359b76851d92 on canwan/delete-exit-without-hdfs into f954382511af074b616b8aff21baf3c85d7d8bf8 on master.

Could you explain why don't we replace hdfs with webhdfs?

This is a low priority work item to use webhdfs instead, so we just want to mitigate this issue now.


can we add a section that shows what data the service's server retain after account closure?

It will probably be difficult to know that, but we can just refer their privacy policy and/or ask on support chat.
I don't know if it would be better for jgmd or jdm but IMO jdm is a better fit.
Also can refer tosdr
For eg. Amazon saves order information for legal reasons after account closure but there could be some expiry date?

I think this is information we rarely get and I'm ok in adding them to the notes when they are provided, so I'm closing the suggestion for now.


[Hotfix] Failed addons

Don't allow addons that are having service issues to prevent file related pages from loading.