Typings for ctx.scene.arg

ctx.scene.arg is needed but feels like a hack. Also, I didn't find a way to enforce typings on it.
It is used for passing initial data to top-level or nested scenes, and also to "return" data when a nested scene exits and the outer scene proceeds. I was considering merging it with ctx.scene.session but I'm not sure how (and if that's a reasonable approach at all).

I'm inclined to getting rid of it. Basically, there are 3 different cases for the arg:
Calling new scene
Calling ctx.scene.call("subscene", arg) could save arg into ctx.scene.session of the new scene instead.
"Go to" within the scene
Basically, we can get rid of arg. If the user needs it, they can use typed ctx.scene.session to pass data around.
Accessing result of calling a nested scene
This is useful in certain scenarios, but I don't know how to handle it without ctx.scene.arg? Unlike calling scene when we can simply treat argument as the initial value of theirs session, we can't put the return value into ours session as we will lose valuable data.
May be call it ctx.scene.exitValue (similar naming to bash exit code)?


Steering Issue #1

This the steering issue -- it documents our roadmap for the next six weeks!
Steering meeting: link
The overall theme of the sprint is end-user experience. Specific subissues:

[ ] Enable proc macros by default: https://github.com/rust-analyzer/rust-analyzer/issues/7328
[ ] Investigate memory usage https://github.com/rust-analyzer/rust-analyzer/issues/7330
[ ] Finish rowan work: https://github.com/rust-analyzer/rust-analyzer/issues/6857
[x] Provided we have sufficient bandwidth, look into resolving local items: ~~https://github.com/rust-analyzer/rust-analyzer/issues/5922~~ Mostly resolved by https://github.com/rust-analyzer/rust-analyzer/pull/7614 / https://github.com/rust-analyzer/rust-analyzer/pull/7627

We didn't ticked the boxes, but we made a great progress.
Understandably, actually ticking the boxes turns out to be challenging. To get better at these, we decided to officially install @matklad as "cheif makes-sure-that-the-boxes-are-ticked officer" for the next cycle.


The code file "train_dsin.py" fails to run.

Hi,
I have set up the enviroment and generated the input data for the DSIN model following the instruction. But I still failed to the train the model executing "train_dsin.py". The error messages are in the attachment.
Thank you for your time!

I revised the 152-th line in "2_gen_dsin_input.py",
sess_input_dict[sess_name][feat], maxlen=SESS_COUNT, padding='post'))
I have changed maxlen=SESS_COUNT to maxlen=DSIN_SESS_MAX_LEN, the previous bug was fixed, but here comes another error:

hi @Cobuild427 ,sorry for the mistake of DSIN_SESS_MAX_LEN .
The Error of GPU Sync failed  seems to be caused by the  environment，you can google it and search for some solutions .


Update login_system.rb to allow requests from our ip_stats script

The goal is to allow that script to access any page it likes without being logged in.
Question: is request available to this class?

Why not?

@pellaea  ahaa, Admin::Emails::FeaturesControllerTest#test_features was still failing.
That's because we actually do use authorize? in the Admin controller. Maybe you wrote that to facilitate using the login system for my controller refactor, now that i think about it.
This should be good to go, now. Lookin forward to finding out how we stack up against April!

Oooooh, thanks, I'll deploy now.  Thanks!
On Thu, Sep 7, 2023 at 3:49 PM andrew nimmo @.***>
wrote:

@pellaea https://github.com/pellaea ahaa,
Admin::Emails::FeaturesControllerTest#test_features was still failing.
That's because we actually do use authorize? in the Admin controller.
Maybe you wrote that to facilitate using the login system for my controller
refactor, now that i think about it.
This should be good to go, now. Lookin forward to finding out how we stack
up against April!
—
Reply to this email directly, view it on GitHub
https://github.com/MushroomObserver/mushroom-observer/pull/1603#issuecomment-1710688142,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYTNNK7Q3BOCZ6GF5RAMNTXZIQOFANCNFSM6AAAAAA4PK7JD4
.
You are receiving this because you were mentioned.Message ID:
@.***>


The values in array returning from lineSting forEachSegment are wrong

"ol": "^6.5.0",
Describe the bug
I try to get the start and end point coordinates of segment using forEachSegment method, like this:
feature.forEachSegment(function (from, to) {
   console.log('forEachSegment', from, to);
});

And the result in console seems correct

After stored the start and end point coordinates of each segment in another arrays, however, I got this:
[
     [
          [3576702.088271712, 2507822.580733749],  [3576702.088271712, 2507822.580733749]
     ],
    [
          [3576702.088271712, 2507822.580733749],  [3576702.088271712, 2507822.580733749]
     ],
]

Then I found the values of each array in console are all same as the final one:

See #11371

Got it, thanks.


[FEATURE] A way to change the test order

Is your feature request related to a problem? Please describe.
It might be beneficial to change the ordering of unit tests in some cases. For example, if there are two operations - "get user" and  "create user", then running the latter first will give more opportunities for the former one to return non-404 responses.
Describe the solution you'd like
It could be a hook that will allow to shuffle the order, or maybe a method on BaseSchema that will accept the ordering function.

Not sure if it is actually that useful - can be achieved with stateful tests


Only add scanners when there are no options

The default scanner list is now deprecated and also does not allow for disabling the secret scanner.
Similar to:

https://github.com/aquasecurity/trivy-azure-pipelines-task/pull/47/
Related to:
https://github.com/aquasecurity/trivy-azure-pipelines-task/issues/41
https://github.com/aquasecurity/trivy-azure-pipelines-task/issues/36

 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.

If the maintainers want I can chaange it so that the scanners are defined in the YAML file with a default value.

Any chance this could be approved? It would be really useful to have this task in our pipelines, this is the only thing that is missing for us.

