Docker-squash not properly working

With the command docker save d5b63701456a | sudo /usr/local/bin/docker-squash -verbose -t test:squashed | docker load I don't get any new images, though there's no error.
Output:
Loading export from STDIN using /tmp/docker-squash299353940 for tempdir
Loaded image w/ 13 layers
Extracting layers...
  -  /tmp/docker-squash299353940/f3376dbeb3b0e4f36439bca922ec3cd370ef05c5243a37f038170716d556aeb3/layer.tar
  -  /tmp/docker-squash299353940/09967547b5df888f5e066a52d72526b1c68f6837e216799c91c26499dd42c6a7/layer.tar
  -  /tmp/docker-squash299353940/457485a3a84745e213bbb7fc065eacc2826c1d0dacc8743dcb47383b9140b248/layer.tar
  -  /tmp/docker-squash299353940/a238fce9a846a5209b8c1d0bc4c620b4cac48fb512c5b391f4bc655a80b3aa79/layer.tar
  -  /tmp/docker-squash299353940/a4d961cdf6bb153d27f8f58f8e2eaec75241ac60e51dd39aecbc34f2164db202/layer.tar
  -  /tmp/docker-squash299353940/ac03b9ff3e20837ea0e0095e093ee76c8bcffc18fb29ce5d70cc317c67129cef/layer.tar
  -  /tmp/docker-squash299353940/b13b4991fd92f5c3f893ec70993dca32bdc80785030e538b575fa68612a9c4e9/layer.tar
  -  /tmp/docker-squash299353940/bf6a503f7a3e7527729622ed72da1999d3d8b5a674ba3e18cd4ef1e01d1b5c97/layer.tar
  -  /tmp/docker-squash299353940/f30d7a68d1426e11ddea1ea508144e78cd1581f2aa710a28bc1157da72d659bb/layer.tar
  -  /tmp/docker-squash299353940/15ca8d025fb12dd0390b50364bf71b5573ba07a4d92d266cf23b7c3c29a87e4b/layer.tar
  -  /tmp/docker-squash299353940/17215e1d258f4f6306eec1764f142fc4fd3cf85d050a88b1580e16ae98626cb6/layer.tar
  -  /tmp/docker-squash299353940/3b5667d6dbc444eb8baaac05ca46bdc18f6d872d0c8d899b9064749a1cbe80f0/layer.tar
  -  /tmp/docker-squash299353940/626f3bd3ed630a7876e2f1f002b7ea8a4020cacf3e0319498831ee2c604c6ee7/layer.tar
Inserted new layer 4455bd2b5c88 after 15ca8d025fb1
  -  15ca8d025fb1
  -> 4455bd2b5c88 /bin/sh -c #(squash) from 15ca8d025fb1
  -  3b5667d6dbc4
  -  626f3bd3ed63
  -  17215e1d258f
  -  ac03b9ff3e20
  -  bf6a503f7a3e
  -  457485a3a847
  -  f3376dbeb3b0
  -  a238fce9a846
  -  b13b4991fd92
  -  a4d961cdf6bb
  -  09967547b5df
  -  f30d7a68d142 /bin/sh -c #(nop) CMD ["/bin/sh" "-c" "node /srv/node/Centra
