Make special characters in environment name work

Summary
Now any character that GitHub supports in the environment name can be used, except for slashes. Also enhanced the validation script to check for bad characters (slashes) before attempting deployment.
Didn't modify the documentation as I don't think we should necessarily promote the usage of special characters.
Checklist

[x] Tested changes end to end
[x] Requested one or more reviewers

@dremin The code changes look good. Is there any concern about OS specific differences for handling of files with special characters? Was this tested on Mac OS only, or also on Windows?

This was tested on Linux and macOS only, which only restrict the / character. Windows has a much longer list of restricted characters: " * / : < > ? \ |. Do you think that we should restrict these for everyone? Restricting them only for Windows users wouldn't really work out since CI, which performs the validation, runs in Linux.

This was tested on Linux and macOS only, which only restrict the / character. Windows has a much longer list of restricted characters: " * / : < > ? \ |. Do you think that we should restrict these for everyone? Restricting them only for Windows users wouldn't really work out since CI, which performs the validation, runs in Linux.

I'm thinking we should be OK. A developer using Windows will be restricted by the OS anyway from creating an environment file with any of these restricted characters, so our script shouldn't need to account for it. Does that sound correct to you as well?

@dremin The code changes look good. Is there any concern about OS specific differences for handling of files with special characters? Was this tested on Mac OS only, or also on Windows?

This was tested on Linux and macOS only, which only restrict the / character. Windows has a much longer list of restricted characters: " * / : < > ? \ |. Do you think that we should restrict these for everyone? Restricting them only for Windows users wouldn't really work out since CI, which performs the validation, runs in Linux.

This was tested on Linux and macOS only, which only restrict the / character. Windows has a much longer list of restricted characters: " * / : < > ? \ |. Do you think that we should restrict these for everyone? Restricting them only for Windows users wouldn't really work out since CI, which performs the validation, runs in Linux.

I'm thinking we should be OK. A developer using Windows will be restricted by the OS anyway from creating an environment file with any of these restricted characters, so our script shouldn't need to account for it. Does that sound correct to you as well?

That's correct!


Fix reading text field of TXT Record

Reading the Text field of a TXT Record did not work due to length property in the constructor of the RecordTxt.cs class always being 0. We can simply use the RecordReader.ReadString function as this takes into account the TXT Length.

The logging interface was designed to be log library independent so you could map it to Serilog or whatever your choice is. Replacing it whole hog is not recommended. Beyond that the updates to the text reading look OK.

The logging interface was designed to be log library independent so you could map it to Serilog or whatever your choice is. Replacing it whole hog is not recommended. Beyond that the updates to the text reading look OK.

Hi Dieter,
Due to the fact the log library uses a GPL3.0 license I had to remove it in my project. Is it possible to change the license of that component to Apache 2.0, so it is the same as the Ubiety.Dns.Core package?
In that case I can revert my change and re-open the PR for reading the TXT Records.

I created a new PR without the logging changes.
https://github.com/ubiety/Ubiety.Dns.Core/pull/51
Is it possible that your create a new nuget for the Ubiety.Dns.Logging and Ubiety.Dns.Core package after the PR completed? There are also some other people waiting on the fix for the TXT Records.
Thanks in advance!


Update Private Send default from 2 to 4 rounds

Rebased to develop branch. See https://github.com/dashpay/dash/pull/2065 for prior convo.

