Repo cleanup.. remove ignored files, update ignore list

this is an offer for me to help, I'm looking for confirmation & maybe some guidance
Problem
I'm seeing a number of changes in my local git gui which could be prevented with some cleanup.
Enhancement

There are some .DS_Store files in the repo which are ignored & show as diffs
it looks like there are some database files in the repo which need cleanup
adding some well placed .keep files can ensure folders are in place upon git checkout
I see some changes in the backup script I'd submit in a separate PR once this is done.

Additional context
I've been running cross platform dev teams for a while. Not everyone knows about a .gitattributes file or .editorconfig.
I'm not super familiar with how to help the actionable code, but I can sure clean up a repo. 😄
I plan on opening a PR with changes soon, I'll have some questions about how best stuff should work.
My local diff in the moment:

Hi @YesThatAllen  - I would love a PR for this!  Thank for your help. 🙏

Here's a start to the work.. all feedback is welcome.
I've got a question regarding timezones.. I wonder if the diff I'm about to paste in could be handled in a separate issue regarding timezone support, but maybe I'm setting my tz to Chicago the wrong way, resulting in the diff.
Diff:

The tz.sh script updates all those files to have your timezone and is run during setup.sh.  The updated.sh uses tz.sh to reset to default (yes, America/Los_Angeles) and then does a git pull and runs tz.sh again to set it back to your local timezone as stored in the local (untracked) tz file.
Yes, it is a hack, but the timezone localization required in all those files didn't allow for an external reference.

Gotcha.. Once we're done with #269, there will be FAR fewer diffs showing, and in my mind, those will be easier to ignore. Addressing the "hack" is fodder for a later date/issue,

Gotcha.. Once we're done with #269, there will be FAR fewer diffs showing, and in my mind, those will be easier to mentally ignore.
Addressing the "hack" is fodder for a later date/issue.

Unfortunately, I can't update to the current version due to the following reason:
admin@ds620slim:~/Powerwall-Dashboard$ ./upgrade.sh
Upgrade Powerwall-Dashboard from 2.9.3 to 2.9.6
---------------------------------------------------------------------
This script will attempt to upgrade you to the latest version without
removing existing data. A backup is still recommended.

Upgrade - Proceed? [y/N] y

Resetting Timezone to Default...

Pull influxdb.sql, dashboard.json, telegraf.conf, and other changes...

No local changes to save
remote: Enumerating objects: 79, done.
remote: Counting objects: 100% (79/79), done.
remote: Compressing objects: 100% (36/36), done.
remote: Total 79 (delta 45), reused 63 (delta 37), pack-reused 0
Unpacking objects: 100% (79/79), 23.43 KiB | 193.00 KiB/s, done.
From https://github.com/jasonacox/Powerwall-Dashboard
   864bcde..da239f4  main       -> origin/main
 * [new tag]         v2.9.6     -> v2.9.6
 * [new tag]         v2.9.4     -> v2.9.4
 * [new tag]         v2.9.5     -> v2.9.5
Updating 864bcde..da239f4
error: unable to create file influxdb/backups/.keep: Permission denied

Any idea what might be causing this (the last upgrades never failed)?
Some files in ~/Powerwall-Dashboard/influxdb belong to the user root, but as far as I understood, I'm not supposed to run ./upgrade as root:
admin@ds620slim:~/Powerwall-Dashboard/influxdb$ ll
total 60
drwxr-xr-x 1 admin users   358 May  7 14:41 .
drwxr-xr-x 1 admin users   948 May  7 14:41 ..
drwxrwxr-x 1 root  root  14382 Feb 11 15:33 backups
drwxr-xr-x 1 root  root     36 Apr 26  2022 data
-rw-r--r-- 1 admin users  1057 Feb 20 11:18 dropcq.sql
-rw-r--r-- 1 admin users 15280 May  7 14:41 influxdb.sql
-rw-r--r-- 1 admin users 15280 May  7 14:41 influxdb.sql.bak
drwxr-xr-x 1 root  root     14 May  7 02:28 meta
-rw-r--r-- 1 admin users  1089 Feb 11 16:43 run-once-2.8.0.sql
-rw-r--r-- 1 admin users     3 Feb 11 16:46 run-once-2.8.0.sql.done
-rw-r--r-- 1 admin users   508 Feb 20 11:18 run-once-2.8.3.sql
-rw-r--r-- 1 admin users     3 Feb 20 11:18 run-once-2.8.3.sql.done
-rw-r--r-- 1 admin users  3590 May  2 17:52 run-once-2.9.2.sql
-rw-r--r-- 1 admin users     3 May  2 17:52 run-once-2.9.2.sql.done
drwx------ 1 root  root     36 Apr 26  2022 wal

Is it possible that my installation is now corrupted since ./upgrade has already started doing some changes when it failed? I guess that at least the timezone has been changed?

Any idea what might be causing this (the last upgrades never failed)?
Some files in ~/Powerwall-Dashboard/influxdb belong to the user root,

Yep influxdb/backups/ was created by root, so the update script can't create a file in it.

but as far as I understood, I'm not supposed to run ./upgrade as root:

Correct. there are a number of ways we might handle this, but the simplest fix for now is to not attempt to create that .keep file. I've submitted a fix in #272

Is it possible that my installation is now corrupted since ./upgrade has already started doing some changes when it failed?

The git operations were called before anything too drastic was attempted on the local setup, so your data should be fine.
(I assume your dashboard is still running and that you can see the grafana interface?)

I guess that at least the timezone has been changed?

The upgrade script should set it back to the timezone you've specified in pypowerwall.env.

Merged!
@jaydkay thanks for opening this!  This shows a gap in test rigs where I do not have active backup scripts running that change permissions.  You should be able to run upgrade.sh again.
Minor correction on timezone - It is set in the tz file when you first ran setup.sh and upgrade will set it back to that after the new release pull.

@jaydkay I believe I was able to replicate a setup similar to yours (with backup owned by root) and the latest upgrade worked without error.

Hi @YesThatAllen and @jasonacox, thanks a lot for your quick support! Unfortunately, probably due to the failed upgrade from 2.9.3 to 2.9.6 I now get the following error:
admin@ds620slim:~/Powerwall-Dashboard$ ./upgrade.sh
Upgrade Powerwall-Dashboard from 2.9.6 to 2.9.7
---------------------------------------------------------------------
This script will attempt to upgrade you to the latest version without
removing existing data. A backup is still recommended.

Upgrade - Proceed? [y/N] y

Resetting Timezone to Default...

Pull influxdb.sql, dashboard.json, telegraf.conf, and other changes...

Saved working directory and index state WIP on main: 864bcde v2.9.3
error: cannot pull with rebase: You have unstaged changes.
error: please commit or stash them.

The upgrade seems to think that I got 2.9.6 installed, but that upgrade failed, so I should still be with 2.9.3. Any idea how to proceed from here?

try starting with git checkout main
and if git pull --rebase doesn't succeed, review what it says is blocking.
you may need to use git checkout to reset a file or two. Post back if there's issues you can't readily get past, or with other findings?

Okay, so:
admin@ds620slim:~/Powerwall-Dashboard$ git checkout main
M       tools/influxdb2/flux/tesla_energy.strings.flux
M       tools/influxdb2/flux/tesla_energy.vitals.flux
Already on 'main'
Your branch is behind 'origin/main' by 15 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

and
admin@ds620slim:~/Powerwall-Dashboard$ git pull --rebase
error: cannot pull with rebase: You have unstaged changes.
error: please commit or stash them.

Sorry, I have no idea how to fix this...

try git status ?

Okay, this gives:
admin@ds620slim:~/Powerwall-Dashboard$ git status
On branch main
Your branch is behind 'origin/main' by 15 commits, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   tools/influxdb2/flux/tesla_energy.strings.flux
        modified:   tools/influxdb2/flux/tesla_energy.vitals.flux

Untracked files:
  (use "git add <file>..." to include in what will be committed)
        .editorconfig
        .gitattributes
        backups/backup.sh
        compose.env
        dashboards/archive/
        grafana.env
        grafana/.keep
        grafana/alerting/
        influxdb/backups/
        influxdb/run-once-2.8.0.sql.done
        influxdb/run-once-2.8.3.sql.done
        influxdb/run-once-2.9.2.sql.done
        telegraf.local
        tmp.sh
        tools/solar-only/grafana/.keep
        tools/solar-only/influxdb/.keep
        tools/tesla-history/tesla-history.auth
        tools/tesla-history/tesla-history.conf
        v6.5.1/grafana/.keep
        v6.5.1/influxdb/.keep

no changes added to commit (use "git add" and/or "git commit -a")

oh.. this is about line endings. you've got the new .gitattributes file which makes your local think the two .flux files have been changed.
rm .gitattributes

and try pulling again?

Okay, removed the file and ran git pull --rebase, which now gives:
admin@ds620slim:~/Powerwall-Dashboard$ git pull --rebase
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 9 (delta 5), reused 8 (delta 5), pack-reused 0
Unpacking objects: 100% (9/9), 1.51 KiB | 155.00 KiB/s, done.
From https://github.com/jasonacox/Powerwall-Dashboard
   da239f4..8dd0f81  main       -> origin/main
Updating 864bcde..8dd0f81
error: The following untracked working tree files would be overwritten by merge:
        .editorconfig
        dashboards/archive/dashboard-animation.json
        dashboards/archive/dashboard-grid.json
        dashboards/archive/dashboard-new.json
        dashboards/archive/dashboard-orig.json
        dashboards/archive/dashboard-v2.8.2.json
        dashboards/archive/dashboard-v2.8.3.json
        dashboards/archive/dashboard-v2.9.0.json
        dashboards/archive/dashboard-v2.9.1.json
        grafana/.keep
        tools/solar-only/grafana/.keep
        tools/solar-only/influxdb/.keep
        v6.5.1/grafana/.keep
        v6.5.1/influxdb/.keep
Please move or remove them before you merge.
Aborting

Gotcha.. so yeah you'd want to remove those as well.
For those playing the home game; the following command, run from the repo's root, would be the thing:
rm rf .gitattributes .editorconfig dashboards/archive/dashboard-animation.json dashboards/archive/dashboard-grid.json dashboards/archive/dashboard-new.json dashboards/archive/dashboard-orig.json dashboards/archive/dashboard-v2.8.2.json dashboards/archive/dashboard-v2.8.3.json dashboards/archive/dashboard-v2.9.0.json dashboards/archive/dashboard-v2.9.1.json grafana/.keep tools/solar-only/grafana/.keep tools/solar-only/influxdb/.keep v6.5.1/grafana/.keep v6.5.1/influxdb/.keep

