EOF errors

╰─± dinghy up --no-proxy
Bringing machine 'dinghy' up with 'virtualbox' provider...
==> dinghy: Checking if box 'codekitchen/boot2docker' is up to date...
==> dinghy: Clearing any previously set forwarded ports...
==> dinghy: Fixed port collision for 2375 => 2375. Now on port 2200.
==> dinghy: Fixed port collision for 2376 => 2376. Now on port 2201.
==> dinghy: Fixed port collision for 22 => 2222. Now on port 2202.
==> dinghy: Clearing any previously set network interfaces...
==> dinghy: Preparing network interfaces based on configuration...
    dinghy: Adapter 1: nat
    dinghy: Adapter 2: hostonly
    dinghy: Adapter 3: hostonly
==> dinghy: Forwarding ports...
    dinghy: 2375 => 2200 (adapter 1)
    dinghy: 2376 => 2201 (adapter 1)
    dinghy: 22 => 2202 (adapter 1)
==> dinghy: Running 'pre-boot' VM customizations...
==> dinghy: Booting VM...
==> dinghy: Waiting for machine to boot. This may take a few minutes...
    dinghy: SSH address: <IP_ADDRESS>:2202
    dinghy: SSH username: docker
    dinghy: SSH auth method: private key
    dinghy: Warning: Connection timeout. Retrying...
==> dinghy: Machine booted and ready!
==> dinghy: Checking for guest additions in VM...
==> dinghy: Checking for host entries
==> dinghy: Configuring and enabling network interfaces...
==> dinghy: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> dinghy: to force provisioning. Provisioners marked to run always will still run.
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: private interface is eth2
==> dinghy: route: SIOCDELRT: No such process
==> dinghy: nameserver <IP_ADDRESS>
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: Preparing /Users/noah NFS mount
Starting NFS daemon, this will require sudo
Waiting for NFS daemon...
Mounting NFS /Users/noah
Writing /Users/noah/.dinghy/certs/key.pem
Writing /Users/noah/.dinghy/certs/ca.pem
Writing /Users/noah/.dinghy/certs/cert.pem
Starting the DNS daemon
Your environment variables are already set correctly.

╰─± docker version
Client version: 1.3.2
Client API version: 1.15
Go version (client): go1.3.3
Git commit (client): 39fa2fa
OS/Arch (client): darwin/amd64
2015/05/31 11:31:47 Get https://<IP_ADDRESS>:2376/v1.15/version: EOF

╰─± docker-compose ps
SSL error: [Errno 8] _ssl.c:507: EOF occurred in violation of protocol

I see two potential issues. One, you should upgrade your docker client, 1.3.2 is a pretty old version.
But probably the primary problem is the port conflict notices from Vagrant, Fixed port collision for 2375 => 2375. Now on port 2200 and the like. It appears that something else is already listening on ports 2375, 2376, and 2222 on your host machine. The first two are standard Docker ports, do you have another docker VM running with those ports bound on your host?
Ideally dinghy would be more flexible about what ports it uses, that'd be a great enhancement.

Thanks @codekitchen ! I got everything running.
Somehow I ended up with two docker client installations. I removed the old one so now I'm on 1.6.2.
I also made sure no other VMs were running in VirtualBox.
╰─± dinghy up --no-proxy
Bringing machine 'dinghy' up with 'virtualbox' provider...
==> dinghy: Checking if box 'codekitchen/boot2docker' is up to date...
==> dinghy: Clearing any previously set forwarded ports...
==> dinghy: Pruning invalid NFS exports. Administrator privileges will be required...
Password:
==> dinghy: Clearing any previously set network interfaces...
==> dinghy: Preparing network interfaces based on configuration...
    dinghy: Adapter 1: nat
    dinghy: Adapter 2: hostonly
    dinghy: Adapter 3: hostonly
==> dinghy: Forwarding ports...
    dinghy: 2375 => 2375 (adapter 1)
    dinghy: 2376 => 2376 (adapter 1)
    dinghy: 22 => 2222 (adapter 1)
==> dinghy: Running 'pre-boot' VM customizations...
==> dinghy: Booting VM...
==> dinghy: Waiting for machine to boot. This may take a few minutes...
    dinghy: SSH address: <IP_ADDRESS>:2222
    dinghy: SSH username: docker
    dinghy: SSH auth method: private key
    dinghy: Warning: Connection timeout. Retrying...
==> dinghy: Machine booted and ready!
==> dinghy: Checking for guest additions in VM...
==> dinghy: Checking for host entries
==> dinghy: Configuring and enabling network interfaces...
==> dinghy: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> dinghy: to force provisioning. Provisioners marked to run always will still run.
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: private interface is eth2
==> dinghy: route: SIOCDELRT: No such process
==> dinghy: nameserver <IP_ADDRESS>
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: Running provisioner: shell...
    dinghy: Running: inline script
==> dinghy: Preparing /Users/noah NFS mount
Starting NFS daemon, this will require sudo
Waiting for NFS daemon...
Mounting NFS /Users/noah
Writing /Users/noah/.dinghy/certs/key.pem
Writing /Users/noah/.dinghy/certs/ca.pem
Writing /Users/noah/.dinghy/certs/cert.pem
Starting the DNS daemon
Your environment variables are already set correctly.

╰─± docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 7c8fca2
OS/Arch (client): darwin/amd64
Server version: 1.6.0
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 4749651
OS/Arch (server): linux/amd64

Do I need to worry about route: SIOCDELRT: No such process ?

route: SIOCDELRT: No such process is caused by sudo /sbin/udhcpc > /dev/null on https://github.com/codekitchen/dinghy/blob/master/vagrant/Vagrantfile#L48.

Yeah, that's ok to ignore for now.


refactor: tracing for the whole request, including auth

Codecov Report

Merging #485 (0ae625c) into main (70593c4) will decrease coverage by 0.04%.
The diff coverage is 15.38%.

@@            Coverage Diff             @@
##             main     #485      +/-   ##
==========================================
- Coverage   30.21%   30.17%   -0.05%
==========================================
  Files          79       79
  Lines        9415     9458      +43
==========================================
+ Hits         2845     2854       +9
- Misses       6311     6346      +35
+ Partials      259      258       -1

Impacted Files
Coverage Δ

server/metrics/tracing.go
61.11% <0.00%> (-9.29%)
:arrow_down:

server/middleware/auth.go
33.92% <0.00%> (-0.94%)
:arrow_down:

server/middleware/middleware.go
0.00% <0.00%> (ø)

server/middleware/tracing.go
0.00% <0.00%> (ø)

