docs: revert Jade to markdown

Previously, the markdown of some chapters was converted to Jade markup to support the conditional exclusion of TS prose parts in Dart chapters.
This commit reverts some of that back to clean markdown, thanks to a few custom directives. (It also fixes a few errors due to markdown syntax being left in Jade markup.)
For example:
-p.
-  We can confirm in the #[+liveExampleLink()] that the #[i flying heroes]
-  display updates as we enter new heroes even when we mutate the
-  #[code heroes] #{_array}.
-  ... a final version of #[code #[+adjExPath('app/main.ts')]]
+:marked
+  We can confirm in the <live-example></live-example> that the _flying heroes_
+  display updates as we enter new heroes even when we mutate the `heroes` #{_array}.
+  ... a final version of app/main.ts>

So no more #[...] Jade interpolation in such cases. Notice the live-example directive which replaces the use of the Jade mixin with a similar name. The ngio-ex directive is used to qualify example path names.
Jade lists with conditional text can be difficult to read; now markdown is fine:
-ul
-  li #[a(href="#http-client") HTTP client sample overview]
-  li #[a(href="#fetch-data") Fetch data with http.get]
-  +ifDocsFor('ts')
-    li #[a(href="#rxjs") RxJS Observable of HTTP Responses]
-    li #[a(href="#enable-rxjs-operators") Enabling RxJS Operators]
-  ...
+:marked
+  - [HTTP client sample overview](#http-client)
+  - [Fetch data with http.get](#fetch-data)
+
 [RxJS Observable of HTTP Responses](#rxjs)

+
 [Enabling RxJS Operators](#enable-rxjs-operators)

+  ...

And it's much easier to do intra-paragraph conditionals now (no more  ):
-h1 Try it!
-p
-  | Try the #[+liveExampleLink2()] which loads the sample app
-  +ifDocsFor('ts')
-    |  in #[a(href="http://plnkr.co/" title="Plunker" target="_blank") plunker]
-  |  and displays the simple message:
+:marked
+  # Try it!
+
+  Try the <live-example></live-example> which loads the sample app
+
+    in plunker
+
+  and displays the simple message:

@Foxandxss @wardbell @kwalrath : ready for review. I think you'll agree that the markdown is easier on the eyes :).

Sounds good for me.

I like what I see here. I didn't review every detail; deferring to @Foxandxss on those.


Add GitHub Workflow for Continuous Integration build

:tada: This issue has been resolved in version 2.0.0-beta6 :tada:
The release is available on:

GitHub Release
NuGet Package


Re-organize to focus on (g)(10)

This consolidates such that the API Resource Guide just focuses on (g)(10) (and 404)
High level navigation looks like this:

Nav now looks like this:


The ability to use multiple goroutines per host

Feature request.
Trying to fetch in a 'browser like' way that permits 4, 6 or 8 goroutines to request content from a given domain.
ie: GET index.html, extract all the images/css/javascript urls, then get those in up to N goroutines.
Would be awesome if I could do that with this library.

Hey Shannon,
Fetchbot's design is based on robots.txt compliance, and as such, it is designed to allow a single request at a time for a given host.
If you don't have/want that constraint, it is probably enough to just launch N goroutines that send GET requests (e.g. read from a channel) regardless of host/robots.txt policies, without the need for a package such as fetchbot.
Martin


Kamikaze Pilot: Pre-process dataset with nextflow tower/nf-core/rnaseq

blocked by #77 #78

[ ] make sure to consider STAR settings mentioned in #73
[ ] update this issue description

I have had trouble getting this pipeline to run with Nextflow Tower. I'm switching my efforts elsewhere for now but wanted to give some information here if someone else wants to take this up (like @uniqueg).
The input samplesheet for nf-core RNA-seq is on our bucket at: s3://rnasoc-scratch-us-east-1/nfcore_samplesheets/samplesheet_mayr.csv. A ONE SAMPLE csv is also at s3://rnasoc-scratch-us-east-1/nfcore_samplesheets/samplesheet_mayr0.csv if you want to start there as well.
Genome could be set to GRCh38 in which case the pipeline uses the UCSC annotation from iGenome. We were talking about using the Ensembl based genome / annotation which could be fed in as separate parameters. At minimum this requires a fasta and gtf file and the pipeline can figure out the other information.
These files are also on our bucket as s3://rnasoc-scratch-us-east-1/genome_resources/Homo_sapiens.GRCh38.dna.primary_assembly.fa.gz for the fasta and s3://rnasoc-scratch-us-east-1/genome_resources/genome_resources/Homo_sapiens.GRCh38.94.gtf.gz for the gtf. Direct links to the FTP is also possible.
Using the --save_reference parameter if the Ensembl annotation will be built as this can be used in the future.

Run completed. Did not include the STAR setting, but shouldn't matter for stranded data (and all data are stranded)


Update Dependencies

I have update some of the dependencies

Can you resolve the conflicts?  Otherwise, LGTM.


Packaging requests: kdenlive

Project description
Kdenlive is a free and open source video editing app.
Metadata

homepage URL: https://kdenlive.org/
source URL:
license: gpl-2.0
platforms:  linux, windows, darwin

I believe kdenlive is already packaged however I am not sure if its also packaged for windows and darwin.
Query: https://search.nixos.org/packages?channel=21.05&from=0&size=50&sort=relevance&query=kdenlive


Provide better error message when field attribute is incorrect

I got this error message:
error: custom attribute panicked
  --> ubiart_toolkit/src/cooked/isg/mod.rs:18:1
   |
18 | #[superstruct(variants(V22, V21, V20, V20C, V19, V18, V17, V16))]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: message: called `Result::unwrap()` on an `Err` value: Error { kind: UnknownField(ErrorUnknownField { name: "V19", did_you_mean: None }), locations: [], span: Some(#0 bytes(619472..619475)) }

which was because I had a field attribute [superstruct(V19)] instead of [superstruct(only(V19))]. It would be nice of the error message detected that the field name is also an attribute and suggests only and any other relevant attributes.
If it could also give the line number that would be even better.

Sorry yeah the error messages in superstruct have not received any polish, so there are a lot of cases like this where we will just crash.
If I find some time I'll try threading the errors and spans around to see if that improves things. It should!


fix(contrib/gce): updated GCE docs with new cloud dns config and commas

Resolves:
WARNING: Lists should be separated by commas, try "--metadata-from-file user-data=gce-user-data,sshKeys=/Users/Thijs/.ssh/deis.pub". If you intend to use sshKeys=/Users/Thijs/.ssh/deis.pub for positional arguments, put them before the flag.
WARNING: Lists should be separated by commas, try "--disk name=cored3,device-name=coredocker". If you intend to use device-name=coredocker for positional arguments, put them before the flag.

Thanks for the contribution! Please ensure your commits follow our style guide. This code will be tested once a Deis maintainer reviews it.

Code LGTM. Thanks for finding and fixing this @tscheepers!

Hi @mboersma, I've updated the commit message, added a couple more commas and I added new Google Cloud DNS config as well. With these changes the docs are up to date again.

Code LGTM.

I'll test this manually today now that I sorted out my GCE billing account. :money_with_wings:

Code LGTM.


Test nextword

Just to highlight changes

Nice work, big steps taken in that direction of passing on a list of tokens. 👍
I was thinking when looking at it that maybe it makes sense to as well keep the existing setup with training from a file next to the list of tokens and that we internally use the list of tokens model learning if the list of tokens has a length > 0.
In that way I can smoothly switch existing flows I have between the new representations and we could compare the 2 to be 100% sure the result is the same.

@jwijffels I made too many unnecessary commits on this branch, so working in the dev-texts branch afresh. I will try to minimize changes.

Thanks for keeping the old arguments.
Interface looks good already.


Organizations can only get Avatars from Gravatar

This means that when Gravatar is disabled, organizations can't have avatars.

I whould love, if that issue gets fixed as soon as possible :+1:

I've found a little dirty workaround:

Login into your server over SSH
Goto your gogs installation path
Goto data/avatars
Rename the avatar for YOUR useraccount to preserve a backup (the file should be named like your gogs user id)
Upload the organization image into YOUR useraccount over the gogs web interface
Rename the new file (with your user id) into the user id of your organization
Rename the backup back to your userid to get back your personal image
Set the "use_custom_avatar" value in the table "user" in the gogs database from 0 to 1
Enjoy your new gravatar-free organization image :+1:

+1

OK, now on develop and https://try.gogs.io , you can upload avatar for organizations.

Close as implemented.


[REQUEST] Add Steam linking.

For example: wish list, friends, achievements, recommendations.

Hydra focus on anonymity. So we won't add friends list.
About achievements, it's an on going development
About recommendations, could you elaborate more what you mean? It's too vague


Tons of warnings

Webpack output and chrome console generates such warnings
 ./~/ngx-fullpage/ngx-fullpage.js
Cannot find source file '../sources/ngx-fullpage.ts': Error: Can't resolve '../sources/ngx-fullpage.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage'
 @ ./src/app/app.module.ts 14:0-48
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/index.js
Cannot find source file '../../sources/components/index.ts': Error: Can't resolve '../../sources/components/index.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components'
 @ ./~/ngx-fullpage/ngx-fullpage.js 10:9-38
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/index.js
Cannot find source file '../../../sources/components/fullpage/index.ts': Error: Can't resolve '../../../sources/components/fullpage/index.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/index.js 6:14-41 7:14-41
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.module.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.module.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.module.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 6:26-56
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.directive.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.directive.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.directive.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 8:29-62
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage-options.class.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage-options.class.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage-options.class.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 10:33-70
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

 ./~/ngx-fullpage/components/fullpage/mnFullpage.service.js
Cannot find source file '../../../sources/components/fullpage/mnFullpage.service.ts': Error: Can't resolve '../../../sources/components/fullpage/mnFullpage.service.ts' in 'C:\Users\Alex\WebstormProjects\aimol\application\node_modules\ngx-fullpage\components\fullpage'
 @ ./~/ngx-fullpage/components/fullpage/index.js 12:27-58
 @ ./~/ngx-fullpage/components/index.js
 @ ./~/ngx-fullpage/ngx-fullpage.js
 @ ./src/app/app.module.ts
 @ ./src/main.ts
 @ multi (webpack)-dev-server/client?http://localhost:8080 ./src/main.ts

@alQlagin are you sure you've excluded the node modules folder in your typescript loader

Outdated


Additional or Quality Metadata for Google Scholar (aka, The Scholar)

We need to rework the metadata per the recommendations from Google in regards to scholarly literature.

https://scholar.google.com/intl/en/scholar/inclusion.html#indexing
Place each article and each abstract in a separate HTML or PDF file
Use Dublin Core tags (e.g., DC.title) as a last resort
Only scholarly papers are appropriate for inclusion in Google Scholar; each paper needs to be listed on a separate URL; and at least the full author-written abstract must be clearly visible on the URL that you wish to be included in Google Scholar search results.

Example Work that we would want to be indexed
https://scholarsphere.psu.edu/concern/generic_works/xwd375x69k
Datasets should be found in Google Dataset Search.
https://developers.google.com/search/docs/data-types/dataset

There are a couple of things that would be very helpful for indexing if possible:

Adding the publication date to the citation_publication_date tags, so they aren't blank, e.g.
A common repository indexing error is using the upload/online date; only the formal publication date should be entered in this field.
Adding only the title of the item, and not the file name, to the citation_title, e.g.
view-source:https://scholarsphere.psu.edu/files/rf55z7756

looks great.

A file with .csv at the end, which would be a red flag for the indexing system. It would not be considered a publication
It's better not to add empty metatags. If you don't have the publication date of an item, for example, it's best not to include the citation_publication_date tag.
Additionally, the journal specific information like vol/issue and page numbers can be left off for repository items. The really crucial items for ScholarSphere would be:

citation_title
citation_author
citation_publication_date
citation_pdf_url

Placeholder for questions to help solve the indexing issues

Does each article require the abstract to be in a separate HTML or PDF file?

Place each article and each abstract in a separate HTML or PDF file

What file formats are excepted? Seems like preservation formats are not the required file formats?

Google Scholar view Partial
https://github.com/psu-stewardship/scholarsphere/blob/2735de0c3994d2f0e32ac2ef5f5219af528f83d8/app/views/shared/_gscholar.html.erb

Perhaps we should require the publication date if a work has the resource type of article, book, journal, part of book, research paper? This would require a change to the new/edit work form to pull the publication date out of the additional metadata. Or we could remove the citation_publication_date from the meta for Google Scholar if it is blank. Might be better to get a date.

We will also need to redo Batch Create because the process uses the filenames as the title of the work.


Remove or flesh out test file

Having an empty/auto-generated test file gives false assurances of testedness.

Test file is no longer empty.


Strategy to update the zfs service to use openzfs

I have a fork of os-services with zfs updated to both 0.8.6 and 2.0.1.
How do we want to handle this?
ZFSonLinux has rebranded to OpenZFS with version 2.0.0.
I could do a PR with the zfs services bumped to 0.8.6 and include a new service openzfs which will be using version 2.0.1.
Or I could do a PR where I just bump the zfs service to version 2.0.1 directly.
From what I can tell, OpenZFS (2.0.1) can import older pools and you need to manually enable any new features that a later version bings (just as it's always been) so I guess we won't be breaking anyones zfs setup by bumping the zfs service to 2.0.1 directly.
Thoughts?

I'm not familiar with zfs at all but based what you are saying it sounds that it is simplest just bump version to latest and test upgrade scenario.
We anyway have now v1.9.1-rc1 testing on going so I think that it simplest if you can create PR against of v1.9.1-rc1 branch on os-services so it can be used to test upgrade scenario.
Upgrade command to RC version is (image must be defined because it is not marked as latest):
sudo ros os upgrade -i burmilla/os:v1.9.1-rc1

I'm not familiar with zfs at all but based what you are saying it sounds that it is simplest just bump version to latest and test upgrade scenario.
We anyway have now v1.9.1-rc1 testing on going so I think that it simplest if you can create PR against of v1.9.1-rc1 branch on os-services so it can be used to test upgrade scenario.
Upgrade command to RC version is (image must be defined because it is not marked as latest):
sudo ros os upgrade -i burmilla/os:v1.9.1-rc1

PR sumitted. https://github.com/burmilla/os-services/pull/13

PR sumitted. https://github.com/burmilla/os-services/pull/13

Build https://github.com/burmilla/os-services/runs/1724229423 passed so now updated version should be available on v1.9.1-rc1 (it might need sudo ros service list --update before visible).

Build https://github.com/burmilla/os-services/runs/1724229423 passed so now updated version should be available on v1.9.1-rc1 (it might need sudo ros service list --update before visible).

I actually had to manually update the config rancher.repositories.core.url to https://raw.githubusercontent.com/burmilla/os-services/v1.9.1-rc1 as that wasn't updated after running sudo ros os upgrade -i burmilla/os:v1.9.1-rc1.
Otherwise a service list --update or a service pull zfs still pulled 0.7.13-1 of zfs.

I actually had to manually update the config rancher.repositories.core.url to https://raw.githubusercontent.com/burmilla/os-services/v1.9.1-rc1 as that wasn't updated after running sudo ros os upgrade -i burmilla/os:v1.9.1-rc1.
Otherwise a service list --update or a service pull zfs still pulled 0.7.13-1 of zfs.

Hmm. So I assume that if you run sudo system-docker ps  it show that console is still on earlier version?
.
That is kind of feature that we do not reset console changes automatically but probably we should then force new value to rancher.repositories.core.url

Hmm. So I assume that if you run sudo system-docker ps  it show that console is still on earlier version?
.
That is kind of feature that we do not reset console changes automatically but probably we should then force new value to rancher.repositories.core.url

Yeah that's correct. It's still on 1.9.0 for the console and I guess that's why the repositories url hasn't been updated?

Yeah that's correct. It's still on 1.9.0 for the console and I guess that's why the repositories url hasn't been updated?

The URL must be https://raw.githubusercontent.com/burmilla/releases/v1.9.x/releases.yml
Then run sudo ros os upgrade -i burmilla/os:v1.9.1-rc1 to upgrade

The URL must be https://raw.githubusercontent.com/burmilla/releases/v1.9.x/releases.yml
Then run sudo ros os upgrade -i burmilla/os:v1.9.1-rc1 to upgrade

@tomaswarynyca That's the upgrade url and not the repository url. The upgrade went fine. It was just that the repositories core url wasn't updated to 1.9.1-rc1 and because of that I wasn't able to pull the latest zfs service.

@tomaswarynyca That's the upgrade url and not the repository url. The upgrade went fine. It was just that the repositories core url wasn't updated to 1.9.1-rc1 and because of that I wasn't able to pull the latest zfs service.

Yeah this is good example of the reasons why I wanted to drop all other consoles as on RancherOS there was too many options so all them are not correctly tested.
On RancherOS default console was non-persistent but most probably this issue have been on all alternative consoles for years.

Yeah this is good example of the reasons why I wanted to drop all other consoles as on RancherOS there was too many options so all them are not correctly tested.
On RancherOS default console was non-persistent but most probably this issue have been on all alternative consoles for years.

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

@tomaswarynyca That's the upgrade url and not the repositories core url. The upgrade went fine. It was just that the repositories core url wasn't updated to 1.9.1-rc1 and because of that I wasn't able to pull the latest zfs service.

Uhh I'm asleep sorry, I read anything heh

@tomaswarynyca That's the upgrade url and not the repositories core url. The upgrade went fine. It was just that the repositories core url wasn't updated to 1.9.1-rc1 and because of that I wasn't able to pull the latest zfs service.

Uhh I'm asleep sorry, I read anything heh

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

It seems like a good idea to me, just yesterday I updated my server and noticed that the installed things were deleted

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

It seems like a good idea to me, just yesterday I updated my server and noticed that the installed things were deleted

Maybe let's have the console discussion in a new issue. I'm running zfs 2.0.1 on v1.9.1-rc1 now so this could be closed i guess.

Maybe let's have the console discussion in a new issue. I'm running zfs 2.0.1 on v1.9.1-rc1 now so this could be closed i guess.

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

Reopened https://github.com/burmilla/os/issues/48 for that discussion.
Anyway, did the ZFS works correctly after upgrade or are still doing more testing?

Could we find a way of only persisting some paths of the console so that the home folder and some apt related stuff are saved to have the console always be the latest but have it automatically reinstall apt packages and keep home dir stuff?

Reopened https://github.com/burmilla/os/issues/48 for that discussion.
Anyway, did the ZFS works correctly after upgrade or are still doing more testing?

Yeap, so far it seems to work. Will write an update if things crash.

Yeap, so far it seems to work. Will write an update if things crash.


Dependency package universal-user-agent has a new version available

We have identified a dependency on version 6.0.0 of universal-user-agent. A new version (7.0.1) is available for upgrade.
Following are the steps to upgrade package dependency.

Understand the breaking changes between the version being used and the version you want to upgrade to.

Identify all packages that take a dependency on this package.

Go to the root folder for each such package (/sdk/service-name/package-name) and update package.json to have the new version.

Run rush update to ensure the new version is pulled in.

Make relevant changes to absorb the breaking changes.

Repeat steps 3 to 5 for each of the packages that have a dependency on this package.

[ ] sdk/cosmosdb/cosmos/package.json:103:    "universal-user-agent": "^6.0.0",

v7 changes:

7.0.0 (2021-09-16)

Features

ES Module (https://github.com/gr2m/universal-user-agent/issues/72) (31029b5)

BREAKING CHANGES

This package is now pure ESM
Node 12+ required


Remove vestigal cache.OperatorSet type.

Nothing of consequence has used OperatorSet in ages, but it's been
lingering in tests and as the result type of the main resolution
method.

I don't think it's worth the extra PR churn, especially since there aren't any Go API stability guarantees for this package.


Is there a .SVG file template to create and import custom font icons?

I am using a square template for creating custom font icons in Inkscape, however but the generated icons from fontello are always slightly right adjusted.
So is there a clean template of 1000x1000px SVG good for Inkscape?

Ok. Just found there are clean svgs inside the source folder. Opening them in inkscape, edit and save solves my issue. However Inkscape does add it's meta tags. There's warning from fontello, but result is fine.


Support for JSXSpreadChild

Flow does not yet parse JSXSpreadChild, which was added to JSX a while ago. It's also in babylon but not yet esprima or acorn.
<Foo>{...children}</Foo>

cc @calebmer

Yeah, lol, I wrote the PR to get this added to the spec 😊. Is there somewhere you would like to use this? This syntax is banned in React which is why we’ve been slow to support it.

Banned in React?
I was hoping to use it in a compile-to-js lang I'm working on, LightScript, which would use the syntax for "jsx comprehensions" (eg; [...for x of arr: [x * 2]] is valid LightScript, and I would like {...for x of arr: <X x={x} />} to be valid as well).
In other words, I have no pressing need for this 😄

Seems like this was introduced in 0.60
This probably can be closed.
/cc @vkurchatkin


Custom View Items

The main goal when I started to change PickerView control was to implement custom view items for a project. I ended up implementing a lot more than that.
I don't know whether you'll agree with all the changes that I did but I'm sending this pull request because I really like the result.
Summary of what I've done:

Added support for custom view items
Added compatibility with Objective-C
Added optional for function delegates that aren't mandatory
For every function delegate that has row parameter added an index parameter. This parameter is pretty handy when dealing with an infinite PickerView. row is the indexPath.row from the internal tableView while index is the index considering indexPath.row % items.count
Added a new function delegate to know when a row was tapped: pickerView(PickerView, didTapRow row: Int, index: Int)
Changed the name of some function delegates to conform with Apple's UIPickerViewDelegate. The names of function delegates were working fine but I prefer to work with their names as close as Apple's.

I know, there's a lot of changes. I should have separated each implementation but I changed the control directly while I was developing the project that I mentioned before. Sorry for that.
I added the custom view option in the Example project for better reference and testing.
Resolves #4

Hello @felipowsky. First of all: Thank you so much for contributing!
I really appreciated your contributions.
I've related this pull request to issue #4 which is where the custom view as an item was requested and I will return tomorrow to finish the review.
tks

No problem.
Let me know what you think and I can help with any changes.
I just noticed I didn't select the correct branch.
If you want we can discuss the changes here and I create a new pull request with a separate branch for merging.

I reviewed it yesterday, but I didn't had time to bring some "philosophical" questions that I would like to discuss with you, sorry about that.
Now I'm heading to your lands (SC), I will stay in Camboriu until January 4, so I think we can close this pull request and discuss the changes in the new one, but if you want to discuss here no problem.
What do you prefer?
Sorry about the delay, my intention was to had it merged before the year ends but this year ending is crazily busy for me :(

Hello! I'm back, happy 2016 bro!
So, I think the only doubt I had was:
We have ScrollingStyle and SelectionStyle to clearly determine how PickerView style will behave.
What do you think about implement the ItemsType enum as nested type (and a property) of PickerView such as the other  enums which determine style behavior?
I got that you determine if it will be a label or a custom view verifying which delegate method the developer has implemented, but it looks a little “abstract”. If we had it as a property of PickerView we could set a value as default (probably .Label) and use it to verify what kind of behavior the developer wants with this property instead of verifying which delegate methods the developer has implemented. See the following lines:
let view = delegate?.pickerView?(self, viewForRow: indexPath.row, index: indexForRow(indexPath.row), highlited: indexPath.row == indexOfSelectedRow, reusingView: pickerViewCell.customView)

if (view != nil) {
    // Implement customView
} else {
    // Implement label
}

Would be something like that:
switch itemsType {
case .Label:
   // Implement label
case .CustomView:
   // Implement custom view
}

In that way the behavior looks more clearly to me, but I really want to hear what do you think about it.

Happy 2016! :)
Hum, I see. It's ok for me.
I think this is more like a personal choice.
My implementation was based on Apple's UIPickerView which considers whether custom view delegate is implemented or not.
Actually, Apple's UIPickerView implementation is more strict because once the custom view delegate is implemented the control ignores the default label completely even if the custom view delegate returns nil.
My intention was to give the developer the impression of using Apple's UIPickverView control and also the possibility to mix custom view and default labels. Honestly I don't know if they want that and I haven't tested the "mixing" feature to see if it really works.
Well, I'm fine if you want to change it.

Sorry about the delay.
I got your point, but I will make the changes to make sense with the other features.
You said before that you would create a new pull request. Should I wait for it to make the changes?
tks

Great.
I've created a new branch with my changes.
New pull request: https://github.com/filipealva/PickerView/pull/6


Separate market making P&L and inventory P&L

Feature Suggestion
Separate trading/market making P&L and inventory P&L. Maybe trading P&L is positive but inventory P&L for assets held to implement strategy is negative. Negative inventory P&L is not very relevant for long term holders of inventory assets and is hopefully temporary. In this case would be nice to see how positive trading P&L is compensating for negative inventory P&L or increasing positive inventory P&L for long term holder.
Trading P&L is also realized P&L and inventory P&L is unrealized P&L.
In the Hold Portfolio stats, comparison to a 100% base asset hold position would also be useful. For example: 100% ETH hold portfolio value / initial % ETH - initial % USDT hold portfolio value / Current portfolio value. This would answer the question: How much better/worse is market making for an asset versus just holding the asset or the initial combination of assets needed for market making?
Impact
More detailed/extensive evaluation of the strategy's performance and relevant opportunity costs.
┆Issue is synchronized with this Clickup task by Unito

@cardosofede External excel calculator?

@dracpet if you want, create a proposal in the discord group with the information that you want with the formulas needed and if the community is aligned we can implement that feature


feat: render HTML within UI

Is your feature request related to a problem? Please describe.
I was working on an integration for entity linking and wanted to get nicely rendered HTML in the UI.
Describe the solution you'd like
I would like to see HTML formatted in both cases.
Describe alternatives you've considered
I´ve considered not using HTML.
Additional context

We've allowed custom, arbitrary HTML rendering inside record cards in previous versions (before OSS launch) and it can get really problematic. We will tackle this need in a controlled manner when we build #1837


renderer: rewrite the GLSL extension enablement

trust GLimp_InitExtensions and deduplicate the code
unify the way to tell an extension is available

Should all of the changed #ifdefs follow one convention with regards to #ifdef vs #if defined?

Should all of the changed #ifdefs follow one convention with regards to #ifdef vs #if defined?

Right, now unified.


Security issue: Please update yargs to 16.1.1 to fix CVE in y18n

Protractor Version 7.0.0
Security issue:
CVE in y18n
Thank you!

Is there an ETA on when yargs will be updated.  There is a critical vulnerability on one of its dependancies<EMAIL_ADDRESS>

Update to 4.0.1 => This affects the package y18n before 3.2.2, 4.0.1 and 5.0.5
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7608


Runtime error caused by slf4j dependency conflict

hector-core-1.0-1 from maven introduces a dependency conflict which prevents the application from launching in systems using log4j.
Caused by: java.lang.NoSuchMethodError:  org.slf4j.helpers.MessageFormatter.format(Ljava/lang/String;Ljava/lang/Object;Ljava/lang/Object;)Ljava/lang/String;
at org.slf4j.impl.Log4jLoggerAdapter.info(Log4jLoggerAdapter.java:341)
at me.prettyprint.cassandra.connection.CassandraHostRetryService.<init>(CassandraHostRetryService.java:37)
at me.prettyprint.cassandra.connection.HConnectionManager.<init>(HConnectionManager.java:61)
at me.prettyprint.cassandra.service.AbstractCluster.<init>(AbstractCluster.java:69)
at me.prettyprint.cassandra.service.AbstractCluster.<init>(AbstractCluster.java:65)
at me.prettyprint.cassandra.service.ThriftCluster.<init>(ThriftCluster.java:17)
at me.prettyprint.hector.api.factory.HFactory.createCluster(HFactory.java:176)
at me.prettyprint.hector.api.factory.HFactory.getOrCreateCluster(HFactory.java:155)
at me.prettyprint.hector.api.factory.HFactory.getOrCreateCluster(HFactory.java:128)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:145)
... 43 more

I believe this is caused by the different versions of SLF4j introduced by the dependency tree:
[INFO] +- me.prettyprint:hector-core:jar:1.0-1:compile
[INFO] |  +- org.apache.thrift:libthrift:jar:0.6.1:compile
[INFO] |  |  \- org.slf4j:slf4j-log4j12:jar:1.5.8:compile
[INFO] |  +- org.slf4j:slf4j-api:jar:1.6.1:compile

Adding the following to my pom.xml fixed the issue:
    <dependency>
        <groupId>org.slf4j</groupId>
        <artifactId>slf4j-log4j12</artifactId>
        <version>1.6.1</version>
        <scope>compile</scope>
    </dependency>

Closing, just looked at the FAQ and realized this is more a libthrift issue. Having hector force an exclusion is probably hack.

For the record, libthrift 0.7 has the proper scope for the dependency. Probably worth opening a ticket to upgrade to libthrift 0.7

thanks for posting the update on this either way - yeah, any library pulling in an slf4j implementation is kind of ghetto.


[libudis86] Fix build error

Fixes #22589
Fix libudis86 build error on MACOS and Linux and UWP.
No features need test.

LGTM thanks!


Needs to delete Phantom Wallet so I can use the app

Describe the bug
I was using the library in the application we are developing for integrating with as many wallets as possible. Did not have this problem before, but appeared now out of nowhere.
To Reproduce
Steps to reproduce the behavior:
Now when I start the application the first error is saying to uninstall Phantom wallet. After doing it, the error disappears.

Expected behavior
I was expecting it not to tell me to delete Phantom wallet and let me use the app as before.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser chrome
Version 106.0.5249.119

This is not a bug with Wallet Adapter. Do you have more than one wallet extension installed?

Closing since there's been no activity. This error you're seeing is typically because you have multiple wallets installed. For example, Glow and Phantom conflict over the same window properties.

Yes, it was because of the multiple wallets installed.
The problem stopping it from working was related to something else.
Even though the error persisted with multiple wallets, it did not stop it from working.


Disambiguation of bibtex keys

Hi,
thanks a lot for better bibtex, which makes zotero useful ;-). I have a small little feature request rather than an error: I have a slight (psychological) problem with the bibtex keys generated by better bibtex, in the sense that the disambiguation results in somewhat illogical bibtex keys. What I mean is that I have set my key format to
This results in keys
smith:2011
smith:2011a
smith:2011b
etc. Is there a way to start with the character appended to the year already for the first paper of an author for that year? I.e. I would like the above sequence to be
smith:2011a
smith:2011b
smith:2011c
This would be more logical to me, since I read the labels in my publications to mean that smith:2011a is the first publication by that person in the year, smith:2011b the second, etc. (the current approach confuses the hell out of me for my own publications and the ones I cite often, since I know the sequence in which they were submitted).
Thanks a lot again for this great piece of software!

It's not impossible in principle, but consider this scenario:

you add a paper by Smith from 2011 (gets key smith:2011), and by Jones from the same year (gets key jones:2011). You cite both
you add a new paper by Smith from the same year. This gets smith2011a

If at step 1. I would have given them citekeys smith:2011a and jones:2011a that looks weird (and ugly, if you ask me). There's nothing to disambiguate, so why add the postfix?
If I'd do business as usual in step 1, but in step 2 change smith:2011 to smith:2011a before handing out smith:2011b, you have a broken reference in one of your papers. It could even be a different paper.
One of the major premises of BBT is that keys are dependable, so 2. is not an option. But to implement 1., keys would always get a postfix, even where not required. If that's what you actually want (always), I can think about how that would be achieved without disrupting the existing key generation, but it won't be the default.

Hi,
thanks for the fast reply. Yes, I always want the postfix added. I know that at first this sounds weird, but  the reason is that I would estimate that 95% of all of my bibkeys need to be disambiguated - I'm talking about a database with about 3000 entries here and in my field it is fairly typical that people have more than one first author publication per year. This means that in the end almost all bibkeys end up having a postfix. So it makes more sense to always have a postfix rather than having one random article per year for each author not to have a postfix.
I guess I am biased by the citation culture in my field where you would cite two papers of the same author which were published in the same year as Smith et al. (2011a) and Smith et al. (2011b), rather than Smith et al. (2011) and Smith et al. (2011a).

That is fairly common I think, but not that you'd also get Jones (2011a) absent any other papers from Jones.
In any case, you can give https://s3.eu-central-1.amazonaws.com/zotplus-builds/zotero-better-bibtex-1.6.34-travis-2427.xpi a spin if you want. After installation, you will have to go into about:config, set citekeyAlwaysPostfix to true, and restart Firefox. OSX is particularly stubborn about keeping apps running even when you've closed the last window. This setting is only read out on startup for performance reasons (the key generation gets called often) so any time you change it you will have to restart.

(btw, if you are looking for consistency between citation key and citation, if you cite only smith:2001a and smith:2001c, you're going to get Smith (2001a) and Smith (2001b) in your paper -- no way around that)

(or even: if you cite only smith:2001c and smith:2001d, you're going to get Smith (2001a) and Smith (2001b) in your paper)

I can merge if this does what you want.

assuming fixed to satisfaction

Coming back to this issue. I also encountered this problem, but rather because of not liking the BBT format, it is because I just migrated from BibDesk, where the format of my keys was Author:Yearaa, always with two postfixes, e.g.: Smith:1990aa, Smith:1993aa, Smith:1993ab, etc.
Is there a way to force this format in BBT in order not to change all my .tex files?
Thanks!

Jeez, how many papers by that one author do you cite? 😆
Can you join #1554?


Display the day and player count in the channel's topic

Closing out feature requests to keep this tracker to bugs-only. This does not mean that this feature is a "won't-add". Further discussion is being moved to the Discord.


Automatically stringify st2.datastore_crypto_key and st2chatop.env values

datastore_crypto_key and st2chatops secrets are both likely to have non-string content.
Examples:

Using YAML or plain JSON formatting for datastore_crypto_key in values instead of a JSON-encoded string wrapped in single quotes.
Using an integer for one of the chatops env vars (like ST2_COMMANDS_RELOAD_INTERVAL: 10 instead of ST2_COMMANDS_RELOAD_INTERVAL: "10")

We can easily cast these to string in the secret templates to fix this.
Resolves #229

@armab I would like to include this one in the next release as well.


Daniel strobl hvg conservation fix

Submission type

[ ] This submission adds a new dataset
[ ] This submission adds a new method
[ ] This submission adds a new metric
[ ] This submission adds a new task
[ ] This submission adds a new Docker image
[ ] This submission fixes a bug (link to related issue: )
[ ] This submission adds a new feature not listed above

Testing

[ ] This submission was written on a forked copy of openproblems
[ ] Nextflow test pipeline is passing on this base branch of this pull
request (include link to passed test on NF Tower found in GitHub Actions summary: )
[ ] If this pull request is not ready for review (including passing the Nextflow test
pipeline), I will open this PR as a draft (click on the down arrow next to the
"Create Pull Request" button)

Submission guidelines

[ ] This submission follows the guidelines in our
Contributing document
[ ] I have checked to ensure there aren't other open Pull Requests for the
same update/change

PR review checklist
This PR will be evaluated on the basis of the following checks:

[ ] The task addresses a valid open problem in single-cell analysis
[ ] The latest version of master is merged and tested
[ ] The methods/metrics are imported to __init__.py and were tested in the pipeline
[ ] Method and metric decorators are annotated with paper title, year, author, code
version, and date
[ ] The README gives an outline of the methods, metrics and datasets in the folder
[ ] The README provides a satisfactory task explanation (for new tasks)
[ ] The sample test data is appropriate to test implementation of all methods and
metrics (for new tasks)

@danielStrobl unfortunately this is not passing tests. Converting back to draft https://github.com/danielStrobl/SingleCellOpenProblems/actions/runs/4045129806/jobs/6956657087

Tests passing at https://tower.nf/orgs/openproblems-bio/workspaces/openproblems-bio/watch/Nl0pbqDX86QsF

We definitely need to add something to the API describing this, otherwise method developers are not aware that there is a bias in the metric. If they use a different flavour of HVG they are punished.

@LuckyMD pending your re-review.

This is just the metric still. Wasn't the PR meant to include the api.py changes as well?

I don't see how this has changed since my last review...

@LuckyMD added to api now

this only calculates them again in the metric if it's not present in adata.uns.

Passing tests locally. Gotta get this moving so I'm going to merge.


[RN]Tried to register two views with the same name RNCWebView

Reported by Decrypt

So the issue I'm having with implementing @magic-sdk/react-native is that the SDK and our app both have react-native-webview as a dependency. Even when I match the version numbers (8.1.2 for RNWebView) I run into the following issue...

Invariant Violation: Tried to register two views with the same name RNCWebView

If I manually go into node_modules/@magic-sdk/react-native/node_modules/ and delete the react-native-webview dependency folder I am able to resolve the issue. Magic works and seems to use the top level RNWebView dependency.

The error is caused by having two identical classes with identical names imported to the app and it’s thrown by the IOS builder.
Will fix it by putting React-native-webview as a peer dependency with a restricted range of versions

"@magic-sdk/react-native": "2.0.0" is released. Closing now


problem of exported metrics

Hi!
There are some metrics in http://vernemq.com/docs/monitoring/ does not received message, such as "/clients/total", "/cluster/bytes/sent/last_5min/value".
There are some metrics publish wrong value, such as "/cluster/bytes/received/last_5min/value"(alwarys 0).

@dcy, the metrics system got a complete rewrite in upcoming 0.13.1. We won't fix this for 0.12.5.


feat: Allow random order of globs

BREAKING CHANGE: This changes the behavior of all config options with arrays of globs to not respect the order similar to how it was in jest 24 and lower.
Fixes #9464 (one or the other way)
Summary
Some history: micromatch 3 (jest 24 and lower) allowed random order of globs (like ['!foo.js', 'foo.js'] would ignore foo.js), whereas micromatch 4 changed this and respects the order (['!foo.js', 'foo.js'] would match foo.js because the second glob runs after the first)
Also negations work slightly different, for example ['*/**.js', '!(test)/**/*.js'] in mm 3 would match foo.js, in mm 4 it would not. Both versions are kinda correct because the negated glob alone only matches "any js file in at least one subfolder that is not named test", because of !(test)/ (this is also that way in globs in bash), but combined with the first (positive) glob the behavior is outside of the "specified" scope of globbing and more like up to the libs how the combine and merge multiple globs.
Both of these changes also happened in jest in version 25 when micromatch was updated to version 4. (e.g. collectCoverageFrom).
Unfortunately, there is no right or wrong here and it's more based on opinion, so treat this PR more like a discussion for now.
So either jest keeps the way it does globs right now (ordered globs) which allows things like:
// Match all js files in all subfolders,
// but ignore all js files in subfolders in the folder `test` and `coverage`,
// except for the js files in `test/utils`
[
  '**/*.js',
  '!(test|coverage)/**/*.js',
  'test/utils/*.js'
]

To accomplish the same with this PR:
[
  '**/*.js',
  '!coverage/**/*.js',
  '!test/!(utils)/**/*.js'
]

Or switch back to the old behavior (jest 24 or lower) where one can do:
// Order does not matter, once a file is ignored it stays ignored, even if it would match in a subsequent glob
[
  '!(test|coverage)/**/*.js',
  '**/*.js'
]

Oh and the same can independently be decided for the negated (mis)behavior, although that could actually be considered broken and be fixed, as hardly anyone will be able to take advantage of the current feature. (I will bring this also up in mm/pm itself)
Test plan
Adjusted unit tests and added new unit tests
TODO

[ ] Discuss and find a preferred way
[ ] Changelog for this PR
[ ] Update docs for the config options with multiple globs and specify the behaviour the globs have.

This is very interesting, thanks for putting it together along with a thorough explanation!
I have to say I find micromatch@4's behaviour more intuitive/easier to understand. Based on that, the fix in #9464 (for the people who saw an improvement rolling back micromatch) is to change the order of their globs?
/cc @cpojer @jeysal @thymikee thoughts?

As a side note, this change in behavior between v3 and v4 should IMO be mentioned in the changelog: https://github.com/micromatch/micromatch/blob/5318752abc2f33153b3ccddf9f1f3b7682000a43/CHANGELOG.md#400---2019-03-20

I agree that on the ordering, micromatch 4 makes more sense (and seems strictly more powerful?), I'd like to be able to specify exceptions to a negated glob later on.
The example on how negated globs work slightly differently I must admit I didn't understand, maybe I'm missing knowledge on how the parentheses or something work in general.

I agree, I would keep the current behavior.

Okay will create PR for the docs and describe how globs are applied.


Dashboard can't/won't talk to datasource after deployment?

Is this a request for help?: Yes, it is.

Version of Helm and Kubernetes: 2.12.0 / 1.10.8
Which chart: Grafana
What happened:
I am trying to deploy Prometheus with Grafana with predefined datasources/dashboards. It works well for Kubernetes cluster monitoring, however I have an issue with external server metrics.
I am not sure where the problem is so I am asking here, correct me if I am wrong. Using https://github.com/marcel-dempers/kube-prometheus-grafana with my changes in
values.yaml:
namespace: monitoring

prometheus:
  k8-api-server: https://kubernetes.default
  service:
    name: prometheus
    port: 9090
  spec:
    image: prom/prometheus:v2.5.0
grafana:
  service:
    name: grafana
  spec:
    image: grafana/grafana:5.2.0
  prometheus:
    endpoint: http://prometheus:9090
  nfsserver:
    endpoint: http://<IP_ADDRESS>:8086

and grafana-datasources.configmap.yaml:
apiVersion: v1
kind: ConfigMap
metadata:
  annotations:
  name: grafana-datasources
  namespace: {{ .Values.namespace }}
data:
  kubernetes.json: |-
    {
      "name": "kubernetes",
      "type": "prometheus",
      "url": "http://{{ .Values.prometheus.service.name }}:{{ .Values.prometheus.service.port }}",
      "access": "proxy"
    }
  nfs-server-metrics.json: |-
    {
      "name": "NFS metrics",
      "type": "influxdb",
      "url": "{{ .Values.grafana.nfsserver.endpoint }}",
      "access": "proxy",
      "database": "telegraf"
    }

Dashboard for NFS metrics is from: https://grafana.com/dashboards/5955
After deployment I have Grafana with two dashboards and two datasources.
As you can see in: https://github.com/marcel-dempers/kube-prometheus-grafana/blob/master/helm/grafana/templates/grafana.deployment.yaml
Datasources are imported before dashboards. However for some reason "Telegraf - system metrics" dashboard can't talk to datasource saying:
Templating init failed
Datasource named ${DS_INFLUXDB} was not found

datasource dropdown menu is set to NFS metrics, but rest of fields like Server, disk, CPU are empty.
The solution for that is to remove dashboard and import it again. Any idea why that happen?
What you expected to happen:
Should display working dashboard
How to reproduce it (as minimally and precisely as possible):
Install from scratch as described above.
Anything else we need to know:

It looks like you're not using the stable/grafana chart from this repo. Maybe you should ask this question in the repo with the helm chart you are using.


Add usage examples to all functions

Essentially all user-facing functions now have examples. The only functions without examples are listed below:
utils.R:
file_marker_parse() - has an example, but currently wrapped in \donttest{} because it fails on example data
plot.R:
plot_tsne()
pretty_palette()
pretty_palette2()
not_pretty_palette()
pretty_palette_ramp_d()
compute_similarity.R:
calc_similarity()
vector_similarity()
cosine()
kl_divergence()
compare_genelist.R:
get_vargenes()
seurat_wrapper.R:
seurat_meta() - has an example, but currently wrapped in \donttest{} because it doesn't work on the s_small or s_small3 objects
object_ref()
common_dplyr.R:
call_to_metadata() - doesn't work with new column example data column names (expects only 'cluster' or 'cell_id')
collapse_to_cluster() - see above


Subfolders

Note toshiba creates folders with names like
DOC100818-10082018130619
and filenames inside like
Page0001.pdf
Page0002.pdf


Improve the editor native shader source visualizer

Use CodeEdit to enable features such as line numbers and minimap.
Enable syntax highlighting.
Use a fixed-width font.
Use the script editor settings.

The native shader source visualizer is the option from this dropdown:

Performance (in terms of the time it takes for the dialog to open) is roughly the same as before.
Preview
Before

After

Thanks!


Doesn't work with ember 2.13.0-beta.1

Just upgraded to ember 2.13.0-beta.1 and torii can't find the torii service when trying to open a provider, getting Cannot read property 'open' of undefined at https://github.com/Vestorly/torii/blob/master/addon/services/torii-session.js#L43  which indicates that the torii service is undefined inside torii-session service.
// env
var ENV = {
  torii: { sessionServiceName: 'session' }
}

// controller
actions: {
  signIn(identification, password) {
    return get(this, 'session').open('oauth2-password-grant', { identification, password });
  }
}

EDIT..
Trying to debugg this and injecting the torii service in the torii-session service works. However getOwner(this) is always undefined so the open of a adapter always fails.

Experiencing the same issue here. I can run with ember-resolver 4.x and ember-cli-babel 6.x (beta) and everything else at the latest and greatest, but as soon as I bump ember-source to 2.13.x, it breaks with this error.

got the same issue

Does this still persist in the release version of 2.13? Our setup seems to work with it but I'm not sure if we are doing something different here.

@Dhaulagiri I'm using 2.13.0 (Stable version) and my case is the same as #353. Now I've got to fall back to Ember 2.12.0.

I was having the same problem with v2.13.0. I decided to go back two versions (2.11.0). The example inside of ember-simple-auth works now.

I am having the same issue with v2.13.0too. From some debugging, I found that this.get('torii') inside open method always return undefined in the addon/services/torii-session.js.

@Dhaulagiri Heads up...2.13.0-beta.2 may create a regression. I was seeinggetOwner(this) return undefined. May have to do something like:
    var owner     = getOwner(this) || this.container,
        torii     = owner.lookup('service:torii'),
        sm        = this.get('stateMachine');

Still not sure what the underlying cause really is.

@crodriguez1a at this point you should be using the 2.13 release version (unless you are trying the 2.14 betas?)

@Dhaulagiri I opted in to a 2.13 beta for a minor bug-fix, but I reverted back. I'm hoping 2.14 will not inherit any of this stuff.

@crodriguez1a i don't understand why you are using the beta at all at this point?

@Dhaulagiri  I meant to say 2.14 (as you pointed out). Sorry for the confusion.

anyone have a reproduction or specific Safari versions/platforms?   has anyone who can reproduce seen this in WebKit nightly?

@krisselden this issue was fixed in https://github.com/Vestorly/torii/pull/355

I am having the same issue with  v2.14.2 with same error on line 49 of torii-session.
return adapter.open(authorization);
In my case solution #355 is implemented but error persist.
Any help will be appreciated cause I´m newbee and really need an auth.


Missing steps

You have " On the Additional security verification page, select Mobile app from the Step 1: How should we contact you area." as the first step....question.....where is the Additional Security Verification page.  Some people cannot find it.

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

ID: 4fc7dec3-d354-6e40-8662-0e8175e3cb09
Version Independent ID: 49976ef5-2893-8f73-3a64-94c2f3753d04
Content: Set up an authenticator app as your two-factor verification method - Azure Active Directory
Content Source: articles/active-directory/user-help/multi-factor-authentication-setup-auth-app.md
Service: active-directory
Sub-service: user-help
GitHub Login: @curtand
Microsoft Alias: curtand

@jamesloker  Thanks for your feedback! We will investigate and update as appropriate.

Hi @jamesloker,
The way to get there is also covered in the previous article:
Access the Additional security verification page
After your organization turns on and sets up two-factor verification, you’ll get a prompt telling you to provide more information to help keep your account secure.

More info required prompt
To access the Additional security verification page
Select Next from the More information required prompt.
The Additional security verification page appears.
You can also get there from myapps.microsoft.com > Profile https://docs.microsoft.com/en-us/azure/active-directory/user-help/multi-factor-authentication-end-user-manage-settings
Or can follow this link  ( myaccount.microsoft.com > Security Info )
I made a pull request to add the link but will leave it open for approval by the author. https://github.com/MicrosoftDocs/azure-docs-pr/pull/114402


How to open quickfixes?

How do I open quickfixes menu? In lua/config/lsp.lua there are mapping for code actions and rename but they're not working

You have not provided relevant info about your system. There is no way I should know why it is not working.


[adc_ctrl] Minor fixes to adc_ctrl

address #10045 by moving "done" 1 cycle back to match captured values.
update interrupt value on match instead of adc_ctrl_done to ensure we
only capture interrupt values when there is a match.

re-based to remove dv commit. I will merge once everything passes.


Add logging example code for when create_cli==no

Extended files:
{{cookiecutter.project_slug}}/src/{{cookiecutter.module_name}}/main.py
{{cookiecutter.project_slug}}/notebooks/example.ipynb

Affected option: config_file
Chosing hocon option creates the following code in main.py:
import logging
from test_hocon import util

logger = logging.getLogger("test_hocon")

def main():
    config = util.load_config()
    util.logging_setup(config)

    logger.info("Looks like you're all set up. Let's get going!")

    # TODO your journey starts here
    print("hello :)")

if __name__ == "__main__":
    main()

and adds this cell content to example.ipynb:
import logging
from test_hocon import util

logger = logging.getLogger("test_hocon")

config = util.load_config()
util.logging_setup(config)

logger.info("Use this setup to start logging in notebooks or to "+
            "get the correct logging format in your test_hocon module")

Chosing yaml option creates the following code in main.py:
import os
import logging
from test_yaml import util

logger = logging.getLogger("test_yaml")

def main():
    config = util.load_config(os.path.join(os.path.abspath(__file__),
                                           *[os.pardir]*3,
                                           "config",
                                           "config.yml"))
    util.logging_setup(config)

    logger.info("Looks like you're all set up. Let's get going!")

    # TODO your journey starts here
    print("hello :)")

if __name__ == "__main__":
    main()

and adds this cell content to example.ipynb:
import os
import logging
from test_yaml import util

logger = logging.getLogger("test_yaml")

config = util.load_config(os.path.join(os.path.abspath(os.pardir),
                                       "config",
                                       "config.yml"))
util.logging_setup(config)

logger.info("Use this setup to start logging in notebooks or to "+
            "get the correct logging format in your test_yaml module")

The path construction to the config.yml may not be ideal, but could be fixed when addressing issue #38 .

In reference to the issue mentioned in PR #26, should python files containing cookiecutter syntax be excluded in  .pre-commit-config.yaml?
Otherwise the check-ast pre-commit hook will always fail parsing .py files as correct python syntax.

I adjusted main.py because I had a few issues with it: discovery of the config file was too complex, just providing a static path should be enough to get you started, and hocon or having no config was not a well-supported case.
I'm still not sure about this PR, because we're adding a lot of complexity here that many of our users might not care for.
If you want to continue with this, can you adjust the notebook code in a similar fashion?

ok, now I'm also not happy with the static config path, because it probably won't work by default for most users (e.g. if you launch it in PyCharm, it will try to find the config relative to main.py and not the project root folder).
well... I don't know. If we have the CLI, we can let the user define the path to the config, but in this case, I don't think we're setting a good example by defining a path in the code where the config has to be.

Yeah, that is the reason why I opted to build the relative path from main.py to the config using os.
I agree that fixing a path in the library is not good design, I thought of it more as an example, so that people would get a hint at how to make use of logging. In that line of reasoning, it would still make sense to have a static path in the notebook, because that is not part of the python package that is being built, and notebooks are always executed from where they are, so the relative path  from example.ipynb to the config should work in any setup.
I also agree that complexity should be kept low, but at the same time we want to encourage good design, which includes logging instead of printing wherever possible. My first experience with the template was just that it didn't paint a clear picture of how to utilize the logger correctly.


Don't always require clientId in hasRole

Token.hasRole should not require the clientId if the realm/application have explicitly been set, as the clientId is not always available (I wonder when this is actually the case, seems like never for me...).
Note: Additionally, if parts.length === 1 the given rule could also be interpreted as realmRole and be checked via return this.hasRealmRole(parts[0]):
const parts = name.split(':');
if (parts.length === 1) {
	if (this.clientId && this.hasApplicationRole(this.clientId, parts[0])) {
		return true;
	} else {
		return this.hasRealmRole(parts[0]);
	}
} else {
	if (parts[0] === 'realm') {
		return this.hasRealmRole(parts[1]);
	} else {
		return this.hasApplicationRole(parts[0], parts[1]);
	}
}

The clientId of the Token is only set if it is specified in the keycloak.json, which isn't the case for the default file that is generated by the keycloak "Installation utility". Maybe this should be noted in the documentation.

Hi @N-Coder just sharing info I'm trying to understand this too [if is correct to set clientId manually on keycloak.json] .
http://lists.jboss.org/pipermail/keycloak-user/2016-June/006527.html

@N-Coder I don't think clientId is mandatory in such scenario. Could you please add specs (tests) for that?

Interesting information from keycloak gitbooks 'securing-client-applications-guide'

resource
The client-id of the application. Each application has a client-id that is used to identify the application. This is REQUIRED.

https://keycloak.gitbooks.io/securing-client-applications-guide/content/topics/oidc/java/java-adapter-config.html

So this line must be changed to resource instead client-id :
https://github.com/keycloak/keycloak-nodejs-auth-utils/blob/443c0a73df4f98018967d904f96cef397acdf149/lib/config.js#L78
I'm not sure but since resource is required and exists in keycloak.json... all consecutive verifications are unnecessary e.g :

if (!this.clientId)
( something && clientId )
etc..

right ?

@N-Coder there was a regression introduced here: https://github.com/keycloak/keycloak-nodejs-auth-utils/commit/fb05d5089d825743368baa027e0a7ce94c86b882#diff-f7bf2b665273dfa66ffa4ad7c0a52bb9L79 which prevented the module from recognizing the property name resource which is what is generated in keycloak.json provided by the server.
https://github.com/keycloak/keycloak-nodejs-auth-utils/commit/dbf36206edf62a77b8a47f4c03f4f60e2d50c497 should resolve the issue for you. We will release an updated version of the module this week, but in the meantime, you can simply change resource to client-id in your keycloak.json file. Can you please test and confirm? Thanks.

@abstractj keycloak exports keycloak.json with 'resource' property not with 'client-id' through installation tab, this file is for any adapter, right ?

@helio-frota now I see the confusion. resource is the client id which is required and mandatory, what I meant and is not necessary is clientId parameter.
It makes sense?

@abstractj Yup ! Makes sense :+1:  thanks

I'm closing this for now as I believe it has been resolved via https://github.com/keycloak/keycloak-nodejs-auth-utils/commit/dbf36206edf62a77b8a47f4c03f4f60e2d50c497. @N-Coder if you have any additional problems, please open a new issue or PR.


README link to version 1.1 spec results in a 404

The link destination is as follows: https://github.com/Adobe-Marketing-Cloud/sightly-spec/blob/1.1/SPECIFICATION.md

Solved by re-tagging version 1.1. Thanks!


Add unauthorized page (resolves #54)

Example page:

The screenshot is from running Flask locally. It's not the full blown deploy, but it should be good. But good point, I'll try with my VM as well to be safe.
Regarding the CSS, I was thinking I just wanted a file that would load quickly without any dependencies. I also came up with this UX "design" on my own, that's somewhat inspired by one I worked on in the past. For better or worse, it's not a pattern that we use on other pages, because this page is not like any other pages, so far. All that said, it probably is best to put the the CSS in a file.

The screenshot is from running Flask locally. It's not the full blown deploy, but it should be good. But good point, I'll try with my VM as well to be safe.

Sounds good!

Regarding the CSS, I was thinking I just wanted a file that would load quickly without any dependencies. I also came up with this UX "design" on my own, that's somewhat inspired by one I worked on in the past. For better or worse, it's not a pattern that we use on other pages, because this page is not like any other pages, so far. All that said, it probably is best to put the the CSS in a file.

Up to you really, I just though I'd bring it up.

Now leaning towards not separating out the CSS. :) It doesn't really fit in any of the existing CSS files, and it currently won't be reused anyway. We can cross the bridge later if we need to reuse it.

@jessebrennan I ended up:

Keeping the CSS in the HTML
Leaving the defaults for project and contact as empty string, but not account, because I explicitly test for None in the template.

Could you please take one final look?
Also, I'm thinking it would be nice to have a contact name and a contact email, that way we wouldn't display the email. But that will require an update to the installer, and is nice to have, so we can tackle that later.


Fix: allow * and ? for function this type

Google Closure Compiler parses function(this:?) and function(this:*) (ex: goog/events/eventhandler.js)
doctrine should be able to parse it without errors expectedly, but actually throws not reach to EOF now.

Coverage remained the same at 99.258% when pulling d2fec70ce25534f0b134dab3e26f6f0751c83959 on teppeis:fix-this-type into 42434ca1f85b264a88afcfd317487a7417e6004b on eslint:master.

Coverage remained the same at 99.258% when pulling d2fec70ce25534f0b134dab3e26f6f0751c83959 on teppeis:fix-this-type into 42434ca1f85b264a88afcfd317487a7417e6004b on eslint:master.

Coverage remained the same at 99.258% when pulling d2fec70ce25534f0b134dab3e26f6f0751c83959 on teppeis:fix-this-type into 42434ca1f85b264a88afcfd317487a7417e6004b on eslint:master.

Coverage remained the same at 99.258% when pulling d2fec70ce25534f0b134dab3e26f6f0751c83959 on teppeis:fix-this-type into 42434ca1f85b264a88afcfd317487a7417e6004b on eslint:master.

Coverage remained the same at 99.258% when pulling d2fec70ce25534f0b134dab3e26f6f0751c83959 on teppeis:fix-this-type into 42434ca1f85b264a88afcfd317487a7417e6004b on eslint:master.

Thanks for this PR. We have decided to officially end-of-life JSDoc support in ESLint. As a result, this repository and project will no longer be maintained.
Thanks for understanding and we apologize for any inconvenience.


Getting started with MQTT and amazon-FreeRTOS on ESP32

Hi everybody,
I am kind of new to all the FreeRTOS chapter and are struggling a lot with all the MQTT communication.
I got all the Amazon-FreeRTOS demos working for MQTT, and also can modify it to subscribe to a different topic or change buffer counts.
But now my problem is, that it is impossible for me to modify the demo to make a simple MQTT communication and publish or subscribe to a topic. I did not even find out how I can publish/subscribe to two different topics, linked with the correct payload.
I was reading a lot through all the community out there trying to find help for my issue and noticed that I´m not alone with my problems. Many new guys out there struggling the same than me, reading through 844 lines of code without understanding anything.
I would really appreciate if somebody could do a really simple MQTT explanation/example.
Let´s say 3 simple examples in the garden managed by ESP32:
1. Switching the watering valve On/Off and read status of valve, publish and subscribe to topic (On/Off)
2. Read an analog water tank level, publish to topic
3. Pass preset value received from topic to a local variable, subscribe to topic
And the most important would be, to start from an empty page with MQTT and explain the complete flow in the example what has to be done in order to get one message successfully published or subscribed to a topic.
Starting from scratch and walk through all the steps that have to be done and how.

Get local values that have to be published.
create payload
link it to the correct topic
connect to broker
publish MQTT package
subscribe to MQTT packages
save received values into local variables
cleanup MQTT connection

I would be really happy, if somebody could make a youtube video out of it and explain the steps he is doing.
Or if it can´t be a video maybe a straight forward explanation in between the steps, in normal words for everybody understandable.
So at the end everybody would be able to make a use out of the MQTT and Amazon-FreeRTOS  at home to switch on/off a lamp for example.
Thank you guys a lot, I really appreciate your help in advance!!!
Thanks, Alex

Hello @KressAlex,
I'm sorry to hear you had difficulty getting started with the MQTT library. We appreciate your feedback and request for more detailed documentation, and we will consider updating it.
Is there any part of the FreeRTOS documentation specifically that you found confusing or needs clarification? Is the MQTT API Reference any more helpful in answering your questions?

Hello @muneebahmed10,
thanks for your quick answer!
I don´t know how to publish a customized message, lets say for example i want to press a button and than it should publish a message which includes some data for the weather.
So I press the button, than I want to publish to topic "Home/CurrentWeather" and the status as payload "Rain"
And during a temp change, on another topic I want to publish the Temperature "Home/CurrentTemp", payload "19 °C"
So I expected something like a function to pass the data:

PublishToTopic("Home/CurrentWeather", "19 °C");
or   d PublishToTopic("Home/CurrentTemp", "Rain");

something like this for example where I can pass my parameters to the Publish function:
typedef struct IotMqttPublishInfo
{
IotMqttQos_t qos;         /< @brief QoS of message. Must be 0 or 1. */
bool retain;              /< @brief MQTT message retain flag. */
const char * pTopicName;  /**< @brief Topic name of PUBLISH. */
uint16_t topicNameLength; /**< @brief Length of #IotMqttPublishInfo_t.pTopicName. */

const void * pPayload;    /**< @brief Payload of PUBLISH. */
size_t payloadLength;     /**< @brief Length of #IotMqttPublishInfo_t.pPayload. For LWT messages, this is limited to 65535. */

uint32_t retryMs;         /**< @brief If no response is received within this time, the message is retransmitted. */
uint32_t retryLimit;      /**< @brief How many times to attempt retransmission. */

} IotMqttPublishInfo_t;
but I don´t understand how to forward all the information into the iot_demo_mqtt.c, because in the demo it´s always the preset Hello World, and than its just numbers counting up and down in the function.
I know that I also have to Initialize the MQTT connection first and than also cleanup.
Thanks a lot @muneebahmed10 !!!

hello @KressAlex,
maybe you can modify freertos/demos/greengrass_connectivity/aws_greengrass_discovery_demo.c. the program explain how to pub/sub JSON message and you can import library sensors.
I give you link about example amazon-freertos-esp32 using dht11 from krazers (https://github.com/krazers/freertos-dht11)
keep spirit bro!

Thanks a lot @monhack!
I will take a look into this and will keep you posted, if I got a step closer or not.
Thanks!
Regards Alex

Hi @KressAlex,
In the MQTT demo function _publishAllMessages, you can see where the topic name and payload are assigned in the publish info struct before calling the MQTT Publish function. You can write your own function using the MQTT API to suit your needs, e.g.
void PublishToTopic( IotMqttConnection_t mqttConnection, const char * topic, const char * payload )
{
    IotMqttError_t publishStatus = IOT_MQTT_STATUS_PENDING;
    IotMqttPublishInfo_t publishInfo = IOT_MQTT_PUBLISH_INFO_INITIALIZER;
    IotMqttCallbackInfo_t publishComplete = IOT_MQTT_CALLBACK_INFO_INITIALIZER;

    publishInfo.qos = IOT_MQTT_QOS_1;
    publishInfo.pTopicName = topic;
    publishInfo.topicNameLength = strlen( topic );
    publishInfo.pPayload = payload;
    publishInfo.payloadLength = strlen( payload );
    publishInfo.retryMs = PUBLISH_RETRY_MS;
    publishInfo.retryLimit = PUBLISH_RETRY_LIMIT;

    //Assume someCallbackFunction is your callback function defined elsewhere.
    //It will be called when the publish completes.
    publishComplete.function = someCallbackFunction;
    //The context should identify the publish that was completed, e.g. the topic (if unique).
    publishComplete.pCallbackContext = ( void * ) topic;

    publishStatus = IotMqtt_Publish( mqttConnection, &publishInfo, 0, &publishComplete, NULL );
}

Hi @muneebahmed10,
I'm still struggling with the MQTT part.
Do you think that it would be possible, that somebody does an example code that could be included in a custom code, just to send the basic MQTT and call the correct steps that has to be done and also close the connection in a correct manner.
And recall that code based on an event, for an example a button is pressed or a value has changed!?
The MQTT example has so much content, that might don't even had to be changed for simple applications and is tightened into so many other things. That would be also like a future request to tell the guys that just get started with the MQTT communication.
Or maybe you can send me a PN.
Thanks so much, regards Alex

Hello @KressAlex,
Our documentation relies on on the customer understanding how the MQTT protocol works on a high-level and also an understanding of the C language.
Unfortunately we do not currently have a blog or sample for an application using a mock or real sensor and I can definitely put into our future planning considerations if this can be created. We have found that interns just starting on the team can quickly create applications to send sensor data to AWS IoT to view using our current demos. It sounds like you are looking for a single topic example that publishes only for you to write over a few lines for your needs? The current demo has multiple topics and I do think you can easily piece together how to do this simply for one topic.
The current iot_mqtt_demo.c in this repo subscribes to the same topics it is publishing to that that in a single thread we can see that data being submitted is also received.
RunMqttDemo() - Shows the high level steps of:

connect
subscribe
publish
unsubscribe
disconnect

Depending on your needs, you may want to publish only and can skip the subscribe examples.
In RunMqttDemo() as you may already know you can modify your subscriptions here:
    /* Topics used as both topic filters and topic names in this demo. */
    const char * pTopics[ TOPIC_FILTER_COUNT ] =
    {
        IOT_DEMO_MQTT_TOPIC_PREFIX "/topic/1",
        IOT_DEMO_MQTT_TOPIC_PREFIX "/topic/2",
        IOT_DEMO_MQTT_TOPIC_PREFIX "/topic/3",
        IOT_DEMO_MQTT_TOPIC_PREFIX "/topic/4",
    };

After connecting to the broker, the next step is to subscribe to these topics.  In _modifySubscriptions() you should be able to find an example of the needed parameters for IotMqtt_TimedSubscribe() being filled out.
    for( i = 0; i < TOPIC_FILTER_COUNT; i++ )
    {
        pSubscriptions[ i ].qos = IOT_MQTT_QOS_1;
        pSubscriptions[ i ].pTopicFilter = pTopicFilters[ i ];
        pSubscriptions[ i ].topicFilterLength = TOPIC_FILTER_LENGTH;
        pSubscriptions[ i ].callback.pCallbackContext = pCallbackParameter;
        pSubscriptions[ i ].callback.function = _mqttSubscriptionCallback;
    }

This logic to use IotMqtt_TimedSubscribe() under the if( operation == IOT_MQTT_SUBSCRIBE ) part.
The next thing you need to do is publish. _publishAllMessages() shows how to fill out the parameters needed for IotMqtt_Publish(). From @muneebahmed10's last post, he shows you how to simplify the function a bit more for whatever your needs may be.
The next steps in the demo is to unsubscribe to the topics it subscribed just before disconnecting.  The logic in _modifySubscriptions() for unsubscribing is shown under the else if( operation == IOT_MQTT_UNSUBSCRIBE ) part.
The disconnection with the server is shown in a correct manner with the example code:
    /* Disconnect the MQTT connection if it was established. */
    if( connectionEstablished == true )
    {
        IotMqtt_Disconnect( mqttConnection, 0 );
    }

    /* Clean up libraries if they were initialized. */
    if( librariesInitialized == true )
    {
        _cleanupDemo();
    }

hi @sarenameas,
Thank you very much on your feedback, I will work on the flow you provided and I hope to get success!
Thanks very much to all of you!
best regards Alex

@KressAlex
And thank you for choosing us! I am going to close this issue now. Feel free to open a new one if you run into any other issues.
Thanks,
Sarena


Create Blackbox Tests for the SMA.

We want to have a set of ready-to-run Blackbox Tests to catch regression bugs for the SMA.

@akramtexas Would you mind moving this issue to the blackbox-testing repo so we can track it there? Thx.

@tsconn23 Done.

Yep, the blackbox-testing is indeed the right spot for this issue 👍
Closing this issue and created Issue-204 in lieu, thanks.


fix: missing trailing commas

What kind of changes does this PR include?

Minor content fixes (broken links, typos, etc.)

Description
As discussed in https://github.com/withastro/docs/pull/1767#discussion_r991704745, inserted some missing trailing commas in package.json example fragments.
(I'm taking part in Hacktoberfest 🎃)

Thank you for the PR @breadadams! 🚀
I would like to follow our translating guidelines and only update our English version of the docs. This way all locales would be aware of the change and can update accordingly.

Ah good point @kevinzunigacuellar, I've reverted the change to the Spanish file and updated the PR.

Hi @breadadams! Nice to see your name around in all these docs PR notifications!  🥳
I'm looking at this now, but I think our code examples are correct as-is. Trailing commas are disallowed in .json objects, so it's proper without them.
For future reference (I know, we have so many rules to follow here because of our complicated setup!), in addition to only changing en files for things like this, some of our files are imported from source content in a different repository and simply mirrored here. So always check at the top of a file when you're editing, and there should be a note to tell you when NOT to edit a file directly and where the source file is located. A couple of these files here are actually like that, so we wouldn't edit them in this repo anyway.
So, I'm closing this PR, but I'm sure I'll be seeing you and your keen eyes in new ones! 🦅 👀

Hey @sarah11918, thanks 😄
Yep, my bad, I was supposed to just fix one case where there's actually a missing comma and I went overboard 😅. I've adjusted the fix again, if you'd consider reopening the PR.
Thanks!

Hi @breadadams, thanks! And yeah, sorry it's all a bit complicated. 😄  But the real problem is that it's not a correction to add the comma at all. There should be no trailing comma in json. In JavaScript it's common, and acceptable. But, not in json.

Yep no worries @sarah11918, I know. The issue lies here, in the Deno deploy guide:

Where a new line is being added to the package.json scripts. I've updated my branch but it doesn't reflect in the PR right now since it's closed.

OK, gotcha! Yes that one (but only the 2nd last line) needs a comma. (And, in the earlier example, which is a diff, no comma needed because the deleted line wouldn't have had a comma, either.)
As long as we're on the same page!  😄

I'm not able to reopen this one, there seems to be a problem. So, submit a different PR I guess? I'll apply the Hacktoberfest label there, too. (And, I think you might get credit for both, as long as the label here isn't removed.)

Ok I'll open a fresh pull request. Thanks and sorry for creating all this noise!


Update to the Additional Transportation Expenses cost field in application form

Describe the task
Incorporate Additional Transportation Expenses cost field into workflow, and add content next to the relevant field on application form.
Content wording to be included in Info banner immediately beneath the cost field
_"Include the following calculation information as listed below
If you travel more than 280 km per week:

Multiply $94 times the number of weeks during your study period that you require the additional transportation allowance. Enter this number in the field below.

If you travel 280 km or less per week:

Multiply [the number of km driven per week] x [0.34] x [the number of weeks in your study period that you will need the additional transportation allowance]. Enter this number in the field below.

Please note in either situation if you are already receiving the $25 weekly allowance for a clinical or practicum placement from your institution please subtract that from the calculated amount of Kilometers driven x 0.34 or from the $94 when travelling over 280 km per week."_
Workflow
Private Zenhub Image
Acceptance Criteria

[ ] Add an Info banner immediately beneath the cost field in the Additional Transportation Question. See above for exact content wording.
[ ] Include the additional Transportation cost in the calculatedDataTotalCost in the workflow. (see image above)
[ ] Store field in database so that it is accessible for IER12.
[ ] Map field to the IER12.

Additional Context

Reviewed Signori comments and function looks correct.
We will need a variable under the student costs section (Steps 1-7 of assessment) and that variable will need to then be included in the calculatedDataTotalCosts

Please see the below screenshot. Except for the first option, the other three options there creates a place to receive uploads and also input the "weekly transportation costs". If that is not the expected behavior, please let us know the expectation.

Copy of SABC Policy Manual - this exception / appeal type IS needed for PT
This will need a new ticket to re-add the Additional Transportation allowance question into the PT application, and to add the corresponding variables into the workflow, similar to however it is reflected in PT workflows.
Private Zenhub Image

FT & PT - question/workflow:

[ ] Same initial question for "Additional transportation cost" with Yes/No radio dial
[ ] "Which of the following" multiple option radio dial still the same.
[ ] Supporting document upload feature
[ ] "Please estimate your weekly transportation cost during the study period" (dollar field)
[ ] This will generate an exception request to the Ministry
[ ] Ministry user can view: Exception type (Additional transportation cost), Radio dial (Which of the following..), Estimated weekly cost (dollar field).
[ ] Ministry user Approves the exception and transportation amount is adjusted:
Part time:

if offeringDelivered = "onsite" && (exception is denied or exception not applied for) then dmnPartTimeProgramYearMaximums.limitTransportationAllownace * offeringWeeks else if offeringDelivered = "onsite" && (exception is approved) then max(dmnPartTimeProgramYearMaximums.limitTransportationMaxAllowance,studentDataTransportationcostsEstimate) * offeringWeeks else 0
[ ] New column in dmnPartTimeProgramYearMaximums for limitWeeklyTransportationAllowanceMax (2023-2024 $94)

@HRAGANBC Is Updates to the application included inthis ticket OR is this just a workflow update?

@HRAGANBC This will not pass User Accessibility in content or workflos- Please lets discuss at our next review. How can we take the bourdon OFF the student for these calculations.

@michesmith
Carly has some additional mock-ups for how this could be handled in a more sophisticated way and save the student from the burden of calculating themselves. However, given this is only used on exceptional basis as it is, and there is plenty of opportunity for Ministry and Student to liaise to get the numbers right, I'd like to continue down this path given it's simplest from Dev perspective for MVP.

@HRAGANBC @CarlyCotton im still uncomfortable with the accessibility of this question. I will confirm the larger strategy with nino but I believe the language here or solution needs to be simplified for students.

@michesmith @CarlyCotton There is always the possibility of adding additional questions to support automatic calculation of these figures, and perhaps that can be done with less additional workload than I assumed. Carly already has these mockups in place that can support a grooming convo with the Devs

@HRAGANBC I've updated this to capture the change required in the application form and created two new tickets to address the actual calculations in FT & PT. This is to support getting the work started and split off the assessment piece as it's in different places when we get to that. Do we want some of the additional context in this ticket on the Ministry Exception screen or can we expect that they know what to do with the data? (Or do we do some calculation to be presented to them in their view)

@CarlyCotton
I don't think we need to provide that info to Ministry staff through the interface - that's something that will always be decided by the Appeals team, and I'm comfortable defering them to an Ops manual type thing for this level of detail. I think this is ready for grooming & implementation so have moved to lather

@Joshua-Lakusta can you please add some basic form validations.

@michesmith what form validations are we wanting on this? length of input? just "required"?

I updated to add content for the questions in the AC's and added validations of the numerical entries in the forms.

Thanks @Joshua-Lakusta for the update.
@CarlyCotton that was raised during the grooming.
The idea is that we are pretty behind in any UI validations for the Student Application.
It would be good if every new field had some validation. When unknown or not clear we can have some ballpark idea around it.
For instance, for distance, it probably will never be negative, it may or may not have decimals and it probably has a limit. If no limit is clear from policy we can have something in place.

As per conformation from @Joshua-Lakusta , the validation for weekly transportation cost is: 0 <= cost <= 9999.

It's been confirmed that the Additional Transportation Costs questions (this story) also apply to PT applications.


Use git tags as single source of truth for versioning

I don't know how or if this would work, but something like Python's setuptools_scm would be nice.

I didn't find anything good, but I also didn't search very thorough. The thing is, the project version only appears in once in the top-level CMakeLists.txt file. When adding a vcpkg port, the version for that is kept in a different repository, so it doesn't even need to be in sync with the real project version.

After adding the vcpkg manifest file, the version also appears there. The easy solution to not duplicating the version in vcpkg.json and the top-level CMakeLists.txt is reading the version from the manifest file with CMake. See https://github.com/fantana21/QuantNd/issues/16.


Update securing-your-node.md for cloud-init

Two NOs have reported this issue so far.

Thank you!


Adding multi cloud details

Proposed changes
Multi cloud is a common deployment model used by many organisations and it is beneficial to add it to this Readme. It will enhance the knowledge of readers who read it.
Types of changes
What types of changes does your content introduce to this project?
Put an x in the boxes that apply (without "`")

[ ] Proofreading (fix spelling, grammar, punctuation, accuracy) Proofreading
[x] New content (new section, new readme, etc.)
[ ] Modifications (modifying existing content)
[ ] Other (please describe)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. Don't hesitate to ask if you're unsure about any of them. We're here to help! This simply reminds us of what we will look for before merging your code.
Note: If you submit code make sure to test it

[ ] Tested any code that was added/modified in this PR
[ ] Added external links
[ ] Added internal links
[ ] Added images
[ ] Added videos
[ ] Added code snippets

Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Adding your name to the contributor's list
Comment "@all-contributors please add @your_username for content" to add your name to the contributor's list.
You can change the "content" with any of this
Reviewers:

[ ] @username

Please ensure that you are not adding any sensitive information like API keys, secrets, passwords, tokens, usernames, or other credentials. Refrain from adding your name, email, or other personal information.

@shhossain can you take a look at this content?

@amoghrajesh PR is merged.


[SSOC 2.0] Readme File for Analog Clock

🛠 Issue (1883)

Closes #1883
Description
Created the readme file for Analog Clock Project
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

Checklist:

[x] I have made this from my own
[x] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@TusharKesarwani @zugzwang03 Pls Review my PR.


Add checks for capabilities that allows container escape

Hi team,
The check_5_3 lists extra capabilities but unfortunately it doesn't describes the risks associated with them. I decided to fill this gap and added checks for capabilities that allow container escape directly.

Nikita Stupin
Advanced Software Technology Lab
Huawei

Thanks for the PR @nikitastupin! Looks good, will merge after a few tests.

So sorry @nikitastupin for the delay, thank you for your contribution.

Hi @konstruktoid, no worries! I'm glad that you've found this PR helpful and merged it.


Set List& Detail resources to Default BundleConfig

I moved the List & Detail path default Config in the Bundle Config.
Think it isnt really need to configure it by your self, should be cleaner.
And if it is there a reason for Change, the user could overwrite the config.

@TheCadien thx for this PR. Very much appreciated.
Will this cause trouble when upgrading and the yaml file is already in place? If yes, then we need to mark it as being a BC break.

Feel free and can test it, but in my mind the old config yaml now simply overwrites the config in the bundle.
Which has no influence on the function but is simply superfluous.
A deprecation note in an Upgrade.md would be sufficient in my eyes.

Will try to prepare a release in the next few days.
If you see other improvements, let me know.


Improve the qiskit.algorithms docs: clearly show legacy vs. primitive algorithms

Emphasize the split in primitive-based and legacy algorithms more clearly

Summary
More clearly emphasize that for the (minimum) eigensolvers there is currently a duplication of algorithms: the legacy, QuantumInstance-based algorithms that are pending deprecation and the new, primitive-based ones.
Details and comments
An alternative would be to keep the separate headings and link to the non-deprecated one, like in the screenshot for the time evolvers below. However since the headings are "Eigensolvers" vs. "Eigen Solvers" I think it would be nice to merge them.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.03%) to 84.864%

Files with Coverage Reduction
New Missed Lines
%

qiskit/extensions/quantum_initializer/squ.py
2
80.0%

src/sabre_swap/layer.rs
2
98.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
66020

Relevant Lines:
77795

💛  - Coveralls

In the future, primitive-based Minimum Eigensolvers should be used in place of the legacy :class:.QuantumInstance-based ones.

Ideally we would like people to start using these new ones now (not in the future) for any new code (and maybe even update existing code), as the the legacy ones ones, while they continue to work, will soon be deprecated and later removed. Hence the "In the future, " bit seems like it could be improved (I just quoted one example above). In the future you will only be able to use these. Now you can too and indeed we recommend you do use these rather than the legacy versions.

That's a good point, how about something like
These algorithms are based on the Qiskit Primitives, a new execution paradigm that replaces the use
of :class:`.QuantumInstance` in algorithms. To ensure continued support and development, we recommend
using the primitive-based Eigensolvers in place of the legacy :class:`.QuantumInstance`-based ones.

?

That's a good point, how about something like

Looks much better to me thx!

Done in bf1f6cc 👍🏻


[ML] Add MoMo Docstrings and Make Models/Consts Public (#30242)

add docstrings for monitoring classes

make models public

fix model performance

black

fix imports

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-ai-ml


As a user I want the home page to have access to trending and popular challenges so I can find the most fun things right away.

The following issues are required to complete the user story in the title.

[x] #144
[x] #143
[x] #142
[ ] Include the games in this page.

Moving to Future milestone, as this has been done by Evon but we aren't going to merge it in for this sprint.


Morphing back in slime from geras will eject you from container

Be slime
Close yourself in a closet
Morph in geras
You are still in closet
Morph back in slime
You ejected from the closet

Fixed by #29731


Automatically run unlocalize task when done building dist/ to restore src/nls/*

I'm seeing so many of my students get stumped by the fact that we touch files in src/nls/* and don't know how to restore them.  I can't believe I didn't think of this before, but we should just be undoing it as soon as we're done.

I think this is fine for this case but it does mean that depending on how you're loading bramble, i.e. from dist or from src, it will support a different set of locales (and strings).