Squashing from 4455bd2b5c88 into 4455bd2b5c88
  -  Deleting whiteouts for layer 3b5667d6dbc4
  -  Deleting whiteouts for layer 626f3bd3ed63
  -  Deleting whiteouts for layer 17215e1d258f
  -  Deleting whiteouts for layer ac03b9ff3e20
  -  Deleting whiteouts for layer bf6a503f7a3e
  -  Deleting whiteouts for layer 457485a3a847
  -  Deleting whiteouts for layer f3376dbeb3b0
  -  Deleting whiteouts for layer a238fce9a846
  -  Deleting whiteouts for layer b13b4991fd92
  -  Deleting whiteouts for layer a4d961cdf6bb
  -  Deleting whiteouts for layer 09967547b5df
  -  Deleting whiteouts for layer f30d7a68d142
  -  Rewriting child history
  -  Removing 3b5667d6dbc4. Squashed. ()
  -  Removing 626f3bd3ed63. Squashed. ()
  -  Removing 17215e1d258f. Squashed. ()
  -  Removing ac03b9ff3e20. Squashed. ()
  -  Removing bf6a503f7a3e. Squashed. ()
  -  Removing 457485a3a847. Squashed. ()
  -  Removing f3376dbeb3b0. Squashed. ()
  -  Removing a238fce9a846. Squashed. ()
  -  Removing b13b4991fd92. Squashed. ()
  -  Removing a4d961cdf6bb. Squashed. ()
  -  Removing 09967547b5df. Squashed. ()
  -  Replacing f30d7a68d142 w/ new layer 9d2df5ab1cca (/bin/sh -c #(nop) CMD ["/bin/sh" "-c" "node /sr...)
Tarring up squashed layer 4455bd2b5c88
Removing extracted layers
Tagging 9d2df5ab1cca as test:squashed
Tarring new image to STDOUT
Done. New image created.
  -  15ca8d025fb1 292.471209 years  130.9 MB
  -  4455bd2b5c88 26 seconds /bin/sh -c #(squash) from 15ca8d025fb1 640.8 MB
  -  9d2df5ab1cca 16 seconds /bin/sh -c #(nop) CMD ["/bin/sh" "-c" "node /srv/node/Cen... 70.64 MB
Removing tempdir /tmp/docker-squash299353940

When docker-squashing into an output file and trying to load it from that, I get the following error:
$ docker load -i squashed.tar Error response from daemon: open /var/lib/docker/tmp/docker-import-102261036/7dc29a8f47df2223a335cd818b446df8cdde86863a46c13a18211916eb5a759c/layer.tar: no such file or directory
I'm using SLES 12 SP 1 Docker version 1.10.3
Any ideas?

+1
I have the same issue

+1

+1 same issue  docker images doesn't  show new squashed image

+1 here, not getting anything after shashing.
docker save IM_ID | sudo docker-squash -from root -t me/repo:tag | docker load
Loaded image ID: sha256:IM_IDnumbers

Same issue (docker images doesn't show new squashed image), and the command given in https://github.com/jwilder/docker-squash/issues/53#issuecomment-222045035 worked fine for me.
tar --delete -f squashed.tar manifest.json

same issue for me (running on mac os).
I do the piped commands:    save..  | sudo  docker-squash... | docker load
works without errors
but 'docker images'   does not show new image.
If it type docker images <id from end of docker load command, after sha256: >  no images

Same issue for me.  There are no errors in the squashing process.   After completion  docker images does not show any new images.   I have tried step by step (save, squash, load) and piped (save | squach | load) same result.   I have tried several different images and have not yet been able to see a squashed image in docker image repo.   Here is my docker version:
Docker version 1.12.1, build 23cf638
[

Same issue for me, whether using the piped commands or the individual commands separately.

Has this project been abandoned? I am also having the same issue.

Having same problem. Not an expert, but it seems docker load is importing actually saved imaged not squashed.
docker save ab4e6a73e308 | sudo TMPDIR=/home/finch/tmp docker-squash -t ubuntu-xenial-build-essential:squash -verbose -from root | docker load

Output
Tagging 5adf140b9b41 as ubuntu-xenial-build-essential:squash
Tarring new image to STDOUT
Done. New image created.
  -  561dcc9b249f 47.499343 years  132.8 MB
  -  5adf140b9b41 3 seconds /bin/sh -c #(squash) from 561dcc9b249f 303.4 MB

Loaded image ID: sha256:ab4e6a73e3081be5d0decd163ab4034bdb33e5b5a7c72d35f8ec9d5bb2b93476

As you can see sha of loaded image is same as exported image (docker save ab4e6a73e308 ...), but IMHO it should be 561dcc9b249f.
Could it be that unix pipe is broken somewhere, so instead of result of docker-squash | docker-load, docker save is actually piped (docker save ab4e6a73e308 | broken pipe | docker load ?

Docker changed how it calculated layer IDs in 1.10: https://blog.docker.com/2016/01/docker-1-10-rc/
docker-squash was built using the original version and broken around this time.  I haven't had time to update the project to use the new hashing model.  There was a start to fix this in #55, but it's not complete.
Docker has added experimental squash support as  docker build --squash. See announcement.  Also, the multi-stage build support recently introduced will also make squashing less necessary.

Thanks for the update.
tom
  From: Jason Wilder<EMAIL_ADDRESS>
To: jwilder/docker-squash<EMAIL_ADDRESS>Cc: ppridge<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Sent: Thursday, June 22, 2017 12:06 PM
Subject: Re: [jwilder/docker-squash] Docker-squash not properly working (#65)
Docker changed how it calculated layer IDs in 1.10: https://blog.docker.com/2016/01/docker-1-10-rc/docker-squash was built using the original version and broken around this time. I haven't had time to update the project to use the new hashing model. There was a start to fix this in #55, but it's not complete.Docker has added experimental squash support as docker build --squash. See announcement. Also, the multi-stage build support recently introduced will also make squashing less necessary.—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.


grug-far  Not Automatically Filling Project Root Path

Bug Report
Description
When invoking the grug-far plugin with the <leader>sr keybinding, the path parameter is not being automatically filled with the project root. Despite passing the correct path to the grug_far function, the plugin does not seem to recognize or utilize the provided path.
Environment

Neovim version: NVIM v0.10
grug-far version: Latest,installed via lazyvim
OS: Fedora 40

Steps to Reproduce

Install and configure grug-far plugin as described in the README.

Add the following keybinding to grug-far.lua:
return {
  "MagicDuck/grug-far.nvim",
  opts = { headerMaxWidth = 80 },
  cmd = "GrugFar",
  config = function()
    require('grug-far').setup({
      -- Any global configuration options
    })
  end,
  keys = {
    {
      "<leader>sr",
      function()
        local grug = require("grug-far")
        local ext = vim.bo.buftype == "" and vim.fn.expand("%:e") or nil
        local project_root = vim.fn.systemlist("git rev-parse --show-toplevel")[1]

        if project_root == "" then
          project_root = vim.fn.getcwd()
        end

        vim.notify("Final Project Root: " .. project_root, vim.log.levels.INFO)

        grug.grug_far({
          transient = true,
          prefills = {
            filesFilter = ext and "*." .. ext or nil,
            path = project_root,
          },
        })

        vim.notify("Calling grug_far with: " .. vim.inspect({
          transient = true,
          prefills = {
            filesFilter = ext and "*." .. ext or nil,
            path = project_root,
          },
        }), vim.log.levels.INFO)
      end,
      mode = { "n", "v" },
      desc = "Search and Replace",
    },
  },
}

Open Neovim in a project with a Git repository.

Trigger the keybinding <leader>sr.

Observe that the path parameter is not correctly set to the project root.

Expected Behavior
The grug-far plugin should automatically use the provided path parameter as the root for search and replace operations.
Actual Behavior
The path parameter does not seem to be utilized, resulting in the plugin not searching in the intended project root directory.
Debug Information

The following debug messages confirm that the path parameter is correctly calculated and passed to the grug_far function:
Final Project Root: /home/user/project
Calling grug_far with: {
  transient = true,
  prefills = {
    filesFilter = "*.rs",
    path = "/home/user/project"
  }
}

The project root is correctly determined using git rev-parse --show-toplevel and falls back to vim.fn.getcwd() if necessary.

@arthur19q3 its paths not path
  prefills = {
    filesFilter = "*.rs",
    paths = "/home/user/project"
  }

@choovick  is correct!
Always make sure to double-check the options here:
https://github.com/MagicDuck/grug-far.nvim/blob/16091184639ca7f2c76734e3a8641d388aebc4e7/lua/grug-far/opts.lua#L155
Also recommend you install https://github.com/folke/lazydev.nvim, that way you get auto-complete:

okk, that was a typo. just have fixed it. thx.


Fix BM25Tokenizer to correctly handle tokenization language

Problem
The word_tokenize function has a language parameter, which defaults to 'english'. However, when this function is called within the BM25Tokenizer, the language parameter is not passed, so it always defaults to 'english', even if self.language is set to a different value.
Solution
Added self.language to the arguments of word_tokenize in the BM25Tokenizer class.
Type of Change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Infrastructure change (CI configs, etc)
[ ] Non-code change (docs, etc)
[ ] None of the above: (explain here)

Test Plan
Describe specific steps for validating this change.

@acatav is this repo still maintained? Is there an alternative you would recommend switching to?


[Bug]: Admin Settings: Unable to edit the Translation section for receivers

Contact Details
No response
What happened?
From Jorge:
"Unable to edit the translation section. I was unable to type in the box, but I was able to use backspace to delete."
At the time of the bug bash, I was able to repro this but am unable to now.

Version
1.0.2 (Default)
What browsers are you seeing the problem on?
Chrome
Relevant log output
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

hey gang! I believe I had made a quick fix since @jorg3lopez found this bug at the Bug Bash, and thus it's not reproducible. However I used this opportunity to better drill into some of the other general weirdness that was encountered on similar JSON textareas, and found that 1) wow, I'd really happy-pathed this Receiver edit screen and 2) each of these fields seem to have their own little built-in rules/behavior about what's valid and what's not from the API perspective:

"translation" straight up can not be null or empty- period.
all the filters ("jurisdictionalFilter","qualityFilter","routingFilter","processingModeFilter") must have brackets ([ ])- either with valid list items, or simply "[]" to denote that it's blank. Sending in "" or null to indicate blank is invalid
"timing" must be "{ with some valid json}" or null to denote that it's blank. Sending in just "{}" passes validation, but it does NOT blank out the field
"transport" is like the "timing" field, except that sending in "{}" FAILS validation

I haven't drilled into the top-level org filter or the (upcoming) sender "keys" fields, but I'm guessing that they will have their own peccadillos. I'm just detailing this right now to start a conversation more than anything, but generally this is all a bit problematic to account for on the React side of things. It would be nice if all these types of fields were treated consistently. Thoughts?
@MauriceReeves-usds @TomNUSDS @jimduff-usds @meckila

Created #4476 to house these API peccadillos


Fix #141 "Loader::raster_bounds" to work as intended.

This fixes issue #141, so that Loader::raster_bounds actually returns tight raster bounds.
Previously, it returned distorted bounds due to usage of "RectF::set_origin_y"
which does not preserve Rect size.

Can you add a test as well?

@jrmuizel I can surely try my best, can you please recommend what's an appropriate test for this use case?
For example, I could test that size of the rect with size 1.0 is comparable to the size of typographic_bounds(), but that would not test the actual origin.
Or I could just hard-code some expected raster_bounds for a sample glyph from a sample font - but then which font should I use?
Also this method is on the trait, but it's not used on Windows, so how should I go about testing on other platforms? (I only have a mac)
Thanks

You can probably just hard code the expected bounds for a sample glyph of Inconsolata or EBGaramond12 which are already in the repository. The existing tests in src/test.rs make use of them and you should be able to just do something similar.

@jrmuizel ready for review

@jrmuizel @pcwalton just checking if there's anything I need to update here for this to be good enough to merge


Problems while building from source: electron-mksnapshot error

VSCode Version: master commit e489a70
OS Version: Ubuntu 18.10

Steps to Reproduce:

clone repository
execute yarn

vscode on  master is 📦 v1.29.0 via ⬢ v8.11.4
➜ yarn
yarn install v1.10.1
$ node build/npm/preinstall.js
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] 🔗  Linking dependencies...
warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>[4/4] 📃  Building fresh packages...
[10/13] ⠈ vscode-sqlite3
[12/13] ⠈ electron-mksnapshot
[8/13] ⠈ vscode-nsfw
[11/13] ⠈ oniguruma
error /home/vharabar/Work/vscode/node_modules/electron-mksnapshot: Command failed.
Exit code: 1
Command: node ./download-mksnapshot.js
Arguments:
Directory: /home/vharabar/Work/vscode/node_modules/electron-mksnapshot
Output:
/home/vharabar/Work/vscode/node_modules/electron-mksnapshot/download-mksnapshot.js:16
  if (error != null) throw error

try again after a git clean (git clean -xfd) and otherwise report an issue against electron-mksnapshot. Thanks


request for discussion: package_override branch

Apologies if I've used the wrong approach for this experiment. None-the-less...
I just pushed a new branch package_override containing a proposal for extending make_gdl (and, if we like the idea, make_fea and make_volt) in such a way as to allow users to override individual methods within the GDL.pm library.
The use case that motivated this experiment is a desire to override the make_name() method for a unicameral script project where all of the inserted underscores to preserve the case distinctions are unnecessary (besides being annoying).
There may be better ways to code the package handling so I'm open to proposals. If we can come to agreement on the best practice, I will implement the same on make_volt and make_fea.

I've incorporated these same idea into make_fea of the package_override branch, and then merged package_override into the master branch. So the --package option is now available for both make_gdl and make_fea.


Status of istio pods are Pending after installation

Describe the bug
After install istio (tried both 1.0.0 release version and 1.1.0 pre-release) on kubernetes cluster environemnt, pods status are in pending status rather than ready, tried several times, got the same result.
Expected behavior
Istio pods are in ready status.
Steps to reproduce the bug

Install docker ce on three vmware machines (centos 7.4 minimal)
Install k8s using kubeadm on those vm machines. They are HA clusters, each of them work as master node and work node.
Install Istio     kubectl create -f  install/kubernetes/istio-demo.yaml
Check pods status kubectl get pods -owide --all-namespaces
NAMESPACE      NAME                                      READY     STATUS    RESTARTS   AGE       IP                NODE
istio-system   grafana-6f5678c94b-fvn95                  0/1       Pending   0          7m
istio-system   istio-citadel-8b8f7f5f-blwk6              0/1       Pending   0          7m
istio-system   istio-cleanup-secrets-kmzrq               0/1       Pending   0          7m
istio-system   istio-egressgateway-7f7946446-8ff4g       0/1       Pending   0          7m
istio-system   istio-galley-59656667f-kw75r              0/1       Pending   0          7m
istio-system   istio-grafana-post-install-52tw8          0/1       Pending   0          7m
istio-system   istio-ingressgateway-5b9697f89-z9j74      0/1       Pending   0          7m
istio-system   istio-pilot-6f9c54b455-bsfn9              0/2       Pending   0          7m
istio-system   istio-policy-694cd867db-n92dw             0/2       Pending   0          7m
istio-system   istio-security-post-install-57rbg         0/1       Pending   0          7m
istio-system   istio-sidecar-injector-6d76b66585-bz47t   0/1       Pending   0          7m
istio-system   istio-telemetry-d8cb8f4b9-wqhpb           0/2       Pending   0          7m
istio-system   istio-tracing-7cd54799d8-x54s2            0/1       Pending   0          7m
istio-system   prometheus-6574b56df9-28h57               0/1       Pending   0          7m
istio-system   servicegraph-666d4ffc7b-twmcl             0/1       Pending   0          7m

Version
istioctl version: 1.0.0 release / 1.1.0 pre-release
kubectl version: 1.11.3
docker version: 18.06.1-ce
Installation
Just list 1.1.0 installation steps, same step for 1.0.0

wget https://github.com/istio/istio/releases/download/1.1.0.snapshot.1/istio-1.1.0.snapshot.1-linux.tar.gz
tar -zxf  istio-1.1.0.snapshot.1-linux.tar.gz
cp bin/istioctl /opt/k8s/bin/
istioctl version
version.BuildInfo{Version:"1.1.0.snapshot.1", GitRevision:"45692c579c6d755194421540149a99ac4cb59528", User:"root", Host:"ac7ff4b30ee4", GolangVersion:"go1.10.1", DockerHub:"gcr.io/istio-release", BuildStatus:"Clean"}
kubectl create -f  install/kubernetes/istio-demo.yaml

Environment
VMware: 14.1.2
OS: Centos 7.4 minimal
istioctl version: 1.0.0 release / 1.1.0 pre-release
kubectl version: 1.11.3
docker version: 18.06.1-ce
etcd cluster version: 3.2.18
Cluster state
This is no log neither in kubectl logs  -n istio-system nor /var/log/messages
istio-dump.tar.gz

I hava got the same problem.Did you solve it?

I hava got the same problem.Did you solve it?

Solved by upgrading CPU to 4 cores and memory to 6GB.


How can I change the graphics of my agar client?

I want for that option that defines the graphics of the game that has' medium, mobile, high and retina

Hold up, mobile quality? Also this is a client sided issue, obviously (though semi-easy to implement).

Yes, teach me how to.

This is a server repo, not a client repo. Client sided.

?

This has nothing to do with MultiOgar-Edited.

If you want the graphics feature as from the current version of agar.io, I can't help you there. Maybe the graphics options from an older version of agar.io (like v72).

Can be

I know a way, learn JS.

mm


[feature] support glob path match in CLI.

⭐ Suggestion

Sometimes, we want to match some paths by a glob pattern. That will be really great if the ast-grep CLI supports a glob pattern like the configuration file globbing.
The VSCode extension which uses ast-grep CLI as its backend, will also support glob if this feature is addressed.
💻 Use Cases

Is this not already supported? https://github.com/ast-grep/ast-grep/discussions/715#discussioncomment-7902065

@reidbarber problem is that is that shell globs are not smart enough to avoid .gitignored stuff like node_modules which is a significant perf impact

I guess something like --glob from ripgrep would be ideal...
I believe that ripgrep is also written in rust, so maybe it uses a common crate for the glob stuff that could be reused here?

yep, it uses this one:
https://crates.io/crates/globset

I guess something like --glob from ripgrep would be ideal...

Agree. ripgrep's API design is a pretty good fit for ast-grep as well.

Thank you!


JWT

Hi,
I didn't find any information about mechanism of JWT authentication.
Anyway, when I study about cookiepack(), I think the JWT and the Rapidoid's cookies and roles system are very similar.
Am I right?

Hi, yes, the mechanism is similar, the cookiepack stores encrypted and signed data, which can be exchanged with a cookie or a "_token" request parameter.
BTW, the "cookiepack" name was a bad naming choice, it will be renamed to "token" in v5.2.0...

Thanks


re-introduce provider-decentralized-k8s tests

It's been a while since we ran the provider-decentralized-k8s. We remove them from CI because they were always breaking but they used to run fine on local. Maybe we can use the CNCF nodes and see if they get green
https://github.com/kairos-io/kairos/blob/master/.github/workflows/image.yaml#L375-L378
https://github.com/kairos-io/kairos/blob/master/.github/workflows/release-arm.yaml#L307

https://github.com/kairos-io/kairos/pull/2730
problem comes from edgevpn
testing 0.23.1 works
testing 0.24.1 doesnt work
Error happens when connecting via dht:
{"level":"ERROR","time":"2024-07-16T09:04:01.565Z","caller":"discovery/dht.go:225","message":"Error connecting to peer '12D3KooWBTAmcJofgtFr2GU1WnQnWEZerpYMd7DRa9mkZESfUemJ': failed to dial: failed to dial 12D3KooWBTAmcJofgtFr2GU1WnQnWEZerpYMd7DRa9mkZESfUemJ: all dials failed\n  * [/ip6/2a01:4f9:6b:142f::2/udp/4001/quic/p2p/12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f/p2p-circuit] error opening hop stream to relay: failed to dial: failed to dial 12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f: no good addresses\n  * [/ip6/2a01:4f9:6b:142f::2/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip6/::1/tcp/34795] dial tcp6 [::1]:34795: connect: connection refused\n  * [/ip4/<IP_ADDRESS>/tcp/40385] dial tcp4 <IP_ADDRESS>:40385: connect: connection refused\n  * [/ip4/<IP_ADDRESS>/tcp/40385] dial tcp4 <IP_ADDRESS>:40385: connect: connection refused\n  * [/ip4/<IP_ADDRESS>/udp/4001/quic/p2p/12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f/p2p-circuit] error opening hop stream to relay: failed to dial: failed to dial 12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f: no good addresses\n  * [/ip4/<IP_ADDRESS>/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip6/2a01:4f9:6b:142f::2/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip4/<IP_ADDRESS>/udp/4001/quic/p2p/12D3KooWB6vYxc5FX68DPFgPgh2uazUhSoippVaNcWYugdLAVmMc/p2p-circuit] error opening hop stream to relay: failed to dial: failed to dial 12D3KooWB6vYxc5FX68DPFgPgh2uazUhSoippVaNcWYugdLAVmMc: no good addresses\n  * [/ip4/<IP_ADDRESS>/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip6/2a01:4f9:6b:142f::2/tcp/4001/p2p/12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f/p2p-circuit] error opening hop stream to relay: failed to dial: failed to dial 12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f: all dials failed\n  * [/ip4/<IP_ADDRESS>/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip6/2a01:4f9:6b:142f::2/udp/4001/quic] QUIC draft-29 has been removed, QUIC (RFC 9000) is accessible with /quic-v1\n  * [/ip6/2a01:4f9:6b:142f::2/tcp/4001] dial tcp6 [2a01:4f9:6b:142f::2]:4001: connect: network is unreachable\n  * [/ip4/<IP_ADDRESS>/tcp/4001/p2p/12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f/p2p-circuit] error opening relay circuit: NO_RESERVATION (204)\n  * [/ip4/<IP_ADDRESS>/tcp/5003/ws/p2p/12D3KooWCPzmui9TSQQG8HTNcZeFiHz6AGS19aaCwxJdjykVqq7f/p2p-circuit] concurrent active dial through the same relay failed with a protocol error\n  * [/ip4/<IP_ADDRESS>/tcp/4001/p2p/12D3KooWB6vYxc5FX68DPFgPgh2uazUhSoippVaNcWYugdLAVmMc/p2p-circuit] error opening hop stream to relay: failed to dial: context deadline exceeded\n"}

This onl[y happens in this specific qemu net user scenario.
This emans that both machines have the same IP, go over the same gateway and have the same DNS but are on isolated networks.
In other network deployments this works as expected.

Confirmed that with bridge networking it works as expected

So if we can fix the test, we don't need this? https://github.com/kairos-io/packages/pull/973

So if we can fix the test, we don't need this? kairos-io/packages#973

yep, in fact we didnt need that from the start but it was discussed as a possibility to downgrade edgevpn so I added the PR just in case we did need it before cutting the release.

I dont think this is viable, too many issues, too many changes to the tests, too many problems in order for such an specific test.

Let's add this to our manual (release) testing for now and revisit it. We could fix it by running the nodes on some cloud (public or not) or by setting up the bridge network or something.


mdoutliner6 SIGSEGV on v0.7.0

Couldn't find a template for opening issues, so excuse me.
Ran everything in the example folder apart from: libraries, android, marhsalling, uidesigner, windowsmanifest and the only thing that didn't work was mdoutliner6.
Here's the output during runtime:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x94a07d]

goroutine 1 [running, locked to thread]:
github.com/mappu/miqt/qt6.(*QWidget).AddActionWithText.func2(0x111df41?, {0x7?, 0x25c3d0e0?})
       /home/aria/.local/share/go/pkg/mod/github.com/mappu/miqt@v0.7.0/qt6/gen_qwidget.go:1308 +0x1d
github.com/mappu/miqt/qt6.(*QWidget).AddActionWithText(0x0, {0x111df41?, 0x7})
       /home/aria/.local/share/go/pkg/mod/github.com/mappu/miqt@v0.7.0/qt6/gen_qwidget.go:1308 +0x78
main.NewAppWindow()
       /home/aria/Desktop/coding/qt-go/main.go:70 +0xad
main.main()
       /home/aria/Desktop/coding/qt-go/main.go:183 +0x2d
exit status 2

Investigated this a little bit,  the issue seems to be on line 68 when creating the fileMenu. It all boils down to passing a nil pointer for h_QWidget here.
Is this example broken for v0.7.0 release or am I doing something wrong?

I see the problem. Yes, this example will be broken in v0.7.0, but it's working again in miqt master (b31a1e3dfeba1e403ae05b9ac7c2969f718d3799) since #101.
I'll tag a new v0.7.1 release soon with collected bugfixes.

I can confirm the crash on v0.7.0 and confirm the fix on new tag v0.7.1. Please try out v0.7.1 and let me know if it's fixed for you too,


RuntimeError: Text is not visible

Hello @moonbings While generating Korean dataset, I have added all given requirements like fonts and everything. I am using below command to generate dataset but getting an error between data generation process.
python -m synthtiger -o results -w 4 -v examples/synthtiger/template.py SynthTiger examples/synthtiger/config_vertical.yaml
Generated 56 data
Generated 57 data
Generated 58 data
Generated 59 data
Generated 60 data
Traceback (most recent call last):
  File "/media/cvpr/CM_22/synthtiger/synthtiger/gen.py", line 71, in _generate
    data = template.generate()
  File "/media/cvpr/CM_22/synthtiger/examples/synthtiger/template.py", line 117, in generate
    image = _blend_images(fg_image, bg_image, self.visibility_check)
  File "/media/cvpr/CM_22/synthtiger/examples/synthtiger/template.py", line 246, in _blend_images
    raise RuntimeError("Text is not visible")
RuntimeError: Text is not visible

Generated 61 data
Generated 62 data
Generated 63 data
Generated 64 data
Generated 65 data
Generated 66 data

Hi,
This engine tries to generate an image until the text is visible, and generates a specified number of images.
This error message means that the image is not saved when the text is not visible in the image.
So you may ignore this message.
Thanks.


Issue with docker-compose

Traceback (most recent call last):
File "docker-compose", line 6, in
File "compose/cli/main.py", line 72, in main
File "compose/cli/main.py", line 128, in perform_command
File "compose/cli/main.py", line 1077, in up
File "compose/cli/main.py", line 1073, in up
File "compose/project.py", line 548, in up
File "compose/service.py", line 355, in ensure_image_exists
File "compose/service.py", line 381, in image
File "site-packages/docker/utils/decorators.py", line 17, in wrapped
docker.errors.NullResource: Resource ID was not provided
[50048] Failed to execute script docker-compose
Facing the above error when executing docker-compose up. Any hints please

found that required configuration which is mentioned in docker-compose file is missing


Refine logic to update package versions

PR Highlights: Two kinds of upgrades are now possible for @ampproject/google-closure-compiler-* packages:

When a major closure update is pushed, all subpackages' versions will follow suit
When code in this repo is changed, the patch version is updated, enabling us to push a new version for amphtml to use

Bonus fix: Remove the useless and outdated node v12 specifier in the CI config

This worked. See logs.


Edit Suspended license

A suspended license can be edited via API ...
ethier return a error 4XX message, or ad another argument to check if the request has been made by the admin or the client (like a force setting value) .

This is an interesting one. Editing the licence via the API won't actually change its suspension status, so there's nothing inherently wrong with allowing a suspended licence to be edited while on suspension
It's something that we can look at changing if there's a big enough backing for it, but since it doesn't affect the suspension of the licence itself, I'm not sure its necessary.


Tooltip example scene updates

Overview
Part of #5164 [GA] Example scene polish

Updated label's backplate material to HolographicBackPlate.mat which is also used in the Slate's title bar and Button.
Added Billboard script(existing in MRTK) to the Tooltip prefab's label.
Added Mars Rover model to demonstrate a practical example of using multiple tooltips for the annotations.
Updated screenshots, content in the README file.
No code changes.

Changes

Fixes: #5164

/azp run mrtk_docs

/azp run mrtk_pr

Might be useful as an example to have some tooltips spawn during runtime on interaction with the rover? Just a thought for future improvements on the scene :)


IB-2785 added a Multi Terms aggregation

Thanks, but we're going to pass on this to keep the package simple.


"Run" Button Missing in Action List After Adding SortableAdminMixin

What version of Unfold are you using?
0.34.0
What version of Django are you using?
4.2.6
What browser are you using?
Chrome 128.0.6613.84
Did you checked changelog/commit history, if the bug is not already fixed?
Yes
Did you searched other issues, if the bug is not already fixed?
Yes
Repository with reproduced bug
.
Describe your issue
I'm encountering an issue with Django admin when using the SortableAdminMixin. Specifically, after adding SortableAdminMixin to my Django admin configuration, the "Run" button for performing bulk actions, such as deleting multiple rows, is no longer visible.
Here's a brief overview of the problem:
Context: I am using SortableAdminMixin to enable sortable functionality in the Django admin interface. This mixin is designed to allow for drag-and-drop sorting of list items.
Problem: After incorporating SortableAdminMixin, the "Run" button, which is typically available for executing bulk actions (e.g., deleting selected rows), is no longer displayed in the action list dropdown menu.
Impact: This issue prevents users from performing batch actions on selected rows, which affects the usability and functionality of the admin interface for managing data efficiently.
Steps to Reproduce:
Add SortableAdminMixin to your admin class.
Observe the admin interface where the bulk action dropdown is displayed.
Notice that the "Run" button is missing from the action list.
Any guidance or solutions to resolve this issue would be greatly appreciated.

I have the same issue.
In the list view, when I select some rows and want to run some action, there is no "Run" button there.
If I disable unfold in the settings, it appears again (as it usually exists in the original django admin).
And it's not a duplicate of #683

facing same issue.

@SAGAR-TAMANG please create a new issue describing your problem. Regarding SortableAdminMixin, this third party app is not officially supported in Unfold.


File saving failed using batch

[REQUIRED] Step 1: Describe your environment

Xcode version: 9.2
Pring version: 0.7.8

[REQUIRED] Step 3: Describe the problem
I tried to save Images using WriteBatch class.
Saving to Firestore is succeeded, but File is not saved in storage.
Relevant Code:
class Image: Object {
    dynamic var file: File?
}

let imageModel = Firebase.Image()
imageModel.file = File(data: UIImageJPEGRepresentation(image, 1.0)!)
let batch = Firestore.firestore().batch()
batch.add(.save, object: imageModel)
batch.commit { error in
    print(error) // printed nil, but file is not exist in storage
}

I have also encountered the same problem.
・Xcode version: 10.0
・Swift version: 4.2
・Pring version: 0.13.6

Has same issue


bootstrap-datepicker.standalone.min.css

in quickadmin/src/Views/admin/partials/header.blade.php
do you really need :
<link rel="stylesheet"           href="https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.5.0/css/bootstrap-datepicker.standalone.min.css"/>
???

I don't see where the problem is. We have a datepicker field and its library, or am I missing something?

I'm wondering why loading these css ?
because the javascript library https://github.com/eternicode/bootstrap-datepicker is not used
The library used for date time picker is :
<script src="https://code.jquery.com/ui/1.11.3/jquery-ui.min.js"></script>
<script src="http://localhost:8001/quickadmin/js/timepicker.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-ui-timepicker-addon/1.4.5/jquery-ui-timepicker-addon.min.js"></script>

and it use jquery ui css theme :
<link rel="stylesheet" href="https://code.jquery.com/ui/1.11.3/themes/smoothness/jquery-ui.css">

Well, as far as I can see - you are asking about datepicker and showing us timepicker. These are two different plugins :)

I've tried to create a crud with a field date picker and a field date and time picker

and twice only use timepicker (jquery ui)
and never bootstrap-datepicker (https://cdnjs.cloudflare.com/ajax/libs/bootstrap-datepicker/1.5.0/js/bootstrap-datepicker.js)
I think I will change after for https://github.com/Eonasdan/bootstrap-datetimepicker
which is compatible bootstap v3.3.6.
And I will remove :

jquery-ui.min.js javascript library and css smoothness/jquery-ui.css
timepicker.js
jquery-ui-timepicker-addon
bootstrap-datepicker.standalone.min.css

and I will only load :

resources/assets/vendor/bootstrap-datetimepicker/css/bootstrap-datetimepicker.min.css
resources/assets/vendor/bootstrap-datepicker-dist/js/bootstrap-datepicker.min.js

Hello,
If you could do a pull request with your modified file - it would be great. At this point we are more focused on some other features


RedisClusterClient default connection congestion

Following up from my question in the Google Group.
As mentioned in the documentation, connections created with RedisClusterClient will always create a default connection to the node with the lowest latency. However, this may cause congestion when one node has a lower latency. If all clients experience the lowest latency with a particular node, then all clients will pick that node for its default connection.
In my case I'd be happy to use randomly selected nodes. That gives me a more predictable distribution of connections. Perhaps some environments prefer selecting by latency, but maybe lettuce could expose the choice as a client configuration?

Thanks for the ticket. The default connection is created to the first node able to connect. RedisClusterClient starts to its connection attempts with the first entry of the Partitions collection (ordered by latency). Randomly selected nodes will work, but it's not a deterministic approach.
There are two other options which both seem reasonable to me:

Sticking to the order of seed nodes: The connection attempts are performed in the order the seed nodes are provided. This approach gives full control to the user.
Using the client count: Lettuce obtains the client connection count for each cluster node while topology discovery (can be disabled) and Partitions is ordered by the client count. Obtaining the number of client connections beyond the seed nodes can be disabled with the upcoming 4.2 version which is useful when running large clusters.

The default will be to connect to the node with the least clients. For now RedisClusterClient will expose getSocketAddressSupplier(Function<Partitions, Collection<RedisClusterNode>> sortFunction) which can be overriden to specify an own function. lettuce ships with TopologyComparators that expose predefined sorting methods (sortByUri, sortByClientCount and predefinedSort). Applying a sorting function requires to subclass RedisClusterClient for now as this is the least invasive approach.
predefinedSort allows to use the initial seed nodes as predefined ordering and apply it to the dynamic topology results from Partitions. Nodes that are not found in the initial seed nodes are ordered by the URI (lexicographical comparison of the host and port string, i.e. <IP_ADDRESS>:6379 < <IP_ADDRESS>:6380). The block of nodes not found in the predefined order comes after the block of nodes with a predefined order.

Implemented.


Fix StandardOutputAppender init not accessible outside the module

StandardOutputAppender was not accessible outside the module, thus couldn't be instantiated like this:
var logger = Logger(name: "main", appenders: [StandardOutputAppender(levels: .info)])

Nice catch - let me look into why travis is failing.


Adding umask param to ConcurrentRotatingFileHandler.

This allows permissions to be set on file creation without the race condition of chmod.
And unlike chmod, it wont fail if run by a user that doesnt own the existing log or lock file.
Fixes #10 via an alternative choice for anyone who has a use case that is exposed to that issue.

So far it looks good to me. I'll take a deeper look and get it merged by early next week.
Since the chmod feature only works on Unix anyway, maybe this should just replace it? The user who requested/added the chmod feature is https://github.com/greenfrog82

Since the chmod feature only works on Unix anyway, maybe this should just replace it?

I could still see someone needing to use chmod instead of umask. Since umask affects all threads, someone could have a multi-threading program where it's important to them for umask to not change, and therefore they shouldn't use it here. As long as they aren't exposed to the scenarios raised in issue #10, chmod will be the better option.

Thanks for your contribution, by the way! It has been released as version 0.9.12.


WIP: basic way to ignore files with *

Just a first approach. I actually decided to have a joker * which can be at any position such that posts/*/post.md works for example.
Problems with current approach:

Generating the regex is not super nice maybe there is a way to escape chars.
The regex should probably be generated once in the scan_input_dir! function instead which would change Vector{String} to Vector{Union{String, Regex}}.

How about letting users put regex in ignore directly instead? E.g.
@def ignore = ["some string", r"some regex"]

I was a bit worried that this might be more bug prone but looking at the code it seems like it would be a natural progression anyway so might as well, what do you think @Wikunia ?

Sounds good to me. People who want that behavior are probably the ones who know enough about regex to make it work + having one in the docs just to show seems reasonable.
Will change the PR.

One problem:
I don't know what's the best way to allow regex for directories or whether that is needed at all.

Thanks a lot Ole, I'll try to have a look at this later today!

I don't know what's the best way to allow regex for directories or whether that is needed at all.

Just a regex that matches the path? For example
r"posts/.*"

would ignore everything in that folder.

Yeah currently there is splitting between files and folders and for folders it only checks whether it starts with the folder and for files there is an exact match.
Probably one can just do the same as for files and just check if it is a regex or not and if it's a string test startwith and otherwise match regex.

I don't know what's the best way to allow regex for directories or whether that is needed at all.

Just a regex that matches the path? For example
r"posts/.*"

would ignore everything in that folder.

note that you can already ignore an entire folder by just adding a / so
@def ignore = ["path/to/dir/", "path/to/file.md"]

will ignore the entire dir and the specific file.


Sailsbot references guideslines that don't exist

When I open a PR, sailsbot lightly scolds me for not formatting my PR title according to the guidelines, but the guidelines it links to don't mention PR titles at all as far as I can tell.
It seems to me that either the contribution guidelines should be updated to mention PR title formatting, or that check should be removed from sailsbot.

Hi @cincodenada, Thanks for the feedback!
We've updated Sailsbot to remove this check.

@eashaw Thanks! That takes care of the issue as far as I'm concerned 👍


How to use this for a sphere

As I understand it, this can be used to 'fill' 3d meshes, or create an illusion of that effect when viewing cross section of that object. I want to use this to fill a sphere and when I import the volume node as child of a rigid body sphere, I'm getting a cube and cross section shown is that of a cube. How to make this module work with different shapes other than cubes?
I'm using godot 3

This is a little dated, and I've made a different, more standard volume renderer since then.
But if you'd like to use this one anyway, what you have to do is voxelize a MeshInstance with a Sphere mesh using the Volume generator. You can read about it in the README. If it's currently not working, just know that I'm not actively developing this anymore.


Nodes looping back on each other

With data like this:
[{name:'0',next:[{index:1},{index:3}]},{name:'1',next:[{index:2},{index:3}]},{name:'2',next:[]},{name:'3',next:[]}]
the arrow between node 1 and 3 is coming around backwards:

ehhh, it is interesting. I will check and fix it.

fixed


Home Page Responsive Fix and some minor fix - GSSOC-'23

Changes Made :-

Fixed Alignment issue that was being caused due to font size being too big
2 .Modified CTA button to span wide on mobile devices
made the logo size fit better on mobile devices

Hey Amogh, We have uploaded the latest version of PaperBrain. Do a pull and work on that.

@SaadAnzar @nawed2611 , Please Review https://github.com/nawed2611/paperbrain/pull/50


[Event Request] Codeunit 99000832, 99000833, 99000834, 99000836, 99000837, 99000838 OnAfterFilterReservFor

please add a new Event trigger OnAfterFilterReservFor in codeunits 99000832, 99000833, 99000834, 99000836
codeunit 99000832:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";SalesLine : Record "Sales Line")
FilterReservEntry.SetSourceFilter(
DATABASE::"Sales Line",SalesLine."Document Type",SalesLine."Document No.",SalesLine."Line No.",FALSE);
FilterReservEntry.SetSourceFilter2('',0);
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;SalesLine);
//-------------------------------------
codeunit 99000833:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";ReqLine : Record "Requisition Line")
FilterReservEntry.SetSourceFilter(DATABASE::"Requisition Line",0,ReqLine."Worksheet Template Name",ReqLine."Line No.",FALSE);
FilterReservEntry.SetSourceFilter2(ReqLine."Journal Batch Name",0);
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;ReqLine);
//-------------------------------------
codeunit 99000834:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";PurchLine : Record "Purchase Line")
FilterReservEntry.SetSourceFilter(
DATABASE::"Purchase Line",PurchLine."Document Type",PurchLine."Document No.",PurchLine."Line No.",FALSE);
FilterReservEntry.SetSourceFilter2('',0);
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;PurchLine);
//-------------------------------------
codeunit 99000836:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";TransLine : Record "Transfer Line";Direction : 'Outbound,Inbound')
FilterReservEntry.SetSourceFilter(DATABASE::"Transfer Line",Direction,TransLine."Document No.",TransLine."Line No.",FALSE);
FilterReservEntry.SetSourceFilter2('',TransLine."Derived From Line No.");
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;TransLine,Direction);
//-------------------------------------
codeunit 99000837:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";ProdOrderLine : Record "Prod. Order Line")
FilterReservEntry.SetSourceFilter(DATABASE::"Prod. Order Line",ProdOrderLine.Status,ProdOrderLine."Prod. Order No.",0,FALSE);
FilterReservEntry.SetSourceFilter2('',ProdOrderLine."Line No.");
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;ProdOrderLine);
//-------------------------------------
codeunit 99000838:
[External] FilterReservFor(VAR FilterReservEntry : Record "Reservation Entry";ProdOrderComp : Record "Prod. Order Component")
FilterReservEntry.SetSourceFilter(
DATABASE::"Prod. Order Component",ProdOrderComp.Status,ProdOrderComp."Prod. Order No.",ProdOrderComp."Line No.",FALSE);
FilterReservEntry.SetSourceFilter2('',ProdOrderComp."Prod. Order Line No.");
//+++++++++++++++++++++++++++++++++++++
OnAfterFilterReservFor(VAR FilterReservEntry;ProdOrderComp);
//-------------------------------------

We do major refactoring of reservation system and going to deprecate these functions. Instead we will use functions like SalesLine.SetReservationFilters(FilterReservEntry). This is already implemented in Master and you check check it in preview builds. Would it be better to implement events in table functions?

Please reply

yes, would be nice to have those new Events then in the tables
e.g. in T37 in SalesLine.SetReservationFilters(FilterReservEntry) the Event
OnAfterFilterReservFor(VAR FilterReservEntry;SalesLine);


Removes use of -k option to curl in Kitty section in docs

No https request is made. And even if, there should be no reason to allow insecure connections anyways.

Note that you dont need to use curl at all. You can just do
kitty +kitten icat https://v3.wttr.in/Tabasco.png

Wlow! I didn't know that with icat. Very cool!
@kovidgoyal is it possible to display sixel or other format in Kitty directly,
so that it would be possible to curl it directly, without icat, like in other terminals?

kitty has no support for sixel, which is an extremely inferior encoding.
You can of course curl images directly, you need to encode them using
kitty's graphics display protocol instead of sixel. icat is a just a
convenient wrapper that does it for you.
https://sw.kovidgoyal.net/kitty/graphics-protocol.html
In fact the next release of kitty adds support for animated images, so
you can get really fancy. https://github.com/kovidgoyal/kitty/issues/3287

@kovidgoyal
Yes, I read it before, but I didn't find any convenient method to convert graphics into the kitty-graphics-protocol-encoded data, to be able to render it on the server side, and just pass the rendered stream to the client, like it works for all other terminals. I tried to use icat but instead of converting data into the kitty-graphics-protocol-encoded format, it just displayed it in the terminal. Probably, there must be some additional cli option for that, but I didn't find anything.
What option or command should I use?

There is no option or command, you just generate the bytes for yourself.
It's pretty simple, see https://sw.kovidgoyal.net/kitty/graphics-protocol.html#a-minimal-example
for a 20 line python scsript to do it, save and run it with a png image
and redirect its stdout to a file to save the result.

Thank you! It works!
Just of the curiosity: why didn't you add this to icat as a special CLI option?

On Sun, Feb 28, 2021 at 10:19:21AM -0800, Igor Chubin wrote:

Thank you! It works!
Just of the curiosity: why didn't you add this to icat as a special CLI option?

No use case. It's pretty trivial to generate the escape codes for simple
cases, and for more complex cases you would typically want the geometry
of the terminal and adjust the output accordingly, in which case
"pre-rendering" is not suitabe.

@kovidgoyal Thank you Kovid! As soon as v3.wttr.in supports Kitty image protocol out of the box, I will let you know

Cool note that wttr is mentioned here: https://sw.kovidgoyal.net/kitty/integrations.html

@kovidgoyal Kovid, thank you for mentioning it; the canonical name of the project is wttr.in not wttr; could you please update it if possible?
I plan to integrate the script that you provided me with, on the server side, so that it would
be possible to curl wttr.in directly from kitty.
By the way, is there any standard way for curl to know that it is running inside kitty? Some terminals set TERM variable (e.g. mlterm sets TERM=mlterm), some terminals some other variables, etc. Is there any canonical way to know that currently we are running inside kitty?

Sure, done.  The TERM value kitty uses is xterm-kitty. Note however the TERM is not a reliable way to detect terminals. Users and terminal multiplexers both often override it.

Yes, I know; what method would you recommend instead?

There is no method that is guaranteed to work across all terminal emulators. The most robust method is to query the terminal emulator via escape codes, see https://sw.kovidgoyal.net/kitty/kittens/query_terminal.html  for an example. However, this has the downside of witing for a response from the TE which might never arrive on TEs that dont support it.

What about KITTY_WINDOW_ID, Kovid? Shouldn't that always be available - at least locally?

Assuming the user isn't sanitizing env vars or isnt over an SSH
connection, yes, it is always set by kitty.

Thank you for the ideas; I think for the beginning $TERM will be enough


HTTPS support

Drivers: security
Requestor: customer request
Internal contact: Alex B or John W

@seemaj @aberghage @mk1s Is this still a requirement/needed feature?

Closing due to lack of activity.


Move jerry-core API implementations and headers into dedicated subdirectories

Merged debugger-related public API declarations from
jerryscript-debugger.h to jerryscript.h. It's part of the
engine's public API, there is no need to force the users of the
library to include yet another header.
Moved all public API headers under the jerry-core/include
directory. This makes installing all the public headers easier.
Also, should we have new public headers in the future (not probable
but possible), their installation will be automatic, there will be
no need to update the build files. Moreover, this aligns better
with the structure of other libraries in the project (in those
cases, public headers always reside in <library>/include).
Moved all public API implementations under the jerry-core/api
directory. This cleans up the root directory of jerry-core,
moving all implementation code under "modules", i.e.,
subdirectories. This also makes the future splitting of the big and
monolithic jerry.c along features easier, if needed. (Debugger
and snapshot-related functions are already in separate sources.)
Note: jerry-snapshot.h is still under jerry-core/api, keeping
it as a non-public header.
JerryScript-DCO-1.0-Signed-off-by: Akos Kiss<EMAIL_ADDRESS>

On top of the main commit, the PR contains an extra patch to speculatively adapt all targets to the include path change.

@akosthekiss I am thinking slightly differently about jerryscript-debugger.h. It is very closely related to jerry-core. However, it is the optional. For me, I don't want to have jerryscript-debugger related declarations when it is turned off. So I want to get your opinion about guarding jerryscript-debugger with JERRY_DEBUGGER like:
// In jerryscript.h
#ifdef JERRY_DEBUGGER
#include "jerryscript-debugger.h"
#endif

Or
// In jerryscript.h
#ifdef JERRY_DEBUGGER
// your merged part of jerryscript-debugger.h
#endif

I don't like merging debugger api to main api as well. Debugger is an extension, although it is so tightly coupled to the core it is not in a separate directory, but it is still an extension.

Come to think of it, jerry debugger api could be an extension to jerry! Yes, the key functions are in the trunk but the whole concept of the debugger is an extension. Promise (#1796) could be an extension as well. @jiangzidong what do you think of that?

I think Promise should be in the same position as string/number/boolean, because they are all JS builtin object. Do you mean to put every builtin-object related APIs into jerry-ext?

Good point. Ok, keep promise in top level.

@glistening I've two arguments against conditionalizing the debugger-related functions:

jerryscript.h or jerryscript-debugger.h (whichever we chose) are public headers. At that point we should not rely on the build configuration of the library itself. When someone uses the library and includes the public headers, s/he may not/should not know what defines were used to build it.
Actually, those functions are really always implemented in the library. If the library was built without debugger support, their implementation is empty or dummy.

This is very much aligned with other optional features. E.g., all snapshot-related API functions work this way. They are always part of the API, but if the built library does not support snapshots, they don't do anything.
@zherczeg @LaszloLango My motivation for merging jerryscript-debugger.h into jerryscript.h was the above-mentioned analogy with snapshots. The debugger functions are always present API functions, only their implementation depends on the availability of a feature. That sounds very core to me. (Changing perspective: if debugger API function declarations should be in a separate header, should snapshot-related functions also be in a separate header?)

@akosthekiss I agree that not using the conditional guards in public header is better. Then, what about keep the jerryscript-debugger.h out of jerryscript.h ? Every developer who want debugger feature could turn on when s/he needs it. I prefer to turn off jerryscript debugger after debugging is done since it is likely to help to reduce the binary or runtime footprint. I think snapshot is slightly different case. Since it is positive to reduce the footprint ( am I right? ), I usually don't turn off ( I've never turned off snapshot). However, debugger is only useful when we debug.

since it is likely to help to reduce the binary or runtime footprint.

To myself, it is unlikely to help to reduce the binary or runtime memory usage by getting rid of jerryscript-debugger.h declarations from jerryscript.h when jerryscript debugger off.
@akosthekiss Personally, I am not familiar with declarations in public header that have no definitions. However, if it is convention in jerryscript, I will accept this convention.

@akosthekiss following that logic everything is core, since everything depends on the internals of JerryScript. Functions in jerryscript-debugger.h are debug specific functions, and there is no reason for them to be available in the main API.

@glistening

What do you mean by library in following ?

those functions are really always implemented in the library. If the library was built without debugger support, their implementation is empty or dummy.

Sorry, that was ambiguous. What I meant was that jerry_debugger_is_connected and all the other jerry_debugger_xxx debugger-related API functions were always built into jerry-core (the library).
bool
jerry_debugger_is_connected (void)
{
#ifdef JERRY_DEBUGGER
  return JERRY_CONTEXT (debugger_flags) & JERRY_DEBUGGER_CONNECTED;
#else
  return false;
#endif /* JERRY_DEBUGGER */
} /* jerry_debugger_is_connected */

This is how jerry_debugger_is_connected looks now. The function is always in jerry-core. If it was built with debugger enabled, then it does something meaningful, but if not, its implementation is dummy.
So, no jerry-core API function is ever missing. Even if some features are disabled in a build, all API functions are callable -- but not necessarily do anything meaningful. This ensures that linking always succeeds. And it is possible to check during execution whether a feature is available or not (via jerry_is_feature_enabled).

@akosthekiss Thank you for clear explanation.

@zherczeg

following that logic everything is core, since everything depends on the internals of JerryScript

Please, elaborate. I'm not sure I know what "everything" means here. Right now, the engine (the jerry-core library) has 3 public headers:

jerryscript.h: all the public API that embedders should/are allowed to call to interact with the engine,
jerryscript-port.h: all the function declarations that port providers must implement to get the engine work, and
jerryscript-debugger.h: function declarations needed to interact with the debugger API of the engine.

My point is, that I see no difference between jerryscript.h and jerryscript-debugger.h because both headers declare API of the engine. The debugger support is not just an extension of the engine, at least not in the sense of the jerry-ext library, because it is not possible to implement its functionality outside / on top of the engine.
That's why I've brought up the snapshot analogy: snapshot saving/execution is not a mandatory part of the engine, you can opt in or out; but it is impossible to implement snapshot saving/execution outside of the engine (outside of jerry-core).
IMHO:

argument handling, common external functions: Optional? Yes. Needed for ES compatibility? No. Needs accessing jerry-core internals? No. --> extension, implemented in jerry-ext, declared in jerryscript-ext/xxx.h
snapshots: Optional? Yes. Needed for ES compatibility? No. Needs accessing jerry-core internals? Yes. --> feature, implemented in jerry-core, declared in jerryscript.h
debugger support: like snapshots. So it's not an "extension" but a "feature". declared where?

@akosthekiss Here is my understanding: If it is impossible to implement some feature outside of jerry-core, it will be part of jerry-core even when it is optional feature. ( Hereafter I will call this feature core-extension to distinguish other extension (user-extension). in this comment. )
Here are my opinions on core-extensions

Where to keep the core-extension's declarations
You seem to like keep whole public things in jerryscript.h than having a separate header (i.e. jerryscript-debugger.h ) and including that header in jerryscript.h. Personally If there will be more core-extensions (currently - two : snapshot, debugger), I prefer to keep separate the feature's public header and include it in jerryscript.h and I found many open sources that use this approach if the public API grows up. Personally this separate container headers makes me easy to find the feature's api and maintain the code.

Zero overhead to keep the optional core-extension
In order to make the public header configuration agnostic, currently we provide dummy implementation in jerry-core library even when the option is off. It makes life easy and simple. However, I still hope zero overhead both in runtime performance and binary footprint since jerryscript is for low profile devices. And current approach put a few overhead for both. It may be removed by using macro like assert statement although the implementation may not look elegant and require tedious work.. What do you think?

@glistening

Where to keep the core-extension's declarations

Actually, any approach can work with me if we apply that approach consistently. Where I disagreed with fellow reviewers was that right now the debugger API/header was treated differently than the rest, although I could not find the reason for that (analysis above).
There are several options to chose from:

keep the whole API in a single header (hard to break consistency then...) -- that's what I've chosen in the first version of this PR,
split the API into separate headers, one for the non-optional part, and one for each "feature" / "core-extension" -- that's the current status but not consistent (debugging feature has its own header, snapshots don't), and
split the API into separate headers, like option 2, but also include these headers into the main one -- I think that's your suggestion -- we don't do this even with the debugger header yet, but it's still a valid approach.

Any of the above works with me, just let's keep things consistent. Or convince me that we shouldn't ( @zherczeg @LaszloLango :) )
Note to self (and to all interested parties): option 2, when applied consistently (i.e., splitting out snapshot-related function declarations), is a breaking change, as library users will have to add an extra #include to their sources if they used snapshots before.