server/metrics/requests.go
82.69% <38.46%> (-11.22%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


drivers/pipes: return after short write if buffer is full

Summary
The write should return even in case of O_NONBLOCK if at least some bytes were written.
The previous state where always all bytes were written was breaking a common combination with poll, because poll would signal POLLOUT and some bytes would really be consumed but write could still block afterwards. That would prevent from execution returning to the poll loop again.
None the less it is also the standard C library behavior for the write function.
Impact
This could have impack on any code that uses pipes and fifos and relies on this non-standard behavior or write always writing all bytes. But it is non-standard behavior and thus considered to be a bug in my eyes.
Testing
Tested with the following code that after this change works:
// Must be longer than CONFIG_DEV_PIPE_SIZE
const char *text =
        "Lorem ipsum odor amet, consectetuer adipiscing elit. Eget litora laoreet ornare elementum pellentesque class penatibus eleifend morbi. Conubia cras accumsan blandit at fames mauris varius. Nisl c
const size_t tlen = strlen(text);
printf("tlen %zd\n", tlen);
int fds[2];
assert(pipe2(fds, 0) == 0);
struct pollfd pfd[2] = {
        {
                .fd = fds[0],
                .events = POLLIN | POLLHUP,
        },
        {
                .fd = fds[1],
                .events = POLLOUT,
        },
};
size_t off = 0;
while (true) {
        if (poll(pfd, 2, -1) == -1) {
                printf("Poll fail %s\n", strerror(errno));
                exit(1);
        }
        if (pfd[1].revents & POLLOUT) {
                ssize_t wlen = write(fds[1], text + off, tlen - off);
                if (wlen < 0) {
                        printf("Write fail %s\n", strerror(errno));
                        exit(1);
                }
                printf("Written %zd\n", wlen);
                off += wlen;
                if (off >= tlen)
                        close(fds[1]);
                continue;
        }
        if (pfd[0].revents & POLLIN) {
                char buf[BUFSIZ];
                ssize_t rlen = read(fds[0], buf, BUFSIZ);
                if (rlen < 0) {
                        printf("Read fail %s\n", strerror(errno));
                        exit(1);
                }
                fwrite(buf, 1, rlen, stdout);
        }
        if (pfd[0].revents & POLLHUP) {
                putc('\n', stdout);
                exit(0);
        }
}

[Experimental Bot, please feedback here]
Yes, this PR appears to meet the NuttX requirements, although some sections could be more explicit.
Strengths:

Clear Summary: The summary explains the problem (blocking write with O_NONBLOCK when partial writes are possible), the solution (returning after a partial write), and the rationale (conforming to standard C library behavior and fixing the interaction with poll).
Impact Description:  The impact section identifies potential compatibility issues with code relying on the previous, non-standard behavior.
Test Case: Provides a concrete test case demonstrating the issue and its resolution. This is crucial for verifying the fix.

Areas for Improvement:

Impact Specificity: While the impact section mentions potential compatibility issues, it would be stronger with more details.  Which specific parts of NuttX or NuttX apps might be affected?  If none are known, explicitly stating that would be helpful.  The current phrasing "This could have impact..."  is vague.  Be more definitive if possible.
Testing Details: While the test code is provided,  the "Testing logs before change" and "Testing logs after change" sections are empty.  Include the actual output of the test program before and after the change.  This concretely demonstrates the fix's effect.  Also specify the Build Host and Target details as requested.
Impact on Documentation: If this change affects how write behaves with pipes/FIFOs, the documentation should be updated to reflect the new behavior.  The Impact section should specify whether documentation updates are included in the PR.
Impact on Security and Compatibility: While it's likely there are no security implications and backward compatibility is the main concern (already addressed), explicitly stating "NO" with a brief justification for security and a more detailed explanation for compatibility (e.g., "Backward compatibility may be affected for applications relying on the non-standard behavior...") would strengthen the PR.

Example of improved Testing Section:
## Testing

I confirm that changes are verified on local setup and works as intended:
* Build Host(s): Linux (Ubuntu 20.04), x86_64, GCC 9.4.0
* Target(s): sim:qemu-x86_64

Testing logs before change:

tlen 295
Written 65536
Poll fail Interrupted system call  <-- Demonstrates the blocking issue

Testing logs after change:

tlen 295
Written 65536
Written 229
Lorem ipsum odor amet, consectetuer adipiscing elit. Eget litora laoreet ornare elementum pellentesque class penatibus eleifend morbi. Conubia cras accumsan blandit at fames mauris varius. Nisl c

By making these improvements, the PR will be clearer, easier to review, and demonstrate a higher level of due diligence.

Sorry @Cynerd: CI Test in arm-02 is failing with Pipe Timeout, I wonder if it's due to this PR?
Configuration/Tool: sabre-6quad/citest,CONFIG_ARM_TOOLCHAIN_GNU_EABI
__________________________________ test_pipe ___________________________________
p = <utils.common.connectNuttx object at 0x7f35223[161](https://github.com/NuttX/nuttx/actions/runs/11713931118/job/32627704349#step:7:162)a0>
    def test_pipe(p):
        ret = p.sendCommand("pipe", "redirect_reader: Returning success", timeout=60)
>       assert ret == 0
E       assert -1 == 0
E         +-1
E         -0

/github/workspace/sources/nuttx/tools/ci/testrun/script/test_example/test_example.py:41: AssertionError
----------------------------- Captured stdout call -----------------------------
+------------------------------------------- Catch Exception -------------------------------------------+
+----------------------------------------------- Result ------------------------------------------------+
| Command     : 'pipe'                                                                                |
| Expect value: ['redirect_reader: Returning success']                                                  |
| Timeout     : 60s                                                                                |
| Test result : Timeout

https://github.com/NuttX/nuttx/actions/runs/11713931118/job/32627704349#step:7:174

Sorry @Cynerd: CI Test in arm-02 is failing with Pipe Timeout, I wonder if it's due to this PR?

It might be. I will look into that. I suspect that it is because of some invalid expectations for some components using the pipe. As I wrote in the "Impact": it might cause issues if code that uses pipecommon relies on write working in a non-standard way.

hello @Cynerd  there is a test failed in libuv [fs_partial_read] after this PR
https://github.com/libuv/libuv/blob/v1.x/test/test-fs.c#L3764
the result expect to be equal to nbytes （1000 which is less than the pipe buffer size 2048)
and i find this explanation about  write api  in https://pubs.opengroup.org/onlinepubs/9799919799/
`Complete/partial/deferred: A write request:
ret = write(fildes, buf, nbyte);
may return:
Complete
ret=nbyte
Partial
ret<nbyte
This shall never happen if nbyte<={PIPE_BUF}. If it does happen (with nbyte>{PIPE_BUF}), this volume of POSIX.1-2024 does not guarantee atomicity, even if ret<={PIPE_BUF}, because atomicity is guaranteed according to the amount requested, not the amount written.`
does this mean that if the nbytes < buffer_size, than the write should be block when the O_NONBLOCK flag is not set

hello @Cynerd there is a test failed in libuv [fs_partial_read] after this PR
https://github.com/libuv/libuv/blob/v1.x/test/test-fs.c#L3764 the result expect to be equal to nbytes （1000 which is less than the pipe buffer size 2048)
and i find this explanation about write api in https://pubs.opengroup.org/onlinepubs/9799919799/
`Complete/partial/deferred: A write request:
ret = write(fildes, buf, nbyte); may return:
Complete ret=nbyte Partial ret<nbyte This shall never happen if nbyte<={PIPE_BUF}. If it does happen (with nbyte>{PIPE_BUF}), this volume of POSIX.1-2024 does not guarantee atomicity, even if ret<={PIPE_BUF}, because atomicity is guaranteed according to the amount requested, not the amount written.`
does this mean that if the nbytes < buffer_size, than the write should be block when the O_NONBLOCK flag is not set

Yes, you are right. My change goes against POSIX for pipes and fifos. I even modified my test and run it on Linux and with sufficiently large buffer size it gets stuck as well:
  size_t tlen = 100000;
  char text[tlen];
  for (size_t i = 0; i < tlen; i++)
    text[i] = 'x';
  int fds[2];
  assert(pipe2(fds, 0) == 0);
  struct pollfd pfd[2] = {
      {
          .fd = fds[0],
          .events = POLLIN | POLLHUP,
      },
      {
          .fd = fds[1],
          .events = POLLOUT,
      },
  };
  size_t off = 0;
  while (true) {
    if (poll(pfd, 2, -1) == -1) {
      printf("Poll fail %s\n", strerror(errno));
      exit(1);
    }
    if (pfd[1].revents & POLLOUT) {
      ssize_t wlen = write(fds[1], text + off, tlen - off);
      if (wlen < 0) {
        printf("Write fail %s\n", strerror(errno));
        exit(1);
      }
      printf("Written %zd\n", wlen);
      off += wlen;
      if (off >= tlen)
        close(fds[1]);
      continue;
    }
    if (pfd[0].revents & POLLIN) {
      char buf[BUFSIZ];
      ssize_t rlen = read(fds[0], buf, BUFSIZ);
      if (rlen < 0) {
        printf("Read fail %s\n", strerror(errno));
        exit(1);
      }
      fwrite(buf, 1, rlen, stdout);
    }
    if (pfd[0].revents & POLLHUP) {
      putc('\n', stdout);
      exit(0);
    }
  }

I came to this from the socket (specifically local socket) side, and thus, I failed to check the POSIX specification for the pipe. Therefore, what is wrong here is not the behavior of pipe implementation but that unix local sockets are backed by them in NuttX.
Thus, this change should be reverted as well as "fix" in apps for pipe test, and fix must be instead at the socket level.

Could you please help revert these two patches first?  @Cynerd


Support more LMS

D2L
Blackboard
Google Classroom
Schoology
Moodle

Canvas is most popular in higher education, but only around 25-50% of the total market share.
Should these be separate extensions or part of this one?

I think the code is different enough for each LMS that they should be separate extensions.

For schoology: https://developers.schoology.com/api

Moodle has APIs but it looks like they are more for schools/university sys-admins
https://moodledev.io/docs/apis

Update: I want to focus on this more in the next few months, ideally starting with Gradescope integration then Blackboard. Gradescope because I have access to it already so it would be a nice test to see how much needs to change in the code, Blackboard because it's the most requested.

I don't know if Gradescope has an API but in my experience it's really easy to scrape.


Support for resource attributes

Hi,
it would be great if it was possible to properly parse files with nested JSON like is described here https://github.com/googlei18n/app-resource-bundle/wiki/ApplicationResourceBundleSpecification#resource-attributes

Sure. What would be a use case that you see?

Hi @long1eu
the simplest sample will be something like this:

"TUTORIAL": {
"TUT_ONE": {
"TITLE": "title 1",
"DESC": "desc 2"
},
"TUT_TWO": {
"TITLE": "title 2",
"DESC": "desc 2"
},
"TUT_THREE": {
"TITLE": "title 3",
"DESC": "desc 3"
},
...
},

Not sure you understood the attributes right. Those attributes are for just one attributes and not for nested resources. Not planning to add that anytime soon since it's out of arb scope. Let me know if you feel that I'm wrong.


Working example app in documentation

What problem does this feature solve?
One of the best things about the vue docs are working examples and the tutorial also provides working examples each step.
I found for me to understand vue router a working example would have helped a lot. I propose adding a tiny working example to the vue router docs.
I would be happy to contribute an extremely basic hello world application that showcases how to use the router.
What does the proposed API look like?
I think the ideal example would showcase a single page application home page on / and would have the components used there also available on their own routes such as /helloworld1 and /helloworld2

Let's track this at https://github.com/vuejs/router/issues/829
I think that using a simple project with vite might be a better option that the currently existing one with html files, I will share with the doc team.


Solidity linting

Add a linter for Solidity, as a script target in the package.json and to the husky hook, then the GitHub hook.
Candidates includes SolHint & EthHint.

Wired up with the sol linter working on CLI execution, however failing execution on pre-commit and GiHub action.
Lib has low npm usage and release over 6 months ago. Replace with Slither from eth-security-tools


Documentation of "prompt" field is conflicting with itself

It appears that select_account is a valid option for the prompt parameter in the auth code flow, however the page presently states the following in its description of the prompt field

The only valid values at this time are login, none, and consent.

Note that select_account is conspicuously missing from that sentence, but strangely further down it shows prompt=select_account is listed as a potential value. I suspect that this is an outcome of #71758 and whoever updated the documentation as a result of that issue forgot to add it to the list of valid options in the top part of the description.

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

ID: 13b44819-ed7b-84bc-f5d2-2b937029f7df
Version Independent ID: db9f8408-c234-90d0-4817-3516e5fc3ba0
Content: Microsoft identity platform and OAuth 2.0 authorization code flow - Microsoft identity platform
Content Source: articles/active-directory/develop/v2-oauth2-auth-code-flow.md
Service: active-directory
Sub-service: develop
GitHub Login: @hpsin
Microsoft Alias: hirsin

@benjamincburns Thanks for the feedback! We will review and update accordingly.

Apologies @hpsin, missed your question of why the first-try fix in https://github.com/MicrosoftDocs/azure-docs/issues/71758 didn't go through. Looks like we're good now, however, so will chalk it up to transient issue.
@benjamincburns I'm now seeing this on the live site, so closing this one out. If you feel this was closed in error, however, please do let me know. Thanks for the call-out on this! #please-close


email

hi barbosik, what is your email so I can contact you?

Barbosik quit this project.
Reporting comment to github.


Add support for outputing namespaces existing in the datahub.

add support for the command
mim namespaces

This is implemented with mim namespace ls


Fixed typo in IOS development roadmao

fixed typo in ios dev roadmap
Fixes Issue
#447
Screenshots

Please close this issue


the useragent is not matching my OS

from fake_useragent import UserAgent
ua = UserAgent(use_cache_server=False)
print(ua.chrome)
Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2227.0 Safari/537.36
(Windows NT 6.1; WOW64)  -->>  does not fit my system.
the  website can find out i'm using a fake useragent.
because he knows i am in windows 10 or linux

Would be cool if we could set a parameter like os="windows" to select the operating system. This parameter could default to the os that is running on the computer if it's not explicitly set by the user.

Fake user-agent by default just gets you a random user agent string (in this case a random chrome user-agent string). Which means it can also be another operating string like Linux.

Upgrade pip  install --upgrade fake-useragent to get the latest version. Which should now give you more up to date user agent strings.
Also you have the ability to set os="windows" now.

https://github.com/fake-useragent/fake-useragent/issues/96#issuecomment-1662862564

@melroy89, per

This parameter could default to the os that is running on the computer if it's not explicitly set by the user.

Does it?

You have the ability now to set the OS.
from fake_useragent import UserAgent
ua = UserAgent(os='windows')
ua.random

Since we don't have a lot of user agent strings, the default is still all OS's.


Production Environment Error: Cannot read properties of undefined (reading 'Graph')

Describe the bug / 问题描述
In DEV environment, everything is ok.
In PROD environmnet, Cannot read properties of undefined (reading 'Graph')
Reproduction link / 重现链接
No response
Steps to Reproduce the Bug or Issue / 重现步骤
Just vue3 + vite
import { Graph } from '@antv/g6'
G6 Version / G6 版本
🆕 5.x
Operating System / 操作系统
macOS
Browser / 浏览器
Chrome
Additional context / 补充说明
No response

vite 2.x version

I created a vue app and used G6, and the built product worked without the problem you described. You can provide more information.

I created a vue app and used G6, and the built product worked without the problem you described. You can provide more information.

I think it is caused by the lower version vite(2.6)

I created a vue app and used G6, and the built product worked without the problem you described. You can provide more information.

In vite 4.x version, everything is ok

Hello! May I ask what caused this?


Dead links in documentation

I stumbled across some dead links (at least at the moment?) in the documentation, in this part:
It is marker based. It supports a wide range of markers: multiple types of markers pattern/barcode multiple independent markers at the same time, or multiple markers acting as a single marker up to you to choose.

#163

Most of the interesting examples are dead (404) links still.

duplicate https://github.com/jeromeetienne/AR.js/issues/362


[Bug]: v3.1.2 doesn't work with local ollama

Opencommit Version
3.1.2
Node Version
20.6.1
NPM Version
10.5.0
What OS are you seeing the problem on?
Other Linux Distro
What happened?
I upgraded to the latest version with npm installation, and my configuration (which worked perfectly with the previous version) doesn't work anymore, I'm getting asked for openAI api key while I don't use their API
Expected Behavior
COmmit generation
Current Behavior
An error message is generated
Possible Solution
Please check if changes in env variables are needed.
If I downgrade to v3.0.20 it works again.
Steps to Reproduce
npm i -g opencommit@latest
oco
Relevant log output
◇  📝 Commit message generated
│
└  ✖ The OPENAI_API_KEY environment variable is missing or empty; either provide it, or instantiate the OpenAI client with an apiKey option, like new OpenAI({ apiKey: 'My API Key' }).

👁

what is your OCO_AI_PROVIDER var set to?

OCO_AI_PROVIDER='ollama/phi3.5:3.8b'

there was a change, you should now set OCO_AI_PROVIDER=ollama and OCO_MODEL=phi3.5:3.8b

THanks, I must have read the documentation better (or maybe give you time to write it :) )