@PaulieD Thanks for this, but I'd prefer if we keep the discussion on a single PR. You can rebase and force-push as @UdjinM6 described and your changes will be added to the original PR. Pull requests are based on Github branches, so whatever your "source" branch is always the source for the PR.
Ok if we close this PR and re-open the previous one? (as that's where the discussion is)

Sure @nmarley I'm still getting used to how to use github properly. This was what I thought @UdjinM6 described

@PaulieD No worries, we're all learning something. :D Will update on your original PR.


Polling needs to be enabled explicitly

To ensure that users only enable polling, if they want to, it will not be enabled automatically on fetch anymore. To make it easy to check whether polling is enabled or not, the transport will be set to None on disable

I marked it as a breaking change because our dependants will have to enable polling explicitly now


About loading pre-trained model

Hi. First, I'm very happy for your work. Thanks for sharing a nice work.
By the way, I'm not familiar with pytorch-lighting package but there is a problem with loading your pre-trained checkpoint checkpoints/male-3-casual/last.ckpt in this line:
system = AnimNeRFSystem.load_from_checkpoint(args.ckpt_path).to(device)

The error is like this:
Error(s) in loading state_dict for AnimNeRFSystem:
	Missing key(s) in state_dict: "evaluator.lpips.scaling_layer.shift", "evaluator.lpips.scaling_layer.scale", "evaluator.lpips.net.slice1.0.weight", "evaluator.lpips.net.slice1.0.bias", "evaluator.lpips.net.slice2.3.weight", "evaluator.lpips.net.slice2.3.bias", "evaluator.lpips.net.slice3.6.weight", "evaluator.lpips.net.slice3.6.bias", "evaluator.lpips.net.slice4.8.weight", "evaluator.lpips.net.slice4.8.bias", "evaluator.lpips.net.slice5.10.weight", "evaluator.lpips.net.slice5.10.bias", "evaluator.lpips.lin0.model.1.weight", "evaluator.lpips.lin1.model.1.weight", "evaluator.lpips.lin2.model.1.weight", "evaluator.lpips.lin3.model.1.weight", "evaluator.lpips.lin4.model.1.weight", "evaluator.lpips.lins.0.model.1.weight", "evaluator.lpips.lins.1.model.1.weight", "evaluator.lpips.lins.2.model.1.weight", "evaluator.lpips.lins.3.model.1.weight", "evaluator.lpips.lins.4.model.1.weight".

I'm not sure but maybe you did intend to load only a certain part of class AnimeNeRFSystem (i.e. self.models), however the pytorch-lighting load_from_checkpoint fucntion couldn't load appropriately the weights and bias from checkpoint file.
I just changed the strict=True parameter of load_from_checkpoint function to load pre-trained model, and now the question:
Is this a right direction for executing code?
If right, could you change your source code?

Thanks for your attention!
You should set strict=False in load_from_checkpoint.
This error 'Missing key(s) in state_dict' is because the metric 'lpips' is not in the pre-trained models, which will not affect the results.

@JanaldoChen Thanks for your answer. I close this issue.


[Feature Request] Guide against single-file structure

Is your feature request related to a problem? Please describe.

Given this single-file pattern of running a Workflow inside a Worker:
https://github.com/temporalio/samples-python/blob/7b3944926c3743bc0dcb3b781d8cc64e0330bac4/hello/hello_activity.py#L47-L64
there is potential (and one past instance I know of) for people learning based off of samples to think that in order to run a Workflow, you need to run it inside an async with Worker. When they try to develop an application based on that paradigm, they run into a number of issues.
Describe the solution you'd like

Make it clear that when developing, we recommend:

running a worker separately from workflows
defaulting to a single worker for all workflows, not one worker per workflow

We could make it clear by structuring all samples that way. OTOH I like the brevity of the single file samples. Another possibility is changing the comment. The drawbacks to that are:

some people don't read comments
the comment might not be clear, unless you point to a multi-file sample, what exactly we recommend doing

Comment is currently:
# While the worker is running, use the client to run the workflow and
# print out its result. Note, in many production setups, the client
# would be in a completely separate process from the worker.

Perhaps could be:
# Use the client to run the workflow and print out its result.
# NOTE: when developing, we recommend starting out running a
# single worker that has all your workflow and activities and
# running client code in a separate process. See, for example,
# how the encryption sample has a separate files to run:
# worker.py runs the worker and starter.py uses the client.

I support any changes you suggest to this effect. We initially wanted single file examples for clarity. I support breaking them into multiple files, changing the comment, or maybe even the best option - same file but different paths based on arg.

I was thinking about suggesting a change where the first example is a single file and has a comment that says something like the above to say "Yo, this is a single file for a simple hello world. All other examples break this into multiple files, you should not build your app in the single file way".
Something extremely clear and to the point.
The other nice thing about multi-file examples, is that a README could be included to explain what is going on with that specific example and why it is included.

you should not build your app in the single file way

FWIW this is subjective based on use case. Many people may have the same app starting the workflow as running it. It's just that most people choose to start somewhere separate than they run.

The other nice thing about multi-file examples, is that a README could be included to explain what is going on with that specific example and why it is included.

This is what we do with all of our multi-file samples in this repo.  Go and TypeScript suffer from this a bit (you can't differentiate the involved samples from the simple snippets due to them all being clumped together). Having said that, if y'all want to break these out I totally support it.

We're gonna move to multi-file samples I think, ref #67


is.chrome() false positive in Opera 41.0

is.chrome() returns true in Opera 41.0 (and possibly other versions, I've only tested against 41.0.2353.46.) The reason is that navigator.vendor === "Google Inc." and chrome is in the userAgent string.

Possible solution would be to include an is.opera() check in the is.chrome() method.

Sounds good.

Sure! See PR #254

Moved to #254.


Bugs in NativeCall example

https://docs.raku.org/language/nativecall#Structs
on the bottom example of Structs, there are all kinds of syntax errors:
#!/usr/bin/env raku
use NativeCall;
class MyStruct is repr('CStruct') {
has CArray[num64] $!arr;
has Str $!str;
has Point $!point; # Point is a user-defined class
submethod TWEAK {
    my $arr := CArray[num64].new;
    $arr[0] = 0.9e0;
    $arr[1] = 0.2e0;
    $!arr := $arr;
    $!str := 'Raku is fun';
    $!point := Point.new;
}

}
$ raku -c NativeCallExampleTest.pl6
===SORRY!===
Type 'Point' is not declared
at /home/linuxutil/NativeCallExampleTest.pl6:8
------>     has Point⏏ $!point; # Point is a user-defined clas
Malformed has
at /home/linuxutil/NativeCallExampleTest.pl6:8
------>     has⏏ Point $!point; # Point is a user-define
I do believe you will find has Str $!str; is a booboo too.

It's not really intended to be used all by itself. You need to compile it in a file or in a way that makes the previous example, which declares Point, available; and it says clearly so in the comment. In general, not all example can be compiled unless they show an OUTPUT, which it does not in this case.
A clarification might be a good thing, however.

It's not really intended to be used all by itself. You need to compile it in a file or in a way that makes the previous example, which declares Point, available; and it says clearly so in the comment. In general, not all example can be compiled unless they show an OUTPUT, which it does not in this case.
A clarification might be a good thing, however.

Just extending the # Point is a user-defined class  into # Point is a user-defined class shown above is enough to clarify.

Just extending the # Point is a user-defined class  into # Point is a user-defined class shown above is enough to clarify.


Validate --github-api-url

Problem
infracost comment github --help

      --github-api-url string     GitHub API URL (default "https://api.github.com")

When implementing the GitHub comment feature, we struggled with knowing why it wasn’t working. Once we changed the comment mode from “update” to “new” it logged the actual URL it was trying to post to. We use GitHub Enterprise and provided an endpoint that included the “/api/v3/” suffix which Infracost appends on its own. The logging is inconsistent between these functions, and it should probably attempt to detect whether the suffix already exists before appending it.
Proposed solution
Since we create github API clients, should we check the --github-api-url and log a user-friendly error if the user has already added /api/v3?

Can you assign this to me?

Thanks @varshneydevansh !

Okay, so from yesterday I set up the project and learned about how it's working with Terraform. (Henceforth, I have also gained some knowledge about it.)
So, according to the above proposed solution, this is what I came up with in the internal/comment/github.go
// Check if "/api/v3/" already exists in the URL path.
if strings.Contains(u.Path, "/api/v3/") {
	return nil, nil, fmt.Errorf("The /api/v3/ suffix should not be included in the --github-api-url.")
}

But, I think if the user is already aware about the /api/v3.
Instead of giving an error, let the user keep going if they put /api/v3 in the apiURL. This would be a good experience because the user already knows about it.
Somewhat like this?
// If "/api/v3/" already exists, do not append "/api/".
if strings.Contains(u.Path, "/api/v3/") {
    apiURL = u.String()
} else {
	// Add api to path if it doesn't exist
	if !strings.HasSuffix(u.Path, "/api/") {
		u.Path += "api/"
	}
	apiURL = u.String()
}

Guide me if I am missing anything here.
For the testing, I have downloaded the required file from the https://www.infracost.io/docs/#2-get-api-key
I will do it today.

Thanks! Given that the user might add env vars for this variable in CI, it's probably best if we ensure they set the correct URL as we might use it in other places too.
I'd just update https://github.com/infracost/infracost/blob/master/internal/comment/github.go#L116 to add this check
if strings.HasSuffix(u.Path, "/api/v3/") {
  return nil, nil, errors.Wrap(err, "API URL should be the base URL without any paths, remove the /api/v3 suffix")
}

Ohh. That makes sense that it could be used in other places too. So, should I do the testing for this, or can I just create a PR?
As this could be my first code PR which will be approved, although my first code PR is still pending for approval in Phoenix Framework project.
I am getting this in my repo after committing.
Able to merge. These branches can be automatically merged.

Regards.

@RomeLeader this is now released in v0.10.25. Thanks @varshneydevansh for your contribution!


mounted does not fire on parent component

mounted does not fire on the parent component. But works on a child component. What could be the reason?

// router.js
const page = path => () => import(`~/pages/${path}`).then(m => m.default || m)
...
{ path: '/:lang/product/:product_slug', name: 'product', component: page('product-view.vue') }

I thought maybe the problem on all parent components, but no. Here is on this component mounted works.

// package.json
...
  "dependencies": {
    "@nuxtjs/router": "^1.3.2",
    "axios": "^0.19.0",
    "core-js": "^2.6.5",
    "dotenv": "^8.0.0",
    "jquery": "^3.4.1",
    "js-cookie": "^2.2.0",
    "mobile-device-detect": "^0.3.3",
    "nuxt": "^2.0.0",
    "popper.js": "^1.15.0",
    "sweetalert2": "^8.18.2",
    "v-click-outside": "^2.1.4",
    "vform": "^1.0.1",
    "vue": "^2.6.10",
    "vue-fragment": "^1.5.1",
    "vue-i18n": "^8.12.0",
    "vue-meta": "^2.3.1",
    "vue-router": "^3.1.3",
    "vue-scrollto": "^2.17.1",
    "webpack": "^4.41.1"
  },
  "devDependencies": {
    "@nuxtjs/eslint-config": "^1.1.2",
    "babel-eslint": "^10.0.3",
    "eslint": "^6.5.1",
    "eslint-loader": "^3.0.2",
    "fs-extra": "^8.1.0",
    "node-sass": "^4.12.0",
    "sass-loader": "^7.1.0"
  }
...

This question is available on Nuxt community (#c9898)

How can I view the design rules if your site is down?

I did not look carefully. Wrote all the code in data.


rename env variable

Hi!
First of all thank you for the awesome setup.
I changed the  env variable DOCKER_JUPYTER_CONTAINER  to  DOCKER_JUPYTER_IMAGE as defined in the docker-compose.yml
Cheers,
Selwyn

The docker-compose.yml says DOCKER_JUPYTER_CONTAINER I think?
https://github.com/defeo/jupyterhub-docker/blob/d2e20a3fa1a899b9f9cd8e8de17597d679a0786e/docker-compose.yml#L12
DOCKER_JUPYTER_IMAGE is a better name though.

Thanks for the suggestion. Indeed this change must be reflected in docker-compose.yml for things to keep working.

I did not notice that DOCKER_JUPYTER_CONTAINER is set in docker-compose.yml. I followed your tutorial https://opendreamkit.org/2018/10/17/jupyterhub-docker/ where the variable is named DOCKER_JUPYTER_IMAGE and got things mixed up.


New command: Install Teams app into a chat

Usage
m365 teams chat app add
Description
Install an app in the specified chat
Options

Option
Description

--id <id>
The ID of the chat conversation.

--appId [appId]
The ID of the app to install. Specify either appId or appName but not both.

--appName [appName]
The name of the app to install. Specify either appId or appName but not both.

Examples
Install an app to a chat using its name.
m365 teams chat app install --id<EMAIL_ADDRESS>--appName HelloWorld

Install an app to a chat using its id.
m365 teams chat app install --id<EMAIL_ADDRESS>--appId "4440558e-8c73-4597-abc7-3644a64c4bce"

Default properties
No response
Additional Info
Add app to chat
Remarks
If the chat is associated with a meeting, the app will be installed into the meeting.
The appId has to be the ID of the app from the Microsoft Teams App Catalog. Do not use the ID from the manifest of the zip app package. Use the teams app list command to get this ID.

I would like to work on this one. Can you assign me?

@Rachit1313 are you still working on this?

Resetting due to lack of response


add substring matching to "swarm service create" constraints

Currently, passing constraints to a swarm service only allows full string matching.  It would be a nice feature to have the ability to match on substrings (either globbing or regex) so that more complex labels (e.g., comma separated values) can be applied to hosts.
Example:
[root@dkh01 ~]# docker node inspect dkh01.example.com | grep -C2 processor_flags
                "EngineVersion": "1.12.3",
                "Labels": {
                    "processor_flags": "aes,apic,avx,clflush,cmov,constant_tsc,cx16,cx8,de,eagerfpu,fpu,fxsr,hypervisor,lahf_lm,lm,mca,mce,mmx,msr,mtrr,nopl,nx,pae,pat,pclmulqdq,pge,pni,popcnt,pse,pse36,rdtscp,rep_good,sep,sse,sse2,sse4_1,sse4_2,ssse3,syscall,tsc,tsc_deadline_timer,vme,x2apic,xsave,xsaveopt"
                },
                "Plugins": [

[root@dkh01 ~]# docker service create --network root_net1 --replicas 3 --name cputest --constraint 'engine.labels.processor_flags =~ avx2' cputest
Error response from daemon: rpc error: code = 2 desc = constraint expected one operator from ==, !=

Currently targeting nodes is more complicated than it could be. I'd say that regex matching / globbing is essential. Of course one could use engine or node labels for this purpose, but this involves another unnecessary step.
In our organization we created a naming scheme to describe the function / placement of our hosts. I think this is quite common, because most tools offer regex matching.
According to this scheme our configuration management and monitoring systems automatically install and configure software, deploy tools / health checks and so on. Labels are a nice addition in certain cases, but regex matching is far superior.

ping @docker/core-swarmkit-maintainers

/cc @dongluochen

It's in our plan to support more flexible constraints. Meanwhile contribution is always welcome.

Do you guys have any plan to do this? It seems this feature is crucial for deploying services in live service.

+1 for this feature to be included

I don't think someone is working on it currently; as mentioned above, contributions are welcome, so if someone wants to write a more complete proposal / design that describes a syntax and behaviour, that could be a start.

Separate from the issue of adding more flexible constraint functions, I think the use case from the original comment could be done by changing the way you use labels. In this case, rather than having one label, processor_flags, whose value is comma-separated strings, expand it into having multiple labels, one for each processor flag:
...
"Labels": {
    "processor_flags.aes": true,
    "processor_flags.apic": true,
    "processor_flags.avx": true,
    ...
},
...

Then your placement constraint flag could be --constraint 'node.labels.processor_flags.avx2 == true'.
We should also probably have a guideline that you should not have structured data in your label values, especially if you plan on using those labels for constraints.


archibot can't get API

Hey
archibot always send a massage that it can't get api for some bots
and today all bots stopped to redeem any keys with only entering the key without using !redeem command  just today but all other commands works what should it do

Please review the guidelines for contributing to this repository.

https://github.com/JustArchi/ArchiSteamFarm/blob/master/CONTRIBUTING.md

If my issue is not meeting contributing guidelines specified above, especially if it's a question or technical issue, please close my issue immediately - I won't complain.

Reason for closing: technical issue is not ASF bug.


Monaco Preview handler hangs/crashes

Microsoft PowerToys version
0.76.1
Installation method
PowerToys auto-update
Running as admin
None
Area(s) with issue?
File Explorer: Preview Pane
Steps to reproduce
Any source code preview failes
✔ Expected Behavior
Preview should show json source code

❌ Actual Behavior
hangs
Other Software
No response

I think I have a related or the same issue: Wanted to preview a Python file and it ends in following empty preview panel:
<img width="321" alt="image" src="https://github.com/microsoft/PowerToys/assets/86119630/ddbdfe47-7512-4084-8d2e-d7ac6fa52c4
Logs:
PowerToysReport_2023-12-12-22-10-21.zip
1">
Logs:

/dup #30370

This was hotfixed with 0.76.2. Please update PowerToys.


WIP: CI

See commit msgs.
ci-e2e with the advanced test case (to be upstreamed) has passed - https://github.com/cilium/cilium/actions/runs/8246356069.

/test

/test

/test

/test

/ci-e2e

/test

/test

/test

/test

/test

Since #31267 and #31266 have merged, will label the backports done here.


add URL to each package source

add URL to each package source
for quick inspecting of the repo.
some kind of docs / README preview would be great too

we now have right click, repo URL


chore: bump rector from 0.18.5 to 0.18.6

resolve #110

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
We've detected an issue with your CI configuration that might affect the accuracy of this pull request's coverage report.
To ensure accuracy in future PRs, please see these guidelines.
A quick fix for this PR: rebase it; your next report should be accurate.

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall first build on fix-rector-error at 79.465%

Totals

Change from base Build<PHONE_NUMBER>:
79.5%

Covered Lines:
1544

Relevant Lines:
1943

💛  - Coveralls


Draft implementation of point estimation

This (draft) pull request is meant to hold discussion and development of point estimation within BayesFlow.
The functionality per se was also discussed in the issue https://github.com/bayesflow-org/bayesflow/issues/121.
The implementation should make it easy to

use standard point estimators,
extend an existing collection with more complex point estimation,
and use custom research estimators.

Commit 093785d9f80fde678f9b491bb3a95323166325c3 contains a first example including ONLY quantile estimation.
Writing down draft specifications and guiding thoughts
Names for everything
What is "inference", does it include point estimation? Are we calling networks discussed below PointInferenceNetworks, PointRegressors, or something else?
For now I stick with ContinuousPointApproximator and PointInferenceNetwork to make their roles in relation to the existing codebase obvious.
Components
A ContinuousPointApproximator parallels the ContinuousApproximator and bundles some feed-forward architecture with an optional summary network suitable for learning point estimates optimized to minimize some Bayes risk.
Thus it serves the same roles (including Adapter calls, summary network, etc), but instead of a sample method it provides an estimate method.
PointInferenceNetwork parallels the InferenceNetwork by providing a base class to inherit from for generative model classes suiteable for the role of approximating a conditional distribution feed-forward model classes suitable for point estimation.
Convenient default estimator
The API for functionality that covers the need of most users could be something like
point_inference_net = NameForStandardCompositePointInferenceNetwork()
point_approximator = ContinuousPointApproximator(
	summary_network = ...,
	inference_network = point_inference_net,
)
# define optimizer, compile(), fit() as usual

, with optional constructor arguments to tweak it a bit:
NameForStandardCompositePointInferenceNetwork.__init__(
	self,
	mean: bool = True,
	std: bool = True,
	quantile_levels: Sequence[float] = [0.1, 0.5, 0.9]
	subnet: str | type = "mlp",
	**kwargs,  # e.g. subnet_kwargs = dict(widths=[64, 32], dropout=0.1)
)

choices in output of estimate
For inference the method estimate(data_dict)) produces the point estimates for a given input/condition/observation.
The default PointInferenceNetwork would produce 5 point estimates (mean, std and three quantile levels) of the marginal distribution for each inference variable.
These estimates need more explanation than samples provided by generative networks typically need. We need to communicate to user, diagnostics code or other downstream tasks which estimate lands where. It seems to me that it would be helpful if such estimate output is structured as a dictionary with the point estimates names as keys, like
dict(mean: tensor, std: tensor, ...)
rather than a tensor from concatenating all individual estimates.
Architecture
The architecture has one shared "body" network as well as separate "head" networks for each scoring rule.
The subnet keyword argument has a default of "mlp", in general the argument is resolved by find_network from the bayesflow.utils which can take a string for predefined networks or a user defined custom class.

future extension direction: I made some pleasant experiences with using regression forests and boosted regression trees as point estimation tech for when a learned summary network is unnecessary. They are attractive for their robust performance and near instant fitting speed if applicable. sklearn and xgboost have mature implementations that are naturally not in pure keras3. Can we still somehow make it possible to use a preexisting random forest /tree boosting implementation?
Currently the non-shared networks are just linear layers.
Instead we could relax this and provide optional subnet_heads that can replace default linear heads. Since I can't currently see anyone having a preference against weight sharing I am avoiding the complexity for now.
For some point estimates (scoring rules) it might be beneficial to specify a specialized activation function. For example exploiting that quantiles ordered by quantile level are always sorted since the CDF monotonously increases.

Extendable design
The first draft only includes a PointInferenceNetwork subclass for quantile estimation, currently called called QuantileRegressor and found in bayesflow/networks/regressors/quantile_regressor.py.
This is just the first step, and we want to support different loss functions (which are typically called scoring rules in this context) that result in other point estimates.
A more flexible API including custom scoring rules /losses could use a PointInferenceNetwork that accepts a single or a sequence of ScoringRules.
This can generate the appropriate number of heads in the build()method.
It also can pass the respective outputs to the corresponding scoring rules that compute their actual loss contributions and sum them up.
PointInferenceNetwork.__init__(
	self,
	loss_func: ScoringRule = None,
	loss_funcs: Sequence[ScoringRule] = None,
	subnet: str | type = "mlp",
	**kwargs,  # e.g. subnet_kwargs = dict(widths=[64, 32], dropout=0.1)
)

A ScoringRule / ScoringLoss has a name (we want to distinguish multiple of them later) and a score / compute method.

in the method score is meant as a verb
it seems the literature has not converged on whether a score (noun) is always maximized (like the opposite of loss) or can be both -> terminology question

A ScoringRule could also compute a prediction_shape in the constructor to be accessed by generic code that generates a corresponding head for the scoring rule.
choice we have here

prediction_shape could also be a prediction_size, an int rather than a tuple
it is possible to score for example a whole covariance matrix or other multi-dimensional predictions, so allowing an arbitrary shape might be a good idea.

The head would have output_shape=(*batch_shape, *prediction_shape, num_variables)

e.g.:

a batch_size of 32 -> batch_shape of (32,) and
a one dimensional point estimator -> (1,)
and 4 inference variables
-> (32, 1, 4) shall be head output_shape
build() creates a Dense layer with 32*1*4 units and reshape operation which together form a head

interaction with choice of output of estimate method: If we choose to allow multidimensional prediction_shapes rather than only prediction_sizes, we can not concatenate output of different heads since each can have an individual prediction_shape.
Thus the decision interacts with whether the predict method should return tensors or a dict of tensors (see above).
Below are some notes how ScoringRule definitions could look like.
class ScoringRule()
	def __init__(
		self,
		name: str = None,
		**kwargs,
	):
		...
	def score(self, prediction, realized_value):
		raise NotImplementedError

class NormedDifferenceLoss(ScoringRule)
	def __init__(
		self,
		name: str = "normed_difference",
		k: int = 2,  # results in an estimator for the mean
		**kwargs,
	):
		super().__init__(**kwargs)

		self.name = name
		self.k = k
		self.prediction_shape = (1,)

	def score(self, prediction, realized_value):
		pointwise_differance = prediction - realized_value[:,None,:]
		score = keras.ops.absolute(pointwise_differance) ** self.k
        score = keras.ops.mean(score)
		return score

class QuantileLoss(ScoringRule)
	def __init__(
		self,
		name: str = "quantile",
		quantile_levels: Sequence[float] = [0.1, 0.5, 0.9],
		**kwargs,
	):
		self.name = name
		self.quantile_levels = quantile_levels
		self.prediction_shape = (len(self.quantile_levels),)

	def score(self, prediction, realized_value):
        pointwise_differance = prediction - realized_value[:,None,:]

		score = pointwise_differance * (
	            keras.ops.cast(pointwise_differance > 0, float)  - self.quantile_levels[None, :, None]
        )
        score = keras.ops.mean(score)
		return score

If we want to support specific activation functions for different scoring rules, we might add a non-parametric activation function to the ScoringRule's definition.
We could also go all the way and have the ScoringRule also contain the head itself, taking the last joint embedding and mapping it to estimates. This then would naturally include an optional nonlinearity in the end and simultaneously give users the option to tweak the architecture of the non-shared weights.
Other notes:

For a PointInferenceNetwork that returns mean and std we could provide sample() and log_prob() under a Gaussian assumption. Maybe someone is interested in implementing even things like a LaplaceApproximator.
later: is there anything to consider for point estimation to fit neatly with the bf.Workflow?

Hans, thanks for the great ideas and the very mature first draft! Here are some initial thoughts from my side. More to come later:

What do you think about the possibility to inherit from ContinuousApproximator instead of Approximator? As far as I can think, the only conceptual differences are in compute_metrics and estimate vs sample.
I wouldn't go for sample methods on the point estimators in order to keep their interface consistent. Even though it may make sense for certain kinds of parametric point estimators (e.g., heteroskedastic regression), one rarely needs anything beyond the distribution parameters in these cases.
I would definitely go for named entities in the output of estimate. Perhaps its time to start thinking in terms of "data classes".
I like the idea of an abstract ScoringRule class. I would call the arguments targets and references in keeping with the rest of the lib (e.g., diagnostics).
The WorkFlow object would need to know whether it's dealing with a point estimator or a fully Baysesian approximator. It can check whether an estimate or a sample method is present, or check for a type (the latter may invalidate my point about inheriting from ContinuousApproximator.
The "non-parametric activation function" for scoring rules is a good idea, because it lets users specify heads with linear output layers (@paul-buerkner - we may call these "link functions"?).
I would go for a single argument in the PointInferenceNetwork that can be either a single scoring rule or a sequence thereof.

This looks really cool already! Thank you for this PR!
There is a lot of content here in this thread already and I may benefit from a call where you show me the current state. This would help me give reasonable feedback. I will contact you offline about it.

Ok cool, Paul!
Stefan, thanks for your takes already! Some notes to some of them:

What do you think about the possibility to inherit from ContinuousApproximator instead of Approximator? As far as I can think, the only conceptual differences are in compute_metrics and estimate vs sample.

I am not sure about this. Tagging @LarsKue for this question, I think you mentioned a preference of parallel implementation rather than inheritance?

I would definitely go for named entities in the output of estimate. Perhaps its time to start thinking in terms of "data classes".

Agreed, that some form of naming is necessary. How do the "data classes" you imagine differ from dictionaries of the type:
# assuming a batch_size of 2 and 3 inference variables:
dict(
    mean=[[ 1, 2, 3], [2, 1, 3]],
    quantile_0.1=[[ -1, 0, 1], [1, -1, -2]],
    quantile_0.9=[[ 3, 4, 5], [3, 2, 5]],
    ...
)

For one thing, carrying the numeric value of the quantile level in the dict key is a bit awkward, but could be acceptable.

I like the idea of an abstract ScoringRule class. I would call the arguments targets and references in keeping with the rest of the lib (e.g., diagnostics).

:+1:
We need to decide on which class holds the heads' neural networks. It seems reasonable to bundle them with the ScoringRule directly, because there is a one-to-one relationship between head and ScoringRule.
If you prefer to keep the head out of an abstract ScoringRule, I would propose to have a Head object which owns both an abstract ScoringRule and a keras.Layer.

The WorkFlow object would need to know whether it's dealing with a point estimator or a fully Baysesian approximator. It can check whether an estimate or a sample method is present, or check for a type (the latter may invalidate my point about inheriting from ContinuousApproximator.

Ok! Just in their defence, I'd say point estimators are also fully Bayesian ;) Functionals of the proper Bayesian posterior distribution.

I would go for a single argument in the PointInferenceNetwork that can be either a single scoring rule or a sequence thereof.

Good point! Those loss_func and loss_funcs is a bit convoluted for no good reason.

Regarding the output, I think we can go with dictionaries for now. I believe some custom data classes will come in handy rather soon.
Just a thought: Can the heads simply be determined automatically assuming the scoring rules know their dims?

Yes, they can mostly be inferred, and I'd suggest linear layers followed by a reshape as an overwritable default.
However, some scoring rules benefit from (e.g. quantiles, monotonously increasing) or need (e.g. covariance matrix, positive definite) a specific architecture.


Update jquery.highchartTable.js

Adding variable to allow for flexibility in the graph axis (th's)

@ptasker there are many changes in this PR. could you make one PR per feature ?


Doesn't create a PDF

Perhaps a dumb question, but I installed the VSCode extension (on Windows 10), created a .typ file, entered some random text, saved it. Nothing happens. No pdf is created, nothing in Output window. VSCode is showing "Typst" for document and extension settings for PDF creation are set "onSave".
Am I missing something obvious? Also, perhaps add a paragraph to readme on what to expect (i.e. if configured properly, a NAME.pdf should appear alongside original text).

There is an error if you only open a file (not a folder). If you look at the "output" tab, select Typst Langage server in the dropdown and you may see this error
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', src/main.rs:26:29

I made a PR to fix this error but github don't want me to create PR (possible outage according to the github status)

Duplicate of https://github.com/nvarner/typst-lsp/issues/36


Allowing fetchy to be trigger by a repo dispatch event

Adding in this new event for when we want to create an endpoint in netlify to trigger this workflow

Also removed the push event since we don't really need it to run once its been merged into the main branch. It would have gone through a PR already. (also when I use the github API to check when the last run was, I don't want the push events included so this would remove them)
P.S. Promise this is the last rename of the fetchy workflow

Question: why do we need a repository dispatch? Can't the api endpoint call the function directly?


Badge Documentation

August 21 - docs in progress - dev: branch already open so link to the issues if there is an active branch so there isnt any double work. Recommend to start in word.

@el-dav @yunjungyeh hi both, what are updates for this docs - were you two able to collaborate and get things moving? Thanks!

@jpmorganchase/salt-content @pseys @bhoppers2008 Badge doc is ready for peer review

August 25 - couple of comments to resolve on this - nav to take a look if time.

Aug 31 - badge doc peer review complete, ready for official content review @jpmorganchase/salt-content

Content review done.

Ready to merge once checks are complete


fix: remove webtransport from default transports

Description
WebTransport is still not working reliably across different browsers. Moreover, the go-libp2p implementation needs to be updated to meet newer revisions of the spec.
As we discussed during Helia WG, the most sensible thing for now is to remove WebTransport from the default transports.
Related to https://github.com/libp2p/js-libp2p/issues/2572
Change checklist

[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation if necessary (this includes comments as well)
[ ] I have added tests that prove my fix is effective or that my feature works

@achingbrain Any thoughts on this?

This makes me a bit 😭 but I don't how else we can give users a good experience otherwise right now.


Button is out of position

The issue appears to occur if you have the '.rgh-clean-dashboard.js-news-feed-event-group' css property on the main page of github.

The !important will be added to the padding-right of the '.rgh-clean-dashboard .dashboard .body > .border-bottom' css property.
Or
delete !important from .rgh-clean-dashboard.js-news-feed-event-group.

sorry.. I mistook Repo.


bump version for development

@jameslamb the version number in R is not updated yet, you can change it together with the new solution of R's versioning.

@jameslamb the version number in R is not updated yet, you can change it together with the new solution of R's versioning.

ok sounds good. Added #3283 to track the work


Document FORCE_COLOR=1 in kapp --help

Describe the problem/challenge you have
In order to include a shortcut for kapp in k9s (see https://github.com/derailed/k9s/pull/1830), I need to pipe kapp output to the less command.
Unless the export FORCE_COLOR=1 prereq, the kapp inspect | less -R fails to display colors. Same with --color or --tty flags
After searching a while, finally found the flag in https://kubernetes.slack.com/archives/CH8KCCKA5/p1600180101408100?thread_ts=1600180052.407500&cid=CH8KCCKA5
Describe the solution you'd like
kapp --help displays :
Environment Variables:
 - FORCE_COLOR: set to 1 to force colors to the printed. Useful in 'kapp ..| less -R'

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

related partial work: https://github.com/vmware-tanzu/carvel/pull/581

Hey @gberche-orange! Thank you for creating this issue. The environment variable addition to kapp help section sounds good to me. Would you like to work on a PR for this?


feat: Infer version from Git

Use nebula-release-plugin to infer the version from Git similar to git describe.
The versioning follows Semver by default, local dev-builds will have a version string similar to this:
<major>.<minor>.<patch>-dev.#+<branchname>.<hash>

nebula-release-plugin is Netflix' fork of the gradle-git release plugin.
Resolves #289
Contains some changes from #295
Signed-off-by: Tobias Nett<EMAIL_ADDRESS>

What would the normal action be that triggers a release?

Still need to document that part... The idea with the nebula plugin is that the commit to release (on master) is tagged using the plugin's task, and then a Github Release is manually triggered by publishing the draft release (automatically preprared by another action).
Publishing a release will lead to an action building that exact commit and uploading the build assets.


Head coverage is not compared to the base coverage when skip-step set to all

Discussed in https://github.com/ArtiomTr/jest-coverage-report-action/discussions/108

Originally posted by adesurirey July  5, 2021

Comparing coverage with base branch.

Looks great, how do I activate this?
I'm currently using v2.0-rc.2 which works great but I do not have this kind of reports on my PR as on the README screenshot.

@ArtiomTr may I help on this one?

@adesurirey, thanks for the suggestion, but unfortunately I have already started working on this. To fix this issue, I need to complete a lot of smaller tasks. In order for you to be able to follow the progress of the work, I created a draft PR (#118). The latest information on the progress of work will appear there.


Bluetooth doesn't work on X250

Enabling Bluetooth doesn't work (nothing happens upon clicking the "turn on" button). Hackintool doesn't show any Bluetooth devices either.
I'm on a ThinkPad x250 running macOS Monterey with Intel Bluetooth.

Try entre to Windows system and check the Bluetooth, then back to MacOS. Because I had the same problem before.

Enabling Bluetooth doesn't work (nothing happens upon clicking the "turn on" button). Hackintool doesn't show any Bluetooth devices either.
I'm on a ThinkPad x250 running macOS Monterey with Intel Bluetooth.

Try entre to Windows system and check the Bluetooth, then back to MacOS. Because I had the same problem before.

Enabling Bluetooth doesn't work (nothing happens upon clicking the "turn on" button). Hackintool doesn't show any Bluetooth devices either.
I'm on a ThinkPad x250 running macOS Monterey with Intel Bluetooth.

Confirm that Bluetooth is not disabled in BIOS.
Check whether Bluetooth can be used in windows.

It's not disabled
It works just fine on Windows.

I've found that Bluetooth works fine on macOS Big Sur, but not on Monterey.
Related issues:
https://github.com/acidanthera/bugtracker/issues/1821
https://github.com/acidanthera/bugtracker/issues/1669

I replaced AirportItlwm.kext with Itlwm.kext and everything's working fine now.


Very misleading error message when you drastically change the starter project and then hot reload

Try this:

create a new app
start an emulator
flutter run your new app
yay, it works!
then, replace your lib/main.dart with the following contents:

import 'package:flutter/material.dart';

void main() {
  runApp(new MyWidget());
}

class MyWidget extends StatelessWidget {

  @override
  Widget build(BuildContext context) {
    return new GestureDetector(
      onTap: () => print('tapped!')

I/flutter ( 3394): ══╡ EXCEPTION CAUGHT BY WIDGETS LIBRARY ╞═══════════════════════════════════════════════════════════
I/flutter ( 3394): The following _CompileTimeError was thrown building MyApp(dirty):
I/flutter ( 3394): 'file:///C:/Users/sethladd/Documents/Code/circles/lib/main.dart': malformed type: line 25: cannot
I/flutter ( 3394): resolve class 'MyHomePage' from 'MyApp'
I/flutter ( 3394):         home : new MyHomePage(title : "Flutter Demo Home Page"),
I/flutter ( 3394):                    ^
I/flutter ( 3394):

This is a pretty poor user experience:

There is no more MyHomePage class in my source code, why is Flutter telling me there's an error here?
There is no suggestion or hint that I need to Hot Restart

Luckily, I then remembered that:

I can Hot Restart
There is some issue about changing types of widgets and not working well with Hot Reload

(Neither of which a new user would understand :/)
Suggestions:

Tolerate changing widget types (from stateless to stateful) during Hot Reloads
Detect when a Hot Reload isn't possible, error out earlier than showing me code that no longer exists
Suggest to the user something like "Bummer, that didn't seem to work. Please try Hot Restart with capital R."

Thanks!

What is happening is this:

We don't rerun the void main() block. That's basically what it means to do a hot reload: we don't rerun the app from the start, we just update the code in place and keep going. Your app has already run its void main, so it won't rerun.

We then mark every object in the system as needing to be rebuilt. In your app, you had a MyApp widget, so we rebuild it. Its build function used to try to instantiate a MyHomePage class. But that class doesn't exist anymore, so when we try to do that we fail.

No widgets are changing types.
The hot reload is possible, and worked fine. It's actually the rebuild that failed. You would get the same failure if you started your app with a MyApp class that tried to build a non-existent MyHomePage class.
We could detect that an error occurred during the hot reload's reassemble step, though, and tell the tool that things went poorly... How could we distinguish that from a typo in your code, though? Like, if all you had done was edit the MyApp builder to build a MyHomeBook instead of a MyHomePage, you'd get the exact same error, and we'd have no way to distinguish that error from the error you got here.
If the VM could report to us the list of classes that changed, and whether they were removed or had their class hierarchies changed, we could specifically rebuild just the widgets that changed, and we could complain if a class that previously was in the tree no longer existed.

Thanks for the analysis!

The hot reload is possible, and worked fine

From the user's perspective, it didn't work fine. I pressed 'r' and I didn't see my change. I got an error about code that no longer existed :(

We could detect that an error occurred during the hot reload's reassemble step, though, and tell the tool that things went poorly

Yes, please! That should cover a variety of cases, and we'll make it super clear: the action that the user requested did not complete, don't worry, just hit big R.
An overall point here is: it's not clear why hot reload failed, and it wasn't clear what to do next. That's really the bug.
As a user, I'm fine hitting big R as my escape hatch. Just tell me to do that in the error message. :)
cc @mit-mit

Yes, please!

You missed the next two sentences which explain why that's not actually possible. :-) If we said "use R" anytime there was any error in hot reload, we'd be telling you to use "R" all the time even though most of the time using "R" will just give you the same error.

Sorry, I did miss it. However, I'm still not satisfied with this user experience :/
Remember, I hit little r a few times and kept getting the same error. I was out of ideas. I was about to just quit the flutter run session (Control-C) and relaunch. That's a valid workaround, but I think we can do better.
I solved this because I a priori knew about Big R. I'm wondering what we can do to make it so that you don't need a priori knowledge ?

The flutter tool announces it in the same sentence as hot reload:
🔥  To hot reload your app on the fly, press "r". To restart the app entirely, press "R".

The ideal solution here is getting the VM to report the information as described above.

cc @a-siva @mit-mit
@Hixie is referring to this text:
"If the VM could report to us the list of classes that changed, and whether they were removed or had their class hierarchies changed, we could specifically rebuild just the widgets that changed, and we could complain if a class that previously was in the tree no longer existed."

cc @lukechurch

@rmacnak-google

Removing a (non-root) widget class and all its uses in build methods would be a valid change. Hot reload should not complain here just because the old tree has a deleted class.
The VM knows that this compilation error happened in stale code (the deleted MyApp class), which is probably a good signal that restart may help. The typo scenario would usually cause an error in the current version of some code.
This change included main, which will not be run again. This special case probably deserves a warning of some kind, but we can't in general know if a change requires a restart to have an effect.

The VM knows that this compilation error happened in stale code (the deleted MyApp class), which is probably a good signal that restart may help

Yes, if we could know when to restart even if reload was requested that would be great. And if not, if we could at least know that something is going to fail and throw an exception, can we change the error message to say something that a little more explicitly?

The VM knows that this compilation error happened in stale code (the deleted MyApp class), which is probably a good signal that restart may help.

Great!

Marking as a duplicate of #12300


(TEPHRA-226) Use older API to run as login user

JIRA : https://issues.apache.org/jira/browse/TEPHRA-226

LGTM


Packager dumps a huge error after installing

After installing and re-running my app the packager dumps a big error that starts (too big to post):
Flow failed to provide parseable output:

`{"passed":false,"errors":[{"message":[{"descr":"ActionSheetIOS\nDuplicate module provider","code":0,"path":"/Users/Daniel/Do...

I'm not sure this is related to the react-native-facebook-login component. Try removing references to it and see if it still fails in this same way. Another thing to try would be to open the example project located with the module, in your node_modules folder, under the react-native-facebook-login folder you should find an example directory with an example project which should build and run without issue.

Hmm.  Maybe theres an issue with my react install.. but I just created a new raw project:
react-native init AwesomeProject
Run that and it works. Then cd into AwesomeProject and run:
npm install --save react-native-facebook-login
Which appears to work.. then I re-run the AwesomeProject (without actually attempting to use the Facebook login) and I see the same packager error.   I was able to get it working without an issue about a week ago or so when I first tried it in a test project.  Not sure what's changed.

After installing flow I've reproduced your error, it seems Flow is identifying two versions of the react-native libraries since it exists in both your node_modules and the node_modules of my component. The easiest solution for you is to ensure your .flowconfig file has the following.
[ignore]
.*/node_modules

This will resolve the packager issue you're seeing. It seems other libraries include a similar pattern, ignoring the node_modules directory. I'm not sure why this isn't a default for flow.

Thanks Magus, I'll give it a try tonight.  And thanks for the project!


Closes #39: CoEQ test data

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral family codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the main branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md under the header # admiral<ext> (development version) if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the Reference page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

Hi @pharmaverse/admiralmetabolic - this is a PR to add a very simple CoEQ test dataset. I have added a couple of reviewers, but could anyone with capacity please take a look and see if the SDTM structure makes sense to you? I have not worked myself with the data and the only thing I had access to was some raw, unmapped data from the Roche side, so I had to "guess" the SDTM mapping! In particular, I also guessed the QSCAT/QSSCAT/QSTEST assignments, but of course we can modify them if needed.
@kathrinflunkert note that I have added the licensing disclaimer as well, which we'll need to send to UoLeeds before we merge in.

Thanks @kathrinflunkert @yurovska for your reviews. I removed QSSCAT, ensured the answer to question 20 is categorical, and made the other suggested updates. Please review again - looking to merge by EoB Wed this week. Thanks!


Add EmacsBehavior to CodeInput and add example

Have CodeInput inherit EmacsBehavior and add "Key bindings" option to CodeInputTest so that users can try out the bindings.

@el-ethan I think the vim side if this debate is absent... :)
Which behavior to have by default for code input... I feel this would be better served as a garden widget, where we can have EmacsCodeInput VIMCodeinput... instead of limiting to one type of behavior let's keep the core widget open for re-usability.

Oh, btw nice job!

This repo is a great place for the behavior itself, but i agree with @akshayaurora that we should not enable it for codeinbut by default. Documenting the usage in the behavior docstring is enough.

@akshayaurora, do you think the vim community would mind if VIMBehavior inherited from EmacsBehavior? Seriously though, I think it would be great if there was a VIMBehavior mixin as well - but better that it be written by a vim user :)
Also, even though CodeInput inherits from EmacsBehavior in this branch, by default the behavior doesn't change from that of kivy master. It will only change if you pass a different value for active_key_bindings.
The reason why I initially added it to the CodeInput is that I was asked to add an example of EmacsBehavior to examples/widgets/codeinput, and this was what I came up with at the time. The active_key_bindings property allows the behavior of the CodeInput to be changed programmatically so that you don't have to decide what kind of behavior you want to use ahead of time. VIMBehavior could be added to CodeInput later, and used the same way.
However, I am not so attached to this example, so if you want me to make some changes, or simply close this pull request, it is fine with me. Probably an example is not necessary anyway, since anyone who will use EmacsBehavior is likely already familiar with Emacs.

I removed EmacsBehavior from CodeInput but I added made a few minor changes so that the example in examples/widgets/codeinput still works and can be further extended in the future with VIMBehavior, PicoBehavior ;),  etc. I can still remove the example altogether, if necessary.

@el-ethan, thanks a lot! :+1:

I've cleaned up a bit in https://github.com/kivy/kivy/pull/3894.
The pr limits EmacsBehavior (feature released in 1.9.1) usage to CodeInput only, before it could also be used with TextInput.
@team, should we move CodeInput.key_bindings to TextInput and preserve the original behavior?

@tito, it was removed.

ref https://github.com/kivy/kivy/pull/3898


Native ARIA Roles: Remove JS Shim

Summary:
Stack
ARIA roles in React Native are implemented on top of accessibilityRole. This is lossy because there are many more ARIA roles than accessibilityRole. This is especially true for RN on desktop where accessibilityRole was designed around accessibility APIs only available on mobile.
This series of changes aims to change this implementation to instead pass the ARIA role to native, alongside any existing accessibilityRole. This gives the platform more control in exactly how to map an ARIA role to native behavior.
As an example, this would allow mapping any ARIA role to AutomationControlType on Windows without needing to fork to add new options to accessibilityRole.
It also allows greater implementation flexibility for other platforms down the line, but for now, iOS and Android behave the same as before (though with their implementation living in native).
Diff
This removes the JS shimming of role to accessibilityRole. It can be landed when the native role implementation for both iOS and Android are live for versions we service OTA.
This will require any out of tree platforms to add their own native implementation for role to continue to work.
Changelog: [Internal]
Differential Revision: D45432518

FYI @acoates-ms @Saadnajmi
To keep role working, and to map it to map the various ARIA roles, you will want to add a native implementation in desktop once this diff (represented as the last commit in this PR) lands.

FYI @acoates-ms @Saadnajmi
To keep role working, and to map it to map the various ARIA roles, you will want to add a native implementation in desktop once this diff (represented as the last commit in this PR) lands.

Is the plan to land this with 0.72 or 0.73? If so, then we can pre-emptively plan for it. I'm pretty sure on macOS already have a native implementation for 'role' because we had to..
https://github.com/microsoft/react-native-macos/blob/main/React/Base/RCTConvert.m#L1437-L1503

FYI @acoates-ms @Saadnajmi
To keep role working, and to map it to map the various ARIA roles, you will want to add a native implementation in desktop once this diff (represented as the last commit in this PR) lands.

Is the plan to land this with 0.72 or 0.73? If so, then we can pre-emptively plan for it. I'm pretty sure on macOS, we already have a native implementation for 'role' because we had to.. https://github.com/microsoft/react-native-macos/blob/main/React/Base/RCTConvert.m#L1437-L1503

It will land in 0.73. The existing implementation there maps AccessibilityRole values, but not ARIA role values. You can take a look at the iOS change here to see what roughly changes.

FYI @acoates-ms @Saadnajmi
To keep role working, and to map it to map the various ARIA roles, you will want to add a native implementation in desktop once this diff (represented as the last commit in this PR) lands.

Is the plan to land this with 0.72 or 0.73? If so, then we can pre-emptively plan for it. I'm pretty sure on macOS, we already have a native implementation for 'role' because we had to.. https://github.com/microsoft/react-native-macos/blob/main/React/Base/RCTConvert.m#L1437-L1503

It will land in 0.73. The existing implementation there maps AccessibilityRole values, but not ARIA role values. You can take a look at the iOS commit here to see what roughly changes. (4bfd06d at time of writing)

@mischreiber @harrieshin @chiuam FYI. I added stuff to our backlog for 0.73, but looks like we'll need to revisit accessibility in a future merge.

Is this Fabric-only or will this affect Paper? The decision/assertion made by the RN release crew was that all new APIs/props (esp. for web / xplat) would be explicitly treated as experimental and Fabric-only, so as not to block releases waiting on Paper implementations. This has trickled down to customers, aka RNW took this to not worry about having to update Paper and instead focus on the Fabric implementation.
RNW's tracking of web props/aria for Fabric:

https://github.com/microsoft/react-native-windows/issues/11185
https://github.com/microsoft/react-native-windows/issues/11432

This affects Paper as well. Most of the existing web props like ARIA role do work on paper in 0.71, with the exception of a couple layout ones which were implemented in native first instead of JS.


IDE generation should include header files located in c++ source directories

Currently, the Xcode generation does not include headers from the c++ source directory in the generated workspace. However, these header files can be referenced from the source files and so should be included in the project to allow a developer to navigate to them, and to refactor and edit them.

Should also work for Visual Studio. Updated the title to reflect this


In the DummyProvider workflow, two Payments are created for the same Order

I'm trying to create a payment provider for Pagseguro (a popular payment gateway here in Brazil), and I'm looking at the implementation of dummy.payments.DummyProvider.
I can debug this code and I notice that DummyProvider.get_form can be called twice: One time before the user sees the payment form, and another time after the user submits the payment form with the CONFIRMED status.

Both times, this method gets a payment instance. I expected this payment instance to be the same on both calls (the payment for that order), but saleor is creating a different payment instance to give to DummyProvider.get_form
This seems to be happening on saleor.order.views.start_payment, when it's calling Payment.objects.get_or_create (line 95 below)

The second time, we're also passing the status=PaymentStatus.WAITING parameter to that function, but the payment status was already changed to PaymentStatus.INPUT the first time, so get_or_create ends up "creating" instead of "getting".
I'm still not very familiar with saleor, so I'm not sure if this is correct behaviour, but it kinda looks like a bug.

Doesn't happend on master anymore after latest payments refactoring.


Update planar_manipulator.py

added description for failure of hw2/mandatory test

Thank you for this comment. I will make sure that all tests are independent, or I will specify dependencies explicitly in the next release of the toolbox.

Resolved in another PR by making tests independent.


Audio not playing on some iphones using built-in speakers

As stated in this thread of the forums :
https://forums.solar2d.com/t/sound-only-in-headphones-some-iphones/352015/4
Describe the bug
For some reasons, audio does not play at all on some iphones using the built-in speakers
It does work perfectly with headphones or over bluetooth.
I do own one of those devices (iphone 11 pro), on which the sound works perfectly with other apps.
I ran the audio sample app, and absolutely no sound comes out.
It does work perfectly on the simulator as well.
To Reproduce
Steps to reproduce the behavior:

build the audio sample app for ios
install on device
try to play a sound

Target platform and where build was made:

Device: iphone 11 pro
OS: 14.3 (Idem on 14.4)
Solar : Version 2021.3637 (2021.2.3)

Additional context
It seems like it does not happen on all iphone devices (or i believe someone would have noticed already).
I am the lucky owner of a device that does not work as it should, so don't hesitate to ping me if you need information/test.
whole test project or build.settings
Just the audio sample app is enough to test.

Just to make sure, did you try mute and volume controls?
Solar2D won't play sounds if device mute switch is on.

Hello Vlad,
Thanks for your help !
Ok, my bad, my phone is always on silent, and that is definitely the reason, it works perfectly now...
But so it means that it is impossible to play sounds if the phone is on silent mode ? I checked other apps that don't seem to have any problem to do so (Spotify, Chess Tactics, Radio France, etc.). It this a limitation of Solar2d ?
Is there any way to check if the user is on silent mode ? (so at least we could inform the user about the fact that he needs to switch sound mode).
Maybe it would make sense to add a Gotcha to the audio.play() API page about this, so others don't run into the same issue.

This is a long standing debate on how sound should behave. According to Apple, if device is on mute, only explicit sound playbacks should work, like when user asks to play a song in Spotify. If you notice, even videos in Safari would start muted if you have your device on mute.
You can try experimenting with this code:
audio.setSessionProperty(audio.MixMode, audio.PlayAndRecordMixMode)

Other Modes are:

AmbientMixMode
SoloAmbientMixMode
MediaPlaybackMixMode
RecordAudioMixMode
PlayAndRecordMixMode
AudioProcessingMixMode

and other properties are:

ActiveMode
MixMode
OverrideMixWithOthers
OtherAudioIsPlaying
OtherMixableAudioShouldDuck


[staging] python3Packages.packaging: 20.7 -> 20.8, python3Packages.wheel: 0.35.1 -> 0.36.2

Motivation for this change
This should be enough to allow python310 wheels to build
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

[08:32:15] jon@nixos ~/projects/nixpkgs (fix-python310-wheels)
$ nix-build -A python310Packages.coverage
/nix/store/gpp6adfvw1d78c2vrcyndyi3k8032kpd-python3.10-coverage-5.3

[08:32:15] jon@nixos ~/projects/nixpkgs (fix-python310-wheels)
$ nix-build -A python310Packages.coverage
/nix/store/gpp6adfvw1d78c2vrcyndyi3k8032kpd-python3.10-coverage-5.3

now to check this didnt massively break anything

now to check this didnt massively break anything

@GrahamcOfBorg build python27Packages.requests
@GrahamcOfBorg build python37Packages.requests
@GrahamcOfBorg build python3Packages.requests
@GrahamcOfBorg build python39Packages.requests
@GrahamcOfBorg build python310Packages.requests

@GrahamcOfBorg build python27Packages.requests
@GrahamcOfBorg build python37Packages.requests
@GrahamcOfBorg build python3Packages.requests
@GrahamcOfBorg build python39Packages.requests
@GrahamcOfBorg build python310Packages.requests

cc @FRidh this is quickly turning into a python-unstable PR :(

cc @FRidh this is quickly turning into a python-unstable PR :(

looks like there was a python-unstable bump


hover color of email shortcut buttons to bright

If you hover over the Google, Yahoo or Outlook button, the hovering color is too bright / white, so that you cannot read the text anymore. Please make the hovering color a bit darker, so that the text is readable again:

Fixed with new components


Allow the partition handling to be set even if we are not using auto clustering

I'm currently manually managing my cluster, but would like to be able to specify the cluster_partition_handling setting.  This change allows for it to be set without setting use_auto_clustering.

:+1:


Google Colab: Orca - Plotly xvfb property set to True, but the xvfb-run executable could not be found on the system path.

I am receiving a Path Error using Orca in Google Colab to save an image in a Google Colab .ipynb Python Machine Learning model.  A Flask App (written in VS Code IDE) uses the Colab trained model to output results to a URL.  To be clear, the errors occur in my Colab Python script.  This error is very similar to issue #252, however, I am unable to recreate the solution used there.
I Colab, I have created the following recommended import lines, as described in many posts:
!pip install plotly>=4.7.1    !wget https://github.com/plotly/orca/releases/download/v1.2.1/orca-1.2.1-x86_64.AppImage -O /usr/local/bin/orca    !chmod +x /usr/local/bin/orca
and
import plotly.graph_objects as go
I then use the following image write command:
fig.write_image('base_pic.svg')
I expect to see 'base_pic.svg' appear as a file when the code runs, but this is not happening.
My error seems to related to a path setting, however, I am unable to find detailed instruction to update and correct this path.  Unfortunately, I am quite novice with troubleshooting paths.
The Error:

ValueError                                Traceback (most recent call last)
 in ()
1 #TEST FUNCTION
----> 2 make_picture('AgesAndHeights.pkl',model, floats_string_to_np_array('1,  3,  3.2,  '),'x.svg')
5 frames
/usr/local/lib/python3.7/dist-packages/plotly/io/_orca.py in validate_executable()
1109 Searched for the executable 'xvfb-run' on the following path:
1110     {formatted_path}""".format(
-> 1111                     formatted_path=formatted_path
1112                 )
1113             )
ValueError:
The plotly.io.orca.config.use_xvfb property is set to True, but the
xvfb-run executable could not be found on the system path.
Searched for the executable 'xvfb-run' on the following path:
/usr/local/nvidia/bin
/usr/local/cuda/bin
/usr/local/sbin
/usr/local/bin
/usr/sbin
/usr/bin

My SetUp:
Windows 10
VS Code to run a Flask app
Google Colab to host the ML model
Python 3.9.7 used via Anaconda
I have noted several discussions where users recommend using Kaleido instead of Orca, and I am using Kaleido within the Flask app, however, I do not believe Colab supports Kaleido.  Is this correct?
Any help would be welcomed.
Mark

https://github.com/werruww/gui-in-colab


Breaking changes with DefaultPasswordGenerator class

After upgrade laravel 5.7 to 5.8 and hyn/multi-tenant from v5.3 to 5.4, all mysql users in my app are receiving the error "Access denied for user...".
After 2+ hours searching the code, I can see that it has a breaking change with key var in tenancy.php and generate method of DefaultPasswordGenerator.
This code in DefaultPasswordGenerator assumes that $key can be null:
$key = $this->app['config']->get('tenancy.key');

// Backward compatibility
        if ($key === null) {
            return md5(sprintf(
                '%s.%d',
                $this->app['config']->get('app.key'),
                $website->id
            ));
        }

        return md5(sprintf(
            '%d.%s.%s.%s',
            $website->id,
            $website->uuid,
            $website->created_at,
            $key
        ));

But $key is always filled (with APP_KEY value), even if env('TENANCY_KEY', env('APP_KEY')), in tenancy.php is missing. The only way I found to run without changing the vendor files was changing
'key' => env('TENANCY_KEY', env('APP_KEY')),
to
'key' => env('TENANCY_KEY', NULL),
So, I would like to suggest this change to tenancy.php file...

Hello Diego,
Thank you for opening this issue. You are correct that this change in the DefaultPasswordGenerator will break existing installations. We are fully aware that this is the case, as such the version was bumped to 5.4 instead of tagging a patch version. Inside the upgrade guide of the documentation we clearly elaborate on this change:

For the full list of backward breaking changes I recommend reading the upgrade guide: https://laravel-tenancy.com/docs/hyn/5.4/upgrade-from-5.3#backward-breaking-changes
Once again thank you for reaching, at this point we see no reason to change the implementation based on your feedback.


After updating the node to the latest version, I have such a mistake. How can I solve it?

Error occurred when executing KSampler:
sliding_sampling_function() got multiple values for argument 'model_options'
File "H:\ComfyUI_windows_portable\ComfyUI\execution.py", line 153, in recursive_execute
output_data, output_ui = get_output_data(obj, input_data_all)
File "H:\ComfyUI_windows_portable\ComfyUI\execution.py", line 83, in get_output_data
return_values = map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True)
File "H:\ComfyUI_windows_portable\ComfyUI\execution.py", line 76, in map_node_over_list
results.append(getattr(obj, func)(**slice_dict(input_data_all, i)))..............
....

I made a series of updates since last week and I would like to confirm if you are still having issues.


access to dpi_scale_factor

I still have an issue with mouse coordinates on hidpi screens when with_automatic_console_resize is false.
doryen-rs provides f32 console cell mouse coordinates. I need to compute them from bracketlib's mouse_pixel_pos and for that I need the dpi_scale_factor.
When with_automatic_console_resize is true, I get this factor on the first resize event but when it's false, no resize event is sent.
I think in a more general way, it would be nice to make this value available to the end user, for example though ctx.dpi_scale_factor

There's actually two issues in one here:

The mouse pixel position available via input.mouse_pixel_pos() really should be scaled to take into account high DPI anyway.
It's a good idea to offer the scale_factor, but it will always be 1.0 on back-ends other than native GL.

There's two commits about to hit that provide both of those.

nice :) Now it works out of the box at start, but if I resize the window, the console is scaled and it's broken again because I can't be aware that the screen size has changed.
I think bracketlib should send Resized event even when with_automatic_console_resize is false. This way the end user can be informed that the char size has changed even though the console size is the same. You removed this event because doryen-rs was systematically resizing the console but it was rather an issue in doryen-rs.

ok it seems all cases are working on native target. now to the web target... :)


Weekday border dose not change with monthview show border false

month view file show include this:
Widget _defaultWeekDayBuilder(int index) {
return WeekDayTile(
dayIndex: index,
weekDayStringBuilder: widget.weekDayStringBuilder,
displayBorder: widget.showBorder, // this line should be added there
);
}

You can make custom weekDayBuilder in that you can access displayBorder field which does the same thing.


Switching to Vert.x 3.4.0.Beta1.

DO NOT MERGE!

I've renamed branch and moved this pull request to #275

Moved to #276

-> #276


[Machine Learning] How to Implement  K Means Clustering Algorithm in Python

Topic Suggestion
Pre-submission advice
By following all our pre-submission advice and reviewing our Resources folder, you will maximise your chances of your topic being approved.
We ask that you please be patient as our team works through approving and publishing all articles/tutorials in a timely manner.
Allow 1-3 days for a topic to be reviewed and/or approved - allow 3-7 days for an articles to be reviewed and/or published.
Be sure to visit our Resources Page for tools, resources, and example articles that will help you propose and write a successful article.
Please ensure that you have only one open issue + linked pull request at a time. This will ensure that we complete the article in a timely manner from inception to publishing.)
We tend to stray away or tend not to publish reviews/comparisons of commercial product offerings.
Writing sample(s):
Include any links or writing samples - to help our team better gauge your writing quality.
Proposal Submission
How to Implement  K Means Clustering Algorithm in Python
Proposed article introduction
K-Means clustering is an unsupervised learning algorithm that sample data points with similar characteristics together. This algorithm is widely used in clustering tasks. The good thing with the K Means algorithm, it works with datasets in both low and high dimensional spaces. This algorithm involves finding the centroids of the clusters and assigning each data point to the cluster with the closest centroid. The K in the K Means means the number of clusters.  There are defined methods used to choose the value of k from the data, i.e., the elbow method.
Below are the steps involved K Mean Algorithm :

Step 1: Choose the number of clusters

Step 2: Choose at random the k initial centroids

Step 3: Assign each observation to the closest centroid

Step 4: Recompute the centroids

Step 5: Reassign each data point to the new closest centroid. If any reassignment occurs, we repeat step four; otherwise, we finish and declare our model ready for classification tasks.

As this is an implementation guide, instead of covering all unnecessary statistical presentations for the K Means algorithm, we will only talk about what happens under each of the above steps with the aid of a visual example, i.e., a scatter plot. By so doing, the learner will have a clear understanding of this algorithm rather than throwing them all the confusing statistical presentations that do not contribute much to its implementation.
So, in our study, we will be restrained within the steps. After we have considered what happens, we will implement this intuition in python using the sklearn library.
Key takeaways

The learner will know what the K Means algorithm is.
The learner will, step by step, know how the K Means algorithm works.
The learner will know some of the methods to choose the number of clusters k.
The learner will know how to implement the K Means algorithm in python.

Article quality
What will make my article different is the way I will deliver the intuition behind this algorithm. To my best, I'll ensure the learner is exposed to what is important for this session. What is not essential will be regarded as noise for this session and thus will not be considered in the study.
The coding session will explain each step in a clear and precise way, and thus the learner will not struggle with following along with all this material
References
N/A
Conclusion
Finally, remove the Pre-Submission advice section and all our blockquoted notes as you fill in the form before you submit.
We look forwarding to reviewing your topic suggestion.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Good afternoon and thank you for submitting your topic to the EngEd program.
After some careful consideration, it struck us that this topic may be a bit over-saturated throughout other blog sites and official documentations.
We typically refrain from publishing content that is covered widely on the net or other blogs. We're more interested in original, practitioner-focused content that takes a deeper dive into programming-centric concepts.
But in order to approve the topic, it has to serve value to the larger developer community at large.
An option and a great way to write this as an in-depth article and make it more add value to the greater developer community at large would be to walk the reader through the USE of methods and functions by building a unique, different, useful project.

We would love to learn your thought process behind the solution you arrived at using these concepts and topics.

That way a developer could see them in action.
As mentioned above - we believe this topic is widely covered on other blog sites.
The best way for students to build a great portfolio is by building what does not exist and what can provide the most value.


Add ability to customise pod annotations

Please add ability to customise pod annotations for deployment k8s-image-availability-exporter
for example:
  template:
    metadata:
      {{- if .Values.k8sImageAvailabilityExporter.annotations }}
      annotations:
       {{- include .Values.k8sImageAvailabilityExporter.annotations . | nindent 8 }}

@artemiyplotnikov sure, but can you elaborate on why you need this? (This is important to know usescases for features).

First of all we use annotations for filtering and configuring scraping options.
For example:
      annotations:
        prometheus.io/scrape: 'true'
        prometheus.io/port: "{{ .Values.env.PROMETHEUS_PORT }}"

I know that there is another options to configure Prometheus scrape but it would multiply configuring options and hardenes

Closed by https://github.com/deckhouse/k8s-image-availability-exporter/pull/212


What is single_attention_param?

Could you explain what is the meaning for setting single_attention_param=True in your AttentionLSTMWrapper()?
Thanks!

It was an option to change the type of attention to use. If single_attention_param=True then the attention component would consist of a single scalar value that would be multiplied at each timestep by the h vector of the LSTM to get the new h vector. Otherwise, if single_attention_param=False the attention component is a vector that is the same dimensionality as the h vector, and multiplies element-wise to get the new h vector at each timestep.


Option to remove a theme

Can you add an option to remove an theme

That's https://github.com/vector-im/element-web/issues/13221


Add SMB flag for treatment history

This PR adds a flag for SMB boluses to the PumpHistoryStorage and subsequently alters the treatment history when displaying boluses. For a manual bolus, it displays a blue filled circle with the word "Bolus" and dosage. For an SMB bolus, it displays a blue filled circle, instead of "Bolus" it displays 🤖 and the dosage.

First off, I love this.
my 2 cents are:
I wonder if it would be clearer for SMB to call it "SMB Bolus" as opposed to a Robot ?  And "Manual Bolus" otherwise
Or maybe a gear ⚙ icon for SMBs. and a Person 🙎 icon  for Manual Bolus. ( like in some process flowcharts).
Cheers

my 2 cents are: I wonder if it would be clearer for SMB to call it "SMB Bolus" as opposed to a Robot ? And "Manual Bolus" otherwise Or maybe a gear ⚙ icon for SMBs. and a Person 🙎 icon for Manual Bolus. ( like in some process flowcharts).

Thanks for your feedback on this. After some more feedback on Discord this was now changed to the following format (@Jon-b-m handled this himself):
Manual Bolus:
Blue Circle <time> Bolus <dose> U Manual
SMB:
Blue circle <time> SMB <dose> U Auto
The robot is gone.

Sounds lovely.   The Robot was pretty cute
On Mon, Sep 25, 2023 at 12:00 PM Deniz Cengiz @.***>
wrote:

my 2 cents are: I wonder if it would be clearer for SMB to call it "SMB
Bolus" as opposed to a Robot ? And "Manual Bolus" otherwise Or maybe a gear
⚙ icon for SMBs. and a Person 🙎 icon for Manual Bolus. ( like in some
process flowcharts).
Thanks for your feedback on this. After some more feedback on Discord this
was now changed to the following format @.***
https://github.com/Jon-b-m handled this himself):
Manual Bolus:
Blue Circle  Bolus  U Manual
SMB:
Blue circle  SMB  U Auto
The robot is gone.
—
Reply to this email directly, view it on GitHub
https://github.com/Artificial-Pancreas/iAPS/pull/219#issuecomment-1734040420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBIJXTBCN63M76XRFWJQLX4GTCVANCNFSM6AAAAAA5FHMAZE
.
You are receiving this because you commented.Message ID:
@.***>

I liked the robot too. Perhaps we could find something almost everyone agrees with?

Från: flyingpie101 @.>
Skickat: Monday, September 25, 2023 6:01:59 PM
Till: Artificial-Pancreas/iAPS @.>
Kopia: Jon B Mårtensson @.>; Mention @.>
Ämne: Re: [Artificial-Pancreas/iAPS] Add SMB flag for treatment history (PR #219)
Sounds lovely. The Robot was pretty cute
On Mon, Sep 25, 2023 at 12:00 PM Deniz Cengiz @.***>
wrote:

my 2 cents are: I wonder if it would be clearer for SMB to call it "SMB
Bolus" as opposed to a Robot ? And "Manual Bolus" otherwise Or maybe a gear
⚙ icon for SMBs. and a Person 🙎 icon for Manual Bolus. ( like in some
process flowcharts).
Thanks for your feedback on this. After some more feedback on Discord this
was now changed to the following format @.***
https://github.com/Jon-b-m handled this himself):
Manual Bolus:
Blue Circle  Bolus  U Manual
SMB:
Blue circle  SMB  U Auto
The robot is gone.
—
Reply to this email directly, view it on GitHub
https://github.com/Artificial-Pancreas/iAPS/pull/219#issuecomment-1734040420,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBIJXTBCN63M76XRFWJQLX4GTCVANCNFSM6AAAAAA5FHMAZE
.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHubhttps://github.com/Artificial-Pancreas/iAPS/pull/219#issuecomment-1734042620, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM3IOX56B6LKW7X5MTAMPDTX4GTHPANCNFSM6AAAAAA5FHMAZE.
You are receiving this because you were mentioned.Message ID: @.***>

@flyingpie101 yes, I really liked the robot too. So did @Jon-b-m.
What do you guys think about either doing 🤖 Auto or completely replacing Auto with just the 🤖?
The former is about the same size/length than the word „Manual“, so it shouldn’t give us space issues or make the view cluttered, while still having something with a smirk in there, and the addition „Auto“ still explains what it means to an extent.

While I do like the robot.
I think for the app, its not enough convey what is happening.
So, yes, either robot plus 'words' or just words.
As much as I think hes cool, he might not be professional enough, lol
On Mon, Sep 25, 2023 at 12:47 PM Deniz Cengiz @.***>
wrote:

@flyingpie101 https://github.com/flyingpie101 yes, I really liked the
robot too. So did @Jon-b-m https://github.com/Jon-b-m.
What do you guys think about either doing 🤖 Auto or completely replacing
Auto with just the 🤖?
The former is about the same size/length than the word „Manual“, so it
shouldn’t give us space issues or make the view cluttered, while still
having something with a smirk in there, and the addition „Auto“ still
explains what it means to an extent.
—
Reply to this email directly, view it on GitHub
https://github.com/Artificial-Pancreas/iAPS/pull/219#issuecomment-1734120080,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACYBIJQ4MTG335RJYTWTE7TX4GYSBANCNFSM6AAAAAA5FHMAZE
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think if we want to be "perfectly clear" and "professional", we should actually do Automated and Manual. I am kind of expecting the first questions why it says "Auto".

Perhaps have a robot to the very left on all of the automatic trratments. SMB and temp basal (but not manual temp basal).  Everybody understands a robot, even kids, which could help make it more clear what is done automatic and what isn’t….

Från: Deniz Cengiz @.>
Skickat: Monday, September 25, 2023 7:33:17 PM
Till: Artificial-Pancreas/iAPS @.>
Kopia: Jon B Mårtensson @.>; Mention @.>
Ämne: Re: [Artificial-Pancreas/iAPS] Add SMB flag for treatment history (PR #219)
I think if we want to be "perfectly clear" and "professional", we should actually do Automated and Manual. I am kind of expecting the first questions why it says "Auto".
—
Reply to this email directly, view it on GitHubhttps://github.com/Artificial-Pancreas/iAPS/pull/219#issuecomment-1734185135, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM3IOXZS2N5ALXOXQRQ7ONDX4G553ANCNFSM6AAAAAA5FHMAZE.
You are receiving this because you were mentioned.Message ID: @.***>

I think if we want to be "perfectly clear" and "professional", we should actually do Automated and Manual. I am kind of expecting the first questions why it says "Auto".

Yes, I choose "Auto" because we already had a translation for "Auto", but "Automatic" is better, I do agree


Fix .editorconfig

The .editorconfig file contains a declaration that is syntactically incorrect:
[*.dsl,*.groovy,Jenkinsfile*]
It is not possible to enumerate globs like this.
Either there is a different way to enumerate them, or this section needs to be split up in three sections.
The more delicate part is then in applying the new formatting.
VS Code was the most pleasant tool to do that, because when indenting the top level element it will also adjust indentation for child elements at the same time.

Wrong repo


Parsing multiple languages for signature type (German + English)

Adds parsing of german language for signature types.
Improvements for later versions:

Add parsing of signature names
Add other languages (help needed)

PS: Thanks for making this tool!

Is it planed to add french too?

If you could tell me the translations for the signature names and types. I will add them!
For other languages too.
Language specific name -> English

If you could tell me the translations for the signature names and groups, I'm able to add these.
(other languages are possible too)
'Cosmic Anomaly',
'Cosmic Signature'
'Combat site',
'Relic site',
etc

Yeah sure, just let me some time to regroup all those names and groups.
Thanks! :)

Do you know if I can find such a list in the installation folder of the game on my computer?
Or do I have to fly through Eve ton make that list?
Where did you found the german names?

I haven't used a list.
But I've done exploration many times before and you've got nearly all sites inside a wh.
That would be the easiest way to start.

Yeah I know, for the wh it's easy, but I try to find the sig in LS/HS/NS too.

The types and groups are always the same.
The name of the signature is currently not parsed.
So the types and groups would be sufficient :)

Ha! I forgot the most important:
Wormhole -> Trou de verre

That should be all!
I will add it today's evening or tomorrow :) depends on my free time

I made a MISTAKE :
Wormhole -> Trou de ver
Das ist der Hammer! Vielen Dank!!

Added french to the latest version.
(Don't forget you've got to rebuild the js files!)

Great!
Just one thing: data site -> site de données  [you wrote site de donnes]
Thanks again!

Oh my fault I thought I copy pasted. Will correct it tomorrow.
Thanks!

(Don't forget you've got to rebuild the js files!)

Weißt du wie ich das machen soll? Ich habe Firefox.

Inside the wiki is an article about it. It's serversided it doesn't matter which browser you're using.
Pathfinder Wiki NodeJs Build
Der Artikel im Wiki den ich oben gelinkt habe beschreibt das ganze sehr gut.

Aber sorry noch mal... Ich verstehe hier gar nichts. Ab '$npm install' funktioniert gar nichts

npm WARN enoent ENOENT: no such file or directory, open C:\Users\Komputername\package.json
und so weiter...

und bei 'npm list --depth=0' bekomme ich nur

C:\Users\Komputername
'-- (empty)

@Pseude you need to stay in directory , where is the package.json located, in other words, change to root of the pathfinder install and then run npm install.

I do not understand how to make the modifications activ.
How should I change to root of the pathfinder install?

I think I have'nt any elements. Do I need to host Pathfinder myself to use the french terms on Pathfinder?
The changes do not come automatically?

Yeah you need to host it yourself. Or you can wait until @exodus4d is merging this into his version.
PS: Sry for the late answer had not really much time.

OK, I understand now.
Alles in Ordnung, das ist perfekt! Danke!

TL:DR
have you already implemented the German language?`
Regards!

Yes it's implemented but it haven't been merged into pathfinder by now.

Currently it running on my private pathfinder installation with no issues :-)

Hi thanks for your work! I´ll have a look at your implementation when v1.2.3 is released. I´m totally busy with the new Admin interface (#494) and ESI improvements, which are scheduled for the  upcoming release for now.
I´m not quite sure if your approach (all languages in a single file) will scale well. When adding more languages to the sig-parser in future. It might be more flexible to have separate language files that can be dynamically required by a client on demand.

Thanks for your answer!
The approach is client sided with a regex. It's possible to precompile that regex to improve the performance.
The benefit of this approach is that the user can paste any language and it's automatically accepted.
Currently only the type of the site is parsed and the name is added as description. (Wasn't sure if someone else than me is interested in this feature)
But it would be possible to parse the name too. Then the next step would be to add a language selection for the UI to show the real name from the selected language.
Imho the best would be to parse any language independent of the selection and show the name and type with the selected language.

@Kill4Free

Hint: The Gulp build Process will be changed in v1.2.4. Please read the updated Wiki, if you are planning to commit Js/Css PRs in future: https://github.com/exodus4d/pathfinder/wiki/GulpJs

@exodus4d thanks for the link :)


Riv review 1

Issue #, if available:
Description of changes:

default to hub cluster in kubectl context
.. more to come

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@markoskandylis

worth to add as a last line of the script:
kubectl config use-context fleet-hub-cluster
Just to assure the hub context will be used?

Good feedback this can be done in subsequent PR


different popus for different markers

From @Danny-weebo on February 18, 2015 14:47
Hey, I'd like to set a different class name for each popup marker so I can have different styles of popups for different types of markers. Any advice on how it's done properly? I thought about attaching a class name to a popup depending on which type of marker was clicked, but I have no idea about how to approach the task.
@israelidanny
Copied from original issue: tombatossals/angular-leaflet-directive#637

From @Getz85 on February 19, 2015 15:30
The message property of marker's object can contain HTML.
You can check this example:
http://tombatossals.github.io/angular-leaflet-directive/examples/markers-angular-template-example.html

From @EvilDaemon on May 1, 2015 15:21
how pass params to template?

From @mastermind1981 on June 19, 2015 0:0
In the continuity of this issue, one of my use case is to have a directive for marker's popup like this :
1.
                 message: '<info-box param1="param1" param="param2"></info-box>',

info-box is a directive with template and it's own scope.
2.
I have another case, where i create an array of makers and i want  to create the popup with parameters of the directive are passed when looping like this
          angular.forEach($scope.hits, function(hit){
               coords = hit._source.location.split(',');
              $scope.markers.push ({
                 title : hit._source.title,
                 lat: parseFloat(coords[0]),
                 lng: parseFloat(coords [1]),
                 getMessageScope: function () { return $scope; },
                 message: '<info-box title="hit._source.title"></info-box>',
                 compileMessage: true,
                   });
           });

Is it possible to make the point 1 and 2?
Thanks in advance,