Zero overhead to keep the optional core-extension

I wouldn't plan function removal for this patch, although I agree that because of the goals of jerryscript, we should aim at zero overhead. Note 1: not including those functions with dummy implementation is a breaking change (users who could link before may not link afterwards). Note 2 (or a question): "removed by using macro like assert statement", I'll have to ask for some explanation this, I'm not sure how this would look like.

It is hard to judge the effect of choices. I would prefer the 1st option if the size of the header will not grow too large. But if it is, I would prefer the 3rd.

I've added a commit that implements option 3 so that we can compare it against option 1. So, the question is, which variant to keep?

@akosthekiss you convinced me. The first was better. :) I agree with @zherczeg

prefer the 1st option if the size of the header will not grow too large. But if it is, I would prefer the 3rd.

I think it isn't too big if we merge and it is easier for Jerry users to use only one header.

Another idea: what about making multiple headers, and jerryscript,h includes them all (it has no other code than including the other headers). So people need to include only one file, but we can separate type declarations, functions prototypes better.

@zherczeg we may consider that too, but I think that could be done in a follow-up work.

It is already done in this patch.

@zherczeg sure. My bad. Too many open PRs :)

@zherczeg Sorry, I'm a bit confused now. The current status of this PR (all 3 commits together) implement option 3 (see above; non-optional jerry-core API in jerryscript.h, feature-dependent APIs in jerryscript-FEATURE.h). But two recent comments seem to conflict with this and with each other: "what about making multiple headers, and jerryscript,h includes them all (it has no other code than including the other headers)" vs "It has already done in this patch".
Note (for option 3, and similar variants): if feature APIs are split out into separate headers which are included by jerryscript.h, then either they cannot be used directly (i.e., user must not include jerryscript-snapshot.h directly) or these feature headers must include jerryscript.h, too (because API function declarations may need types defined in jerryscript.h; that's how jerryscript-snapshot.h looks right now; works, but it's not nice, IMHO).

