RPJ/Casper testing lang

Issue
This testing lang is up for discussion https://notes.ethereum.org/6ozACHyKR9i86vfkt086Ow#.
Once we decide we like it, we should implement :)
This issue can either be implemented in conjunction with https://github.com/ethereum/beacon_chain/issues/13 or after

@prestonvanloon has put together the following thoughts. Can you guys take a look and let us know what you think? Thanks!

Properties
Here are the properties I would find useful:

Comment support

This is important for self documentation, and also quickly disabling/re-enabling tests
Note that JSON does not support comment

Readable

This means white-space are insignificant so we can prettify alignment by using whitespaces

Can be autogenerated

This will be helpful to create new test cases
Can serve as dump format for logs or crashes for reproduction.

A clear distinction between input, output and exceptions

The exceptions should be properly defined as well (i.e. say integer overflow vs array indexing error)

Comments on current proposal
It seems like inspired by CSV for input, with : to separate constants: votes: result, rules should be clear on:

separator allowed (only , and :)
if ever needed:

quote ' "
escaping quotes, comments, line breaks and the escape characters

What is needed?
To clarify what is needed, we should probably make sure of what the lang should encode, I note:

Validator
Epoch length
Shard Count
Min Committee Size
numerical range of validator
uppercase alphabetical range of fork choice. I probably missed it but are there situation with more than 26 choices?
specifying empty slots
validators from multiple sets voting for the same fork 2-7AC [2]6-7AC
asserting the slot you are in [=6]
Am I missing something?

Canonical test
This vote part for slot 2 and 3 is a bit unclear 0-5AB, 2-7AC [2]6-7AC

In slot 2, validators 0-5 of the validator set of slot 2 vote on B, a child of A
In slot 3, validators 2-7 of the validator set of slot 3 vote on C, a child of A, and validators 6-7 from the validator set of slot 2 do the same

So we could use the following as an equivalent right?
6-7AC [3]2-7AC, [2]0-5AB

@mratsim I guess the comma separates what event should happen in when.
If we focus on the validators 6-7 defined in slot 2.

in ..., 0-5AB, 2-7AC [2]6-7AC case: they vote on slot 3 (the 16~23 seconds)
in ..., 6-7AC [3]2-7AC, [2]0-5AB case: they vote on slot 2 (the 8~15 seconds)
By the way, the [3]2-7AC might be causally problematic, as the validators defined in slot 3 is undefined in slot 2.


task: beta releases

Description: Sets up the example app for internal distribution to testers, so people can install it on their phones and play with Embed mobile. Uses fastlane and it's a manual process for now that can be triggered via a command ./beta.sh ios|android. Release notes can also be added with ./beta.sh notes:"Added [x]". Uses Firebase App Distribution to handle releases and testers groups.
NOTE: For now I'm using my own gr4vy Google account for Firebase, if this works well for everyone we can later move things to<EMAIL_ADDRESS>NOTE: iOS users have to enable developer mode in order to install and use the app distributed by Firebase. This is a known limitation, although it might be annoying / not desired by people. I will get some feedback on that and use TestFlight instead of Firebase for iOS if needed.
Ticket: https://gr4vy.atlassian.net/browse/TA-4603

:rocket: PR was released in v1.1.0 :rocket:


Implement @use scheme

[x] Allow annotations like @use after capture types
[x] Implement @use scheme:

We allow @use on parameter types.
If we narrow cap to a reach capability under a @use, the reach capability becomes use-declared.
We print such reach capabilities as x*@use for debugging.
A use-declared capability can leak into the method owner the parameter.
User-written reach capabilities of parameters whose type carries a @use annotation are also allowed to leak into the enclosing method..
On the other hand, if we pass an actual argument(-part) to (part-of) a formal parameter type that is annotated with @use, we charge the deep capture set of the argument to the currently enclosing environments.

[x] Check that overridden methods are @use correct. This means if an overridden method has @use in some parameter types, the overriding method must have these parameter types under @use as well.
[x] Drop previous @unbox scheme.
[ ] Make sure @use appears only in covariant positions of parameters, nowhere else.
[ ] Infer @use annotations. If a parameter has a type containing occurrences of cap and the parameter is not referred to from a function result, add an implied @use to the parameter type. The idea is that we'd pass a parameter with universal capturing type only if the parameter is either returned or used in the method. So if it is not returned we can infer an @use.
[ ] Generalize the scheme to also handle capture set variables in addition to reach capabilities.

Built on the paths PR

Good luck for https://github.com/unbox, bad luck for https://github.com/use (or their inboxes 😉). I hope no language or framework author ever thinks @lrytz would be a nice annotation.

OK, will backquote things from now on.

I hope no language or framework author ever thinks @lrytz would be a nice annotation.

New experimental polymorphic effect system confirmed.

Closing since I am no longer hopeful that this approach will work out.


Property 'getChatCompletionWithConfig' does not exist on type 'Service'.ts(2339)

Property 'getChatCompletionWithConfig' does not exist on type 'Service'.ts(2339)

TypeScript is not supported yet.


IBusControl.StopAsync() does not clean up connection to RabbitMQ

Used 3.4.1, then upgraded to 3.5.2
When IBusControl.StopAsync() with 3.4.1, all open connections to RabbitMQ are closed.
With 3.5.2, the consumers are disconnected, but the connection to RabbitMQ lives on until the host application is shutdown.
Comparing the relevant code I see that the older version stopped ReceiveEndpointHandles but the new version does not.
https://github.com/MassTransit/MassTransit/blob/v3.5.2/src/MassTransit/MassTransitBus.cs#L271

Never Mind. Was on our end, sorry for the useless issue


Add Cohen's kappa to performance measures.

Heres' an implementation suggested by Rahul Goyal at this julia discourse thread:
function kappa(predictions, original)
    # Confusion matrix
    confmat = MLJ.confusion_matrix(mode.(predictions), original)
    confmat = confmat.mat
    z = (TP = confmat[1,1], FP = confmat[1,2], FN = confmat[2,1], TN = confmat[2,2])

    # Calculate kappa
    length_y = length(original)

    p_0 = (z.TN + z.TP)/length_y
    p_e_1 = (z.TP + z.FP) * (z.TP + z.FN)/(length_y^2)
    p_e_2 = (z.TN + z.FP) * (z.TN + z.FN)/(length_y^2)
    p_e = p_e_1 + p_e_2
    κ = (p_0 - p_e)/(1 - p_e)

    return κ
end

The above thread includes updated code for the multiclass case. Since the binary case is just an immediate specialisation of the multiclass case, there would be no need to implement a special binary version.
Apart from the user guidelines for measures, there are these guidelines for adding new measures.
The new code would live here.
The type Kappa would be Aggregated <: Measure and we'd declare:
metadata_measure(Kappa;
                 instances = ["kappa",],
                 target_scitype           = FiniteArrMissing,
                 prediction_type          = :deterministic,
                 orientation              = :score)

Here FiniteArrMissing is an alias for AbstractArray{<:Union{Finite,Missing}} defined in MLJBase.

@ablaom I created the code for Kappa but am unable to create a branch to raise a PR. Can you please let me know how to do that?

Sure. Thanks for working on this. Note, you will need to be somewhat familiar with git version control to understand some of the instructions.
The procedure is:

Fork the MLJBase repository, which creates a new repo in your personal github account
Clone the fork repository to a local clone on your local machine. You can do this by:

opening up your fork in github and clicking on the green "Code" button, which gives you the opportunity to copy the url for the fork into your clipboard
on your local machine, run (in a unix shell, say) git clone <contents of clipboard> from within a directory which you use to contain github repos. So, this will look something like git clone https://github.com/Rahulub3r/MLJBase.jl.git. Now you have a directory called MLJBase.jl on your computer, the local clone.

make changes you want in the local clone. You can do this in the dev branch that will be checked out by default or, if you want and know how, create a new branch off dev branch.
commit the changes
push the modified branch (I'll assume it's dev) to your github fork. I believe the command you'll need is something like git push -u origin dev, which assumes the remote repository is called origin which I think is the default behaviour.
Make your PR, selecting dev at your fork as the source, and dev at JuliaAI/MLJBase as the target. Probably, the next time you open your fork (or refresh it) an automated option to do this will appear, and you just follow your nose.

Let me know if you get stuck at some point.

Thank you for the detailed instructions. Created a PR - https://github.com/JuliaAI/MLJBase.jl/pull/738

Sure. Thanks for working on this. Note, you will need to be somewhat familiar with git version control to understand some of the instructions.
The procedure is:

Fork the MLJBase repository, which creates a new repo in your personal github account

Clone the fork repository to a local clone on your local machine. You can do this by:

opening up your fork in github and clicking on the green "Code" button, which gives you the opportunity to copy the url for the fork into your clipboard
on your local machine, run (in a unix shell, say) git clone <contents of clipboard> from within a directory which you use to contain github repos. So, this will look something like git clone https://github.com/Rahulub3r/MLJBase.jl.git. Now you have a directory called MLJBase.jl on your computer, the local clone.

make changes you want in the local clone. You can do this in the dev branch that will be checked out by default or, if you want and know how, create a new branch off dev branch.

commit the changes

push the modified branch (I'll assume it's dev) to your github fork. I believe the command you'll need is something like git push -u origin dev, which assumes the remote repository is called origin which I think is the default behaviour.

Make your PR, selecting dev at your fork as the source, and dev at JuliaAI/MLJBase as the target. Probably, the next time you open your fork (or refresh it) an automated option to do this will appear, and you just follow your nose.

Let me know if you get stuck at some point.

Maybe this should be pinned somewhere visible within this repo to aid first time contributors.


Is updation of an autofollow replication rule allowed?

Is updation of an autofollow replication rule allowed?
Consider that an autofollow replication rule (test-rule) exists in the system which corresponds to the index pattern (test-). Now when we try to update the rule with a new index pattern (new-), the API returns {acknowledge: true} but there is no index getting replicated of the updated index pattern (new-). The indices falling under test- are getting replicated even after the updation of replication rule.
What is the expected behavior?

If updation of replication rule is allowed, then the new index pattern should be considered for the replication.
If its not allowed, then the API should not return with response 200.

Hi @ankitkala @monusingh-1,
Any insight on the above query ?
In the above sceanrio, it would be better to check if there any existing replication rule before creating a new replication rule (i.e) the API should throw exception in case of overriding an existing rule.

I think we should block the autofollow rule updates with proper validations.

Hi @ankitkala ,
can you assign this ticket to me? I would like to work on it :)

