Automatically scale components based on metrics

Hello!
It is not clear to me how to horizontally scale single components. Is this something we need to handle ourselves based on exported metrics or does the operator manage this somehow?
Are there any known best practices from people with high volume of traces?
Thanks!

Hi, right now it is not automatic and you should scale the components manually via created CR.

We do have auto-scaling in the roadmap, though.

#856 added support for autoscaling on the collector.
Stop me if I'm wrong, but I suppose this is groundwork for other components as well? I'm particularly thinking about the ingester, obviously.
I'll use autoscaling on the 1.17 release, and will be very happy to provide feedback, if anything doens't go the way expected.

That's absolutely right. If HPA works as expected, we can apply the same idea to the ingester.

This has now been implemented in #856 (for collector) and #1006 (for ingester). Feel free to reopen if something is missing.


"Inclusions" Feature

whenever I put the video link there and then I enabled it, the video I'm watching with the same link doesn't show on my discord status

Do you have this setting on?

And if so, make sure the link you put into the box contains no spaces and that it is in the first box. The second box is for when you want to include videos that have a key word in the title or channel name only.

I have that enabled and added the link to the "first box" and it doesn't show on my Discord Status

Thank you for bringing this to my attention and sorry for the delay! I've fixed the error and the extension will be officially updated shortly.


Facebook og data does not work when $fallback_url is used

It appears that Facebook will try to get the og data from the fallback_url and not from the branch link.

Interesting. I just saw this in our code too. If you use $desktop_url, $ios_url and $android_url, your OG tags will be respected. I hesitate to change this now since it's been live for about 7 months. Sorry for the surprise @zanemcca !

Yeah that is the workaround I started using.

Sorry about the confusion 👎

Thats alright. It would be nice if this info was available in the documentation as well.

Got it on my todos


[Analyzer] switch on FutureOr<T> marks case T value as unmatchable

Though it does properly detect that it matches all cases. On SDK 3.1.0-48.0.dev:
Reproduction:
import 'dart:async';

int foo(FutureOr<int> future) =>
    // The matched value type 'FutureOr<int>' can never match the required type 'int'.
    // Try using a different pattern.dart(pattern_never_matches_value_type)
    //                vvv
    switch (future) { int i => i, Future<int> _ => -1 };

void main() {
  print(foo(123));
  print(foo(Future.value(1234)));
}

https://dart-review.googlesource.com/c/sdk/+/302442


Change security slack notifications to alert based on open code scanning results

Right now our Trivy code scanning workflow will send Slack alerts based on whether the Trivy CLI finds any unresolved issues in our images/binaries. It also posts them to GitHub's Code Scanning tool for our repo, which allows us to mark them as resolved/wontfix.
The problem is that if we have a wontfix it will be closed from GitHub, but Trivy will still report it as present. If we could trigger based on the open Code Scanning tickets instead we could have a better picture of unresolved items. It looks like it should be possible using GitHub's API.
If we get this working we should also fix this with other Carvel projects.

This turned out to be slightly more complicated than I thought since we're scanning the latest release as well. I don't think there's a good way to associate a code scan alert with a release, so for instance if we had a fixed vulnerability in develop but that was still vulnerable in the latest release, I'm not sure it's simple to distinguish where it's fixed

Reopening since this is gonna bother me forever. I looked into it a bit today but was blocked by https://github.com/github/codeql-action/issues/890. There looks like there will be a fix there shortly so I'll revisit once that's merged.


Update README.md

Changed my github handle so I'd like reference to my previous work to be updated to reflect that, thanks!

Hi Ruth,
I've rectified this in the recent update. Thanks


Make the history and completion lists prettier

Fixes https://github.com/mozilla/tofino/issues/1171
Signed-off-by: Victor Porof<EMAIL_ADDRESS>

Looks good!


Postprocess navmeshes to work around engine nav mesh baking bugs

Stop-gap fix for #264 until the underlying engine issues are fixed.

Thank you. I'll merge it in. Functionally this is better and addresses the broken nav mesh generation and the errors. However cosmetically, this creates holes in the nav mesh that aren't there without this post processing. They're all over the place.

They are cosmetic only, as the enemy will happily traverse them.
https://github.com/TokisanGames/Terrain3D/assets/632766/da927b65-7143-40e4-a72d-9ace61eeb467
Do you want to close #264, or mark it as waiting for godot?

Those holes are just where the navmesh debug polygons drop below the surface of the terrain. If it appears to be new, it's probably just because vertices have moved by up to 0.25 units.

Do you want to close #264, or mark it as waiting for godot?

Whatever you prefer! We could close it. I'm subscribed to the Godot issue, so when there's a fix I'll get a notification and we can reopen #264 or create a new issue.

I tested with and without, and the visual holes are definitely there only after post processing. They make it difficult to determine where the nav mesh is not generated due to slope. ¯\_ (ツ)_/¯

vertices have moved by up to 0.25 units

Where does this happen?

Where does this happen?

_postprocess_nav_mesh_round_vertices rounds vertex coordinates to the nearest cell_size/cell_height. The default value for cell_size & cell_height is 0.25.
They're not really holes, they're just the terrain poking through the nav mesh.


How GPU-accelerated video processing with ffmpeg

Q
A

Bug?
no

New Feature?
maybe

Version Used
0.18.0

FFmpeg Version
7:3.4.8-0ubuntu0.2

OS
Ubuntu 18.04

Actual Behavior
How GPU-accelerated video processing with ffmpeg?
Expected Behavior
ffmpeg use GPU for accelerating
Steps to Reproduce
I use this parameters but I get Encoding failed
$format->setAdditionalParameters(["-hwaccel cuda"]);

I also have the same doubt

You can use this code if you want to process video with GPU-accelerated
Example
$format->setAdditionalParameters(['-c:v', 'h264_nvenc']);

There's have 3 codecs that supported encoding with GPU and 1 codec if you want processing with cpu

libx264 (Encode with cpu)
h264_qsv (Encode with Intel GPU)
h264_nvenc (Encode with Nvidia GPU)
h264_amf (Encode with AMD GPU)

macos
ffmpeg -hwaccels
ffmpeg version 7.0 Copyright (c) 2000-2024 the FFmpeg developers
Hardware acceleration methods:
videotoolbox
macos下貌似只有这个 videotoolbox 来加速


Allow to send multiple log messages in a single HTTP request

Problem Statement
The maximum throughput for https-based syslog drains is limited by the message roundtrip time:
max_logs_per_second = 1 / message_roundtrip_time_in_seconds.

This is a consequence of the syslog agent using one connection per drain and sending http-requests sequentially.
This limits the throughput especially in high latency scenarios. Messages are buffered if the message rate exceeds the throughput. Once the the syslog agent buffer is full, all messages are dropped.
Proposal
To increase the throughput and avoid loss we propose to introduce an option that allows the agent to batch multiple log messages into a single HTTP request.
@bgoerzig @juergen-walter @nicklas-dohrn

We are open to contribute this feature if our proposal is accepted.
Since the syslog RFC 5424 doesn't specify a batched format we have to define a structure that is accepted by the community.
From our point of view, the easiest implementation would be to use multi-line batches.

Hi @bgoerzig, thanks for taking the time to write up this proposal. I think https is the least optimal of the schemes that Syslog Agent offers for streaming syslog messages. Because of that we typically encourage use of the other schemes. May I ask why you're so interested in using this scheme in particular?
My first take is that we would be open to a PR to change the https scheme to batch messages, as long as the change is feature-flagged. AFAIK there's no RFC for syslog over HTTPS, so our implementation of it is already special and there's nothing stopping us from making it more special. Feature-flagging the change would be necessary because otherwise we're talking about a breaking change for pre-existing https drains. Multi-line seems like a reasonable implementation approach as well.
I need to re-read up on these schemes, I can no longer recall exactly why https is less optimal than the others 😅.

We've discussed the same issue in our team when @fhambrec and @dark5un were doing Syslog Agent performance tests. The difference between the unencrypted and encrypted traffic and the protocol https vs syslog-tls issignificant. That's why our end recommendation is to use syslog-tls scheme foe higher loads.
We've talked about the possible improvements, thought about batching messages in single requests as well, but the we think that's not the way to go, as there is nothing defined in the Syslog RFC and the client (Syslog Agent in our case) amd the server (3rd party Syslog server) would both have to know how to pack and unpack the request body. As we only control the client in this case, we've concluded that this solution is not the right one.
At the end, our discussion went into direction of refactoring Syslog Agent's egress so that we have roughly speaking a connection poll with load balancing. The Syslog agent opens multiple connections and sends the messages in parallel. We can revive topic in our team ans see what can we do about it.

I need to re-read up on these schemes, I can no longer recall exactly why https is less optimal than the others

The reason that http drains perform badly is that the requests are sent one after the other over one tcp connection. The throughput is therefore 1/(roundtrip time) which is less than 200/s inside an AWS datacenter. We reproduced that in performance tests. With syslog > 4000/s could be sent (independent if it is with (m)tls or not).
I see three options to overcome this, maybe there are more:

Using more than one connection for an http sylog drain.

Advantage: Server behaviour unchanged, they can just receive one line per request like currently
Disadvantage: Handling of connection pool, unclear how big it should be; order of logs may get lost

Batching the requests, sending all available requests via one http request

Advantage: (Relatively) simple to implement on syslog agent side
Disadvantage: Non-standard, therefore adaption on server side needed

Using http2

