problems reading Fedora epel8 yum repo

Have been using your module for checking for updates in RHEL and epel repos and have found it really useful
But today I got this when run against an epel 8 mirror, below an example to reproduce issue
>>> import repomd
>>> this_repo_path="https://d2lzkl7pfhq30w.cloudfront.net/pub/epel/8/Everything/x86_64/"
>>> repo = repomd.load(this_repo_path)
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/nexor/release/virtualenvs/conan-rhel8/lib64/python3.6/site-packages/repomd.py", line 39, in load
    metadata = defusedxml.lxml.fromstring(uncompressed.read())
  File "/usr/lib64/python3.6/gzip.py", line 276, in read
    return self._buffer.read(size)
  File "/usr/lib64/python3.6/gzip.py", line 463, in read
    if not self._read_gzip_header():
  File "/usr/lib64/python3.6/gzip.py", line 411, in _read_gzip_header
    raise OSError('Not a gzipped file (%r)' % magic)
OSError: Not a gzipped file (b'\xfd7')

It had just successfully read the rhel 8 AppStreams and BaseOS repos but gets that failure on epel 8
Has there been some update to the way they package repodata thats breaking your module?
Just noticed that the epel8 repo has .xz files in its repodata rather than .gz that the rhel repos use which is why your module is having problems
-rw-r--r--. 1 root root  2438476 Jul  5 09:10 17303968ee78f94990aa4e02ef531b28251553f793c987990024f70e19a78f43-primary.xml.xz
-rw-r--r--. 1 root root  1134339 Jul  5 09:10 2c7fdb21e5a08f8afa7c7accb1fec9d38d98d483d46138802d671c57c379dac7-updateinfo.xml.bz2
-rw-r--r--. 1 root root    25704 Jul  5 09:10 783ce06abb85cc09757a9ffcb069277589dd60ee77ea194582cb6bec1f3122ea-comps-Everything.x86_64.xml.xz
-rw-r--r--. 1 root root 10762172 Jul  5 09:10 97275104e72f8cdfbc4e232d63a6edf45da8c70a22c22004779329c11a34dd90-filelists.xml.xz
-rw-r--r--. 1 root root 11200972 Jul  5 09:10 c0a2751531cc6b3554c186a77ea1b829ff4984ed52f6762e374f39170f961675-filelists.sqlite.xz
-rw-r--r--. 1 root root  1870828 Jul  5 09:10 cbfac394d5aab0de2479333cd872d4bf5bafea119ff6f9c4c904e110a7493108-other.sqlite.xz
-rw-r--r--. 1 root root  4656408 Jul  5 09:10 d6cefefbf0a58809acea4b62d660f54afbf3331239c0f4bf5e016d977ca19d4a-primary.sqlite.xz
-rw-r--r--. 1 root root     1240 Jul  5 09:10 f400b281aafab2de9e1e5ef9e53e9cb7f759af4e2806df940a9562c142144510-prestodelta.xml.xz
-rw-r--r--. 1 root root  1117344 Jul  5 09:10 fe90c5141099711570285dc0660968fba0f8bd9deaac3f140d1d3d19a476236b-other.xml.xz
-rw-r--r--. 1 root root     4521 Jul  5 09:10 repomd.xml

Just checked the epel 7 and epel 9 repos and they both use .gz for the repodata, its only the epel 8 repo that seems to be using .xz
Root cause discovered here https://pagure.io/releng/issue/12097 they broke it 2 months back by moving to .zst format from .gz, then rather than revert back to .gz they decided to change to using .xz

You're spot on regarding the cause of the issue.  When I originally wrote this library, gz repodata was the dominate standard and so that was the only compression format I wrote code to handle.  I knew that wouldn't be the case forever, but never got around to adding code to handle other compression formats.  At some point I'll add code to handle xz and probably even zst.  I don't know when that will be, I'm long overdue to improve this library and respond to open pull requests here, I just haven't made time for it yet.


renamed macro FLUTTER_PLUGIN_EXPORT

This fixes https://github.com/bitsdojo/bitsdojo_window/issues/3

Thank you, Thomas!

Is there a reason you removed the #ifdefs around that macro in the first place? Unless I'm not understanding the error, this only happened because you removed code that was in the template (and was there for a reason).

Hi Stuart,
Thank you for making me take a second look at this.
Actually, I could remove that macro altogether and the usage in the BitsdojoWindowPluginRegisterWithRegistrar function definition as I see no need for it. The package compiles as a static library so I believe there is no need for __declspec(export) or __declspec(dllimport).
Open to any suggestions you might have regarding this.

The package compiles as a static library

Can I ask why you made that change? The Windows plugin system is designed for shared libraries; what you are doing is not supported, and could easily break in the future, or in conjunction with other plugins (especially if they made the same unsupported change).

I need to run code that handles specific window messages very early in the window creation process (e.g. WM_NCCALCSIZE) and to make sure that the window is hidden on startup and I could not find any way to do it from a shared library.
Shared libraries plugins are loaded way too late to handle those messages and the only option was to create a static library that can run code when the executable is started.
Do you know any way to achieve the same from a shared library? If so, I would be happy to modify the package.

I need to run code that handles specific window messages very early in the window creation process

