Support custom timezone

Expand the concept of today.
Today can be two different dates based on timezone.
In some situations you want to set the context timezone different than the client machine and by adding timeZone: React.PropTypes.string prop this can be achieved.

[Current coverage][cc-pull] is 92.26%

Merging [#506][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.13%

5 files in src were modified. more

Misses +1
Hits +2

@@             master       #506   diff @@
==========================================
  Files            10         10
  Lines           329        336     +7
  Methods          13         13
  Messages          0          0
  Branches         48         51     +3
==========================================
+ Hits            304        310     +6
- Misses           15         16     +1
  Partials         10         10

[][cc-pull]

Powered by Codecov. Last updated by [de50699...688ca75][cc-compare]
[cc-base-branch]: https://codecov.io/gh/Hacker0x01/react-datepicker/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/Hacker0x01/react-datepicker/compare/de506996b3cf2c7467441a261d8ba268037e16b5...688ca75b9c2ee91dd198b7aa2f203729bc39ae49
[cc-pull]: https://codecov.io/gh/Hacker0x01/react-datepicker/pull/506?src=pr

Hey @cristiango, thanks for the contribution.  This seems okay but I'm wondering if this is the wrong solution to your problem; since you mention timezones I wonder if a fix to #498 should be implemented instead.  FWIW I generally prefer fixing the root of the problem rather than giving a workaround, and since this is an API addition I want to make sure it's the right thing to support in the long term.

@rafeememon I've opened that issues a couple of times an read an re-read it over. Not even sure if fixing the UTC problem will solve this problem

You are in UTC+2 and want to select today in UTC-9.

The fact that the controls show information about today make is zone dependent

Sorry, the relevant part of the other bug I meant to highlight was the idea of adding a timezone offset option (which is just a more general case of adding a UTC flag).  What do you think?

Yes indeed adding UTC flag will make more sense in the long run.
I will try to come up with a solution for this

@rafeememon what do you think about the new solution?

Ping @rafeememon


Recommendation to add titles to links?

While re-implementing STAC Browser, it more and more often occurs to me that missing titles lead to a bad user experience.
For example, I'd like to show a "breadcrumb" and want to show the title or root catalog and parent without actually loading up those files, I'd need titles for those links as otherwise, I need to show something generic that is later replaced with the actual titles once the file has been loaded.
As most of these catalogs have titles anyway, it should be easy enough to list them in the links, right? So I'm thinking whether we should recommend adding titles to links such as item, child, root, and parent.

I'm definitely into it, see https://github.com/stac-utils/stactools/issues/22 where I wanted it to be an option for STAC Tools.
I don't know that this clears the bar for me as worth resetting our 1.0.0 counter with another release candidate. I guess if we put it in best practice then maybe it doesn't need a new release candidate?
I'd also be in favor of making it the default in pystac, and we can recommend it in the api spec. And then put it as a PR for a 1.0.1 release (do be done when there's a few good issues to get in).

I don't think such a recommendation would need a reset of the 1.0.0 counter as it's just a best practice, similarly to the other issues in https://github.com/radiantearth/stac-spec/milestone/23, which we may integrate but likely won't reset the counter.

Cool, I think the main thing to me is to not touch the actual spec documents (though I suppose I'm open to it). Putting it in best practice sounds good. And also updating all examples to reflect it also would be good.


GPU addon fails to install drivers due to GPG error

Summary

Installation of the GPU addon fails because the NVIDIA GPU Driver containers cannot install the required driver packages with apt due to outdated/missing GPG keys:
W: GPG error: https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64  InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY A4B469963BF863CC
Nvidia changed their CUDA Linux GPG repository key on April 28th but v1.8.2 of the GPU operator uses version 470.57.02 of the 'NVIDIA GPU Driver' image which only contains the old key.
What Should Happen Instead?

Nvidia Driver installation should complete successfuly and all GPU operator installation should progress normally.
Reproduction Steps

microk8s enable gpu
check output of nvidia-driver-ctr of the nvidia-driver-daemonset for GPG Errors

Introspection Report

inspection-report-20220518_161245.tar.gz
Can you suggest a fix?

Install v1.10+ of the GPU operator with the addon since it uses a 'NVIDIA GPU Driver' image which contains the new GPG key.
Are you interested in contributing with a fix?

Thank you for reporting this @CJLvU and apologies for the late reply. We will update the GPU addon as soon as possible.


Food Pheromones

Please add the food pheromones similarly to the home_pheromones. They should be colored in green.

Hi, as a first try, I added the food_pheromones for each ant, that is crossing a food_source. The movement functuion has not been changed, this will have to be done in another step. Please go through the code, test it and let me know if there any problems you are encountering. You can review the code here: https://github.com/lucasthierry17/Ant_Project/blob/lucas/pygame_grids.py

Hey, your code works!
Unfortunately I couldn't solve the problem yet. Maybe you could help to identify what we have to change in order to update the values of pheromones in positions where pheromones already are placed. @Fouad1806 @svenatgithub
So that the weak pheromones get refreshed when other ants go over that position and place their pheromone trail.

So I uploadad a new main.py in my branch, which integrates a backend_pherone method, that is important to manipulate the movemant of the ant. If they use this as their orientation, we sucessfully manage to get it look like as if the ants follow the visualized pheromones. Like we discussed in Teams.

We've successfully implemented the green pheromones, when the ant is carrying food.


Client connection IP is reported as <IP_ADDRESS>

Is this something cluster and/or mup is doing, or is it a problem with some other package?
Accounts.onLogin (info) ->
  console.log('onLogin', info.connection.clientAddress)
  console.log(info.connection.httpHeaders)

[parlay.io] onLogin <IP_ADDRESS>[parlay.io]
[parlay.io] { host: 'parlay.io',[parlay.io]
[parlay.io]   'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36',[parlay.io]
[parlay.io]   'accept-language': 'en-US,en;q=0.8' }[parlay.io]

Are you using mup SSL?
On Thu, May 7, 2015 at 1:48 PM Loren Sands-Ramshaw<EMAIL_ADDRESS>wrote:

Is this something cluster and/or mup is doing, or is it a problem with
some other package?
Accounts.onLogin (info) ->
console.log('onLogin', info.connection.clientAddress)
console.log(info.connection.httpHeaders)
[parlay.io] onLogin <IP_ADDRESS>[parlay.io]
[parlay.io] { host: 'parlay.io',[parlay.io]
[parlay.io]   'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36',[parlay.io]
[parlay.io]   'accept-language': 'en-US,en;q=0.8' }[parlay.io]
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54.

Yes
On Thu, May 7, 2015 at 1:20 AM, Arunoda Susiripala<EMAIL_ADDRESS>
wrote:

Are you using mup SSL?
On Thu, May 7, 2015 at 1:48 PM Loren Sands-Ramshaw <
<EMAIL_ADDRESS>wrote:

Is this something cluster and/or mup is doing, or is it a problem with
some other package?
Accounts.onLogin (info) ->
console.log('onLogin', info.connection.clientAddress)
console.log(info.connection.httpHeaders)
[parlay.io] onLogin <IP_ADDRESS>[parlay.io]
[parlay.io] { host: 'parlay.io',[parlay.io]
[parlay.io] 'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X
10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135
Safari/537.36',[parlay.io]
[parlay.io] 'accept-language': 'en-US,en;q=0.8' }[parlay.io]
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54.

—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54#issuecomment-99767300.

That's the issue. Since its a SSL terminator it does not write headers.
Check the mupx branch of mup. We have a solution.
On 2015 මැයි 7, බ්‍රහස් at ප.ව. 1.51 Loren Sands-Ramshaw <
<EMAIL_ADDRESS>wrote:

Yes
On Thu, May 7, 2015 at 1:20 AM, Arunoda Susiripala <
<EMAIL_ADDRESS>
wrote:

Are you using mup SSL?
On Thu, May 7, 2015 at 1:48 PM Loren Sands-Ramshaw <
<EMAIL_ADDRESS>wrote:

Is this something cluster and/or mup is doing, or is it a problem with
some other package?
Accounts.onLogin (info) ->
console.log('onLogin', info.connection.clientAddress)
console.log(info.connection.httpHeaders)
[parlay.io] onLogin <IP_ADDRESS>[parlay.io]
[parlay.io] { host: 'parlay.io',[parlay.io]
[parlay.io] 'user-agent': 'Mozilla/5.0 (Macintosh; Intel Mac OS X
10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135
Safari/537.36',[parlay.io]
[parlay.io] 'accept-language': 'en-US,en;q=0.8' }[parlay.io]
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54.

—
Reply to this email directly or view it on GitHub
<https://github.com/meteorhacks/cluster/issues/54#issuecomment-99767300
.

—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54#issuecomment-99767813.

Thank you, I look forward to it being stable and merged into mup.

Okay. Sure.
On 2015 මැයි 7, බ්‍රහස් at ප.ව. 2.02 Loren Sands-Ramshaw <
<EMAIL_ADDRESS>wrote:

Closed #54 https://github.com/meteorhacks/cluster/issues/54.
—
Reply to this email directly or view it on GitHub
https://github.com/meteorhacks/cluster/issues/54#event-299027438.

FYI with Galaxy, info.connection.httpHeaders['x-forwarded-for'] is filled in, and the value is used for info.connection.clientAddress


implement [data_blobs]

This implements support for [data_blobs] for service workers, which lets you bind some data from a file as an ArrayBuffer in service-worker format workers. It also adds a --data-blob cli argument for the same.
Fixes #231

I implemented this mechanically by mirroring the implementation from text_blobs in https://github.com/cloudflare/miniflare/pull/228. Happy to iterate!

!! That would be amazing!


Doesn't teleport to correct coordinates

When using /lc it doesn't teleport you to the correct coordinates. The blockray gets the location of the chunk
Optional<BlockRayHit<World>> c = BlockRay.from(b).stopFilter(BlockRay.onlyAirFilter()).to(a.getPosition().sub(a.getX(), 1, a.getZ())).end();
it should be
Optional<BlockRayHit<World>> c = BlockRay.from(b).stopFilter(BlockRay.onlyAirFilter()).to(a.getPosition().sub(b.getX(), 1, b.getZ())).end()
I believe. This is the conversation where we looked at the issue: https://pastebin.com/raw/Qv3yWHEd

Will be fixed in the next update.


Minor Physics Fixes for Network Visualizer

I made some minor physics changes to the network visualizer, with the help of a tool provided by the graph library.
Personally, I believe it greatly improves the feel of the physics, and it does so without harming the ability to manipulate the graph much, if at all.

Looks good to me! Thanks :)