Yes, users can only include jerryscript.h. The current API would be moved to jerryscript-api.h, which would be the first file in the include list of jerryscript.h. The rest is already in the patch, so this is little work.

I've updated the PR according to the latest comments (added a 4th commit that splits out the main API into a new header).

@akosthekiss @zherczeg, jerryscript-api.h is quite odd. jerryscript-debugger.h and jerryscript-snapshot.h are also api headers. What do you think about jerryscript-common.h or jerryscript-core.h?

@LaszloLango both -api.h and -core.h are OK with me. (-common.h looks a bit strange to me)

I like the -core postfix. or -base.

I've changed jerryscript-api.h to -core.h and squashed all commits.


Terminal Glitch when splitting from tsc --watch

Issue Type: Bug

Run tsc --watch
Terminal split

VS Code version: Code - Insiders 1.24.0-insider<PHONE_NUMBER>4dcbe9aca0e5ca3ba8a53808b122b6, 2018-06-01T13:37:15.690Z)
OS version: Darwin x64 17.5.0

System Info

Item
Value

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

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: enabledrasterization: enabledvideo_decode: enabledvideo_encode: enabledvpx_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
3, 2, 2

Memory (System)
16.00GB (0.98GB free)

Process Argv
/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron -psn_0_1364301

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