(leave out the -rf to confirm operations & you'll just have to hit "ok" a bunch)

Okay, seems we're getting closer... ;) Deleted all the files and tried again:
admin@ds620slim:~/Powerwall-Dashboard$ git pull --rebase
Updating 864bcde..8dd0f81
Fast-forward
 .editorconfig                                            |  21 +++++++++++++++++++++
 .gitattributes                                           |  25 +++++++++++++++++++++++++
 .github/ISSUE_TEMPLATE/other.md                          |   2 --
 .gitignore                                               |  35 +++++++++++++++++++++++++++++++----
 README.md                                                |  17 +++++++----------
 RELEASE.md                                               |  29 ++++++++++++++++++++++++-----
 VERSION                                                  |   2 +-
 _config.yml                                              |   2 +-
 compose.env.sample                                       |   6 +++---
 dashboard.json                                           |  58 +++++++++++++++++++++++++++++++++++++++++++---------------
 dashboards/README.md                                     |   3 ---
 dashboards/{ => archive}/dashboard-animation.json        |   0
 dashboards/{ => archive}/dashboard-grid.json             |   0
 dashboards/{ => archive}/dashboard-new.json              |   0
 dashboards/{ => archive}/dashboard-orig.json             |   0
 dashboards/{ => archive}/dashboard-v2.8.2.json           |   0
 dashboards/{ => archive}/dashboard-v2.8.3.json           |   0
 dashboards/{ => archive}/dashboard-v2.9.0.json           |   0
 dashboards/{ => archive}/dashboard-v2.9.1.json           |   0
 dashboards/dashboard.json                                |  58 +++++++++++++++++++++++++++++++++++++++++++---------------
 dashboards/powerflow-animation.html                      |   6 +++---
 grafana/.DS_Store                                        | Bin 6148 -> 0 bytes
 grafana/.keep                                            |   1 +
 grafana/README.md                                        |   2 --
 influxdb.conf                                            |   1 -
 influxdb/.DS_Store                                       | Bin 6148 -> 0 bytes
 influxdb/README.md                                       |   2 --
 location.html                                            |   1 -
 powerwall.yml                                            |  11 +++++------
 pypowerwall.sample                                       |   5 -----
 telegraf.local.sample                                    |   4 ++--
 tools/ecowitt-weather-history/ecowitt-weather-history.py |   6 +++---
 tools/influxdb2/flux/tesla_energy.strings.flux           |  52 ++++++++++++++++++++++++++--------------------------
 tools/influxdb2/flux/tesla_energy.vitals.flux            |  66 +++++++++++++++++++++++++++++++++---------------------------------
 tools/solar-only/grafana/.keep                           |   1 +
 tools/solar-only/grafana/README.md                       |   2 --
 tools/solar-only/influxdb/.keep                          |   1 +
 tools/solar-only/influxdb/README.md                      |   2 --
 upgrade.sh                                               |  22 +++++++++++-----------
 v6.5.1/grafana/.DS_Store                                 | Bin 6148 -> 0 bytes
 v6.5.1/grafana/.keep                                     |   1 +
 v6.5.1/grafana/README.md                                 |   2 --
 v6.5.1/influxdb/.DS_Store                                | Bin 6148 -> 0 bytes
 v6.5.1/influxdb/.keep                                    |   1 +
 v6.5.1/influxdb/README.md                                |   2 --
 v6.5.1/pypowerwall.sample                                |   5 -----
 verify.sh                                                |   4 ++--
 47 files changed, 289 insertions(+), 169 deletions(-)
 create mode 100644 .editorconfig
 create mode 100644 .gitattributes
 rename dashboards/{ => archive}/dashboard-animation.json (100%)
 rename dashboards/{ => archive}/dashboard-grid.json (100%)
 rename dashboards/{ => archive}/dashboard-new.json (100%)
 rename dashboards/{ => archive}/dashboard-orig.json (100%)
 rename dashboards/{ => archive}/dashboard-v2.8.2.json (100%)
 rename dashboards/{ => archive}/dashboard-v2.8.3.json (100%)
 rename dashboards/{ => archive}/dashboard-v2.9.0.json (100%)
 rename dashboards/{ => archive}/dashboard-v2.9.1.json (100%)
 delete mode 100644 grafana/.DS_Store
 create mode 100644 grafana/.keep
 delete mode 100644 grafana/README.md
 delete mode 100644 influxdb/.DS_Store
 delete mode 100644 influxdb/README.md
 delete mode 100644 pypowerwall.sample
 create mode 100644 tools/solar-only/grafana/.keep
 delete mode 100644 tools/solar-only/grafana/README.md
 create mode 100644 tools/solar-only/influxdb/.keep
 delete mode 100644 tools/solar-only/influxdb/README.md
 delete mode 100644 v6.5.1/grafana/.DS_Store
 create mode 100644 v6.5.1/grafana/.keep
 delete mode 100644 v6.5.1/grafana/README.md
 delete mode 100644 v6.5.1/influxdb/.DS_Store
 create mode 100644 v6.5.1/influxdb/.keep
 delete mode 100644 v6.5.1/influxdb/README.md
 delete mode 100644 v6.5.1/pypowerwall.sample

I suppose I can now try to normally invoke the ./upgrade.sh script? Thank you!

Yep, the script had failed on the git pull --rebase. You've done that now so the upgrade script should work as expected.

Upgrade will show same version, but you want to continue (technically you should always be able to re-install same version). Also, can you run ./verify.sh to ensure everything is still set up and running correctly?
@YesThatAllen should we add anything to upgrade.sh to accomodate for the repo changes?

Yes, ./upgrade.sh made an update from 2.9.7 to 2.9.7 and completed without errors. Also, ./verify.shshows that everything is working as expected. Thanks a lot to both of you!

@YesThatAllen should we add anything to upgrade.sh to accommodate for the repo changes?

Removing the .keep from backups should be enough to prevent anyone else running in to this issue.
Other changes to the upgrade & backup scripts are fodder for separate issues.

I started putting my thoughts separate issues:

potential backup script improvements in https://github.com/jasonacox/Powerwall-Dashboard/issues/273
potential upgrade script improvements in https://github.com/jasonacox/Powerwall-Dashboard/issues/274

I imagine we can close this issue once it goes a while without addition related issues like @jaydkay pointed out.

Another benefit I hoped to get from this cleanup was to remove the pretty incessant logging of this statement in the grafana docker container:
="ignoring unexpected file while scanning local working directory" filename=/var/lib/grafana/alerting/.DS_Store

I ended up git-pulling and updating my local without the script, then updating docker itself, so the containers restarted. I was still seeing that error.. I don't know enough about how docker populates its containers to know if the .DS_Store file should be expected to get removed.
I was able to remove it manually by using the terminal in the container & running
rm /var/lib/grafana/alerting/.DS_Store
What I actually did

$ ls -al /var/lib/grafana/alerting/
total 8
drwxr-x--- 4 1000 1000  128 May  5 17:24 .
drwxr-xr-x 8 1000 1000  256 May 12 17:04 ..
-rw-r--r-- 1 1000 1000 6148 May  5 17:24 .DS_Store
drwxr-x--- 3 1000 1000   96 May 12 17:03 1
$ rm /var/lib/grafana/alerting/.DS_Store
$ ls -al /var/lib/grafana/alerting/
total 0
drwxr-x--- 3 1000 1000  96 May 12 17:07 .
drwxr-xr-x 8 1000 1000 256 May 12 17:04 ..
drwxr-x--- 3 1000 1000  96 May 12 17:03 1
$ ```

</details>

I _assume_ that no one who's starting this project fresh would see that message. Woot?

I noticed we still have a dashboard.json at the top level and a slightly newer copy at dashboards/dashboard.json. Should we cleanup the one at the top level and keep them all in the dashboards folder?

The original purpose of the dashboards folder was to collect user submitted "Alternative Dashboards" as the README.md says. If we move the default dashboard there, we would need to update the setup instructions in setup.sh, upgrade.sh and Readme. I have been reluctant to do that in order to make the setup easy (keeping what you need in the root folder) but the duplicate file is probably a good reason to reconsider.

I'm fine leaving it in the root folder, but then we should remove the duplicate in the dashboards folder. The one in dashboards had some slight tweaks to two of the queries.

I think that proves that we should clean it up and just use the one in the dashboards folder.  It is logical and shouldn't be difficult for the community to figure out.  I updated the instructions including the setup.sh and upgrade.sh references to the new location.  Thanks for raise this @jgleigh ! 🙏

The tz.sh script updates all those files to have your timezone and is run during setup.sh. The updated.sh uses tz.sh to reset to default (yes, America/Los_Angeles) and then does a git pull and runs tz.sh again to set it back to your local timezone as stored in the local (untracked) tz file.
Yes, it is a hack, but the timezone localization required in all those files didn't allow for an external reference.

What about to use template files and create the final ones from them?
The template files would have $TZ as reference, and then envsubst command could be used to change it and write the final files.


ensure all formalized datetime formats are supported

Feature
All formalized datetime formats should be supported, e.g. RFC 3339, ISO 8601, etc.
Update the README.md section Features.
Also see https://www.unixtimestamp.com/index.php

As of 0.0.34

[X] ISO 8601 https://github.com/jtmoon79/super-speedy-syslog-searcher/blob/0.0.34/src/data/datetime.rs#L2084-L2116
[X] RFC 3339 https://github.com/jtmoon79/super-speedy-syslog-searcher/blob/0.0.34/src/data/datetime.rs#L2084-L2116
[ ] RFC 3164 supported, but the test cases need to be commented like // RFC 3164 syntax
[ ] RFC 2822 supported but very limited, the test cases need to be commented like // RFC 2822 syntax, also need more varying forms of it as RFC 2822 allows arbitrary whitespace. Not all permuations need to be supported (like for example, datetimes crossing newlines would not be possible) but an attempt to support more variations could easily be done.
[ ] RFC 5424 supported, but the test cases need to be commented like // RFC 5424 syntax

Each one of these formalized types needs a sample log file under ./logs/standards/.

Once this is fixed then this Issue can be closed.
$ ./target/release/s4 ./logs/standards/RFC-2822.log
WARNING: no syslines found "./logs/standards/RFC-2822.log"

$ ./target/release/s4 --version
super_speedy_syslog_searcher 0.4.57


Allow to disable arrow binding for selected/future shapes

(copied from https://github.com/excalidraw/excalidraw/pull/2146#issuecomment-739240175)
Proposal A
Introduce an element-specific property bindingEnabled: boolean (accessible from element property menu), either for all linear elements, or just arrows (as is currently).
By default, new shapes would inherit it from currentBindingEnabled appState prop (same as we do with other shape properties), so it'd be easy to both disable/enable the behavior for all future shapes (so users who don't like auto-binding would simply disable it once for a scene, while still being able to enable this for a few specific elements on the scene as needed). The default would not change from current, so there would be no breaking change.
Bindable elements (non-linear elements) would keep auto-binding only to linear elements which have bindingEnabled set to true.
Apart from the benefits described above, I can see we could add binding support for lines as well, since it would not be as problematic as it is currently.
Proposal B
Same as above, but also enable the same prop for non-linear elements such as rectangles, which would exclude these shapes from being bindable to arrow elements even if they were bind-enabled.

I generally face issues with arrows which i think is being solved by Proposal A. Proposal B is also a good addition to have and I think can be extended once Proposal A is implemented.


Update part-8-rtk-query-advanced.md

Thanks for the PR!
To better assist you, please select the type of PR you want to create.
Click the "Preview" tab above, and click on the link for the PR type:

:bug: Bug fix or new feature
:memo: Documentation Fix
:book: New/Updated Documentation Content

Thanks!

Hmm. For the record, the current version of the "Essentials" example app is still using React-Router v5.  So, technically I think this change to the code snippets in the docs is incorrect on two levels - it doesn't match the actual code in the sandbox / repo, and it is wrong for the version of React-Router we're using.

Ah, gotcha. I've got repo whiplash from just working in the RR one 😀


How to set up the app? Flutter run isn't working

Hi Fredrik! First of all, I am a great fan, cheers from Brazil! 🇧🇷
Frederik, even when usem FVM to try to flutter run on version < 1.22.4 the project doesn't seem to work
Is there anyway in which you could explain to us how to run the project starting from git clone?
Thanks for your patience and GREAT WORK!!! keep going!!

Hello, please try with Flutter SDK Version 1.22.4 for now, it should work.
I will probably make an update in the future to work with other versions.
Steps that works for me with sdk version 1.22.4:

Clone project
Open project with android studio
Replace google-services with a real one from firebase
Press "get dependencies" (should be a bar in the top), it's also
possible to run using command
Run project (green play button)

If this doesn't work, please provide me with more details about what errors
you get.
I can help you more later today, currently at work.
// Fredrik
Den fre 11 juni 2021 kl 14:48 skrev Leonardo Gomes @.***

:

Hi Fredrik! First of all, I am a great fan, cheers from Brazil! 🇧🇷
Frederik, even when usem FVM to try to flutter run on version < 1.22.4 the
project doesn't seem to work
Is there anyway in which you could explain to us how to run the project
starting from git clone?
Thanks for your patience and GREAT WORK!!! keep going!!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dgewe/Tinder-App-Flutter/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALFSARDP2ZUPL2WODM6X6NLTSIAYNANCNFSM46QVLYEA
.

Hey Fredrik! Your step by step was awesome, and it's working smoothly now!
I hope you had a great day at work, and thanks a lot!
Wish you the best 👋

Just wanted to say that I am your biggest fan, cheers from Sweden!
Please continue sharing more apps. 💯👍

Hi I don't seem to have the green play button at the top?


Add Python agents

Agent images to run Python based pipelines

Thanks for merging! When can I expect the new image to be published?

@hodossy  I just notice that a build is failing because this image can't be published :) a link here to a jira issue would have been nice to understand the context anyway Apparently nobody created the appropriate docker repository which I am going to do now :)

INFRA-2277

[INFRA-2277|https://issues.jenkins-ci.org/browse/INFRA-2277] is now done-done and the images are available on [DockerHub|https://cloud.docker.com/u/jenkins/repository/docker/jenkins/jnlp-agent-python/general] thanks @hodossy for this contribution, and meanwhile I created [JENKINS-59474|https://issues.jenkins-ci.org/browse/JENKINS-59474] in order to have images with jnlp using jdk11


Which regulator is used?

I want to flash the ESP but not sure which regulator you are using, could you please tell me the model?

I used a development board like this.

Download
https://www.mediafire.com/file/5t7dozm7sptcuqj/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Added information about regulators to README.


SPLAT-1280: update documentation for vSphere

Update documentation with details about vSphere control plane machine set implementation.

/lgtm

/lgtm

/assign @damdo

/test unit

/test unit

/test unit

/test unit
unit tests are failing for a different reason every time they are run, retesting..

/test unit
tests are oomkilling

/test unit

Will look into it. Thanks @rvanderp3


Shell completion generation fails in loop with global flags/options

Rust Version
N/A
Affected Version of clap
Probably all but 2.20.3 was the one where the bug was encountered.
Expected Behavior Summary
Build and compilation should succeed.
Actual Behavior Summary
Build fails with the following output:
$ cargo build
   Compiling mwe v0.1.0 (file:///D:/GitHub/rust-phpup)
error: failed to run custom build command for `mwe v0.1.0 (file:///D:/GitHub/rust-phpup)`
process didn't exit successfully: `D:\GitHub\rust-phpup\target\debug\build\mwe-563482c66f20550f\build-script-build` (exit code: 101)
--- stderr
thread 'main' panicked at 'Non-unique argument name: quiet is already in use', C:\Users\Fleshgrinder\.cargo\registry\src\github.com-1ecc6299db9ec823\clap-2.20.3\src\app\parser.rs:147
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Steps to Reproduce the issue
cargo build the code linked in the Gist
Sample Code or Link to Sample Code
https://gist.github.com/Fleshgrinder/3b562bb6c91deb49635543e68f720651
Reason
The problem occurs due to gen_completion and build.rs where the app is reused in the loop as you discovered already in a short Gitter chat.

Thanks, as per our discussion on gitter, I shuold have this fixed soon 😄

Also, incase anyone else is running into this calling the gen_completions causes all global Args to be propogated, on second and further iterations of the loop, this causes duplicate Args to be built which is an error.
This is a bug, and those duplicate Args should be ignored in this case.
The temporary fix is to rebuild the App struct with each iteration of the loop (which takes nanoseconds, so isn't a big deal).
for shell in &[Shell::Bash, Shell::PowerShell] {
    let mut app = build_cli();
    app.gen_completions(env!("CARGO_PKG_NAME"), *shell, env!("OUT_DIR"));
}


Magic 8 Ball

"shake" the Magic 8 Ball and get a response to your life changing questions.
have options for
Classic Responses
Funny Responses
Sarcastic Responses
Mean "grumpy cat" Responses
Random Response from above responses

Here are the standards you would find on a real magic 8-ball:
const phrases = [
  'It is certain',
  'It is decidedly so',
  'Without a doubt',
  'Yes definitely',
  'You may rely on it',
  'As I see it, yes',
  'Most likely',
  'Outlook good',
  'Yes',
  'Signs point to yes',
  'Reply hazy try again',
  'Ask again later',
  'Better not tell you now',
  'Cannot predict now',
  'Concentrate and ask again',
  'Don\'t count on it',
  'My reply is no',
  'My sources say no',
  'Outlook not so good',
  'Very doubtful'
]

Looking forward to Grumpy Cat versions.

I have that in my go bot (the standard list). Thank you for posting them here too. If I write or, or anyone else for that matter, I'd like it to implement flat file/json response data. That way anyone can add response files into a directory and 8ball can load them.

yeah, I think grumpy cat responses could be fun

Jody are you working on this one?

I'd love to work on this if you don't mind, btw? Either way, work on branch feature/command-8ball and push and pull changes as soon as you commit.


Effiency around functions

Wouldn't it be more efficient to register the function like this:

FunctionRegistry.RegisterFunction("sin", (Func<double, double>)Math.Sin, false);`

Instead of

FunctionRegistry.RegisterFunction("sin", (Func<double, double>)((a) => Math.Sin(a)), false);

Thinking of that it would be one less function call.
But I may be mistaken.

yes, you are fully right. It would indeed be an improvement to do so.

Done in the dev branch. It will be released as part of Jace 1.0

Thanks for quick reply


Use {{ stdlib("c") }} (if possible)

We have sysroot_* in a couple spots in this recipe
https://github.com/conda-forge/cuda-nvcc-feedstock/blob/53eb8f143391e135b5d89f81b9cc72abc0c65d56/recipe/meta.yaml#L55-L64
In other feedstocks we have changed uses of sysroot_* to {{ stdlib("c") }}. However those used sysroot_{{ target_platform }}
Whereas this feedstock uses sysroot_{{ cross_target_platform }}. So this may not be as easy (or even possible) to change
For now simply filing to track
xref: https://github.com/conda-forge/cuda-feedstock/issues/26

@conda-forge-admin , please re-render


Add JustList: Viro

Checklist

[x] I understand that this is not the place to request a token listing.
[ ] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[ ] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL: https://virotoken.com/justlist.json
JustList Name: Viro
Link to the official homepage of the JustList manager: https://virotoken.com/

We found that all the tokens in the application List you submitted except “VIRO” have been included in the Tron Alliance List. Since there is only one new token, we suggest adding “VIRO” to the existing List, such as Tron Alliance List:https://github.com/listtronalliance/tronalliance.

Sorry, your issue will be closed as the issue has not been replied for more than one month.Please submit again if you would like to apply for a new list.
Finally, thank you again for your application.I hope you are having a great day.


/dev/fd/63: Operation not permitted

I want to use ffmpeg to concatenate mp3 files.
This is the command:
ffmpeg -f concat -i <(printf "file '%s'\n" ./*.mp3) -c copy output.mp3
And the error I am getting is:
/dev/fd/63: Operation not permitted
I checked if I can write in the folder (with touch) and that works.

It looks like your syntax might be screwed up?
http://unix.stackexchange.com/questions/156084/why-does-process-substitution-result-in-a-file-called-dev-fd-63-which-is-a-pipe
Guy is getting the same error outside of WSL with a very similar input to what you're doing.

The command works in my ubuntu. It also works for others, see here: http://superuser.com/questions/202809/join-multiple-mp3-files-lossless/584123#584123
Have you tried it directly? The difference between this command and and the link you posted is exactly what their question answers: you need a file output there, this is exactly what printf provides (in contrast to ls).

Oh, guess I'm wrong!  Maybe it's because ffmpeg is out of date? Or maybe it's a WSL problem as you said.

Latest ffmpeg, wasn't so easy to install because it's not built-in to Ubuntu 14.04 (only from 15 on again) :)

This is fixed in Creators Update.


Add instance labels

Closes #42.

Testing...

Found some issues. Currently testing http provider for Traefik instead

Renamed to labels instead of instance labels. For beter clarity.


JsonParserIterator.init future timeout

Description
This PR adds a timeout to the future.get method call in used with JsonParserIterator.init if DirectDruidClient.QUERY_FAIL_TIME is set on the query context of the query, to plug up a potential hole which would allow the broker to overshoot query timeout.
Using DirectDruidClient.QUERY_FAIL_TIME does mean that (as far as I can tell) this currently only works with the JsonParserIterator used by DirectDruidClient, since otherwise we would need to pass in request start time in order to set the correct timeout of the remaining timeout on the future. MetadataSegmentView and SystemSchema do not seem to have direct access to any sort of timeout or cancellation due to timeout facilities, so it didn't seem worth the effort to directly use the timeout on the query context.
This is currently using System.currentTimeMillis() despite #8505 in order to be consistent with DirectDruidClient.checkQueryTimeout which also uses System.currentTimeMillis(), in favor of addressing this in future work that fixes this up everywhere.

This PR has:

[x] been self-reviewed.
[x] added unit tests or modified existing tests to cover new code paths.

Inspection failure looks like a false positive as the error is for a file that's not modified by this PR:
processing/src/main/java/org/apache/druid/query
    ChainedExecutionQueryRunner.java (1)
        151: make() Unchecked assignment: 'com.google.common.collect.Ordering' to 'java.util.Comparator<T>'. Reason: 'ordering' has raw type, so result of nullsFirst is erased

The travis failure looks legit.
[ERROR] testQueryTimeoutFromFuture(org.apache.druid.client.DirectDruidClientTest)  Time elapsed: 0.102 s  <<< FAILURE!
org.junit.ComparisonFailure: expected:<[Resource limit exceeded]> but was:<[Query timeout]>


Add codeowners file

Should this affect how we approach renovate dependency updates?
https://github.com/android/health-samples/pull/307/files
I've been following the Wear samples guides for updates, but maybe we want those split out if possible along these project lines?

Should this affect how we approach renovate dependency updates?
https://github.com/android/health-samples/pull/307/files
I've been following the Wear samples guides for updates, but maybe we want those split out if possible along these project lines?

Yes, I think this does affect that. I think the bulk of the HC/HP sample updates so far have been renovate-bot changes. And if we kept the CODEOWNERS file as is, I think it would mean that someone from HC would be required to also approve any renovate bot PRs.

If I move renovate.json into the health-services folder does that solve things?

If I move renovate.json into the health-services folder does that solve things?

Let me check.

If I move renovate.json into the health-services folder does that solve things?

Let me check. But no need to block this PR.

I somehow missed the second sentence 🤦🏾
I think includePaths does what we need

Well this is a better outcome


[🐛 Bug]: iron-session error 405 method-not-allow

next-on-pages environment related information

Local PC: Macos Apple silicon M2/M1
Nodejs 18.19
wrangler 3.9.0
Deployment: CloudFlare Pages

Description
I am building Nextjs 14 app on Cloudflare Pages with iron-session as a Auth option.
The local webapp builds and runs well with next-on-pages.
But running on CloudFlare Pages gets the 405 error.
I also try to debug with real-time log but, it shows nothing.
Please help for this simple code in Next-iron-session
Reproduction

Get the sample code
Fill env vars
Build and deploy to CF Pages by github or wrangler
Test login with account: john/123

Pages Deployment Method
None
Pages Deployment ID
No response
Additional Information
No response
Would you like to help?

[ ] Would you like to help fixing this bug?

@all Please kindly share your experience on Auth options with Next-on-pages apps:

Next-Auth v5 with backend workers (I also got error 405)
Iron-session
Others

the only solution i found for this issue is to add export const runtime = "edge" to the root layout


Improvement: optimize pow2 air constraint for output aggregation

This PR address #199.
Introduce a separate column to keep the value of previous row output.

Thanks for the review. I've actioned on the requested changes. Requesting you to kindly let me know your thoughts on the latest PR.
Regarding updating the diagrams, can we update the image with the new png file instead of creating a new link?

Regarding updating the diagrams, can we update the image with the new png file instead of creating a new link?

Good point about storing the diagrams in a better way, thanks! After discussion, we'd like to start storing them in github instead of externally. Can you make a new "assets" directory inside of the "docs" crate and add the new diagrams there? We'll migrate the rest of the images to this directory in a future PR.

@grjte Thanks for the detailed review. I've actioned on the changes you've requested. Please let me know your thoughts on the latest PR.
1. Can you address my above response to your question about images and add the new images to an assets directory?
In this PR, I've created a new folder "assets" in docs crate for the diagrams. We can create a new issue to migrate rest all diagrams to assets folder.
Finally, a nit, but if you're using semantic commits (which is great to see!) I would prefer if you follow the same system we do and use "feat" for production code additions and improvements, rather than "imp", so that we are all internally consistent.
Thanks. I've updated the commits to maintain consistency.

Thanks @grjte for initiating a discussion on this. @bobbinth: We have come up with an updated diagram of auxiliary table comprising changes in bitwise & pow2 co-processor section. We want to introduce operation selectors in the co-processor to make the diagram much more intuitive & clear to the readers. Kindly let us know your views on this.

@0xKanekiKen I like the idea! A couple of small suggestions:

In the internal selectors, I'd probably not use 0's and 1's as I don't think there is any special structure there (i.e., (1, 1) could be followed by (0, 0)). I think using just vertical dashes should be fine.
If we are adding selector components to the bitwise/pow2 sections, might as well add them to the hasher component. There, we have 3 columns which are used as selectors (also no special structure).

@bobbinth - Thanks for your suggestions. Let me know if I should upgrade these diagrams in a separate PR. Anyways, we have to migrate rest of the diagrams in the assets folder and if we are planning to do it in a separate PR then it will be nice if we include this upgrade in the PR.


Creates auth credential for Game Center sign in

Creates a AuthCredential for a Game Center sign in.
 GameCenterAuthProvider.getCredential()
  .sink { completion in
    /* On completion */
  } receiveValue: { credential in
    /* On received credential */
  }
  .store(in: &cancellables)

Thanks for sending this PR, @ziadtamim!
A couple of notes:

Please make sure the file is in the correct folder
Please add some tests (see FIRSignInWithGameCenterTests.m)

Also, always feel free to use draft PRs when staging your work.

@peterfriese Tests added for SignInWithGameCenter and GameCenterAuthProvider.


Add strategy conflict test case

Expand on the test cases to cover expected conflicts such as a load balanced and simple strategy having been used.
Wait until https://github.com/Kuadrant/dns-operator/issues/187 is complete.
Remove the same test from Kuadrant-operator.

@mikenairn is there still value in keeping the Kuadrant Operator test but ensuring it is simply validating that the status in the DNSPolicy resource is correct given it is the user facing API?

@mikenairn is there still value in keeping the Kuadrant Operator test but ensuring it is simply validating that the status in the DNSPolicy resource is correct given it is the user facing API?

I think this should be a test we have in the kuadrant operator DNSPolicy tests even if it is tested at the DNSRecord level in the dns operator suite.

the test was added in https://github.com/Kuadrant/kuadrant-operator/pull/699 PR (issue https://github.com/Kuadrant/kuadrant-operator/issues/606 ). During #187, it will be almost unchanged.
The test creates conflicting policies and makes sure we display errors in statuses of Policies and Records. I'll close this issue as there is not work to be done


Bundle sccache binaries

FIXME: Try to run bundled sccache

sccache --version works fine on Windows and Linux, Mac TBD.

@alexeykuzmin Where did the prebuilt's come from, they need to come from my hashing branch if we want the hashing to work across machines 🤔

@MarshallOfSound
https://github.com/mozilla/sccache/releases/tag/0.2.6

if we want the hashing to work across machines

Honestly I don't even understand what you're talking about )

Mac fails with dyld: Library not loaded<EMAIL_ADDRESS>error

Everything's ok now. sccache statically linked with the openssl works well.

@alespergl it's 25MB of binaries combined.
I probably could make them entirely optional: like put them in an external storage, add a script to fetch them when they're needed and os on, but it would be too complicated.
I totally understand your concern though. If we continue to add more stuff in the repo, eventually it will become huge and slow, and we definitely don't want it to happen.


about camer parameters

I'm going to add some projection loss to HybrIK. But there is an disalignment between the object and the mesh projected from 3D to 2D like below. The camera parameters from annotions cant be wrong, can they? Any suggestions?
Thank you for your great work, and I have learned a lot from it！

I finally figure it out! They differ by a distance of root joint!


Prefix-n-Shorten fails in Chrome because address bar hides http://

(First time issue writer, advanced apologies for doing it wrong.)
In Chrome, the address bar hides the http:// part of a url, unless it is https:// in which case Chrome leaves it alone. When using the prefix-n-shorten, since Chrome hides the http:// on most pages, the shortening will fail.
Expected behavior: the shortened url shown on the admin panel after using the prefix-n-shorten shortcut of YOURLS.
Actual behavior: the landing page of my YOURLS installation.
Steps to reproduce:

Open Chrome
Go to non-https page
Prefix the URL on said page in the address with the yourls installation path
Fails to produce the shortened url

Example:

myyourls.com/theverge.com/blah/blah | fails
myyourls.com/http://theverge.com/blah/blah | works

Other information:

PHP 5.5.9
MYSQL 14.14
Ubuntu 14.04
YOURLS 1.7

I love using the prefix-n-shorten feature, and while this is annoying, I end up just typing the http:// by hand. Even if there is no way to fix this, I figured it might helpful to document somewhere.

This is a browser issue, nothing YOURLS can fix (how to know if http://sho.rt/omg.com is a short URL or a shortening attempt?)
In Firefox: about:config then set browser.urlbar.trimURLs to false
In Chrome, there's probably something similar. Not a user, I don't know, but Google will probably be your friend :)


how to know 'cat''s descendants and ancestors?

Where do you get this prior information?
sorry for my simple question, I'm a newbie for this topic.

It is obtained from wordnet in nltk package of python.
You could take materials/get_induced_graph.py as reference.
Good luck to your work.


Vscode not import types and values declaration correctly when they are in same file

Does this issue occur when all extensions are disabled?: yes

VS Code Version:
Version : 1.62.0 (user setup)
Commit : b3318bc0524af3d74034b8bb8a64df0ccf35549a
Date : 2021-11-03T15:23:01.379Z
Electron : 13.5.1
Chrome : 91.0.4472.164
Node.js : 14.16.0
V8 : 9.1.269.39-electron.0
OS : Windows_NT x64 10.0.19042

Steps to Reproduce:

create 2 file , examle A.ts and B.ts
add in file A.ts type and concret variable
try import in B.ts , A.ts stuff, and let vscode help you to import stuff, it will not fellow rule correctly.

Hi everyone, is it possible to maybe add a option to separate type and value import correctly, because this give big head hash if we use a ts rule like:
 "importsNotUsedAsValues": "error",
Example if we have 2 file without import:
test1.ts
export type helperA = any;
export const A = "Concret";

test2.ts
export const b:helperA = {};
const x:string = A

And we mouse hover const x:string = A;
Vscode will suggest fix to import value

And vscode will write for you the import, this is perfect and super productive !
result:import { A } from './test1';

After if we mouse over the second declaration
Vscode will suggest import as value in same import declaration

result:import { A, helperA } from './test1';
This is maybe correct but is not what we want if we use rule like
"importsNotUsedAsValues": "error",

Vscode should understand this rule and suggest **add this as type separately **
Expected result:
import { A } from './test1';
import type { helperA } from './test1';

Because actually import type and value in the same import make broken some bundler like vitejs.
Error like
Uncaught SyntaxError: The requested module '/src/core/test1.ts?t=1636477934311' does not provide an export named 'Interpreters'
So i need to always manually change the import made by vscode, where is little waste of time !
or change my rule by  "importsNotUsedAsValues": "remove" where is not what i want !
Here related discutions that's explain this new issue.
https://github.com/evanw/esbuild/issues/1525
https://github.com/microsoft/TypeScript/issues/43393
So to make everything fine, i think if we can maybe add a setting in vscode to say Prefer import type and value separately it will be nice
No more need to hack manually what Vscode suggest when import stuff !
I say add a new option, if for you,  because i dont know this can affect some other pattern of project, but on my side i want keep error, and allowed to import type and concret from same file
(i know it recommend to separate types and values, but it recommend, is not a law !).
thanks

Does this reproduce in the latest VS Code insiders build with TS 4.5+?

Does this reproduce in the latest VS Code insiders build with TS 4.5+?

yep,

if the last vscode is 1.62.0

The current insiders version is 1.63. Please test using it and also make sure the workspace version of TS is 4.5+ (not just tsc)

The current insiders version is 1.63. Please test using it and also make sure the workspace version of TS is 4.5+ (not just tsc)

sry , it taked me time to have a free moment.
I installed Insider and confirm the insider have same behavior with the rule "importsNotUsedAsValues": "error",
Vscode always merge types in values in the same import, and will make crash esBuild.
Tested on
Version: 1.63.0-insider (user setup)
Commit: c1096372119bcf83b9bd8ccee96dcf266f35de76
Date: 2021-11-11T13:18:41.690Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19042

and seem ts 4.5.1-rc

here a little gif also if it can help to understand what i mean with my lack of English 😁

Thanks for all your awesome work !

Thanks for testing. As you note, the way the import is added is fine — and seems preferable in most cases to having two imports for the same file. We generally don't adapt our generic TS behavior to very specific eslint rules like this unless we get significant feedback (and the existing behavior has been in place for a while)
Therefore I'm closing this as by-design


Format Merging Auto Correction

When downloading different formats and merging them, but entering -f someaudio+somevideo, the programme returns: ERROR: The first format must contain the video, try using "-f somevideo+someaudio". If it already "understands" the formats and can offer the alternate form, why can the programme not be run with the alternate form, preserving normal stream order in the merge? :confused:

It would complicate a bit the code, why can't you just use -f somevideo+someaudio?

It wasn't a purposeful use of the argument, I only discovered it after I
ran the program overnight, stopping at the error. I'd just think that this
"problem" could have been avoided...
On Sat, 7 Mar 2015 at 12:17 Jaime Marquínez Ferrándiz <
<EMAIL_ADDRESS>wrote:

It would complicate a bit the code, why can't you just use -f
somevideo+someaudio?
—
Reply to this email directly or view it on GitHub
https://github.com/rg3/youtube-dl/issues/5154#issuecomment-77682771.

From the option help:

You can merge the video and audio of two formats into a single file using -f <video-format>+<audio-format>

So I think it's OK to only support that order.

I strongly disagree with the closing of this bug. The current behavior is extremely user-hostile.
Just ran into this needless annoyance again, for about the 100th time. You see the Terminal lists the audio-only streams first, so naturally I will sometimes input those first.
Essentially the error message is saying "I know what you want to do. I know it will work, because I've already parsed all the formats. I know the exact thing to do to fix the problem. But I (the robot), am going to make you (the human) do some extra work just so you can accomplish what I already know you want."
I submitted the patch above (which imo did not "complicate the code"). It also fixed some bugs (audio+audio/video+video) that weren't fixed yet, and the later fix... complicated the code.
Seriously @jaimeMF, WTF? How is this UI annoyance the least undesirable behavior? "RTFM" is no excuse.

As #6454 is more general than #8157, we'll look at the latter as changing the code one time and solve two problems is better than changing the code two times.


Remove old VC implementation

In 65ebfa64144f3c56d21ecbb3dbee1404d2fe0927, Verifiable Credential encoding for attestations was added to the server API. This was copied from the frontend in uwazi/entity-page/src/lib/vc.js.
To prevent having two implementations some tasks are needed:

[ ] Move tests to backend and make pre-commit hooks use that
[ ] Remove frontend code
[ ] Have frontend use server API for VC export instead

I don't think this really matters that much anymore. The frontend code is not in this repo anymore, and the backend code is not going to change anytime soon.


Improvements to keyboard-only dialog naivgation

I'm submitting a...

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

This issue consists of three sub-issues that are all somewhat related and build on top of each other.
Current behavior

the ngneat-close-dialog div currently doesn't have a tabindex attribute, making it "untabbable" to
even when manually giving the div tabindex="0", it doesn't react to space or enter presses, just clicks
while a dialog is opened, I can still tab into the background, behind the backdrop

Expected behavior

add a tabindex, I used a value of 0 to not fumble with the order. this should maybe be customizable
add corresponding listeners to common "confirm-keys" (I can only think of enter and spacebar rn) to the close icon div
ideally, I should only be able to tab around the dialog's elements

I imagine tihs to be somewhat tricky, in other words, no clue how to approach this

Minimal reproduction of the problem with instructions

go to https://ngneat.github.io/dialog/
press the very first open button (from ng-template)
press tab a bunch of times

this will send you through the elements behind the dialog top to bottom
afterwards, it'll focus the dialog's close button (the <button> at the bottom, not the cross in the top right!)
finally (end of dom), you'll tab somewhere into your browser's window controls until it wraps back around to the start of the page

What is the motivation / use case for changing the behavior?
Better accessibility for people without a mouse, faster controls for power users
Environment

Angular version: 16.0.5

Browser:
- [x] Chrome (desktop) version 114.0.5735.110
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [x] Firefox version 102.12.0esr (64-bit)
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [x] Edge version 114.0.1823.43

For Tooling issues: N/A

Others:

I'm happy to contribute code and could probably figure out the first two points, just not the third one.
Since I feel like these three are best addressed together, I haven't actually written anything.

You're welcome to create a PR


add probes to machine-approver to ensure it is functioning

Currently machine-approver only has a metrics endpoint (no healthz) and no healthchecks on the pod. We need health probes to ensure the program is still functioning for monitoring and availability reasons.
This adds probes to the deployment to ensure it is monitored over time. Later prs if other probes come available can be made to adjust the endpoint being probed.
Details for probe are here:
https://github.com/openshift/cluster-machine-approver/blob/master/pkg/metrics/metrics.go#L13

Thanks!
/lgtm
/approve


Complete monitoring configuration in GKE

rancher/rancher:master
When enabling cluster-level monitoring in GKE, we need to scrap kubelet metrics (AKA. container_** metrics ) from http-metrics endpoint.
We should let the user to config this in enable monitoring page, or we detect GKE ourself :

exporter-kubelets.https should be false when deploying in GKE. Default is true.

It came from https://github.com/rancher/system-charts/pull/8#issuecomment-458446962
reproduce steps:

Create GKE cluster
Enable Monitoring

result:
Go into Prometheus UI, query on Graph page, cannot see any container_** metrics.

Version: Master 2.2 (2/19/19)
Confirmed issue. I am now able to see Workload, Pod, and Container charts.
Smoke tested this; ran a stress test on an ubuntu workload, etc and charts appear to be working correctly.


[Messaging] AMQP transport updates

Summary
The focus of these changes is to update the AMQP transport to unlock support for TLS v1.3 and allow the host to set defaults for send/receive buffer sizes.  Also included are some minor updates to the Service Bus sender docs to clarify whether or not partial success is possible.
References and Related

Atomicity of sending a message batch to a queue (#40409)

/azp run net - eventhub - tests


FloydWarshall in python 3

Description
Added FloydWarshall code in Python
Fixes #1123
Type of change
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings

@Saurabh4626 updated


Google Video search result triggers HTTP 404 Error

Executing a command returning a particular search result throws an exception on Mac OS X, newest version of youtube-dl:
$  youtube-dl --verbose --get-filename --default-search gvsearch2  "large apple"
[debug] System config: []
[debug] User config: [u'--format', u'mp4']
[debug] Command-line args: [u'--verbose', u'--get-filename', u'--default-search', u'gvsearch2', u'large apple']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.09.28
[debug] Python version 2.7.10 - Darwin-14.5.0-x86_64-i386-64bit
[debug] exe versions: avconv 11.4, avprobe 11.4, ffmpeg 2.8, ffprobe 2.8, rtmpdump 2.4
[debug] Proxy map: {}
Pruning a large old apple tree-Qar8TmsobPk.mp4
ERROR: Unable to download XML: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 327, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1865, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 437, in open
    response = meth(req, response)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 550, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 475, in error
    return self._call_chain(*args)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 558, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

In this case it is the second search result from "large apple" that throws the error. Any other search term, or searching for just 1 item shows no error. I can't see what that search result is, so I can only hope your search returns the same results as mine.

A little more data when omitting the --get-filename option. Seems as if the offending link is the Apple Trailers page for "Over the Hedge".
[debug] System config: []
[debug] User config: [u'--format', u'mp4']
[debug] Command-line args: [u'--verbose', u'--default-search', u'gvsearch2', u'large apple']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.09.28
[debug] Python version 2.7.10 - Darwin-14.5.0-x86_64-i386-64bit
[debug] exe versions: avconv 11.4, avprobe 11.4, ffmpeg 2.8, ffprobe 2.8, rtmpdump 2.4
[debug] Proxy map: {}
[video.google:search] gvsearch:large apple: Downloading result page 1
[download] Downloading playlist: large apple
[video.google:search] playlist large apple: Collected 2 video ids (downloading 2 of them)
[download] Downloading video 1 of 2
[youtube] Qar8TmsobPk: Downloading webpage
[youtube] Qar8TmsobPk: Downloading video info webpage
[youtube] Qar8TmsobPk: Extracting video information
[youtube] Qar8TmsobPk: Downloading DASH manifest
[youtube] Qar8TmsobPk: Downloading DASH manifest
[debug] Invoking downloader on u'https://r8---sn-ufuxaxjvh-q4fe.googlevideo.com/videoplayback?id=o-AMz4jcNgHxsDLwKJ-d5sQrvouWQoX5JFKpy4P1K5r_i9&pl=21&mm=31&mn=sn-ufuxaxjvh-q4fe&ms=au&signature=69B2BD3FE1ED91A0DCD323A4A004FBA89E1A6728.843986E9B9862435A3B5222E81AD8D558128978B&mt=1443820766&sparams=dur%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpcm2%2Cpcm2cms%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cupn%2Cexpire&mv=m&ip=<IP_ADDRESS>&pcm2=yes&requiressl=yes&ratebypass=yes&expire=1443842452&sver=3&ipbits=0&dur=469.762&itag=22&mime=video%2Fmp4&lmt=1389259956459837&key=yt6&fexp=9406513%2C9407157%2C9408491%2C9408710%2C9409069%2C9412773%2C9412846%2C9414764%2C9415365%2C9415485%2C9415521%2C9416023%2C9416126%2C9416729%2C9417707%2C9418153%2C9418392%2C9418448%2C9418494%2C9419321%2C9419446%2C9419786%2C9419862%2C9420348%2C9420981%2C9421013%2C9421369%2C9421410%2C9421655%2C9421943&pcm2cms=yes&upn=JGItI3NQtD0&source=youtube&initcwndbps=2691250'
[download] Pruning a large old apple tree-Qar8TmsobPk.mp4 has already been downloaded
[download] 100% of 166.18MiB
[download] Downloading video 2 of 2
[AppleTrailers] overthehedge: Downloading XML
ERROR: Unable to download XML: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 327, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1865, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 437, in open
    response = meth(req, response)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 550, in http_response
    'http', request, response, code, msg, hdrs)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 475, in error
    return self._call_chain(*args)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 409, in _call_chain
    result = func(*args)
  File "/usr/local/Cellar/python/2.7.10_2/Frameworks/Python.framework/Versions/2.7/lib/python2.7/urllib2.py", line 558, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)

Should be fixed since commit 494172d2e5b2d5b6f309b42e1a2bd7108aed40de. Feel free to open new issues if similar problems occur again.


feat: support multiple resolvers on fields

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #3120
Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

@meskill Thanks! This is a great PR. We need to update the docs for each directive here — https://tailcall.run/docs/tailcall-dsl-graphql-custom-directives/

@meskill Thanks! This is a great PR. We need to update the docs for each directive here — https://tailcall.run/docs/tailcall-dsl-graphql-custom-directives/

added documentation here https://github.com/tailcallhq/tailcallhq.github.io/pull/560


fix container cmd args may parsed as ctr args

Signed-off-by: Lifubang<EMAIL_ADDRESS>For ctr t exec:
root@dockerdemo:~/gocode/src/github.com/containerd/containerd# bin/ctr t exec redis echo -e "test"
Incorrect Usage: flag provided but not defined: -e

For ctr run:
root@dockerdemo:~/gocode/src/github.com/containerd/containerd# bin/ctr run docker.acmcoder.com/public/redis:latest redist echo -e "test"
Incorrect Usage: flag provided but not defined: -e

Set SkipArgReorder to true can resolve this problem.

@lifubang it might be confusing to user. It seems that the -e "test" is part of the echo.

@lifubang it might be confusing to user. It seems that the --tty "test" is part of the echo.

I think we don't need -t when test an echo.
root@dockerdemo:~/gocode/src/github.com/containerd/containerd# bin/ctr run docker.acmcoder.com/public/redis:latest redist1 echo -e "test"
test

# vagrant @ ubuntu-xenial in ~ [0:54:00]
$ sudo ctr run --rm docker.io/library/busybox:1.24 t echo -e "hi"
hi

# vagrant @ ubuntu-xenial in ~ [0:54:03]
$ sudo ctr run docker.io/library/busybox:1.24 t echo -e "hi"
Incorrect Usage: flag provided but not defined: -e

NAME:
   ctr run - run a container

USAGE:
   ctr run [command options] [flags] Image|RootFS ID [COMMAND] [ARG...]

OPTIONS:
   --tty, -t            allocate a TTY for the container
   --runtime value      runtime name (io.containerd.runtime.v1.linux, io.containerd.runtime.v1.windows, io.containerd.runtime.v1.com.vmware.linux) (default: "io.containerd.runtime.v1.linux")
   --readonly           set the containers filesystem as readonly
   --net-host           enable host networking for the container
   --mount value        specify additional container mount (ex: type=bind,src=/tmp,dest=/host,options=rbind:ro)
   --env value          specify additional container environment variables (i.e. FOO=bar)
   --label value        specify additional labels (foo=bar)
   --rm                 remove the container after running
   --checkpoint value   provide the checkpoint digest to restore the container
   --cwd value          specify the working directory of the process
   --null-io            send all IO to /dev/null
   --detach, -d         detach from the task after it has started execution
   --snapshotter value  snapshotter name. Empty value stands for the default value. (default: "overlayfs") [$CONTAINERD_SNAPSHOTTER]
   --rootfs             use custom rootfs that is not managed by containerd snapshotter

ctr: flag provided but not defined: -e

The behaviour is weird. And it seems that  we can find other to handle this well. will look at this issue.

Usually when you have flags on docker or whatever, you need to separate the CMD args and the ctr args by --

@fuweid my example may confuse you, there is another example:
root@dockerdemo:~# ctr run docker.io/library/busybox:1.24 t echo "test"
test

so, -t is not need for echo test.
There is another issue before this patch:
root@dockerdemo:~# ctr run docker.io/library/busybox:1.24 t2 echo "test" --rm
test

while echo "test" --rm should be:
root@dockerdemo:~# echo "test" --rm
test --rm

so, --rm parsed not for echo, but for ctr run.
The other project's situation:

docker

root@dockerdemo:~# docker run docker.io/library/busybox:1.24 echo "test" --rm
test --rm

runc

root@dockerdemo:/opt/runctest/redis# runc ps redis -aux
USER       PID %CPU %MEM    VSZ   RSS TTY      STAT START   TIME COMMAND
root      8504  0.0  0.0  17968  2708 ?        Ss   09:17   0:00 /bin/bash /st 28808
root      8513  0.0  0.2  41836  9444 ?        Sl   09:17   0:00 redis-server *:28808
root@dockerdemo:/opt/runctest/redis# runc ps --format json redis -aux
[8504,8513]

I think these issue and example can help you to think about it. Thanks.

Codecov Report

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

@@            Coverage Diff            @@
##           master    #2793     +/-   ##
=========================================
+ Coverage   43.72%   44.02%   +0.3%
=========================================
  Files         100      100
  Lines       10734    10819     +85
=========================================
+ Hits         4693     4763     +70
- Misses       5311     5322     +11
- Partials      730      734      +4

Flag
Coverage Δ

#linux
47.39% <ø> (ø)
:arrow_up:

#windows
40.92% <ø> (+0.03%)
:arrow_up:

Impacted Files
Coverage Δ

runtime/v2/shim/util.go
0% <0%> (ø)
:arrow_up:

remotes/docker/resolver.go
70.29% <0%> (+11.92%)
:arrow_up:

Continue to review full report at Codecov.

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


InstrumentedResourceMethodApplicationListener doesn't accurately track latency with @Suspended AsyncResponse

I'm using metrics included in Dropwizard 0.8.2. Several of my methods are using AsyncResponse to offload long running tasks to another thread pool (in this case the Jersey Client thread pool to pipe the uploaded image to another service) so as to not tie up Jetty threads for long periods of time.
Heroku properly notices that my requests are taking 30 seconds, however my @Timed annotated method metric is reporting an 11ms 99th percentile. The reason for this is that InstrumentedResourceMethodApplicationListener.TimerRequestEventListener only wraps the timer around RESOURCE_METHOD_START and RESOURCE_METHOD_FINISHED. When using @Suspended AsyncResponse parameters, however, the HTTP request isn't necessarily complete when RESOURCE_METHOD_FINISHED is fired.
RequestEvent.Type has some other candidates that I think would be better suited to match on for stopping the timer: RESP_FILTERS_START, RESP_FILTERS_FINISHED, or FINISHED. Which one to choose would depend on how much of the request lifecycle we'd want included in the timer. RESOURCE_METHOD_START means we're already excluding all of the routing and request parsing. If we want to remain consistent with RESOURCE_METHOD_FINISHED and only time the service execution and none of the rendering then switching to RESP_FILTERS_START or RESP_FILTERS_FINISHED would likely suffice.

Yea, there was a similar issue with metrics-servlet recently. I'll try changing the events and see what happens.

Any news on this?
Or are we forced to use a different InstrumentedExecutorService for each call that we want to have timed?

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain plentyproductions.com has exceeded the max emails per hour (205/200 (102%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from github-smtp2-ext3.iad.github.net ([<IP_ADDRESS>]:50947 helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by server21.abstractdns.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1bE6vH-0007HR-AS
for<EMAIL_ADDRESS>Sat, 18 Jun 2016 03:27:51 +0000
Date: Thu, 16 Jun 2016 05:50:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1466081433;
bh=UDIbNB5FGJpu+brXdD5Eu/RJRqKYh9g6b5EPfT+QdYE=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=vOP5AjF9rVRK2O4p+AJWEYFBqj9bPZG6HFkx73YDF1H1diTM4fi5d9Fjz3CVrtiBi
w7mNb0ea0P9RJiovBrN/S1hyG7mZpnegzopJR3cM9eysN50LScsPLX9gjMmSfiE0oG
Roth0wisLPPvsr8t29up9bLKtRWaWzXdFYDFBnPo=
From: Sjoerd Talsma<EMAIL_ADDRESS>Reply-To: dropwizard/metrics<EMAIL_ADDRESS>To: dropwizard/metrics<EMAIL_ADDRESS>Cc:
Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [dropwizard/metrics]
InstrumentedResourceMethodApplicationListener doesn't accurately track latency
with @Suspended AsyncResponse (#838)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_5762a09933e01_a793fa587bed2c01292aa";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: sjoerdtalsma
X-GitHub-Recipient: gtrevg
List-ID: dropwizard/metrics <metrics.dropwizard.github.com>
List-Archive: https://github.com/dropwizard/metrics
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ABA47XGkay7FdDMnrvWQUbECoSKs85Kwks5qMUaZgaJpZM4FemuE
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>----==_mimepart_5762a09933e01_a793fa587bed2c01292aa
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Any news on this?
Or are we forced to use a different InstrumentedExecutorService for each call that we want to have timed?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/dropwizard/metrics/issues/838#issuecomment-226475455
----==_mimepart_5762a09933e01_a793fa587bed2c01292aa
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Any news on this?
Or are we forced to use a different InstrumentedExecutorService for each call that we want to have timed?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_5762a09933e01_a793fa587bed2c01292aa--

+1. Are there any updates on this? :-)

https://bitbucket.org/marshallpierce/jersey2-metrics should measure async responses correctly. I've got a test for it: https://bitbucket.org/marshallpierce/jersey2-metrics/src/326470d2bc4bb8863c535303523816ae897eb81d/jersey2-metrics-core/src/test/java/org/mpierce/jersey2/metrics/FullStackTest.java?at=master&fileviewer=file-view-default#FullStackTest.java-79
It should be pretty easy to drop in instead of the stock Jersey integration. Let me know if it's not :)

why did you tag my username?

Any update on this? @marshallpierce its not working for me :( event type that I am getting is         RESOURCE_METHOD_FINISHED, and its checked as Type.Finished


Remove set but not used variable

reported by clang.
And If I understand the code correctly: this old code (3.01) calculates  gap, but never use it...
https://github.com/tesseract-ocr/tesseract/blob/1569e5080810f4652b720bcd344026a9b236ec50/src/ccmain/control.cpp#L1687-L1698

I wonder whether it would be better to use some variables in (configurable) debug output. Some of them can help to get a better understanding of the code.

No problem for me - I just wanted:

to highlight these variables as they indicate not used/unfinished/not cleaned code
to have a clean build without warnings

https://en.cppreference.com/w/cpp/language/attributes/maybe_unused


Using better app service & app insights integration in Iac project

Better app service & app insights integration. It's connected through an instrumentation key, but they can get connected much better. For example, we can tell app insights our app service is based on the .net 6 web app so it can monitor it better than before.

@msangtarash
please mention what project is this issue for (at least in the title) and also add the appropriate labels to the issue.


How Can I Compile TdLib Independent of Processor Architecture?

Hello
I am using Tdlib on Android on Xamarin.
But I Have a Problem That Each .so File Of Tdlib Represents A Separate Processor Architecture.
arm,arm64,x86, x86_64 vs vs
How Do We Make Them Independent?
It Is Really Difficult To Download .so File According To The Processor Architecture Of User's Device
In short, I need a Tdlib Library Independent of the Processor Architecture.
Urgent!

This is not possible. The correct library version should be chosen automatically when the app is installed on the device.

This is not possible. The correct library version should be chosen automatically when the app is installed on the device.

okay.
Well, can we reduce the size of the .so file to less than 20mb?

No, Unzipped size of arm64-v8a binary is near 20 megabytes. The armeabi-v7a version is 1.5-2 times smaller. Packed size should be a lot smaller.

No, Unzipped size of arm64-v8a binary is near 20 megabytes. The armeabi-v7a version is 1.5-2 times smaller. Packed size should be a lot smaller.

thanks
i am zip the binaries


Can not build/install llama-cpp-python with HIPBLAS/ROCm on Windows

I have 7900xtx GPU, and I've installed ROCm SDK and I followed the instruction to install llama-cpp-python, but it came out a error of "Building wheel for llama-cpp-python (pyproject.toml) did not run successfully".
I tried to figure out the problem, it seems that it picked the wrong C compiler and the CXX compiler to build it. The log is:
 -- Building for: Visual Studio 17 2022
      -- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
      -- The C compiler identification is MSVC 19.37.32824.0
      -- The CXX compiler identification is MSVC 19.37.32824.0
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: C:/Program Files/Microsoft Visual Studio/2022/Community/VC/Tools/MSVC/14.37.32822/bin/Hostx64/x64/cl.exe - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done

 CMake Warning at vendor/llama.cpp/CMakeLists.txt:362 (message):
        Only LLVM is supported for HIP, hint: CC=/opt/rocm/llvm/bin/clang

      CMake Warning at vendor/llama.cpp/CMakeLists.txt:365 (message):
        Only LLVM is supported for HIP, hint: CXX=/opt/rocm/llvm/bin/clang++

However in Windows System, the path of clang.exe and clang++.exe is in the directory
"C:\Program Files\AMD\ROCm\5.5\bin\clang.exe"
But if I setup the "CMAKE_ARGS" using
$env:CMAKE_ARGS = "-DLLAMA_HIPBLAS=on -CC=C:/Program Files/AMD/ROCm/5.5/bin/clang.exe -CXX=C:/Program Files/AMD/ROCm/5.5/bin/clang++.exe"

, the build code cannot get the correct path of the clang.exe and clang++.exe because "Program Files" has the space character. It will print the error like this below:
 2023-12-15 00:38:39,823 - scikit_build_core - WARNING - Can't find a Python library, got libdir=None, ldlibrary=None, multiarch=None, masd=None
      CMake Warning:
        Ignoring extra path from command line:

         "Files/AMD/ROCm/5.5/bin/clang++.exe"

      loading initial cache file C:\Users\xxx\AppData\Local\Temp\tmp8684hemo\build\CMakeInit.txt
      loading initial cache file C=C:/Program
      CMake Error: Not a file: C:/Users/xxx/AppData/Local/Temp/pip-install-igpxs4bu/llama-cpp-python_d279312aff8b4f86847ce3be44ed5b09/C=C:/Program
      CMake Error: Error processing file: C:/Users/xxx/AppData/Local/Temp/pip-install-igpxs4bu/llama-cpp-python_d279312aff8b4f86847ce3be44ed5b09/C=C:/Program
      loading initial cache file XX=C:/Program
      CMake Error: Not a file: C:/Users/xxx/AppData/Local/Temp/pip-install-igpxs4bu/llama-cpp-python_d279312aff8b4f86847ce3be44ed5b09/XX=C:/Program
      CMake Error: Error processing file: C:/Users/xxx/AppData/Local/Temp/pip-install-igpxs4bu/llama-cpp-python_d279312aff8b4f86847ce3be44ed5b09/XX=C:/Program
      -- Building for: Visual Studio 17 2022
      -- Selecting Windows SDK version 10.0.22621.0 to target Windows 10.0.22631.
      -- The C compiler identification is MSVC 19.37.32824.0

So is that a bug? Or Is there a better solution to avoid that?

Can't you put the file path into single quotes? I have never built using Windows though.

@EndEdge did @m-from-space suggestion work for you? I also noticed that HIPBLAS was temporariy broken in llama.cpp but should be fixed now, let me know if you're still encountering this issue.
Cheers

Well, I have used your code to built llama-cpp myself and put your source code in my project then it can work on windows, but the efficiency is very low, maybe ROCm is not supported well on Windows. So I decide to change to Linux. I will close this issue. Thank you for your response.


Add PUNS

Plugin Update Notification System

Neat idea !!
Haven't tried the plugin but a quick glance at your code shows that you're including CSS and JS from a hardcoded path (/css/yada.css and /js/yada.js) which isn't going to work on install in a folder instead of root. You should be using something like:
<script src="<?php yourls_site_url(); ?>/js/yada.js?v=<?php echo YOURLS_VERSION; ?>" type="text/javascript"></script>
(see function yourls_html_head() in functions-html.php)

thanks for the tip, updated. I'm wondering if it would be appropriate to update the plugin docs with some information regarding versioning? It would be great to see something like this standardized?

Definitely!


Adding recipe model to tasties.

Adding recipe model to tasties app.
Add a delete and edit methods to the recipe model.
Adding a test for the recipe model and for the methods.
This PR relies on #43
Close #38

check you'r PyTest.


⚠ Adacta-fintech.com has degraded performance

In 7afe738, Adacta-fintech.com (https://www.adacta-fintech.com) experienced degraded performance:

HTTP code: 200
Response time: 863 ms

Resolved: Adacta-fintech.com performance has improved in dfaeedb.


debian 11 duplaceted rules after restart

after stop start a container rules added twice which prevent forwarding
after stopping a container I need to do  nft flush ruleset and start container.

Yes, I see a similar problem in Debian 11. I'll try to figure it out later.

the issue seems to be incomplete cleanup of rules it creates.

@thefiredragon , @AlekseyMelikov , @vrga , PRs are welcomed!


x/pkgsite: github.com/vbsw/cmdl not found

What is the URL of the page with the issue?
https://github.com/golang/go/issues/new?title=x/pkgsite:&body=<!--Please+answer+these+questions+before+submitting+your+issue.+Thanks!-->+###+What+is+the+URL+of+the+page+with+the+issue?+++###+What+is+your+user+agent?+<!--+You+can+find+your+user+agent+here:https://www.whatismybrowser.com/detect/what-is-my-user-agent-->+++###+Screenshot+<!--Please+paste+a+screenshot+of+the+page.-->+++###+What+did+you+do?+<!--If+possible,+provide+a+recipe+for+reproducing+the+error.-->+++###+What+did+you+expect+to+see?+++###+What+did+you+see+instead?
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.107 Safari/537.36
Screenshot

What did you do?
I created go package "github.com/vbsw/cmdl". The file go.mod was wrong. I deleted this package on github.com and created it again.
I call in my browser the page: https://pkg.go.dev/github.com/vbsw/cmdl
What did you expect to see?
I expect to see the documentation for my package on https://pkg.go.dev/github.com/vbsw/cmdl
Like for my other package on gitLAB, see: https://pkg.go.dev/gitlab.com/vbsw/cmdl
What did you see instead?
I see the error: "github.com/vbsw/cmdl" could not be found.

The problem is that once the Go module proxy learns about a version, it will never forget it. So the v1.0.0 that the proxy has is the old one, with the wrong go.mod. Just tag the current commit v1.0.1 or anything over v1.0.0, then go get it, and it should be fine.
Closing, but reopen if the problem continues.


Fix WebCmdlets bug -WebSession -AllowInsecureRedirect -MaximumRedirection together wrong number of redirections

PR Summary
The WebSession.MaximumRedirection parameter shouldn't change as we handle redirections.
This bug appears in edge cases when we use -WebSession -AllowInsecureRedirect -MaximumRedirection together.

PR Context
Fix #19183

PR Checklist

[ ] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[ ] Summarized changes
[ ] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[ ] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[ ] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[ ] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and opened an issue in the relevant tool repository. This may include:

[ ] Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode
(which runs in a different PS Host).

[ ] Issue filed:

[ ] Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.

[ ] Issue filed:

[ ] Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).

[ ] Issue filed:

[ ] Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[ ] Issue filed:

@CarloToso I suggest don't modify existing test and add new one - create WebRequestSession $session = [WebRequestSession]::new(), assign properties, iwr -WebSession $session and check that properties are unchenged.

@CarloToso Please update the PR title and description.


Add studyDesign property and StudyDesign class

The diagram contains a "studyDesign" property and a "StudyDesign" class but we don't have those in our ontology yet.
I can add them but want to know more about them first, do we have predefined instances for the study design class?

Discussed with @vdornauer and @FranziskaJahn on 2021-05-26, decision: Remove both.


Method decorator compile error while lua ouput seems right

Environment

  "devDependencies": {
    "lua-types": "^2.13.1",
    "typescript": "^5.1.3",
    "typescript-to-lua": "^1.16.2"
  }

TS still compile error.

while output seems right.

Your TypeScript is incorrect, that is why you are getting a TypeScript error. This is not related to TSTL.
Example with correct TypeScript code: https://typescripttolua.github.io/play#code/GYVwdgxgLglg9mABAEwKYTgJwIZSwHgGEAbbAZzID4AKKbTAc1SgC5ETyyAaRDMKVAA9W7UhQCyzABZxkAEXRZcWQggHCAlGwBucGMkQBvAFCIziAA6YY-agCI0AIxANes1HY3GAvseMQxMkQAMTg4I1NzAAE0DBw8TEizCxBHYhgIRABbaVkAJmoNI0RMZhBMJAAWAG5EX28gA


Admin Notice for Conflict with Future Discourse Update

I got an admin notice on my site using this plugin today referencing an issue with future Discourse upgrades
https://meta.discourse.org/t/preparing-for-discourses-upgrade-to-ember-5/287211
The info I see in my console is

l @ deprecated.js:54
deprecated.js:54 [THEME 24 'discourse-social-links-clickable'] Deprecation notice: Defining connector classes via registerConnectorClass is deprecated. See https://meta.discourse.org/t/32727 for more modern patterns. [deprecation id: discourse.register-connector-class-legacy]
l @ deprecated.js:54
deprecated.js:54 [THEME 24 'discourse-social-links-clickable'] Deprecation notice: Defining connector classes via registerConnectorClass is deprecated. See https://meta.discourse.org/t/32727 for more modern patterns. [deprecation id: discourse.register-connector-class-legacy]
l @ deprecated.js:54
plugin-api.js:154 [THEME 24 'discourse-social-links-clickable'] To prevent errors in tests, add a pluginId key to your modifyClass call. This will ensure the modification is only applied once.
je @ plugin-api.js:154

Also getting this and noticed in addition it broke my Admin user pages (though not other users), only the very initial header displayed, no page content or admin menu or anything.

Same problem everywhere. See here for error message:
https://meta.discourse.org/t/clickable-social-icon-links-on-profile/158136/59

Check out this merged PR!
https://github.com/weallwegot/discourse-social-links-clickable/pull/16


Update URL for Screen Wake Lock API

Fixes https://github.com/tidoust/reffy/issues/303.

Closing without merging as the update should no longer be needed, see discussion in #303.


[Chocolatey Package] Could we add bazelisk to PATH as bazel?

@digitalcoyote, I super appreciate your Chocolatey package for Bazelisk--as someone now booting up on Windows after working with Bazel on macOS and Linux.
Could I ask you if, by any chance, you'd be willing to have the package (additionally) add Bazelisk to the PATH as bazel? That's a super handy feature on other platforms that makes it easy to use as a drop-in replacement.
Thanks so much for your consideration and all you've done.
Chris

(That is, during install cmd: mklink C:\ProgramDatachocolatey\bin\bazel.exe C:\ProgramDatachocolatey\bin\bazelisk.exe)

Thanks so much for working on this, Curtis! Will definitely make things extra awesome. Sorry if I should have filed it over in digitalcoyote/chocolatey-packages
No pressure to respond, but this Windows newbie is curious what went into choosing a hard link (vs soft). (I know things are different over in windows-land.)

Honestly, I just default to hard links anytime I'm on the same drive ever since I read an article about some Windows utilities having issues following soft links.

Okey
31 Mart 2022 Perşembe tarihinde Curtis Carter @.***>
yazdı:

Honestly, I just default to hard links anytime I'm on the same drive ever
since I read an article about some Windows utilities having issues
following soft links.
—
Reply to this email directly, view it on GitHub
https://github.com/bazelbuild/bazelisk/issues/311#issuecomment-1084444990,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ANILBIEIKZLGA7NMEXWWTGDVCWDGHANCNFSM5SA7WBVA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
Cevdet Bayram

Pushed a fix version to chocolatey (has today's date appended to the bazelisk version) that should include bazel on the path.

Thank you again!
From https://community.chocolatey.org/packages/bazelisk, it looks like it's already available! (That is the review process, right?)
Before closing, I'll toss up a quick PR to document the choco support so more people can use and find it!


Capitalise first letter of all messages

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
ClusterAdmissionPolicies, among others, show messages in which the first letter is lowercase.
Expected Behavior
The first letter should be capitalized
Steps To Reproduce
No response
Environment
- OS:
- Architecture:

Anything else?
No response

@kwwii Can you give some examples of where the messages are located? The only ones that come to mind are the messages returned from Jaeger in the Tracing tabs, am I missing any?

The only place I noticed this was the red text that appears in the jaeger tracing messeges. Not sure if it happens anywhere else, but I haven't seen it

https://github.com/rancher/dashboard/commit/d1a89fe1f24fcfcbac20f4870958def1c9756d1a

The response message that is returned from Jaeger will now be capitalized.


mockbuild: use public EPEL-9

This pull request includes:

[ ] adequate testing for the new functionality or fixed issue
[ ] adequate documentation informing people about the change such as

[ ] submit a PR for the guides repository if this PR changed any behavior described there: https://www.osbuild.org/guides/

I'm not sure if we need the mock templates. When I added centos-9 runner in osbuild repository it wasn't needed... https://github.com/osbuild/osbuild/pull/974 Should I remove them?

CS9 mock templates are shipped in mock-core-configs, RHEL 9's are not yet (I guess they are waiting for GA).
my fedora 35 $ ls /etc/mock/ | grep centos-stream-9
centos-stream-9-aarch64.cfg
centos-stream-9-ppc64le.cfg
centos-stream-9-s390x.cfg
centos-stream-9-x86_64.cfg

CS9 mock templates are shipped in mock-core-configs, RHEL 9's are not yet (I guess they are waiting for GA).
my fedora 35 $ ls /etc/mock/ | grep centos-stream-9
centos-stream-9-aarch64.cfg
centos-stream-9-ppc64le.cfg
centos-stream-9-s390x.cfg
centos-stream-9-x86_64.cfg

Ok I've just remove the centos-stream-9 ones.

Huh, since when this is a thing? ERROR    Libvirt version does not support UEFI. It's in all the failed jobs.


Invoking "make -j8 -l8" failed

Hello everyone!
I encountered an error while trying to compile (./catkin_make_release). Compiling reaches around 73% and just stop.
[ 73%] Building CXX object computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/gpu/dt_GPU.cpp.o
[ 73%] Building CXX object computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/gpu/multithreading.cpp.o
[ 73%] Building CXX object computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/gpu/get_boxes.cpp.o
/home/strax90/Autoware/ros/src/computing/perception/detection/vision_detector/libs/dpm_ttic/gpu/get_boxes.cpp: In function ‘FLOAT* dpm_ttic_gpu_get_boxes(FLOAT**, FLOAT*, int*, GPUModel*, int*, FLOAT*, FLOAT)’:
/home/strax90/Autoware/ros/src/computing/perception/detection/vision_detector/libs/dpm_ttic/gpu/get_boxes.cpp:1226:34: error: call of overloaded ‘abs(FLOAT&)’ is ambiguous
FLOAT abs_threshold = abs(thresh);
^
In file included from /usr/include/c++/6/cstdlib:75:0,
from /usr/include/c++/6/bits/stl_algo.h:59,
from /usr/include/c++/6/algorithm:62,
from /home/strax90/Autoware/ros/src/computing/perception/detection/vision_detector/libs/dpm_ttic/gpu/get_boxes.cpp:6:
/usr/include/stdlib.h:774:12: note: candidate: int abs(int)
extern int abs (int __x) __THROW attribute ((const)) __wur;
^~~
In file included from /usr/include/c++/6/bits/stl_algo.h:59:0,
from /usr/include/c++/6/algorithm:62,
from /home/strax90/Autoware/ros/src/computing/perception/detection/vision_detector/libs/dpm_ttic/gpu/get_boxes.cpp:6:
/usr/include/c++/6/cstdlib:180:3: note: candidate: long long int std::abs(long long int)
abs(long long __x) { return __builtin_llabs (__x); }
^~~
/usr/include/c++/6/cstdlib:172:3: note: candidate: long int std::abs(long int)
abs(long __i) { return __builtin_labs(__i); }
^~~
computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/build.make:566: recipe for target 'computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/gpu/get_boxes.cpp.o' failed
make[2]: *** [computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/gpu/get_boxes.cpp.o] Error 1
CMakeFiles/Makefile2:15275: recipe for target 'computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/all' failed
make[1]: *** [computing/perception/detection/vision_detector/libs/dpm_ttic/CMakeFiles/libdpm_ttic.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 73%] Building CXX object util/packages/autoware_rviz_plugins/CMakeFiles/autoware_rviz_plugins.dir/autoware_rviz_plugins_automoc.cpp.o
[ 73%] Linking CXX shared library /home/strax90/Autoware/ros/devel/lib/libautoware_rviz_plugins.so
[ 73%] Built target autoware_rviz_plugins
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j8 -l8" failed
Specifications

Ubuntu version: 16.04.
ROS version: Kinetic
Autoware branch: Master

Anyone has an idea what is wrong?
Thank you
Strahinja

Did you do "rosdep" to clear out all dependency?

@4n00815 seems you're not using Ubuntu 16.04 standard compiler (gcc 5.4).
Try downgrading, otherwise you'll be required to fix this kind of errors.
Please, reopen if you need extra help.

@wmpang I've done that before catkin_make
@amc-nu You are right, I was using version 6.4. When i try to compile with version 5.5 I got following error:
[  1%] Building CXX object sensing/drivers/lidar/packages/hokuyo/CMakeFiles/hokuyo_3d.dir/nodes/hokuyo_3d/hokuyo_3d.cpp.o
92 errors detected in the compilation of "/tmp/tmpxft_00000f82_00000000-6_NormalDistributionsTransform.cpp1.ii".
[  1%] Built target adis16470_node
Scanning dependencies of target image_rectifier
CMake Error at ndt_gpu_generated_NormalDistributionsTransform.cu.o.cmake:266 (message):
Error generating file
/home/strax90/Autoware/ros/build/computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/src/./ndt_gpu_generated_NormalDistributionsTransform.cu.o
computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/build.make:77: recipe for target 'computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/src/ndt_gpu_generated_NormalDistributionsTransform.cu.o' failed
make[2]: *** [computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/src/ndt_gpu_generated_NormalDistributionsTransform.cu.o] Error 1
CMakeFiles/Makefile2:2160: recipe for target 'computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/all' failed
make[1]: *** [computing/perception/localization/lib/ndt_gpu/CMakeFiles/ndt_gpu.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[  1%] Building CXX object sensing/filters/packages/image_processor/CMakeFiles/image_rectifier.dir/nodes/image_rectifier/image_rectifier_node.cpp.o
[  1%] Linking CXX executable /home/strax90/Autoware/ros/devel/lib/vectacam/vectacam_node
[  1%] Linking CXX executable /home/strax90/Autoware/ros/devel/lib/fake_drivers/fake_camera
[  1%] Built target vectacam_node
[  1%] Linking CXX shared library /home/strax90/Autoware/ros/devel/lib/libfastvirtualscan.so
[  1%] Built target fake_camera
[  1%] Built target fastvirtualscan
[  1%] Built target pcl_omp_registration
[  1%] Linking CXX executable /home/strax90/Autoware/ros/devel/lib/image_processor/image_rectifier
[  1%] Built target image_rectifier
[  1%] Linking CXX executable /home/strax90/Autoware/ros/devel/lib/garmin/garmin_gps_18x_lvc
[  1%] Built target garmin_gps_18x_lvc
[  1%] Linking CXX executable /home/strax90/Autoware/ros/devel/lib/hokuyo/hokuyo_3d
[  1%] Built target hokuyo_3d
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j8 -l8" failed
Version 5.4 was upgraded to 5.5 during ROS installation for some reason, and I couldn't avoid that.
Thank you for your replies.

Solved by downgrading GCC version to 5.4.
Thank you everyone for help!


Update to kernel 5.4.49

Superseded by https://github.com/balena-os/balena-intel/pull/338

Superseded by https://github.com/balena-os/balena-intel/pull/338