Performance problems at 0178f8632521dd97339fde7c06f90760de6455bb

We've just finished replacing node-gearman with GearmaNode in our app but in testing we noticed a cpu load increase and a massive drop in performance.
I've run some benchmarks with a php server and a node-gearman vs GearmaNode client and the results are very interesting.
For small payload sizes node-gearman is competitive but (~25% slower) but when the payload gets to about about 10K things start to going south quickly. By the time the job payload is 1MB GearmaNode is processing about ~3 jobs / sec vs node-gearman at ~140 jobs / sec.
The naive benchmarking scripts I used are below.
client
var numCompleted = 0;
var bytesRecieved = 0;

function completeNodeGearman (data) {
    numCompleted++;
    bytesRecieved+= data.length;
}

function completeGearmaNode () {
    numCompleted++;
    bytesRecieved+= this.response.length;
}

setTimeout(function() {
    function fileSizeSI(a,b,c,d,e){
         return (b=Math,c=b.log,d=1e3,e=c(a)/c(d)|0,a/b.pow(d,e)).toFixed(2)+' '+(e?'kMGTPEZY'[--e]+'B':'Bytes')
    }
    console.log(
        "completed %d jobs and %s of payload",
        numCompleted,
        fileSizeSI(bytesRecieved)
    );
    process.exit();
}, 10*1000);

var jobName;
jobName = 'cnt';
jobName = '1K';
jobName = '10K';
jobName = '100K';
jobName = '1M';

if (false) {
    var gearmanode = require('gearmanode');
    gearmanode.Client.logger.transports.console.level = 'error';
    var client = gearmanode.client();
    setInterval(function() {
        var job = client.submitJob(jobName, "");
        job.on('complete', completeGearmaNode);
    }, 1);
} else {
    var NodeGearman = require("node-gearman");
    var nodegearman = new NodeGearman();
    setInterval(function() {
        var job = nodegearman.submitJob(jobName, "");
        job.on("data", completeNodeGearman);
    }, 1);
}

// cnt - GearmanNode ~340 jobs / second, node-gearman ~450 jobs / second
// 1K - GearmanNode ~340 jobs / second, node-gearman ~450 jobs / second
// 10K - GearmanNode ~300 jobs / second, node-gearman ~450 jobs / second
// 100K - GearmanNode ~34 jobs / second, node-gearman ~340 jobs / second
// 1M - GearmanNode ~3 jobs / second, node-gearman ~140 jobs / second

server
<?php

$worker= new GearmanWorker();
$worker->addServer();

$c = 0;
$worker->addFunction("cnt", function ($job) use (&$c) {
    $c++;
    print("job {$c}\n");
    return $c;
});

$onek = str_pad('', 1024);
$worker->addFunction("1K", function ($job) use ($onek) {
    print("job 1K\n");
    return $onek;
});

$tenk = str_pad('', 1024*10);
$worker->addFunction("10K", function ($job) use ($tenk) {
    print("job 10K\n");
    return $tenk;
});

$hundredk = str_pad('', 1024*100);
$worker->addFunction("100K", function ($job) use ($hundredk) {
    print("job 100K\n");
    return $hundredk;
});

$onem = str_pad('', 1024*1024);
$worker->addFunction("1M", function ($job) use ($onem) {
    print("job 1M\n");
    return $onem;
});

while ($worker->work()) {
    continue;
}

Our app spends most of it's time processing around 30 jobs per second but this sometimes bursts to 500+. Payloads are typically small or null but infrequently we push payloads of ~0.1-5MB which is absolutely trashing performance.

Performance optimization can be a time consuming task. I focus on it during weekend.

Thanks Veny - really appreciated.

I think 90% of this is related to the very extensive logging. If you all the calls to winston .log() are removed performance improves massively. In the worst case it appears GearmaNode is only 25% slower than nodegearman when you do this.

yes, you are right, I discovered it too.
I just released v0.2.2 with corresponding fix.


Drawing Classifier should not save batch_size

The drawing classifier saves the batch_size values given in the create(...) call to its state. It's not clear how/if this is used since evaluate(...), predict(...) and predict_topk(...) all take a batch_size parameter.
In generally we don't want to store batch size in model state. Batch size isn't really model dependent but dependent on the machine it is running on.

The evaluate and predict methods shouldn't take a batch size at all. Let's be consistent with OD and AC for now, which do preserve batch size.
In the general case, batch size can affect model quality, so I think it's legitimate for a user to want to know what the batch size was.

I think we need to have a larger discussion here. I'm surprised that the object detector and activity classifier don't have a batch_size parameter on their evaluate(...) and predict(...) methods. All other toolkits that can use the GPU do have this parameter.
To me the batch size is more about the machine that is running the model than the model itself. Consider the scenario where the model is trained on a powerful machine but the model is used on less powerful machines. I think it's reasonable to want different batch sizes.

What toolkits are you referring to that already expose batch size?
In general, if the question is about machine configuration, we should try to configure the batch size ourselves.
If it's about training behavior (e.g. due to batch norm), then it really only makes sense to configure it on the create method.

image_classifier, sound_classifier and drawing_classifier all have a batch_size parameter on the following methods: classify(...), evaluate(...), predict(...) and predict_topk(...).
image_similarity has batch_size on query(...).
style_transfer has batch_size on stylize(...).

Hmm, for image classification and sound classification, we only perform NN inference, so batch size only determines performance. The object detection, activity classification, and style transfer toolkits (all the toolkits with NN training that predate this year) all store the batch size, which at least in principle affects the quality of the final model by determining how many instances inform each iteration's estimate of the gradient, as well as determining how many updates are performed (when total training time is defined by number of epochs). It's quite reasonable for somebody to try training models varying only the batch size, to evaluate the effect on model quality. For that reason, I think we should store the batch size for any toolkit that updates NN weights.
Consequently, I suggest that inference-based methods default to the stored batch size by default, although certainly it's reasonable for users to override that for performance reasons. The same GPU can likely accommodate larger batch sizes for inference than for training


Update to Fody Version 2

Fody Version 2 is out and you will need to do an update for your addin to be usable with it
Specifically:

Update to the newest Fody.Cecil nuget
Change the min dependency range for Fody to be at least 2.0

Please ping me if u need help

Hi Simon,
Thanks for the notice.  This project is more-or-less abandonware - it hasn't seen any development for years now.  I would be surprised if anyone uses it; if someone does and has interest, I'd gladly hand it over.  I won't be doing any further work on it myself.

@benjamin-bader , do you know any project which is like yours? I mean, I feel very comfortable to develop DI with Android, but I need a complement to use with Ninject on C#.

Hi Marcos,
I'm not sure what people use with Xamarin these days; I haven't done any mobile C# work in 4-5 years, it seems, and so am pretty out-of-touch.  Last time I checked, TinyIOC was popular but unsuited to the kind of application architectures I was working with.
If you're not targeting iOS, I think ninject should work fine - iOS, with its restrictions on runtime codegen, is the limiting factor for most Xamarin DI frameworks.

A quick Google search seems to indicate that the Unity container is officially recommended by Xamarin/MSFT: https://developer.xamarin.com/guides/xamarin-forms/enterprise-application-patterns/dependency-injection/
I've never used it and can't vouch for it, but it would be a worthwhile topic to investigate.

Sorry i dont have capacity to take this over. Perhaps add a note in the readme saying “no longer being actively developed”

Sounds like a fine idea!


Decrease duplication by removing redundant LNil.singletonFormat

object LNil extends LNil, so there's no need for a JsonFormat[LNil.type].

This doesn't work because everything is invariant, which I guess is a design choice of the library (I noticed a bunch more duplication because of it).
Perhaps it would be good to explain why that choice makes sense for sjson-new.

Given a type Apple, treating it as an Apple or its parent trait Fruit has different effect in serialization.

Shouldn't there just be a priority system? Use the format for Apple is present, and the one for Fruit if not?

In general I prefer a typeclass to be invariant unless it makes it impossible to use in a normal fashion.


Encoding issues