markdown-emoji
bie
0.0.7

tslint
eg2
1.0.30

vsc-material-theme
Equ
2.1.0

prettier-vscode
esb
1.4.0

theme-monokai-pro-vscode
mon
1.1.6

vscode-scss
mrm
0.6.2

debugger-for-chrome
msj
4.5.0

vetur
oct
0.12.3

vscode-proun
oct
0.0.1

polacode
pnp
0.2.2

vscode-sort-json
ric
1.11.0

vscode-csstree
sme
0.7.0

language-stylus
sys
1.9.2

vim
vsc
0.12.0

(2 theme extensions excluded)

The shadowy scorllbar persists even after closing split terminal.

Removing from May milestone after checking with @Tyriar.

:confused: :scream: Given the artifacts that's manifesting with, this looks like it might be an electron/chromium bug, and not an xterm.js bug.

@bgw yes this is the canvas renderer. My first impression was it's a Chromium thing but it looks like the black columns are lining up with the terminal columns which makes me think it's our bug.

Updating to latest xterm.js doesn't appear to fix this.

May be related to https://github.com/Microsoft/vscode/issues/51602

This is looking more and more like a Chromium bug. If I change this line to be #FF0000, I do not get the bars. changing it to #888888 however and I do:

Moving to June as it appears to be a Chrome issue and it's less impact than I first thought; it only impacts "null" rows. This does not happen when the viewport has been filled (you see a flicker but it goes away the next frame).