i'm updating the docs, thank you <3


skeema: init at 1.7.0

Motivation for this change
Skeema is a pure-SQL schema management utility. Simply track your desired schema state in a repo of CREATE statements, and the tool figures out how to apply any changes to your tables and routines. You won't need to code migrations, use obscure DSLs, or write verbose XML ever again.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@aaronjheng I guess this needs a rebase now?

@humancalico Yes.

pinging @SuperSandro2000 for merge 🙈


Remove Cmd-K shortcut

Command-K is very widely used across the web (e.g. in Gmail, Google docs) to insert links. It took me a few minutes this morning to debug why this shortcut suddenly stopped working. Eventually I traced it back to Quick Tabs.
This is pretty disruptive to set by default.

Thanks @danvk, I was in two minds about mapping ctrl+J/K by default but couldn't see any key conflicts within Chrome itself (except to view the downloads page).  If Google is using ctrl+K I will leave the shortcuts unmapped to keep things simple/unobtrusive.

So, how do I bind a custom key to the extension now?

@mattsson you can map shortcut keys using the "Keyboard shortcuts" link at the bottom of the Chrome extensions settings page, mine looks like this:

The next/Previous tab options default to unset to avoid unexpected behaviors like the one described here.

Great, thanks! What an odd place to put that.

@babyman I just felt compelled to offer you my heartiest thanks.


Allow authors to override focus order for keyboard navigation

Depends on #1608.

This can now be closed: FocusTraversalPolicy subclasses implement custom policy, and DefaultFocusTraversal widgets place that policy in the tree.


VS Code Solidity extension: Highlight Only Uninitialized Immutable Variables and Constructor

In the Solidity extension, currently, when immutable state variables are not initialized, the entire contract is highlighted in red. This is not optimal for understanding the issue at hand. It would be more helpful if only the uninitialized immutable variables and the related constructor were highlighted.
Steps to Reproduce:

Declare an immutable state variable in a Solidity contract.
Create a constructor without initializing the immutable variable.

Expected: Highlighting of immutable variable and constructor to be have red squiggly lines.
Actual: Everything is red, making it hard to see which immutable variables are the problem.

(Can take this up is this is an actual issue!)

This is a great suggestion for an improvement.
What is happening is that that solc is giving an error (solc 2658). The range that solc is giving in the source code is the entire contract:

With the extension we can manipulate that source range so that it is limited to the constructor, more specifically just to the constructor keyword.
The way this would be implemented is by providing a new CompilerDiagnistic for 2658. This diagnostic would provide no code actions but transform the solc error by constraining the source range by implementing fromHardhatCompilerError, and constraining to the constructor keyword. You can see a similar move here:
https://github.com/NomicFoundation/hardhat-vscode/blob/12bb234327561fb1c6877a2ced5ea2f6fc324a45/server/src/compilerDiagnostics/diagnostics/ConstrainMutability.ts#L25

Thanks! I can implement this, but I'm not working extensively till end of week. Could you assign it to me so I can keep a tab on it and close it this weekend?

Hey @AbhinavMir I have assigned it to you. Thanks and good luck.


[FEATURE] Add events for charging station status change

Duplicate issue

[X] I've searched for any related issues and avoided creating a duplicate issue.

Description
Allow to take decision at charging station level on:

start
stop
connector status change
...

Attachments
No response

Add event emission in https://github.com/SAP/e-mobility-charging-stations-simulator/commit/f130b8e620e8808516bbf80bc4247c81fae02186 for ChargingStationWorkerMessageEvents.


Fix python 3 incompatibity on TermsFilter

Replace dict.iteritems() method by six.iteritems(dict) one.

Thanks for the patch, it works!


Bluetooth: BAP: Move TX guard to not cover verify funcs

Move the BT_AUDIO_TX guard so that it does not cover the verification functions for valid_codec and qos, as they are also relevant for receivers to verify what remote devices send.

Marked as bug as this give build errors in certain build configurations


Search bar responsive issues

Describe the bug
The search bar overflows after around 500px screen width
Screenshots

Noted on

Device: Pixel2 XL

Can I do this one?


Connection/Application state on disconnect/deleted connections don't get cleaned up

@aaomidi cool, makes sense.  We probably still have an issue of keeping connection details retained in the application state after connections are disconnected\deleted.  Though if there are no user facing bugs that seems like a lower-priority.  Thanks!

Originally posted by @kburtram in https://github.com/microsoft/azuredatastudio/pull/6560#issuecomment-518315949

Closing older engineering-focused bugs to prioritize customer scenario-facing bugs.  We can analyze connection internal state in perf testing for this area.


GUI for Snapchats Filter in a face image

A GUI webapp that can show some funny filters in real time along with a capture button.

@akshitagupta15june I want to work  on it, can you please assign me this.

@akshitagupta15june I want to work  on it, can you please assign me this.

@akshitagupta15june Can we start working on this isuue for GSSOC21 ?

Yes @Aayush-hub you can work on this.

can you elaborate this issue a little?


mongoc: 1.27.6 -> 1.28.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mongodb/mongo-c-driver/releases.
meta.description for mongoc is: Official C client library for MongoDB
meta.homepage for mongoc is: http://mongoc.org
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.28.0 with grep in /nix/store/var17mgf0xhsbdfy0p3n4a80a96arz8a-mongoc-1.28.0
found 1.28.0 in filename of file in /nix/store/var17mgf0xhsbdfy0p3n4a80a96arz8a-mongoc-1.28.0

Rebuild report (if merged into master) (click to expand)

8 total rebuild path(s)

8 package rebuild(s)

First fifty rebuilds by attrpath

collectd
libmongocrypt
mongoc
mongocxx
n8n
rsyslog
syslogng

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/var17mgf0xhsbdfy0p3n4a80a96arz8a-mongoc-1.28.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mongoc https://github.com/r-ryantm/nixpkgs/archive/d0c4de080649c0cae6be672bfe3d8c4cac688b5f.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d0c4de080649c0cae6be672bfe3d8c4cac688b5f#mongoc

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/var17mgf0xhsbdfy0p3n4a80a96arz8a-mongoc-1.28.0
ls -la /nix/store/var17mgf0xhsbdfy0p3n4a80a96arz8a-mongoc-1.28.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

8 packages built:

collectd
libmongocrypt
mongoc
mongocxx
n8n
rsyslog
syslogng
syslogng.man

Maintainer pings
cc @archer-65 for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 342953 run on x86_64-darwin 1

1 package marked as broken and skipped:

collectd

1 package failed to build:

n8n

2 packages built:

libmongocrypt
mongoc


Update create account form

as a user, I can create a Flow Testnet account
Notes:
Scope for this ticket is to update the account creation form - other page elements will be handled separately.
Should contain:

Public key

Label
Description (copy tbd)
Input field

Signature & hash algorithm

Label
Description (copy tbd)
Signature algorithm select. Options:

ECDSA_P256 (default)
ECDSA_secp256k1

Hash algorithm select. Options:

SHA2_256 (default)
SHA3_256

hCaptcha
Create new account button

Design:
Figma

confirmed this is no longer relevant, close it for now


Add support for external apidoc URLs for both Scala and Java projects.

We now support attaching external apidoc URL for both Scala and Java projects via explicit keys scalaApiMappings and javaApiMappings respectively.
The old key apiMappings is thus deprecated in favor of more explicitly named scalaApiMappings.
The new set POM properties preserving the apidoc URLs are info.scalaApiURL and info.javaApiURL for Scala apidoc and Java apidoc respectively.

Can one of the admins verify this patch?

Ok, so the ivy related code looks fine.  You may also need to hit here:
The POM reader in the sbt-eether-resolver plugin: https://github.com/sbt/sbt/blob/0.13/sbt-maven-resolver/src/main/java/org/apache/maven/repository/internal/SbtArtifactDescriptorReader.java#L274-L289
Then, after the POM properties are read into Aether, they are translated into Ivy Properties here:
https://github.com/sbt/sbt/blob/0.13/sbt-maven-resolver/src/main/scala/sbt/mavenint/MavenRepositoryResolver.scala#L146-L148
We need this path to work as well, as I expect at some point we may just stop relying on Ivy's maven-integration in favor of Aether handling its own mess.

@indrajitr We just had a discussion that opened some cans of worms here.  Besides Aether-integration, we kind of have to figure out what tools may be using info.apiURL before we remove it.   @eed3si9n has convinced me of the rightness of sticking with info.apiURL for scaladoc (and possibly adding info.javadocURL, for javadoc).
I wish we had done this in a cleaner fashion immediately.  Also, relating to info.apiURL, we should try to push this convention on thw hole maven ecosystem and all toolign aroudn maven artifacts.   Otherwise it's an obscure sbt feature.   Ideas here welcome.

@jsuereth wrote:

We do a survey of recently released scala libs and figure out the % which are actively using the apiURL feature. Given its low press, I'm assuming it's not heavily used yet.

Let's start from the most widely used OSS Scala library, which is named scala-library. Here's from scala-library-2.11.6.pom:
<properties>
<info.apiURL>http://www.scala-lang.org/api/2.11.6/</info.apiURL>
</properties>

