Internal Server Error when opening any tab on cups homepage

Hi,
I'm facing a cups issue that I don't know how to debug. cups web page returns 500 Internal Server Error whenever opening Administration/Classes/Help/Jobs/Printers tabs. I've enabled maximum log verbosity (debug2), but I still see nothing meaningful/important beyond cupsdSendError code=500, auth_type=0, which leads me nowhere. Here's the log: https://pastebin.com/nzQrs45L
cups version is 2.2.6, it's an Optware-ng package on an armv7 router. Optware-ng currently uses patches from Debian (see here) and two local patches: cupsd-set-default-for-RIPCache-to-auto.patch and ppdc.patch. I've tried building cups without any patches (except the second local one, needed to cross-compile cups), the result is the same, and, by the way, the error_log from above was generated by an 'almost-clean' cups-2.2.6 version (ppdc.patch only).

Please tell me if there's something else I can do to debug this issue.
Thanks,
Alex
P.S. I forgot to mention another interesting part of the error_log:
D [12/Dec/2017:20:37:01 +0200] [Client 2] Waiting for CGI data.
d [12/Dec/2017:20:37:01 +0200] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1513103821
d [12/Dec/2017:20:37:01 +0200] process_children()
d [12/Dec/2017:20:37:01 +0200] cupsdFinishProcess(pid=24546, name=0xbe874398, namelen=1024, job_id=0xbe87436c(0)) = "/opt/lib/cups/cgi-bin/jobs.cgi"
D [12/Dec/2017:20:37:01 +0200] PID 24546 (/opt/lib/cups/cgi-bin/jobs.cgi) stopped with status 127 (File too large)

This at least gives the cgi crash error code. However, I don't know where to dig further...

I got this issue fixed. It's the same issue with uClibc-ng as #4496 with OpenBSD. Here's the patch that fixes this issue for me:
--- a/scheduler/process.c
+++ b/scheduler/process.c
@@ -25,7 +25,7 @@
 extern char **environ;
 #endif /* HAVE_POSIX_SPAWN */
 #ifdef HAVE_POSIX_SPAWN
-#  if !defined(__OpenBSD__) || OpenBSD >= 201505
+#  if (!defined(__OpenBSD__) || OpenBSD >= 201505) && !defined(__UCLIBC__)
 #    define USE_POSIX_SPAWN 1
 #  else
 #    define USE_POSIX_SPAWN 0

@alllexx88 Have you reported this bug in posix_spawn to the uClibc folks?
I hesitate to unilaterally disable posix_spawn with uClibc - seems like we either want a similar version check or add a configure option to disable posix_spawn.

@michaelrsweet I'll do this soon, now that I've narrowed it down to a standalone working example that works with GNU lib C, but fails with uClibc-mg 1.0.26:
#include <stdlib.h>
#include <stdio.h>
#include <string.h>

#include <unistd.h>
#include <spawn.h>
#include <sys/wait.h>

extern char **environ;

void run_cmd(char *cmd)
{
    pid_t pid;
    posix_spawnattr_t attrs;
    posix_spawn_file_actions_t actions;
    sigset_t defsignals;
    char *argv[] = {"sh", "-c", cmd, NULL};
    int status;

    sigemptyset(&defsignals);
    sigaddset(&defsignals, SIGTERM);
    sigaddset(&defsignals, SIGCHLD);
    sigaddset(&defsignals, SIGPIPE);

    posix_spawnattr_init(&attrs);
    posix_spawnattr_setflags(&attrs, POSIX_SPAWN_SETPGROUP | POSIX_SPAWN_SETSIGDEF);
    posix_spawnattr_setpgroup(&attrs, 0);
    posix_spawnattr_setsigdefault(&attrs, &defsignals);

    printf("Run command: %s\n", cmd);
    status = posix_spawn(&pid, "/bin/sh", &actions, &attrs, argv, environ);
    if (status == 0) {
        printf("Child pid: %i\n", pid);
        if (waitpid(pid, &status, 0) != -1) {
            printf("Child exited with status %i\n", status);
        } else {
            perror("waitpid");
        }
    } else {
        printf("posix_spawn: %s\n", strerror(status));
    }
}

int main(int argc, char* argv[])
{
    run_cmd(argv[1]);
    return 0;
}

Just like it was with OpenBSD, the problems seems to be with POSIX_SPAWN_SETSIGDEF usage. If I remove this flag, posix_spawn works fine.

@michaelrsweet Looks like posix_spawn works fine starting from uClibc-ng version 1.0.27 (Optware-ng used 1.0.26, now upgraded to 1.0.27). We could test for uClibc version like this:
--- a/scheduler/process.c
+++ b/scheduler/process.c
@@ -25,11 +25,15 @@
 extern char **environ;
 #endif /* HAVE_POSIX_SPAWN */
 #ifdef HAVE_POSIX_SPAWN
