Dots in ped are problematic

When using samples with dots in it, the pipeline crashes at the creation of a gemini database
[2019-07-30T10:17Z] GEMINI: create database with vcf2db
[2019-07-30T10:17Z] name_disp None
[2019-07-30T10:17Z] Traceback (most recent call last):
[2019-07-30T10:17Z]   File "/local/bin/vcf2db.py", line 924, in <module>
[2019-07-30T10:17Z]     impacts_extras=a.impacts_field, aok=a.a_ok)
[2019-07-30T10:17Z]   File /local/bin/vcf2db.py", line 228, in __init__
[2019-07-30T10:17Z]     self.samples = self.create_samples()
[2019-07-30T10:17Z]   File "/local/bin/vcf2db.py", line 598, in create_samples
[2019-07-30T10:17Z]     vals = [r[i] for r in rows]
[2019-07-30T10:17Z] IndexError: list index out of range
[2019-07-30T10:17Z] Uncaught exception occurred
Traceback (most recent call last):
  File "/software/local/share/bcbio/anaconda/lib/python3.6/site-packages/bcbio/provenance/do.py", line 26, in run
    _do_run(cmd, checks, log_stdout, env=env)
  File "/software/local/share/bcbio/anaconda/lib/python3.6/site-packages/bcbio/provenance/do.py", line 106, in _do_run
    raise subprocess.CalledProcessError(exitcode, error_msg)
subprocess.CalledProcessError: Command '/local/bin/vcf2db.py /analysis/CW136MW/work/gemini/CW136-freebayes-nomultiallelic-annotated-dbnsfp.vcf.gz /analysis/CW136MW/work/gemini/CW136-freebayes-nomultiallelic.ped /analysis/CW136MW/work/bcbiotx/tmp0k2nspxr/CW136-freebayes.db
name_disp None
Traceback (most recent call last):
  File "/local/bin/vcf2db.py", line 924, in <module>
    impacts_extras=a.impacts_field, aok=a.a_ok)
  File "/local/bin/vcf2db.py", line 228, in __init__
    self.samples = self.create_samples()
  File "/local/bin/vcf2db.py", line 598, in create_samples
    vals = [r[i] for r in rows]
IndexError: list index out of range
' returned non-zero exit status 1.

My input ped looks like this
#family_id	name	paternal_id	maternal_id	sex	phenotype	name_ID	name_disp
CW136	import_CW136P.gatk	import_CW136F.gatk	CW136M	2	2	42	CW136P
CW136	CW136M	0	0	2	1	43	CW136M
CW136	import_CW136F.gatk	0	0	1	1	44	CW136F

while the ped file generated for gemini import looks like this
#Family_ID	Individual_ID	Paternal_ID	Maternal_ID	Sex	Phenotype	Ethnicity	name_disp
CW136	import_CW136F_gatk	-9	-9	1	1	-9
CW136	CW136M	0	0	2	1	43	CW136M
CW136	import_CW136P_gatk	-9	-9	2	2	-9

Hi @mmoisse,
Thanks-- what do the sample names in your VCF look like? The PED file names are different because we do some cleaning up of sample names before running bcbio. Do the sample names in the PED file for GEMINI import match the sample names in the header?

In the vcf header all dots have been replaced by _ so these are the sample names
CW136M, import_CW136F_gatk and import_CW136P_gatk

Thank you, is there any way you could pass on the VCF and the PED file so we can look at it to try to figure out what the problem is?

Please find attached the input ped file and a subset of the vcf file.
Tx
CW136MW.ped.zip
CW136-freebayes-nomultiallelic-annotated-dbnsfp.subset.vcf.zip

Hi @mmoisse,
If you switch the . to _ in the PED file like bcbio did and use that to load the database, this seems to work fine. Does it not work if you do that?

Hi @roryk,
Indeed switching . to _ does work, but it seems a bit weird because in your yaml and csv file you can use . in the name but in the ped you can not, and then I would need to use other names in the ped then in the yaml and csv files.
Would it be possible to give a warning or also clean the sample names in de ped file?
Kind regards,
Matthieu

Hi Matthieu,
Hm-- we do clean up the names, which is why in the PED file generated for the GEMINI import has dashes in it.
/local/bin/vcf2db.py /analysis/CW136MW/work/gemini/CW136-freebayes-nomultiallelic-annotated-dbnsfp.vcf.gz /analysis/CW136MW/work/gemini/CW136-freebayes-nomultiallelic.ped foo.db
That's the command that is failing, but it works with the files you gave me. I'm guessing that the . vs _ isn't the problem, since in that command they've been converted to dashes in the PED and the VCF file. Can you confirm that the above command gives you the error? If so, can you send along the entire VCF file or at least a subset that fails with the same error?

I believe the issue occurs here:
First it reads the original ped file, with the . in the file name and sets that as key
https://github.com/bcbio/bcbio-nextgen/blob/90c156d5e5b6c5e99a4d8280965c2e7580fac41d/bcbio/variation/population.py#L253-L259
Then you get the cleaned sample names from the vcf file
https://github.com/bcbio/bcbio-nextgen/blob/90c156d5e5b6c5e99a4d8280965c2e7580fac41d/bcbio/variation/population.py#L263
To then query the original ped file with cleaned sample names, which fails in case of . in the sample name.
https://github.com/bcbio/bcbio-nextgen/blob/90c156d5e5b6c5e99a4d8280965c2e7580fac41d/bcbio/variation/population.py#L269-L272

Thanks-- does the pipeline fail somewhere else then? It looks like in the original issues the failure is calling out to vcf2db.py, is that not where the failure is actually happening?

Ok, I figured out where the original problem is coming from. The PED file has extra columns in it, I see there are columns for name_ID and name_DISP which I think is what is causing the problem. If I keep those columns in, I get the original problem but if drop those columns from the PED file it works fine.

Thank you.
I will test it and come back to you, probably not before Monday.

Thanks-- does the pipeline fail somewhere else then? It looks like in the original issues the failure is calling out to vcf2db.py, is that not where the failure is actually happening?

Yes the issue occurs in vcf2db.py. But I believe, this is due to an issue in the conversion of the input ped-file to the gemini ped-file. In the input file import_CW136P.gatk has a father and a mother while in the gemini ped-file the both parents are set to -9 (unknown). Additionally, if a sample is not found in the input ped-file 7 column are write to the gemini ped-file, while if the sample is found the same number of columns as in the input ped-file are written to the gemini ped-file. Probably this mismatch in the number of columns per row is the cause of the crash of vcf2db.py ?
Thank you for your time.

Thanks, I checked and this definitely is due to the extra columns in the input PED file-- if you limit them to just the normal columns this should work fine. Thanks!


elim max duration constraint on movieFileOutput

Remove maxRecordedDuration constraint on AVCaptureMovieFileOutput. Instead, pause recording when recordedDuration hits 10s. This should prevent the creation of any empty time ranges in the AVVideoComposition that will cause failure on export.

Does this turn out being precise enough? Noticed that we're still tracking elapsed capture time over a signal.

Is this extremely precise? No. But since the movieFileOutput's recordedDuration isn't KVO, I'm not sure how to enforce a strict 10s limit. Seems like you'll have to do some kind of periodic observing on recordedDuration, which by its nature won't yield an exact 10 second limit. I don't think this would yield anything close to an 11s video, so I guess the question is how much leeway do we have on out 10s video limit. We could always clip the range of any excess time before saving, as well.

:+1: flippin' nice

NOICE


Eliminate avrotools generator patterns

Also do a lot of refactoring
Issue #404

This looks very nice, thanks @dcolligan. I like the general approach, and the reuseable Avro type switch mechanism is ingenious. There are two general points that come through for me:

We need more docstrings. In general, every public method of a class should have a docstring. This would be very tedious in this case to have docstrings for all the handleX methods, but we can still explain how this all works a lot better.
The code here is a bit verbose in places for my taste --- I've highlighted some places where we can cut out a lot of lines of code using list and dictionary comprehensions, increasing readability (IMO).

@jeromekelleher pushed an update

Looks great, thanks @dcolligan. I'm +1 modulo the Bogus vs Invalid discussion above.

@jeromekelleher alright, pushed an update that split SchemaTool into two classes, Validator and Creator -- there's nothing named 'bogus' now

Thanks @dcolligan, +1.


ODHack: Make it easier to sum 2 Portfolio instances

Adjust the Portfolio class so that two of its instances can be summed together, resulting in a portfolio containing tokens from both summed portfolios. The Portfolio class is implemented here: https://github.com/CarmineOptions/derisk-research/blob/master/src/helpers.py#L78.

Hi can I hop on this?

Hi! @lukaspetrasek I would like to take this task. I estimate no more than 2 days for the changes to be ready.
This would be my first issue on this project, but I have experience working with python. The proposed approach would be to implement a custom add method in the class, which will create a new instance of Portfolio with he combined tokens.

Hi! @lukaspetrasek I would like to take this task. I estimate no more than 2 days for the changes to be ready.
This would be my first issue on this project, but I have experience working with python. The proposed approach would be to implement a custom add method in the class, which will create a new instance of Portfolio with he combined tokens.

Hi, assigning @lindsaymoralesb  , because they provided a better description of the approach and lower ETA.
@lindsaymoralesb  Let me know if everything is clear and whether you'll be working on the issue. If you have any questions, please ask here. What is you TG handler please? 🙏🏼
Consider joining our TG group.
See also our contributor guidelines.

Thanks! Yes, I’ll be working on this.
Already joined the group, my tg is @lindsaymorales. Will let you know if I have any doubts.

hey @lukaspetrasek ! so the changes are already in this PR.
I just had a question on how I could test this new feature of adding two portfolios, I tested the code outside to make sure it will work, but I was wondering if there was a way of testing it on the project just to double check!

Hi, added 1 comment 😉

Hi @lindsaymoralesb , few more simple comments.

Hey! @lukaspetrasek did you leave them on the PR? I can’t find them

Hey! @lukaspetrasek did you leave them on the PR? I can’t find them

Oh shoot, forgot to submit them. Now it's done.

No worries! Changes are ready for review.


Steps to reproduce the bug

Steps to reproduce the behavior:

Open any combo box