[Catch All Triage - Attendees 1, 2, 3, 4, 5]


1.0.4 IE11 functionality is broken

The "Implement 'important' prop handling" commit broke IE11 functionality.
The "this.$el.style.setProperty('height', heightVal, important)" in the resize() function silently fails on IE11 when "important" is undefined.
Consider modifying to (tested on my end):
if (important) {
      this.$el.style.setProperty('height', heightVal, important);
} else {
      this.$el.style.setProperty('height', heightVal);
}

broken on Edge too, turn :important to true fix it.


Fix formatting

I see that we already have a .swift-format file, so I ran swift-format, and there are some changes, perhaps because I didn't run it before submitting a previous PR. Maybe we can configure a GitHub action so that all PRs are checked before merging. Once this is merged, I'll revise my previous PR to remove changes due to formatting differences.
Would you mind if we remove lineBreakBeforeControlFlowKeywords? I find the code more difficult to read with this setting enabled, and I think most Swift code does not use this rule, but it's also a matter of personal taste.

Closing in favor of https://github.com/johnmai-dev/Jinja/pull/10


merge MONDO_0016248 'familial ovarian cancer' with MONDO_0004033 'familial ovarian carcinoma'

consider merging MONDO_0016248 'familial ovarian cancer' with MONDO_0004033 'familial ovarian carcinoma'
from the comments on this class:
Editor note: TODO check why ORDO classifies as non-epithelial.  See also familiar ovarian carcinoma, consider merge
Is this comment referring to MONDO_0004033 'familial ovarian carcinoma'?

It looks like Orphanet is using familial ovarian cancer as a grouping class - it says "This term does not characterize a disease but a group of diseases. To learn about the diseases included under this term, you can consult the classifications."
The children are:
MONDO_0003582 'hereditary breast ovarian cancer syndrome'
MONDO_0016249 'hereditary site-specific ovarian cancer syndrome'
I don't think these would be properly classified as children of MONDO_0004033 'familial ovarian carcinoma'
I think these terms should not be merged. I will remove the comment on a PR (that suggests to merge the terms) but please reject my PR if you disagree.


Documentation Needs Updating

This is a issue for discussing a current push towards updating the documentation.

Have done a fairly complete review of the documentation (actually learned a lot), the biggest area for improvement that I see is in the Motivation and Tutorial sections, e.g., the approach on handling errors is pretty amazing and not apparent from these sections.  As part of the review, I spent time writing a separate series of articles on Medium that captures a lot of what I believe would be helpful to incorporate.
https://medium.com/@johntucker_48673/redux-actions-through-example-part-1-f5b2dc71de06

This is awesome! Would love to incorporate these posts into the Motivation/Tutorial sections.

Before I started to propose to make changes to the documentation, I sat down and documented how the documentation was organized (that is a mouthful).  Was sufficiently interesting, that I wrote yet another Medium article on it:
https://medium.com/@johntucker_48673/open-source-documentation-by-example-8599c81d4ab7

BTW... Through the documentation, it seems that the files in the docs folder have been updated but the generated web site was not re-generated.  This seems to be the first order of business (either manual or with Travis CI).

This has been fixed, because the docs were based on a fork by a contributor. It's now in sync with docs on master.


Error response from daemon: Missing certificate domain.cert for key domain.key

Hi all,
I've been hacking my registry for almost 2 days now and no luck finding a solution to this so far.
I've setup a registry at this address:
curl -vvvv -i -L https://registry.equalexperts.io:5000/v2/
The docker compose is pretty straight forward:
cache:
  image: redis
registry:
  restart: always
  image: registry:2
  ports:
    - 5000:5000
  links:
    - cache
  volumes:
    - /home/ubuntu/data:/var/lib/registry
    - /home/ubuntu/certs:/certs
    - /home/ubuntu/auth:/auth
    - /home/ubuntu/config.yml:/etc/docker/registry/config.yml
frontend:
  image: konradkleine/docker-registry-frontend
  ports:
    - 8081:80
  environment:
    ENV_DOCKER_REGISTRY_HOST: registry
    ENV_DOCKER_REGISTRY_PORT: 5000

with the config.yml being:
version: 0.1
log:
  level: debug
  fields:
    service: registry
    environment: staging
storage:
  s3:
    accesskey: <ACCESS_KEY>
    secretkey: <SECRET_KEY>
    region: eu-west-1
    bucket: ee-docker-registry-data
    encrypt: false
    secure: true
    v4auth: true
    chunksize: 5242880
    rootdirectory: /registry
auth:
  htpasswd:
    realm: basic-realm
    path: /auth/htpasswd
http:
    addr: <IP_ADDRESS>:5000
    host: https://registry.equalexperts.io:5000
    tls:
      certificate: /certs/registry.equalexperts.io.chained.crt
      key: /certs/registry.equalexperts.io.key
    debug:
        addr: localhost:5001
redis:
    addr: localhost:6379
    db: 0

I do successfully curl and login to my registry from a docker-machine running on max os
docker -v Docker version 1.9.1, build a34a1d5
docker-machine -v Version: 0.5.5, build 02c4254

However attempting to push an image causes this error:
Error response from daemon: Missing certificate registry.equalexperts.io.cert for key registry.equalexperts.io.key
The whole list of commands is:
docker run hello-world
docker tag hello-world registry.equalexperts.io:5000/hello-world
docker push registry.equalexperts.io:5000/hello-world
docker tag hello-world registry.equalexperts.io:5000/hello-world
docker push registry.equalexperts.io:5000/hello-world

The certificates are created with sslmate, and as you can see in the config.yml I am passing the chained one to the docker registry.
I really can't see what is wrong with my configuration.
Thanks in advance,
toni
Quick addition (that might help if anybody else is searching for workarounds), amending sudo vi /var/lib/boot2docker/profile the docker-machine file by adding:
--insecure-registry registry.equalexperts.io:5000  inside the default: EXTRA_ARGS='--label provider=virtualbox' did the trick (you will have to restart the docker daemon sudo /etc/init.d/docker restart
Makes the push work, of course, the whole point of getting a certificate was to have a secure registry, so this will unblock me for now but doesn't seem a reasonable solution.

You need to copy the cert to /etc/docker/certs/registry.equalexperts.io:5000/cert on the docker engine host and restart it.
This was covered here but was unintentionally removed.

thanks @stevvooe for the prompt reply, I'll try that, I am happy to restore that documentation and send a pull request

Make sure on the daemon that TLS client certificates have the ending ".cert", and CA certificates have the ending ".crt", if you have ".key" without a ".cert" you will get that error, it will not attempt to use a ".crt" file.

@aterreno I've filed #19473 to get back the new documentation. The PR #19511 has been submitted to fix that. It would be good to get your feedback as this can be a sticking point for registry deployment.

I suppose it's clear.
One doubt check my tree here:
├── certs
│   └── registry.equalexperts.io:5000
│       └── cert
│           ├── client.cert
│           ├── client.key
│           └── registry.equalexperts.io.crt
├── certs.d
│   └── registry.equalexperts.io:5000
│       ├── client.cert
│       ├── client.key
│       └── registry.equalexperts.io.crt
└── key.json

The cert/reg/cert folder is as @stevvooe suggested, the certs.d dir is as the docs suggest.
I am running on Linux ip-172-20-0-147 3.19.0-20-generic #20-Ubuntu SMP Fri May 29 10:10:47 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
and the /etc/init.d/docker doesn't tell much on where those certs should be, do you think it woulds be a good idea to put those infos there? I feel like it should be an optional environment variable.
Last but not least, I've generated client.cert and client.key as described in the docker docs on the boxes where docker daemon will pull and the crt file is the same of the docker registry: does it make sense?
thanks a lot

@aterreno No problem. I'll close this when we work out the documentation issues. Thank you for your patience.

I'll probably blog about how to set the registry up, in combination with
how to get login inside a kubernetes cluster, the two together now work
like a charm but I had to do a bit of reverse engineering on both projects
docs to get it right :)
Thanks a lot for your help guys, really appreciated
On Thu, Jan 21, 2016 at 7:57 PM, Stephen Day<EMAIL_ADDRESS>wrote:

@aterreno https://github.com/aterreno No problem. I'll close this when
we work out the documentation issues. Thank you for your patience.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/distribution/issues/1371#issuecomment-173690939
.

I'll probably blog about how to set the registry up

I hope you're nice. ;)
Let's us know if you need anything else.

Closing now. Let me know if this needs reopening.


Adding entity_cids and entity_types to Sentence

LGTM!

Do CIDs need to be stored at the candidate level to handle cases such as compound entity mentions and to subsume ImplicitSpans?

@stephenbach So I also submitted a PR for storing them at the candidate level a few days ago- this PR is just to enable tagging entities as part of the preprocessing stage.  I.e. I want to be able to run all the PubMed entity parsers without having to create (and thus pre-specify) a Candidate set.
Any suggestions of how to make this distinction clearer though are welcome?

Ah, perfect! Thanks for the clarification!
On Mon, Nov 14, 2016 at 6:55 PM Alex Ratner<EMAIL_ADDRESS>wrote:

@stephenbach https://github.com/stephenbach So I also submitted a PR
for storing them at the candidate level a few days ago- this PR is just to
enable tagging entities as part of the preprocessing stage. I.e. I want to
be able to run all the PubMed entity parsers without having to create (and
thus pre-specify) a Candidate set.
Any suggestions of how to make this distinction clearer though are welcome?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HazyResearch/snorkel/pull/485#issuecomment-260533029,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA01sqJP0HM5G8nhNHOFl3pcyjzjQB0jks5q-R8JgaJpZM4KyD7I
.


Kinetix.Tools.Core + T4 and parameters singleton removal + .NET Core

Preparing groundwork for KleeGroup/kinetix-tools#9, KleeGroup/kinetix-tools#10 and KleeGroup/kinetix-tools#11
This is a PR because it's completely untested, though I am confident there won't be any regression 😃
I created Kinetix.Tools.Common where I put all parameter types (GeneratorParameters and co.), the Model namespace (i needed to use ModelProperty so I copied everything over), FileWriter in prevision of the TS gen migration, and every TS util we had across both generators.
While working on parameters, I removed the Singletons.GeneratorParameters and gave every class the parameters it needed to work instead. I realized we some of them were actually misplaced, so I moved them :

Kinetix from root to csharp
DefaultValuesFile, NoTableFile, HistoriqueCreationFile from root to ssdt

