Permission denial when restoring backup

Steps to reproduce
Migrated  backup from another device with whole folder
Restore successfully yet this popped after the message of success.

Not gonna lie, I don't see anything missing, the chapters seem to be correct and up to date but still wanted to report just in case it is something noteworthy
Expected behavior
The 3rrir shouldn't pop?
Actual behavior
A weird error pops up
Crash logs
No response
Yōkai version
<IP_ADDRESS>
Android version
14
Device
Poco x6 Pro
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, or a request for an extension, I should be contacting the extensions repository's maintainer/support for help.
[X] I am reporting an issue exclusive to this fork. I have also checked that is not an issue on the main version of Mihon
[X] I have tried the troubleshooting guide.
[X] I have updated the app to version <IP_ADDRESS>.
[X] I have updated all installed extensions.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I have filled out all of the requested information in this form.

Restore successfully yet this popped after the message of success

Both failed and success notification appeared?

Restore successfully yet this popped after the message of success

Both failed and success notification appeared?

Yep, and as far as I can tell everything seems to be right. To give more context, this was my main device but I broke it so used my secondary to read and stuff. When I repaired my main I did a manual backup of secondary and migrated to main. Almost the same Manga, just one migrated to another source and that's it as far as I recall.
But then again, migration went successfully and with no issues. Just a minor glitch that made the last chapter appear beneath the last chapter when main device broke, it solved with a global update


Dummy PR for merging 3.1.1 into main

This is a dummy PR showing the differences between main and v3.1.1-dev after merging

#4074

Do not merge!
Once #4074 is merged, this will be replaced with a "Release PR" for merging v3.1.1-dev into main.

Closing this dummy PR


Question about SHIR Data Redundancy

Hi Team,
I found below description in this doc:
Microsoft-managed failover does not apply to self-hosted integration runtime (SHIR) since this infrastructure is typically customer-managed. If the SHIR is set up on Azure VM, then the recommendation is to leverage [Azure site recovery](https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-overview) for handling the [Azure VM failover](https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-architecture) to another region.

But in another docs, for the high availability, connecting muliple node for 1 SHIR is also recommended.
https://learn.microsoft.com/en-us/azure/data-factory/create-self-hosted-integration-runtime?tabs=data-factory
You can associate a self-hosted integration runtime with multiple on-premises machines or virtual machines in Azure. These machines are called nodes. You can have up to four nodes associated with a self-hosted integration runtime.

I thought connecting multiple node (deploy primary node to region A and deploy another node to region B etc) for 1 SHIR is sufficient but is there any motivation to use Azure Site Recovery instead of this multiple node approach?
If any, it'd be helpful to mention that point.
Thank you!

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

ID: 3ca2635d-02b8-e4ee-03c9-0abc105eae94
Version Independent ID: efaf8754-aebe-172a-2af8-aa84db32778e
Content: Data redundancy in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/concepts-data-redundancy.md
Service: data-factory
Sub-service: concepts
GitHub Login: @nabhishek
Microsoft Alias: abnarain

@yutaro113
Thanks for your feedback! We will investigate and update as appropriate.

@yutaro113
Thank you for bringing this to our attention. I've assigned this issue to the author who will investigate and update as appropriate.

@yutaro113
Thank you for bringing this to our attention. I've assigned this issue to the author who will investigate and update as appropriate.

@nabhishek
Could you please check and add your comments on this, update as appropriate.

@nabhishek
Could you please check and add your comments on this, update as appropriate.

Thanks for your dedication to our documentation @yutaro113. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


docs(crashlytics): Initialise plugin from dart. Updated docs to illustrate upload-symbols script implementation.

Description
Initialise Crashlytics from Dart code. Update instructions on how to implement upload-symbols script.
Notes
I left a TODO for android as I believe there is a soft fail for uploading symbols that can be addressed with an id in the gradle script.
Related Issues
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[ ] All existing and new tests are passing.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] The analyzer (melos run analyze) does not report any problems on my PR.
[ ] I read and followed the Flutter Style Guide.
[ ] I signed the CLA.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

Copied this in last night to docs directly


Wrong behavior of docker build for Windows-based images

Description
docker build command behaves differently in Github actions than it should.
I have Dockerfile that uses 2 images:

mcr.microsoft.com/windows/nanoserver:1809 as a base image
mcr.microsoft.com/dotnet/framework/sdk:4.8 as a build image

I expect that building Dockerfile on Windows locally and using Github Action should behave in the same way, but it is not.
I tried locally (on a few different Windows 10 machines with Windows 10 Pro 21H1) and on Appveyor(build link https://ci.appveyor.com/project/Antonytm/dianoga/builds/44060111). I am able to build Dockerfile everywhere except Github Actions.
I made an investigation and found that docker build behaves differently in Github Actions.
Differences are present in Actual/Expected fields.
Platforms affected

[ ] Azure DevOps
[X] GitHub Actions

Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
Build link:
https://github.com/Antonytm/Dianoga/runs/7168405045?check_suite_focus=true
Exact the same build approach worked 4 months ago, sample build link:
https://github.com/Antonytm/Dianoga/runs/5240306180?check_suite_focus=true
but the log was removed: The log was not found. It may have been deleted based on retention settings.
Is it regression?
Yes
Expected behavior
For mcr.microsoft.com/dotnet/framework/sdk:4.8 image

I should be able to use $env:something inside Dockerfile to get the environment variable.
I should be able to use RUN mkdir ./src/bin command inside Dockerfile to create new folder src/bin.a

Actual behavior

I am not able to use $env:something inside Dockerfile to get the environment variable.
I was able to use %something% inside Dockerfile to get the environment variable. But that is different from all other places, where I tried to build this docker image.
RUN mkdir ./src/bin inside Dockerfile fails

Repro steps

Use mcr.microsoft.com/dotnet/framework/sdk:4.8 as base/build image
Set argument ARG TEST0=test
Try to access the argument using

RUN echo $env:TEST0
RUN echo ${TEST}
RUN echo $TEST0
RUN echo %TEST%

You will see that %TEST% works. But should work $env:TEST0

Update:
Presence of 2 Windows in the list when I reported the bug gave me an idea to try running on windows-2019 instead of windows-latest. And I got successful build on windows-2019.
Successful build link:
https://github.com/Antonytm/Dianoga/runs/7168986642?check_suite_focus=true
The problem is inconsistency. Docker builds should have the same result on both platforms. You should not support 2 Dockerfil files depending on where you want to build it.

As I can see the default shell in your build is cmd(The command 'cmd /S /C dotnet build -c $env:BUILD_CONFIGURATION' returned a non-zero code: 1),  that's why %TEST% syntax is working. If you want to use $env:Var the default shell should be set up to powershell.
You can set the shell of the docker image in the Dockerfile:
SHELL ["powershell", "-Command"]

@al-cheb
It works.
But why do I get a different shell for the same Dockerfile based on the same images for different environments?
Was it expected that they switched from the default shell from powershell to cmd in windows-2022?

@Antonytm
According to the documentation it should be  'cmd /S /C':
https://docs.docker.com/engine/reference/builder/
https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-docker/manage-windows-dockerfile
RUN has 2 forms:

RUN  (shell form, the command is run in a shell, which by default is /bin/sh -c on Linux or cmd /S /C on Windows)
RUN ["executable", "param1", "param2"] (exec form)

Here's an example of the exec form:
FROM mcr.microsoft.com/windows/servercore:ltsc2019

RUN ["powershell", "New-Item", "c:/test"]

The resulting image runs the powershell New-Item c:/test command:
docker history doc-exe-method

IMAGE               CREATED             CREATED BY                    SIZE                COMMENT
b3452b13e472        2 minutes ago       powershell New-Item c:/test   30.76 MB

To contrast, the following example runs the same operation in shell form:
FROM mcr.microsoft.com/windows/servercore:ltsc2019
RUN powershell New-Item c:\test

The resulting image has a run instruction of cmd /S /C powershell New-Item c:\test.
docker history doc-shell-method

IMAGE               CREATED             CREATED BY                              SIZE                COMMENT
062a543374fc        19 seconds ago      cmd /S /C powershell New-Item c:\test   30.76 MB

If the default should be 'cmd /S /C then it means that it doesn't work properly on windows-2019 environments. And there is the issue with running PowerShell instead of cmd.
But shouldn't the shell be inherited from the base image?
I run a local test on 2 images:
mcr.microsoft.com/dotnet/framework/sdk:4.8 - default shell is PowerShell
mcr.microsoft.com/windows/nanoserver:1809 - default shell is cmd
And locally I should not force usage of PowerShell by the command SHELL ["powershell", "-Command"]. And the same behavior was for windows-2019.
P.S. I double-checked that the same image was used in both tests, local and Github action: mcr.microsoft.com/dotnet/framework/sdk:4.8  with digest 96a507e6fe9cadd75a31a8781fccaf747447d66bcc51463abb705f8cab7b60b.

If the default should be 'cmd /S /C then it means that it doesn't work properly on windows-2019 environments. And there is the issue with running PowerShell instead of cmd. - It works by design.
You compare two different images with different configs:
Windows Server 2019(ContainerConfig - Shell is powershell):
"Id": "sha256:02dae5a894765af039e4057cda81e25d938947fdf7c27dd6f6c32eb7520cfbe3",
"RepoTags": [
         "mcr.microsoft.com/dotnet/framework/sdk:4.8",
         "mcr.microsoft.com/dotnet/framework/sdk:4.8-windowsservercore-ltsc2019"
],
"RepoDigests": [
    "mcr.microsoft.com/dotnet/framework/sdk@sha256:296a507e6fe9cadd75a31a8781fccaf747447d66bcc51463abb705f8cab7b60b",
    "mcr.microsoft.com/dotnet/framework/sdk@sha256:82e0a5e2c8747b9f2c88a15e7f652fd4b437cbe0399ab15ac54a0680dde8b453"
],

"Shell": [
                "powershell",
                "-Command",
                "$ErrorActionPreference = 'Stop'; $ProgressPreference = 'SilentlyContinue';"
            ]
],

Windows Server 2022(ContainerConfig - Shell is not set):
"RepoTags": [
            "mcr.microsoft.com/dotnet/framework/sdk:4.8",
            "mcr.microsoft.com/dotnet/framework/sdk:4.8-windowsservercore-ltsc2022"
],
"RepoDigests": [
"mcr.microsoft.com/dotnet/framework/sdk@sha256:296a507e6fe9cadd75a31a8781fccaf747447d66bcc51463abb705f8cab7b60b",
"mcr.microsoft.com/dotnet/framework/sdk@sha256:6c490f4528cb625c60aa1[19](https://github.com/roasted-eggplant/alcheb-test/runs/7176305181?check_suite_focus=true#step:2:20)669830639ae3988c3c23dfb2f94a4ef19df2eb606"
],

https://any-api.com/docker_com/engine/docs/Definitions/ContainerConfig
Shell:array[string:]
Shell for when RUN, CMD, and ENTRYPOINT uses a shell.