While improving our automation process, i stumbled upon a bunch of files, that seem to be wrong encoded (UTF16). On Windows, this doesn't seem to be a big problem, but on Linux, these files are garbled with asian nonsense, e.g.:
Id: ChristianSchenk.MiKTeX
਍嘀攀爀猀椀漀渀㨀 ㈀⸀㤀⸀㜀㐀㐀㈀ഀഀ
Name: MiKTeX
਍倀甀戀氀椀猀栀攀爀㨀 䌀栀爀椀猀琀椀愀渀 匀挀栀攀渀欀ഀഀ
License: Redistributing MiKTeX
਍䰀椀挀攀渀猀攀唀爀氀㨀 栀琀琀瀀猀㨀⼀⼀洀椀欀琀攀砀⸀漀爀最⼀挀漀瀀礀椀渀最ഀഀ
AppMoniker: miktex
਍吀愀最猀㨀 琀攀砀Ⰰ 琀礀瀀攀猀攀琀琀椀渀最Ⰰ 氀愀琀攀砀Ⰰ 琀攀砀眀漀爀欀猀ഀഀ
Description: MiKTeX (pronounced mick-tech) is an up-to-date implementation of TeX/LaTeX and related programs. TeX is a typesetting system written by Donald Ervin Knuth who says that it is intended for the creation of beautiful books - and especially for books that contain a lot of mathematics.
਍䠀漀洀攀瀀愀最攀㨀 栀琀琀瀀猀㨀⼀⼀洀椀欀琀攀砀⸀漀爀最⼀ഀഀ
Installers:
਍  ⴀ 䄀爀挀栀㨀 砀㘀㐀ഀഀ
    Url: https://muug.ca/mirror/ctan/systems/win32/miktex/setup/windows-x64/basic-miktex-2.9.7442-x64.exe
਍    匀栀愀㈀㔀㘀㨀 䔀㌀㄀䔀㔀㐀㔀　㐀㔀㔀　㄀㠀㜀䈀㤀㈀㔀㤀䄀䄀㤀㔀䘀㤀㈀㄀㔀㜀㐀㔀㠀㘀㤀　　㌀　䐀　　㔀㤀㐀㜀㌀㈀㌀㠀䈀㠀䈀㔀㠀㜀㠀㔀㐀䄀㈀㌀㠀䈀ഀഀ
    InstallerType: exe
਍    匀眀椀琀挀栀攀猀㨀ഀഀ
      Silent: "--unattended"
਍      匀椀氀攀渀琀圀椀琀栀倀爀漀最爀攀猀猀㨀 ∀ⴀⴀ甀渀愀琀琀攀渀搀攀搀∀

List of affected files:

https://github.com/microsoft/winget-pkgs/blob/master/manifests/ChristianSchenk/MiKTeX/2.9.7442.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/CodeLite/CodeLite/14.0.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/DasKeyboard/DasKeyboard/3.2.6.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Files-UWP/FilesUWP/<IP_ADDRESS>.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Files-UWP/FilesUWP/0.9.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Files-UWP/FilesUWP/0.9.1.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Firetrust/MailWasherPro/7.12.29.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Gauge/Gauge/1.0.6.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/GeoGebra/GeoGebraClassic/6.0.583.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/GeoGebra/GeoGebraClassic6/6.0.583.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/GeoGebra/Geometry/6.0.583.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/GeoGebra/GraphingCalculator/6.0.583.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/GnuWin32/MakeforWindows/3.81.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Insomnia/InsomniaDesigner/2020.2.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/IsWiX/IsWiX/4.14.5.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/KKBOX/KKBOX/7.2.30.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Krisp/Krisp/1.14.3.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/LyX/LyX/<IP_ADDRESS>.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/MarkText/MarkText/0.16.1.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Microsoft/MouseAndKeyboardCenter/<IP_ADDRESS>.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Microsoft/dotnet/5.0.100-preview.4.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/MongoDB/Compass/Community/1.21.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/MongoDB/Compass/Full/1.21.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/MongoDB/Compass/Isolated/1.21.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/MongoDB/Compass/Readonly/1.21.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Mu/Mu/1.0.3.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/NagleCode/PacketSender/6.2.3.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/NimbusWeb/NimbusWeb/6.10.34.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/ONLYOFFICE/DesktopEditors/5.5.1.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/OSGeo/QGIS/3.12.3.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/PicoTorrent/PicoTorrent/0.18.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Plex/Plexamp/3.0.3.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/RStudio/RStudio/1.3.959.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Renode/Renode/1.9.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/RevoUninstaller/RevoUninstaller/2.1.5.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/RevoUninstaller/RevoUninstallerPro/4.3.1.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/SMPlayer/SMPlayer/20.4.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TGRMNSoftware/BulkRenameUtility/<IP_ADDRESS>.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TTYPlus/MTPutty/1.7.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TechSmith/Camtasia/2020.0.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TechSmith/Snagit/6.10.34.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TeraTermProject/TeraTerm/4.105.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TheHandBrakeTeam/HandBrake/1.3.2.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/TonyPottier/ImageView/2.0.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/VivaldiTechnologies/Vivaldi/3.0.1874.38.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Zap/Zap/2.9.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/Zettlr/Zettlr/1.6.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/canonical/MicroK8s/2.0.0.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/canonical/Multipass/1.2.1.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/gnupg/GnuPG/2.2.20.yaml
https://github.com/microsoft/winget-pkgs/blob/master/manifests/isaaclevin/presencelight/2.0.49.yaml

I already wrote something to fix this, however i'm limited to one file per PR, so i will have to create 51 pull requests.
@KevinLaMS @denelon I would prefer to create a branch where i push all fixed files at once. When done, I would link it so you could grab and merge it. Or is there no way around the 1 file / PR limitation?

Here's the branch with the fixed files: https://github.com/SoftCreatR/winget-pkgs/commit/ba2819a10146af12c026ea83d66ed78661133865

There are also significantly more that are using us-ascii encoding
$ find manifests/ -type f -exec file --mime {} \; | grep "charset=us-ascii" | wc -l
553

Even more than are using UTF-8
$ find manifests/ -type f -exec file --mime {} \; | grep "charset=utf-8" | wc -l
156

I think requiring UTF-8 encoding is probably the best way forward.

I just found/fixed these, because they cannot be read on a linux machine. Good examples are https://wingetit.com and https://winstall.app where affected manifests are not listed. On https://www.winget.it I already fixed it, regardless of my PR.


