Add more GPT-4 experiments

( All "sections" references below belong to the "GPT-4 Experiments notebook", I wasn't able to hyperlink it :( )
This PR addresses the following comments:

@ravwojdyla

Somewhere in here, is there a performance broken down by class? I essentially curious to check for Simpson's paradox.

See notebook section 1.2

Apart from maybe debugging some specific cases to make sure there's no big issues, if we want GPT tagger to perform better, prompt engineering would certainly be an interesting improvement. And specifically the CoT https://github.com/related-sciences/nxontology-ml/pull/21#user-content-fn-1-5fad6721aad68a63d474ea48c7193973 Re https://github.com/related-sciences/nxontology-ml/pull/20 and other potential issues with GPT skipping or duplicating records

See notebook section 4
(Gist: Adding CoT didn't change the performance much. Note that I changed your prompt a bit - see prompts/rav_cot_precision_v1.txt)
Please tell me what you think but it might be worth doing another pass at CoT prompts at a later time (i.e. after the workshop next week)

maybe we could include a CSV (in the prompt) with specific record IDs and missing precision column (there are only 2 columns), and ask GPT to fill in the precision in the CSV, I suspect it would be much less likely for GPT to produce "corrupted" output.

I ended up cutting that corner and postponing this idea since it was causing significant changes to the way the prompts are currently injected/constructed.

@eric-czech

Do you have some examples you can share before scaling up? Specifically, I mean logs of prompts being sent and responses received for them. I think this is all within the realm of expectation, but a second look could help.

See notebook section 2.1

I'm not opposed to adding more few-shot examples. It would help to have some examples like I mentioned above ... we might be able to add in "difficult" cases as a part of the prompt to some net positive effect.

See notebook section 1.3 (and similarly 2.3)

Additionally, I wanted to see the impact of varying the number of completions ("choices") and see the impact on MAE.
(gist: Not surprisingly the more choices the better performance, although not drastic).

Nicely organized @yonromai 👍.  That notebook is a big help.

Do you have some examples you can share before scaling up?

See notebook section 2.1

Looking at a prompt and a corresponding completion doesn't turn up anything immediately concerning for me.  Those classifications from GPT4 make sense for the most part.
Looking at some of the misclassifications didn't surface anything alarming either.  I break them into 3 cases:

Our "true" label is wrong; here are 3 examples:

"Malformation syndrome with hamartosis" (Orphanet:98196) should be 02-disease-root not 03-disease-area
"neurotoxicity" (EFO:0011057) should be 02-disease-root (or  maybe 03-disease-area .. close call), not 01-disease-subtype; I agree w/ GPT4 in calling this a "low" precision term given only the label/description
"papillary carcinoma" (EFO:1000646) should be 02-disease-root not 03-disease-area

The GPT4 label is inexplicable given the term details

e.g. "Osteosclerosis - ichthyosis - premature ovarian failure" does not suggest a low precision label

The GPT4 label is right and the "true" label is actually determined by EFO implementation details (i.e. the structure)

Malformation syndrome with hamartosis is a good example of this where high precision labels from GPT4 are a great choice given only our definition of the task and the term details, yet the existence of descendants for this term in EFO would dictate it's probably better as a medium term.

Overall, I would say I agree with ~80% of the GPT4 classifications in these misclassified examples.  To be clear, this does not suggest that 80% of those true labels are wrong -- making this classification using only labels + descriptions is a somewhat orthogonal task to doing it within the confines of EFO's structure (i.e. lots of these fall into case # 3 above).
I do think we can add these misclassified examples to the prompt though:
- id: Orphanet:75325
  label: Osteosclerosis - ichthyosis - premature ovarian failure
  definition: NA
  precision: high
- id: EFO:0007237
  label: dipetalonemiasis
  definition: A filariasis that is a zoonotic infection caused by the nematode of the genus Dipetalonema.
  precision: high
- id: MONDO:0013742
  label: familial mesial temporal lobe epilepsy with febrile seizures
  definition: NA
  precision: high
- id: MONDO:0002321
  label: sensory peripheral neuropathy
  definition: Inflammation or degeneration of the sensory nerves.
  precision: medium
- id: EFO:1000646
  label: papillary carcinoma
  definition: A malignant epithelial neoplasm characterized by a papillary growth pattern.
  precision: medium
- id: EFO:0011057
  label: neurotoxicity
  definition: Toxicity that causes injury to the central or peripheral nervous system or damages its function.
  precision: low

That would increase our few-shot example count from 9 to 15.

Ditto - awesome work @yonromai!

Most high distance from true label nodes are of class 01-disease-subtype

So that means, GPT would frequently assign low precision to something that is actually high precision? afaiu that would fall into the 2nd bucket in Eric's misclassification classification. Here's one example of that from the notebook:

{'dist': 6,
'efo_definition': 'A viral infectious disease that results_in infection in '
'sheep and rarely humans, has_material_basis_in Louping '
'ill virus, which is transmitted_by sheep tick, Ixodes '
'ricinus. The infection has_symptom lethargy, has_symptom '
'muscle pains, has_symptom fever, and has_symptom focal '
'neurological signs.',
'efo_id': 'EFO:0007348',
'efo_label': 'louping ill',
'precisions': ['low', 'low', 'low'],
'true_label': '01-disease-subtype'},

I'm surprised GPT would assign low precision here, just high level based on the description it, it does sound like high precision disease, given the details. It would be interesting to have the reasoning/CoT for this case, for debugging purposes. I guess we do see that in the per class scores:

Thanks for those btw ^ 🙏

Please tell me what you think but it might be worth doing another pass at CoT prompts at a later time (i.e. after the workshop next week

Thanks for giving that a try, do you happen to have the explanations available somewhere? Like for the EFO:0007348 above. WRT further prompt tuning (after the workshop):

I defer to Eric/Daniel about how much we want to optimize this - I suspect not much
to actually make an educated decision about this, it would be worth to take a look at the actual explanations from the current CoT prompts and look for patterns that we could improve, at least that worked well for me in the past. Otherwise we would be doing a "shotgun prompt tuning" ™ ?

(I'd like to rebase this notebook on an upcoming change so I'll merge this PR and open a new one soon with updates)


Support an array of default files for each linter, based on that linters expectations.

I too would love for Super-Linter to support an array of default files for each linter, based on that linters expectations. This would likely be considered a feature request.

Originally posted by @BretFisher in https://github.com/super-linter/super-linter/issues/2581#issuecomment-1066208434

👏👏👏


User groups for better control of permissions

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
It would be useful to define user groups with different permissions for actions like:

Deleting projects
Inviting users via link
View/work on projects

For example, an Admin group would be able to:

Delete any project
Delete user accounts
Invite any user
View and work on all projects (e.g. Projects 1 - 10)

Users in Group A would be able to:

View and work on only Project 1

Describe alternatives you've considered
According to the documentation, user management actions are limited to account creation, invitations by link, and password reset.
Additional context
N/A

@kenlee-ga This feature is implemented in our platform: www.heartex.com.


Reconnect to database

Rope's behaviour isn't well defined right now but it should keep attempting to reconnect to the database indefinitely (I think, or with a backoff).
We should also expose the health of the connection as an API for healthz. Right now I have to restart all our services when we roll the database nodes, when really I'd like them to just transparently reconnect to the new node.

That would cause a blocked application if that is done while executing a query. The application should take care for that I think. In that way the app developer could decide to be informed about database issues via logging and could fix it.


Fix Json.add and Json.merge operations

Fixes #118
Changes:

Json.add should return object with added/updated field
Json.merge should work as Map.plus
Json.toList should use Pair to Tuple2 function
Add test cases for add and merge operations

Agreed, add and merge should only work on JsObjects.
However, I'm not sure if add and merge serve the same purpose. With add you can add JsString, JsNumber etc. to a JsObject with a certain key.
The merge function should merge two JsObjects together. This way we can avoid the following confusing situtations:
val a = JsObject("weight" to JsFloat(61.4f))
val b = JsString("abc")

val c = a.merge(b) // c == b for no reason

If we constrain the merge function to JsObjects only, these situations will not able to happen. I'm happy to make these changes, if we can agree on these.

As it is on this PR, merge serves the same purpose than add because if, continuing with your example, a.merge(b) doesn't do anything because b has to be a JsObject.
You can restrict that making merge to receive a JsObject directly and it would be the same as add with the insignificant difference that add just allow you to add new values one by one and merge would allow you to add them all at the same call.

I agree to move them to JsObject but I would like the opinion of @nomisRev here too

@AdrianRaFo @nomisRev How should we proceed? 🤔

Hey @nomisRev,
Sorry for the delay. Made the changes today, caught up with upstream and integrated the testing changes from arrow test. Please take a look at it, as I'm not sure I got it right.

@ambrusadrianzh no worries! Thank you for the contributions! I saw @AdrianRaFo already checked out your PR, I can give it a look next week. This week is a little busy with travelling and KotlinConf ;)


Package guardian-agent

Package Request: guardian-agent
guardian-agent is a way of being able to do agent forwarding when using mosh. It also allows verifying commands being executed. I don't fully understand how it works, but it seems valuable, especially as I shift back to using mosh on high-latency links.

This project looks abandoned, it has been released as as beta in 2017.

Hm, disappointing, but good point. I opened this to confirm: https://github.com/StanfordSNR/guardian-agent/issues/24

@mmahut I'm not really sure if we should proceed. I was going to close it, based on the response to the issue I filed on the guardian-agent repo, but I see you have a PR open now...

@colemickens while I thought the same, I changed my mind because of two things. First of all there is sadly no alternative to this and mosh won't implement one, they own recommendation is actually using guardian-agent (as per https://github.com/mobile-shell/mosh/issues/120#issuecomment-418008147). And in the second place, the author of the project, Dima Kogan, did reply to my mail almost instantly, so while this is marked as beta, I think we should ship it with NixOS and help catch any outstanding bugs/problems with it.


filter_fuzz_test fails for ext_proc filter

Description:
filter_fuzz_test picks http filters by random to fuzz. The test fails when it picks the ext_proc filter, as the filter is instantiated with a mock Grpc::AsyncClientManager, which returns a null grpc client. The test seg faults when invoking a method on the null grpc client.
Repro steps:
Replace seed % filter_names.size() with 5 here to force the test to pick ext_proc and reproduce the failure.

The test also fails for envoy.filters.http.alternate_protocols_cache. See CI failure for #20112

Note that this pre-existing condition. Filters are selected randomly and apparently we were lucky up to now.
I think we need to address two things:

Fix failing filters.
Remove randomness from the test. It should really cover all filters.


change emulator apn proxy

It is very nice app and lib.
I just wonder if the app or lib could support to change proxy in emulator.
I know there is no wifi actually in emulator, but there is APN with proxy setting.
Thanks.

Hi lecheck, how about a version that supports ROOT for all those changes that cannot be done without it?

It's not the reason for what Proxy Settings and APL have been created. Anyway I'll think about it.


Unable to connect to Avatar using Master branch js/browser/avatar

The error message I get on screen is:
Unable to start avatar: Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="name resolver error: no matching vi websocket error code: 1011
I am using the correct key for an S0 Speech Service. I was able to connect to the CommunicationService and obtain my credentials.
But when I click "Start Session", in about 30 seconds, I receive this error.

Hi @kdubious, could you try the least SDK to see if this happens or not? We have fixed a similar issue.

Closed since no further customer update, presumed fixed in latest SDK releases.


two bugs in code ?

agent_s/GraphSearchAgent.py
Ln80:  "self.grounding_agent = OpenACIGroundingAgent()"
but openaci/ubuntu/Grounding.py:  "def init(self, obs, top_app=None)",  required parameter “obs”

agent_s/DAGPlanner.py
Ln313:   "self.active_apps = agent.get_current_applications(initial_observation)"
method(get_current_applications) is not exist in the openaci/ubuntu/Grounding.py

Hi, we just refactored the codebase and fixed some bugs. can you try the new release?


Charter SBYC DAO w/ logo and info

We want to add our DAO to Realms official directory

Please fix the merge conflict

Please fix the merge conflict

Resolved.


[🌟] dark mode support

Description
It would be very helpful to have a dark mode support. Thank you.
Proposed Solution
Add option showing image picker in dark or light mode?

Is this feature been released?


ConPTY pass-through sequences are being truncated

Environment
Windows build number: Version 10.0.18362.418
Windows Terminal version (if applicable): commit d711d731d7d00259b2e0fe5847928c9f1c1121ed
Steps to reproduce

Open a bash shell in Windows Terminal
Execute the sequence: printf "\e[?999h 12345 Hello World"

Expected behavior
999 isn't a supported mode, so that should be ignored and passed through to the conpty client. Then the text  12345 Hello World should be output.
Actual behavior
The unrecognized mode sequence gets truncated, losing the final character. and then the start of the text that is output is also truncated, leaving just ello World.
What's happening is that the missing character leaves the state machine in a state where it's waiting for a final character, so it ends up eating the characters that follow, until it gets to the H in Hello World.
I believe this is a regression caused by PR #3956. I think it's the calculation of the _run variable that is off by 1, but it may be more complicated than that:
https://github.com/microsoft/terminal/blob/d711d731d7d00259b2e0fe5847928c9f1c1121ed/src/terminal/parser/stateMachine.cpp#L1252
Also note that _run is initialized in more than one place.

On further review, I see the _run variable actually serves a different purpose, so changing that is not the solution. It's just not the right thing to be using for the pass-through.
To be honest I think we'd be better off just dropping this pass-through idea as a general concept. If there are specific sequences that we don't support in conhost, but we know another conpty client can handle, then we should be evaluating those on a case by case basis, and deciding whether they're safe to pass through.
The concept only really makes sense for operations that have no interaction with other parts of the system. For example, passing through a sequence to change the cursor color might be OK, but passing through a sequence that sets the left and right margins is never going to work - it'll just leave the conhost and conpty client completely out of sync.

@j4james, we should file another issue to further refine the reasoning behind what is and is not passthrough. I've taken this issue to generate a PR to restore the behavior I broke so as to not block the next release. Thank you for the find and apologies for the grief.


RN 0.47 android createJSModules deprecation fix

hi @Jiasm  i created RN 0.47 createJSModules deprecation fix. it would be nice to review and merge this PR when you have time. thnx.

CC @cyqresig


fix: Include dir patch

Checklist

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

In my installation of carma the directory was already absolute which led to some CMake issues (basically pointing to the same directory twice).

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/recipe.yaml) and found it was in an excellent condition.


Questions and advice for GDCRNATools

When I use it to build ceRNA network,I notice the internal dataset "pcTarget" and "lncTarget" of this package.
QUESTION:
According to your published article,you use 3 data sources including StarBase v2.0 (Li et al.,2014), miRcode (Jeggari et al., 2012), and spongeScan (Furio´ -Tarı´et al., 2016).So I was confused when I found only 137 lncRNAs in lncTarget dataset.Whether you use intersect or union of them?
Because starBase had been updated to v3.0 with 531 lncRNAs with miRNA interaction.I wonder whether to use my new data.Counld you give some suggestion?
ADVICE:
I found an error would appear if some miRNAs in the matrix of users didn't exist in the  "pcTarget"/ "lncTarget" or self-defined datasets of users.And I think the next code for mirCorTestFun function would avoid this problems.Your suggestion?
mirCorTestFun <- function(lncDa,pcDa, mir,mir.expr) {    if(mir %in% rownames(mir.expr)){     ## miRNA in the matrix(your raw codes)     mirDa <- unlist(mir.expr[mir,])     corlm <- cor.test(lncDa, mirDa, alternative='less')     corpm <- cor.test(pcDa, mirDa, alternative='less')     reglm <- corlm$estimate     regpm <- corpm$estimate   } else {     ## miRNA not exist,so correlation could not be calculated.     reglm <- NA     regpm <- NA   }   return (c(reglm, regpm)) ## lnc then pc }
Look forward to your return.Thank you!

Moreover,for the result from gdcCEAnalysis function,could you give a suggestion about proper cut-off of parameters for a real ceRNA network?

Hi,
I am trying to use gdcCEAnalysis function and it gives two main errors:
1.) Error in colnames<-(*tmp*, value = c("lncRNAs", "Genes", "Counts",  :
attempt to set 'colnames' on an object with less than two dimensions
2.)Error in cor.test.default(lncDa, mirDa, alternative = "less") :
not enough finite observations.
I believe huangwb8 has suggested some changes regarding same. However, I am new to R and it would really help if you can help me resolve the issue.


What happens when no menu input from user?

It doesn't mention what happens when the user does not input anything into the Auto-Attendant Menu. What happens? Also how long does it take before this happens?
Can any of the parameters be modified?

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

ID: a9ee465f-fae3-0ea0-bdf3-f7b8c3d91709
Version Independent ID: a9ee465f-fae3-0ea0-bdf3-f7b8c3d91709
Content: Set up an auto attendant for Microsoft Teams - Microsoft Teams
Content Source: Teams/create-a-phone-system-auto-attendant-experiment.md
Service: msteams
GitHub Login: @DaniEASmith
Microsoft Alias: danismith

Thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Android - Payments - app crashed after make default payment

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:
Precondition: Add payments into your account

Launch the app
Log in with your account
Go to Setting - Payments
Select on of your bank account
Tap Make default payment method
Put your password
Tap Make default payment method

Expected Result:
Selected account added as Default payment
Actual Result:
App crashed when making default payment
Workaround:
Unknown
Platform:

Where is this issue occurring?

iOS
Android

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers<EMAIL_ADDRESS>Logs: https://stackoverflow.com/c/expensify/questions/4856
https://user-images.githubusercontent.com/93399543/193384145-608785c0-f940-46f7-8a0c-2c65499c535c.mp4
log1.txt
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

I'm not able to reproduce the crash in staging, but I can see an error in the console that may be related:

Tested with<EMAIL_ADDRESS>and with<EMAIL_ADDRESS>and got the same results... no crash, but the error in the console. There is also no feedback on if the change was applied or not

The error is happening around here:

cc @Justicea83 as this may have happen because of this change: https://github.com/Expensify/App/pull/10447

Closing this issue in favor of this.

@Justicea83 it is not obvious to me how this issue is connected/related/similar to https://github.com/Expensify/App/issues/11454, can you explain :)? otherwise I think we should reopen this.

I think I linked the wrong issue. This is it.


Fix security issue

I didn't see the need for class components because there isn't any state living here. I also fixed the eslint reporting of a security issue for not using  rel="noreferrer" but I also added noopener as well.

thanks! Sorry this took so long, will fix in the next refactor


Generate language selector links with use_directory_urls in mind

We use use_directory_urls true on our build, because our webserver doesn't use index files, so we need the full file path.
I think the links generated for the language selector should acknowledge that option to generate the links like this when use_directory_urls is set to true: /fr/index.html, /de/index.html etc.

Thanks for the input @Delivator, that's a very good point!
I have this done locally but want to add tests before releasing it, I'm on it mate

@Delivator MR is up, do you have the possibility to test it and validate that it works as expected?

@ultrabug How can I test this? I only know how to install via PIP.

 I totally got it wrong.
Mkdocs adds adds the /index.html to the links if use_directory_urls: false not true. (Docs for reference)
So here we would need to check if config.get("use_directory_urls") is False:
https://github.com/ultrabug/mkdocs-static-i18n/blob/3a9efa8c8c68d9626409c99fb0732971ad3a1802/mkdocs_static_i18n/plugin.py#L210
Sorry again.

No it's me who apologizes @Delivator I saw it during development but I lost it because of the problems I ran into for the tests...
version 0.12 is released to fix that !
PS: like the project? spread the word and give it a :star: if you feel like it <3

@ultrabug Awesome, thanks a lot!
Yeah it works really well! We should probably add a page to our docs mentioning all the awesome plugins we use :)


How can use this library for Favorite

Hi, thanks for this awesome library ❤
But i have a problem, how can i use this in favorite feature?!
I want when click this button and added into favorite list, turn on button for ever for this post. and when delete post from favorite list turn off this button !
How can i it? can you send me code?

Thanks. :)
You can use setChecked method on SparkButton to enable or disable the state of the button.

Can you send me sample code?


Translate May 15 covid report into Spanish

Happy weekend @nextstrain/spanish,
The situation report from 2020-05-15 is ready to be translated to Spanish. This week's report is short and focuses on mutations. It's targeted more at the public than some of our previous reports and is intended to answer some of the many questions we've been receiving on the subject. I hope it will be useful for Spanish speakers.
Sadly, this will be our last weekly Situation Report for awhile although we'll issue periodic sit-reps as needed. Thank you, thank you, thank you for translating these reports. It's been an amazing collaborative effort to be involved in. I'll miss working with you on them.  I've personally derived a lot of global solidarity from our work together. Although we will all probably enjoy having more time on the weekend!
Branch to translate on: sit-rep_es
File to translate: https://github.com/nextstrain/translations/blob/sit-rep_es/narratives/translations_ncov_sit-rep_es_2020-05-15.md You can translate directly in this file, but please remember to push often as other people may be working on the translation!
Link to preview: https://nextstrain.org/community/narratives/nextstrain/translations@sit-rep_es/ncov/sit-rep/es/2020-05-15
Twitter post to translate:
“Our latest situation report focuses on viral mutations: why they occur, when they matter, and how they can be useful in tracking outbreaks. The report is now available in Spanish.
Since repeated patterns of viral introduction and spread across the world have become clear, we'll be pausing weekly situation reports for a while. We will publish periodic situation reports as the data allows.
Thank you to @, @, @ for their rapid translation of this report. Thank you to @, @ for their work on previous translations as well."
Regards,
Cassia
Logistics
Please update the translations board as you work on the translation: https://github.com/orgs/nextstrain/projects/7
Please assign yourself to the translation if you’re working on it this week.
When a translation is ready for publication -- at minimum meaning two people have worked on it and both agree that it’s ready -- please create a pull request to merge to master and tag me and the issue in it!
Discussion board for your team is here: https://github.com/orgs/nextstrain/teams/spanish
Standard rules for translation:
Note that the file to translate is in Markdown. In general, it is important not to change any formatting or links. (Although it is okay to update Wikipedia or CDC links to the appropriate language version.) Comments to help with translation are noted in comment symbols like <! -- Comment -->.
Please add your name under translators: with new line, tab, and dash, formatted just like authors are. Please also add a link to your professional page (can use Twitter) under translatorLinks:.
Note: You may know of other great resources available in Spanish; please don’t add them to the situation report. We need to keep content the same across all translations, so we can be confident in the accuracy of what we publish. Thanks for understanding.
At minimum, I require two sets of eyes on every translation; one of those people should have a background in phylogenetics. Although if you have more, that’s fine too.
Feel free to use a live, online editor like hackmd (sign in with GitHub) to translate together.

Hey y'all- glad to start off our last weekly report! I can start translating the first half through "Variation in viruses' genetic code is useful for tracing outbreaks" if someone else can do the second half?

Just pushed the translation for the first half -- anyone willing to do the second half?

Hi @miparedes and all,
Apologies for the late reply. I could do the second part.
Cheers,
Roy

Hi @miparedes
Translation for second part and proofreading of first part is done. If you could proofread my translation, we'll be done :)
Cheers,
Roy

Thanks so much @Cholokiwi ! Just pushed minor edits and it should be good for publication @cassiawag . Again thanks so much for all the work these last couple of weeks -- it's been a privilege to work with you all.

Published: https://nextstrain.org/narratives/ncov/sit-rep/es/2020-05-15! Thanks all.
Would one of you mind translating the twitter post?

Thanks @cassiawag!
Please find twitter post below.
"Nuestro último reporte situacional del COVID19 se enfoca en mutaciones virales: ¿Porque ocurren las mutaciones?, ¿Cuándo son importantes?, y ¿Cómo pueden ser útiles para rastrear los brotes? El reporte está ahora disponible en español."

Thanks Roy! It's tweeted now.


Change team of a user

User story

As a website admin
I need to be able to change the team of a user
So that I can add new admins or assign users special roles.

Acceptance criteria

The user data can be requested by the frontend to be displayed in the frontend.
There is an endpoint that can change the teams of a user. The endpoint receives all the teams a user should have and after the update the user is assigned to these and only these teams.
This functionality is implemented as an appwrite function that can be accessed through the appwrite API.
This function can only be executed by admins.
There should be a (Python) script that creates the function for appwrite if it does not yet exist.

All required functionalities are already fulfilled by the appwrite api.
The Team api provides methods to get, create and delete memberships (https://appwrite.io/docs/client/teams).
Precondition: At leased one user in the team 'Admins' with an 'owner' role (done via init-script).
Make someone admin -> a team member of 'Admins' with the role 'owner' can create a membership for user in team 'Admin', if the role of the new admin is also set to 'owner', the new admin also can make users to admins.
Remove somebody from 'Admins' team -> also only 'Admins' with 'owner' role can do that.


Add info about Enterprise Managed Users

Solves #86.

@qmacro: I cannot yet see my contribution on the corresponding SAP Help Portal page. Could you please check?

@qmacro: I checked. The publishing step for HTML wasn't done yet. I's done now.

@qmacro: I checked. The publishing step for HTML wasn't done yet. I's done now.


[medCropToolBox] fixed user-splittable crash

Solves https://github.com/Inria-Asclepios/music/issues/367
(The PR that introduced this could not have worked properly. Please make sure changes are properly tested before making PRs, and also after making changes requested by reviewers)

Solves the pb, nice.
Needs to be merged quickly.

Good for me!


WSL support + Fake duplicate records issue.

Additional parameter to support WSL.
Register-SecretVault -ModuleName 'SecretManagement.LastPass' -VaultParameters @{wsl = $true }

I found another issue.
I had the following error with our company vault (2k records)

In Get-Secret, there was a logical issue with the following statement.
   Where-Object {
            $_ -match $lsLongOutput | Out-Null
            $pattern.IsMatch($Matches[2])
        }

 $_ -match $lsLongOutput | Out-Null do not reset $Matches to $null and thus, if your previous result was $true and the current one is $false, $Patter.IsMatch get evaluated against the previous $Matches assignment.
The end result for me was that all folders, which did not matches $lsLongOutput, got added in the list anyway because $Pattern.IsMatch picked up the previous iteration record.
Get-SecretInfo failed with the aforementionned error for that reason.
Using :  Where-Object { $_ -match $lsLongOutput -and $pattern.IsMatch($Matches[2])} | instead of the orignal statement fix the problem.

Closing this one, I did that on my main branch, will reopen through feature branch to make sure I don't commit stuff over in-between.


build broken

The following is the content of zabapgit:
No leaf found: zif_abapgit_gui_page,
zif_abapgit_gui_page->faces zif_abapgit_gui_event_handler, zif_abapgit_gui_page->faces zif_abapgit_gui_renderable,

abapmerge's npm test failing

yeah, see https://github.com/larshp/abapGit/issues/2525

and https://github.com/larshp/abapmerge/issues/80

Nice, thank you very much for the information. Please, consider merging this PR for abapmerge:
https://github.com/larshp/abapmerge/pull/81

try again, latest version, build should be fixed now

Indeed, the current version of zabapgit is OK. Thank you very much. Even abapmerge works on my machine. Well done!


Improve UI of Login and SignUp Activity

Fixes #553
Screenshots for the change:
Before:-

After:-

This is my first PR here. Can anyone guide how things goes here.

@dreadpool2  review please

@nikit19 review please

@nikit review pls


Make tests consistent

don't rerun pit, if we run in a timeout
make sure we are getting the menu from the workbench window

@LorenzoBettini or @echebbi would you have a look at these changes and merge please?

Thank you @JKutscha !


Design the Website to be Reponsive

Once we have our main CSS polished and finish we need our website to be accessible to different device's screen sizes

used skeleton framework to make framework responsive


Speculative fix for store_dart_post_cobject signature mismatch with ffigen >= 6.0

Based on this comment.
This fixes the syntax error and allows my project to build with ffigen >= 6.0. I haven't tested thoroughly and I don't fully understand what's going on, so I'm relying on CI to validate it. If CI doesn't pass then I'll dig into it more.
This is a breaking change, as I expect this PR to cause flutter_rust_bridge to break with ffigen < 6.0. ffigen can be upgraded by running dart pub global activate ffigen.
Resolves #478 and resolves #512.

Looks like I need to run codegen in at least one of the example projects. I'll update the PR shortly.

Does the CI needs to be updated to match the requirements in CONTRIBUTING.md, or does CONTRIBUTING.md need to be changed to match an 80-character line length in the example projects? Codegen formats with a line length of 80, but the existing code is 120. 120 matches CONTRIBUTING.md. If I format it I get one error, and if I leave it I get another error.

I'm also unsure about the valgrind stuff. I don't have time to dig into it now, but I'll tackle it as soon as I'm able.

Well I admit it is a mixed line length currently: The frb_dart is 80, since the pub.dev only give "scores" to 80 width not 120. The examples is 120, since it is more easy to read...

I think something is still broken here. Bindgen on CI seems to be spitting out code with a line length of 80 and then complaining that it doesn't match what's been checked in.
I'll try to fix it when I look at this again.

I've run the following commands and pushed the changes:
flutter_rust_bridge_codegen --rust-input frb_example/pure_dart/rust/src/api.rs --dart-output frb_example/pure_dart/dart/lib/bridge_generated.dart --dart-format-line-length 120

flutter_rust_bridge_codegen --rust-input frb_example/with_flutter/rust/src/api.rs --dart-output frb_example/with_flutter/lib/bridge_generated.dart --c-output frb_example/with_flutter/ios/Runner/bridge_generated.h --dart-format-line-length 120

According to my git tooling, nothing actually changed in the files. I'm not sure why CI is failing, since it's running effectively the same command. Maybe it's a line ending issue?

For anyone coming after, you currently need to do the following on Windows to pass CI:

Run codegen on the examples, making sure to add --dart-format-line-length 120 to the bindgen command

Open .\frb_example\pure_dart\dart\lib\bridge_generated.dart

Find the following line (should be near the end of the file):
typedef uintptr_t = ffi.UnsignedLongLong;

and replace it with the following:
typedef uintptr_t = ffi.UnsignedLong;

Commit and push the changes

Alright, I think this is ready to merge from my side. Let me know if you'd like any other changes.

It's now the case that the checked-in bridge_generated.dart is not technically valid for all platforms.

I agree... Feel free to PR, either for doc, for justfile, or for code!


minAvailable vs maxUnavailable

Hello!
Reading README.md, I understood that the controller works by creating a PDB with minAvailable: 1.
But when I've deployed the controller, the PDBs are created with maxUnavailable: 1.
It looks like this behavior has changed in PR #16, but it wasn't updated in the README.
The other thing is that I really didn't understand why minAvailable: 1 shouldn't work (as #16 states).
Reading the code I see that changing this behavior ( maxUnavailable to minAvailable ) with env variables or entry point command flags is not possible, right?
Any suggestions on how to use minAvailable instead maxUnavailable ??

If you have 10 pods of a deployment and use minAvailable: 1 then it's allowed to have 9 out of 10 pods unavailable, which is not really desirable in most cases.
We should at least fix the README, but we could also make it configurable if there is a good use case to use something else.


Feature Request: Integration of Multimodal LLMs

I want to suggest a significant enhancement that could vastly expand the capabilities of TaskingAI - the integration of multimodal Large Language Models (LLMs), particularly those akin to GPT-4V, which possess the ability to process and understand images alongside text.
I believe that this enhancement aligns with TaskingAI's commitment to innovation and would significantly benefit the diverse user base seeking to explore the frontiers of AI applications.

Thank you for your suggestion on integrating multimodal LLMs like GPT-4V into TaskingAI. We've accepted your idea and included it in our development roadmap. This enhancement will enhance our platform's capabilities and offer our users a more comprehensive AI experience.
Stay tuned for updates, and thanks again for your valuable input!

Great suggestion Casey! You are absolutely right. As a fact, the integration of multimodal LLMs is already undergoing. I cannot provide a exact timeline now, but you can expect to see that feature soon. Please stay tuned


We should provide images for each officially supported Go version (that is, for the two latest major versions). The Go version included should be expressed via tags, e.g. v1-go1.16, v1.1.0-go1.17 and so on. Minor- and bugfix versions of Go are not relevant for this use case.

The minor version will appear in the SBOM (e.g. when -std is used or in the tools element once we include the compiler info there). This will need more planning.


Add configuration to hide foreground notifications (Android)

hi @colmharte would appreciate your help again
We are still getting some feedback from Playstore (NZ COVID Tracer App 3.0.2) that the notification stuck issue is still occuring:

Constantly stuck checking exposure keys on my s10. Chewing through battery 5% in 10 min at this rate my battery will be flat in just over 3 hours. If this can be fixed will need to delete app.

Still getting the infinite checking keys bug. Apart from that it seems to do what it's supposed to.

It seems that workers with a FGS do not have a timeout, while normal workers do timeout after 10 min
Added a configuration to hide foreground notifications altogether

@willatrush I have concerns that this change is not fixing your actual problem. Is the battery being consumed by ENS or your covid app? Whether you are using a foreground service or not will not change battery consumption. The 10 minute timeout for non foreground services also is not the solution. I can't see how this module would be spending 10 minutes plus processing. So hiding the foreground notification is masking the issue rather than solving it

@colmharte my 2 pence about this change in the light of your comment:

I have concerns that this change is not fixing your actual problem. Is the battery being consumed by ENS or your covid app? Whether you are using a foreground service or not will not change battery consumption. The 10 minute timeout for non foreground services also is not the solution. I can't see how this module would be spending 10 minutes plus processing. So hiding the foreground notification is masking the issue rather than solving it

After the previous fixes for the stuck "Checking for exposures" notification from the foreground service we haven't been able to reproduce that issue yet, so we are just trusting our users on this one and applying some general thinking. To answer your question about battery consumption, we don't know. We had some battery issues that weren't related to EN or the plugin, but those should be fixed in our app in the version some users reported it for.
While we are looking for a way to reproduce the "stuck" issue, the general thinking is:

Service being foreground can (somehow) hypothetically be an essential prerequisite for it getting stuck. In this case not running it in foreground could solve the issue (although I admit, this is a stab in the dark).
Or it's getting stuck somewhere else. In this case not running it in foreground can partially mitigate the problem by enforcing  a 10m timeout so that if it's stuck, it's not stuck forever.

That reasoning alone may not justify modification of the plugin used by many developers enough. However, I think there could be some unrelated functional benefit that's generally useful. For the servers that allow for processing in under 10m (I'm assuming most if not all of them), developers would be able to choose how they want their apps to behave: stick with the defaults when checks are surfaced to the users or make checks invisible.


python312Packages.uiprotect: 5.3.0 -> 5.4.0

Diff: https://github.com/uilibs/uiprotect/compare/refs/tags/v5.3.0...v5.4.0
Changelog: https://github.com/uilibs/uiprotect/blob/refs/tags/v5.4.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 329166 run on x86_64-linux 1

5 packages built:

home-assistant-component-tests.unifiprotect
python311Packages.uiprotect
python311Packages.uiprotect.dist
python312Packages.uiprotect
python312Packages.uiprotect.dist


text and number input: submit value when enter is pressed

With this change, hitting enter when focused on a text or number input submits its value to the store (i.e. has the same effect as blurring). This is convenient because hitting enter is a typical cue that a user is done with editing the value. The other somewhat coupled (and not the most elegant) reason is that when a user hits enter, we want to make sure the value is submitted before rerunning the juttle program in https://github.com/juttle/juttle-viewer/pull/20.
@mnibecker

lgtm


Cmake build

@mcallegari
I opened this pull request for #1408 "Update build system to CMake".
It uses MSYS64 + Qt + MinGW on the Windows platform.
It also works well on Unix platforms.
Please review it and give me feedback.

Since the git history is too complex, I will close this PR and reopen a new PR.


Viewer and Editor roles are disabled

Describe the bug
Previous 0.x versions of K8up (helm chart) come with Viewer and Editor roles included.
This is not the case anymore.
Additional context

The Viewer and Editor roles are already there, but not activated in Kustomize
Old versions defined a catch-all ClusterRole like:

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  labels:
    app.kubernetes.io/instance: k8up
    app.kubernetes.io/managed-by: Tiller
    app.kubernetes.io/name: k8up
    app.kubernetes.io/version: v0.1.10
    argocd.argoproj.io/instance: backup-k8up
    helm.sh/chart: k8up-0.6.1
    rbac.authorization.k8s.io/aggregate-to-admin: "true"
    rbac.authorization.k8s.io/aggregate-to-edit: "true"
  name: k8up-edit
rules:
- apiGroups:
  - backup.appuio.ch
  resources:
  - '*'
  verbs:
  - '*'

Since Helm charts is basing its RBAC objects on Kustomize, the newest Chart PR doesn't include viewer and editor roles either at this time.

Expected behavior
Viewer and Editor roles should be included again.
However, we could discuss following options:

Use the fine-granular roles (for each CRD archive, backup, check. restore. prune, schedule prebackuppod its own viewer/editor role)
Use the catch-all roles mentioned like before
Combine both options 1) and 2) to support easy, but also granular role bindings
Split into "user-facing" and "system" roles, e.g. user facing are schedule, prebackuppod and restore(in one role definition), the rest is "system" (also in 1 role definition).
Other combinations?

