Have an option to install google-services.json

Describe the solution you'd like
Many android apps and some ios have to have google-services.json file in the project tree. It contains some sensitive information and should not be stored in repo. Having ability to set its content and path would be nice feature
Describe alternatives you've considered
Copy google-services.json to env variable and echo it in the post-clone.sh
Additional context
my post-clone script
#!/usr/bin/env bash
path is MODULE/src/VARIANCE/google-services.json
echo "create app/src/release/google-services.json"
echo $GOOGLE_SERVICES > app/src/release/google-services.json
ls -la app/src/release

Check out Setup AppCenter forward https://dev.to/adamgold/how-to-setup-appcenter-with-gitlab-without-pushing-secret-files-4mk8

@dougg0k yes, this works, but i requested the possibility to upload the google-services.json like we do with the signing keys


JSON config functionality

Added json config read/write to GameSettings and a virtual default that can be overwritten for games utilizing the engine.

I will fix naming ;)


to a newcomer it's hard to figure, how to handle submitting

I got it, but please, for the future, can you add some brief note about onSubmit on the "Getting Started" page?
I haven't found how to listen to submit event, and tried the example, but even there there's no onSubmit handler - I had to figure it through the error message.

I agree that the docs on that are lacking. I'm in the process of reworking all the docs, and I will definitely take this into consideration.
The definitive docs at the moment is under handleSubmit here.
Thank you for your feedback.

@sosloow How did you wire up the handleSubmit to an action?

@sosloow yes - posting an example would be nice since others seem to be running into this too...


caffeinated/modules viewa using a double-colon syntax

i usecaffeinated/modules to create modules,i need to render view that useing a double-colon syntax ,
i have a doubt,laravel is don't support this syntax ,can you tell me the theory about to  implementation.

It's simple, you don't have to take care about if laravel supports this syntax, the package make Laravel work with this syntax to get specific module views.
return view('posts.show');
Returns view in  base_path('resources/views/posts/show.blade.php')
return view('blog::posts.show');
Returns view in  config('modules.path')/blog/Resources/Views/posts/show.blade.php


Local notification restarting activity after upgrading to 4.2.1

It seems like there is either a bug or an undocumented breaking change for android in version 4.2.1
On an emulator running Android API 30, after upgrading from 4.2.0 to 4.2.1, tapping the notification generated by calling postLocalNotification while the app is running appears to restart the app/activity.
This behavior is the same on the latest version 4.2.2.
Things work normally on Android API 29.
Thanks for your work on this library! Let me know if you can't reproduce this and I can try to narrow down a more specific repro :)

Ah, looks like this is a duplicate of #825


Arabic Language Pull Request

I created YML, csv dictionary, and txt wordlistreadme files for arabic language support on TT9, Please test and let me know if this would be able to be pulled.
IMPORTANT: THIS LANGUAGE READS RIGHT TO LEFT, thorough testing may be needed due to difference in right vs left hand justification.

CSV file changed from spaces to tabs for frequency count

Synced fork with upsteam

IMPORTANT: THIS LANGUAGE READS RIGHT TO LEFT

Right, the way you have structured the CSV confuses the validator. Make sure you put the words first, then the frequency. The words must be written from right to left, though, as one would normally write them.

thorough testing may be needed due to difference in right vs left hand justification.

I am not sure what justification are you referring to. The only place Arabic text would be displayed in TT9 is the labels on the virtual keypad (if it is enabled). But they are centered, so it shouldn't matter. Or do you mean something else?
Finally, I can't read Arabic, so I won't be able to check for invalid or misspelled words. The word list will be used as it is. However, you are welcome to submit corrections later.

The reason i mentioned justification is that the TT9 software in abc mode shows the letter selection left to right in english when keys are being selected and was just wondering if it would automatically switch to right to left selections in arabic mode.

I dont see the options for this in any of the files but even though the physical arabic keypad shows<PHONE_NUMBER>, it types out as<PHONE_NUMBER> (in that order, in arabic the numbers read from left to right just like english, even though the rest of the language is read right to left). the java.util.Locale doesn't include any Arabic locales by default but I wonder if the system and/or input locale was changed to arabic that the numbers would automatically switch to the arabic versions.

Roboto or Roboto Lt don't support arabic, currently the dictionary file is in courier new i believe but would noto sans arabic be better? currently the dictionary loader is not loading the dictionary, throwing something like "��!'" on line 1 is not a valid word. The justification of the language gets corrected when the system locale is set to arabic, but the only issue is that when selecting in that mode, the right arrow will go left, and the left arrow will go right. Also for some reason the abcString is not doing anything and the mode select just displays the keys on the 2 key which is not correct.

I tried converting the dictionary file to utf-8 using libiconv but it instead went to UTF-8 with BOM, but this is an improvement as now, even though the dictionary loader on the phone is still not loading the dictionary, it actually displays the arabic letters on the fail on line one instead of ��!'. I think if the file were to be converted to pure UTF-8, without BOM, the dictionary would load and the only outstanding issue left would be the abcString not displaying.

I converted the dictionary file into pure UTF-8 and now the dictionary loads and predictive typing works!!!!! So that issue is completely resolved the only major issue that i would like some feedback on is about the abcString problem. Other than that, some minor things that can be added later to the Arabic keyboard is the arabic numbers and to fix when the phone locale is set to arabic, the letter/word options in TT9 are mapped wrong to the arrow keys (left goes right and right goes left)

I am glad you resolved most of your problems. It looks like we are almost good to go.
As for the ABC string - it can anything you want. It is there for user convenience, so that people know which mode is on. Usually, the first three letters of the alphabet make it clear enough.
Now, when it comes to computers, they don't care about left-to-right or right-to-left, they just see strings. This is why you had problems with dictionary validation and this is why the ABC string appears backwards. You always have to type from left to right, so - in the dictionary, put the word first, then the frequency, and the ABC - spell it backwards. There is need to change any code in ModeABC.
One more thing that comes to my mind is the virtual keyboard - the keys will also be labeled backwards. isArabic() could be used there too.
Now let's talk about the numbers. This is something I completely forgot. Replacing the characters shouldn't be a big effort. In each mode class, in the onNumber() function, there is something like: suggestions.add(String.valueOf(number));. Instead of just using the number, there could be a Language.getKeyNumber(), just like there is: language.getKeyCharacters(number).
However, the question is where to do it. I suppose it makes sense only in ModePredictive and ModeABC. Mode123 is meant for typing in numeric, date, money, phone number and similar fields in apps and websites. I am certain many websites will reject Arabic numbers as invalid, so in my opinion it is best to leave Western numbers there. However, I am not familiar with the Arabic part of the Internet. If you can confirm Arabic numbers work, I am OK with leaving them in Mode123, too. One would have to use another language to type Western numbers.

I am glad you resolved most of your problems. It looks like we are almost good to go.
As for the ABC string - it can anything you want. It is there for user convenience, so that people know which mode is on. Usually, the first three letters of the alphabet make it clear enough.
Now, when it comes to computers, they don't care about left-to-right or right-to-left, they just see strings. This is why you had problems with dictionary validation and this is why the ABC string appears backwards. You always have to type from left to right, so - in the dictionary, put the word first, then the frequency, and the ABC - spell it backwards. There is need to change any code in Language.getABCString().
One more thing that comes to my mind is the virtual keyboard - the keys will also be labeled backwards. isArabic() could be used there too.
Now let's talk about the numbers. This is something I completely forgot. Replacing the characters shouldn't be a big effort. In each mode class, in the onNumber() function, there is something like: suggestions.add(String.valueOf(number));. Instead of just using the number, there could be a Language.getKeyNumber(), just like there is: language.getKeyCharacters(number).
However, the question is where to do it. I suppose it makes sense only in ModePredictive and ModeABC. Mode123 is meant for typing in numeric, date, money, phone number and similar fields in apps and websites. I am certain many websites will reject Arabic numbers as invalid, so in my opinion it is best to leave Western numbers there. However, I am not familiar with the Arabic part of the Internet. If you can confirm Arabic numbers work, I am OK with leaving them in Mode123, too. One would have to use another language to type Western numbers.

yea thats what i thought too, i have the abcString set in the yml file just like how it is done in the hebrew and yiddish files but every time i compiled and pushed to my phone, it would just default to using the first three letters on the 2 key. This is the only reason that i made the change to the Language.getABCString() function, just for testing purposes to see whether or not the abcString would change. As it stands right now, the abcString that i have in the yml file keeps getting seen as null by the language file for some reason so the only way for the abcString to show up is for the getABCString() changes. I like your idea of using isArabic() in the virtual keyboard to display the keys from right to left but to be honest its not that important of a feature, mostly just cosmetic polish. About the numbers, I agree with you that the arabic numbers should only show up in modePredictive and ModeABC and leave Mode123 with western numbers. Most well programmed websites/apps will accept arabic numbers just the same as western numbers, even most dialers wont complain, but for the rest it is a 50/50 whether or not arabic numbers will cause something to break, even most smartphone arabic ime's include both arabic and western numbers for this reason.
I still havent been able to figure out what is causing the arabic yml abcString to be seen as null but once i figure that out i will revert the changes in Language.getABCString() back to original. Finally, my semester has started and I will probably have a little bit less time to work on this but please feel free to suggest or let me know of any changes that need to be made or that will make it better.

Thank you for telling me where to add support for the arabic numbers, full arabic number support has now been implemented in ModeABC and ModePredictive, tested and working. Mode123 i left untouched like you said for better support with allowing western number input into various applications/websites so as not to cause issues.
I still can't figure out what is causing the abcString from the arabic.yml to be read by Language.java as null, this is now the only outstanding issue to my knowledge.
After some testing on my phone, the ui will change the letter suggestions from left to right or right to left depending on the system locale, this is fine but it means that if we wanted to change how the suggestions and maybe even the on screen keyboard show, we might have to detect what the system locale is, or force it to be one way no matter what the android locale is set to. But to me this does not bother me as it is mostly cosmetic and doesnt affect function (i havent done any testing on the on screen keyboard however).