Advantage: Standard way to de-serialize http request over one connection, simple to implement on syslog agent side (just using https://pkg.go.dev/golang.org/x/net/http2)
Disadvantage: ?

I would favor http2. We had already planned to look into it on SAP side. This is in my opinion the most standard way. We could e.g. add the scheme "https2" to the list addiotionally to https, syslog and syslog+tls

My first take is that we would be open to a PR to change the https scheme to batch messages, as long as the change is feature-flagged.

I would go one step further and would request that the feature is per drain. We are running multi-tenant foundations and cannot break existing customers using an http syslog drain. Maybe an option would be to configure it with a query parameter in the syslog drain url (like the drain-type).

Thank you for the refresher @stefanlay!

I would favor http2.

I agree with this. Using http2 seems the more "standard" way to pump up the performance of this drain option.

I would go one step further and would request that the feature is per drain... Maybe an option would be to configure it with a query parameter in the syslog drain url (like the drain-type).

That's a very reasonable request. I'm in favor of this as well.

Howdy!
Just want to inject some context and thoughts.
Firstly, honestly speaking, I'm very much not opposed to adding the ability to batch into the syslog-agent code base. Not only do i suspect that batching will give us huge performance gains for https drains, if and when we start to look more into adding additional protocol support to the drain-agent(syslog-agent) we'd have a reusable consistant tool which we could easily add to other interfaces that require or would benefit from batching(such as for example, otlp).
Back in cf-for-k8s times, we spent a lot of time looking into our path to shared nothing for log-cache. As we were working on deprecating the firehose and moving over to syslog, and we saw that the performance of syslog ingress for log-cache was somewhat abysmal. The syslog server could accept traffic quite rapidly and efficiently but the GRPC throughput from syslog-server to log-cache was horrendous. The way that we fixed that performance bottleneck is to batch envelopes from the syslog-server to the log-cache rather then send them one by one. I think it's easy to look at this and apply the same lesson to http drains, and while performance testing seems reasonable, I highly suspect based on this that our performance will show marked increase.
The main reason I feel like we have not pursued this is just the general lack of priority and interest in https drains in general. Https drains are I think still largely something I see as a "proof of concept" that happens to be present in production code. I'm not aware of a rfc supported method to send syslog over https in general. It seems like we "send syslog formatted messages" over https, and so does heroku(!?!?!?), but you'd think anyone who uses https as their interface would prefer fully formatted json messages. As I say this, there's some point about the concern of adding performance cost to the drain agent from marshalling messages into json(something we've seen can be extremely costly), but I digress. As long as we're shoving syslog formatted messages into a json message, https feels a bit awkward to me.
There's a second thing that makes it feel like a proof of concept interface. Internally, the model use case for http drains is and somewhat has been sending logs and metrics to a aws lambda service. Now I did a little research and one thing I noticed is that lambda doesn't support http2. Now this isn't necessarily a problem, as far as I understand no actual user has set up a aws lambda service to accept their logs and metrics. One major problem is I'd suspect such a use-case would be extremely extremely expensive. But I'd be interested in some sort of mental model and use-case explanation to replace the existing one I have, and I wonder if in pursuing that mental model and use-case we could come up with possibly more acceptable models and solutions. Right now we're talking about how to better support performance with http, and we might go into a solution workflow where we do continue to support https, or support http/2(s), but I could imagine us also talking about other protocols that still don't require tcp level routing but still would be a good community standard, for example.
Now as for the configurability of batching, I really do think that unconfigurable could and probubly would be fine. We've gotten away with universal batching size for v2 loggregator for a long time now, and in fact, not configuring the size of the batches also means we don't have to configure the size of our grpc buffers either(although we did have to change them to be accurate). I don't even think we have to specifically tune them per say to be the most performant, I think in many cases good enough will be good enough. The biggest risk in my mind would be users who expect 1 envelope and suddenly start receiving say, 100, and stop processing lots of envelopes.
Let me know what you think though.

Sorry for taking so long to move on this topic, we now have a draft proposal ready to talk about this improvement once more.
We did some testing on our side with a custom built loggr-syslog-agent binary which contains the changes I provided in this draft PR:
https://github.com/cloudfoundry/loggregator-agent-release/pull/491
These changes only implement the syslog-batching approach we described above, with a pretty minimal and non invasive code change to be enabled via query parameter for a user-provided-service.
Please let me know what you think of this approach, and how we could improve it to make it a contributable part of the coming loggregator versions.
Greetings, Nicklas

It's probably not going to have as big an impact as batching, but I found that we were not using fasthttp appropriately in our HTTPSWriter. That may have had a negative impact on the performance of Syslog Agent's HTTPS drains. Should be resolved in this PR: https://github.com/cloudfoundry/loggregator-agent-release/pull/573.

@nicklas-dohrn I've re-read through this issue and the current implementation of Syslog Agent, and I think #491 is slightly off track.
Instead of using a new batching=true query param in the syslog drain URL to indicate to the HTTPSWriter that batching is enabled, a new protocol should be defined. I like https-batch, but open to other naming schemes. Then syslog drain URLs matching https-batch://..., for example, will be redirected to a HTTPSBatchWriter, or equivalent, that will batch messages over HTTPS using \n as a separator.
The reason I think a new protocol would be better is twofold:

The current implementation doesn't have other examples of using query params to change the behaviour of the writers. That all happens at higher levels.
Conceptually, we are defining a new communication protocol here: multiple syslog messages separated by newlines delivered in the same HTTPS request.

Yes, looking from a more broad perspective, I see the appeal of having it split out from a higher up point in the call chain.
I will look into how I can incorporate this way of switching Writers, but from thinking about it from the top of my head right now, this should be rather straight forward to be implemented.
I will come back to you, if I have a fledged out draft on how this could be realized, And if there are any points in the whole chain of touched systems that prevents us from using it like this.

It's probably not going to have as big an impact as batching, but I found that we were not using fasthttp appropriately in our HTTPSWriter. That may have had a negative impact on the performance of Syslog Agent's HTTPS drains. Should be resolved in this PR: #573.

@nicklas-dohrn and other folks on this issue, what do you think of this change?

I think that might prove helpful on the issue, but will for sure not resolve our issues, as we are currently allowing cross consumption into different availability zones, like from US to EU or else.
Sending single log entries with single https requests is depending on the size of the logs mostly inefficient, and might even be costly on datacenters with high IO costs.
We also have seen a positive impact on our routing infrastructure, as having bundled logs sent through nginx is way more efficient.
I will nonetheless try out this approach with my dev setup and see how it performs in our usecase, as the only comparison I have found so far is:
https://github.com/nurmohammed840/web-benchmark?tab=readme-ov-file#go-v116-linux
From what I guess so far, is that it would increase the throuput probably quite substantially, but  I doubt it will increase by more than 200%, and we unfortunately likely need way more than that (at least 5x).
but I will come back to you with my results, once I have some :)

Thank you!
I understand, the batching PR is still desirable.

I tried it, yes, was not really conclusive yet.

I meant to close #573 not this Issue. My bad. This issue is prioritized.


Update protobuf dependency to 3.2.x

Looks great to me but I'd like at least one of @nicolasnoble and @dgquintas to also review and approve.

Abandoned — in favor of the parallel/superset pull request #9821 that aims to update protobuf.


Problem generating correct swagger.json