To Reproduce
Steps to reproduce the behavior:

Specs

kustomize build config/rbac

@schnitzel
Do you have requirements for more granular roles? or is the catch-all (as until now) good enough?

@schnitzel
Do you have requirements for more granular roles? or is the catch-all (as until now) good enough?

@ccremer
mhh, no specific need from our side, lagoon is running as admin within a namespace so as long as the admin role can do everything with k8up it will be happy

@ccremer
mhh, no specific need from our side, lagoon is running as admin within a namespace so as long as the admin role can do everything with k8up it will be happy

Thanks for the answer.
I think meanwhile I have found the best possible option: role aggregation. by simply settings labels, the API will ensure that the K8up viewer and editor roles get added to built-in default view, editor and admin roles automatically, so no need to maintain custom role bindings. This also reflects the current behaviour of previous K8up versions, where the exact same method was used.

Thanks for the answer.
I think meanwhile I have found the best possible option: role aggregation. by simply settings labels, the API will ensure that the K8up viewer and editor roles get added to built-in default view, editor and admin roles automatically, so no need to maintain custom role bindings. This also reflects the current behaviour of previous K8up versions, where the exact same method was used.


Fix shfmt linting error

Thanks so much for this PR! Merging now, but would you mind following up on why shfmt is complaining? No worries if you don't - I just won't be able to pull this and investigate myself until later this weekend.
As a side note, I love the PR template and will absolutely be stealing it :)