I see. I hadn't looked at the details of what you were doing.
Hopefully you are aware that essentially everything you are doing here is unsupported; this is not so much a plugin as something that modifies the runner's behavior that is (ab)using the plugin infrastructure to get itself loaded. There's no guarantee that much of what you are doing here won't break in the future.
The right way to change window creation itself is, currently, to change code in the runner. Hooking it using static initialization instead is, IMO, a hack, and is fragile. (As one of many possible examples: there's no reason that the window class name couldn't change in the future. Or even that someone making an app couldn't change their own window class name.) For non creation-time things, there is an API to register window message handlers that's official and supported, and I'm not sure why you aren't using it.
This is certainly interesting as a proof of concept, but publishing it as a plugin without any caveats that it's unsupported seems like it has a high potential for future issues and confusion.

Do you have any specific situation in mind?

This issue was one; no other plugin has the same collision problem. I've mentioned another already. Another possibility is a one-definition-rule violation, which causes undefined behavior for the entire application. I doubt that's an exhaustive list.

Devs will love this as a plugin, as it very much improves the appearance of a flutter app on windows. Although I agree, that this functionality should be included in the flutter framework itself, it should be okay to have it within a plugin until that happens.
Maybe the fact that this plugin's approach could break in the future should be documented when publishing it on pub.dev. Is there something like an experimental flag on pub.dev?
People really like to get going with Flutter on Desktop and this plugin helps to fix one of the remaining key issues (like Drag & Drop across application boundaries) that's urgently needed.

The right way to change window creation itself is, currently, to change code in the runner. Hooking it using static initialization instead is, IMO, a hack, and is fragile.

I agree what you, it would be ideal to change code in the runner to do this. However, we must keep in mind that not every Flutter developer is a Win32 developer and forcing them to learn about window messages to modify runner code would be, I believe, harder than using a package like this. This is the reason why this package was created:
I was getting tired of modifying the runner code to add window message handling for every new desktop app I wanted to create with Flutter. So I created this package as an easier way to do this for every app.

(As one of many possible examples: there's no reason that the window class name couldn't change in the future.

This could be easily fixed with a future update and I believe there is a low probability that this would change so frequently in order for it to be considered an issue.

Or even that someone making an app couldn't change their own window class name.)

Someone changing their own window class name probably has enough win32 knowledge to know what they are doing and probably wouldn't need this package in the first place.

For non creation-time things, there is an API to register window message handlers that's official and supported, and I'm not sure why you aren't using it.

I used it initially when starting to work on this package but I later dropped it as it didn't help with messages sent before WM_CREATE.

Hopefully you are aware that essentially everything you are doing here is unsupported; this is not so much a plugin as something that modifies the runner's behavior that is (ab)using the plugin infrastructure to get itself loaded.

The current plugin system in Flutter does not offer a way to achieve this without linking it as a static library so yes, you can say it is unsupported for that reason. Plugins are only loaded during WM_CREATE so the functionality provided by this package is not available when building it as a shared library.
That's why the package was built as a static library. There is currently no other way I know of to achieve this functionality, and the official API to register window message handlers doesn't help with this.
I believe that currently this is the easiest way for a Flutter dev to achieve this functionality in their app without having to learn about Windows messages and modifying the runner code to add their custom handlers.
An ideal way would be for Flutter to offer a mechanism for plugins to run their code before the window is created. If that would happen in the future then this package could be built as a shared library. Until then,  a static library remains the only option to achieve this without forcing users to learn win32 message handling to modify the runner code.

The current plugin system in Flutter does not offer a way to achieve this without linking it as a static library so yes, you can say it is unsupported for that reason.

I'm not clear on why you can't build as a DLL and export a function that your README tells people to call in wWinMain before window creation. That would make the plugin significantly less non-standard, and thus more future-proof, at the cost of needing to add a single line in the runner (which you're already doing anyway).

Plugins are only loaded during WM_CREATE

I'm not sure what this means. The plugins DLLs aren't being loaded manually by anything in Flutter, they are specified at build time. Their registration method is called during the window bringup, but that doesn't mean you couldn't call other exported methods earlier.

An ideal way would be for Flutter to offer a mechanism for plugins to run their code before the window is created.

A lot of things will change when multi-window is supported.

Until then, a static library remains the only option to achieve this without forcing users to learn win32 message handling to modify the runner code.

What I described above doesn't require users to know anything more than how to add a single line of generic C++ code to one file; I would be interested to know why that doesn't work.

That would make the plugin significantly less non-standard, and thus more future-proof, at the cost of needing to add a single line in the runner (which you're already doing anyway).

Where would you add that line?

In wWinMain, sometime before the call to window.CreateAndShow.
Am I not understanding the way the hook registration works? I would assume you just need call it before the window creation happens. In which case an explicit call, rather than relying on static initialization as you are currently doing, seems like it would be much more robust.

In wWinMain, sometime before the call to window.CreateAndShow.

That's how it worked initially. During some early sharing with other Flutter devs not familiar with how win32 works, I found out that simple instructions like
"Add these two lines at the beginning of this file" works better than:
"In wWinMain, sometime before the call to window.CreateAndShow."
and is also more future proof in case the runner code template changes and that Create And Show function is renamed to something else or included in another function.
Another thing to take into consideration is performance. This is code that runs when the application is starting and you want that window to appear on screen as soon as possible. Wasting time with dynamic linking would add some extra time that would make that window appear later on screen.
In case you have a plugin that exposes functionality that will be used on demand, based on user interaction then sure, I would also prefer dynamic linking. However, here we have a piece of code that will always run when the app starts and you want that code to run as fast as possible. That's when I choose static linking.

I found out that simple instructions like:
"Add these two lines at the beginning of this file" works better than:
"In wWinMain, sometime before the call to window.CreateAndShow."

You could tell them to make it the first line of wWinMain if that's a concern.

and is also more future proof in case the runner code template changes

If you ignore the fact that building a plugin as a static library on Windows is not supported, and is subject to breakage at any time.

Another thing to take into consideration is performance. This is code that runs when the application is starting and you want that window to appear on screen as soon as possible. Wasting time with dynamic linking would add some extra time that would make that window appear later on screen.

The whole Flutter engine is dynamically linked, so I'm doubtful that this is going to make an appreciable difference.
Also, static initialization is well known to slow startup, so the fact that you're using it in multiple places as your bootstrapping method suggests you aren't actually optimizing for performance.

In case you have a plugin that exposes functionality that will be used on demand, based on user interaction then sure, I would also prefer dynamic linking. However, here we have a piece of code that will always run when the app starts and you want that code to run as fast as possible. That's when I choose static linking.

Again though, the situation is not that you have two supported options and chose one; you are explicitly changing away from the only supported option to do something that we do not guarantee will actually work. As long as you continue to use static linking your plugin will always be subject to breakage at any time, without warning.
I think you're also underestimating the substantial issues that may arise over time if other developers decide to copy your approach of changing the library type. The possibility of ODR violations that only happen when using a specific combination of plugins, for instance.
It doesn't seem like we're going to agree here though, so I'll bow out at this point.

Also, static initialization is well known to slow startup

The discussion here is about static linking not static initialization. Those are two different things: static initialization != static linking

It doesn't seem like we're going to agree here though, so I'll bow out at this point.

Sure, trying to come to an agreement when not mentioning the same topic is hard (see example above) so we can agree to disagree.

The discussion here is about static linking not static initialization. Those are two different things: static initialization != static linking

I'm well aware of that. My point was simply that arguing that static linking is important to not slow startup seems odd to me given that in several places in the plugin you are using static initialization rather than an explicit calls to bootstrap your hooks. I would not expect someone trying to micro-optimize startup to use something that's a startup-optimization anti-pattern.
My other comments were clearly about static linking, but 🤷

My point was simply that arguing that static linking is important to not slow startup seems odd to me given that in several places in the plugin you are using static initialization rather than an explicit call to bootstrap your hooks. I would not expect someone trying to micro-optimize startup to use something that's a startup-optimization anti-pattern.

If you can point a specific example of static initialization in this repository that slows down the startup time, I would be happy to see it. Without an example, this discussion is irelevant.

My other comments were clearly about static linking, but 🤷

Comments like this one?

I think you're also underestimating the substantial issues that may arise over time if other developers decide to copy your approach of changing the library type. The possibility of ODR violations that only happen when using a specific combination of plugins, for instance.

Every developer is responsible for their work. One should only do this if they know what they are doing. Again, using a static library is useful when that code needs to run early at startup (e.g: enhancing window creation like this repository does).
There are lots of things happening when a DLL is loaded. Those are related to different actors outside of your application (AV/security solutions) and they can all influence startup time.
One should not go blindly and simply use a dynamic library or static library just because everyone else is doing it. I believe one should choose the right tool for the specific job they need to get done and not try to come up with generic and vague arguments to support a point of view.
If you have a specific suggestion for an improvement in this package then I am happy to discuss it.
Other than that, vaguely mentioning potential situations with low possibility of happening in the future or making vague comments about the code in this repository without pointing something specific, don’t really help anyone.
You and I both have more important things to take care of in our lives. Let’s not waste it on unproductive discussions.
I appreciate you taking the time to reply here and hope that we can have more productive discussions in the future.


crash with \n in replace function

hello (again) :),
wkhtmltopdf crash when i use a php variable with \n inside in the replace function.
i must use : str_replace("\n", "", $text);
thx you !!

You mean when you use the replace feature? I think, that's not easy to fix. Keep in mind, that this library simply creates a (huge) command line string to call wkhtmltopdf. That string of course must not contain line breaks.
If you find a way to pass linebreaks in CLI arguments, we can think about a solution. I can also have a look - but will not have much time. Actually I think, this is a ticket for our https://github.com/mikehaertl/php-shellcommand (that's what we use to call wkhtmltopdf). We probably need a generic solution that also works on Windows.
If you find time, feel free to open an issue there.

yes, i test the feature from your wrapper.
$tocOption = array(
	'header-html'=> $header,
	'header-line',
	'toc-header-text'=>"sommaire",
	'footer-center'=>"CONFIDENTIEL",
	'footer-right'=>"[page]/[toPage]",
	'footer-left'=>"[date] [time]",
	'footer-line',
	'header-spacing'=>0.5,
	'replace' => array(
		'{titre_livret}' => $json->titre_livret,
		'{logo_societe}' => '../public/static/img/logo.png',
		'{titre_page}' => remplace_shash_n($section->meta->titre_page),
	),
);

thx

so after using replace function from wkhtmltopdf, i will don't use that because i replace a html url in a relative path and i must write the relative path since wkhtmltopdf.exe...
thx !!


⚠ Spryr has degraded performance

In ed247dd, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 3853 ms

Resolved: Spryr performance has improved in 81de2c3 after 7 minutes.


Clusterloader - update vendor client-go dynamic package

Why we need it:
https://github.com/kubernetes/perf-tests/issues/414
What this PR does:
Related to https://github.com/kubernetes/perf-tests/pull/423
This PR only update packages k8s.io/client-go/dynamic/dynamicinformer and k8s.io/client-go/dynamic/dynamiclister, so that their revisions are different from package k8s.io/client-go/dynamic. However, it's compatible.
What not update k8s.io/client-go/dynamic:
This commit update k8s.io/apimachinery/pkg/apis/meta/v1, https://github.com/kubernetes/kubernetes/commit/0e1d50e70fdc9ed838d75a7a1abbe5fa607d22a1, but i think i should not update it.

/assign @wojtek-t

/lgtm
/approve
/ok-to-test


Switch selector not changing its values in "options" attribute when translated.

I have come across a problem ---> I'm using translations in my project and by default the language selected is English but whenever I change my translations to Hindi or any other language the "Yes or No" options in my Switch Selector does not change.
PS - the values in the switch selector for attribute "options" is defined in some other .js file and are being accessed from there
eg. translation.js --> LOGIN_WITH_SAME_EMAIL_ID =  [
{ label: "yes", value: strings.yes },
{ label: "no", value: strings.no },
];
// strings.js is another file containing translations of yes and no in different languages.
and
<SwitchSelector
initial={0}
onPress={(value) => {//some function}}
options={GLOBALS.LOGIN_WITH_SAME_EMAIL_ID}
/>
here the value is only converted when I go to translation.js and do a force save on the file..!
but when I use the direct way i.e. directly initializing "options" it works...
but I need to use the previous way, because all the translations should be accessed from an external .js file only.!

label property inside of the options object means the presented(visual) value of the switch, while the value property is the value that will be passed to the SwitchSelector onPress property when the switch values changes.
If I correcly understand your problem and implementation, I suggest you to change your translation.js this way:
LOGIN_WITH_SAME_EMAIL_ID = [
- { label: "yes", value: strings.yes },
- { label: "no", value: strings.no },
+ { label: strings.yes, value: "yes" },
+ { label: strings.no, value: "no" },
];


Would it be possible to get an example of Product Based Throttling?

Hi,
Would it be possible to get an example of Product Based Throttling?
Is this correct?
<rate-limit-by-key calls="1" renewal-period="1" counter-key="@(context.Subscription?.Key ?? "anonymous")" />

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

ID: c64c31f4-ee3f-1482-14a8-3585ff5ef2de
Version Independent ID: 8e50e224-bfd8-061c-3203-4d19016d16dd
Content: Advanced request throttling with Azure API Management
Content Source: articles/api-management/api-management-sample-flexible-throttling.md
Service: api-management
GitHub Login: @vladvino
Microsoft Alias: apimpm

Thank you for your detailed feedback.  We are looking into the issue, and we will respond when we have more information.

@msfe Sorry for the late reply. Yes, that's correct! Let us know if you're encountering any issues using the <rate-limit-by-key /> policy.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

@Mike-Ubezzi-MSFT thanks for confirming. I would still suggest that you include that in the article than as an example for the Product Based Throttling header.


Supported Kerberos Encryption Type Numbers

Please add support for Kerberos eType=32 (now unassigned) for encryptionType=gost-cts-hmac-streebog256.
BouncyCastle supports both required algorithms
GOST3410-2012 - since v1.58
GOST R 34.11-2012 - since v1.55
eType=32 is used in AstraLinux SE v1.5.
See also:
https://www.iana.org/assignments/kerberos-parameters/kerberos-parameters.xhtml#kerberos-parameters-1

+1


Compile ARM build

Error:
ERROR: LLVM was built without ARM target
0x556bde: ??? at ??
0x111731d: ??? at ??
0x119082f: ??? at ??
0x117b782: ??? at ??
0x1cd105e: ??? at ??
0x5bce69: ??? at ??
0x5892dd: main at ??
0x7f424692f830: __libc_start_main at ??
0x5562e1: ??? at ??

Error: you've found a bug in the Crystal compiler. Please open an issue, including source code that will allow us to reproduce the bug: https://github.com/crystal-lang/crystal/issues

My question now: How can I build LLVM with an ARM architecture?
By the way, when there will be a release for Crystal under the ARM architecture? Crystal on a Raspberry PI would be awesome.

There's a raspbian repository here: http://public.portalier.com/raspbian.
There's a guide to compiling llvm here: http://llvm.org/docs/GettingStarted.html

Awesome. Thanks for the quick answer.


Matrix: are the matrices one-indexed or zero-indexed?

The instructions suggest they're one indexed; however, the tests appear to require 0-based indices:
 matrix_test.go:239: Matrix("1 2 3\n4 5 6\n7 8 9").Set(0, 0, 10) returned !ok, want ok.

Not sure if we should do something here. The instructions are according to the spec of the exercise and they never mention those numbers as being indexes. I don't think this is a source of confusion for students.


Suggestions to make it easier to exclude null and undefined

Hello.
I would like to suggest additional operators that will help exclude null and undefined from the sequence.
I think you'll need ritual code like filter(i => i! == null && i! == undefined) or map(i => i !!) to exclude null and undefined from the sequence.
I found a hint from Kotlin to solve this problem and used it as a reference.

filterNotNull
mapNotNull

I hope this proposal is meaningful to the project.
Thank you for reading.
PS:
I wrote the composition using Google Translate. Please forgive me for the dull sentences ...

@samunohito
Thank you for your prompt suggestion.
I am thinking about the criteria for adding the operator.
Please wait a moment.
PS:
I can't do anything without DeepL.

@samunohito
We thought about it.
In conclusion, I believe that these features should not be added.
The most important reason is that these features have different levels of abstraction, or more specifically, orthogonality of functionality.
Basically, we should be cautious about adding functionality to a library or framework just because it reduces the amount of description. The number of functions in a library will increase infinitely if we are not conscious of orthogonality assurance.In the case of leseq, the orthogonality guarantee is also due to the fact that it preserves TreeShaking affinity. Since we already have a means to filter data by some criteria, shouldn't we write them separately in filter and map?
(In some cases, additional functionality may be added to reduce the amount of description, in which case the amount of reduction possible should be reasonable.)
I also believe that is why many non-Kotlin environments do not opt for features like mapNotNull/filterNotNull.
This article is in Japanese, but I think it will be helpful.
https://atmarkit.itmedia.co.jp/fdotnet/chushin/roadtolinq_01/roadtolinq_01_01.html
As a side note since leseq is a library, in the case of a framework, the functionality to be added should be in line with the scenario envisioned by the framework. In the case of a library, you can add features that would degrade performance if they did not conform to the scenario, which is something that cannot be added in the case of a library. In any case, I don't think we should add features at random "just because it's useful".
I would appreciate your input.

@ugaya40
Thank you for your reply.
I read the article along with your reply.
I found your opinion and the article to be absolutely correct.
Thank you for explaining why. It was very helpful.
I will withdraw this pull request.
Thank you for your time.

@samunohito
Basically

Provide "things that cannot be achieved by combining other functions" in a way that ensures orthogonality as much as possible.

would be an additional criterion.
The exception is that it would be better to provide

Significant performance contribution
The meaning of the word is clear.
The reduction in the amount of description is enormous.

would be worth providing under an alias.
Thank you very much. I appreciate your suggestions very much!


Make user's ability to upvote their own posts/comments consistent, then make an admin setting to have it be the other way

Right now users automatically upvote their own posts but cannot vote on their own comments, which is inconsistent.
The behavior should be the same on both posts and comments. Whatever is made the default, the other option should be added as an option admins can turn on.

I remember it was initially done this way in purpose, to give posts more "value" over comments
Also because back then posting tons of comments in very very old posts was an effective way to farm points and level up unnoticed. It might not be neccessary now that posts get archived automatically

Another option is that users automatically "upvote" themselves but it doesn't add to their total score when they do (have to make sure it doesn't lower their total score if they unvote on themselves).


Add reviewdog/action-tflint

I also added a link to the issue as an example of creating reviewdog GitHub Actions.
Is it ok @Vlaaaaaaad ?

Yup, it's very much ok!

Thanks!


When I launch example games, the view zooms away to a dot very quickly

More visible in the Pong game which puts the text up immediately - it seems to halve in size every frame until it's invisible.
This is on a Mac laptop that is running a hidpi screen with pixel-doubling, maybe that's the issue?

Hah! Sorry, yeah, this is currently happening on native builds - I think it's a bug with Starling's viewport. I'm stuck with HTML5 and flash until they sort it out, sorry!

Ok, well, I've gone and reported this one to the Haxe Starling project, so hopefully it'll be sorted out soon!
https://github.com/openfl/starling/issues/35

That was quick! @jgranick to the rescue again!
I'll make sure the next haxelib version of this has native support, (which means I can finally drop the -alpha bit from the version number...)


workflow for publishing docs

Description
Build/publish documentation automatically when merging to develop. To enable this workflow, someone with admin rights needs to click settings/pages. And then change the "source" to "GitHub Actions"
Partially addresses https://github.com/oneapi-src/oneMKL/issues/459. I also wasted time following the conan instructions, then found that conan support was dropped. I also saw that someone had updated the documentation to reflect the change. But I never saw that because the new documentation was not published. The published documentation has not been updated for 2 years!

Would it be sufficient to use "publishing from a branch"? We might also want to restrict publishing only when there are changes in the docs directory.

It's a different implementation to publish from a branch. Publishing from a branch is a little more manual, but also more flexible. I can make the changes, but I would rather do it after https://github.com/oneapi-src/oneMKL/pull/483 is merged. It will work better if there is a single workflow file so I can structure checks, unit tests, and doc publishing as CI jobs that depend on each other. With that in mind, I am closing this PR. It will help me to wrap this up if we can get https://github.com/oneapi-src/oneMKL/pull/483 merged and I can add new CI jobs there.


[FEATURE REQUEST] Save to custom directory

Is your feature request related to a problem? Please describe.
I have directories being synced using nextcloud. But since there is no way to automatically save to a specific directory, i have to manually move every file to the desired (and being synced) directory.
Describe the solution you'd like
would be great to be able to choose where i want the scanned files to be save to
Describe alternatives you've considered
other apps, moving files manually, etc

@maverick74 not sure i understand what you want:

are we talking about syncing app data, pdf, images?
are you saying you want different scans to be saved in different folders?

@farfromrefug
Forget the sync detail (that is all handled by nextcloud client)
Basically i want to be able to say:
All scanned documents generated by OSS-DocumentScanner are saved into this folder

@maverick74 you can't change where the internal data off the app is saved. But you can create a sync setting to sync all PDF / images to a local folder. Loo k in the sync setings

@maverick74 you can't change where the internal data off the app is saved. But you can create a sync setting to sync all PDF / images to a local folder. Loo k in the sync setings

I'll try that!
Still... apps like open camera allow one to set the folder/path where one wants the app to save the photos/files...
it's the same thing i'm proposing here :)

@maverick74 well the situation is very different actually. Opencamera on create/delete files. I need to create folder and do all.kind of disk operations. Because of SAF it became extremely difficult to do that inside custom folder.
I would need to require the manage all files permission which the play store won't Le me do

@maverick74 well the situation is very different actually. Opencamera on create/delete files. I need to create folder and do all.kind of disk operations. Because of SAF it became extremely difficult to do that inside custom folder. I would need to require the manage all files permission which the play store won't Le me do

Oh... i see.......... i'll try the workaround then :)
feel free to close this if you wish :)


Add metadata() function for debugging

/**
 * @internal
 */
export function metadata<Types extends unknown[]>(): IMetadataApplication;

Above function would be newly added for debugging #372

Done


Autolinking should account for plurals

If I do <dfn>early error</dfn>, then the phrase "early errors" should autolink to that dfn.
This should be a fun one :)

Yeah I noticed this as well. My plan is to fix it by allowing "s" or "es" to follow a term. Probably good enough.


Syncing with GitHub

Describe the bug
I am pretty sure this is not the right place to ask this question but I have searched everywhere (Forum, Wiki, Github, etc) and have not been able to find an answer.
I linked up CodeWars to my GitHub account when I first registered with CodeWars. I am no GitHub expert but I thought that my solutions on CodeWars would be syncing up/saving on GitHub. I see, of course, that they are not.
Can someone tell me what I need to do to get CodeWars' solutions to save to GitHub? I created a repo but do not understand how I can link it to CodeWars in order for it to save my solutions.
If everyone is uploading solutions to GitHub manually, then ignore my question. (But also let me know!)
To Reproduce
Steps to reproduce the behavior:

Complete a Kata successfully.

Expected Behavior

Solution is saved in GitHub.

Contexts

username: SabahatPK
OS: Windows 10 Pro
Browser: Chrome
Browser Version: Version 69.0.3497.100 (Official Build) (64-bit)

We do not sync solutions to GitHub. Also, uploading to GitHub manually is strongly discouraged because this will allow new users to easily look up the solution.


Adding CLI options and improving CLI aesthetics

Adding CLI options and improving CLI aesthetics
Changes Made:

Fixed a problem with the Google Translator functionality and updated the library accordingly.

Installed the Figlet library to enhance the appearance of the json-translator CLI output.

Added the Commendor.js library for easier and more professional handling of CLI options and to create comprehensive help documentation.

Implemented new CLI options: --translator,  --from  and,  --to  for specifying translation parameters. using languages code ISO 639-1

Modified the behavior to not halt execution if the to-languages parameter is not specified. Instead, the checkbox list will be reopened.

Added CLI options documentation to the README.md file.

Note: Just modify the version
These changes aim to improve the functionality, aesthetics, and user experience of the json-translator library. Please review and merge this pull request.

Hey guys, Thank you for your contribution @FathiGuemri
quick note: I will take a detailed look at the new changes soon.

Waiting for this feature to be merged before using this tool

@Demetri0 @ParvinEyvazov I think it's done, just are there any syntax errors in the console message

@Demetri0 @ParvinEyvazov I believe his mission is over.  just,  Are there any linguistic errors in the control unit message?

As it is over, I will merge it soon.
Thank you for your contribution @FathiGuemri . Also thank you for support @Demetri0

No thanks for the duty  . I also need these features. It would be a  defect if I didn't implement this, and I am well aware that I can do it. ❤👌

PR is finally merged 🥳. Huge thanks to @FathiGuemri for his great work!
Also thank you for the support @Demetri0 . You guys are great.

@ParvinEyvazov pardon

@FathiGuemri you mean about version of vitalets/google-translate-api? No worries.
I just tried a bit with new version, right now, it looks fine. Lets see if anyone complains about it or not.

@ParvinEyvazov  I don't know what the exact problems are. I think it's a compatibility issue with nodejs version or typescript or something like that. I didn't delve into the problem at the time.  I updated the library directly.  In general it works well


FileNotFoundException when file exists based on reported path

There is a check if the file exists based on a relative file in JakartaEeMigrationTransform.kt. The exists method doesn't resolve relative files the same way as getAbsolutePath which can lead to confusion as in my case the result of getAbsolutePath exists (for more details see jdk-4483097). It would probably be better to resolve using getAbsolutePath before checking if it exists and always use the absolute path.

Not sure if #7 is related, the build seems to fail as soon as hits the exception and the artifact reported is present. If I'm understanding that issue correctly, then it would be trying to do the transform before the artifact was actually created.


Add field for architect:wikidata

architect:wikidata=*
See #168

see https://github.com/openstreetmap/id-tagging-schema/pull/769#issuecomment-1411862885


Allow applications to configure crash bucketing

We would like the ability to refine how our crash issues are bucketed within AppCenter. Often, we find separate issues with similar callstacks that we need to combine, or general buckets masking several issues that we need to break apart. Some ability to refine these bucketing parameters within AppCenter would be ideal. We would like the ability to combine multiple Diagnosis issues into one, or split apart a single issue into multiple issues based on individual callstacks.
Describe alternatives you've considered
An alternative would be to allow us to define the bucketing parameters for Diagnosis issues, so we can determine the depth of stack used to constitute a match for bucketing.
Additional context
Currently, we have to manage the combination of issues in AppCenter externally. A greater set of tools to combine and divide issue buckets within the tool would be preferred.

Hi, thanks for your feature request. This is not in our upcoming plans, but we will consider it for future planning.
Can you describe more how you do this combination of issues externally?

We may, for example, find a set of callstacks in separate buckets which are all below a common scope or cause. We collect these into a single bug within our own database for tracking. We’d prefer to group these within AppCenter so we can more easily track their impact as a whole.
On the opposite side, we sometimes find buckets in AppCenter which contain multiple root causes we would prefer to track separately by their individual callstacks.
As an example of the latter, consider this crash bucket on std::terminate()
https://appcenter.ms/orgs/minecraft/apps/mc_vanilla_android/crashes/errors/2081732835u/overview
Inside that bucket, we find multiple separate occurrences with unique callstacks that coincidentally end in a call to std::terminate. These are distinct issues we would prefer to break apart into separate crash events for AppCenter to track.
https://appcenter.ms/orgs/minecraft/apps/mc_vanilla_android/crashes/errors/2081732835u/reports/2518284377449999999-c3422d2e-edd9-459e-9093-21df6f29bf4d/threads
https://appcenter.ms/orgs/minecraft/apps/mc_vanilla_android/crashes/errors/2081732835u/reports/2518284411609999999-368f2ad4-d486-4969-a9f7-f5dfe85a6891/threads
We assume this is because AppCenter is bucketing on a limited match of lines within a callstack. One potential mitigation is to allow us to specify the depth of the callstack we wish to bucket on for our application. This would help us break apart larger buckets into their discrete parts. If we could then also select multiple crash issues and somehow mark them as a Group, that would be very helpful to us.
Thanks!


Allow wildcard matching for "branches" command

This update adds wildcard pattern branch name matching to the "branches" command.
The use case is when a repository has many active branches and you just want to see branches matching a particular naming pattern.
The branch name wildcard patterns follow Unix filename pattern matching standards (from documentation for fnmatch):

Pattern
Meaning

*
matches everything

?
matches any single character

[seq]
matches any character in seq

[!seq]
matches any character not in seq

For a literal match, wrap the meta-characters in brackets. For example, '[?]' matches the character '?'.
Examples
branches without wildcard:
$ git branches
   develop               (published)
*  gu-branches-wildcard  (published)
   master                (published)

branches with wildcard:
$ git branches gu*
*  gu-branches-wildcard  (published)

@frostming thanks for your consideration of this improvement to legit!

Thanks so much for the merge @frostming! I look forward to a new 1.1.0 legit package published on PyPi soon!


Remove AvailabilityForTablet

This PR is meant to delete the AvailabilityForTablet class which was located in public API and only used by 2 integration tests: ImportExportIT and TableOperationsIT. Upon deleting the class, its usages were replaced which maintained the original functionality. This PR also fixes a typo in TableOperationsIT.
The following files have been modified:

core/src/main/java/org/apache/accumulo/core/client/admin/AvailabilityForTablet.java: Deleted.
test/src/main/java/org/apache/accumulo/test/ImportExportIT.java:  Replace usages of List<AvailabilityForTablet> objects with Map<TabletId, TabletAvailability>.
test/src/main/java/org/apache/accumulo/test/TableOperationsIT.java: Replace usages of List<AvailabilityForTablet> objects with Map<TabletId, TabletAvailability>. In doing so, changed the assertion on line 742: previously, was an assertEquals assertion that compared the TabletId field of objects in expected/actual Lists; now, is an assertTrue assertion that checks if the (expected) Map<TabletId, TabletAvailability> expectedAvailability contains the same TabletId's as those in the (actual) List<TabletInformation> tabletInfo. Since there is an assertion (line 740) for checking that both structures have the same size, this change can serve the same purpose as the original assertion and ensures that expectedAvailability and tabletInfo contain equal values.

UPDATE: verifyTabletAvailabilities on line 735 of TableOperationsIT has been simplified to compare two Maps instead of a Map and a List, resulting in only one Assertion needed.

Fix all occurences of typo verifyTabletAvailabilites -> verifyTabletAvailabilities in both ImportExportIT and TableOperationsIT.

Resolves: #4706 "Remove AvailabilityForTablet from public API"

@meatballspaghetti if this your first PR to Accumulo then feel free to make a PR to add yourself as a contributor on the People page.


Using paste in the Pin code input causes issues

Describe the bug
When using the Pin code input feature within a number-input component, pasting a verification code only pastes the character into the first input field, while the remaining digits are omitted. This behavior can significantly affect the user experience, as typically, pasting a verification code should fill all input fields.
Reproduction
It seems that this issue is also present in the official documentation for this feature: number-input/#pin-code-input
Flowbite version and System Info
System:
    OS: Windows 11 10.0.22631
    CPU: (6) x64 Intel(R) Core(TM) i5-9600KF CPU @ 3.70GHz
    Memory: 11.32 GB / 23.94 GB
  Binaries:
    Node: 20.11.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.2.4 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.9.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (127.0.2651.74)
    Internet Explorer: 11.0.22621.3527
  npmPackages:
    @nuxt/kit: ^3.13.0 => 3.13.0
    flowbite: ^2.5.1 => 2.5.1
    nuxt: ^3.13.0 => 3.13.0
    vite: ^5.4.2 => 5.4.2
    vue: ^3.4.38 => 3.4.38

Sorry, I should submit this issue to the main repository.


A small error in the Turkmen locale.

Hi guys. The turkmen locale have a small bug. The index ago do not translate.
Return this:

1 sekunt ago

1 minut ago

1 sagat ago

....

Expected this:

1 sekunt ozal

1 minut ozal

1 sagat ozal

...

This bug have bulgarian (bg) locale too.

And turkmen domain is tm

Do not tk. This is Tokelau's domain

Hello,
Thanks for your help.
tk this is not the country code, but the language code, they are different, because 1 country can have multiple languages and 1 language can be used in multiple countries:
https://fr.wikipedia.org/wiki/Liste_des_codes_ISO_639-1
And full code is tk_TM (language_REGION)
Translations of it are there:
https://github.com/briannesbitt/Carbon/blob/master/src/Carbon/Lang/tk_TM.php
Please edit and fill the missing translations:
// translate the English values to the right (keep :time, :count, {1}, ]1,Inf[ unchanged)
    'ago' => ':time ago',
    'from_now' => ':time from now',
    'after' => ':time after',
    'before' => ':time before',
    'diff_now' => 'just now',
    'diff_yesterday' => 'yesterday',
    'diff_tomorrow' => 'tomorrow',
    'diff_before_yesterday' => 'before yesterday',
    'diff_after_tomorrow' => 'after tomorrow',
    'period_recurrences' => '{1}once|{0}:count times|]1,Inf[:count times',
    'period_interval' => 'every :interval',
    'period_start_date' => 'from :date',
    'period_end_date' => 'to :date',

And add your name in the Authors: list to appear in our translators list: https://carbon.nesbot.com/contribute/translators/
You can do the whole thing on GitHub, it will ask you to fork, will automatically create a branch, then you'll be able to create a Pull request with this branch.
Thanks

Of course. Thanks!

Great, feel free to ask if you have any trouble in submitting the pull request.


EDU-310 Rename language to uiLanguage where it is the UI language

Closes https://educandu.atlassian.net/browse/EDU-310

Note:
Let's do another search for usages of useLanguage after merging https://educandu.atlassian.net/browse/EDU-305 ,
we'll probably have new usages introduced with it

Note: Let's do another search for usages of useLanguage after merging https://educandu.atlassian.net/browse/EDU-305 , we'll probably have new usages introduced with it

Yes, let's merge https://educandu.atlassian.net/browse/EDU-305 first and I'll review the changes again.


Remove or rename files from ibroadcast

Is it possible to remove or rename files from ibroadcast when I delete or rename it from local beets collections?
Thanks.

@catap Good questions!
As written currently, when you rename a track in beets, that should bump the mtime, which should trigger beets-ibroadcast to delete your old track and reupload the new version the next time you run beet ibroadcast <query> with a matching query. I haven't tested it, though. Curious to hear whether you have success with that.
As for deleting: there is currently no mechanism to delete a track from iBroadcast in response to the track being deleted from beets. One way we could accomplish that would be to listen for item_removed and delete the iBroadcast track in response.
If the event-based approach works well for deleting, we could potentially also use it for renaming or other metadata updates—the after_write function looks promising for that.
I don't have time to implement these changes now, but we can leave this issue open as a reminder. And of course, PRs are welcome any time if you have the time and interest to work on such things.

@ctrueden thanks to make this clear. I can try to implement it, but I have no idea when I'll have time to it.


        # These assignments allow 0.0 to be used as a bound...
        low_bool = low_bound is not False
        hi_bool = hi_bound is not False

        if bool(low_q) ^ low_bool and low_q != 0:
            raise ValueError(
                f"You must supply both a lower quantile and lower bound, "
                f"or neither. Got: low_q={low_q}, low_bound={low_bound} "
                f"for validation entitled {title}"
            )
        if bool(hi_q) ^ hi_bool:
            raise ValueError(
                f"You must supply both a lower quantile and lower bound, "
                f"or neither. Got: low_q={hi_q}, low_bound={hi_bound} "
                f"for validation entitled {title}"
            )

        if query != "":
            df = df.copy().query(query)
        if title != "":
            logger.info(title)
        if weight_col is None or weight_col == "":
            df["ones"] = 1.0
            weight_col = "ones"
        if low_q >= 0 and low_bool:
            low_test = weighted_quantile(df[data_col], df[weight_col], low_q)
            logger.info(f"{data_col} ({low_q:.0%}): {low_test:.6} >= {low_bound:.6}")
            if low_test < low_bound:
                raise ValueError(
                    f"{low_q:.0%} quantile ({low_test}) "
                    f"is below lower bound ({low_bound}) "
                    f"in validation entitled {title}"
                )
        if hi_q <= 1 and hi_bool:
            hi_test = weighted_quantile(df[data_col], df[weight_col], hi_q)
            logger.info(f"{data_col} ({hi_q:.0%}): {hi_test:.6} <= {hi_bound:.6}")
            if hi_test > hi_bound:
>               raise ValueError(
                    f"{hi_q:.0%} quantile ({hi_test}) "
                    f"is above upper bound ({hi_bound}) "
                    f"in validation entitled {title}"
                )
E               ValueError: 95% quantile (7.896900000000001) is above upper bound (7.8) in validation entitled Natural Gas Fuel Costs (tails, 2015+)

Next steps
@zaneselvans my best guess is that this is due to the new EIA data that was integrated in e1cdcb882d6720cc905f2e796ab9106704660530 - does that make sense to you? If so, the next steps are probably to investigate the new data & see if there's an error vs. the thresholds needing to change.

Yes, 95th percentile of gas prices was a little out of bounds, probably because late 2022 had high prices due to Putin.  I've adjusted it upwards slightly and am re-validating locally. Will push a fix as soon as validations pass.


res.Error() takes code and string

Change is as follows:
type ResponseWriter interface {
    Error(Status, string) // instead of Error(Status)
// ...
}

Servers can (and should) send explanations along with error codes.
When clients receive an error response from a server, they return a *ResponseError which contains the code and the explanation string. @ttacon

Ya, I really, really like the idea of passing back a message with the code - saves some of what I was doing passing structs back to do it before. I have one question though, any reason to not export okStatus? It's reasonable (and a common occurrence) to pass back StatusOK, imho.

Fair point. It was a vestige of when Status implemented error. Fixed.


rich-counters:0.2.0

I am submitting

[ ] a new package
[x] an update for a package

Description: Counters that can depend on other counters. This PR is a minor fix for version 0.2.0.
I have read and followed the submission guidelines and, in particular, I

[x] selected a name that isn't the most obvious or canonical name for what the package does
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] tested my package locally on my system and it worked
[x] excluded PDFs or README images, if any, but not the LICENSE