@Tyriar, what was the workaround for this?

@bgw the workaround didn't fix it, I tried to use clearRect in TextRenderLayer.onGridChanged which seemed to work on macOS, but didn't on other platforms https://github.com/Microsoft/vscode/issues/51749#issuecomment-396869595

Can't repro this out of sources anymore 😕

I'm on e585e4bf008a50e5b1f4fde71cf6d255e25381bf

Yeah I see it in insiders, no running out of sources though 😕

I've also seen this happen:

Something similar can also happen in the color picker:

I think this one is fixed in Electron 3

This is also fixed by the webgl renderer I just build https://github.com/xtermjs/xterm.js/pull/1790, not sure if we would ship that before Electron 3 though.


4B4F07D9 - Warriors Orochi 1

Validation

[X] I've read the FAQ.
[X] The Xenia build used is from a canary branch. (not MLBS/AlexVS/master/pull requests, etc)
[X] This issue isn't for help (tech support) with Xenia, or a game.
[X] I've checked if this game doesn't already have a compatibility report.

Xbox 360 Marketplace link
https://marketplace.xbox.com/Product/WARRIORS-OROCHI/66acd000-77fe-1000-9115-d8024b4f07d9?&DownloadType=Game
Xenia version
https://github.com/xenia-canary/xenia-canary/commit/921923472b48f3e29f695cda196be3d63a3b28cb/
Issues
Once a menu bg glitches audio starts repeating and game does not start.
render_target_path_d3d12 = "rov" does not fix anything.
d3d12_readback_resolve = true prevents the game to go just even in the clan choose part.
Log
xenia.zip
Screenshots

