Use std::conditional_t for type-switching pattern

Slightly reduce the burden on compilers during template instantiation.

Nice, yes - this is another hangover from the original colony implementation supporting c++98/03. Will implement. I also need to do a bunch of other changes so will either accept this and do them after or just do it in the beta then submit.

Fixed in beta
On 14/04/2022 4:48 pm, A. Jiang wrote:

Slightly reduce the burden on compilers during template instantiation.

    You can view, comment on, or merge this pull request online at:

https://github.com/mattreecebentley/plf_hive/pull/4
https://github.com/mattreecebentley/plf_hive/pull/4
    Commit Summary

3c3feb7
https://github.com/mattreecebentley/plf_hive/pull/4/commits/3c3feb7b67a4673df2dcb455084a4b07d163fcf2
Use std::conditional_t
File Changes

(1 file https://github.com/mattreecebentley/plf_hive/pull/4/files)

M plf_hive.h
https://github.com/mattreecebentley/plf_hive/pull/4/files#diff-32c2d2d70cc51caff8e906577e1188f330416501f24ed8f89b78bfae65c791c2
(23)
Patch Links:

https://github.com/mattreecebentley/plf_hive/pull/4.patch
https://github.com/mattreecebentley/plf_hive/pull/4.patch

https://github.com/mattreecebentley/plf_hive/pull/4.diff
https://github.com/mattreecebentley/plf_hive/pull/4.diff

—
Reply to this email directly, view it on GitHub
https://github.com/mattreecebentley/plf_hive/pull/4, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABE4FISCANXQYMVTNLPCFY3VE6PRDANCNFSM5TMTPMFA.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Fixed in new version - thank you


Force lavapipe on local testing system when multiple GPUs are present

This is my attempt to force lavapipe to generate the screenshots, but I had alot of trouble generating screenshots for
https://github.com/pygfx/pygfx/pull/712
My strategy was:

SSH into a linux machine that doesn't have a GPU.
Regenerate from that machine.

But given the progress in https://github.com/pygfx/pygfx/pull/709 it seems that we should be able to create a fixture to force pytest to use the lavapipe based GPU.
Locally, on Ubuntu 23.10  (and likely a few other mods) I get failures on the following tests
examples/tests/test_examples.py::test_examples_compare[validate_text_anchor] FAILED [ 77%]
examples/tests/test_examples.py::test_examples_compare[validate_culling] FAILED [ 88%]
examples/tests/test_examples.py::test_examples_compare[validate_transparency] FAILED [ 94%]
examples/tests/test_examples.py::test_examples_compare[validate_text_size] FAILED [ 95%]

The errors seem to be associated with the edge of the text. On Ubuntu 22.04 it seems fine. I have seen many font differences between Ubuntu 20.04, 22.04 and 23.10 in terms of font support so I would like to attribute it to that.
xref: https://github.com/pygfx/pygfx/issues/684

ah i see.


Add kotlin-multiplatform-mobile topic

The Kotlin team is now changing its approach to the Multiplatform mobile samples. The number of great projects is growing, and we can't keep adding them to the already huge table in the documentation.
Instead, we decided to keep a handful of projects in the table and give a link to a handy search by the GitHub topic. To add the topic to your project, please use the kotlin-multiplatform-mobile tag in the About section of your GitHub repository.

Thanks Danil for letting me know.


Enforce strong passwords

Pen test result:
"The password length is weak when creating candidate accounts, 6 chars, OWASP recommends 12. There also does not appear to be any complexity requirements as 123456 is a valid password."
https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Authentication_Cheat_Sheet.md
To apply to new accounts. May send reset link to existing account holders. Or evaluate password when they log in.

There is some guidance from GDS here: https://design-system.service.gov.uk/patterns/passwords/

And adding the 'Show' button as mentioned by MOJ here: https://moj-design-system.herokuapp.com/components/password-reveal


get activity types

Is it possible to get the type of activity with the distance sample?
I want to make a difference between e.g. a 5km walk, or a 10km run.
Thanks!

actually, there is. But it isn't well-documented feature.
Check this file - https://github.com/StasDoskalenko/react-native-google-fit/blob/master/android/src/main/java/com/reactnative/googlefit/ActivityHistory.java
getActivitySamples - returns you all activities along with there name.
Note - name actually is a number from this list
https://developers.google.com/fit/rest/v1/reference/activity-types


Fix workinghour mixin

coverage: 88.674% (+0.2%) from 88.449% when pulling 763e9899615f7de07c22328ecb418feb8994a376 on fix-workinghour-mixin into 153557d67f6ac423e4cf114f500eaac2e01f8a3e on main.


upgrade ark & jarslink version

#120

Pull Request Test Coverage Report for Build 306

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 72.175%

Totals

Change from base Build 296:
0.0%

Covered Lines:
2306

Relevant Lines:
3195

💛  - Coveralls


Allow specifying a different repo for issue tracking

I'm currently working on a codebase where there's one repo for issues and another for code, this is to aid in separating concerns as far as I understand it. So I'm wondering if it would be a useful feature for others as well as myself to be able to optionally specify a different repo to use for issues. I expect this kind of use case isn't entirely uncommon on Github? however I'll happily stand corrected if it is. Thanks.

@danhalson I am in a similar situation.  I just realized if you can put repo:myApp/nameOfRepo in the query.  I use my PR/code repo for PR queries and issue tracking repo for my issue queries.

Thanks @levitate-chris this has solved the issue for me, I guess just a mention of this in the docs could be handy?

Actually it is referenced in the query syntax link. Will close.


Viewing data that are already on the GPU

Is there a way to make pygfx work with data that are already on the GPU? Such as tensorflow or torch Tensor arrays. I was looking at how WGPU works with the textures and as far as I understand you give it a texture and then it writes it to GPU (queue.write_texture) But is there a way to make a Texture from a array already on the GPU?

I think it's all scoped to a device object's context ID. I don't think you can acces any memory that is owned by another context. That would be a serious security issue.

Ah I see, just read up on CUDA contexts. Is there anything equivalent to interprocess communication that can run on the GPU to send data between a CUDA context and WGPU context (maybe like zmq on GPU?).
Anyways I think I'll benchmark the roundtrip of a cuda torch Tensor -> numpy array -> wgpu texture before seeing if it's really necessary.

Is there anything equivalent to interprocess communication that can run on the GPU to send data between a CUDA context and WGPU context (maybe like zmq on GPU?).

I have no idea ...

If there is something like that it certainly won't be running on the GPU, it can't run anything sophisticated like that because it's not a CPU. :)

Thanks for the details!
Tested it out and roundtrip GPU -> CPU -> GPU is more than fast enough for visualizations. (4096, 4096) can be done at at least 30Hz on a RTX 3080 (running on a new Debian install, for some reason it's maxing out at half my vsync, I'll figure that out later).
fpl example but should be same performance with pygfx
import torch
import fastplotlib as fpl
from wgpu.gui.auto import WgpuCanvas
import pygfx

canvas = WgpuCanvas()
renderer = pygfx.WgpuRenderer(canvas, show_fps=True)

plot = fpl.Plot(canvas=canvas, renderer=renderer)

size = (4096, 4096)

img = plot.add_image(torch.cuda.FloatTensor(*size).random_().cpu().numpy(), name="img")

def update(p):
    p["img"].data = torch.cuda.FloatTensor(*size).random_().cpu().numpy()

plot.add_animations(update)
plot.show()

fpl.run()


Fix Fuzz 4147

Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4147
Doesn't crash if user passes in arg.type!=STRING for GRPC_ARG_HTTP_CONNECT_SERVER.
Let me know what you think of this. If you don't want to semi-silently pass this error, then we should propagate the failure up somehow. Aborts are never good, even on bogus input.

****************************************************************

libgrpc.so

     VM SIZE                                                                      FILE SIZE
 ++++++++++++++ GROWING                                                        ++++++++++++++
  +0.0%     +80 [None]                                                            +416  +0.0%

 -------------- SHRINKING                                                      --------------
  -0.6%     -16 src/core/ext/filters/client_channel/http_connect_handshaker.cc     -16  -0.6%
      -1.9%     -16 http_connect_handshaker_do_handshake                               -16  -1.9%

  +0.0%     +64 TOTAL                                                             +400  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

Had an offline discussion with @vjpai about what is and is not valid fuzz scenarios. The conclusion is that the api_fuzzer is not meant to exercise users misusing our API. In that case, having the ASSERT in this code is fine, because passing in GRPC_ARG_HTTP_CONNECT_SERVER as an int type is a misuse of the API.
The right fix, then, would be to stop the api_fuzzer from inputting this arg incorrectly. I'll leave this around so more can weigh in, then change to fix it the other way tomorrow

[microbenchmarks] No significant performance differences

****************************************************************

libgrpc.so

     VM SIZE                                                                      FILE SIZE
 ++++++++++++++ GROWING                                                        ++++++++++++++
  +0.0%     +48 [None]                                                             +72  +0.0%

 -------------- SHRINKING                                                      --------------
  -0.6%     -16 src/core/ext/filters/client_channel/http_connect_handshaker.cc     -16  -0.6%
     -11.5%     -11 [Unmapped]                                                         -11 -11.5%
      -0.6%      -5 http_connect_handshaker_do_handshake                                -5  -0.6%

  +0.0%     +32 TOTAL                                                              +56  +0.0%

****************************************************************

libgrpc++.so

     VM SIZE        FILE SIZE
 ++++++++++++++  ++++++++++++++

  [ = ]       0        0  [ = ]

[trickle] No significant performance differences

[microbenchmarks] Performance differences noted:
Benchmark                                                                                cpu_time    real_time
---------------------------------------------------------------------------------------  ----------  -----------
BM_StreamingPingPong<InProcess, NoOpMutator, NoOpMutator>/32768/2                        -4%         -4%
BM_StreamingPingPongMsgs<InProcess, NoOpMutator, NoOpMutator>/32768                      -7%         -7%
BM_StreamingPingPongWithCoalescingApi<MinInProcess, NoOpMutator, NoOpMutator>/32768/1/0  -4%         -4%
BM_UnaryPingPong<MinInProcess, NoOpMutator, NoOpMutator>/32768/32768                     -6%         -6%


Less verbose way to pass through props into components?

Describe the problem
When creating games with svelte, its very common to create "Sprite" components. For example, if I wanted to create a resizable textbox, with a fancy drag handle (e.g. a small knob that appears when hovering on a corner), it could look something like this.
<ResizeableTextbox>
  ...
  <DragHandle/> // top left
  <DragHandle/> // top right
  <DragHandle/> // bottom left
  <DragHandle/> // bottom right
  ...
</ResizeableTextbox>

I want the <DragHandle> component to only encapsulate the fancy rendering of the knob, and not to contain any behavior/control logic. Also, since I use tailwind, I want to be able to apply style overrides via classes.
If <DragHandle> was an element, I could simply do:
<ResizeableTextbox>
  ...

 // Assume 'draggable' is a custom svelte action.

  ...
</ResizeableTextbox>

But since it's a component, I have to explicitly declare the props in the DragHandle.svelte component and manually pass it along to the root element.
// DragHandle.svelte

   ...

I'd like to see some way to reduce this boilerplate that needs to be repeated for every component that I want to use as a 'Sprite'. More generally, for tailwind users, allowing the extension of the class of the root element in a component is a pretty frequent pattern.
Describe the proposed solution
I don't have a clear solution, but here are some ideas to get the brainstorm ball rolling:

A new attribute on elements that inherits all the props of the component?

// DragHandle.svelte

  ...

Introduce some kind of way to do inheritance in svelte components.
Discussed already in issue 192.

Alternatives considered
1. Wrap the Component in a div and apply the styles on the div.
<ResizeableTextbox>
  ...

    <DragHandle/>

  ...
</ResizeableTextbox>

Cons: Creates an unnecessary div.  Doesn't allow full flexibility as the node of the actions applied refer to the wrapper div and not the sprite.
2. Create sprites as a custom element
Cons: The cons of custom elements are in the svelte docs.
Importance
would make my life easier
Additional Information
No response

you may have to move this issue to the svelte repo instead https://github.com/sveltejs/svelte
I think the maintainers will revisit svelte once sveltekit 1.0 is stable


Check truthy/falsy-ness for non-primitives to identify unreachable code

Suggestion
In some cases TypeScript can identify unreachable code and throws an error:
const isTrue = true;
if (isTrue === false) {
  console.log('Can never be reached.')
}

In other cases it is currently not possible, but it would be very helpful. (Maybe even with a suggestion what could have been meant - see array example.)
const isArray = ['hello'];
if (!isArray) {
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}

const isObject = {};
if (!isObject) {
  console.log('Can never be reached.')
}

🔍 Search Terms

reachable / unreachable
dead code
condition
falsy / truthy
primitive / non-primitive
always

✅ Viability Checklist

My suggestion meets these guidelines:

[ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code -> It can break code, but only to show potential bugs.
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Throw errors on unreachable code examples.
const isArray = ['hello'];
if (!isArray) { // error: This condition will always return false. Did you meant to check `isArray.length`?
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}

const isObject = {};
if (!isObject) { // error: This condition will always return false.
  console.log('Can never be reached.')
}

// OR:
if (isArray) {
} else {
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}

📃 Motivating Example
This week I saw a colleague which could have found a bug way sooner by introducing such a check. ❤
💻 Use Cases
Finding bugs.

This is a good idea, but I don't know how hard it is to create a check that doesn't have too many false positives — or even true positives, to avoid introduces lots of new errors at once. Probably the best thing is to run a prototype on a bunch of real code.

Examples of incorrect code for this rule:
function head<T>(items: T[]) {
  // items can never be nullable, so this is unnecessary
  if (items) {
    return items[0].toUpperCase();
  }
}

function foo(arg: 'bar' | 'baz') {
  // arg is never nullable or empty string, so this is unnecessary
  if (arg) {
  }
}

we can run no-unnecessary-condition on real world code.

Keywords: equals equality object objects comparability reference equality value equality semantics


Pulling an image with --all-platforms fails if the image contains an SLSA provenance manifest

Environmental Info:
K3s Version:
k3s version v1.26.1+k3s1 (f10af367)
go version go1.19.6

Node(s) CPU architecture, OS, and Version:
Linux beast 6.1.14 #1-NixOS SMP PREEMPT_DYNAMIC Sat Feb 25 10:25:43 UTC 2023 x86_64 GNU/Linux

Cluster Configuration:
Single node setup for testing purposes
Describe the bug:
We pull images in order to save them to an onprem bundle, when pulling a recent version of keycloak, the operation failed with ctr: failed to extract layer sha256:09a85f55824bc820d92dc7578e2a0afe1d19cdc5dbdbd1b994891ee1ae5bb0b8: failed to get stream processor for application/vnd.in-toto+json: no processor for media-type: unknown
Steps To Reproduce:
k3s ctr images pull --all-platforms quay.io/keycloak/keycloak:20.0.5

Expected behavior:
It pulls the image correctly.
Actual behavior:
It fails with ctr: failed to extract layer sha256:09a85f55824bc820d92dc7578e2a0afe1d19cdc5dbdbd1b994891ee1ae5bb0b8: failed to get stream processor for application/vnd.in-toto+json: no processor for media-type: unknown
Additional context / logs:
unpacking linux/amd64 sha256:054ef67eb7dae0129bbb9eb0e0797fd2392cd6d135094a6063ae7ff7773ef81f...
unpacking linux/arm64 sha256:054ef67eb7dae0129bbb9eb0e0797fd2392cd6d135094a6063ae7ff7773ef81f...
unpacking unknown/unknown sha256:054ef67eb7dae0129bbb9eb0e0797fd2392cd6d135094a6063ae7ff7773ef81f...
INFO[0020] apply failure, attempting cleanup             error="failed to extract layer sha256:09a85f55824bc820d92dc7578e2a0afe1d19cdc5dbdbd1b994891ee1ae5bb0b8: failed to get stream processor for application/vnd.in-toto+json: no processor for media-type: unknown" key="extract-348288778-KLGm sha256:09a85f55824bc820d92dc7578e2a0afe1d19cdc5dbdbd1b994891ee1ae5bb0b8"
ctr: failed to extract layer sha256:09a85f55824bc820d92dc7578e2a0afe1d19cdc5dbdbd1b994891ee1ae5bb0b8: failed to get stream processor for application/vnd.in-toto+json: no processor for media-type: unknown

We package containerd's ctr binary but it is not part of this project. You should check with the upstream project at https://github.com/containerd/containerd to see if there is already an issue reported for what you're experiencing.


Created keys in two confirmation models with ambiguous constraints.

I notice two fields related to the confirmation having some potential issues, either missing the constraints or use it in an incorrect way. Could you help fix it?
Thanks in advance.
Issue 1

The field key in RealmCreationKey is created using the secrets.token_bytes and we can add the unique constraint in the model, just in case.
This is the common practice to add unique constraints.  Also, Zulip adds such constraints in other models, like the generated emailtoken for Stream model.

class RealmCreationKey(models.Model):
    creation_key = models.CharField("activation key", db_index=True, max_length=40)

def generate_realm_creation_url(by_admin: bool = False) -> str:
    key = generate_key()
    RealmCreationKey.objects.create(
        creation_key=key, date_created=timezone_now(), presume_email_valid=by_admin
    )

Potential fix
Add the unique constraints to creation_key field.
Issue 2

I am a little confused about the confirmation_key field in Confirmation model.
It is also a generated random string, so we may safely assume that it should usually always be unique.
Of course, we can also want it to be unique_together with type.

class Confirmation(models.Model):
    class Meta:
        unique_together = ("type", "confirmation_key")

def create_confirmation_link( obj: ContentType, confirmation_type: int, ...):
    key = generate_key()

    Confirmation.objects.create(
        content_object=obj,
        date_sent=timezone_now(),
        confirmation_key=key,
        realm=realm,
        type=confirmation_type,
    )

However, we fetch the data using the confirmation_key only, (not together with type).This is inconsistent with the unique constraints.
It may also lead to MultipleObjectsReturned Exception.
def accounts_register(request: HttpRequest) -> HttpResponse:
    try:
        key = request.POST.get("key", default="")
        confirmation = Confirmation.objects.get(confirmation_key=key)
    except Confirmation.DoesNotExist:
        return render(request, "zerver/confirmation_link_expired_error.html")

(Also in (def maybe_send_to_registration))
Potential fix

Either When fetching data, use confirmation_key and type together / not use .get(confirmation_key=key).
Or Make confirmation_key to be unique alone.

Thanks!

Thanks for the report!  I think we discussed this in chat.zulip.org.
Just to summarize the conclusions: issue 2 was resolved with solution (1), namely removing use of Confirmation.objects.get(confirmation_key=key), in a014ef75a3a0ed7f24ebb157632ba58751e732c6.  While the security bug wasn't this precise index issue, I think we did notice it while thinking about this set of questions, so your raising them is much appreciated.
For issue 1, I think the right plan is likely to remove the RealmCreationKey model in favor of it just being another Confirmation object instance -- I don't see a clear reason to have a parallel database field for this.  I believe if we complete that change, we can close this issue as resolved.  I've tagged this as a priority because removing security-sensitive duplicate code paths is valuable work.
@mateuszmandera @chdinesh1089 FYI.


register_files fails

open() an file fd
runs io_uring_register_files_update(...) to register fd
close fd using io_uring_prep_close
repeat above process for many other files
after about 20+ open/register fd all of a sudden raises OSError(9, 'Bad file descriptor')

All the liburing register test passes, in one of my software test it fails. If I disable register, test passes.
Testing in Linux 5.13

related to https://github.com/axboe/liburing/issues/377 problems

Let's reopen and keep separate, I'm not sure yet it's a valid program and so.
Can you provide some more details? Having a link to the test would be great.

Will do if I can find a proper test case to reproduce this, for now its related to #377 (I think)

Depends how you create issues, but we want to have a separate issue for each problem. #377 is already problematic as it's just a pile of thoughts, not related userspace issues, backport/stable problems and so on, and it's hard to track anything particular there. #377 doesn't mention anything registered files related, neither I see such in logs.
So, I do consider it a separate issue, and if it would turn otherwise, we'd mark it dup'ed and close, as any other project would do. And it has no chances to be solved (if there is an issue in the first place), if it stays closed.

I see.
I did created these tests and they are passing https://github.com/YoSTEALTH/Liburing/blob/master/test/register_file_test.py

I did create these tests and they are passing https://github.com/YoSTEALTH/Liburing/blob/master/test/register_file_test.py

Ok, so... is everything works now? If not, what is the question or the problem?

Yes, everything is working now. Other issue was causing this issue, since its fixed, its all good.


Id3v2 -- should recognize "Blues" as a valid genre

I was writing some small scripts to analyze the mp3s I have in my OS/X Music library, looking for metadata inconsistencies.  To do that I have some python code that makes calls out to mediainfo --Output=JSON -f on each file and then turning them into python objects.  All of that is working great.
The only odd bug that I couldn't figure out is that I had a couple ripped CDs with "Genre" == "Blues" and that field was not showing up correctly.  Indeed, Music.app (f/k/a iTunes) showed the genre just fine but mediainfo's CLI reported that the file had not been tagged with a genre!
That led me down a bit of a rabbit hole, but I think I understand the problem.  As you probably remember, ID3 can tag genres either as free-form text or as numeric codes.  Apple Music will support either, but if you use a genre that has a well-known ID3v1 numeric code it will use that (likely for maximum compatibly with ancient mp3-reading software)
The numeric code for "Blues" happens to be zero (see https://en.wikipedia.org/wiki/List_of_ID3v1_Genres )  MediaInfoLib knows this as well (see Genre_000 in Source/Resource/Text/Language/DefaultLanguage.csv )
However, the code that interprets the numeric genre codes treats both "0" and "255" as unset values.  In Source/MediaInfo/Tag/File_Id3v2.cpp :
        case Elements::TCON :
[...]
                                if (Element_Value==__T("0") || Element_Value==__T("255"))
                                    Element_Value.clear();
                                Fill(Stream_General, 0, General_Genre, Element_Value);
[...]
        case Elements::TCO  :
[...]
                                if (Element_Value==__T("0") || Element_Value==__T("255"))
                                    Element_Value.clear();
                                if (!Element_Value.empty())
                                    Fill(Stream_General, 0, General_Genre, Element_Value);

So both in the code to handle TCO and TCON tags ("Content type") will treat a string with the value "0" as if it were unset.  This means any file that Music.app sets to have genre "Blues" is considered genre-less by MediaInfoLib.
I assume that this may have been done as a workaround for buggy mp3 generators that may have left 0 or 255 as incorrect ways of indicating a missing genre.  However, I can't find any documentation about that.  I checked in the git history and the logic seems unchanged since the code was first imported into a VCS, and there isn't anything related to "blues" in the changelog.
It seems possible to me that the code is being overly paranoid, or possibly working around an encoder bug that has long since become irrelevant.  Possibly can 0 be accepted as a valid genre per the id3v1 spec?

Just another datapoint -- ffprobe shows the genre on these mp3s correctly.  Checking the source code, it accepts genre strings that are numeric (or numeric surrounded by parens) as synonyms for ID3v1 numeric genres, but it doesn't treat "0" as special: https://github.com/FFmpeg/FFmpeg/blob/master/libavformat/id3v2.c#L337
    unsigned genre;
[...]
    if (!(strcmp(key, "TCON") && strcmp(key, "TCO"))                         &&
        (sscanf(dst, "(%d)", &genre) == 1 || sscanf(dst, "%d", &genre) == 1) &&
        genre <= ID3v1_GENRE_MAX) {
        av_freep(&dst);
        dst = av_strdup(ff_id3v1_genre_str[genre]);

So any integer string from "0" to "191" is accepted as a genre to map

Same problem in the 22.12 release

Fixed by https://github.com/MediaArea/MediaInfoLib/pull/1708#issuecomment-1458203378.

Unfortunately this still seems to not work, at least for me even in the 23.06 release.
I haven't dug into the source code again, but looking at the #1708 change it only patches one place, while my original bug report found two suspect locations.  Maybe that's related?

@mitchblank my mistake, I should not have closed the issue so quickly.
Please try this dev snapshot, I fixed the other line of code + ID3 (not v2).

Sorry, I didn't have a chance to try the snapshot you provided (I just am using the mediainfo CLI tool from homebrew and never found time to integrate a library snapshot.  However I can verify that the 23.11 release has fixed the issue.


double-beep: Watch dr.uwenboherbalhome(?:@gmail.com)?

double-beep requests the watch of the watch_keyword dr\.uwenboherbalhome(?:@gmail\.com)?. See the MS search here and the Stack Exchange search here.

dr\.uwenboherbalhome(?:@gmail\.com)? has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


[BUG] Integer enums that don't have explicit values set produce broken types

Is there an existing issue for this?

[X] I have searched the existing issues

Nature of Your Project
JavaScript, TypeScript
Current Behavior
When defining an integer enum without explicitly assigning values to the keys, the generated types will contain syntax errors (see repro for a sample model).
These enums can be compiled without issue, although the output looks a bit unexpected:
$ cds repl
> await cds.load('foo.cds')
{
  definitions: {
    Foo: {
      kind: 'type',
      type: 'cds.Integer',
      enum: { a: {}, b: {}, c: {} }
    }
  },
  meta: { creator: 'CDS Compiler v4.5.1', flavor: 'inferred' },
  '$version': '2.0'
}

Expected Behavior
Expected output is not clear either. I would have expected to have the keys enumerated in order, starting from 0 (or 1?). The type should be set accordingly.
Log a fatal error prompting the user to explicitly define values. See comment below. Type could be just number iff we want to make sure the run produces syntactically correct types even in this case.
Steps To Reproduce

create a file:

// foo.cds
type Foo: Integer enum { a; b; c; }

run:

cds-typer foo.cds

check the generated index.ts file and find:

export const Foo = {
  a: undefined,
  b: undefined,
  c: undefined,
} as const;
export type Foo =   // <- syntax error

Environment
- **OS**: Mac
- **Node**: irrelevant
- **npm**: irrelevant
- **cds-typer**: 0.16
- **cds**: irrelevant

|  | https://github.com/<your/repo> |
|:---------------------- | ----------- |
| Node.js                | v19.9.0     |
| @sap/cds               | 7.6.0       |
| @sap/cds-compiler      | 4.5.1       |
| @sap/cds-dk            | -- missing  |
| @sap/cds-dk (global)   | 7.5.1       |
| @sap/eslint-plugin-cds | 2.6.5       |
| @sap/cds-mtxs          | 1.14.0      |
| @cap-js/cds-types      | -- missing  |

Repository Containing a Minimal Reproducible Example
No response
Anything else?
This is probably a rather easily fixable issue by iterating over the entries of integer enums and coalescing the values with their respective index.
https://github.com/cap-js/cds-typer/blob/main/lib/components/enum.js

After conferring with @bugwelle we came to the conclusion that we should not assume an implicit numbering for missing values at this point in time. The compiler may at some point introduce an implicit numbering that could start with either 0 or 1 and would not be resilient to adding new enum values between existing values. So anything we could use would probably produce breaking changes.
While the compiler currently only produces a warning, this should warrant an error from cds-typer, as this is something we currently simply can not provide definitive types for.

To consider: duplicate values?


Enable deploy multiple compute node clusters on one datastore with resource isolation

Is your feature request related to a problem? Please describe.
The current configuration of the RisingWave doesn't allow the deployment of two separate compute node clusters with resource isolation. This limitation makes it challenging to have one cluster solely dedicated to serving online queries without being affected by other batching/streaming tasks. This could potentially lead to delays or bottlenecks, especially in high-demand environments.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

We do have a doc for dedicated serving cluster WIP, @CharlieSYH .

Yeah! That would be nice. Will try it later.

Doc: https://www.risingwave.dev/docs/current/dedicated-compute-node/
Please let me know if any problems.


Tests for string_utf8 standard coder.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @ihji

LGTM. Will add the same test for Java to #8228.

Run Portable_Python PreCommit


Added a couple of resources

I have added a couple of resources to the list.
Full disclosure I am a Microsoft employee, however this commit is my own work and nothing to do with my employer

Hi @Sam-Rowe
Thanks for being here. Please add some description for both of them. Also please change first link this this one: https://channel9.msdn.com/Browse/Series So people can choose what to learn and not refer only to c# series. I hope you got it.
P.s. I'm huge fan of Microsoft
Thanks Again.

Hi @dreamtocode
I have included descriptions as requested.
Have a great day :)


DN4J-8: enable Apoc triggers

@francescoinfante this will enable apoc triggers in pre-prod, looks good for you ?

cc @pierre-etienne-deutsch

Tested by @XavierDeMontis


Issue #15 - Refresh timeline programmatically from a message channel …

…event fired from outside the managed package
You may find it easier to test it by using the boilerplate made in this branch:
https://github.com/ArielS1/ActivityTimelineLWC/tree/feature/refresh_from_event_example
by using flow Create_Case
and lwc refreshDataExample

@ArielS1 I like this contribution, but would like to get some input from you on how to implement it in the package. If you have some time this or next week to have a short call about this?


Fix issue 845: sub-typing behavior for arrays of operations

Fixes #845.
Added details on Expressions page in "Arrays of Callables" subsection, but added a mention on the Types page with a link to the details.

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Lowestcategoryscore
Spellingissues
Scorecard
Processed

articles/user-guide/language/expressions.md
85
52
0
link
:white_check_mark:

articles/user-guide/language/types.md
80
51
0
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Docs Build status updates of commit 6f47150:
:warning: Validation status: warnings

File
Status
Preview URL
Details

ValidatePublishRequest
:warning:Warning

Details

articles/user-guide/language/expressions.md
:white_check_mark:Succeeded
View

articles/user-guide/language/types.md
:white_check_mark:Succeeded
View

ValidatePublishRequest

[Warning-RepositoryOwnerAuthorizedCrendentialInvalid] The owner of the repository https://github.com/MicrosoftDocs/quantum-docs-pr, 'adkinn' no longer has Admin permission to the repository. This has no impact to published pages or Docs site, but may cause potential issues for repository management. To resolve this issue, please ask anyone of Admin permission of the repo to set a new owner on Docs portal (https://ops.microsoft.com).

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Running multiple versions of roots in the same machine

I'm sorry for the noob question: I have multiple projects, running different versions of roots.
How do I make a roots watch of a project made in roots 2.4.1?  The new roots 3.1.0 does not output correctly and the configuration does not seem to force the old version of roots upon roots watch

One solution is to specify the roots version in package.json and then add an alias in your bash profile: alias roots-local="./node_modules/roots/bin/roots", then run roots-local whenever you want to run the version of roots specific to the project you're working on.

Sorry for the late followup, but yeah that should do this trick! Thanks Josh :grinning:

@joshrowley can you be more specific on were is package.json located?. I don't program in this technology, I'm a roots user. How do you manage to keep both versions in the same machine?

A better solution would be to install roots locally: npm install<EMAIL_ADDRESS>(no -g). Then in your package.json (in the root directory of your roots project), add the following to the scripts key:
"watch": "roots watch"

Then you just run npm run watch and it will use the local version of roots (local to the project).

Thanks @Leeds-eBooks: do I have to cd to the directory were the project is before doing the install? will this affect the other, more recent, roots installation?

Yes you do, and no it won't :)

If you don't already have a package.json, you'll need to run npm init in the project directory first.

Excellent! thanks a lot for your help @Leed-eBooks

No problem! Let me know if you have any problems.

 Period. The error log for the —attempted— installation is 1.5MB.
Do you have any idea of which version of Node should I install to get it to run again? I'm trying to use NVM to install an old version and see if I can bring this old project (2 years old) back from the dead.
HINT I have another machine running El Capitán with this project working. Is there anyway that I can use to move the binaries for roots to my machine that may allow me to keep owrking on the project?
Any help is truly appreciated
Tail of the error in the teminal
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make: *** [Release/obj.target/binding/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (.nvm/versions/io.js/v3.3.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)
gyp ERR! stack     at emitTwo (events.js:87:13)
gyp ERR! stack     at ChildProcess.emit (events.js:172:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Darwin 15.4.0
gyp ERR! command "/Volumes/Legacy/Users/ganar/.nvm/versions/io.js/v3.3.1/bin/iojs" ".nvm/versions/io.js/v3.3.1/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Volumes/Legacy/webserver/projects/eck/bocetos/redesign/node_modules/roots/node_modules/node-sass
gyp ERR! node -v v3.3.1
gyp ERR! node-gyp -v v3.0.3
gyp ERR! not ok
Build failed
npm ERR! Darwin 15.4.0
npm ERR! argv "/Volumes/Legacy/Users/ganar/.nvm/versions/io.js/v3.3.1/bin/iojs" "/Volumes/Legacy/Users/ganar/.nvm/versions/io.js/v3.3.1/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! node v3.3.1
npm ERR! npm  v2.14.3
npm ERR! code ELIFECYCLE

npm ERR<EMAIL_ADDRESS>install: `node build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node build.js'.
npm ERR! This is most likely a problem with the node-sass package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node build.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls node-sass
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     /Volumes/Legacy/webserver/projects/eck/bocetos/redesign/npm-debug.log

@ganar
It could also very well be that you might have forgot to install all the necessary dependencies Node.js needs to build native modules, one of which seems to be Node.js itself. According to this line in your error:
gyp ERR! stack     at ChildProcess.onExit (.nvm/versions/io.js/v3.3.1/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:270:23)

You're attempting to build a legacy Node.js project with io.js.
Try running this first:
$ nvm install 0.10 && nvm use 0.10

Then try $ npm install roots once again.
If that still doesn't work, and you still get references to node-gyp in your error log, you might need to install Python (specifically version 2.7, if I remember correctly) as well as Xcode (You also need to install the Command Line Tools via Xcode. You can find this under the menu Xcode -> Preferences -> Downloads. This step will install gcc and the related toolchain containing make)

Do you have any idea of which version of Node should I install to get it to run again? I'm trying to use NVM to install an old version and see if I can bring this old project (2 years old) back from the dead.

You can infer this information from the engines field in package.json on the branch that contains v2.1.4 (permalink) - according to the link, the node version should be greater than or equal to v0.8. (although, I do remember having Node.js v0.10.x compatibility in Roots v2.x)

@declandewet Great answer! So clear and thorough at the same time! Kudos! I particularly appreciate the link to the specific line on package.json with the dependency. I'm a designer that uses roots, not a node developer: the curve to use, and, above all, maintain the projects over time, using this kind of technologies has been quite steep.
My roots 2.1.4 installation is finally up and running, the only change to your instructions that I would appreciate very much  in your answer —for all of us noobs in the audience— is this:
npm install -g<EMAIL_ADDRESS>
It does not work without the -g (global) option, and the roots version has to be specified. Other than that the answer is perfect.


Order details page: order summary is not readable on large screens

Actual Behavior

The order summary is shown with full width. That's why it is hard to assign the labels to the related prices.
Expected Behavior

The order summary is not shown with full width on large screens.
Steps to Reproduce the Bug
Steps to reproduce the behavior:

Create an order as registered user
Go to order details page
Check order summary

has already been fixed


i18n(id): Update customization.mdx translation

Description

Update ID translation guides for customization.mdx file

PS:

I am participating in Hacktoberfest. Please add hacktoberfest-accepted label in this PR. Thank you

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

id
guides/customization.mdx
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


[Event Request] Codeunit 1381 "Customer Templ. Mgt."  - OnBeforeOpenBlankCardConfirmed

Please add the following Event OnBeforeOpenBlankCardConfirmed in Codeunit 1381 "Customer Templ. Mgt."
    procedure IsOpenBlankCardConfirmed(): Boolean
    var
        ConfirmManagement: Codeunit "Confirm Management";
        IsHandled: Boolean;
        Result: Boolean;
    begin
       //>> New event
       OnBeforeOpenBlankCardConfirmed(Result,IsHandled);
       if IsHandled then
         exit(Result);
       //<< End
       exit(ConfirmManagement.GetResponse(OpenBlankCardQst, false));
    end;

    [IntegrationEvent(false, false)]
    local procedure OnBeforeOpenBlankCardConfirmed(var Result: Boolean; var IsHandled: Boolean)
    begin
    end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 12406.


Feature Request: Sticky Header + Often used items on header

If I have been scrolling for a while I can't search new questions anymore until I scroll all the way back up. It would be useful to have a sticky header with a pesistent searchbar. Additionally it have an icon link to a FAQ on about us/stampy related questions, e.g.:
LHS : Stampy Logo only (on click return to main page)
Mid : Search
RHS : Share link, Get Involved, Help Code, discord (moved to unified place instead of bottom right)
Also I would reccomend using unified flaticons for everything for a more syncd and clean aesthetic.

I'm going to vote for a lesswrong style sticky header where if you do a small scroll up it pops up but it's not visible in taking up screen real estate while you're scrolling down. See e.g. https://www.lesswrong.com/posts/orhEa4wuRJHPmHFsR/six-plausible-meta-ethical-alternatives

FTR lesswrong style jumping headers drive me crazy, I had to write custom CSS to disable the annoying feature for myself - so I vote against jumping headers or any floating icons. Happy to be overruled if majority of stakeholders vote for it. (my vote agains infiniscoll  was also overruled - but my solution would have been to have Show more and Back to top link buttons at the bottom of the page if both features were up to me)

I dont really understand what you mean by 'jumping' headers. Do you mean that you would rather that they stayed on screen all the time? The main objective I had in my mind was easy access to the search for new queries.
Also by floating icons do you mean how the discord icon is currently implemented on the bottom right? If so then yeah I am against that as well. Just as it is helpful to have access to the search bar, it is similarly helpful to have constant easy access to the links from the icons which is why I suggested putting them on the bar (not as floating around somewhere on the page).

I was just poking around and found some icons I had in mind. I think just the black and white version which changes to one of the stampy theme colors on hover would look good on the top bar. Maybe just even a black/gray fill on hover. I'll link them here in case they are useful: Share link icon, Discord icon, Get involved icon, Help code icon
There are also various stamp related icons if you wanna stick to the whole stamp theme. Something like a helpful answer gets a stamp of approval, or other kinds of stamps for things like edit, tags, etc. Maybe these can be used on the playful stampy.ai version only. Here are some examples:  Stamp helpful, Stamp heart
There are some animated alternatives, if you guys wanna inject a little more dynamism: share, helpful, code
If this seems like something that is even worthwhile doing I can find more in whatever style you guys like.

LOL! I'm definitely non-ADHD but living in a house full of moderately ADHD-diagnosed people probably skews my perception.
I wasn't around for the vote but FTR, I do agree the infinite scroll feels "overactive."
Not a big fan of the floating Discord button either but always thought it was a "requirement." Is there a reason why it can't be just another icon like the link to GitHub and Coda?
However, I'm not fundamentally opposed to sticky/fixed headers if used properly. Does the sticky header on this GitHub page bug you @Aprillion? In general, I would consider GitHub a pretty minimal distraction site.
On a completely different note... I find the LessWrong website aesthetically pleasing but it took me forever to figure out how to use it. Now that you mention it, all the things popping up were cool but also rather disorienting for me.

Yes, I feel the GH sticky header works nicely and is subtle. Perhaps we can consider something along those lines with the search bar and possibly 3 icons + discord? Having the user scroll all the way back to the top feels arcane.

Happy to defer to cc on this


headerCssClass  being ignored/removed

I am attempting to control the column with with headerCssClass. My header on the page looks like this:
Type

The class property is being removed on render. How do I set the header column width?

Hi, try
Type
A.A.

I'm having the same problem and have tried both versions listen above to no avail.


Running e2e tests with 60 ginkgo nodes causes issues

So last night I tried running the e2e tests against a 5 node n1-standard4 GKE cluster with 60 ginkgo nodes. I saw two obvious problems:

Huge response time spikes from router -

The router is constantly churning because we are creating apps so quickly that it can never fully come up and serve traffic before we hup it again. (This may not be exactly what is happening but it seems that way). This results in us seeing huge numbers of 503s.

Addressing no. 1 and no. 2 above separately...
I don't think no. 1 is actually an issue with the router. A slight, but necessary, tangent here... I've looked at the query and the orange trend line is mislabeled. It represents mean; not max. So keep that in mind. (I'll open an issue for that.) Since requests bound for the controller flow through the router, as with any other routable service, the router's max and mean response times reflect not only response times for requests made to applications deployed via workflow, but controller requests as well. The controller takes a lot of traffic in the course of the e2e tests. Many controller requests run longer than the average application request to begin with, but also consider that in this case you have 60 Ginkgo nodes, each making (typically) multiple requests to the controller per spec, and the controller's got only 5 gunicorn threads running. Poor response times from the controller aren't any surprise under these conditions and I believe they're influencing max and mean response times from the router. Especially when you consider the majority of all requests made from the e2e tests are bound for the controller, controller response times have, by far, the most significant influence on the mean response time from the router. Indeed, if I replicate this test, I see a strong correlation between the router's mean and max response times and the response times from the controller itself (upper left-hand graph showing response time by app). If anything, it may be the controller that needs to scale to better accommodate these tests.
Re: no.2:

The router is constantly churning because we are creating apps so quickly that it can never fully come up and serve traffic before we hup it again. (This may not be exactly what is happening but it seems that way). This results in us seeing huge numbers of 503s.

The router reloads configuration without restarting.  This is from Nginx's own documentation:

Once the master process receives the signal to reload configuration, it checks the syntax validity of the new configuration file and tries to apply the configuration provided in it. If this is a success, the master process starts new worker processes and sends messages to old worker processes, requesting them to shut down.

http://nginx.org/en/docs/beginners_guide.html
However, I do not doubt a preponderance of 503s under these circumstances. It is possible that they originate not with the router, but from the kube-proxy. I'm trying to think of how we can test that.

i wonder if we should make the number of gunicorn threads configurable via an env var and then test it via e2e-runner

fixed mislabeled alias via - https://github.com/deis/monitor/pull/99

so we can influence the number of worker threads via - GUNICORN_WORKERS  via - https://github.com/deis/controller/blob/master/rootfs/deis/gconf.py#L7

Lemme see what happens if I tweak that. Already I'm wondering how we can deal with this gracefully. Is it possible that installing workflow for running e2e tests and for "normal use" require two different configurations? For some reason, that doesn't sit well with me, but I honestly don't know any way around that if our tests are going to put a higher than realistic degree of stress on certain components.

Sure its totally acceptable that these e2e tests may require a slightly different configuration than the standard one. Specifically because we are trying to run these tests as fast as we possibly cna. This also shakes down some of the configuration params that people might want to tweak in a high load situation.

wrt no. 1, the graph doesn't change a whole lot with varying numbers of gunicorn workers in the controller pod, but response times are always low the test applications. If the controller were introducing any latency, I'd expect response times for the the test applications to be affected as well.
As for no. 2, I'm still looking into it.

Once again re: no. 1, I'm going to dismiss this as controller requests that (for whatever reason) are actually long-running. I don't believe the router has introduced any latency because I'd expect to see that affect response times for all the test apps as well, but it does not seem to.
No. 2 has remained more elusive. I've spent the whole day attempting to replicate it...
I've tested with two clusters:

GKE w/ 3 worker nodes (4 vCPU and 15 GB memory each) and k8s 1.2.4
AWS w/ 3 worker nodes (4 vCPU and 16 GB memory each) and k8s 1.2.0

In both clusters, I deployed example-go as a buildpack app and scaled to 2 instances.
No amount of load placed on either setup using ab produced any 5xx errors.
One observation, however, has been that @jchauncey's cluster is pretty old. @kmala has observed difficulties with kube-proxy in older clusters. I'm going to keep an eye out for this issue, but I'm pretty confident right now in presuming the issue to be upstream. When we have more data to back us up on that, we can open an issue against Kubernetes.
I'm going to close this for now, as I don't think there's anything actionable here for router itself. I'm happy to re-open this in the future if evidence dictates we do so.


pull request for e2e test at 12/05/2016 20:45:01

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[Vercast] Search Domains command + minor refactor

Description
This is a feature I wanted to add since  PR #12056 for Netlify. In this 1st pass I have:

updated deps
minor refactor to remove the FetchHeaders "TODO"
utilized mapResult and initialData of useFetch for some cleanup
replaced some push with Action.Push
added the Search Domains command (right now we can only "View" but in future we can add views to configure DNS Records and more

Screencast
https://github.com/user-attachments/assets/d36b97ba-b10d-479f-aaab-265d16888a2e
NOTE
I would appreciate it if someone can add metadata screenshot for Search Domains command as it seems to be using a Dynamic Wallpaper but finding the exact shade is a challenge 👀.
Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Thanks for the update @xmok 🔥
@MaxLeiter do you want to check this?


Table sort

Adding the ability to sort a table by a column. This is not hooked up to the UI yet. This is more of a sanity check before I continue.

@KevinMarren happy to go over this in-person if you'd like.

#12

I've added tests in Table.spec with the latest commit @milemilo .


Proxy not work

I am afraid but it seems like ip is not changing:
import tls_client

s = tls_client.Session(
    client_identifier="chrome_105"
)
res = s.get("http://httpbin.org/ip", proxy="http://6j80wk0dmeef:vsioosoz@<IP_ADDRESS>:7492")

print(res.text)

works fine, try this: https://api.ipify.org/?format=json

works fine, try this: https://api.ipify.org/?format=json

Not work, check pls with http url. It don't change your ip.

have not tried with http link, probably they dont have the support for it yet

most of the websites redirect to https link in any case

works fine, skill issue

most of the websites redirect to https link in any case

yeap but some not


adjust ZafiraListener to display before suite/class/method real time items

https://github.com/qaprosoft/zafira-client/blob/3ec134e3fe1a2c46ab3cc3513c93f6d75a1de869/src/main/java/com/qaprosoft/zafira/listener/ZafiraListener.java#L56
it is suggested to start test registration for onBeforeConfiguration as well, providing temp zafira testname. It should allow much better track failures in prerequisites including logs, screenshots and video recording...
As only test started we have to rename all temp items into exact test name and continue as usual.
As example for detecting such prerequisites you can use: https://github.com/qaprosoft/carina/blob/0d0c5e3bd1a4de3cc09ae87b62b291f6acf7cf31/carina-core/src/main/java/com/qaprosoft/carina/core/foundation/listeners/CarinaListener.java#L217

headless tests already supported in 1.6+ if I remember


Update Trivy and Starboard helmcharts

Supereceded by https://github.com/XenitAB/terraform-modules/pull/1085. Closing.


[Feature] Running the bot on existing pull requests?

I have just installed the bot on our repositories and it seems to work well for new pull requests. Over old ones did not get the comment to sign the CLA. Is it possible to somehow trigger the bot to process those too? I've tried creating a "recheck" comment, but that didn't do anything.

Sorry I spoke too quickly - it seems typing "recheck" works.


sap/suite/ui/commons/networkgraph/Node custom Style and custom Status colors not being rendered

OpenUI5 version:  1.60.5
Browser/version (+device/version): Chrome 71 / Windows 10
Steps to reproduce the problem:

add  aggregations with custom Colors to a Graph
for each Node add addStyleClass()

What is the expected result?
The custom status background are being rendered and additional class is being applied
What happens instead?
Both custom status color and additional class is not being applied.
Any other information? (attach screenshot if possible)
I noticed that these issues have been fixed in version 1.6.1
sap/suite/ui/commons/networkgraph/Node.js
Line 1194
if (this.aCustomStyleClasses) { 			sCustomClass = this.aCustomStyleClasses.join(" "); 		}
Line 743
var sStatusStyle = this._getColorStyle({ 				"background-color": ElementBase.ColorType.Background 			}, true);
Can you please fix these in 1.60?
Thanks
Kosta

Hello @costa-satsati,
Thank you for sharing this finding. I've created an internal incident. The status of the issue will be updated here in GitHub.
Since this issue is not within the scope of OpenUI5, could You create internal incidents instead of GitHub issues in the future?
Regards,
Plamen Ivanov

Apologies for the issue.  By 5th of June the newest Network Graph codebase (1.67) will be downported to 1.60. Please verify after the mentioned date and if fixed close the issue. Thanks! Jan


olm.js broken with emscripten 2.0.5

emscripten 2.0.5 broke olm.js again (build successful, tests fail).
Steps to reproduce the behavior:

make js
cd javascript && npm install && node_modules/.bin/jasmine-node test

têst1 -> { plaintext: 'têst1', message_index: 0 }
hot beverage: ☕ -> { plaintext: 'hot beverage: ☕', message_index: 1 }
☕ -> { plaintext: '☕', message_index: 2 }
.têst1 -> têst1
hot beverage: ☕ -> hot beverage: ☕
..FFF.RuntimeError: memory access out of bounds
    at Hb (<anonymous>:wasm-function[162]:0x10cfa)
    at x (/home/fmd/olm/javascript/olm.js:22:355)
    at N (/home/fmd/olm/javascript/olm.js:88:379)
    at new U (/home/fmd/olm/javascript/olm.js:85:76)
    at /home/fmd/olm/javascript/test/sas.spec.js:25:19
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
/home/fmd/olm/javascript/olm.js:17
if(ia)n=m?require("path").dirname(n)+"/":__dirname+"/",ka=function(b,c){ma||(ma=require("fs"));na||(na=require("path"));b=na.normalize(b);return ma.readFileSync(b,c?null:"utf8")},la=function(b){b=ka(b,!0);b.buffer||(b=new Uint8Array(b));b.buffer||q("Assertion failed: undefined");return b},1<process.argv.length&&process.argv[1].replace(/\\/g,"/"),process.argv.slice(2),process.on("uncaughtException",function(b){throw b;}),process.on("unhandledRejection",q),a.inspect=function(){return"[Emscripten Module object]"};
                                                                                ^

RuntimeError: abort(RuntimeError: memory access out of bounds). Build with -s ASSERTIONS=1 for more info.
    at process.q (/home/fmd/olm/javascript/olm.js:27:55)
    at process.emit (events.js:314:20)
    at processPromiseRejections (internal/process/promises.js:245:33)
    at processTicksAndRejections (internal/process/task_queues.js:94:32)

Expected behavior
têst1 -> { plaintext: 'têst1', message_index: 0 }
hot beverage: ☕ -> { plaintext: 'hot beverage: ☕', message_index: 1 }
☕ -> { plaintext: '☕', message_index: 2 }
.têst1 -> têst1
hot beverage: ☕ -> hot beverage: ☕
..têst1 -> têst1
hot beverage: ☕ -> hot beverage: ☕
.têst1 -> têst1
....

Finished in 0.14 seconds
8 tests, 20 assertions, 0 failures, 0 skipped

Comparing the builds with emscripten 2.0.4 and 2.0.5, these files differ in size:

path
size with 2.0.4
size with 2.0.5

build/javascript/lib/crypto-algorithms/aes.o
31557
31577

javascript/olm.js
40432
40163

javascript/olm_legacy.js
439160
438403

javascript/olm.wasm
153672
153655

Using object files from 2.0.5 and link with 2.0.4 works, object files from 2.0.4 and link with 2.0.5 does reproduce this bug. Therefore, the problem is in the link step (output of javascript/olm.js, javascript/olm_legacy.js, and javascript/olm.wasm).

Adding -s ASSERTIONS=1 and removing --closure 1 from EMCC_FLAGS helped.
The problem is the allocate call in function stack in olm_post.js:10:

RuntimeError: abort(Assertion failed: allocate no longer takes a type argument)
RuntimeError: abort(RuntimeError: abort(Assertion failed: allocate no longer takes a number as arg0)

This issue can be solved by replacing the allocate function with:
return allocate(typeof size_or_array == 'number' ? new Int8Array(size_or_array) : size_or_array, Module['ALLOC_STACK']);

There may be a better solution and I don't know if that's compatible with previous emscripten versions.

This function is compatible with 2.0.4 and 2.0.5:
function stack(size_or_array) {
    var size = (typeof size_or_array == 'number') ? size_or_array : size_or_array.length;
    var ptr = Module['stackAlloc'](size);
    var arr = new Uint8Array(Module['HEAPU8'].buffer, ptr, size);

    if (typeof size_or_array == 'number') {
        arr.fill(0);
    } else {
        arr.set(size_or_array);
    }

    return ptr;
}

Then, there is an opportunity to simplify random_stack:
/* allocate a number of bytes of storage on the stack.
 *
 * If size_or_array is a Number, allocates that number of filler-initialised bytes
 * (zero-initialized if filler is falsy).
 */
function stack(size_or_array, filler) {
    var size = (typeof size_or_array == 'number') ? size_or_array : size_or_array.length;
    var ptr = Module['stackAlloc'](size);
    var arr = new Uint8Array(Module['HEAPU8'].buffer, ptr, size);

    if (typeof size_or_array == 'number') {
        (filler || (x=>x.fill(0)))(arr);
    } else {
        arr.set(size_or_array);
    }

    return ptr;
}

function random_stack(size) {
    return stack(size, get_random_values);
}

https://github.com/emscripten-core/emscripten/issues/7795 says: The allocate() function is great to be removed. Therefore, using stackAlloc seems to be preferable in addition to compatibility with both 2.0.4 and 2.0.5.

Please merge the stackalloc branch of https://gitlab.com/famedly/libraries/olm. It is compatible with emscripten 2.0.4 and 2.0.5. It doesn't use arrow functions anymore, so it should remain compatible with old browsers. Additionally, the branch includes the "simplify Makefile"-change for olm_legacy.js too.

Merged.  Thanks


Adding support for 'hd' hosted domain string

On a couple of occasions I have needed to validate the hosted domain returned by services like google-login. At the moment I am doing a manual check once the token has been validated but it would be great to have a 'verify_hd' option within JWT for these situations. Happy to write a pr but will need some assistance creating the correct JWT::Error message.
Many thanks

@bubbaspaarx This won't be implemented into this gem. The hd claim is not an official reserved JWT claim. Only these will be handled by default in this gem.
There is a list of additional reserved claims for different use cases. https://www.iana.org/assignments/jwt/jwt.xhtml#claims
It looks like the hd claim is a private one.


Peer to peer Review

looks great, I would just suggest adding a border-bottom with some padding in the container with "about us", everything else looks great. :) nice work

looks great, I would just suggest adding a border-bottom with some padding in the container with "about us", everything else looks great. :) nice work

I'll work on that, thank you for your suggestion


[requires.io] dependency update on master branch

did it manually with the script inside so I published all versions :tada:


[BUG] React Native: Not setting correlation headers on fetch requests

Description/Screenshot
Hi
We're trying to integrate our React Native app with Applications Insight but we're facing multiple issues. Mainly, it's not setting correlation headers (Request-Id, Request-Context etc.).
Steps to Reproduce
OS/Browser:

"react-native": "0.63.3",

SDK Version [e.g. 22]:

"@microsoft/applicationinsights-react-native": "^2.3.5",
"@microsoft/applicationinsights-web": "^2.6.5",

How you initialized the SDK:
import { ApplicationInsights } from '@microsoft/applicationinsights-web';
import { ReactNativePlugin } from '@microsoft/applicationinsights-react-native';
import { applicationInsightsKey } from 'react-native-dotenv';

let appInsights;

export function setupApplicationInsights() {
  var RNPlugin = new ReactNativePlugin();
  appInsights = new ApplicationInsights({
    config: {
      instrumentationKey: applicationInsightsKey,
      disableAjaxTracking: false,
      extensions: [RNPlugin],
      samplingPercentage: 100,
      loggingLevelTelemetry: 2,
      diagnosticLogInterval: 100,
      disableFetchTracking: false,
      disableCorrelationHeaders: false,
      enableCorsCorrelation: true,
      enableRequestHeaderTracking: true,
      enableResponseHeaderTracking: true,
    },
  });

  appInsights.loadAppInsights();

  var telemetryInitializer = envelope => {
    if (envelope.baseData.name != null && envelope.baseData.name.includes('heartbeat')) {
      return false;
    }

    envelope.tags['ai.cloud.role'] = 'courier-app';
    envelope.tags['ai.cloud.roleInstance'] = 'courier-app';
  };

  appInsights.addTelemetryInitializer(telemetryInitializer);
}

Expected behavior
We thought this would add the necessary headers to each fetch request and also send the necessary tracking data to the AI backend but it seems we're only getting some data in to AI which is not being correlated with our other services.
Additional context
We managed to get the application to send correlation data by adding this hack before we initialize AI.
  global.fetch.polyfill = false;

But this feels like a bad thing to do and it still didn't correlate the requests in the application map.
We're using react-navigation v5 and are sending appInsights.trackPageView(/*data*/) on each screen change. These page views does show in AI.
So our biggest issues right now are:

Data isn't being correlated correctly in the Application Map view.
Transactions aren't being grouped in a sane way in the end-to-end transactions view. They all seem to fall under the same operation id which we're not sure how to fix.

React Native uses a polyfill from whatwg-fetch, which uses XHR.
As such to avoid double reporting of both fetch and XHR for the same request ApplicationInsights does not instrument requests originating from a polyfill instance.
So you should not need to set global.fetch.polyfill = false as your outbound fetch requests should still be getting instrumented via the standard XHR requests (you should be able to confirm this via reviewing the F12 developer tools (or fiddler trace)
On the grouping / correlation (I think they are probably related), I'll let someone else (@xiao-lix, @Karlie-777 or @kryalama) jump in as I'm going to be unavailable for the next couple of weeks.
If react-navigation supports updating the URL, by default the applicationinsights-analytics extension (included in the main AISKU) will listen to the locationchange event (https://github.com/microsoft/ApplicationInsights-JS/blob/master/extensions/applicationinsights-analytics-js/src/JavaScriptSDK/ApplicationInsights.ts#L679-L689 and enabled/disabled by the enableAutoRouteTracking  config) which update the traceId. So if it doesn't update the URL, you may need to do something similar before calling trackPageView

Hi @niklas-r ,
For the correlation header:  headers should be included if the current domain matches the request domain. If they do not match (CORS), we will check correlationHeaderDomains or  correlationHeaderExcludedDomains to determine if headers are included. Some environments don't give information on currentHost and if this is the case,  domains must be manually supplied to include correlation headers  otherwise no headers will be added. But I am not sure if this applies to your issues, let us know if it works.

@MSNev Thank you for your response. I also have a feeling that the grouping and correlation might be related. You're right about React Native using whatwg-fetch. So you're suggesting that we disable fetch tracking because it's a polyfill and instead use the regular ajax tracking?
There's no concept of URL in React Native since it's compiled into a native app, so I don't think we can make it work with enableAutoRouteTracking. Unless there would be a native component in @microsoft/applicationinsights-react-native which could detect screen changes on the native level, I think we're bound to use trackPageView, which is totally fine.
@Karlie-777 Thank you for your response. We can try to configure correlationHeaderDomains but I'm not sure it's going to work since CORS is not a thing in native apps. But since React Native has done a lot of polyfilling of global objects to make the environment somewhat seem like a browser it might just do the trick.


Bump Dependencies (Plugins, pi4j, Java)

This PR updates various dependencies across the project to ensure better compatibility, enhanced performance, and to take advantage of new features.
Key Changes:

GitHub Actions Workflows:

Updated Java version from JDK 11 to JDK 17 (version from pi4j-os)
Updated GitHub Actions setup for both Gradle and Maven workflows:
Moved from actions/checkout@v2 to actions/checkout@v3.
Moved from actions/setup-java@v1 to actions/setup-java@v4 with Temurin distribution for Java 17.
Enhanced workflows for Gradle and Maven, ensuring smoother builds on the latest environment.

Dependencies:

SLF4J dependencies updated from version 2.0.12 to 2.0.16.
Pi4J libraries updated from version 2.6.0 to 2.7.0 for core, Raspberry Pi, and GPIOD plugins.

Gradle Wrapper:

Updated Gradle distribution from version 6.6 to 8.10.2 for improved build tooling and compatibility with the latest Java and plugins.

This update addresses compatibility improvements and optimizations by keeping the project dependencies up to date.

@dariuszzbyrad can you please check what went wrong here?
https://github.com/Pi4J/pi4j-example-minimal/actions/runs/11418405375/job/31771799870
Run ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-8.10.2-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%

Welcome to Gradle 8.10.2!

Here are the highlights of this release:
 - Support for Java 23
 - Faster configuration cache
 - Better configuration cache reports

For more details see https://docs.gradle.org/8.10.2/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':copyDistribution'.
> Resolving dependency configuration 'default' is not allowed as it is defined as 'canBeResolved=false'.
  Instead, a resolvable ('canBeResolved=true') dependency configuration that extends 'default' should be resolved.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org./

BUILD FAILED in 11s
Error: Process completed with exit code 1.

@dariuszzbyrad can you please check what went wrong here? https://github.com/Pi4J/pi4j-example-minimal/actions/runs/11418405375/job/31771799870
Run ./gradlew build
Downloading https://services.gradle.org/distributions/gradle-8.10.2-bin.zip
.............10%.............20%.............30%.............40%.............50%.............60%.............70%.............80%.............90%.............100%

Welcome to Gradle 8.10.2!

Here are the highlights of this release:
 - Support for Java 23
 - Faster configuration cache
 - Better configuration cache reports

For more details see https://docs.gradle.org/8.10.2/release-notes.html

Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
Could not determine the dependencies of task ':copyDistribution'.
> Resolving dependency configuration 'default' is not allowed as it is defined as 'canBeResolved=false'.
  Instead, a resolvable ('canBeResolved=true') dependency configuration that extends 'default' should be resolved.

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org./

BUILD FAILED in 11s
Error: Process completed with exit code 1.

Check this one:
https://github.com/Pi4J/pi4j-example-minimal/pull/10


[ir_builder] unroll const loops with extent=1

Thanks for contributing to TVM!   Please refer to guideline https://docs.tvm.ai/contribute/ for useful information and tips. After the pull request is submitted, please request code reviews from others in the community.

Please request reviews from https://github.com/dmlc/tvm/blob/master/CONTRIBUTORS.md#reviewers

@yzhliu @were @kevinthesun please review, thanks!

I am not sure if we really want this eager behavior in the ir builder, as it complicates the implementation and makes the user's intention a bit ambiguous.

the reason we do this is that, we can eliminate the backward dependence for false loops(with extent=1) when we inject sync in coproc_sync pass. Actually we improve the coproc_sync to support injecting syncs across the pipelines compared to inject just for neighbors of pipelines, and also we inject syncs based on dependence compared to only consider if they are from different pipelines. that's why we got backward dependence for loops. so these loops with extent = 1 hurt performance badly.
I understand the reason you mentioned. another solution i come up with is that add a new pass to mark all these false loop as unrolled, and also expose a flag to users.
Anyway, I can close these and send a new one based on our discussion result.

I think we should close this. We can, however, enforce unroll of loop with extent=1 in the loop unrolling pass


tasmoadmin, portainer, cockpit are all operational but not the others

OK here's the thing.
If I remove all the domains from Caddyfile and then add them one by one they all get a certificate and work (except Glances which gets a cert but can't connect oddly but checked and not working with Caddy 1 either)
So your addon seems to shit itself if there's more than one domain in there.
My last log is this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] scripts: applying...
[fix-attrs.d] scripts: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
 Add-on: Caddy 2
 Caddy 2 web server
-----------------------------------------------------------
 Add-on version: 0.1.1
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 10 (buster)  (amd64 / intel-nuc)
 Home Assistant Core: 2021.1.4
 Home Assistant Supervisor: 2021.01.5
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting Caddy...
INFO: Setting NAMECHEAP_API_USER to ******
INFO: Setting NAMECHEAP_API_KEY to ******
INFO: Found custom Caddy at /share/caddy2/caddy
v2.3.0 h1:fnrqJLa3G5vfxcxmOH/+kJOcunPLhSBnjgIvjXV/QTA=
INFO: Caddyfile found at /share/caddy2/Caddyfile
{"level":"info","ts":1611276127.0818422,"msg":"using provided configuration","config_file":"/share/caddy2/Caddyfile","config_adapter":""}
{"level":"info","ts":1611276127.0872865,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","<IP_ADDRESS>:2019"]}
{"level":"info","ts":1611276127.0879924,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00023c000"}
{"level":"info","ts":1611276128.2643938,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
{"level":"info","ts":1611276128.2665076,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["logviewer.mydomain.com","portainer.mydomain.com","cockpit.mydomain.com","mydomain.com","tasmoadmin.mydomain.com"]}
{"level":"info","ts":1611276128.2722676,"logger":"tls","msg":"cleaned up storage units"}
{"level":"warn","ts":1611276128.311583,"logger":"tls","msg":"stapling OCSP","error":"no OCSP stapling for [tasmoadmin.mydomain.com]: parsing OCSP response: ocsp: error from server: unauthorized"}
{"level":"info","ts":1611276128.3125632,"msg":"autosaved config","file":"/data/caddy/autosave.json"}
{"level":"info","ts":1611276128.3125944,"msg":"serving initial configuration"}
{"level":"info","ts":1611276128.3126988,"logger":"watcher","msg":"watching config file for changes","config_file":"/share/caddy2/Caddyfile"}

A warning for TasmoAdmin but it still seems to work???

OK here's the thing.
If I remove all the domains from Caddyfile and then add them one by one they all get a certificate and work (except Glances which gets a cert but can't connect oddly but checked and not working with Caddy 1 either)
So your addon seems to shit itself if there's more than one domain in there.
My last log is this:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] scripts: applying...
[fix-attrs.d] scripts: exited 0.
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
 Add-on: Caddy 2
 Caddy 2 web server
-----------------------------------------------------------
 Add-on version: 0.1.1
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 10 (buster)  (amd64 / intel-nuc)
 Home Assistant Core: 2021.1.4
 Home Assistant Supervisor: 2021.01.5
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
Log level is set to INFO
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
INFO: Starting Caddy...
INFO: Setting NAMECHEAP_API_USER to ******
INFO: Setting NAMECHEAP_API_KEY to ******
INFO: Found custom Caddy at /share/caddy2/caddy
v2.3.0 h1:fnrqJLa3G5vfxcxmOH/+kJOcunPLhSBnjgIvjXV/QTA=
INFO: Caddyfile found at /share/caddy2/Caddyfile
{"level":"info","ts":1611276127.0818422,"msg":"using provided configuration","config_file":"/share/caddy2/Caddyfile","config_adapter":""}
{"level":"info","ts":1611276127.0872865,"logger":"admin","msg":"admin endpoint started","address":"tcp/localhost:2019","enforce_origin":false,"origins":["localhost:2019","[::1]:2019","<IP_ADDRESS>:2019"]}
{"level":"info","ts":1611276127.0879924,"logger":"tls.cache.maintenance","msg":"started background certificate maintenance","cache":"0xc00023c000"}
{"level":"info","ts":1611276128.2643938,"logger":"http","msg":"enabling automatic HTTP->HTTPS redirects","server_name":"srv0"}
{"level":"info","ts":1611276128.2665076,"logger":"http","msg":"enabling automatic TLS certificate management","domains":["logviewer.mydomain.com","portainer.mydomain.com","cockpit.mydomain.com","mydomain.com","tasmoadmin.mydomain.com"]}
{"level":"info","ts":1611276128.2722676,"logger":"tls","msg":"cleaned up storage units"}
{"level":"warn","ts":1611276128.311583,"logger":"tls","msg":"stapling OCSP","error":"no OCSP stapling for [tasmoadmin.mydomain.com]: parsing OCSP response: ocsp: error from server: unauthorized"}
{"level":"info","ts":1611276128.3125632,"msg":"autosaved config","file":"/data/caddy/autosave.json"}
{"level":"info","ts":1611276128.3125944,"msg":"serving initial configuration"}
{"level":"info","ts":1611276128.3126988,"logger":"watcher","msg":"watching config file for changes","config_file":"/share/caddy2/Caddyfile"}

A warning for TasmoAdmin but it still seems to work???

@anyone finding this issue:
Reason for the errors seems to be the deprecated DNS challenge provider plugin, which seemed to check all txt records at the same time, individually. Thus locking the domain account.
Solved this with help of the On-Demand TLS feature provided by Caddy.
https://caddyserver.com/docs/automatic-https#on-demand-tls

@anyone finding this issue:
Reason for the errors seems to be the deprecated DNS challenge provider plugin, which seemed to check all txt records at the same time, individually. Thus locking the domain account.
Solved this with help of the On-Demand TLS feature provided by Caddy.
https://caddyserver.com/docs/automatic-https#on-demand-tls


[css] add coloring of @apply support

From @philippelesaux on December 16, 2016 18:9
It looks like themes are not respecting the new @apply rules, at least in regards to color-coding.
Using 1.8.0 stable

edit: This is the default dark theme, but I see the issue in Dracula, Light+, Monokai, and others
Copied from original issue: Microsoft/vscode-css-languageservice#19

Syntax coloring is not provided by vscode-css-languageservice but by a text mate grammar.

Thank you @aeschli for moving this to the appropriate project!

This issue was moved to atom/language-css#130


How to manage breaking changes from main lib for binding?

Now, each binding uses a published crate of main lib, but what would happen if the main lib signature is changed like in #31?
Should the changes in main lib be merged into some "dev" branch, then publish new version of the main crate from approved "dev" branch and then update main crate dependency of each binding, fix binding and then make a pull request to main?

Looking at the coming contributions, I agree on dev branch idea.
Some published API doc for main lib will help facilitate this as well. As it will be more clear about the change/breaking of API.

Or we use a version branching model like https://github.com/elixir-lang/elixir or https://github.com/golang/go/. They has a main branch for development and create a branch per version (v1.0, v1.1, etc). With this way, we can have a breaking change in main (or development) branch and can easily backport a bug to support version.


Fix for duplication of existing error aria-describedby. Issue 1331.

#1331 bottom comment.

please add a unit test

Yes, my bad, I'll do it some time this week.

@pascallapointe would still be great if you could add the unit test.

Unit tests added. Let me know if something is missing.

Close until I got better unit test.


Crash when executing on Mac Mini

Mac Configuration

System Log
Process:               MBPMid2010-GPU-Fix [438]
Path:                  /Users/USER/Downloads/MBPMid2010-GPU-Fix.app/Contents/MacOS/MBPMid2010-GPU-Fix
Identifier:            Lektroniik.MBPMid2010-GPU-Fix
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           MBPMid2010-GPU-Fix [438]
User ID:               501

Date/Time:             2017-05-02 14:24:49.848 +0200
OS Version:            Mac OS X 10.11.6 (15G1108)
Report Version:        11
Anonymous UUID:        15F15266-9FEC-83CC-A4A9-EAB3E42153EB

Time Awake Since Boot: 220 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @rpath/QtWidgets.framework/Versions/5/QtWidgets
  Referenced from: /Users/USER/Downloads/MBPMid2010-GPU-Fix.app/Contents/MacOS/MBPMid2010-GPU-Fix
  Reason: image not found

Binary Images:
    0x7fff6aeed000 -     0x7fff6af24a47  dyld (360.22) <DC81CC9D-651A-3A45-8809-928282052BD3> /usr/lib/dyld

Model: Macmini7,1, BootROM MM71.0220.B07, 2 processors, Intel Core i5, 1,4 GHz, 4 GB, SMC 2.24f32
Graphics: Intel HD Graphics 5000, Intel HD Graphics 5000, Built-In
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A54414C41522D4E5444
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1600 MHz, 0x80AD, 0x483943434E4E4E384A54414C41522D4E5444
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x13B), Broadcom BCM43xx 1.0 (<IP_ADDRESS>.1a6)
Bluetooth: Version 4.4.6f1 17910, 3 services, 27 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: APPLE HDD HTS545050A7E362, 500,11 GB
USB Device: USB 3.0 Bus
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB Receiver
USB Device: Dell USB Keyboard
Thunderbolt Bus: Mac mini, Apple Inc., 26.1

Didn't deployed app properly, libraries are missing.
macdeployqt command from Qt The Mac Deployment Tool should be used to generate the app.
Fix will be provided tonight


bootstrap compatibility

is there a way to use this on other version of bootstrap? my page has different version of bootstrap and the page display are ruined if i try to implement the boostrap needed by the editor. or if i use other version of bootstrap the form for editing doesnt show at all, thank you and god bless!!

which version do you want to use?

bootstrap 3 because my webpage is using bootstrap 3, is there a way i can hard code the css popper so i can maintain my version of bootstrap,  and still have the pop up for editing. thank you

thank you so much for the information i will look into it


Fixing Knight interpreter written in Knight link

On the main page, there's a link to the Knight interpreter, written in Knight, that links to https://github.com/knight-lang/knight/knight.kn, which is broken, as the correct link is https://github.com/knight-lang/knight-lang/blob/master/knight.kn.

Fixed, forgot to close the issue :+1:


VeeValidate 2.0 -> validate() vs validateAll()

Hello,
I wonder what's the difference between methods validate() and validateAll() in VeeValidate 2.0. It is not mentioned in the docs.

validate() is just an alias for validateAll, so there is no difference between them the validateAll was an older API.


[Procrastination]: Github actions

Explain your issue
Eventually change the deprecated functions in github actions and update the workflows
Code of Conduct

[X] I agree to follow this project's Code of Conduct

i have to wait for the github action softprops/action-gh-release to update their action before im able to update the release built workflow, the debug build workflow has been already updated in f335331 on the dev branch


Fix #528

Description
Grant a configuration point regarding the default HTTP protocol to be used for Storage Account connection when eg. checkpointing.
A new property has been added: spring.cloud.azure.defaultHttpProtocol (not mandatory, default value https) to manage this configuration point.
Steps to Test
Unset

Configure a storage account with Secure Transfer enabled
Let the spring.cloud.azure.defaultHttpProtocol be unset
Use the Azure EventHubs Stream Binder specifying the forementioned Storage Account (spring.cloud.azure.eventhub.checkpoint-storage-account=my-storage-account)
There should be no errors when connecting/checkpointing

https

Configure a storage account with Secure Transfer enabled
Set the spring.cloud.azure.defaultHttpProtocol to https
Use the Azure EventHubs Stream Binder specifying the forementioned Storage Account (spring.cloud.azure.eventhub.checkpoint-storage-account=my-storage-account)
There should be no errors when connecting/checkpointing

http

Configure a storage account with Secure Transfer enabled
Set the spring.cloud.azure.defaultHttpProtocol to http
Use the Azure EventHubs Stream Binder specifying the forementioned Storage Account (spring.cloud.azure.eventhub.checkpoint-storage-account=my-storage-account)
There should be the following error when bootstrapping the application: com.microsoft.azure.storage.StorageException: The account being accessed does not support http

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Mizaroth sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report

Merging #529 into master will decrease coverage by 0.11%.
The diff coverage is 9.09%.

@@             Coverage Diff              @@
##             master     #529      +/-   ##
============================================
- Coverage     54.43%   54.31%   -0.12%
- Complexity      651      652       +1
============================================
  Files           158      158
  Lines          2897     2907      +10
  Branches        169      169
============================================
+ Hits           1577     1579       +2
- Misses         1202     1210       +8
  Partials        118      118

Impacted Files
Coverage Δ
Complexity Δ

...nfigure/storage/AzureStorageAutoConfiguration.java
26.31% <0%> (ø)
3 <0> (ø)
:arrow_down:

...igure/eventhub/AzureEventHubAutoConfiguration.java
18.18% <0%> (ø)
3 <0> (ø)
:arrow_down:

...t/core/storage/StorageConnectionStringBuilder.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../core/storage/StorageConnectionStringProvider.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...ing/cloud/context/core/config/AzureProperties.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...nfigure/context/AzureContextAutoConfiguration.java
33.33% <100%> (+8.33%)
3 <1> (+1)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update fff66d9...06913c0. Read the comment docs.


merge package template from Kronos-Tools/npm-package-template

Updated standard to latest version

Current coverage is 87.77% (diff: 100%)

Merging #73 into master will not change coverage

@@             master        #73   diff @@
==========================================
  Files             2          2
  Lines            90         90
  Methods           8          8
  Messages          0          0
  Branches         23         23
==========================================
  Hits             79         79
  Misses           11         11
  Partials          0          0

Powered by Codecov. Last update bb3dfb5...fffb1c5


Fix/13 dockertest reenabled

Fixes #13.

We could enable these tests again, as they will probably run. But they're incomplete themselves, the actual idea was to generate a completely valid DIMR model and actually run it using the FM Docker container automatically. That integration is still missing AFAIK.

@arthurvd On second thought, we do run Docker. See the CI step, which mounts the test ouput at tests/data/output/docker (meaning we can only run a single test for now!). The actual problem is that we don't get the correct error messages from Docker. It currently fails with:
** ERROR  : Observation cross section file 'ObservationPoints_crs.ini' not found!


Babel 6.0 does not create node package "babel"; package is not found

Babel has broken out functionality.
jsx.js line 21 failes to find "babel" when using latest Babel package (installing babel-cli instead of babel)
For latest Babel, should be 'babel-core'
Just something I ran into and thought I would let you know.
Ignore if you want
Thanks for the plugin!

I'm having similar problem. And finally I realized that I should have babel support for my node. I don't think the doc should assume that everyone understands node and babel.

The solution is to install babel 5.8.34. It solves my problem.
npm install --save-dev<EMAIL_ADDRESS>


Hide archived workflows in Console

NamedEntities can now have a state value indicating they are archived. The goal of this is to allow users to archive workflows so that they aren't cluttering up the UI. Supporting this in the UI is fairly trivial (update our list request to add a filter for only the active state).
I also added a test file for ProjectWorkflows and a test to assert that we are filtering to only active workflows and updated the yarn.lock file.

Codecov Report

Merging #71 into master will increase coverage by 0.48%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #71      +/-   ##
==========================================
+ Coverage   58.65%   59.13%   +0.48%
==========================================
  Files         363      364       +1
  Lines        5664     5673       +9
  Branches      847      847
==========================================
+ Hits         3322     3355      +33
+ Misses       2342     2318      -24

Impacted Files
Coverage Δ

src/components/Project/ProjectWorkflows.tsx
100.00% <100.00%> (+33.33%)
:arrow_up:

src/test/modelUtils.ts
100.00% <100.00%> (ø)

src/routes/routes.ts
47.72% <0.00%> (+2.27%)
:arrow_up:

src/components/hooks/useNamedEntity.ts
55.55% <0.00%> (+14.81%)
:arrow_up:

...components/Workflow/SearchableWorkflowNameList.tsx
93.33% <0.00%> (+40.00%)
:arrow_up:

...rc/components/common/SearchableNamedEntityList.tsx
100.00% <0.00%> (+45.45%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d4d9b03...65a1d42. Read the comment docs.


[#546] Update how swiftlint is used

Closes #546

Include swiftlint binary into repository.
Have separate swiftlint config for code and for tests.

This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation).  For more in-depth discussion of how we think about code review, please see Code Review Guidelines.
Author

[x] Self-review: Did you review your own code in GitHub's web interface? Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
[ ] Does the code abide by the Coding Guidelines?
[ ] Automated tests: Did you add appropriate automated tests for any code changes?
[ ] Code coverage: Did you check the code coverage report for the automated tests?  While we are not looking for perfect coverage, the tool can point out potential cases that have been missed.
[ ] Documentation: Did you update Docs as appropiate? (E.g README.md, etc.)
[ ] Run the app: Did you run the app and try the changes?
[ ] Did you provide Screenshots of what the App looks like before and after your changes as part of the description of this PR? (only applicable to UI Changes)
[x] Rebase and squash: Did you pull in the latest changes from the main branch and squash your commits before assigning a reviewer? Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.

Reviewer

[ ] Checklist review: Did you go through the code with the Code Review Guidelines checklist?
[ ] Ad hoc review: Did you perform an ad hoc review?  In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
[ ] Automated tests: Did you review the automated tests?
[ ] Manual tests: Did you review the manual tests?You will find manual testing guidelines under our manual testing section
[ ] How is Code Coverage affected by this PR? We encourage you to compare coverage before and after your changes and when possible, leave it in a better place. Learn More...
[ ] Documentation: Did you review Docs, README.md, LICENSE.md, and Architecture.md as appropriate?
[ ] Run the app: Did you run the app and try the changes? While the CI server runs the app to look for build failures or crashes, humans running the app are more likely to notice unexpected log messages, UI inconsistencies, or bad output data.

I removed Swiftlint binary. I introduced different config for code and tests (same as in the SDK). And I used same configs as are used in the SDK.