Expected behavior

There would be a shadow
Version Info

Windows 10 version
Saw the problem?

May 2019 Update (18362)
Yes

October 2018 Update (17763)
No

Device form factor
Saw the problem?

Desktop
Yes

I would have thought Shadows would come under the "enable visual effects" setting, not the transparency one

I would have thought Shadows would come under the "enable visual effects" setting, not the transparency one

Me too, it's possible the code is just checking for the wrong setting. There is a "Show shadows under windows" setting that I would think should be respected here instead:

I wish all of those settings were in the UWP Settings app. It's kinda sad how Windows is holding this back.

The text in the Control Panel settings dialog, should probably be re-worded to something like
Show shadows on windows and on screen controls

I think it should be separate. That wouldn't match anything else in that dialogue.

The fact it is using the same setting as what turns off Acrylic is on purpose, but I seem to remember this setting said something else. Investigating...

I think it should be separate. That wouldn't match anything else in that dialogue.

So you want two options, something like this?
Show shadows under windows
Show shadows within apps

@mdtauk and @Poopooracoocoo , This is not something we can control (not my team to decide) so please open Feedback Hub item and let me know the ID of the item you opened so I can track the item's progress on my end.

@mdtauk There are things like

show shadows under windows
show shadows under mouse pointer

so something like

show shadows under menus

would be appropriate
@chigy
What category?

@Poopooracoocoo I do think there should be a greater distinction between the transparency and shadow effects. Since Fluent Design has become more diverse in what it contains over time, there should be separate toggles for each of them. (Ideally, in the Settings app)

A setting for Shadows, and a setting for Transparency.

@Poopooracoocoo , It should be opened against 'Desktop environment' + 'Settings'

https://aka.ms/AA5burp

@Poopooracoocoo , Thanks. I've added details on our end for whoever is responsible for this setting to have the context. May I close this item since there is nothing WinUI can do at this point?
FYI @mdtauk

I hope something gets done.

@Poopooracoocoo , since I am not from the team who makes the call, I am not able to promise anything but, at least, it is on the hands of people who does to take a look.

And from experience, they won't take a look. :(
Have a nice day

Sorry for mentioning you again @chigy I hope the bot doesn't move this lol
Do you know if this has progressed? Are any of the peeps who work on these kind of things on GitHub or Twitter?
This kind of setting would bring consistency. win32 tooltips and menus keep their shadows but WinUI ones don't.

@Poopooracoocoo , I see on the database, it has the following comment. Good news is that they didn't dismiss it, and it will be considered in the future feature discussion. I cannot tell how much in future, however...
"Thanks for the feedback!
This is not a product issue, but rather a feature request/spec defect.  We will consider this feedback among all others of its kind periodically as we work to deliver outstanding experiences to our customers and partners."

btw I found more issues!

UWP apps don't listen to:

fade or slide menus into view
fade or slide tooltips into view
fade out menu items after clicking
slide open combo boxes

Unticking animate controls and elements inside windows also disables smooth scrolling in Edge Spartan
and now that I see your comment again, I wish I could see that FBH comment myself.

@Poopooracoocoo , your last comments are slightly different from the original request. The difference here is that you area asking UWP to link to existing settings vs. the previous one was to change the existing setting to conform to a new UWP behavior somehow. Latter is hard because our team don't own the settings themselves.
I won't promise anything here but if you created a request that reads something like "UWP should respect existing settings," and if this is something the team feels worth investment now, I'll see what I can do. Again, this will only be UWP respecting existing setting as is, rather than asking to add new settings. Latter will still need to go to Feedback Hub.

I'm not asking for the existing setting to conform to new UWP behaviour. In both the issue and the comment I'm asking for the same thing: for UWP to link to existing settings. :)
Sorry, I may have misunderstood your reply. :/ I read my own comment again and the original issue but I don't understand what you meant.

@Poopooracoocoo , because you are asking our new features to conform to more than a decade old settings, certain features are easier to do than others. Shadow one will require revisiting the way setting is setup in order to properly support the new features. Whereas your latest asks seems doable within the current setting framework/definition on my first look (though it may not be once we take a look).

It's still weird that shadows and acrylic are tied together.


PyLance misreporting GeneralTypeIssues on dictionary comprehension

Environment data

Language Server version: v2022.12.20
OS and version: Windows 11 Pro 22H2
Python version (& distribution if applicable, e.g. Anaconda): 3.10
Visual Studio Code version: 1.74.0

Code Snippet
dict_keys = [1,2,3]
mydict = {
    k: None for k in dict_keys
}
key = 3
value = 5
mydict[key] = value

Repro Steps
Enter the example code into a Python file in VSCode with Pylance.
Expected behavior
There should be no type errors or red squiggly lines underneath any of this code.
Actual behavior
mydict[key] has a red squiggly line under it, and Pylance indicates reportGeneralTypeIssues
I could be wrong since I'm still improving my knowledge regarding Python type hinting. What I think is happening it that the k: None in the dictionary comprehension is being misinterpreted by Pylance. Because there is a : it thinks that the k has a type hint of type None. Therefore trying to put an int there is causing it to report  a type issue. This : is not a type hint, it's part of a dictionary comprehension.
What the code is supposed to do is pre-load the keys in the dictionary, but set the initial values to None. Then later on the code may replace some or all of the values in the dictionary with integers.
Logs
[Info  - 9:31:07 AM] (282216) Pylance language server 2022.12.20 (pyright 621d886b) starting
[Info  - 9:31:07 AM] (282216) Server root directory: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist
[Info  - 9:31:07 AM] (282216) Starting service instance "temp"
[Info  - 9:31:07 AM] (282216) Notebook support: LSP
[Info  - 9:31:07 AM] (282216) Interactive window support: LSP
[Info  - 9:31:07 AM] (282216) No configuration file found.
[Info  - 9:31:07 AM] (282216) No pyproject.toml file found.
[Warn  - 9:31:07 AM] (282216) stubPath d:\Desktop\temp\typings is not a valid directory.
[Info  - 9:31:07 AM] (282216) Assuming Python platform Windows
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
[Info  - 9:31:08 AM] (282216) Search paths for d:\Desktop\temp
[Info  - 9:31:08 AM] (282216)   c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib
[Info  - 9:31:08 AM] (282216)   d:\Desktop\temp
[Info  - 9:31:08 AM] (282216)   d:\Desktop\temp\typings
[Info  - 9:31:08 AM] (282216)   c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stubs\...
[Info  - 9:31:08 AM] (282216)   c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\bundled\stubs
[Info  - 9:31:08 AM] (282216) Adding fs watcher for directories:
 d:\Desktop\temp