Can you please make that a new patch release? Once a package is published, its code should not change.

also if it was just accepted yesterday?

I agree that the rule of having to make a new release is a bit strict but I prefer to enforce it at all times rather than judging individually for each package if this should be a patch release or if it can be hotfixed in the previous release. Also, patch releases exist for this kind of changes, it makes sense to have a new release just for that bug fix. Sorry, I understand that this is a bit more work for you.


Consolidate commonly used GroupResource objects

Cleans up some tech debt from #463
Signed-off-by: Nolan Brubaker<EMAIL_ADDRESS>

LGTM.


exports is not defined

[Script Loader] ReferenceError: exports is not defined
at eval (eval at module.exports (addScript.js?3fe7:27), :166:1)
at eval ()
at module.exports (addScript.js?3fe7:20)
at eval (Blob.js?42b3:1)
at Object../node_modules/script-loader/index.js!./src/common/exportExcel/Blob.js (33.js:48)
at webpack_require (app.js:708)
at fn (app.js:113)
at eval (Export2Excel.js?8513:3)
at Object../src/common/exportExcel/Export2Excel.js (33.js:63)
at webpack_require (app.js:708)

https://github.com/xrkffgg/Kvue/issues/2


Not finding coverageresults

@tonerdo
After running the command, I got this message and I don't see any coverage results json file. I would expect to see the coverage results even when Test Run Failed.
dotnet test /p:CollectCoverage=true
Total tests: 32. Passed: 28. Failed: 4. Skipped: 0.
Test Run Failed.
Test execution time: 16.6057 Seconds