I removed the T4 files and kept the generated C#, that I cleaned up by removing all the useless things that were generated. It is perfectly usable as it is, but it would be better if we could build in the future something like CSharpWriter on top of it.
Again, a lot of stuff moved around, because that's my favorite thing to do 😛
Please update your config file and test the PR to confirm there's no regression on your side (well, you could wait for me to test it first on Monday).
(Also, I might have changed the output folder of the generators to remove the framework prefix, so we can more easily test between full .NET and Core in the future.)

I checked on my project and it works well.
I added a new feature to use the default values from the OOM to generate the adequate C# for EF and the default value in the generated SQL. I think it should work with SSDT too, with the default value file overriding the default values set in the OOM.
I also removed the MSBuild dependency for SSDT as discussed (since wildcards work!)
Finally, I rebased (painfully) on master, so please check that everything still works fine for you, and you can merge.

I managed to get both generators work on .NET Core with minimal changes.
You'll need the 2.1 SDK installed (it doesn't come with VS yet) and to change your generators calls from %modgen%.exe to dotnet %modgen%.dll.

So, I tried It.
Class generator
Almost ok, it changed the content of my sqlproj file by what seems to be the content of a list factory sql file
----
---- ATTENTION CE FICHIER EST GENERE AUTOMATIQUEMENT (7667C01C58993CD698162FA04A2840CE180E56F7) !
----

-- ===========================================================================================
--   Description		:	Insertion des valeurs de listes statiques.
-- ===========================================================================================

Service generator
It doesn't run:

The ModGen issue is weird and I'd appreciate if you could take a look at what's happening (since you have a SSDT project on hand). It should be pretty trivial to find the problem and fix it.
And I'm pretty sure the ServiceGen issue comes from the fact that your project is a classic ASP.NET project that the .NET Core SDK cannot open... Which is probably (one of the reasons) why the classic MSBuildWorkspace isn't supported on Core. I'm gonna look into it when I have the time to try and find a solution for this (which doesn't force us to go back to full .NET)

Okay I found why it changed the .sqlproj file
https://github.com/get-focus/kinetix-tools/blob/preemptive-refactor/Kinetix.ClassGenerator/SsdtSchemaGenerator/SqlScriptEngine.cs#L100

The sqlproj problem should be fixed now, and I added the option to multitarget net471 and netcoreapp2.1 because using MSBuildWorkspace is mandatory to handle non-Core projects and isn't available on Core.
I also noticed that Buildalyzer wasn't properly emulating MSBuildWorkspace on Core because it didn't fill the Folders property on each Document. So I added a workaround for it (specific to Core) and fixed the code so that the behavior (and the output) is identical between both versions. Meaning I can use the net471 version to generate for a Core project (netcoreapp2.1 will be mandatory when we'll want to package it as a tool but we're not here yet).
Please let me know if it works fine for you, so that we can merge it and go forward with new changes.


Naming check for StaticMember StaticMethod

Hello and thank you for the patch.
LLVM does not use github for its development process, but Phabricator. You can create a new Patch there, it will then be reviewed and commited to trunk when accepted.
You will be of course mentioned in the patch!
If you have further question, just ask them :)

What I forgot:
Please write the title in the following form: "[clang-tidy] Patch...", so the right people get automatically notified.

Thank you!


New: space-infix-ops rule (#156)

more-or-less based on the core rule, handling only the typescript-specific part.

i'm closing this as eslint/eslint#10935 resolved the issue


New Test scripts to validate dashboard page title_73199

ADO-79152
Description

Added test case to validate the Dashboard page heading in English
Added test case to validate the Dashboard page heading in French

What to test for/How to test
Dashboard Page heading in French and English
Additional Notes

I see nothing wrong here. Just a question, why do we use two files to return simple cy.get() objects? Just curious. :)


issue138-bufix-numberunitrewriter #138

Resolves https://github.com/querqy/querqy/issues/138

Thank you  @JohannesDaniel

Thank you  @JohannesDaniel


debug expression operator

I'd like to be able to debug what an object looks like in a vega expression.
Let's say I'm trying to write an expression for a formula transform. I want to know what properties the datum has and what their types are.
{
  "type": "formula",
  "as": "height",
  "expr": "(datum[\"???\"] + 1) * 21"
}

Maybe I can write something like
{
  "type": "formula",
  "as": "height",
  "expr": "debug(datum)"
}

and would either get a JSON representation of the object or the object gets logged in the console (or both so I can see for example objects in axis labels).

I imagine this being a pure "side-effect" method. The return value would be identical to the input value, but internally a debug message would be generated using the existing dataflow/view logger instance. Sound good?
By default, I think one would need to have the debug logging level set (e.g., vega.Debug) for messages to actually be generated and printed. Among other things, this would allow debug messages to be optionally included but "turned off" to improve performance and squash output. The drawback is that some folks might be confused when their debug calls have no apparent effect (likely to happen since the default logging level is for Warn messages only). Please respond with any opinions on this question...

Another related question:
Since the goal is not to derive a new field, I'm wondering why it should be an expression in a formula transform rather than its own "debug" transform or something similar?

Sorry @kanitw, I don't think I understand your question. For general operators, simply calling view.logLevel(vega.Debug) will result in rich console debugging output, including inspectable state for all operators and pulses that execute. So I'm not sure what a Debug transform would add to this.
OTOH, I can totally appreciate the need for a debug method in the expression language. There are plenty of times I personally would have found it useful. My suggestion above is also flexible (e.g., one could call debug in multiple places within the same expression, no problem). The debug method probably needs to accept at least two parameters: the value to log, and an optional additional message to include to help disambiguate multiple debug outputs.
For me, the main open question is what the appropriate log-level should be for this. The vega.Debug level seems the most obvious, but might be missed by some users and could also lead to expression debug messages getting drowned out among all the Operator-level debug outputs. So I'm trying to determine if either Warn or Info are more sensible default logging levels for expression debug statements. One could argue that if one explicitly invokes debug, one wants to see the message by default, and one could always use log level None to suppress all output.

Couple of alternatives I see:

Separate functions for the each level, which would only log the message
if the threshold is met.
A property within the config block to control log level; has the added
benefit of only logging output from one Vega visualization on a page that
contains several.

On Tue, Nov 29, 2016 at 2:20 PM Jeffrey Heer<EMAIL_ADDRESS>wrote:

Sorry @kanitw https://github.com/kanitw, I don't think I understand
your question. For general operators, simply calling
view.logLevel(vega.Debug) will result in rich console debugging output,
including inspectable state for all operators and pulses that execute. So
I'm not sure what a Debug transform would add to this.
OTOH, I can totally appreciate the need for a debug method in the
expression language. There are plenty of times I personally would have
found it useful. My suggestion above is also flexible (e.g., one could call
debug in multiple places within the same expression, no problem). The
debug method probably needs to accept at least two parameters: the value
to log, and an optional additional message to include to help disambiguate
multiple debug outputs.
For me, the main open question is what the appropriate log-level should be
for this. The vega.Debug level seems the most obvious, but might be
missed by some users and could also lead to expression debug messages
getting drowned out among all the Operator-level debug outputs. So I'm
trying to determine if either Warn or Info are more sensible default
logging levels for expression debug statements. One could argue that if one
explicitly invokes debug, one wants to see the message by default, and one
could always use log level None to suppress all output.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/vega/vega-parser/issues/3#issuecomment-263718591, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAClFrSKzaYwiWRxwTCOF3tJb9PArrjwks5rDKUVgaJpZM4K_XFJ
.

--
-Arvind
Arvind Satyanarayan http://arvindsatya.com
Sent from my iPhone

The debug function could take the log level as another optional log level parameter that defaults to Info, Debug or Warn. I guess this is similar to @arvind's suggestion to have separate debug, info, and warn methods.

I like @arvind's suggestion and have added debug, info and warn functions in 045abbcb728f3415ae34600459ed12a9528daf0a. This provides the most flexibility for both debugging and logging. Thanks!

I just used warn and immediately found out what the right property name is. :-D


shellcheck fixes for helmdiff.sh