I don't think we should now deprecate this. As it stands, this PR is not ready for 0.13.9.

I'll refresh the change shortly. Sorry about the radio silence.
I just need to squash my changes and update this request (for 0.13.10 maybe?).
Few points though:

Existing POMs are never in danger because the code was intended to always honor info.apiURL as fallback to info.scalaApiURL.
That said, I agree that the keeping info.apiURL around is safer.
So we should just have info.apiURL and info.javaApiURL (and have necessary comments in the code so that our future self remembers the decision).

Fair?

@indrajitr Are you still interested in this?


Release 0.4.0

Prerequisites

[x] Have at least Editor level access to quilkin Google Cloud project.
[x] Local gcloud configuration is pointing at the quilkin Google Cloud project.
[x] Local git remote upstream points at git@github.com:googleforgames/quilkin.git.

Steps

[x] Review that closed issues have appropriate tags for the changelog.
[x] Review that merged PRs have appropriate tags for the changelog.
[x] Run git remote update && git checkout main && git reset --hard upstream/main to ensure your code is in line
with upstream.
[x] Update Cargo version for release

[x] Edit the version field in ./Cargo.toml and remove the -dev suffix.
[x] Edit the quilkin-macros dependency in ./Cargo.toml and remove the -dev suffix.
[x] Edit the version field in ./macros/Cargo.toml and remove the -dev suffix.

[x] cd to ./build/release and run make to submit the cloud build
[x] Download all the artifacts from the cloud build.
[x] Move the CHANGELOG.md to the root of this repository, replacing any previous versions.
[x] Review license.html to ensure that there aren't any new MPL, or CDDL dependencies from the last
release. If there are:

[x] Add the dependencies to archive_dependencies.sh
so that the source is archived in the container image.
[x] Reset checklist back to "run make to submit the cloud build", and start from there again.

[x] Run cd macros && cargo publish --dry-run --allow-dirty and ensure there are no issues.
[x] Run cargo publish --dry-run --allow-dirty and ensure there are no issues.
[x] Add a release item to README.md "Documentation" > "Releases" list with related links in reverse chronological
order.
[x] Remove any data-proofer-ignore attributes from links in the documentation in ./docs.
[x] Submit these changes as a PR, and merge with approval.
[x] Create a Github release using the
Github release template.

[x] Populate the tag with v0.4.0, description, and relevant changelog sections.
[x] Attach all the remaining cloud build artifacts to the release.

[x] Run git remote update && git checkout main && git reset --hard upstream/main to ensure your code is in line
with upstream.
[x] Run git checkout -b release-0.4.0 && git push upstream release-0.4.0 to create a release branch.
[x] Publish to crates.io/crates/quilkin-macros: run cd macros && cargo publish
[x] Publish to crates.io/crates/quilkin: run cargo publish
[x] Submit the release.
[x] Post an announcement to the mailing list.
[ ] Post to the Twitter account.
[ ] Update Cargo version for development

[ ] Edit Cargo.toml and increment the minor version and apply the -dev suffix to the
version.
[ ] Edit the quilkin-macros dependency in ./Cargo.toml and increment the minor version
and apply the -dev suffix to the version.
[ ] Edit the version field in ./macros/Cargo.tomland increment the minor version
and apply the -dev suffix to the version.

[ ] Submit this change as a PR, and merge with approval.

Congratulation! 🎉 You have successfully released Quilkin!

Twitter post is scheduled for nice EU/AMER crossover time (~9am US Pacific / 7pm Helsinki)


Proxy latency metrics

Hello!
Are there any plans to add proxy latency metrics?
Basically I'd be interested in tracking the time it takes to route a particular request without taking into consideration how long the upstream took to reply.
Client -------> Gateway Proxying time -------> Upstream
Client <------- Gateway Proxying time <------- Upstream

See #12


Option to hover to view

The plugin is great but an option to hover over the text instead of selecting the text and using a shortcut key would be way more convinent.

@Riven53 I agree! Will implement that in a later release

Implemented in 0.1.0


Delete modal close button not working and cancel button working as delete

Steps to reproduce -

Go to scanpipe project details page "/project/<PROJECT_ID>"
Press delete/trash button below project name.
ISSUE 1 - Try closing modal using close button. It doesn't work.
ISSUE 2 - Press "No, Cancel". It deletes the project.

Issue fixed in this PR https://github.com/nexB/scancode.io/pull/115

@Sagarsangwan thanks for reporting those issues and for providing a PR. Much appreciated.
See https://github.com/nexB/scancode.io/commit/2b31db6c7bfc536d554b8fe8a0c5671e4f2180b4 for a solution that does not require inline JS.


Can't migrate with references on Postgres.

Precheck

Do not use the issues tracker for help or support requests (try Stack Overflow, IRC or mailing lists, etc).
For proposing a new feature, please start a discussion on elixir-ecto.
For bugs, do a quick search and make sure the bug has not yet been reported.
Finally, be nice and have fun!

Environment

Elixir v1.4.4
Ecto v2.1.4
PostgreSQL 9.4
Postgrex 0.13.2
Operating system: Arch GNU/Linux

Current behavior
Include code samples, errors and stacktraces if appropriate.
Currently refusing to create tables based on migrations. Unsure why.
Get this error message every time:
The database for WarnServ.DB.Repo has been dropped
The database for WarnServ.DB.Repo has been created

22:33:40.503 [info]  == Running WarnServ.DB.Repo.Migrations.CreateNicks.change/0 forward

22:33:40.503 [info]  create table nicks

22:33:40.519 [info]  == Migrated in 0.0s

22:33:40.565 [info]  == Running WarnServ.DB.Repo.Migrations.CreateChannels.change/0 forward

22:33:40.566 [info]  create table channels

22:33:40.575 [info]  == Migrated in 0.0s

22:33:40.600 [info]  == Running WarnServ.DB.Repo.Migrations.CreateReasons.change/0 forward

22:33:40.600 [info]  create table reasons

22:33:40.608 [info]  == Migrated in 0.0s

22:33:40.633 [info]  == Running WarnServ.DB.Repo.Migrations.CreateWarnings.change/0 forward

22:33:40.633 [info]  create table warnings
** (FunctionClauseError) no function clause matching in Keyword.get/3
    (elixir) lib/keyword.ex:150: Keyword.get(%Ecto.Migration.Reference{column: :id, name: nil, on_delete: :nothing, on_update: :nothing, table: :channels, type: :serial}, :size, nil)
    (ecto) lib/ecto/adapters/postgres/connection.ex:821: Ecto.Adapters.Postgres.Connection.column_type/2
    (ecto) lib/ecto/adapters/postgres/connection.ex:729: Ecto.Adapters.Postgres.Connection.column_definition/2
    (ecto) lib/ecto/adapters/postgres/connection.ex:904: Ecto.Adapters.Postgres.Connection.intersperse_map/4
    (ecto) lib/ecto/adapters/postgres/connection.ex:600: Ecto.Adapters.Postgres.Connection.execute_ddl/1
    (ecto) lib/ecto/adapters/postgres.ex:86: Ecto.Adapters.Postgres.execute_ddl/3
    (ecto) lib/ecto/migration/runner.ex:98: anonymous fn/2 in Ecto.Migration.Runner.flush/0
    (elixir) lib/enum.ex:1755: Enum."-reduce/3-lists^foldl/2-0-"/3

Code sample for table warnings:
defmodule WarnServ.DB.Repo.Migrations.CreateWarnings do
  use Ecto.Migration

  def change do
    create table(:warnings) do
      add :channel_id, :integer, references(:channels,
        on_delete: :nothing)

      add :nick_id, :integer, references(:nicks,
        on_delete: :nothing)

      add :reason_id, :integer, references(:reasons,
        on_delete: :nothing)

      add :warn_count, :integer

      add :active, :boolean
    end
  end

Same behavior every time.
Expected behavior
Expected Ecto to just create the tables, not do this current behavior.
Worth nothing, when I added a size: column, it proceeded further, but still crashed. Think that is not the solution. Shouldn't have to add a size: column, imho.
Thanks!

It should be:
add :channel_id, references(:channels, on_delete: :nothing)

We will make sure to raise better errors. Also please file proper titles when reporting issues, I am sure maintainers will appreciate it. 😅

Hi,
José Valim<EMAIL_ADDRESS>writes:

It should be:
add :channel_id, references(:channels, on_delete: :nothing)

Damn, I see. I had gone through all the docs, and saw nothing wrong at
first glance. I think I was having one of "those days" regarding
code. :smile:

We will make sure to raise better errors.

OK, sounds good. It did baffle me, but now you've shown me the fix,
it's obvious (to me) what the issue was. Thanks.

Also please file proper titles when reporting issues, I am sure
maintainers will appreciate it. 😅

So sorry about this. I filed this issue late at night (for me,
anyway), and I completely forgot to make a better title. Definitely
was not deliberate.
Will edit the title once I get an internet connection again; currently
on a train with very dodgy WiFi.
Many thanks for the quick response. Helped a lot, Jose.
--
Kind regards,
Dom Rodriguez (shymega/dzr{_,})
"Freedom is the freedom to say two plus two make four.
If that is granted, all else follows."
-- George Orwell, Nineteen Eighty-Four.


HDFS PERMISSION 777

@hwuu  This job running in a hadoop-run container which contains full hadoop-configuration.


Add files via upload

Upload for Educational License - Okinawa Christian School International

@tokiolabs Pull request merged. Thank you!


Fix incorrect reference in Queue

Fixes an issue I had when building amdvlk with clang 19:
/var/tmp/portage/media-libs/amdvlk-2024.3.3/work/pal/shared/devdriver/shared/legacy/inc/util/queue.h:371:25: error: no member named 'allocCb' in 'Queue<T, BlockSize, MinIndexCacheSize>'; did you mean 'm_allocCb'?
  371 |             : Queue(rhs.allocCb)
      |                         ^~~~~~~
      |                         m_allocCb
/var/tmp/portage/media-libs/amdvlk-2024.3.3/work/pal/shared/devdriver/shared/legacy/inc/util/queue.h:367:17: note: 'm_allocCb' declared here
  367 |         AllocCb m_allocCb;

Thanks for the fix!
This has been merged internally and should appear in one of the next releases (probably not the next one due to release cycles and changes taking time to propagate).


Append Host in Group

Hello
With the previous version of check_point_mgmt, we could append member to a group by using set-group command

check_point_mgmt:
  command: set-group
  parameters:
    name: MyHost_Group
      members:
        add:
        - MyHost_Name

And this currently seems impossible (add argument to members no longer recognized for check_point.mgmt.cp_mgmt_group), when we add one member in a group, all other members present before disappear.
Is it possible to fix this issue, please ?

Hi,
Thanks for reaching us.
Hi,
I will sum it up.
In the API in many "set" commands (e.g. set-group), when there is a parameter of type "list" (e.g. members) there are 4 options of value the list can get: add/remove/string/list:string
We intentionally removed the first three options because it damages one of Ansible requirements for idempotency.
But it's still possible to add/remove an element from list (members) by supplying the whole list with/except the elements you want to add/remove.
Thanks,
Or