I found the linting error bug. I haven't used shfmt before, so I had to install it.
As for the PR template... it came from this repo...
https://github.com/MetricMike/asdf-awscli/blob/main/.github/PULL_REQUEST/pull_request_template.md
I thought I was just following your contributing guide. Perhaps running the code through shellcheck and shfmt should be added to that doc. ¯\_(ツ)_/¯

@MetricMike I added some detail to the contributing guide as well. ☝

Oh XD. #10 came without it, so I forgot.
Thanks for the contribution guide update. Github actions used to run on every PR so it was more obvious if something failed a check, but cryptomining forced a change where I've got to kick it off manually for first time contributors now.

Those damned cryptominers ruining it for everybody smh. thanks dude


New version: Jackett.Jackett version 0.21.631

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/116393&drop=dogfoodAlpha

@wingetbot run

/AzurePipelines run


feature request: source reset options supported

For the source reset option, add support for ?skip=entitlements which removes accounts, but not entitlements or roles
see: resetting a source
I've had to remove all accounts on a couple of occasions but did not want to lose the roles.

Additional menu items please. It’s a small number of options and mostly I’ve reset all.
Although skipping entitlements might become my go to.
Get Outlook for iOShttps://aka.ms/o0ukef

From: yannick-beot-sp @.>
Sent: Friday, October 14, 2022 3:13:36 AM
To: yannick-beot-sp/vscode-sailpoint-identitynow @.>
Cc: Rob Buskens @.>; Author @.>
Subject: Re: [yannick-beot-sp/vscode-sailpoint-identitynow] feature request: source reset options supported (Issue #26)
Completely doable. Would you prefer an additional menus like "reset source" and "reset source skipping entitlements" and "reset skipping accounts" or an additional step: instead of asking for confirmation, we could have the choice of resetting
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Completely doable.
Would you prefer an additional menus like "reset source" and "reset source skipping entitlements" and "reset skipping accounts" or an additional step: instead of asking for confirmation, we could have the choice of resetting everything or skip something?
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/yannick-beot-sp/vscode-sailpoint-identitynow/issues/26*issuecomment-1278650129__;Iw!!MsNKLpFGsw!M9uG5lnpWFhlAcqYufxDG8iZs_u3zp9wU_xIg8nKChbb-gRyUTME4z9ibFEJ6JXM-I3Bc_Y_bgPIbh5s2k5XGT8LIvgS$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AZH2GPKDEFBIXKHOTYHEPP3WDEI3BANCNFSM6AAAAAARCRYS6E__;!!MsNKLpFGsw!M9uG5lnpWFhlAcqYufxDG8iZs_u3zp9wU_xIg8nKChbb-gRyUTME4z9ibFEJ6JXM-I3Bc_Y_bgPIbh5s2k5XGWdPDs7p$.
You are receiving this because you authored the thread.Message ID: @.***>

Implemented in v0.0.14

Implemented in v0.0.14


AvailabilityGroup awareness with IndexMaintenance if databases explicitly listed?

I've seen somewhere notes that say the IndexMaintenance is aware of Availability Groups and won't touch secondary replicas when specifying the AVAILABILITY_GROUP_DATABASES as the target.
If I specify a single or list of databases that are in an AG, will the script still figure that out and skip the secondaries?
Thank you!

IndexOptimize will always skip secondary replicas (regardless of how you are selecting them).


Switch from uniform to defines

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/16006/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/16006/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/16006/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/16006/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/16006/merge
https://gui.babylonjs.com/?snapshot=refs/pull/16006/merge
https://nme.babylonjs.com/?snapshot=refs/pull/16006/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/16006/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/16006/merge/testResults/webgl2playwright/index.html


Windows DLL for version 0.7.5

I succesfully compiled Win64 DLL for version 0.7.5. It currently fits my purpose but it was absolutely not tested outside that context. Please feel free to test and use it in the binary distribution.

libdmtx-64.zip


Horribly slow file descriptors over docker socket

docker logs -f blah is horrendously slow, is it not line buffered or something?
It's fast from the dlite VM over SSH, so there's some fuckery on that.
Another example is docker pull. The output comes in patches.
Ty for dlite by the way, been using it for a while now for some tasks!

@akatrevorjay is it possible for you to create an example application with the same issues?

This problem isn't solved, it's just slightly better now.
Also the logs command doesn't work either?
Hmm

You can especially tell when watching a docker pull of an image, the refresh rate is not near what say docker-machine (xhyve or vbox drivers) provides.

I'm seeing this as well. For logs, pull and the likes I'm currently using ssh to circumvent this.
  function dl () {
    nmap local.docker -PN -p ssh | grep -q 'open'
    if [ "$?" != "0" ]; then
      echo "Error: The SSH port is not opened at local.docker"
      return 1
    fi

    ssh -q -o "BatchMode yes" local.docker docker $@
    return 0
  }

I've found that it only seems to matter when streaming, ie using the -f option.

What seems to matter? Are you saying you get better performance streaming vs not streaming?

I'm saying streaming doesn't even work at all.

Non-streaming, ie docker logs, seems to work fine.

It's the proxy that's causing this.
It works fine going directly to port 2375. Also the CPU usage skyrockets by the dlite process during a simple download, no extraction. At the same time over SSH watching the system, theres's no cpu usage to be seen.

It's nearly unusable while streaming unfortunately, spite at the time has
high CPU usage that isn't seen from inside of the vm. Maybe the loop is too
tight in lib_proxy.go?
If I avoid the unix to tcp proxy and connect directly to port 2375, all is
well. An easy test is just watching the output of docker pull, you'll see
the refresh rate start out not so great,  and it at least appears to get
worse, multiple seconds in between updates.
On Mar 13, 2016 3:03 PM, "Nathan LaFreniere"<EMAIL_ADDRESS>wrote:

What seems to matter? Are you saying you get better performance streaming
vs not streaming?
—
Reply to this email directly or view it on GitHub
https://github.com/nlf/dlite/issues/139#issuecomment-196021422.

i can replicate, working on a fix now

interestingly enough, it was actually the reverse of what we thought. streaming logs is a plain http request, not an upgrade request so it wasn't going over the raw socket. i've switched things to always hijack the request and use the raw socket instead, which from my testing has drastically improved things.
if you can, test out 2.0.0-beta4 and let me know how it looks for you

Yep, all better!
So, Docker uses long polling for streamed log output? Strange. Very strange.


Fix SoChildList auditing

Original pull request by Lei Zheng (Bitbucket: realthunder, GitHub: realthunder).

The current implementation of SoChildList::truncate() notify path auditor by calling its removeIndex() with forward order. This creates problem according to SoPath::removeIndex() implementation here. This patch corrects it by reverse the order when calling removeIndex().

Original comment by Thomas Moeller (Bitbucket: TheHubbit, GitHub: TheHubbit).

The change looks good. Thanks for sending a fix. Could you please also provide an example how to reproduce this problem and make sure it is fixed with this change?

Original comment by Lei Zheng (Bitbucket: realthunder, GitHub: realthunder).

The following example is provide using python with pivy
from pivy import coin
parent = coin.SoGroup()
child1 = coin.SoGroup()
child2 = coin.SoGroup()
parent.addChild(child1)
parent.addChild(child2)
path = coin.SoPath(2)
path.append(parent)
path.append(child2)
path.getLength() # print 2
parent.removeAllChildren()
path.getLength() # expect 1, but print 2

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

Thanks a lot Lei and Thomas, I think we’re good to merge.


With commonAxis, dragging axis doesnt update axis style

If we have a commonAxis, the text on the first axis is visible, the others have an on-hover functionality. If I drag the first axis to the middle, the styles do not update.
The problem is that the order on the dom is still the same, so it believes it to still be the first axis. Need to look into how to get the ordinal drawn order...
See px-vis-multi-axis for code

Not relevant post design refresh


support for mobile layout

Summary 🎯
I added support for mobile layout: on mobile the table of content is displayed in the left sidebar:

One thing is missing, but I couldn't figure it out. After clicking on something the sidebar remains opened.
Additionally there are a few minor changes:

to allow development in browser
there was a react error on the console: each child in a list should have unique key

@sotiwin

What do you think of using the left sidebar? Maybe there are other options. For example put an icon in the top of the page, which would open table of contents in a floating window.

I guess the current approach is good because:

it delivers value with fewer changes
it naturally fits with the native feature (sidebar) of RemNote

However, a floating window could be great if we can develop it well. Feel free to try it if you're interested :)

@sotiwin

What do you think of using the left sidebar? Maybe there are other options. For example put an icon in the top of the page, which would open table of contents in a floating window.

I guess the current approach is good because:

it delivers value with fewer changes
it naturally fits with the native feature (sidebar) of RemNote

However, a floating window could be great if we can develop it well. Feel free to try it if you're interested :)

Okay, maybe in the future :)
For now I updated the merge request and reverted the manifest changes.