Hi @arunprasathv, because of msbuild limitations the coverage task will not be executed if your tests fail and as a result no coverage result file will be generated

Hi @arunprasathv,
Try this format
/p:Exclude="[NUnit3.*]*"
In my case I would like to exclude NUnit3TestAdapter assembly and all types.
See here:
https://bitbucket.org/andre-castro-garcia/ducktales/src
Andre Garcia

@andre-castro-garcia In my case its a dependency and generates assembly under \bin\Debug\netcoreapp2.0,i tried this option as well but it still takes the assembly, at least i see in the report.

It works, just changed the pattern instead of NUnit3.* changed to NUnit*

Hi @arunprasathv,
My test project generates an assembly Nunit3.TestAdapter.dll to the same folder as your project (bin\Debug\netcoreapp2.0).
If i run the coverage without a 'Exclude' param he instrument a NUnit3 assembly as well, see:
Iniciando execução de teste, espere...
NUnit Adapter <IP_ADDRESS>: Test execution started
Running all tests in C:\temp\ducktales\test\ducktales.tests\bin\Debug\netcoreapp2.0\ducktales.tests.dll
NUnit3TestExecutor converted 7 of 7 NUnit test cases
NUnit Adapter <IP_ADDRESS>: Test execution complete

Total de testes: 7. Aprovados: 7. Com falha: 0. Ignorados: 0.
Execução de Teste Bem-sucedida.
Tempo de execução de teste: 22,1852 Segundos