[libremidi] Add new port

Fixes #20623

[X] Changes comply with the maintainer guide
[X] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[X] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx
[X] The versioning scheme in vcpkg.json matches what upstream says.
[X] The license declaration in vcpkg.json matches what upstream says.
[X] The installed as the "copyright" file matches what upstream says.
[X] The source code of the component installed comes from an authoritative source.
[X] The generated "usage text" is accurate. See adding-usage for context.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is in the new port's versions file.
[X] Only one version is added to each modified port's versions file.

Opened as draft for testing/comment

Usage test pass with following triplets:
x86-windows
x64-windows
x64-windows-static

yay ^-^

We accidentally merged this without verifying:

Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx

and the port breaks that rule:
## JACK support ##
if(NOT LIBREMIDI_NO_JACK)
  find_path(WEAKJACK_PATH weakjack/weak_libjack.h HINTS ${WEAKJACK_FOLDER})
  find_path(JACK_PATH jack/jack.h)
  if(WEAKJACK_PATH AND JACK_PATH)
    message(STATUS "libremidi: using WeakJACK")
    set(LIBREMIDI_HAS_JACK 1)

    target_include_directories(libremidi ${_public} $<BUILD_INTERFACE:${WEAKJACK_PATH}> $<BUILD_INTERFACE:${JACK_PATH}>)
  elseif(JACK_PATH)
    find_library(JACK_LIBRARIES jack)
    if(JACK_LIBRARIES)
      message(STATUS "libremidi: using linked JACK")
      set(LIBREMIDI_HAS_JACK 1)

      target_link_libraries(libremidi ${_public} ${JACK_LIBRARIES})
      target_include_directories(libremidi ${_public} $<BUILD_INTERFACE:${JACK_PATH}>)
    endif()
  endif()

  if(LIBREMIDI_HAS_JACK)
    target_compile_definitions(libremidi ${_public} LIBREMIDI_JACK)
  endif()
endif()

and as a result this port fails in CI because jack2 happened to be installed first.
I submitted https://github.com/microsoft/vcpkg/pull/34223 which should fix this.

I have commented on another issue but maybe this one is more relevant. The link to my comment is:
https://github.com/microsoft/vcpkg/issues/20623#issuecomment-1774173080


⚠ Bofrost.be has degraded performance

In 9137cc3, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1246 ms

Resolved: Bofrost.be performance has improved in 7e40728 after 20 minutes.


ssh_host keys present in manila image

The manila images (https://object-storage.public.mtl1.vexxhost.net/swift/v1/b98c5fdfb9be4e39a34b93d0b425ac2b/atmosphere-images/) contain matching ssh_host private and public keys in /etc/ssh. The keys appear to belong to root@fv-az551-124.

Opening issue in atmosphere repo instead.


Documentation lacks type for TaskRequest::setTaskVariables parameter

The documentation says "mixed".
So what do I have to set?

An instance of VariableInstance?
An array of variable Instances?
An associative array with the variable name as key and VariableInstance as value?
An associative array with the variable name as key and Variable as Value?

Nothing seems to work so far.

Okay, seems like I was looking for variables, not taskVariables.
But if somebody is wondering: It's an associative array with key, value pairs.


[non-substantive] Clarify genesis finalized checkpoint root

https://github.com/ethereum/eth2.0-specs/pull/1867

non-substantive, no code change

We aren't/weren't actually doing this. This should be merged to master, to conform asap.

Fixed with #1102


Add support for torch FP8 dtypes

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
This PR fixes #254 and adds native thunder support for the following dtypes:
torch.float8_e5m2
torch.float8_e5m2fnuz
torch.float8_e4m3fn
torch.float8_e4m3fnuz

Since the float8 dtype is implemented in 4 different variants I added  the variant mechanism for Thunder dtypes such that we can differentiate between them.
This PR also adds the option to create test fp8 tensors with make_tensor so that we can start testing fp8 operations. After running the existing operators tests it is evident that the support for this dtype in torch is scarce since the majority of tests fail with "not implemented" runtime errors. With that I decided to skip the operator testing for all the fp8.
Furthermore, I updated the type promotion table, please get a look and don't hesitate to comment if you think some promotions are not in the right place.
Did you have fun?
Oh yes!

Thanks everybody for your comments! I though about it a bit and I mainly agree with your points, the support for this dtype in torch is so low that I agree with you, we should delay the type promotion.
Regarding the tests, I also had the idea to disable them from the start but I didn't realize how ugly the pytest.skip everywhere ended up looking. I introduce the float_math_dtypes set of floating datatypes so that it is possible to @instantiate the test with only the floating dtypes that are worth testing for now.

Thank you @riccardofelluga @crcrpar @kshitij12345 @mruberry @lantiga


Support Spring 5 and Spring Boot 2

@whiskeysierra
Are there any remaining tasks?

It might work already. Did you give it a try?
On Mon, Mar 26, 2018, 06:41 wreulicke<EMAIL_ADDRESS>wrote:

@whiskeysierra https://github.com/whiskeysierra
Are there any remaining tasks?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zalando/logbook/issues/194#issuecomment-376044527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAaPnf1ahPw5wNBsKACnBWNXvbD250dtks5tiHFogaJpZM4RcYFg
.

It might work already. Did you give it a try?

I did not try. I will try it.

It worked for me.
spring boot 2.0.1

Sounds like we need to update some docs.

He migrado mi aplicación a Spring Boot 2.0.2-RELEASE y ahora al tratar de arrancar el servicio me lanza un error:
java.lang.NoClassDefFoundError: org/springframework/boot/bind/RelaxedPropertyResolver 	at org.springframework.boot.autoconfigure.AutoConfigurationImportSelector.getExcludeAutoConfigurationsProperty(AutoConfigurationImportSelector.java:215) 	at org.springframework.boot.autoconfigure.AutoConfigurationImportSelector.getExclusions(AutoConfigurationImportSelector.java:209) 	at org.springframework.boot.autoconfigure.AutoConfigurationImportSelector.selectImports(AutoConfigurationImportSelector.java:99) 	at org.springframework.context.annotation.ConfigurationClassParser$DefaultDeferredImportSelectorGroup.process(ConfigurationClassParser.java:841) 	at org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGrouping.getImports(ConfigurationClassParser.java:827) 	at org.springframework.context.annotation.ConfigurationClassParser.processDeferredImportSelectors(ConfigurationClassParser.java:560) 	at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:188) 	at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:316) 	at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:233) 	at
If I comment the logbook-spring-boot-starter from the pom.xml the service starts normally.
I'm using logbook version 1.7.3

@atrujillofalcon Is that the full stacktrace?

@whiskeysierra I've realized the cause of the issue. When I import the logbook-spring-boot-starter Maven automatically includes in the classpath the org.springframework.boot:spring-boot-autoconfigure:1.5.10.RELEASE dependency (wrong version, clash with new SB2 autoconfigure dependency).
I've been able to fix it adding a Maven exclusion, but it's just a workaround:
<dependency>             <groupId>org.zalando</groupId>             <artifactId>logbook-spring-boot-starter</artifactId>             <version>1.7.3</version>             <exclusions>                 <!--logbook spring-boot-autoconfigure exclude wrong version-->                 <exclusion>                     <groupId>org.springframework.boot</groupId>                     <artifactId>spring-boot-autoconfigure</artifactId>                 </exclusion>             </exclusions>         </dependency>

I'm preparing a pull request as we speak in order to set the scope to provided. That should solve it.

Thanks @whiskeysierra . I will keep the exclusion until the next version that includes this fix is released.


add delete to the multiple box check actions..

why cant we delete multiple hosts at the same time?
Thanks!!!

@joshzitting you should be able to delete multiple clients from the clients index.
But I agree, is would be nice to be able to delete multiple clients from the events index.


LinkPreview content lingers when mouse is no longer hovering over trigger

Describe the bug
If I quickly drag my mouse over many LinkPreview.Trigger components, then all of the "touched" triggers will display their LinkPreview.Content, even though my mouse is no longer hovering over the triggers.
Related issue
Reproduction
https://stackblitz.com/edit/github-bnmjm7-p2msgy?file=src%2Froutes%2F%2Bpage.svelte
Logs
No response
System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @sveltejs/kit: ^2.5.27 => 2.7.7
    bits-ui: 1.0.0-next.45 => 1.0.0-next.45
    svelte: ^5.0.0 => 5.1.10

Severity
blocking an upgrade

Thanks for creating this issue with a great reproduction. Digging into this now.

Alright I definitely see what is going on, just trying to work on a clean solution to the problem. Since we have a delay on the open and a delay on the close, moving your pointer in and out really quick triggers the open timeout which seems to not be cleared before the close timeout kicks off which is an issue.


--publish-service not available in docker run

Hi, started the two hosts setup with the Vagrantfile:
$ docker info
Containers: 1
Images: 4
Server Version: 1.9.0-dev
Storage Driver: aufs
Root Dir: /var/lib/docker/0.0/aufs
Backing Filesystem: extfs
Dirs: 6
Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.19.0-30-generic
Operating System: Ubuntu 15.04
CPUs: 1
Total Memory: 993.1 MiB
Name: vagrant-ubuntu-vivid-64
ID: UHQQ:GZSM:CVCL:2T56:COG3:WYSM:MRFJ:LORJ:INI3:UZI3:X4PR:CGS6
WARNING: No swap limit support
Experimental: true
Cluster store: consul://<IP_ADDRESS>:8500
vagrant@vagrant-ubuntu-vivid-64:~$ docker version
Client:
Version:      1.9.0-dev
API version:  1.22
Go version:   go1.4.3
Git commit:   add0d25
Built:        Thu Oct 15 18:08:18 UTC 2015
OS/Arch:      linux/amd64
Experimental: true
Server:
Version:      1.9.0-dev
API version:  1.22
Go version:   go1.4.3
Git commit:   add0d25
Built:        Thu Oct 15 18:08:18 UTC 2015
OS/Arch:      linux/amd64
Experimental: true
vagrant@vagrant-ubuntu-vivid-64:~$
I can create a network but not a service:
$ docker service ls
docker: 'service' is not a docker command.
See 'docker --help'.
$ docker network ls
NETWORK ID          NAME                DRIVER
928f84a7058d        foobar              overlay
a56ba30d9d19        bridge              bridge
f399ecb48df2        none                null
44031322c1ed        host                host
$ docker run -ti --publish-service=foo.foobar ubuntu:14.04
flag provided but not defined: --publish-service
See 'docker run --help'.
So there seems to be a few things out of sync.

docker --help does not list network or service as commands
docker run --net can be used to attach a container to a network from lib network but I did not see clear docs around this.
And --publish-service does not seem to be available anymore

Or I am missing something :)

--publish-service is an experimental UX and have been removed. you can take a look at https://github.com/docker/docker/pull/16645