If we take an image with the same configuration(e.g. - https://hub.docker.com/_/microsoft-dotnet-samples/):

Similar issue for reference https://github.com/actions/virtual-environments/issues/5296


Add Display component

Feature request 🚀
Display component is added to improve the readability of normal layout.
Expected:

Remove props caption & shadow on zi-image
Add component Display
Add props darkBash to zi-code

Examples:
Refer to React Component

Hi, could you make the zeit-ui/react repo open source?
I want contribution it

Hey, the zeit-ui/react is still under development, and the project architecture may need to be refactored, which is not friendly to contributors. I am in the process of perf testing and will be online in the near future. (1 - 2 weeks 🤗🤗)

Oh I see. Waiting for your release.


Deploy

Successfully deploy application to GitHub pages when it's complete.

Successfully deployed my app to GitHub pages.


Consider adding support for generator expression in pkgConfig.cmake.in

urdfdom is providing libraries with generator expression in it, which is not supported by the pkgConfig.cmake.in template as it will call find_library on it: https://github.com/ros/urdf/issues/37
Maybe it could just add the library if it looks like a generator expression as suggested by https://github.com/ros/urdf/issues/37#issuecomment-939183824
https://github.com/ros/catkin/blob/085e8950cafa3eb979edff1646b9e3fe55a7053a/cmake/templates/pkgConfig.cmake.in#L122
https://github.com/ros/catkin/blob/085e8950cafa3eb979edff1646b9e3fe55a7053a/cmake/templates/pkgConfig.cmake.in#L171

if("${library}" MATCHES "^(debug|optimized|general)$")

Just in case there's a confusion, that line is matching configuration keywords, which are not the same as generator expressions.

Maybe it could just add the library if it looks like a generator expression as suggested by ros/urdf#37 (comment)

I don't think that's going to work.
e.g. the error reported there was caused by the line $<$<NOT:$<CONFIG:Debug>>:/usr/lib/liburdfdom_sensor.so>.
In that case, you only want to try to find that library for non-debug builds.
The issue should be solved by making sure that PKG_CONFIG_LIBRARIES has a list of actual libraries, with all generator expressions already (somehow) resolved.
PKG_CONFIG_LIBRARIES is generated here.
Once you get the generators expressions in the pkgConfig file, I don't think it's possible to do something reasonable with them (though there might be a way to fix the issue there).

can we add extra filter to extract pure library name from those regex expression in where that (https://github.com/ros/catkin/blob/085e8950cafa3eb979edff1646b9e3fe55a7053a/cmake/templates/pkgConfig.cmake.in#L119) generated ?
by the way,  why urdf will cause something to generate that ugly expression, I have build hundred ros packages, only urdf's cmake file raise those errors.

-- check library: urdf
-- check library: $<$>:/usr/local/lib/liburdfdom_sensor.dylib>
CMake Error at /Users/xlla/ros_catkin_ws/install_isolated/share/urdf/cmake/urdfConfig.cmake:174 (message):
  Project 'gazebo_plugins' tried to find library
  '$<$>:/usr/local/lib/liburdfdom_sensor.dylib>'.  The
  library is neither a target nor built/installed properly.  Did you compile
  project 'urdf'? Did you find_package() it before the subdirectory
  containing its code is included?
Call Stack (most recent call first):
  /Users/xlla/ros_catkin_ws/install_isolated/share/catkin/cmake/catkinConfig.cmake:76 (find_package)
  CMakeLists.txt:7 (find_package)

by the way, why urdf will cause something to generate that ugly expression, I have build hundred ros packages, only urdf's cmake file raise those errors.

Those are cmake generator expressions.
See was it was added here https://github.com/ros2/urdfdom/pull/16.
If you use modern cmake targets and they automatically generated export file, they also generate the same kind of generator expressions.
I'm rereading this thread and https://github.com/ros/urdf/issues/37, and I think the suggestion here is fine https://github.com/ros/urdf/issues/37#issuecomment-939183824.
If a generator expression is detected, add the library to the list unconditionally.
That should fix the issue.

can we add extra filter to extract pure library name from those regex expression in where that (

I'm not sure what you're suggesting.
Is your suggestion the same as https://github.com/ros/urdf/issues/37#issuecomment-939183824?
If yes, that sounds fine.
If not, could you clarify a bit? Thanks!

I'm not sure what you're suggesting.

hi @ivanpauno , I have tried the solutions on https://github.com/ros/urdf/issues/37#issuecomment-939183824 ,  manual remove those regex expressions actually work but trivial and bring mistake sometimes.
AchmadFathoni's sed regex command just remove the prefix of lib regex expression and leave suffix ">" there.
the filter I mean is like this

sorry, I don't know how to avoid html to render these special symbols so I have to post a picture to demonstrate it.

I'm not sure what are you trying to do.
You don't need to filter, but instead add all generator expressions unconditionally without checking.
i.e. you would need to replace this https://github.com/ros/catkin/blob/7fa3eb3508ba12c34d85b8e54bbdf4bbdc60a5c1/cmake/templates/pkgConfig.cmake.in#L122-L123 with:
 if("${library}" MATCHES "^\\$<.*>$")
   list(APPEND @PROJECT_NAME@_LIBRARIES ${library})
 elseif("${library}" MATCHES "^(debug|optimized|general)$")
   list(APPEND @PROJECT_NAME@_LIBRARIES ${library})

The regex expression I proposed my need to be adjusted.
I don't have time to test it now, but I think something like that should fix the issue.

I just want to pass the build of the package that depend on urdfdom lib.
Those cmake-generator-expressions does not got eval or parsed while pass to function find_library, and they even goes into ros install_isolated/lib/pkgconfig/urdf.pc , and cause many build problems.

Those cmake-generator-expressions does not got eval or parsed while pass to function find_library

Yes, but it never should reach this find_library() line with the fix I mentioned.

and they even goes into ros install_isolated/lib/pkgconfig/urdf.pc , and cause many build problems.

That's bad. I'm not sure how that could be fixed.
The thing is that generator expressions cannot be evaluated at configuration time, only at build time (because of things like https://cmake.org/cmake/help/latest/prop_gbl/GENERATOR_IS_MULTI_CONFIG.html).
Maybe using https://cmake.org/cmake/help/v3.13/command/file.html#generate instead of will help https://github.com/ros/catkin/blob/7fa3eb3508ba12c34d85b8e54bbdf4bbdc60a5c1/cmake/em_expand.cmake#L5
But getting that right is going to be tricky.


Creation function throwError should align with other constants like EMPTY, NEVER

Description Of The Issue
As we have constants like EMPTY, NEVER  why not create THROW and be align with the rest and have a more consistent API?

empty / never is no-value constant while throwError needs value to be thrown. Mind elaborate how throw can be cobstant interface?

 I should stop creating issuea at 1:30 am.. :)


Introduce 4th row in service menu

See https://github.com/our-city-app/oca-backend/issues/680

Original issue is put on hold


Revert "Support upstream http filters with tcp tunneling (#27183)"

This reverts commit 50e9108c22c2e46d4ad04a977d24d89201aa0c62.
@vikaschoudhary16 no idea how your PR passed CI  but caused permafail on the compile time options but back-syncing it seems to pass before and fail after.  maybe was a race with something else merged right before it?

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@alyssawilk what is the ci failure because of which this change is reverted?
I re-pushed the changes in a new PR but unable to see any ci failure on that one.

@vikaschoudhary16 the issue was a general timeout issue - not sure it was related to your PR, other than that was where the issue became apparent. Other measures have been added to address the timeout/s so probs its safe to reland

@phlax recreated https://github.com/envoyproxy/envoy/pull/32991


3D donut high chart not appear

I try to display chart using Jquery and webmehtod Now in my app there is  drop-down and calendar  when i select value from drop-down and dates from  calendar  then for test first i try to show data in alert box and i succesfully  done this then i try to show data in chart for this first i create web method and this web method return me successfully data like this
[['DDSB', 39], ['DPSB', 9], ['DSB', 26], ['MV', 35], ['PSB', 52]]
now when i run the app first alert box is appear then alert u and then alert uu is appear when alert uu is display chart is also display but when  i click on OK button chart disappear
This is what i try
<script type="text/javascript">
     var strArray = [['sfdsdfLi', 9], ['Kiwsdfi', 3], ['Mixesdfd nuts', 1], ['Oranges', 6], ['Grapes (bunch)', 1]];
     $(function () {
         $('[ID*=search_data]').on('click', function () {
             var from = $('[ID*=fromdate]').val();
             var to = $('[ID*=todate]').val();
             var reg = $('[id*=regiondrop] option:selected')[0].value; // changed this to .val()
             var obj = {};
             obj.fdate = from;
             obj.tdate = to;
             obj.region = reg;
             GetData(obj);
             return false;
         });
     });
     function GetData(obj) {
         $.ajax({
             type: "POST",
             contentType: "application/json; charset=utf-8",
             url: "WebForm1.aspx/GetVo",
             data: JSON.stringify(obj),
            dataType: "json",
             async: true,
             cache: false,
             success: function (result) {
                 alert(result.d);
                 alert('u');
                 // start
                 strArray = result.d;
                 var myarray = eval(strArray);
                 DreawChart(myarray);
                 alert('uu');
                  } ,
                  error: function (result) {
                   alert("Error");
                 }
         });
}
function DreawChart(result) {
    $('#container').highcharts({
        chart: {
            type: 'pie',
            options3d: {
                enabled: true,
                alpha: 45
            }
        },
        title: {
            text: 'Contents of Highsoft\'s weekly fruit delivery'
        },
        subtitle: {
            text: '3D donut in Highcharts'
        },
        plotOptions: {
            pie: {
                innerSize: 100,
                depth: 45
            }
        },
        series: [{
            name: 'Delivered amount',
            data: result
        }]
    });
}
 </script>

check image
http://i.stack.imgur.com/K6DvM.png
any solution please

and again: for how-to questions, please use stackoverflow or similar. see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker

why u continuously closed this question

because this is not the right place to ask the questions. READ https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker


Fix/188 review page change links should not link directly to fields

review before:

review after:

edit before:

edit after:

job post before:

job post after:

 Review page 'change' links should not link directly to fields


[Question] Automatic HTTP->S redirects with the http and layer4 apps

Hi Matt, Francis,
I'm trying to use the Layer 4 plugin as a multiplexer by forwarding requests over port 443 to their relevant destinations while continuing to leverage Caddy's more traditional reverse proxy functionality. However, I am unable to get the HTTP -> HTTPS redirects to work with the standard http app. I used this post in the Caddy community as a guide.
I have boiled down the troubling configuration to an extremely basic form.
logging:
  logs:
    default:
      level: DEBUG
apps:
  layer4:
    servers:
      srv0:
        listen:
        - ":443"
        routes:
        - handle:
          - handler: proxy
            upstreams:
            - dial:
              - <IP_ADDRESS>:1337 # simply forward everything to Layer 7
  http:
    https_port: 1337 # since port 443 is occupied, use 1337 here
    servers:
      srv1:
        listen:
        - ":80"
        - "<IP_ADDRESS>:1337"
        logs: {}
        routes:
        - match:
          - host:
            - subdomain.example.tld
          handle:
          - handler: subroute
            routes:
            - handle:
              - handler: reverse_proxy
                upstreams:
                - dial: localhost:1234
          terminal: true

I run this configuration by using
$ xcaddy build \
  --with github.com/mholt/caddy-l4 \
  --with github.com/abiosoft/caddy-yaml
$ caddy run --config config.yaml --adapter yaml

My test cases include an HTTP curl, and an HTTPS curl. I would expect the HTTP curl to produce a 308 Permanent Redirect, but it does not. Note that Caddy's logs do contain a "msg":"enabling automatic HTTP->HTTPS redirects".
$ curl -vvI http://subdomain.example.tld
*   Trying XX.XX.XXX.XXX:80...
* Connected to subdomain.example.tld (XX.XX.XXX.XXX) port 80 (#0)
> HEAD / HTTP/1.1
> Host: subdomain.example.tld
> User-Agent: curl/7.80.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 303 See Other
HTTP/1.1 303 See Other
< Content-Type: text/html
Content-Type: text/html
< Date: Mon, 20 Dec 2021 02:53:58 GMT
Date: Mon, 20 Dec 2021 02:53:58 GMT
< location: /loginRedir
location: /loginRedir
< server: Caddy
server: Caddy
< server: SomeOtherServer
server: SomeOtherServer

<
* Connection #0 to host subdomain.example.tld left intact

$ curl -vvI https://subdomain.example.tld
*   Trying XX.XX.XXX.XXX:443...
* Connected to subdomain.example.tld (XX.XX.XXX.XXX) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: none
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_128_GCM_SHA256
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=subdomain.example.tld
*  start date: Dec 20 01:39:41 2021 GMT
*  expire date: Mar 20 01:39:40 2022 GMT
*  subjectAltName: host "subdomain.example.tld" matched cert's "subdomain.example.tld"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x55e7f03029d0)
> HEAD / HTTP/2
> Host: subdomain.example.tld
> user-agent: curl/7.80.0
> accept: */*
>
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* Connection state changed (MAX_CONCURRENT_STREAMS == 250)!
< HTTP/2 303
HTTP/2 303
< content-type: text/html
content-type: text/html
< date: Mon, 20 Dec 2021 02:56:08 GMT
date: Mon, 20 Dec 2021 02:56:08 GMT
< location: /loginRedir
location: /loginRedir
< server: Caddy
server: Caddy
< server: SomeOtherServer
server: SomeOtherServer

<
* Connection #0 to host subdomain.example.tld left intact

Let me know if you have any ideas about this. Thanks for your help!

The problem is here:
        listen:
        - ":80"

Since you actually define a listener for :80, it'll override the routes that would otherwise be set up for HTTP->HTTPS redirects. Remove :80 and it should work fine.

The problem is here:
        listen:
        - ":80"

Since you actually define a listener for :80, it'll override the routes that would otherwise be set up for HTTP->HTTPS redirects. Remove :80 and it should work fine.

Unfortunately that just seems to remove port 80 from the picture.
curl: (7) Failed to connect to subdomain.example.tld port 80 after 84 ms: Connection refused

Weird, Automatic HTTPS should trigger and add a server that listens on port 80.
Do you see the log message server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS? Do you see enabling automatic HTTP->HTTPS redirects?
Anyways, you can add a 2nd server to the HTTP app and manually do the HTTP->HTTPS redirect yourself. It's just a static_response handler with the Location header set to https://{http.request.host}{http.request.uri}. https://caddyserver.com/docs/json/apps/http/servers/routes/handle/static_response/

Weird, Automatic HTTPS should trigger and add a server that listens on port 80.
Do you see the log message server is listening only on the HTTPS port but has no TLS connection policies; adding one to enable TLS? Do you see enabling automatic HTTP->HTTPS redirects?

With the :80 removed, I am able to see both those lines.

Anyways, you can add a 2nd server listening on port 80 to the HTTP app and manually do the HTTP->HTTPS redirect yourself. It's just a static_response handler with the Location header set to https://{http.request.host}{http.request.uri}. https://caddyserver.com/docs/json/apps/http/servers/routes/handle/static_response/

Thanks, the below seems to work:
apps:
  layer4:
    servers:
      srv0:
        listen:
        - ":443"
        routes:
        - handle:
          - handler: proxy
            upstreams:
            - dial:
              - <IP_ADDRESS>:1337 # simply forward everything to Layer 7
  http:
    https_port: 1337 # since port 443 is occupied, use 1337 here
    servers:
      srv1:     # handles HTTPS
        listen:
        - "<IP_ADDRESS>:1337"
        routes:
        - match:
          - host:
            - subdomain.example.tld
          handle:
          - handler: subroute
            routes:
            - handle:
              - handler: reverse_proxy
                upstreams:
                - dial: localhost:1234
          terminal: true
      srv2:     # redirects HTTP to HTTPS
        listen:
          - ":80"   # bind to all addresses
        routes:
          - handle:
            - handler: static_response
              headers:
                Location:
                - https://{http.request.host}{http.request.uri}

Huh, like Francis, I'm also curious as to why automatic HTTPS isn't enabling redirects from port 80 for you in your earlier config.
I'd like this to be looked into further when we have a chance.

After looking into it, I'm unable to reproduce the bug. Simply removing the :80 as Francis suggested works for me. (And this is expected, since if you manually specify :80, then you're telling Caddy that you want to serve this over plaintext HTTP. By omitting it, you're letting Caddy do the redirects.)
My config (I am using localhost instead of a real domain here since I'm just testing locally, but same auto HTTPS effect):
{
	"logging": {
		"logs": {
			"default": {
				"level": "DEBUG"
			}
		}
	},
	"apps": {
		"layer4": {
			"servers": {
				"srv0": {
					"listen": [
						":443"
					],
					"routes": [
						{
							"handle": [
								{
									"handler": "proxy",
									"upstreams": [
										{
											"dial": [
												"<IP_ADDRESS>:1337"
											]
										}
									]
								}
							]
						}
					]
				}
			}
		},
		"http": {
			"https_port": 1337,
			"servers": {
				"srv1": {
					"listen": [
						"<IP_ADDRESS>:1337"
					],
					"logs": {},
					"routes": [
						{
							"match": [
								{
									"host": [
										"localhost"
									]
								}
							],
							"handle": [
								{
									"handler": "subroute",
									"routes": [
										{
											"handle": [
												{
													"handler": "reverse_proxy",
													"upstreams": [
														{
															"dial": "localhost:1234"
														}
													]
												}
											]
										}
									]
								}
							],
							"terminal": true
						}
					]
				}
			}
		}
	}
}

Results:
$ curl -v "http://localhost"
*   Trying <IP_ADDRESS>:80...
* Connected to localhost (<IP_ADDRESS>) port 80 (#0)
> GET / HTTP/1.1
> Host: localhost
> User-Agent: curl/7.74.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 308 Permanent Redirect
< Connection: close
< Location: https://localhost/
< Server: Caddy
< Date: Fri, 11 Mar 2022 19:00:18 GMT
< Content-Length: 0
<
* Closing connection 0

Note that I did not have to manually do the redirects.
Everything seems to be working as expected.


CIV-13408 notification for help with fees in review

JIRA link (if applicable)
CIV-13408
Change description
Add notification for claimant after requesting help with fees
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[X] No

https://build.hmcts.net/blue/organizations/jenkins/HMCTS_a_to_c%2Fcivil-service/detail/PR-4529/17/pipeline/ got green


shortcuts with 3 keys

remapping shortcuts with 3 keys, for example, remap Ctrl+shift+2 to Shift+space and etc

have more choices with remapping and reassigning shortcuts.

@tarikhname what was the remap that you tried to do? We do currently support remaps from/to shortcuts with 3 keys, so the scenario you mentioned should work but we haven't yet supported more than 3 keys.

Dear Arjun Balgovind
I can't find 3keys shortcuts!
there are only 2keys shortcuts.
On Wed, Jun 17, 2020 at 9:54 PM Arjun Balgovind<EMAIL_ADDRESS>wrote:

@tarikhname https://github.com/tarikhname what was the remap that you
tried to do? We do currently support remaps from/to shortcuts with 3 keys,
so the scenario you mentioned should work but we haven't yet supported more
than 3 keys.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4353#issuecomment-645512066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7QB5WWYUDE5TLF2BWLJADRXD345ANCNFSM4OAKAFVQ
.

@tarikhname this is possible on the Remap shortcuts option

Here is a gif which shows how to add Ctrl+Shift+2 -> Shift+Space in two ways, either you can press those keys together with the Type Shortcut button, or you can search for those keys from the drop down.

Let us know if this what you meant.

Thank you very much for your response.
On Mon, Jun 29, 2020 at 6:30 AM msftbot[bot]<EMAIL_ADDRESS>wrote:

This issue has been automatically marked as stale because it has been
marked as requiring author feedback but has not had any activity for 5
days. It will be closed if no further activity occurs within 5 days of
this comment.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/4353#issuecomment-650862184,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP7QB5WKCC6T67KLGYOCZZDRY7YU3ANCNFSM4OAKAFVQ
.

@tarikhname what was the remap that you tried to do? We do currently support remaps from/to shortcuts with 3 keys, so the scenario you mentioned should work but we haven't yet supported more than 3 keys.

Is this 3 keys functionality removed? I am on PowerToys 0.72.0 and trying to map:
Ctrl-U => Shift-Home-Backspace

But I am not allowed to do this:

Same Issue where is three keys?

@SteveLauC https://github.com/microsoft/PowerToys/issues/33272#issuecomment-2153918191


How to manage the cache data

I found many large files in .local/share/lbry/lbrynet/blobfiles/. It almost stuff full my hard drive. Is it safe to delete those files? or any way to manage the cache size?

This is based on a setting in advanced app options. See lbry.com/faq/host-content and https://lbry.com/faq/how-to-change-lbry-blob-files

This is based on a setting in advanced app options. See lbry.com/faq/host-content and https://lbry.com/faq/how-to-change-lbry-blob-files

Guess the rule of the thumb is to sort the files by creation date and delete from either end to keep the optimal number of seeded videos intact.


Add files via upload

Hi JetBrains team,
I added my university's information in this file. Please check it for me. Thank you.

@CodingChicken101 file.zip: this request has an incorrect file path format, please ensure that you are familiar with     this repository rules located at the bottom of this page and change     your request accordingly. If you don't know how to change request, close it and open a new one.     If you are not able to make the pull request according the instructions, please send us an email to<EMAIL_ADDRESS>Please mention this request URL in the message.


[Feature Request] Migrate to Node.js for YAML Config Validator

Is your feature request related to a problem? Please describe.
The current Python implementation of our YAML Config Validator has limitations that significantly impact its effectiveness and user experience:

It can only report one error at a time, requiring multiple runs to identify all issues in a configuration file.
The error messages lack detailed context and suggestions for fixing issues.
The validator's performance is suboptimal for large configuration files.
The Python implementation has limited support for complex JSON Schema features.

These limitations result in a time-consuming and frustrating process for users trying to validate and correct their YAML configurations.
Describe the solution you'd like
We propose migrating the YAML Config Validator to Node.js, utilizing the following libraries:

Ajv for JSON Schema validation
js-yaml for YAML parsing
better-ajv-errors for detailed error reporting

This migration would provide the following improvements:

Multiple error reporting in a single run
More comprehensive and context-rich error messages
Better performance for large configuration files
More extensive JSON Schema support for complex validation rules
Improved integration with web-based tools and services

Describe alternatives you've considered
We considered the following alternatives:

Enhancing the current Python implementation:

Pros: Keeps existing codebase, familiar to current maintainers
Cons: Limited libraries for advanced JSON Schema validation, may not fully address all current limitations

Using a different language (e.g., Go, Rust):

Pros: Potential performance improvements
Cons: Smaller ecosystem for JSON Schema validation, steeper learning curve for the team

Creating a custom validation engine from scratch:

Pros: Full control over features and implementation
Cons: Time-consuming, risk of introducing new bugs, maintenance burden

Additional context
The Node.js ecosystem has mature and well-maintained libraries for JSON Schema validation and YAML parsing. This migration aligns with our goal of providing a more robust and user-friendly tool for configuration validation.
Example of the improved error output with the Node.js implementation:
full.yaml
Validation errors:
TYPE must be number

  216 |             {
  217 |               "module_type": "recency_filter",
> 218 |               "threshold": "2015-01-01T00:00:00.000Z"
      |                            ^^^^^^^^^^^^^^^^^^^^^^^^^^ 👈🏽  type must be number

REQUIRED must have required property 'module_type'

  358 |               ]
  359 |             },
> 360 |             {
      |             ^ ☹  module_type is missing here!
  361 |               "module_type1": "openai_llm",
  362 |               "llm": "gpt-3.5-turbo",
  363 |               "temperature": 0.8

... (additional detailed error information)

This migration will significantly improve the user experience and effectiveness of our YAML Config Validator.

https://github.com/hongsw/AutoRAG-YAML-Config-Validator

@vkehfdl1 we need to change the full.yaml file
- module_type: recency_filter
            threshold: 2015-01-01

Restrict 'threshold' config to numbers only for module_type

https://json-schema-everywhere.github.io/yaml


BF16 vector conversion and round-to-odd

Follow-up to @krovers 's https://github.com/riscv/riscv-bfloat16/issues/52
Could it make sense to add right away (in Zvbfbmin) a BF16 version of RVV 1.0 vfncvt.rod.f.f.w vd, vs2, vm ?
As round-to-odd might be quite useful for use cases of this type of conversions and I do not think it is available by default in https://github.com/riscv/riscv-bfloat16/blob/main/doc/insns/vfncvtbf16_f_f_w.adoc (since frm does offer round-to-odd).

Thanks for the question, Nicolas.
Is there a particular use for round to odd targeting BF16.
As I understand it, round to odd is used for an intermediate conversion, when the ultimate goal is to round to an even smaller format. Since we don't have a smaller format, it doesn't seem like we need a round-to-odd flavor when converting to BF16.
This is further clarified by the following non-normative text from the RVV spec:
A full set of floating-point narrowing conversions is not supported as single instructions. Conversions can be implemented in a sequence of halving steps. Results are equivalently rounded and the same exception flags are raised if all but the last halving step use round-towards-odd (vfncvt.rod.f.f.w). Only the final step should use the desired rounding mode.

Is there a particular use for round-to-odd conversion targeting BF16?

I did not have a particular example in mind and you explanation makes me think there might not be one (I cannot think of a use-case FP32 -> BF16 -> FP8 where someone would want to avoid double-rounding issue through intermediary use of round-to-odd and as you said FP8 is not even a legal format yet).
I am going to ask around to user more familiar with this matter.


Dropdown always opens upwards if near the bottom of the page, even if there's enough space in the browser window below.

Dropdown always opens upwards if near the bottom of the page, even if there's enough space in the browser window below.
The way viewportBottom is calculated below seems to work fine in my case, but I haven't tested it extensively. The change is at line 873 in select2.js version select2-release-3.2:
    positionDropdown: function() {
        var offset = this.container.offset(),
            height = this.container.outerHeight(),
            width = this.container.outerWidth(),
            dropHeight = this.dropdown.outerHeight(),
            viewportBottom = $(window).scrollTop() + Math.max($(document).height(), $(window).height(), document.documentElement.clientHeight),

In Firefox, if the body has no height(99% of cases) it will open upwards, all the time.


Is there a way to resume download in command line app

If for some reason I quit the application(while downloading) in  the middleway, is there a way to resume the download from where I have left it earlier?

Shouldn't it? Unless you delete /tmp the completed pieces should remain there. iirc

I didn't notice this. Sorry for the trouble.

@hackerkid I'm not saying that that's the way it works for certain. If that doesn't happen, reopen the issue :)

@DiegoRBaquero It's storing the data in the directory from which it was invoked. And it's resuming from where it's left. I didn't notice it before. Thanks. :smile:


Allow files depend on assets

Use case:
component.css:
background: svg-load("icon.svg");

Brunch does not consider icon.svg a dependency. We need to expose API (additional props in dependencies; not "completely new thing") to allow this.

Probably related to progeny. Should it be part of it?

Not related. progeny should be dropped from postcss-brunch.


Fix release-hash-check

The release-hash-check jobs checks out the PR git reference, which is the result of the merging of that PR into master.
But that reference may not be up to date with the latest master.
To run the release-hash-check job always on the latest master, the job now manually fetches the latest master and merges the PR manually into it.

Tested successfully on a fork: https://github.com/FlorianVeaux/integrations-core/runs/1285820584

Created the PR with valid signatures, the test passes
Updated the content of one python file on master
Re-run the workflow, the test fails


Make sglang compat with vllm 0.5.1

vLLM just updated to version 0.5.1 and its changes in Vision Language Model implementation break current SGLang from initializing any model correctly due to the removal of VisionLanguageConfig

Vision Language Model adding support for Phi3-Vision, dynamic image size, and a registry for processing model inputs (https://github.com/vllm-project/vllm/pull/4986, https://github.com/vllm-project/vllm/pull/5276, https://github.com/vllm-project/vllm/pull/5214)

Notably, it has a breaking change that all VLM specific arguments are now removed from engine APIs so you no longer need to set it globally via CLI. However, you now only need to pass in  into the prompt instead of complicated prompt formatting. See more here
There is also a new guide on adding VLMs! We would love your contribution for new models!

This minimal patch at least makes vLLM happy and prevent SRT crashes. I've only tested this patch non-vision model (Qwen2) as I don't have any vision models locally.

@M0gician It is merged. Thanks for the contribution!


1.12.2 Dispensers in jungle temples get turned into lootr chests

The reason this occurs is because of a design decision made to work around the lack of a forge:chest block tag in 1.12. There is now an option where the mod will try to convert any tile entity that has a loot table associated with it. That is enabled by default for 1.12. However, I forgot to consider that jungle temple dispensers are using a loot table...
There are two solutions I see here:

Since the ADDITIONAL_CHESTS config is a blacklist in this mode, I could add minecraft:dispenser to the blacklist by default. However, you specifically will still need to add it yourself since you already have a config generated.
Disable the tile entity replacement mode by default. This means that only vanilla chests will be converted. The main disadvantage of that is that I'll get bug reports about other loot chests not converting themselves like they would on 1.16.

I think solution 1 is probably better here; what do you think?

Oh I see I didn't pay close attention to the config (I probably should have done that lmao) yea def the 1st one

Okay, that's what I've implemented in 0.3.0. Note that you'll still need to add the entry to the config yourself since you previously used an older version.


Mark classes that have a document as comment

To make documentation more discoverable, we should mark the classes that hold live document as comment.

An improved feedback cycle would be created if the ones without a comment would by default show up with the comment tab selected in coder instead of methods :-)

We won't address this. With the introduction of Lepiter the expectation is to have rich comments everywhere there are comments.


KF Hungarian Node bugfixes

Bugfixes for KF Hungarian Node:

Fix uuid local variable reference before assignment issue
Catch all TF lookup-transform related errors
Rename conflicting with Nav2 marker topic
Fix incorrect transform due to translation resetting in do_transform_vector3() function

Otherwise LGTM


Observing Array crashes in Swift 1.2 (Xcode 6.3 Beta)

In a Playground, the following code will result in a runtime error EXC_BAD_ACCESS. In a compiled Swift app, it crashes both the app and Xcode (if debugging), or just the app (if running a release configuration). This makes it tricky to pinpoint the source of this issue.
Since observing arrays used to work previous to this update to Swift, we are probably dealing with a bug in the (reportedly newly improved) compiler. I would file a bug report with Apple, but I have no idea which language feature is actually misbehaving. Perhaps it will be a little more obvious to you, slazyk?
import Observable

class Test {
    var vals = Observable<[Int]>([])

    func put(val: Int) {
        vals.value.append(val)
    }
}

let t = Test()

t.vals.afterChange.add {
    println($0.newValue)
}

t.put(2)

Can you still reproduce in the latest beta?

Nope! Observing Arrays now works now without any errors or crashes.


Fix ansible-lint error on double quote

On my install, I have this error (which is not in ci)
--> Scenario: 'default'
--> Action: 'lint'
--> Executing Yamllint on files found in ansible-minio/...
Lint completed successfully.
--> Executing Flake8 on files found in ansible-minio/molecule/default/tests/...
    ansible-minio/molecule/default/tests/test_minio_default.py:43:17: Q000 Remove bad quotes
An error occurred during the test sequence action: 'lint'. Cleaning up.

ansible-lint --version
ansible-lint 4.1.0

Thanks! :)


Update README.md

Error in readme file, forgot the ngrx-prefix for the store-log-monitor component.

fix readme file

Thanks!


for attribute not working

I can't seem to get:
h('label', {
            attrs: {
                for: 'test'
            }
        },
['test']);

to work. I've tried using props as well.
The text node is rendered but not the for attribute.

Is everything else working as expected?
Are you including all the needed modules in the init call?
var patch = snabbdom.init([
  require('snabbdom/modules/attributes'),
  require('snabbdom/modules/props')
])

I just tested your code (in requirebin.com) and it works ok.
If you're using props, remember you need to use the htmlFor key:
props: {
  htmlFor: 'test'
}

https://developer.mozilla.org/en/docs/Web/API/HTMLLabelElement

htmlFor is just what I needed, thanks for that ;)


Feature: 关于导入schem等Minecraft多方块结构的插件的实施办法

待完善

标题有歧义容易误导其他人，已更改

我认为我需要攻克读取文件这个问题，是否有相关库可以帮助我们？

This feature should using C related codes, such as DLL, etc.

really not context deadline? who will reslove this problem?

really not context deadline? who will resolve this problem?

translate this issue 2 plugin market object is wise

really not context deadline? who will resolve this problem?

I don't know. But I think we will not resolve this problem within 6 months.
But I think we could resolve this issue slowly, so delete context deadline maybe is a choice.

此功能应使用 C 相关功能，例如 DLL 等。

就在刚刚，我找到了一个最后更新在两年前，使用C语言的NBT解析库，测试目前为止可以正常使用

此功能应使用 C 相关功能，例如 DLL 等。

就在刚刚，我找到了一个最后更新在两年前，使用C语言的NBT解析库，测试目前为止可以正常使用

我需要尝试修改一下，以适配Python！


Expand guidance on use of GitHub organisations to explain the GOV.UK One Login now uses govuk-one-login

Comment on 'Use GitHub' (https://gds-way.digital.cabinet-office.gov.uk/standards/source-code/use-github.html)
alphagov is no longer the only GitHub organisation for storing GDS code. The GOV.UK One Login team is moving into a separate organisation govuk-one-login so the guidance should acknowledge this

Updated as part of #884 so closing this issue


fix(#112): replace map by timestamp and add a getUser method

This issue will need to migrate the database because it changes a component of the UserData class

Failed to merge as there were problems in the rebase with the main branch


Raise a meaningful error if relation name is one of the reserved names

For now we know that relations can't be used as a name of a relation. Would be good to look into code and figure out if there are any other names that could break things.

@solnic I'm happy to help with this one

@GustavoCaso cool. Let's start with relations then. We can then add more reserved names easily whenever we discover them.


[Feature Request] Integration with reminders too, not just calendars

Thank you for your app! BUT!!!
one thing that is missing to make it not just the best - but legendary - is the integration with reminders! In this case, when the user would tap on the application icon he would be able to see not only events from the calendar - but also events from reminders, which would give the opportunity to view ALL events, not just events from the calendar! I would gladly pay for such an app upgrade, because this upgrade would make your app absolutely indispensable and has absolutely no competitors! Especially this upgrade would not spoil anything. Those users who do not want reminders to be visible in Itsycal - you could uncheck the checkbox from showing reminders in the section where you select calendars to display.
The new app https://remindercal.bilaal.co.uk/ is trying to solve this problem now - but it does it very inconveniently. But look how many users it has gotten in just half a year! That's because this flaw in viewing events from the calendar and reminders at the same time would be ideally addressed by an app like yours. So I suggest that you do it.
With respect and faith in your app

It turns out that such functionality is already implemented in the application Dato, but still this application is not as convenient as yours. Besides, reminders are NOT displayed as dots in the app itself when you click on the app icon - only calendar events are displayed.
A better way would be to make the reminder dots just a different color. For example, calendar events are blue dots and reminders are orange dots.
So, if you intergrate reminders into your app - then it will definitely be the best. And even if it is paid.

Is it going to be added now that apple calendar will integrate also the reminders? It would be really really handy to see the reminders also in the app. Thanks!

Yeah, it is so exciting someone else is also interested in this.


Bringing up quick pick of Reviewers takes a long time

Version: 1.45.0-insider
Commit: 92ff20ac39c7507fdf4164e2bedfdfb700805fe1
Date: 2020-04-14T18:06:32.175Z
Electron: 7.2.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 17.7.0

Nightly Build of extension: 2020.4.21062
I am working on a PR in https://github.com/micrsoft/vscode-node-azure-pack
On the Description Page, click on the "+" next to Reviewers on the right side

result: after a few minutes the quick pick of people came up.
I realize there are a lot of people in the Microsoft org, but I had time to open the browser and search for a set of issues in this repository before the list came up :).  Maybe there is some progress we can show, or show just the first 100 and page in the rest ...

We should show progress, even though we can't make it any faster.

Looks like showing progress has been fixed in the meantime.


Disable comments on PRs from Coveralls tool.

Steps to reproduce
Working on a PR. For example check #79.
Expected behavior
To see only relevant stuff in the page.
Actual behavior
There are 3 tools enabled at the time of writing . All of them validate the quality of the submitted code. But only 1 of them is spamming with comments in the thread (coveralls).
The report in the bottom is plenty of a status data and there are links to see details if something fails.
So to my point, is there a way to silence it (configuration or something)?
Frameworks tested
Which module / plugin were you using?

[ ] Other (contributing to GITHIB's repo for LCache)

I don't maintain the Coveralls configuration, but I've let others on the team here know.

Done. Coveralls won't leave comments on PRs any longer.


Add script to enumerate installed MSBuild versions

Adding a script, EnumerateMSBuild.ps1, which will output a file
containing all dll/exe files under the Visual Studio instances installed
on your machine. This can be helpful debugging support issues where
symptoms look like mismatched MSBuild versions.

I'm still seeing some truncation in the log file
Microsoft.Build.Tasks.Core.resources.dll              15.6.82+g7377aec628                                                                               C:\Program Files (x86)\Microsoft Vi...

It is. It started out so simple :(


It exit NORMAL mode every time use command.

Every time I use command from NORMAL mode it goes back to INSERT mode.
Can I set default mode to NORMAL?

VIM_MODE_INITIAL_KEYMAP=last

@Wolowit, if the documentation is confusing, please re-open this issue to let me know.


ORT reports error, if copyrightText in SPDX Document is empty

ORT is currently only supporting SPDX version 2.2, where is not clearly specified what to do if the copyrightText of a file is empty.
In Version 2.3 it is now defined to use NOASSERTION if the copyrightText is empty. Since this is not a major version update it should be the same in version 2.2.
See https://github.com/spdx/spdx-spec/blob/development/v2.3/schemas/spdx-schema.json#L520 and https://github.com/spdx/spdx-spec/blob/development/v2.2/schemas/spdx-schema.json#L441 to compare.
Another option would be to simply assume NONE if the string is empty. Either way, ORT should not report an error.
This seems to be similar to https://github.com/oss-review-toolkit/ort/pull/6985
Excerpt from one of our users spdx json file:
"files": [
  {
   "fileName": "/etc/X11/Xsession.d/90gpg-agent",
   "SPDXID": "SPDXRef-File-etc-X11-Xsession.d-90gpg-agent-a17b5f10826a8aca",
   "checksums": [
    {
     "algorithm": "SHA1",
     "checksumValue": "0000000000000000000000000000000000000000"
    }
   ],
   "licenseConcluded": "NOASSERTION",
   "copyrightText": "",
   "comment": "layerID: sha256:f9eef85611c1fa226ded9a9d4fcc070448e050b7282bf662f32167ade49c4a03"
  },
  {
   "fileName": "/etc/alternatives/README",
   "SPDXID": "SPDXRef-File-etc-alternatives-README-2dd9e31817f87f65",
   "checksums": [
    {
     "algorithm": "SHA1",
     "checksumValue": "0000000000000000000000000000000000000000"
    }
   ],
   "licenseConcluded": "NOASSERTION",
   "copyrightText": "",
   "comment": "layerID: sha256:cdd7c73923174e45ea648d66996665c288e1b17a0f45efdbeca860f6dafdf731"
  },

So, this is about reading SPDX files generated by another party via the SpdxDocumentFile "package manager", right? I.e. it is not about SPDX files writing by ORT, which indeed already now should never have a blank string as copyrightText.
If I'm reading your request right, you say that ORT should not complain about copyrightText beig set to a blank string when reading such SPDX files. However, the specs you quote only refer to the case when the "field is not present", not to the case when it is present but set to a blank string.
The specs over here are also not super clear about how to deal with blank strings, but given that the field description says "Any text related to a copyright notice, even if not complete" I'd personally say that a blank string is not related to a copyright notice, and it's also not an incomplete copyright notice (but simply no copyright notice at all).
TL;DR, in my opinion the above SPDX example is invalid according to the specs, and ORT rightfully refuses to parse it. Unfortunately, https://tools.spdx.org/ is currently down so I cannot easily run the validator on it.

However, I believe https://github.com/oss-review-toolkit/ort/pull/7224 is a correct thing to do.

TL;DR, in my opinion the above SPDX example is invalid according to the specs, and ORT rightfully refuses to parse it.

Moreover, the semantics of a blank copyrightText are really unclear: Should it correspond to NOASSERTION or NONE, or should the blank string be taken as a literal copyright statement (which does not really make sense, as it adds no value)? That's one more argument why I believe a blank string should be invalid here.

So, this is about reading SPDX files generated by another party via the SpdxDocumentFile "package manager", right? I.e. it is not about SPDX files written by ORT, which indeed already now should never have a blank string as copyrightText.
If I'm reading your request right, you say that ORT should not complain about copyrightText being set to a blank string when reading such SPDX files.

Yes, that is correct. I have provided your answer to the user who raised this issue with us and will get back to you.

Hey @sschuberth @hanna-modica, I raised this issue and I totally agree that this is definitely not clear in any documentation.
I just ran our spdx.json with these entries trough the validator and it says it is valid. I'm definitely no expert in spdx and don't know what exactly is validated there or which version is taken into account...
But since everybody and every tool generating spdx can have different interpretations and ORT I guess wants to be a general analyzer, I would like to see ORT handling everything gracefully.
I personally would vote for an empty string being the same as if the field is not present and therefore means NOASSERTION. This would, at least in our case, also fit the values for "licenseConcluded" and could also fit the description of NOASSERTION "if
the SPDX document creator has made no attempt to determine this field; or

the SPDX document creator has intentionally provided no information (no meaning should be implied from the absence of an assertion)."  (https://spdx.github.io/spdx-spec/v2.3/file-information/#88-copyright-text-field)

So an empty string means the creator intentionally did not specify this.
But again there is plenty of room for different interpretations...
Would there even be a difference between NONE and NOASSERTION for the copyrightText? I thought the license is more important. In version 2.3 the copyrightText is even not mandatory anymore...

I guess wants to be a general analyzer, I would like to see ORT handling everything gracefully.

Actually, to me an important aspect of ORT also is to enforce best practices and standards. Sure, we could be lenient when reading and strict when writing, but that probably does not help much to question ambiguous SPDX documents that are in the wild, in order to bubble up to the tools that created them and fix these.

also fit the values for "licenseConcluded"

I believe you, like @hanna-modica, are mixing up the cases where licenseConcluded is not specified at all vs. set to an empty string: It's out of question now that an absent licenseConcluded should be interpreted as NOASSERTION. But what if someone would set a licenseConcluded to the empty string? It's not specified that this should map to NOASSERTION; NONE would just make as much sense, IMO.

Would there even be a difference between NONE and NOASSERTION for the copyrightText?

Yes: NONE means that you have tried to find you the copyright, and came to the conclusion that there is none. NOASSERTION can either mean that you didn't try in the first place, or that you tried but came to no conclusion.
To me the question boils down to: Why risk that something could be misinterpreted by using unspecified values? Instead, as an SPDX document author I'd simply play safe and avoid empty / blank string being written for licenseConcluded, and be explicit about what I mean by using NOASSERTIONor NONE.

Actually, to me an important aspect of ORT also is to enforce best practices and standards. Sure, we could be lenient when reading and strict when writing, but that probably does not help much to question ambiguous SPDX documents that are in the wild, in order to bubble up to the tools that created them and fix these.

I would expect the SPDX community to enforce best practices and standards. At the end ORT and all other tools are just users of SPDX and as already mentioned can have different interpretations of unclear statements.

I believe you, like @hanna-modica, are mixing up the cases where licenseConcluded is not specified at all vs. set to an empty string: It's out of question now that an absent licenseConcluded should be interpreted as NOASSERTION. But what if someone would set a licenseConcluded to the empty string? It's not specified that this should map to NOASSERTION; NONE would just make as much sense, IMO.

You are totally right that it is the same case for licenseConcluded, but in the example above licenseConcluded is set to NOASSERTION but for the copyrightText we have the empty string. That's why I meant in this case one could assume the empty string also means NOASSERTION as it would match the license.

Instead, as an SPDX document author I'd simply play safe and avoid empty / blank strings being written for licenseConcluded, and be explicit about what I mean by using NOASSERTIONor NONE.

The licenseConcluded is set to NOASSERTION but the copyrightText is not.
Interestingly on the linked specs from the website this field is marked as mandatory: https://spdx.github.io/spdx-spec/v2.2.2/file-information/#88-copyright-text-field
Whereas it is not mandatory in the linked specs from the GitHub repo: https://spdx.github.io/spdx-spec/v2-draft/file-information/#88-copyright-text-field
If it is not mandatory I would even say that ORT could totally ignore it if there is no valid entry.
Lets see what the SPDX guys tell us.

Lets see what the SPDX guys tell us.

👍🏻

I just ran our spdx.json with these entries trough the validator and it says it is valid.

Interesting. When I set the text for an existing copyrightText to the empty string in https://github.com/spdx/tools-java/blob/master/testResources/SPDXJSONExample-v2.2.spdx.json, then https://tools.spdx.org/app/validate/ tells me
The following warning(s) were raised: [Relationship error: Relationship error: Missing required copyright text for ./src/org/spdx/parser/DOAPProject.java in ./src/org/spdx/parser/DOAPProject.java in glibc in glibc in SPDX-Tools-v2.0]

Indeed interesting, if I just add an file from our spdx to your example it is still valid. Thats what I added to files section
    {
      "fileName": "/etc/X11/Xsession.d/90gpg-agent",
      "SPDXID": "SPDXRef-File-etc-X11-Xsession.d-90gpg-agent-a17b5f10826a8aca",
      "checksums": [
        {
          "algorithm": "SHA1",
          "checksumValue": "0000000000000000000000000000000000000000"
        }
      ],
      "licenseConcluded": "NOASSERTION",
      "copyrightText": "",
      "comment": "layerID: sha256:f9eef85611c1fa226ded9a9d4fcc070448e050b7282bf662f32167ade49c4a03"
    },

Interesting. When I set the text for an existing copyrightText to the empty string in https://github.com/spdx/tools-java/blob/master/testResources/SPDXJSONExample-v2.2.spdx.json, then https://tools.spdx.org/app/validate/ tells me

This is because in version 2.2 of the spec, the copyrighText was required.  In version 2.3, this restriction was removed.  If you try an empty copyright in the 2.3 examples, it should return valid.

This is because in version 2.2 of the spec, the copyrighText was required. In version 2.3, this restriction was removed.

But note that "not present" is not the same thing as "present and set to empty".

ORT is currently only supporting SPDX version 2.2, where is not clearly specified what to do if the copyrightText of a file is empty.

With the statement from here, it has been clarified that proving a blank string for the copyrightText fields as part of an SPDX 2.2 document (which is the only version ORT supports currently, also see this, although it refers more to output than input of SPDX) is invalid, and the SPDX producer should use NOASSERTION instead.
In that regard ORT's behavior is strict, but correct, so I'm closing this. For making SPDX parsing optionally less strict also see https://github.com/oss-review-toolkit/ort/issues/8052 (at the example of licenseInfoInFiles).


better passwdgen

Patch for a better passwdgen function.
It can generates nearly infinity lenght of passwords and uses [0-9a-zA-Z_] as base chars.
patch: https://github.com/TuxCoder/dotfiles/commit/a8fc8a9f4295d9861bdf19421e44e4c15fd13b4e

better passwdgen is also merged, thx


Added a start_local.bat to start the compose file directly in Windows

This makes life a little bit easier.
To make it work, #158 also needs to be merged, otherwise the compose startup will fail.

So this would work to start the server directly in the CMD prompt on Windows? When using WSL, the current start_local.sh script already works right?
Assuming yes, while it's nice to make getting started easier on Windows, because Windows users will need WSL anyway to run the Plandex CLI, I'm wondering if directing them towards WSL in the self-hosting guide would be better.


Formatting of stories below fold is incorrect - GEM MOLO (FED)

@peterp please review this commit:
https://github.com/praekelt/molo-gem/pull/103/commits/f14903f4c87b2114dd4af62a3c48887048e28ede
Solve: Commented out old _style.scss and _enhanced.scss styles for a uniform button _styles.scss style
Old

New

NOTE: I added it by mistake, already created it's own issue here:
https://github.com/praekelt/molo-gem/issues/105

@peterp please review

Current issue:


Updated HST data

Updated HST data. amu.rep files from 2019 FGS calibration. siaf.dat files from 2022 COS LP6 update.

Seems like the new siaf.dat-Latest file has spaces at the end of each line that weren't in the old file.  I'm not sure if that would break things, but it looks like it's passing tests.


Discord not opening with betterdiscord installed

I'm getting an error on startup that prevents Discord from opening.
Error: EACCES: permission denied, open '/home/user/.local/share/betterdiscordctl/bd/0/betterdiscord/config.json'
at Object.openSync (fs.js:447:3)
at Object.func (electron/js2c/asar.js:140:31)
at Object.func [as openSync] (electron/js2c/asar.js:140:31)
at Object.writeFileSync (fs.js:1206:35)
at Object.<anonymous> (/home/user/.local/share/betterdiscordctl/bd/0/betterdiscord/index.js:28:4)
at Module._compile (internal/modules/cjs/loader.js:880:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:892:10)
at Module.load (internal/modules/cjs/loader.js:735:32)
at Module._load (internal/modules/cjs/loader.js:648:12)
at Module._load (electron/js2c/asar.js:717:26)

It doesn't seem like the file it's trying to load exists, here's the directory tree:
user@pc:~/.local/share/betterdiscord$  tree
.
└── custom
    └── notifications
        └── sounds
            ├── Oxygen-Im-Contact-In.ogg
            └── Oxygen-Im-Contact-Out.ogg

3 directories, 2 files

sudo betterdiscordctl reinstall -v -v results:
VV: Scanning /opt
VV: Trying flavor ''
VV: Trying flavor 'canary'
VV: Trying flavor 'ptb'
VV: Scanning /usr/share
VV: Trying flavor ''
V: Using Discord at /usr/share/discord
V: Found modules in /home/user/.config/discord/0.0.10/modules
Killing Discord processes...

V: Linking BetterDiscord injector...
Reinstalled.

I ran sudo betterdiscordctl update and sudo betterdiscordctl upgrade a few times for good measure, before and after reinstalling. Uninstalling and installing produces the same error on startup. Discord opens without error when BD is uninstalled.

Stop using sudo. Remove ~/.local/share/betterdiscordctl and try again.

Thank you!


[Feature] Support to post multiple comments without overwriting existing comments

First of all, thank you for this incredibly helpful tool!
Currently, the action overwrites existing comments when it runs. While this behavior can be useful in some cases, I have a workflow where PRs run multiple Playwright tests from different sources. For example:

API tests
UI tests

In this situation, I need the ability to post multiple comments on the same PR, instead of having the latest one overwrite the previous comment.
Request
Could you please add a feature that allows the action to post multiple comments without overwriting the existing ones?
Thanks a lot!

This already exists :) When you pass in a different report-tag option to each test report, it will only overwrite the comments if they were created by that report. See this comment for an example.


Fixes #2734 by only using the available assigned ports instead of all…

… dynamically assigned ports.
Problem in short:
step 1: user send ports=[0] this will result in ports=[10000]
step 2: user updates ports to ports=[10000, 0]
the logic would see 10000 as available free port, remembers that and will it assign to the next dynamic value. This will result in [10000, 10000] which breaks validation.

:rocket:


SPIFFS on Wemos D1 Mini

Trying to get SPIFFS working on a Wemos D1 Mini. These boards have 4meg of flash, 3meg for code/data and 1meg for SPIFFS. Using SPIFFS with the Arduino IDE on the board works.
The problem is getting the SPIFFS bin flashed to the board correctly.
My makefile looks like this:
PROGRAM=tempsensor
EXTRA_COMPONENTS = extras/i2c extras/bmp180 extras/paho_mqtt_c extras/spiffs extras/sntp
ESPPORT = /dev/ttyUSB0
FLASH_SIZE = 4
SPIFFS_BASE_ADDR = 0x300000
SPIFFS_SIZE = 0x19000
SPIFFS_SINGLETON = 1
include /home/wesw/dev/esp8266/esp-open-rtos/common.mk
$(eval $(call make_spiffs_image,files))
When I run "make flash" I get the following:
esptool.py v1.2
Connecting...
Running Cesanta flasher stub...
Flash params set to 0x0000
Writing 4096 @ 0x0... 4096 (100 %)
Wrote 4096 bytes at 0x0 in 0.4 seconds (90.1 kbit/s)...
Writing 4096 @ 0x1000... 4096 (100 %)
Wrote 4096 bytes at 0x1000 in 0.4 seconds (90.1 kbit/s)...
Writing 282624 @ 0x2000... 282624 (100 %)
Wrote 282624 bytes at 0x2000 in 24.4 seconds (92.8 kbit/s)...
WARNING: Unlikely to work as data goes beyond end of flash. Hint: Use --flash_size
Writing 102400 @ 0x300000... 102400 (100 %)
Wrote 102400 bytes at 0x300000 in 8.8 seconds (92.8 kbit/s)...
Leaving...
The ESPTOOL says that the SPIFFS image is being flashed beyond the end of the flash. Strange because the 0x300000 address is not beyond the end.
Can someone tell me how to use SPIFFS with this board and ESP Open RTOS??

This appears to be caused by the fact that esp open rtos has an ancient version of esptool. Using the current (v2.5) of esptool works properly.


Slower but better: more redundant data for metamodels

Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CLA).
[x] All tests passed, and additional code has been covered with new tests.

Good but deprecated by other PRs.


Spigot?

You should publish this on Spigot...

No need to publish on the spigot area as it's already on bukkitdev - http://dev.bukkit.org/bukkit-plugins/jpanel/
Plugins on bukkitdev generally work on spigot - it's best to try them first before asking if they work :)


Connect to actual robot

How do you use this to actually control the Dorna robot?
I can open "rosrun dorna_nodes dorna_moveit_gazebo.py" and plan movement but how do I actually get it to connect?
I tried opening another command prompt and connecting there using the normal python robot.connect() but that doesn't seem to help either.
When I'm in RViz under MotionPlanning -> Planning and I click Execute I just get failed.
Any help would be greatly appreciated!

Just saw this I am so sorry.
The gazebo simulation is not connected to the actual robot.  If you want to move the actual robot then you should run:
roslaunch dorna_ros.launch

This is in the dorna_ros package

Moveit is not directly connected to the robot, it provides a trajectory to the DornaRos object in dorna_ros_node.py and then re-formats that ros message to a dorna message in dorna_cmd_utils.py

@mfogelson I think I got a bit further. Now I am getting the error: ABORTED: Solution found but controller failed during execution, when I try and Execute a MotionPlanning event. However I only get this far after running  roslaunch dorna_gazebo dorna.launch. When running  roslaunch dorna_ros dorna_ros.launch, the motion library doesn't load.
I feel like something is missing in the repo. Could you reupload your working files? Or perhaps post a YouTube video showing how to set this up correctly. I've tried about 100 different ways and I keep running into errors.


pep508 dependency specification

the current setup.py does not conform to pep508. Hence it can lead to issues like this.
This PR rewrites the dependencies using pep508

This PR is a bit old, due to lapses on the fault of maintainers for reviewing PRs and merging them. That said, There's a conflict with the main branch that must be resolved. WIthout that resolution soon (next week or so) I'd recommend closing this PR without merging.


Add simple solution to update of OAuth with more consistent identifiers

See issue #952
All tests are passing, but might need to add new ones to showcase what this fixes.

Let's go like this :) Thanks @ricfri!

@all-contributors add @ricfri for bug


how to set multiple values  via js ?  version:select2-bootstrap-theme.

I download the latest version of select2, and I want to use bootstrap theme ,so I selected the version of select2-bootstrap-theme.but when I want to set multiple values for it ,it not work.
my code:
$("#select2-button-addons-single-input-group-sm-1").select2("val",["2126244","3620194"]);
file I used:
bootstrap/css/bootstrap.css
//cdnjs.cloudflare.com/ajax/libs/select2/4.0.3/css/select2.min.css
bootstrap/css/select2-bootstrap.css
jquery/1.12.4/jquery.min.js
select2/4.0.3/js/select2.full.js
bootstrap/js/bootstrap.min.js
js/anchor.min.js
Who can tell me  what the reason is  ? thanks very much

hey bro  can you set select2 input-sm

$("#your-select-input").val(["val1", "val2"]).trigger("change");
Check the documentation: https://select2.github.io/examples.html#programmatic

Yes, the select2('val', ... method has been removed and replaced with .val().  See the documentation.


Correct lowLevelDevices versus lowLevel capability

Correct and clarify information regarding the lowLevelDevices capability, and the lowLevel device capability. Two very different things with similar and misleading names!

Removed en-us from new links.

@msatranjr @mikematteson I have removed en-us from the links. Please review when you get a chance. Thanks.

@jordanrh1 : Sorry for the delay in getting back to this. I see the 'en-us/' has been removed from the device interface link URL, but there are 5 or 6 other URLs later in the PR text that still include the locale specifier. Would you please remove those too?
@msatranjr : Would you please review the PR further and let Jordan know if additional changes will be needed beyond what I've flagged from the checklist? Thanks!

@mikematteson Oops. I went ahead and removed the other en-us references.

@jordanrh1 : Confirmed that locale specifiers have been removed from the PR text, so this submission now passes our acceptance checklist. Still need Michael to review.
@msatranjr :  Please review. Also, please note:

The GitHub UI is reporting a merge conflict for this PR now. Would you please resolve if possible?
Some 'en-us' locale specifiers remain in URLs outside the scope of the PR. Please address in the private repo as time permits.

Fixed merge conflict.

@mikematteson Any other changes you'd like me to make?

@jordanrh1 Looks good, thanks. I've marked all checklist hits as resolved.
@msatranjr Merge conflict and locale specifiers have been addressed. Any other concerns to work out with Jordan, or can this be merged? Thanks!


Support for timeZone in Scheduled Spark Jobs

What question do you want to ask?
I’d like to request the addition of a timeZone option for scheduled Spark jobs in the Spark Operator. Starting with Kubernetes 1.25, the timeZone field is supported in CronJobs, allowing users to specify the timezone for scheduling. However, this feature does not currently appear to be supported in the Spark Operator’s scheduled job configuration.
This omission makes it challenging to manage Spark job schedules in multi-timezone environments. Users have to resort to workarounds, such as adjusting schedules manually or modifying their application logic, which can be error-prone and less intuitive compared to native timezone support.
It would be great if the Spark Operator could include support for timeZone, aligning with Kubernetes’ native CronJob capabilities. This addition would enhance usability and make scheduling Spark jobs more straightforward and consistent with Kubernetes standards.
Looking forward to hearing your thoughts on this! Please let me know.
Additional context
No response
Have the same question?
Give it a 👍 We prioritize the question with most 👍

Left a comment on the earlier issue https://github.com/kubeflow/spark-operator/issues/1712#issuecomment-2495671280


[helm-oci] disable cache in oci registry client

fixes #787
If implemented, the oci registry client is created with cache disabled.
Signed-off-by: Soule BA<EMAIL_ADDRESS>

github.com/fluxcd/pkg/helmtestserver has to be downgraded to v0.7.2 to work. Otherwise we need to update it first I think.

@souleb can you rebase please.


First proper pull request to implement the bmx160 into goflying

This is the right version.

This was merged into branch stratux_master instead of master.  Will eventually merge stratux_master into master branch.


Ability to stop collection of user analytics / SDK UUID.

Before opening a feature request against this repo, consider whether the feature is generic enough for the SDK, or it should be a specific plugin/extension to the SDK.
Is your feature request related to a problem?
There is no way to disable collecting SDK UID using the SDK.
Describe the solution you'd like.
Add ability to disable collecting OS version. Ideally, add a method semanticContext->SetSDKUID() which can take null, empty string, "redacted" or take an option to turn it off.
Describe alternatives you've considered.
Additional context.

As discussed, please use custom decorator to clear the field.

Closing as no response. Please reopen if still required,


make contracts-input-box-block optional

will manually change base branch back to main before merge

Reminder to review this PR. Thanks :)


Text is not visible in light-theme for useSyncedEffect hook's doc

Describe the bug

In light theme, text is not visible for useSyncedEffect hook's doc

Expected behavior

Background should change according to theme.

Screenshots

How to fix

Go to src/hooks/use-synced-effect/example.tsx to fix the issue.

i can solve it assign it to me

I've identified a potential cause of the background color issue in light mode. The div lacks a dark: variant for the background color, so I propose to change the line to


build pipeline in TeamCity fails

I came across your well crafted solution for docker-phoenix and I'm trying to get it work in TeamCity to achieve a documented build pipeline,
Connected a TeamCity-Project to a repo in gogs (git like selfhosted repo)
and set up a TeamCity Build Step: Command Line  with command  docker-compose up --build
[docker compose up --build  (without the minus) didn't work]
Due to my yet limited experience using Docker and Phoenix I'm asking you if you could possibly point me into the right direction why this build fails.
I did the following steps according to the README:
git clone https://github.com/nickjj/docker-phoenix-example hellophoenix
cd hellophoenix
cp .env.example .env

[committed the .env to the testrepo and changed .gitignore and .dockerignore to not ignore .env]
docker-compose up --build   # in teamcity shell command
The build fails with the following log:
Step 1/1: Command Line
23:16:40   Starting: /opt/buildagent/temp/agentTmp/custom_script3179222894012803463
23:16:40   in directory: /opt/buildagent/work/34b3e6d02e4125c3
23:16:41   Building web
23:16:41   #2 [internal] load build definition from Dockerfile
23:16:41   #2 transferring dockerfile: 2.99kB done
23:16:41   #2 DONE 0.1s
23:16:41
23:16:41   #1 [internal] load .dockerignore
23:16:41   #1 transferring context: 151B done
23:16:41   #1 DONE 0.1s
23:16:41
23:16:41   #4 [internal] load metadata for docker.io/library/elixir:1.15.4-slim
23:16:44   #4 DONE 2.5s
23:16:44
23:16:44   #3 [internal] load metadata for docker.io/library/node:18.15.0-bullseye-slim
23:16:44   #3 DONE 2.5s
23:16:44
23:16:44   #13 [dev  1/11] FROM docker.io/library/elixir:1.15.4-slim@sha256:430b719241b01d3326ab9ff24b9799c6bcc22e93206ae54e626403f17227d33b
23:16:44   #13 DONE 0.0s
23:16:44
23:16:44   #14 [assets 1/7] FROM docker.io/library/node:18.15.0-bullseye-slim@sha256:639e94182196dccc83a45224a10d2a3cb4139c0e3d05194b64d6587ce2919e8c
23:16:44   #14 DONE 0.0s
23:16:44
23:16:44   #12 [internal] load build context
23:16:44   #12 transferring context: 373.48kB 0.0s done
23:16:44   #12 DONE 0.1s
23:16:44
23:16:44   #6 [assets 2/7] WORKDIR /app/assets
23:16:44   #6 CACHED
23:16:44
23:16:44   #20 [dev  4/11] RUN mix local.hex --force && mix local.rebar --force
23:16:44   #20 CACHED
23:16:44
23:16:44   #5 [assets 3/7] RUN apt-get update   && apt-get install -y --no-install-recommends build-essential   && rm -rf /var/lib/apt/lists/* /usr/share/doc /usr/share/man   && apt-get clean   && groupmod -g "1000" node && usermod -u "1000" -g "1000" node   && mkdir -p /node_modules && chown node:node -R /node_modules /app
23:16:44   #5 CACHED
23:16:44
23:16:44   #16 [assets 4/7] COPY --chown=node:node assets/package.json assets/*yarn* ./
23:16:44   #16 CACHED
23:16:44
23:16:44   #11 [assets 7/7] RUN if [ "development" != "development" ]; then   ../run yarn:build:js && ../run yarn:build:css; else mkdir -p /app/priv/static; fi
23:16:44   #11 CACHED
23:16:44
23:16:44   #18 [dev  3/11] RUN apt-get update   && apt-get install -y --no-install-recommends build-essential curl inotify-tools   && rm -rf /var/lib/apt/lists/* /usr/share/doc /usr/share/man   && apt-get clean   && groupadd -g "1000" elixir   && useradd --create-home --no-log-init -u "1000" -g "1000" elixir   && mkdir -p /mix && chown elixir:elixir -R /mix /app
23:16:44   #18 CACHED
23:16:44
23:16:44   #7 [dev  6/11] RUN if [ "dev" = "dev" ]; then   mix deps.get; else mix deps.get --only "dev"; fi
23:16:44   #7 CACHED
23:16:44
23:16:44   #10 [assets 5/7] RUN yarn install && yarn cache clean
23:16:44   #10 CACHED
23:16:44
23:16:44   #8 [dev  7/11] COPY --chown=elixir:elixir config/config.exs config/dev.exs config/
23:16:44   #8 CACHED
23:16:44
23:16:44   #15 [dev  9/11] COPY --chown=elixir:elixir --from=assets /app/priv/static /public
23:16:44   #15 CACHED
23:16:44
23:16:44   #9 [dev 10/11] COPY --chown=elixir:elixir . .
23:16:44   #9 CACHED
23:16:44
23:16:44   #17 [assets 6/7] COPY --chown=node:node . ..
23:16:44   #17 CACHED
23:16:44
23:16:44   #21 [dev  2/11] WORKDIR /app
23:16:44   #21 CACHED
23:16:44
23:16:44   #19 [dev  5/11] COPY --chown=elixir:elixir mix.* ./
23:16:44   #19 CACHED
23:16:44
23:16:44   #22 [dev  8/11] RUN mix deps.compile
23:16:44   #22 CACHED
23:16:44
23:16:44   #23 [dev 11/11] RUN if [ "dev" != "dev" ]; then   ln -s /public /app/priv/static     && mix phx.digest && mix release && rm -rf /app/priv/static; fi
23:16:44   #23 CACHED
23:16:44
23:16:44   #24 exporting to image
23:16:44   #24 exporting layers done
23:16:44   #24 writing image sha256:be40c12202c0f327dd77937e94add4995104c209222c6677afbe2dd6ce30f5d0 0.0s done
23:16:44   #24 naming to docker.io/library/hellophoenix_web 0.0s done
23:16:44   #24 DONE 0.0s
23:16:44   Successfully built be40c12202c0f327dd77937e94add4995104c209222c6677afbe2dd6ce30f5d0
23:16:44   Building js
23:16:44   #2 [internal] load build definition from Dockerfile
23:16:44   #2 transferring dockerfile: 2.99kB done
23:16:44   #2 DONE 0.1s
23:16:44
23:16:44   #1 [internal] load .dockerignore
23:16:44   #1 transferring context: 151B done
23:16:44   #1 DONE 0.1s
23:16:44
23:16:44   #3 [internal] load metadata for docker.io/library/node:18.15.0-bullseye-slim
23:16:45   #3 DONE 0.2s
23:16:45
23:16:45   #11 [assets 1/7] FROM docker.io/library/node:18.15.0-bullseye-slim@sha256:639e94182196dccc83a45224a10d2a3cb4139c0e3d05194b64d6587ce2919e8c
23:16:45   #11 DONE 0.0s
23:16:45
23:16:45   #8 [internal] load build context
23:16:45   #8 transferring context: 4.54kB 0.0s done
23:16:45   #8 DONE 0.0s
23:16:45
23:16:45   #9 [assets 3/7] RUN apt-get update   && apt-get install -y --no-install-recommends build-essential   && rm -rf /var/lib/apt/lists/* /usr/share/doc /usr/share/man   && apt-get clean   && groupmod -g "1000" node && usermod -u "1000" -g "1000" node   && mkdir -p /node_modules && chown node:node -R /node_modules /app
23:16:45   #9 CACHED
23:16:45
23:16:45   #6 [assets 5/7] RUN yarn install && yarn cache clean
23:16:45   #6 CACHED
23:16:45
23:16:45   #10 [assets 2/7] WORKDIR /app/assets
23:16:45   #10 CACHED
23:16:45
23:16:45   #5 [assets 6/7] COPY --chown=node:node . ..
23:16:45   #5 CACHED
23:16:45
23:16:45   #7 [assets 4/7] COPY --chown=node:node assets/package.json assets/*yarn* ./
23:16:45   #7 CACHED
23:16:45
23:16:45   #4 [assets 7/7] RUN if [ "development" != "development" ]; then   ../run yarn:build:js && ../run yarn:build:css; else mkdir -p /app/priv/static; fi
23:16:45   #4 CACHED
23:16:45
23:16:45   #12 exporting to image
23:16:45   #12 exporting layers done
23:16:45   #12 writing image sha256:7d72edda23eda94e9e4cdcba3be001a0c2107e9836562c8246aacb75da4b4d7f 0.0s done
23:16:45   #12 naming to docker.io/library/hellophoenix_js 0.0s done
23:16:45   #12 DONE 0.0s
23:16:45   Successfully built 7d72edda23eda94e9e4cdcba3be001a0c2107e9836562c8246aacb75da4b4d7f
23:16:45   Building css
23:16:45   #1 [internal] load .dockerignore
23:16:45   #1 transferring context: 151B done
23:16:45   #1 DONE 0.0s
23:16:45
23:16:45   #2 [internal] load build definition from Dockerfile
23:16:45   #2 transferring dockerfile: 2.99kB done
23:16:45   #2 DONE 0.0s
23:16:45
23:16:45   #3 [internal] load metadata for docker.io/library/node:18.15.0-bullseye-slim
23:16:45   #3 DONE 0.2s
23:16:45
23:16:45   #6 [assets 1/7] FROM docker.io/library/node:18.15.0-bullseye-slim@sha256:639e94182196dccc83a45224a10d2a3cb4139c0e3d05194b64d6587ce2919e8c
23:16:45   #6 DONE 0.0s
23:16:45
23:16:45   #11 [internal] load build context
23:16:45   #11 transferring context: 4.54kB 0.0s done
23:16:45   #11 DONE 0.0s
23:16:45
23:16:45   #5 [assets 2/7] WORKDIR /app/assets
23:16:45   #5 CACHED
23:16:45
23:16:45   #10 [assets 4/7] COPY --chown=node:node assets/package.json assets/*yarn* ./
23:16:45   #10 CACHED
23:16:45
23:16:45   #4 [assets 3/7] RUN apt-get update   && apt-get install -y --no-install-recommends build-essential   && rm -rf /var/lib/apt/lists/* /usr/share/doc /usr/share/man   && apt-get clean   && groupmod -g "1000" node && usermod -u "1000" -g "1000" node   && mkdir -p /node_modules && chown node:node -R /node_modules /app
23:16:45   #4 CACHED
23:16:45
23:16:45   #9 [assets 5/7] RUN yarn install && yarn cache clean
23:16:45   #9 CACHED
23:16:45
23:16:45   #8 [assets 6/7] COPY --chown=node:node . ..
23:16:45   #8 CACHED
23:16:45
23:16:45   #7 [assets 7/7] RUN if [ "development" != "development" ]; then   ../run yarn:build:js && ../run yarn:build:css; else mkdir -p /app/priv/static; fi
23:16:45   #7 CACHED
23:16:45
23:16:45   #12 exporting to image
23:16:45   #12 exporting layers done
23:16:45   #12 writing image sha256:7d72edda23eda94e9e4cdcba3be001a0c2107e9836562c8246aacb75da4b4d7f 0.0s done
23:16:45   #12 naming to docker.io/library/hellophoenix_css 0.0s done
23:16:45   #12 DONE 0.0s
23:16:45   Successfully built 7d72edda23eda94e9e4cdcba3be001a0c2107e9836562c8246aacb75da4b4d7f
23:16:45   Creating hellophoenix_postgres_1 ...
23:16:45   Creating hellophoenix_css_1      ...
23:16:45   Creating hellophoenix_js_1       ...
23:16:48   Creating hellophoenix_js_1       ... done
23:16:48   Creating hellophoenix_postgres_1 ... done
23:16:48   Creating hellophoenix_web_1      ...
23:16:49   Creating hellophoenix_css_1      ... done
23:16:50   Creating hellophoenix_web_1      ... error
23:16:50
23:16:50   ERROR: for hellophoenix_web_1  Cannot start service web: failed to create task for container:
failed to create shim task: OCI runtime create failed:
runc create failed: unable to start container process:
exec: "/app/bin/docker-entrypoint-web": stat /app/bin/docker-entrypoint-web:
no such file or directory: unknown
23:16:50
23:16:50   ERROR: for web  Cannot start service web: failed to create task for container:
                                  failed to create shim task: OCI runtime create failed:
                                   runc create failed: unable to start container process:
                                  exec: "/app/bin/docker-entrypoint-web": stat /app/bin/docker-entrypoint-web:
                                 no such file or directory: unknown
23:16:50   Encountered errors while bringing up the project.
23:16:51   Process exited with code 1
23:16:51   Process exited with code 1 (Step: Command Line)
23:16:51   Step Command Line failed

Hi,
I've never used TeamCity. How do they install Docker? What version of Docker and Docker Compose is running?
I've also seem similar errors in the past when a file has been saved with Windows line endings (CRLF) when it expects Unix line endings (LF). In this case maybe the entrypoint file got saved like that.

Hi, thank you for your quick response!
This is running on Ubuntu 20.04 focal, installed docker-ce, installed TeamCity as Docker Image
Docker version 24.0.5, build ced0996
docker-compose version 1.25.0, build unknown
I saved the entrypoint file again but it outputs the same error

Are you able to use Docker Compose v2?
Did you save it with LF line endings?

Sorry, I have installed docker-compose version 1.25.0 just now but remembered now to have it installed as plugin like so
apt-get install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin and removed docker-compose version 1.25.0 again
Yes,
docker compose version reports:
Docker Compose version v2.20.2
Yes, I recreated the file and checked that the line endings are LF
As I mentioned the command docker compose up --build doesnt work in the build setup
unknown flag: --build - maybe this is the problem?

Ok I found out what version is really used if running the command from TeamCity ...
Docker version 24.0.5, build ced0996
docker-compose version 1.28.5, build c4eb3a1f

So I guess this has nothing to do with your docker-phoenix-example anymore.
Thank you for your help leading me one step further!

I'm surprised --build comes up as an unknown flag. That flag has been around for a really long time.
I'd suggest removing everything Docker related on the system using apt-get remove --purge on all Docker packages. Then run a which docker-compose and find out where this file is installed and delete it.
Then, install Docker:
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh ./get-docker.sh

Then, install the latest Docker Compose v2:
sudo apt-get install docker-compose-plugin

Then verify things with docker info and docker compose version, running which docker-compose should produce a not found since you wouldn't have Docker Compose v1 installed.


Button Force refresh

Would it be possible to add some button to force refresh manually, as when I refresh state in Bluelink? Thanks a lot

Easy enough for you to add it.

Yes you can you can also view it in developer tools actions.  I believe referenced in the readme for the title.

Thanks. Indeed it's kia_uvo.force_update

hello, I'm sorry but I didn't understand where to find this function in H.A
Can you help me ?

Thanks a lot


'rate_limit_status' Not updated anymore for  'followers_ids'

Hi,
There seems to be a recent issue on the update of rate_limits. The bellow code worked well for weeks, but since yesterday, the last line keeps printing '15', meaning that the rate limit doesn't update. However, after 15 queries, twitter API returns the error 'rate_limit exceeded', but the  api.rate_limit_status()['resources']['followers']['/followers/ids']['remaining'] stays at '15'. Any idea what might cause that? Is it on Twitter side, or Tweepy side?
api = tweepy.API(auth)

for user in user_list:
    def limit_handled(cursor):
        while True:
                try:
                    yield cursor.next()
                except BaseException as e:
                    print('failed_on_CURSOR_NEXT', str(e))

     data = api.rate_limit_status()
     user_followers_remaining = data['resources']['followers']['/followers/ids']['remaining']

    for follower in limit_handled(tweepy.Cursor(api.followers_ids, id = id_i).pages()):
        for fll in follower:
           print(fll)
    print(str(user_followers_remaining))

Thank you.

Well, I just gave it few days and tried the same code again today, and it's working now. Maybe some problems that got resolved on the API side... I'm closing this thread now.


The action 'index' could not be found for Refinery::Blog::Admin::SettingsController

Index action missing in Refinery::Blog::Admin::SettingsController
getting this:
AbstractController::ActionNotFound (The action 'index' could not be found for Refinery::Blog::Admin::SettingsController):

I think this is an issue within Refinery::Blog, not settings.
Blog has its own controller for Settings.


[UI] Programs page is covered by footer

Description
Programs page at https://meshery.io/programs is hidden by the footer
Expected Behavior
Subcribe form should be visible to user and not hidden
Screenshots/Logs

Environment:

Meshery Version:
Kubernetes Version:
Host OS: MacOS
Browser:  Firefox latest version

Whoops, wrong repo

Hey @Kn99HN  Good catch.. This is a valid issue ..
Please Open it here https://github.com/layer5io/meshery.io


DBZ-6758 When using pgoutput in postgres connector, (+/-)Infinity is not supported in decimal values

https://issues.redhat.com/browse/DBZ-6758

@harveyyue Thanks for the PR. The statement io.debezium.connector.postgresql.AbstractRecordsProducerTest.INSERT_NUMERIC_TYPES_STMT was expected to test infinite values and was passing before the change. Could you please check why it was the case? If this scenario is not cevered, could you please add another test?

@jpechane OK

@jpechane The IT AbstractRecordsProducerTest  not match following properties:
plugin.name=pgoutput
decimal.handling.mode=string

@harveyyue Makes sense. Apllied, thanks a lot!