Icedrift

Adding a program to deal with the daily average from CICE (iceh.????-??-??.nc) in which the 24h ice drift will be diagnosed and restored into NC file. To consider the concerned result will be used for assimilation of ice drift observation, this program also supports the ensemble runs. In addition, there are some simple scripts for evaluation of the created NC files and for comparison with the used observations.

I did not check it, I don't see a problem merging it.
Are you planning additional updates?
I can go ahead and merge it and then test it.

Thank Alfatih,
I added one sentence correction in the code.
It should have no merging issue.
Cheers,
Jiping

On 6 Mar 2023, at 10:46, Alfatih Ali @.***> wrote:
I did not check it, I don't see a problem merging it.
Are you planning additional updates?
I can go ahead and merge it and then test it.
—
Reply to this email directly, view it on GitHub https://github.com/nansencenter/NERSC-HYCOM-CICE/pull/180#issuecomment-1455805202, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGDZNKM67QNO7SUOKR5ERILW2WXADANCNFSM6AAAAAAVEUB7CY.
You are receiving this because you authored the thread.


Extension causes high cpu load

Issue Type: Performance
Extension Name: vsliveshare-audio
Extension Version: 0.1.91
OS Version: Windows_NT x64 10.0.19042
VS Code version: 1.62.3

:warning: Make sure to attach this file from your home-directory:
:warning:c:\Users\MARIO~1.DOM\AppData\Local\Temp\ms-vsliveshare.vsliveshare-audio-unresponsive.cpuprofile.txt
Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load

We're unable to prioritize fixes to this area as we re-evaluate our priorities and product direction. We understand that this maybe disappointing. We appreciate your input and comments on this issue till now. We will soon be sunsetting this feature and will work towards a better use experience for communication needs for Live Share users from the editor.


Ref #11 now using console.log in web-server script

Use of "util.puts" is deprecated. The server logs recommend using "console.log" instead. This commit replaces occurrences of "util.puts" with "console.log".

Thanks.. those were part of the scaffolding seed I used.


image playground doesnt work

POST foundation-models/model/image/stability.stable-diffusion-xl/invoke HTTP/1.1" 500 Internal Server E

The model name was updated, but this app wasn't... I added a PR to fix it, but it seems this repo is not being maintained?


https://github.com/nodegit/nodegit/i

https://github.com/nodegit/nodegit/issues/1764
Originally posted by @implausible in https://github.com/nodegit/nodegit/pull/1766

@will809  Can you please explain what this issue is regarding?


Update to SALifetime Bytes value for QM

@brenduns - Would you review the proposed changes? Thanks

#sign-off


Allow new timezones from tzdata that do not yet exist in system

Fixes #136

Codecov Report

Merging #159 (7b5f8ac) into main (fb2ce69) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   96.74%   96.74%
=======================================
  Files          43       43
  Lines        2548     2548
=======================================
  Hits         2465     2465
  Misses         83       83

Impacted Files
Coverage Δ

ical/tzif/timezoneinfo.py
80.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


ERROR: could not spawn 'C:\Users\cel\.julia\v0.6\SARSOP\deps\appl-0.96\src\pomdpsol' model.pomdpx --output out.policy: no such file or directory (ENOENT)

I am trying to run tiger.pomdp. Here is the full error:
policy = solve(solver, pomdp)
Generating a pomdpx file: model.pomdpx
ERROR: could not spawn 'C:\Users\cel\.julia\v0.6\SARSOP\deps\appl-0.96\src\pomdpsol' model.pomdpx --output out.policy: no such file or directory (ENOENT)
Stacktrace:
[1] _jl_spawn(::String, ::Array{String,1}, ::Ptr{Void}, ::Base.Process, ::RawFD, ::RawFD, ::RawFD) at .\process.jl:360
[2] #375 at .\process.jl:512 [inlined]
[3] setup_stdio(::Base.##375#376{Cmd}, ::Tuple{RawFD,RawFD,RawFD}) at .\process.jl:499
[4] #spawn#374(::Nullable{Base.ProcessChain}, ::Function, ::Cmd, ::Tuple{RawFD,RawFD,RawFD}) at .\process.jl:511
[5] run(::Cmd) at .\process.jl:650
[6] solve(::SARSOP.SARSOPSolver, ::TigerPOMDP, ::SARSOP.POMDPPolicy) at C:\Users\cel.julia\v0.6\SARSOP\src\solver.jl:96
[7] solve(::SARSOP.SARSOPSolver, ::TigerPOMDP) at C:\Users\cel.julia\v0.6\SARSOP\src\solver.jl:94

Sorry, sir. I'm new in Julia. So may be it is my mistake. I could not
understand why this problem occurred.
On Fri, Jul 21, 2017 at 8:08 PM, Tony Kelman<EMAIL_ADDRESS>wrote:

What makes you think this is a problem with Graphs.jl?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/JuliaArchive/Graphs.jl/issues/244#issuecomment-317138801,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AILGU9NTH7Nov4Mgw5RP5cHpaBkZV0K-ks5sQT1rgaJpZM4Of_TF
.

--
Mr. Aritra Ghosh
Graduate Research Assistant
Department of eLearning
Florida Atlantic University
Boca Raton, Florida,
U.S.A 33486

This should be opened at https://github.com/JuliaPOMDP/SARSOP.jl


Better handling of infinite loops in repetitions.

Fixes #598

Consider leaving the infinite loop docs so older versions errors links would still be valid.


Add fields via application.properties

First, i really want to thanks you for the effort to have structured logging in quarkus.
I have a question (and a possible request). Is there a way to set some constants in the log via application.properties?
something like: quarkis.logging.json."serviceName".value=test
Log:
{ serviceName: "test" , message:"message"}
Regards

It's not possible right now, only foreach message using StructuredArgument.
I will implement it, after the feature I am currently working on.

I have just release version 0.1.5, with this feature.

Thanks :)


[Question]: No PDF or literature note detected, what to do?

Bug Description
I wouldn't actually call this a bug, rather a question on whether I'm doing something wrong.
I have this entry with the citekey @Campbell2022The-Souls-Tool: which is generated by BibDesk. I've tried to turn off the colon generation, but I can't seem to find a solution for it.

Despite the colon not showing up in the preview in this BibDesk pannel, it's present as a separator in every other citation that is generated in it. Of course, I thought it was going to cause some problems with other software. When creating a literature note in Obsidian, the colon gets converted to an underline:

The name of the associated PDF is also generated through Auto-File in BibDesk. The PDF is attached, and it shows as such in BibDesk:

The PDF doesn't have a colon nor an underscore.
(I can't take a screenshot of what shows up because of modifier keys) In Alfred, all that shows up are the 🏷 keyword and 📄 abstract icons.
What can I do to make Alfred recognise the literature note in Obsidian and the PDF that's linked in BibDesk? Is there any rule for the citations?
Also notable information: my PDFs are stored on a server. They can be easily accessed from the button in BibDesk, but not from anywhere else currently.
Relevant Screenshot
No response
To Reproduce
No response
Debugging Log
i can't get the workflow to open when the debugger is turned on. supercharged citation picker just stops showing up

Sample BibTeX Entries
@book{White1976Plato-on-Knowle,
	author = {White, Nicholas P.},
	booktitle = {Plato on Knowledge and Reality},
	date-added = {2024-05-27 10:42:12 +0300},
	date-modified = {2024-05-27 10:42:55 +0300},
	place = {Indianapolis},
	publisher = {Hacket Publishing Company},
	title = {Plato on Knowledge and Reality},
	year = {1976},
	bdsk-file-1 = {YnBsaXN0MDDSAQIDBFxyZWxhdGl2ZVBhdGhYYm9va21hcmtfED8uLi8uLi8uLi8uLi8uLi9Wb2x1bWVzL2hvbWUvcGFwZXJzL3doaXRlMTk3NnBsYXRvLW9uLWtub3dsZS5wZGZPEQSQYm9va5AEAAAAAAQQMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAsAMAAAcAAAABAQAAVm9sdW1lcwAEAAAAAQEAAGhvbWUGAAAAAQEAAHBhcGVycwAAHAAAAAEBAAB3aGl0ZTE5NzZwbGF0by1vbi1rbm93bGUucGRmEAAAAAEGAAAEAAAAFAAAACAAAAAwAAAACAAAAAQDAACzQQAAAAAAAAAAAAABCgAAEAAAAAEGAABsAAAAfAAAAHwAAAB8AAAACAAAAAAEAABBxgHeuvVMChgAAAABAgAAAQAAAAAAAAAPAAAAAAAAAAAAAAAAAAAAFQAAAAEJAABmaWxlOi8vL1ZvbHVtZXMvaG9tZS8AAAAIAAAABAMAAACgmZl7AwAACAAAAAAEAABBxcmfqPwvYhgAAAABAgAAAAAAAAAAAADvEwAAAQAAAAAAAAAAAAAADQAAAAEBAAAvVm9sdW1lcy9ob21lAAAANAAAAAEJAABzbWI6Ly9zaWFpbmJ1bGV0aW5AU2lhLVN5bm9sb2d5Ll9zbWIuX3RjcC5sb2NhbC9ob21lCAAAAAEJAABmaWxlOi8vLwwAAAABAQAATWFjaW50b3NoIEhECAAAAAQDAAAAUAZeOgAAAAgAAAAABAAAQcX1BKwAAAAkAAAAAQEAAEI1MkJGOUM3LTMxMDAtNEZDNC05N0RDLUY4QUY2Nzc5RDkyMRgAAAABAgAAgQAAAAEAAADvEwAAAQAAAAAAAAAAAAAAAQAAAAEBAAAvAAAAYAAAAP7///8A8AAAAAAAAAcAAAACIAAAEAIAAAAAAAAFIAAAgAEAAAAAAAAQIAAAkAEAAAAAAAARIAAAxAEAAAAAAAASIAAApAEAAAAAAAATIAAAtAEAAAAAAAAgIAAA8AEAAAAAAAAEAAAAAwMAAADwAAAEAAAAAwMAAAAAAAAEAAAAAwMAAAEAAAAUAAAAAQYAAIQCAACQAgAAnAIAAJACAACQAgAA4wAAAAECAAA3OTFjYWZhZDY4NTdlMjE2MTkwMTcyNmU1OTZiZGYwMDlkYWFmMThjM2IwN2MzYTkwYzc0MDY5MDhjMzVmYzY3OzAwOzAwMDAwMDAwOzAwMDAwMDAwOzAwMDAwMDAwOzAwMDAwMDAwMDAwMDAwMjA7Y29tLmFwcGxlLmFwcC1zYW5kYm94LnJlYWQtd3JpdGU7MDE7MzYwMDAwMDI7MDAwMDAwMDAwMDBlOTc2MjswYzsvdm9sdW1lcy9ob21lL3BhcGVycy93aGl0ZTE5NzZwbGF0by1vbi1rbm93bGUucGRmAACoAAAA/v///wEAAAAcAgAADQAAAAQQAABUAAAAAAAAAAUQAACEAAAAAAAAABAQAACsAAAAAAAAAEAQAACcAAAAAAAAAAAgAACoAgAAAAAAAAIgAAAsAQAAAAAAAAUgAADMAAAAAAAAABAgAAAUAAAAAAAAABIgAADsAAAAAAAAABMgAAD8AAAAAAAAACAgAAAMAQAAAAAAAFAgAABEAQAAAAAAAIDwAADEAgAAAAAAAAAIAA0AGgAjAGUAAAAAAAACAQAAAAAAAAAFAAAAAAAAAAAAAAAAAAAE+Q==}}

@incollection{Kelsey2000Recollection-in,
	author = {Kelsey, S.},
	booktitle = {Proceedings of the Boston Area Colloquium in Ancient Philosophy},
	cited-by = {Campbell2022The-Souls-Tool:},
	date-added = {2024-05-26 22:27:45 +0300},
	date-modified = {2024-05-26 22:28:41 +0300},
	pages = {91--121},
	title = {Recollection in the Phaedo},
	volume = {16},
	year = {2000}}

Buffer Files
buffer.json
last_version.txt
Workflow Configuration

Checklist

[X] I have updated to the latest version of this workflow.
[X] I have tried manually reloading the buffer (Alfred keyword scp, select Force Buffer Reload).

What can I do to make Alfred recognise the literature note in Obsidian and the PDF that's linked in BibDesk? Is there any rule for the citations?

Well, the literature note and the PDF must be exactly named like the citekey. From the screenshot, it looks like this is not the case for either. So I assume the problem is indeed the citekey.
Unfortunately, I do not use BibDesk, and therefore cannot help much here, sorry. Better ask at some BibDesk forum how to fix that problem? Otherwise, I do not really see much that I can help on my end.


Label image disappears when performing clustering on timelapse data

Steps to reproduce:

Fresh installation of Napari following the instructions of https://biapol.github.io/blog/mara_lampert/getting_started_with_mambaforge_and_python/readme.html
Import label_image.tif contained in label_image.zip (zip file contains file label_image.tif, which github did not allow to upload directly)

The same label may occur in multiple frames.

Load measurements contained in
measurements.csv using Tools > Measurements > Load from CSV

The same label may occur in multiple frames. However, the combination label-frame is unique.

When plotting two features, e.g. Branch Sinousity and Branch displacement and making a selection, the original label image label turns black (which is unexpected) and the id layer does not really show the results.

When using the 2D-view (i.e. multiple slices per timepoint), the selection performed in the cluster plotter widget seems to be shown correct. However, the original label image is still black.
It is a bit unclear to me, if the provided data is not sufficient or if there actually is a bug in Napari Cluster Plotter

Hi @stefanhahmann !
A quick thing I could notice is that you have a label 0 in the table. The 0 usually refers to the background, so I think you should avoid having that. Maybe you have to increment all labels. This may be at least part of the problem.
To better investigate that, you could check the checkbox "Show selected" on the top-left. This should allow you to check which row of the table correspond to which object, like shown in the first gif here. I am not sure if this works with time-lapse data, but I would expect it does.

Hi @stefanhahmann !
A quick thing I could notice is that you have a label 0 in the table. The 0 usually refers to the background, so I think you should avoid having that. Maybe you have to increment all labels. This may be at least part of the problem.

Thanks for pointing this out. The label 0 caused the problem. After incrementing everything by 1 (i.e. the labels in the image and the labels in the corresponding table), it works as expected:

However, the effect that the label image disappears after the cluster plotter has been used for the first time, still feels like a bug to me.

To better investigate that, you could check the checkbox "Show selected" on the top-left. This should allow you to check which row of the table correspond to which object, like shown in the first gif here. I am not sure if this works with time-lapse data, but I would expect it does.

Thanks for the hint. I can confirm that this works for timelapse data.

I close this issue in favor of: https://github.com/BiAPoL/napari-clusters-plotter/issues/271


chore: update pasta gpg key to reflect new subkeys

Issue being fixed or feature implemented
I've added 2 subkeys to my GPG key 29590362EC878A81FD3C202B52527BEDABE87984 to better follow best practices, which avoids using your primary key whenever possible. All future git commit signing, and potentially releases will be signed by a subkey instead of the primary key.
These updated subkeys keys are now included on all the major keyservers
hkps://keyserver.ubuntu.com
hkps://pgp.mit.edu
hkps://keyserver.ubuntu.com
keybase has 1 of the 2 subkeys already, will add the other soon.
What was done?
How Has This Been Tested?
Breaking Changes
Users who validate my signatures may have to refresh the key from keyservers via gpg --refresh-keys or pull down from keybase via curl https://keybase.io/pasta/pgp_keys.asc | gpg --import
Checklist:

[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added or updated relevant unit/integration/functional/e2e tests
[ ] I have made corresponding changes to the documentation
[x] I have assigned this pull request to a milestone (for repository code-owners and collaborators only)

keys do not match https://keybase.io/pasta/pgp_keys.asc?fingerprint=29590362EC878A81FD3C202B52527BEDABE87984 🤷♂

keys do not match https://keybase.io/pasta/pgp_keys.asc?fingerprint=29590362EC878A81FD3C202B52527BEDABE87984 🤷♂

Imported via keybase:
pub  rsa4096/52527BEDABE87984
     created: 2019-08-14  expires: 2026-08-16  usage: SC
     trust: unknown       validity: unknown
sub  rsa4096/99F8136674CE12CB
     created: 2019-08-14  expires: 2026-08-16  usage: E
sub  ed25519/E2F3D7916E722D38
     created: 2024-09-26  expires: 2026-09-26  usage: S
sub  ed25519/CDDEA7E911316053
     created: 2024-09-26  expires: 2026-09-26  usage: S
[ unknown] (1). Pasta<EMAIL_ADDRESS>[ unknown] (2)  Pasta (See keybase.io/pasta for proofs on my identify. 60ACF70BF712645049EE6F15EFEAF16686225F64 is my offline only GPG key.)
[ unknown] (3)  Pasta<EMAIL_ADDRESS>
imported from this PR
pub  rsa4096/52527BEDABE87984
     created: 2019-08-14  expires: 2026-08-16  usage: SC
     trust: unknown       validity: unknown
sub  rsa4096/99F8136674CE12CB
     created: 2019-08-14  expires: 2026-08-16  usage: E
sub  ed25519/E2F3D7916E722D38
     created: 2024-09-26  expires: 2026-09-26  usage: S
sub  ed25519/CDDEA7E911316053
     created: 2024-09-26  expires: 2026-09-26  usage: S
[ unknown] (1). Pasta<EMAIL_ADDRESS>[ unknown] (2)  Pasta (See keybase.io/pasta for proofs on my identify. 60ACF70BF712645049EE6F15EFEAF16686225F64 is my offline only GPG key.)
[ unknown] (3)  Pasta<EMAIL_ADDRESS>
They appear to match to me based on this? maybe some metadata is in a different order or something? I'm not sure I guess if desired, I could update this one to match the keybase one exactly?

keys do not match https://keybase.io/pasta/pgp_keys.asc?fingerprint=29590362EC878A81FD3C202B52527BEDABE87984 🤷♂

...
They appear to match to me based on this? maybe some metadata is in a different order or something? I'm not sure I guess if desired, I could update this one to match the keybase one exactly?

I think ideally they should match exactly. Makes it easier to verify.


About a code problem

Hello, when I read your code, there is problem.
In your code, SelfReg-main/codes/utils.py line 224-226
if is_self_reg:     output, feat = model.extract_features(x)     proj = model.projection(feat) elif is_positive_pair:     output, feat = model.extract_features(x1)     output2, feat2 = model.extract_features(x2)
I want to know the function about elif, what the is_positive_pair is and x1, x2 is what,
Wish your respond.

Hi, @ToxicDoubleH !
I'm sorry for the confusion.
Those codes are traces of what I was researching in the past. ( is_positive_pair condition )
I thought I deleted it, but it's still there. :(
I'll clean it up properly when I clean up the code later.
Thank you for your interesting in our research.

Thank you for your respond! Sorry for 2 days later.
Yours a nice job!
And there is an other question. Your batchsize is 128, and PACS has only 7 classes, each class may have 18 imges. So if a dataset does not have so many images for a single class. Does it works? You say that negative pairs is damage, can your work be worked with negative pairs, such as triplet loss?
Wish your respond.

Dear @ToxicDoubleH
As you know, SelfReg doesn't use negative pairs.
I think SelfReg will work, if you want to use Selfreg with negative pairs.
But then, there may not be much difference between SelfReg and triple loss.
Thank you.

Thanks for your respond. I got it.


Update MQTT library and API models

Issue #4
These changes are intended to make it possible to use the wss and mqtts protocols...
Does any other change need to be implemented?
In the future, the back-end API needs to receive certificates and provide them to the MQTT client
Example: https://github.com/mqttjs/MQTT.js/issues/1011#issuecomment-645503247
Shall we use MQTT.js to connect to AWS brokers? Things may have changed, but an issue from 2018 says it's not possible: https://github.com/mqttjs/MQTT.js/issues/747#issuecomment-355491210

Hello @Wdestroier
thanks you for your contribution!
It seems you only changed the versions in package.json but did not run yarn after your change. Please do this at least, then make sure everything starts up fine.
Repository sensebox/openSenseMap-API contains a test suite which also tests the communication between the api and this project. Check these instructions
Once the test suite works with the changes in your PR, we can merge :)

Hi, Gerald! Thanks, I will look into it.

Hi all,
I have opened up a second PR https://github.com/sensebox/mqtt-osem-integration/pull/7 for updating MQTT and also GRPC libraries. Started it before my holidays.
The PR is already deployed on our testing environment and successfully connected to HiveMQ by mqtts.
Still there is some work to do in our API repository https://github.com/sensebox/openSenseMap-API
But I hope we can get the changes to production next week.

@ubergesundheit I've ran the tests and it is working the same way as before the changes... I'm not sure the if the API tests are passing, because there are no logs in the terminal.
Logs:

@mpfeil is working on the same issue and it's already in the test environment, should I close this pull request?

@Wdestroier we can close this one in favor of #7
if you want to try if the new mqtt integration is working. you can register at https://testing.opensensemap.org
It´s running the latest api and mqtt integration.


Change bacalhau serve so it can be run without any arguments

Would be nice if bacalhau serve just worked everywhere with no args. Then we could have a simple k3s-like installer (maybe with nicer UX 😉).

duplicate of #1231


Security fix

Security fix

We could look at archiving this if it is no longer maintained/needed @SEQUOIIA @ZaradarDFDS

Spoken to @ZaradarDFDS he thinks it is still relevant.


[Editable] cannot delete text when max-length reached

🐛 Bug report
I was playing around with Ark components until I've noticed <Editable> component doesn't work properly when using maxLength prop, even if you keep hitting the backspace it doesn't type or erase anything, I've look in the code and thought this my related to zag:
https://github.com/chakra-ui/zag/assets/30840709/08985ddd-c30b-4a7e-8483-4880516bb657
💥 Steps to reproduce

Write a component either if <Editable> or using @zag-js/editable directly
Add maxLength 10
Keep typing...
Try to delete using backspace

💻 Link to reproduction

Stackblitz
🧐 Expected behavior
Characters in the editable input should be deleted as I press backspace
🧭 Possible Solution
Not entirely sure, but maybe it's related to TYPE event in the machine 🤔:
https://github.com/chakra-ui/zag/blob/99c5a68890058b26f1d39ac25081ab8d3a6a96b6/packages/machines/editable/src/editable.machine.ts#L75-L80
🌍 System information

Software
Version(s)

Zag Version

Browser

Operating System

📝 Additional information

Good catch @jeferson-sb.
I just pushed a fix for this. We'll release an update shortly.
If the issue persists after upgrading, I'll re-open it.


How to create a theme? tutorials are missing

I want to get tips about how to create a theme, but the page is missing, please help.
the missing page: https://gohugo.io/tutorials/creating-a-new-theme/

Where did you find the URL? It does not seem to exist. And, please post issues like this at gohugoio/hugoDocs

@peaceiris  Thanks a lot!  I didn't find topics about creating themes on gohugo.io, so I get the URL above by search "how to create hugo theme" on google


Inconsistent coloring of JSON formatted content files in default editor

VSCode Version: Version 1.11.0-insider (1.11.0-insider) 05f19eec2042555ca04e5f014befa95248a65fe9
OS Version: 10.12.3 (16D32) (mac OS Sierra)

Steps to Reproduce:

open launch.json file in VSCode
open users settings settings.json in VSCode
Use default dark VS theme

Sorry if that is reported already but I couldn't find using expected keywords.
I've noticed that the syntex rendering is inconsistent between files in recent versions of VSCode.
Here are the screenshots of JSON formatted files, both with extra comments and both in VSCode launched without extensions enabled:

launch.json:

settings.json

What's more interesting. If I copy and paste content of launch.json into the panel of users settings the rendering will be OK, so that seems to be not related to the content of JSON file:

Thanks!

In the launch.json we deemphasise (grey out) some attributes based on their semantics to improve the usability.
So what you see is the desired behaviour.
/cc @isidorn

Thanks! But that enhancement leads me to think there is an error. I'm used to think such rendering is a problem in Atom:
https://github.com/atom/atom/issues/10203
or in VSCode:
https://github.com/Microsoft/vscode/commit/0cffe5f8a7c26ea428e917d5d22151fbd68f5257

Don't want to be a jerk, just for self-note. I can see the same coloring on the documentation page. But I cannot read the reason behind such coloring:
https://code.visualstudio.com/docs/editor/debugging

@peterblazejewicz please see https://code.visualstudio.com/updates/v1_7#_node-debugging.
This is the outcome of user studies that took place to understand why user have difficulties to setup debugging.

bingo! Thanks and sorry for being PITA!


Keep orderedness information of lists

I was wondering if it is possible to know whether a <list> in the extracted output came from an
 or an
. Even with include_formatting (which I don't need), this information is omitted.
I saw that , for instance, retains the level in the rend attribute. A similar attribute would be handy in <list> as well.
On a related note, description lists (
s) are handled even worse, as both
s and
s are extracted as separate <item>s. Something like this:

dt1: dd1
dt2: dd2

would probably serve the purpose better.

Hi @DavidNemeskey, thanks for your feedback. It is definitely doable, I would split your remark into two parts:

[ ] add type information to <list>, possibly in a rend attribute
[ ] check extraction order of
 elements and (optionally) add a numbered attribute

@adbar thanks, that would be great. Let me know if can be of any help.

Hi @DavidNemeskey, I believe I addressed both concerns, does that work for you?

Will take a look in a few days, thanks!


Self-close tags

As I see hyntax cannot parse self-close custom tags https://astexplorer.net/#/gist/1f1cf8a9a27f821c3a0273dc5b269036/71c30bb3d449100886cb2ebf0a594fdd54135e38 ?
Do you plan any support of this?

Those are not really part of the HTML standard, the only possible self-closing tags by the specs are so-called void elements, which are area, base, br, col, embed, hr, img, input, link, meta, param, source, track, wbr. So unless HTML standard changes, I'm not going to add support for this.
One thing you could do, even though it's not easy, is to create a custom tree constructor. tokenize() function returns an array of raw tokens and you can pass this array to a custom AST builder that supports custom syntax like <custom-tag />.

You can check that browsers also don't support such syntax.
Code:

Browser output:

Don't know what is your exact usecase, but might be you don't even need such tags as browsers won't be able to parse them correctly.

Well It's for vue, angular frameworks. But anyway thank you.

But I want to note that the parser stopped parsing html at one point when it encountered an unregistered void tag. The readme.md says that you can write any invalid html)

Yes, it should continue parsing anyway. Could you provide HTML you're trying to parse?

Well It's for vue, angular frameworks. But anyway thank you.

Ok, I understand. Those frameworks, along with React's JSX use their own custom syntax, which looks like an HTML but with additional features outside of HTML specs. They use their own custom parsers.

Oh, sorry. I looked up in the ast tree better and not found a mistake.
I close this issue. I think I need to change parser because of my circumstances


Web patch

Pins new dependencies and fixes a few bugs in the LDC and contam tool.

Hi @nespinoza ! I updated a few deprecated package build settings (including renaming several files) and got the builds working. I also found a few Web app bugs that don't get caught in the pytest tests but I found when I tried to test drive it. If you could sign off on this when you get a chance, I'd appreciate it!

Plus, this has to be merged with develop before develop is merged with master.


az connectedk8s enable-features --features cluster-connect failes as helm 3.7 removed chart command

Describe the bug
Command Name
az connectedk8s enable-features Extension Name: connectedk8s. Version: 1.1.10.
Errors:
Unable to pull helm chart from the registry 'mcr.microsoft.com/azurearck8s/batch1/stable/azure-arc-k8sagents:1.4.0': Error: unknown command "chart" for "helm"
Run 'helm --help' for usage.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

AKS HCI cluster connected through Azure ARC
az connectedk8s enable-features --features cluster-connect -n {} -g {}

Expected Behavior
complete feature activation like helm 3.6.3. Since in Helm 3.7.0 chart command has been removed, this does not work anymore.
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.28.0

Extensions:
connectedk8s 1.1.10

Additional Context

I saw it is referenced here: https://docs.microsoft.com/en-us/azure/azure-arc/kubernetes/troubleshooting#azure-cli-is-unable-to-download-helm-chart-for-azure-arc-agents

route to service team

@Banchio ,
For the time being, please use the mitigation suggested in the link you pasted above. We will soon release a fix for this issue and let you know

@Banchio
This issue has been fixed in the latest release of connectedk8s CLI. (version 1.1.11)
Please upgrade using the cmd 'az extension update -n connectedk8s' ant try again.
Note that the 1.1.11 version of the CLI no longer has dependency on the helm client installed by the user. The CLI, during runtime will download a suitable helm version and use it.
'Helm' is no longer a pre-requisite for the connectedk8s CLI


Feature/refactor

Adjusted 'Create' and 'Update' methods in services.
'Version' is now required on Am models.
Removed 'FirstVersionId' from Am models.
Fixed tests that failed after adjustments to Am models
Fixed client after adjustments to Am models updated mimirorg packages).

Fantastisk bra @kahovden 👍


fix: Fixed tests failing you check out with \n on windows.

coverage: 91.909%. remained the same
when pulling 9ba37b7123fe210f0bc8ec4c029610efdb0bb454 on ITR13:newline-fix
into e3891871f6dba1ec6d94f06e4827755d21f0f75c on SamboyCoding:master.


Move off of ReadMe.io

Must be GitHub based
Must be Markdown based

Top candidate is Docusaurus, possibly served via GitHub pages

I'm taking the lead on this, hopefully with the help of @kaichaosun.
Here's the motivation and plan for moving https://docs.google.com/document/d/1Gq0a7jFMjL1txpm21twBCLg6dcEs5SWidD3cifwfPZE/edit#
I hope to make more progress this week and will update the plan. I hope to use this issue moving forward.

I'm working on translation and localization by following the guide:
https://docusaurus.io/docs/en/translation

Summary about how to do the localization:
doc
TODO:

[x] Enable translation and localization in Docusaurus
[ ] Create Crowndin project with the proper account, it should be the admin of this repo, better not to use a personal account.
[ ] Integrate with CI, blocked by Crowndin account creation.
[ ] Discuss around version control.

@kaichaosun Looks awesome. I've approved you PR to enable l10n. FYI for the CI portions were using circleci.com. Checkout the /circleci/config.yml. I'll be happy to help with getting it to work with crowdin.
@shawntabrizi Let's capture our discussion from riot in here.

You're suggesting we move this repo to substrate-developer-hub.github.io so it is our "org page". That means docusaurus would build to master, and we would do our work on source branch. We can change our github default branch to be source branch.

I'm fine with all that. Please confirm that I understood correctly.

Actually, I've broken the scope of this task down into more manageable issues and put them in the "Migrate to Docusaurus" milestone.
@kaichaosun let's track the l10n progress in https://github.com/substrate-developer-hub/docs/issues/84


Listen for https errors

Reviewer:

Description:

Listen for https upgrade errors to remove bad upgrades.
Steps to test this PR:
Easiest way to find broken https upgrades is to:

Build a dev version of the extension.
Open the extension console and set the https whitelist to an empty list
window.dbg.https.whitelist = []
Navigate to some sites that were on the whitelist. They should be completely broken now.

Automated tests:

[ ] Unit tests
[ ] Integration tests

Reviewer Checklist:

[ ] Ensure the PR solves the problem
[ ] Review every line of code
[ ] Ensure the PR does no harm by testing the changes thoroughly
[ ] Get help if you're uncomfortable with any of the above!
[ ] Determine if there are any quick wins that improve the implementation

PR Author Checklist:

[ ] Get advice or leverage existing code
[ ] Agree on technical approach with reviewer (if the changes are nuanced)
[ ] Ensure that there is a testing strategy (and documented non-automated tests)
[ ] Ensure there is a documented monitoring strategy (if necessary)
[ ] Consider systems implications

Thanks for the changes, looks good to me now 👍


Turtlebot 4 Cannot charge without power to payload

According to all Clearapth manuals and Create 3 manual, there is no way to charge the TB4 without the payload active.
Considering the RPLidar uses a belt, ( just a bit better than the rubber bands used in previous models) the device will wear out due to mechanical wear prematurely as it will operate continually in charging and device operation.
Other than to unplug the lidar or the entire payload (remove card from storage bay). There really should be an option to shutdown the payload during charging. ( say set a sleep or time-out function.)
Its clear this was overlooked during the design of the Turtlebot 4.

duplicated with 299, Closed as it was not bug or feature.


[Bug]: Backup failures with unexpected error messages

What happened?
Backup invocation of multiple users at a time is showing unexpected errors:
maximum retries or unretryable:  BadRequest Unsupported request: Change tracking is not supported against 'microsoft.graph.event'.: error status code received from the API

maximum retries or unretryable:  BadRequest Unsupported request: Change tracking is not supported against 'microsoft.graph.message'.: error status code received from the API

maximum retries or unretryable:  ErrorInvalidUser The requested user 'contactFolders' is invalid.: error status code received from the API

Corso Version?
Corso v0.3.0 but I will confirm
Where are you running Corso?
Linux
Relevant log output
No response

More investigation is required as the sequence of failures appears in Mail, Contacts, and Calendars.

Closing - no reported or observed repros


Fixed: Show more monitors in CNS on very large displays #6503

Proposed Changes

Fixes #6503

@ohcnetwork/care-fe-code-reviewers
Merge Checklist

[ ] Add specs that demonstrate bug / test a new feature.
[ ] Update product documentation.
[X] Ensure that UI text is kept in I18n files.
[X] Prep screenshot or demo video for changelog entry, and attach it to issue.
[X] Request for Peer Reviews
[ ] Completion of QA

Summary by CodeRabbit

New Features

Enhanced responsiveness of the Central Nursing Station component by dynamically adjusting the number of items displayed per page based on window size.

Bug Fixes

Improved pagination functionality to better accommodate various screen widths.

Style

Updated grid layout class for improved adaptability to different display sizes.

@rithviknishad ,is it okay now

Closing as duplicate of #9013


Fix "Open File Location" function

fixes #616

It also syncs the dev server working folder with the dist's one

Thanks!


Error on load and connection

First error is because you're setting Skungee to load on a port that is already in use, that is user error. Try a different port, and remember the port is not the same as the Bungeecord/Server port, it's gotta have it's.own dedicated open port.
Second error will be looked into.

Yes, the 1rst error is because I've tried to make a test in another bungeecord server because in my principal bungeecord I've got the second problem with skungee and network variables and skungee skripts are bug.

I start bungeecord and when it pass 1 minute it send that and all network variable skripts stop working and bugs all skungee skripts.

Global scripts and network variables will be working, this is not related.

I've see and when this error appear in bungee all network variables on /plugins/Skungee/variables remove the contents of variables.csv

Fixed in next version.

Thanks, and when will be the next version released?

1.0.13 which was just released.

Mm I think it happens now too, Do I need to restart all servers with skungee?

This still occurs for me as well:
https://github.com/Skungee/Skungee/issues/167


"DataType" Sampling shoulnd't be mandatory

In 1.0RC8 "DataType Sampling" shoulnd't be mandatory as it contains only optional elements. Cardinality to be changed to [0..1].

Included for next version


Support version 0.9.0

Hello and thanks for an awesome role!
This is a patch to support v0.9.0. The filename does not have the "v" from v0.9.0..
Tested on Debian 10 with Postgres 11. Metrics are collected.
Those extra metrics are now all in the queries.yml in upstream https://github.com/prometheus-community/postgres_exporter/blob/master/queries.yaml so maybe we could also remove those extra files in this role? Thoughts?

(base) /tmp $diff queries-upstream.yml queries-default.yml
0a1,6
> # {{ ansible_managed }}
>
> ######################################################################
> # Copied from
> # https://github.com/prometheus-community/postgres_exporter/blob/677d38bc5d652ad1882e80f8aed5dd23b46e958b/queries.yaml
>

heh. Indeed!

Made a few changes, hoping it goes better now? :)
Sure are a lot of whitespaces and such in the file in the exporter repo.

@joshmoore seems the linting issues are still there. Any preference for how to tackle this ?
We could:

exclude this file from linting
modify the file so it doesn't
some other way i have t figured out :)