[GSSOC'23]  To Add Graphical User Interface(GUI)  in QR-Code-Bot

Hello @neelshah2409 , I can add graphical interface window using the "custom tkinter" library of python in QR Code Bot.
I'll be glad if you assign this task to me.

@neelshah2409
@neelshah2409

@neelshah2409
@Shubhanshu156
@Shubhanshu156


Module build failed: ReferenceError: Unknown plugin "system-import-transformer"

@tofumatt @thgreasi
I get this error when building my project and using the v1.3.0 of localforage and webpack (with babel):
Module build failed: ReferenceError: Unknown plugin "system-import-transformer"
As per your Readme instructions, I use the following code to require localforage:
require('script!localforage');
I also tried import localforage from 'localforage'; but I get the same error.
What needs to be changed with this setup?
Thank you!

Are you targeting the src folder?

In 1.3 you don't need to use require('script!localforage');, a plain require should work (we should change that in README). The dist files are precompiled es5 and are bundled with webpack.
If you try to make your own build using the src files then you should install the system-import-transformer.
https://github.com/thgreasi/babel-plugin-system-import-transformer

@thgreasi
Thanks, indeed I added the "babel-plugin-system-import-transformer": "^1.1.4" in my package.json and it now works. I would recommend that this is documented somewhere as other developers may also want to build solutions with webpack having localforage as an 'import'.


max() arg is an empty sequence error on listing empty tasks table

If I have a pyproject.toml file with an empty [tool.taskipy.tasks] table, taskipy.help.HelpFormatter.print errors out on the call to max with "max() arg is an empty sequence". I'd expect that there should instead be an empty table printed or something like "No tasks."
$ ls
pyproject.toml
$ cat pyproject.toml
[tool.taskipy.tasks]
$ task -l
max() arg is an empty sequence
$ echo $?
1

$ echo 'test_task = "echo 'test'"' >> pyproject.toml
$ cat pyproject.toml
[tool.taskipy.tasks]
test_task = "echo test"
$ task -l
test_task echo test

Environment:
$ pip list
Package    Version
---------- -------
colorama   0.4.5
pip        22.0.4
psutil     5.9.1
setuptools 58.1.0
taskipy    1.10.2
tomli      2.0.1

Hey! Thanks for the bug report!
I fixed the bug and opened a PR here: #52
Please review when you have some free time and I'll merge it once approved :)

Fix released as taskipy 1.10.13


Autocomplete from extension for extension file type not working in v1.49.2

The extension has not been updated since 2017 so this issue cannot be the fault of the extension which has been working fine ever since. Please do not instantly close my issue.
Issue Type: Bug
My autocomplete/tab complete has randomly broken. It was working fine a couple of days ago. I did not change any settings. It was almost like I accidentally pressed a keyboard combination that managed to break it.
It works fine for every language except this:
https://marketplace.visualstudio.com/items?itemName=aStonedPenguin.glua
Upon typing something and pressing tab, it just shows the tab completion popup with just "Loading..." indefinitely:

I have tried disabling the "glualint" extension which did not fix the issue.
My autocomplete setting:

I also tried downgrading to v1.48.2 but that did not fix anything.

Old grammar file: file:///c%3A/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/extensions/lua/syntaxes/lua.tmLanguage.json.
New grammar file: file:///c%3A/Users/billy/.vscode/extensions/astonedpenguin.glua-1.1.0/syntaxes/lua.tmLanguage
register @ TMScopeRegistry.ts:43
mainThreadExtensionService.ts:65 [[object Object]]Cannot read property 'document' of undefined
$onExtensionRuntimeError @ host.ts:10
mainThreadExtensionService.ts:66 TypeError: Cannot read property 'document' of undefined
	at Array. (c:\Users\billy\.vscode\extensions\goz3rr.vscode-glualint-0.5.0\out\glualintProvider.js:19:90)
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:495)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:821:892
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at b.acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:699:482)
	at b.$acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:697:401)
	at g._doInvokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:464)
	at g._invokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:156)
	at g._receiveRequest (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:858:817)
	at g._receiveOneMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:857:623)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:855:691
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1047:649
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at t.PersistentProtocol._receiveMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:261:451)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:258:489
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at p.acceptChunk (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:851)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:203
	at Socket.t (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:263:54)
	at Socket.emit (events.js:223:5)
	at addChunk (_stream_readable.js:309:12)
	at readableAddChunk (_stream_readable.js:290:11)
	at Socket.Readable.push (_stream_readable.js:224:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
$onExtensionRuntimeError @ host.ts:10
listWidget.ts:726 List with id 'list_id_10' was styled with a non-opaque background color. This will break sub-pixel antialiasing.
style @ listWidget.ts:675
listWidget.ts:726 List with id 'list_id_11' was styled with a non-opaque background color. This will break sub-pixel antialiasing.
style @ listWidget.ts:675
mainThreadExtensionService.ts:65 [[object Object]]Cannot read property 'document' of undefined
$onExtensionRuntimeError @ host.ts:10
mainThreadExtensionService.ts:66 TypeError: Cannot read property 'document' of undefined
	at Array. (c:\Users\billy\.vscode\extensions\goz3rr.vscode-glualint-0.5.0\out\glualintProvider.js:19:90)
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:495)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:821:892
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at b.acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:699:482)
	at b.$acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:697:401)
	at g._doInvokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:464)
	at g._invokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:156)
	at g._receiveRequest (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:858:817)
	at g._receiveOneMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:857:623)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:855:691
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1047:649
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at t.PersistentProtocol._receiveMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:261:451)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:258:489
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at p.acceptChunk (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:851)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:203
	at Socket.t (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:263:54)
	at Socket.emit (events.js:223:5)
	at Socket.EventEmitter.emit (domain.js:475:20)
	at addChunk (_stream_readable.js:309:12)
	at readableAddChunk (_stream_readable.js:290:11)
	at Socket.Readable.push (_stream_readable.js:224:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
$onExtensionRuntimeError @ host.ts:10
mainThreadExtensionService.ts:65 [[object Object]]Cannot read property 'document' of undefined
$onExtensionRuntimeError @ host.ts:10
mainThreadExtensionService.ts:66 TypeError: Cannot read property 'document' of undefined
	at Array. (c:\Users\billy\.vscode\extensions\goz3rr.vscode-glualint-0.5.0\out\glualintProvider.js:19:90)
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:495)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:821:892
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at b.acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:699:482)
	at b.$acceptDocumentsAndEditorsDelta (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:697:401)
	at g._doInvokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:464)
	at g._invokeHandler (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:860:156)
	at g._receiveRequest (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:858:817)
	at g._receiveOneMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:857:623)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:855:691
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:1047:649
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at v.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:256:381)
	at t.PersistentProtocol._receiveMessage (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:261:451)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:258:489
	at l.fire (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:46:475)
	at p.acceptChunk (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:851)
	at c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:253:203
	at Socket.t (c:\Users\billy\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\services\extensions\node\extensionHostProcess.js:263:54)
	at Socket.emit (events.js:223:5)
	at Socket.EventEmitter.emit (domain.js:475:20)
	at addChunk (_stream_readable.js:309:12)
	at readableAddChunk (_stream_readable.js:290:11)
	at Socket.Readable.push (_stream_readable.js:224:10)
	at Pipe.onStreamRead (internal/stream_base_commons.js:181:23)
$onExtensionRuntimeError @ host.ts:10
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/semver-umd.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/index.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/ExperimentationService.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/TasApiFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/FilteredFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/BaseFeatureProvider.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/AxiosHttpClient.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/ExperimentationServiceAutoPolling.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/MemoryKeyValueStorage.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/ExperimentationServiceBase.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/PollingService.js.map:
DevTools failed to load SourceMap: Could not load content for file:///C:/Users/billy/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/code/electron-browser/workbench/main.js.map:

Thank you for adding information not previously given in #107548. But now you have closed this one. Did you solve the problem yourself?

You know what, you weren't wrong, kind of... it was caused by ANOTHER extension. Whammy.


Add Kleros

Thanks! Can you put the bounty information on a page of our own with more details? See some of the other links for examples of what you might want to include, as well as the disclose.io information.

I added a mention of the bounties for deployed contracts in the auditor.md file.

Great, thanks! I don't want this site to list the various terms for everyone's bounty programs so I'm going to edit that out of your writeup.


Enhanced MQTT authentication requirements

Currently, supported MQTT scenario is:

authentication scenario of using username and password (optional, can be null / None)
connection using TLS (partial support) or without HTTP

What needs to be added:

connection without authentication
connection with certificate-based authentication (certfile, keyfile)
customization of further TLS parameters (cert_reqs, tls_version, ciphers)

Proposed action plan:

[ ] make password mandatory
[ ] allow customization of the user agent
[ ] add certificate-based authentication options
[ ] add TLS customization

Resolved, implemented all missing features described.


cmake: Use proper build configuration during compiler/linker flag tests

This PR makes all compiler/linker flag tests use the following build configuration:

CMAKE_BUILD_TYPE with single-config generator, which means the same configuration during tests and the build.
the default configuration, which is "RelWithDebInfo", with multi-config generators.

Addresses the issue raised during today's CMake-WG call.

cc @fanquake @TheCharlatan @theuni

Lol. See comment here: https://github.com/hebasto/bitcoin/pull/282#issuecomment-2258822859
I just came to the exact same conclusion :)

ACK 60d061a2b7c0468406108586e06436f40518d98e
Before PR with single config generators different flags were passed to TRY_COMPILE steps and after PR they matched. With multi config generators (I tested with Ninja) and before PR applied, no flags associated with build type were used with TRY_COMPILE steps. After PR flags associated with RelWithDebInfo.
It is worth noting that there is an (unavoidable?) subtle difference now between single config generator and multi config generators in that single config generators will align TRY_COMPILE flags with the actual compile flags. Whereas multi config generators will use different flags at compile time depending on build type selected and always flags associated with RelWithDebInfo for configuration time TRY_COMPILE checks.

Rebased due to the recent sync/rebase cycle.

reACK e51c781ae725f432cf732d2b51b18258def7cfdc

It is worth noting that there is an (unavoidable?) subtle difference now between single config generator and multi config generators in that single config generators will align TRY_COMPILE flags with the actual compile flags. Whereas multi config generators will use different flags at compile time depending on build type selected and always flags associated with RelWithDebInfo for configuration time TRY_COMPILE checks.

Agree this is annoying, but it's unfortunately just how CMake works. The lead dev says as much in the issue linked above. Ideally multi-config would do checks for each type (and even more ideally, in parallel), but this is just how it is for now I'm afraid.


Add support for Arch Linux SSO

We'd like to connect most/all of our projects to our Keycloak instance. This would require this project to support either SAML or OIDC.
We track this here: https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/26

This could be a useful library for SSO: https://github.com/onelogin/python3-saml
I am gonna work myself into the tricker, would like to implement SSO later as I also do this professionally

I'm not aware that anyone is currently working on this so it'd be great if you could get started on this.

We'd prefer going for OIDC as we want most of our service hooked up with it. The aur is going to use authlib for SSO integration so that might be something to use. (Also has some flask client parts)

Thanks for the input about authlib! I got flask-oidc-ex to work but it wasn't nice, so I think I will give authlib another try
I am trying to implement SSO in such a way that you could still turn it off and work with standard authentication (e.g. for local development)
How do you want to handle the accounts?
Should they be created locally and/or updated to have their role set on roles/groups configured in the idp?
This would still keep a local copy of the account which you could utilize for local use.

Can you elaborate for the sake of paper trail and knowledge what was not nice about flask-oidc-ex
Related to local auth method, it would be great to be able to have a config value which kind of auth method is enabled, local or SSO. For the local development flow it can just remain as it is right now, for the SSO one we want to create users on keycloak ourselves and not via the security-tracker. the access role will be provided in keycloak and the security-tracker needs something like a config key related to the auth method with a mapping of keycloak role to security-tracker role.

Hi @anthraxx - thanks for the detail!
Yes, I have that configuration option already to switch between SSO and local auth.
So to sum up the envisioned flow:

create user in keycloak
assign role in keycloak
SSO into the security-tracker, role is based on result of mapping from keycloak to security-tracker-roles