[Info  - 9:31:08 AM] (282216) Searching for source files
[Info  - 9:31:08 AM] (282216) Found 1 source file
(282216) [IDX(FG)] index libraries d:\Desktop\temp (index) ...
(282216) [IDX(FG)]   read stdlib indices (44ms)
(282216) [IDX(FG)] index libraries d:\Desktop\temp (index) [succeed] (48ms)
(282216) [FG] parsing: d:\Desktop\temp\test.py (15ms)
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 9ms] (85ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\builtins.pyi (34ms)
(282216) [FG] binding: d:\Desktop\temp\test.py (0ms)
Python was not found; run without arguments to install from the Microsoft Store, or disable this shortcut from Settings > Manage App Execution Aliases.
[Info  - 9:31:08 AM] (282216) Background analysis(1) root directory: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist
[Info  - 9:31:08 AM] (282216) Background analysis(1) started
(282216) Background analysis message: setConfigOptions
(282216) Background analysis message: setImportResolver
(282216) Background analysis message: ensurePartialStubPackages
(282216) Background analysis message: setTrackedFiles
(282216) Background analysis message: markAllFilesDirty
(282216) Background analysis message: setFileOpened
(282216) Background analysis message: getSemanticTokens full
(282216) [BG(1)] getSemanticTokens full at d:\Desktop\temp\test.py ...
(282216) [BG(1)]   parsing: d:\Desktop\temp\test.py (10ms)
(282216) [BG(1)]   parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\builtins.pyi [fs read 4ms] (82ms)
(282216) [BG(1)]   binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\builtins.pyi (39ms)
(282216) [BG(1)]   binding: d:\Desktop\temp\test.py (0ms)
(282216) [BG(1)] getSemanticTokens full at d:\Desktop\temp\test.py (135ms)
(282216) Background analysis message: analyze
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py ...
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py (16ms)
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py (16ms)
(282216) Background analysis message: getSemanticTokens range
(282216) [BG(1)] getSemanticTokens range 0:0 - 0:0 at d:\Desktop\temp\test.py (0ms)
(282216) Background analysis message: resumeAnalysis
(282216) Background analysis message: setFileOpened
(282216) Background analysis message: markFilesDirty
(282216) [FG] parsing: d:\Desktop\temp\test.py (1ms)
(282216) [FG] binding: d:\Desktop\temp\test.py (1ms)
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: analyze
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py ...
(282216) [BG(1)]   parsing: d:\Desktop\temp\test.py (1ms)
(282216) [BG(1)]   binding: d:\Desktop\temp\test.py (0ms)
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py ...
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing.pyi [fs read 9ms] (33ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing.pyi (11ms)
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 11ms] (18ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing_extensions.pyi (2ms)
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi [fs read 7ms] (20ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_typeshed\__init__.pyi (3ms)
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\types.pyi [fs read 9ms] (21ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\types.pyi (7ms)
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\abc.pyi [fs read 6ms] (6ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\abc.pyi (0ms)
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py (175ms)
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py (177ms)
(282216) Background analysis message: resumeAnalysis
(282216) Background analysis message: getSemanticTokens delta
(282216) [BG(1)] getSemanticTokens delta previousResultId:1670682668522 at d:\Desktop\temp\test.py (1ms)
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: setFileOpened
(282216) Background analysis message: markFilesDirty
(282216) Background analysis message: analyze
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py ...
(282216) [BG(1)]   parsing: d:\Desktop\temp\test.py (1ms)
(282216) [BG(1)]   binding: d:\Desktop\temp\test.py (0ms)
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py (0ms)
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py (1ms)
(282216) Background analysis message: resumeAnalysis
(282216) [FG] parsing: d:\Desktop\temp\test.py (0ms)
(282216) [FG] binding: d:\Desktop\temp\test.py (0ms)
(282216) Background analysis message: getSemanticTokens delta
(282216) [BG(1)] getSemanticTokens delta previousResultId:1670682672205 at d:\Desktop\temp\test.py (0ms)
(282216) Background analysis message: setFileOpened
(282216) Background analysis message: markFilesDirty
(282216) [FG] parsing: d:\Desktop\temp\test.py (2ms)
(282216) [FG] binding: d:\Desktop\temp\test.py (0ms)
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getSemanticTokens delta
(282216) [BG(1)] getSemanticTokens delta previousResultId:1670682673008 at d:\Desktop\temp\test.py ...
(282216) [BG(1)]   parsing: d:\Desktop\temp\test.py (1ms)
(282216) [BG(1)]   binding: d:\Desktop\temp\test.py (1ms)
(282216) [BG(1)] getSemanticTokens delta previousResultId:1670682673008 at d:\Desktop\temp\test.py (3ms)
(282216) Background analysis message: analyze
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py ...
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py ...
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 9ms] (12ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_collections_abc.pyi (0ms)
(282216) [BG(1)]     parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 6ms] (7ms)
(282216) [BG(1)]     binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\collections\abc.pyi (1ms)
(282216) [BG(1)]   checking: d:\Desktop\temp\test.py (47ms)
(282216) [BG(1)] analyzing: d:\Desktop\temp\test.py (47ms)
(282216) Background analysis message: resumeAnalysis
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing.pyi [fs read 2ms] (39ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing.pyi (9ms)
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing_extensions.pyi [fs read 1ms] (5ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\typing_extensions.pyi (2ms)
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_collections_abc.pyi [fs read 1ms] (2ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\_collections_abc.pyi (1ms)
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\collections\abc.pyi [fs read 0ms] (0ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\collections\abc.pyi (1ms)
(282216) [FG] parsing: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\abc.pyi [fs read 1ms] (2ms)
(282216) [FG] binding: c:\Users\aprec\.vscode\extensions\ms-python.vscode-pylance-2022.12.20\dist\typeshed-fallback\stdlib\abc.pyi (1ms)
(282216) Background analysis message: getDiagnosticsForRange
(282216) Background analysis message: getDiagnosticsForRange

You have provided no type declaration for mydict, so pyright (the type checker that underlies pylance) is inferring its type based on its assigned value. In this case, the inference logic determines that its type is dict[int, None]. That means any subsequent attempt to assign values other than None to the dictionary is considered a type violation. For more details about pyright's dictionary type inference, refer to this documentation.
The recommended way to handle this case is to provide a type declaration as follows:
mydict: dict[int, int | None] = {k: None for k in dict_keys}

Or you can place the declaration on a separate line:
mydict: dict[int, int | None]
mydict = {k: None for k in dict_keys}

You have provided no type declaration for mydict, so pyright (the type checker that underlies pylance) is inferring its type based on its assigned value. In this case, the inference logic determines that its type is dict[int, None]. That means any subsequent attempt to assign values other than None to the dictionary is considered a type violation. For more details about pyright's dictionary type inference, refer to this documentation.
The recommended way to handle this case is to provide a type declaration as follows:
mydict: dict[int, int | None] = {k: None for k in dict_keys}

Or you can place the declaration on a separate line:
mydict: dict[int, int | None]
mydict = {k: None for k in dict_keys}

Oooooho. Thanks so much!  I think this may be the only good example of a type declaration of a dictionary comprehension on the web. I was not able to find one. I ended up structuring the code differently to avoid this issue, but now I understand.


Make range staging more discoverable

Right-clicking or making the + - clickable to stage would be a good start.

This is now much better! Just merged a PR for editor context actions. There are global commands, which keybindings can bind to. There are editor gutter decorations which help out as well.


Typed torii-client abstractions and query API

Background
Torii-client currently exposes functions to fetch from torii-server. Right now they are low level abstractions, we can improve these to make it very easy for any js app to sync or fetch with a remote torii.
Right now we sync the entire of the world state onload, and also when state changes these are reflected. This is great for prototyping however when applications become more complex and the state grows the whole application and UX slows because of this.
We can provide a clean abstraction for users to query the state allowing for extremely effiecent apps.
Tasks
This task is to build pure JS abstractions within the torii-client package which can then be used upstream in react or other frameworks.

Here's my suggestion for the interface. Examples below are based on the Dojo starter.
Fetching a single entity
If you only want a single entity, you should be able to query the model directly.
const move = dojo.moves.find({
  where: {
    player: "0x0"
  }
}

This will strongly type the move variable as an instance of Moves. The where query should also be typed.
const move: Moves | undefined;

(property) where: {
  player?: string;
  remaining?: number;
  last_direction?: Direction;
}

Fetching multiple entities from the same model
const moves = dojo.moves.findMany({
  where: {
    remaining: 0
  }
}

Same as before, moves will be strongly typed, just like the where query.
const moves: Array<Moves>;

Fetching multiple entities from different models
const entities = dojo.findEntities(
  {
    where: {
      player: "0x0",
    },
  },
  [Models.Moves, Models.Position]
);

The resulting entities array will by typed by being an array of Moves and Position elements. Consumers can differentiate by checking the added __modelName on the entity. Or we could also export a typeguard for every model so that it can be checked that way.
const move: Array<Moves | Position>;

Executing a call
Executing functions should also be strongly typed, to have the best DX.
Again, for the Dojo starter, this should result in the code below being valid (and fully typed)
await dojo.actions.spawn("0x0");

await dojo.actions.move("0x0", [Directions.Up]);

This generally looks good!
One concern is with the namespacing of the models / contracts (resources). Attaching actions and moves directly to the dojo namespace will cause issues when there are multiple resourceswith the same name.
At the dojo level, we are working towards namespacing resources using the fully qualified url.
For example,
dojo_examples::models::moves
dojo_examples::actions::actions

Then a different project could have the same resource names:
other_project::models::moves
other_project::actions::actions

We should have a generic base api:
dojo.findEntities(...)
...

And then generate a namespaced client per project:
import examples from "dojo_examples";
import other from "other_project";

const moves = examples.models.moves.findMany({
  where: {
    remaining: 0
  }
}

const otherMoves = other.models.moves.findMany({
  where: {
    remaining: 0
  }
}

Another approach to consider is the runtime type inference projects like https://github.com/wevm/abitype provide. I haven't looked into it but it seems people prefer this now over generated clients for typescript.

I think that makes sense and having something similar to abitype would be really nice for typescript users, if we can get a nice typed interface for everything with compile time type checking then it would be really powerful. For eg. if we can leverage typescript at compile time to check if we can query 2 models at once that share the same field (it would throw an error at compile time otherwise, if we try to use a field that isnt present in one of them).
I think it also makes sense to potentially have the state management on the dojo.native side (bindings/dojo.c). Then we could register for callbacks or updates (by abstracting remote calls) to update the state on our side which would be more tailored for the type of sdk we're building. Like for Unity, that state would translate into game objects and components. I'm not sure about the efficiency of that as it would involve having 2 states in some cases but I think it really is the best devX compared to other solutions


MapView doesnt work with async/await

This probably applies to all interfaces that inherits from corePromise
If you try to return MapMiew instance in a promise using async& await you get compilation error:
Return expression in async function does not have a valid callable 'then' member.

Because async/await uses  ES6 's Promise interface , but ESRI jsapi uses dojo 's IPromise interface , they are not the same.

Yeah it's not the same. I was wondering if devs from ESRI knows about this issue and whether or not they are going to support ES6.

You can convert any promise-like object such as IPromise into an ES6 promise by using Promise.resolve:
await Promise.resolve(mapView);

However, there is another issue that you will immediately run into. Several objects in the JavaScript API are promises that fullfill with themselves when resolved. When attempting to resolve such promises, promise implementations that follow the A+ promise specification must recurse forever (or optionally detect the cycle and reject with a TypeError). This applies to most browser's native implementations and several popular polyfills such as Bluebird. If you run the above code in e.g. Google Chrome, it will simply hang forever. To get around this, I created the following helper function (written in TypeScript, which I infer is what you're using):
/**
 * Returns a promise that is fulfilled when the given Esri API object is ready.
 * @param object The object to wait for.
 */
export function ready(object: any): Promise<void> {
    return new Promise<void>((resolve, reject) => {
        if (object && typeof object.then === "function") {
            object.then(() => resolve(), reject);
        } else {
            resolve();
        }
    });
}

The trick is that it returns a Promise<void> instead of e.g. Promise<MapView>. The usage would then be:
await ready(mapView);

You might also find this helper useful as well:
/**
 * Loads the given Esri API object and returns a promise that is fulfilled when
 * the object is loaded.
 * @param object The object to load.
 */
export async function load(object: any): Promise<void> {
    if (object && typeof object.load === "function") {
        object = object.load();
    }

    await ready(object);
}

Then you can do this if you need to load e.g. a layer:
await load(layer);

Just ran into this issue, but with Layers, and could see this being a really annoying issue going forward. Would it be possible to alter the type definitions to specify that IPromise inherits from TypeScript's Promise or Thenable interfaces?


MTV-1375: add warning about certain guest configurations

JIRA

MTV-1375

PREVIEW

4.5. Creating migration plans

lgtm!

please merge


Inline version of fuzzy-finder?

With fzf I use the --height option to make it not go "fullscreen". With tab, if I type tab or ctrl-t, then decide not to go into one of the sessions and hit escape, it annoyingly still clears my current session.

Also, fwiw, I tried to see what would happen if I piped the name of a tab into tab so I could actually use it with fzf easily:
$ echo one | tab
thread 'tokio-runtime-worker' panicked at 'failed to enable raw mode: IoError(Os { code: 25, kind: Other, message: "Inappropriate ioctl for device" })', /Users/kbd/.cargo/registry/src/github.com-1ecc6299db9ec823/tab-command-0.5.4/src/service/terminal.rs:32:48
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I think there a few things I could do here:

I think I could make tab; ESC preserve your command history.  It wouldn't work if you had disconnected from a session though - as tab resets the terminal state when disconnecting (removing the stdout from your root shell from the buffer).
It definitely makes sense to have echo foo | tab do something.  Maybe open the fuzzy finder with the input as a query.

I think there a few things I could do here:

I think I could make tab; ESC preserve your command history.  It wouldn't work if you had disconnected from a session though - as tab resets the terminal state when disconnecting (removing the stdout from your root shell from the buffer).
It definitely makes sense to have echo foo | tab do something.  Maybe open the fuzzy finder with the input as a query.

Just so I'm clear, here's a quick screencast of what I'm talking about with the first point. This is just opening tab up and hitting escape:

Just so I'm clear, here's a quick screencast of what I'm talking about with the first point. This is just opening tab up and hitting escape:

Yeah, that's expected behavior at the moment.  I think I can make it better w/ the alternate buffer though.

Yeah, that's expected behavior at the moment.  I think I can make it better w/ the alternate buffer though.

Ah, the inappropriate ioctl error is an upstream issue in crossterm: https://github.com/crossterm-rs/crossterm/issues/396
I was able to fix the 'clearing' issue though.  It'll be going out with v0.6.0.

Ah, the inappropriate ioctl error is an upstream issue in crossterm: https://github.com/crossterm-rs/crossterm/issues/396
I was able to fix the 'clearing' issue though.  It'll be going out with v0.6.0.


Test Bot 2

Test Bot 2

Test Bot 2

Test Bot 2

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.001 ETH (4.08 USD @ $4075.25/ETH)  attached to it.

If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.
These users each claimed they can complete the work by 264 years, 11 months from now.
Please review their action plans below:
1) test3 has been approved to start work.
The quick brown fox jumps over the lazy dog.
2) test4 has applied to start work (Funders only: approve worker | reject worker).
The quick brown fox jumps over the lazy dog.
3) test5 has applied to start work (Funders only: approve worker | reject worker).
The quick brown fox jumps over the lazy dog.
Learn more on the Gitcoin Issue Details page.

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

@test3

@nutrina please take a look at the submitted work:

PR by @test3

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 0.001 ETH  has been submitted by:

@test3

@nutrina please take a look at the submitted work:

PR by @test3

Learn more on the Gitcoin Issue Details page
Want to chip in? Add your own contribution here.
Questions? Checkout Gitcoin Help or the Gitcoin's Discord
$0 more funded OSS Work available on the Gitcoin Issue Explorer


service-ad-impression-proxy.clusters.pluto.tv

Hi,
service-ad-impression-proxy.clusters.pluto.tv is needed for play stream on this website.

Thank you for this Oliver @F4HTB.
This isn't going to change.
Closing.


Pre-trained model

How can I load the pre-trained model for DIB-R or where can I find the pretrained parameters for  DIB-R ?  I have seen the author say that he released the pre-trained models in the paper .

the same question

Sorry we can't release pre-trained model in Kaolin, closing.


Minor hie-cabal.yaml improvements

I ran haskell-language-server in the background for a bit and fixed a
few things.

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[ ] Relevant tickets are mentioned in commit messages

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

If you updated any cabal files or added Haskell packages:

[ ] $(nix-build default.nix -A dev.scripts.updateMaterialized) to update the materialized Nix files
[ ] Update hie-*.yaml files if needed

If you changed any Haskell files:

[ ] $(nix-shell shell.nix --run fix-stylish-haskell) to fix any formatting issues

If you changed any Purescript files:

[ ] $(nix-shell shell.nix --run fix-purty) to fix any formatting issues

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

No updates for hie-stack.yaml?

This is "I did it for my own usage and I thought I might as well commit it" rather than "I sat down to update the hie-*.yaml files properly". I would like to do the latter, but I thought I might as well commit these bits.

The plutus-core:exe path is missing.

Fixed a few small things, more later!


ASP.NET assemblies are being included in neon-cli?

I'm seeing 17MB+ of Microsoft.AspNetCore.*.dll  files when building/publishing neon-cli.  One of our package references must be referencing ASP.NET somewhere.  We're seeing the same thing with neon-desktop.
I wonder if this could be related to these warnings:
Severity	Code	Description	Project	File	Line	Suppression State
Warning	CS8032	An instance of analyzer Microsoft.CodeAnalysis.CSharp.Analyzers.FixAnalyzers.CSharpFixerWithFixAllAnalyzer cannot be created from C:\Users\jeff\.nuget\packages\microsoft.codeanalysis.analyzers\1.1.0\analyzers\dotnet\cs\Microsoft.CodeAnalysis.CSharp.Analyzers.dll: Could not load type 'Microsoft.CodeAnalysis.Analyzers.FixAnalyzers.FixerWithFixAllAnalyzer`1' from assembly 'Microsoft.CodeAnalysis.Analyzers, Version=<IP_ADDRESS>3, Culture=neutral, PublicKeyToken=31bf3856ad364e35'..	neon-cluster-operator	C:\Users\jeff\.nuget\packages\microsoft.codeanalysis.analyzers\1.1.0\analyzers\dotnet\cs\Microsoft.CodeAnalysis.CSharp.Analyzers.dll	1	Active

These projects are referencing the ASP.NET analyzers when they shouldn't.

After poking around, it looks like the problem may be due to the Neon.Kube.Setup library project having a project reference to Neon.Kube.Operator which uses the Microsoft.AspNetCore.JsonPatch nuget package.

FIXED: I removed the Neon.Kube.Operator project reference and the Microsoft.AspNetCore.*.dll assemblies in the build output folders are gone now.
This didn't fix the analyzer warnings though.  I'm going to have a look at that as well.

FIXED: The build warnings were coming from Neon.Kube.Operators.  I fixed this by explicitly referencing the Microsoft.CodeAnalysis.Analyzers v3.3.4 nuget package as described here:
https://github.com/dotnet/roslyn-analyzers/issues/6395


pagination bootstrap wont work

not working
$(document).ready ->
$('.offers-table table').dataTable({
sPaginationType: "bootstrap",
});
working but no bootstrap style
$(document).ready ->
$('.offers-table table').dataTable({
pagingType: "full_numbers",
});
how can i implement bootstrap pagination thanks

You just have to link in the DataTable Bootstrap JS/CSS and use 'full_numbers' for pagingType.
Bootstrap 3 config
Make sure you only load the jquery.dataTables.bootstrap file

Hi @delacruzjames,  this thread can be closed?

@ricardodovalle yah got it thanks

Thansk @jh125486 :clap: :+1:  and @delacruzjames

Hey, sorry to re-open this... I can file a separate issue, but this seemed pertinent.
Some Background:
I just updated the gem from 3.1.1 to 3.3.0.  Everything was working before, but I was doing a bunch of housekeeping, and updating outdated gems.
I am using Bootstrap 2 styles, and have implemented them as documented in the README - Bootstrap 2 Installation.  As specified, I have set the pagingType: "bootstrap" when I initialize the datatables plugin.
As of the update, setting the pagingType to "bootstrap" throws an exception, and no datatable is rendered.  If I set the pagingType to "full_numbers" or "simple_numbers", the plugin works but the pagination links are unstyled.
After setting some breakpoints in the browser, I can see that where the exception is raised (inside the _fnFeatureHtmlPaginate method), that the DataTable.ext.pager dictionary has no key bootstrap. So the fact the the exception is raise I guess makes sense.
Is there still supposed to be a pagingType: "bootstrap" for bootstrap 2 styles? or should I be using "full_numbers" like for bootstrap 3?  (and yes, I'm aware that bootstrap 2 is no longer developed and that I should update to bootstrap 3, but my hands are tied on that one at the moment).
On a side note, perhaps wrapping this bit in a try/catch structure in the _fnFeatureHtmlPaginate method  would prevent the javascript from completely failing... but that belongs in the datatables javascript implementation, rather than in this gem.


huge pages

https://nvdimm.wiki.kernel.org/2mib_fs_dax explains how memory mapping a file on a dax-capable filesystem can be done with huge pages (2MiB) instead of the normal 4KiB.
We should write a test that verifies whether an application can use huge pages. The Wiki has instructions for testing this.
This test might currently fail, because the Wiki mentions a "-E stride=512" option for mkfs.ext4 and some other changes for xfs which we currently don't use. We might have to add that.

The test can be an extension of the existing https://github.com/intel/pmem-csi/blob/devel/test/e2e/storage/dax/dax.go

I tried the steps (no k8s involved, just command line for starter) from above-mentioned page in a VM we use for CI tests (running Clear) , but I see no traces in /sys/kernel/debug/tracing/trace. I wonder is that trace supposed to appear in VM. If no trace on VM, then it's not easy to use that technique in CI tests.
Next, I will try on bare metal for comparison.
Another side question is, what determines the page size for given region: is there some setting (to be set where?), or is this supposed to be transparent to user? Or is it so that bigger page is tried first with fallback to smaller size?

I don't know. Please ask our Intel colleagues who work on the kernel support for PMEM.

Resolved via https://github.com/intel/pmem-csi/pull/499


new_data_update is not emitted when the change is a new key in the referenced path

I am using a reference to listen for changes in a path. However, the signal only fires when an existing path is edited, not when a new key is added somewhere.
 Cause database-wise listeners not seeing new keys is a known thing.
Can you share your reference initialization snippet?

This is a known fact.
Atm, I don't really know how to deal with that


clowns don't waddle in replays

Description
clowns don't waddle in replays and instead walk like normal, not sure why its just saddening to not see clowns waddling in the replays
Reproduction
open a replay
the
https://github.com/space-wizards/space-station-14/assets/156087924/90072a15-0149-49a0-a69c-61ebc0bbc0f0
Additional context
outrageous and a crime, honk

waddling has been reverted and will need a proper re-implementation with an animation system


#147 bug fix

#147 bug fix

I'll have to close this one as React Native's fast change pace makes adding and supporting backwards compatibility with older releases impractical. However, all breaking changes will be released with a major version bump, so please consider using<EMAIL_ADDRESS>if your project depends on pre-0.40 React Native.


Create rgb-hex convert

Description
I've added two functions for converting between HEX and RGB color representations. The hex_to_rgb function converts a HEX color code to its RGB components, while the rgb_to_hex function does the reverse.
Changes Made

Added hex_to_rgb function.
Added rgb_to_hex function.

Examples
RGB to HEX Conversion
print(rgb_to_hex(0, 0, 0))         # Output: #000000
print(rgb_to_hex(34, 139, 34))     # Output: #228B22
print(rgb_to_hex(0, 128, 255))     # Output: #0080FF
print(rgb_to_hex(255, 255, 0))     # Output: #FFFF00
print(rgb_to_hex(255, 0, 128))     # Output: #FF0080

HEX to RGB Conversion
print(hex_to_rgb("#000000"))       # Output: (r: 0, g: 0, b: 0)
print(hex_to_rgb("#228B22"))       # Output: (r: 34, g: 139, b: 34)
print(hex_to_rgb("#0080FF"))       # Output: (r: 0, g: 128, b: 255)
print(hex_to_rgb("#FFFF00"))       # Output: (r: 255, g: 255, b: 0)
print(hex_to_rgb("#FF0080"))       # Output: (r: 255, g: 0, b: 128)

do you need any help in this conversion process ? do let me know am ready for contribution and to help you out


I can't get Istanbul to work with Mocha (--delay) and ESM

I have the following mocha command that I run for my tests...
istanbul cover mocha --delay --exit ./test/suite.js

async function wire(){
    await import("./Class.spec");
    ...
    run();
}
wire();

When I run I get...

(node:20108) ExperimentalWarning: The ESM module loader is experimental.
I:\Code\praesto-dna\packages\services\packages\callminer\node_modules.bin\mocha.CMD:1
(function (exports, require, module, __filename, __dirname) { @IF EXIST "%~dp0\node.exe" (
^
SyntaxError: Invalid or unexpected token
at new Script (vm.js:79:7)

How do I get this to work with my ESM mocha tests?

Same here please assist?


Patch releases for supported versions

Description
The current docker images have flagged CVE issues (at least some of which are known not to affect us)
There were also some issue with the last patch releases related to docs and the version reported by the binary
For above reasons we will be releasing some patch versions:

[ ] 1.19.4 - #20795
[ ] 1.20.3 - #20824
[ ] 1.21.2 - #20825

Release images for 1.18 and below have not been included as these are EOL
We may want to make this clearer with docs etc if we are not going to patch them

Do we have something like cherry-pick bot in Istio like https://github.com/istio/istio/pull/37873#issuecomment-1065814764? I think it is useful and make backport easier and clearer.

@pradeepcrao i have created milestones for each of the patch releases and updated the links in this ticket to reflect
i have also grouped any PRs i could see into their relevant milestone


HDF5 version of ImageNet (ilsvrc 2012) and CIFAR-10 datasets.

Where can I download HDF5 version of ImageNet (ilsvrc 2012) and CIFAR-10 datasets?
Can you just provide a download link?
It will be very helpful for me!
Thanks!

Sorry, we don't have it. You'll have to download and compile it yourself.


Publish this package on Pypi.org

Hi, I think this package can be in pypi.org, so this PR aims to prepare this package to this.
Since I am not the creator, i will not publish this package, but I hope that you will.
I am using this script to show the optical flow and i think this will be useful to other too.
To prepare this package:

I moved the example from a script to the README
I did a setup.py
I automated with a makefile (that should publish the package with a make deploy command)

Hi Susana, thank you very much for the contribution. I agree that it may be nice to have this package on pypi.org -- I will look at your PR later this week, merge the changes and submit to the repository. Thank you!

Hi @sbouchardet -- I just packaged the repository and pushed to PyPi. I did not merge the pull request as I made some additional changes. I did give you credits in the acknowledgements in the readme file, I hope that's OK! Thank you very much for the encouragements and packaging help.
https://pypi.org/project/flow-vis/0.1/


Write a "best practices" doc for ANP/BANP

There seems to be some confusion about how best to use ANP and BANP. More specifically regarding some best practices for using these objects in a cluster.  This issue will track the creation of an ANP+BANP "best practices" doc which will assist with these difficulties it should answer at least the following questions

How can we prove through set of policies that ANP with PASS action does not stop evaluation even though match has happened  like DENY and ALLOW action?
Besides zero-trust, what other security postures could BANP take? (even with zero-trust, we know now that it won’t work as is because it hampers essential cluster services)
Would a distro be responsible to come up with set of policies that leaves cluster in usable state after zero trust BANP policy is applied or customer needs to figure that out with help of our Tech Support?

/reopen


Add 3DES and file support to des.py

python des.py -c<PHONE_NUMBER>abcdef  d3001515557aadadd3001515557aadae
python des.py -d 161f79c6910b9c2d d3001515557aadadd3001515557aadae
-><PHONE_NUMBER>abcdef

Sorry for the late response. I'm out of town at the moment, but I will look at this next week.


Feature request: check for exception string (like Catch's CHECK_THROWS_WITH)

Description
I would like to have a macro equivalent to Catch's CHECK_THROWS_WITH, see https://github.com/philsquared/Catch/blob/master/docs/assertions.md#exceptions.
Currently, I would need to provide a try/catch block on my own and call CHECK on the exception's what() function.

Matchers are on the roadmap but I won't have the time to implement them properly in the next 2-3 months - just signed a 3 month contract to get some funds...
    }
    SUBCASE("should pass") {
        REQUIRE_THROWS_WITH(throw std::runtime_error("wtf"), "wtf");
    }
    SUBCASE("non-std::exception related") {
        CHECK_THROWS_WITH(throw 5, "wtf");
    }
    SUBCASE("doesn't throw") {
        CHECK_THROWS_WITH(printf("side-effects\n"), "wtf");
    }
}

The output from this will look like this:
[doctest] doctest version is "1.2.5"
[doctest] run with "--help" for options
===============================================================================
C:\doctest\scripts\playground\test.cpp(52)
TEST CASE:  using a custom exception assert macro
  runtime_error

C:\doctest\scripts\playground\test.cpp(54) ERROR!
  throw std::runtime_error("omg")
The expression threw an exception with a different message!
  Expected: "omg 2!!!"
  Received: "omg"

===============================================================================
C:\doctest\scripts\playground\test.cpp(52)
TEST CASE:  using a custom exception assert macro
  non-std::exception related

C:\doctest\scripts\playground\test.cpp(60) ERROR!
  throw 5
The expression threw an exception which does not derive from "std::exception"!

side-effects
===============================================================================
C:\doctest\scripts\playground\test.cpp(52)
TEST CASE:  using a custom exception assert macro
  doesn't throw

C:\doctest\scripts\playground\test.cpp(63) ERROR!
  printf("side-effects\n")
The expression didn't throw at all!

===============================================================================
[doctest] test cases:      1 |      0 passed |      1 failed |      0 skipped
[doctest] assertions:      3 |      0 passed |      3 failed |
[doctest] Status: FAILURE!

Matchers are on the roadmap but I won't have the time to implement them properly in the next 2-3 months - just signed a 3 month contract to get some cash... Until then you could use this solution:
#include "doctest.h"

#include <stdexcept>

#define DOCTEST_EXT_THROWS_WITH_IMPL(the_assert, expr, message)                                    \
    do {                                                                                \
        doctest::String _doctest_exception_string;                                                 \
        try {                                                                                \
            expr;                                                                                \
        } catch(std::exception & e) { _doctest_exception_string = e.what(); } catch(...) {         \
            _doctest_exception_string = "Unknown exception";                                       \
        }                                                                                \
        DOCTEST_EXPAND_VA_ARGS(the_assert)(_doctest_exception_string == doctest::String(message)); \
    } while((void)0, 0)

#define CHECK_THROWS_WITH(expr, message) DOCTEST_EXT_THROWS_WITH_IMPL(DOCTEST_CHECK, expr, message)
#define REQUIRE_THROWS_WITH(expr, message) DOCTEST_EXT_THROWS_WITH_IMPL(DOCTEST_REQUIRE, expr, message)

TEST_CASE("using a custom exception assert macro") {
    CHECK_THROWS_WITH(throw std::runtime_error("omg"), "omg 2!!!");
    REQUIRE_THROWS_WITH(throw std::runtime_error("wtf"), "wtf");
    CHECK_THROWS_WITH(throw 5, "wtf");
    CHECK_THROWS_WITH(((void)0), "wtf");
}

the output message will contain the exception result and what was expected - its not perfect, but should do the trick

Any news on this?

This is a high priority feature. I'll try to get version 2.1 out by the end of the year but cannot promise it - will notify here when done. Thanks for waiting.

This is now in the master branch!
in a few hours I'll update the changelog and make a github release.
So currently you can pass only C strings to the <LEVEL>_THROWS_WITH macros - like this:
CHECK_THROWS_WITH(do_parsing(), "bad parse!");

In the future support for matchers will be added (the ability to use objects instead of just plain old C strings) but the interface of the macros will not change.

@nlohmann aaand a bit unrelated to this issue, but I just released version 2.2 and now the DOCTEST_CONFIG_SUPER_FAST_ASSERTS config option also affects the normal asserts and not just the binary) - see the results in the benchmarks


RedisCommandTimeoutException: Command timed out after 10 second(s)

The configuration of our project is shown in the figure, the topology refresh mechanism has been configured.

It's been normal for a month, but there's a problem today.
2021-12-13 10:29:50,920 [http-nio2-8080-exec-128] ERROR com.paytm.pgplus.redis.RedisBridgeWorker.get():94 {REQUEST_ID=1595523588463} - Exception while reading from redis cluster:  io.lettuce.core.RedisCommandTimeoutException: Command timed out after 1 second(s) 	at io.lettuce.core.ExceptionFactory.createTimeoutException(ExceptionFactory.java:51) 	at io.lettuce.core.LettuceFutures.awaitOrCancel(LettuceFutures.java:114) 	at io.lettuce.core.cluster.ClusterFutureSyncInvocationHandler.handleInvocation(ClusterFutureSyncInvocationHandler.java:123) 	at io.lettuce.core.internal.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:80) 	at com.sun.proxy.$Proxy211.get(Unknown Source)
The problem is that we see that the connection exists on the service. Use command lsof - I :port also can see connection.
I'm sorry, because it was an emergency, we restarted the machine without leaving stack or IO log。
SpringBoot version: 2.3.1.RELEASE
Lettuce version: 5.3.1.RELEASE

Check out the reference documentation on timeouts.

I've seen it, but It doesn't work.
now I set up Netty keepLive, I hope it works.
`ClientResources clientResources = ClientResources.builder()
.nettyCustomizer(new NettyCustomizer() {
@Override
public void afterChannelInitialized(Channel channel) {
                    channel.pipeline().addLast(new IdleStateHandler(10, 0, 0));
                    channel.pipeline().addLast(new ChannelDuplexHandler() {
                        @Override
                        public void userEventTriggered(ChannelHandlerContext ctx, Object evt) throws Exception {
                            if (evt instanceof IdleStateEvent) {
                                ctx.disconnect();
                            }
                        }
                    });
                }
            }).build();`

I got same Exception.  My situation is after long time without operation ,  studdenly  send request more than thirty times , then this exception happen


Improved SQL formatting

It would be nice to have a option of formatting the SQL in more advanced ways than just keyword changes especially prettifying with line changes with from and with so it follows the SQL shown in the configuration options under SQL Configuration

Sorry, I didn't get it.
Could you post some example?


support_url_nameid translatable

This issue is imported from pivotal - Originaly created at Oct 7, 2019 by Thijs Kinkhorst
EB currently has a support_url_nameid (called openconext.supportUrlNameId in the INI file) setting that is global. Meaning the same URL is used for the NL and EN (and PT) interfaces. It would be nice if the url is 'translatable', that is, a different URL for each language so the EN interface links to EN documentation. Likely this means to move it to the languages files.

Additional background information: The support url was added in https://github.com/OpenConext/OpenConext-engineblock/commit/2652e2e844957b582581a612b28f072fa54f3e90 part of PR#555 (Michiel Kodde - Feb 25, 2020)

@thijskh I encountered the following url\'s and wondered  if they also need to be translatable now when I\'m on it? The latter is the one requested in this issue.

    openconext_support_url: \'https://example.org\'
    openconext_terms_of_use_url: \'https://example.org\'
    openconext_support_name_id_url: \'https://example.org\'

I also encountered translations in the parameter.yml when I removed the engineblock.ini configuration. Do we want to  have the translations in the parameters.yml and not in the translation files where someone would likely expect them?
(bstrooband - Apr 1, 2020)

Probably best to make all translatable indeed. (Thijs Kinkhorst - Apr 1, 2020)

Maybe it's me, but I don't see this change (Thijs Kinkhorst - May 13, 2020)

No it was me, I had finished the issue but only based my decision to do so on the description and not the complete conversation. My apologies. (bstrooband - May 20, 2020)


installation error

installation error when I'm at step
nmake
see below error
C:\dev\openSSL>nmake
Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX86\x86\nmake.exe" /                   depend && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX86\x86\nmake.exe" /                   _all

Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    IF EXIST .manifest DEL /F /Q .manifest
    IF EXIST libcrypto-1_1-x64.dll DEL /F /Q libcrypto-1_1-x64.dll
    link /nologo /debug /dll  /nologo /debug  /implib:libcrypto.lib /out:libcrypto-1_1-x64.dll /def:libcrypto.def @C:\Users\Jeffrey\AppData\Local\Temp\nmE52F.tmp || (DEL /Q libcrypto-1_1-x64.* libcrypto.lib && EXIT 1)

crypto\aes\aesni-mb-x86_64.obj : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'x86'
Could Not Find C:\dev\openSSL\libcrypto-1_1-x64.*
NMAKE : fatal error U1077: 'link' : return code '0x1'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX86\x86\nmake.exe"' : return code '0x2'
Stop.
-->
dump.txt

module machine type 'x64' conflicts with target machine type 'x86'

This indicates a conflict between the architecture for the Configure target and the toolchain. Typically this happens if you "Configure" for 64 bit ("VC-WIN64A") but you are using the Microsoft 32-bit toolchain (or vice versa).
If you want to build 64-bit OpenSSL make sure your environment is setup for the 64-bit compiler/linker. Similarly for 32-bit. You should be able to check what flavour of compiler you are currently using by running cl from the command line with no arguments:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29111 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

As you can see, in this case, I get the x64 toolchain.

ok thanks. wasnt a windows programmer, mainly mac. 1st tie building windows code on a windows pc.

C:\dev\openSSL>nmake
Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64\nmake.exe" /                   depend && "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64\nmake.exe" /                   _build_sw

Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
Microsoft (R) Program Maintenance Utility Version 14.27.29112.0
Copyright (C) Microsoft Corporation.  All rights reserved.
    "lib" /nologo /out:providers\libimplementations_static.lib @C:\Users\Jeffrey\AppData\Local\Temp\nm396E.tmp

crypto\md5\libimplementations-lib-md5_dgst.obj : fatal error LNK1112: module machine type 'x86' conflicts with target machine type 'x64'
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64\lib.EXE"' : return code '0x458'
Stop.
NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\VC\Tools\MSVC\14.27.29110\bin\HostX64\x64\nmake.exe"' : return code '0x2'
Stop.
C:\dev\openSSL>cl
Microsoft (R) C/C++ Optimizing Compiler Version 19.27.29112 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.
usage: cl [ option... ] filename... [ /link linkoption... ]

my cl is x64 but this error still occur

nvm i fixed it by re cloning (maybe old .o files not removed)


Fairly assign home/away matches amongst players

I really like your use of the circle method here, however, when using robin() I found myself wanting to fairly assign "home" matches to players, meaning that in the event of an odd number of players, each player has the same amount of home matches:
// players 1-5 all play 2 home and 2 away matches

// [ away, home ]
[
  [ [ 2, 5 ], [ 3, 4 ] ],
  [ [ 5, 1 ], [ 2, 3 ] ],
  [ [ 1, 4 ], [ 5, 3 ] ],
  [ [ 3, 1 ], [ 4, 2 ] ],
  [ [ 1, 2 ], [ 4, 5 ] ]
]

or in the event of an even number of players, each player has at most 1 more/less home match:
// players 1,3,5 each play 2 home and 3 away matches
// while players 2,4,6 each play 3 home and 2 away matches

// [ away, home ]
[
  [ [ 1, 6 ], [ 2, 5 ], [ 3, 4 ] ],
  [ [ 5, 1 ], [ 6, 4 ], [ 2, 3 ] ],
  [ [ 1, 4 ], [ 5, 3 ], [ 6, 2 ] ],
  [ [ 3, 1 ], [ 4, 2 ], [ 5, 6 ] ],
  [ [ 1, 2 ], [ 3, 6 ], [ 4, 5 ] ]
]

This PR accomplishes this.
This method was also mentioned in the wiki article you referenced in robin.js

The upper and lower rows can indicate home/away in sports, white/black in chess, etc.; to ensure fairness, this must alternate between rounds since competitor 1 is always on the first row.

I also bumped the version to 2.0.0 as some might see this as a breaking change if they for some reason relied on the order of the match arrays (although I doubt it because the [ away, home ] concept is new and I don't see why else the order would matter).
Let me know what you think :)

I think this is a great idea, and it's handled very gracefully. I agree that a major is needed (even though the interface itself is unchanged, and the change will likely go under the radar), as it does change determinism of groupstages higher up the stack, so people trying to resume a tournament might be confused.
Will leave a few questions on the PR, but overall the thing looks pretty good right of the bat. Thanks a lot for doing this!

Perhaps we should also update README.md to list the fact that in version 2.0.0 a user can expect fair home/away assignment and also explain the [ away, home ] ordering/reasoning.

Perhaps we should also update README.md to say that in version 2.0.0 a user can expect fair home/away assignment and also explain the [ away, home ] ordering/reasoning.

Done in commit 6d06751a41348c90692e01ffe2bbc2ad2b8ba53c.
How does it look?

How does it look?

Looks great :-)
As a somewhat amusing sidenote; this will be the second ever update to this library. Last PR was ~7 years ago (issue #1).

As a somewhat amusing sidenote; this will be the second ever update to this library. Last PR was ~7 years ago (issue #1).

Haha, yeah I know this repo is a bit old but while I was working on a React Native side project I needed to lay out teams in a round robin format and I thought I'd see if anyone had done it yet. Turns out you had, I just needed to add home/away support. Figured I'd open a PR rather than just keep the changes to myself :)

Definitely appreciated :-)

<EMAIL_ADDRESS>released :tada:


[#91916332] Print view

include data prin styles to index.html
add print scss
create scss utilities
add .no-print css rule which hide the element in print

merged


setup.py is not necessary?

Hello!
I don't have "setup.py" in this repository, is that okay?

That's correct. This package uses pyproject.toml to specify the build backend. Please see the setuptools documentation for more information.

That's correct. This package uses pyproject.toml to specify the build backend. Please see the setuptools documentation for more information.


Some countries are starting with lower case letters

In some localizations there are countries that start with lower case letters when they should not.
To identify them you can use vscode search/replace

The files with more than one match are the one that have countries that start with lower case letters that should be fixed.

Nice find. There is probably a method to replace those in vs code.

There is probably a method to replace those in vs code.

@cedvdb plans to change case for those countries? Should I submit a PR for this?

@hbatalhaStch Yes you may submit a PR,
Thanks


Update [ChangeNow changenow.io] #exchange #memo-required GDBIXG…NO2PNY

Address: GDBIXGZ3EKI3M4DBM65ADLHVNYIOG7JXGOHW5DHUZQAXPORY3QNO2PNY
Tags: exchange memo-required
Title: ChangeNow  Domain: changenow.io
Requested by @zhidilin05

good afternoon, do you want to return my lumens? transaction<PHONE_NUMBER>46334209	GBGW…QGXL transferred 31,372.465818 XLM to GDBI…2PNY
Memo (TEXT):<PHONE_NUMBER>648688
Account credited - 31,372.465818 XLM transferred to GDBI…2PNY
Account debited - 31,372.465818 XLM transferred from GBGW…QGXL

Hello @Zhidilin05,
This is combined with the same question asked in issue #402
https://github.com/stellar-expert/public-directory/issues/402


Added Svelte Package and NPM in README

Added Svelte Package and NPM package along with bun

@Zaid-maker Fixed the spelling now check


rhcos-puddle: start rebuilding openshift-clients too

ref. https://jira.coreos.com/browse/ART-844
also move move scheduled-job to proper jobs/build
also, add notification on failure (ref. https://jira.coreos.com/browse/ART-752)

lgtm, looks like you nailed those major points


Naming of aggregation feature which outputs multiple columns returns TypeError in feature_base/hash

Bug/Feature Request Description
This is similar to #540, as I have not found documentation for these kind of primitives.
I would like to create aggregation primitive, which creates multiple columns at once. However, naming is important part of this procedure, and I have achieved to add the clumns, but not to name them.
This is caused by feature_base\feature_base.py in hash(self)
This is my test benchmark:
import featuretools as ft
import pandas as pd
import numpy as np

CURRENT_FUNCTIONS = dict(
    max=np.nanmax,
    min=np.nanmin,
    mean=np.nanmean,
    sum=np.nansum,
    count=len,
    mean_monthly=lambda x: np.nanmean(x) / 12,
)

def agg_last_x_days(values, time_col, days, time=None):
    """
    Aggregate given data using prespecified aggregation functions.
    Possibilities are set in CURRENT_FUNCTIONS

    """
    data = values[
        time_col.values >= np.datetime64(time - np.timedelta64(days, "D"))
    ].values

    # only floats can have infinities
    if data.dtype.kind == "f":
        # we need to remove infinities before aggregation to be consistent with oracle
        data[np.isinf(data)] = np.nan
    result = []
    try:
        for function in CURRENT_FUNCTIONS.values():
            result += [function(data)]
#     except ValueError:
#         result = [None] * len(CURRENT_FUNCTIONS)
    except KeyError:
        raise KeyError("Unidentified aggregation function as parameter 'func'")
#     breakpoint()
    return result

def agg_last_x_days_generate_name(self, child_entity_id, base_feature_names, **kwargs):
    # print(self.kwargs)]})"
    names = ["{func}_{days}D({child_entity_id}.{feature}{where_string})".format(
            func=func.upper(),
            days=str(self.kwargs["days"]),
            child_entity_id=child_entity_id,
            feature=base_feature_names[0],
            where_string=kwargs["where_str"],
        ) for func in CURRENT_FUNCTIONS.keys()]
    return names

AGG_LAST_X_DAYS = ft.primitives.make_agg_primitive(
    function=agg_last_x_days,  # function to be used
    input_types=[
        ft.variable_types.Numeric,
        ft.variable_types.DatetimeTimeIndex,
    ],  # input data types
    number_output_features=len(CURRENT_FUNCTIONS),
    return_type=ft.variable_types.Numeric,  # data types to be returned
    uses_calc_time=True,  # whether function can utilize cutoff time information
    stack_on_self=False,  # whether the primitive could be stacked on itself
    cls_attributes={
        "generate_name": agg_last_x_days_generate_name
    },  # passing of name generating function
)

df = pd.DataFrame(
    {
        "ID": [1, 1, 1, 1, 2, 2],
        "dtime": [
            "2016-06-28 09:51:51.0",
            "2017-06-03 12:16:08.0",
            "2017-07-02 12:15:08.0",
            "2017-07-04 12:15:08.0",
            "2017-07-02 12:15:08.0",
            "2017-07-05 13:15:08.0",
        ],
        "value": [0, 3.0, 5, 0, 11, 14],  # float
        "value2": [1, 11, 1, 1, 11, 11],  # int
    }
)

cutoff_times = pd.DataFrame(
    {"ID": [1, 2], "time": ["2017-07-03 12:15:08.0", "2017-07-03 12:15:08.0"]}
)
df["dtime"] = pd.to_datetime(df["dtime"])
cutoff_times["time"] = pd.to_datetime(cutoff_times["time"])

es = ft.EntitySet("Dataset")
es.entity_from_dataframe(
    dataframe=df, entity_id="CAPP", index="index", time_index="dtime"
)

es.normalize_entity(
    base_entity_id="CAPP", new_entity_id="CLIENT", index="ID", make_time_index=False
)

fm, features = ft.dfs(
    entityset=es,
    target_entity="CLIENT",
    agg_primitives=[AGG_LAST_X_DAYS(days=1000)],
    features_only=False)

fm

this exact code raises:

2019-06-12 10:11:32,461 featuretools.entityset - WARNING    index index not found in dataframe, creating new integer column

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-68-ad74bb4230d5> in <module>
    102     target_entity="CLIENT",
    103     agg_primitives=[AGG_LAST_X_DAYS(days=1000)],
--> 104     features_only=False)
    105
    106 fm

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\utils\entry_point.py in function_wrapper(*args, **kwargs)
     44                     ep.on_error(error=e,
     45                                 runtime=runtime)
---> 46                 raise e
     47
     48             # send return value

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\utils\entry_point.py in function_wrapper(*args, **kwargs)
     36                 # call function
     37                 start = time.time()
---> 38                 return_value = func(*args, **kwargs)
     39                 runtime = time.time() - start
     40             except Exception as e:

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\synthesis\dfs.py in dfs(entities, relationships, entityset, target_entity, cutoff_time, instance_ids, agg_primitives, trans_primitives, groupby_trans_primitives, allowed_paths, max_depth, ignore_entities, ignore_variables, seed_features, drop_contains, drop_exact, where_primitives, max_features, cutoff_time_in_index, save_progress, features_only, training_window, approximate, chunk_size, n_jobs, dask_kwargs, verbose, return_variable_types)
    197
    198     features = dfs_object.build_features(
--> 199         verbose=verbose, return_variable_types=return_variable_types)
    200
    201     if features_only:

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\synthesis\deep_feature_synthesis.py in build_features(self, return_variable_types, verbose)
    225
    226         self._run_dfs(self.es[self.target_entity_id], [],
--> 227                       all_features, max_depth=self.max_depth)
    228
    229         new_features = list(all_features[self.target_entity_id].values())

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\synthesis\deep_feature_synthesis.py in _run_dfs(self, entity, entity_path, all_features, max_depth)
    334                                      child_entity=self.es[b_entity_id],
    335                                      all_features=all_features,
--> 336                                      max_depth=max_depth)
    337
    338         """

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\synthesis\deep_feature_synthesis.py in _build_agg_features(self, all_features, parent_entity, child_entity, max_depth)
    595                                            parent_entity=parent_entity,
    596                                            primitive=agg_prim)
--> 597                 self._handle_new_feature(new_f, all_features)
    598
    599                 # Obey allow where

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\synthesis\deep_feature_synthesis.py in _handle_new_feature(self, new_feature, all_features)
    410             return
    411         entity_id = new_feature.entity.id
--> 412         if new_feature.hash() in all_features[entity_id]:
    413             return
    414             raise Exception("DFS runtime error: tried to add feature %s"

c:\program files (x86)\microsoft visual studio\shared\python37_64\lib\site-packages\featuretools\feature_base\feature_base.py in hash(self)
    160
    161     def hash(self):
--> 162         return hash(self.get_name() + self.entity.id)
    163
    164     def __hash__(self):

TypeError: can only concatenate list (not "str") to list

This is caused by passing list of names into cls.generate_name, and this is killed inside hash function.
Unlike transformation primitive, aggregation primitive does not have get_feature_names function as mentioned in #540
I am running this on Win10, using FT 0.8.0 & Python 3.7

Currently, we do not support giving specific names to each of the output dimensions. When you set number_output_features featuretools will automatically append __0 ... __n-1 to your output features.
If you remove your code for generate name, what you've done about should work to produce features.
If you want specific names, I'd recommend breaking your custom primitive into multiple functions for now.

Opened issue #593 for this, so closing this issue for now.
Feel free to follow up here if the proposal above doesn't work for you

Hi @kmax12. I've run into this same issue, and it doesn't seem to be fixed by pull #679.
You've created a variable in FeatureBase to store a list of column names, but I can't see how you intend to set this value manually.
The get_names function simply appends an index to the string passed by the custom generate_name function. This means it still isn't possible to give each column of a multi-output a custom name.
@rwedge proposed adding a generate_names function which returns a list, which could be used by the get_names function. Then you could simply do this:
    def get_names(self):
        if not self._names:
            self._names = self.generate_names()
        return self._names

@apemann ,
Thanks for binging this up,  that PR did not fix this issue!  I'll reopen #593.  I think the generate_names function is a good solution.


New App Submission

App Logo (Required)

App Details (Required)
Type: Wallet
Name: Go Pocket
Homepage Url: https://gopocket.finance
Chains supported: Ethereum, Polygon, Arbitrum, BSC, HECO(not yet)
App Url (Required - at least one)
iOS Url: https://testflight.apple.com/join/KoUa5pBP
Android Url: https://play.google.com/store/apps/details?id=io.gopocket

Well, respond is a little bit slow...

Added on commit 63a809a4d2f1851c33cec14bc757afff82e4af6a

Hi thx for your respond!


Add description folder into App

Is your feature request related to a problem? Please describe.
No description in folder section
Describe the solution you'd like
Iterate the description folder;
"item": [
  {
    "name": "Employees",
    "item": [ // objects...],
    "description": "Employees is a users of the system" // <---- this
  }
]

Describe alternatives you've considered
For this moment no considered any alternative
Additional context

Implement in 8de490f


javaForms template not working on ARM 32 devices

When trying to use the javaForms template not working on ARM 32 devices, the following error is shown on the build of the Dockerfile.debug:
Executing task: DOCKER_HOST= docker compose build --pull --build-arg SSHUSERNAME=torizon --build-arg APP_ROOT=/home/torizon/app --build-arg IMAGE_ARCH=arm --build-arg SSH_DEBUG_PORT=2234 --build-arg GPU= testjavaforms-debug

WARN[0000] The "DOCKER_LOGIN" variable is not set. Defaulting to a blank string.
[+] Building 14.1s (10/17)                                                                                docker:default
 => [testjavaforms-debug internal] load build definition from Dockerfile.debug                                                      0.0s
 => => transferring dockerfile: 3.90kB                                                                                0.0s
 => [testjavaforms-debug internal] load metadata for docker.io/torizon/wayland-base:4-rc                                            1.3s
 => [testjavaforms-debug auth] torizon/wayland-base:pull token for registry-1.docker.io                                             0.0s
 => [testjavaforms-debug internal] load .dockerignore                                                                               0.0s
 => => transferring context: 56B                                                                                0.0s
 => [testjavaforms-debug  1/12] FROM docker.io/torizon/wayland-base:4-rc@sha256:d793656c981c67215939c2590a3ec67521674d8d13472a8ae6  0.0s
 => [testjavaforms-debug internal] load build context                                                                               0.0s
 => => transferring context: 274B                                                                                0.0s
 => CACHED [testjavaforms-debug  2/12] RUN sed -i 's/sid/bookworm/g' /etc/apt/sources.list.d/debian.sources                         0.0s
 => CACHED [testjavaforms-debug  3/12] RUN apt-get -q -y update &&         if [ "" = "-vivante" ] || [ "" = "-imx8" ]; then         0.0s
 => CACHED [testjavaforms-debug  4/12] RUN apt-get -q -y update &&     apt-get install wget lsb-release -y &&     wget https://pac  0.0s
 => ERROR [testjavaforms-debug  5/12] RUN apt-get -q -y update &&     apt-get -q -y install     openssl     openssh-server     rs  12.8s
------
 > [testjavaforms-debug  5/12] RUN apt-get -q -y update &&     apt-get -q -y install     openssl     openssh-server     rsync     tzdata     locales     fontconfig     libxrender1     libxtst6     libxi6     msopenjdk-21     file &&     apt-get clean && apt-get autoremove &&     rm -rf /var/lib/apt/lists/*:
0.654 Get:1 http://deb.debian.org/debian bookworm InRelease [151 kB]
0.742 Get:2 http://deb.debian.org/debian bookworm-updates InRelease [52.1 kB]
0.742 Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48.0 kB]
1.222 Get:4 https://packages.microsoft.com/debian/10/prod buster InRelease [6537 B]
1.762 Get:5 http://deb.debian.org/debian bookworm/main armhf Packages [8497 kB]
2.764 Get:6 http://deb.debian.org/debian bookworm-updates/main armhf Packages [12.1 kB]
3.751 Get:7 http://deb.debian.org/debian-security bookworm-security/main armhf Packages [129 kB]
5.902 Get:8 https://packages.microsoft.com/debian/10/prod buster/main amd64 Packages [202 kB]
6.285 Get:9 https://packages.microsoft.com/debian/10/prod buster/main all Packages [2393 B]
6.287 Get:10 https://packages.microsoft.com/debian/10/prod buster/main arm64 Packages [26.3 kB]
6.288 Get:11 https://packages.microsoft.com/debian/10/prod buster/main armhf Packages [22.1 kB]
6.381 Fetched 9149 kB in 6s (1560 kB/s)
6.381 Reading package lists...
9.361 Reading package lists...
12.08 Building dependency tree...
12.58 Reading state information...
12.61 E: Unable to locate package msopenjdk-21

So, there is no build of msopenjdk-21 for ARMv7 https://github.com/adoptium/containers/issues/502

Since the Java appears to be abandoning 32bit architectures
https://openjdk.org/jeps/449
I was not able to find a JEP for the aarch32 deprecation, but
since 2021 there is not maintainance for the aarch32 port of
OpenJDK.
So, we are also removing support for arm32 from the template.


Update the comment on ssl3_write_pending()

The struct s->s3 has been modified.
Check if there is a SSL3_BUFFER left, ssl3_write_pending() should be called.

Checklist

[x] documentation is added or updated

This pull request is ready to merge

Merged to the master branch. Thank you for your contribution.


Phase-based work policies

Originally created by Tom Smyth at 2018-03-16 09:20, migrated from redmine-#8157

Version set to 6.0

By Tom Smyth at 2018-04-29 11:24

Status changed from New to Closed

By Tom Smyth at 2018-03-20 00:13


add option to override IR in runLocalGenerationForWorkspace

@sahil485 added a couple comments, but broadly looks good to me


WIP Work Item Estimate Filter

This PR addresses #48, to give session users the ability to filter the work item card list in three ways.
Filter Options:

Show All (Unfiltered)
Show Only Unestimated Work Items
Show Only Work Items with an estimate

Live Updating
This update is intended to allow the Estimate Filter to update the work item list for all users connected to a session.

@cschleiden I know that there are a lot of moving pieces in passing events around to all the session users with SignalR, so is there anything I should be mindful of as I try to implement this feature request?


the zdiff function of player is no longer available?

it seems that it only works on items but not player in the newer version of pubg
btw, thanks for your great work

yes its not working in this version. but I will work on it.
thanks

I use your second version on xbox but the arrow for player change in game the  friends become enemies and the distance deasapear how I can resolve this please?
and very good work

can you send me xbox pcap? discord: TomatoMan#6006


Error: No platforms added to this project.

Get this error
"Error: No platforms added to this project. Please use cordova platform add <platform>."
When I run npm run android and npm run build.
Any ideas?

Because you forgot to run npm run restore. Please follow the docs


-march is not cross-plaform

Same issue as in https://github.com/Quantco/tabmat/issues/223
The setup script tries to set argument -march=native:
https://github.com/Quantco/glum/blob/a405fd73bdb959f533358027201ebb641a60f700/setup.py#L37
But this argument is not accepted by GCC in platforms like ARM and PPC. Instead, those platforms use mcpu (at least for GCC in linux), so to achieve the same thing, it should use -mcpu=native.

One way around this is to set the environment variable
GLM_ARCHITECTURE=default

before running pip install.
"default" would arguably have been a better default than "native".

I would prefer to remove the -march=native code completely. Most users will use the binary wheels or conda packages. People that opt for compiling on their own due to performance will have sufficient knowledge to tune C(XX)FLAGS.


How to keep multiple different monaco-editor instance in one project?

Our project depends on another dependency which uses an old version monaco, but our project uses a newer one.
Both our project and the dependency use monaco-loader to load monaco.
But I don't know why once we import the dependency, the monaco-loader loads the older one instead the newer one.
So, is there any method to make the monaco instance only takes effect in the specific area or namespace?

Currently, it's not possible with the same monaco-loader. monaco-loader loads monaco once and always returns what it loaded the first time.

So the old monaco in dependency can be "override" if I ensure the new monaco in my project loads first? For example, load it in the "index.tsx" of my project?

So the old monaco in dependency can be "override" if I ensure the new monaco in my project loads first?

right (if we are talking about monaco-usage only by @monaco-editor/react)


added generic function param to delete action

Summary
fixed the function definition of getEventsAfterDeleteSchedule to not require type asserting
Fixes

return type is correctly inferred by the param at call
better than type asserting

Closing because this function will get removed when we merge #457 (according to @bevm0)


suggest to combine the client version and server version together into one unified js file

suggest to combine the client version and server version together into one unified js file

They ARE unified when you compile it using browserify, or when you use the standalone file


Fix project.json files

With these changes the project compiles against netstandard 1.1 which increases the number of platforms it can be used on by a lot  (see platforms). The test project is compiled against netcoreapp1.0 and therefor runs on both the full framework as well as .net core. BenchmarkDotNet unfortunately only supports the full framework so I had to go with .net 4.5.1 for it.

That's excellent thank you!
I'm not so worried about the full framework requirement of BenchmarkDotNet for now, nor Appveyor failing on the build.

I can fix AppVeyor, two mins :)

Nice one @Jeavon !

Fixed the install but having a hard time getting it compile with the unsafe flag, not sure if this might be a clue https://blogs.msdn.microsoft.com/dotnet/2016/05/16/announcing-net-core-rc2/#div-comment-68235

Errm I think that's actually something else. I was able to build it locally ok.

From the command line?

Hmm, maybe MS have changed the latest path from http://dotnetcli.blob.core.windows.net/dotnet/dev/Installers/Latest/dotnet-win-x64.latest.msi Will see if Choco package gets updated

Yeah @Jeavon
To get it running uninstall your previous CLI version and ASP tools then install the following.

The .NET Core SDK Installer
(Preview 1) - Click .NET Core SDK Installer (Preview 1)
The .NET Core Tooling Preview 1 for Visual Studio 2015 - Click .NET Core Tooling Preview 1 for Visual Studio 2015.

From the package manager window I was able to compile it using.
dotnet build .\src\ImageProcessorCore\

I did get a warning
Project ImageProcessorCore (.NETStandard,Version=v1.1) will be compiled because expected outputs are missing

but it still compiled sucessfully

I cant build the other projects though using Visual Studio.
Severity	Code	Description	Project	File	Line	Suppression State

Error		C:\development\github\ImageProcessor\tests\ImageProcessorCore.Benchmarks\error CS0006: Metadata file 'C:\development\github\ImageProcessor\src\ImageProcessorCore\bin\Release\netstandard1.1\ImageProcessorCore.dll' could not be found	ImageProcessorCore.Benchmarks	C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Common.Targets	241

@Jeavon I just pushed a commit that fixes my build issues and gets the VS test runner going.
https://github.com/JimBobSquarePants/ImageProcessor/commit/cd4cf4e1c23f337e6dec1c4bdd8881fbd17f8420
Haven't been brave enough to run the CI yet as I think the Chocolaty package is out of date. There's is a discussion around the latest tools getting natively installed though on AppVeyor.
http://help.appveyor.com/discussions/questions/2249-how-to-use-latest-dotnet-cli

@JimBobSquarePants yeah, I have added a comment to the AppVeyor thread

@Jeavon Good man!

@Jeavon I wonder if we could make use of this in the interim?
https://github.com/c3-ls/ServiceFabric-Http/blob/master/build-definition.ps1#L64

I believe the new AppVeyor images will be available tomorrow or Friday


Does this only join self-created meeting?

I could not join the meeting created by another account.

only when u publish your zoom bot in marketplace, you can join other ppls meeting

only when u publish your zoom bot in marketplace, you can join other ppls meeting

I don't understand,
When I try to join meeting which is created by another account, it is not connecting
But when I try to join in the meeting which is created by same account, it is automatically joined.

Is there any solution for joining meeting which is created by another account