so maybe we could also remove those extra files in this role?

How would you propose dropping the duplicated file altogether?

so maybe we could also remove those extra files in this role?

How would you propose dropping the duplicated file altogether?

This made me realize that I should not have bundled updating queries.yml with support for version 0.9.0 of the exporter.
Sorry about the mess.
Force pushed and removed updates to queries.yml. I need to double-check and confirm that, maybe with a future update.

Sorry about the mess.

No worries. Happy to look at the query update next.

Force pushed

:+1: Just one small issue:
Error: [line-length] line too long (87 > 80 characters)

Will this be merged any time soon?
Thanks!

Sorry, the workflows didn't auto-launch. I've done so now. If everything is green, propose to release as 0.5.0.

Sorry, still failing on:
Error: [line-length] line too long (87 > 80 characters)

@martbhell I've made a PR to fix the above issue in your repo.

Thanks, @serpa-dystematic . I went ahead and pushed and am re-running the workflows.

Thanks @joshmoore, looks good now! 😄


Add Support for HTTPS

Hello guys, i made all these changes but i cannot run this app with https. After all these changes i should configure apache2 for ssl ?

Hey guys,
I’m sorry I haven’t maintained this project as well as I should, it seems
like several people have forked the repo and added changes. I will review
the code this weekend and commit a new version afterwards. Thanks for all
your guys work!
~ Matt May
On Thu, Mar 15, 2018 at 10:13 AM Poulis Vassilis<EMAIL_ADDRESS>wrote:

Hello guys, i made all these changes but i cannot run this app with https.
After all these changes i should configure apache2 for ssl ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MatthewClarkMay/geoip-attack-map/pull/20#issuecomment-373389660,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AP6p9f5QJ7jTAFriRMjszOA0T4mLqD9rks5tencMgaJpZM4QYU4_
.

Hello Matthew
i found a guy with this blog
https://samiux.blogspot.gr/2016/12/traffic-and-attack-map-for-suricata.html
i dont know if you have in mind!
I contact him and he send me some files moderated that way so the map can
read data from suricata IDS with parse method to eve.json.
He told me that he abandoned this project but i told him to send me the
files and that i won't bother him again.
I build it that way and i can tell that i have real time data!
I don't want to upload a code in github that it isn't mine, so if you want
i can send you everything to refresh yours.
I like this project very much and i make some changes on my one most of all
in layout, map, etc.
I wrote a script so i can change me external ip inside python scripts and
restart.sh for easy restarts.
I'm new in programming and if you like we can keep contact. I use a lot
Discord, Telegram apps.
Also forgive me for my English if i make mistakes.
I have the map online many hours the day if you like to see
vppoulis.ddns.net:8888
I live in Greece so i don't know if we have common free hours
Thanx
2018-03-15 22:40 GMT+02:00 Matthew May<EMAIL_ADDRESS>
Hey guys,
I’m sorry I haven’t maintained this project as well as I should, it seems
like several people have forked the repo and added changes. I will review
the code this weekend and commit a new version afterwards. Thanks for all
your guys work!
~ Matt May
On Thu, Mar 15, 2018 at 10:13 AM Poulis Vassilis<EMAIL_ADDRESS>
wrote:

Hello guys, i made all these changes but i cannot run this app with
https.
After all these changes i should configure apache2 for ssl ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/MatthewClarkMay/geoip-attack-
map/pull/20#issuecomment-373389660>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AP6p9f5QJ7jTAFriRMjszOA0T4mLqD9rks5tencMgaJpZM4QYU4_>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MatthewClarkMay/geoip-attack-map/pull/20#issuecomment-373515716,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIt7vfs3PnVrafLdZHWZtkguAISVR-sxks5tetHEgaJpZM4QYU4_
.


Firebase auth plugin crash IOS and android

Hi,
I'm trying to use the Firebase auth plugin for my app, but after installing everything as explained in the firebase docs and running it, it crash on both Android and IOS.
My pubspec.yaml:
dependencies:
  google_sign_in: ^4.0.0
  firebase_auth: ^0.8.0+1