hmm, I couldn't check its behavior because of this error.

However, the screenshot looks good so I approve this. Thank you your contribution!

I'll merge it and upload to plugin store

hmm, I couldn't check its behavior because of this error.

I totally had forgotten the tricky nature that it doesn't work with browser but with the native app.
Great work!


Enabling 2FA breaks sync

A couple users have reported that enabling two-factor authentication for an already syncing account breaks the sync.

I run into this issue. To make it work again, i've needed to

deactivate 2FA
remove the application access in the security panel of my gmail account
delete the account in Nylas
re-add the account in Nylas

Confirmed

@tito @Cu8eR So, I tried reproducing the issue but couldn't. I followed the following steps:

Sync an account without 2FA with N1
Turn-on 2FA for this account
Observe that the account isn't syncing anymore
Delete the account from N1 and re-add it
Observe that the sync is working again.

Did you do anything else different? Did you try authenticating with an app-specific password?
regards,
Karim

@khamidou I have the same problem, on mac, do your steps, but not work for me, how to use app-specific password? N1 is using web login.

Sounds like it's happening Exchange as well.
https://nylas.zendesk.com/agent/tickets/2221

Another report from Peter @ Nylas.

Same problem for me (on Mac). I used N1 for a while without problem but suddenly all my accounts that use 2FA don't sync anymore. Putting the password in again (for the gmail using web login) that I used in the first place doesn't help. I keep getting the message:

Several of you accounts are having issues. You will not be able to send or receive mail.

I contacted support and had them delete my old account data in an attempt to get around this issue, which did not work. Is there any eta for having this fixed? I have cancelled my Nylas Pro subscription in the meantime.

Another incidence: https://nylas.zendesk.com/agent/tickets/5828

An incidence with IMAP: https://nylas.zendesk.com/agent/tickets/6184

Having the same issue at the moment but I'm using a self hosted sync engine if that makes any difference.


small device iOS

For example, when pressing the back arrow on the top left of the screen, the time at the top of the
phone overlaps the back arrow, making it hard to click and see, some apps allow you to switch
back to the app when you tap next to the time on iOS so it causes the bitcoin wallet to exit
to a different app instead of going back

Done,

iOS not out yet


[API] Add pagination to ListBranches

as title followup of  #14202 for api & ui ...
add pagination to GetBranches-git-backend

util, helper and etc package names should be depreciated.


Use maven frontend plugin + fix parent groupId

Use maven frontend plugin to automatically download node+npm.
Fix parent groupId error

Hi @petro-rudenko , thanks for your commit, I'll have a look at it today :)

I tested the updated build config on my machine and it builds fine, I am merging the PR. Thanks!


Seg fault when executing spot termination script

lifecycled: time="2018-12-11T21:57:55Z" level=info msg="Looking up instance id from metadata service"
lifecycled: time="2018-12-11T21:57:55Z" level=info msg="Starting listener" instanceId=i-xxx listener=spot
lifecycled: time="2018-12-11T21:57:55Z" level=info msg="Waiting for termination notices" instanceId=i-xxx
lifecycled: time="2018-12-11T22:00:30Z" level=info msg="Stopped listener" instanceId=i-xxx listener=spot
lifecycled: time="2018-12-11T22:00:30Z" level=info msg="Received termination notice" instanceId=i-xxx notice=spot
lifecycled: time="2018-12-11T22:00:30Z" level=info msg="Executing handler" instanceId=i-xxx notice=spot
lifecycled: panic: runtime error: invalid memory address or nil pointer dereference
lifecycled: [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x878249]
lifecycled: goroutine 1 [running]:
lifecycled: os.(*File).Name(...)
lifecycled: /usr/local/Cellar/go/1.11.1/libexec/src/os/file.go:50
lifecycled: github.com/buildkite/lifecycled.(*FileHandler).Execute(0xc00000c030, 0xab5ac0, 0xc0000521c0, 0xc00030cc00, 0x3, 0x3, 0x14, 0x5c10337e)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/daemon.go:163 +0x29
lifecycled: github.com/buildkite/lifecycled.(*spotTerminationNotice).Handle(0xc0000d7ae0, 0xab5ac0, 0xc0000521c0, 0xab09e0, 0xc00000c030, 0xc000204f00, 0x0, 0xc0001458b0)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/spot.go:91 +0x11e
lifecycled: main.main.func1(0xc000196e10, 0x0, 0x0)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/cmd/lifecycled/main.go:150 +0x7be
lifecycled: github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin.(*actionMixin).applyActions(0xc0000e86a8, 0xc000196e10, 0x0, 0x0)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin/actions.go:28 +0x6d
lifecycled: github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin.(*Application).applyActions(0xc0000e8690, 0xc000196e10, 0x0, 0x0)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin/app.go:551 +0x3f
lifecycled: github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin.(*Application).execute(0xc0000e8690, 0xc000196e10, 0x0, 0x0, 0x0, 0x0, 0x0, 0xc0000d66e0, 0x0)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin/app.go:390 +0x8f
lifecycled: github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin.(*Application).Parse(0xc0000e8690, 0xc00001c1b0, 0x0, 0x0, 0x1, 0xc0000a4198, 0x0, 0x1)
lifecycled: /Users/lachlan/go/src/github.com/buildkite/lifecycled/vendor/github.com/alecthomas/kingpin/app.go:222 +0x1fa
lifecycled: main.main()