Could you confirm that? Are there any other requirements I should know about?

Ah and about the problems I had with flask-oauth-ex:

maintenance of flask-oauth has ceased and flask-oauth-ex is also quite old
documentation is scarce and didn't help me personally
It manages the sessions and everything itself which I would like to avoid

@anthraxx @jelly could you kindly confirm if I understood the envisioned flow here correctly?

@flxw yes, there is a group mapping like this:
https://gitlab.archlinux.org/archlinux/infrastructure/-/blob/master/tf-stage2/keycloak.tf#L308
Can you PoC something we can iterate over? Don't get me wrong, I understand that a good requirement definition is key to avoid unneeded work, but I believe the group layout and mapping is just a tiny part of the overall architecture that we could already iterate over.


download_remote_db fails

Running download_remote_db throws an error, which spits out the usage info for scp and then says the download didn't work.
The problem is that the scp port is added to the command as a quoted string, but it should not be quoted. Line 895 (upload_script) does it the right way: ${scp_port} whereas line 735 is incorrect: "$scp_port". I guess this might work in some environments, but it doesn't in mine (bash, Ubuntu 12.04).
The confusing thing is that because you echo the command to execute first, it looks like it should be ok, but what actually gets executed is (assuming port 8822 for ssh):
scp -q "-P 123 "user@host:~/web_dir/.bak/bakname.bz2 .

The curly brackets method ${scp_port} works fine.

Would https://github.com/jplew/SyncDB/pull/14 fix this issue?


Grad call (with no jit) is much slower than forward model call (that has some parts of it jitted) on cpu

Description
Hello,
I have a forward model that consists of many function calls and if statements for control flow running on CPU. The computationally heavy parts of the forward model are jitted but the whole model is not because of the control flow. This makes the model fast to run 0.36 sec per forward model call instead of 1.8 sec without jitting some functions in it.
Now trying to call grad()  on the forward model, takes much longer than the forward call itself.  It takes 47 seconds on the first grad call, and 6.2 seconds on subsequent grad calls. Note that I cannot use jit on grad since the forward model itself has some if statements.
Where would the slowdown be coming from? It doesnt seem to depend on the size of the input and the first call is much slower than subsequent calls. Finally, even the fastest grad call is slower than the version of the forward model with no jitted function.
Thanks a lot for the help and pointers.
What jax/jaxlib version are you using?
pip install "jax[cuda11_cudnn82]" -f https://storage.googleapis.com/jax-releases/jax_cuda_releases.html
Which accelerator(s) are you using?
CPU
Additional system info
Python V 3.10.6. WSL.
NVIDIA GPU info
No response

It is expected that an un-jitted gradient of a oomputation will be slower than the computation itself.
Why? It's because the gradient in general is an intrinsically more complicated operation. For example, if you have the function $f(x) = x^n$, which is a single operation, the gradient will be $f^\prime(x) = 2 x^{n - 1}$, which is three operations.
You can see this play out by examining the jaxpr for this function and its gradient:
import jax

def f(x):
  return x ** 2

print(jax.make_jaxpr(f)(10.0))
# { lambda ; a:f32[]. let b:f32[] = integer_pow[y=2] a in (b,) }

print(jax.make_jaxpr(jax.grad(f))(10.0))
# { lambda ; a:f32[]. let
#     _:f32[] = integer_pow[y=2] a
#     b:f32[] = integer_pow[y=1] a
#     c:f32[] = mul 2.0 b
#     d:f32[] = mul 1.0 c
#   in (d,) }

When you jit-compile the latter, XLA can often fuse these multiple operations to limit the slowdown. But the grad of a function almost always requires more operations than the function itself, so absent JIT it will almost always be a factor of a few slower.
So where does that leave you? If the cost of an un-jitted gradient is too much for your use case, I think the only way to do better is to JIT compile it, which will require modifying your code to make the original function compatible with JIT.

That makes sense in terms of why it takes longer but I have a few quick follow-up questions:

In terms of restructuring the code, is the recommendation to use lax.cond for control-flow or to avoid conditional statements all together? If so, is there a best practice published somewhere?
I tried the same model in Pytorch, and while the gradient computation is slower than the forward model there as well. It is much closer in terms of time. For example, in Torch, the forward model takes 0.8 sec and the grad call takes 1 sec. As opposed to 0.3 sec forward call in Jax and 6 sec for grad?
Finally, is there a reason why the first grad call takes much longer than subsequent ones?

Thanks a lot for the help and explanations
Best ,

In terms of restructuring the code, is the recommendation to use lax.cond for control-flow or to avoid conditional statements all together? If so, is there a best practice published somewhere?

Yes, if the problem is if statements, you can generally replace those with lax.cond, jnp.where, masking, or another mechanism depending on the nature of the code.

I tried the same model in Pytorch, and while the gradient computation is slower than the forward model there as well. It is much closer in terms of time. For example, in Torch, the forward model takes 0.8 sec and the grad call takes 1 sec. As opposed to 0.3 sec forward call in Jax and 6 sec for grad?

It's hard to guess why the timings might be different without any hint of what your code is doing

Finally, is there a reason why the first grad call takes much longer than subsequent ones?

I suspect this is due to JIT compilation overhead (for the individual functions being called by grad) on the first run.


Refactor flattenNestedObject method.

There is currently a method called flattenNestedObject  that lives in /lib/flattenNestedObject.js.
While this method is very well written, it creates several methods that could be broken out utilized elsewhere in the project! In a similar manner that the lib/flattenNestedObject.js file requires 'flattenArray', it should also:

require("hasNestedProperties")
require("getKeyValuePairs")
require("isObject")

While the naming convention of these functions makes sense to the isolated scope of the flattenNestedObject method, feel free to take liberty in renaming them where you see fit.
Since we are creating 3 new free-standing methods, there should also be 3 new test suites surrounding them.
Acceptance Criteria:

There are at least 6 new files introduced - one for each method, and a test to accompany each method.
Running yarn test <methodName> results in tests passing for flattenNestedObject, hasNestedProperties, getKeyValuePairs, and isObject.
You have written tests for hasNestedProperties, getKeyValuePairs, and isObject
Running yarn lint does not print any errors to the console!
Optional: write a new skeleton method for someone else to work on.

Hey, I'd love to take this on!

Cool @indirap !! Go for it. I'll apply the 'in progress' label. This buys you 24 hours. If you need more time, feel free to reach out and I'll happily oblige! Good luck and thanks for your contribution!!

All done now! 🙂

Boom. Freakin' awesome job! Thanks


Resolving Issue of Helm chart

Created Helm chart as per instruction using Kustohelmize

Hi @jshaktiraj , thanks for the contribution. On the first looks this PR needs quite some rework! You have included a lot of generated and temporary files in the Helm charts/ directory. Also you have changed other vital parameters that have nothing to do with Helm that will break the local deployment.

Hi Reimer,
Thanks for the prompt reply. Yes I know it will require some rework ,
actually I am still learning and want to explore opensource projects with
kubernetes , helm , CI/CD etc. I am really happy to get updates and replies
this quickly. Let me know if I could help in any way I can.
Thanks and regards
Shakti
On Wed, Nov 9, 2022, 13:08 M.-Leander Reimer @.***>
wrote:

Hi @jshaktiraj https://github.com/jshaktiraj , thanks for the
contribution. On the first looks this PR needs quite some rework! You have
included a lot of generated and temporary files in the Helm charts/
directory. Also you have changed other vital parameters that have nothing
to do with Helm that will break the local deployment.
—
Reply to this email directly, view it on GitHub
https://github.com/qaware/cloud-native-weather-nodejs/pull/28#issuecomment-1308336117,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APP7WZSCMYE3AUA42RI7OBTWHNIGBANCNFSM6AAAAAAR3DPIWA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Complete branching steps for Rancher 2.9 for EKS Operator

Tasks

[x] change the rancher-version annotation to catalog.cattle.io/rancher-version: '>= 2.9.0-0 < 2.10.0-0' while adding charts to dev-v2.9 branch. We do this so we can add patches to a  particular Rancher minor version, in this case, it would be the Rancher 2.9 line.
[x] must have a new chart inside the rancher/charts repository that has a version 104.0.0+upX.Y.Z instead of 103.x.x+upX.Y.Z.
[ ] testing

PR's

[x] https://github.com/rancher/charts/pull/3339

Validated as fixed on build: v2.9-12467fadeb539d35a249702dc0933bd84a166433-head using fresh install setup and upgraded setup from 2.8.1 > 2.9-head
EKS operator p0 scenarios are passed and version installed is	rancher-eks-operator:104.0.0+up1.4.0-rc1


project is missing a key file

The project is missing a file "tourny_data.json"
meaning that the project cannot be run. Can you add an example into the git repository so the program will run?

The file is automatically created by the program when a new tournament is started (by inputting a negative round at the beginning dialogue).
While I could theoretically add an example tourny_data.json file, I do not see the point, as it would very quickly be deleted and overwritten by just using the program.

no so - I ran it twice and it crashed

oh - why a -ve round?


How to actually connect to icloud calender?

There are sample for other thing except the first part how to actually connect to Icloud Calender and get token and so on...
Thank you

Connecting to iCloud is an application concern. I suggest you ask on StackOverflow; it has nothing to do with ical.net specifically, or RFC-5545 data in general.


Json Schema code editor shows null after adding extractor