Crash on IOS:
Launching lib/main.dart on iPhone XS Max in debug mode...
Xcode build done.                                            7.3s
*** First throw call stack:
(
	0   CoreFoundation                      0x000000010576329b __exceptionPreprocess + 331
	1   libobjc.A.dylib                     0x0000000104cff735 objc_exception_throw + 48
	2   CoreFoundation                      0x00000001057630f5 +[NSException raise:format:] + 197
	3   Runner                              0x00000001019449f0 +[FIRApp configure] + 576
	4   Runner                              0x00000001019a3e3c -[FLTFirebaseAuthPlugin init] + 188
	5   Runner                              0x00000001019a3cad +[FLTFirebaseAuthPlugin registerWithRegistrar:] + 173
	6   Runner                              0x00000001018e9c4b +[GeneratedPluginRegistrant registerWithRegistry:] + 123
	7   Runner                            <…>

Crash on android:

Launching lib/main.dart on ONEPLUS A5010 in debug mode...
Initializing gradle...                                       1.0s
Resolving dependencies...                                    2.3s
Gradle task 'assembleDebug'...
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:9: error: cannot find symbol
import androidx.annotation.NonNull;
                          ^
  symbol:   class NonNull
  location: package androidx.annotation
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:10: error: cannot find symbol
import androidx.annotation.Nullable;
                          ^
  symbol:   class Nullable
  location: package androidx.annotation
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:638: error: cannot find symbol
  private void reportException(Result result, @Nullable Exception exception) {
                                               ^
  symbol:   class Nullable
  location: class FirebaseAuthPlugin
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:550: error: cannot find symbol
    public void onComplete(@NonNull Task<AuthResult> task) {
                            ^
  symbol:   class NonNull
  location: class FirebaseAuthPlugin.SignInCompleteListener
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:569: error: cannot find symbol
    public void onComplete(@NonNull Task<Void> task) {
                            ^
  symbol:   class NonNull
  location: class FirebaseAuthPlugin.TaskVoidCompleteListener
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:587: error: cannot find symbol
    public void onComplete(@NonNull Task<SignInMethodQueryResult> task) {
                            ^
  symbol:   class NonNull
  location: class FirebaseAuthPlugin.GetSignInMethodsCompleteListener
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:186: error: cannot find symbol
                      public void onComplete(@NonNull Task<AuthResult> task) {
                                              ^
  symbol: class NonNull
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:445: error: cannot find symbol
              public void onComplete(@NonNull Task<GetTokenResult> task) {
                                      ^
  symbol: class NonNull
/Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java:499: error: cannot find symbol
          public void onAuthStateChanged(@NonNull FirebaseAuth firebaseAuth) {
                                          ^
  symbol: class NonNull
Note: /Users/theo/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_auth-0.8.0+1/android/src/main/java/io/flutter/plugins/firebaseauth/FirebaseAuthPlugin.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
9 errors

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':firebase_auth:compileDebugJavaWithJavac'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s

Gradle task 'assembleDebug'... Done                          5.4s
Gradle task assembleDebug failed with exit code 1

flutter doctor -v
[✓] Flutter (Channel stable, v1.0.0, on Mac OS X 10.14 18A391, locale en-AU)
    • Flutter version 1.0.0 at /Users/theo/flutter
    • Framework revision 5391447fae (9 weeks ago), 2018-11-29 19:41:26 -0800
    • Engine revision 7375a0f414
    • Dart version 2.1.0 (build 2.1.0-dev.9.4 f9ebf21297)

The Android error is caused by the migration to AndroidX. Check this comment on how to resolve that issue: https://github.com/flutter/flutter/issues/27106#issuecomment-458366675
Have you followed to iOS integration guide from the google_sign_in plugin? https://pub.dartlang.org/packages/google_sign_in

@theochampion
I was getting these errors as well. See if these steps help. At the moment, I can only confirm that both the iOS and Android versions of my app build successfully. I have not yet had a chance to test how thoroughly they are working properly with Firebase. If anyone with more knowledge than I sees anything that shouldn't be done the way I am suggesting or should be done differently, please let me know. The intent of this is to do good, not harm.

Note: I'm using IntelliJ Idea CE. If you are using VSCode or the command line, you will have to adjust accordingly. Also, I create my Flutter projects with Kotlin and Swift. So, if you are creating yours with Java and/or Objective-C, you may have to make additional adjustments to these instructions.

iOS
First of all, do not add
import Firebase and FirebaseApp.configure()
to your [my_project]/ios/Runner/AppDelegate.swift file as instructed in the Firebase instructions. This will be handled by the Firebase plugins. If you do have those lines of code, either remove them or comment them out.

Make sure you are using the latest version of the plugins in your pubspec.yaml file (I'm also using firebase_core):

dependencies:
  flutter:
    sdk: flutter
  firebase_core: ^0.3.0
  firebase_auth: ^0.8.0+1
  google_sign_in: ^4.0.0

Run Tools > Flutter > Flutter Packages Get (I ran Tools > Flutter > Flutter Clean first).

If your iOS app has not already been added to your Firebase project, add it and download the GoogleService-Info.plist file. I downloaded mine to [my_project]/ios/Runner, although downloading it there does not install it.

Note: I added GoogleService-Info.plist to my [my_project]/.gitignore based upon the answer to the stackoverflow question Firebase: Should I add GoogleService-Info.plist to .gitignore?.

In your Flutter project, open [my_project]/ios/Runner.xcworkspace in Xcode. In IntelliJ Idea, you can do this by right-clicking the Runner.xcworkspace folder and selecting Flutter > Open iOS module in Xcode.

In Xcode, if you downloaded the GoogleService-Info.plist file to [my_project]/ios/Runner, you will likely still not see it in the Runner project subdirectory. Open a macOS finder window, navigate to the GoogleService-Info.plist in your Flutter project (e.g. ~/IdeaProjects/[my_project]/ios/Runner/GoogleService-Info.plist), click it and drag it to the Runner project subdirectory in Xcode (not the parent Runner workspace directory). Xcode will ask you to confirm, so do so.

Note: I don't recall if this particular confirmation dialogue box contains the dropdown selector for the build method option - Legacy vs New, but if it does, I selected Legacy. This might be important to do. Perhaps someone else can confirm.

Still in Xcode, if File > Save is available (I don't recall if it is because some actions in Xcode don't require saves), then save and quit Xcode. Otherwise, just quit Xcode.

Back in IntelliJ Idea, per the google_sign_in plugin instructions, add the following lines of code to the [my_project]/ios/Runner/Info.plist file:

<!-- Google Sign-in Section -->
<key>CFBundleURLTypes</key>
<array>
  <dict>
    <key>CFBundleTypeRole</key>
    <string>Editor</string>
    <key>CFBundleURLSchemes</key>
    <array>
      <!-- TODO Replace this value: -->
      <!-- Copied from GoogleServices-Info.plist key REVERSED_CLIENT_ID -->
      <string>com.googleusercontent.apps.861823949799-vc35cprkp249096uujjn0vvnmcvjppkn</string>
    </array>
  </dict>
</array>
<!-- End of the Google Sign-in Section -->

I don't know that it matters exactly where amongst the keys in the file you put it. I placed it between these two lines:
<key>LSRequiresIPhoneOS</key>
<true/>
<!-- Google Sign-in Section -->
  .
  .
  .
<!-- End of the Google Sign-in Section -->
<key>UILaunchStoryboardName</key>
<string>LaunchScreen</string>

Open your [my_project]/ios/Runner/GoogleService-Info.plist file, copy the REVERSED_CLIENT_ID string, and paste it into the code you just added to the Info.plist file in the previous step, replacing the sample REVERSED_CLIENT_ID string provided (as indicated in the TODO code comment). Save.

I may have completed these steps with a final pod install in the [my_project]/ios directory in the terminal, although, if I did, I'm not sure it was necessary but felt it couldn't hurt.

After these steps (I don't believe I've left anything out), I opened the iOS Simulator (I'm using iPhone XS Max - 12.1) and ran the app and it built successfully. :smiley:

Note: If I build in Xcode rather than in IntelliJ Idea, I get a number of warnings. All of these warnings, however, are related to code in the plugins. So, I'm not sure there is anything for me to do to address them.

Android

Open the Android portion of your Flutter project in Android Studio. Make sure you are using Android Studio 3.3. (I closed IntelliJ Idea altogether, opened Android Studio, clicked on File > Open, and navigated to the ~/IdeaProjects/[my_project]/android folder in my Flutter project. Upon opening the Android project followed by Android Studio starting to sync it, a message/pop-up appeared asking if it could update the Gradle plugin, so I let it. It was upgraded to version 3.3.0.)

Add the following 2 lines to the bottom of the [my_project]/android/gradle.properties file:

android.useAndroidX=true
android.enableJetifier=true

Note: I'm not sure if android.enableJetifier=true could have been, or should have been, set to false. Perhaps someone else can clarify under which conditions it should be true vs false. I believe it has something to do with whether or not the project has additional libraries that haven't yet been migrated to AndroidX, but, if my belief is correct, I don't know if when this setting is set to true it means Android Studio will migrate these libraries to AndroidX or that it will make code adjustments to account for the fact that the libraries aren't yet AndroidX compatible. Or maybe I'm totally wrong and it is something else altogether.

In the Android Studio main menus, select Refactor > Migrate to Androidx.... Follow this with File > Save All and then quit Android Studio.

If your Android app has not already been added to your Firebase project, add it and download the google-services.json file either directly to the ~/IdeaProjects/[my_project]/android/app subdirectory or elsewhere (e.g. ~/Downloads) and then drag it there in the Finder.

Note: google-services.json was already an entry in my [my_project]/.gitignore file. If it is not in yours, you may want to add it, based upon the answer to the stackoverflow question Firebase: Should I add GoogleService-Info.plist to .gitignore?, since it would seem to apply to this file as well.

Reopen your Flutter project in IntelliJ Idea and update your Kotlin plugin to version 1.3.20, if it has not been previously updated. This is done with IntelliJ IDEA > Preferences > Languages & Frameworks > Kotlin. With Update Channel set to Stable, if a message indicating an updated version is not already visible, clicking the Check again button will reveal if there is an update to the plugin. If you are not currently using 1.3.20, then update to it.

In the [my_project]/android/build.gradle file, change the Kotlin version to match the updated plugin version (the release suffix on the plugin version, e.g. -release-IJ2018.3-1, is not needed):

buildscript {
    ext.kotlin_version = '1.3.20'
	.
	.
	.

Note: Since there are two build.gradle files in the Android version of your app, [my_project]/android/build.gradle and [my_project]/android/app/build.gradle, ensure that you are make code changes to the correct file. This advice may be obvious, but I thought it couldn't hurt to emphasize it.

In your [my_project]/android/app/build.gradle file, make the follwoing changes:

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.2-alpha01'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.2-alpha01'
}

These were code analysis suggestions by IntelliJ Idea. The change in the implementation line to jdk is subtle and perhaps possible to miss.
Change these lines in the [my_project]/android/app/build.gradle file as well (although I don't recall the specific source(s) that recommended them).
android {
    compileSdkVersion 28
    .
    .
    .
    defaultConfig {
        .
        .
        .
        minSdkVersion 21
        targetSdkVersion 28

Either before or after the next step, a pop-up in IntelliJ Idea informed me Kotlin migrations to the new version could be run, so I chose to let it do so.

Per the firebase_auth plugin instructions, add/change the following lines of code in the [my_project]/android/build.gradle file, although I updated the com.android.tools.build:gradle version to 3.3.0 rather than the keeping the 3.2.1  in the instructions (see the last sentence in Step 1 above)) :

dependencies {
  // Example existing classpath
  classpath 'com.android.tools.build:gradle:3.3.0'
  // Existing classpath, unchanged
  classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
  // Add the google services classpath
  classpath 'com.google.gms:google-services:4.2.0'
}

Also per the firebase_auth plugin instructions, add the following line of code to the bottom of the [my_project]/android/app/build.gradle file:

apply plugin: 'com.google.gms.google-services'

After this, in the IntelliJ Idea main menus, I ran Tools > Flutter > Flutter Clean, followed by Tools > Flutter > Flutter Packages Get. As with running a final pod install with the iOS version of the app, I'm not sure this was necessary, but felt it couldn't hurt.

After these steps (once again, I don't think I've left anything out), I opened the Android Emulator (I'm using the Nexus 5X API 28 because it supports Google Play, which I believe is necessary for Firebase) and ran the app and it built successfully. :smiley:
Hope this helps. Cheers!

Even though the Android app was building and connecting to Firebase, I was briefly seeing the
"ERROR: [TAG] Failed to resolve variable '${animal.sniffer.version}'" error, so I added these lines
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

to the [my_project]/android/app/build.gradle file here:
android {
    compileSdkVersion 28

    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
.
.
.

as suggested in Dhaval Patel's answer to the stackoverflow question Failed to resolve variable '${animal.sniffer.version}' when migrate to AndroidX and this appears to have resolved it.

From now on I'm only working in Android Studio for Flutter projects, and doing gradle sync. And create a projects with Kotlin support. And also did migrate to AndroidX from Studio's Refactor menu.
I solved this for now by having in android/gradle.build:
classpath 'com.android.tools.build:gradle:3.2.1' <-- notice version 3.2.1
and
classpath 'com.google.gms:google-services:4.2.0' <-- 4.2.0
and put ext.kotlin_version = '1.3.20'. (Had to update kotlin plugin in studio)
In android/app/gradle.build have same SDK versions as mentioned here but didn't put JavaVersion. And my dependencies are:
implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
testImplementation 'junit:junit:4.12'
androidTestImplementation 'androidx.test:runner:1.1.2-alpha01'
androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.2-alpha01'
implementation 'com.google.firebase:firebase-core:16.0.1'

import androidx.annotation.NonNull;

This looks like #27106

@theochampion
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1117. Any further collaboration will be done there.

@theochampion
I was getting these errors as well. See if these steps help. At the moment, I can only confirm that both the iOS and Android versions of my app build successfully. I have not yet had a chance to test how thoroughly they are working properly with Firebase. If anyone with more knowledge than I sees anything that shouldn't be done the way I am suggesting or should be done differently, please let me know. The intent of this is to do good, not harm.

Note: I'm using IntelliJ Idea CE. If you are using VSCode or the command line, you will have to adjust accordingly. Also, I create my Flutter projects with Kotlin and Swift. So, if you are creating yours with Java and/or Objective-C, you may have to make additional adjustments to these instructions.

iOS
First of all, do not add
import Firebase and FirebaseApp.configure()
to your [my_project]/ios/Runner/AppDelegate.swift file as instructed in the Firebase instructions. This will be handled by the Firebase plugins. If you do have those lines of code, either remove them or comment them out.

Make sure you are using the latest version of the plugins in your pubspec.yaml file (I'm also using firebase_core):

dependencies:
  flutter:
    sdk: flutter
  firebase_core: ^0.3.0
  firebase_auth: ^0.8.0+1
  google_sign_in: ^4.0.0

Run Tools > Flutter > Flutter Packages Get (I ran Tools > Flutter > Flutter Clean first).
If your iOS app has not already been added to your Firebase project, add it and download the GoogleService-Info.plist file. I downloaded mine to [my_project]/ios/Runner, although downloading it there does not install it.

Note: I added GoogleService-Info.plist to my [my_project]/.gitignore based upon the answer to the stackoverflow question Firebase: Should I add GoogleService-Info.plist to .gitignore?.

In your Flutter project, open [my_project]/ios/Runner.xcworkspace in Xcode. In IntelliJ Idea, you can do this by right-clicking the Runner.xcworkspace folder and selecting Flutter > Open iOS module in Xcode.
In Xcode, if you downloaded the GoogleService-Info.plist file to [my_project]/ios/Runner, you will likely still not see it in the Runner project subdirectory. Open a macOS finder window, navigate to the GoogleService-Info.plist in your Flutter project (e.g. ~/IdeaProjects/[my_project]/ios/Runner/GoogleService-Info.plist), click it and drag it to the Runner project subdirectory in Xcode (not the parent Runner workspace directory). Xcode will ask you to confirm, so do so. (Alternatively, you can right-click the Runner project subdirectory and select Add Files to "Runner"... The file selector will already be in the Runner subdirectory, so if you saved the GoogleService-Info.plist file there when you downloaded it, all you need to do is select it and add it.)

Note: I made these additional adjustments while in Xcode: * File > Workspace Settings...: confirmed Build System was set to Legacy Build System* Selected Runner at top of left panel, then Build Settings at top of center panel, entered "Swift" into search box, then set Swift 3 @objc Inference to "Default" (applied to all 3 - Debug, Profile, Release)* Still in Build Settings, entered "iOS" in search box, then set iOS Deployment Target to "12.1"* In right hand panel, under Project Document, set Project Format to "Xcode 10.0-compatible"* Clicked on gold warnings triangle at the top of the center panel, then in the left hand panel on Update to recommended settings and updated to recommended settings.

Quit Xcode.
Back in IntelliJ Idea, per the google_sign_in plugin instructions, add the following lines of code to the [my_project]/ios/Runner/Info.plist file:

<!-- Google Sign-in Section -->
<key>CFBundleURLTypes</key>
<array>
  <dict>
    <key>CFBundleTypeRole</key>
    <string>Editor</string>
    <key>CFBundleURLSchemes</key>
    <array>
      <!-- TODO Replace this value: -->
      <!-- Copied from GoogleServices-Info.plist key REVERSED_CLIENT_ID -->
      <string>com.googleusercontent.apps.861823949799-vc35cprkp249096uujjn0vvnmcvjppkn</string>
    </array>
  </dict>
</array>
<!-- End of the Google Sign-in Section -->

I don't know that it matters exactly where amongst the keys in the file you put it. I placed it between these two lines:
<key>LSRequiresIPhoneOS</key>
<true/>
<!-- Google Sign-in Section -->
  .
  .
  .
<!-- End of the Google Sign-in Section -->
<key>UILaunchStoryboardName</key>
<string>LaunchScreen</string>

Open your [my_project]/ios/Runner/GoogleService-Info.plist file, copy the REVERSED_CLIENT_ID string, and paste it into the code you just added to the Info.plist file in the previous step, replacing the sample REVERSED_CLIENT_ID string provided (as indicated in the TODO code comment). Save.
If you don't yet have a Podfile in your [my_project]/ios subdirectory, open the terminal, cd to the [my_project]/ios subdirectory, then run pod init. After this, if, in Step 5 above, you changed the iOS Deployment Target setting in Xcode (see "Note" after Step 5), open your Podfile, uncomment the platform :ios line at the top, and change the iOS version to match your setting in Xcode (e.g. platform :ios, '12.1').

Note: If, like me, you are using the firebase_core plugin, you will need to include pod 'Firebase/Core' in your [my_project]/ios/Podfile file, here:

target 'Runner' do
  use_frameworks!
  pod 'Firebase/Core'

and add #include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig" to [my_project]/ios/Flutter/Release.xconfig

In the terminal, in the [my_project]/ios subdirectory, run pod install. (Before this, I may have run Tools > Flutter > Flutter Clean, then File > Save All, then File > Invalidate Caches/Restart..., then after restart Tools > Flutter > Flutter Packages Get just to make sure everything was clean).

After these steps (I don't believe I've left anything out), I opened the iOS Simulator (I'm using iPhone XS Max - 12.1) and ran the app and it built successfully. 😃

Note: If I build in Xcode rather than in IntelliJ Idea, I get a number of warnings. All of these warnings, however, are related to code in the plugins. So, I'm not sure there is anything for me to do to address them.

Android

Open the Android portion of your Flutter project in Android Studio. Make sure you are using Android Studio 3.3. (I closed IntelliJ Idea altogether, opened Android Studio, clicked on File > Open, and navigated to the ~/IdeaProjects/[my_project]/android folder in my Flutter project. Upon opening the Android project followed by Android Studio starting to sync it, a message/pop-up appeared asking if it could update the Gradle plugin, so I let it. It was upgraded to version 3.3.0.)
Add the following 2 lines to the bottom of the [my_project]/android/gradle.properties file:

android.useAndroidX=true
android.enableJetifier=true

Note: I'm not sure if android.enableJetifier=true could have been, or should have been, set to false. Perhaps someone else can clarify under which conditions it should be true vs false. I believe it has something to do with whether or not the project has additional libraries that haven't yet been migrated to AndroidX, but, if my belief is correct, I don't know if when this setting is set to true it means Android Studio will migrate these libraries to AndroidX or that it will make code adjustments to account for the fact that the libraries aren't yet AndroidX compatible. Or maybe I'm totally wrong and it is something else altogether.

In the Android Studio main menus, select Refactor > Migrate to Androidx..., saving a backup of your project to a .zip file. Follow this with File > Save All and then quit Android Studio.
If your Android app has not already been added to your Firebase project, add it and download the google-services.json file either directly to the ~/IdeaProjects/[my_project]/android/app subdirectory or elsewhere (e.g. ~/Downloads) and then drag it there in the Finder.

Note: google-services.json was already an entry in my [my_project]/.gitignore file. If it is not in yours, you may want to add it, based upon the answer to the stackoverflow question Firebase: Should I add GoogleService-Info.plist to .gitignore?, since it would seem to apply to this file as well.

Reopen your Flutter project in IntelliJ Idea and update your Kotlin plugin to version 1.3.20, if it has not been previously updated. This is done with IntelliJ IDEA > Preferences > Languages & Frameworks > Kotlin. With Update Channel set to Stable, if a message indicating an updated version is not already visible, clicking the Check again button will reveal if there is an update to the plugin. If you are not currently using 1.3.20, then update to it.
In the [my_project]/android/build.gradle file, change the Kotlin version to match the updated plugin version (the release suffix on the plugin version, e.g. -release-IJ2018.3-1, is not needed):

buildscript {
    ext.kotlin_version = '1.3.20'
	.
	.
	.

Note: Since there are two build.gradle files in the Android version of your app, [my_project]/android/build.gradle and [my_project]/android/app/build.gradle, ensure that you are make code changes to the correct file. This advice may be obvious, but I thought it couldn't hurt to emphasize it.

In your [my_project]/android/app/build.gradle file, make the following changes:

dependencies {
    implementation "org.jetbrains.kotlin:kotlin-stdlib-jdk7:$kotlin_version"
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'androidx.test:runner:1.1.2-alpha01'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.1.2-alpha01'
}

These were code analysis suggestions by IntelliJ Idea. The change in the implementation line to jdk is subtle and perhaps possible to miss.
Change these lines in the [my_project]/android/app/build.gradle file as well (although I don't recall the specific source(s) that recommended them).
android {
    compileSdkVersion 28
    .
    .
    .
    defaultConfig {
        .
        .
        .
        minSdkVersion 21
        targetSdkVersion 28

Either before or after the next step, a pop-up in IntelliJ Idea informed me Kotlin migrations to the new version could be run, so I chose to let it do so.

Per the firebase_auth plugin instructions, add/change the following lines of code in the [my_project]/android/build.gradle file, although I updated the com.android.tools.build:gradle version to 3.3.0 rather than keeping it 3.2.1  as in the instructions (see the last sentence in Step 1 above)) :

dependencies {
  // Example existing classpath
  classpath 'com.android.tools.build:gradle:3.3.0'
  // Existing classpath, unchanged
  classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"
  // Add the google services classpath
  classpath 'com.google.gms:google-services:4.2.0'
}

Also per the firebase_auth plugin instructions, add the following line of code to the bottom of the [my_project]/android/app/build.gradle file:

apply plugin: 'com.google.gms.google-services'

Note: After Step 9, I ran Tools > Flutter > Flutter Clean, then File > Save All, then File > Invalidate Caches/Restart..., then after restart Tools > Flutter > Flutter Packages Get just to make sure everything was clean.

After these steps (once again, I don't think I've left anything out), I opened the Android Emulator (I'm using the Nexus 5X API 28 because it supports Google Play, which I believe is necessary for Firebase) and ran the app and it built successfully. 😃
Hope this helps. Cheers!
UPDATE (03-04-19): See one additional step for Android in my follow up comment below.

Thank you. It's work...


nomination-pools: Investigate adding joining pools

New joiners to a bonding pool can be unfairly subjected to a slash if they join a pool after a slash is recorded, but before it is applied.
For new joiners to avoid unfair slashing, I think we would need slash_defer_duration joining pools, and have some way of triggering any joining pools that are older than slash_defer_duration to be merged into the main bonded pool. This way, if a slash is applied, we could have it just affect the bonded pool and the unbonding pools, sparing the delegators in the joining pools.
Any time a slash is applied, we would need to guarantee that a delegator who joined by time the slash was recorded is included in the bonded pool or unbonding pools. This is tricky because the merging of joining pools into the main bonded pool likely cannot be reasonably coupled with recording or applying slashes without significantly increasing the I/O complexity of pool slashes. One idea would be to have a hook on era change that merges any joining pools. Another idea would be to have the slashing logic incorporate any joining pools within the slash range while calculating slashes.
It should be noted that delegators could simply be advised to not join pools that have a pending slash.
Should wait until #10694 is merged to start working on this.

patiently waiting to attempt this :)

patiently waiting to attempt this :)

Happy to hear :) Keep in mind that we aren't sure this will ever actually be added (hence "investigate" in the title). Nonetheless it would be a great project to get a in depth understanding of the pools code. I suspect the trickiest part will be the logic for applying big slashes that would need to dip into the joining pool funds.


Add simple script for helping generate boilerplate detector and cam classes

I'm not sure if this should live in this ophyd repository, but essentially this script allows for generating a bunch of boilerplate for new Detector and Cam classes by simply parsing the .template files for a specified areaDetector driver. To get an idea of what it does, you can take a look at a PR I am making adding the generated classes (with some minor hand-done fixes after) to add ADPICam detector and cam classes.
The ADPICam driver: https://github.com/areaDetector/ADPICam
I think long term this script will be replaced by some other, better, solution, like utilizing PVI from Diamond, but for now this should really simplify adding support for any new drivers.

Made some changes that "I think" address the issues raised, let me know if I missed something

Oh, just remembered. @jwlodek, why the template name is {det_name}_boilerplate, not {det_name}_boilerplate.py? I think it would make sense to add the .py extension so that the editors display it with syntax highlighting.

Sure that makes sense to me, thanks for the suggestion @mrakitin !


Move JRuby warnings in README.md file to bottom of the page

The warning about JRuby problems has become very much outdated, and can at least be pushed to the bottom of the readme. Can also be considered to be removed totally.

I'm working on #71 currently and README will be rewritted a lot (splitting Ruby DSL and CLI documentation into 2 repos). I've already moved this section below, but I didn't think about its actuality. I'll think about it, thank you.

JRuby <IP_ADDRESS> was released on May 15 2017, so I'm sure we can definitely delete this warning.

#71 was resolve and now there is no warning about old version of JRuby in the README. @thomasfl, thank you for attention to this thing. :clap:


Feature/Refactor-logic-for-ScreenedForBP-&-ScreenedForDiabetes

Jira ticket: https://thepalladiumgroup.atlassian.net/browse/KHP3-4776
Mainly added the following table to the linelist ART:
Hypertension as HasHypertension
IsHyperTensiveAndScreenedBPLastVisit
IsHyperTensiveAndBPControlledAtLastVisit
Diabetes as HasDiabetes
IsDiabeticAndScreenedDiabetes
IsDiabeticAndDiabetesControlledAtLastTest
FirstHypertensionRecoredeDate
FirstDiabetesRecordedDate

Please order asc for hypertension ordering

@Marymary-dev  nice catch, I have updated.


Release alluxio-enterprise 2.4.1-2.1.1-1.0 (automated commit)

Description:
Alluxio Enterprise Edition
Source URL: https://alluxio-dcos-dev.s3.amazonaws.com/autodelete7d/alluxio-enterprise/20191220-130909-cOWSIdjzfhjmZ6df/stub-universe-alluxio-enterprise.json
Changes between revisions 200 => 300:
0 files added: []
0 files removed: []
3 files changed:
--- 200/marathon.json.mustache
+++ 300/marathon.json.mustache
@@ -21,10 +21,10 @@
   },
   {{/service.service-account-secret}}
   "env": {
-    "PACKAGE_BUILD_TIME_EPOCH_MS": "1573601154976",
-    "PACKAGE_BUILD_TIME_STR": "Tue Nov 12 2019 23:25:54 +0000",
+    "PACKAGE_BUILD_TIME_EPOCH_MS": "1576876153455",
+    "PACKAGE_BUILD_TIME_STR": "Fri Dec 20 2019 21:09:13 +0000",
     "PACKAGE_NAME": "alluxio-enterprise",
-    "PACKAGE_VERSION": "2.4.0-2.1.0-1.0",
+    "PACKAGE_VERSION": "2.4.1-2.1.1-1.0",

     "BOOTSTRAP_URI": "{{resource.assets.uris.bootstrap-zip}}",
     "EXECUTOR_URI": "{{resource.assets.uris.executor-zip}}",
@@ -48,7 +48,7 @@
     "SERVICE_USER": "{{service.user}}",
     "TASKCFG_ALL_ALLUXIO_DISTRIBUTION": "{{service.alluxio-distribution}}",
     "TASKCFG_ALL_ALLUXIO_LICENSE": "{{service.license}}",
-    "TASKCFG_ALL_ALLUXIO_VERSION": "2.1.0-1.0",
+    "TASKCFG_ALL_ALLUXIO_VERSION": "2.1.1-1.0",
     "TASKCFG_ALL_LOG_LEVEL": "{{service.log-level}}",
     "TASKCFG_ALL_SERVICE_NAME": "{{service.name}}",

--- 200/package.json
+++ 300/package.json
@@ -3,7 +3,7 @@
   "upgradesFrom": [],
   "downgradesTo": [],
   "name": "alluxio-enterprise",
-  "version": "2.4.0-2.1.0-1.0",
+  "version": "2.4.1-2.1.1-1.0",
   "maintainer"<EMAIL_ADDRESS>   "description": "Alluxio, formerly Tachyon, is the world's first system that unifies disparate storage systems at memory speed. With Alluxio, enterprises can manage data efficiently, accelerate business analytics, and ease the adoption of hybrid cloud. \n\n Alluxio Enterprise Edition delivers operational benefits of a stable, high performance system with enterprise features and support for critical deployments. Please refer to https://alluxio.com/docs/enterprise/1.7/en/Alluxio-on-DCOS.html for a detailed operation guide. \n\n Release Notes: \n - Upgrade to version 2.1.0 of Alluxio",
   "selected": false,
--- 200/resource.json
+++ 300/resource.json
@@ -5,12 +5,12 @@
       "alluxio-agent-darwin_amd64": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/darwin_amd64/alluxio-dcos",
       "alluxio-agent-linux_386": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/linux_386/alluxio-dcos",
       "alluxio-agent-linux_amd64": "https://alluxio-dcos-release.s3.amazonaws.com/agent/v1.5.0/linux_amd64/alluxio-dcos",
-      "bootstrap-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/bootstrap.zip",
-      "executor-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/executor.zip",
+      "bootstrap-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/bootstrap.zip",
+      "executor-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/executor.zip",
       "java-tar-gz": "https://alluxio-dcos-release.s3.amazonaws.com/jdk/jdk1.8.0_144_jce_policy.tar.gz",
       "jre-tar-gz": "https://downloads.mesosphere.com/java/server-jre-8u162-linux-x64.tar.gz",
       "libmesos-bundle-tar-gz": "https://downloads.mesosphere.com/libmesos-bundle/libmesos-bundle-master-28f8827.tar.gz",
-      "scheduler-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/alluxio-enterprise-scheduler.zip"
+      "scheduler-zip": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/alluxio-enterprise-scheduler.zip"
     }
   },
   "images": {
@@ -29,7 +29,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/dcos-service-cli-darwin"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli-darwin"
         }
       },
       "linux": {
@@ -41,7 +41,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/dcos-service-cli-linux"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli-linux"
         }
       },
       "windows": {
@@ -53,7 +53,7 @@
             }
           ],
           "kind": "executable",
-          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.0-2.1.0-1.0/dcos-service-cli.exe"
+          "url": "https://alluxio-dcos-release.s3.amazonaws.com/artifacts/2.4.1-2.1.1-1.0/dcos-service-cli.exe"
         }
       }
     }

@ryadav88 Please take a look.

gentle ping?


Apportionment Processes for CAMPD

Overview
The apportionment process produces the unit-level emissions data used in CAMPD by doing the following:

Flattens the HI, SO2 Mass, NOx Mass, NOx Rate and CO2 Mass values reported in the ECMPS Derived Hourly Value table and the CO2 Mass values reported in the Daily Emission table into hourly rows containing each of the values, Operating Time, Load, SO2 and CO2 rates, and measured information for each of the parameters.
Apportions values measured at stacks or pipes to the connected units

The ECMPS 2.0 process should generally follow the ECMPS 1.0 process, and utilize the 1.0 details.
The ECMPS 1.0 apporitonment process involves the following apportionment tables in CAMDECMPS (CAMDBSP) and CAMDDMW (CAMDPUB):

Monitor Hourly: CAMDECMPS: MONITOR_HOUR  CAMDDMW: HOUR_MONITOR_DATA
Monitor Daily: CAMDECMPS: MONITOR_DAY  CAMDDMW: DAY_MONITOR_DATA
Monitor Monthly: CAMDECMPS: MONITOR_MONTH  CAMDDMW: MONTH_MONITOR_DATA
Monitor Quarterly: CAMDECMPS: MONITOR_QUARTER  CAMDDMW: QUARTER_MONITOR_DATA
Unit Hourly: CAMDECMPS: UNIT_HOUR  CAMDDMW: HOUR_UNIT_DATA
Unit Daily: CAMDECMPS: UNIT_DAY  CAMDDMW: DAY_UNIT_DATA
Unit Monthly: CAMDECMPS: UNIT_MONTH  CAMDDMW: MONTH_UNIT_DATA
Unit Quarterly: CAMDECMPS: UNIT_QUARTER  CAMDDMW: QUARTER_UNIT_DATA
MATS Monitor Hourly: CAMDECMPS: MATS_MONITOR_HOUR  CAMDDMW: HOUR_MONITOR_MATS_DATA
MATS Unit Hourly: CAMDECMPS: MATS_UNIT_HOUR  CAMDDMW: HOUR_UNIT_MATS_DATA

Notes:

The process performs the apportionment using the CAMDECMPS apportionment tables (actually the ECMPS Client version of the tables), and then moves the data to the CAMDDMW tables.
The CAMDECMPS SO2, NOx and CO2 masses are in pounds.  For CAMDDMW, the CO2 mass is in pounds, but the SO2 and NOx masses are in tons, and additional columns exist that contain the SO2 and NOx pound values.  The summing of mass values should occur using pounds values, not tons.
CAMPD currently only contains the "unit" version of the apportionment tables.  However, CAMD plans to implement the "monitor" version of the tables.
MATS data are not aggregated to day, month nor quarter values.

CAMDDMW also includes the following apportionment tables:

ANNUAL_MONITOR_DATA
ANNUAL_UNIT_DATA
OZONE_MONITOR_DATA
OZONE_UNIT_DATA

The following Reported Emission tables in CAMDECMPS contain the source data for apportionment:

HRLY_OP_DATA: Contains the operating time and load for each location and hour.
DERIVED_HRLY_VALUE: Contains the heat input, SO2 Mass, NOx Mass, NOx Rate, and CO2 Mass rows for each location and hour.
DAILY_EMISSION: Contains daily CO2 emissions for a location.  For apportionment, the daily emissions are divided equally for the operating hours for the location and day.

The ECMPS 1.0 version involves the following steps:

Pull the Reported Emissions data from HRLY_OP_DATA, DERIVED_HRLY_VALUE and DAILY_EMISSION tables, flattent the data into hourly rows, and store the row in MONITOR_HOUR.
For monitoring plans (MP) that contain a single unit, populate the UNIT_HOUR row for the unit and hour from the MONITOR_HOUR row for the unit and hour.
For other MP, populate the UNIT_HOUR for the unit nad hour based on the MONITOR_HOUR rows for all locations in the MP, and the connections between the locations in the MP.
Sum MONITOR_HOUR rows to produce MONITOR_DAY rows, MONITOR_DAY to produce MONITOR_MONTH rows, and MONITOR_MONTH to produce MONITOR_QUARTER rows.
Sum UNIT_HOUR rows to produce UNIT_DAY rows, UNIT_DAY to produce UNIT_MONTH rows, and UNIT_MONTH to produce UNIT_QUARTER rows.
Populate CAMDDMW tables from their matching CAMDECMPS tables.
Create or replace ANNUAL_MONITOR_DATA and ANNUAL_UNIT_DATA rows by summing QUARTER_MONITOR_DATA and QUARTER_UNIT_DATA rows respectively.
Create or replace OZONE_MONITOR_DATA and OZONE_UNIT_DATA rows by summing MONTH_MONITOR_DATA and MONTH_UNIT_DATA rows respectively.

Complex Apportionment:
Most apportionment occurs automatically based on the MP configuration.  However, complex configurations and some changing configurations require formulas to determine how to apportion data.  Those formulas are stored in the following tables on both the ECMPS 1.0 Host (CAMDECMPSAUX) and Client (ECMPS).

APPORTIONMENT: Parent table that indicates the MP, begin quarter, and if it exists end quarter for the apportionment formulas.
APPORTIONMENT_RANGE: Child table used to create separate formulas for distinct ranges for a monitoring plan.  Typically used when formulas are needed for a MP with configuration changes.
APPORTIONMENT_DATA: Grandchild table that stores actual apportionment formulas.  Multiple rows may exist for an APPORTIONMENT_RANGE parent.  When that occurs the rows are ordered and all but the last contains a condition to determine whether it is the row used for the apportionment.  This usually provides the ability to apply different formulas based on which locations are operating.  Additionally, APPORTIONMENT_DATA allows the ability to indicate when a stack is a duct contributing to another stack for which the emissions should be reduced before being apportioned.

Key ECMPS 1.0 Non-Table Objects

Application : DM Project (C#): Controls the apportionment process and performs the actual apportionment.
Application : DM.cUpdateEmissions Class (C#): Calls delegates needed to interact with the database or methods similating the database for testing purposes.
Application : EmissionsReport.cUpdateEmissionsDb Class (C#): Links the ECMPS.DB.cUpdateEmissions object to the supporting database objects and tables.
Application : EmissionsReport.cUpdateEmissionsDb.UpdateUnitHour Method (C#): Bulk loads the apportioned hourly data into the MONITOR_HOUR and MATS_MONITOR_HOUR tables.
Database    : DmEm.UpdateInit: Loads "monitor" apportionment tables and returns sets of data needed by the check engine to apportion data.
Database    : DmEm.UpdateSuccess: Loads "unit" day, month and quarter apportionment tables.
Database    : DmEm.GatherMonitorHour: Gathers hourly monitor data for the MONITOR_HOUR table.
Database    : DmEm.GatherMatsMonitorHour Gathers hourly monitor data for the MATS_MONITOR_HOUR table.

Note that all apportionment related ECMPS 1.0 database objects are in the "DmEm" schema.
Other Notes:

The new ECMPS 2.0 apportionment process will need to add a record the CAMDDMW.OP_YEAR table for each new year that is processed:

OP_YEAR - newly submitted year

ARCHIVE_IND - 0

HOURLY_DATA_IND - 1

Needed Decisions:

Determine whether the Check Engine DM Emission process should utilize a set of DM tables to perform the re-calculation process, or will use the target CAMDDMW tables directly.  Note that the NOXM
Determine whether the CAMPD emissions, whether in CAMDECMPS, CAMDDMW, or both should be deleted when an emission report is resubmitted, or just when the CAMPD emissions are reproduced.
Ensure that existing DM emissions are cleared for a submitted emission report,  This could occur as part of the DM Emissions job.

### Tasks

Chris Deprioritized, focused on the Beta release and this will not be worked on until after march

Programming Task Checklist

Create Tables (CAMDECMPSCALC):

[ ] DM_EMISSIONS

[ ] DM_EMISSIONS_USER
[ ] MATS_MONITOR_HOUR
[ ] MATS_UNIT_HOUR
[ ] MONITOR_HOUR
[ ] UNIT_DAY
[ ] UNIT_HOUR
[ ] UNIT_MONTH
[ ] UNIT_QUARTER

Create Stored Procedures and Functions

[ ] DeleteUnitData (?)
[ ] GetApportionmentData
[ ] UpdateFailure
[ ] UpdateInit

[ ] GetReportDates
[ ] isMatsEmissionReport
[ ] LoadMonitorData

[ ] DeleteMonitorData
[ ] LoadMatsMonitorHour

[ ] GatherMatsMonitorHour

[ ] MatsModcToMeasureCode
[ ] ScientificNotationToFloat

[ ] LoadMonitorHour

[ ] GatherMonitorHour

[ ] UpdateInit_Check

[ ] UpdateReset
[ ] UpdateSuccess

[ ] LoadUnitDay
[ ] LoadUnitMonth
[ ] LoadUnitQuarter


Nightly wrap_comments can break code blocks

Given:
    /// To add a key compatible with the above service and user run a command like the following:
    /// ```console
    /// $ secret-tool store --label="Descriptive name" service chezmoi-modify-manager username konversation-login
    /// ```

wrap_comments reformats this to:
    /// To add a key compatible with the above service and user run a command
    /// like the following: ```console
    /// $ secret-tool store --label="Descriptive name" service chezmoi-modify-manager username konversation-login
    /// ```

It should instead be reformatted to:
    /// To add a key compatible with the above service and user run a command
    /// like the following:
    /// ```console
    /// $ secret-tool store --label="Descriptive name" service chezmoi-modify-manager username konversation-login
    /// ```

This relates to #3347

Closing this as a duplicate of #5244


file updates after the first one are not detected

reported on Linux Mint, reproduced on Ubuntu

I did some more testing and I was only able to reproduce the bug using gedit on Ubuntu 17.10. The issue appeared both when I opened the file in gedit first and then in MarkdownFox and the other way round.
I was not able to reproduce the issue with nano, Visual Studio Code or Atom (all also on Ubuntu 17.10).
A possible cause for the issue could be that gedit handles file saving different than the other editors and maybe removes the old file and saves a new one. I imagine such behaviour could cause problems with the file's inode and Node's fs.watch (see docs). Unfortunately I have no idea how to fix this except using the more inefficient fs.watchFile and I don't want to do that.
TL;DR: Don't know how to fix this issue that seems to be specific for gedit. Help appreciated.


Support in spec for closure/shutdown

Background
As it currently stands, it doesn't appear there is current support within the spec or providers for shutdown or closure functionality. Multiple flag vendors instruct within their documentation that feature flagging clients should be shut down upon closure of the application or other necessity within the implementation: LaunchDarkly client closing, Go Feature Flag deferred closing, Harness feature flags closing.
There are several reasons that a closing of the flag provision could be necessary:

a user who has since logged out should not continue to get flags targeted to them post-logout
memory leaks (especially lower-level languages/stacks)
ceasing of polling/streaming that many flagging tools utilize
some change in the app/service state that requires re-connecting to the Provider and therefore invalidation of the prior OpenFeature/Provider connection

Some of these reasons are even potential security issues (i.e. user information could remain inside OpenFeature and a Provider after logout in some cases). It's probably not a large or frequent issue, but security risks usually start that way.
Other Considerations
Post-shutdown behavior
The natural follow-up question if shutdown is provided is "what comes next?" That's a great question, and some thought is required to make sure it's handled well.
For example, take the case that an OpenFeature client is instantiated via a Provider and utilized in an application. Some state changes in the application that triggers the need for a shutdown, and with a pseudocode client.shutdown() available, the closing of the OpenFeature Client as well as the flag vendor downstream though the Provider is successful. Everything is now shut down.
With the client now closed, how should calls for flag values be handled? Throwing errors on flag state calls makes sense, but it's not the entire picture.
After shutdown, how should re-instantiation be handled? The metadata and context are defined for OpenFeature at instantiation of the OpenFeature client, so should those be cleared out as well on shutdown? In other words, does it make the most sense to clear everything out of the OpenFeature Client upon shutdown and render it unusable, throwing an error on every method?
This seems strict, but requiring re-instantiation of OpenFeature with new metadata likely makes the most sense if the flag vendor it is abstracting is also needing to be re-instantiated. A shut down client should not be functional in any way.
Shutdown/closing mean different things across flagging tools
This is perhaps the never ending question OpenFeature must handle: how can shutdown behavior be handled in a universally acceptable way? If a flag vendor does not support shutdown or closing, how can the Provider do so nonetheless? These answers will need to be handled on a case by case Provider basis with the expected behavior defined by the consensus at the OpenFeature spec level.
Hook to shut down?
In exploration of this issue, I looked into a hook as a potential option, but as they are related to flag call lifecycles and not the lifecycle of either the OpenFeature Client or Provider connection, hooks are not a viable solution.
Suggested Implementation
I propose a shutdown method on the OpenFeature Client that:

utilizes the Provider to trigger whatever function causes the vendor/flag-tool equivalent of close if available
will clear the metadata assigned at the time of OpenFeature instantiation
will clear the logger/telemetry collector assigned at the time of OpenFeature instantiation (and that connection if possible?)
will cause InactiveClientError or ShutdownClientError errors if any methods are invoked post-shutdown (or another informative error name)

The upside is an increase in robustness, durability, and flexibility, and the downside is not immediately clear. Perhaps a downside is a lack of universality in what "shutdown" means across the flag vendors, but that shouldn't mean OpenFeature's spec cannot define what "shutdown" means with some finality.
I would argue that this functionality is not bloat or a request to support an insignificant, random use-case but rather is one of the areas where the spec can mature. I'm sure there will be more areas like this identified as utilization of both feature flagging and OpenFeature specifically grows.

Apologies for creating this issue within the repo for spec and not ofep. Thanks for the feedback @toddbaert . I added comments as well on https://github.com/open-feature/ofep/pull/25.

@jakedoublev no need to apologize. Thanks again for your contribution!
I can't ping you in the OFEP, because you are not in the org (I can invite you if you're interested!) but I attempted to address some of your observations in https://github.com/open-feature/ofep/pull/30#issuecomment-1331261337, and I would appreciate your feedback.

@toddbaert I am interested! As I'm sure is universal - I'm not sure how much I can commit to contributing, but I'd like to be involved as much has I'm able. I encouraged my org to utilize OpenFeature at work (different GH account) and led development of a Provider to use internally as one wasn't yet available for our use case.

@toddbaert I am interested! As I'm sure is universal - I'm not sure how much I can commit to contributing, but I'd like to be involved as much has I'm able. I encouraged my org to utilize OpenFeature at work (different GH account) and led development of a Provider to use internally as one wasn't yet available for our use case.

I will invite you to the org. Contribution level is always up to you.
I would love to understand your usage more. For many reasons, including CNCF graduation progress, understanding use-cases is very important!

Happy to share more async @toddbaert Feel free to shoot me a DM in the CNCF Slack and we can talk more there or via email. :)

The spec now defines shutdown behavior.


metrics not collected when server is down

build user:       "ecastro"
build date:       "2020-02-25T18:49:45Z"
go version:       go1.13.8

When collecting data from a server, the iperf3_received_bytes & iperf3_received_seconds are stored in prometheus but if the server is stopped or goes down (or connectivity issues) these metrics are no longer stored in prometheus, only the "e.success" metric is stored with a 0 value.
The problem with this behaviour is that it creates gaps with no measure at all. I believe it would be better to include the
iperf3_received_bytes, iperf3_received_seconds both with 0 value.
if err != nil {
     ch <- prometheus.MustNewConstMetric(e.success, prometheus.GaugeValue, 0)
     ch <- prometheus.MustNewConstMetric(e.receivedSeconds, prometheus.GaugeValue, 0) //iperf3_received_bytes = 0
     ch <- prometheus.MustNewConstMetric(e.receivedBytes, prometheus.GaugeValue, 1)//iperf3_received_seconds = 1
     iperfErrors.Inc()
     log.Errorf("Failed to run iperf3: %s", err)
     return
}

Check the image attached, in red the resulting measure if the iperf3_received_bytes, iperf3_received_seconds are always stored

Have you solved the problem? I have the same problem

Yes but without a pull request, I just build a custom version and I using that version with the changes to the code so it reports 0 bps instead of nothing

Would you mind sharing the updated code?


Set-up and register an image sitemap

Relates to #1224
Type

✨ Feature

Problem to be solved / User Story
Many of the works pages/images on Wellcome Collection are not crawlable, since they are only discovered through search. In order to help users discover images via Google (and other search engines) we need to ensure timely and accurate indexing by search engines.
As a user, I expect that when I use a search engine such as Google, relevant content from Wellcome Collection appears in the results.
Acceptance/Success Criteria

[ ] Sitemap should validate
[ ] Sitemap should appear in Google Search console
[ ] The number of indexed pages (as shown in Google Search console) should increase
[ ] Traffic to the site from Google should increase (particularly referrers from images in analytics)

Tasks required to make this happen:

[ ] Determine what should/can be included in the sitemap

N.B.

seems sensible to generate a sitemap for works (so they can also be indexed), with the image extension, rather than a separate image sitemap. Can list multiple images per work once we have them.

 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
<TODO: add example sitemap and sitemap index>

[ ] Generate the sitemap automatically

N.B.

sitemap can contain maximum of 50,000 urls and be no more than 50MB uncompressed.

will need to split sitemap into multiple files and list them in a sitemap index file.

potentially generate sitemaps and sitemap index with AWS lambda, outputting to S3 bucket

it's ok to host sitemaps on another domain as long as use robots.txt file to point to them see Sitemaps & Cross Submits

[ ] Register the sitemap

robots.txt is sufficient for indexing

However, to see sitemaps in the report page of Search console, it will have to be submitted through that tool too. This will require

[ ] verifying S3 bucket in search console OR using nginx to point to the s3 bucket from our domain.

[ ] We'll need to verify the loris server domain. As our image URLs are not on the same domain as our site we need to verify both domains in Google Search Console. (https://support.google.com/webmasters/answer/178636?hl=en)