Ok i just took a look at the virtual keyboard (see attached photos) and i am having four issues, first the question mark is not the arabic question mark but this should be a very easy fix, Second is that all the letters displayed below the numbers are connecting as if they were trying to form a word, maybe theres a way to slightly space them out so that they show as individual letters and not connecting? third is that even in modePredictive and ModeABC, the numbers are not displaying as arabic numbers, although they type as arabic numbers (this should be the easiest to fix) and lastly in arabic locale systemwide, the ui flips itself entirely, showing 321 instead of 123 and so on, not sure how to fix this one yet.

OK, seeing your screenshots, I agree some more small adjustments are necessary. I believe "JO" shouldn't be displayed like this in ABC mode. The string should be the equivalent of "AR / alif-ba-ta", where "AR" is the abbreviated name of the language, not the name of the country (I suppose "JO" is for "Jordan"?). If you could provide the string I'll fix it. I can also fix the other small things.
Having said all this, I am currently busy optimizing the database, and I will have to take of several other languages, so it will probably take at least a month, until I am to finalize and release this PR. Just so you know.

yea of course, idk why its taking the second half of the locale ar-JO (yes, JO is Jordan) to display the language, but looking at other locales most are just one segment (eg "en") or both segments are the same. ive been using "أﺏﺕ" as the alif ba ta string so it should be something like "AR / أﺏﺕ".
No worries about the time frame, like I said earlier im also having more stuff to do this time as well. As long as incrementally things are getting fixed, it doesnt really matter as much how long it takes.

yea of course, idk why its taking the second half of the locale ar-JO (yes, JO is Jordan) to display the language, but looking at other locales most are just one segment (eg "en") or both segments are the same.

Apologies, I checked and it seems that Java does not support neutral Arabic locale. Let's keep "ar-JO".

i pulled out the old samsung again to reference a few things and i noticed that the equivalent of the abcString used there is just alif ba "اب" to prevent letters from connecting (ابت doesnt look as good as أﺏﺕ, but the latter uses a unicode non connecting standalone ba letter not found on the keyboard so if the أﺏﺕ doesnt work we can just use اب)

It's OK to use two letters only, as long as it is clear what it means. And I believe it is. As I said it is just a label for user convenience. The application itself doesn't care about it.

Also is there a way to replace text with a predefined word once the correct letters have been typed, specifically replacing it with the correct harakat for certain words?

Probably, you could use the "add word" function, but I am not sure what exactly do you mean. Could you please provide an example?

Nearly all arabic input methods automatically place the correct accents on الله once all the letters are typed out, so i was wondering if there is a way to automatically switch the word with this version either once the ه is typed or once the user presses space both in ModeABC and ModePredictive.

I had educate myself a bit, to understand what you mean.
Answering your question - no, unfortunately, TT9 is not able to do such complex conversions. But it isn't really necessary. It is only a matter of having the correct words in the dictionary.
For example, in French, "élève" could be written without diactritics as "eleve", but this is actually a different word. TT9 works this out by having the correct form of word in the dictionary, "élève"; and all the possible mappings "é", "è" and "e" on 3-key in the French.yml file. This way it knows that typing "35383" must yield "élève".
And as I understand, the currently included word list contains no diacritics, so you are seeing ambiguous suggestions. Can they be added somehow? Or can you find a word list the already contains them?
Adding diacritics on-the-fly is beyond my knowledge and amount of free time, so I can not offer this solution.

For this word the wordlist does include its accents on it, i was wondering if there was a way to do it in ModeABC just for this one word however, not necessarily on the fly diacritic adding for all letter, that would be way out of reach.

I see. OK, then please add the accented letters next to the regular ones in the .yml file. Also, if it is just one word, you could replace it with the accented variant in the dictionary file. This way it will appear correctly in Predictive mode, too.

Is there anything else we need to do before merging currently?