Hi!
I'm experiencing something I think is a bug. It's a bit complicated and hard to explain but I'll try my best. I have provided a repo to reproduce the issue here.
In a project our objects have an Id of type ObjectId; the why of it is irrelevant for the question; it is how it is. I can use this ObjectId in a route (e.g. /foo/bar/{objectid} and it works fine when posted as a property of an object (e.g. Customer.Id). However, I can't get it to work correctly as a querystring argument (e.g. /foo?id=123). That is: the swagger json doesn't seem to line up correctly and so the Swagger UI doesn't generate the correct request.
The following reproduces my issue(s):

The ObjectId isn't even picked up unless I use [FromQuery] attribute (expected: 2 arguments, id and name, only name is picked up)
When I use a [FromQuery] attribute the argumentname is picked up as IsNew which happens to be the first property on ObjectId (expected: id)
When I use a [FromQuery] attribute with an explicit name (e.g. [FromQuery(Name = "id")]) the name is ignored

Whenever I change the url, changing IsNew to id (e.g. https://localhost:44373/Test/testgetquerystring2?IsNew=123&name=abc => https://localhost:44373/Test/testgetquerystring2?id=123&name=abc for the second case for example) it works as expected.
When I change ObjectId to string it works fine, same when I change to long and even changing to Guid (which more closely resembles an ObjectId since it's also a struct) works just fine.
So my question is: am I doing something wrong or missing something? What is the difference between ObjectId (not working) and string or long (working) and even Guid (working, also a struct like ObjectId). Or is this maybe a bug?
P.S. Sorry for the title; I'm having a hard time describing this issue in a single line...

🤔hmmm, when I change the IsNew property to an IsNew() method then 2 and 3 (both using the [FromQuery] attributes) seem to work correctly, 1 still doesn't pick the argument up and only shows the name argument.

Technically this is a dup of #1864 - or at least the route cause is the same. Swashbuckle relies heavily on the metadata that's surfaced by ApiExplorer, part of ASP.NET Core. And unfortunately, that component does not honor custom model binders. That is, it doesn't know you want the ObjectId instance to be represented as a single query parameter. Instead, it describes it as multiple query parameters - one for each property of the class because this is the default model binding behavior for complex types.
I guess you could say this is a bug but I can also understand why they don't because it's challenging to determine serialization behavior that's defined by runtime code as opposed to static constructs like attributes, classes, method signatures etc. Furthermore, they recommend a TypeConverter as opposed to a custom model binder for a simple string -> SomeType mapping as per the model binding docs:

We recommended you create a type converter if you have a simple string -> SomeType mapping that doesn't require external resources.

This is a very simple change (see #1864 for an example) and if you're in a position to do it, then this will solve your problem as ApiExplorer does honor Type Converters. If not, your options are a bit more limited and you're probably looking at hooking into the Swagger generator and modifying the Operation parameters with an IOperationFilter (see readme).


Authenticator helps

Setup

TODO, No settings

Helps
Q: What is Open Authenticator?
A: Open Authenticator is an open source and secure TOTP authenticator.
Q: How to contact or report a problem
A：Send an email to<EMAIL_ADDRESS>or create a new Issus.

How to get authentic code

How to get authentic code

@naledzanimarubini Here 👉 https://github.com/odroe/ootp/tree/main/open-authenticator Download APK for Adnroid / App Store search Open Authenticator for iOS, Or you using flutter compile a copy by yourself

How can I get a otp


Still active?

Since you started this because others were abandoned (and now you are the top search result), I wondered if this package is still in active development.
Would also love to contribute somehow :)

Well I'm not sure about the package, at the very least I'm still active!
I believe all the features that existed in March should be supported, but there may be newer ones that I don't know exist. If you come across any, feel free to let me know and I'll add support for them.
Regarding contributing, I was unfortunately unable to find a solution for #12 so far. If you somehow manage to it would be great.

I'll have a look at it :)

You can solve it by generating a python file for #12 .
https://github.com/GitHub30/win11toast/issues/20#issuecomment-1462045834

You can solve it by generating a python file for #12 . GitHub30/win11toast#20 (comment)

Certainly interesting but also possibly veering towards being too invasive. I'll keep this open in case any better solutions come around, but will consider it. Nice library by the way.


Updates to dependency tracking to work with the fs-merger.

This PR builds on top of the typescript port in PR #190. You should only review the commits starting with Use the fs-merger facade in dependency tracking. in this PR.
This PR also requires that we land https://github.com/SparshithNR/fs-merger/pull/35 and require that new version to be used. This project doesn't have a production dependency on the fs-merger package so I'm not sure what the best way to accomplish that is (maybe a runtime check? maybe a peerDependency? Maybe release a new version of broccoli-plugin that bumps the dependency spec for fs-merger).
Overview of Changes
The dependency tracker was conceptually well aligned to use the FSMerger because it tracked files outside the tree separately from files inside the tree. The dependency tracker allows relative paths which are assumed to be relative to the file the dependencies are being registered against. It also allows absolute paths to be provided as dependencies. The public API for setting dependencies made no distinction for the caller about "paths in the tree" vs "paths outside the tree", instead it sorted that out for them. Given that broccoli-plugin still exposes inputPaths, I think we have to be able to make sense of absolute paths in general without putting that onus on the API user.
As noted above, I've submitted a PR to the fs-merger to allow me to take an absolute path and check if it's part of any input tree. I think this is a good compromise since it doesn't expose the root paths of the fs-merger, rather it will only confirm them if the caller happens to have a reference to one of the root paths.
You'll note that the new utility function resolveRelative raises an error if you try to create a relative path that escapes the local filesystem root. I feel like this is an important abstraction boundary and I worry about trees generally trying to read from other trees that aren't in the input trees if we don't create a firm boundary around reading relative paths through the fs-merger (fwiw, the fs-merger doesn't currently enforce that boundary -- I think that's a bug, the semantics of reading ../foo.txt from all of the input paths to the merge seems ill-defined to me).
The result of not allowing relative paths to escape the input tree technically constitutes a breaking change. But I don't think that in practice it will be one, since the dependency API is not widely used (I might be the only user and I never do this in any of my code). I leave it to your judgement about whether you should bump the major version because of this.
This PR also changes the serialized form of dependencies . I handle this in the code by refusing to deserialize any cached dependency tracking from older versions of the code. This will cause the first build after upgrading to be slow (it was probably already invalidated through other means but I wanted to be sure I wouldn't cause an error).
Let me know if you have any questions or concerns.

Note: The tests are failing because the dependency on https://github.com/SparshithNR/fs-merger/pull/35 hasn't landed. It will pass locally if you yarn link my branch to this code.


Fusion 360 stops working after a while

Describe the bug
The Fusion 360 works fine for some time, the parts can be modeled, everything works well. However, suddenly, for some reasons I cannot detect, the graphical area becomes gray with rendering glitches.

When I try to open Preperences, firstly I get the message below, and then the Preferences are opened:

When I try to save the file, I'm getting the dialog with corrupted visual elements:

Also an error message appears in the bottom corner:

And when I open the file, I get the message that the file is corrupt:

To Reproduce
Steps to reproduce the behavior:

Just use it as usual
Try to lock the screen
Leave the part opened for some time, 30 min or so
Try to save the part
Or open another one
Gray glitches may appear
Kill and restart Fusion
Everything works well again for some time

Expected behavior
No graphical issues. No interrupted workflow.
Screenshots
See above.
Desktop (please complete the following information):

Version number of Autodesk Fusion 360: 2.0.15509 x86_64

Graphics card model + Graphics card driver (Version number):

Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 620 (KBL GT2) (0x5917)
Version: 22.3.7

Operating system (OpenSUSE Leap 15.3, Fedora 34, ...): Fedora 37 Workstation

Desktop environment (XFCE 4.16, Gnome 40, ...): GNOME 43.3

DXVK- or OpenGL-Mode: both

Wine 8.2, 8.4

Additional context
Probably the issue is somehow related to #299.

I have no problems with graphics, but after 30 minutes of work I get the same error when trying to save the project. STL model is not saved either.
This is a very annoying bug! Imagine, you've been working on a model for a long time and then it turns out that you can't save your progress.
Error: D:\Stage\workspace\protein\release\2021.10.R2023\protein\src\libs\protein4\archiveadaptor.cpp(210)stream can not open!!
Error: ParaMeshBlobSerializer - createZipPartFromFile failed!

Error: Autodesk Translation Services failed to translate the current document to stl file!
Error: Translator failed to export data

OS: Manjaro
GPU: NVIDIA GeForce GTX 1650
Fusion 360: 2.0.15509
Wine: wine-staging 8.4
DXVK or OpenGL: both

@wu5, did you try the workaround with an SD card, mentioned in #299?

It seems to be working with microSD card through a USB card reader. I kept Fusion 360 open for about an hour and the save did not show any errors.

I run into this issue even on a machine that does not have an SD card reader. It does have additionally mounted drives. wine-8.12.

I have testing in the Network-Settings of Fusion360 directly "no proxy" and "Server verification " i have changed to "No warning when accessing via an intermediate server".
I hope, this is the correct english Translation (in German: "Serververifizierung: Beim Zugriff über einen Zwischenserver keine Warnung ausgeben").
An that is the solution for me, on two different computers, even after a restart. I was working over 1 hour, with no crash and i can always save and export my work.
I have Zorin OS 16.3 (Ubuntu-based)

I can confirm that solution related with network setting work for me. I had mentioned issue immediately 1-2 minute after start of fusion, now i can save document without problem longer time after start.

I can confirm that I am still experiencing this issue.
Fusion 2.0.19215 x86_64

I am experiencing this issue, both graphical and inability to save after X minutes, every time I try and use it. It gives an error of:
Error: Got an unknown exception during persistence Protein Assets to a local file on disk!
Error: ParaMeshBlobSerializer - createZipPartFromFile failed!
Error: DesignConfigurationTableBlobSerializer::doSave - createZipPartFromFile failed!

I just found this thread, so going to test out some of the workarounds and report back if it fixes for me.

Please check here: https://github.com/cryinkfly/Autodesk-Fusion-360-for-Linux/issues/362#issuecomment-1889835832


(WIP) Fix #1469: (createTable deser exposes table command) add tests, change deserialization logic

What this PR does:
Adds reproduction of #1469 to show the issues, and changes deserialization to defer validation failures after APIFeature check.
Which issue(s) this PR fixes:
Fixes #1469
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated
[x] CLA Signed: DataStax CLA

Fix here works but not completely convinced we want to take this approach -- however, if we do want to solve the issue something like this is needed.

PR hard to merge due to concurrent refactorings -- leaving open in case it needs to be revived; if so, will probably need to re-create.

Due to concurrent refactorings, pr no longer maintainable: will close.


Typescript error with Windicss attributify

I am trying out solid + solid-start + typescript + WindiCSS attributify mode, all latest versions.
Attributify mode lets you define tailwind classes as html attributes
const HeaderMenuButton = (props: Props) => {
  return (
    <div flex="~" align="items-center" lg:display="hidden" p="r-4">
      <button
        p="1"
        flex="~ items-center"
        hover:text="gray-900"
        focus:outline="none"
        focus:shadow="outline"
        transform="~"
        transition="scale duration-300 ease-in-out"
        hover="scale-105"
        text={props.raised() ? 'gray-800' : 'white'}
        onClick={props.onClick}
      >
        <Icon class="fill-current h-6 w-6" />
      </button>
    </div>
  )
}

There is a "conflict" between Solid's JSX.HTMLAttributes.align and WindiCSS align attribute (and possible others).

Is there a way to override solid typescript definitions for JSX? Or any other way to tell typescript to allow a simple string.

I guess I can avoid this problem by using a prefix for windicss attributes, but that's kinda ugly. There's gotta be a better way!

On the positive it looks like align has been deprecated a long time ago. It is supported in Microsoft Edge though but nothing else.
I wasn't able to find it in types of other JSX libraries so I can likely just remove it. I don't know what other conflicts there would be. Although I imagine other libraries would hit the exact same problem if Windi chose to use other existing DOM attributes.


Nicer error message  / workaround when the dbname is passed as an argument.

The error is "normal", postgres is not a valid dsn.
In psql, using a database name as the argument of the program connects to the database.
Maybe we could do that or make a nicer error message.
(pgactivity) [vagrant@pgluq pg_activity]$ pg_activity -h /tmp -U postgres postgres
Traceback (most recent call last):
  File "/home/vagrant/tmp/pgactivity/bin/pg_activity", line 306, in <module>
    min_duration=options.minduration,
  File "/home/vagrant/tmp/pgactivity/lib64/python3.6/site-packages/pgactivity/data.py", line 408, in pg_connect
    hide_queries_in_logs=options.hide_queries_in_logs,
  File "/home/vagrant/tmp/pgactivity/lib64/python3.6/site-packages/pgactivity/data.py", line 153, in pg_connect
    cursor_factory=psycopg2.extras.DictCursor,
  File "/home/vagrant/tmp/pgactivity/lib64/python3.6/site-packages/psycopg2/__init__.py", line 126, in connect
    dsn = _ext.make_dsn(dsn, **kwargs)
  File "/home/vagrant/tmp/pgactivity/lib64/python3.6/site-packages/psycopg2/extensions.py", line 167, in make_dsn
    tmp = parse_dsn(dsn)
psycopg2.ProgrammingError: invalid dsn: missing "=" after "postgres" in connection info string

Merged #195


ENH: Support reading a mesh of non-3D points from a .vtk PolyData file

itk::MeshFileWriter does allow writing non-3D points to a .vtk file, so it
appears both reasonable and useful for itk::MeshFileReader to allow reading
those points back.
Implemented by setting the PointDimension within MeshFileReader::GenerateData(),
and tested by GTest VTKPolyDataMeshIO.SupportsAnyPointDimensionGreaterThanZero.
Related to issue https://github.com/slicersalt/ITKShape/issues/8 "Add 2D mesh support" by Matt McCormick (@thewtex).

For the record, the initial "itkVTKPolyDataMeshIO.cxx" commit (9403e3b37a2250fe6fa2ef61de7c19cf014689ba, "ENH: Add mesh IO", 26 August 2011) already prevented reading non-3D points from a .vtk file: https://github.com/InsightSoftwareConsortium/ITK/blob/9403e3b37a2250fe6fa2ef61de7c19cf014689ba/Modules/IO/Mesh/src/itkVTKPolyDataMeshIO.cxx#L175
this->m_PointDimension = 3; // vtk only support 3 dimensional points

Still it appeared quite easy to add non-3D support, just by removing that particular line of code from "itkVTKPolyDataMeshIO.cxx", and adding a m_MeshIO->SetPointDimension(OutputPointDimension) call to the MeshFileReader.

Linux-Build8777-PR3549-Reading-non-3D-VTKPolyDataLegacyRemoved https://open.cdash.org/viewBuildError.php?type=1&buildid=8100674 says:
In file included from Modules/Core/Common/include/itkQuadrilateralCell.h:171:0,
                 from Modules/Core/Common/include/itkHexahedronCell.h:21,
                 from Modules/IO/MeshBase/include/itkMeshFileReader.h:23,
                 from Modules/IO/MeshVTK/test/itkVTKPolyDataMeshIOGTest.cxx:20:
/.../s/Modules/Core/Common/include/itkQuadrilateralCell.hxx: In member function 'bool itk::QuadrilateralCell<TCellInterface>::EvaluatePosition(typename itk::QuadrilateralCell<TCellInterface>::Superclass::CoordRepType*, typename itk::QuadrilateralCell<TCellInterface>::Superclass::PointsContainer*, typename itk::QuadrilateralCell<TCellInterface>::Superclass::CoordRepType*, typename itk::QuadrilateralCell<TCellInterface>::Superclass::CoordRepType*, double*, typename itk::QuadrilateralCell<TCellInterface>::Superclass::InterpolationWeightType*) [with TCellInterface = itk::CellInterface<int, itk::CellTraitsInfo<1, float, float, long unsigned int, long unsigned int, long unsigned int, itk::Point<float, 1>, itk::VectorContainer<long unsigned int, itk::Point<float, 1> >, std::set<long unsigned int> > >]':

Modules/Core/Common/include/itkQuadrilateralCell.hxx:326:26: warning: iteration 1 invokes undefined behavior [-Waggressive-loop-optimizations]

         fcol[j] += pt[j] * weights[i];
                    ~~~~~~^~~~~~~~~~
Modules/Core/Common/include/itkQuadrilateralCell.hxx:324:34: note: within this loop

       for (unsigned int j = 0; j < CellDimension; ++j)

I think this warning is specifically for the unit test of 1D point support. The warning does make some sense, as QuadrilateralCell has CellDimension = 2, so access to pt[j] goes wrong when pt is a 1D point.
However, adding 1D support to QuadrilateralCell seems beyond the scope of this pull request. For now, I find it much more important to have tested 2D, and possibly 4D support for .vtk file reading. So for now, I'll just remove the 1D test from the unit test, with the next force-push.

Note that originally, itk::VTKPolyDataMeshIO did already "accidentally" support reading 2D points. In last months version of ReadPointsBufferAsASCII, at https://github.com/InsightSoftwareConsortium/ITK/blob/87f8716216a5e3199897a1f7f0754c9b3d0d1697/Modules/IO/MeshVTK/include/itkVTKPolyDataMeshIO.h#L207-L212
    /**  Load the point coordinates into the itk::Mesh */
    SizeValueType numberOfComponents = this->m_NumberOfPoints * this->m_PointDimension;
    for (SizeValueType ii = 0; ii < numberOfComponents; ++ii)
    {
      inputFile >> buffer[ii];
    }

This code would very much overestimate numberOfComponents for 2D, because m_PointDimension was set to 3, even for 2D.  But then, in practice, the inputFile >> buffer[ii] insertion would fail silently once the last point coordinate was read. But then, all of its 2D point coordinates were usually correctly read already!
With pull request #3542 commit 678b97eaebed1a1fddcb77f64cfb5e293700edea (BUG: VTKPolyDataMeshIO should not hang on inf and NaN in ASCII .vtk file), error checking is added, so the insertion of components from the input file into the buffer will no longer silently fail.  Which is why numberOfComponents should not be overestimated anymore, in order to support 2D.

@N-Dekker thank you so much for working on this! :pray:
Please see my comment in https://github.com/slicersalt/ITKShape/issues/8
Can you please verify the test outputs can be read with:

ParaView
3D Slicer
meshio

?

Thanks for merging, @dzenanz I hope it's also fine to Matt (@thewtex) now. It's really useful for elastix/transformix to allow 2D points in a .vtk file.

3D Slicer did not complain, and it certainly did not crash, when I gave it a .vtk file, containing 2D points. I do not know whether it can do any further processing on them. But I can imagine that it likes 3D points better, given the name, "3D Slicer".

If it was loaded correctly, you should have been able to visualize the data.
There are many mesh libraries that use VTK or have their own implementation that follow the VTK standard. For other tools to use 2D .vtk files ITK produces, the test outputs will need to change.
For 2D and 4D meshes (including point sets), try the itk-wasm *.iwm format.


"Create all role assignments" from json missing from the article

This guide tells us how to "Save all role assignments" to a file using:
az role assignment list --all --include-inherited --output json > roleassignments.json
But it doesn't tell us how to "Create all role assignments" from the json file that we just exported using the above command.
Can the article be updated to include the necessary information?

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

ID: 9afab524-67c2-2e76-fd7a-46238cb9d249
Version Independent ID: ae2da577-6026-f322-1c09-dbcc6068c01a
Content: Transfer an Azure subscription to a different Azure AD directory
Content Source: articles/role-based-access-control/transfer-subscription.md
Service: role-based-access-control
GitHub Login: @rolyon
Microsoft Alias: rolyon

Hi @sopopa2
Thanks for taking the time to provide feedback. I've shared your feedback with the team about creating role assignments when transferring a subscription. If they have any guidance, we'll update the documentation.
Let us know if you have any additional feedback about the documentation.
thanks

#please-close


CF Release

Added

capital-framework: Added CSS autoprefixer to build pipeline.

Changed

cf-typography: Many documentation fixes and standardization.
cf-core: Standardized the usage doc.
cf-tables: Fix documentation order and details.

Removed

cf-typography: Removed remaining Less from branded bullets
cf-buttons: Removed vendor prefixes handled by autoprefixer.
cf-core: Removed vendor prefixes handled by autoprefixer.
cf-grid: Removed vendor prefixes handled by autoprefixer.
cf-icons: Removed vendor prefixes handled by autoprefixer.

Review

@cfpb/front-end-team-admin

I am a bot. If I did something wrong, blame a human.

@Scotchester Rather than closing this PR, want to just push the above fixes to release1470071472394?

@contolini Fine by me!

:shipit:

👍


Invalid command now notifies for which module

This is just in case the response is delayed, it would be nice to know
for what module the command was for?

typo fixed.


[stable/grafana] Make watch METHOD of dashboard sidecar configurable

What this PR does / why we need it:
This makes the watch METHOD environment variable of the dashboard sidecar container configurable
Starting with kiwigrid/k8s-sidecar:0.1.75 METHOD also supports a SLEEP mode that lists all ConfigMaps and sleeps for 60s. This fixes issues where long running watch requests may break because of assumptions in software defined network solutions.
See also https://github.com/kiwigrid/k8s-sidecar/pull/52
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/ok-to-test

/lgtm


Added Clone Hero support via memory reading + Added 64-bit application support to MemoryReader

This pull request proposes the following changes:

Added support for Clone Hero via memory reading
Variables are:

Actual Pointer Data:

Note streak
Star Power active
Star Power percent
Score
Total notes passed
At menu indicator
Solo percent
Currently pressed frets

Inferred Data (after extra calulcations)

FC indicator
Note streak 1x, 2x, 3x, 4x

Added default Clone Hero profile
Altered MemoryReader to allow 64-bit application support
Altered MemoryReader to allow selecting a specific module
Updated other games' memread constructors to account for changes

Known issues/To do:

Issue: Restarting a song causes the pointers to change. Restarting again fixes it. I attempted to if this by detecting when it was in the restarted state and changing the pointers based on that, but it didn't work. Until we get official GSI this is not fixable.
Issue: Changing the background image/video breaks pointers, requires game restart. Until we get official GSI this is not fixable.

Proof that it works via other people:


[Bug] Release v1.1.0's version number is incorrect when downloading source

The version number that is displayed when running eget -v on version v1.1.0 shows the wrong version when building with go build or go install.
Steps to reproduce
Method 1
Run:
go install<EMAIL_ADDRESS>
Method 2
Download the latest release (v1.1.0) zip on the releases page.
Then, navigate to the directory with the zip file in it, and run:
unzip eget-1.1.0.zip
cd eget-1.1.0/
go install

Result
Regardless of which method you used, run:
~/go/bin/eget -v

Output
eget version 1.0.1+src

Expected Output
eget version 1.1.0+src

How to fix
It looks like the version number wasn't updated in version.go. This should be able to be resolved by releasing a new v1.1.1 release with the version number set correctly.
See also #31.

New version is released.


Switch to builder methodology

TODO:

[x] MutinyWalletConfig
[x] MutinyWallet
[x] NodeManager
[x] Node

Will probably get rid of MutinyWalletConfigBuilder once I make my way through it all and just use MutinyWalletBuilder instead. But baby steps.
This will make it a lot easier to do specific things with MutinyWallet but not init the whole thing.

I won't touch mutiny-wasm for now since I don't know how that'll effect the frontend yet. Also, in follow ups I can work on removing the places where config is passed around, and instead build things with independent variables. For instance, NodeManager is partially built with MutinyWalletConfig and I want to remove that, but I think this PR is in a good place as is without needing to restructure that yet.

Handled and made sure network is required for all of the builders.


Add ignore_errors: yes by default to all roles

There are times where roles may fail (such as dmidecode). Setting ignore_errors: yes by default for the roles we can continue on despite errors that may occur. Additionally, many of these roles already have this set in the individual role so it would really just be making it a default.

/cc @aakarshg


Add Patient Consent Lab

It seems to me that a different name ought to be found because it sounds like client data is put on the ledger which is clearly something no one should ever do.

It seems to me that a different name ought to be found because it sounds like client data is put on the ledger which is clearly something no one should ever do.

Done. Please check again.

Please put the short description (and small scope definition) in the description of this ticket.

Please put the short description (and small scope definition) in the description of this ticket.

Done. Please check again. Also just added remaining people to committers list

@vipinsun : Did you agree to be a sponsor this lab?
@hyperledger-labs/lab-stewards : The request is to create to lab repos for this lab. Since this is new, I would like to hear your thoughts on this request. Today with have a 1:1 relationship between lab requests and repos. This would break that. I see two options if we want to maintain this 1:1 mapping:

Create two separate lab proposals -- one for the Fabric implementation and one for the Sawtooth one. This seems like overkill.
Create only one repo, but have two separate sub-directories -- one for the Fabric implementation and one for the Sawtooth implementation

Hi All,
2c from my side in regards of 1:1 mapping:

I'm contributor to one more hyperledger labs project. Among basic stuff
that is stored under hyperledger lab control I prepared android client for
that project too. And not sure where to keep it. Currently it is stored
under my github profile. From one hand it can be added to existing repo to
separate folder. From another hand for Android development another IDE is
used (Android Studio) and it is not the best option to clone the whole repo
just for android client coding.

Similar for Sawtooth and Fabric versions at one repo - If I responsible
on Sawtooth version - why do i need to clone and update Fabric version?

Thanks,
Alex
On Fri, Oct 4, 2019 at 5:22 PM Tracy Kuhrt<EMAIL_ADDRESS>wrote:

@vipinsun https://github.com/vipinsun : Did you agree to be a sponsor
this lab?
@hyperledger-labs/lab-stewards
https://github.com/orgs/hyperledger-labs/teams/lab-stewards : The
request is to create to lab repos for this lab. Since this is new, I would
like to hear your thoughts on this request. Today with have a 1:1
relationship between lab requests and repos. This would break that. I see
two options if we want to maintain this 1:1 mapping:

Create two separate lab proposals -- one for the Fabric
implementation and one for the Sawtooth one. This seems like overkill.
Create only one repo, but have two separate sub-directories -- one
for the Fabric implementation and one for the Sawtooth implementation

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/93?email_source=notifications&email_token=AEEZI2J4WU26HR3LBLKLC6DQM5GQZA5CNFSM4I5B2VP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALZXTA#issuecomment-538418124,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEEZI2PVNYZI2V6ER7XCO2TQM5GQZANCNFSM4I5B2VPQ
.

Hi All, 2c from my side in regards of 1:1 mapping: - I'm contributor to one more hyperledger labs project. Among basic stuff that is stored under hyperledger lab control I prepared android client for that project too. And not sure where to keep it. Currently it is stored under my github profile. From one hand it can be added to existing repo to separate folder. From another hand for Android development another IDE is used (Android Studio) and it is not the best option to clone the whole repo just for android client coding.

For this other lab and the Android development, it would be worth creating a new lab proposal for this portion. I might name it something like -android-client. That would allow you to share this code with others and possibly attract more contributors.
Regarding your point about this lab, maybe it does make sense to create two lab proposals then.

I might be convinced otherwise but I tend to agree with Tracy. If you want two repos you might as well create two labs. The overhead is minimal and I can see the value in keeping a 1:1 mapping.

On the other hand, if we have a strict rule with the lab name being used as the prefix for all related repos maybe it's ok to have more than one repo for a lab. That's certainly the case for the projects...

It might be hard for us to keep track of all the repos being created. If I am correct, with @ryjones stepping down as a lab steward, creating new lab repos probably falls to us lab stewards. Without at least an issue to create the new lab sub-repos, we may not be able to keep track. I could be convinced that we use issue tracking on this repo to keep track of sub-repos for labs.

Hi All, 2c from my side in regards of 1:1 mapping: - I'm contributor to one more hyperledger labs project. Among basic stuff that is stored under hyperledger lab control I prepared android client for that project too. And not sure where to keep it. Currently it is stored under my github profile. From one hand it can be added to existing repo to separate folder. From another hand for Android development another IDE is used (Android Studio) and it is not the best option to clone the whole repo just for android client coding. - Similar for Sawtooth and Fabric versions at one repo - If I responsible on Sawtooth version - why do i need to clone and update Fabric version? Thanks, Alex
…
On Fri, Oct 4, 2019 at 5:22 PM Tracy Kuhrt @.***> wrote: @vipinsun https://github.com/vipinsun : Did you agree to be a sponsor this lab? @hyperledger-labs/lab-stewards https://github.com/orgs/hyperledger-labs/teams/lab-stewards : The request is to create to lab repos for this lab. Since this is new, I would like to hear your thoughts on this request. Today with have a 1:1 relationship between lab requests and repos. This would break that. I see two options if we want to maintain this 1:1 mapping: 1. Create two separate lab proposals -- one for the Fabric implementation and one for the Sawtooth one. This seems like overkill. 2. Create only one repo, but have two separate sub-directories -- one for the Fabric implementation and one for the Sawtooth implementation — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#93?email_source=notifications&email_token=AEEZI2J4WU26HR3LBLKLC6DQM5GQZA5CNFSM4I5B2VP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEALZXTA#issuecomment-538418124>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEEZI2PVNYZI2V6ER7XCO2TQM5GQZANCNFSM4I5B2VPQ .

I think we are overthinking this. There are plenty of repos where multiple pathways to build and deploy are available. i.e. one for the Android-Client, another for Fabric another for Sawtooth. Let them be in sub-directories. Start with a directory structure that will accommodate this vision and let them build the ones that they are working on (Option 2.)

Ok, let's keep the limit to one repo per lab. If anyone wants more, it's up to them to propose multiple labs.

Ok, let's keep the limit to one repo per lab. If anyone wants more, it's up to them to propose multiple labs.

So we need one more approval to merge the PR- Unless we have objections from one of the reviewers.

It might be hard for us to keep track of all the repos being created. If I am correct, with @ryjones stepping down as a lab steward, creating new lab repos probably falls to us lab stewards. Without at least an issue to create the new lab sub-repos, we may not be able to keep track. I could be convinced that we use issue tracking on this repo to keep track of sub-repos for labs.

Ry was heavily against sub-repos (i.e. github based sub-repos)

My "sub-repos" was referring to repos that all started with the same lab name (e.g., lab, lab-foo, lab-bar)

@lehors @trbs @tkuhrt one of you Please approve, otherwise suggest a path forward.
So far we have:

A clean proposal
DCO signoff
There seems to be agreement for 1:1 repo and labname (any subdirectories have to be managed by the lab committers)

Is there anything I am forgetting?
@tkuhrt has said that we need to get involved in creating repos, since Ry is no longer a steward. I can do that. @AlexZhovnuvaty what do you want the lab repo to be called? I suggest patient-consent

"patient-consent" is Ok.
Thanks!
On Sat, Oct 5, 2019 at 7:41 PM Vipin Bharathan<EMAIL_ADDRESS>wrote:

@lehors https://github.com/lehors @trbs https://github.com/trbs
@tkuhrt https://github.com/tkuhrt one of you Please approve, otherwise
suggest a path forward.
So far we have:

A clean proposal
DCO signoff
There seems to be agreement for 1:1 repo and labname (any
subdirectories have to be managed by the lab committers)

Is there anything I am forgetting?
@tkuhrt https://github.com/tkuhrt has said that we need to get involved
in creating repos, since Ry is no longer a steward. I can do that.
@AlexZhovnuvaty https://github.com/AlexZhovnuvaty what do you want the
lab repo to be called? I suggest patient-consent
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hyperledger-labs/hyperledger-labs.github.io/pull/93?email_source=notifications&email_token=AEEZI2PNXJYCEX25P7B54M3QNC7TDA5CNFSM4I5B2VP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEANWLDA#issuecomment-538666380,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEEZI2MSL2P6Z5ANZCANTTTQNC7TDANCNFSM4I5B2VPQ
.

+1

@lehors @vipinsun pls create "patient-consent" branch for this project with appropriate permissions for committers. Thanks!

@AlexZhovnuvaty https://github.com/hyperledger-labs/patient-consent all yours

Great! Thanks!


abort() was called at PC 0x400839d7 on core 0 (IDFGH-1674)

Here is my error:
abort() was called at PC 0x400839d7 on core 0
0x400839d7: vPortAssertIfInISR at /home/jakub/CLionProjects/NS_Internship/prodlinesys_freertos/amazon-freertos/freertos_kernel/portable/ThirdParty/GCC/Xtensa_ESP32/port.c:258
Backtrace: 0x4008684c:0x3ffc04d0 0x40086a1b:0x3ffc04f0 0x400839d7:0x3ffc0510 0x400851c2:0x3ffc0530 0x400856a3:0x3ffc0550 0x40080dbd:0x3ffc0570 0x400d1318:0x3ffc0590 0x400d0880:0x3ffc05c0 0x400818d2:0x3ffc05e0 0x4008152e:0x3ffc0600 0x400d23ad:0x00000000
0x4008684c: invoke_abort at /home/jakub/CLionProjects/NS_Internship/prodlinesys_freertos/amazon-freertos/vendors/espressif/esp-idf/components/esp32/panic.c:676
0x40086a1b: abort at /home/jakub/CLionProjects/NS_Internship/prodlinesys_freertos/amazon-freertos/vendors/espressif/esp-idf/components/esp32/panic.c:676
0x400839d7: vPortAssertIfInISR at /home/jakub/CLionProjects/NS_Internship/prodlinesys_freertos/amazon-freertos/freertos_kernel/portable/ThirdParty/GCC/Xtensa_ESP32/port.c:258
Im using:

ESP32-WROOM-32D
CLion
IDF_version 201906.00_Major-225-g523c08a
CMake
Linux
xtensa 5.2.0
USB cable

The error occured as I was trying to use pointers as function params
// button test
void isr_button_pressed(void *args) {
    struct LEDTest *test = args; // <----------------------- HERE
    int btn_state = gpio_get_level(test->button_gpio);
    if (btn_state == 0) {
        gpio_set_level(test->LED_gpio, 0);
    } else {
        gpio_set_level(test->LED_gpio, 1);
    }
}

void interrupt_test(void *args) {
    struct LEDTest *test = args; // <----------------------- HERE
    configure_button(test->button_gpio);

    gpio_install_isr_service(0);
    gpio_isr_handler_add(test->button_gpio, isr_button_pressed, test);

    // Wait
    while(1) {
        vTaskDelay(1000 / portTICK_PERIOD_MS);
    }

}

This is from my main:
LEDIndicator yellowLED = {.GPIOPort = 26, .mode = GPIO_MODE_OUTPUT, .time = 1000, ._TaskHandler = NULL};
    LEDIndicatorInit(&yellowLED);
    printf("LED configured");

    struct LEDTest test = {.button_gpio = 25, .LED_gpio = 26};

    xTaskCreate(&interrupt_test, "testInterrupt", 2048, &test, 5, NULL);

Problem description
Im trying to make LED blinking when I press the button. When I was just using params declared inside functions (not pointers) everything was working properly. Now everytime I press the button it keeps rebooting.
Thanks in advance for any help on this.

Thanks for reporting the issue. Would you please help provide more details as suggested in the issue template? Thanks. @kuba1342

I suspect "struct LEDTest test" has gone out of scope when the above functions use their pointer to it.

@boarchuz Thanks for reply. Do you have any suggestions how can I fix this? I tried using malloc but result was the same

It's probably not that then. You're going to have to provide more info.
To test, I would've just moved "struct LEDTest test" to global scope. If it still aborts, it's something else.

@kuba1342
Backtrace: 0x4008684c:0x3ffc04d0 0x40086a1b:0x3ffc04f0 0x400839d7:0x3ffc0510 0x400851c2:0x3ffc0530 0x400856a3:0x3ffc0550 0x40080dbd:0x3ffc0570 0x400d1318:0x3ffc0590 0x400d0880:0x3ffc05c0 0x400818d2:0x3ffc05e0 0x4008152e:0x3ffc0600 0x400d23ad:0x00000000

It would be helpful if you could decode the entire backtrace using addr2line. It will help narrow down what lead to the call of vPortAssertIfInISR()

@kuba1342 Thanks for reporting, would you please help share if any updates for the issue? Thanks.


Separate handling of missing/zero width/height in chart-widget constr…

Type of PR: bugfix
PR checklist:

[x] Addresses an existing issue: fixes #353
[x] Includes tests
[ ] Documentation update

Overview of change:
I noticed this issue when browsing the 3.0 milestone and saw it had the help-wanted tag.
Width/height were only adjusted to the container size if both are 0 or missing, but not if only one of them is missing. This fixes it.
Is there anything you'd like reviewers to focus on?
I think it would make sense to move the highDPI-fix to the unconditional path or mention it in the docs that width/height should be chosen so that (width-or-height * devicePixelRatio) % 2 === 0, or that could be a gotcha for people specifying their own width/height.
If the intention of not doing so is to ensure the resulting DOM element has exactly the requested width/height, we could add the potentially lost pixel as padding on the right or bottom (where the price scale and time scale are), so that the enclosing element still has exactly the same width/height as specified (that might be important to people doing absolute positioning to build an interface, as an example, so they don't get missing single pixel lines that they can't explain).

If the intention of not doing so is to ensure the resulting DOM element has exactly the requested width/height, we could add the potentially lost pixel as padding on the right or bottom (where the price scale and time scale are), so that the enclosing element still has exactly the same width/height as specified (that might be important to people doing absolute positioning to build an interface, as an example, so they don't get missing single pixel lines that they can't explain).

@eugene-korobko that's for you 😂

Sure! I've added a graphics test-case that sub-divides the container vertically to try all 4 combinations of width/height being set or not, creating a test image like this:

Awesome! Thank you!


x/tools/gopls/internal/lsp/template: panic - slice bounds out of range (crash)

gopls version: v0.11.0 (go1.19.3)
gopls flags:
update flags: proxy
extension version: 0.37.0
go version: 1.19.3
environment: Visual Studio Code win32
initialization error: undefined
issue timestamp: Tue, 20 Dec 2022 12:17:00 GMT
restart history:
Tue, 20 Dec 2022 09:27:58 GMT: activation (enabled: true)
ATTENTION: PLEASE PROVIDE THE DETAILS REQUESTED BELOW.
Describe what you observed.

panic: runtime error: slice bounds out of range [39:37]

goroutine 163 [running]:
golang.org/x/tools/gopls/internal/lsp/template.(*completer).complete(0xc001ea7350)
	  completion.go:116  0xd05
golang.org/x/tools/gopls/internal/lsp/template.Completion({0xc0016cd740%3F, 0xc001a4b048%3F}, {0x164d118%3F, 0xc0009a0160%3F}, {0x1644920, 0xc0004b7ce0}, {0x0%3F, 0x0%3F}, {0x1, {0x0, ...}})
	  completion.go:55  0x30e
golang.org/x/tools/gopls/internal/lsp.(*Server).completion(0x1257ec0%3F, {0x1640c78, 0xc000192300}, 0xc0018d5d10)
	  completion.go:43  0x31d
golang.org/x/tools/gopls/internal/lsp.(*Server).Completion(0xc000196320%3F, {0x1640c78%3F, 0xc000192300%3F}, 0x1257ec0%3F)
	  server_gen.go:28  0x25
golang.org/x/tools/gopls/internal/lsp/protocol.serverDispatch({0x1640c78, 0xc000192300}, {0x1650ae0, 0xc00037a100}, 0xc0018d2270, {0x1641068, 0xc000192280})
	  tsserver.go:269  0x20c2
golang.org/x/tools/gopls/internal/lsp/protocol.ServerHandler.func1({0x1640c78, 0xc000192300}, 0xc0018d2270, {0x1641068, 0xc000192280})
	  protocol.go:157  0x90
golang.org/x/tools/gopls/internal/lsp/lsprpc.handshaker.func1({0x1640c78, 0xc000192300}, 0xc0018d2270, {0x1641068%3F, 0xc000192280%3F})
	  lsprpc.go:519  0xa39
golang.org/x/tools/internal/jsonrpc2.MustReplyHandler.func1({0x1640c78, 0xc000192300}, 0xc00028e378, {0x1641068%3F, 0xc000192280%3F})
	  handler.go:35  0xf6
golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1.2()
	  handler.go:103  0xa3
created by golang.org/x/tools/internal/jsonrpc2.AsyncHandler.func1
	  handler.go:100  0x20a
[Error - 13:16:48]
OPTIONAL: If you would like to share more information, you can attach your complete gopls logs.
NOTE: THESE MAY CONTAIN SENSITIVE INFORMATION ABOUT YOUR CODEBASE.
DO NOT SHARE LOGS IF YOU ARE WORKING IN A PRIVATE REPOSITORY.
<OPTIONAL: ATTACH LOGS HERE>

CC @pjweinb

Dup of #59674. I have verified that this was fixed by CL 487017.

I'm not at all familiar with the internal/lsp/template package, but from the crash information we can tell that the failure is below in completion.go, and that the cause is that c.offset is greater than start (39 > 37) but start itself is within bounds (since the error didn't mention "with capacity").
func (c *completer) complete() (*protocol.CompletionList, error) {
	ans := &protocol.CompletionList{IsIncomplete: true, Items: []protocol.CompletionItem{}}
	start := c.p.FromPosition(c.pos)
	sofar := c.p.buf[c.offset:start] // panic (39:37)

Reading a little more, we can tell that:

c.offset is 39, computed from start (37) + len("{{") (2).
inTemplate must have returned 37.
c.p.FromPosition(c.pos) must also be 37, since it provides the upper bound of the slice.
offset within inTemplate must be 37, since it comes from the same expression.
the first loop within inTemplate does not return, because it can only return a value less than offset, but the function returns 37, which is equal to offset.
therefore the second loop must have returned, since the final return is negative.
thus 37 must have come from fc.elided, and the region being tested for {{ and }} is empty.
so elideAt(37) must have been called. This means there was "{{" at 37. In short, the completion point was before a "{{".

I just tried creating a new template file in VSCode, inserting {{, backing up by two characters, and inserting a, and I got a panic similar to this one. Yay.

This seems like it's not getting fixed for v0.12.0. That's ok. It was marked as a release blocker because it is a crasher, but I don't think the template feature should block the release. Moving to v0.13.0.


I can't change the camera "current" state

Tested versions
Godot Engine v4.2.1.stable.arch_linux
System information
Godot v4.2.1.stable unknown - Arch Linux #1 SMP PREEMPT_DYNAMIC Thu, 29 Feb 2024 19:08:51 +0000 - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6700 XT () - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)
Issue description
My code
$Camera3D.current = ;Camera2D.current
$Camera2D.current = $Camera3D.current

doesn't work.
But
$Camera3D.current = false
$Camera2D.current = true

Works great
video
Steps to reproduce

Minimal reproduction project (MRP)

There isn't a current value on Camera2D, did you add it yourself?

There isn't a current value on Camera2D, did you add it yourself?

Camera2D is camera3D but I changed the name

OP named one of the Camera3D nodes "Camera2D" (confusing I know).

Please in the future be more clear when all you provide is a short snippet of code and a video
As instructed though you need to add an MRP:

A small Godot project which reproduces the issue, with no unnecessary files included. Be sure to not include the .godot folder in the archive (but keep project.godot).
Having an MRP is very important for contributors to be able to reproduce the bug in the same way that you are experiencing it. When testing a potential fix for the issue, contributors will use the MRP to validate that the fix is working as intended.
Drag and drop a ZIP archive to upload it (max 10 MB). Do not select another field until the project is done uploading.
Note for C# users: If your issue is not C#-specific, please upload a minimal reproduction project written in GDScript. This will make it easier for contributors to reproduce the issue locally as not everyone has a .NET setup available.

Or wait, this isn't a bug, and is documented:

If multiple cameras are in the scene, one will always be made current. For example, if two Camera3D nodes are present in the scene and only one is current, setting one camera's current to false will cause the other camera to be made current.

You just can't do it like this, you need to do:
if $Camera2D.current:
   $Camera2D.current = false
   $Camera3D.current = true

Or similar
Or just use make_current, that's just work

I don't think the documentation is vague here, I don't know that it needs a "setting this won't make the current camera current if another camera is already current", because it says how it works
But if you can suggest some way to make this clearer we can improve the documentation

So, with more clarity the code is as follows, with the claim that it doesn't work:
first_camera.current = second_camera.current
second_camera.current = first_camera.current

Yeah, makes sense. Only one camera can be "current" within the same Viewport.
When you make the first assignment, second_camera.current becomes false.
When you make the second assignment, first_camera.current becomes false.
So literally nothing changes.

Or wait, this isn't a bug, and is documented:

If multiple cameras are in the scene, one will always be made current. For example, if two Camera3D nodes are present in the scene and only one is current, setting one camera's current to false will cause the other camera to be made current.

You just can't do it like this, you need to do:
if $Camera2D.current:
   $Camera2D.current = false
   $Camera3D.current = true

Or similar
Or just use make_current, that'll just work regardless

But I just want to enter 2 lines instead of code 6.
I mean the code is:
$Camera3D.current = !$Camera3D.current
$Camera2D.current = !$Camera2D.current

Will automatically change the state to the opposite

You can't, it doesn't work like that, and it couldn't possibly work like that
You need to either do what I suggested, or use make_current

You can't, it doesn't work like that, and it couldn't possibly work like that
You need to either do what I suggested, or use make_current

Sadly. But thanks

Or this, (which is less comprehensible in this use-case).
var inactive_camera = $Camera3D if $Camera2D.current else $Camera3D
inactive_camera.current = true

No programming language I know would allow you to do this in fewer steps, I'm sorry. Next time you're in doubt, I would recommend asking on the Godot Forums.


Improved and Enhanced Footer

The footer wasn't nice-looking, it wasn't responsive, the code wasn't
written well and it wasn't clean, no indentation and misuse of
attributes and several other things.
I fixed everything, made it responsive, somehow improved and enhanced
the design and made it look more professional!
Solving issue #39
Live Link: https://elgayar.github.io/pslab.fossasia.org/

Before:

After:

@mariobehling

Done!
Fixing issue #39
Live Link: https://elgayar.github.io/pslab.fossasia.org/
@hemantjadon

I guess Contact section and social section below it will seem nicer. Your views @mariobehling

When will it get merged please?

@mariobehling @hemantjadon is there any amendments that I should do?

Thank you.


Remove newly unsupported external_tester methods from iTunesConnect documentation

…ocumentation

The iTunesConnect.md document describes several external tester methods that are no longer present after changes to iTunesConnect. This PR removes references to those methods from the documentation.

@mpirri this is ready to be merged, see comment above 👍

From what I could tell, the other samples were correct.  Those three were the only ones that seemed to not apply any more.


Test with vc-http-api 0.0.2 test suite

This PR adds a Node.js module to locally test didkit-http using vc-http-api-test-server.
Normally, vc-http-api-test-server tests several vendors/implementations via remote endpoints. It also wraps the results of running Jest into HTML report. For our test module, we instead run the tests with a single configured endpoint, a localhost URL where didkit-http is listening. We don't generate the HTML report but simply pass through the console output from Jest.
This PR uses the current HTTP routes; these should be updated in the test config if #102 is merged first.
The remaining failing test (fixture case-5) should pass once the following PRs are merged in ssi, and the ssi ref in DIDKit's CI config updated accordingly:

[x] https://github.com/spruceid/ssi/pull/119
[x] https://github.com/spruceid/ssi/pull/121
[x] https://github.com/spruceid/ssi/pull/128
[x] https://github.com/spruceid/ssi/pull/132

Great work, thank you.


STP - better logging suggestion

Currently when STP agent is working, all materialized infotons are written to agents.log
This overloads the log, and it very hard to monitor it progress or errors, especially when several number of agents are running in parallel
What I suggest is to do the following:
agents log - provide statistics on progress per agent - on normal work each 5 minutes (on horizon each 1 minute) - Received/Materlized/Failed + Performance - Infoton/Sec
Stop printing entire infotons in the log (Enable this in DEBUG)
red.log - for each failed infoton to write one liner with infoton name, cause of failure and number of failure
baddata.log (or some other name) will summaries all failed infotons with number of failure from red log
That way we'll be able to monitor the red.log to see how many infotons failed and if needed go to baddata.log and check what was the failure of specific infoton.

[ ] Stop logging successful infotons in agents.log
[ ] Add periodic status updates (dashboard info) into agents.log
[ ] Add failed infotons to red.log
[ ] Add detail of failure to bad data log

we need to write failed infotons to red.log both _sp and _in. I think there should be a infoton path and the reason of failure in one liner


Publish java version to rubygems

In order to get the zk gem working with jruby I had to build the java version of this zookeeper gem myself and then upload it to our local gem server (using gem build zookeeper.gemspec)
If you were to build and publish zookeeper-1.4.11-java.gem to the rubygems.org server then this step would not be necessary (assuming one has internet access when installing ruby gems)

Um, I'm not sure why you had to build it yourself, I publish both the zookeeper and zookeeper-java gems as part of the release. I just tried to build and push it again, and got the following error:
jsimms@weasel:~/zookeeper   (master)   {ruby-1.9.3-p545}
[20151022-00.44.30]$ env JAVA_GEM=1  gem build zookeeper.gemspec
WARNING:  licenses is empty, but is recommended.  Use a license abbreviation from:
http://opensource.org/licenses/alphabetical
WARNING:  See http://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: zookeeper
  Version: 1.4.11
  File: zookeeper-1.4.11-java.gem
jsimms@weasel:~/zookeeper   (master)   {ruby-1.9.3-p545}
[20151022-00.44.34]$ gem push zookeeper-1.4.11-java.gem
Pushing gem to https://rubygems.org...
Repushing of gem versions is not allowed.
Please use `gem yank` to remove bad gem releases.

My original target was jruby, so I'm pretty sure this setup works (I haven't modified it in ages).

Huh, that's weird - I'm unable to reproduce this on my work machine.  Maybe there's a weird setup on my laptop at home, I'll close this ticket then.


codec(ticdc): simple protocol support encode dml event

What problem does this PR solve?

Issue Number: close #9902, close #10186, close #10185,
What is changed and how it works?

simple protocol support encode and decode DML event.
entry schema test helper support convert DDL to DDLEvent, DML to RowChangedEvent
add simple basic integration test

Check List
Tests

Unit test
Integration test

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
`None`

/test verify

/retest

/test cdc-integration-storage-test

/test dm-integration-test

/retest

/retest

/test cdc-integration-pulsar-test


Merge work in forks

There are various forks of the original project. Moreover, there are forks of those forks. The goal of this is that when a common code base is provided, we can unify the work of so many people, so we can work together to be effective, do not duplicate work and not to confuse end users.
Known forks that we would like to merge eventually (actually rather soon):

AlexaPi for Raspberry Pi

[ ] @flooie https://github.com/flooie/AlexaPi/
[ ] @novaspirit https://github.com/novaspirit/AlexaPi

[ ] @PhyberApex https://github.com/PhyberApex/AlexaPi/tree/voice-activated

[ ] @sammachin https://github.com/sammachin/AlexaCHIP

[ ] @jitto https://github.com/jitto/AlexaCHIP
[ ] @johnwskinner https://github.com/johnwskinner/AlexaCHIP
[ ] @billzajac https://github.com/billzajac/AlexaCHIP

[ ] @dony71 https://github.com/dony71/AlexaOPi

[ ] @GadgetReactor https://github.com/GadgetReactor/AlexaOPi

[ ] @pedrominatel https://github.com/pedrominatel/intel-edison-alexa
[ ] @respeaker https://github.com/respeaker/Alexa

If you are one of the devs mentioned above and seeing this, please consider joining forces with us. The new code base that is gonna support multiple devices and OS platforms is gonna be ready in a week or two for testing and implementing new things. This is a note so you might consider this. If you have any questions, do not hesitate to ask in comments. Thank you!

@renekliment happy to help.  just let me know what you need me to do.  I'm not a professional dev.

@renekliment My changes were to run in python3 and use USB audio and a few months old.  If these are not already in upstream, I can definitely create a PR once the new code base is ready.

Awesome, glad to hear that :-) I'll let you know once the new code base is ready.

Reporting in. I don't know what the "current" code base is but I did the voice activation by a third party thing called "Snowboy" so I am ready to help out once the codebase is up.

Also, if any of you has some time and wants to at least review Pull Requests in this project, please contact @sammachin and ask him to add you to the organization. Thanks!

So before we're ready to merge the changes in your forks, we have to first stabilize the new code base. However, it seems that there's not so many people with much free time to help out with that. Do you guys (@flooie, @PhyberApex, @jitto, others mentioned) have any free time to do code review / testing of the PRs I'm pushing?
Sorry for spamming so much and thanks!

@renekliment - Unfortunately, I am starting a new job tomorrow - so my availability will be significantly limited for the foreseeable future.

Sorry for the late reply, I will be happy to help but availability (and
capability) is limited.
My code is running on an OrangePi. I have a RaspberryPi 3 but I don't have
a USB mic.
On Sep 19, 2016 1:57 AM, "flooie"<EMAIL_ADDRESS>wrote:

@renekliment https://github.com/renekliment - Unfortunately, I am
starting a new job tomorrow - so my availability will be significantly
limited for the foreseeable future.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/alexa-pi/AlexaPi/issues/6#issuecomment-247862722, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AI62U0_JyCmdZVNzBsBdRumstIM6cj0sks5qrXuggaJpZM4J5sG3
.

@bdatdo0601 I somehow missed your fork, sorry! If you have any amount of free time, please join us here :)

@renekliment this sounds really amazing. For my fork I worked on combining AlexaPi with Snowboy and ensure only one audio input stream is active. I really want to switch from Snowboy and use Python Speech Recognition as a hotword detection for this project.
Unfortunately, I don't have a lot free time. I think I will mostly available during the weekend so I can help out then. Just let me know when you need me :).
Oh and I'm not a professional dev neither. Just doing this out of curiosity.

I've noticed that also @jaws-ug-kobe and @rhee have been doing some work in their forks. Do you guys want to join us to make one great repo / version?

Also tagging @tomh05, @Robertsl2 and @the-raspberry-pi-guy.

And tagging @rhee

@renekliment My fork works on the Intel Edison boards with the MRAA. I'm considering this!
Thanks!

@pedrominatel Great to hear that! From a brief look, it should be enough to create a new device_platform (there's a plenty to take an inspiration from).

@jaws-ug-kobe @haruharuharuby
I see you're doing various work on the old AlexaPi fork. How about joining forces here?

@renekliment sure! i will soon join here.


Normalization for segmentation

Hello!
Thank you again for posting the solution and answering my previosu questions.
As I am trying to recreate and learn from your solution, I am confused by the normalizatoin of the prediction of 3d segmentatoin model.
When training, the normalization is done in the dice loss function through smp, but when predicting, no normalizatoin was done and the outputs were still in logits.
I understand that, if after sigmoid, it is OK to turn array to binary through final_outputs>0.5. But when there is no normalization, should the line be, instead, final_output > 0?
I wonder if this is a mistake or intentionally?
https://github.com/Nischaydnk/RSNA-2023-1st-place-solution/blob/77ed554f80c626195d0e18adcd8a739b2a96ef86/Datasets/make_info_data.py#L179
Best

And may I ask what is the final loss for 3d segmentation? Without TOTAL SEGMENTATOR data, I am stuck around 0.3.


change http links to https

fix links to secure versions and remove broken grunt badge

 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.Calvin Freitas seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


chore: switch to ECR Public from Docker Hub

What does this PR try to resolve?
We're hitting this hard.
[internal] load metadata for docker.io/library/httpd:2.4-alpine
ERROR: failed to copy: httpReadSeeker:
failed open: unexpected status code https://registry-1.docker.io/v2/library/httpd/manifests/sha256:66c49302c02430619abb84240a438bcfc083015661009fcaaeaac931450f62cd:
  429 Too Many Requests - Server message: toomanyrequests:
You have reached your pull rate limit.
You may increase the limit by authenticating and upgrading:
https://www.docker.com/increase-rate-limit

And the rate limit seems quite easy to hit.

The rate limits of 100 container image requests per six hours for
anonymous usage, > and 200 container image requests per six hours
for free Docker accounts are now in effect. Image requests exceeding
these limits will be denied until the six hour window elapses.

This PR switches to Amazon ECR public, and alternative image registry,
to unblock us from the rate limit of the official Docker registry.
Both of the two images are verified and uploaded by Docker

https://gallery.ecr.aws/docker/library/alpine
https://gallery.ecr.aws/docker/library/httpd

See also https://gallery.ecr.aws/

Just a thought: arguably we should switch to Azure's registry instead, since GitHub workers probably run on Azure? (I'm not totally sure they have public mirrors of this but it seems like they would?)

.. In a bit of searching I can't find public mirrors like this on Azure.
Within GH itself, there is https://github.com/linuxcontainers/alpine/pkgs/container/alpine but I don't think this includes Apache and I'm not sure it should be equally trusted.

Seems like we have recovered from the rate limit: https://github.com/rust-lang/cargo/pull/14682#issuecomment-2412539891. I am fine with either closing or merging this.

.. In a bit of searching I can't find public mirrors like this on Azure.

Neither can I find Azure equivalent. And nothing in https://github.com/orgs/apache/packages nor https://github.com/orgs/alpinelinux/packages 😞.

I opened https://github.com/rust-lang/infra-team/issues/176 to figure out what we should do here.

Going to close in favor of the discussion https://github.com/rust-lang/infra-team/issues/176.


Is width a parameter of the Python object vim.current.window?

I am trying to use PYthon to interface with VIM in my vimrc. I am aware that
this can be done in vimrc in VIML, but I don't want to learn VIML too much,
and am already familiar with Python.
I looked into some of the examples here: http://vimhelp.appspot.com/if_pyth.txt.html#python-window
Its mentioned here the width is a parameter of any window object.
However, when I do py3 print(dir(vim.current.window)), it gives me the
following output:
['__dir__', 'buffer', 'col', 'cursor', 'height', 'number', 'options', 'row', 'tabpage', 'v alid', 'vars'].
This doesn't contain width as one of the attributes of current.window,
however, when I use the following ex command:
:py3 print(vim.current.window.width)
It does give me a output of 90, so it seems width is indeed an attribute of
vim.current.window.
Is this a bug or how this is supposed to happen?

I did search through the repository to find where the interface might be located, but my initial search just resulted in bunch of .vim files.

See src/if_python3.c and src/if_py_both.h to know how the python 3 interface is implemented.

Hmm, it looks there is a mistake in the implementation:
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -3838,7 +3838,7 @@ get_firstwin(TabPageObject *tabObject)
 }
 static char *WindowAttrs[] = {
     "buffer", "cursor", "height", "vars", "options", "number", "row", "col",
-    "tabpage", "valid",
+    "tabpage", "valid", "width",
     NULL
 };

Ok.. thanks for letting me know. I can make the patch.. but probably you know more about what steps need to be followed. Let me know if you need help..

Ken Takata wrote:

Hmm, it looks there is a mistake in the implementation:
--- a/src/if_py_both.h
+++ b/src/if_py_both.h
@@ -3838,7 +3838,7 @@ get_firstwin(TabPageObject *tabObject)
 }
 static char *WindowAttrs[] = {
     "buffer", "cursor", "height", "vars", "options", "number", "row", "col",
-    "tabpage", "valid",
+    "tabpage", "valid", "width",
     NULL
 };

Thanks.  Let's order the items as they are used in the WindowAttr()
function, that makes it a bit easier to keep in sync.
--
Tips for aliens in New York: Land anywhere.  Central Park, anywhere.
No one will care or indeed even notice.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \
\\  an exciting new programming language -- http://www.Zimbu.org        ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Fixed with 8.1.0041: https://github.com/vim/vim/commit/e950f9992b291a07e4fb41cb561156f5b382cd5d


Improve cookie attributes in management console

Purpose
Improving cookie attributes in management console which was originally reported against WSO2 IS 5.2.0.

Resolves  /wso2/carbon-kernel/issues/1759


Airdatepicker

changes date range inputs to use shinyWidgets::airDatePickerInput() with modifications to make the date field not editable.

Closes #12 because it's now impossible to choose a range with the end date earlier than the start date.  Closes #7 because app doesn't refresh until the calendar popup is closed.

Couldn't figure out how to (nicely) move the date range selector to the top of the app (#21), but did make the background darker which improves things quite a bit I think.  It's now much clearer that the date sidebar is for the whole page hopefully.


Fix conversion errors between bitfields and enums in yoga

Summary
Compiler: LLVM version 10.0.1
My hypothesis: When I was running RNTester it crashed immediately because of a sign issue when storing YG Enum values inside bitfields. In my specific case, I set flexDirection() to 0b10 (YGFlexDirectionColumnReverse) which resulted in -2 because bitfields are signed with my compiler.
  YGFlexDirection flexDirection() const { return flexDirection_; }
  BITFIELD_REF(flexDirection) flexDirection() { return {*this}; }

I'm not sure what's the "proper" way to address this issue. It seems a bit invasive to change the type of all enums and I'm not sure if there are any other concerns (I've seen ABI stability mentioned occasionally in yoga context).
I'm open to suggestions/concerns. I haven't been using C++ much and I might have misunderstood something.
Minimal repro
#include <iostream>
#import <Foundation/Foundation.h>