Labels
state-menus

Tested on: https://github.com/xenia-project/xenia/commit/7003e54e510fa2169a9434cdb8d608bff7f7be1e
xenia.zip

looping audio.
press F5 or enable clear_memory_page_state to clear artifacts.
game speed tied to FPS, don't disable vsync.

No changes since last report, freeze somewhere in the menus. It's either timing, thread affinities, or maybe both. Running Canary on 1 or 2 threads goes much further in the menus. After setting ignore_thread_affinities to false, which also makes things slower, I managed to reach gameplay.

This game runs well on Nukernel, somehow even audio is fine. Keep in mind this build is heavily experimental, possibly abandoned.
Screenshots from Nukernel

apu-garbage | backwards-compatibility-unsupported | vsync-off-speedup


SSL Certverification error when run the setup 2

SSLCertVerificationError                  Traceback (most recent call last)
/usr/lib/python3.10/urllib/request.py in do_open(self, http_class, req, **http_conn_args)
1347             try:
-> 1348                 h.request(req.get_method(), req.selector, req.data, headers,
1349                           encode_chunked=req.has_header('Transfer-encoding'))
18 frames
SSLCertVerificationError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1007)
During handling of the above exception, another exception occurred:
URLError                                  Traceback (most recent call last)
/usr/lib/python3.10/urllib/request.py in do_open(self, http_class, req, **http_conn_args)
1349                           encode_chunked=req.has_header('Transfer-encoding'))
1350             except OSError as err: # timeout error
-> 1351                 raise URLError(err)
1352             r = h.getresponse()
1353         except:
URLError: <urlopen error [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1007)>

Please describe when this occurs


Handle the old db migration. Need study.

ref: https://docs.expo.dev/versions/latest/sdk/sqlite/#importing-an-existing-database

There might be no way to solve it. Here is what I have found:

In my original app, the shelter.db file lives in path: /data/data/com.unicornio.happyinseat/database/shelter.db on Android device
In our new RN app, it lives in path: /data/data/com.unicornio.happyinseat/files/SQLite/shelter.db on Android device
When I try to find a way to assign certain path, the documentation of SQLite.ts says below and it means we simply can't assign path here:
/**

Open a database, creating it if it doesn't exist, and return a Database object. On disk,
the database will be created under the app's documents directory, i.e.
${FileSystem.documentDirectory}/SQLite/${name}.

The version, description and size arguments are ignored, but are accepted by the function

for compatibility with the WebSQL specification.
@param name Name of the database file to open.
@param version
@param description
@param size
@param callback
@return
*/
export function openDatabase(
name: string,
version: string = '1.0',
description: string = name,
size: number = 1,
callback?: (db: WebSQLDatabase) => void
): WebSQLDatabase {...}

I lost any clues at this point. If you have any ideas, please let me know.

Trying the doc Jerry provided above

It is doable. According to doc, we can use below logic to perform one time copy from existing db:
 await FileSystem.downloadAsync(
    Asset.fromModule(require(pathToOldDatabaseFile)).uri,
    FileSystem.documentDirectory + 'SQLite/shelter.db'
  );

and example from here as well: https://stackoverflow.com/questions/55622372/expo-sqlite-use-existing-database

To reproduce:

Install a debug version from original app
Install a debug version with same debug key from new app
Check if database can show old records.

** to obtain step 2, must change credentials.json temporally to override android debug key and build with eas.

Potential fix pushed at import-existing-db


Fixed incorrect icon url

Fixed invalid url for the Icon path which i haven't noticed before.

Hi, please resolve conflicts so we can merge this pr. thx.

Hmm, though the validation check would have caught that error.

Hmm, thought the validation check would have caught that error.

I think it would have to check if the HTTP response is 200. to catch this error.


Update apiextensions to save the releaseOperatorDeploy field

The releaseOperatorDeploy was being lost when unmarshalling, editing, and marshalling the Release in devctl release create because it was using a version of apiextensions without that field.

Dependency version update only, going with this.


Tutorial: Making your own custom Data Package creator and importer

As a Data Manager I want my data publishers to create data packages for me according to a specific metadata and/or data schema so that the data I get is high quality and consistent.
As a Data Manager I want to customize/build my own data package creator like datapackagist so that I can support the previous user story.

This issue was moved to frictionlessdata/frictionlessdata.io#57


fix: psql connect error

Codecov Report
Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (61684d9) 35.36% compared to head (1cc8891) 35.36%.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #164   +/-   ##
========================================
  Coverage    35.36%   35.36%
========================================
  Files           11       11
  Lines         1377     1377
========================================
  Hits           487      487
  Misses         793      793
  Partials        97       97

Files
Coverage Δ

pkg/cmd/gtctl/cluster/create/create.go
0.00% <0.00%> (ø)

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


Create Diet Recommendation for Pregnancy

Info about the related issue

[x] GSSOC Participant
[x] Contributor

Closes: #220
My solution involves collecting a comprehensive dataset with pregnant women's characteristics, pregnancy stage, dietary restrictions, nutritional needs, and food items with nutritional information. The data has been preprocessed to handle missing values, encode categorical variables, and scale numerical features. Multiple multi-label classification models, including Random Forest and neural network model, has been evaluated and trained on the dataset. Hyperparameter tuning has also been performed to enhance model performance.
Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] Any dependent changes have been merged and published in downstream modules.

Screenshots

Sir I will update the readme and dataset if you can review and let me know if this project will be accepted !


Service principal supports admin APIs

The considerations and limitations section indicates that the Service principle does not support any admin APIs, but that's not completely true, because it supports the read-only admin API (see: https://docs.microsoft.com/en-us/power-bi/admin/read-only-apis-service-principal-authentication).
There is a lot of confusion about this, so can you please clarify this?
Thank you very much.

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

ID: 794566fc-c06c-1d9c-b656-2e7b59bc2874
Version Independent ID: 4c57568f-c4f2-0bd6-b724-9868b2455d50
Content: Embed Power BI content in an embedded analytics application with service principal and an application secret enabling better embedded BI insights - Power BI
Content Source: powerbi-docs/developer/embedded/embed-service-principal.md
Service: powerbi
Sub-service: powerbi-developer
GitHub Login: @KesemSharabi
Microsoft Alias: kesharab

Thanks for your comment, @Anouk-Gorris. We’ve forwarded your feedback to the writer, who should respond to this thread shortly. Thanks!

Hi @Anouk-Gorris,
Thanks for your comment. I updated the service principal article to indicate that service principal supports some read-only admin APIs. See Considerations and limitations.
I also updated the Enable service principal authentication for read-only admin APIs article to include the list of Supported APIs in a separate section.
Thanks,
Kesem

Hi Kesem,
Thank you very much for this update.
Best regards,
Anouk
On Sun, Feb 7, 2021 at 10:29 AM Kesem Sharabi<EMAIL_ADDRESS>wrote:

Hi @Anouk-Gorris, Thanks for your comment. I updated the service principal
article to indicate that service principal supports some read-only admin
APIs. See Considerations and limitations. I also upd
External<EMAIL_ADDRESS>Report This Email
https://shared.outlook.inky.com/report?id=Y29sbGlicmEvYW5vdWsuZ29ycmlzQGNvbGxpYnJhLmNvbS80OTg1YWRmNDg5ZTg3N2QzZTAyNWFiZmNiMjk5MjZhMy8xNjEyNjkwMTY0Ljgy#key=f863d2d3d87ef0089ca9ad226a723a1f
FAQ https://www.inky.com/banner-faq/  Protection by INKY
https://www.inky.com
Hi @Anouk-Gorris https://github.com/Anouk-Gorris,
Thanks for your comment. I updated the service principal article to
indicate that service principal supports some read-only admin APIs. See Considerations
and limitations
https://docs.microsoft.com/power-bi/developer/embedded/embed-service-principal#considerations-and-limitations
.
I also updated the Enable service principal authentication for read-only
admin APIs
https://docs.microsoft.com/power-bi/admin/read-only-apis-service-principal-authentication
article to include the list of Supported APIs
https://docs.microsoft.com/power-bi/admin/read-only-apis-service-principal-authentication#supported-apis
in a separate section.
Thanks,
Kesem
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/powerbi-docs/issues/2795#issuecomment-774641958,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASTVRE3Z3AX6JQKVKXZSQSDS5ZMPBANCNFSM4W4ZXO5A
.

--
Anouk Gorris
Technical Writer
—
<EMAIL_ADDRESS>collibra.com


HHVM and PHP-fpm problem

Hi,
I have the following errors :
[Mon Mar 21 10:26:32 2016] [hphp] [4431:7f1171bff700:17:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:26:32 2016] [hphp] [4431:7f1171bff700:17:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused [Mon Mar 21 10:26:39 2016] [hphp] [4431:7f1169fff700:15:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:26:39 2016] [hphp] [4431:7f1169fff700:15:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused [Mon Mar 21 10:26:43 2016] [hphp] [4431:7f1171bff700:18:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:26:43 2016] [hphp] [4431:7f1171bff700:18:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused [Mon Mar 21 10:26:47 2016] [hphp] [4431:7f1169fff700:16:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:26:47 2016] [hphp] [4431:7f1169fff700:16:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused [Mon Mar 21 10:27:24 2016] [hphp] [4431:7f1171bff700:19:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:27:24 2016] [hphp] [4431:7f1171bff700:19:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused [Mon Mar 21 10:28:25 2016] [hphp] [4431:7f1169fff700:17:000001] [] \nWarning: failed to connect to <IP_ADDRESS> [111]: Connection refused [Mon Mar 21 10:28:25 2016] [hphp] [4431:7f1169fff700:17:000002] [] \nWarning: Failed connecting to redis server at <IP_ADDRESS>: Connection refused
sb_release -a : [
`No LSB modules are available.

Thanks !

Sorry for a delayed reply. We no longer support HHVM. Please use PHP 7.
We are cleaning up issue tracker and closing this issue because we won't be able to contribute to this discussion further.
Please use http://community.rtcamp.com/c/easyengine for future support questions.


fix(x/tokenfilter): return error OnRecvPacket

Resolves #2488

Codecov Report

Merging #2609 (df0e33c) into main (dea20c5) will decrease coverage by 0.01%.
Report is 1 commits behind head on main.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main    #2609      +/-   ##
==========================================
- Coverage   20.63%   20.62%   -0.01%
==========================================
  Files         133      133
  Lines       15346    15345       -1
==========================================
- Hits         3166     3165       -1
  Misses      11877    11877
  Partials      303      303

Files
Coverage Δ

x/tokenfilter/ibc_middleware.go
100.00% <100.00%> (ø)

So personally I don't think this is the correct action as I think it's outside the responsibility of the middleware to make such a validity check as I described in the comments, however I'm not married to this idea if we want to change it.

I don't think this is the correct action as I think it's outside the responsibility of the middleware to make such a validity check as I described in the comments

This is also my hesitation in approving this. I'm not sure we have a suitable enough reason to change this behavior. The work is good @ninabarbakadze, and apologies for not discussing this in the issue before this work was taken on.


switch to wsl 2 or use wsl 2 by default

hello, when creating a distro the distro is created on wsl 1. How to use wsl 2 ?

hello, when creating a distro the distro is created on wsl 1. How to use wsl 2 ?

In theory, it should be .\LxRunOffline.exe i -v 2 -n <DistribName> -d <InstallDir> -f <DistribFile>
Or just ommit the -v 2, it will use latest value 2 as default.
However, It seems that version setting for wsl not works, it just creates distribution using wsl1 for all.

@Xephobia Creating WSL2 distros isn't supported. However, you can convert an existing distro to WSL2 using wsl --set-version <name> 2
@minghu6 '-v is for filesystem version rather than WSL version. During the evolution of WSL1, it has used different versions of file systems which use different directory layout and file attributes. So it has nothing to do with WSL2.

@Xephobia Creating WSL2 distros isn't supported. However, you can convert an existing distro to WSL2 using wsl --set-version <name> 2
@minghu6 -v is for filesystem version rather than WSL version. During the evolution of WSL1, it has used different versions of file systems which use different directory layout and file attributes. So it has nothing to do with WSL2. (Probably I should make it clear in the help text.)

En, maybe the reason is the wincpp style makes me uncomfortable to read its detiails.
I have installde ditrib from miscrosoft store and move it using LxRunOffline move as a install-distribution-by-wsl2 workaround.


Fixed #6946

Description:
Fixes #6946
BREAKING CHANGE:
No breaking change expected
Related issue (if exists): #6946

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

Note: The bundler is not actively maintained in favor of turbopack


Do not use version literals in BOMs

The failed native tests are passing for me locally. Let's handle if we see oom exceptions in the future.


List dependencies to run upterm with appImage

I use alpine linux (without glibc) and it doesn't run.
There should be some dependencies like glibc and maybe more to run it with linux?

Added glibc, glib and fuse as dependencies for alpine linux, but still not starting.
/ # ./upterm-0.4.0-x86_64-linux.AppImage
./upterm-0.4.0-x86_64-linux.AppImage: Relink `/usr/lib/libintl.so.8' with `/usr/glibc-compat/lib/libc.so.6' for IFUNC symbol `stpcpy'
Segmentation fault

Which OS do you use, @pwFoo?

Alpine Linux
https://alpinelinux.org/
"Alpine Linux is built around musl libc and busybox"

@pwFoo, there was another guy with the same question and the same OS; can't find it for some reason. I'm afraid I don't know what's missing, but if you find out please let me know and I'll update README.

@pwFoo
I think you should install libc6-compat package.
https://pkgs.alpinelinux.org/packages?name=libc6-compat&branch=edge


Validation accuracy remains below 60%

Hello, I'm trying to verify I get correct results training with the forest trails dataset, using the instructions in the wiki, before I try to fine tune with my own data. However, I haven't been able to get validation accuracy above 60%.
I tried running 40 epochs, without much difference.  Here's a few screenshots and a caffe log.  What other info can I provide to help diagnose this issue?

caffe_output(5).log

Hello,
60% validation accuracy is certainly low if you are training orientation head on original Forest Trails. With ResNet-18 you should easily get up to 85%. How did you create the dataset? I would guess you used our idsia_trails_dataset_digits.py with undersampling? The model that you are using looks good to me, it's the same that we used to train orientation head.
There are few options you can try:

try creating larger dataset (oversampling)
try using ordinary CE (cross entropy) loss instead of our custom loss by setting all parameters like entScale and others to 0 in cee_loss layer.
try using a very small subset of your dataset to see if you can get higher accuracy.
try changing other parameters, most notably minibatch size and learning rate.

If everything is setup correctly, here is what you should get (or something like that):

If nothing of that helps, I will try to re-train our nets again but this might not happen until April as we have GTC 2018 next week and currently a bit busy.

Thanks for your detailed response.  Turns out the underlying issue was a corrupted Forest Trails dataset zip file.
I downloaded the sets individually, recreated the data set with oversampling, and ran the training again.
Results now look as expected...

Hi @TritonSailor , I ran into the same problem. My accuracy is only 50%. I tried to rebuild the dataset using  idsia_trails_dataset_digits.py, but nothing change. How did you solve the problem?
BTW, I have 1 Titan X and it took me 10 hours to complete 20 epochs. Is it normal?
Thank you.


5.17 Explain everything related to Fluentd

Signed-off-by: Asmit2952<EMAIL_ADDRESS>
Description 📜
Added documenatation on Fluentd
Fixes #653

Type of change 📝

[x] Documentation (Content Creation in the form of codes or tutorials)

Domain of Contribution 📊

[x] Open #Source

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

@Aryamanz29 Please review this PR.


Add VCS user

Codecov Report

Merging #256 (c2fdb58) into main (7833239) will decrease coverage by 0.04%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##             main     #256      +/-   ##
==========================================
- Coverage   70.60%   70.55%   -0.05%
==========================================
  Files          27       27
  Lines        1677     1681       +4
==========================================
+ Hits         1184     1186       +2
- Misses        380      381       +1
- Partials      113      114       +1

Impacted Files
Coverage Δ

pkg/kubeinteraction/secrets.go
58.82% <50.00%> (-2.47%)
:arrow_down:

pkg/pipelineascode/pipelineascode.go
72.45% <100.00%> (+0.16%)
: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 7833239...c2fdb58. Read the comment docs.


Add help dialog

fix #9

Codecov Report

Merging #10 (f299622) into master (a392df3) will decrease coverage by 1.69%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master      #10      +/-   ##
==========================================
- Coverage   80.92%   79.23%   -1.70%
==========================================
  Files          14       14
  Lines         409      419      +10
  Branches       96       97       +1
==========================================
+ Hits          331      332       +1
- Misses         12       21       +9
  Partials       66       66

Impacted Files
Coverage Δ

src/app.rs
69.69% <20.00%> (-7.84%)
:arrow_down:

src/handler/input_event_handler.rs
57.89% <0.00%> (+5.26%)
: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 a392df3...f299622. Read the comment docs.