Description
Shell checks were ignored for file: dev-tools/helmdiff.sh, this PR fixes the warnings provided by shellcheck (#3544 )
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Above doesn't apply, logic of script isn't changed
Testing Performed
executed command "make shell-style"

/ok-to-test


Add documentation for suspend-resume.

Adding documentation for my suspend-resume feature for Durable Functions.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This bit looks good to me, @Julio-Arroyo.
However, it seems we're missing the corresponding "Resume" component, right? Please add that at your earliest convience.
I think there's a few other places that may need an explanation. For instance, I think some docs talk about all the valid states that orchestrators can be, and that may need some updating too.
Let's aim to find these pieces. Perhaps @lilyjma can help us do an exhaustive job in here.

For instance, I see we talk about the status'es here: https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-instance-management?tabs=csharp#query-instances
So that would be good to update. There's a few other places too. I'll look to find them, but you may be able to find them as well with a CTRL+F in this directory for "Terminate"

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This bit looks good to me, @Julio-Arroyo. However, it seems we're missing the corresponding "Resume" component, right? Please add that at your earliest convenience.
I think there's a few other places that may need an explanation. For instance, I think some docs talk about all the valid states that orchestrators can be, and that may need some updating too.
Let's aim to find all those places. Perhaps @lilyjma can help us do an exhaustive job in here.

I added the resume HTTP API documentation, and also for suspend-resume in the "Instance Management" section.

@cgillum
After this PR is taken out of draft mode and ready to go, can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@Julio-Arroyo : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This is looking almost ready to me, Julio. Good job on finding the other locations where runtimeStatus is referenced. Let me do a quick manual check on my end that you didn't miss any other places, but so far so good.
My remaining requests are: (1) to reach consensus on the HTTP code for suspending a suspended orchestrator. In my opinion HTTP 500 isn't quite right. I'm ok with HTTP 202 with a special message saying that it will be ignored, though first I'd like us to triple check what Terminate does when terminating an already finished orchestrator.
(2) Might be good for you to check in with our PM in case she has any further documentation requests.

Regarding your request (1): I checked what Terminate does. It returns the HTTP 410 (Gone) code. I don't think we should return that code if we try to suspend a suspended orchestration since it wouldn't be completed or failed but rather may be resumed later.
I will reach out to our PM.

@davidmrdavid @Julio-Arroyo Any chance we can move this to the azure-docs-pr repo? This is where internal contributors are supposed to contribute docs, and it has a lot of extra features that we'll want, like published previews, automated grammar and style checks, etc. I can provide you with some instructions offline if that would help.

Now that the PR has been moved: @Julio-Arroyo, could you please close this one? Thanks!

Moved this pull request to: https://github.com/MicrosoftDocs/azure-docs-pr/pull/208725


Can I rename prefix ?

Hi !
I have output like that window["html"]["history"] , can I customize it ? for example this["project"]["history"] ?

And can I convert code into 1 line ?


Add fake 64_json string to test image response

What:

[x] Bug Fix
[ ] New Feature

Description:
According to issue #340 it is not possible to receive a fake b64_json string when testing the image response.
The PR solves this issue.
Related:
Issue #340

Thanks @JanSuthacheeva

Although you merged into main, I don't see the updated source code in the main branch @gehrisandro - Am I missing something here?

Even though you merged the PR, I don't see the updated source code in the main branch - Am I missing something here @gehrisandro?


Noticed the /me API get route in Auth seems to throw an error whenever I try to access...

https://github.com/2201gh-team-saturn/grace-shopper-main/blob/9c88f402307d8ccbc289056ce6a946f4074f6471/server/auth/index.js#L14-L33
This has also made me wonder if maybe we should be getting our carts through the UserId, as opposed to the cartID? Because no one else should be able to access your cart except you, but as it stands anyone can type in "http://localhost:8080/cart/2". I'm wondering if we need the User with the correct token to access the cart.

This is partially me not realizing that /me wouldn't populate API information, but this helped spawn a conversation about security that helped us secure our API routes


A11y_SQLAzureDataStudio_SQLServerBigDataCluster_Summary_ScreenReader:The name of the page is not announced.

Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11y_SQLAzureDataStudioBenchmark;#A11yMAS;#A11ySev1;#A11yTCS;#SQL Azure Data Studio;#Benchmark;#DesktopApp;#Win32;#JAWS;#MAS1.3.1;
Environment Details:
Application Name: Azure Data Studio
Version: 1.16.0-insider
OS: Windows_NT x64 10.0.18363
Additional Details:
Screen reader:JAWS
MAS References:MAS1.3.1
Repro Steps:

Launch Azure Data Studio.
Select the Connections icon (if not already selected) from left bar.
Click on the ellipses '...' and select "New Deployment".
Select "SQL Server Big Data Cluster" card under deployment options.
Select the version & checkbox.
Navigate till Selet button & hit enter.
Launch screen reader as JAWS
Select Configuration profile --> Update Azure settings --> Update Cluster settings --> Update Service settings & hit Next.

Actual:
When the page is loaded the "alert"  message is announced and the name of the screen in display is not announced.
Issue not  observed with NVDA
Expected:
The screen name in display should be announced.
User Impact:
Screen reader users will not know which page they have landed on.
Attachment link for Reference :
A11y_SQLAzureDataStudio_SQLServerBigDataCluster_Summary_ScreenReader9347.zip

dupe of #9348

As "SQL Server Big Data Cluster" feature has been removed
GithubTags:#Closed;

GitHubTags:#SQLADS-Win32-Feb2020;


Linker error: multiple definition of

We're evaluating NanoVG for our game's GUI and have run into a problem testing it that looks like it may be a bug. If the header <nanovg_gl.h> is included multiple times in the project (for example, two different .cpp files), the linker will gag at redefinitions of the nvg* GL functions:
src/main.o: In function `nvgCreateGL3':
nanovg_gl.h:1553: multiple definition of `nvgCreateGL3'
nanovg_gl.h:1553: first defined here
src/main.o: In function `nvgDeleteGL3':
nanovg_gl.h:1598: multiple definition of `nvgDeleteGL3'
nanovg_gl.h:1598: first defined here
src/main.o: In function `nvglCreateImageFromHandleGL3':
nanovg_gl.h:1611: multiple definition of `nvglCreateImageFromHandleGL3'
nanovg_gl.h:1611: first defined here
src/main.o: In function `nvglImageHandleGL3':
nanovg_gl.h:1635: multiple definition of `nvglImageHandleGL3'
nanovg_gl.h:1635: first defined here

Not sure what we're doing wrong, if we're doing anything wrong at all. Here's some background:

gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12)
GNU ld (GNU Binutils for Ubuntu) 2.27
NanoVG is included in the project by having built the original repo in the original NanoVG directory (premake4 and all) and then copying nanovg.a and its headers into our lib directory. NanoVG is then linked into our project using -lnanovg.
Our project uses a threaded build (make -j8) where .cpp files are built together to .o files in parallel before being linked in a final single stage.
The error does not occur if <nanovg_gl.h> is only included once, in one .cpp file, in the entire project.
The error can be supressed with the "-z muldefs" linker option, but we'd prefer not to use this.

You should define NANOVG_GL2_IMPLEMENTATION only in one file. it follows the stb style [1] one header lib idea.
[1] https://github.com/nothings/stb#why-single-file-headers

That fixes it! Thank you for your help.


TdApi.java - MessageChatDeleteHistory content missing

After compiled tdlib for java, the generated TdAPI.java doesn't contains MessageChatDeleteHistory class.
I tried to clear history of a chat in Telegram App and then call the function GetChatHistory that returns no messages, not even a message with content MessageChatDeleteHistory (that seems to exists in this repository) saying that history was cleared.
Is it a way to add this support by myself ?
Thanks for the help

Because there is no such an object and a message content in TDLib API.
MessageChatDeleteHistory is not a real message. It even not always means that the history was cleared. It is just a marker that the chat should be kept in the chat list. It is handled internally by TDLib and never treated as a real message. There is no way such a message can be received by an app from TDLib and there is no reason to return in to the app either.