This is a perplexing one. It looks like the handler object getting passed in is nil. Any ideas @itsdalmo?

Assuming that this is version 3.0.0?
Based on these log entries:
lifecycled: os.(*File).Name(...)
lifecycled: /usr/local/Cellar/go/1.11.1/libexec/src/os/file.go:50

And os.(*File).Name() being defined as:
func (f *File) Name() string { return f.name }

It doesn't seem like Handler itself is nil, but rather Handler.file? Perhaps lifecycled was started without --handler being specified, and since it's not required or validated to be non-nil, this is what causes the crash? Either way, with the current implementation in main.go then --handler should be a required argument - I can submit a PR.

Sidenote; I'm wondering if perhaps more of the logic that currently lives in cmd/lifecycled/main.go should be moved into the module so it can thoroughly tested (would be a good idea if we want to support more handlers as well, e.g. #54).

Yup, I think it makes a lot of sense to move as much as possible of main.go into something testable.

Ref this PR: https://github.com/buildkite/elastic-ci-stack-for-aws/pull/507
Seems like handler not being set might have been the issue here? Sorry about that!

Yeah, I suspect that was the cause, as we weren't restarting lifecycled after setting it's config. No problems, appreciate your help fixing it!

Closed via #63.


Remove GoCenter since it is deprecated