Calculating coverage result...
  Generating report 'C:\temp\ducktales\test\ducktales.tests\coverage.json'

+--------------------+--------+--------+--------+
| Module             | Line   | Branch | Method |
+--------------------+--------+--------+--------+
| ducktales.api      | 100%   | 75%    | 100%   |
+--------------------+--------+--------+--------+
| ducktales.data     | 100%   | 100%   | 100%   |
+--------------------+--------+--------+--------+
| ducktales.models   | 98,1%  | 88,9%  | 100%   |
+--------------------+--------+--------+--------+
| NUnit3.TestAdapter | 41,9%  | 35%    | 56,4%  |
+--------------------+--------+--------+--------+

+---------+--------+---------+--------+
|         | Line   | Branch  | Method |
+---------+--------+---------+--------+
| Average | 85%    | 74,725% | 89,1%  |
+---------+--------+---------+--------+

Run coverage with 'Exclude' param he ignores NUnit3 assembly, see:
Iniciando execução de teste, espere...
NUnit Adapter <IP_ADDRESS>: Test execution started
Running all tests in C:\temp\ducktales\test\ducktales.tests\bin\Debug\netcoreapp2.0\ducktales.tests.dll
NUnit3TestExecutor converted 7 of 7 NUnit test cases
NUnit Adapter <IP_ADDRESS>: Test execution complete

Total de testes: 7. Aprovados: 7. Com falha: 0. Ignorados: 0.
Execução de Teste Bem-sucedida.
Tempo de execução de teste: 1,4433 Segundos

Calculating coverage result...
  Generating report 'C:\temp\ducktales\test\ducktales.tests\coverage.json'

+------------------+--------+--------+--------+
| Module           | Line   | Branch | Method |
+------------------+--------+--------+--------+
| ducktales.api    | 100%   | 75%    | 100%   |
+------------------+--------+--------+--------+
| ducktales.data   | 100%   | 100%   | 100%   |
+------------------+--------+--------+--------+
| ducktales.models | 98,1%  | 88,9%  | 100%   |
+------------------+--------+--------+--------+

+---------+-------------------+-------------------+--------+
|         | Line              | Branch            | Method |
+---------+-------------------+-------------------+--------+
| Average | 99,3666666666667% | 87,9666666666667% | 100%   |
+---------+-------------------+-------------------+--------+

Another interestelly thing, i run these commands with a Git Bash, the format of command changes to:
$ dotnet test test/ducktales.tests/ducktales.tests.csproj -p:CollectCoverage=true -p:Exclude="[NUnit3.*]*"
I think that's occurs because Git Bash simulates a unix terminal. :)
Andre Garcia

@andre-castro-garcia This issue has been resolved.


Add "Target ref" column to list views for new style policies

Description
Add a new "target ref" column to policy list views if the currently selected policy type is a new style policy.
To be determined:

How can we know when to show this column? Should we add a field hasTopLevelTargetRef or isNewStylePolicy to /policies?
What should the show column show? Only the target ref kind? Also the target ref name if set? Docs: https://kuma.io/docs/2.3.x/policies/targetref/

Figma design for reference: https://www.figma.com/file/Q5z8lPJeU26763q30S9GTy/branch/tzdIVkISDMa1jluZviIFO3/MinK?type=design&node-id=1789-31966&mode=design&t=V1dMZS2O39CNzAU1-0

This was implemented in https://github.com/kumahq/kuma-gui/pull/1356.


Update Graphql test

Partially resolves #1103
Hi @broody , let me know if I am going in the right way

Ah I was thinking to just to remove model_fixtures and use spinup_types_test like entites/models. But this will work too, tho maybe use Subrecord instead of Record for ur tests,  recreating all that ty is probably not necessary.

Ok. I now use Subrecord and  Record(recreating just some of the ty).
I used to get errors implementing  spinup_types_test like entites/models. Gonna try again :+1:


ERROR:  operator class "vector_cos_ops" does not exist for access method "vectors"

I'm using version 0.2.0 on postgres15 (Debian bookworm ARM64 installed via .deb file) and see the error
ERROR:  operator class "vector_cos_ops" does not exist for access method "vectors"
when trying to add an index after SET vectors.pgvector_compatibility=on; with
      CREATE INDEX IF NOT EXISTS indexname ON tablename
      USING hnsw (embedding vector_cosine_ops)
      WITH (ef_construction = 300, m = 16);

Datatype of embedding is vector(512).
The database had an extension installation of version 0.1.11 before. But I removed that with DROP EXTENSION, reset shared library path, restarted and had a postgres database without pgvecto.rs extension. Then, I followed the install instructions for 0.2.0
Any pointers?

Hello, I think this may be related to some error at:
https://github.com/tensorchord/pgvecto.rs/blob/8aa621a4bfa484d1acb952ac4d0bbcbc84ad408e/src/index/compat.rs#L18
Could you please show your logs after logging_collector=on:
There might be some warnings containing will not be overwritten.
The log might be at /var/lib/postgresql/15/main/log/postgresql-2024-01-11_094502.log or /var/log/postgresql/postgresql-15-main.log, when logging_collector is on or off, if you installed by deb at local machine.

There might be some errors at schema installing.
Could you please run:
SELECT am.amname AS index_method,
       opc.opcname AS opclass_name,
       opc.opcintype::regtype AS indexed_type,
       opc.opcdefault AS is_default
    FROM pg_am am, pg_opclass opc
    WHERE opc.opcmethod = am.oid AND am.amname = 'vectors'
    ORDER BY index_method, opclass_name;

and show the result.

This is possibly related to the search path problem. Can you show the result of SHOW search_path;?
Ref: https://github.com/tensorchord/pgvecto.rs/issues/383

@cutecutecat Thanks for the quick response! The result looks different:
 index_method |  opclass_name  |  indexed_type  | is_default
--------------+----------------+----------------+------------
 vectors      | vecf16_cos_ops | vectors.vecf16 | f
 vectors      | vecf16_dot_ops | vectors.vecf16 | f
 vectors      | vecf16_l2_ops  | vectors.vecf16 | f
 vectors      | vector_cos_ops | vectors.vector | f
 vectors      | vector_dot_ops | vectors.vector | f
 vectors      | vector_l2_ops  | vectors.vector | f

How can i fix this?
@VoVAllen result of SHOW search_path; is
 "$user", public, vectors

The result looks different

Based on postgres doc:

All of the OID alias types for objects grouped by namespace accept schema-qualified names, and will display schema-qualified names on output if the object would not be found in the current search path without being qualified.

The displayed vectors.vector usually means search_path is not set/correct, but as you shows it has been set, so it might be strange, need a deeper survey.