-#  if !defined(__OpenBSD__) || OpenBSD >= 201505
+#  if (!defined(__OpenBSD__) || OpenBSD >= 201505) && \
+      (!defined(__UCLIBC__) || (__UCLIBC_MAJOR__ > 1) || \
+       ((__UCLIBC_MAJOR__ == 1) && (__UCLIBC_MINOR__ > 0)) || \
+       ((__UCLIBC_MAJOR__ == 1) && (__UCLIBC_MINOR__ == 0) && \
+                                   (__UCLIBC_SUBLEVEL__ >= 27))
 #    define USE_POSIX_SPAWN 1
 #  else
 #    define USE_POSIX_SPAWN 0
-#  endif /* !__OpenBSD__ || */
+#  endif /* (!defined(__OpenBSD__) || */
 #else
 #  define USE_POSIX_SPAWN 0
 #endif /* HAVE_POSIX_SPAWN */

Looks a bit cluttered to me, but it gets the job done. What do you think about it?

[master 9e44dfbe6] Add conditional code for posix_spawn when using uClibc (Issue #5188)

If anyone finds this bug thinking it is not fixed in 2.2.7, make sure the /etc/cups is owned by cups and cups-files.conf has values User and Group set to 209.


On iOS, opening links with one's default browser

I would enjoy NetNewsWire much more if it enabled me to quickly open links with my default browser, instead of the app's own browser.
My iPhone has Safari extensions that I'd like to use. Opening a discrete window also facilitates quickly switching between NetNewsWire and the page.
Thanks.

Duplicate of #3029

I can’t find this setting anymore. Was it removed? Why? :(

It is still there in the TestFlight build for iOS.


Annotation for settings SAN on ingress resource.

Is your feature request related to a problem? Please describe.
I have a application that uses TLS on application level, but when creating a cert with cert manager only the ingress domain name is used in the cert (And any settings on the certificate spec), so any client from inside my cluster accessing my application via service name will fail.
Describe the solution you'd like
To be able to annotate SAN names on the ingress resource, so the certificate created can be used by ANY application pod and accessed by service name inside kubernetes.
Describe alternatives you've considered

manual installation of certificate.

Additional context
Add any other context about the feature request here.
Environment details (if applicable):
installing my application by helm chart.
/kind feature

Thanks for the feature request - a few questions:

What issuer type are you using?
So you are using an Ingress to expose your application, so that your
ingress controller performs TLS as well as your backend application (both
serving with the same cert). This seems like a bit of a strange setup.
Could you not just add your service name to ingress.tls.hosts to achieve
the same thing?

On Tue, 28 Aug 2018 at 05:05, Mazon<EMAIL_ADDRESS>wrote:

Is your feature request related to a problem? Please describe.
I have a application that uses TLS on application level, but when creating
a cert with cert manager only the ingress domain name is used in the cert
(And any settings on the certificate spec), so any client accessing my
application via service name will fail.
Describe the solution you'd like
To be able to annotate SAN names on the ingress resource, so the
certificate created can be used by ANY application pod and accessed by
service name inside kubernetes.
Describe alternatives you've considered

manual installation of certificate.

Additional context
Add any other context about the feature request here.
Environment details (if applicable):
installing my application by helm chart.
/kind feature
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jetstack/cert-manager/issues/860, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMbPzfuoCN9gxBgf77KQK3SrPbX0IDfks5uVMF_gaJpZM4WO4O9
.

Thank you for reply. you are correct, it will not work. :) i have thought about it some more. Will look into using istio for handling internal CA and secure communications between pods.


Move doc of Pandas UDF to additional-functionality

This PR is to move doc of Pandas UDF to additional-functionality/rapids-udfs.
closes https://github.com/NVIDIA/spark-rapids/issues/1939
Signed-off-by: Firestarman<EMAIL_ADDRESS>

build


nixos/rspamd: Preserve runtime directory when using socket activation

Motivation for this change
When I added support for socket activation to rspamd module in #34562 I missed that systemd deletes the RuntimeDirectory when the service is stopped. Since the default worker socket is in that directory it means that if the service is stopped the socket is deleted which means the socket unit needs to be restarted for the socket to be recreated.
Setting the RuntimeDirectoryPreserve option stops systemd from deleting the runtime directory so this change does that.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[X] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

also backported: 0f4e1170540


automatically updating documentation?

It doesn't look like all the new docstrings have been added to the documentation.
e.g.
https://github.com/YosefLab/scVI/blob/adcb5035bd9884f0c52675f484c6465e69da3523/scvi/inference/classifier_inference.py#L9-L19
doesn't show up in
https://scvi.readthedocs.io/en//latest/models.html#module-scvi.models
Is there a way to make it so that readthedocs automatically stay in sync with the master branch?

Readthedocs is sync with the master branch right now, but I think we need to put the .rst files on will class we want to include on readthedocs. I will update the new docstrings tonight.

Doesn't look like it updated

sorry, the build was failing but it should be resolved by #120

It's updated now. I think I still need to trigger the build on readthedocs.

The titles under usage section are very long. Should I shorten the titles on jupyter notebook so that it can look better?
(Also the inference section doesn't show up - looking into that. )

Yes, short titles are good.
Is there a way to have trigger the readthedocs build automatically, perhaps by adding something to . travis.yml?

Hmm... a lot of the titles in the notebook really would be better as text, or perhaps bold text. Let me commit a revised version.

I still don't see any documentation for, e.g., classifier inference:
https://scvi.readthedocs.io/en/master/inference.html

Fixed by #130 and adding a webhook.


Write a first iteration of the tool

Write a first working iteration of the tool. Refactor afterwards.

TODO

change ProjectItem data type -> replace functions by interfaces
add error handling to skeleton.go, might need to use defer to close files etc
finish go skeleton
implement clean command
implement functionality determined by flags
add testing
add github CI/CD (whatever its name is)

WON'T DO

change ProjectItem data type -> replace functions by interfaces

DONE

finish go skeleton

TODO

add error handling to skeleton.go, might need to use defer to close files etc
implement clean command
implement functionality determined by flags
add testing
add github CI/CD (whatever its name is)

Everything done, except a couple of issues that I am leaving for the next iteration


package-openssh

Our workflow needs to be smart to handle version with epoch for source and binary package file name.
Eg:
version=1:9.4p1-1gardenlinux~cdbd07d2c2d87772cbad5c2fe7a166581509fa94
version_orig=1:9.4p1
The source and binary package file name should be just versioned as 9.4p1 in this case:
More failed details:
https://github.com/gardenlinux/package-openssh/actions/runs/7086470581/job/19284800108

Builds with "nocheck noudeb":
https://github.com/gardenlinux/package-openssh/actions/runs/7113105419


[WIP] Feature/version 5

Still needs unit tests, obviously, and also has a couple phpcs sniffs.

Changes Unknown when pulling e98dfa1adde30008d2d6dc580ec2ac475f723c46 on DASPRiD:feature/version-5 into ** on soliantconsulting:master**.

Changes Unknown when pulling e98dfa1adde30008d2d6dc580ec2ac475f723c46 on DASPRiD:feature/version-5 into ** on soliantconsulting:master**.

Changes Unknown when pulling dae1501f7f7b0c84710398d3e208d10765c89082 on DASPRiD:feature/version-5 into ** on soliantconsulting:master**.

Changes Unknown when pulling b944924fb045af5d1ee867d86c35ec757f4712c9 on DASPRiD:feature/version-5 into ** on soliantconsulting:master**.

Changes Unknown when pulling b944924fb045af5d1ee867d86c35ec757f4712c9 on DASPRiD:feature/version-5 into ** on soliantconsulting:master**.

Changes Unknown when pulling d3a5e7afdb8a33b1561ebaa5e9a8e1090e5190c4 on DASPRiD:feature/version-5 into ** on soliantconsulting:develop**.

Squashed commits and remote merged with ff47056ef4d624390d356593b14f26a17fa73fb4


[SPARK-42171][PYSPARK][TESTS] Fix pyspark-errors module and enable it in GitHub Action

What changes were proposed in this pull request?
This PR aims to enable pyspark-errors module test coverall in GitHub Action and fix it.
Why are the changes needed?
#39387 added pyspark_errors module, but didn't enable it in GitHub Action.
The bug was not exposed in #39387 initially because ERROR_CLASSES_JSON has only one item in this PR.
https://github.com/apache/spark/blob/8b8d92334faee889d4106a665ce769403e098240/python/pyspark/errors/tests/test_errors.py#L31
The bug is exposed in the subsequent PRs. So, currently, it's broken.
$ python/run-tests.py --modules pyspark-errors
...
test_error_classes (pyspark.errors.tests.test_errors.ErrorsTest.test_error_classes) ... ERROR

======================================================================
ERROR: test_error_classes (pyspark.errors.tests.test_errors.ErrorsTest.test_error_classes)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/dongjoon/APACHE/spark-merge/python/pyspark/errors/tests/test_errors.py", line 31, in test_error_classes
    error_class_names[i] < error_class_names[i + 1],
    ~~~~~~~~~~~~~~~~~^^^
KeyError: 0

Does this PR introduce any user-facing change?
No.
How was this patch tested?
This PR shows the failure at the first commit by adding pyspark-errors test coverage.

https://github.com/dongjoon-hyun/spark/actions/runs/3999180114/jobs/6862791939

The second commit passed pyspark-errors in the CIs.

https://github.com/dongjoon-hyun/spark/actions/runs/3999260298/jobs/6862968301

cc @itholic and @HyukjinKwon

cc @xinrong-meng too

Could you review this, @huaxingao ?

Thank you so much, @viirya and @huaxingao ! Merged to master.

Thank you!

Late LGTM, thanks for fixing!


Replace "initialize" with "onReady"

For the instructions above, I had to replace:
Office.initialize = function (reason)
with
 Office.onReady(function (reason)

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

ID: 15be7148-d1e8-b58b-b026-9f072efb638a
Version Independent ID: 53a5d00c-d82b-6536-2e80-3e2a3452879a
Content: Build an Outlook Add-in
Content Source: docs/add-ins/quick-start.md
Product: outlook
GitHub Login: @jasonjoh
Microsoft Alias: jasonjoh

@glittle: Can you share what caused you to have to replace Office.initialize with Office.onReady? Did you hit an error? Having these details can help us determine next steps. Thanks.

@glittle thank you for the feedback. This quick start will be updated later this week when PR #475 is merged and the docs are refreshed.


Timeout values added

Added Timeout values for both blue-green-upgrade and expand-contract-upgrade in Gke-rolling-updates-demo repo. I verified the timeout values and added a buffer '1m' more..the way you asked me to.

Test this please


Ubuntu

Add Ubuntu packages tasks for each release. And I have an offer to you: make tasks for each type of OS with naming them  such as Debian or RedHat OS family, (Debian.yml or RedHat.yml) May be It will decrease conditions count in main task file.
That's my opinion, just think about it.
Best regards!

Sry, this is my first pull request )


Match more interface types

currently, some of the built in rules will only match interface types that meet the following pattern:
parent: ^interface\s+GigabitEthernet0/[0-9]+$
However, IOS L3 devices have more interface naming conventions than this.  I think it would be good to instead of having a long ass regex here for all the interface patterns, this be an alias to something like L3Interfaces that then that longer regex gets substituted for.
For example, on an ISR4331, the built in interfaces will be name:
interface GigabitEthernet0/0/0 - 2
The EHWIC L3 port first number will be higher.
Old 2800s will be name:
interface FastEthernet0/0
2900s will be named:
as above, GigabitEthernet0/[0-9]+$
I'm assuming as similar set of issues on the ASA side:
ASA5508s will be:
interface GigabitEthernet1/1
ASA5505s will be:
ASA5510s will be:
ASA5516s will be:
ASA5525s will be:

A more generic regex is probably the right answer, any kind of Ethernet interface \S+Ethernet\s+ or something like that, with any numbering scheme. Honestly the only reason we care about matching the word Ethernet is because of Ethernet-specific features like portfast, proxy-ARP, etc. The rest is irrelevant I think.

Agree
maybe something closer to
parent: ^interface\s+Ethernet/[0-9]+$
I think starting the line with interface is important though

Yes, I was suggesting something like:
parent: ^interface\s+\S*Ethernet[0-9/.]+$"
This would work on Nexus and IOSv where simply Ethernet is used.


add commonLabels value

Signed-off-by: BOSSER, Bastien<EMAIL_ADDRESS>Describe what this PR does
Add a commonLabels variable in the values.yml file that allows to add additional labels on all helm chart resources.
As you know, labels can be used to organize and to select subsets of objects. In my case of use it allows me to group the applications by category and to check by a simple command the status of it.
As examples, for all security applications, I put a label "my-cluster-name/application_group: security". Then I just have to make the command "kubectl get all -A -l my-cluster-name/application_group=security" to know the status of all applications that provide security.
Related issues
Fixes: #3437

@nixpanic I changed the commit message.
@Madhu-1 What type of test would you like me to develop? Should I just add the customLabels value in the helm deploy?

@nixpanic I changed the commit message. @Madhu-1 What type of test would you like me to develop? Should I just add the customLabels value in the helm deploy?

Just add some sample custom labels to the above script

@Madhu-1 Are the tests suitable for you?

changes LGTM, please squash the commits.

Normally you can do this directly during the merge @Madhu-1

changes LGTM, please squash the commits.

Normally you can do this directly during the merge @Madhu-1

@bastienbosser
This is currently automated in cephcsi repo.
merigfyio bot will be merging this pr with rebase and merge logic after approvals and successful ci runs.
It'll be cleaner to have one commit for this pr.
Thanks !

changes LGTM, please squash the commits.

Normally you can do this directly during the merge @Madhu-1

@bastienbosser This is currently automated in cephcsi repo. merigfyio bot will be merging this pr with rebase and merge logic after approvals and successful ci runs. It'll be cleaner to have one commit for this pr.
Thanks !

Done

After other PRs are done with their CI runs, this can be rebased by Mergify and de ok-to-test label can be added

@mergifyio rebase

There are a lot of failed tests but I'm having a little trouble relating these errors to the changes made. Can any of you (@nixpanic @Madhu-1) help me?

It seems the deploying through Helm is not working. All CI jobs fail in a similar way:

job: https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/organizations/jenkins/k8s-e2e-external-storage-1.25/detail/k8s-e2e-external-storage-1.25/31/pipeline/96
logs: https://jenkins-ceph-csi.apps.ocp.ci.centos.org/blue/rest/organizations/jenkins/pipelines/k8s-e2e-external-storage-1.25/runs/31/nodes/96/log/?start=0

Snippet:
Fri Oct 28 20:20:37 UTC 2022: 'kubectl_retry label node/minikube test.failure-domain/zone=testzone' done (ret=0)
node/minikube labeled
Error: unknown flag: --set-json
...

Maybe --set-json is something of a newer Helm version? You can change the Helm version in the build.env file.

Yes, because of the missing flag, deployment was not successful and csi pods are not running as expected. Can you please use some other existing flag to set it or we need to update the helm version in the build.env?

I changed the helm version in the build.env file to make the tests work.

I changed the helm version in the build.env file to make the tests work.

How this value can be set if someone is using an older helm version? Do you have the sample command?

/test ci/centos/mini-e2e/k8s-1.25

/test ci/centos/mini-e2e/k8s-1.25

/test ci/centos/mini-e2e/k8s-1.25

Seems to run well now!

@mergifyio rebase


Added EKS-D 1.24-1 prod

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


DAP debugging not working

This is most likely a user error but hoping you have some insight. I’m running Arch on an old T410 and when I just start a bare bones cargo project ‘cargo new —lib foo’. I’m not able to debug the initial unit test. Essentially nothing happens at all. Is there a way I can debug to get more info?
I have all the requirements met and you can see my configs here: https://github.com/wonbyte/.dotfiles/tree/main/.config/nvim
I’m also running ‘terminator’ as my terminal

Are you setting a breakpoint?

Yep, I just get a message “Compiling a debug build for debugging. This may take some time…” but nothing ever happens

Nm, total user error. I didn’t realize dap ui was a separate package and got confused based on README screenshot.


How to check request cookies in server-side Redux action?

In our app, we store a JWT inside a secure cookie to do initial authentication and bounce away from logged-in routes if a user isn't logged in.
Basically, I want to check for this cookie inside the load function in src/redux/modules/auth.js.
The load function by default looks like this:
export function load() {
  return {
    types: [LOAD, LOAD_SUCCESS, LOAD_FAIL],
    promise: (client) => client.get('/loadAuth')
  }
}

Instead of calling to an endpoint, I just need to examine the request itself.
Sorry for posting a blatantly help-related issue, but I am having trouble figuring this out.

Send other property, like checkCookie, and handle that in your middleware. Or use sagas to handle that in a prettier way.

@gabriel-miranda Sorry, could you expand more? Where would I send checkCookie, and what middleware?
Also, I came across reactGo, which is basically a fork of this project, except with sagas. Do you have any experience with it?


Docs - TODOs

for Welcome section of Docs:

[ ] Insert concise technical description of protocol
[x] Add link to new Medium(?) article from Althea and Ki Chong

we will do an overall documentation improvement when V2 is out.


[GHSA-p5c5-6564-vvr8] Improper Authentication in Apache CXF

Updates

Affected products
References

Comments
Add a patch https://github.com/apache/cxf/commit/295a4e2f9eb3e7e0513980202949ccc424dee2d4, of which the commit message claims [CXF-4776] - Fix + re-enable tests git-svn-id: https://svn.apache.org/repos/asf/cxf/trunk@1438424 13f79535-47bb-0310-9956-ffa450edef68

Hey @MarkLee131, I believe this is a dupe of the commit we already have on record.
https://github.com/apache/cxf/commit/e4c6b3b0899ef2ba87c2610efc323b71c13dd421


Fix examples

Coverage remained the same at 96.913% when pulling 145f05daa022ccec7024c347f157d1b88e9df3dd on georgeu2000:fix-upgrade-server into bf4b930c19934521bb0ffcfa19486ff7e415ed55 on igrigorik:master.

Coverage remained the same at 96.913% when pulling 145f05daa022ccec7024c347f157d1b88e9df3dd on georgeu2000:fix-upgrade-server into bf4b930c19934521bb0ffcfa19486ff7e415ed55 on igrigorik:master.

We really should have some tests to keep these examples working. ..

Indeed, that would be great.

Thanks for fixing these!

My pleasure.


netcdf

Hi Lion,
I got a friend asking me about the asdf. But unfortunately, he wants the netcdf...
I think hdf5 is thought to be better than netcdf. But do we have plans to provide netcdf in the future?

There are no plans to support netcdf4. It would be possible but its really kind of pointless for the ASDF format and we do gain a lot by sticking to a single container format.
netcdf4 is based on top of HDF5 so it is "just" another layer sitting on top of. It is indeed very useful for high-dimensional gridded data like they are common for example in climate science, e.g. a global 4 dimensional wind field but that is mainly due to the available tools.
We would gain nothing from using netcdf4; we would actually lose some feature like references which the netcdf data model AFAIK cannot accomodate. Also one less software layer means one less point of failure and as parallel I/O is still very tricky across different machines (as I'm sure you've noticed ;-) ) that is actually a pretty big advantage.

OK. I am going to tell him.
I think rather than providing the netcdf, it is better to provide multiple language interface for the potential users, including the fortran, C/C++, python.
We should make it simple, clean and easy to learn. So people can modify the I/O in their code to accommodate asdf.

I think rather than providing the netcdf, it is better to provide multiple language interface for the potential users, including the fortran, C/C++, python.
We should make it simple, clean and easy to learn. So people can modify the I/O in their code to accommodate asdf.

:+1: This is also exactly what we have been doing :-)


🐛 skill search is broken

When I tried to search for a new competence, the screen blink, and my search is reset.
https://user-images.githubusercontent.com/10440081/140068408-4b576851-0008-4ae1-8f80-fbbb901379fa.mov

This is caused by #126 , when navigating the 404 custom page is loaded for a short time before rendering the actual page.


Class cast exception when GStrings are used with System.getProperty

Summary:
GString substitution is now working. It works fine with Gradle 6.4.1 and earlier. But it break on Gradle 6.5
Steps to Reproduce
task bugFoo{
doLast {
String appCode = "XX"
println (":app-${appCode}:${System.getProperty('os.name', "${appCode}-gunit")}")
}
}
Expected Behavior
Should print ":app-XX:Mac OS X" without any exception
Current Behavior
It throws following error
"""* Where:
Build file '/Users/svenkatachalam/gw/lab/gosu-java-single-proj/build.gradle' line: 118

What went wrong:
Execution failed for task ':bugFoo'.

org.codehaus.groovy.runtime.GStringImpl cannot be cast to java.lang.String
"""

Thanks @sadheeshv - this looks real.
As a workaround, I think you can remove the extra layer of interpolation:

println (":app-${appCode}:${System.getProperty('os.name', "${appCode}-gunit")}")

becomes

println (":app-${appCode}:${System.getProperty('os.name', appCode+"-gunit")}")

Fixed via https://github.com/gradle/gradle/pull/13585.


Use setuptools "Extras" feature?

Documentation: https://pythonhosted.org/setuptools/setuptools.html#declaring-extras-optional-features-with-their-own-dependencies
Ipython leverages the extras_require keyword argument when running setup.py, so that users and libraries that depend on ipython can easily specify which set of extras utilities they will use.
For example:
pip install ipython[test]

Will also install nose and requests, which are specified like this:
https://github.com/ipython/ipython/blob/rel-3.0.0/setup.py#L251-L260
simpl should probably do this, so that simpl is keeping track of the specification of the required third party library, rather than forcing libraries that depend on simpl to (more or less) figure it out for themselves. Since some libraries actually share the same python namespace but have different names on PyPI, so this is probably the best route to go.
We could start with
pip install simpl[server]

which would install simpl, webob, and bottle.

I like this approach. Saw it for the first time with requests[security]. It seems like a pretty elegant way to deal with multiple dependency sets within the same project.
Can you reference one extra with another?
extra_requires = dict(
server =["bottle"],
all = ["simpl[server]"]

)

Very cool. This requires pip?

Does not require pip

Even cooler, then!

Can you reference one extra with another?

Good question. My guess would be "yes". I will test this and report back here


[Bug]: Mocked function returned by jest.mocked is not a function using ESM + Typescript

Version
29.0.1
Steps to reproduce
package.json:
{
devDependencies: {
    "@babel/core": "7.18.13",
    "@babel/plugin-transform-modules-commonjs": "7.15.0",
    "@babel/plugin-transform-runtime": "7.18.10",
    "@babel/preset-env": "7.18.10",
    "@babel/preset-typescript": "7.18.6",
    "@babel/runtime": "7.18.9",
    "@jest/globals": "29.0.1",
    "@types/jest": "29.0.0",
    "jest": "29.0.1",
    "ts-jest": "28.0.8",
    "ts-node": "10.2.1",
    "typescript": "4.8.2"
},
"jest": {
    "rootDir": "src",
    "testEnvironment": "jest-environment-node",
    "coverageDirectory": "../coverage/",
    "extensionsToTreatAsEsm": [
      ".ts"
    ],
    "preset": "ts-jest/presets/js-with-babel",
    "globals": {
      "ts-jest": {
        "useESM": true
      }
    },
    "moduleNameMapper": {
      "^(\\.{1,2}/.*)\\.js$": "$1"
    }
  }
}

And the following test setup:
import { jest } from "@jest/globals";
import File from "path/to/file"

jest.mock("path/to/file");

const mockedFile = jest.mocked(File);

describe("test", () => {
    beforeAll(() => {
        mockedFile.mockResolvedValue(value);
    });
})

Expected behavior
The function to resolve to the value specified in my mock
Actual behavior
TypeError: mockedFile.mockResolvedValue is not a function
Additional context
The code I've written doesn't make use of any ESM and uses only CommonJS, however, some of the packages I've imported make use of ESM. I've previously been able to circumvent any issues by using a certain transformIgnorePattern + moduleNameMapper. But since I've had to switch to yarn PnP that patch isn't available to me anymore and I can't switch back to node_modules.
Environment
System:
    OS: Linux 5.15 Ubuntu 20.04.4 LTS (Focal Fossa)
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
  Binaries:
    Node: 14.20.0 - ~/.nvm/versions/node/v14.20.0/bin/node
    Yarn: 3.2.3 - ~/.nvm/versions/node/v14.20.0/bin/yarn
    npm: 6.14.17 - ~/.nvm/versions/node/v14.20.0/bin/npm

It would be good to see minimal reproduction repo (without ts-jest and @types/jest).
Did you try running some simple test without involving jest.mocked()? I mean writing it in pure JavaScript, not TypeScript. If it does not work in JavaScript as well, then there is nothing wrong with jest.mocked(). From your description it is not clear how did you came to the idea to blame jest.mocked().

Hi, I have the same Problem.
Definitions of @types/jest und @jest differs
function createMockFromModule<T>(moduleName: string): T;
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/7c95278b06595be213b6991b65661077bbad579a/types/jest/index.d.ts#L140
createMockFromModule(moduleName: string): unknown;
https://github.com/facebook/jest/blame/616fcf56bb8481d29ba29cc34be32a92b1cf85e5/packages/jest-environment/src/index.ts#L95
After uninstalling @types/jest the problem remains.
It turns out, that other dependencies also depends on @types/jest like @testing-library/jest-dom.
Solution?!?
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/61862#issuecomment-1231461459
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62037


Suggested fix for #1000: not passing Command Line Args to dotnet projects, when launching from Visual Studio's debugger

For issue #1000
As mentioned in the issue:

When not debugging, ApplicationExecutor.cs PrepareProjectExecutables() will construct the command line arguments from the launchProfile.
It looks like this logic is either missing in Aspire when debugging, or dotnet.exe is supposed to be picking up the launch profile some other way (DOTNET_LAUNCH_PROFILE?) but it's not working for me.
This code works for my particular use case, but I'm not sure if there needs to be a "dotnet run" or "--" or whatnot to properly submit the args to the project.

@dotnet-policy-service agree

Thank you @jaredthirsk  for submitting the issue and taking a stab at a fix--very much appreciated.
I have added a comment to https://github.com/dotnet/aspire/issues/1000 explaining why I suspect this is Visual Studio issue and why I think this change is probably not what we want.

Issue #1000 closed instead by https://github.com/dotnet/aspire/pull/1212 (wiring up "csharp-launch-profile").


In index.html metadata, ignore <keyword> metadata in @keys/@href contexts

Description
Updates the HTML5 metadata generation in index.html to not consider <keyword> elements in @keys and @href contexts:

Text variable definitions
Topic-specific (i.e. not map-level) metadata

Motivation and Context
Fixes #4405.
How Has This Been Tested?
I ran the testcase from #4405. I also ran the usual tests.
Type of Changes

Bug fix (non-breaking change which fixes an issue)

In get-meta.xsl, the metadata template that matches <keywords> elements is updated to exclude any elements that have a @keys or @href attribute in the element ancestry.
Documentation and Compatibility
No documentation change is needed. A release notes entry could be as follows:

In the DITA-OT 4.2 release, the HTML5 transformation was updated to include map-level <keywords> metadata in the index.html file (#4351, #4352). However, this inadvertently also included variable definition keywords. In this release, only <keywords> not in a @keys (key definition) or @href (topic) context are considered. (#4405)

Checklist

My code follows the code style of this project.

https://github.com/dita-ot/dita-ot/wiki/XSLT-Coding-Conventions

@chrispy-snps if you have a draft PR, based on the title prefix "Draft: ", it's better to use a draft PR.

@jelovirt - thanks for the note on correctly filing draft PRs!
I filed this as Draft because I was going to ask the senior developers for feedback on the correct exclusion filter. But while writing up my thoughts in that message, I led myself to a conclusion.
Originally I was going to remove the descendant axis as you mentioned. But I think exclusions are better done by semantics than structure. For example, map-level metadata might be organized into topicgroup containers (we do this in some more complex publications), or perhaps a future version of the DITA (or user plugins similar to what @kirkilj uses) might explicitly populate keywords in <submap> containers for downstream processing.
After thought and experimentation, I updated this PR to exclude both @keys-related and @href-related <keyword> elements. Given the following DITA map:
<map>
  <title>My Map</title>

  <!-- keyword metadata -->
  <topicmeta>
    <keywords>
      <keyword>keyword1</keyword>
    </keywords>
  </topicmeta>

  <!-- keyword metadata in topicgroup-->
  <topicgroup>
    <topicmeta>
      <keywords>
        <keyword>keyword2</keyword>
      </keywords>
    </topicmeta>
  </topicgroup>

  <!-- variable definition -->
  <keydef keys="var1">
    <topicmeta>
      <keywords>
        <keyword>variable1</keyword>
      </keywords>
    </topicmeta>
  </keydef>

  <!-- keyword metadata in a non-@keys topicref -->
  <topicref href="topic.dita">
    <topicmeta>
      <keywords>
        <keyword>keyword-in-nonkeys-topicref</keyword>
      </keywords>
    </topicmeta>
  </topicref>

  <!-- keyword metadata in a @keys topicref -->
  <topicref href="topic.dita">
    <topicmeta>
      <keywords>
        <keyword>keyword-in-keys-topicref</keyword>
      </keywords>
    </topicmeta>
  </topicref>

</map>

the index.html metadata is as follows:
<meta name="keywords" content="keyword1, keyword2">

which is what I would expect for truly map-level metadata.
Feedback is welcomed!

If there's no further feedback or dissent, I think this should be included in 4.2.1.

In the example, I don't think keyword2 should be included in the keywords list. It's inside a <topicgroup>, not part of the root metadata. @robander what's your take?

Opened https://github.com/dita-ot/dita-ot/pull/4418 as I think this fix is incorrect. Nested topicmeta should not be used for index.html. For example if you have 2000 topicrefs and each has a two keywords in the topicmeta, the index.html would have 10 000 keywords in the HTML metadata. It can be argued that index.html "contains" all the content in the source set, but IMO index.html is the TOC, not "everything in the source set". If you replace keyword with author metadata, IMO it's not intuitive to think that index.html has been written by 10 000 different author just because each topic has two distinct authors.

@jelovirt - my fix does not collect from topic references, as explained in my description and shown in my example. I would have preferred an opportunity to receive feedback and refine the fix, if needed.

@robander - Thanks for your detailed thoughts.
For topics, I agree that nested-subtopic prologs should be considered. We use nested subtopics with topic/subtopic prologs regularly. All are relevant to the document as a whole.
For maps, we sometimes use bare <topicgroup> as containers to organize things in the Oxygen DITA Maps Manager tree view. So my mental model is that they are intrinsically transparent unless decorated with attributes that require otherwise. I tried to to be semantic in my solution, but perhaps it is better to take a more conservative approach and expand as needed.
But the root-map metadata we need for our flow is at the <map> root. Plus, #4418 has unit tests, which is always good. So I'm closing this request in favor of that one.


Attr: derive a few more traits

This is for use in downstream library which want to reference Attr type,
but need it to implement more traits.
One example is 'bread':
https://github.com/mkpankov/bread

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @huonw (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Thanks!


Customer feedback - This API does not signal all possible errors

Type of issue
Typo
Feedback
@lorihollasch try not to hate me too much 😄
An eagle-eyed colleague pointed out that the implementation of this in some OS versions is just a call to CcSetFileSizesEx which then  ignores any error status from it.
This argues either that this function is not reporting all errors or that the 'ex' version never reports errors via a status.  Or it could mean that the errors reported in the status from the 'ex' version are less important,
It seems like something should be done I just don't know what.
For myself I now just use the 'ex' version and either use the status it returns or the status it throws.  This seems to cover all eventualities - I would certainly be leery of using this function
Page URL
https://learn.microsoft.com/en-us/windows-hardware/drivers/ddi/ntifs/nf-ntifs-ccsetfilesizes
Content source URL
https://github.com/MicrosoftDocs/windows-driver-docs-ddi/blob/staging/wdk-ddi-src/content/ntifs/nf-ntifs-ccsetfilesizes.md
Author
@lorihollasch

LOL, no one could ever hate you, @rodwiddowson! I'll run your comments past the dev team ...

OK, @rodwiddowson, I've heard back from the cache manager team and once again your issue is a great call-out. I've updated the Ex page with some key info RE error codes and exception raising. I've also updated the non-Ex page to recommend that people use the Ex version instead. Thanks as always. Have a great weekend!


vertex_attrib_pointer_f32 doesn't work without a VAO

If I just bind the ARRAY_BUFFER and call enable_vertex_attrib_array + vertex_attrib_pointer_f32 on attribute location, nothing will be drawn to the screen.
Calling enable_vertex_attrib_array + vertex_attrib_pointer_f32 after bind_vertex_array works normally.

Hi! :wave: If I understand correctly, this state is associated with the bound VAO, so this is expected.

iirc, using VAO is a way to cache the vertex_attrib_pointer_f32 calls, but using vertex_attrib_pointer_f32 directly should work too

Depending on the exact GL profile and version you're using then there may be a default VAO, e.g. from the Khronos OpenGL wiki (https://www.khronos.org/opengl/wiki/Vertex_Specification):

The compatibility OpenGL profile makes VAO object 0 a default object. The core OpenGL profile makes VAO object 0 not an object at all. So if VAO 0 is bound in the core profile, you should not call any function that modifies VAO state. This includes binding the GL_ELEMENT_ARRAY_BUFFER with glBindBuffer.

You can also check the specification depending on the profile/versions you're targeting, e.g. in OpenGL when a non-zero VAO is required (https://registry.khronos.org/OpenGL-Refpages/gl4/html/glVertexAttribPointer.xhtml):

GL_INVALID_OPERATION is generated if zero is bound to the GL_ARRAY_BUFFER buffer object binding point and the pointer argument is not NULL.

Okay, I will take a look at my targets to see whether it accepts zero VAO.


Error: Unable to deserialize response with Content-Type application/JSON. Supported decodings are [/^application/json/, /^text/./, /^multipart/./, /^application/x-www-form-urlencoded/]

General information

SDK/Library version: 1.0.0
Node Version: v12.14.1

Issue description
During use of Paypal Payouts SDK, the first POST request to /api.paypal.com/v1/payments/payouts returns a 201 (it's working fine), then my app gets this weird error :

Error: Unable to deserialize response with Content-Type application/JSON. Supported decodings are [/^application/json/, /^text/./, /^multipart/./, /^application/x-www-form-urlencoded/]

It looks like the serializeRequest function is looking for application\/json/ content type while we're using application/JSON , which are causing our app to crash.while the server is responding with application/JSON  content-type, causing the library to throw an error

i'm having the same issue !
it looks like that the response from /api.paypal.com/v1/payments/payouts does not return the correct header....

I am also getting the same issue.

Same issue.

i've made a PR here to handle both UPPER & lower case content-type for json: https://github.com/paypal/paypalhttp_node/pull/6

same issue here, out of nowhere

No issue on sandbox env on my end.

@grawk great news ! 🚀  thanks for the quick reactivity !
is there any ETA yet ?

Looks like another checkpoint in an hour or so. It may be resolved by then.

Potential fix in place. Can anyone on this thread verify?

@grawk did you have something in place around 9:10 eastern time? We had a successful payout at that time without a JSON parse issue.

Haven't seen it happen since 3 hours ago aprox! 🙌

Seems to be fixed
On Tue, Apr 20, 2021 at 10:17 AM Miquel de Arcayne @.***>
wrote:

Haven't seen it happen since 3 hours ago aprox! 🙌
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/paypal/paypalhttp_node/issues/5#issuecomment-823311580,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACW6RWKQ5O4BYJZD3G7QAQTTJWEH7ANCNFSM43F6QQHQ
.

Seems good for me too !

@grawk I had payout items being paid multiple times and as a developer, I don't think fixing the backend is good enough if that's not open-source.
Could you merge https://github.com/paypal/paypalhttp_node/pull/6 so I can make sure that the library isn't going to be affected by the same mistake twice?

Hi @kewitz I'm sorry I don't own this repository. I am trying to find the right internal owners to help with the code fix/release.

Hi Leo, the way around the duplicate payouts (I used to have this issue) is
to issue an idempontcy token to each payout request, this is a unique key
that can’t be reused on two payouts in the last 30 days, it is the
sender_batch_id in the POST call in the sender_batch_header
On Tue, Apr 20, 2021 at 10:50 AM Leo Kewitz @.***>
wrote:

@grawk https://github.com/grawk I had payout items being paid multiple
times and as a developer, I don't think fixing the backend is good enough
if that's not open-source.
Could you merge #6 https://github.com/paypal/paypalhttp_node/pull/6 so
I can make sure that the library isn't going to be affected by the same
mistake twice?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/paypal/paypalhttp_node/issues/5#issuecomment-823337971,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACW6RWPTGBLB6IXXIYI7OI3TJWIEZANCNFSM43F6QQHQ
.

Thanks @andrewwiik! I was setting sender_item_id hoping that would also work. I'll make sure to refactor how I calculate sender_batch_id to ensure I'm not paying for the same stuff multiple times.

+1 on merging that PR.

This happened in production for us yet again.
Could it be possible to make a durable fix on this ?

Issue reopened, we still have the error in production.
Could you merge PR #6 please ?

@remmmmmm can you please provide a debug id ? which endpoint are you using?

@aninja8 there is no debug id, the request does not go through we're only left with the error message Error: Unable to deserialize response with Content-Type application/JSON. Supported decodings are [/^application/json/, /^text/./, /^multipart/./, /^application/x-www-form-urlencoded/]
We're hitting the endpoint: /api.paypal.com/v1/payments/payouts

@Sufiane can you give me a time window?

happened for the first time today at 3:06 PM Paris, France time
and a second time at 3:29PM Paris, France time.
We then proceed to black every payment made via paypal.

@Sufiane did you place any other requests in between the time frame? was this intermittent ?

We did not place any other requests, not that i'm aware of at least.
It happened every time we tried to make a payment with paypal.

please merge #6

@grawk any news ?

@aninja8 do you have some news for us please ?


How do I change path where compiled NAVX is created?

I know there's a property to change where the "packages" folder lives, however when I press F5 to compile and deploy my extension, the NAVX file is created at the root of my repo. Is there a way to change this so that the NAVX file is created somewhere else?

This is currently not possible when building from vscode directly. However you can achieve it by using alc.exe:
alc.exe /project:<path to project folder> /packagecachepath:<folder containing navx reference packages> /out:<path to output navx file>

We will consider adding a setting to the vscode extension to control the output path

Closing this as it is old and using the command line is sufficient for my needs.


HDDS-2464. Avoid unnecessary allocations for FileChannel.open call

What changes were proposed in this pull request?
ChunkUtils calls FileChannel#open(Path, OpenOption...).  Vararg array elements are then added to a new HashSet to be passed to FileChannel#open(Path, Set<? extends OpenOption>, FileAttribute<?>...).  We can call the latter directly instead.
https://issues.apache.org/jira/browse/HDDS-2464
How was this patch tested?
Ran TestChunkUtils.

Test failures are not related to this change.

Thanks @nandakumar131 for reviewing and merging it.


Improve/harmonize mobile builds (2.1)

Android:

Inexistent DEBUG_MEMORY_ALLOC replaced by DEBUG_MEMORY_ENABLED.

iOS:

Unconditional -fblocks. Formerly it was being added only if GameCenter enabled.
Fix failing build if GameCenter disabled by adding GameController explicitly.
Make release and release_debug be the same, except for DEBUG_ENABLED (for Android we are doing the same), which is: -O2 -ftree-vectorize -fomit-frame-pointer -ffast-math -funsafe-math-optimizations.
Drop the profile target.
Enable link-time optimization (slow, but hopefully gives a faster engine).

@punto-, could you have a look?:

I know you removed -ffast-math because of a possible compìler bug. Do you think that still applies?
Do you know about anyone using the profile target?
And any other possible wrong thing you find.

NOTE: The master version is subject to @punto-'s opinion at least, so this shouldn't be merged before the other one is approved.

I know you removed -ffast-math because of a possible compìler bug. Do you think that still applies?

I prefer not taking risks in the stable branch, I usually get 0 testers for pre-release binaries on iOS, if -ffast-math introduces issues, I don't want it until we're sure we can use it.

I can understand it.
If @punto- could shed some light over this maybe we'd know if this is no
longer a concern.
As an alternative, we can merge only the version for master and keep
this one pending until we have more information or find a reliable way
of testing (something like running physics-heavy games on the full range
supported architectures and OS versions in a meaningfull set of devices).
El 05/06/2017 a las 15:35, Rémi Verschelde escribió:

I know you removed -ffast-math because of a possible compìler bug.
Do you think that still applies?

I prefer not taking risks in the /stable/ branch, I usually get /0/
testers for pre-release binaries on iOS, if |-ffast-math| introduces
issues, I don't want it until we're sure we can use it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/8948#issuecomment-306188670,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCtqKAzGUufHCeOTp24KPupcQm2_poks5sBAQHgaJpZM4NoNkM.

No answer so far, so let's give it a spin; we'll just have to test the iOS template thoroughly before we decide to release 2.1.4-stable.

To give you some peace of mind, my game, although 2D, uses physics,
shaders, etc. extensively and at least on 64-bit ARM it's working
flawlessly.
El 17/06/2017 a las 11:51, Rémi Verschelde escribió:

No answer so far, so let's give it a spin; we'll just have to test the
iOS template thoroughly before we decide to release 2.1.4-stable.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/8948#issuecomment-309205383,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALQCtrU8k3aKW0-Ady849YAEg-zsQsteks5sE6GhgaJpZM4NoNkM.


Remove modeshape's ServletCredentials from the HTTP layers

Addresses: https://jira.duraspace.org/browse/FCREPO-1694
I am taking these one at a time now. Please bear with me. The Repository::login method requires a javax.jcr.Credentials object (which is a simple marker class: it doesn't do anything on its own), and the fcrepo-auth-* modules expect that the Credentials object is an instanceof modeshape's ServletCredentials.
Thus, in order to remove this particular modeshape dependency from fcrepo-http-commons, I added a CredentialsService as an injected "shim". There may be other ways to implement this, but I couldn't think of another way to do this without extensive changes. I would appreciate a review of this.

:+1:


1.0.0-rc3 throws exception when XML comments are readed

System.NullReferenceException: Object reference not set to an instance of an object.
   at Swashbuckle.AspNetCore.SwaggerGen.XmlCommentsOperationFilter.<>c.<ApplyPropertiesXmlToPropertyParameters>b__11_0(ApiParameterDescription p)
   at System.Linq.Enumerable.WhereListIterator`1.MoveNext()
   at System.Linq.Enumerable.FirstOrDefault[TSource](IEnumerable`1 source, Func`2 predicate)
   at Swashbuckle.AspNetCore.SwaggerGen.XmlCommentsOperationFilter.ApplyPropertiesXmlToPropertyParameters(IList`1 parameters, ApiDescription apiDescription)
   at Swashbuckle.AspNetCore.SwaggerGen.XmlCommentsOperationFilter.Apply(Operation operation, OperationFilterContext context)
   at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.CreateOperation(ApiDescription apiDescription, ISchemaRegistry schemaRegistry)
   at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.CreatePathItem(IEnumerable`1 apiDescriptions, ISchemaRegistry schemaRegistry)
   at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.<>c__DisplayClass4_0.<GetSwagger>b__5(IGrouping`2 group)
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector, IEqualityComparer`1 comparer)
   at System.Linq.Enumerable.ToDictionary[TSource,TKey,TElement](IEnumerable`1 source, Func`2 keySelector, Func`2 elementSelector)
   at Swashbuckle.AspNetCore.SwaggerGen.SwaggerGenerator.GetSwagger(String documentName, String host, String basePath, String[] schemes)
   at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Builder.Extensions.MapMiddleware.<Invoke>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.MigrationsEndPointMiddleware.<Invoke>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Diagnostics.EntityFrameworkCore.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

Looks like it happens here
https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/1292e2b9f410bb6ef29c457d685241d2730330c1/src/Swashbuckle.AspNetCore.SwaggerGen/Annotations/XmlCommentsOperationFilter.cs#L100

Can ParameterDescriptions or parameter.Name be null?

I see, same as #316


[Question] Blacklisting Spawn Egg from Spawner

Hey, I'm having trouble using the blacklist config Banned Mobs in the spawner.cfg.
I've tried with the following values:
quark:stoneling
stoneling
"quark:stoneling"
"stoneling"
At this point I'm a bit sick of /reloading, could you tell me what the correct syntax is please? :)

quark:stoneling should be the proper syntax assuming thats the registry name.
Also those configs don't support /reload, unfortunately.

That did the trick, thanks - I thought /reload worked so I hadn't actually tried quark:stoneling
Sidenote, I was given the advancement Spawner Modifier when I clicked a spawner with the blacklisted spawn egg for quark:stoneling


WSL failed to start after update Windows

Windows build number:
Microsoft Windows [Version 10.0.19041.113]

What you're doing and what's happening:
Run:
PS C:\> wsl -d ubuntu-19-04-server
Freezes in an attempt to launch and nothing happens.

What's wrong / what should be happening instead:
Distro should launched and worked.

Detailed logs
lxcore__.etl.zip

Hello, I have the exact same problem with the same Windows version (Version 10.0.19041.113)
I'd like to add that after some time (about 15 to 25 minutes) it shows the message:

The operation could not be started because a required feature is not installed.
[process exited with code<PHONE_NUMBER>]

This happened after an update 10 2004 (20H1) KB4540409  (Comulative update for Windows 10 Version 2004 for x64 based systems)

Thanks, @pedrodaniel10 ! The solution you found helped me too.

Same issue here with 19569.rs_prerelease.200214-1419.
Issue manifesting itself as:

The operation could not be started because a required feature is not installed.

Workaround link provided by @pedrodaniel10 did work and removed the issue in my case.

Hello, I have the exact same problem with the same Windows version (Version 10.0.19041.113)
I'd like to add that after some time (about 15 to 25 minutes) it shows the message:

The operation could not be started because a required feature is not installed.
[process exited with code<PHONE_NUMBER>]

This happened after an update 10 2004 (20H1) KB4540409 (Comulative update for Windows 10 Version 2004 for x64 based systems)
EDIT: I guess it was some configurations of Hyper-V that changed with the update. Following this post https://www.surfacetablethelp.com/2018/10/fix-hyper-v-not-working-after-windows-10-v1809-upgraded.html fixed my problem.

Thank you! I fixed my problem.

This did not work for me but it's a bit different,
WSL starts fine and MS Store Unbuntu 18.04.4 LTS runs fine. Yet Ubuntu 20.04 returns:
The system cannot find the file specified.
[process exited with code<PHONE_NUMBER>]

@ThomasMConnors what does wsl.exe -l -v shows?

It shows
C:\temp>wsl.exe -l --all
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
Ubuntu-20.04
(There was no -v option for wsl)
From: onomatopellan<EMAIL_ADDRESS>Sent: Friday, April 24, 2020 3:18 PM
To: microsoft/WSL<EMAIL_ADDRESS>Cc: Tom Connors<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [microsoft/WSL] WSL failed to start after update Windows (#4939)
Importance: Low
@ThomasMConnorshttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FThomasMConnors&data=02|01||bcfb88321d5345ba4d3408d7e88441d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637233527058349776&sdata=OzWWIi%2BfHVwc1aO2jD6ahPrz0bxsUlzwdV2lvUv1s%2Fg%3D&reserved=0 what does wsl.exe -l -v show?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2FWSL%2Fissues%2F4939%23issuecomment-619195885&data=02|01||bcfb88321d5345ba4d3408d7e88441d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637233527058359770&sdata=llW0eIz6ltyqA5KFvzbiS1gHJdmBXBq%2FMzf77KONXAw%3D&reserved=0, or unsubscribehttps://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAD3DSC3FVIG6KGEWJNWBRHTROHQX5ANCNFSM4K7HVMCQ&data=02|01||bcfb88321d5345ba4d3408d7e88441d7|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637233527058369761&sdata=Y6saPGR9W%2BI9nZtjQz%2BgFK4X%2FhaFwTVYa2Ub3rCHTlg%3D&reserved=0.

@ThomasMConnors Thanks. Then it seems you are still in WSL1 and this thread's issue is more about WSL2 and hyper-v.
In WSL1 that message could mean the Ubuntu 20.04 app is not installed in C:
See https://docs.microsoft.com/en-us/windows/wsl/install-win10#troubleshooting

After windows 10 2004 update wsl is not working the commands also not working

After windows 10 2004 update wsl is not working the commands also not working

Same here, no matter which distro I chose to start on Windows 10 2004,  I got a `[process exited with code<PHONE_NUMBER>]'
PS C:\Users\username> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         2
  Ubuntu          Stopped         2
  Ubuntu-18.04    Stopped         2

Tried steps in https://www.surfacetablethelp.com/2018/10/fix-hyper-v-not-working-after-windows-10-v1809-upgraded.html, but nothing happened.

@leizhilong Try this https://github.com/microsoft/WSL/issues/4929#issuecomment-636419019

@leizhilong Try this #4929 (comment)

Thanks @onomatopellan for the clue.
I tried the method metioned in the comment. Unluckily,  my attempt to remove the Hyper-V virtual eth adapter end up with the same<PHONE_NUMBER> error code.  I guess errors with 0xffffffff  and<PHONE_NUMBER>  might be due to differenet causes.
When I use wsl -d Ubuntu to run WSL after deleting virtual adapter and reboot,   the Hyper-V virtual eth adapter would appear again but WSL still dosen't work.
Thanks anyway.

netsh winsock reset saved my day.
see:
https://github.com/microsoft/WSL/issues/5092#issuecomment-615545141

After windows 10 2004 update wsl is not working the commands also not working

Same here, no matter which distro I chose to start on Windows 10 2004, I got a
[process exited with code<PHONE_NUMBER>]
PS C:\Users\username> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         2
  Ubuntu          Stopped         2
  Ubuntu-18.04    Stopped         2

Tried steps in https://www.surfacetablethelp.com/2018/10/fix-hyper-v-not-working-after-windows-10-v1809-upgraded.html, but nothing happened.

This problem was solved by reinstalling windows features
Hyper-V,
Windows subsystem from Linux,
Virtual machine platform

I was able to resolve the issue with the following steps.

Make the above security settings changes.
Update WSL2 kernel

I don't know if it was disabling and re-enabling the features (Microsoft-Windows-Subsystem-Linux, and VirtualMachinePlatform, then rebooting), or running netsh winsock reset and rebooting, which saved me.

https://github.com/microsoft/WSL/issues/4904#issuecomment-643883570

netsh winsock reset saved my day.
see:
#5092 (comment)

Yes it works!

After windows 10 2004 update wsl is not working the commands also not working

Same here, no matter which distro I chose to start on Windows 10 2004, I got a
[process exited with code<PHONE_NUMBER>]
PS C:\Users\username> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         2
  Ubuntu          Stopped         2
  Ubuntu-18.04    Stopped         2

Tried steps in https://www.surfacetablethelp.com/2018/10/fix-hyper-v-not-working-after-windows-10-v1809-upgraded.html, but nothing happened.

This problem was solved by reinstalling windows features
Hyper-V,
Windows subsystem from Linux,
Virtual machine platform

Yes,Maybe Hyper-V has error

I've spent multiple hours on this problem on a few different occasions and I don't remember the same solution working twice. This usually seems to happen after a Windows Insider update (verified the build version was higher than the minimum), but I had it happen for no reason that I could determine yesterday. After spending almost four hours trying to fix this problem for the third time, the thing that just worked for me was running through the installation steps without uninstalling first WSL or Ubuntu: https://docs.microsoft.com/en-us/windows/wsl/install-win10. This could have worked because it might have applied an update that I wasn't getting, but I have no idea which step fixed if it that's not what happened =\ This is not a technically good answer, but I hope it helps someone else who's reached the end of their patience and felt like they've tried everything too.

Tried to enable and disable optional components Windows for WSL:

Disable

dism.exe /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart
dism.exe /online /disable-feature /featurename:VirtualMachinePlatform /norestart

Restart machine
Enable

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart

Restart machine
List WSL Distros:

PS C:\>  wsl -l --all

Распределения подсистемы Windows для Linux:
ubuntu-19-04-server (по умолчанию)

Run Distro:

PS C:\> wsl -d ubuntu-19-04-server

Similar. Freezes in an attempt to launch and nothing happens.

I faced the same problem on my machine's Ubuntu-20.04 distro (WSL2) after compacting its ext4.vhdx file.
I've tried netsh winsock reset but failed. Yet your solution works for me. Thank you very much.


Allowed to annotate nodes based on the local variable names.

Seeing of the node names in the .svg is helpful for debugging.

Looks like a great idea :+1:


Allow marshaling model.TraceID to/from a string

Coverage remained the same at 100.0% when pulling b4baea50e452e3d7c817c3545eb461fbb211cafd on marshal-trace-id into 9ccf1469224b2199c677eeacfe3ec895f80df418 on master.

Coverage remained the same at 100.0% when pulling 62bbc6f00275e2c97d1c7198f85d942892d7f248 on marshal-trace-id into 9ccf1469224b2199c677eeacfe3ec895f80df418 on master.

Coverage remained the same at 100.0% when pulling 5b3d5003d16fd134c85a8d5426e8358bbe7fac2d on marshal-trace-id into 9ccf1469224b2199c677eeacfe3ec895f80df418 on master.

Coverage remained the same at 100.0% when pulling 5b3d5003d16fd134c85a8d5426e8358bbe7fac2d on marshal-trace-id into 9ccf1469224b2199c677eeacfe3ec895f80df418 on master.


Add literal union predicate helper

What are you changing?

add literalUnionPredicate helper method, that creates type predicates that narrow primitives to literal type unions

Why?

it’s convenient and is already used in dotcom-rendering and @guardian/identity-auth.

Example
import { literalUnionPredicate } from "@guardian/libs";

const stages = ["DEV", "PROD"] as const;
const isStage = literalUnionPredicate(stages);

const maybeStage = process.env.STAGE;
if (isStage(maybeStage)) {
  // here maybeStage is narrowed to "DEV" | "PROD"
}

I tried to use the const type parameter in a1e60ae399266099a53f82face60d855413e29ba from @chrislomaxjones’s demo in the Client-Side Meetup, but Rollup failed to parse the file…


Fix required_without rule bug. v1.0.1

Description
Verify that the field exists. no validation value is valid.
Checklist:

[x] Securely signed commits
[x] Component(s) with PHPdocs
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

@bangbangda Looks good, I'm glad you acknowledged my logic. I would change code to:
if (empty($data[$field]) && ($data[$field] != '0')) { return false; }
Even though this should rarely happen - empty string ' ' should be valid input.

The required rules have always required that it is not empty or not 0. Empty strings have always failed the require rule. For cases like that, we do have the permit_empty rule.

Is this better?
Support for empty arrays.
if (! array_key_exists($field, $data) || ! $this->required($data[$field] ?? ''))
@lonnieezell @niteraven7

Hi @lonnieezell I think you may have confused him :)
I've been thinking about the permit_empty rule and I'd like to propose a change. I don't understand why the rule seems to superseded all other rules if it's in there? Rules are supposed to cascade from one rule to the next and I think it would be helpful if permit_empty functioned the same way. For example, I have a form that requires an email address OR phone number OR both. The validation rules are as follows:
public $recipient = [
'first_name' => 'required|min_length[1]|max_length[50]',
'last_name' => 'required|min_length[1]|max_length[50]',
'email' => 'required_without[number]|permit_empty|valid_email',
'number'	=> 'required_without[email]|permit_empty|numeric'
];
I'd like the rule set to check if email OR number exists and then if one does permit the other to be empty. permit_empty seems to hijack the whole thing. Why can't it just cascade like all the other rules?
Please put some thought into this.
Thank you,
Kyle

I'd like the rule set to check if email OR number exists and then if one does permit the other to be empty. permit_empty seems to hijack the whole thing. Why can't it just cascade like all the other rules?

Please put some thought into this.

Because of the way required works currently, but it wouldn't hurt for that all to have a revisit. I did that library pretty early on and it's showing some cracks. Anyone want to take a crack at it? :)

There is confusion in the method definition of required_without.
It says, "The field is required when all of the other fields are not present in the data."
I guess the definition should be like,
"The field is required when all of the other fields are present in the data but not required(means, the value can be blank or empty)."

Ah, that makes sense then. Yes, it should be modified to only use non-empty fields to check against so that it's functionality matches required_with.

I guess we can close this PR as the definitions are changed in the #1862.


Functions client 404s on existing functions

Describe the bug
I may very well be doing something wrong here, but I cannot get the functions invoke endpoint to work. All attempts to invoke a function 404.
I can get this to work with the JavaScript client, which calls https://mysubdomain.supabase.co/rest/v1/rpc/testing_func. The Python client, however, attempts to call https://mysubdomain.functions.supabase.co/testing_func which 404s for me.
To Reproduce
Steps to reproduce the behavior:

Create any function.

create or replace function testing_func (
  num int
)
returns table (
  num_ret int
)
language plpgsql
as $$
begin
  return query
  select
    num;
end;
$$;

Attempt to invoke the function

import asyncio
import os

from dotenv import load_dotenv
from supabase import create_client

load_dotenv()

url = os.environ.get("SUPABASE_ENDPOINT")
key = os.environ.get("SUPABASE_PRIVATE_KEY")
supabase = create_client(url, key)
func = supabase.functions()

async def test_func():
    resp = await func.invoke(
        function_name="testing_func",
        invoke_options={
            "body": {
                "num": 1,
            }
        },
    )
    return resp

resp = asyncio.run(test_func())
print(resp)

{'data': b'Function not found', 'error': None}

Expected behavior
The function executes successfully.
Screenshots

n/a

Desktop (please complete the following information):

OS: macOS
Version supabase==1.0.3

Smartphone (please complete the following information):

n/a

Additional context

n/a

Fixed in #467 - the correct URL is now used for the functions client. Feel free to re-open if the issue still exists


Rename AAD to Entra in docs. Closes #5780

Rename AAD to Entra in docs. Closes #5780

Thanks @nanddeepn, we'll review it ASAP.

Hi @nanddeepn just had a quick look at your PR, seems like you only updated one page. The purpose of the issue was to replace all Azure AD, AAD, ... occurrences in the docs. Can you still add the missing pages to this PR? Thanks!

Apologies for delay.
I will update PR by this Sunday.

Looks there are conflicts. I will raise new PR.

Raised new PR at https://github.com/pnp/cli-microsoft365/pull/5877
Closing this.


Activate repo on travis for testing

This repo is not active on travis and therefore will not be automatically tested.

activated


Expose a getter for the model that resides inside the Lockstep state

Exposing the getter enables writing custom functions that act on the model. For example:
instance StateModel (Lockstep state) where
  {- other class methods elided -}
  precondition st act = Lockstep.precondition st act && modelPrecondition (getModel st) act

-- | Custom precondition
modelPrecondition :: state -> LockstepAction state a -> Bool
modelPrecondition = ...

Thank you kindly :)


Portis is not working

When I try to log in to manager.rns.rifos.org on mainnet I get this modal and I cannot move forward.
Steps to reproduce:

go to manager.rns.rifos.org/
press connect wallet
follow portis indications
modal appears

Hey @miltonwg,
Thanks, this has been reported with #428. I'm going to close this ticket and use the original one.


FIELD_INTRGRITY_EXCEPTION when trying to update/create metadata records in managed package

We are using mdapi to create/update metadata records in a managed package. Everything works fine in the packaging as well as any other developer orgs. However, when we install the beta package in a different org, MetadataService.upsertMetadata returns a FIELD_INTRGRITY_EXCEPTION. But this error doesn't report which field has issue.
Attaching the JSON formatted result of MetadataService.upsertMetadata call.

This looks like an issue with the org i would report this to Salesforce. You should run the code via Execute Annonymous and thus in the Debug Log will be the XML request. You can then pass this to Salesforce when raising a case to reproduce the issue (via curl) without having to use the Apex wrapper which will distract the triaging of this issue.


tests: fix filtering on integration platforms

Fixed filtering on integration platforms.
Fixes #39738
Signed-off-by: Anas Nashif<EMAIL_ADDRESS>

I see the PR doesn't address all errors from the issue this PR marks as getting fixed. Validating if the reported error is fixed is a bit hard, because the errors are exposed in another PR #36433. It means we might need to rebase #36433 onto this PR to check if this PR fixes some errors exposed in #36433. I can rebase my PR onto this one, and we will see if the errors are gone.
@nashif Is the plan to fix those errors in parts? After validating rebasing on in #36433 I can approve this PR, but after it is merged and there are still not all errors fixed, i will reopen #39738 and edit to what errors are left.

@PerMac  this is not going to work and I am not sure why I was assigned to https://github.com/zephyrproject-rtos/zephyr/issues/39738 in the first place, just trying to get rid of this bug and remove it from my plate.
The right way to do it is to fix all issues your PR (#36433) finds in the same PR, otherwise this will continue to be a chicken and egg problem.
This PR fixes the issues listed in the original issue, if you think it does not, please let me know what it does not fix and I will look at it.
I can't be dealing with an open-ended bug that depends on something else.

@nashif Is the plan to fix those errors in parts? After validating rebasing on in #36433 I can approve this PR, but after it is merged and there are still not all errors fixed, i will reopen #39738 and edit to what errors are left.

IMO You should fix those in the same PR you are exposing them.

@nashif:

@PerMac this is not going to work and I am not sure why I was assigned to https://github.com/zephyrproject-rtos/zephyr/issues/39738 in the first place, just trying to get rid of this bug and remove it from my plate.

Twister and CI is leaky. Many regressions are caught by developers by chance, after being in the main for a while. I am aware of all the difficulties in such a vast project, with hundreds of platforms and thousands of tests that can be executed. Testing everything is just not feasible.
We try patching those breaches by providing new fixes and workflows. Having the CI decided what to test and what to skip is probably necessary for such a vast project, but we need at least reliability and traceability of the "decision process". One of the ideas to get a bit more control over the CI was to use "integration_platforms". This list not only tells CI which platform to choose for testing but what is IMO more important it should forbid the CI to skip such configurations. I mean, what is even the point of explicitly telling CI which configuration to test, if the CI could decide to skip it at one point, and no one will even realized, that there is 0 coverage in the CI for a given feature/module/etc? And the problem is that it actually continue to happen.
IMO having unreliable CI is a HIGH PRIORITY issue. I think our mindset should be "how to improve the quality/reliability" and not "get rid of this bug".

IMO You should fix those in the same PR you are exposing them.

Ok, we can try this approach. I will certainly ask for help, since I don't have enough knowledge about all the exposed bugs

This PR fixes the issues listed in the original issue, if you think it does not, please let me know what it does not fix and I will look at it.

The mentioned issue listed 5 exposed failures, where in this PR you addressed 2 of them. I am sorry, but I don't see a point in coping the issue's body here. I rebased my PR exposing the issues on this one and main and some of the reported issues are still there.

I can't be dealing with an open-ended bug that depends on something else.

It is not an open ended bug. It has clear definition of failing samples. It seems after all the rebasing new issues were exposed, but there are not reported as the part of the issue yet and don't have to be. So I don't expect you to keep on fixing all the newly exposed bugs, neither do I plan to have the issue growing. I can open a new one and try fixing other issues. But please, don't imply that I am making the original issue open ended. The scope was clearly defined and not fully addressed.

IMO having unreliable CI is a HIGH PRIORITY issue. I think our mindset should be "how to improve the quality/reliability" and not "get rid of this bug".

huh, cool down. I am fine with this being fixed, however the approach is not ideal. You are introducing a change that exposes issues, fine, fix those issues with the change so we can get it integrated the earliest. Filing bugs against each issue is just going to delay this and the fixes are trivial enough to be part of the code that introduces them.

The mentioned issue listed 5 exposed failures, where in this PR you addressed 2 of them. I am sorry, but I don't see a point in coping the issue's body here. I rebased my PR exposing the issues on this one and main and some of the reported issues are still there.
Because 1 was fixed automagically and did not need a fix and 2 others can't be fixed, they depend on a module that is not in the manifest, so there is nothing to fix.

It is not an open ended bug. It has clear definition of failing samples. It seems after all the rebasing new issues were exposed, but there are not reported as the part of the issue yet and don't have to be.

yes, thats what I call open-ended, but the time something is fixed, new issues will show up because we did not integrate the change that would guard against them, so this is going to be a whack a mole type of situation, read: open-ended.

The commit was cherry-picked into #36433 as suggested. This is the PR which exposes the issue and will come with the fixes for exposed failures.


How to add new line?

Hi,
As far as I know, new line in markdown is added by

adding two space at the end of the line
adding two new line characters
adding \ at the end of the line
adding
 at the end of the line

I tried all of the above and none of them worked. Is there another way of adding new lines that vue-simple-markdown supports?

Hi,
You need to press enter key just like in any text editor. There is no special way to make a line break.
If You press enter key one time, You will get one new line (one line break)
If You press enter key two times, You will get two new lines (two line breaks)
etc
If You still have a problem, please paste here an example of the text which doesn't work.

Same problem here - The text that is being passed to :source has \r\n for line breaks. The \r\n should probably be replaced with
 by vue-simple-markdown, but it's being included in the output HTML as is, and the browser simply ignores it while rendering the HTML. Sample code:
<tempalte>

    <vue-simple-markdown :source="text"></vue-simple-markdown>

</template>

HTML Output:

A
B
C

I've also had this issue and found that I needed to include the css file within my component, as per the doc's guidance - https://github.com/Vivify-Ideas/vue-simple-markdown/blob/master/README.md#bundler-webpack-rollup
import 'vue-simple-markdown/dist/vue-simple-markdown.css';

My markdown renderer component:
<template lang="pug">
.container
  vue-simple-markdown(
    :source="content"
  )
</template>

This is the magic line: white-space: pre-wrap;

@owenandrews Could you give some more detail? Where should I include that line and how does it work?

@portikM Give your markdown element a class, say .markdown-body and then in your CSS file add:
.markdown-body {
    white-space: pre-wrap;
}


Make it simpler to create coverage for a particular target.

Thus it is possible to test if a particular unit test provides all the
necessary coverage, not other tests that accidentally cover that code
path.
Update dependencies to run coverage in development environment.

Codecov Report

Merging #1394 (c33e8ac) into master (6b27242) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head c33e8ac differs from pull request most recent head 6e3f13a. Consider uploading reports for the commit 6e3f13a to get more accurate results

@@           Coverage Diff           @@
##           master    #1394   +/-   ##
=======================================
  Coverage   92.90%   92.90%
=======================================
  Files         340      340
  Lines       23832    23832
=======================================
  Hits        22141    22141
  Misses       1691     1691

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


Improve default SpotLight.beamWidth default value

Currently the default values match the VRML ones but it is not a valid setup in Webots given that there is the constraint that beamWidth has to be less or equal to cutOffAngle.

test me

Build Passed :ok_hand:
You can safely merge 'enhancement-spotlight-default-beamwidth' into 'develop'.

:+1:

:eyes:

I am wondering if we should not use a 'nicer' value (e.g. something which makes the light 'smooth' e.g. 0.7) to help the user designing nice simulations?

Yes, I also though about it.
But then I was hesitating in choosing an arbitrary value so I simply chose the value that is automatically set in the current version so that the behaviour doesn't change.
0.7 is a good value.

test me

Build Passed :ok_hand:
You can safely merge 'enhancement-spotlight-default-beamwidth' into 'develop'.

This contradicts VRML'97 default value: http://www.lighthouse3d.com/vrml/tutorial/index.shtml?slight
We should therefore add some code to import/export to VRML'97 and handle correctly the default VRML97 value.

We should therefore add some code to import/export to VRML'97 and handle correctly the default VRML97 value.

Just note that we never handled correctly the default VRML 97 value.
The version with beamWidth 0.785 was working exactly as before.

Adding code to correctly export VRML'97 is very quick, but the import code is more complicated.
So at the end I think that it is better to keep the default VRML value even if it is not supported in Webots and resetting the beamWidth to default value will throw an error as this is a very minor issue.

A good compromise might be to set a good default value when we create a new SpotLight node (we did something similar for Box.size).

Yes, this is easy done.
I can commit it if you want.
But it doesn't solve the original issue that is that the default value (the one set by reset) is not supported by Webots.


WIP: Documentation Contribution Guide

Here's a draft of the documentation contribution guide. Please provide comments to the existing content.
Currently missing chapters:

Metadata and Attributes
Requirements (naming, supportability statements, legal requirements etc.)
Internal JIRA issues workflow
Publishing

Notes:

The Merging Contributions chapter is a lightly edited version of @inoxx03's contribution to README.adoc, which I moved into the Contribution Guide.

Resolves #239.

Since you seem to be okay with it as it is, I'm removing the WIP flag and creating a follow-up issue that will address the missing stuff.

merging...

merged: 8aae1c3ec3a14bc09d3da7c20212467f29dce9d6