typedef NS_ENUM(int, YGFlexDirection) {
    YGFlexDirectionRow,
    YGFlexDirectionRowReverse,
    YGFlexDirectionColumn,
    YGFlexDirectionColumnReverse,
};

struct ClassWithBitfields {
    YGFlexDirection direction: 2;
};

int main(int argc, const char * argv[]) {
    ClassWithBitfields instance;
    // This line produces a warning:
    // Implicit truncation from 'YGFlexDirection' to bit-field changes value from 2 to -2
    instance.direction = YGFlexDirectionColumn;
}

Changelog
[Internal] [Fixed] - Fixed conversion errors between bitfields and enums in yoga
Test Plan
Build and run RNTester with fabric enabled. The result probably differs between targets and compilers.

Thank you for your PR. Please send Yoga related PRs to the Yoga repository here: https://github.com/facebook/yoga

@cpojer thanks! I discovered there’s a related PR sin yoga repo but it hasn’t gotten any feedback in four months:
https://github.com/facebook/yoga/pull/870
It’s puzzling to me how yoga works at all for you (I hit this crash on two different machines). Do you think you could somehow document the compiler versions you use?

@wokalski I pinged @davidaurelio who said he'll be able to merge that PR :)

facebook/yoga#870

That causes a bunch of internal failures at FB :-( . Gonna have to work through them one by one.


Fix link to contributing guide

The link on the bottom of the readme.md document is wrong. It leads nowhere.

thank you for raising the issue. it has been fixed now. please verify the same.


Error when injecting the icon provider

Hi,
hope I'm not wrong with that but as far as I can see there's an error in the tutorial when injecting the icon provider. Referring to the branch es5-tutorial the error occurs in the tutorial step number 4. The code according to the tutorial is something like that:
...
  angular
      .module('starterApp', ['ngMaterial', 'users'])
      .config(function( $mdIconProvider ){
          // Register the user avatar icons
          $mdIconProvider
                  .defaultIconSet("./assets/svg/avatars.svg", 128);
      });
...
Executing this code angular raises an error saying: Unknown provider: $mdIconProviderProvider
If I change the parameter from $mdIconProvider to $mdIcon angular resolves the provider properly, but then angular gives me a TypeError telling me, that $mdIcon.defaultIconSet is not a function.
I'm somehow lost with that...

Consider this JsBin http://jsbin.com/manewahome/edit?html,output

If you look at the dev console, you will not see any errors AND the avatars render as desired.

That JSBin uses the angular/bower-material/master branch and Angular 1.4.9.

I am unclear why you are getting such an error. Please provide a codePen or JSbin to validate and resolve your error.

First of all thanks a lot for replying that fast! I uploaded the sample as it is here
Even though it's not CodePen oder JSBin but you should be able to reproduce the issue if you open up any browser's developer tools and take a look at the console. All libraries were installed using bower yesterday.
Thanks a lot in advance for spending your time on my issue!

You are trying to configure the provider in the .run( ... ) block:
angular
    .module("mdIconProviderApp", ["ngMaterial"])
    .run(function ($mdIconProvider) {
        // Register the user `avatar` icons
        // $mdIconProvider.defaultIconSet("./assets/svg/avatars.svg", 128);
        // $mdIcon.icon("menu", "./assets/svg/menu.svg", 24);
    });

Try using the .config( ... ) block:
angular
    .module("mdIconProviderApp", ["ngMaterial"])
    .config(function ($mdIconProvider) {
        // Register the user `avatar` icons
        // $mdIconProvider.defaultIconSet("./assets/svg/avatars.svg", 128);
        // $mdIcon.icon("menu", "./assets/svg/menu.svg", 24);
    });

Oh man facepalm I am really sorry for bothering you, yes you're right, that was the problem.
Thank you very much!


Mark-to-base attachments sometimes don't work with omar-type fonts.

Mark-to-base attachments sometimes don't work when a GSUB lookup replaces a medial form glyph as an example with 2 or 3 glyphs. As an example a base, tanqeet (dotting) and a khatt (stroke) can replace a initial form glyph, afterwhich the GPOS mark-to-base lookup will naively pick the first previous base glyph to attempt to attach to, and obviously it will not find any valid attachment points. This is my best assessment for what is happening in this case, in some cases it finds the correct base, but it has no attachment points in the font itself, so this is because some GPOS lookups are not yet handled.

No longer relevant, fixed with new architecture.


First element occurring k times in an array

🚀 Feature
Given an array of n integers. The task is to find the first element that occurs k number of times. If no element occurs k times then print -1. The distribution of integer elements could be in any range.
(A clear and concise description of what the feature is.)
Have you read the Contributing Guidelines on Pull Requests?
yes
(Write your answer here.)
Motivation
As a GSSOC participant I want to contribute in this feature
(Please outline the motivation for the proposal.)
Pitch
This program is used for array and array has many real world application.
(Please explain why this feature should be implemented and how it would be used.)

/assign


stringFirst/stringLast do not work correctly at ingest time

Affected Version
Druid 0.16.0
Description
It might be related to https://github.com/apache/incubator-druid/issues/7243 I am not sure
Ingested data with this spec in a quickstart cluster:
{
  "type": "index_parallel",
  "ioConfig": {
    "type": "index_parallel",
    "firehose": {
      "type": "http",
      "uris": [
        "https://druid.apache.org/data/wikipedia.json.gz"
      ]
    }
  },
  "tuningConfig": {
    "type": "index_parallel"
  },
  "dataSchema": {
    "dataSource": "wikipedia-test",
    "granularitySpec": {
      "type": "uniform",
      "segmentGranularity": "DAY",
      "queryGranularity": "HOUR",
      "rollup": true
    },
    "parser": {
      "type": "string",
      "parseSpec": {
        "format": "json",
        "timestampSpec": {
          "column": "timestamp",
          "format": "iso"
        },
        "dimensionsSpec": {
          "dimensions": [
            "channel",
            "cityName",
            "comment",
            "countryIsoCode",
            "countryName",
            "flags",
            "isAnonymous",
            "isMinor",
            "isNew",
            "isRobot",
            "isUnpatrolled",
            "namespace",
            "page",
            "regionIsoCode",
            "regionName"
          ]
        }
      }
    },
    "metricsSpec": [
      {
        "name": "count",
        "type": "count"
      },
      {
        "name": "sum_added",
        "type": "longSum",
        "fieldName": "added"
      },
      {
        "name": "sum_commentLength",
        "type": "longSum",
        "fieldName": "commentLength"
      },
      {
        "name": "sum_deleted",
        "type": "longSum",
        "fieldName": "deleted"
      },
      {
        "name": "sum_metroCode",
        "type": "longSum",
        "fieldName": "metroCode"
      },
      {
        "name": "sum_deltaBucket",
        "type": "longSum",
        "fieldName": "deltaBucket"
      },
      {
        "name": "sum_delta",
        "type": "longSum",
        "fieldName": "delta"
      },
      {
        "name": "test",
        "type": "stringFirst",
        "fieldName": "user"
      }
    ]
  }
}

And got:

Also that column's data type gets reported as OTHER

Everything here looks correct: the stringLast aggregator results are stored as a pair of timestamp + string. So it really should be OTHER, and the "select" query you wrote looks good.
#7243 still looks like a problem, but the stuff here looks OK to me so I'll close the issue. Please reopen if I'm missing something.

How to search the string in the aggregated value for the "OTHER" field?

bump


Simplify table with confusing score/error/rank_score

Partially addresses #539.
https://mooc-forums.inria.fr/moocsl/t/error-in-hyperparameter-tuning-lecture/4530
I named the column mean_test_error and only kept the mean_test_error in the table

I guess the explicit ranking column was indeed unnecessary, can we do the same for the dataframe in lines 129 to 133?

Indeed good catch, we seem to do something similar in python_scripts/ensemble_sol_01.py as well:
❯ git grep -P 'mean_test_score.+= -cv.+mean_test_score' python_scripts/
python_scripts/ensemble_hyperparameters.py:cv_results["mean_test_score"] = -cv_results["mean_test_score"]
python_scripts/ensemble_hyperparameters.py:cv_results["mean_test_score"] = -cv_results["mean_test_score"]
python_scripts/ensemble_sol_01.py:cv_results["mean_test_score"] = -cv_results["mean_test_score"]

Ok with the proposed change but we need to restore the original ordering:

:thinking: this is the original ordering, since rank_score is actually best score first so smaller error first.
This PR:

main:

Merging this one!