@Clivern your changes have been merged, thanks for your contribution 👍


Method not allowed - correct procedure

ALT defined in its specification REST API methods for getting and setting service records policy. However, service records policy won't be used in this application. This question is about proper behavior of the application (or setting a precedence what to do, in case something like this happens in other applications.) when it encounters a REST  API method that will not be implemented.
Following options need to be analyzed and one picked:

delete get/setServiceRecordsPolicy from API specification ( I was told, that this is not an option, in order to keep API same for all applications.).  -- no further action on server side is needed
delete only controller methods on server side -- default message and status code will be returned
allow those methods to return also 405 Method Not Allowed -- this must be implemented in specification, the return code should be added to ApplicationPattern and code in ALT needs to return this status code
implement the methods on server side, return existing status code 400 (this does not really tell the real reason why an error is returned and can be confused with not-expected application behavior)
implement the methods on server side, return existing status code 200 (this does not really tell the real reason why was the request successful with no data to be returned and can be confused with expected application behavior)

In options 3,4,5 the question is also, if this request should be logged by OAMLog application.

Conclusion: correct procedure to implement is:
3. allow those methods to return also [405 Method Not Allowed](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/405) -- this must be implemented in specification, the return code should be added to ApplicationPattern and code in ALT needs to return this status code
Created #263 to track specification changes.
Created #264 to track implementation changes in ALT.
Created openBackhaul/ApplicationPattern#593 to track changes in Application Pattern.