Thanks for your time and help. I was finally able to figure it out:
The vectors schema was owned by the postgres default user. The database in question (and debug commands run for this issue) is accessed by another user. Changing the owner of the vectors schema to my application user resolved the issues.
For my future self or other with the same issue:
ALTER SCHEMA vectors OWNER TO yourUserName.


Inappropriate UX for text size.

Describe the bug
The text size configurable currently has an inappropriate user experience.

Which site: phanpy.social
Which instance: not relevant

To Reproduce
Steps to reproduce the behavior:

Click on the hamburger menu.
Click on 'Settings'.
Observe that 'text size' is a slider with five positions.

Expected behavior
Text size should be an actual number input, either a spin-box (number box with up/down arrows) or a regular number box.
Screenshots

Desktop (please complete the following information):

OS: macOS Ventura 13.4.1
Browser: Firefox
Version: 119.0

Additional context
This is an issue because browser zoom is not a suitable replacement for freely choosing a font size that is usable by the user, lacking among other things the ability to ensure click-targets remain a reasonable size. I recognise that I could apply userCSS, but this is not a reasonable approach either as most visually-impaired/blind users are not going to be technically competent enough for that to be an option. I also recognise that other applications think that a slider is an appropriate interface; they are wrong, too.

Noting an additional problem; small or even imperceptible mouse movements can cause the slider to move around wildly.
2024-10-09_02.webm
Desktop

OS: Fedora 40

Linux Kernel 6.10.10 (64-bit)
KDE Plasma 6.1.5

Browser: Firefox 130.0.1 (64-bit)
Phanpy Version: 2<IP_ADDRESS>a176e2

@irasponsible could you report this as separate bug? (not part of this issue) Thanks.

I would consider this to be an additional argument against using a slider for this issue, even if this is an issue for the slider widget in general rather than this one specifically.


kubectl rollingnodeupdate

Capturing conversation with @bgrant0607 just now.
New feature for kubectl:
when you run kubectl rollingnodeupdate --exec myprogram --success_label=k3=v3 --fail_label=k4-v4 --selector k1=v1,k2=v2, then it would do this:
for each node matching the selector and not matching success_label or fail_label:
   cleanly remove the node
   exec myprogram with env vars set like KUBE_NODE_NAME=nodename
   depending on the return code of myprogram, do one of the following:
     set success_label on the node and return the node to service
     set failed_label and don't retry the node and do return it to service.
     set failed_label and don't retry the node, and do not return it to service.
     set no label and retry the node and do return it to service.
     set no label and retry the node, and do not return it to service.

This cleanly separates the problem of taking a node in and out (which kubectl should know about) from what you might do to a node once it is removed.  Things you might do when it is removed include making salt/chef/puppet update the node, reboot the node, delete the node, power it down and wait for a human to touch it, etc.
The clean removal steps are documented in docs/cluster_management.md under Maintenance on a node.

@bgrant0607

@jhonce @ravip

Oops, @pravisankar instead

cc @rvangent

@mbforbes you are interested in node upgrades.

And me. I need to figure out how this would fit in with #5472, though, because I had intended rollingupdate to fall in under there eventually (with client calls).

See also #3885 and #6080

Like Deployment #1743, we'll eventually want this as a service, not just in the client #12143.


Add view command into DG

Added new UML Diagrams + View command.
Resolves https://github.com/AY2122S2-CS2103T-T09-2/tp/issues/103

Codecov Report

Merging #104 (326a2d5) into master (ba2281f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #104   +/-   ##
=========================================
  Coverage     73.16%   73.16%
  Complexity      445      445
=========================================
  Files            76       76
  Lines          1323     1323
  Branches        140      140
=========================================
  Hits            968      968
  Misses          321      321
  Partials         34       34

Continue to review full report at Codecov.

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


Reconnect before mochad switch send command

Description:
Connection to mochad occasionally stalls on RPi and CM19A. Re-connect the underlying socket in controller.PyMochad when X10 swtich is set to on/off.
Current design of mochad in homeassistant is to keep 24/7 connection to mochad server open. There is no watchdog nor automatic reconnect routine.
There is a known issue for mochad to get locked up occasionally. e.g. as seen often on RPi.
https://sourceforge.net/p/mochad/discussion/1320003/thread/1c193f01/
When this happens, mochad can be recovered by restarting it. However, mochad.py components in home-assistant once connected on HA startup, won't ever reconnect.
This improvement allows to reconnect underlying socket in controller. PyMochad when X10 commands are sent to mochad server. It's tested to work fine on my HA.
Related issue (if applicable): fixes #
https://sourceforge.net/p/mochad/discussion/1320003/thread/1c193f01/

There are some linting issues and you need to mock the dependency pymochad.exceptions in the tests for the switch.

Regarding mocking the exceptions for switches. do you have any example? I looked in home-assistant\tests\components\switch\ and didn't see any.

I think you can extend the existing pymochad mock fixture and patch pymochad.exceptions in sys.modules.


hx-boost not working with JinjaX

I'm not sure if this is a JinjaX issue or not but I'm facing a bug that does not exist in Jinja2.
I want to use hx-boost to enhance my links so that:

If HTMX is available it will do a AJAX request + partial update
If not or if someone opens the link directly, it will do a normal request + full render

The idea is that I dont have to differentiate HTMX vs. HTTP calls in the backend and have HTMX intelligently decide between full and partial updates.
This is supported by HTMX out of the box but it doesn't work with JinjaX. It will always render the full page into the target element.
Any idea what's going on?

It was my own fault. Can be closed.


Finish implementing features that are not fully implemented yet

There are a few things we started, but still need to be finished:

Email activation
Maintenance actions
Resources page
User management CRUD functionality

Image dispatcher and normal entry point emulation are ready.


Added unit tests for using nodal parameters.

The model class correctly returns the closest nodal parameter value for
a given query, or throws an exception if one does not exist. From the
elment / physics side, we are still looking for elemental parameters. We
need to discuss: which should be the default case?

Current coverage is 91.32% (diff: 100%)

Merging #44 into master will increase coverage by 0.70%

@@             master        #44   diff @@
==========================================
  Files            42         42
  Lines          2153       2075    -78
  Methods         327        327
  Messages          0          0
  Branches        377        310    -67
==========================================
- Hits           1951       1895    -56
+ Misses          202        180    -22
  Partials          0          0

Powered by Codecov. Last update 8fb4025...f9e9b40


Small typo in runtime/readme

Fixed a really small typo in the readme about the custom Flutter runtime.

fixed in https://github.com/realm/realm-dart/commit/e95154325a1c6e3c86f9d94b83a467e88884d21b


Reference to AbstractSpecies type broken due to deprecated enzymeml-specifications

MTPHandler is currently not working, as Plate references https://github.com/EnzymeML/enzymeml-specifications.git@AbstractSpecies as the type of its field species.
In enzymeml-specifications, the AbstractSpecies contains an XML declaration that is deprecated and broken since upgrading sdRDM to pydantic v2.
Thus, for MTPHandler to work again, enzymeml-specifications has to be updated.

Refactored data model and removed the AbstractSpecies type


Add dataset description to Sentry

This would be useful to identify unique(-ish) datasets run. In the case of OpenFMRI datasets, it would allow us to attempt reproductions for unreported crashes.

How can we uniquely identify datasets?

Hash of dataset_description.json?


Add a dark theme or relax CSP

What's the problem this feature will solve?
The website might no longer burn its users' eyes out.
Describe the solution you'd like
Add a dark theme -- using the CSS media feature "prefers-color-scheme"? -- or relax CSP, so one can use one of the many extensions that allow one to use custom styles on websites.

Yeah, I expected that no one would like the idea of relaxing the CSP. There other option, however, has gained traction slowly over the years with a website here, website there adopting it and it seems like it'd be the way to go.

is this issue open for work?


"$ref" not working with custom object "array"

{
properties : {
cars : {
children : {
type: array,
items: {
ref : Test.json
}
}
}
}
}
Here I want a List cars.
But its not working.
What am I missing

Not sure what is in Test.json, but you need to remove the 'children' level, or put it inside a 'properties'.


run the test scripts receive some error info

When I finished install the Calvin, I run a test scripts, I saw some expected output but also I saw these error information:
D:\calvin-base-master>csdeploy calvin/scripts/test1.calvin
2015-07-22 14:16:23,325 INFO     calvin.calvin.runtime.north.calvincontrol: Listening on: localhost:5001
Unhandled Error
Traceback (most recent call last):
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\runtime\north\scheduler.py", line 44, in run
async.run_ioloop()
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\runtime\south\plugins\async\twistedimpl\async.py", line 38, in run_ioloop
reactor.run()
File "C:\Python27\lib\site-packages\twisted-15.2.1-py2.7-win32.egg\twisted\internet\base.py", line 1194, in run
self.mainLoop()
File "C:\Python27\lib\site-packages\twisted-15.2.1-py2.7-win32.egg\twisted\internet\base.py", line 1203, in mainLoop
self.runUntilCurrent()
---  ---
File "C:\Python27\lib\site-packages\twisted-15.2.1-py2.7-win32.egg\twisted\internet\base.py", line 825, in runUntilCurrent
call.func(*call.args, **call.kw)
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\runtime\north\calvin_node.py", line 149, in start
self.network.start_listeners([self.uri])
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\runtime\north\calvin_network.py", line 160, in start_listeners
self.transports[schema].listen(uri)
exceptions.KeyError: 'calvinip'
2015-07-22 14:16:24,010 INFO     calvin.StandardOut: StandardOut<54f676c0-f9f5-4716-8226-fef05a2fe64d>: 1
Traceback (most recent call last):
File "c:\python27\scripts\csdeploy-script.py", line 9, in
load_entry_point('calvin==0.1', 'console_scripts', 'csdeploy')()
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\Tools\deploy_app.py", line 173, in main
select.select([], [], [], timeout)
select.error: (10022, 'An invalid argument was supplied')
2015-07-22 14:16:24,121 INFO     calvin.StandardOut: StandardOut<54f676c0-f9f5-4716-8226-fef05a2fe64d>: 2
2015-07-22 14:16:24,230 INFO     calvin.StandardOut: StandardOut<54f676c0-f9f5-4716-8226-fef05a2fe64d>: 3
2015-07-22 14:16:24,339 INFO     calvin.StandardOut: StandardOut<54f676c0-f9f5-4716-8226-fef05a2fe64d>: 4
What is the error information 'Unhandled Error' and 'exceptions.KeyError: 'calvinip'' mean? how to remove these error?