Replaced experimental --publish-service with --net=

@sebgoa It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

For a bug: do you still experience the issue with the latest version?
For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to https://github.com/docker/libnetwork/issues/1926


Adding documents you’ll need list to Start page

Addresses #332
This tells users they'll need their vehicle registration number and other documentation – UR showed people wanted to know upfront what they would need.

I still prefer the box suggestion, this would look like the summary box on the payment screen (screenshot at bottom of this pull request). I don't see that it would be used wrongly any more than any other element of the prototype?
Sanjay would need to put in the localisation rule that V5C only shows when required by council.
The page is now long and includes some repetition. I have more concise content for the page in my CD review
However as with concessionary travel #458 the info on this page may be absorbed better by users if split into 2 pages, with About this service (retitled About your application in CD review) on the next page, as users have shown us they don't like to read too much on one page.

Before

After

Box design example

How we could use it

@lizziebruce Looks like this PR is also covered by #512?

@sanjaypoyzer Yes, correct. This was also a faster fix for if the more complex changes in 512 didn't get through in time for user testing on Monday.


Adding BUFFER_TIME for ORC multifile cloud reader

Closes #9210
BUFFER_TIME wasn't being logged for the multifile ORC reader path so it caused confusion with readFsTime > bufferTime

build

Closing as issue is not with BUFFER_TIME but with READ_FS_TIME and WRITE_BUFFER_TIME metrics being inside a thread context.   I'll file a separate PR to track those fixes.


Blocking Legacy Auth

I don't see any policies for blocking legacy auth. Is there a reason that this is was not included?

It's included in all policy sets, however split up:

300 -  - Attack surface reduction - All apps: Block access When using other clients
301 -  - Attack surface reduction - All apps: Block access When using active sync

This allows you to block a first subset of legacy authN while you are working on the other

Awesome, thanks, I totally missed that.


ng serve not detecting file changes

Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
Yes
Description
Generate a brand new project ng new project
Select scss and all other defaults
run npm start
any changes 4.a change *.ts 4.b change *.html 4.c change *.css
save file
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
No response
Anything else?
No response

Can you please provide the output of ng version

Angular CLI: 17.0.0
Node: 20.9.0
Package Manager: npm 10.1.0
OS: win32 x64
Angular:
...
Package                      Version
@angular-devkit/architect    0.1700.0 (cli-only)
@angular-devkit/core         17.0.0 (cli-only)
@angular-devkit/schematics   17.0.0 (cli-only)
@schematics/angular          17.0.0 (cli-only)
Ruslan Katz
пт, 10 нояб. 2023 г. в 16:46, Alan Agius @.***>:

Can you please provide the output of ng version
—
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/26325#issuecomment-1805873709,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRSPWW7INZO7BFLA2IMFUTYDY425AVCNFSM6AAAAAA7GIYNAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVHA3TGNZQHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

We're also seeing this from migrating to @angular-devkit/build-angular:application.
Interestingly the dev server is picking up changes to ts and scss but completely ignores html.

The dev server isn't picking up changes to ts, html and scss at all.
Do you have some solution?
Ruslan Katz
пт, 10 нояб. 2023 г. в 17:38, Michael Guay @.***>:

We're also seeing this from migrating to
@angular-devkit/build-angular:application.
Interestingly the dev server is picking up changes to ts and scss but
completely ignores html.
—
Reply to this email directly, view it on GitHub
https://github.com/angular/angular-cli/issues/26325#issuecomment-1805957369,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJRSPWS3TKZQGEU5ZBMR3ZTYDZC6RAVCNFSM6AAAAAA7GIYNAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBVHE2TOMZWHE
.
You are receiving this because you authored the thread.Message ID:
@.***>

cannot confirm 100%. watch and reload works for me on apple silicon with node 20.9 and<EMAIL_ADDRESS>

but does not recover from error after fix and save for (s)css files.
broke scss, saved, fixed, saved,... will not recover from error

I am also facing the same issue, it sometimes work and sometimes it doesn't. Most of the times it detect changes a few times and then suddenly stops deteting the changes.

BUT it seems not to recover from broken scss (angular-sass) code

This is exactly what I'm experiencing as well. Changes to .scss files are compiled by the CLI successfully and loaded correctly in the browser until there's a compilation error. Once you fix that compilation error in the file, the CLI continues to report a compilation error.

Confirm the same issue

In my case, a similar problem began to occur after migrating to application builder (it was fine while using webpack). It turned out that the server did not detect file changes when the source directory name started with a dot (.). Changing the folder name so that it does not start with a dot solved the problem for me


Enabling this will ignore any other width settings and set the width of the video to the width of the container it's in.
Default Width:
640
Height:
360
I want to Constrain Vertical videos to default aspect ratio.
But I can't do. Please, somebody help me do this.
Create a sample code via:
[fluid-player-extended
vast_file="vast.xml"
layout="default"
auto-play="true"
allow-download="true"
playback-speed-control="true"
poster-image="https://www.fluidplayer.com/images/valerian-thumbnail.jpg"

logo="https://www.fluidplayer.com/images/yourlogo.png"
logo-position="top right"
logo-opacity=".8"
logo-hyperlink="https://www.fluidplayer.com/"

ad-text="adText"
ad-cta-text="adCTAText"

html-on-pause-block-width="100"
html-on-pause-block-height="100"

responsive="true"]

[fluid-player-multi-res-video]
    [
        {"label": "720", "url": "https://cdn.fluidplayer.com/videos/valerian-720p.mkv"},
        {"label": "480", "url": "https://cdn.fluidplayer.com/videos/valerian-480p.mkv"}
    ]
[/fluid-player-multi-res-video]

[fluid-player-html-block]

[/fluid-player-html-block]

[/fluid-player-extended]
How can I add Vertical Videos into this Code?
How can Constrain Vertical videos to default aspect ratio?
Because when I add a 568x320 video, it opens on a page 3 times the size of the Video Player.
HELP ME!

Hi,
You can pass CSS property object-fit: fill to the player, then the video view will occupy full height and width of player
have created an example in codepen 'https://codepen.io/bharath-exads/pen/Bgdjer' please check and let me know if this helps


Fix a couple problems with Jupyter protocol compliance

Fix handling of ZMQ identities in message parsing. mit-scheme-kernel previously assumed there was exactly 1 ZMQ identity; in fact there can be zero or more. See here.

Remove the payload field from execute_reply, since it was being encoded incorrectly anyway (as {} instead of []) and it's deprecated. Here's what the Jupyter spec says:

# 'payload' will be a list of payload dicts, and is optional.
# payloads are considered deprecated.

🎉 thanks for this!


Turtle Clock

Description
A simple Analog Clock made with Python Turtle
Type of issue

[x] Feature (New Script)

Checklist:

[x] I have read the project guidelines.
[x] I have checked all the existing projects, before submitting a new project issue.
[x] I have checked previous issues to avoid duplicates.
[x] This issue will be meaningful for the project.

@ADV1K  Please don't clear the Issue or PR template from next time

can I submit my pull request on this topic?

can I submit my pull request on this topic?

No, this issue has been claimed


update saas template to use serviceAccount reference for pullSecrets

this is needed for dsaas+osd4 compatibility, same thing as https://github.com/fabric8-launcher/launcher-application/pull/1025
@inoxx03 / @quintesse ptal! thanks.

compliments https://github.com/fabric8-launcher/launcher-application/pull/1025


NestedField from FieldSet.from_nemo

Hello
I'm testing OceanParcels' NestedField function as I have two fields with different resolutions from a FieldSet.from_nemo field. Until now, when I run the code with the structure suggested in the function, it does not recognize the second field when loading the nestings in U and V, but it does not give me any errors either.
This is the structure I am following:
Field 1
mfpathu = 'E:/MAESTRIA/DATOS/U/'
mfpathv = 'E:/MAESTRIA/DATOS/V/'
mfpathd = 'E:/MAESTRIA/DATOS/Domain/1_domain_cfg.nc'
mfufiles = (mfpathu + '1_CARIB_1h_20090101_20090131_grid_U.nc')
mfvfiles = (mfpathv + '1_CARIB_1h_20090101_20090131_grid_V.nc')
mffilenames = {'U': {'lon': mfpathd,'lat': mfpathd,'data': mfufiles},
'V': {'lon': mfpathd,'lat': mfpathd,'data': mfvfiles}}
mfvariables = {'U': 'uo', 'V': 'vo'}
mfdimensions = {'lat': 'gphif','lon': 'glamf','time': 'time_counter'}
mffieldset = FieldSet.from_nemo(mffilenames, mfvariables, mfdimensions, allow_time_extrapolation=False)
Field 2
mgpathu = 'E:/MAESTRIA/DATOS/MallaGrande/'
mgpathv = 'E:/MAESTRIA/DATOS/MallaGrande/'
mgpathd = 'E:/MAESTRIA/DATOS/MallaGrande/domain_cfg.nc'
mgufiles = (mgpathu + 'CARIB_1h_20090101_20090131_grid_U.nc')
mgvfiles = (mgpathv + 'CARIB_1h_20090101_20090131_grid_V.nc')
mgfilenames = {'U': {'lon': mgpathd,'lat': mgpathd,'data': mgufiles},
'V': {'lon': mgpathd,'lat': mgpathd,'data': mgvfiles}}
mgvariables = {'U': 'uo', 'V': 'vo'}
mgdimensions = {'lat': 'gphif','lon': 'glamf','time': 'time_counter'}
mgfieldset = FieldSet.from_nemo(mgfilenames, mgvariables, mgdimensions, allow_time_extrapolation=False)
U = NestedField('U', [mffieldset.U, mgfieldset.U])
V = NestedField('V', [mffieldset.V, mgfieldset.V])
fieldset = FieldSet(U, V)
Why could it not read the second field? I've noticed that when I reverse the fields in NestedField for U and V, it still doesn't recognize the second input field.
Greetings

Dear @pablohs27, thanks for asking this question. And also good that you posted some code. But in order to help, I'd need to understand better what you mean with 'read the second field'. What behaviour do you see, and what did you expect? Please be as specific as possible, otherwise it'll be very difficult for me to find out what's going wrong

Thank you Dr. Erick for your response.
I'm specifically referring to the following part of the code:
U = NestedField('U', [mffieldset.U, mgfieldset.U])
V = NestedField('V', [mffieldset.V, mgfieldset.V])
When I load the velocities in U and V for both fields.
"mffieldset" is my field 1 (with a higher resolution) and "mgfieldset" is my field 2.
The code works but when I plot the trajectories of the particles, only the trajectories of field 1 entered in the NestedField function appear.
I expect my particles to go from my field 1 to my field 2. But field 2 is not recognized.

Thanks for this extra information, but it's not really what I meant. To be able to help you, I would need a minimal reproducible example. So provide the full code, the full output etc.