ok, thanks for the answer.
It would have been interesting for a user to know that the history of a chat was cleared by himself or his correspodent and also when it was cleared...
For example, the correspondent go into the chat and see that there is no message anymore (indeed, the other user has cleared the history but he doesn't know it), he will maybe thinking that there is a bug in the app because all the messages of this chat disapears.
Is it a way to know this with TDLib ?

No, there is no way to know this with TDLib.
The history is often cleared without keeping a MessageChatDeleteHistory message with complete removal of the chat from the chat list, so there is no way to reliably get this information at all. Clients show "History was cleared" only in the chat list if there are no messages and a draft in the chat.

ok, thanks for all these information.
Regards


Deletes don't take effect until the app is relaunched.

As the title states the deleted rows can still be seen in the table until the app is restarted.
Noted on both the people & locations windows.

Solved: Oversight on my part. Func was defined but empty.
Closing but I will keep an eye to it


feat: add charm tracing integration

Description
We add charm tracing integration making it possible to send charm traces to Tempo and observe them in Grafana.
Usage
Deploy COS lite with Tempo
Create a model for COS
juju add-model cos
Deploy cos-lite
juju deploy cos-lite --trust
Deploy tempo and integrate it with grafana
juju deploy tempo-k8s tempo
juju integrate grafana:grafana-source tempo:grafana-source
Deploy Manual TLS Certificates
Create a new model
juju add-model dev
Deploy Manual Signed Certificates
juju deploy manual-tls-certificates
Integrate Manual TLS Certificates with Tempo
From the COS model, create an offer:
juju offer cos.tempo:tracing
From the dev model, consume the offer:
juju consume obs.tempo
Integrate Manual TLS Certificates with Tempo
juju integrate manual-tls-certificates tempo
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

Closing as it is a duplicate of #210


Fix CAP code collection parsing

According to CAP, the 'code' field should be a collection, not a single field. I've changed it to a collection and implemented parsing of it.

Hi Damian, good catch & thanks for the PR!


transfers: read user Gateway for FileHeader

Codecov Report

Merging #463 into master will decrease coverage by 1.34%.
The diff coverage is 48.64%.

@@            Coverage Diff             @@
##           master     #463      +/-   ##
==========================================
- Coverage   58.66%   57.31%   -1.35%
==========================================
  Files         110      111       +1
  Lines        8293     6614    -1679
==========================================
- Hits         4865     3791    -1074
+ Misses       2710     2138     -572
+ Partials      718      685      -33

Impacted Files
Coverage Δ

cmd/server/main.go
19.48% <0.00%> (+2.55%)
:arrow_up:

internal/gateways/mock_repository.go
0.00% <0.00%> (ø)

internal/transfers/transfers.go
59.09% <33.33%> (+1.22%)
:arrow_up:

...nal/depository/verification/microdeposit/router.go
63.88% <66.66%> (+0.81%)
:arrow_up:

internal/gateways/storage.go
65.21% <83.33%> (+4.77%)
:arrow_up:

internal/gateways/http.go
67.39% <100.00%> (+4.89%)
:arrow_up:

internal/model/gateways.go
100.00% <100.00%> (ø)

internal/remoteach/files.go
62.31% <100.00%> (+2.07%)
:arrow_up:

internal/customers/client.go
11.42% <0.00%> (-56.55%)
:arrow_down:

internal/accounts/client.go
9.09% <0.00%> (-54.95%)
:arrow_down:

... and 101 more

Continue to review full report at Codecov.

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


NotFoundLookupError: cast(tensorflow.python.framework.dtypes.DType, numpy.ndarray) could not be resolved.

With the new version from yesterday, my code throws the following exception in MaternKarhunenLoeveKernel._spectrum():
NotFoundLookupError: `cast(tensorflow.python.framework.dtypes.DType, numpy.ndarray)` could not be resolved.

I'm using the code from the mesh example. With the old version (do not know the version) my code still worked. So I'm assuming that there might be a bug in the new framework code?
Stack trace, or error message
---------------------------------------------------------------------------
NotFoundLookupError                       Traceback (most recent call last)
Cell In[18], line 27
     20 # kernel.nu.assign(np.array(np.inf))
     21 # kernel.nu.assign(3/2.0)
     22 # kernel.lengthscale.assign(0.5)
     24 model = gpflow.models.GPR(
     25     (X, Y), kernel, mean_function=DefaultFloatZeroMeanFunction(), noise_variance=1.1e-6
     26 )
---> 27 print("LML", model.log_marginal_likelihood().numpy())
     29 X_test = np.arange(mesh.num_vertices).reshape(-1, 1)
     31 mean_prediction, variance_prediction = model.predict_f(X_test)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/check_shapes/integration/tf.py:76, in install_tf_integration.<locals>.TfWrapperPostProcessor.on_wrap.<locals>.wrapped_method(self, *args, **kwargs)
     75 def wrapped_method(self: Any, *args: Any, **kwargs: Any) -> Any:
---> 76     return wrapped_function(self, *args, **kwargs)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/check_shapes/decorator.py:192, in check_shapes.<locals>._check_shapes.<locals>.wrapped_function(*args, **kwargs)
    190 with set_shape_checker(checker):
    191     try:
--> 192         result = func(*args, **kwargs)
    193     except Exception:
    194         drop_stack_frame()

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/gpflow/models/gpr.py:100, in GPR_deprecated.log_marginal_likelihood(self)
     92 r"""
     93 Computes the log marginal likelihood.
     94
   (...)
     97
     98 """
     99 X, Y = self.data
--> 100 K = self.kernel(X)
    101 ks = add_likelihood_noise_cov(K, self.likelihood, X)
    102 L = tf.linalg.cholesky(ks)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/check_shapes/integration/tf.py:76, in install_tf_integration.<locals>.TfWrapperPostProcessor.on_wrap.<locals>.wrapped_method(self, *args, **kwargs)
     75 def wrapped_method(self: Any, *args: Any, **kwargs: Any) -> Any:
---> 76     return wrapped_function(self, *args, **kwargs)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/check_shapes/decorator.py:192, in check_shapes.<locals>._check_shapes.<locals>.wrapped_function(*args, **kwargs)
    190 with set_shape_checker(checker):
    191     try:
--> 192         result = func(*args, **kwargs)
    193     except Exception:
    194         drop_stack_frame()

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/gpflow/kernels/base.py:214, in Kernel.__call__(self, X, X2, full_cov, presliced)
    211     return self.K_diag(X)
    213 else:
--> 214     return self.K(X, X2)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/geometric_kernels/frontends/gpflow.py:121, in GPflowGeometricKernel.K(self, X, X2)
    119 variance = tf.convert_to_tensor(self.variance)
    120 params = dict(lengthscale=lengthscale, nu=nu)
--> 121 return variance * self.base_kernel.K(params, X, X2)

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/geometric_kernels/kernels/karhunen_loeve.py:199, in MaternKarhunenLoeveKernel.K(self, params, X, X2, **kwargs)
    196 assert "nu" in params
    197 assert params["nu"].shape == (1,)
--> 199 weights = B.cast(B.dtype(params["nu"]), self.eigenvalues(params))  # [L, 1]
    200 Phi = self.eigenfunctions
    201 K = Phi.weighted_outerproduct(weights, X, X2, **params)  # [N, N2]

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/geometric_kernels/kernels/karhunen_loeve.py:171, in MaternKarhunenLoeveKernel.eigenvalues(self, params, normalize)
    168 assert "nu" in params
    169 assert params["nu"].shape == (1,)
--> 171 spectral_values = self._spectrum(
    172     self.eigenvalues_laplacian,
    173     nu=params["nu"],
    174     lengthscale=params["lengthscale"],
    175 )
    176 normalize = normalize or (normalize is None and self.normalize)
    177 if normalize:

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/geometric_kernels/kernels/karhunen_loeve.py:117, in MaternKarhunenLoeveKernel._spectrum(self, s, nu, lengthscale)
    114 assert nu.shape == (1,)
    116 # Note: 1.0 in safe_nu can be replaced by any finite positive value
--> 117 safe_nu = B.where(nu == np.inf, B.cast(B.dtype(lengthscale), np.r_[1.0]), nu)
    119 # for nu == np.inf
    120 spectral_values_nu_infinite = B.exp(
    121     -(lengthscale**2) / 2.0 * B.cast(B.dtype(lengthscale), s)
    122 )

    [... skipping hidden 1 frame]

File ~/Downloads/geoflow/.venv/lib64/python3.11/site-packages/lab/util.py:214, in abstract.<locals>.decorator.<locals>.wrapper(*args, **kw_args)
    212 if types_before == types_after:
    213     signature = plum.signature.Signature(*types_after)
--> 214     raise plum.NotFoundLookupError(f.__name__, signature, [])
    216 # Retry call.
    217 return getattr(B, f.__name__)(*args, **kw_args)

NotFoundLookupError: `cast(tensorflow.python.framework.dtypes.DType, numpy.ndarray)` could not be resolved.

Expected behavior
No error at all.
System information

GeometricKernels version 0.2
TensorFlow version 2.16.1
Python version 3.11.8
Operating system OpenSUSE Tumbleweed

Hey @MBulli, thanks for reporting this! I think I know what the problem is. I will look into it later today or tomorrow and get back to you.

Could you please post the output of
pip show backends

Sure!
Name: backends
Version: 1.6.3
Summary: A generic interface for linear algebra backends
Home-page: https://github.com/wesselb/lab
Author: Wessel Bruinsma
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/markus/Downloads/geoflow/.venv/lib64/python3.11/site-packages
Requires: fdm, numpy, opt-einsum, plum-dispatch, scipy
Required-by: geometric_kernels

btw is B.dtype(lengthscale) correct in the faulty line? Shouldn't it be B.dtype(nu)?

Hi @MBulli, could you please provide a minimal reproducible example? It would help us debug the problem.

btw is B.dtype(lengthscale) correct in the faulty line? Shouldn't it be B.dtype(nu)?

Yes, we assume that params["nu"] and params["lengthscale"] dtypes are the same but also that lengthscale's dtype takes precedence if they are not.
I'm having trouble reproducing this, could you please post the full source code that leads to it?
BTW, did you do import geometric_kernels.tensorflow right after import geometric_kernels?


Off-topic - Aurelia

Hey Chris.
Hope all is well with you. (And, sorry this doesn't really belong here, as I didn't know how to contact you through other channels.)
I just ran into a thread in the Aurelia Github repo which you started and said, wow, what a coincidence. I've been evaluating Aurelia (at a distance, because I am even less of a front-end dev), but have been seriously thinking of making Aurelia our core front-end framework too. I noticed you mentioned you were also evaluating it.
How have you found it? Are you completely convinced it is a good framework? Are you also convinced of its modularity being an core and big advantage?
I personally like how it pushes the front-end framework envelope and I've only read good things about it too. I am very interested in your views of Aurelia.
Scott

I really don't like front-end development. It's just not my cup of tea. So, I've looked at the big ones (angular, ember, jquery, polymer, etc.) and have landed on Aurelia for a couple reasons. First, it uses next-generation standards so its modules and such are going to be more future proof. Ember and Angular are also working in this direction. It's also developed by a solid team with a lot of js experience and its well documented.
But for me, the kicker was its learning curve. I just found it an easier transition for a backend guy like me. I didn't have to worry about the DOM or async stuff as much. It is modular, which I get because of composer and pip. It just fit for my coding style, which meant I could use it without having to get deeper into js. Also, it seemed easier (and has been so far) to use with different CSS frameworks. I like Foundation 5 for the same reasons, and they have played well together for me.
I haven't used it in production, and haven't really even dug into it as I am far away from front end stuff. But I'm convinced its the way to go for me, at least.

Cool. I like Aurelia too. I haven't even worked with it in depth, but I can see the things you noted even from "the outside". This video is also pretty cool. https://channel9.msdn.com/Events/Seth-on-the-Road/DevIntersection-2015/Rob-Eisenberg-on-Aurelia
Scott


Fixes on absolute time sensors

Hi @astrandb,
I have addressed the problem related to the issue https://github.com/astrandb/miele/issues/288, by forcing none value on started time abs and elapsed time when appliance is off.
I also refactored the code related to time sensor to be more readable and I have fixed two other issues:

sometimes absolute time sensors keep updating their value with a string that is +/-1 minute because it is computed starting from now +/- the relative time in minutes obtained from API --> I have stripped out from now the seconds and microseconds, so it should now be more precise
finish time sensor did not take into account time until delayed start --> I have added the time to start the appliance in order to have correct finish time

I'm testing this branch in these days, so I will write here when this branch is safe to be merged.
Thanks
Andrea

Hi @astrandb, I think it can be merged.


Calculate distance values based on Proximity-output from this package

Dear all,
in addition to the metrics provided by this package (ECI,PCI, Outlook gain and outlook index) I would like to calculate the distance value for each product-year-country instance. Those familiar with economic complexity know the definition:
Distance (value between 0 and 1, for product p to country c): the sum of the proximities connecting a new good p to all the products that country c is not currently exporting. We normalize distance by dividing it by the sum of proximities between all products and product p. In other words, distance is the weighted proportion of products connected to good p that country c is not exporting.
I am able to transform the product-proximity matrix resulting from the package into a 3-column dataframe (Hs-code p1, hs-code p2, proxmity) and I also have created a dummy variable 0 and 1 based on whether the country has and RCA in this product. But I am struggling now to code a command/function to calculate the distance.
I attached my data again (its for the year 1995, but the logic is the same) and the code that I started for this calculation
How to calculate distance value.zip

@pachamaltese is there maybe a specific spot in the source code where I can find this? Because I think in order to calculate the opportunity gain index in your package you already need to make use of the distance values as an intermediary outcome?

Hi
Thanks. Yes, I 'll need to modify the code. Will you be available to review
it?
On Thu, Feb 11, 2021, 7:15 AM fabianscheifele<EMAIL_ADDRESS>wrote:

@pachamaltese https://github.com/pachamaltese is there maybe a specific
spot in the source code where I can find this? Because I think in order to
calculate the opportunity gain index in your package you already need to
make use of the distance values as an intermediary outcome?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pachamaltese/economiccomplexity/issues/17#issuecomment-777337392,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACM7UOILCR2IUSQAA67BF4DS6OU5JANCNFSM4XORQSDA
.

So you are going to create a new command that calculates the distance value?
I am not yet a very experienced R user nor a programmer. Hence, I think I will not be able to follow the code fully, but I know the concept of the distance value and can check whether the code calculates what it is supposed to...

@fabianscheifele "I know the concept of the distance value and can check whether the code calculates what it is supposed to." this is exactly what I need to double check my results

@fabianscheifele Hi! I've separated the outlook from the distance function. You can install the package with this new change by running remotes::install_github("pachamaltese/economiccomplexity"). If everything makes sense, please let me know to increase the version number and send the new version to CRAN.

@pachamaltese I checked the function with the attached dataset (HS92 tradedata from oec website for the year 2017) and I have the following observations:
There very minimal differences between the value calculated by the command and my manual re-calculation (based on the proximity matrix created by the proximity command):
Country | Product | Value calculated   by command | Manually calculated
Argentina | 10111 | 0.8514521 | 0.85309528
Armenia | 10111 | 0.943737 | 0.943629
Albania | 10111 | 0.929481 | 0.9293449
Albania | 10410 | 0.8495048 | 0.8491
These differences may be due to rounding of number in intermediary calculation steps. The command appears to be working fine and returns the distance value for all product-country combinations previously identified by the balassa_index command and by the product proximity command (hence all products and countries with at least one positive export value recorded in the database that you are using. In case you have a continous database with the same product codes for multiple year and some of those product codes do not in a particular year (but maybe in a previous or a later year), they will be filtered out by the balassa command, when you calculate it for this particular year. Probably to make the matrix more lean
distance value check.zip
).
I highly appreciate this additional functionality because it allow you now to calculate all key complexity metrics used in the Atlas.

@fabianscheifele Thanks a lot! Well, your function is quite long!!
It might be rounding since I'm using matrices. You can try tradestatistics.io, it has a quite decent API and there's https://github.com/rpensci/tradestatiistics to use that API from R, it shall ease data extraction a lot.
When I have completely checked your manual calculation, I shall increase the version number and send to CRAN.

@fabianscheifele there are a few things I don't get from your script. For example, where does all_comb17 come from?

@fabianscheifele Hi! After reading the Atlas again, the equation

Can be correctly expressed as a matrix operation with this line of code
tcrossprod(1 - balassa_index, proximity_product / rowSums(proximity_product))

So, the distance function is correct, and the difference is because of rounding (your codes mixes data.frame, tibble and data.table)

okay, yes this makes sense. the rowSums is basically summing up all the proximities of product p, while the (1-balassa index, proximity-product) is only summing up those instances in matrix where Balassa Index =0.


  If you then select a child node at the same level but with a different parent, both child nodes get highlighted.  Only the one selected should be highlighted.

Label ID's must be unique.


coreman000

coreman000 ID3 challenge

Marking closed as valid submissions are in another PR.

Marking closed as valid submissions are in another PR.


Don't work on android 12L

Can confirm, Pixel Launcher crashes and won't even let you use system gestures.

Please check this on this beta build.
https://t.me/pixelifysupport/16388

Please check this on this beta build.
https://t.me/pixelifysupport/16388

Thanks.
The build works but the gboard is the old theme.
Screenshot_20220313-093440_GitHub.png

Please check this on this beta build.
https://t.me/pixelifysupport/16388

Thanks


[agent] allow nested, exportable components

What does this PR do?

allow exporting nested components
add docker manager component
export host in docker manager and agent component
export docker manager in docker agent component

Which scenarios this will impact?
vm, docker, kind
Motivation
We want to have fully autonomous components, that exporting anything they need to setup a client. This changes are then handled by this PR
Additional Notes

/merge


You should prevent Kata names that resemble to some existing path [BUG]

You can take this Kata as an example, you will never be able to get to it.

Duplicate of #1086


Data fetching

Closes: #80

Where are the new changes?

Where are the new changes? @MahtaMirzaei

Wasn't pushed completly last time.


OnNotificationPressed not activating due to error in example code?

After much experimenting, I've got everything running but couldn't get OnNotificationPressed or onNotificationButtonPressed to work reliably.
Turns out the issue was that the sample code (which I was using) for onRepeatEvent was causing this error at runtime:
E/flutter (15661): [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: Invalid argument: is a regular instance reachable via : Instance of 'DateTime'
E/flutter (15661): #0      _SendPort._sendInternal (dart:isolate-patch/isolate_patch.dart:250:43)
E/flutter (15661): #1      _SendPort.send (dart:isolate-patch/isolate_patch.dart:231:5)
E/flutter (15661): #2      FirstTaskHandler.onRepeatEvent (package:flutter_application_1/widgets/test_page.dart:39:15)
E/flutter (15661): #3      FlutterForegroundTask.setTaskHandler.<anonymous closure> (package:flutter_foreground_task/flutter_foreground_task.dart:269:19)

I haven't investigated the error too much and this could be the side effect of something else, but thought I would post it here in case anyone else runs into this (everything running but the events not firing). The error text only shows up when "continuing" the debugger (as it seems to disconnect when the application loses focus).
I just commented out that line (the .send() call) and everything works perfectly:
  // Called every [interval] milliseconds in [ForegroundTaskOptions].
  @override
  void onRepeatEvent(DateTime timestamp, SendPort? sendPort) async {
    // Send data to the main isolate.
    // sendPort?.send(timestamp);
  }

Again, this might be my fault or due to some misconfiguration but I would be curious if this makes sense for someone out there, or at least can be helpful.

SendPort doesn't seem to allow sending DateTime in release mode.
Updated readme on how to send DateTime.
Thank you for reporting the issue.


"Git changes not show in the file explorer" It is still a BUG

Hi, as I cannot reply to the issues: https://github.com/microsoft/vscode/issues/89104, https://github.com/microsoft/vscode/issues/89373, https://github.com/microsoft/vscode/issues/89143, https://github.com/microsoft/vscode/issues/90774 (all these issues are locked), I want to ask are there any workaround to fix these issues now? It seems downgrading git is not a feasible method. I tried many methods mentioned in these threads. And the price is I lost the code that cost me 3 hours to implement.
Could you please fix this issue? For me, the issue happens on the head node of a cluster when opening the project on the head node remotely.

@lszomoru  Hi, the current vs-code version is
Version: 1.64.0 (Universal)
Commit: 5554b12acf27056905806867f251c859323ff7e9
Date: 2022-02-03T04:20:17.224Z (1 mo ago)
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 21.4.0

and the git version of the remote machine is git version 2.34.1.
The issue happens when I open a remote project on my local machine.
I guess I am using the Remote - SSH extension. Hope someone can fix this issue.

@GoingMyWay, would you be able to create a screen recording illustrating the problem.
That would help significantly with the investigation. Thank you very much!

@lszomoru

Hi, as shown in the figure, I clone the https://github.com/microsoft/vscode on the remote machine. I connect the remote machine and open this repo on my local machine. I made a change in the file, but the git does not show the change in the file explorer bar.
However, I cloned the repo on my local machine and opened the repo locally. It can show the changes.

This issue happens on opening a repo remotely on a head node of a cluster. You can easily reproduce this problem by connecting any supercomputers' head nodes or any clusters' head nodes.
I hope this issue can be resolved. You can find the same problems in other issues I mentioned above.

@lszomoru
Hi, as shown in the figure, I clone the https://github.com/microsoft/vscode on the remote machine. I connect the remote machine and open this repo on my local machine. I made a change in the file, but the git does not show the change in the file explorer bar.
However, I cloned the repo on my local machine and opened the repo locally. It can show the changes.

This issue happens on opening a repo remotely on a head node of a cluster. You can easily reproduce this problem by connecting any supercomputers' head nodes or any clusters' head nodes.
I hope this issue can be resolved. You can find the same problems in other issues I mentioned above.

@lszomoru Hi, anything I can do for you to debug the issue?

@GoingMyWay, thank you very much for sharing the additional information. VS Code is using file system events to refresh various UI elements in the source control viewlet as well as the editor (ex: diff decorators shown in the editor gutter). Could you please implement the following steps both when opening the folder locally as well as on the remote:

Open the folder/workspace in VS Code
Enable file system logging as described in this wiki.
Use the Git: Set Git Log Level... command and set the log level to Trace
Make a change to a file and save it.
Share the file system watcher logs and the contents of the git output that you can access using the Git: Show Git Output command.

@GoingMyWay, thank you very much for sharing the additional information. VS Code is using file system events to refresh various UI elements in the source control viewlet as well as the editor (ex: diff decorators shown in the editor gutter). Could you please implement the following steps both when opening the folder locally as well as on the remote:

Open the folder/workspace in VS Code
Enable file system logging as described in this wiki.
Use the Git: Set Git Log Level... command and set the log level to Trace
Make a change to a file and save it.
Share the file system watcher logs and the contents of the git output that you can access using the Git: Show Git Output command.

@lszomoru Hi, the following is the output of step 5.
[2022-04-12T00:42:04.422Z] Validating found git in: git
[2022-04-12T00:42:04.481Z] Using git 2.34.1 from git
[2022-04-12T00:42:05.103Z] > git rev-parse --git-dir [340ms]
[2022-04-12T00:42:05.110Z] Open repository: /mnt/home/qiuwei/Projects/sail/game-ai/sail_marl
[2022-04-12T00:42:29.482Z] > git symbolic-ref --short HEAD [31ms]
[2022-04-12T00:42:29.536Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/main refs/remotes/main [42ms]
[2022-04-12T00:42:29.597Z] > git remote --verbose [41ms]
[2022-04-12T00:42:29.614Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [66ms]
[2022-04-12T00:42:29.646Z] > git config --get commit.template [17ms]
[2022-04-12T00:42:30.200Z] > git rev-parse --git-dir [28ms]
[2022-04-12T00:42:30.204Z] Open repository: /mnt/home/qiuwei/Projects/sail/game-ai/sail_marl/third_party/meltingpot
[2022-04-12T00:42:30.306Z] > git rev-parse --git-dir [35ms]
[2022-04-12T00:42:30.309Z] Open repository: /mnt/home/qiuwei/Projects/sail/game-ai/sail_marl/third_party/ray
[2022-04-12T00:42:30.445Z] > git rev-parse --git-dir [38ms]
[2022-04-12T00:42:30.447Z] Open repository: /mnt/home/qiuwei/Projects/sail/game-ai/sail_marl/third_party/lb-foraging
[2022-04-12T00:42:30.619Z] > git symbolic-ref --short HEAD [41ms]
[2022-04-12T00:42:30.757Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/master refs/remotes/master [129ms]
[2022-04-12T00:42:30.888Z] > git remote --verbose [113ms]
[2022-04-12T00:42:30.993Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [226ms]
[2022-04-12T00:42:31.145Z] > git config --get commit.template [139ms]
[2022-04-12T00:42:33.881Z] > git symbolic-ref --short HEAD [28ms]
[2022-04-12T00:42:33.881Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T00:42:33.919Z] > git rev-parse HEAD [27ms]
[2022-04-12T00:42:33.978Z] > git remote --verbose [43ms]
[2022-04-12T00:42:33.983Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [55ms]
[2022-04-12T00:42:34.019Z] > git config --get commit.template [22ms]
[2022-04-12T00:42:39.135Z] > git symbolic-ref --short HEAD [62ms]
[2022-04-12T00:42:39.135Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T00:42:39.168Z] > git rev-parse HEAD [26ms]
[2022-04-12T00:42:39.213Z] > git remote --verbose [31ms]
[2022-04-12T00:42:39.361Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [186ms]
[2022-04-12T00:42:39.393Z] > git config --get commit.template [15ms]
[2022-04-12T03:18:53.031Z] > git fetch [899ms]
[2022-04-12T03:18:53.463Z] > git fetch [1307ms]
[2022-04-12T03:18:53.595Z] > git fetch [1451ms]
[2022-04-12T03:18:53.891Z] > git symbolic-ref --short HEAD [62ms]
[2022-04-12T03:18:53.962Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/master refs/remotes/master [60ms]
[2022-04-12T03:18:54.046Z] > git remote --verbose [63ms]
[2022-04-12T03:18:54.062Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [89ms]
[2022-04-12T03:18:54.080Z] > git fetch [1958ms]
[2022-04-12T03:18:54.080Z] From git.insea.io:sail/gameai/sail_marl
   20a4aea..fc7fc7d  main       -> origin/main
[2022-04-12T03:18:54.105Z] > git config --get commit.template [26ms]
[2022-04-12T03:18:58.955Z] > git symbolic-ref --short HEAD [47ms]
[2022-04-12T03:18:58.955Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:18:58.992Z] > git rev-parse HEAD [25ms]
[2022-04-12T03:18:59.095Z] > git remote --verbose [87ms]
[2022-04-12T03:18:59.104Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [103ms]
[2022-04-12T03:18:59.175Z] > git config --get commit.template [59ms]
[2022-04-12T03:19:09.409Z] > git symbolic-ref --short HEAD [22ms]
[2022-04-12T03:19:09.410Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:19:09.445Z] > git rev-parse HEAD [21ms]
[2022-04-12T03:19:09.494Z] > git remote --verbose [28ms]
[2022-04-12T03:19:09.498Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [42ms]
[2022-04-12T03:19:09.529Z] > git config --get commit.template [16ms]
[2022-04-12T03:19:09.793Z] > git symbolic-ref --short HEAD [21ms]
[2022-04-12T03:19:09.842Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/main refs/remotes/main [41ms]
[2022-04-12T03:19:09.886Z] > git remote --verbose [29ms]
[2022-04-12T03:19:09.896Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [47ms]
[2022-04-12T03:19:09.920Z] > git config --get commit.template [11ms]
[2022-04-12T03:23:44.870Z] > git fetch [1071ms]
[2022-04-12T03:23:45.036Z] > git fetch [1249ms]
[2022-04-12T03:23:45.083Z] > git fetch [1260ms]
[2022-04-12T03:23:45.104Z] > git fetch [1293ms]
[2022-04-12T03:23:45.267Z] > git symbolic-ref --short HEAD [50ms]
[2022-04-12T03:23:46.966Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/master refs/remotes/master [1679ms]
[2022-04-12T03:23:47.073Z] > git remote --verbose [80ms]
[2022-04-12T03:23:47.095Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [115ms]
[2022-04-12T03:23:47.149Z] > git config --get commit.template [41ms]
[2022-04-12T03:23:51.139Z] > git symbolic-ref --short HEAD [33ms]
[2022-04-12T03:23:51.139Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:23:51.176Z] > git rev-parse HEAD [26ms]
[2022-04-12T03:23:51.242Z] > git remote --verbose [43ms]
[2022-04-12T03:23:51.243Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [53ms]
[2022-04-12T03:23:51.276Z] > git config --get commit.template [22ms]
[2022-04-12T03:24:00.378Z] > git symbolic-ref --short HEAD [32ms]
[2022-04-12T03:24:00.379Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:24:00.416Z] > git rev-parse HEAD [26ms]
[2022-04-12T03:24:00.472Z] > git remote --verbose [39ms]
[2022-04-12T03:24:00.478Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [53ms]
[2022-04-12T03:24:00.520Z] > git config --get commit.template [24ms]
[2022-04-12T03:24:02.760Z] > git symbolic-ref --short HEAD [16ms]
[2022-04-12T03:24:02.811Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/main refs/remotes/main [34ms]
[2022-04-12T03:24:02.856Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [35ms]
[2022-04-12T03:24:02.859Z] > git remote --verbose [27ms]
[2022-04-12T03:24:02.884Z] > git config --get commit.template [11ms]
[2022-04-12T03:24:28.861Z] > git log --oneline --cherry main...main@{upstream} -- [38ms]
[2022-04-12T03:24:30.408Z] > git pull --tags origin main [1537ms]
[2022-04-12T03:24:30.408Z] From git.insea.io:sail/gameai/sail_marl
 * branch            main       -> FETCH_HEAD
[2022-04-12T03:24:38.092Z] > git symbolic-ref --short HEAD [17ms]
[2022-04-12T03:24:38.153Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/main refs/remotes/main [55ms]
[2022-04-12T03:24:38.260Z] > git remote --verbose [85ms]
[2022-04-12T03:24:38.277Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [112ms]
[2022-04-12T03:24:38.320Z] > git config --get commit.template [22ms]
[2022-04-12T03:26:51.459Z] > git fetch [1010ms]
[2022-04-12T03:26:51.562Z] > git symbolic-ref --short HEAD [17ms]
[2022-04-12T03:26:51.594Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/master refs/remotes/master [25ms]
[2022-04-12T03:26:51.635Z] > git remote --verbose [27ms]
[2022-04-12T03:26:51.637Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [36ms]
[2022-04-12T03:26:51.660Z] > git config --get commit.template [13ms]
[2022-04-12T03:26:51.955Z] > git fetch [668ms]
[2022-04-12T03:26:54.161Z] > git symbolic-ref --short HEAD [17ms]
[2022-04-12T03:26:54.161Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:26:54.183Z] > git rev-parse HEAD [14ms]
[2022-04-12T03:26:54.224Z] > git remote --verbose [26ms]
[2022-04-12T03:26:54.225Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [34ms]
[2022-04-12T03:26:54.251Z] > git config --get commit.template [13ms]
[2022-04-12T03:27:01.258Z] > git fetch [725ms]
[2022-04-12T03:27:04.004Z] > git fetch [1107ms]
[2022-04-12T03:27:09.175Z] > git symbolic-ref --short HEAD [29ms]
[2022-04-12T03:27:09.175Z] fatal: ref HEAD is not a symbolic ref
[2022-04-12T03:27:09.211Z] > git rev-parse HEAD [25ms]
[2022-04-12T03:27:09.273Z] > git remote --verbose [41ms]
[2022-04-12T03:27:09.274Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [51ms]
[2022-04-12T03:27:09.306Z] > git config --get commit.template [21ms]
[2022-04-12T03:27:13.289Z] > git symbolic-ref --short HEAD [26ms]
[2022-04-12T03:27:13.334Z] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track) refs/heads/main refs/remotes/main [34ms]
[2022-04-12T03:27:13.379Z] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [33ms]
[2022-04-12T03:27:13.381Z] > git remote --verbose [24ms]
[2022-04-12T03:27:13.403Z] > git config --get commit.template [11ms]
[2022-04-12T03:27:17.121Z] Log level changed to: Trace

@lszomoru Hi sir, is it possible to detect the issue?

Note that, on head nodes of clusters, the /home/username is normally mounted to /mnt/home/username. I do not if such setting caused this issue.

Yes, this might have something to do with what you are seeing. How do you open the folder/workspace when you are connected to the remote using the SSH extension? Are you using the cli (ex: code) or are you opening the folder using File -> Open Folder, or you are opening the folder/workspace by clicking on an item in the "Recent" list on the welcome screen?
Could you also please do a test for me:

Open the folder/workspace while being connected to the remote
Make a change to a file (ex: bootstrap-amd.js), and save the file

This file will not have the diff decorators in the editor. Do not close the file.
Does the file appear under "Changes" in the Source Control viewlet? If not, hit the "Refresh" button.

Right click on the file in the "Changes" list and choose "Open File" from the context menu.

Does this action open a second editor instance with bootstrap-amd.js?
If so, does this file have the correct diff decorators in the editor?
If so, what is the path of this resource (you can get it when you hover over the editor tab)

@lszomoru Hi, I appreciate your work on debugging the issue.

thus improving the sample efficiency and increasing agent's performance.

Answer: I open the fold by opening the folder using File -> Open Folder.

Does the file appear under "Changes" in the Source Control viewlet? If not, hit the "Refresh" button.

Answer: Yes.

Does the file appear under "Changes" in the Source Control viewlet? If not, hit the "Refresh" button.

Answer: Yes. It shows the correct diff decorators.

@lszomoru By the way, the git is also very slow. vs-code on cluster's head node performs really poor. It wastes a lot of time.

@lszomoru Hi, I appreciate your work on debugging the issue.

thus improving the sample efficiency and increasing agent's performance.

Answer: I open the fold by opening the folder using File -> Open Folder.

Does the file appear under "Changes" in the Source Control viewlet? If not, hit the "Refresh" button.

Answer: Yes.

Does the file appear under "Changes" in the Source Control viewlet? If not, hit the "Refresh" button.

Answer: Yes. It also shows the correct diff decorators.

Hope my answers can help you to debug the issue. If you need any help, please let me know.

@lszomoru Hi, I found a workaround to fix this issue, that is, opening the absolute path of /mnt/path/to/the/project/ and then the git can work. However, git still works very slow when using commit.

@GoingMyWay, apologies for not getting back to you on this until now, as the notification for the issue has gotten lost in my GitHub inbox. Thank you very much for implementing the requested steps and sharing the results. The information that you have shared that you are indeed running into the limitation that the git extension does not support symbolic links. That is a long standing feature request tracked in https://github.com/microsoft/vscode/issues/5970. Until support for symbolic links is added the only workaround is to open the absolute path, which you have already discovered.
I will go ahead and close this issue now. Thank you very much for your patience during the investigation.

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

@GoingMyWay, apologies for not getting back to you on this until now, as the notification for the issue has gotten lost in my GitHub inbox. Thank you very much for implementing the requested steps and sharing the results. The information that you have shared that you are indeed running into the limitation that the git extension does not support symbolic links. That is a long standing feature request tracked in #5970. Until support for symbolic links is added the only workaround is to open the absolute path, which you have already discovered.
I will go ahead and close this issue now. Thank you very much for your patience during the investigation.

@lszomoru, thank you for the reply. I am looking forward to the new release supporting this feature.

@GoingMyWay, my pleasure. Please subscribe to https://github.com/microsoft/vscode/issues/5970 to get notified when the feature is implemented.


Separate deprecated reports endpoint

Trying to improve the reports endpoint:
Want to make clear that we are trying to move users to the new endpoint. Putting the old get_daily_report documentation into it's own "deprecated" to make it explicit that it should no longer be used for those going back looking for documentation.

🚀 Deployed on https://640260c70dfed01c09d8f602--cozy-fox-0defec.netlify.app


curating sample pipelines to expand on

adding some pipelines snippet code to show kfserving usage. Will be expanded with more robus examples moving forward [added some missing license headers which caught the eye]

This change is

/lgtm

@animeshsingh Do we plan to add the pipeline sample in the kubeflow Pipeline repo?

Not these - there shall be one final good sample there, but the ones here will be representative of multiple scenarios we create.

/approve


Suppress false-positives in credential scanning

Fixes https://github.com/aspnet/AspNetCore-Internal/issues/1471

@Eilon PTAL to make sure you're okay with these kinds of suppressions


Save Current Snapshot.

I can see this might be tricky as the ui asks for confirmation when you save a snapshot, but being able to ensure that the current snapshot is saved when I select a new snapshot would be very helpful for my workflow, especially in soundchecks when I may be switching between acts/snapshots.
If it needs a confirmation, maybe that could be provided as a separate function, to be used on button up. In my workflow confirmation is never an issue. Losing changes is definitely an issue.

Thanks for your feature request! If you (or somebody else) create a proper design for this necessary actions and data flow I could implement this. This includes the necessary actions (and possibly feedbacks) to be implemented as well as considerations around a confirmation action. I think that we could need both a confirmable save action and one that just overwrites the snapshot.

The underlying connection library does not support snapshot/show save at the moment. This would be the first step to implement.

https://github.com/fmalcher/soundcraft-ui/issues/144

I just created the necessary functions in the connection lib. It is now possible to save a snapshot by name, and we can also update the current snapshot (because we know the names of current show and snapshot).
It has to be integrated into the Companion module now.


[wrangler 2.0.5] Devtools is broken on a newly created template project

🐛 Bug report
Describe the bug
After creating a new typescript worker with npx wrangler init, and running npm start with no changes, devtools fails to initialize.
Reproduce the bug

npm i wrangler@beta -g
npx wrangler init avrc-backend-worker
cd avrc-backend-worker
npm start
Press d

Expected behavior
Devtools should open and connect.
Actual behavior
Devtools opens, but fails to connect. If I open the browser devtools and look in the console, there are errors that look like:
Protocol Error: the message with wrong id: {"id":2,"result":{"id":"f218df53bf0d4a12"}}
reportProtocolError @ InspectorBackend.ts:122

Environment and versions
Fill out the following information about your environment.

operating system: Windows 11
output of wrangler -V:

PS C:\Users\bd\src\avrc\avrc-backend-worker> wrangler -V

wrangler

Commands:
  wrangler init [name]       📥 Create a wrangler.toml configuration file
  wrangler dev [script]      👂 Start a local server for developing your worker
  wrangler publish [script]  🆙 Publish your Worker to Cloudflare.
  wrangler tail [name]       🦚 Starts a log tailing session for a published Worker.
  wrangler secret            🤫 Generate a secret that can be referenced in the worker script
  wrangler kv:namespace      🗂  Interact with your Workers KV Namespaces
  wrangler kv:key            🔑 Individually manage Workers KV key-value pairs
  wrangler kv:bulk           💪 Interact with multiple Workers KV key-value pairs at once
  wrangler pages             ⚡ Configure Cloudflare Pages
  wrangler r2                📦 Interact with an R2 store
  wrangler login             🔓 Login to Cloudflare
  wrangler logout            🚪 Logout from Cloudflare
  wrangler whoami            🕵  Retrieve your user info and test your auth config

Flags:
  -c, --config   Path to .toml configuration file  [string]
  -h, --help     Show help  [boolean]
  -v, --version  Show version number  [boolean]

X [ERROR] Unknown argument: V

PS C:\Users\bd\src\avrc\avrc-backend-worker> wrangler -v
2.0.5

output of node -v:

PS C:\Users\bd\src\avrc\avrc-backend-worker> node -v
v16.13.2

content of wrangler.toml:

PS C:\Users\bd\src\avrc\avrc-backend-worker> cat .\wrangler.toml
name = "avrc-backend-worker"
main = "src/index.ts"
compatibility_date = "2022-05-15"

Sorry about this. We're going to work on making our devtools integration better. That particular error should be fine for now, it shouldn't break anything. Could you tell me what browser you use? And where did you open the browser devtools? Thanks!

I use chrome 101.0.4951.54 on Windows 11 Version 21H2, running on the same host that is running wrangler dev.

It does seem that the REPL works, but I'm unable to open any of my source code in the sources tab, so I can't set breakpoints (hence why I initially thought it was completely broken)

This is a known limitation. We only support displaying console log messages in the DevTools. We are working on adding debugging support. See https://github.com/cloudflare/wrangler2/issues/188.
I think this is working as expected, right now. Please follow along with #188 to see progress on better DevTools experience.


401 Unauthorized

Cant do anything, not authorized depsite Account/Bot being admin

For bots, you'll need to add the "Bot " prefix.
Example: Bot xxxxx.yyyyy.zzzzz
Not like this: xxxxx.yyyyy.zzzzz
It might be confusing, so I'll add a bot flag for the config command in the next release.

Update: I've added a bot flag in release 1.11.1.
Example:
dscli config -t=<YOUR-DISCORD-BOT-TOKEN> -i=<YOUR-SERVER-ID> -b

The bot prefix way still works:
dscli config -t="Bot <YOUR-DISCORD-BOT-TOKEN>" -i=<YOUR-SERVER-ID>

Yep putting Bot <token> worked!

I wonder... do you think it would be possible to make a background runner for this to constantly keep it incheck? like pinging the server for a file list to compare to the local filelist every five... ten minutes or so?

That's great! The Discord API requires "Bot " to be added in front of a bot token so that's creates quite a bit of confusion.

I wonder... do you think it would be possible to make a background runner for this to constantly keep it incheck? like pinging the server for a file list to compare to the local filelist every five... ten minutes or so?

Not quite sure what you mean. Are you referring to syncing files automatically?

Yeah, syncing files automatically! However that would require a small timestamp for last edit to be implemented

I think this would need to be implemented as an external tool.
Fortunately, you can get the timestamps with dscli ls -l. Each line is in the format <filesize> <unix timestamp> <filename>.
I don't really think it is possible to edit files without major changes, so the best that can be done currently is comparing timestamps, deleting the old file and uploading the new file.

deleting the old file and uploading the new file.

Or deleting the old file, and downloading the new one

Oh I see, the other way around.
It is a lot more doable I think if that is the case.

ViceVersa would be nice, but if it is setup as a one way sync that would be cool!

That sounds cool!
However, I think dscli should stay the way it is, with additional functionality provided by external tools. Here is an example of a basic GUI frontend to make it easier to upload and download files (https://github.com/darenliang/dsgui).

oh neat! Did not know that even existed!


fix: derive_param_tte() fails for dplyr 1.1.0

Closes #1962
What happened?
If dlpyr 1.1.0 is used, some tests for derive_param_tte() fail. They pass for dplyr 1.0.5 (minimum version required by admiraldev) and also for dplyr 1.1.1.
In derive_param_tte()
    full_join(
      mutate(by_groups, temp_dummy = 1),
      mutate(source_datasets[[i]], temp_dummy = 1),
      by = "temp_dummy",
      relationship = "many-to-many"
    ) %>%
    select(-temp_dummy)

should be replaced by
    crossing(
      by_groups,
      source_datasets[[i]]
    )

This is simpler and avoids the dplyr issue.

Hi Tarun.  I have added you to the repo.  Please use @devel at the end of your branch as this will get latest updates from the admiral depenednecy packages admiral.test and admiraldev
It will also give you the Pull Request TEmplate in your PR - not sure if that was removed or doesn't work with the fork.  But the PR template will walk you through our conventions (testing, style, linting, etc) with links to our documentation.
Thanks again for jumping on this!

Hi @tarunsamanta2k20 do you need help with this PR - we were hoping to finish by the end of the week.

Hi @tarunsamanta2k20 do you need help with this PR - we were hoping to finish by the end of the week.

@bms63 style check is failing. i don't know why. could you please look into this.

Run this line of code -

Hey @tarunsamanta2k20 I put the checklist into your PR - I recommend following through each item as they will help you diagnose common issues you are facing - aslo be sure to check out our dev docs - https://pharmaverse.github.io/admiraldev/devel/articles/development_process.html

Hi @tarunsamanta2k20 thanks for trying to make this happen.  We have this and several other bug fixes being worked on in #1987 - so will close this PR.
I think this was  a tough issue to work on with being new to admiral.  Could you try out #1839 and I can assist you on how to fix common issues from CI and R packages - then we can pick another issue for you to work on.  HAppy to help and don't want to lose your enthusiasm!!

there are failing - I blieve this is due to not having @devel at the end of your branch.
https://pharmaverse.github.io/admiraldev/devel/articles/git_usage.html#create-a-new-feature-branch-from-github-from-devel


New iOS simulator names, Xs, Xs Max, Xʀ

The simulator names changed after updating to Xcode 10.2 (iOS 12.2 SDK)
I don't know how to prevent this change from affecting those who didn't update yet, but it's worth noting that updating to this version is now required in order to submit iOS apps to the App Store

@mcornella sorry I'm not very familiar with Status: testers needed,  is there something I can do to get this PR merged or do we need to wait for someone to test it, what if no one volunteered to do so
Thanks for your effort

It's definitely documented that this change in naming has happened (one instance).
What I'm worried about is how this alias change will play out on users that haven't updated Xcode, and see how we can mitigate these side effects. Maybe we could even check the output of xcrun simctl list devices to see if these new simulator names are there?

Would be awesome, but honestly this is currently beyond my skills level, I don't know how should we proceed on it, we might need to wait until someone contribute in fixing it the same way you mentioned

I can try to look at it this week. Should be able to read the device list output, select which version of the naming scheme to use and run the simulators. That will make this plugin significantly more complex, but it could also open up other cool possibilities, like being able to prompt a user if they have multiple iOS SDK versioned sims for the same device, to select which one they want to run, or handle other conditions. 👍

In the meantime and just for your convenience you can override these aliases in your zshrc file (after OMZ is sourced)
alias rniosxs='react-native run-ios --simulator "iPhone Xs"'
alias rniosxsm='react-native run-ios --simulator "iPhone Xs Max"'
alias rniosxr='react-native run-ios --simulator "iPhone Xʀ"'


When opening GitHub Copilot chat in the editor, the text at the bottom is not fully displayed

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
版本: 1.88.0-insider
提交: 6c19c003574b02afc604c0c1c471b1441b33a3d3
日期: 2024-03-08T06:00:59.312Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0

OS Version: macOS 14.4

Can't repro this. Can you check whether it happens in VS Code Insiders, and does it happen every time for you?

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!