Steps to reproduce:

Go to Schemas
Create new Scema
Type testSchemaName in name field
Type {"$id":"testID"} at code editor and press upload button -> the URI name should become testID
Press Save
Go to testSchemaName -> SchemaExtractors -> Add Extractor add extractor with accessor testExtractor and Json path .data
Press Save
Go to testSchemaName schema

Expected code editor contains  {"$id":"testID"}
Actual: code editor contains  null

Fixed in 424ca9fc90071134478cc8b91c95dbd53278963c , thanks for reporting.


Unclear User Guide

Not sure what the last bullet point means.
Also, is it better to name the points numerically instead of having bullet points so that users can point out issue(s) straightaway?

When you use this command, you will not be brought to the group page if you are currently viewing a different page


missing details

I'm looking at "In JavaScript functions, access the table output using context.bindings.<name>." and I'm not sure what it means. What does table output mean in this context?
When pushing data to the table, when is it written to the table? As soon as you call push or only when context.done is called?
How do I access any error codes?  The example code doesn't show that.  I'm assuming in the above doc reference I'm supposed to set a variable equal to the results of the call to context.bindings.mytable.push but it doesn't say.
How do I get the unique key for the row I just wrote to the table?

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

ID: 6d35c032-eae7-ac4b-2ad3-32fd0cd2318f
Version Independent ID: 92b0a972-eabe-8048-36b1-a1cefb3acf43
Content: Azure Table storage bindings for Azure Functions
Content Source: articles/azure-functions/functions-bindings-storage-table.md
Service: functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@jwargo Thanks for bringing this to our attention. Your feedback has been shared with the content owner for further review.

What is the maximum number of records that can be retrived from a table in one request? Do we get some kind of continuation token from the bindings so request the next batch?

@jwargo and @camiloramirezf these are both great questions about working with the context object in a JavaScript function. @ColbyTresness is working on some improvements to the JavaScript documentation and would be interested in this feedback.

Please assign to @craigshoemaker.

@femsulu can you also please change the service label to azure-functions/svc? Thanks!

the documentation describes using filter and take to specify what you want to retrieve in javascript but there is no further documentation on this.  please provide

#reassign:craigshoemaker

@GuyHarwood - can you provide some more detail on what you mean, please?

Function.json allows you to have filter and take attributes on input bindings for querying table storage rows.  This is not documented anywhere

@jwargo - I updated the article to include a replacement token in sample code to make the intent more clear. I hope this helps.
I am leaving this issue open in order to address @camiloramirezf and @GuyHarwood's questions. On both accounts I have contacted the Engineering team for details to use in the article.

As the original intent of this issue is addressed, I am going to #please-close this issue. I have requests out to the Product Team regarding the requests made by @camiloramirezf and @GuyHarwood's questions and will update the doc once that content is ready.


fail to use after updated to 17.9.6 (Visual Studio 2022)

down-grading to previous version could use, while updated to new version (17.9.6) failed to use (cannot open the "Quick File Open" window). Will there be any update on that? Thanks.

It's working for me in 17.9.6. If you have any more information about a specific environment that is causing problems or log files or anything, I'd be happy to take a look. As of now, I can't reproduce the issue.

Sorry for the late reply, seems that my shortcut key setting is conflict with Visual Studio updated key bindings. Since I could open the "Quick File Open" window manually in the tool bar (just found it). I close the issue now. Sorry for the false alarm. Thank you for your time.


add io stall stats interface

Signed-off-by: Little-Wallace<EMAIL_ADDRESS>Add interface to get count of each write stall reason.

/run-all-tests

@yiwu-arbug  PTAL. Is there any update about rustfmt or rustc?


Synchronize dependency order with visualizer and IaC references

For visualizer, we want unit -> role directions
For IaC, unit references role, so also unit -> role
If we represent the graph internally like this, then the IaC should create variable for resources in the graph in inverse order (role first, then unit).
Standard checks

Unit tests: Any special considerations?
Docs: Do we need to update any docs, internal or public?
Backwards compatibility: Will this break existing apps? If so, what would be the extra work required to keep them working?

For IaC, unit references role, so also unit -> role
I believe this is opposite in terms of deployment order. we dont actually care about the reference in terms of the graph today in our iac plugin but this could change

also if we are reversing the order of our resourceGraph wouldnt we want to do the same for our ConstructGraph?


Upgrade helm to 2.14.1

Description
This PR upgrade helm to 2.14.1

Thanks! I've released the new version


Autoclosing single tick '

I don't know how to reasonably fix it, but it's a bit annoying that when I want to declare a type parameter 'a, I first get to input '', then I type a, and then remove the final '.
On the other hand, I find this behavior handy when typing chars

I can't think of a good way to do this at the moment so I have disabled the auto closing for the single quote here 2f1cc84b224cfa4869826538bd4f5e498d059686.

Let's leave it open until we figure that out. Maybe OCaml or SML modes would give some inspiration?

Ok. Let's keep it open and I'll get back to it at a later time.


Choosing a background : Glassmorphism

Description
The first thing to understand about glassmorphism is that not any type of background image or gradient will match. Research a bit about backgrounds to be used in these designs .
Folder Structure : UI_UX/Glassmorphism/Background
Domain
UI/UX
Type of Contribution
Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign

I would like to work on this issue (documentation)


Kairos release v2.4.2

🗺 What's left for release
<List of items with remaining PRs and/or Issues to be considered for this release>
🔦 Highlights
< top highlights for this release notes >
Blockers

[x] https://github.com/kairos-io/kairos/issues/1984

✅ Release Checklist

[ ] Stage 0 - Finishing Touches