@simar7 Can you help on this? It looks like someone forgot about this repository :(

Hey guys, is it being addressed? We're having issues in the CI pipeline because of this.

Agreed. This is still an issue for us.

Hi,
There's a typo in this commit, which causes the task to fail with the error FATAL	Fatal error	unknown flag: --scanner
The added line should say --scanners instead of --scanner


Fail PR test of pylint / pycodestyle if new files have suggestions

Impact of the new feature
WMCore CI
Is your feature request related to a problem? Please describe.
As we try to rely more on automatic checks and reduce human review and interaction, my suggestion is to make static code analysis of new modules to fail when the provided file is not free of issues.
Note that this should apply only to new files. For already existent files, it's hard to know what lines where changed in the PR, so we cannot enforce it.
Describe the solution you'd like
When evaluating a PR in jenkins, we should identify what are the new python modules and:

fail the pylint check (Py3 Pylint) if it reports any problems for new modules;
fail the pycodestyle (Pycodestyle) if it reports any problems for new modules.

Most of this code is already in place, but I noticed that we do not have a "Pycodestyle" check in GH (only in our report).
Describe alternatives you've considered
Not enforce it and just provide the this output to the PR author. But then it decreases the overall quality of our code.
Additional context
None

It would be great to have it in the repository, but we would have to run a massive autofix for pylint errors/warnings...


URI malformed

Environment
Docker
Version
No response
Describe the problem
I've used Homarr successfully for many months. I'm running it in Docker and running off the :latest tag.  Today, the site isn't accessible any longer. I've stopped the container, pulled the latest, restarted and the issue continues.  I have deprecation errors in the long and an error about a malformed URI. I haven't changed anything in the app in a few weeks, so I'm not sure what went wrong.  Here is the error in the logs when I try to access the page. Any help is greatly appreciated!
root@fileserver:/docker/containers/homarr# docker logs -f homarr
Listening on port 7575 url: http://0b364d8056f5:7575
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'
Error [URIError]: URI malformed
    at decodeURIComponent (<anonymous>)
    at parseCookieString (file:///app/.next/server/src/middleware.js:628:22)
    at new RequestCookies (file:///app/.next/server/src/middleware.js:678:28)
    at new NextRequest (file:///app/.next/server/src/middleware.js:851:22)
    at new NextRequestHint (file:///app/.next/server/src/middleware.js:1106:9)
    at adapter (file:///app/.next/server/src/middleware.js:1163:21)
    at next_middleware_loaderabsolutePagePath_private_next_root_dir_2Fsrc_2Fmiddleware_ts_page_2Fsrc_2Fmiddleware_rootDir_2Fhome_2Frunner_2Fwork_2Fhomarr_2Fhomarr_matchers_ (file:///app/.next/server/src/middleware.js:1313:18)
    at <unknown> (file:///app/node_modules/next/dist/server/web/sandbox/sandbox.js:73:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.runMiddleware (file:///app/node_modules/next/dist/server/next-server.js:1137:24)
TypeError: Cannot read properties of undefined (reading '_nextI18Next')
    at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
    at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)

Additional info
No response
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues
[X] You've tried to debug yourself

Hi @rubylaser ,
thank you for your issue.
Let me quickly grab your log and explain what's going on:
[DEPRECATED] default export is deprecated, instead import { create } from'zustand'

This is a deprecation issue, which has been caused by the change of the custom CSS input in the last update.
Although it is not optimal and should be fixed, it is okay to ignore it for now. @ajnart has already fixed this in #707.
Error [URIError]: URI malformed

This is the error, that keeps you from loading the page.
It seems like this has been caused by an update of an dependency.
We've already fixed this in #710 , but until then, you can clear the cache of your browser and it should work again.
TypeError: Cannot read properties of undefined (reading '_nextI18Next')

This is a known issue of our localization library, that we haven't been able to fix yet.
It might be an upstream issue, but we can't confirm yet.
This error does not keep you from loading the page and can be ignored too.
I hope that this helps. Let me know if you have other questions
TLDR: Try clearing your browser cache and reload the page

That is the fastest response I have ever received on any application issue. Thank you!   That fixed the issue up for me.  Thanks again for the speedy and thorough help and explanation of both issues!

That is the fastest response I have ever received on any application issue.

Haha, thanks!

 That fixed the issue up for me.

Don't worry. This issue is not obvious at all not not an error on your side.
It's an oversight on ours. It seems like this only happens, if you use a specific reverse proxy configuration.
Because none of the maintainers had this configuration, we never noticed this "bug".
Anyhow, this will be fixed in 0.11.5. I'll pin this issue, as some other users might experience the same issue.
Let me know if there is anything else I can help you with 💪

Hi! I recently installed Homarr and I'm having exactly the same issue mentioned. Here is the error log for more context: I'm accessing Homarr through Traefik and I also have an Authelia authentication layer. Below I provide the error and configuration of my services.
Error [URIError]: URI malformed
    at decodeURIComponent (<anonymous>)
    at parseCookieString (file:///app/.next/server/src/middleware.js:628:22)
    at new RequestCookies (file:///app/.next/server/src/middleware.js:678:28)
    at new NextRequest (file:///app/.next/server/src/middleware.js:851:22)
    at new NextRequestHint (file:///app/.next/server/src/middleware.js:1106:9)
    at adapter (file:///app/.next/server/src/middleware.js:1163:21)
    at next_middleware_loaderabsolutePagePath_private_next_root_dir_2Fsrc_2Fmiddleware_ts_page_2Fsrc_2Fmiddleware_rootDir_2Fhome_2Frunner_2Fwork_2Fhomarr_2Fhomarr_matchers_ (file:///app/.next/server/src/middleware.js:1313:18)
    at <unknown> (file:///app/node_modules/next/dist/server/web/sandbox/sandbox.js:73:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.runMiddleware (file:///app/node_modules/next/dist/server/next-server.js:1137:24)
TypeError: Cannot read properties of undefined (reading '_nextI18Next')
    at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
    at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)

Here is my homarr settings:
version: '3'

services:
  homarr:
    image: ghcr.io/ajnart/homarr:latest
    container_name: homarr
    security_opt:
      - "no-new-privileges:true"
    environment:
      - TZ=America/Argentina/Buenos_Aires
    restart: unless-stopped
    networks:
      - proxy
    volumes:
      - ./data/configs:/app/data/configs
      - ./data/icons:/app/public/icons
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.panel.entrypoints=websecure"
      - "traefik.http.routers.panel.rule=Host(`panel-homelab.com`)"
      - "traefik.http.services.panel.loadbalancer.server.port=7575"
      - 'traefik.http.routers.panel.middlewares=authelia@docker'

networks:
  proxy:
    external: true

Hi! I recently installed Homarr and I'm having exactly the same issue mentioned. Here is the error log for more context: I'm accessing Homarr through Traefik and I also have an Authelia authentication layer. Below I provide the error and configuration of my services.
Error [URIError]: URI malformed
    at decodeURIComponent (<anonymous>)
    at parseCookieString (file:///app/.next/server/src/middleware.js:628:22)
    at new RequestCookies (file:///app/.next/server/src/middleware.js:678:28)
    at new NextRequest (file:///app/.next/server/src/middleware.js:851:22)
    at new NextRequestHint (file:///app/.next/server/src/middleware.js:1106:9)
    at adapter (file:///app/.next/server/src/middleware.js:1163:21)
    at next_middleware_loaderabsolutePagePath_private_next_root_dir_2Fsrc_2Fmiddleware_ts_page_2Fsrc_2Fmiddleware_rootDir_2Fhome_2Frunner_2Fwork_2Fhomarr_2Fhomarr_matchers_ (file:///app/.next/server/src/middleware.js:1313:18)
    at <unknown> (file:///app/node_modules/next/dist/server/web/sandbox/sandbox.js:73:30)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async NextNodeServer.runMiddleware (file:///app/node_modules/next/dist/server/next-server.js:1137:24)
TypeError: Cannot read properties of undefined (reading '_nextI18Next')
    at AppWithTranslation (/app/node_modules/next-i18next/dist/commonjs/appWithTranslation.js:92:29)
    at Wc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:68:44)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:253)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:70:481)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:89)
    at $c (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:78:98)
    at bd (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:77:404)
    at Z (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:76:217)
    at Zc (/app/node_modules/react-dom/cjs/react-dom-server.browser.production.min.js:71:479)

Here is my homarr settings:
version: '3'

services:
  homarr:
    image: ghcr.io/ajnart/homarr:latest
    container_name: homarr
    security_opt:
      - "no-new-privileges:true"
    environment:
      - TZ=America/Argentina/Buenos_Aires
    restart: unless-stopped
    networks:
      - proxy
    volumes:
      - ./data/configs:/app/data/configs
      - ./data/icons:/app/public/icons
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.panel.entrypoints=websecure"
      - "traefik.http.routers.panel.rule=Host(`panel-homelab.com`)"
      - "traefik.http.services.panel.loadbalancer.server.port=7575"
      - 'traefik.http.routers.panel.middlewares=authelia@docker'

networks:
  proxy:
    external: true

I tried pulling the image again to see if it had changes but the problem persists.
EDIT: Already clean the cache and has an erratious behavior, sometimes it works and sometimes returns to throw the same error, on the page it shows only "Internal Server Error"

What version are you running?

This is the output of docker image inspect ghcr.io/ajnart/homarr:latest.
[
    {
        "Id": "sha256:5b2443197c8b0b00e315fb75fcdb8c712a5c0fde0806442b8a4d646b59f3ca59",
        "RepoTags": [
            "ghcr.io/ajnart/homarr:latest"
        ],
        "RepoDigests": [
            "ghcr.io/ajnart/homarr@sha256:39258ef601b8b503c7f0a6bb81adb317cd46478c48bb605818b45dbf0d1edb42"
        ],
        "Parent": "",
        "Comment": "buildkit.dockerfile.v0",
        "Created": "2023-02-24T23:31:54.784447207Z",
        "Container": "",
        "ContainerConfig": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": null,
            "Cmd": null,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "",
            "Entrypoint": null,
            "OnBuild": null,
            "Labels": null
        },
        "DockerVersion": "",
        "Author": "",
        "Config": {
            "Hostname": "",
            "Domainname": "",
            "User": "",
            "AttachStdin": false,
            "AttachStdout": false,
            "AttachStderr": false,
            "ExposedPorts": {
                "7575/tcp": {}
            },
            "Tty": false,
            "OpenStdin": false,
            "StdinOnce": false,
            "Env": [
                "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
                "NODE_VERSION=16.19.1",
                "YARN_VERSION=1.22.19",
                "NEXT_TELEMETRY_DISABLED=1",
                "NODE_ENV=production",
                "PORT=7575"
            ],
            "Cmd": [
                "node",
                "server.js"
            ],
            "ArgsEscaped": true,
            "Image": "",
            "Volumes": null,
            "WorkingDir": "/app",
            "Entrypoint": [
                "docker-entrypoint.sh"
            ],
            "OnBuild": null,
            "Labels": {
                "org.opencontainers.image.created": "2023-02-24T23:31:28.192Z",
                "org.opencontainers.image.description": "Customizable browser's home page to interact with your homeserver's Docker containers (e.g. Sonarr/Radarr)",
                "org.opencontainers.image.licenses": "MIT",
                "org.opencontainers.image.revision": "05423440f317f7305772c777a2a95eedd85e9b1f",
                "org.opencontainers.image.source": "https://github.com/ajnart/homarr",
                "org.opencontainers.image.title": "homarr",
                "org.opencontainers.image.url": "https://github.com/ajnart/homarr",
                "org.opencontainers.image.version": "0.11.5"
            }
        },
        "Architecture": "amd64",
        "Os": "linux",
        "Size": 145812038,
        "VirtualSize": 145812038,
        "GraphDriver": {
            "Data": {
                "LowerDir": "/var/lib/docker/overlay2/f579c8f26f0689cba4c4013da43ee14ddbfb13a52dbc3ba9fe0d4150be858876/diff:/var/lib/docker/overlay2/c1cbe418a567bb91234143e477f8284c16c3f8fbc96585d39f9cb332d9020b4e/diff:/var/lib/docker/overlay2/f3457b4fccb259157a203162261e74101fa12622c1b555b58cbf6154903029aa/diff:/var/lib/docker/overlay2/1a92e9a0d8166201cb6f02a6568d2ad755ad3eb803da4886c58657c3b94de2b1/diff:/var/lib/docker/overlay2/7f079af48d6460333dbb35e63486380ee8332d1c8a70aa386642a4332d2c2868/diff:/var/lib/docker/overlay2/33359f4cda2f754cfb6d606965e777b68ee1cfdb782d5ed73f4356680c63c909/diff:/var/lib/docker/overlay2/fa988ba0140ffac0e456c5f03338ae93822c2376680ca4193df6a8914c7f040e/diff:/var/lib/docker/overlay2/07d0ebcfb21c4cc41e70c422cde4955ebfabeb8751ea889a9b52dffede88ee3b/diff:/var/lib/docker/overlay2/8264bb1add15db85eae0d68691a264e7ac685594bc213928ce7683daafc728c2/diff",
                "MergedDir": "/var/lib/docker/overlay2/ebb3634c85f28bcd5da5b718832b351d73a1e8299929579081d2a25ec051d44d/merged",
                "UpperDir": "/var/lib/docker/overlay2/ebb3634c85f28bcd5da5b718832b351d73a1e8299929579081d2a25ec051d44d/diff",
                "WorkDir": "/var/lib/docker/overlay2/ebb3634c85f28bcd5da5b718832b351d73a1e8299929579081d2a25ec051d44d/work"
            },
            "Name": "overlay2"
        },
        "RootFS": {
            "Type": "layers",
            "Layers": [
                "sha256:7cd52847ad775a5ddc4b58326cf884beee34544296402c6292ed76474c686d39",
                "sha256:af1fa49a98d89e6b2549da4b4bfc43c9f15ff9cd06ce30cca4c888a1198ca607",
                "sha256:a1ce792246f9e7263ef38f455569bd9e57f899dad8716f8a7fcc4b80839d1b56",
                "sha256:67246b9bbb93f0d0f6343ef46696e95b6a09e36e49a78af133e373a7f8c6601e",
                "sha256:ae96fce3ce00f02410a5464dff9ad12efff6390f69162e990bfe793901e7db5a",
                "sha256:631ea1dbbde636e1e52d1560abdf39f2791209ef980e93d7c26e0ce815479fa0",
                "sha256:26ac02225c028cb959516940a5bdc0d3f7126c8af461441420e5a327b0a75a1c",
                "sha256:ec639284e98724da97b895931003bf81229d828a1dc2129515f396e8e54e01ee",
                "sha256:b840e10490cf8191bfe874b2d87e7ddd847f0589640e8419dcd56a7789961234",
                "sha256:0f4359c4c86fe8debc9ec2ce07c667b3070398ed2862cb7b5292dc720bc26381"
            ]
        },
        "Metadata": {
            "LastTagTime": "0001-01-01T00:00:00Z"
        }
    }
]

If I'm not mistaken it is "org.opencontainers.image.version": "0.11.5"

I am having the same problem as @benabhi. Using homarr docker image but in my case I access it through swag (not traeffik). I have tried using authelia or not with the same results. Clearing cache does not help. Accessing homarr directly in the internal IP (not through swag) does work. Let me know if I can provide any more info to help solving this issue.

#740 was a duplicated issue. But according to the information of the reporter, the issue seems to be with the cookie having multiple values.
Can anyone confirm this?
FYI: @ajnart

But according to the information of the reporter, the issue seems to be with the cookie having multiple values.

Yes, sorry for the duplicate. It seems that everything ran through my eyes, but at first I did not understand that this is the same problem as mine. But I can confirm that the problem disappears after deleting this cookie. If you need any additional information, I am ready to provide.

No worries.
I think this line is the issue:
https://github.com/ajnart/homarr/blob/05423440f317f7305772c777a2a95eedd85e9b1f/src/middleware.ts#L10
I don't really have time for this... But I'll quickly try to debug

What exactly is the authelia_session? Is that something you can dump here without rising your security?

Never-mind my previous values. I have found a way of reproducing this error:

Open the developer tools
Open the storage tab
Add a new cookie
Choose any cookie name you want, eg. session
Set a%AFcasdw as the value
Refresh the page - it crashes

I wasn't able to reproduce using a newer version of Next.js.
Can anyone of you confirm, using this test image? :test-url-malformed
Make sure to create a backup first

I run Authelia and SWAG in my environment. This new tag worked without issue for me across Chrome, Firefox, and Safari.

I can also confirm that the :test-url-malformed test image solves the problem in my case.

I haven't tested it thoroughly but seems to work fine! I have not seen any
problems with it.
El mié, 1 mar 2023, 16:23, Manuel @.***> escribió:

Great to hear! Where there any side effects in this image?
I am asking, because the updated Nextjs version might break existing code,
we haven't noticed yet.
—
Reply to this email directly, view it on GitHub
https://github.com/ajnart/homarr/issues/716#issuecomment-1450332319, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AFJLP7U26U2KJP26F6AJ5R3WZ5SVZANCNFSM6AAAAAAUZO6FOU
.
You are receiving this because you commented.Message ID:
@.***>

We don't have an ETA on this.
I am very busy at work currently, and don't have time for this - sorry.
@ajnart perhaps you could make a small 0.11.6 release for this?

Point of interest. I just got this message. Removed the docker image and pulled it again. App worked as expected.


Fix +[RLMObject createInRealm:withValue:] when given an NSArray

It now matches values in the array with properties in the order that the properties are declared. This is the documented behavior.
We had been matching values in the order that the properties were stored in the Realm file. This order often matched the declared order, but isn't guaranteed to.
Fixes #2697.
I need to figure out how to write a test for this.

testRearrangeProperties is the existing test which creates a Realm with a different column order then verifies that the accessor object works correctly.

Thanks for the pointer!

This is now ready for review.

It'd be good to also test -[RLMMigration createObject:withValue:] with prop order != col order, since funky things are done with the schema for migrations and while I suspect it works now, it's something that has a good chance of breaking.

:+1: great fix. Thanks for not ripping apart too many of the guts involved here.

:+1:


Support explicit column width in pixels

Problem
Achieving table-like layouts with Adaptive is hard because one has to use several ColumnSets on top of each other and there are only two ways to ensure that all columns in all those set have the same widths:

Use weights
Use auto and make sure the content always has the same width. That is easy enough with images, but very hard (near impossible) with text

Solution
Allow columns to have an explicit width, expressed in pixels. Essentially, make it possible in an easy and straightforward way to do what is already possible with a column containing an explicitly sized invisible image, which card authors will do to achieve the results they want.

Property
Type
Description

Column.pixelWidth
number
Defines the width of the column in pixels. pixelWidth overrides the width property.

Example use:
{
	"$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
	"type": "AdaptiveCard",
	"version": "1.0",
	"body": [
		{
		    "type": "ColumnSet",
		    "columns": [
		        {
		            "pixelWidth": 50,
		            "items": [
		                {
		                    "type": "Image",
		                    "url": "http://3.bp.blogspot.com/-Xo0EuTNYNQg/UEI1zqGDUTI/AAAAAAAAAYE/PLYx5H4J4-k/s1600/smiley+face+super+happy.jpg",
		                    "size": "stretch"
		                }
		            ]
		        },
		        {
		            "width": "stretch",
		            "verticalContentAlignment": "center",
		            "items": [
		                {
		                    "type": "TextBlock",
		                    "text": "This card has two ColumnSets on top of each other. In each, the left column is explicitly sized to be 50 pixels wide.",
		                    "wrap": true
		                }
		            ]
		        }
		    ]
		},
		{
		    "type": "ColumnSet",
		    "columns": [
		        {
		            "pixelWidth": 50
		        },
		        {
		            "width": "stretch",
		            "verticalContentAlignment": "center",
		            "items": [
		                {
		                    "type": "TextBlock",
		                    "text": "In this second ColumnSet, columns align perfectly even though there is nothing in the left column.",
		                    "wrap": true
		                }
		            ]
		        }
		    ]
		}
	]
}

As rendered:

The reason I went with pixelWidth is we also need explicit image sizes in pixels. But Image doesn't have a width nor a height property and I didn't want to overload the size property so it supports syntax line "50px*50px" which I think is horrible. A cleaner approach IMO was to introduce a width and a height property on Image, and given that the only accepted unit would be pixels I went for pixelWidth and pixelHeight. And therefore, I opted for pixelWidth for Column as well for consistency.
Overall it seems to me that introducing explicit properties for pixel sizes is cleaner. The rule would be that pixelWidth wins over width (same on Image).
Thoughts?

David,
Thanks for the explanation, with the image scenario, I completely agree that overloading size and having to parse a string to extract both the width and the height would be horrible.
But pixelWidth and pixelHeight start becoming restrictive if we want to introduce new measures and units in the future.
If we keep the names generic width and height for images, we could take pixels initially and have the initial version only accept pixels with the px unit specified in the string, but keeping the possibility in the future of accepting other units or ways of specifying the width and the height without introducing more properties.
The rule would still apply that width and height take precedence over the size parameter for images.

I used the names pixelWidth and pixelHeight so as to be able to type them as number and be explicit as to what unit they were expressed in.
What you suggest is definitely an option. However it requires that we make these properties strings instead of numbers. I would prefer using actual numbers when possible, it makes payload validation and schema-based IntelliSense easier. Also note that the "width" property in Column can be expressed as a number, representing a weight. I'd say it would be a bit weird to let authors specify a weight as a number but pixels as a string.
Typically, if we used "width" and "height" as string, it would likely be so we support values like "" for stretch, "auto" for automatic, "150px" for explicit pixels. Both "" and "auto" are already handled via the "size" property. So if we used "width" and "height" as strings IMO it would really only be in order to maybe support additional units in the future, such as "mm", "in", "em" or whatnot, and I am really not sure we would ever need to go there.
All that said, I am open. If there is a consensus around "width" and "height" as strings, I can live with it.

My opinion for future-proofing would be either (in order of preference):

Use type string with a syntax of <number><unit>. E.g., 50px or 2*
This seems aligned with what all other UI platforms have done at my knowledge.

Use type object with named properties for the value, and the unit

{
  "type": "Image",
  "width": {
     "value": 50,
     "unit": "px"
  }
}

The question is, do we actually need to future proof this? This page lists supported units in CSS; I do not imagine we'd ever want to support any of them aside from % (e.g. our weight sizing for Column) and explicit pixels...

BTW we might want to make a quick decision here, as I believe pixelWidth/pixelHeight is already in the process of being implemented in either the Android or iOS SDK (or both) and if we go with that for image then we should do the same for Column IMO.

I would rather keep Width and Height and have them as strings for future proofing even if we don't make use of other units.

I can live with that. That said going with this approach on Column will introduce some inconsistency given that Column.width can be expressed as a number to represent a weight.

I have one question regarding to relative width; i.e. width without unit (e.g. "px"). in a columnset with both explicit and relative width, how relative width should be handled? For example, column 1 has "50px" and column 2 has "5". Should we consider explicit width in determining the width for relative widths?

Any column that requests an explicit width in pixels gets what it asked for. All other columns (weight, auto or stretch) share the remaining space.

Documentation is done and in the mahiding/site1.1 branch.


Fix button halo drawing despite wire_drawoutline 0

Fixes: #2087

Going ahead with the merge since it's a very simple bugfix


0.2.0 tag/release not found

Hi there, on 2024-11-18 you announced a 0.2.0 at http://freshcode.club/projects/oomstaller pointing at HEAD, but there is no corresponding tag or release.

Thanks, fixed in 0.2.0
I believe the tool will have a niche usage, but in that niche may solve a particular problem. If you are looking for more exposure and feedback, maybe blog about a practical example with a specifically large build.

Thank you for your suggestion!


re-implement clustered prediction

we took it out while removing subpredictors because it was initially designed to be flexible enough to handle subpredictors on it's own, which just lead to convoluted code.
it wasn't widely used yet anyways.

the difficulty here is splitting our training data into more and more subsets. removing again.


Updates for v0.1.0 release

Number of build structure changes introduced in this release:

Now builds from submodule to allow for shared base sdk
Added future support for BLE libs and linkers to BGM111 and BGM13 families
Updates CMake structure for current work flow
Updates Silabs Gecko SDK to 5.8.0

Change-type: minor
Signed-off-by: Alex Bucknall<EMAIL_ADDRESS>

@Bucknalla Should we add instructions on how to build in the top level README?
Something like -

Update submodule with the command -
git submodule update --init
For balenaFin version 1.0 run
make bgm1b
& for balenaFin version 1.1 run
make bgm13

I also had issues with building the project locally on my development machine after running submodule update, make setup, and make bgm13.

@anujdeshpande it should now build for both BGM13 and BGM1B - I don't plan to include info in the README.md about the BGM13 as this module does not exist on any released versions of the fin so no point confusing people about its existence until it is available.

fe3e36d8c182bb63bf55dae268c9cffa74a7f611 should handle git submodule update --init

I want to just do some testing of this on a v1.0 and v1.1 before I release - concerned we might have some issues

@anujdeshpande did you get a chance to test this against a Fin?

Due to some issues with this building incorrectly, I'm going to close this PR and forward the history with changes to the original structure. I'd like to revisit this in the future.


:sparkles: :poop: changed one problem with registration form and allo…

…ws deactivation of buttons on chapter page.
This is handy for new chapters, so the registration buttons can be deactivated when you cannot register yourself yet.

Thanks @kleinicke! 👍


Inherit styles from UI theme

While looking for a way to display TODO's in my files, I found this package which does the trick nicely. Great job!
One thing I noticed though was that the results contrasted quite strongly with the rest of atom's UI. As I was about to add some styles to my user stylesheet to fix this, I realized it would be better if the package just picked up my UI themes styles. So here I am.
While I was in show-todo.less, I noticed there were a lot of unused styles. I added a few commits to clean it up a little, but anything after 9758249 is really just extra, so I guess include those at your discretion.
Let me know if anything is wrong. Thanks!

This looks great so far. Would you mind adding a screenshot?

Sure:

Is this something you would want added to the screenshot folder? If so, in a new file or replace preview.png?

Mainly in the PR lol. Don't worry about putting it in the repo :).
On Wed, Jan 14, 2015 at 11:40 PM Michael Hadley<EMAIL_ADDRESS>wrote:

Sure:
[image: selection_002]
https://cloud.githubusercontent.com/assets/2635560/5753970/9981f0a8-9c46-11e4-91c1-ec51ff1060e5.png
Is this something you would want added to the screenshot folder? If so, in
a new file or replace preview.png?
—
Reply to this email directly or view it on GitHub
https://github.com/jamischarles/atom-todo-show/pull/32#issuecomment-70050016
.

I was just about to do the same thing, good thing I checked the repo first haha

works great. Thx


Migrate start

This PR contains the flutter migrate start command. It is split off of https://github.com/flutter/flutter/pull/103145 and is dependent on https://github.com/flutter/flutter/pull/107665 landing first.

Pending https://github.com/flutter/flutter/pull/107665 still before last chunk of code can be added to this PR.

@GaryQian is this PR still relevant?

@GaryQian is this PR still relevant?

Speculatively closing this as obsolete--feel free to re-open if I'm mistaken.


the example always return "invalid channel id"

error message:
on_event(event: Err(JsonDecode(MissingFieldError("type"))), raw_json: "{"ok":false,"reply_to":0,"error":{"code":0,"msg":"invalid channel id"}}")

Does the slack team associated with the api key you are using have a #general channel?

Thank you.
There is a #general channel is the team. I added a new bot user and create a new RtmClient with api token for the bot.
However, in bot configuration page, I found my bot is in no channels. I am still new to slack and not  sure why. Do you have any suggestions?

It's been a while since I created a fresh bot integration, but I think sending /invite @bot_name in #general may be the solution.

I've just tested, and even with an offline bot, sending /remove @bot_name and then /invite @bot_name removed and added the bot to #general in my test group.

If that solves your problem then I'll add a note to the readme.

Yes, it works :)
"/invite @botname" resolved the issue and I can even see "<@U0LMWUZFD|botname> has joined the channel" in realtime response.

Excellent.
On Feb 12, 2016 08:13, "Piaoger"<EMAIL_ADDRESS>wrote:

Yes, it works :)
"/invite @botname https://github.com/botname" resolved the issue and I
can even see "<@U0LMWUZFD|botname> has joined the channel" in realtime
response.
—
Reply to this email directly or view it on GitHub
https://github.com/BenTheElder/slack-rs/issues/35#issuecomment-183322751
.


Add files.uploadV2

⚠ WIP!
This PR supersedes #90 and fixes #89. It builds upon previous work done by @taiga533; I intend to get it over the finish line.
TODO

[ ] Get full list of requested changes from #90 and add to this list!

Confirmed that we have a CLA on file for @racTaiga533 (signed 2023/12/15) - can ignore the CLA bot's complaints.

What's the status on this PR? I need this functionality, it would be nice if it was merged and deployed.

still not working, is there any way I can use this PR temporarily until it's merged?

The code provided does work but I'd probably change the API a bit. Is this moving forward? Shall/May I take over?


runtime/autoload/netrw: Correct symlink handling in tree liststyle

Fixes #2386 #445
The actual implementation of s:NetrwTreeDir causes symlinks to be
handled wrong in case the current netrw_liststyle is the tree view
('3'). This happens for file and for directory symlinks, which are
edited itself.
I tried to contact Mr. Campbell via mail but unfortunately there was no response yet.
Now I will use the PR to sync the request into the vim-dev maillist.
I use the beta from drchip too. It had behaved differently but did not solve the issue. The correction was done based on the stable version.

Codecov Report

Merging #3609 into master will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #3609      +/-   ##
==========================================
+ Coverage   77.36%   77.36%   +<.01%
==========================================
  Files          99       99
  Lines      139341   139341
==========================================
+ Hits       107800   107803       +3
+ Misses      31541    31538       -3

Impacted Files
Coverage Δ

src/version.c
85.2% <0%> (-0.9%)
:arrow_down:

src/if_xcmdsrv.c
83.63% <0%> (-0.72%)
:arrow_down:

src/diff.c
84.21% <0%> (-0.14%)
:arrow_down:

src/channel.c
83.18% <0%> (-0.08%)
:arrow_down:

src/os_unix.c
57.43% <0%> (-0.05%)
:arrow_down:

src/gui_gtk_x11.c
48.1% <0%> (ø)
:arrow_up:

src/ex_docmd.c
79.26% <0%> (+0.01%)
:arrow_up:

src/terminal.c
74.12% <0%> (+0.04%)
:arrow_up:

src/gui.c
57.03% <0%> (+0.15%)
:arrow_up:

src/term.c
60.57% <0%> (+0.2%)
:arrow_up:

... and 1 more

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 61fb8d8...9e2b877. Read the comment docs.

Any idea when this will be merged?

I suggest contacting charles directly. He might not notice here.

@chrisbra who is charles and how do i get ahold of him?

Charles is the maintainer of netrw and his account is @cecamp.
He prefers direct mail than contacting on GitHub.
His mail address is written at the top of each netrw source file. (Don't forget to remove 'N', 'O', 'S', 'P', 'A', 'M.)

Charles is the maintainer of netrw and his account is @cecamp.
He prefers direct mail than contacting on GitHub.
His mail address is written at the top of each netrw source file. (Don't forget to remove 'N', 'O', 'S', 'P', 'A', 'M.)

Charles let me know that he is getting a different email address.
I can give it when needed in a private mail.
--
I just planted an Algebra tree. It has square roots.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

For those who install Vim via Homebrew (Mac) and want to use this fix already, you can have Homebrew build vim from source and apply this patch like so:

brew edit vim
Add these four lines to the file (not sure if order matters, I put them above the install block):

patch do
  url "https://patch-diff.githubusercontent.com/raw/vim/vim/pull/3609.diff"
  sha256 "be474766e32ff81bbb9882a4e373f0a945623039d65ede1b36da72cba2de4f72"
end

brew uninstall vim
brew install --build-from-source vim

Opening symlinks from tree view is working now.

i write some code to temporarily solve this problem
https://github.com/vim/vim/issues/2386#issuecomment-1410216343


Add Cloud guide

One thing I want to rope into this: I want to write alt text for all the images. There's something wrong with that right now, so @jaclarke is helping me out with it. Wanted to go ahead and get this PR in just in case it needs to be merged before that's done.
Oh, and you may not love what I've done to make the "Join Cloud Waitlist" button work here. I just applied some inline styles. Dropping the raw HTML in didn't work. It stretched the full width of the text column.

Let's push this. We'll need another PR to educate people how to use secret keys to connect to cloud instances from vercel et al


Prevent readOnly attribute and its value being passed

Hi all,
I have some fields that are readOnly and their values are loaded from API requests. I don't want these values to be passed. Is there any way we can prevent readOnly attribute and its value from being passed?
Tried changing the key and valueTransformer,onSaved,onSubmitted to return null. But nothing worked.
Thanks!

Hi @yasirraku,
Thanks for the suggestion.
We may consider maybe setting a flag that will be used to decide on whether values from read-only fields should be returned.
What do you think @awhitford?

@danvick Are you thinking of adding a flag to the saveAndValidate() call?  (If skipReadyOnly is true then it could filter out the readOnly widgets when saving?) I think I could see that work.
Did you have another idea?

Yes! That pretty much sums up the idea.
Same way HTML doesn't send back values for readonly inputs - but ours would be optional.

Thank you so much @danvick @awhitford :)

@danvick In retrospect, rather than adding a skipReadOnly flag to the saveAndValidate method, I think an easier approach will be to override the onSave method to be a no-op, controlled by a FormBuilder property.  (Once my FormBuilderField class is a base class, this is easy to do.)

Ooh. Yeah, I was thinking skipReadOnly to be an attribute of FormBuilder rather than a param for saveAndValidate() method.


Adds Learning Module

Hello @Raahul-Singh! Thanks for opening this PR.

In the file pythia/learning/datamodule.py:

Line 61:24: E225 missing whitespace around operator
Line 95:85: E225 missing whitespace around operator
Line 98:83: E225 missing whitespace around operator
Line 101:101: E501 line too long (116 > 100 characters)
Line 102:101: E501 line too long (114 > 100 characters)
Line 107:5: E303 too many blank lines (2)
Line 116:101: E501 line too long (120 > 100 characters)
Line 119:101: E501 line too long (120 > 100 characters)
Line 132:54: E127 continuation line over-indented for visual indent
Line 134:101: E501 line too long (117 > 100 characters)
Line 136:54: E127 continuation line over-indented for visual indent
Line 140:52: E127 continuation line over-indented for visual indent
Line 142:101: E501 line too long (119 > 100 characters)
Line 144:52: E127 continuation line over-indented for visual indent
Line 151:53: E127 continuation line over-indented for visual indent
Line 153:101: E501 line too long (116 > 100 characters)
Line 155:53: E127 continuation line over-indented for visual indent

In the file pythia/learning/datasets.py:

Line 9:1: E302 expected 2 blank lines, found 1

In the file pythia/learning/tests/test_datasets.py:

Line 14:1: E302 expected 2 blank lines, found 1
Line 16:22: E203 whitespace before ':'
Line 27:21: E203 whitespace before ':'

In the file pythia/learning/tests/test_transforms.py:

Line 16:43: E231 missing whitespace after ','
Line 44:1: E302 expected 2 blank lines, found 1
Line 52:1: E302 expected 2 blank lines, found 1
Line 60:1: E302 expected 2 blank lines, found 1
Line 70:27: E231 missing whitespace after ','

In the file pythia/learning/transforms.py:

Line 8:42: E261 at least two spaces before inline comment
Line 9:48: E261 at least two spaces before inline comment
Line 42:24: E231 missing whitespace after ','
Line 152:36: E261 at least two spaces before inline comment

Do see the Hitchhiker's guide to code style


Linux - Can't work properly on GitHub Codespaces

Info
Framework (tested): net6.0, net7.0
Package version: 6.2.1
Environment: GitHub Codespaces, 4 cores, 16 GB RAM, 32 GB storage
Minimum reproduce steps

Set up a codespace with C# toolkits (can be automatically configured when creating codespace on any C# repos).

Wait for setting up, and run the following commands in bash:
dotnet new console -n TestTextCopy
cd ./TestTextCopy
dotnet add package TextCopy

Replace Program.cs with the following code:
using TextCopy;

string text = "Hello World!";
ClipboardService.SetText(text);

dotnet run.

Result
Unhandled exception. System.Exception: Could not execute process. Command line: bash -c "cat /tmp/tmp8us3aw.tmp | xsel -i --clipboard ".
Output:

Error: xsel: Can't open display: (null)
: Inappropriate ioctl for device

   at BashRunner.Run(String commandLine) in /_/src/TextCopy/BashRunner.cs:line 42
   at LinuxClipboard.InnerSetText(String tempFileName) in /_/src/TextCopy/LinuxClipboard_2.1.cs:line 42
   at LinuxClipboard.SetText(String text) in /_/src/TextCopy/LinuxClipboard_2.1.cs:line 29
   at TextCopy.ClipboardService.SetText(String text) in /_/src/TextCopy/ClipboardService.cs:line 61
   at Program.<Main>$(String[] args) in /workspaces/[ExampleRepo]/TestTextCopy/Program.cs:line 4

happy to accept a pull request that fixes this


Running a compiled function crashes RStudio

To reproduce: http://rpubs.com/fritzo/compiler_demo

I think this is an easy one.  Specifying arg1 and arg2 as double(2) in the
run function definition means 2-dimensional arguments, which is what the
compiled version is expecting. (i.e. arrays or matrices).
So either change the argument specifications to "arg1 = double(1)", to a
vector such as c(0.0, 0.5), or change the values of arg1, arg2, and
expectedResult to be R matrices (or dimension=2 arrays).  (for example,
array(0, c(2,2)).
On Wed, Apr 19, 2017 at 8:57 PM, Fritz Obermeyer<EMAIL_ADDRESS>wrote:

To reproduce: http://rpubs.com/fritzo/compiler_demo
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nimble-dev/nimble/issues/296, or mute the thread
https://github.com/notifications/unsubscribe-auth/AETW4XNgwmvx4dUkn5cotyV-lE7VBfZJks5rxq1-gaJpZM4NCag4
.

Right, this error was caught, but in the manner of our current run-time error-trapping, we emit an informational message and continue execution.  A topic that came up in our discussion earlier this week is that our run-time error trapping (from both permanent and generated C++) has been stable for a while, so it could make sense to make them bail out of execution and return safely to R.
I am going to close this issue since it is not a bug but leads to a more general feature request.  Let's make a wiki page or project to keep track of ideas for that.

The current warn-and-continue behavior of assertions leads to a bad user experience, in my case crashing RStudio and causing me to lose about 30 minutes of unsaved work. I'll write up a little NIM_ASSERT(-,-) macro in C++ to avoid this pain in the future.

That would be great.  See section 6.2 of Writing R Extensions for R's API to stop() and warning().  I'd guess error() is a good way to bail out back to R.  You could start by using it at the warning you triggered, which is in inst/include/nimble/RcppNimbleUtils.h for testing purposes.  Then we can build it into generated run-time checks ("assertions" in the exprClass objects).  I note that in the particular case you triggered, we could probably provide correct treatment for wrong number number of dimensions or wrong scalar type, but at the time we preferred not to.

Fixed by #297


Use prom-client for metrics

https://github.com/paritytech/substrate-matrix-faucet/blob/82728e9e91e1978dbd623c616fe8e8c53dd8c7a7/src/server/routes/metrics.ts#L52

Done


futures_unordered::IterMut does not implement Send

I'm trying to write code that looks like this:
async fn foo() {
    for future in futures_unordered.iter_mut() {
        do_something_async().await;
    }
}

This, unfortunately, makes the future returned by foo non-Send because the IterMut exists across an await boundary. Is it possible to fix this and have IterMut implement Send?

Yes, there's no interesting reason why it isn't Send. I suspect it's just "an impl needs to be added" since it contains raw pointers.


[COU] Adding more details while the shipment is In Transit

When we click the "Scan & Pick-up Shipment" button, the status automatically (as in the case of In Preparation) will change to Pick-up at Warehouse (for Sponsor, Site) /  Dispatched (for CMO).

Before, the Courier first added the shipment ID (1 - scan shipment -> 2 - add details (shipment ID) -> 3 - sign) and then continued updating the shipment details. We are slightly improving the procedure by combining these steps (as shown below).
The user will have a 5-step wizard with the following steps:
1 - Scan Shipment
2 - Add Shipment Details
3 - Add Documents
4 - Add Comment
5 - Sign
1 - Scan Shipment

Note: To be discussed (see figure above)
2 - Add Shipment Details
All details to be added:
•      Shipment ID
•      Master-Way Bill Number
•      HS Code [mandatory]
•      Bill of Landing No. [text]
•      Service type [text]
•      Inco Terms [drop-down]
•      EXW Works
•      Free Carrier - FCA
•      Carrier Paid to - CPT
•      Carrier & Insurance Paid to - CIP
•      Delivered at Place - DAP
•      Delivered Duty Paid - DDP
•      Other
•      Spot/Contract Rates [text]
•      Temperature Logger ID

3 - Add Documents
you
4 - Add Comment

5 - Sign

Once the Courier clicked "Sign", the status of the shipment will be changed to In Transit (from Pick-up at Warehouse).

@klivit it is totally wrong to change the status of the shipment without performing the logistic scan

@klivit it is totally wrong to change the status of the shipment without performing the logistic scan

@Mastaleru Unfortunately, scanning here has crucial role in minimizing human error (and many related issues). I propose to discuss this issue today to brainstorm on all our options to make it feasible (or modify).

We did not merge the steps but keep two stages (1 -- shipment ID + logger ID / 2-- New shipment details for Courier)


Add support for passing in a changeset transformer when opening a SharedRealm

@bdash

@bdash do we need to do anything else before we can merge?

@alazier, responding to my questions above would be a start.

Didn't see your latest comment...

@bdash this has been updated to use the latest sync version which stores the cooker as a shared_ptr. @radu-tutueanu

I'm not quite sure what's happened here, but the commit history appears to show a bunch of duplicated commits. Can we sort that out before merging?


add prepend() & append() to TupleN, N in [1..7].

for exemple in Tuple2 :
public <A> Tuple3<A, T1, T2> prepend(A v) {
    return Tuple.of(v, _1, _2);
}

public <A> Tuple3<T1, T2, A> append(A v) {
    return Tuple.of(_1, _2, v);
}

[Current coverage][cc-pull] is 97.10%

Merging [#1452][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.15%

@@             master      #1452   diff @@
==========================================
  Files            86         86
  Lines         10384      10398    +14
  Methods           0          0
  Messages          0          0
  Branches       1825       1825
==========================================
- Hits          10099      10097     -2
- Misses          159        174    +15
- Partials        126        127     +1

Powered by Codecov. Last updated by [81fa282...ef4c355][cc-compare]
[cc-base-branch]: https://codecov.io/gh/javaslang/javaslang/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/javaslang/javaslang/compare/81fa282f6102312e87f2f67615c615daa3746d22...ef4c3558a16d679184ff630845edddf0f624caf5?src=pr
[cc-pull]: https://codecov.io/gh/javaslang/javaslang/pull/1452?src=pr

Hi @ronanM
Could you add tests?

@ruslansennov not yet, sorry.

@ruslansennov tests added.

Tuples are no collections, they intentionally do not have operations such as insert, remove, head, tail, ...
Do you have a real-world use-case for adding these operations? Instead of building a tuple step-by-step with append and prepend, why not just create a tuple in one step?
I'm not sure we need these methods. Please convince me :-)

Like HList use cases.

https://github.com/milessabin/shapeless/wiki/Feature-overview:-shapeless-2.0.0#hlist-style-operations-on-standard-scala-tuples

I understand, let's pull it in. Please fix the conflicts.

Merged, mvn ok, but I don't know what to do with Break CI build on PRs where committed differ from generated sources ?

@ronanM you have to add all changed files to this PR (including changes in generated sources). These files are orphaned:
ruslan@FB160424:~/proj/javaslang$ mvn test; git status
On branch tuple-prepend-append
Your branch is up-to-date with 'ronan/tuple-prepend-append'.
Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git checkout -- <file>..." to discard changes in working directory)

	modified:   javaslang/src-gen/main/java/javaslang/Tuple1.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple2.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple3.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple4.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple5.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple6.java
	modified:   javaslang/src-gen/main/java/javaslang/Tuple7.java

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

@ruslansennov Ooops, I thought all files were committed.

Why Tuple0 has no append/prepend methods?

Tuple0 prepend() & append() added.

@ronanM please review my PR into your repo

Hi @ronanM, thanks for the contribution! I have some comments...

These all cooments is my fault, sorry :)

Hi @ronanM, many thanks - looks good to me!
The build currently breaks because you forgot to check in the generated Tuples of your last Generator.scala change (removed one newline).
Please check in the generated Tuples and I will pull it in.

Thx!

Hi @ronanM, could you please create a new PR. This one broke the build, see #1505 and https://travis-ci.org/javaslang/javaslang/builds/153129703

New PR created #1509


Does not build due to v changes.

I'll find the error soon.

@Ccode-lang https://github.com/adsharma/py2many has a V backend now, I am focusing my efforts on that.

👍


Data validation formulae undefined bug

Receiving the following error:
TypeError: Cannot read property 'forEach' of undefined
      at node_modules/exceljs/lib/xlsx/xform/sheet/data-validations-xform.js:114:23
      at node_modules/exceljs/node_modules/lodash/lodash.js:4944:15
      at baseForOwn (node_modules/exceljs/node_modules/lodash/lodash.js:3001:24)
      at node_modules/exceljs/node_modules/lodash/lodash.js:4913:18
      at Function.forEach (node_modules/exceljs/node_modules/lodash/lodash.js:9359:14)
      at render (node_modules/exceljs/lib/xlsx/xform/sheet/data-validations-xform.js:83:9)
      at render (node_modules/exceljs/lib/xlsx/xform/sheet/worksheet-xform.js:119:30)
      at node_modules/exceljs/lib/xlsx/xlsx.js:342:24
      at Array.forEach (native)
      at node_modules/exceljs/lib/xlsx/xlsx.js:340:24
      at Promise._execute (node_modules/bluebird/js/release/debuggability.js:300:9)
      at Promise._resolveFromExecutor (node_modules/bluebird/js/release/promise.js:481:18)
      at new Promise (node_modules/bluebird/js/release/promise.js:77:14)
      at Object.addWorksheets (node_modules/exceljs/lib/xlsx/xlsx.js:334:12)
      at node_modules/exceljs/lib/xlsx/xlsx.js:418:21
      at tryCatcher (node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (node_modules/bluebird/js/release/promise.js:510:31)
      at Promise._settlePromise (node_modules/bluebird/js/release/promise.js:567:18)
      at Promise._settlePromise0 (node_modules/bluebird/js/release/promise.js:612:10)
      at Promise._settlePromises (node_modules/bluebird/js/release/promise.js:691:18)
      at Promise._fulfill (node_modules/bluebird/js/release/promise.js:636:18)
      at PromiseArray._resolve (node_modules/bluebird/js/release/promise_array.js:125:19)
      at PromiseArray._promiseFulfilled (node_modules/bluebird/js/release/promise_array.js:143:14)
      at Promise._settlePromise (node_modules/bluebird/js/release/promise.js:572:26)
      at Promise._settlePromise0 (node_modules/bluebird/js/release/promise.js:612:10)
      at Promise._settlePromises (node_modules/bluebird/js/release/promise.js:691:18)
      at Async._drainQueue (node_modules/bluebird/js/release/async.js:133:16)
      at Async._drainQueues (node_modules/bluebird/js/release/async.js:143:10)
      at Immediate.Async.drainQueues (node_modules/bluebird/js/release/async.js:17:14)

for a data validation that is parsed as:
{
    "type": "decimal",
    "allowBlank": true,
    "showInputMessage": true,
    "promptTitle": "Decimal",
    "prompt": "Value must be a decimal"
}

See #253


Cannot configure O3D303

When I want to use ROS to configure the O3D303 camera by using "roslaunch o3d3xx config.launch infile:=/home/administrator/wspace/src/o3d3xx/json/ex_camera2.json", I always get the message:
[ INFO] [1458240896.994179177]: status=-9014
[ INFO] [1458240896.994316742]: msg=XMLRPC value out of range
I also tried to use "rosservice call /o3d3xx/camera/Dump > /tmp/camera.json" to get the current setting, do nothing and run "roslaunch o3d3xx config.launch infile:=/tmp/camera.json" I will get the message:
[ INFO] [1458241148.110545217]: status=-1
[ INFO] [1458241148.110678292]: msg=(1): expected object or array
Does anybody know how to fix it? Thank you!

Can you please provide the version of your firmware on the camera. For example dumped by 3d3xx-dump

It is "O3D3xx FW 1.3.1001".
I tried to run o3d3xx-dump, but got the error:
Failed to dump camera configuration:
XMLRPC call timed out

A couple of things... First, as @graugans says, please make sure you are using a supported software stack. IFM firmware + libo3d3xx + o3d3xx-ros. The main README's for both libo3d3xx and o3d3xx-ros have software compatibility matrices that will allow you to trace to the proper stack.
Now for the specific issues...

When I want to use ROS to configure the O3D303 camera by using "roslaunch o3d3xx config.launch infile:=/home/administrator/wspace/src/o3d3xx/json/ex_camera2.json", I always get the message:
[ INFO] [1458240896.994179177]: status=-9014
[ INFO] [1458240896.994316742]: msg=XMLRPC value out of range

Likely some value you are setting in the file exceeds a valid range. What did you change? I'd start there. Also, you can look at the libo3d3xx logs (they go to /tmp by default) to get more info.

I also tried to use "rosservice call /o3d3xx/camera/Dump > /tmp/camera.json" to get the current setting, do nothing and run "roslaunch o3d3xx config.launch infile:=/tmp/camera.json" I will get the message:
[ INFO] [1458241148.110545217]: status=-1
[ INFO] [1458241148.110678292]: msg=(1): expected object or array

The output from rosservice is not valid json. The return values from the service call are annotated by the rosservice variable names. You either have to edit the file so it is actually valid JSON or just use the libo3d3xx equivalent command line tools to the rosservice calls. Those are o3d3xx-config and o3d3xx-dump.

I tried to run o3d3xx-dump, but got the error:
Failed to dump camera configuration:
XMLRPC call timed out

Sounds to me your network setup is odd. The XMLRPC timeouts are coming directly from libcurl. Is your routing table correct? Are you on a noisy network (e.g., Wifi)? Anything else non-standard or wierd we should be aware of when helping you troubleshoot this?

Solved in #47. Thank you!


Add benchmark tests and new infrastructure for matrix based methods

Many changes to accommodate matrix based transforms, including widespread variable renaming.  Benchmarks are added, but are only compiled for release builds to allow rapid debug builds still.

Codecov Report

Merging #41 into master will decrease coverage by 0.2%.
The diff coverage is 93.45%.

@@            Coverage Diff             @@
##           master      #41      +/-   ##
==========================================
- Coverage   95.13%   94.92%   -0.21%
==========================================
  Files          41       44       +3
  Lines        3658     4415     +757
==========================================
+ Hits         3480     4191     +711
- Misses        178      224      +46

Impacted Files
Coverage Δ

src/helpme.h
97.33% <ø> (-0.54%)
:arrow_down:

test/unittests/unittest-fullrun-compressed.cpp
100% <100%> (ø)

test/unittests/unittest-tensor.cpp
100% <100%> (ø)

src/gamma.h
95.95% <100%> (ø)
:arrow_up:

src/matrix.h
96.95% <100%> (ø)
:arrow_up:

test/unittests/unittest-fullrun.cpp
100% <100%> (ø)
:arrow_up:

test/unittests/unittest-latticeupdates.cpp
100% <100%> (ø)
:arrow_up:

python/pywrappers.cc
90.24% <100%> (+0.24%)
:arrow_up:

test/fullexample_parallel.cpp
98.63% <100%> (+0.51%)
:arrow_up:

test/fullexample_parallel.F90
93.75% <100%> (+1.15%)
:arrow_up:

... and 14 more

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 0cac0e6...7949c6d. Read the comment docs.

This pull request introduces 12 alerts and fixes 8 when merging 7949c6d2b95167b436767c436745b2e8776c0e01 into 0cac0e6b0c1fb674b374f6bc7a6e797a46687485 - view on LGTM.com
new alerts:

9 for Multiplication result converted to larger type
3 for Unused import

fixed alerts:

8 for Multiplication result converted to larger type

Comment posted by LGTM.com


fix: always download the last file #81

Codecov Report

Merging #86 (fdb35c2) into master (cd0eac0) will increase coverage by 0.63%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##           master      #86      +/-   ##
==========================================
+ Coverage   94.10%   94.73%   +0.63%
==========================================
  Files           9        9
  Lines         475      475
==========================================
+ Hits          447      450       +3
+ Misses         28       25       -3

see 2 files with indirect coverage changes


Pika timeout fix

Proposed changes:

fix https://github.com/RasaHQ/rasa-x/issues/1399
use SelectConnection instead of BlockingConnection in order to be able to process heart beat events from the event broker in the background

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog
[x] reformat files using black (please check Readme for instructions)

Can you make sure to test this on docker before merging (if you haven't done so)?

I tested it with local Rasa connected to a RabbitMQ running in docker 👍


Share problem

Once I select share only for me last the first time. It will never more ask me.
What can I do?
Tks

I don't understand the issue could you give more details?

Hi, Rendy:
Sorry about my first message.
I'm using facebookclient to login and share photos to facebook.
The very first time I shared, I had to answer a question informing if it
was to be shared only for me, public, etc.
I answered to share only for me.
The issue is that I didn't get this question any more. So I can't change my
option to public or what else. All my shares always go to be seen only for
me.
I don't know how to "reset" this.
Can you help me?
Thanks
On Wed, Apr 11, 2018 at 11:34 PM, Rendy Del Rosario <
<EMAIL_ADDRESS>wrote:

I don't understand the issue could you give more details?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/CrossGeeks/FacebookClientPlugin/issues/20#issuecomment-380655773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOuSPSuyKI8rUXqsAJ2gZmWKsldEq4Rbks5tnr0zgaJpZM4TQ7Kp
.


No-blocking operations for web based clients

What are you trying to accomplish? The current design of ewebsock is already non-blocking

Hello @emilk, thanks for your response, we used ewebsokets to implemented this https://github.com/virto-network/virto-sdk/blob/8e5fadbb4e415e9514b5365401f3598d8264668e/sube/src/ws.rs while I saw we can use the wake up function, there are situations where the context that the wake up needs is not longer accesible by it. In our case we need to "wait" until new messages are coming, but as you were using "try_receiv" it requires to have a loop in a new thread that constantly are asking if there are new messages available, thats why I migrated it to use Future Streams to "wait" until a new message are ready and avoid use a blocking loop and use the same thread in web or native contexts.
// before
 // waits to wake up function to be called
 while let Ok(Some(event)) = receiver.try_receive() {

 }
// now you can use this  without blocking the current thread
  while let Some(event) = receiver.next().await { {
        // custom logic here
    }

Hey @emilk , did you have the chance to review it?

@emilk any thoughts on top of this? or do you recommend to fork a new brand library with this specific changes?

I'm sorry, I don't have a lot of time on my hands.
I don't want to add a bunch of async to ewebsock if it can be avoided.
I also don't want the API for web and native to diverge.
If you want to be able to write .await instead of using the callback-based API, then please see if that is something you can build on top of the existing ewebsocket API. If not, make it opt-in.


[SR SQL Planner Summer Camp]New Parser and Analyzer support DropRoleStmt

What type of PR is this：

[x] enhancement

Which issues of this PR fixes ：

Fixes #7950

run starrocks_fe_unittest

[FE PR Coverage Check]
:disappointed: fail : 8 / 13 (61.54%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[395]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
0
3
00.00%
[547, 548, 550]

:large_blue_circle:
com/starrocks/analysis/DropRoleStmt.java
2
3
66.67%
[54]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeStmtAnalyzer.java
2
2
100.00%
[]

run starrocks_admit_test

run starrocks_admit_test

[FE PR Coverage Check]
:disappointed: fail : 8 / 13 (61.54%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/ast/AstVisitor.java
0
1
00.00%
[406]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeChecker.java
0
3
00.00%
[551, 552, 554]

:large_blue_circle:
com/starrocks/analysis/DropRoleStmt.java
2
3
66.67%
[54]

:large_blue_circle:
com/starrocks/sql/analyzer/Analyzer.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
2
2
100.00%
[]

:large_blue_circle:
com/starrocks/sql/analyzer/PrivilegeStmtAnalyzer.java
2
2
100.00%
[]


[Request] Add Build Tools for Visual Studio 2019

Would be nice to have the Microsoft C++ Compiler available.
Visit
https://visualstudio.microsoft.com/downloads/
Under All downloads/Tools for Visual Studio 2019/Build Tools for Visual Studio 2019
"These Build Tools allow you to build Visual Studio projects from a command-line interface. Supported projects include: ASP.NET, Azure, C++ desktop, ClickOnce, containers, .NET Core, .NET Desktop, Node.js, Office and SharePoint, Python, TypeScript, Unit Tests, UWP, WCF, and Xamarin."

That would be hard since it is installed using the visual studio installer and has multiple add-ons.

wish @Microsoft would just help everyone that will have to deal with installing that package in a sane, configurable manner.
not doing that is pure sadism.
jokes aside, its just as expected of them. they are the only blockers for this and many other goodies for users and developers.

CLICK ME

aside:
if you want to let @Microsoft know the obvious. just go to https://visualstudio.microsoft.com/downloads/# and click on  the blue Feedback button on right side(ensure ad-block doesn't block or interfere with it, I had to disable 'ublock origin'). Rate the page 1 star. And give your feedback about the current situation.
3 of my suggestions would be-

installing Build tools 2019 and
ask them to support installation via scoop
and per-user installs like VSCode supports.

The more people make noise about it, the more incentive they will have. I hope.
Another approach would be to boycott their  tools. And use and encourage better tools. Unless users and developers unite to improve the ecosystem. But that is mostly a dream.

developers always have to wade in cesspools of crap. only to make these installers work in a sub-par manner.
hope you succeed despite all the challenges.
good luck! b(￣▽￣)d

cheers tratTalks

How about just Visual Studio Installer

I suspect this (https://docs.microsoft.com/en-us/visualstudio/install/use-command-line-parameters-to-install-visual-studio?view=vs-2019) may work.
Perhaps also consider this (https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk/)
From what I have tested, you simply has to install the individual build tool component and Windows SDK. Then, export the proper PATH, LIB, and INCLUDE` variable to build c++ software.

This issue is actually duplicate with #1861

#1861


I have some troubles to build

I want to make some adjustments / PRs but I have some bigger problems to get it running. I don't know if it is a problem with the plugin or with my environment.
All issues are happening with a clean copy of the branch develop
Issues:
1. install
npm install:
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/webpack
npm ERR!   dev<EMAIL_ADDRESS>from the root project

Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
pnpm install
 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies
.
└─┬ webpack-manifest-plugin 3.1.1
  └── ✕ unmet peer<EMAIL_ADDRESS>found 4.42.0

Changing to 4.44.2 solves the problem:
https://github.com/privatenumber/webpack-localize-assets-plugin/blob/77a5c924b5b5e6794ef9f38182722d8510549222/package.json#L71
2. pnpm run build:
dist is generated but following is printed. I installed the packages with pnpm install. With npm install the error is not showing.
><EMAIL_ADDRESS>build D:\Daten\Projekte\Github\webpack-localize-assets-plugin
> tsc

node_modules/.pnpm/@types+mini-css-extract-plugin@2.4.0/node_modules/@types/mini-css-extract-plugin/index.d.ts:10:23 - error TS4090: Conflicting definitions for 'node' found at 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+node<EMAIL_ADDRESS>and 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+node<EMAIL_ADDRESS>Consider installing a specific version of this library to resolve the conflict.
  The file is in the program because:
    Type library referenced via 'node' from file 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+webpack<EMAIL_ADDRESS>with packageId
'<EMAIL_ADDRESS>    Type library referenced via 'node' from file 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+mini-css-extract-plugin<EMAIL_ADDRESS>with packageId '<EMAIL_ADDRESS>
10 /// <reference types="node" />
                         ~~~~

  node_modules/.pnpm/@types+webpack@4.41.32/node_modules/@types/webpack/index.d.ts:28:23
    28 /// <reference types="node" />
                             ~~~~
    File is included via type library reference here.

node_modules/.pnpm/@types+webpack-sources@2.1.0/node_modules/@types/webpack-sources/index.d.ts:7:23 - error TS4090: Conflicting definitions for 'node' found at 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+node<EMAIL_ADDRESS>and 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+node<EMAIL_ADDRESS>Consider installing a specific version of this library to resolve the conflict.
  The file is in the program because:
    Type library referenced via 'node' from file 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+webpack<EMAIL_ADDRESS>with packageId
'<EMAIL_ADDRESS>    Type library referenced via 'node' from file 'D:/Daten/Projekte/Github/webpack-localize-assets-plugin/node_modules/.pnpm/@types+webpack-sources<EMAIL_ADDRESS>with packageId '<EMAIL_ADDRESS>
7 /// <reference types="node" />
                        ~~~~

  node_modules/.pnpm/@types+webpack@4.41.32/node_modules/@types/webpack/index.d.ts:28:23
    28 /// <reference types="node" />
                             ~~~~
    File is included via type library reference here.

src/multi-locale.ts:2:64 - error TS7016: Could not find a declaration file for module 'webpack-sources'<EMAIL_ADDRESS>implicitly has an 'any' type.
  If the 'webpack-sources' package actually exposes this module, consider sending a pull request to amend 'https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/webpack-sources'

2 import { RawSource, SourceMapSource, SourceAndMapResult } from 'webpack-sources';
                                                                 ~~~~~~~~~~~~~~~~~

Found 3 errors.

 ELIFECYCLE  Command failed with exit code 2.

3. Tests are failing

npm run build
npm run test

 Webpack 4.44.2 › passing › dynamically load relative locale json path

    expect(received).toBe(expected) // Object.is equality

    Expected: "Hello World"
    Received: "Hello world-key"

      942 |                     delete watching.require.cache['/dist/index.en.js'];
      943 |                     enBuild = watching.require('/dist/index.en.js');
    > 944 |                     expect(enBuild).toBe('Hello World');
          |                                     ^
      945 |
      946 |                     watching.fs.writeFileSync('/src/locales/en.json', JSON.stringify({
      947 |                             'world-key': 'World',

      at Object.<anonymous> (tests/webpack-localize-assets-plugin.spec.ts:944:20)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 2 skipped, 40 passed, 43 total

4. npm run test:wp5 - webpack-cli
One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:
 - webpack-cli (https://github.com/webpack/webpack-cli)
   The original webpack full-featured CLI.
We will use "npm" to install the CLI via "npm install -D".
Do you want to install 'webpack-cli'

I suggest to add webpack-cli to the dependencies
5. npm run test:wp5 - not executing
><EMAIL_ADDRESS>test:wp5
> WEBPACK=5 jest

[webpack-cli] Unknown command or entry '=5'
[webpack-cli] Run 'webpack --help' to see available commands and options

6. npm install ../webpack-localize-assets-plugin
I want to include the local build (develop) of webpack-localize-assets-plugin in a other project but when I run npm install ../webpack-localize-assets-plugin and then build my project I get following error. (it's working fine with the npm-server version)
ERROR in ./MY_PPROJECT/index.js
No template for dependency: ConstDependency

Environment

webpack-localize-asets-plugin version: develop
Webpack version: 5.69.1
Operating System: Windows 10
Node version: v16.13.1
Package manager (npm/yarn/pnpm) and version: npm 7.24.1

Running fine on CI: https://github.com/privatenumber/webpack-localize-assets-plugin/actions/workflows/test.yml
Try aligning your environment specified here: https://github.com/privatenumber/webpack-localize-assets-plugin/blob/develop/.github/workflows/test.yml

5 might still fail since WEBPACK=5 is UNIX env syntax. I'm hoping pnpm will resolve this as it spawns a shell emulator.
If not, can you try creating a .npmrc file with:
shell-emulator=true

Happy to accept PR if it works.

6 is a result of the local dev dependencies getting resolved as a peer dependency instead of the dependency provided by the app. There's no easy way to work around this right now with npm link, but I made a feature request in npx link.
For now, I recommend using https://github.com/privatenumber/git-publish

RE 3:  On Windows I have some issues, I'm currently working on a PR
RE 6: Thank you, I will try it out!

:tada: This issue has been resolved in version 1.5.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


HybridMemory not found

Hybridmemory cannot be found in hdcrl.models. Did you forget to upload it?

sorry, and it has been uploaded.


HBASE-28305 Add "Uncompressed StoreFileSize" column to the table.jsp

Currently, HBase Web UI can only see the uncompressed StoreFile size of each Region on the Region Server page, but sometimes we also hope to see this information on the table details page, which can help analyze the data distribution of each table.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 54s
master passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 41s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
spotless
0m 41s
patch has no errors when running spotless:check.


[opentelemetry-cpp] Missing features

There are missing OpenTelemetry features:

otlp
zpages

OTLP exporter depends on opentelemetry-proto which is utilized as a submodule at opentelemetry-cpp/third_party/opentelemetry-proto@795cc81 if I do manually add otlp to the feature list in the vcpkg portfile.cmake then the vcpkg build fails because the third_party folder was empty. It is needed to clone the submodules after downloading open-telemetry-opentelemetry-cpp-v1.0.1.tar.gz
vcpkg_check_features(OUT_FEATURE_OPTIONS FEATURE_OPTIONS
    FEATURES
        etw WITH_ETW
        zipkin WITH_ZIPKIN
        prometheus WITH_PROMETHEUS
        elasticsearch WITH_ELASTICSEARCH
        jaeger WITH_JAEGER

        otlp WITH_OTLP
)

Hello,
the CMakeLists file from opentelemetry offers two flags for OTLP: WITH_OTLP_GRPC and WITH_OTLP_HTTP (and other options).
In my specific case I need to use the otlp-http feature, which requires the generic otlp feature in vcpkg, and it works as expected.
But, in the vcpkg.json of this port, there is no otlp-grpc and thus gRPC is added as dependencies for the generic otlp feature (see here), while here we can see that is required only when gRPC is explicitly requested.
Now, as I said above everything works for otlp-http but gRPC is still downloaded and compiled, taking an infinite amount of time (more than half an hour on my machine for gRPC only), and resources for nothing.
Wouldn't be better to separate the two features such as only the required dependencies are downloaded and compiled?

I think what you are asking for, was done at #29483 by @ThomsonTan
try to do with the latest vcpkg
vcpkg search opentelemetry-cpp

azure-core-tracing-opentelemetry-cpp 1.0.0-beta.4 Microsoft Azure Core Tracing OpenTelemetry SDK for C++
opentelemetry-cpp        1.8.3#1          OpenTelemetry is a collection of tools, APIs, and SDKs.
opentelemetry-cpp[elasticsearch]          Whether to include the Elasticsearch Client in the SDK
opentelemetry-cpp[etw]                    Whether to include the ETW Exporter in the SDK
opentelemetry-cpp[jaeger]                 Whether to include the Jaeger exporter
opentelemetry-cpp[otlp]                   Whether to include the OpenTelemetry Protocol in the SDK
opentelemetry-cpp[otlp-http]              Whether to include the OpenTelemetry Protocol over HTTP in the SDK
opentelemetry-cpp[prometheus]             Whether to include the Prometheus Client in the SDK
opentelemetry-cpp[zipkin]                 Whether to include the Zipkin exporter in the SDK
opentelemetry-cpp[zpages]                 Whether to include the Zpages Server in the SDK
The result may be outdated. Run `git pull` to get the latest results.
If your port is not listed, please open an issue at and/or consider making a pull request.    -  https://github.com/Microsoft/vcpkg/issues

I suggest creating a new issue here and pinging @ThomsonTan and asking for help at https://cloud-native.slack.com/archives/C01N3AT62SJ

Thank you @juandemanjon, I'm actually using that version and as I described above it downloads "unwanted" dependencies for the http version.
I'm going to open a new issue as you suggested, thank you for the support.


Various code quality enhancements

For some reason rln, multiplier, utils and semaphore are using io::Error and io::Result, they should be changed to basic Error and Result
multiplier has a ton of unwraps, even in the functions return some kind of a Result, this should be changed
a lot of assert! and assert_eq!calls, which could panic anytime, should be changed, extremely important

Yes, for some reason https://github.com/vacp2p/zerokit/pull/114 did not automatically close the issue


PyQt6: apparently QThread usage conflicts with uic.loadUi()

Environment
mcon@ikea:~/projects/nuitka_test$ venv/bin/python -m nuitka --version
1.1.7
Commercial: None
Python: 3.10.7 (main, Oct  1 2022, 04:31:04) [GCC 12.2.0]
Flavor: Debian Python
Executable: /home/mcon/projects/nuitka_test/venv/bin/python
OS: Linux
Arch: x86_64
Distribution: Debian sid

Basic python3 is from Debian distribution (sudo apt install python3)
Virtual environment was built with plain:
mcon@ikea:~/projects/nuitka_test$ python3 -m venv venv
mcon@ikea:~/projects/nuitka_test$ venv/bin/pip install pyqt6 nuitka bottle
Collecting pyqt6
  Using cached PyQt6-6.4.0-cp37-abi3-manylinux_2_28_x86_64.whl (8.0 MB)
Collecting nuitka
  Using cached Nuitka-1.1.7.tar.gz (3.9 MB)
  Preparing metadata (setup.py) ... done
Collecting bottle
  Using cached bottle-0.12.23-py3-none-any.whl (90 kB)
Collecting PyQt6-Qt6>=6.4.0
  Using cached PyQt6_Qt6-6.4.0-py3-none-manylinux_2_28_x86_64.whl (56.5 MB)
Collecting PyQt6-sip<14,>=13.4
  Using cached PyQt6_sip-13.4.0-cp310-cp310-manylinux1_x86_64.whl (310 kB)
Installing collected packages: PyQt6-Qt6, nuitka, bottle, PyQt6-sip, pyqt6
  DEPRECATION: nuitka is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  Running setup.py install for nuitka ... done
Successfully installed PyQt6-Qt6-6.4.0 PyQt6-sip-13.4.0 bottle-0.12.23 nuitka-1.1.7 pyqt6-6.4.0

Test Program
Minimal test program to reproduce error is:
from os import path

from PyQt6 import uic
from PyQt6.QtCore import QObject, pyqtSlot, QThread
from PyQt6.QtWidgets import QApplication, QMainWindow
from bottle import Bottle, run

bot = Bottle()

@bot.route('/hello')
def hello():
    return "Hello World!"

def do_bottle():
    run(bot, host='localhost', port=8080)

class MyWin(QMainWindow):
    def __init__(self, parent=None):
        super().__init__(parent)
        uic.loadUi(path.join(path.dirname(__file__), "MainWindow.ui"), self)

        self.runner = None
        self.thread = None
        self.bottle_runner()

    @pyqtSlot()
    def on_pushButton_clicked(self):
        print("button pushed!")

    class BottleRunner(QObject):
        def __init__(self, *args, **kwargs):
            super().__init__()

        @pyqtSlot()
        def started(self):
            print("Here I'm in thread")
            do_bottle()

    def bottle_runner(self, port=8080):
        self.runner = self.BottleRunner()
        self.thread = QThread()
        self.runner.moveToThread(self.thread)
        self.thread.started.connect(self.runner.started)
        print("About to start thread")
        self.thread.start()
        print("Thread started")

app = QApplication([])
win = MyWin()
win.show()
app.exec()

which relies on MainWindow.ui:
<?xml version="1.0" encoding="UTF-8"?>
<ui version="4.0">
 <class>MainWindow</class>
 <widget class="QMainWindow" name="MainWindow">
  <property name="geometry">
   <rect>
    <x>0</x>
    <y>0</y>
    <width>800</width>
    <height>600</height>
   </rect>
  </property>
  <property name="windowTitle">
   <string>MainWindow</string>
  </property>
  <widget class="QWidget" name="centralwidget">
   <layout class="QVBoxLayout" name="verticalLayout">
    <item>
     <widget class="QPushButton" name="pushButton">
      <property name="text">
       <string>PushButton</string>
      </property>
     </widget>
    </item>
    <item>
     <widget class="QTableView" name="tableView"/>
    </item>
   </layout>
  </widget>
  <widget class="QMenuBar" name="menubar">
   <property name="geometry">
    <rect>
     <x>0</x>
     <y>0</y>
     <width>800</width>
     <height>19</height>
    </rect>
   </property>
  </widget>
  <widget class="QStatusBar" name="statusbar"/>
 </widget>
 <resources/>
 <connections/>
</ui>

Note: not using uic.loadUi() to initialize GUI will not show the problem.

I compile with Nuitka with:
mcon@ikea:~/projects/nuitka_test$ venv/bin/python -m nuitka --standalone --enable-plugin=pyqt6 --include-data-files=MainWindow.ui=. test.py
Nuitka-Options:INFO: Used command line options: --standalone --enable-plugin=pyqt6 --include-data-files=MainWindow.ui=. test.py
Nuitka:WARNING: Using very slow fallback for ordered sets, please install 'ordered-set' PyPI package for best Python compile time performance.
Nuitka-Plugins:WARNING: pyqt6: Support for PyQt6 is experimental, use PySide6 if you can.
Nuitka:INFO: Starting Python compilation with Nuitka '1.1.7' on Python '3.10' commercial grade 'not installed'.
Nuitka-Plugins:INFO: pyqt6: Injecting post-module load code for module 'PyQt6.QtCore':
Nuitka-Plugins:INFO: pyqt6:     Setting Qt library path to distribution folder. We need to avoid loading target
Nuitka-Plugins:INFO: pyqt6:     system Qt plugins, which may be from another Qt version.
Nuitka:INFO: Completed Python level compilation and optimization.
Nuitka:INFO: Generating source code for C backend compiler.
Nuitka:INFO: Running data composer tool for optimal constant value handling.
Nuitka:INFO: Running C compilation via Scons.
Nuitka-Scons:INFO: Backend C compiler: gcc (gcc).
Nuitka-Scons:INFO: Backend linking program with 33 files (no progress information available).
Nuitka-Scons:WARNING: You are not using ccache.
Nuitka-Options:INFO: Included data file '.' due to specified data file 'MainWindow.ui=.' on command line.
Nuitka-Plugins:INFO: pyqt6: Including Qt plugins 'egldeviceintegrations,iconengines,imageformats,platforms,platformthemes,printsupport,wayland-decoration-client,wayland-graphics-integration-client,wayland-shell-integration,xcbglintegrations' below 'PyQt6/qt-plugins'.
Nuitka:INFO: Keeping build directory 'test.build'.
Nuitka:INFO: Successfully created 'test.dist/test'.

The problem:
When I start program I get:
con@ikea:~/projects/nuitka_test$ test.dist/test
About to start thread
Thread started
Here I'm in thread
Bottle v0.12.23 server starting up (using WSGIRefServer())...
Listening on http://localhost:8080/
Hit Ctrl-C to quit.

At this point GUI is a black window with just window decoration visible.
If I hit Ctrl-C and thus I kill Bottle the GUI becomes visible and functional.

Note: Starting program "normally" (venv/bin/python test.py) the GUI is visible and hitting Ctrl-C will not kill Bottle.

I actually misread previous reports which lead me to assume that Qt threading works, and apparently it does, but maybe not in conjuction with slots. I have revisited another PyQt5 example and migrated it to PyQt6, and this one shows the issue. Notice that no standalone mode is needed to demonstrate the issue. I have contacted Riverbank about it.

import signal

from PyQt6 import QtCore, QtWidgets

signal.signal(signal.SIGINT, signal.SIG_DFL)

def n(x):
    on = x.objectName()
    return on if on != "" else str(x)

class Test(QtCore.QObject):
    def __init__(self):
        super().__init__()

    def move(self):
        self.__creationThread = QtCore.QThread.currentThread()
        self.__myThread = QtCore.QThread()
        self.__myThread.setObjectName("Test thread")
        self.moveToThread(self.__myThread)
        self.__myThread.started.connect(self.testSlot)
        self.__myThread.start()

    @QtCore.pyqtSlot()
    def testSlot(self):
        qth = QtCore.QThread.currentThread()
        if self.thread() is not qth or self.__myThread is not qth:
            print(
                "Threading problem detected, \n\tm:%s t:%s c:%s"
                % (n(self.__myThread), n(self.thread()), n(qth))
            )
        else:
            print(
                "OK, \n\tm:%s t:%s c:%s"
                % (n(self.__myThread), n(self.thread()), n(qth))
            )

    @QtCore.pyqtSlot()
    def starting(self):
        print("started")
        self.testSlot()
        print("*" * 20)

app = QtWidgets.QApplication([])
qth = QtCore.QThread.currentThread()
qth.setObjectName("main")

t = Test()
timer = QtCore.QTimer()

timer.timeout.connect(t.testSlot)
t.move()

timer.setInterval(1000)
timer.start()

app.exec()

This is delayed and probably needs a PyQt6 or sip change rather than a Nuitka change at all.


text cut off at the bottom

Hello I open this issue because parfoit the text is cut at the bottom some letters the bottom is not visible ....

+1
I am pretty sure this got introduced by the new arrow-implementation and affects 4.5.0 but now 4.4.0.
The tooltip has a ::before that is just a box and an ::after that is the rotated box that forms the arrow. The tooltip has padding: 8px 21px;, so with position=top or position=bottom the 8px is too little so the box ends up being on-top of the content. I guess whether it actually hides text also depends on the font/line-height/other stuff, but ::before shouldn't overlap the content regardless. I am not sure what purpose the box even - I guess you can color the arrow or something?

Hi! I found the solution ... using the doc
basically i used the padding props on  it works for sure. but i think it would be good if it was fixed without the need to add the padding props

I'll keep both issues opened, if someone can do a PR for that, I'll be very thankful, thanks!

Please, take a look at https://react-tooltip.com/docs/examples/basic-examples
And let me know your thoughts, thanks!


Reduce default pool size to 1

It looks like this is querying pypi very rapidly by default. Even after I set POOL_SIZE=1, it rapidly exhausts the rate limit and then instead of waiting, it fails.
It looks like license_check itself isn't at fault, but the way that yolk is configured & how it isn't respecting rate limits.
This is on a requirements.txt file of about 20 packages.
xmlrpc.client.Fault: <Fault -32500: 'HTTPTooManyRequests: The action could not be performed because there were too many requests by the client. Limit may reset in 53 seconds.'>

@matthewdeanmartin can you add your requirements.txt file here for testing purposes?

I'll take a look at this, though if you can include your reqs.txt that'd be great and then I can scratch my head over this 😁

Nothing special about the requirements.txt file -- I was reviewing a variety of license checking tools.
I think the issue has something to do with pypi a while ago blocking all xmlrpc calls because someone in the world was essentially DDOSing those endpoint & if they work again at all, pypi is definitely doing some aggressive rate limiting.
$ cat requirements.txt
certifi==2021.5.30
charset-normalizer==2.0.4
cleo==0.8.1
click==7.1.2
clikit==0.6.2
crashtest==0.3.1
Flask==1.1.4
greenlet==1.1.1
idna==3.2
itsdangerous==1.1.0
Jinja2==2.11.3
license-info==0.8.7
licensecheck==2021.3
lilili==0.1.0
MarkupSafe==2.0.1
pastel==0.2.1
pip-licenses==3.5.1
pkgtools==0.7.3
PTable==0.9.2
pylev==1.4.0
PyYAML==5.4.1
requests==2.26.0
requirements-parser==0.2.0
SQLAlchemy==1.4.22
tomlkit==0.7.2
urllib3==1.26.6
Werkzeug==1.0.1

Can I confirm this is the sort of thing you'd be wanting to do? https://stackoverflow.com/questions/18466079/can-i-change-the-connection-pool-size-for-pythons-requests-module
(Just rather than using 100 using a lower value and perhaps even allowing an end user to configure this?)

Oh shoot! I just realized a filed a bug against the wrong repo! I feel dumb now. I checked, there is no way for the endpoint you are using (ref https://warehouse.pypa.io/api-reference/index.html ) since those things are cached on CDNs
I am fighting other bugs while using licensecheck, which I will file separately.


In case site is not active and customer restarts the app, site restart analysis is not capturing the restart

When site is not active and customer restarts the app from portal, its a no-op for site as no site process is active.
However for completeness sake, we should still capture the controller logs and report a restart.

We should probably clarify that the site did not actually do a restart however, just to b

Didn't mean to close


bump wrangler to v1.0.2

IMPORTANT: Please do not create a Pull Request without creating an issue first.
Problem:

PR bumps up wrangler to v1.0.2 to address https://avd.aquasec.com/nvd/2022/cve-2022-31249/
Additional advisory information available here: https://github.com/rancher/wrangler/security/advisories/GHSA-qrg7-hfx7-95c5
Solution:

Related Issue:
Test plan:

@mergify backport v1.1

Close as we have already included the wrangler bump in https://github.com/harvester/harvester/pull/3535 and it is bumped to newer version v1.1.0, thanks.