As per last discussion, we need to recheck if 405 Method not allowed would be a correct response code for this scenario. The proposed response code is 404.
Assigning back to Dana for rechecking

Path deleted from specification.


chore: bump sdk version written in code

Description
I overlooked the version changes when reviewing #124, so bump those
References
Review Checklist

[x ] I have clicked on "allow edits by maintainers".
[ ] I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
[x] The correct base branch is being used, if not main
[ ] I have added tests to validate that the change in functionality is working as expected

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 25.45%. Comparing base (704f526) to head (46c8cae).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #125   +/-   ##
=======================================
  Coverage   25.45%   25.45%
=======================================
  Files         102      102
  Lines       10576    10576
=======================================
  Hits         2692     2692
  Misses       7612     7612
  Partials      272      272

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Entity validation should be able to call validations on sub-objects

I'm submitting a feature request
Current behavior:
There's no way to pass validation down to sub objects
Expected/desired behavior:

I'd like to be able to pass validation down to associated sub objects.
export class Parent {
   name : string;
   address: Address;
   children: Child[] = [];

  constructor() {
      ValidationRules
            .ensure('name').required()
            .ensure('address').required().isValid()
            .ensure('children').isValid()
            .on(this)
  }
}

export class Child {
   name : string;
   address: Address;

  constructor() {
      ValidationRules
            .ensure('name').required()
            .ensure('address').required().isValid()
            .on(this)
  }
}

export class Address() {
   line1: string;
   line2: string;
   city: string;
   state: string;
   zip: string;

    constructor() {
        ValidationRules
            .ensure('line1').required()
            .ensure('city').required()
            .ensure('state').required()
            .ensure('zip').required()
            .on(this)
    }
}

What is the expected behavior?

Validation should check the sub-objects when validating the parent object if the parent object's rules include the isValid() method on the child object

What is the motivation / use case for changing the behavior?

Being able to model rich domain models with associated validations

The ValidationController is capable of multi-entity validation. Use ValidationController.addObject and ValidationController.removeObject to add and remove validation targets.
http://aurelia.io/hub.html#/doc/article/aurelia/validation/latest/validation-basics/9

That's not really the same thing. I only want to validate the child objects if the parent object is validated. If I remove the parent object from the validation controller the child objects would still be validated.
Also, I'd have to pass the validation controller to the constructor of my domain models, which means I can't have form-agnostic validations defined for my domain models that go across multiple viewmodels and forms.

Further, the isValid() would let me add contextual validations in addition to the static validations defined on the domain models.
export class myViewModel() {

private parent : Parent;

validate() {
   ValidationRules
      .ensure('parent').isValid()
      .ensure('parent.children'). maxItems(3).withMessage('In this case you can only have 3 children')
      .on(this)
}

}

Bump on this,  I'd like to also be able to have a parent run through child validation.

Another bump. This is an important feature.


NEXT-12345 - Example Pull Request

Important! Please make sure your PRs follows the following structure:
-My commit(s) look like this "next-XXXX/my-commit-massage" (next-xxxx is found in the title of the issue)
-My title looks something like this "NEXT-XXXX - Issue name" (You can use the same Title as in the issue you're dealing with)
Please make sure to fulfill our general contribution guideline (https://docs.shopware.com/en/shopware-platform-dev-en/contribution/contribution-guideline?category=shopware-platform-dev-en/contribution).
Do your changes need to be mentioned in the documentation?
Add notes on your change right now in the documentation files in /src/Docs/Resources and add them to the pull request as well.
1. What does this change do, exactly?
This is just an example. Please have a look at the commit massage as well.
This changes the color of the dashboard.
2. Describe each step to reproduce the issue or behaviour.

Open the administration
visit the dashboard
See color that I think is bad

3. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] I have written or adjusted the documentation according to my changes
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


chore: add else to avoid kotlin error exhaustive "when"

Summary
Fix the problem when try to compile kotlin show a error because the "when" clausure is exhaustive
Motivation
Fixing a bug when try to use the library
Testing

[x] I tested this manually
[ ] I added automated tests

Documentation
Select one:

[ ] I have added relevant documentation for my changes.
[x] This PR does not result in any developer-facing changes.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

addressed in https://github.com/stripe/stripe-react-native/pull/1195/files, but thankyou @harcorp !


[Bug]: Delete unique constraints, foreign key constraints and detection constraints cannot submit SQL

ODC version
odc423
OB version

What happened?

What did you expect to happen?
Generate delete statement
How can we reproduce it (as minimally and precisely as possible)?
Create a constraint table and then delete the constraint
Anything else we need to know?
No response
Cloud
No response

The same goes for deleting indexes

pass


0.9.5 JAR on CurseForge self-reports as 0.9.4

The 0.9.5 JAR that's currently up on CurseForge self-reports as 0.9.4. It contains this:
// ModTweaker2.class
@Mod(modid="modtweaker2", version="0.9.5", dependencies="required-after:MineTweaker3")

There was also a good JAR file on CurseForge for part of today and yesterday. (I know because I happened to download to my local installation yesterday and to my server today.) As a result, clients with the bad JAR cannot connect to servers with the good one.

ah Thanks for this report!
To many ocurances where i have to change Versionnumbers, i have forgotten some.

Download while it's fresh, hot and not available else http://ci.tterrag.com/job/ModTweaker2/166/


channels: use better upstream branches, and update

This updates unstable, 21.11, and 22.05 channels to their latest versions.
For the stable channels, it uses the nixos-xx.xx branches that have passed upstream CI, instead of the release-xx.xx branches that have not.
For the unstable channel, it switches to nixpkgs-unstable, which better matches the name. nixpkgs-unstable is updated more often than nixos-unstable and has less CI checks done, but those CI checks are mostly about the graphical systems and NixOS itself, so I don't think they're appropriate for our use case.
remove java-language-server, which does not build with nixpkgs-unstable and we do not use it in the java templates

We think this broke nix repls https://replit.slack.com/archives/C04EJC19BL5/p1670637649813709

swift*
maybe other languages too


Makes some of the messages plural.

Why did you close this? I wanted to help you

Sorry, my friend closed this from my account


Confusing realm_manager.datasource config.

Description:
In the migration doc [1], in Step 1.4 we request to add the following config,
[realm_manager]
data_source = "WSO2USER_DB"

How do we decide the correct value for the data_source ?
Is this mandatory or when should we add this?
The doc is not clear for above queries. As per my findings, this config is required if we have configured [database.user] datasource config only. The data_source value should be always WSO2USER_DB.
Please correct the doc.
[1] - https://apim.docs.wso2.com/en/3.0.0/install-and-setup/upgrading-wso2-api-manager/upgrading-from-260-to-300/
Suggested Labels:

Suggested Assignees:

Affected Product Version:
3.0.0, 3.1.0
OS, DB, other environment details and versions:
Steps to reproduce:
Related Issues:

@Krishanx92 , please provide input in this regard.

Fixed with https://github.com/wso2/docs-apim/commit/b3f260172c7f6f863034239499e94864f5b199a2