This the full code:
`
from parcels import FieldSet, ParticleSet, JITParticle, ParticleFile, plotTrajectoriesFile, ErrorCode, AdvectionRK4, Field, NestedField
from argparse import ArgumentParser
import numpy as np
import pytest
from glob import glob
from datetime import timedelta as delta
from os import path
import time
from netCDF4 import Dataset
import xarray as xr
import cartopy
import matplotlib.pyplot as plt
Field 1
mfpathu = 'E:/MAESTRIA/DATOS/U/'
mfpathv = 'E:/MAESTRIA/DATOS/V/'
mfpathd = 'E:/MAESTRIA/DATOS/Domain/1_domain_cfg.nc'
mfufiles = (mfpathu + '1_CARIB_1h_20090101_20090131_grid_U.nc')
mfvfiles = (mfpathv + '1_CARIB_1h_20090101_20090131_grid_V.nc')
mffilenames = {'U': {'lon': mfpathd,'lat': mfpathd,'data': mfufiles},
'V': {'lon': mfpathd,'lat': mfpathd,'data': mfvfiles}}
mfvariables = {'U': 'uo', 'V': 'vo'}
mfdimensions = {'lat': 'gphif','lon': 'glamf','time': 'time_counter'}
mffieldset = FieldSet.from_nemo(mffilenames, mfvariables, mfdimensions)
Field 2
mgpathu = 'E:/MAESTRIA/DATOS/MallaGrande/'
mgpathv = 'E:/MAESTRIA/DATOS/MallaGrande/'
mgpathd = 'E:/MAESTRIA/DATOS/MallaGrande/domain_cfg.nc'
mgufiles = (mgpathu + 'CARIB_1h_20090101_20090131_grid_U.nc')
mgvfiles = (mgpathv + 'CARIB_1h_20090101_20090131_grid_V.nc')
mgfilenames = {'U': {'lon': mgpathd,'lat': mgpathd,'data': mgufiles},
'V': {'lon': mgpathd,'lat': mgpathd,'data': mgvfiles}}
mgvariables = {'U': 'uo', 'V': 'vo'}
mgdimensions = {'lat': 'gphif','lon': 'glamf','time': 'time_counter'}
mgfieldset = FieldSet.from_nemo(mgfilenames, mgvariables, mgdimensions)
U = NestedField('U', [mffieldset.U, mgfieldset.U])
V = NestedField('V', [mffieldset.V, mgfieldset.V])
fieldset = FieldSet(U, V)
pset = ParticleSet(fieldset, pclass=JITParticle, lon=[-93.33], lat=[18.51])
output_file = pset.ParticleFile(
name="27NFTT.zarr", outputdt=7200)
pset.execute(AdvectionRK4, runtime=1728000, dt=600, output_file=output_file)
ds = xr.open_zarr("27NFTT.zarr")
plt.plot(ds.lon.T, ds.lat.T, ".-")
plt.show()`
And this is the output when plot trajectories:

Although the code runs and doesn't give me any errors. The straight line shows the edge of field 1, so the trajectory does not pass into field 2

OK, this helps a bit but I still don't know how to replicate this. I don't know what your velocity feels are like, where they come from, what their domains are, how the grids are defined etc.
I'm sorry, but you need to provide me with a version that I can run myself; otherwise I can't help.


When an APP must display ATT modal?

Hello all,
I have an application that does not show ads, but we want to promote this app using the ad campaigns.
Our partner asked us about the ATT and SKAdNetwork implementation inside our app, but right now we do not do that.
The only tracking we have is google analytics for internal usage, not sharing with ad networks.
My question is, if I dont have ad inside the app, should I add ATT just to promote my app using ads?
I know that this is not an issue about the module, but like me, someone else maybe is with the exactly same doubts and we can improve the README with this information =)
Thanks for the help =)

Hi,
In summary, if your app or any client-side SDK/library within your app requires access to the IDFA (Identifier for Advertisers), you need to request App Tracking Transparency (ATT) permission. Without this permission, the default IDFA will be all zeroes and will not be usable for tracking the user or device.

Hey @deniza , thanks a lot to asnwer that.
That is clear now... =)
Thanks for this great plugin =)


Method injection call handler not being released

We are attempting to upgrade from Unity 2x to Unity 5.8.11.  Everything appears to be working except that the memory allocated for CallHandlers associated with a class that uses a TransientLifetimeManager is not be released by Unity.
I have tried registering the class two different ways with the same result:

Could it me the same issue?

I'm not sure why the message posted before I was finished.  I will continue here:
I registered the class in two different ways:
_unityContainer.RegisterType<ISystemPreferenceRepository, SystemPreferenceRepository>(
new Interceptor(),
new InterceptionBehavior());
or
_unityContainer.RegisterType(
new Interceptor(),
new InterceptionBehavior());
_unityContainer.RegisterType<ISystemPreferenceRepository, SystemPreferenceRepository>();
It didn't have any impact on it.
Here is an example of a method causing the problem.
[Memoization(ConfigurationName = LruCachingKeys.PerProcess)]
public virtual SystemPreference GetSystemPreference(string name, bool ignoreMemoization = false)
I have tested it by repeatably calling
var rep1 = _unityContainer.Resolve();
var rec1 = rep1.GetSystemPreference("Current Year");
I can put a breakpoint on the destructor of the MemoizationCallHandler and then execute
GC.Collect();
GC.WaitForPendingFinalizers();
In Unity 2x, the breakpoints on the call handler will be hit, indicating it is being freed.  In 5x, they are not being hit.
If I dispose of the UnityContainer in 5x, then the breakpoints are being hit, indicating that it is Unity that is holding a reference to the call handlers.
We have a long running process that typically runs about 8 hours, with a significant number of calls to a variety of repositories, many have which have call handlers associated with them.  With the upgrade to 5x, the server ran very low on memory and it took over 26 hours to complete.
We have the source code to 5.8.11 but have been unable to determine where the reference to the call handler is being stored.   Any help would be greatly appreciated.   The upgrade to 5x significantly improved performance in resolving objects, but the memory loss has made it unusable for us.

Unfortunately that did not work.  I upgraded to 5.8.13 and am still getting the same results.  The call handlers do not appear to be releasing until I dispose of the UnityContainer.  I'm testing this in our full application, but I can try to put together a small test app to get to you.

Please do, otherwise I would have no idea what is wrong.

I am attaching a zip file with two projects in it - one for 5.8.13 and one using the old Unity 2x.   I create three instances of the repository class that has a call handler based attribute.  After that I run the garbage collector to see what is being released.   In the 2x version, you can see that the MemoizationCallHandler is being released at the same time as the TestRepository class.  However, in the 5x version, you can see that the MemoizationCallHandler is not being released until the UnityContainer is disposed.  For some reason in 2x there appear to be 2 instances of the MemoizationCallHandler for each TestRepository,
Unity 2x

Unity 5.8.13

Please let me know if you need anything else from me on this.  Thank you.
TestCallHandlers.zip


MM-24693 Add since query param to the getGroups api request

Summary
In the websocket reconnect function on the Mattermost Mobile repo, we need to implement logic to get groups "since" the last time we had disconnected. The get groups will return us groups that have been created, updated, deleted since the last time we disconnected and we will need to update our redux state accordingly.
Ticket Link
https://mattermost.atlassian.net/browse/MM-24693
Checklist

[x] Add "since" query param on reconnect

Device Information
This PR was tested on: iPhone 11, iOS 14.4 Simulator

@anurag6713 what's with this PR? does this belong to 1.43?
cc: @amyblais

@enahum I found an issue while testing some use cases and that's why I still haven't merged it. I will confirm them and get this merged soon.

/update-branch

@anurag6713 please add release notes so we can merge this


PIE794 false positive when mutating class variable. Also leads to a bad fix.

class Person:
    name = "Foo"
    name = name + " Bar"

with unsafe fixes applied becomes:
class Person:
    name = "Foo"

It may not be the cleanest way of writing that, but it probably shouldn't trigger.
class Person:
    names = ["Foo"]
    names = names + ["Bar"]

is a use case I've actually seen in real code that probably should not be flagged.
ruff version is 0.1.4.

making it do += seems to be a decent mitigation for the objects which define it, but that may not always be an option depending on the Python object.


Extend the selector list

The list of online objects needs to be extended to

contain a "delete" button to delete the Altspace item entirely
(later) contain an "edit" button to edit the Altspace item's metadata
contain an indication of the Unity Asset's state (unconfigured, missing, present)

Need to modularize the selector list to avoid duplicate code. Build the selector list to use AltVRListItem in general.

Asset state indicator tests out OK.


simp usually reduces Fin n literals, but not n itself

Very conveniently, simp knows about Fin n literals, and reduces them mod n:
example (n : Fin 25) (P : Fin 25 → Prop): P (26) := by
  simp
  guard_target = P 1

It does not do that for n itself, though:
/-- error: simp made no progress -/
#guard_msgs in
example (n : Fin 25) (P : Fin 25 → Prop): P (25) := by
  simp

I expect this to simplify to P 0.
Note that it also doesn't change 0 to n:
/-- error: simp made no progress -/
#guard_msgs in
example (n : Fin 25) (P : Fin 25 → Prop): P 0 := by
  simp

It would be desirable if simp would consistently reduce all Fin n literals (with concrete n) modulo n.
This came up in the equational_theories project.
Versions
"4.12.0-nightly-2024-10-03"

Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

Out of curiosity, would a similar fix to this one be appropriate for https://leanprover.zulipchat.com/#narrow/channel/270676-lean4/topic/simproc.20for.20Fin as well? Or are the fixes there the correct way to proceed

I'm not an expert on the API design here.  I'd say that whenever a simp rule works it should be used over a simproc. I'm not sure about the conclusion of that thread - did someone find a simp lemma that works?

I'd say that whenever a simp rule works it should be used over a simproc.

I think this answers my question!

I'm not sure about the conclusion of that thread - did someone find a simp lemma that works?

It is somewhat explicit in that thread, but the addition which works is
import Mathlib.Data.Fin.Basic

@[simp]
theorem coe_ofNat_of_lt (m n : ℕ) [NeZero m] (h : n < m) :
    ((no_index (OfNat.ofNat n) : Fin m) : ℕ) = OfNat.ofNat n := by
  rwa [Fin.coe_ofNat_eq_mod, Nat.mod_eq_of_lt]

example : ((3 : Fin 4) : Nat) = 3 := by
  simp

If the discrimnation tree behaviour is ok here (I assume it will be tried on every Fin-to-Nat coercion), then yes, looks plausible.


ReturnType returns unknown if function's return type is generic argument of the function (with default value) that has not been set

🔎 Search Terms
ReturnType, generic, default
🕗 Version & Regression Information

This is a crash
This changed between versions ______ and _______
This changed in commit or PR _______
This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
I was unable to test this on prior versions because _______

⏯ Playground Link
No response
💻 Code
const func = <Return = string>(): Return {
   //
}

type ShouldBeNumber = ReturnType<typeof func<number>>; // number
type ShouldBeString = ReturnType<typeof func>; // unknown

🙁 Actual behavior
ReturnType returns unknown.
🙂 Expected behavior
ReturnType returns default type.
Additional information about the issue
This was encountered when trying to write this kind of function:

const invoker  = <Endpoint extends (...args: any) => any>(endpoint: Endpoint, ...parameters: Parameters<Endpoint>): ReturnType<Endpoint> {
    // Perform some logic before endpoint function is called

    return endpoint(...parameters);
}

Duplicate of #48870.

I do not think this is working as indented in sense that it is working well. I see this rather as a side effect.

That exhibits the same distinction as
type Fun1<T = string> = () => T;
type Fun2 = <T = string>() => T;

One is a generic type (i.e. a type-function) that resolves to a concrete function type.  The other is the type of a generic function, whose return type is not known until it’s called.
Note that this is the same reason you can’t write Fun2<number>.

One is a generic type (i.e. a type-function) that resolves to a concrete function type. The other is the type of a generic function, whose return type is not known until it’s called.

I agree on the reasoning, but also that this is a silly way for the program to behave.
What's really intended is an instantiation expression with an empty type arguments list, e.g.:
// note: this gives an error:
// Type argument list cannot be empty.
type ShouldBeString = ReturnType< typeof func<> >;

A workaround (that I hate) is to add a dummy variable, so you can create an instantiation expression:
const func = <IGNORED, Return = string>(x:T): T =>{
  throw new Error("implement me")
}
type F1 = typeof func<null>
type F2 = typeof func<null,string>

@fatcerberus and what if I do this?
type Fun2<T = string> = () => T;

type L = Fun2<number>;

Do not get me wrong I understand what causes the reported bug above. But I do think that this distinguishment is frankly odd.

If not removing this split competely, some expression that can be used to convert one to another might fix this issue?

Is this what you're looking for?
const func = <Return,>(): Return => {
  throw new Error("implement me")
}
type Func<T=string,> = typeof func<T>
type ShouldBeNumber = ReturnType<Func<number>>; // number
//   ^?
type ShouldBeString = ReturnType<Func>; // string
//   ^?

https://www.typescriptlang.org/play?#code/MYewdgzgLgBAZgVzMGBeGAeASgUyggJzABoA+ACgEoAuGXfItUmAbwCgYYoALAkAdxhgcggKIE+BcgCIAlgFsADgBsc8nGFjrplNgF82UAJ6KcMAGJJgGACqpoBWWADmZNFxM4QceFdulDTxgAZW4QBGUAEwAhHAA5BHkAIxwCd3pCMBtPDEtkDDBElIJSUgBuGAB6SqEi1LZqzhgAPQB+QNMQsIiYnGCoRxd0vEzs01yrcqqahydnBprONqA

@cts-tradeit In case it's not clear, the reason for the distinction is:
type Fun1<T = string> = () => T;
type Fun2 = <T = string>() => T;

let x: Fun1  = () => "foo";  // ok
let y: Fun1 = () => 42;  // not ok, number is not assignable to string
let z: Fun2 = () => "foo";  // not ok, () => string can't function as a generic
let w: Fun2 = <T,>() => ({}) as T;

Without this distinction, you'd have no type you could use for w, which is important when you want to use generic functions as HOFs.

@rotu No not exactly. Imagine using a package (which i cannot alter) that exports the function below. Why the singature looks like this? Who knows. The author chose it for some reason. Beyond this function there are 50 more that have similar signature.
export const loadData = <Data = BasicData>(): Promise<Data> => {
   // omitted
}

Now, I need to know what type the function loadData defaults to when generic is not explicitly defined. See the function invoker in the first post. Your proposed solution would require me to explicitly define type for every single one of the 50 functions.

export const loadData = <Data = BasicData>(): Promise<Data> => {
   // omitted
}

Now, I need to know what type the function loadData defaults to when generic is not explicitly defined.

From that signature, you can't know what loadData will return.
If the author wants to communicate an actual type bound, it's with an extends clause:
export const loadData = <Data extends BasicData,>(): Promise<Data> => {
   // omitted
}

In this case, ReturnType<typeof loadData> will be Promise<BasicData>

@fatcerberus If i understood the proposal correctly, it would allow me to do something like this:
type Func = <T = string>(param: number) => T;

type FuncParams = Parameters<T>;

type FuncReturn = ValueForArguments<Func, FuncParams>;  // string

@rotu what about adding something like this to the language?
export const loadData = <Data = BasicData>(): Promise<Data> => {
   // omitted
}

type R = ReturnType<typeof loadData<default>>;

@rotu what about adding something like this to the language?
type R = ReturnType<typeof loadData<default>>; // BasicData

I think I'd prefer if ReturnType<typeof loadData<>> were legal, since it's a straightforward extrapolation of the existing syntax and fits with existing convention (e.g. you don't write [default] for an empty list). I'm kind of surprised that the empty type parameter list doesn't work, given that you can declare a type with an empty list of type variables: type Foo<> = {}.
I do think it's ugly that type variables in generic functions can have defaults. I don't see a use for them versus extends constraints.

If decisions we make either agree with you or are stupid, then I don't see much point in trying to engage with this issue. Seems like other folks have covered all the relevant points here - there are open issues on multiple possible avenues of solution for the particular problem.

@RyanCavanaugh That is called false dichotomy. There are certainly more possibilities than these two.


Updating KEP-3 (CLI) to reflect current state of 0.2.0

What would you like to be added:
We need to update KEP-3 to reflect current changes with 0.2.0
Why is this needed:
Some commands got renamed or we have new logic implemented. The CLI KEP should reflect this in its user stories.

I think updating keps back is just too much work, we should rather keep them small and maybe "close" them when they are already obsolete


[Feature] dubbo lossless upgrade  by uds  support

mosn v0.23.0，dubbo lossless upgrade  by uds  has a bug。
2021-06-22 00:09:46,517 [ERROR] [network] [transfer] [read] transferRead failed: unexpected net.Conn type; expected TCPConn or mtls.TLSConn, got *net.UnixConn

PR Welcome  ^_^


Highlighting in tsx seems broken

From @janpieterz on June 27, 2016 12:59

VSCode Version: Code - Insiders 1.3.0-insider (41f53d27a8cb477130f84116c78f43ddacbaf24b, 2016-06-27T05:07:29.758Z)
OS Version: Windows_NT ia32 10.0.10586

It seems to break on the <T,T> parts
Steps to Reproduce:

Create a tsx file with at least one class that extends React.Component
See!

import * as React from 'react';

class Test extends React.Component<{},{}> {
    public constructor() {
        super();
        console.log('created');
    }
}

class OtherTest extends React.Component<{},{}> {
    public constructor(){
        super();
        console.log('created');
    }
}

Copied from original issue: Microsoft/vscode#8188

From @boxstart on June 27, 2016 13:50
This seems to be related to commit 88f88a90938243434488ed72a81498651782607b, where the processing of angle brackets has been changed.

Well...

duplicate of #202


Android: Video not shared in other device in group call

I am able to launch and test the android setup in multiple devices. I am able to generate the access token and start the group call. It launch the front camera of the device and the video is rendered on the same device but it in transmitting to other device.
If I debug the code, function _call_RemoteParticipantsUpdated(object sender, ParticipantsUpdatedEventArgs e) never called.
Can you please help to resolve this issue?
Thanks in advance!
I have just attached the screenshot of emulator but in real device I can only see my picture.

Sorry for late reply. Perhaps you could try a few things just to make sure everything is setup correctly:

You are generating different tokens for each device, right?
You are joining the same group(guid) on all devices?
Are you able to run the ACS web demo, and if so, can you try joining a group call from the mobile client?

Thanks Thomas for your response.
Initially, I was generating separate tokens but some how it was not working then I started using the same token.
Today, I again tried with the sperate token for the devices and it worked.
Apart from that, Do you have any reference for the text chat which could be utilized in Xamarin Forms APP.
Thanks

@NeerajRai111 The chat is bundled in a separate aar from microsoft: https://search.maven.org/search?q=a:azure-communication-chat for android and this one for ios: https://cocoapods.org/pods/AzureCommunicationChat
I never had any use for chat, so I never made a nuget for these, sorry...


Withdraw error

I got error while try to withdraw.
Withdraw error (2): Error: The wallet passphrase entered was incorrect.
I check passphrase from file /root/opentrade/server/modules/private_constants.js
in a command line with cmd
examplecoind walletpassphrase LONG_passphrase_string 60
and its correct!

I try to setup exchange on another vps, encrypt wallet and got same error, when trying to withdraw.

have no issues here please answer the following so we can try and help you better:

in private_constants.js does it say LONG_passphrase_string
is the wallet encrypted?
what kind of coin are you trying to withdraw from? is it a Dash fork?

Does you tried another pass phrase?  For example, try "123"

@3s3s simpler passphrase with uppercase and lowercase symbols solve the issue. Symbols like !@#$% was fail to decrypt. Thank you!
@jonn4y thank you for attention to my issue!


Using run keyboard shortcut while another run is executing causes a double run

Steps to replicate:

Press run on a long-running script.
Press control-r or cmd-r

Confirmed closed in 1c982805d894ac1307254e2e3ffe5d625935c347


[Feature request] transcribe/translate local audio

Thank you for wanting to share an idea! But before starting, ensure to check if this feature request respects the following requirements:

[x] It is written in English (I can translate what you say, but issues written in English are easier to read for the other users).
[x] There is not already a similar feature request among the open or closed issues.

Since everything is locally computed and batteries included, An option for transcribe/translate local audio file may be feasible and cost-effective(think whisper apis+llm translate apis pricing).

Hi @mzltest, thank you for your suggestion, I've added this to the list of possible feature to include in the future (although it probably won't come very soon since I have little time to dedicate to the app at the moment and I prefer to focus on improving the features it already has).


Error while setting Expand Icon using Multi-Select

Godot version
4.0 dev alpha 8
System information
MacOS 12.3.1 Arm64
Issue description
I received this series of errors after I must-selected three buttons and clicked the Expand Icon checkmark.  Then I unchecked it and got the second error.
core/object/undo_redo.cpp:326 - Error calling UndoRedo method operation 'refresh': 'EditorInspector::refresh': Method not found.
MultiNode Set expand_icon
core/object/undo_redo.cpp:326 - Error calling UndoRedo method operation 'refresh': 'EditorInspector::refresh': Method not found.
MultiNode Set expand_icon
Steps to reproduce
Create a new project.
Create a Control node as the scene root
Add two buttons as children
Select both buttons and click the Expand Icon check mark.
Minimal reproduction project
Uploading Test.zip…

This is an error I've seen numerous times when toggling various properties. It's not specific to Expand Icon.

EditorInspector::refresh was removed in #45879 but seems like there are some leftover UndoRedo actions trying to call it.


Add Dimensional Hub Commands

(ignore the 'add no header registration functions commit', that was another commit that is not needed on the main branch and was causing merge conflicts, and it was needed for the new language system which hasn't been fully built yet)

comment - needs to be looked at

This has been implemented in the 1.0.0 branch and supports adding the commands in the config file so that they are not hardcoded in the plugin