I don't think I need anything else from you.
As for me, after I release v27.0, I will review the code again and double check the ABC string, the text justification and if Backspace looks and works correctly (and anything else that we've discussed before); after that I'll fix any outstanding issues, then merge it.

@Arabi12321, I am closing this and opening a new PR from a new branch, because I can't edit your master.
Let's continue in #431.


Prepare for change in package identity semantics

To support package registries (#2967), we need to change the semantics around how packages are identified. Currently, they're based on a name computed from the package's effective URL, because the name declared in the package isn't known until the manifest has been parsed. We should instead use the declared URL of a package dependency as its identity.
After submitting #3023 and discussing with @neonichu & @tomerd, I think that we should tackle this first, independently of the package registry work. This PR lays the groundwork for making this change by introducing a new PackageIdentity type and updating existing calls to helper methods like PackageReference.computeIdentity to go through this new API. If everything works as intended, this shouldn't change any existing behavior.
From here, changing the semantics to use URL as a package identifier will entail the following:

Auditing calls to DependecyMirrors.effectiveURL to ensure that the original URL is used to establish identity, rather than any set mirrored URL
Auditing calls to the PackageIdentity.computedName property, which this PR uses to preserve the current behavior
Conditionalizing the new behavior on Swift tools version > 5.3
Looking at any newly-failing tests and determining whether the described behavior is correct, in which case we fix the implementation; otherwise, we change or remove the test. (I have specific concerns about testRootPackageOverrides and testPackageMirror).

@swift-ci please smoke test

I’m curious what happens—and what is supposed to happen—when there is a diamond and the two pointers at the bottom node differ only in the presence or absence of .git at the end of the URL. I don’t know if there are any tests that cover it, but it is something that has worked in the past (albeit with pins permanently stale in some toolchains).

@SDGGiesbrecht As far as I can tell, that should behave exactly the same. In the current implementation of computeDefaultName(fromURL:), a package's computed name (which, when lowercased constitutes its identity) is the last path component of the package dependency URL, removing any .git suffix. With the new PackageIdentity type, a package's identity would be insensitive to the following differences:

case or normalization
.git suffix or none
https://, git://, or ssh:// (either implicit or explicit) scheme
user, password, or port URL components

@swift-ci please smoke test

@swift-ci please smoke test linux

@swift-ci please smoke test linux

I think testRootPackageOverrides is absolute behaviour we have to retain. That'll be part of the stronger sense of identity we discussed offline. I'll be digging into how to implement it this week.

Conditionalizing the new behavior on Swift tools version > 5.3

I'm a little concerned about this idea, because I don't think two different senses of identity can compose well. Would this mean if my root package has a newer tools version, we generally use the new behaviour?

Conditionalizing the new behavior on Swift tools version > 5.3

I'm a little concerned about this idea, because I don't think two different senses of identity can compose well. Would this mean if my root package has a newer tools version, we generally use the new behaviour?

Sorry, I misspoke. What I meant was that we conditionalize the behavior based on the version of Swift / Swift Package Manager. That is, Swift 5.3 and below use the current behavior, and the next versions adopt the new behavior.

@swift-ci please smoke test

@swift-ci please smoke test

@mattt this looking great, thanks for putting together. at a high level I would prefer to carry PackageIdentity anywhere we deal with package's identity over leaving String based identity around, but lets see what @neonichu @abertelrud think

@mattt this looking great, thanks for putting together. at a high level I would prefer to carry PackageIdentity anywhere we deal with package's identity over leaving String based identity around, but lets see what @neonichu @abertelrud think

Yes, agreed. I think that's necessary for the work on making package identity more sophisticated. That said, I don't have a strong preference on whether we address that as part of that work or as part of this PR.

@mattt this looking great, thanks for putting together. at a high level I would prefer to carry PackageIdentity anywhere we deal with package's identity over leaving String based identity around, but lets see what @neonichu @abertelrud think
Yes, agreed. I think that's necessary for the work on making package identity more sophisticated. That said, I don't have a strong preference on whether we address that as part of that work or as part of this PR.
I agree as well (noted earlier but repeated here).  It doesn't have to be part of this PR but it would be ideal if it were.

@mattt this looking great, thanks for putting together. at a high level I would prefer to carry PackageIdentity anywhere we deal with package's identity over leaving String based identity around, but lets see what @neonichu @abertelrud think

Yes, agreed. I think that's necessary for the work on making package identity more sophisticated. That said, I don't have a strong preference on whether we address that as part of that work or as part of this PR.

I agree as well (noted earlier but repeated here). It doesn't have to be part of this PR but it would be ideal if it were.

@mattt wdyt? how much more complicated would it be to push it further?

@mattt this looking great, thanks for putting together. at a high level I would prefer to carry PackageIdentity anywhere we deal with package's identity over leaving String based identity around, but lets see what @neonichu @abertelrud think

Yes, agreed. I think that's necessary for the work on making package identity more sophisticated. That said, I don't have a strong preference on whether we address that as part of that work or as part of this PR.

I agree as well (noted earlier but repeated here). It doesn't have to be part of this PR but it would be ideal if it were.

@mattt wdyt? how much more complicated would it be to push it further?

I'm hesitant to do that for fear of introducing unintended functional differences. If the primary concern is losing fidelity / type hinting by downconversion to String, I think a better stop-gap measure would be to rewrite 75525f8 to, instead of removing the PackageReference.PackageIdentity typealias, renaming to something that doesn't shadow the new PackageIdentity type. With that, we'll have everything lined up to migrate to the new semantics in the next phase.

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

@swift-ci please smoke test

Closing as per offline discussion among the reviewers. Will open a new PR taking a new approach using dependency injection to consolidate call sites usage to a single PackageIdentity type.


Upgrade codecov action

Upgrading the action version of codecov
flagging the tests executed to organize coverage

Codecov Report

Merging #25 (08f6f07) into main (6f4b71e) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 08f6f07 differs from pull request most recent head 200ec94. Consider uploading reports for the commit 200ec94 to get more accurate results

@@           Coverage Diff           @@
##             main      #25   +/-   ##
=======================================
  Coverage   96.15%   96.15%
=======================================
  Files          10       10
  Lines         442      442
=======================================
  Hits          425      425
  Misses         17       17

Flag
Coverage Δ

api
96.15% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Remove-Item NUL

Sometimes a file such as NUL is created in error. This file can be removed
with cmd.exe like this:
DEL \\?\C:\NUL

but it appears cannot be removed with PowerShell. With current PowerShell, the
command just silently fails. With PowerShell 5.1, you get this:
PS C:\> Remove-Item '\\?\C:\NUL'
Remove-Item : An object at the specified path \\?\C:\NUL does not exist.

https://superuser.com/questions/282194

PowerShell explicitly blocks NUL and other reserved device names (in reservedDeviceNames array).

In PowerShell 7.0.3 you can use Remove-Item -LiteralPath \\?\C:\NUL (the LiteralPath param is key). I'm not sure why it doesn't work for just -Path but if you are using a newer PowerShell version then it's certainly possible.

Thanks. I did some more testing, and looks like it works since version 6.1.0
(Sep 2018):
https://github.com/PowerShell/PowerShell/releases/tag/v6.1.0


merge from arlac77/template-github-action,arlac77/template-kronos-component

.github/workflows/ci.yml

chore(deps): add 15.0.1 remove 15.0.0 (jobs.build.strategy.matrix.node-version)

Codecov Report

Merging #1409 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master     #1409   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines           39        39
  Branches         1         1
=========================================
  Hits            39        39

Continue to review full report at Codecov.

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


Collection exercises

Completed draft PR

Hey @builtbybea - left a comment in #3 that also applies to this pull request. You can find it here


Questions on the paper writing

Very impressive paper. But may I raise a question about some statements in the paper? I found some statements about mathematical reasoning might be not rigorous enough. It seems the authors may have unintentionally used the term "MathQA dataset" to refer to the GSM8K dataset, which could lead to confusion for readers. It would be great to clarify this in the paper and use the correct terminology to avoid any misunderstandings. The corresponding statements include:

"ChatGPT has improved significantly, which can tell from its accuracy increase from 71.40% to 78.00% on the MathQA dataset." Location: Section 3.2 (3)
"Task Name: MathQA" Location: Table 2
"One error example of ChatGPT’s January version on MathQA dataset." Location: Caption of Table 3

The key problem is, MathQA is another specific dataset from [1], which is completely different from GSM8K. GSM8K mainly focuses on arithmetic reasoning, and MathQA from [1] includes more diverse math word problems and is more challenging compared to GSM8K (though its annotation is noisier). According to [2], the performance of GPT-3.5 models is significantly lower on the MathQA dataset compared to the GSM8K. This makes the statements like " its accuracy increase from 71.40% to 78.00% on the MathQA dataset. " in your paper less rigorous. If we directly use the "MathQA dataset" to refer to the GSM8K dataset in the paper, we might cause unnecessary (but also very significant) misunderstandings.
These are my personal thoughts and I am not sure if they are reasonable. It would be appreciated a lot if I can get feedback from you and these corresponding statements can be fixed in the future version (if my opinion is reasonable).
[1] Amini, Aida, et al. "Mathqa: Towards interpretable math word problem solving with operation-based formalisms." arXiv preprint arXiv:1905.13319 (2019).
[2] Fu, Yao, et al. "Complexity-based prompting for multi-step reasoning." arXiv preprint arXiv:2210.00720 (2022).

Thanks for your advice!
In fact, I didn't know Mathqa is another work. We follow Jack_of_all[1], where the "MathQA" actually refer to GSM8K.
Thanks a lot for pointing out the co-reference problem. I will use GSM8K in the future version of our paper.
[1] Kocoń J, Cichecki I, Kaszyca O, et al. ChatGPT: Jack of all trades, master of none[J]. arXiv, 2023.


Add UX Test for clustering

In-depth testing is probably good for clustering
This is a placeholder ticket for far, where the community can discuss what to test for the clustering

@wetneb by any chance, do you have the dataset referenced in the doc for clustering ?, (The one with the districts, SWABBYS HOME, BALLARDS)

Also @wetneb , I am trying to play with clustering, but I am probably missing something
I have this very simple dataset, but when hitting edit cells/clustering, no clusters are detected
I was expecting to have at least "BALLARDS RIVER", with a cluster of size 2

CLUSTER.tsv.zip

Hmm, the doc about this is not actually very helpful! It should show an example where different values are clustered together. I think the screenshot in the docs was taken before #4004 was fixed.
So, as a dataset you could try this:
SWABYS HOME
SWABYS   HOME
BALLARDS river
BALLARDS River

Looks like @fgiroud didn't get around to completing this. I'll take a look to see if I can finish it so we can have a Cypress test for the cluster and edit dialog.


As support staff, it would be nice to have a "Debug Mode"

It might be worth having a "debug mode" that sets up kubeapi watch commands before any resources get created (other than the CRDs themselves)
This could help with diagnosing any race conditions or unmet dependencies.

This sounds to be something for users who have great knowledge of internals. ... I.e. us developers of the system.
I am not as convinced that regular users will have use for it.
Except when something breaks, to activate it on request from a developer, to get a deeper view into the operation and derailing.

Right, I guess the title is wrong. Should be "As a support engineer".

Now that makes sense


Tags not working as intended.

I have issues
I have the following TF config.
locals {
  tags = {
    "Environment" = var.environment
    "Platform"    = var.platform
    "Provisioner" = var.provisioner
    "Component" = ""
  }
}

module "eks_cluster" {
  source       = "terraform-aws-modules/eks/aws"
  cluster_name = local.name
  subnets      = local.private_subnets
  vpc_id       = local.vpc_id

  worker_groups_launch_template = [{
    name                 = "default-worker-group"
    instance_type        = var.worker_instance_type
    asg_desired_capacity = 1
    tags = merge(local.tags, map("Component", "workers"))
  }]
  tags = merge(local.tags, map("Component", "master"))
}

I want to have different tags on the main resources but different tags on the worker resources. Atm all the tags are concatenated into a single list via this line in the code:
https://github.com/terraform-aws-modules/terraform-aws-eks/blob/master/workers.tf#L68
I would like to use completely different tags or some different set of tags for certain resources, By using merge instead of concat, I believe we can achieve this.
I'm submitting a...

bug report
[ ] feature request
[ ] support request
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
Current behaviour is that all tags are combined. If duplicate keys are passed TF will fail.
Are you able to fix this problem and submit a PR? Link here if you have already.
If we agree on a solution, I can send a PR.

Affected module version:v5.0.0
OS: MacOS
Terraform version:0.12.5

This is a related issue as well: https://github.com/terraform-aws-modules/terraform-aws-eks/issues/428

Any feedback about this issue? I would want to have different tags for workers vs the rest of the resuorces and this does not permit that option

By using merge instead of concat, I believe we can achieve this.

Sounds reasonable to me. Feel free to make a PR 😃


[csrng/rtl] gen cmd additional data for multiple channels

This fix handle the case where multiple csrng application channels are running, and the gen command has additional data.
Signed-off-by: Mark Branstad<EMAIL_ADDRESS>

Thanks @mwbranstad for addressing the comments!


stdhttp: Receive a mux as interface instead of *http.ServeMux

I'm currently implementing open-telemetry, and I want to have the route pattern as part of the operation name.
I would be able to get the method and route pattern by injecting a custom ServeMux during the handler initialization.
Following the open-closed principle, you should accept interfaces and return structs. Would it be possible to accept a mux interface instead of the *http.ServeMux struct?
I offer myself for implementing it if approved.

Would we see this as a breaking change? If so, it's something we can control via a flag.
It sounds reasonable though!

It's not a breaking change. You would simply replace the struct with the expectations of what the struct should implement

Cool! Yeah we're happy to accept a PR for IT, hopefully can squeeze into the next release (ETA unknown)

@jamietanna I opened a Pull Request at #1720


acknowledge licensing issue in PrettyByteString

https://github.com/apache/incubator-pekko/blob/60279703a49d0a678de44b3cf14f4904eff9def3/actor/src/main/scala/org/apache/pekko/util/PrettyByteString.scala#L17-L18
Any code comment that has the words 'based on' in it is currently acting as release blocker. The Incubator PMC will not let us do any releases until we account for everything.
@jrudolph would you be able to provide some background on this code and what you would like us to document in the Pekko related license?
The code is not widely used. Not used anyway in this repo and I only found 1 usage in some test code in pekko-http-core.

see https://github.com/apache/incubator-pekko/pull/427 and https://github.com/apache/incubator-pekko-http/pull/191


Generate Help from Module Manifest psd1 file

Would it be possible to generate markdown help, probably closer related to the about help markdown creation via a module manifest psd1 file?
Or is there perhaps a best practice I'm not seeing for generating a general help file for a module? Like am I supposed to generate the about template and just fill that in manually for each module?

Also, would it be possible to generate markdown of the releasenotes, version information, and anything in the @PSDATA sectiion really. I feel it would be helpful and they are already part of built in standards of powershell modules. Why not make them more accessible in help files?

It's a great idea. The about help file can definitely use some love and improvements. Perhaps, a new parameter set for New-MarkdownAboutHelp that would take the module information and provide a more specific template. I think it's a lovely idea. Do you want to take a stub at it?

It might be a month or so before I have real time to dedicate to it. But I can give it shot.

We have reviewed the request and discussed the options. This is not a feature that we want to invest in. Most people solve this in their build scripts.


Playback of recorded file does not work as expected

Describe the bug
When trying to replay an recorded file I get the same frame over and over (same timestamp). When I try to access the color data of the recording my app crashes when trying to create a opencv Mat object from the received buffer.
To Reproduce

Go to https://www.microsoft.com/en-us/download/details.aspx?id=58385&WT.mc_id=
Download the OFFICE_SAMPLE_NFOV_UNBINNED.zip
Change path to the downloaded file in the following code and execute it:

#include "iostream"
#include <stdio.h>
#include <k4a/k4a.hpp>
#include <k4arecord/types.h>
#include <k4arecord/playback.hpp>

#include <opencv2/highgui/highgui.hpp>
#include <opencv2/core/core.hpp>
int main(int argc, char **argv) {
    k4a_playback_t playback_handle = NULL;
    if (k4a_playback_open("/home/raphael/Downloads/OFFICE_SAMPLE_NFOV_UNBINNED.mkv", &playback_handle) != K4A_RESULT_SUCCEEDED) {
        printf("Failed to open recording\n");
        return 1;
    }
    k4a::playback record(playback_handle);
    std::chrono::seconds s = std::chrono::duration_cast<std::chrono::seconds>(record.get_recording_length());
    printf("duration of record: %li", s.count());

    k4a::capture cap;
    bool run = true;
    while (run) {
        k4a_wait_result_t result = (k4a_wait_result_t) record.get_next_capture(&cap);
        if (result == K4A_STREAM_RESULT_SUCCEEDED) {
            // Process capture here
            std::cout << "SUCCESS\n";
            k4a::image img = cap.get_depth_image();

            int rows = img.get_height_pixels();
            int cols = img.get_width_pixels();
            std::cout << "depth image size: " << img.get_size() << "\n";
            cv::Mat depthMat(rows, cols, CV_16UC1, (void *) img.get_buffer(), cv::Mat::AUTO_STEP);
            cv::imshow("Bla", depthMat);
            cv::waitKey(1);

            k4a::image img2 = cap.get_color_image();
                int rows2 = img2.get_height_pixels();
                int cols2 = img2.get_width_pixels();
                std::cout << "color image size: " << img2.get_size() << "\n";
                std::cout << "Timestamp: " << img2.get_device_timestamp().count() << "\n";
//        cv::Mat image(cv::Size(rows2,cols2), CV_8UC4);
//        memcpy(image.data, img.get_buffer(),cols2 * rows2 * 4* sizeof(unsigned char));
//        cv::imshow("Bla",image);
//        cv::waitKey(0);
        }
        if (result == K4A_STREAM_RESULT_FAILED) {
            // Process capture here
            std::cout << "FAILED";
        }
        if (result == K4A_STREAM_RESULT_EOF) {
            // Process capture here
            std::cout << "EOF";
            run = false;
        }
    }

}

Output:
SUCCESS
depth image size: 737280
color image size: 360619
Timestamp: 10116077
SUCCESS
depth image size: 737280
color image size: 360619
Timestamp: 10116077
SUCCESS
depth image size: 737280
color image size: 360619
Timestamp: 10116077

And so on, timestamp stays the same even though I call get next capture.
I also tried to create the capture inside the while loop, but this leads to a crash of the app
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/allocator/allocator.c (118): k4a_capture_t_get_context(). Invalid k4a_capture_t (nil)
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/allocator/allocator.c (359): Invalid argument to capture_get_depth_image(). capture_handle ((nil)) is not a valid handle of type k4a_capture_t
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (51): k4a_image_t_get_context(). Invalid k4a_image_t (nil)
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (397): Invalid argument to image_get_height_pixels(). image_handle ((nil)) is not a valid handle of type k4a_image_t
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (51): k4a_image_t_get_context(). Invalid k4a_image_t (nil)
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (390): Invalid argument to image_get_width_pixels(). image_handle ((nil)) is not a valid handle of type k4a_image_t
depth image size: [2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (51): k4a_image_t_get_context(). Invalid k4a_image_t (nil)
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (366): Invalid argument to image_get_size(). image_handle ((nil)) is not a valid handle of type k4a_image_t
0
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (51): k4a_image_t_get_context(). Invalid k4a_image_t (nil)
[2019-10-04 12:10:08.837] [error] [t=20934] ../src/image/image.c (359): Invalid argument to image_get_buffer(). image_handle ((nil)) is not a valid handle of type k4a_image_t
When I try to execute this for opening a recording:
    k4a::playback record;
    record.open("/home/raphael/Downloads/OFFICE_SAMPLE_NFOV_UNBINNED.mkv");

then I get:
[2019-10-04 12:15:19.620] [error] [t=22100] ../src/../include/k4ainternal/matroska_read.h (143): k4a_playback_t_get_context(). Invalid k4a_playback_t (nil)
[2019-10-04 12:15:19.620] [error] [t=22100] ../src/record/sdk/playback.cpp (640): Invalid argument to k4a_playback_get_recording_length_usec(). playback_handle ((nil)) is not a valid handle of type k4a_playback_t
duration of record: 0[2019-10-04 12:15:19.620] [error] [t=22100] ../src/../include/k4ainternal/matroska_read.h (143): k4a_playback_t_get_context(). Invalid k4a_playback_t (nil)
[2019-10-04 12:15:19.620] [error] [t=22100] ../src/record/sdk/playback.cpp (449): Invalid argument to k4a_playback_get_next_capture(). playback_handle ((nil)) is not a valid handle of type k4a_playback_t
Expected behavior
Get different images when calling get next capture.
Desktop:

OS with Version: Ubuntu 18.04.2 LTS
SDK Version:   v1.3.0-beta.0-rc (Needed to update to this since I had a problem with the spdlogger in 1.2)
Firmware version:
== Azure Kinect DK Firmware Tool ==
Device Serial Number:<PHONE_NUMBER>12
Current Firmware Versions:
RGB camera firmware:      1.6.98
Depth camera firmware:    1.6.70
Depth config file:        6109.7
Audio firmware:           1.6.14
Build Config:             Production
Certificate Type:         Microsoft

You use the open method the wrong way.
It is a static method that you must not call with an object.
Use:
k4a::playback handle = k4a::playback::open("/home/raphael/Downloads/OFFICE_SAMPLE_NFOV_UNBINNED.mkv");

Also the readme file has Synchronized images only: No which means get_capture can return only a color or a depth image. So you nee d to NULL check to ensure they were captured. If it were yes, then you would not need to NULL check as every capture would have a synchronized depth and color image.

Thanks to your help I changed my code to this and got it working:
#include "iostream"
#include <stdio.h>
#include <k4a/k4a.hpp>
#include <k4arecord/playback.hpp>

#include <opencv2/highgui/highgui.hpp>
#include <opencv2/core/core.hpp>

int main(int argc, char **argv) {

    k4a::playback handle =  k4a::playback::open("/home/raphael/Downloads/OFFICE_SAMPLE_NFOV_UNBINNED.mkv");

    std::chrono::seconds s = std::chrono::duration_cast<std::chrono::seconds>(handle.get_recording_length());
    printf("duration of record: %li\n", s.count());

    k4a::capture cap;
    while(handle.get_next_capture(&cap))
    {
        k4a::image img = cap.get_depth_image();

        int rows = img.get_height_pixels();
        int cols = img.get_width_pixels();
        std::cout << "depth image size: " << img.get_size() << "\n";
        std::cout << "Timestamp: " << img.get_device_timestamp().count() << "\n";
        cv::Mat depthMat(rows, cols, CV_16UC1, (void *) img.get_buffer(), cv::Mat::AUTO_STEP);
        cv::imshow("Bla", depthMat);

        k4a::image img2 = cap.get_color_image();
        if(img2){
            int rows2 = img2.get_height_pixels();
            int cols2 = img2.get_width_pixels();
            std::cout << "color image size: " << img2.get_size() << "\n";
            std::cout << "Timestamp: " << img2.get_device_timestamp().count() << "\n";
            std::cout << "width: " << cols2 << "\n";
            std::cout << "heigth: " << rows2 << "\n";
            cv::Mat rawData( 1, img2.get_size(), CV_8UC1, (void*)img2.get_buffer() );
            cv::Mat decodedImage  =  cv::imdecode( rawData,  cv::IMREAD_UNCHANGED );
            cv::imshow("bla",decodedImage);
            cv::waitKey(1);
        }
    }
}

Is there an option to use the provided recorder tool to record synchronized files?
And is there an example on how to use the files for playback of a recorded scene?
Thank you very much for your support.

There is no current option to record only synchrnoized frames, but it would be easy to add. It's tracked in issue #557 . It's not exactly what you want, but we do have one playback example.


Can anyone share an example of nginx sidecar implementation?

I have a pre-build image which implements a custom REST API for prediction, /custom-prediction for example. I want to put this image into Kfserving without changing code or image at all. I think I could put an nginx image which forward /v1/models/custom-sample:predict to /custom-prediction to make it work.
Can anyone share an example yaml file for my case? Thanks in advance.

@rtrobin Currently we only support Istio as ingress, we are working towards v1beta1 which is going to make istio optional.

@rtrobin, we also don't enforce the API. If you want to run your container as-is and call it at /custom-prediction, it should work just fine.

It is not a problem in v0.4 now. I'm closing the issue.

@rtrobin how did you implement to use nginx in v0.4? Thanks

@HassanOuda KFServing v0.4 already supports custom prediction route. So for my case, nginx is not needed anymore. What's your case for using nginx?

Our production environment uses an external F5 loadbalancer that links to our nginx in kubernetes. so only ingress resources with a dns recognized by our loadbalancer can be used to expose a service in kubernetes. So how would that work with KFServing that purely uses Istio?
PS. I have Istio installed as part of the kubeflow installation and i created a nginx ingress resource that points the istio-ingressgateway:80 for path '/' on a specific DNS we created for our loadbalancer.


{AzureStorage} fixes Azure/azure-cli#23536

More Info: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-blob-index-how-to?tabs=azure-cli#upload-a-new-blob-with-index-tags
fixes Azure/azure-cli#23536
The Blob tags write operation can be performed by "Storage Blob Data Owner". So this role should be listed while the operation fails.
For CLI extensions the PR has been already created.  https://github.com/Azure/azure-cli-extensions/pull/5242
Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

AzureStorage


num_leds not referenced for i and j

In the following file, instead of referencing num_leds, the value for i and j is fixed to 30:
https://github.com/benevpi/pico_python_ws2812b/blob/226330d7b1b140c7d462da958809714384ffb3fb/examples/flash.py#L4-L9
Thanks!
Martin

Whoops. I'll update on Monday.
Ben
On Fri, 22 Jan 2021, 6:34 pm Martin from HiPi<EMAIL_ADDRESS>wrote:

In the following file, instead of referencing num_leds, the value for i
and j is fixed to 30:
https://github.com/benevpi/pico_python_ws2812b/blob/226330d7b1b140c7d462da958809714384ffb3fb/examples/flash.py#L4-L9
Thanks!
Martin
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/benevpi/pico_python_ws2812b/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHMR7ABFPUGSXHT4BXXUPPTS3HAKRANCNFSM4WO4AOXA
.

Whoops. I'll update on Monday.
Ben
On Fri, 22 Jan 2021, 6:34 pm Martin from HiPi<EMAIL_ADDRESS>wrote:

In the following file, instead of referencing num_leds, the value for i
and j is fixed to 30:
https://github.com/benevpi/pico_python_ws2812b/blob/226330d7b1b140c7d462da958809714384ffb3fb/examples/flash.py#L4-L9
Thanks!
Martin
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/benevpi/pico_python_ws2812b/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHMR7ABFPUGSXHT4BXXUPPTS3HAKRANCNFSM4WO4AOXA
.

Fixed.

Fixed.


Minor improvement for cu solver/lapack

Minor improvement for cu solver/lapack:

enforced F order for cusolver
few simple tests to ensure orders are working as intended

Addresses this issue: https://github.com/deeplearning4j/nd4j/issues/1681

Build triggered. sha1 is merged.


Fix Mondo reasoning example in 'contributing to obo ontologies' tutorial

The modelling approach suggested in the tutorial here  is wrong.
Tutorial text says:

But it is not safe to add this subClassOf axiom unless all instances of farmer's lung disease are caused by 'Penicillium glabrum'.  This is well illustrated by the automated classification it gets under 'cork-handler's disease' if you follow the tutorial. This has the definition:

In this case, the disease is defined as a reaction to 'Penicillium glabrum', so the restriction is justified and the classification under 'fungal lung disease' is correct.  But classification of farmer's lung disease as a cork handler's disease is clearly not.
CC @nicolevasilevsky @matentzn  - I think we need to fix this example in the tutorial.

thanks @dosumis, I will fix this in the tutorial asap

I am just going to delete these improper instructions for now. I'll work on adding a proper example later.


Context menu bug Google Chrome

Upon selection of a track via checkbox or right click the context menu shows for a second and quickly hides itself again. thus the context options can't be clicked.  This behaviour presents itself on windows using chrome and also on android. behaves as expected in firefox.

@raymiec This is a known issue and was tied to the 'Copy URI' functionality introduced in 2.6.4. It'll be resolved in the next release (currently in dev).
Just to confirm - you're experiencing this on touch devices only?

Yeah both are touch devices, although the laptop is a hybrid (has a touch screen), i disabled the hid drivers, and rebooted, the issue still presents itself on chrome, i'll check it later on a normal laptop and report back.   For now i moved the context menu div.

		<contextmenu></contextmenu>

it now functions on chrome in android, the menu appears static on the header of the page, is this expected behaviour? would be better if it floated at the top of the screen instead of having to scroll to the top to execute actions, kinda defies the point of a context menu i.m.o.     The script itself is lovely. much appreciated.

It's weird that moving the markup changed anything (I broke it on environment).
I suspect the browser was detecting (rightly or wrongly) a scroll event, and hid the context menu. This doesn't make for a friendly UX on touch devices in any case, so I've limited it to non-touch devices.
I've just pushed this to develop branch now (commit 2707b70). Are you able to confirm that this fixes the issue?

Sorry i removed the scroll event, the js file was cached so thought it was just moving the contextmenu div.   What negative impact is removing that event likely to have?

yeah looking at your commit that's what i removed and it fixed the issue on mobile.  on the desktop browser right click is not working and neither is when you check the boxes in the list of tracks, if you resize the browser to mobile size then selection of the checkboxes work. although if you proceed to right click it totally screws it again.

This appears to be an issue with a hybrid device. I don't have such a device to test on, so it'll be tricky to accurately patch this.
It sounds like you're pretty handy with HTML + Javascript, perhaps you could have a look into this?

Just tested it on my other laptop, not hybrid, similar specs,  windows 10, latest ver of chrome. The problem still persists. I'll look into it and hopefully get a proper fix for it soon. I'm going to get in about the project over the weekend. I've not worked with Angular.js before so once i get my head round that i may be able to contribute more.
Also a bit offtopic for this thread sorry but there's a modification i would like to make to it,  a kick in the right direction would be appreciated. I want to add a separate page to the left menu, that fetches a json string of spotify tracks from another server and populates the a listview and gives me access to the same functionality the app has already, i.e right click to add to queue etc..  Like i said a kick in the right direction would be appreciated when working with angular,  if its something you wouldn't mind coding yourself as a separate addon for me i would happily send a little something to your paypal account.   Thanks

Same issue on iPhone in both Chrome and Safari.

I'm just waiting on a new micro sd card being delivered for my raspberry pi and i'll get another installation built and look into the issue properly.

This fixes the context menu issue on i devices :
app.js 30471
// still no context menu? then we have clicked outside of one, so hide 'em
if( !contextMenu.is('contextmenu') && !$rootScope.isTouchDevice()){
	$rootScope.$broadcast('spotmop:contextMenu:hide');
}

@gaiterjones confirmed fix on android/chrome too. nice one.
to tie the whole context menu thing up, we need to disable right click on touch devices and when emulated touch is active. at present when you right click on a touch device part of the context menu will appear with none of its formatting properties which also breaks the context menu check selecting a checkbox.

Awesome work guys, I've found it quite tricky as some devices seem to work fine with this functionality whilst others experience this phantom context menu issue.
I'd like to maintain the functionality where the context menu is hidden when you click anywhere outside of the context menu (expected UX). It's just a matter of working it out across all devices.
In the meantime, I've changed the Emulate Touch Device setting. It's now a radio button to allow the user to govern how their hybrid device behaves. Have a peep on the develop branch. It'd be great if you could have a quick spin on a hybrid device and let me know if this works for you.

Nice one good work, i gave it a shot, works as expected. tested on
normal windows 10 laptop, firefox & chrome,
hybrid laptop windows 8.1, firefox and chrome
Android Chrome.
i prefer the context menu being static at the bottom as well.
Couple of side notes, if you get time will you look into the bug with the android webview, not being able to authenticate spotify, the injected iframe listens for a postmessage, in the chrome browser its fine but within a webview container the value isn't passed, returns null.
also how did you get on with running mopidy on osmc ?
https://discourse.osmc.tv/t/mopidy-on-osmc-alpha-4/456/2

another couple of minor issues,  if you have a list on items in the queue, you can select multiple  as expected, navigate away from the page and go back and now it will only let you select one item at a time.
When on mobile or if i resize the browser when i try re order the queue an overlay appears from the side, this is fine on desktop but not needed on mobile, plus the formatting is a mess, half of it is clipped.

@raymiec Can you please create a new issue for the postmessage error in Android webview?
Regarding the other issues, I've patched the bug where multi-select stopped working on the Now Playing tracklist when navigating away. This was due to an orphaned $rootScope listener.
These patches will be included in the next release which will be coming out shortly.


Adding AWS login support for older versions of docker

Docker login is rather brittle across versions, specifically Docker login commands that work with CircleCI 2.0 will break with CircleCI 1.0. This attempts to fix that.

I'm trying to come up with a more central way of differentiating between docker version and all the various places that they may differ.
What if you put the docker check logic into another script docker-resolve (or something) and have it export DOCKER_EMAIL_FLAG and run that before the aws ecr login That way, we also have a place to start adding all docker version specific changes as necessary?   I think the logic block you have in place can be copied over pretty much wholesale. I think its a smart way to detect the flag's presense.
If you think thats a good idea, make sure you add docker-resolve to the shellcheck line in the circle.yml. If you think its a bad idea, let me know why.


Use correct svmhelper artifact + newer version

mavenCentral artifacts are preferable over jitpack in my opinion, because jitpack is inherently unsafe/their tags can be manipulated easily from my understanding.
Last time I forgot to release the staging release on sonatype, this time I didn't, so it should work!

Maven Central artifacts are preferable, and yes you forgot the staging release last time, but I disagree with everything else you said. :3 You are probably thinking of BinTray/JCenter, which was very unsafe. If you can "easily" manipulate JitPack tags, please release SquidSquad 4.0.0-a999 under its correct JitPack coordinates ( https://jitpack.io/#yellowstonegames/SquidSquad/v4.0.0-alpha1 has the coordinates for alpha 1), without me knowing. I'll merge this, but I do want to know why you think JitPack is "inherently unsafe."

I do want to know why you think JitPack is "inherently unsafe."

What I meant was, that the jitpack builds are not immutable. This means, you can just change a tag, delete the existing artifacts and build a new one for an already released version.
I just found out that artifacts get immutable after 7 days which I didn't knew, which makes it way better than I thought. However, in my opinion artifacts should be immediately immutable.

I believe logging into JitPack lets you click the Freeze icon (a snowflake) next to any build to make it immutable.


Event alert feature for event section (Feature Request)

Is your feature request related to a problem? Please describe.
This feature is not related to any problem.
Describe the solution you'd like
In this feature we will ask our visitors for their email addresses so whenever an event will be updated they will get an automated email alert.
benefit of this feature

Increase our community networks.

Promote beginner to get involved in events.

Would, you like to work on
Yes, I love to work on this feature with the help of experts of this community

Great feature.
I was thinking about it.
But before that would you like to see the issue #158

I'm interested in this issue, can you assign me this?

@imabp This will be a great add-on for lead generation. Go for it. 🚀


navigator is not defined

system: win10
browser: chrome version  62.0.3202.75
node: 8.1.2
npm: 5.0.3
I copyed the tree demo in my project, code followed:

and then I suffered this bug as followed:

source code as followed:

I don't know why I got the problem.

It's odd you're seeing this, since navigator is a common global -- especially in that version of chrome -- however, we could probably fix this by prefixing the var with window.
Some thing like:
window.navigator && test(window.navigator)

Pull requests welcome!

I've tried this but failed again. window is not defined...

I'm not sure how window could be undefined? https://developer.mozilla.org/en-US/docs/Web/API/Window


Make data Ingesting How To

As the workflow for ingesting data comes together, we should be writing and updating  the guide as we go. It should include relevant functions, common obstacles, and recommended workflow.

adding data tests
One PR for scripts and another for data files

it will eventually include links to template scripts.

Duplicate of #11


Fix pining

Checklist

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

@conda-forge-admin, please rerender

Solving https://github.com/stack-of-tasks/pinocchio/issues/1935


feat: support for gitlab and github and safer token storage

Updated version after commit dustinwloring1988:feat/enhanced-github-connection

Secure Git Credentials Management System
Overview
Implemented a secure credential management system for GitHub and GitLab integrations, featuring encrypted storage and seamless authentication handling.
Key Features

Secure encryption using Web Crypto API with AES-GCM
Automatic encryption key management without user intervention
Support for both GitHub and GitLab credentials
Automatic migration from legacy cookie storage
Unified interface for managing multiple Git provider credentials
Improved error handling and user feedback
Clean separation of concerns between UI and credential management

Technical Implementation

Uses AES-GCM encryption for secure credential storage
Implements automatic key generation and management
Stores encrypted credentials in cookies with proper domain isolation
Provides fallback and migration from legacy storage formats
Handles both GitHub and GitLab API authentication formats
Includes comprehensive error handling and user notifications

UI/UX Improvements

Clear feedback for authentication states
Guided user flow for credential setup
Improved error messages and notifications
GitHub or GitLab button visible on workbench when credentials are set
Streamlined repository creation process

GitHub setup form

GitLab setup form

Only show push to ... button when there are credentials set.

@D-Byte - Great work on this! I noticed you're importing useCredentials in the hooks section, but it's not being used as a hook. To improve the implementation, could you:
Wrap these functions into a custom hook
Use useEffect to initialize the master key within the hook
This way, we avoid redundant
Let me know if you'd like help with the implementation.

@thecodacus, Thanks is it maybe an idea that i put all the git stuf in a lib and also the auth stuf in a lib? So that these can scale more easy the git related things in there?

@thecodacus, Thanks is it maybe an idea that i put all the git stuf in a lib and also the auth stuf in a lib? So that these can scale more easy the git related things in there?

this makes more sense, thanks

also one thing is bugging me whats the point of encrypting if the key to decryption is also stored in browser?

@thecodacus You are right but my reasoning was some encryption is better than none. But for most cases its safer than a normal cookie. The local storage is protected by the Same-Origin Policy. For now I think this is a little better. I first wanted to have this function with GitLab and GitHub working. The encryption is some extra that need some extra attention later on, maybe some other community user has a bright idea about it.
I am now going to test if pulling and pushing to GitHub works.

@D-Byte I really like this PR however can you please run pnpm typecheck and fix the errors

@D-Byte I really like this PR however can you please run pnpm typecheck and fix the errors

I am moving some things around again to make the code more flexible so it can host other git providers without breaking.
So at the moment its a WIP

@thecodacus, @dustinwloring1988 I think its ready for testing, it only do some basic pull, push and commit (create, update)
Only in my test i sometimes not see the icons on the buttons and in the connection settings page.

looks good so far, I am not able to connect to gitlab though, even after adding api, write_repository, scopes
will test again, and if all look good will target for 0.0.5 release

looks good so far, I am not able to connect to gitlab though, even after adding api, write_repository, scopes
will test again, and if all look good will target for 0.0.5 release

You are right, there was a token not set in the gitlab request. Now its fixed and it should work as intended


Add snippets to PubSub's javadoc, PubSubSnippets class and tests

Coverage remained the same at 84.883% when pulling 5bcf665596a6185faf0d08494066c6820f5e7cc3 on mziccard:pubsub-snippets into 9c840d6b939bc856c161c74e11cc278bb555d2c0 on GoogleCloudPlatform:master.

/cc @lesv

LGTM

Coverage remained the same at 84.883% when pulling e0dbb7e7f9d70698d39cdcc4817b1188ff7669a1 on mziccard:pubsub-snippets into 9c840d6b939bc856c161c74e11cc278bb555d2c0 on GoogleCloudPlatform:master.

LGTM


Alma Adapter Refactor

This does the following:

Converts the alma adapter into an instance rather than a class.
Makes the alma adapter use the Alma client.
Re-organizes the specs to have fewer lets.
Extracts stubbing of Alma IDs to a method in test.
Extracts a class to handle converting a BibSet to a Marc-XML record set.

Coverage decreased (-0.7%) to 76.229% when pulling c2ca85da4e92c0c30bd58d86b25702c29282ae18 on refactor_alma_adapter into 24e9b0f16dd242970c25a7d9417d51ee10a7a28b on alma.


希望增加删除聊天记录功能||Want to add delete chat history function

清空全部聊天记录，可勾选多条聊天记录的删除。||To clear all chat records, you can select multiple chat records to delete.

I dont think this a good idea, if even discord not have this feature.
i dont think delete message is a normal action, can you tell me whats your reason about request this feature?

Company internal management: For chat tools used within the company, not providing the deletion function may lead to the long-term retention of some sensitive information, increasing the risk of information disclosure, and may also affect the trust and comfort among employees。
Privacy protection concerns: Users may want to delete sensitive information or private conversations in some cases to protect personal privacy. Failure to delete chat logs may make users feel uneasy and worried about personal information being leaked

But I found out that retraction already exists, so this idea is just a suggestion.

I dont think this a good idea, if even discord not have this feature.
i dont think delete message is a normal action, can you tell me whats your reason about request this feature?

for 1. you can delete it in admin platform. as manager.
for 2. user can delete his message one by one. I think its enough


is there a vinalla js alternative?

Is there a vinilla js alternative for react-infinite-scroller?

https://infinite-scroll.com/ is an alternative


Sheaf

update domain, sheaf and fiber classes:

Fiber is an elementary domain (hypercube/torus) spanningtorch.Tensor instances
Sheaf is a dictionary of domains spanning Field instances
Use Sheaf(adj) or Sheaf.sparse([N0, ... , Nd], [[i0, ..., id], [j0, ..., jd]]) to create a sheaf with keys represented by a sparse adjacency tensor adj.

Graph inherits from Sheaf, Graph[d] created by Sheaf.sparse

merge #30 into devel


jit lax.scatter_add does not improve performance in CPU

In CPU, the following script
import numpy as onp
import jax.numpy as np
from jax import jit, lax
from jax.config import config; config.update("jax_platform_name", "cpu")

@jit
def vector_to_tril_matrix(t):
    idx = np.reshape(np.arange(79 * 79), (79, 79))[onp.tril_indices(79, 0)]
    x = lax.scatter_add(np.zeros((t.shape[0], 79 * 79)), np.expand_dims(idx, axis=-1), t,
                        lax.ScatterDimensionNumbers(update_window_dims=range(t.ndim - 1),
                                                    inserted_window_dims=(t.ndim - 1,),
                                                    scatter_dims_to_operand_dims=(t.ndim - 1,)))
    return np.reshape(x, (-1, 79, 79))

%time vector_to_tril_matrix(np.ones((8000, 3160)))
%time vector_to_tril_matrix(np.ones((8000, 3160)))

returns 5.61 s and 5.28 s,
while in GPU the script returns 631 ms and 9.29 ms.
Because the difference of pre-cached and after-cached are large in GPU, I would expect the same happens for CPU but it seems not be the case.
However, testing for a smaller batch of input in CPU, we can see that jit works. For example,
%time vector_to_tril_matrix(np.ones((8, 3160)))
%time vector_to_tril_matrix(np.ones((8, 3160)))

returns 254 ms and 786 µs, which is expected.
Because the shape is decreased by 1000, I would expect the speed of vector_to_tril_matrix(np.ones((8000, 3160))) would be around 786 µs * 1000 = 786 ms (or much smaller than that if vectorization works here) but the first test shows that it is not the case.

I will note that on my desktop I seem to get a substantially faster result:
CPU times: user 1.48 s, sys: 167 ms, total: 1.65 s
Wall time: 789 ms

That said I agree those times aren't great!
My guess is that this simply says that XLA's scatter implementation on CPU is slow, and the JIT compilation time is negligible in comparison to the scatter itself. From memory it's currently a fairly naive reference implementation on CPU, whereas the implementation on GPU is more optimized. I'll file a feature request with the XLA folks.

Thanks Peter! Looking like it takes much effort for XLA devs to support various platforms because the implementations are done separately.

The implementations do share a lot of code, but GPU is often higher priority than CPU because that's what most deep learning users want.
In this case, I think no-one has ever gotten around to adding a CPU-specific lowering for scatter; it's actually expanded into a loop at the HLO level by this code:
https://github.com/tensorflow/tensorflow/blob/master/tensorflow/compiler/xla/service/scatter_expander.h
The GPU code started out the same way, but eventually someone added a better implementation that gets better GPU utilization.

Looking like it takes much effort for XLA devs to support various platforms because the implementations are done separately.

Yes, but the promise of XLA is to solve that problem once and for all and remove it as a concern for its users.
That is, systems like TF often need to implement separate CPU and GPU versions of many ops (and those systems often have O(hundreds) or O(thousands) of ops). XLA aims to solve that problem once and for all by having a relatively small number of ops (like O(dozens)) and being able to generate code for the ops and their compositions for multiple different backends. That makes it super easy to bring up a new front-end system like JAX that can immediately target CPU or GPU (or TPU!). But the XLA team still has to solve the hard problem of generating different instructions and kernels for different platforms.
So XLA devs are solving the hard multi-device problems for us (and other libraries like JAX), and moreover their task is much better scoped because they rely on a small number of ops and compositionality.

This is getting tangential, but on the subject of leveraging XLA to bring up new front-end systems easily, take a look at the XLA in Python notebook.

Yup, I can imagine that situation. That said how lucky I am to be able to use JAX seamlessly accross CPU/GPU because much of the hard job are done by JAX/XLA devs. :) Thanks a lot!

The commit mentioned above should greatly increase the speed of this computation.  I observed ~20x faster on my machine.
Note that you may still observe the fact that you get a nonlinear slowdown as you increase the computation's size.  That is, if the tensors are 10x bigger, the computation may be 100x slower, or worse.  This is a fundamental property of CPUs, caches, etc.
Thank you for reporting this bug!

Woohoo XLA!
(As usual we'll need to update jaxlib, or else users will need to rebuild jaxlib from source, to get an upgraded XLA.)

For posterity, IIUC @jlebar also pointed out this parent commit as responsible for the 20x (!!) speedup he just gave us.

Thanks @jlebar ! I am looking forward to try it soon. :)

On CPU on my Macbook, I now get:
CPU times: user 310 ms, sys: 169 ms, total: 478 ms
Wall time: 576 ms
CPU times: user 41.1 ms, sys: 4.74 ms, total: 45.8 ms
Wall time: 9.09 ms

I think we can declare this fixed! Thanks Justin!

I should add: that timing is with the newly released Jaxlib 0.1.16.


'boolean' widget without default value behaves strangely

- Do you want to request a feature or report a bug?
bug
- What is the current behavior?
A boolean field without a default defined in config.yml will initially render as false, but the field will fail the required check:

Clicking the widget twice so it turns on and back off allows me to persist a value of false.
- If the current behavior is a bug, please provide the steps to reproduce.

Define a field like this in config.yml:

-
  label: Awesome
  name: awesome
  widget: boolean

Create a new item in the collection
Try to publish the item

You'll get an "AWESOME IS REQUIRED" error.
For the record, specifying default: false for the field makes the problem disappear.
Because default presently doesn't work for editor components, this problem makes it hard to get the boolean widget working in that setting.
- What is the expected behavior?
That the error does not show and awesome: false gets persisted. Or that an error is thrown early because the field doesn't have a default specified. Alternatively that a distinct "undefined" state be added for boolean fields so that you could at least tell the difference between "off" and "undefined".

- Please mention your versions where applicable.

Netlify CMS version: 1.8.4
Browser version: 67.0.3396.62/OSX

Node.JS version: 9.5.0
Operating System: Mac OSX 10.13.4 (High Sierra)

never mind, I see where it defaults to false but it's just not persisting that value.

@erquhart if a default is not specified for the boolean widget are you cool with having it default to false?

@erquhart/ @papandreou  is this issue still valid? It's open but it looks like a fix was merged for widgets. Just looking for an issue to help out with :)

@TatisLois, I can still reproduce it with<EMAIL_ADDRESS>Which fix is that?

Same here! @papandreou https://github.com/netlify/netlify-cms/pull/1662

#1662 was never merged, that's probably why it didn't have an effect :laughing:

I opened a PR in https://github.com/netlify/netlify-cms/pull/2525. Reviews are welcome 😊

This should be resolved when #1407 is resolved. Leaving open until then.

Specifying a false default as in - {label: "Noindex", name: "no_index", widget: "boolean", default: false} does not work for me. I am still forced to click twice on the toggle to make it falsy.

@erquhart Any update on this? I'm having the same problem that @belmarca  has.

Hi @miguelt1, the best way to move this issue forward is to submit a contribution for it


UMA BUILD ISSUES

I have two issues that I am hoping someone can help with.

For some reason Build looks for UMA character save text files in a folder outside of the project. This means I have to copy files from the folder where they are auto saved in the Editor to this other folder, where the build expects to find them. This means I usually have to keep two sets of UMA files. How can I set the path to the UMA folder used in the Editor. Also why wouldn't these text files just be included in the build? Why does UMA have to find these in a folder outside of the project? Am I doing something wrong??

2.I use the above workaround from the main location where I do my game development. However, I will occasionally want to take build with me to a different office (different city). And so I usually have to be sure to copy the UMA text files and put them where I know the game expects to find them. Well, that seems to be working for the player character. But all of the other UMA characters are invisible! Apparently they are in the scene (you an even interact with the ones capable of interacting); but they are NOT being rendered! I will check folder. Not sure why this one character would load, but not the others. But, more importantly, the player character is totally naked! None of her gear is showing up that she should be wearing. When I try to equip gear, instead of displaying on the UMA, it ends up on the ground, under the character's feet!
How can I control where UMA saves my characters? How can I set UMA to save /load from the same folder used in the Editor? Also any ideas about what might be going on with my gear? That is a totally new issue that I have never seen before. But it has been a long time, since I have tried to run my game from a different computer.
Any feedback would be very appreciated!

it's simplest if you save your characters to a resource file, and then load them from resources.
As for your characters showing up naked in a build, thats usually because you have your items in the global library, and they don't have references. You should be able to open the global library window before you build, and see if that is the case.


go 1.21 is needed

The use of slices impose the use of go 1.21, currently it's 1.20:
https://github.com/mjl-/adns/blob/2dc8715bf4afd32329d53d3ac4fdc4f3b2d8ffc7/go.mod#L3

thanks for reporting, i bumped the version!
are you using some linting tool that reports this? or did you happen to have a previous go version around that couldn't compile the code?

thanks for reporting, i bumped the version!

Thanks you for your work on mox!

are you using some linting tool that reports this? or did you happen to have a previous go version around that couldn't compile the code?

Neither, I was packaging mox for Guix. To achieve that I used the command guix import go which generated Guix packages using the go version specified in go.mod. Trying to build those generated packages failed but the error message from go explicit enough to figure out it was an issue about the go version used.


NoSuchElementException - {"method":"css selector","selector":"time"}

Hey everyone, was just wondering if anyone has a fix for this problem?

Same Issue here. Have you found any solution to resolve the issue?

Same here as well

Exception has occurred: NoSuchElementException
Message: no such element: Unable to locate element: {"method":"css selector","selector":"time"}
(Session info: chrome=95.0.4638.69)
Stacktrace:
Backtrace:
Ordinal0 [0x00AC06F3+2492147]
Ordinal0 [0x00A59BD1+2071505]
Ordinal0 [0x00962478+1057912]
Ordinal0 [0x0098C964+1231204]
Ordinal0 [0x009834E1+1193185]
Ordinal0 [0x009A57FA+1333242]
Ordinal0 [0x00983466+1193062]
Ordinal0 [0x009A58AA+1333418]
Ordinal0 [0x009B4F38+1396536]
Ordinal0 [0x009A568B+1332875]
Ordinal0 [0x009821D4+1188308]
Ordinal0 [0x0098302F+1191983]
GetHandleVerifier [0x00C467A6+1545030]
GetHandleVerifier [0x00CF105C+2243580]
GetHandleVerifier [0x00B4BC97+518199]
GetHandleVerifier [0x00B4AD80+514336]
Ordinal0 [0x00A5ED2D+2092333]
Ordinal0 [0x00A62EE8+2109160]
Ordinal0 [0x00A63022+2109474]
Ordinal0 [0x00A6CB71+2149233]
BaseThreadInitThunk [0x752FFA29+25]
RtlGetAppContainerNamedObjectPath [0x77137A9E+286]
RtlGetAppContainerNamedObjectPath [0x77137A6E+238]
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 116, in scrape_date
date = review.find_element_by_tag_name(
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 302, in scrape
return fdictfield
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 322, in extract_review
res[field] = scrape(field, review, author)
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 345, in extract_from_page
data = extract_review(review)
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 492, in main
reviews_df = extract_from_page()
File "E:\GitHub\Web Scrapping\Glassgoor-Reviews-PY\main.py", line 516, in
main()

I have the same issue - any ideas anyone?


Cannot find module "pouchdb/extras/promise"

I am trying to use this plugin with pouchdb-browser and pouchdb-find. However I am getting below error.
Can you please suggest what should be done to avoid?
utils.js:3Uncaught Error: Cannot find module "pouchdb/extras/promise"     at webpackMissingModule (utils.js:3)     at Object.<anonymous> (utils.js:3)     at Object.<anonymous> (utils.js:241)     at __webpack_require__ (bootstrap 788ff5c…:555)     at fn (bootstrap 788ff5c…:86)     at Object.<anonymous> (utils.js:3)     at __webpack_require__ (bootstrap 788ff5c…:555)     at fn (bootstrap 788ff5c…:86)     at Object.<anonymous> (in-memory-filter.js:11)

PouchDB 6 has some breaking changes and I haven't upgraded this project yet. In the meantime try with PouchDB 5.

Fixed in 0.3.0


plot appearance: make further improvements

mobile view:

individual data points seem to be too large on a narrow screen -- of course this has to do with the total number of points per screen width.
the legend for the referrer/path plots takes too much space: explore max width, or better: placing the legend in the vertical dimension.

data view in general:

for forks and stargazers, extend time series until today. Otherwise the plot may be misleading, especially when the time axis is labeled so that it has little precision (did this really grow recently, or is this the same shape I saw three weeks ago)?

individual data points seem to be too large on a narrow screen -- of course this has to do with the total number of points per screen width.

Improved on that in the 1.3.0 release.

for forks and stargazers, extend time series until today.

Hm. This is actually maybe a better idea that I had there for determining the right boundary of all axes shown! (it's effectively the same as today with using the newest data point from view/clone data, but a simpler approach to achieve the same outcome, a  more explicit intent)

the legend for the referrer/path plots takes too much space: explore max width, or better: placing the legend in the vertical dimension.

Done that in the 1.3.0 release.

Closing this for now, as 'done'.


Update Chinese Translation

The layout of lblfmpegnote (at  line 164) will be wrong, and the Chinese translation has been corrected

Merged. thanks for your help


update package.json dependencies

Update dependencies in package.json to (mostly) latest available
versions.
Updating these dependencies removes warnings when bower is installed
as a devDependency in other packages and keep the code fresh.
Methodology:

npm install
npm test (all tests pass)
npm-check-updates -u
npm test (find errors, suspect semver, back off to ~2.3.0 in
package.json)
rm -rf node_modules (and .gitignored files)
npm install
npm test (all pass, deem updated version compatible)
revert to package.json from master
npm install (install the old dependencies)
switch back to updated package.json
npm install (upgrade dependencies in place)
npm test (all tests still pass, deem upgrades safe)

As to the semver dependency, it seems that updating to 4.x requires
handling breaking changes, which is TODO.
Closes #1622

There's nothing especially magical about this, I just thought that if the legwork was holding up updates, I could do that. :)

@laurelnaiad big updates, nice job!

Don't forget to release :)

I for one think this might want to cook in master for a little while. Lots of code changes underneath this....


Failed to quantify two models simultaneously

I want to train two models for encoder and decoder, so I did an experiment that trained two models and quantified them simultaneously, here is my code:
train(success)

quantize(failed)

error code:

the question is why first xmodel is CNN2 rather than CNN1? and why can't quantify two models simultaneously?

Two or more models can not be quantized simultaneously. You can do the quantization one by one.


Permissions

Would it be possible to use the modifications to only allow the bot to receive messages sent by a specific user / group? I basically would like to cancel all messages except mine and reply to them with some kind of "Action not allowed" message

You can check every incoming message and remove it if not meet your criteria:
const MY_ID = 000000;

bot.mod('message', (data) => {
  const msg = data.message;
  const userId = msg.from.id;

  if (userId !== MY_ID) {
    // Remove this message
    data.message = {};
    // Send deny message
    bot.sendMessage(userId, 'Action not allowed!');
  }

  return data;
});

Working perfectly! You might want to add this as an example ;)


Login successful but no dashboard appears

No errors on deployment.  Added app to Teams.  Able to login, but no dashboard appears.  SharePoint permissions assigned.

Here is a Fiddler trace when the Teams TEOC tab is reloaded:

Hi @kilianb-cosp,
Thanks for reaching out to us. Can you please confirm whether you are able to access the SharePoint site?
https://xxx.sharepoint.com/sites/TeamsEOCSite
I believe, you have provided the same SharePoint site name while creating the resource group which was provisioned in Step 1.

I had the same experience when I first deployed this, in my case I accidentally entered the full URL for the SharePoint site in this field (shown below), rather than just the site name.  Based on your request header, it looks like you may have done the same.  I ended up completely deleting the App Service/Plan/Etc. and redeploying it using the exact same 'base resource name' and then it worked.

I have resolved the issue.  I had assigned a baseResourceName which had a dash (-) in the name.  Updating the name, using all letters only, and re-deploying the app services in Azure, resulted in the dashboard appearing in the Teams client.  I was successful in creating a test incident.
Thank you to @sheacm for providing the insight.


Remove errors if plugin executable not available

Remove error output if plugin is enabled for npm, pyenv, rbenv but the executable is not available.
Useful for keeping the same configs synced across machines that may not have them installed.

Nice, thanks!


Allow disable/uninstall of a "soft" dependency in an Extension Pack

I created a "meta" extension pack that is simply a combination of other extensions.  https://marketplace.visualstudio.com/items?itemName=johnpapa.angular-essentials
In this case, someone may want to disable or uninstall one of these, which is not supported. I assume this is because the meta extension may actually depend on it.
I propose that extension packs have an option to designate soft dependencies, so we can create these meta extension packs and let users consume them and disable/uninstall ones they don't want.
cc @chrisdias

Duplicate of #48430


Improve Tencent.QQ <IP_ADDRESS>940 URLs

Related to [New Feature]: Replace dldir1.qq.com with dldir1v6.qq.com for Improved IPv6 Support #116525
Microsoft Reviewers: Open in CodeFlow

Why?

Installer Verification Analysis Context Information:
Installer https://dldir1v6.qq.com/qqfile/qq/PCQQ9.7.1/QQ<IP_ADDRESS>940.exe
Scan request id: '94526533-91e7-473c-8858-1aa808d8bbb7'
Error information: BlockingDetectionFound

The IPv6 host is blocking our data center, the same as in https://github.com/microsoft/winget-pkgs/pull/117018.

Please try again?

Stale PR; Please update or close
[Policy] Needs-Author-Feedback


build error: pnpm

Describe the bug

Encountered build error several times -: pnpm nx build @fluid-experimental
To Reproduce
Steps to reproduce the behavior:

Go to pnpm branch
Click on pnpm nx build @fluid-experimental
See error

Hi @anjola-adeuyi! Thanks a lot for trying out the pnpm branch and filing this issue. The pnpm branch was an exploration into alternative tools to use within the repo. We're planning work right now to update the repo tooling, and the pnpm branch has been removed.


Add timeout to Ceph GET API calls

This is to add neccessary changes in go-ceph to handle the ceph-csi issue #https://github.com/ceph/ceph-csi/issues/3657.
Provide a way to configure the timeout for the ceph Get API calls to avoid command stuck if there is some problem between the ceph cluster and the csi driver (cluster health, slow ops, or short network connectivity problem)
For more info please refer to the ceph-csi issue.

Can you be more specific about what APIs you mean? When I read "Get API calls" I think RGW (HTTP) APIs, but when I look at the linked issue it doesn't seem to be RGW specific.
The APIs that wrap C calls from Ceph do not support things like Go's contexts so the typical methods for timing out in Go do not work. There are some timeout related parameters in the ceph configuration that you could apply to a rados connection. You'd probably need to experiment with them to see what works for your use-case (if any).

Hi @phlogistonjohn, the problem that we are trying to solve is csi pod hang when there is something wrong in the ceph cluster or some network problems. In such cases pod restart is the only manual fix available at the moment. So we are trying to add timeouts to such csi calls (mainly the get calls). So if it is possible to do that directly on the RGW APIs that would be great. Or else we might need to write wrappers around the get calls to handle it. Some more context on this can be found here (a bit old though).
Thanks for your inputs on the timeout related parameters in ceph configs. Let me check whether those can be useful here.

any updates?

The main question that I have, is if it is possible to terminate a goroutine if it is executing a librados, librbd or libcephfs call. Interrupting the C-library call may not be possible, or may not be reliable depending on the call?
Experimenting with that and sharing research results would be needed to really understand if this approach gives any benefits.
@ansiwen might have ideas about interrupting CGo calls too.


ROS 2 documentation suggestions

Guides/Developing-a-ROS-2-Package.html

"Creating a package" - "in your workspace (usually ~/ros2_ws/src)". I would expect your workspace would be named after your project. For example, "nav2_ws" or "carma_ws."

Guides/Developing-a-ROS-2-Package.html

"C++ Packages" - "to create executable nodes and link dependencies." Probably helpful to also mention that it also automatically handles include dirs. This could avoid a potential misunderstanding and redundant code in CMakefiles.

index.html

Under "Where to start" and in the index on the left of the page, "Concepts" are listed after Tutorials and Guides, even though the Concepts bullet section mentions: "Concepts are high-level explanations and background information on core ROS2 concepts, which should provide some context for topics covered in the tutorials." If they are helpful for providing context for the tutorials, shouldn't they be read before the tutorials? Or, is the approach to reference them when needed?

index.html

The "Contributing" bullet section mentions, "..for contributing new ROS 2 content...". I tend to think of "content" as documentation or something other than code. However, I think that the content mentioned here also includes code. Could clarify that all contributions (code and non-code) are welcome.

index.html

The text under the "About ROS 2" section mentions, "If you're interested in the business and advancement side of the ROS 2 project,...".  Looking at the bullet items, it seems that only "Project goverance" and "Marketing materials" really only related to that topic. The other items are really more about technical details of ROS 2. I would've split the technical items out into a subsequent section.

Tutorials/Configuring-ROS2-Environment.html

"Background" - "Subsequent local workspaces are called overlays" - It seems to me that what's an "overlay" and what's an "underlay" depend on your point of view. For example, from the perspective of Nav2, everything sourced before nav2 is the "underlay" while nav2 is the "overlay."

Guides/Installation-Troubleshooting.html

'General' section (applying to all platforms) - Mentions updating your firewall configuration using ufw and sudo, which are not applicable to Windows. This needs to be restructured so that the General information is indeed general.

Concepts/About-Different-Middleware-Vendors.html

"Supported RMW implementations" - "Default middlware since Galactic." This seems to imply that Cyclone is the default middlware provider starting with Galactic. Or, will there be a selection process for each release. If so, I recommend the text be: "Default middleware for Galactic."

Concepts/About-Different-Middleware-Vendors.html

"Default RMW implementation" - "...the default RMW implementation since Galactic is selected as Cyclone DDS if it’s available." This can be made more concise. How about, "...the default RMW implementation is Cyclone DDS." The next sentence mentions what happens if it is not installed, so "if it's available" does have to also be in the first sentence.

Concepts/About-Composition.html

"Using Components" - This section could be organized as "Compile time", Launch time", and "Run time"

Concepts/About-Client-Interfaces.html

"The rclpy Package" - "by using the rcl API in the implementation it stays consistent with the other client libraries in terms of feature parity and behavior."  It helps with feature parity but is not suffient to ensure feature parity; there is much that still has to happen in rclpy itself.

Hey, I would like to work on this, I'll start working right away

That'd be great @Aut0R3V - feel free to @ me as a reviewer!

Hi, is this still open? I'd like to contribute to this.

This is still open, so feel free to contribute.  I'll suggest doing a separate pull request for each of the items, so that it is easier to review.

Hi, ls is not going to work on Win10-CMD terminal. So, could please improve this, enter ls in the workspace root (~/ros2_ws)?
Maybe dir command can be used to work on Win10-CMD terminal.

Please consider submitting a pull request to add that, we are happy to review it.

Hi, @clalancette! I am new to ROS2, and I want to know which branch of ros2_documentation I should fork?

Hi, @clalancette! I am new to ROS2, and I want to know which branch of ros2_documentation I should fork?

The rolling branch is where we do the main development for the documentation.  If you submit a pull request targeting that, we will then have the bot automatically backport it to the other branches.  Thanks!

Hi, I am new to ROS2 Contributions. I have been using ROS-2 Humble Hawksbill LTS for a month now and want to contribute back to the community. I hope this is still open for contribution?
Also, if anyone else is also working on the same, feel free to connect.

Hi, I am new to ROS2 Contributions. I have been using ROS-2 Humble Hawksbill LTS for a month now and want to contribute back to the community. I hope this is still open for contribution?
Also, if anyone else is also working on the same, feel free to connect.

Yes, please feel free to go through the open comments here and make PRs related to them.  We can review the changes in the individual PRs.


refactor(crux): refactored deprecated prisma function

Codecov Report

Merging #81 (fc8cdf9) into develop (f62a939) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head fc8cdf9 differs from pull request most recent head ec62865. Consider uploading reports for the commit ec62865 to get more accurate results

@@           Coverage Diff           @@
##           develop     #81   +/-   ##
=======================================
  Coverage     6.37%   6.37%
=======================================
  Files           62      62
  Lines         4391    4391
=======================================
  Hits           280     280
  Misses        4107    4107
  Partials         4       4

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Ability to share link to a map view

It would be nice to be able to share a direct link to a view of a specific area of the map

Do you mean something more than https://openbenches.org/bench/123 ?
I guess you mean the whole dataset but zoomed into a specific location?

Yep, the ability to zoom into a specific area of the dataset and share that view.
E.g. as a contributor I'd like to share a map of the benches I've just added. Or show benches in an area (e.g. in and around Bath)


Add support for custom stylesheet

Includes a styles/custom-styles.css in index.html (and adds it to .gitignore) so custom CSS styles can be added and not lost when updating from the repository.

ok, why not

only filename is debatable, maybe just custom.css ?