[ ] Check if Kairos-docs were updated and consider tagging them with the same version as Kairos ( https://github.com/kairos-io/kairos-docs/pull/103)
[x] Check if osbuilder is in the wanted version/latest
[x] Check if any kairos/packages was bumped and they were merged and repo updated (https://github.com/kairos-io/packages)
[x] Check latest repository update was merged, otherwise trigger its job (https://github.com/kairos-io/kairos/actions/workflows/bump_repos.yml)
[x] Make sure CI tests are passing.
[x] Consider cutting an rc, alpha, ... based on changes on the CI

[ ] Stage 1 - Manual testing

How: Using the assets from master, make sure that test scenarios not covered by automatic tests are passing, and that docs are still aligned

[x] Fedora flavor install, and manual upgrade works
[x] Any flavor interactive install (did kairos-alpine-3.18-standard-amd64-generic-v2.4.2-rc1-k3sv1.28.2+k3s1.iso)
[x] Any flavor recovery reset
[ ] ARM images (openSUSE, alpine) boots and manual upgrade works
[ ] ARM images passive and recovery booting
[ ] ARM images reset works
[ ] ARM images /oem exists

Check that arch is correct in the various images

[✓] quay.io/kairos/ubuntu:20.04-core-arm64-rpi4-v2.4.2-rc1 -> It's arm64
[✓] quay.io/kairos/opensuse:leap-15.5-standard-amd64-generic-v2.4.2-rc1-k3sv1.26.9-k3s1 -> it's amd64
[✓] quay.io/kairos/opensuse:leap-15.5-core-arm64-generic-v2.4.2-rc1 -> arm64

[x] Stage 3 - Release

[x] Tag the release on master. - https://github.com/kairos-io/kairos/releases/tag/v2.4.2-rc1

[ ] Stage 4 - Update provider-kairos

[ ] Update go mod to consume kairos-io/kairos.
[ ] Check if any changes on the pipelines and building pieces are required

[ ] Flavor changes
[ ] osbuilder version bumps

[ ] Update the CORE_VERSION file of kairos-io/provider to match the release tag of kairos-io/kairos
[ ] Tag the release on provider-kairos

[ ] Stage 5 - Announcement

[ ] Blog post announcement

QA checks:
checking that arch is correct in the various images

[✓] quay.io/kairos/ubuntu:20.04-core-arm64-rpi4-v2.4.2-rc1 -> It's arm
[ ]

Known issues:

#1994
#1995
Some keyboards may not before the OS is loaded (e.g. during grub menu). @jimmykarily mechanical ducky keyboard for example. The raspberry pi keyboard works so it's not w general issue.

We don't consider these blockers because they only happen with Alpine (first 2) or with only some hardware (the third one).
Only known issue we are trying to fix is the cgroups error that prevents k3s from starting on rpi:
time="2023-11-08T17:10:53Z" level=fatal msg="failed to find memory cgroup, you may need to add \"cgroup_memory=1 cgroup_enable=memory\" to your linux cmdline (/boot/cmdline.txt on a Raspberry Pi)"

If that only happens on Alpine too, we will document it in the release notes like the others and continue. Otherwise we will just apply the fix but adding the needed arguments to the cmdline when on rpi.

This has been merged to kairos master now: https://github.com/kairos-io/kairos-agent/pull/171/files . I will install opensuse on rpi, will do a reset and check if I still get serial access after rebooting.


update workflows to py3.10

Following workflows are using 2.7 and probably just require superficial porting of scripts to move to py3:

pypi
sphinx
copyright

Other workflows do use py3 but are currently on 3.7, probably time to move to 3.10.

Fixed in #1611


Update copy:files to glob “src” not “src/govuk”

This PR widens gulp copy:files to glob ./src/**/* not just the "govuk" directory
Why? Since https://github.com/alphagov/govuk-frontend/pull/2851 was merged we're now running build tasks on files within:
./src/govuk
./src/govuk-prototype-kit

As suggested by @36degrees in https://github.com/alphagov/govuk-frontend/pull/2851#pullrequestreview-1167005193 we could remove some unnecessary file operations:

(I think it'd be neater if the .js and .scss files were handled by the existing copy-files task, but that looks like it's caught up in the fact that config.src is actually src/govuk so happy to revisit that later)

These changes were made possible by:

https://github.com/alphagov/govuk-frontend/pull/2962

@36degrees Does this PR address your code review suggestion?


Workers not acknowledging after upgrate to v0.4

{
    "job": null,
    "context": {
        "id": "JID-01H1F31FYEDKGH94XQEDX4ZSYA",
        "status": "Pending",
        "run_at": "2023-05-27T17:10:33.166137782Z",
        "attempts": 0,
        "max_attempts": 25,
        "last_error": null,
        "lock_at": null,
        "lock_by": null,
        "done_at": null
    }
}

{"v":0,"name":"majinn","msg":"Sending email: EmailApalis","level":30,"hostname":"samuel","pid":87291,"time":"2023-05-27T17:10:32.792390087Z","line":23}
I'm getting this from redis and the trace respectively. Any hints on what could be?

Could you share a simple working sample? Just with the needed parts.

Hey, is the exact same example as in the README. No difference at all. What might be interesting is that I'm racing it agains an actix-web server using tokio::select!, but I did the same for version 0.3 and worked.

What is the complete error?

Acknowledgement could not be called due to missing ack data in context .............................?
This seems like the ack service is missing something in context

It can be reproduced by running the redis example. Might be tied to the redis storage since it doesn't happen with the postgres storage.
Complete log:
2023-05-31T12:46:11.255706Z DEBUG apalis_redis::storage: Received new job with id: JID-01H1RXG9SQJRFPG2RZ39M6H3Z7 to list: apalis::Email:active
2023-05-31T12:46:11.308607Z DEBUG job{job_id="JID-01H1RXG9SQJRFPG2RZ39M6H3Z7" current_attempt=0}: apalis_core::layers::tracing::on_request: job.start
2023-05-31T12:46:11.308758Z  INFO job{job_id="JID-01H1RXG9SQJRFPG2RZ39M6H3Z7" current_attempt=0}: email_service: Attempting to send email to<EMAIL_ADDRESS>2023-05-31T12:46:11.308810Z  WARN job{job_id="JID-01H1RXG9SQJRFPG2RZ39M6H3Z7" current_attempt=0}: apalis_core::layers::ack: Acknowledgement could not be called due to missing ack data in context : apalis_core::job::JobId
2023-05-31T12:46:11.308857Z DEBUG job{job_id="JID-01H1RXG9SQJRFPG2RZ39M6H3Z7" current_attempt=0}: apalis_core::layers::tracing::on_response: job.done done_in=0ms result=()

Sorry I didn't have time to reproduce it as I moved forward with previous version, but tit was exactly the same error, thanks @bastienriviereocd

I will release a fix for this tonight--
Geoffrey Mureithi
+254713622599
mureithi.me
Skype: live:mureithinjuguna


[Bug] No flash or lines collected if settings menu is open

Lines should probably continue to collect even if the menu is open. It might also be good to automatically close the window in such a case (and flash if it's enabled ) to get the user's attention.
EDIT: The same is true for editing text too - we'd probably want to update that as well.

iirc that was actually kind of wanted - currently there is no differentiation between the sources from which a text comes from.. but without that you would either get lines inserted to the page or flashing when e. g. pasting sth to the settings menu/while editing - and i saw those as times where typically anways no new text would appear so i choose the quicker way : >
if you think that it is more common that there is a continous stream of text even in such scenarios i may can check for such a change i described and consider to block new lines only for paste cases when settings are open / line is in editing while flashing for other sources

Yeah, that's a good point. I know I've left the menu open at this point already and been surprised to look over and see it open and missing lines.
I think it's probably worth making sure the user isn't losing lines though. I'm guessing pasting stuff into the settings is actually less common, since you're only do it with custom css & maybe a port for sockets here and there.


[Suggestion] Provide an option to specify Docker container name and run docker exec to execute pihole -g

I just set up a secondary pihole for my home network using Docker and I was looking to use this tool to sync the two together.  To make this work with my docker container, I'm planning on running it on my docker host (Ubuntu 20.04) and changing the pihole_dir to match the volume for the pihole dir of the Docker container.  This should work fine but the pihole -g command won't be able to run on the host, it has to be directed to the container instead - docker exec <container_name> pihole -g
Note: I considered running docker-compose restart or other docker equivalent command but I don't feel it is necessary, as pihole runs the gravity update on a cron anyway, so restarting the whole container feels like overkill in this use case.
I'm planning on simply replacing the two pihole -g commands in the bash script to said docker command instead, and it should work.  Perhaps an option can be included similar to the shared hosts option where you if you specify a container name, it will run the docker exec command instead of simply pihole -g
The only other way I could think of to get this to work for a docker container would be to build your own docker image from the pihole image, but have the dockerbuild bring in Git and this tool.  However, that's a bit more complicated - especially for the average user - so I figured adding an option as explained above would be a simple yet effective alternative.

Making those changes appears to have worked, however I missed the service pihole-FTL start and stop lines.  I changed them  in the initpull and pull functions as follows
-                       $SUDO service pihole-FTL stop
+                       $SUDO docker exec pihole service pihole-FTL stop
                        $SUDO cp $gravity_db $custom_list $pihole_dir
-                       $SUDO service pihole-FTL start
+                       $SUDO docker exec pihole service pihole-FTL start

There is only one error I encountered when doing this:
/usr/local/bin/pihole-cloudsync$ /usr/local/bin/pihole-cloudsync/pihole-cloudsync --initpull
Shared Hosts Mode DISABLED.
--initpull option detected. Initializing local Git repo for Pull/Download.
[sudo] password for justin:
s6-svc: warning: /var/run/s6/services/pihole-FTL/notification-fd not present - ignoring request for readiness notification
  [i] Neutrino emissions detected...
  [✓] Pulling blocklist source list into range

  [✓] Preparing new gravity database
  ....etc.

I don't run docker, but will you please confirm that this same fix works with v5 of the script? If so, I can include it as an option. :)

Closing this unless/until we establish it works with v5. Please do a fresh commit if necessary.


test cgroups v2 without selinux

What this PR does / why we need it:
This PR is a clone of this PR https://github.com/kubevirt/kubevirt/pull/6042 but disables SELinux on the nodes in order to being able to test cgroups v2 lane. This is since container-selinux' policy had a bug in it which is fixed but we are not yet affected by the fix.

/test pull-kubevirt-e2e-k8s-1.20-cgroupsv2-rook-ceph

/test pull-kubevirt-e2e-k8s-1.20-cgroupsv2-rook-ceph

/test pull-kubevirt-e2e-k8s-1.20-cgroupsv2-rook-ceph

/close


added docker-compose.yml file and fix commands

added docker-compose.yml file and fix commands

i believe it ready for review now


[Feature request] Option to not auto-run the process on startup

As per in the title, it would be nice if the processes did not run automatically on mprocs's startup, but had to be run manually.

Sure thing. I will add it in the next version.

mprocs 0.5.0 adds an autostart option:
procs:
  bash:
    shell: bash
    autostart: false


Add a CSV logger

**Describe the Issue (Bug/Feature) **
I'll add a CSV logger to the project so that the results from SBK API can be easily parsed for post-processing.
Additional context
Passing this SbkCSVLogger to SBK run would create a CSV file and dump the metrics there. That file can then be used for easy post-processing, instead of using the stdout dump.

thanks Aditiya.. please submit the PR with your code changes and test logs too.


Enh/#12 billing without postal

Pull Request
Description

as mentioned in #12, if the postal info is missing we can just put dummy values in the invoice
Closes

closes #12

woops hehe, fixed


Question on session limit relating to GPU memory

I am running RDP wrapper on a sizeable machine (48 cores, ~750GB RAM, Window 10 Enterprise 21H2 19044.2846). Despite the sizeable CPU and RAM available, I've ran into the issue where RDP would no longer connect a session when more than 5-6 sessions were already connected (giving only a black screen or the image below). When that happens, currently disconnected users are also often locked out, until someone logs in locally. RDP Config shows in all cases that the build is supported and the client is listening.

Based on issue #192 I think the problem could be related to resources running out, particularly the memory of our undersized GPU (which only has 2GB of dedicated memory). It is mentioned there that RDP consumes GPU memory and it running out might be the reason for a session limit.
I have checked that there is no limit of connections in gpedit.msc. I've also since deactivated GPU acceleration in gpedit, which seems to have solved the problem for now. To get ahead of future issues, however, I was wondering whether RDP would only care about the dedicated GPU memory available, or whether it will work fine if only virtual GPU memory is available. Due to the amount of RAM available on the machine, we have plenty of virtual GPU memory so this would hardly ever become an issue. If RDP requires availability of dedicated GPU memory, I will know to upgrade the GPU.
Thanks in advance for your insight!

I am running RDP wrapper on a sizeable machine (48 cores, ~750GB RAM, Window 10 Enterprise 21H2 19044.2846). Despite the sizeable CPU and RAM available, I've ran into the issue where RDP would no longer connect a session when more than 5-6 sessions

Try uninstall RDP Wrapper and switch your SKU to ServerRdsh (Enterprise for Virtual desktops). You can find GVLK key in Google.
This Edition is RDS role without RDS CAL licenses.
If this problem is not seen on ServerRdsh, but it is on Enterprise with RDP Wrapper, then it is most likely an RDP Wrapper problem.

I have checked that there is no limit of connections in gpedit.msc. I've also since deactivated GPU acceleration in gpedit, which seems to have solved the problem for now.

--> Not an RDP Wrapper issue. --> closed...


Multi-select of consecutively listed facet objects

I sometimes find I need to select ('include') more than a handful of consecutive objects from a text facet and since clicking each one in the facet takes a while, I find the only way to do this to to make another boolean-output facet that discriminates the set I need. This works fine, but it occurred to me that it would be nice to be able to multi-select the facet objects with a shift-click as is common for other listings (like file browsers).
For example, suppose I have a text column 'Name' with a text facet and there are many unique names. The facet, by default, lists the names alphabetically, though you can switch to order by count. If I want to select/include all of the names starting with A plus the first few starting with B then, rather than clicking my way through each name (or coming up with another boolean facet), the proposed feature would allow me to just select the first A name, then scroll down to the last B name I want included and shift-click on it. This then selects all of the options between the first and last items I clicked (inclusively). If the facet were ordered by count, this feature would allow me to easily select, say, the 20 most common names.

So there would be a range.  And the start of the range is indicated how?
If I have a set of 5 and I have some checked as below, is there no user interaction needed to indicate the start of the range?
[X] 1
[ ] 2
[X] 3
[ ] 4
[ ] 5
Given the above state of a Facet, what happens if I just SHIFT+LMB click on 5?
Would only 4 also be checked automatically to include in the range?
I do understand you want a user interaction with the SHIFT+LMB click to choose the end of the range.

The start of the range is given by an already-selected object, so yes it needs further clarification when there are more than one. I've just looked to see what Mac's file browser does and it's actually a bit complicated since it depends on the most recently selected object. This would probably be a step too far for OR, but I think the following simple logic would suffice for a shift+LMB click on a facet object:
case, there are no selected objects : select the clicked object as as though it were a normal click
case, the clicked object is already selected : do nothing
case, there is one selected object : select all object listed between and including that object and the clicked object
case, there are multiple selected objects AND all selected objects are before the clicked object : select all objects after the highest selected one, up to and including the clicked object
case, there are multiple selected objects AND all selected objects are after the clicked object : select all objects before the lowest selected one, down to and including the clicked object
case, there are multiple selected objects AND the clicked object falls between selected objects : just select the clicked object as though it were a normal click

It seems to me that anything which doesn't match the behavior of the host UI is going to be confusing to the user. We should just use the standard system UI conventions (and implementation, if possible).

Agreed. I just don't know if the code currently supports remembering which is the most recently selected object, so I proposed what I think would still be logical behaviour without requiring this (and still satisfying the requirements for the original case descriptions) .


Returned data to include accuracy

This package returns latitude and longitude. Can you include accuracy in the data returned? For example, if the accuracy is +/- 1000 meters then accuracy should be 1000. This should help to filter out the "spikes".

Hi @afung2468
Thank you for opening an issue.
I believe we have accuracy in the data model;

Thanks for the quick reply. The accuracy data helps a lot in determining if the location reading is useful. Thanks.


deployment fails on wait for time server sync

ceph-salt deployment fails when waiting for time server sync
Failure in minion: master.ses7.com
__id__: run sync script
__run_num__: 43
__sls__: ceph-salt.time-sync
changes:
  pid: 14090
  retcode: 1
  stderr: ''
  stdout: 503 No such source
comment: 'Command "/tmp/chrony_sync_clock.sh

If I tried ceph-salt -ldebug apply --non-interactive again, the time syncing will succeed. It only happens on first attemp.
Other information:
version: ceph-salt 15.2.4+1589550818.gaf48859

    master:   o- time_server ......................................................................................................... [enabled]
    master:     o- external_servers ........................................................................................................ [1]
    master:     | o- pool.ntp.org ........................................................................................................ [...]
    master:     o- server_hostname ........................................................................................... [master.ses7.com]
    master:     o- subnet ...................................................................................................... [<IP_ADDRESS>/24]

Log file:
time_sync_error.log

I tried using a NTP server in my country and it succeeded at first pass.

Yes, I think it makes sense for ceph-salt to try to sync the clock more than once before giving up.


Fix NSInvalidArgumentException in + [ARSpotlight webpageURLForEntity:], line 75

Version: 2.3.0 (2015.10.15) | net.artsy.artsy
Stacktrace
ARSpotlight;webpageURLForEntity:;ARSpotlight.m;75
ARSpotlight;searchAttributesForEntity:includeIdentifier:completion:;ARSpotlight.m;271
ARSpotlight;addEntityToSpotlightIndex:;ARSpotlight.m;193
Reason
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL URLByAppendingPathComponent:]: component, components, or pathExtension cannot be nil.'
Link to HockeyApp

https://rink.hockeyapp.net/manage/apps/37029/crash_reasons/48973143

all of these crashes + #925  #946 happen when a user has just signed up according to the analytics patterns

It appears that this issue still exists in 2.3.2.


[ROCm] xla_gpu_enable_cublaslst and matrix_ops_simple_test is cuda only

This new merged PR (https://github.com/tensorflow/tensorflow/pull/56761) only for cuda gpu so far. We hope it be more generical.
@cheshire

@cheshire gentle ping

@akuegel Thanks a lot for the feedback. This is really helpful.
All changes are made, please take another look.


Fixing usage of btn-inverse (has been deprecated in bootstrap3)

Hi @wofl. Test are failing here. Can you update and address that?

I'm going to close this since it's stale. Happy to review an updated version.


Fetch failed - Error 500

Describe the bug
When loading the /og_image/og.png url on my production server i got an 500 error
(Things works fine on my computer)

[nuxt] [request error] [unhandled] [500] fetch failed (https://mydomain.com/api/og-image-options?path=/item/item-slug)   at $fetchRaw2 (./.output/server/node_modules/ofetch/dist/shared/ofetch.502a4799.mjs:180:24)   at ./node_modules/nuxt-og-image/dist/runtime/nitro/middleware/og.png.mjs:16:19   at Object.handler (./.output/server/node_modules/h3/dist/index.mjs:1247:19)   at Server.toNodeHandle (./.output/server/node_modules/h3/dist/index.mjs:1322:7) [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [nuxt] [request error] [unhandled] [500] fetch failed (https://mydomain.com/api/og-image-options?path=/item/item-slug)   at $fetchRaw2 (./.output/server/node_modules/ofetch/dist/shared/ofetch.502a4799.mjs:180:24)   at ./node_modules/nuxt-og-image/dist/runtime/nitro/middleware/og.png.mjs:16:19   at Object.handler (./.output/server/node_modules/h3/dist/index.mjs:1247:19)   at Server.toNodeHandle (./.output/server/node_modules/h3/dist/index.mjs:1322:7) [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png" [Vue Router warn]: No match found for location with path "/item/item-slug/__og_image__/og.png"
Thanks for your help!
Reproduction
/
System / Nuxt Info
System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (6) x64 AMD EPYC 7542 32-Core Processor
    Memory: 8.55 GB / 15.63 GB
    Container: Yes
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 19.8.1 - ~/.nvm/versions/node/v19.8.1/bin/node
    npm: 9.6.2 - ~/.nvm/versions/node/v19.8.1/bin/npm

Hi @luminous8, could you share what version you're using and anything else that would be useful for reproducing the error.

Yes, sorry (I knew i was forgetting something)
I was using 1.5.7
and I've now migrated to the ^2.0.0-beta.30 (hopping it would fix the bug)
My code is fairly simple, I'm using
defineOgImageStatic({   component: 'MyOgImage',   item: item, });
and my component looks like this
`

`

You can try to access the URL it's trying to fetch directly and see what 500 error is thrown
http://localhost:3000/api/og-image-options?path=/item/item-slug

I'm getting an ERR_CONNECTION_TIMED_OUT in my browser (i've done the same in local and it works perfectly)

Which nitro preset are you using and are you using nuxt build or nuxt generate?

I'm using Nuxt build
On Wed, May 3, 2023 at 12:16 PM Harlan Wilton @.***>
wrote:

Which nitro preset are you using and are you using nuxt build or nuxt
generate?
—
Reply to this email directly, view it on GitHub
https://github.com/harlan-zw/nuxt-og-image/issues/47#issuecomment-1532775379,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEIMBXLTCQFYE2SMODWTBLLXEIV6FANCNFSM6AAAAAAXUE2IOE
.
You are receiving this because you were mentioned.Message ID:
@.***>

I'm having the exact same issue. Also using nuxt build.

update on my side: it's really weird, it started working after a couple of hours - i haven't changed anything

Hmm very strange! Feel free to re-open if it pops back up :)


JuliaCon 2024: LinkedIn Page Event

Can we have an updated version for the JuliaCon 2024 LinkedIn page (currently it says 2023 and MIT)

Yes, I'm going to work on it this weekend...

Can we merge this with issue #18

Not sure how to merge, so closing as duplicate...