Hi,
calvinip is the uri schema currently implemented for connecting nodes over ip. It is expected to have successfully manged to register this transport plugin. Since it is missing in the dictionary (unknown key) it has failed. This could be for a number of reasons e.g. missing requirements, faulty configuration file (framework should be twisted) or perhaps that we have not tested enough on Windows (seems you run on Windows). I would expect the last to be the problem. Unfortunately I'm not at a computer to be able to verify the problem. Maybe someone else in the team could check it out.

I have hopefully fixed this issue when running on Windows (with today's commit on the master branch). Let me know if it works so we can close this bug.

Yes. It seems the bugs have been fixed. I updated calvin_network.py and ran the test script, the errors 'Unhandled Error' and  'exceptions.KeyError: 'calvinip''  had gone.
But I notice there a statement 'select.error: (10022, 'An invalid argument was supplied')' , what is that mean?
Test result:
D:\calvin-base-master\calvin\scripts>csdeploy test1.calvin
2015-07-24 14:12:07,157 INFO     calvin.calvin.runtime.north.calvincontrol: Listening on: localhost:5001
Traceback (most recent call last):
File "c:\python27\scripts\csdeploy-script.py", line 9, in
load_entry_point('calvin==0.1', 'console_scripts', 'csdeploy')()
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\Tools\deploy_app.py", line 173, in main
select.select([], [], [], timeout)
select.error: (10022, 'An invalid argument was supplied')
2015-07-24 14:12:07,578 INFO     calvin.StandardOut: StandardOut: 1
2015-07-24 14:12:07,687 INFO     calvin.StandardOut: StandardOut: 2
2015-07-24 14:12:07,796 INFO     calvin.StandardOut: StandardOut: 3
2015-07-24 14:12:07,905 INFO     calvin.StandardOut: StandardOut: 4
2015-07-24 14:12:08,015 INFO     calvin.StandardOut: StandardOut: 5
2015-07-24 14:12:08,124 INFO     calvin.StandardOut: StandardOut: 6

It appears that passing 3 empty lists to select.select() gives this error under Windows. Since the select here simply a wait, I think the error is non-critical.
-----Original Message-----
From: deven2014<EMAIL_ADDRESS>Received: fredag, 24 jul 2015, 14:18
To: EricssonResearch/calvin-base<EMAIL_ADDRESS>Subject: Re: [calvin-base] run the test scripts receive some error info (#6)
Yes. It seems the bugs have been fixed. I updated calvin_network.py and ran the test script, the errors 'Unhandled Error' and 'exceptions.KeyError: 'calvinip'' had gone.
But I notice there a statement 'select.error: (10022, 'An invalid argument was supplied')' , what is that mean?
Test result:
D:\calvin-base-master\calvin\scripts>csdeploy test1.calvin
2015-07-24 14:12:07,157 INFO calvin.calvin.runtime.north.calvincontrol: Listening on: localhost:5001
Traceback (most recent call last):
File "c:\python27\scripts\csdeploy-script.py", line 9, in
load_entry_point('calvin==0.1', 'console_scripts', 'csdeploy')()
File "C:\Python27\lib\site-packages\calvin-0.1-py2.7.egg\calvin\Tools\deploy_app.py", line 173, in main
select.select([], [], [], timeout)
select.error: (10022, 'An invalid argument was supplied')
2015-07-24 14:12:07,578 INFO calvin.StandardOut: StandardOut: 1
2015-07-24 14:12:07,687 INFO calvin.StandardOut: StandardOut: 2
2015-07-24 14:12:07,796 INFO calvin.StandardOut: StandardOut: 3
2015-07-24 14:12:07,905 INFO calvin.StandardOut: StandardOut: 4
2015-07-24 14:12:08,015 INFO calvin.StandardOut: StandardOut: 5
2015-07-24 14:12:08,124 INFO calvin.StandardOut: StandardOut: 6
—
Reply to this email directly or view it on GitHubhttps://github.com/EricssonResearch/calvin-base/issues/6#issuecomment-124501543.

OK, Thank you for your help. I am trying to do another test(deploy 2 actors in different runtimes and connect the two actor) also met some problem. I refer in another issue. So I think I can close this issue now.


Add target libraries/executables to executable's RPATH

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

xref: https://github.com/conda-forge/cuda-feedstock/issues/10
Only libnvvp/nvvp binary executable needs patching here.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

In the test phase on CI, this had a clobbering warning
ERROR:conda.stderr:
ClobberWarning: This transaction has incompatible packages due to a shared path.
  packages: conda-forge/linux-64::cuda-nvprof-12.6.80-hbd13f7d_0, local/linux-64::cuda-nvvp-12.6.80-hbd13f7d_1
  path: 'LICENSE'

done
Executing transaction: ...working... ERROR:conda.stderr:
ClobberWarning: Conda was asked to clobber an existing path.
  source path: /home/conda/feedstock_root/build_artifacts/pkg_cache/cuda-nvvp-12.6.80-hbd13f7d_1/LICENSE
  target path: /home/conda/feedstock_root/build_artifacts/cuda-nvvp_1730696031572/_test_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placeh/LICENSE

done

This may be nothing as it is talking about the license files clobbering, which doesn't make a lot of sense. So will try restarting. If we still see it, we may want to take a closer look

@conda-forge-admin , please restart CI

For some reason CI couldn't checkout the PR. Restarting again
@conda-forge-admin , please restart CI

Going to try doing this manually

@conda-forge-admin , please re-render

Hi! This is the friendly automated conda-forge-webservice.
I tried to rerender for you, but it looks like there was nothing to do.
This message was generated by GitHub actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/11673615986.

It seems CI is just misbehaving. To fix CI, we may need to try...

Pushing additional commits to this PR
Closing this PR and opening a new one

Thanks Billy! 🙏
As discussed yesterday, the clobbering warning is a real issue. However it is tangential to the issue we are solving here.
To follow up on clobbering, have filed upstream issue: https://github.com/conda-forge/cuda-feedstock/issues/52

Also noticed there was a second PR opened with these changes: https://github.com/conda-forge/cuda-nvvp-feedstock/pull/15
Did we want to stick with this PR or is there something else needed in that PR?

Also noticed there was a second PR opened with these changes: #15
Did we want to stick with this PR or is there something else needed in that PR?

I just closed #15 :) I had opened it because this PR was broken but now it seems working now.

Ah right the CI issues. Thanks Billy! 🙏
Ok let's get this in then


No link definition found with markdown reference

VS Code Version: 1.72.1
OS Version: Windows 11

Steps to Reproduce:
...

- [vuepress-plugin-blog2][blog2]: Blog plugin for VuePress2

...

[blog2]: https://vuepress-theme-hope.github.io/v2/blog/

Getting:
No link definition found: 'vuepress-plugin-blog2' (link.no-such-reference)

I do think this is a incorrect warning,

Duplicate of https://github.com/microsoft/vscode/issues/162691


Create method to transform vertext set.

The vertexSet() method returns a UnModifiableCollection which is only a wrapper around the original collection.
This makes sure reads are not dirty.

@gengmao


HEAP Explodes Under heavy load

http://www.rabbitmq.com/tutorials/tutorial-three-go.html
I've been debugging some golang code I maintain that uses this library to spin up golang consumers for rabbitmq.
It seems that the amqp.Delivery is always allocated on the heap in my runtime and golang never gets around to free()'ing them.
To test my sanity I hooked up the example log-file consumer here to a heavily overloaded rabbitmq bus - and just like my more complex examples the VIRT/RES shoots up linearly overruntime until the program crashes. Is this normal/expected behavior or something I can tune with rabbitMQ?
I'm running on RHEL6.10 using Golang 1.9+.  I pulled the heap profile using PPROF and saw 98% in amqp.Delivery from the recvCon(method. Similar for the example consumer.
V/r,

It would be great to provide code and exact reproduction / diagnosis steps for people like me who aren't as familiar with profiling tools. Or, a PR with a fix. Anything you can do to reduce the amount of time maintainers have to guess and write code to try and reproduce what you report is greatly appreciated.

https://github.com/rabbitmq/rabbitmq-tutorials/blob/master/go/receive_logs.go
If you compile this and run it under heavy load, the heap explodes even if you pipe output to /dev/null.
Is this normal? I've compiled with pointer analysis on, and I notice that when reading from the consumer channel the local variable for the delivery is ALWAYS ESCAPING TO THE HEAP.
If I modify the code somewhat to keep the local delivery variable from escaping , the heap doesn't grow out of control and the memory profile stays flat - say by changing to loggin the length of the ContentType instead of the whole boddy.

https://play.golang.org/p/0aS4X9LaTQ3

https://github.com/carbonblack/cb-event-forwarder/blob/master/test/stress_rabbit/stress_rabbit.py

(Above is a sample of the code i'm using to test the consumer and the stressor I use to dump messages onto rabbit MQ)

ALWAYS ESCAPING TO THE HEAP.

There's no need to use all caps.
The tutorial code does not set a QoS (prefetch) value, so there is no limit on the number of messages that RabbitMQ will try to send to it. Go's GC may not be able to keep up, or there may be an issue in this library where the buffer used for the message body isn't managed correctly.
I suspect that changing the tutorial code to use QoS and to not use auto-ack would mitigate this issue. This would require sending an ack within the for...range loop.

Thanks luke :) I tried adding a select-default to see if the consuming queue stays empty/full under runtime and it was staying pretty empty. I'll try this and report back.

I modified 'util.go' above from the playground above , to force manual acking of the messages.
This did not change my results, at all. What QoS parameters are relevant?
22252 bit9qa    20   0  279m  10m 2184 S 148.1  0.1   0:06.52 util
command-line-arguments
./util.go:11:28: msg escapes to heap
./util.go:9:33: leaking param: msg
./util.go:11:28: err escapes to heap
./util.go:9:33: leaking param: err
./util.go:11:27: failOnError ... argument does not escape
./util.go:66:12: func literal escapes to heap
./util.go:66:12: func literal escapes to heap
./util.go:64:24: main make(chan bool) does not escape
command-line-arguments
./util.go:11:28: msg escapes to heap
./util.go:9:33: leaking param: msg
./util.go:11:28: err escapes to heap
./util.go:9:33: leaking param: err
./util.go:11:27: failOnError ... argument does not escape
./util.go:66:12: func literal escapes to heap
./util.go:66:12: func literal escapes to heap
./util.go:68:48: d.Body escapes to heap
./util.go:64:24: main make(chan bool) does not escape
./util.go:68:35: main.func1 ... argument does not escape
22288 bit9qa    20   0 2903m 2.7g 2180 S 167.5 17.2   0:14.34 util
The difference in these two runs, is that I commented out the multivaradic function that escapes the delivery in the second. Are there relevant unit tests for this library that exercise this function?
I'll add the pprof to the goplayground shortly.

That's the documented trade-off betweeen manual and automatic acknowledgement modes: the higher the prefetch, the higher will peak consumer memory consumption but also higher the throughput (up to a point).


fixes plot locations and changes PI

Closes #1
This PR

fixes plot locations
changes the PI to Caleb Brooks

Closes #6


Add logo hyperlink to repo

Made the logo a hyperlink to the repo

Yeah, sure

Applied requested changes.


microk8s command isn't installed on Windows

The official installation guide 1 let us open cmd and run microk8s  command though, microk8s command isn't available. cmd returned the following error message. Is the installation guide correct?
> microk8s
'microk8s' is not recognized as an internal or external command,
operable program or batch file.

I looked for microk8s executable in my computer (C:\Program Files, C:\Program Files (x86), %USERPROFILE%\AppData), but I couldn't find that executable.

Hi @pjxiao
Thank you for reporting that. We have a bug in our docs, the link of the "Download MicroK8s for Windows" button should point to [1]. Could you try that installer?
Apologies for the inconvenience. We are working to fix this.
[1] https://github.com/ubuntu/microk8s/releases/download/installer-v1.0.0/microk8s-installer.exe

Hi @ktsakalozos
I succeeded in installing microk8s by using microk8s-installer.exe and confirmed that a MicroK8s launched. Thank you.
Now, my problem has been resolved but that link in the document is still broken. Shouldn't I close this issue until the document is fixed?

Pleased to hear this worked for you. We track the issue in [1] and there is already a PR under review.
We can close this issue.
[1] https://github.com/canonical-web-and-design/microk8s.io/issues/241

Again Microsoft Windows has a tutorial with a product that doesn't work with Microsoft Windows.  Linux here we come again!!!!!


Create Ritik.tsx by Ritik Pandey

Please note that this is a basic console-based example. In a real application, you would likely want to use some kind of user interface (e.g., web or mobile) to interact with the app and display notes visually. You can also incorporate features like saving notes to a database or local storage for persistence.

done


CommandError: Can't find msgfmt. Make sure you have GNU gettext tools 0.15 or newer installed.

Note: for support questions, please use the cookiecutter-django tag on stackoverflow. This repository's issues are reserved for feature requests and bug reports. If you need quick professional paid support for your project, contact<EMAIL_ADDRESS>

**I'm submitting a ... **

[ ] bug report
[ ] feature request
[ ] support request => Please do not submit support request here, see note at the top of this template.

Do you want to request a feature or report a bug?

What is the current behavior?

sudo docker-compose -f local.yml run django python manage.py compilemessages

CommandError: Can't find msgfmt. Make sure you have GNU gettext tools 0.15 or newer installed.

But in OS gettext and msgfmt already installed..

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

This happens in any cookieecutter-django project, where I try to use gettext

What is the expected behavior?

I want to create files in the locale folder in the languages I have chosen.

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, gitter, etc)

You're using Docker, hence, gettrxt must be installed in the django services Dockerfile.

Add gettext and msgfmt to your compose/local/django/Dockerfile and re-build the image.
RUN apt-get update && apt-get install -y \
gettext \
msgfmt \

@sfdye
E: Unable to locate package msgfmt

@narnikgamarnikus
which msgfmt

It should be installed already.


Incomplete method_name argument documentation in estimate_effect

Ask your question
It would be very helpful to have more detail about the method_name argument of the estimate_effect method.
Currently, some examples of possible options are provided, but they are not comprehensive.
https://www.pywhy.org/dowhy/main/_modules/dowhy/causal_model.html#CausalModel.estimate_effect
Moreover, this seems not to be entirely correct
 specific estimation method: "[backdoor/iv].estimation_method_name". Following methods are supported.
What about frontdoor methods such as frontdoor.two_stage_regression?
Expected behavior
I would like the documentation to list all of the possibilities for native method_names (I understand the econml method names have their own documentation).

Thanks for raising thsi @matsuobasho . Will add it to the docs.


Additional systems tests and some fixes for bugs found

I'm still a bit confused why this PR is so huge... From the title (and no description) it seems it should be a fairly small number of commits/changes - but it has many commits from both @GDYendell and @MJGaughran...

OK, I've taken a look at the history and it looks like it's just a long-running branch. The commits don't appear elsewhere (at a glance at least).
The title seems to indicate two kinds of changes. And no summary description on the PR makes it harder to review. There are a couple of re-factoring exercises in there - which would have been nice to have in the original description when you raised the PR.
I've had a quick scan through the changes, but I'm having to rely on the green lights from our continuous integration and trust it's all OK :smile:


[Fix] Consistent naming and using of StrEnums instead of string literals

Fixes #518

To not forget to harmonize where previous strings were used. For instance get_fm_qubits in utils.py

Hmm. Good catch. This constructor is independent of the configs created here, but very similar use indeed. I will add it, and also rename fm_strategy to multivariate_strategy since that is what that property is called in types. It might be a slight breaking change for someone using this constructor (However, I don't think it is being used much, so should not cause too much bother on the user side).


chore: fix clippy warnings from Rust release 1.69

Fixed running cargo clippy --fix

Codecov Report

Merging #263 (683cc03) into development (9cd7348) will decrease coverage by 0.02%.
The diff coverage is 28.57%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@               Coverage Diff               @@
##           development     #263      +/-   ##
===============================================
- Coverage        45.38%   45.37%   -0.02%
===============================================
  Files               85       85
  Lines             7231     7231
===============================================
- Hits              3282     3281       -1
- Misses            3949     3950       +1

Impacted Files
Coverage Δ

src/model_selection/kfold.rs
59.52% <ø> (ø)

src/readers/csv.rs
56.36% <0.00%> (ø)

src/linalg/basic/matrix.rs
48.83% <33.33%> (ø)

... and 10 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@Mec-iS Please review and merge if you think that it is ok


move release scripts out of open source repo

I'd like to propose that we move our release-specific code out of the open source repo and into a private repo.
This would include code such as:

https://github.com/docker/docker/blob/master/hack/release.sh
https://github.com/docker/docker/blob/master/hack/make/release-rpm
https://github.com/docker/docker/blob/master/hack/make/release-deb

And documentation such as:

https://github.com/docker/docker/blob/master/project/RELEASE-CHECKLIST.md

They contain code that is very specific to the infrastructure of releasing the build artifacts that should not be tied to the version of the code.
Stuff that should still be kept with the open source code are the scripts for actually building the artifacts, like building deb, rpm, etc. packages.
I feel we should still have documentation on how we make decisions about releases so that the open source know what to expect in terms of timeline and such:

https://github.com/docker/docker/blob/master/project/RELEASE-PROCESS.md

/cc @vieux @mlaventure @tiborvass
We should not expect this change to hold up any release schedule. i.e. still use the scripts while they are migrated over to the private repo. When we're confident of the private repo's scripts we can delete from open source repo.

SGTM
/cc @icecrime

I'm a bit in doubt over fully removing the checklist / procedure, as it contains some information that may still be useful (at what point is the API version bumped, where to announce the release, etc.). Otherwise sgtm if we're changing the tooling for our releases

Why is this necessary? This is still an open source project.

@unclejack those scripts are specific to the way we make the releases here at docker. @thaJeztah point on keeping the doc makes sense, but the release scripts themselves are not useful to anyone else.
Note that the scripts that actually generates the deb/rpm aren't going to disappear from the repo.

We used to make Docker releases only with what was open source. Only some credentials were required to make a release. There were no closed source bits used in the pipeline. This was very nice because it made it possible to make those releases through a process.
I do agree some of that could be in a separate repository, but it should still be open source. I don't think there's anything to gain from a closed source repository for release tooling.

@unclejack some of the internal tooling technologies we're using are specific to our needs, such as using aws s3 for storage of artifacts. There are some hard-coded stuff that is there only for a docker public release and may not be desirable for everybody distributing their own docker binaries. Nor do we have an intention to making the release scripts desirable for everybody's situation (not really interested in supporting parameters for release.sh to push to a ftp server instead of aws s3).
We also have more tools and scripts that are specific to our release process that we have not open sourced. We have specific procedures for our infrastructure, like flushing http proxy caches and sending out notifications, that we don't have plans for open sourcing.
However, we do value open source community and will be looking to open source what makes sense if it can be valuable for other people in the community. Our team is still in discussion about what that is specifically, but we do know we desire to split off the release scripts from the main docker code so that we can start to make changes to how things are released on a time cycle different than docker development cycle.
It is interesting to know that you use the release.sh scripts to make your release to aws s3. Do you also use the GPG signing parts of release-deb?

@andrewhsu I'm not making releases right now, but I'll try this out soon. The releases I've mentioned above were the official Docker releases we were making.


windows: html_with_xls extension crashes

html with doc is ok

xls parser fails (ok), parserTypeByFileContent is fishy.

rtf -> odf -> xls (2nd round) -> doc -> ppt -> eml -> html.
actually failing at meta.

problem in html meta parser

lat_modification_date crash

not checking string_to_date return value


Works only once problem

Spin animation works only when changing mustStartSpinning prop first time, otherwise roulette directly showing the result without animation. If I manually remove the .started-spinning class from DOM and start again it works fine. I didn't try but maybe these changes fix the problem.
const startSpinning = () => {
    setHasStartedSpinning(true);
    setHasStoppedSpinning(false) // +
    setTimeout(() => {
      setHasStartedSpinning(false); // +
      setHasStoppedSpinning(true);
    }, START_SPINNING_TIME + CONTINUE_SPINNING_TIME + STOP_SPINNING_TIME - 300);
  };

i have the same problem. in the initial spin, the animation works fine, but when i spin again the wheel the animation isnt working properly

I am looking for solution also.

@ahmetcanaydemir have you found the solution?

Also looking for solution, I thing we need to render the whole component again on ever button click

@ahmetcanaydemir Hey! Just pushed a multi-spin feature, you can find a basic example here:
https://github.com/effectussoftware/react-custom-roulette#multi-spin
Could you try it out and tell me if it's working as expected?

I don't think it works - see https://wheel.wss.repl.co/<EMAIL_ADDRESS>Btw, is there any way to control wheel speed? (or calculate time when it will finish spinning?)

@and7ey Can you show exactly how are you calling the Wheel component? If you see in the example, you would have to add something like this for it to work:
onStopSpinning={() => {
     setMustSpin(false)
}}

In the /example folder there's a working example of this feature.
Also, no. At the moment there's only one spin speed, we will discuss it and see if we can add this feature on a future release!

You may see the code at the second link I gave -<EMAIL_ADDRESS>I just copied your example.

@and7ey Just saw you had version 1.1.4 in your package.json. Try upgrading to 1.1.5 and it should work

Thanks, it works well now.
Sorry for the confusion - I was checking the packages tab at repl.it and it was showing the latest version 1.1.5.