Task doesn't run on folder open anymore

https://github.com/microsoft/vscode-github-issue-notebooks
notice that the task.json has a "runOn": "folderOpen"-script
run the task manually
reload window
:bug: the task doesn't start automatically

cc @alexr00 you fixed this in the past

I certainly caused this w the task reconnection - will look into it

this is working for me now - likely fixed with one of my recent PRs related to automatic tasks

Sorry, this doesn't work

this was working a few days ago, so regression must've been recent

@jrieken you need to allow automatic tasks to run. have you run

https://user-images.githubusercontent.com/29464607/192539252-1dc5784f-17be-4a6d-92f0-2b09c93fa472.mov

https://user-images.githubusercontent.com/1794099/192539724-f992690f-10e3-4d04-ba66-fb7d276a77ab.mov

@jrieken you need to allow automatic tasks to run. have you run

Why is this now needed? I have trusted this workspace and I have run this exact task successfully in the past?

it's always been needed. if you've ever hit disallow, it won't work. once you've allowed for the folder once, you shouldn't have to again

it's always been needed.

I doubt that's true. When I hit allow it writes a workspace setting and that wasn't needed, it came in via https://github.com/microsoft/vscode/pull/154171. I have been using this feature years before this change - albeit infrequently in side projects.
I already have the `"runOn": "folderOpen"- option and I have given trust to the folder. So, why do we put up further hurdles to use this feature?

#154171 was added to prevent these tasks from running automatically without consent of the user in a workspace that may or may not have been set up /configured by them.

some people can find it jarring and unwanted if they run automatically - even if they trust the workspace and happen to have that in their tasks.json file

If I'm remembering right there was always an opt-in via notification (maybe requiring engaging with the task system before it shows?). Whether a task runs on startup is a user preference, so instead of a hidden preference stored in local storage, tasks has moved to a setting. Is the problem that there was no migration to the setting?

Is the problem that there was no migration to the setting?

Yes I think so

If I'm remembering right there was always an opt-in via notification

Looping in @alexr00 for reference but if I remember correctly this notification was the workaround for the lack of workspace trust. We prompted folks with an FYI to give them consent - similar prompts existed for eslint or tsserver and workspace trust is the answer

Whether a task runs on startup is a user preference,

No. This is a workspace setting which means "team preference". It is the same as using source maps for debugging or not. Or what typescript version to use etc. Also, the "Manage Automatic Tasks in Folder" writes a workspace setting not a user setting

Looping in @alexr00 for reference but if I remember correctly this notification was the workaround for the lack of workspace trust. We prompted folks with an FYI to ask them for consent

It was added here https://github.com/microsoft/vscode/issues/64613, derived from this terminal change https://github.com/microsoft/vscode/issues/23362. The discussion in the terminal feature request is here: https://github.com/microsoft/vscode/issues/19758.
I did remember some of this wrong after digging into it and it was added primarily for security, but it's not the only reason for it now. The UX of this is an important part that was refined over time and carried over to terminal profiles; I have a preference of never wanting a workspace to modify my default terminal profile, regardless of whether I trust it.

No. This is a workspace configuration file which means "team preference".

@jrieken I disagree, I've always had auto run tasks disabled as I want to control when they run. This was a consideration when the notification was added. Source maps are a bad comparison as if they work they're almost always a better experience (though I often disable them to access ran variable names).

Also, the "Manage Automatic Tasks in Folder" writes a workspace setting not a user setting

Yes, we simplified it from opt-in to auto running tasks per workspace as that's handled by workspace trust now, to simply "am I a user who wants to enable auto run tasks?". That seems like it aligns with you wanting to have them always enabled and me wanted to have them always disabled.

I have a preference of never wanting a workspace to modify my default terminal profile, regardless of whether I trust it.

I also have many my preferences but the team preferences overrule them: source maps, prettier, lint rules etc pp. That's part of agreeing what are team and personal settings. As a side note: I am not aware that auto tasks have ever been a topic for us (VS Code) and I also don't see any of them in our task.json file. Don't get me wrong: I am happy with a "overrule team decision and go with my preference" path. I think this applies to a few none-critical things, like I want that for source maps.
Anyways, the implementation for auto-run task is poor:

no migration, essentially breaking the feature
the "manage automatic task in folder"-command write a team/workspace-setting which defeats the purpose of overruling  team configuration
the default value for task.allowAutomaticTasks is auto. Its docs say "Prompt for permission for each folder" which is not true and misleading

My initial feeling about this was if the folder is trusted, the tasks should run automatically when configured to do so.
Several points I encountered when I raised this were:

the "manage automatic task in folder"-command writes a team/workspace-setting
this has been around for a long time and we didn't want to remove it for those that are used to it

The setting would make it easier and more discoverable to manage automatic tasks.
I am in favor of removing the prompt per folder and respecting 1) a trusted workspace 2) the setting as configured via the actions or directly

of removing the prompt per folder and respecting 1) a trusted workspace 2) the setting as configured via the actions or directly.

I like that but the action shouldn't write a workspace-setting because task.json is already a "workspace setting". I would argue this should only be allowed as user-setting (which I believe our settings model supports). Also, the default should be on because you conflict team-choice - doing that shouldn't be default. In untrusted workspaces don't ever auto-run a task and maybe show a squiggle in task.json that signals that

Yes I meant as a user setting and agree with you re untrusted workspaces

We're bringing this to the UX sync to decide what the right approach is

Proposal:
Untrusted: ❌ automatic tasks
Trusted: ✅  based on user setting

Approved in the UX sync

Storage target will now be user and storage scope will be profile

We will prompt only once (default is still auto), but you should not see this prompt if you've already answered for the workspace


TSCheck: dot not needed on the end of quick fix action titles

Refs: #25322
There should not be a dot on the end of the titles of quick fix actions. Just compare it to all the other actions we have in the context menu. None of them have a dot at the end

Opened https://github.com/Microsoft/TypeScript/issues/15399 to track this upstream


Generate aes_cipher_core netlist

@satnam6502 trying to generate the netlist for aes_cipher_core_simplified_Netlist causes CI to run out of memory (and be killed), same thing happens locally for me. Any ideas whats wrong here?
This currently compiles all our aes modules into one module. A backup plan would be to create all the netlist separately and then instantiate them explicitly (so separate systemverilog files for all).

Superseded by #573


expose enable_transform for all methods.

the current API does not allow to not perform sampling in unconstrained space.
In scenarios where one has already transformed parameters to unconstrained space, one workaround is to manually build potential functions and pass them to the posterior object.
But it would be nice to enable this for build_posterior as well, as it offers more flexibility to switch between sampling methods etc.
This PR exposes the enable_transform argument from mcmc_transform at the top level to allow this for all methods.
Note: To keep things parallel for all three methods, this PR reverts #714, which enabled custom transforms for NPE.

Codecov Report

Merging #756 (e0ed19b) into main (a240efb) will increase coverage by 0.20%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #756      +/-   ##
==========================================
+ Coverage   73.87%   74.08%   +0.20%
==========================================
  Files          78       78
  Lines        6071     6065       -6
==========================================
+ Hits         4485     4493       +8
+ Misses       1586     1572      -14

Flag
Coverage Δ

unittests
74.08% <100.00%> (+0.20%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sbi/inference/posteriors/direct_posterior.py
98.21% <ø> (ø)

sbi/inference/snle/snle_base.py
91.58% <ø> (ø)

sbi/inference/snre/snre_base.py
91.45% <ø> (ø)

sbi/utils/sbiutils.py
78.86% <ø> (ø)

...inference/potentials/likelihood_based_potential.py
100.00% <100.00%> (ø)

.../inference/potentials/posterior_based_potential.py
100.00% <100.00%> (ø)

sbi/inference/potentials/ratio_based_potential.py
100.00% <100.00%> (ø)

sbi/inference/snpe/snpe_base.py
88.81% <100.00%> (ø)

sbi/neural_nets/embedding_nets.py
60.41% <0.00%> (+23.87%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

I see your point and agree, we can expose it only in the sampler interface.
I encountered the additional problem that TransformedDistribution would result in an AttributeError in mcmc_transform, which is fixed now as well. So in that case it is possible to still use the convenience of build_posterior.


Include infra container metrics in pod metrics - enables network metrics

@mwielgus As discussed - pretty simple in the end following your advice!

@mwielgus: One question I have: with this approach (infra container metrics only being included in pod metrics, not as separate container) will the infra container metrics be sent to sinks?

LGTM, thanks for the PR.

Sinks get all metric sets (containers as well as pods, namespaces and cluster aggregates) and all data that are in metricsets. And of course they can write only a subset of data. Moreover, the exactly same data are available through the API (api is implemented as sink).

Thanks for the explanation.


Idea when opening multiple devices

An ideea to use a random port opened so you don`t have to enter a new one by cli.

Made a script that helps starting in random ports and passing parameter when you have more than one device connected.
Copy to /usr/local/bin/android.sh
run
android.sh
*will take first device connected
run
android.sh [param]
*where param is the device counter, example, for first device connected use 1, for second device use 2, etc
`
#!/bin/bash
random-port() {
while [[ not != found ]]; do
# 2000..33500
port=$((RANDOM + 2000))
while [[ $port -gt 33500 ]]; do
port=$((RANDOM + 2000))
done
    # 2000..65001
    [[ $((RANDOM % 2)) = 0 ]] && port=$((port + 31501))

    # 2000..65000
    [[ $port = 65001 ]] && continue
    echo $port
    break
done

}
printf "Random port used = %05d\n" $(random-port)
#List of devices attached
#9889db394248483045  device
#emulator-5554   device
#scrcpy -p $(random-port)
adb devices > adbdevices
fileItemString=$(cat adbdevices |tr "\n" " ")
fileItemArray=($fileItemString)
Length=${#fileItemArray[@]}
echo $Length
#echo ${fileItemArray[0]}
#echo ${fileItemArray[1]}
taking firts word
#echo "asd dd"  | head -n1 | cut -d " " -f1
parameter=$1
echo $parameter
if [ $# -eq 0 ]
then
echo "No arguments supplied"
parameter=1
fi
counter=1
for i in $(seq 4 2 $Length)
do
var=${fileItemArray[$i]}
if [ $parameter = $counter ]; then
    echo $var
    #executing
    scrcpy -p $(random-port) -s $var
else
  echo "try again"
fi

counter=$((counter + 1))
done
`

A mechanism had been implemented on dev: dc7fcf3c7a7a0e26c2447990206b798742e062c7


Link in DESIGN.md leads to 404

I have found that https://github.com/tigerbeetle/tigerbeetle/blob/5ae6bcdfd6c9e7cef399dc105ce2a0066e7235d1/docs/DESIGN.md?plain=1#L66 points to https://skillsmatter.com/skillscasts/5247-the-lmax-exchange-architecture-high-throughput-low-latency-and-plain-old-java which answers with a 404 Not Found. I was not able to find an alternative link because https://skillsmatter.com/ does not seem to be live (only has an early access list registration form).
Should there maybe be no link, should that link maybe be made public by skillsmatter (if the 404 is fake), or should there be a link to somewhere else instead?

One potential alternative is https://martinfowler.com/articles/lmax.html but as I have never seen the original target of the link, I can't really tell what the author intended here.


Unexpected error "Skipping non-existent file"

Not really sure what else to say 😅

Perhaps there's another problem and the error message is wrong?

Hmm it looks like you're running on Windows - is that correct? This issue has popped up before, the backslash confuses the code even though it should treat file separators generically

Yeah, Windows. Figured so, Windows accepts either slash so / works but native shells on Windows like PowerShell and Nushell tab-complete to the OS default of \.
Node.js has APIs for each operating system so you can switch the parser based on path.sep. Unfortunately it defaults to POSIX only but you can call path.win32 on Windows and path.posix on Linux.


fix: upgrade to version 3.0.628

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jenkins-x-labs-bot
You can assign the PR to them by writing /assign @jenkins-x-labs-bot in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
5b4d529168f1a2fada5f918191adf6cd6bd4bcbb
link
/test vault

gsm
5b4d529168f1a2fada5f918191adf6cd6bd4bcbb
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test gsm

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
5b4d529168f1a2fada5f918191adf6cd6bd4bcbb
link
/test vault

gsm
5b4d529168f1a2fada5f918191adf6cd6bd4bcbb
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


Click 'Auto-Create' And this message popped up

I clicked 'Auto-Create' and this message popped up.
Could anyone tell me how to fix this?
Thank you!

Auto-Create can only add Sollumz objects to the YTYP. So lets say you create or import a YDR in Blender using Sollumz then you can use Auto-Create to add it to the YTYP.
It looks like your object is just a Blender Mesh.
You might want to take a look at the Sollumz Wiki
and here a video I just found that might help you Basic Emissive Logo with Blender/Sollumz

Auto-Create can only add Sollumz objects to the YTYP. So lets say you create or import a YDR in Blender using Sollumz then you can use Auto-Create to add it to the YTYP.
It looks like your object is just a Blender Mesh.
You might want to take a look at the Sollumz Wiki and here a video I just found that might help you Basic Emissive Logo with Blender/Sollumz

Thank you so much for your reply!  Already well solved! ♥

I got the same issue


Implement Table.auto_value_types

The method should allow to try to find a more specific value type in a given column, as described in the design.

[ ] Implement logic for setting a more precise value type for Mixed columns, as described.
[ ] Implement the use_smallest feature to find more precise types.

By default, all integers will fall back to 64-bit ints, but with use_smallest, a 32-bit size will be used if all integers are sufficiently small.
Similarly for text - a max_size will be selected, and if all texts have equal length, it will be set to be fixed-length.

This will only work on in-memory tables. We want the API to be present on Database table for consistency, but always throw Unsupported_Database_Operation.

@jdunkerley I'd like to clarify 2 things.

It will never use Bits_16 or Byte.

Why are we not allowing smaller sizes?

I assume the logic mostly applies for Mixed columns. Parsing Text columns into more specific types is handled by the separate parse method, right?

When we discussed in Gdansk it was agreed it would be the default for integer types. Users can specify them if they wish.
Yes this is to work out the types as needed when we don't know them. It should shrink number types as well.

When we discussed in Gdansk it was agreed it would be the default for integer types. Users can specify them if they wish.

64-bit is the default, right? Then if we use use_smallest, we allow it to go down to 32-bit. IMHO it is a bit un-intuitive that use_smallest still won't use the smallest value, just a slightly smaller one.
I'm fine with keeping it that way though (as, as you said - we can always specify the 16 bits explicitly if needed), but I feel like this may cause confusion. We definitely need to explain this well in the doc comment to be clear that use_smallest will still not use 16-bit ints.

When we discussed in Gdansk it was agreed it would be the default for integer types. Users can specify them if they wish.

64-bit is the default, right? Then if we use use_smallest, we allow it to go down to 32-bit. IMHO it is a bit un-intuitive that use_smallest still won't use the smallest value, just a slightly smaller one.
I'm fine with keeping it that way though (as, as you said - we can always specify the 16 bits explicitly if needed), but I feel like this may cause confusion. We definitely need to explain this well in the doc comment to be clear that use_smallest will still not use 16-bit ints.

I think should be 16-bit smallest. It was 8-bit unsigned byte that we want to avoid, but if you are aiming to make least memory per row short is probably the right target.


docs: Add GlobalVariables to CombinedConstantData

Reflect the changes from #6031 in the protocol-specs.

Docs Preview
Hey there! 👋 You can check your preview at https://662c236852d90f38c0907795--aztec-docs-dev.netlify.app


network_host does not respect system signal

network_host uses tcpserver.serve_forever() method. The serve_forever seems to be running in a tight loop and this might be the reason why signal.SIGINT is not dispatch to the network_host. Maybe, run the server in a background thread or a process and try handling signals.

Fixed. Turns out this was my wrong terminal setting.


Grid: Improve accessibility by adding props aria-readonly & role="rowgroup"

What changed?

aria-readonly is set on the outer <div> with role="grid" to indicate it contains elements which are operable but not editable (contra the grid role default). It can be overridden. The default value is true.

role="rowgroup" is set on the inner container <div> to establish the relationship between the outer <div> with role="grid" and children with role="row". It helps assistive technologies identify the inner container as something akin to a <tbody>. It can be overridden. The default value is "rowgroup".

Why did it change?
Together, these props allow JAWS to recognize Grid as a table and enable “Table Layer” reading commands.

This is excellent! Thanks for improving accessibility! ❤
I'm going to hold off on merging this until #743 has been merged since that PR is pretty complicated and I don't want to cause any conflicts.

I've merged master into this branch and manually resolved conflicts

This feature has been released in version 9.10.0. Thank you for contributing!


Support for Windows Subsystem for Linux

By using DirectX-Headers version v1.0.1 or later, the library can be built for Linux using cmake.

Command-line tool is only supported for Win32 currently

Hacked up the code to use fstream on Windows and verified DDS, TGA, and HDR codecs passed the test suite.

Hacked up the code to use fstream on Windows and verified DDS, TGA, and HDR codecs passed the test suite.


Retrieve nested group membership

At the moment kube-ldap reads the direct group membership from the ldap user account. For example when binding to Microsoft Active Directory we retrieve the memberOf attribute. However, those groups could be members of other groups.
We have a situation where we could have multiple k8 clusters and we would like a default RBAC rule bound to a particular group. Within that group we would have other groups, Ops/InfoSec etc. Instead of having to manage multiple RoleBindings/ClusterRoleBindings for each cluster, we would like to leverage the one parent group.

hm.. I like the idea of supporting nested group memberships.
however, in my opinion the most generic way would be to follow the memberOf (or whatever attribute is configured) values recursively. but this can probably be very costly and would introduce some new challenges (like detecting cycles etc.).

I removed this feature from the  2.0.0 milestone since I haven't found any generic and nice way to support nested group memberships.
Probably I will implement a method do support nested group memberships for Microsoft AD which can be activated via a config parameter.


collect respondent's parents' phone numbers?

In LHI, we don't collect respondent's parents' phone numbers, and we just put their addresses on the order forms (this is a nondomestic example):

Continue that, or start collecting phone like we currently have in Docassemble?

Also note, the parent info seems to be missing from the sexual assault order in LHI, though it was collected, is that intentional?

@ABillmire @normon66
Please see the info above. In the Docassemble version, we currently do collect the phone number for respondents' parent(s) when appropriate, and add them to the forms. (I'm guessing we built that in because the forms refer to the phone number, and we hadn't yet checked that detail in LHI.)
However, I just noticed in the LHI version we don't collect the parents' phone numbers. Would it be better to roll back and collect only the parental address, not phone? Or is it OK to optionally collect their phone?
Also, note the second finding above, is parental info intentionally left off the sexual assault petition or is that a bug in the LHI version? (or a misunderstanding by me)

Let's optionally collect the parents' phone numbers. A phone number is not required in the court rules.
Re: the name(s) and addresse(s) of the minor respondent's parents/guardians/custodians, please add those to the minor PPOs if the info is provided. Let's make those optional fields for the names and addresses of parents/guardians/custodians as well. I want to document the reason: MCR 3.706(D) says that "If the respondent is a minor, and the whereabouts of the respondent's parent or parents, guardian, or custodian is known, the petitioner shall also in the same manner serve the order on the respondent's parent or parents, guardian, or custodian."
Likewise MCR 3.703(C) provides that a petition against a minor must list the names and addresses of the minor respondent's parent or parents, guardian, or custodian if known or can be easily ascertained. I'm going to ask SCAO if the petition forms should be revised for that, because currently there are no spaces for that info.
I'd also like to make a wording change in the interview:
-Where it says "Because [respondent] is an unemancipated minor, both [respondent] and his parents, guardian(s), or custodian(s) must be served with your petition for a personal protection order," I'd like to change it to "If you know or can easily find out the names and addresses of [respondent]'s parent(s), guardian(s), or custodian(s), fill in the information on the following pages." (or something to that effect)

Got it, thanks Amy!
And just double-checking that all this applies to the minor sexual assault petition as well? (see above note about discrepancy in LHI version)

Yes. I believe that discrepancy was unintentional. I can't find any reason for it.

Good catch, @ekressmiller! The discrepancy in the sexual assault order was indeed unintentional. You can see in the image below that those fields were missing, and probably have been all along. All other minor-respondent orders, including the Spanish versions (which were just marked up English forms), included the address of the parents or guardians.

The minor sexual assault order will now include that information, and I'll also update the interview and all minor respondent orders to optionally include phone numbers for parents and guardians, as well.

Thanks @normon66! I defer to @ABillmire, but I don't think you need to update the LHI interview with that phone number change since we're getting closer all the time to being ready with the Docassemble version.

@ABillmire - sounds good. Would you still like me to make the names and addresses for parents optional?

@normon66 again I defer to @ABillmire but my two cents is that change is sort of an enhancement/not necessary in LHI.

@normon66 If it is a quick change, then yes go ahead please.

@normon66 Just to tack on to Amy's go-ahead, we just discussed it and she said that any information is better than none. So if they have an address but no name for a parent, for example, we would want to include the address.

The live Petition for PPO interview has been updated to allow for optional parent names and contact information.


url parameters added, ActivityData module added

Closing this pull request because it has been merge to new PR (https://github.com/spencer-rafada/things-to-do-in-Rexburg/pull/12)


How to scrambler Using Multi Keys

@lelegard  Hii sir !!!
How to scrambler Using Multi Keys
#!/bin/bash
openssl rand -hex 8 > key
export KEY=head -1 key
tsp -v -m --synchronous-log -I ip -r $INPUT_URL
-P scrambler --ignore-scrambled --cw $KEY --dvb-csa2 2001
-P reduce --target-bitrate 2000000 -P pcrbitrate
-P cat -c -a "$CAS_ID/$CA_ID"
-P svrename --provider "$PROVIDER"
-P filter --negate --pid 0x1FFF
-O ip $OUTPUT_URL
I using this script for scrambling... it was one time scrambling
How to automatically key changing for every 10 minutes & How to do this without stopping the stream?
Thank you !

@lelegard Thank you for your reply sir !
#!/bin/bash
if [ -f key ]; then
rm -r key
fi
openssl rand -hex 8 >> key
I am using this script to KeyGeneration....  I want to KeyGeneration every 10 minutes
tsp -v -m --synchronous-log -I ip -r $INPUT_URL
-P scrambler --ignore-scrambled --cw $KEY --dvb-csa2 2001
-P reduce --target-bitrate 2000000 -P pcrbitrate
-P cat -c -a "$CAS_ID/$CA_ID"
-P svrename --provider "$PROVIDER"
-P filter --negate --pid 0x1FFF
-O ip $OUTPUT_URL

if  i  Generated the key automatically in file, how to read the key automatically every 10s when in run my command line ... without stopping the stream. It possible?
-P scrambler --ignore-scrambled --cw $KEY --dvb-csa2 2001

You need to think globally, at system level, end to end. Encrypting is not a goal in itself. Encrypting is done so that only selected people can decrypt the service. This means that you need to provide the decryption key to those selected people.
In your exercise, you generate a random key every 10s, you encrypt with this key, and then what? Nobody knows the decryption keys, nobody can decrypt the stream, you's better throw the stream to the bin instead of wasting broadcast resources.
More seriously, this is what I explained in the previous post. Changing keys requires a system view to distribute the decryption keys to selected recipients. This is why you need a CAS, conditional access system, or your can call it whatever. The DVB-defined interface to the CAS is an ECMG. When using an ECMG for a given CAS, the scrambler plugin will generate random keys for you every N seconds (your choice) but an ECMG is required so that those random encryption keys are not lost and securely transmitted to the selected subscribers.
 The system is unusable, it serves no purpose.

Thankyou sir @lelegard
i have another one doubt pls reply me...
How to multi users plying the SRT stream
tsp -v -m --synchronous-log -I ip -r $INPUT_URL \
-P analyze -i 30 -o report.txt  \
-O srt --listener $SRT_IP --transtype live --messageapi ``` --multiple ```

It playing only one user ... If extra another users trying to play but the stream doesnot playing
first user only play the stream.... i think it unicast method .... How to output stream was multicasting

how to output stream was multicasting.... any commad

This is not related to this thread of discussion. Maybe you are referring to #1150

Thankyou sir @lelegard


Need to set libraries to be installed with control center installation

Currently, this lib - libssl1.0-dev is missing and when user tries to login for the first time, it throws error. Please @Erkin97 investigate and fix it.

Click resolve button

Done.

Fixed.


Map.! error when incorporating mdgriffith/elm-style-animation (another SSCCE)

Does your title concisely summarize the problem? ✔
Did you include a minimal, reproducable example? Is it an SSCCE? ✔
What OS and browser are you using? What versions?
macOS 10.13.6 (17G4015)
Chrome 71.0.3578.98 (Official Build) (64-bit)

What version of Elm are you using?
0.19

I've put the SSCCE here: https://github.com/clozach/sscce-for-elm-compiler-issue-1851.
Steps to reproduce are in the README.

The recent Parcel is compiling with --debug enabled, that is causing your problem. You can downgrade to version 1.10.3 which did not have this option. Please refer https://github.com/parcel-bundler/parcel/pull/2626#issuecomment-462212763.

There is also proposed fix in https://github.com/elm/compiler/pull/1850

I believe this will be fixed by the changes described in this comment: https://github.com/elm/compiler/pull/1850#issuecomment-509327575
I would like to confirm that it works here, but I would not consider this an SSCCE. I would expect to see a single Main.elm file and a single elm.json file all inline in the issue. It is not practical to try reproducing things with parcel. If it is calling elm then that would be part of the SSCCE.
I think it makes sense to close since (1) I think this will be fixed when 0.19.1 and (2) I am not clear on how to reproduce this exactly and confirm myself.

Boy, it's been a long time since I clicked on my github notifications. 😳 Apologies for the extremely delayed response!
TL;DR
My first attempt was created in ignorance, but now I've updated my SSCCE to be truly minimal with far clearer steps to reproduce. No action is needed by anyone here
LV;FFTS*
*Long version; Feel free to skip
Viir wrote:

Why does this not include the --debug flag mentioned in the referenced issue?

By the time I got around to attempting the SSCCE, I'd been wrestling with the error for hours. In my mentally-depleted state, I didn't notice that the --debug flag was relevant.

Why do you depend on Parcel in your example?

The answer's partly because I didn't understand what kyasu1 helpfully pointed out: Parcel compiles with --debug by default. I first encountered the issue when trying to start a new project using Parcel. Not understanding the importance of the flag in repro'ing the error, I reported it as I was able to reproduce it, namely, with Parcel. 🙄
Wanting to have something cleaner to test against once 0.19.1 comes out, I simplified the code in my sscce repo to just elm.json + Main.elm. I also boiled the README down so it should now be easy to follow. 🤓


Fix breaking changes on Data Catalog library update

On the new Data Catalog library version there was a breaking change on the package naming, to make it clearer what version is being used, hence the tests started failing. Updating the sample codes as requested on the PR: #2102

Fix: https://github.com/GoogleCloudPlatform/java-docs-samples/issues/2132

@mesmacosta, it seems these tests don't seem to quite finish? Are they just really long running?

@nnegrey They are really quick, you have to tag the PR with a label kokoro:run to start the tests on the PR.


Raven not sanitizing query string parameters

I just stepped through this locally and found that this line never returns true:
https://github.com/getsentry/raven-ruby/blob/master/lib/raven/processor/sanitizedata.rb#L26
The reason this is happening is because k == :querystring not k == "querystring" it appears at least locally when I'm running this.
To test what was happening I monkey patched into that module and inspected the result of process when my filtered parameter was in the response. I noticed that even the parameter password I had added (one which is in the default parameters) appears to be in plaintext when it's done filtering. Inspecting that line and then switching it to a symbol fixed the issue for me locally.
An aside: I'd wager there's some additional filtering being done on sentry's side for any parameters which slip through? I did notice password is filtered in the listed querystring on an error on my sentry dashboard despite the fact the sanitization didn't work. Also a random parameter is sanitized fanclub_api_key but I don't have key api_key etc in my filtered list. Is that intentional? Not clear from the gem where that filtering occurs.

I'd wager there's some additional filtering being done on sentry's side for any parameters which slip through?

Yes, there is.

Also a random parameter is sanitized fanclub_api_key but I don't have key api_key etc in my filtered list. Is that intentional?

That's correct - this is also something filtered on the Sentry server. We should probably add that to our list as well.

Which version of the gem are you using, and are you using the default processors?

Hey Nate, using 0.13.0 but it looks like 0.13.3 has the same code here:
https://github.com/getsentry/raven-ruby/blob/0.13.3/lib/raven/processor/sanitizedata.rb#L26
Using the default processors. I was actually looking into why fanclub_api_key was getting sanitized when I noticed that my query string locally wasn't getting sanitized at all. I stepped through and then noticed that the key for the query string field for me was a symbol which was why it wasn't decoding the parameters and running them through. Once I did switch it to a symbol on my machine then fanclub_api_key wasn't sanitized (because as you mentioned that was a server only one) but password was (where it wasn't prior to my change locally).

I've been running into this for awhile and was adding "query_string" to sanitize_fields to prevent data leakage. Unfortunately this meant I didn't capture other query params that were useful for debugging.
https://github.com/getsentry/raven-ruby/pull/349 updates the sanitization so :query_string the symbol gets handled as well.


Error when translate to English

`
Loading ./XXX.srt as ASS
... Exception while loading as ASS try as SRT
Loading ./XXX.srt as SRT
Backup file found = ./XXX.srt.tmp
Starting from subtitle 0
... Translating 0 %
Timed out trying to get element (XPATH = //button[@data-testid='translator-lang-option-en'] | //button[text()='English'])
Saving ./XXX.srt.tmp
Traceback (most recent call last):
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\translators\selenium_utils.py", line 89, in init
self.element = find_element(*locator)
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 861, in find_element
return self.execute(Command.FIND_ELEMENT, {"using": by, "value": value})["value"]
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 444, in execute
self.error_handler.check_response(response)
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 249, in check_response
raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.NoSuchElementException: Message: Unable to locate element: //button[@data-testid='translator-lang-option-en'] | //button[text()='English']
Stacktrace:
RemoteError@chrome://remote/content/shared/RemoteError.sys.mjs:8:8
WebDriverError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:189:5
NoSuchElementError@chrome://remote/content/shared/webdriver/Errors.sys.mjs:507:5
dom.find/</<@chrome://remote/content/shared/DOM.sys.mjs:132:16
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator_main_.py", line 126, in
sub.translate(translator, args.src_lang, args.dest_lang)
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\srt_file.py", line 181, in translate
translation = translator.translate(
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\translators\deepl_scrap.py", line 137, in translate
self._set_destination_language(destination_language)
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\translators\deepl_scrap.py", line 108, in _set_destination_language
self._set_language(language, "//*[@data-testid='translator-target-lang']")
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\translators\deepl_scrap.py", line 123, in _set_language
Button(self.driver, "XPATH", xpath).click()
File "C:\Users\dldbd\AppData\Local\Programs\Python\Python310\lib\site-packages\srtranslator\translators\selenium_utils.py", line 98, in init
sys.exit()
SystemExit
WARNING:urllib3.connectionpool:Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000028C6013B1F0>: Failed to establish a new connection: [WinError 10061] 대상 컴퓨터에서 연결을 거부했으므로 연결하지 못했습니다')': /session/a53afbad-9f06-4a68-bce5-739d4de2eb49
WARNING:urllib3.connectionpool:Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000028C60257970>: Failed to establish a new connection: [WinError 10061] 대상 컴퓨터에서 연결을 거부했으므로 연결하지 못했습니다')': /session/a53afbad-9f06-4a68-bce5-739d4de2eb49
WARNING:urllib3.connectionpool:Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'NewConnectionError('<urllib3.connection.HTTPConnection object at 0x0000028C60257AC0>: Failed to establish a new connection: [WinError 10061] 대상 컴퓨터에서 연결을 거부했으므로 연결하지 못했습니다')': /session/a53afbad-9f06-4a68-bce5-739d4de2eb49
`
I used the command from Windows' CMD
python -m srtranslator "./XXX.srt" -i ko -o en
However, only English makes error when try to translate. id(Indonesian), ja(japan) doesn't make error.
Do you know why?

Look here.
There are two english options for translation so deepl name it different. -o en wont work.
Use -o en-US or -o en-GB


.one(undefined) returns the same result as .getList()

Take the following example (from the readme):
module.factory('Users', function(Restangular) {
  return Restangular.service('users');
});

// undefined instead of an integer
Users.one(undefined).get();

// The above returns the same result as
Users.getList();

I'm not sure if this is supposed to happen? If I pass undefined, I would suppose it would throw an exception of some sort, not return an array of all my objects.

Well, as per docs and REST spec, if you pass "undefined" route generated is still /users/, so if you have /users to return the entire collection, that's desired approach.
But generally yes, I do agree that an exception should be thrown if there's undefined passed as in 99% it's going to be implementation error that can get quite confusing.

If I do .one(), I expect the route to be generated to be /users/:id. If I want /users, I'd of course use .all(). So yes, throwing an error would be a good idea :)

Also similar to #779. As users tend to use this method for creating resources, error should be thrown only when one tries to call get(), delete() or put() (as put expects an id which is undefined anyway). post() is allowed in case resource might be created.
Why?
$scope.newThing = Restangular.one('things');
// some modifications
$scope.newThing.save();

This should do POST request to /things.
$scope.newThing = Restangular.one('things').get() or Restangular.one('things, undefinedProperty).get();

This throws an error.

@Quagh please see #892 with my comment for explanation how to create new elements properly. Undefined in one() is not going to be handled by replacing with empty string as this is not the correct usage of this method.

Actually, we need to allow .one('user').get() to do GET /user/ (where we expect single element to be returned). .all('user').getList() will invoke the same URL but expect an array to be returned.


Unable to close floating dialog when saving elm file with syntax errors

Describe the bug

I've got this elm file:
myDef: String
myDef = "Hello"

error in my func
0.0

When I save :w I see this dialog

I can't close it with q or navigate to it with <C-w>w.
What does make it go away is opening a Telescope picker, like "Workspace Diagnostics" (<leader>sd)
To Reproduce

Load the elm code from above:myDef: String
myDef = "Hello"

error in my func
0.0

Think you need elmls and elm-format installed.
Save the flie :w
The dialog should open, and not be focusable or closable.

Extra infoz

If I do :wq I get this message
Desktop

OS: OpenSUSE Tumbleweed 20240714
Terminal: Alacritty, fish shell
Tmux 3.4 and regular non-tmux produces the same result
Kernel: Linux 6.9.9-1-default

Neovim Version

NVIM v0.10.0
Build type: RelWithDebInfo
LuaJIT 2.1.1707061634
Run ":verbose version" for more info.0

So, what have I found after some digging:

When you get "No write since last change for buffer "[Prompt]"" you can close that telescope window by using ":q!", but be careful because it doesn't always close telescope window and may close the buffer without saving your changes (I haven't found why this behavior exists).
When you use <leader>f or :lua vim.lsp.buf.format() it correctly focuses on the error window, so you can close it.
This is looks like elm_format issue because it's reporting a strange error code that neither conform nor vim.lsp.buf.format recognize. I say this because this doesn't happen with formatters for other languages.

Temporary solution:
Silence all errors from elm_format in conform.nvim opts
Mini example:
  {
    'stevearc/conform.nvim',
    opts = {
      formatters_by_ft = {
        elm = { 'elm_format', quiet = true },
      }
    }
  }

What probably should be done
You can open an issue in elm_format mentioning something from this response or try fixing it yourself and open a PR.

Is this really a kickstart issue or more a Telescope/elm LSP issue?

The only way I see to fix it from kickstart is to add configuration for elm formatter

OK thanks. Please report this issue to whatever LSP or formatter elm uses :)


[Enhancement] Conversion of trainer to iteration-based approach, rather than epoch-based.

Training most of the networks on speech dataset require little time per epoch, but are always hungry for training for at least couple of hundred epochs.
During the training I've noticed that for around 30 hours of data, mb-melgan needs no more than 1 minute per epoch on 2x Quadro RTX 8000.  But, it suffers from the delay between epochs during which the dataloader creates the new set.
Changing the epoch-based training to iteration-based training would save up fellow engineers around 15-20% of the training time. After-epoch calculations could be done in parallel (microservice-alike module).
P.S. would be happy to help you out hack this feature in case you need it.

Is that a problem of DataLoader?


Dark theme is now the default theme

Azure Data Studio Version: 1.20.0

Steps to Reproduce:

Open shell

Expected: Default theme is light theme
Actual: Default theme is dark theme

@anthonydresser it looks like the default theme changed in a recent code merge.  Could you please take a look? Thanks!


Add multiple send detection module

Fixes #219

Thanks Joran! Can you please add a test for this as well?


fix: make storybook-source-link a dev dependency

Description
See title
Related issue(s)

Fixes #865

What kind of change does this PR introduce? (check at least one)

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New Feature (non-breaking change which adds functionality)
[ ] New Feature (BREAKING CHANGE which adds functionality)
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

The PR fulfills these requirements:

[x] It's submitted to the main branch
[x] When resolving a specific issue, it's referenced in the related issue section above
[ ] My change requires a change to the documentation. (Managed by Tremor Team)
[ ] I have added tests to cover my changes
[x] Check the "Allow edits from maintainers" option while creating your PR.
[x] Add refs #XXX or fixes #XXX to the related issue section if your PR refers to or fixes an issue.
[x] By contributing to Tremor, you confirm that you have read and agreed to Tremor's CONTRIBUTING.md guideline. You also agree that your contributions will be licensed under the Apache License 2.0 license.

storybook works for me locally after making storybook-source-link a dev dependency. Can you paste the Vercel preview deployment logs?

Many thanks for the dependency hint! Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json. I fixed this on another branch which will be released in 3.12.1.

Thanks @severinlandolt, I used npm i instead of pnpm i, my bad


added program 9,13,20,14  all in cpp format

this is amazing.
thanks for the contribution in my repo and please share this in social media and tag me on twitter.


import key script for Zeyple does not work

Classification
Please delete options that are not relevant.

[ ] Question
[ ] Deliverability issue
[ ] Crash/Hang/Data loss
[X] Serious bug
[ ] Minor bug
[ ] Vulnerability
[ ] Feature/Enhancement
[ ] Documentation

Reproducibility
Please delete options that are not relevant.

[X] Always
[ ] Sometimes
[ ] Rarely
[ ] Unable
[ ] I didn’t try
[ ] Not applicable

Description
running the encryption.sh script returns
gpg<EMAIL_ADDRESS>not a key ID: skipping
Steps to reproduce

Turn on Zeyple
log into container
run "encryption.sh import-all-keys"

Expected results
I would expect it to import all the keys for all the email boxes
Actual results
fails with
gpg<EMAIL_ADDRESS>not a key ID: skipping
Debugging information
looking at the script it appears to try to download the keys using the --recv-keys which needs a key ID but the script is providing the users email address.

This issue has been marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.


remove run_export from _...-level packages

The run_export is added by the -microarch-level package. The _-microarch-level package is used only to select packages during a solve.
closes #6

Checklist

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

@conda-forge-admin, please rerender


OS 2.1: comment field for motions does not appear

In the motion settings an can add a comment field. But I cannot see a place where I can use my created comment field.

If you create a motion comment field in setting, go to a motion update form. You find the motion comment field in an editor at the end of the update form dialog. Hope this helps you.

go to a motion update form. You find the motion comment field in an editor at the end of the update form dialog.

What is a motion update form? When I edit a motion I cannot see a comment anywhere. Do you have a screenshot for me please?

Ping.

Test with a fresh database:

Add a (private) motion comment field "foo"
create new motion
-> in motion form dialog (at the end) you find a editor field with label "foo". There you can enter some comments...
save motion and open motion detail view
-> "foo" comment is listed at the end of this page

So works for me.

Add a (private) motion comment field

Ah, this is a new feature that was no described. I described it now in the docs.


Provide Doxygen

I do not like the current method of documenting this SDK with a PDF. I would appreciate if Doxygen was employed in order to create easy-to-read and easy-to-browse documentation.

Please find the doxygen api documentation at https://github.com/adobe/XMP-Toolkit-SDK/blob/main/docs/API/index.html

OK, that wasn't immediately obvious to me. Maybe I should have looked harder :)
I do think that it wouldn't be a bad idea to add a public URL or at least visible documentation of the Doxygen page, but that's another matter.


Update configmap docs with subpath limitation

This note should be added to avoid confusion just as Secrets

Hello @glongzh , please could you sign the CNCF CLA per instructions on this comment

I signed it

Will await for another sig docs approver/reviewer to sign this off.
/lgtm

/approve


Investment table translations should be more intelligible

The translations of the investment table are currently linked to the slider translations. Because of this, it is not always clear which row in the table refers to which converter. E.g. we have multiple 'coal heaters' in the industry section but it is not clear which one refers to which industrial subsector. We can solve this by adding custom translations for the ambiguous entries.

NOTE: To update the investment table, use the script! https://github.com/quintel/modeling_experiments/blob/master/query_generation/investment_table.py

@marliekeverweij: I'm afraid I won't be able to fix this before the deploy. Is that ok with you?


I installed ROS and gazebo before  your installation steps.
After your installation steps. it showed no module gazebo and no pip.
Now I re-flashed my jetson tx2 with 3.2.1 jetpack.
Thanks.

Hi @asegulucar2016, the repo does that automatically during setup, so you shouldn't have to do that unless there is a problem.
  Thanks.

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/dusty-nv/jetson-reinforcement/issues/18, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOpDK2W5oXxye7GjHipo4tVd1-P0IV7_ks5uDJD-gaJpZM4VCS9s.

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

Hi
Thanks for answer. Now it works perfectly.


Fix typo - introducton -> introduction

Maybe change tojson to toJSON at the same time?

@bebraw tnx!
@nightwolfz which tojson?


[blogpost] KodaDot Products: Exploring the New Horizon of NFTs

Probably @Jarsen136 is around 👀
title
KodaDot Products: Exploring the New Horizon of NFTs
date
20/8/2023

KodaDot, a trailblazer in the blockchain sector, has been on a relentless quest to redefine the Non-Fungible Tokens (NFTs) marketplace. Its suite of distinct kodadot products is a testament to the unceasing innovation that this platform brings to the table. In this article, let's dive deep into the world of KodaDot and its products, with a special focus on their web3 merchandise shop.
KodaDot's Evolutionary Journey
Over the past two years, the team behind KodaDot has been experimenting with various facets of blockchain technology. The spring of 2021 saw a bull run that sparked a flurry of activities within the platform's primary repository. The KodaDot developers successfully managed to handle more than 5000 issues and made over 3000 updates to the KodaDot codebase.
KodaDot's journey has been marked by successful product experiments. The team recognized the potential and need for unique branding within the cryptocurrency market. Unlike other platforms that often presented mundane logos, KodaDot seized the opportunity to create distinctive designs. They began collaborating with artists and communities, aiming to showcase premium designs from artists in their marketplace and support the community.
Vibrant open-source community around nft marketplace
Thanks to 112 contributors and counting, KodaDot has managed to cross a few records among the open source community and set the proper contributors' ethics. They are currently developing at 190 pull requests/month, where the previous record was 250 pull requests in 2/2022, slowly returning to trend stronger and with proper processes. Crossing 15k commits with 13k LOC codebase in single repository distributed among 1100 files, make it superior coordination game-winning streaks in the next bull run, probably dominate any NFT market share with web3 tooling.

KodaDot's Web3 Merchandise Shop
KodaDot's web3 merchandise shop, also called KodaShop has been a resounding success. The shop hit the century mark barely two months after its launch in February 2023. The shop features NFTs that enable users to reveal specific phrases for their NFT owners. It's still in private beta, and KodaDot's team has been providing onboarding assistance to interested users.
The merchandise shop has been a key component of KodaDot's branding strategy. It not only showcases unique artwork but also serves as a platform for early adopters and artists to gain visibility. As KodaDot continues to grow, the shop is expected to feature even more diverse and unique pieces.
KodaShop is the home of 42+ community designs and over 300 sales to our loyal fans who stick with KodaDot brand and are proud to wear our anime-styled designs. We are happy to continue on this journey. We are collecting NFT projects and partners who would like to be with us.

The Pay-Per-Contribution Model
KodaDot has also been exploring bounty-based models to reward contributors. They believe in gig work and are seeking ways to incorporate these strategies across their products. Over $600k in 1000+ on-chain bounties have been processed for contributors, and KodaDot is continuously exploring ways to make the reward system more seamless for others.
KodaDot's pay-per-contribution model has succeeded, with code contributors receiving $KSM and $DOT rewards. Contributors who have made significant contributions are eligible for baseline payrolls, and additional bounties are offered to motivate quick delivery, even over weekends.
You can have a look on rewards sent to contributors in our repository

KodaDot Transfer
KodaDot Transfer is another significant offering from KodaDot. It's a tool that facilitates the transfer of $KSM, $DOT, and in the future, $USDT. The KodaDot transfer has successfully processed over $500k through its transfer dialogue. The transfer flow is currently being revamped, and soon, it will be a full-fledged app for your web3 team to use natively for payrolls

KodaDot API - Uniquery
KodaDot boasts of offering the most endpoints for NFTs in the Polkadot ecosystem. It has been exploring ways to accommodate the customization needs of blue-chip collections and gaming collections. KodaDot's API has been a crucial tool in achieving this goal. Currently except KodaDot itself, there are few teams using KodaDot API - Uniquery for their production
Want to build NFT project quickly? Uniquery is your choice!
KodaDot Fandom Shops
We've been exploring ways to enhance blue-chip collections and, more importantly, accommodate customizations of storefronts required for each gaming collection of artists to feel native. Under the hood, it's supercharged by KodaDot technologies. To some extent, we've found a win-win situation. We've leveraged our KodaDot API - Uniquery and created a quick demonstration. The good news? More than three storefronts are already in the wild using our API in its infant stage.
Learn more about fandom audience growth
KodaDot's Collaboration with Tanssi
KodaDot's collaboration with Tanssi, the Appchain Infrastructure Protocol, has been a game-changer. This partnership allows KodaDot to deploy its own appchain swiftly and effectively, leveraging Tanssi's suite of infrastructure tools and services.
Tanssi's appchain infrastructure protocol streamlines the deployment process, equipping KodaDot developers with an array of powerful tools for swift, permissionless, and efficient appchain deployment.
KodaDot's Appchain
KodaDot's appchain is a significant leap towards enhancing scalability and cost-efficiency in the NFT marketplace. It facilitates quick processing of high-volume transactions and lowers transaction fees. The appchain deployment, powered by Tanssi's infrastructure, allows KodaDot to focus more on enhancing code quality, user experience, and community engagement. This part is in private beta testing.
KodaDot's NFT Marketplace
KodaDot's NFT marketplace is a testament to its commitment to providing an inclusive and diverse environment for transactions. The marketplace supports nine NFT standards across nine Polkadot parachains. As KodaDot expands its multichain strategy beyond the Polkadot ecosystem, its collaboration with Tanssi is supporting its plans to broaden the marketplace's scope to include EVM, zkSync, Arbitrum, BuildOnBase, Starkware and other L2 networks.
The Future of KodaDot
KodaDot's future looks promising, with a TestNet deployment scheduled for later this year, setting the stage for a mainnet launch in 2024. KodaDot's suite of kodadot products is constantly evolving, and the platform is committed to introducing a wide variety of NFT standards and services. This relentless innovation and user-centric approach are what sets KodaDot apart in the NFT marketplace.
Conclusion
In conclusion, KodaDot is blazing a trail in the world of NFTs, with its unique offering of kodadot products. Its web3 merchandise shop, pay-per-contribution model, KodaDot transfer, appchain, and NFT marketplace are all testaments to the platform's commitment to innovation and user satisfaction. As KodaDot continues to evolve, it is set to redefine the blockchain sector and the world of NFTs.

Probably @Jarsen136 is around 👀

Yes, sir

Yes, sir

Added one more section, definitely worth mention! :)

Vibrant open-source community around nft marketplace


Bazel sync breaks Java SDK selection

Hey there esteemed Bazel team,
When I run the Bazel sync in the IntelliJ plugin, it seems to lose my Java SDK, or maybe it can't detect it properly in Bazel? Even if I set an explicit path / Java runtime, it fails to set this up in IDEA.
Is this a known issue, or is anyone else running into it?

hey there Bazel team... could you help with this?

@brendandouglas / @jin?

Hello @sgammon, Could you please provide more details to reproduce the issue at our end. And can you try to test the same with latest bazel plugin and Intellij IDE.  Thanks!

this is so old that i suspect it has been fixed @sgowroji - i'm on M1 now and i've had many fewer problems with bazel and intellij since filing this. will close and re-open if needed :) thank you for the followup.


Rename gcsCredentials to gcpCredentials

Is your feature request related to a problem? Please describe.
That doesn't cause any problem. But, we use the credentials schema to authenticate Google Cloud Platform, not Google Cloud Storage. Something like gcpCredentials sounds more natural. For instance, when I created a BigQuery connector, I was a bit upset to fill out information of credentials by GCS Credentials.

Describe the solution you'd like
We can rename gcsCredentials.json to gcpCredentials.json and its contents.

https://github.com/open-metadata/OpenMetadata/blob/main/openmetadata-spec/src/main/resources/json/schema/security/credentials/gcsCredentials.json

Describe alternatives you've considered
N/A
Additional context

https://openmetadata.slack.com/archives/C02DZK3QH8Q/p1674517036236469

@MilanBariya when working on this let's review the UI page on the dbt ingestion and see if anything is required from the UI team. I believe that page we build manually not from JSON Schema

@MilanBariya I would like to sophisticate gcsConfig at the same time of rename, because specifically selecting multiple projects is a bit to optimized to Google Cloud Storage.
Take an a bit complicated example of BigQuery, for instance. We assume if we would like to ingest metadata of BigQuery in project X and project Y on the right side. Technically, we create a service account in project A. However, we grant no IAMs to it in project B. Instead, we grant roles/bigquery.jobUser in project B and roles/bigquery.dataViewer in project X and Y respectively. To do that, the service account is authorized in project A. The project ID of a BigQuery client must be project B.

My proposal is to extract only authorization parts from gcsConfig. We reuse the extracted parts to BigQuery , Spanner ans so on . Moreover, we implement a new schema specialized Google Cloud Storage.  What do you think?

hi @yu-iskw could you please open a separate feature request for this proposal? The goal of this ticket is to align the naming for GCS vs. GCP. We can fine-tune the configuration later on.
Thanks
cc @MilanBariya


Fix type Proc.Out to return stream after process start

Looks like when a process is created with echo.StartProc() the returned io.Reader via Proc.Out() is empty after the process has been started.
        p := e.StartProc(`curl -LO "https://someurl/file"`)
        b := make([]byte, 1024)
	for {
		n, err := p.Out().Read(b)
		if err != nil {
			if err == io.EOF {
				fmt.Println(string(b[:n]))
				break
			}
			fmt.Println(err)
			os.Exit(1)
		}
		fmt.Println(string(b[:n]))
	}
...

Fixed by #23


Day 418

Good morning! Here's your coding interview problem for today.
This problem was asked by Atlassian.
MegaCorp wants to give bonuses to its employees based on how many lines of codes they have written. They would like to give the smallest positive amount to each worker consistent with the constraint that if a developer has written more lines of code than their neighbor, they should receive more money.
Given an array representing a line of seats of employees at MegaCorp, determine how much each one should get paid.
For example, given [10, 40, 200, 1000, 60, 30], you should return [1, 2, 3, 4, 2, 1].

Identical to Day 265: https://github.com/vaskoz/dailycodingproblem-go/issues/541


encode ignores getstate returning empty dict

I have a custom __getstate__ which excludes attributes that are not seriazable. However if there are no other attributes and __getstate__ therefore returns an empty dict, jsonpickle.encode ignores __getstate__, resulting in an error.
The problem is here (line 627):
https://github.com/jsonpickle/jsonpickle/blob/ef95ebcf56670c4967703c3357ea4c5abeead233/jsonpickle/pickler.py#L618-L628
Just for clarity, this is my code:
class Serializable:
    def __getstate__(self):
        state = copy(self.__dict__)
        exclude = getattr(self, "__exclude__", [])

        for name in exclude:
            state.pop(name, None)

       return state

class ServerConnection(Serializable):
    client_ws: WebSocketClientProtocol
    websocket_server: WebSocketClientProtocol

    __exclude__ = ["websocket_server", "client_ws"]

   ...

Thanks for reporting this! I'm unsure how to properly handle this while maintaining backwards-compatibility though, since this seems like behavior that some people would rely on. I know that the project for which I use jsonpickle actually does rely on this behavior. Would a feature flag be an acceptable solution for this use case?

A feature flag sounds good to me.


Add equivalent to nano.db.list

As it stands, there's no facility for listing all databases on a CouchDB server in slouch.

Took a peek at the code, seems like something like this would work:
DB.prototype.listDatabases = function () {
  return this._slouch._req({
    uri: this._slouch._url + '/_all_dbs',
    method: 'GET'
  });
};

Thanks, but this functionality already exists at slouch.db.all() and it is more scalable as it uses a StreamIterator, e.g.
slouch.db.all().each(function (db) {

  // for each db

}).then(function () {

  // Done iterating through all docs

}).catch (function (err) {

  // An error occurred

});


ciao-controller: Image ID is not shown when workloads listing

ImageID is not shown when running:
ciao-cli workload list

Steps to reproduce it

Create a workload with this https://github.com/01org/ciao/blob/master/ciao-cli/examples/fedora_cloud.yaml
Run ciao-cli workload list

You will see this output:
Workload 1
        Name: Fedora VM no storage
        UUID:3f875e60-da16-46c9-8a9a-dfc60d790611
        Image UUID:
        CPUs: 2
        Memory: 128 MB

This issue was resolved by #1233


Add domain='auto' to pf.dsp.normalize

Added domain='auto' as default for normalization.
Sets domain to 'freq' for FrequencyData and 'time' for TimeData and Signal
Closes #572

@hoyer-a - we decided that it should be a hotfix. Can you please cherry-pick the commts and branch from main? If the tests pass, you can merge directly without furhter review...

Closed in favor of #649


Fix ParseFlags so -stdlib flag goes in CXXFLAGS

gpsd 3.25 failed to build with recent clang if -stdlib=libc++ was passed by the user in CXXFLAGS because gpsd used MergeFlags (which uses ParseFlags) to move the flags where SCons thinks they belong, and because SCons did not know where -stdlib goes it put it in CCFLAGS, which was then passed to the C compiler during a test, and clang emitted a warning that the -stdlib flag was unknown, and the test had requested that warnings be turned into errors with -Werror, which caused the test to get the wrong result which caused compilation to fail later.
See: https://gitlab.com/gpsd/gpsd/-/issues/279
Contributor Checklist:

[ ] I have created a new test or updated the unit tests to cover the new/changed functionality.
[ ] I have updated CHANGES.txt (and read the README.rst)
[ ] I have updated the appropriate documentation

Yes, unfortunately ParseFlags depends on being able to recognize each option, so it's down to people figuring out something is needed and how to handle it. Looks reasonable to me.
Will need to work up changleog entries and preferably add a testcase (most of these are touched either in SCons/EnvironmentTests.py or in test/ParseConfig.py).

@ryandesign - Yup as @mwichmann , please add a blurb to CHANGES.txt and RELEASE.txt, and a test and we'll get this merged.

I'm not planning any further changes to this PR right now but others are welcome to add the missing pieces.


Add Sendable annotations to LanguageServerProtocol, LSPLogging and SKSupport

LanguageServerProtocol was just about slapping Sendable on basically everything because all the request and response types are value types and sendable
LSPLogging was also pretty trivial
SKSupport required a little bit of restructuring in AsyncQueue to get sendable checks to pass. The change actually localize potential races, so it’s for the better.

The most controversial change might be that I’m raising the package description version to 5.8 and adding .enableExperimentalFeature("StrictConcurrency") to the audited modules. But I think it’s fine. I checked that the package still builds with Xcode 15.0.

@swift-ci Please test

@swift-ci Please test Windows


Some of the final changes for 1.x

Though curious as how documentation changes have caused a 0.04% decrease in code coverage, it is currently not something I am to worried about.


Limit on List Prompt Commits not being respected it seems

Issue you'd like to raise.
The limit field in the list_prompt_commits seems to not be respected. I've written a unit test to grab the commits using the Client method, and debugged into it. Here is what I'm seeing:
First, the assertion error when limit is set to 1, asserting that there is only 1 commit returned.
# Test case 2: List commits with limit
limited_commits = list(manager.list_prompt_commits(name, limit=1))

Stepping into the code, we see it yielding for all the commits that the prompt has; that's all well and good, as we see that the limit is correctly set to 1, and the items property correctly only has 1 commit.

Yet, when we return from the method back into the test:

We see that the length of limited_commits = 4, instead of 1.
Suggestion:
Debug limit flag on list_prompt_commits. Maybe this has something to do with the while true and yield loop.

hm, upon further reading this may be expected behavior. Unclear. If so, feel free to close.
Note:
            This method uses pagination to retrieve commits. It will make multiple API calls if necessary to retrieve all commits
            or up to the specified limit.
so I'm assuming the limit is used only for pagination

Thanks for flagging

Should be fixed now! LMK if you still run into issues


Apply foreach on class StringLineGroup got phantom empty line, is it expected?

I' m writing code to dump a FencedCodeBlock, here is the function:
        private static void HandleCodeBlock(FencedCodeBlock codeblock, int level)
        {
            Console.ForegroundColor = ConsoleColor.DarkYellow;
            if (!string.IsNullOrEmpty(codeblock.Info))
            {
                PrintIndent(level);
                Console.WriteLine($"lang: {codeblock.Info}, info args: {codeblock.Arguments}");
            }
            Console.ForegroundColor = ConsoleColor.White;

            foreach (var line in codeblock.Lines)
                Console.WriteLine(line);
        }

Then I see output contains suspicious empty line like this:
  FencedCodeBlock: 36/692-735 @1
 characters.sifeng.voice("c1s1", 3)

And the corresponding markdown is:
```
characters.sifeng.voice("c1s1", 3)
```
After some investigation, I found the enumerator of StringLineGroup returns internal array's enumerator directly. The array contains reserved slot for future item adding, that's the reason why we see phantom empty lines.
Shall we change the GetEnumerator() for StringLineGroup? I can provide some help.

Shall we change the GetEnumerator() for StringLineGroup? I can provide some help.

Yep most likely, you can make a PR for a fix, thanks!

Sorry for using incorrect email address. I will use correct information to commit later.


Support interface default methods

I added possibility to use default method in jdk proxy configuration.
For Javassist and CGLIB default mehods work properly.

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


Explore horizontal layout on web for state pages

working with Ali on designs for this

Any updates?

I'm not prioritizing right now (unless you think it's worthwhile), because this would make sense for desktop but not for mobile


Broken link to Apollo Server docs example

https://www.apollographql.com/docs/graphql-tools/#example reads

To get started with graphql-tools right away, run the example from the Apollo Server docs.

The link is broken.

#965


Query user_id from server when token provided

Trying to fix issue https://github.com/matrix-org/matrix-python-sdk/issues/38

implemented whoami API method https://matrix.org/docs/spec/client_server/r0.3.0.html#get-matrix-client-r0-account-whoami
implemented tests for whoami API method
added user_id detection with whoami API method if token at client initialization provided
added deprication warning if user_id at client initialization provided
implemented test forclient initialization with token provided

Signed-off-by: Pavel Kardash<EMAIL_ADDRESS>

Cleared merge commits from this PR.


Document how the Catalog is cached for Singer-based plugins

From https://github.com/meltano/meltano/issues/2848#issuecomment-1163851856:

the important short-term enhancement is actually to address the point that @tayloramurphy pointed out, which is that the fact of a cached catalog file is currently not mentioned in the documentation.
I've had a quick look through the documentation, and the most sensible place to add a note about the cached catalog (and potentially a hint about using a tap reinstall as a workaround for the missing cache clear feature) seems to be the CLI reference documentation. e.g. in the select section.
Running select is how I had my first introduction to the catalog cache (using transferwise tap-postgres). And if I had chosen to start reading the documentation in order to find out why my select output does not match my list of source entities, I probably would have ended up reading the select CLI reference documentation.

FYI @afolson

Thanks @tayloramurphy
Should I be good to just give it crack and write up a PR with the suggested doc update for the Cached Catalog?

@cwegener updating the reference would be great and if you feel comfortable adding a sentence or two in https://docs.meltano.com/guide/integration#extractor-catalog-generation would be amazing as well.


Options for extending Neuroglancer with UI widgets

I was wondering what the pros/cons are of different approaches for developing UI components/widgets that work together with neuroglancer. There seems to be a few different approches taken by the connectomics community, like

Janelia's clio framework, embedding/wrapping neuroglancer via dedicated react component within a react framework
ng-extend: using vue-based widgets to extend neuroglancer, embedding/wrapping neuroglancer as component, in ng-extend
neuroglancer workspace, using its tile manager and native implementations of new widget, e.g. like in the h01 c3 workspace
integration of Flask, Plotly's Dash, and Python-based neuroglancer

I really like the approach #1 for its flexibility and existing development libraries and tools, but I see that more direct integration of UI widgets into neuroglancer itself (like in #2 or #3) is also nice. What is your perspective on this @jbms, maybe also in terms of better understanding what you see as the planned scope for the functionality of neuroglancer, and development workflows. Thanks!

The advantage of an approach like clio (similar to embedding Neuroglancer in an iframe) where you only interact with Neuroglancer via the JSON state is that you can be fairly confident that your code with continue to work without modification even as Neuroglancer changes, because I try very hard to maintain backwards compatibility with the JSON state representation.  On the other hand, you are limited in what you can do.  For the most part you won't be able to get much data out of Neuroglancer --- only what you can extract from the JSON state.
With an approach like ng-extend, or adding additional functionality directly to neuroglancer itself, you have full control, but as you will be using internal Neuroglancer APIs that will likely change over time, your maintenance burden will be higher if you want your code to continue to work with updated versions of Neuroglancer.  Previously Neuroglancer itself did not offer a particularly convenient way to add additional UI panels that integrated nicely with the rest of the UI, but with the recently-added "side panel" abstraction, that is now significantly easier.
The Python integration is currently very much targeted at the use case of a single server per user, running on a local machine.  For creating a more conventional web application with a Python backend, I think it would need some significant changes.
In principle the upstream Neuroglancer repository itself could contain additional optional UI panels for more specialized functions.  But it is hard to judge whether that would make sense without a specific case to consider.

Thank you for your response and sorry for the delay.
If I read the clio code correctly, it uses the Neuroglancer viewer object, setup via setupDefaultViewer, and adds callbacks etc., so it seems that it can also access state and functions that go beyond the JSON state (i.e. understood as what can be encoded in the URL query parameter). What do you exactly mean by JSON state in this context, is everything that is exposed via the viewer object part of the JSON state?
If some functions/properties are not available via the viewer object/JSON state, but accessible via the UI, what is your policy of adding that to the upstream viewer object? Is it difficult?
Building optional UI panels in a fork of Neuroglancer would perhaps work, but one loses e.g. the benefits that come with using a web framework like Vue or React, and it is also harder to build up collections of "standalone" components that may not even need Neuroglancer. So I will be looking further into the option of embedding Neuroglancer as a React Component like clio for a single server multiple user use cases, i.e. using the Python integration is also not an option.
As for my current understanding of the problem, I think what I would want in terms of data display is implementing a HTTP API which delivers annotation objects (in particular, Points, Lines, Spheres, Ellipsoids and Boxes) to Neuroglancer as a new data source. I'd like to reduce the amount of code reimplementation for parsing/display logic I'd have to do on the frontend as much as possible. So I was thinking of basically using the "copy-paste" the precomputed datasource, and implement the backend API accordingly so that it delivers data according to its spec (including an info file). The difference would be that the data comes from a database in the backend, instead of static files. Does this approach make sense, or would you propose another route/or data source as a scaffold? Also, is this something you might consider for merging upstream?
As far as creating new annotations are concerned, the normal approach would be to add this functionality in Neuroglancer itself. However, in the interest of reducing maintenance burden and being able to track upstream Neuroglancer, I might get away with this approach: I would just intercept key commands, or register Neuroglancer onClick callbacks (I assume they exist), for creating annotations, but instead of creating Neuroglancer objects, I'd just post those annotations to the API (above) and call a refresh function in Neuroglancer to refetch new annotations. This would add some delay due to the server round trip, which would be okay for my use case, but would simplify the implementation a lot. Do you think this approach may work? Or do you have another recommendation?
As for deleting annotations, I think introducing a notion of an "active" object (instead of just a selection list) would be necessary. I can elaborate on that in another issue.

As far as the clio code, I see that I was a bit mistaken as to how it works.  You are correct: The neuroglancer-react package that Janelia has developed defines an abstraction layer that indeed allows setting up event handlers and such, and is not just limited to what can be done using the JSON state.
The "viewer" object just provides access to the internal APIs, so essentially everything that can be manipulated in the UI can also be accessed through that.  However, the neuroglancer-react abstraction layer only provides limited access --- if you were using that, you may find you need to add additional functionality to it, but there is no particular issue with doing that.
As far as serving annotations from a database, for read-only use you could indeed just serve precisely the existing precomputed annotation format, using the same URL structure, and then potentially could just use the existing precomputed datasource to display those annotations, without any copy pasting needed at all.  For write access, there is already a framework in Neuroglancer for annotation sources that allow adding new annotations and modifying existing ones.  Currently the only example of that is the brainmaps datasource, but you could use that as an example.

I do have the following follow-up questions regarding serving annotations from a custom API/database:

When adding the annotation source layer, I would want to add query parameters to the source URL (for project selection, and possibly other filtering information, API tokens etc.). I saw a related discussion #316 #322. It would be nice to show the key-value pair as textfield in the UI panel somewhere for the user to edit them manually if necessary. And/or keep them internally.

Additionally, these parameters should be added to the annotation data GET requests, either as query parameters again, or in the request body. The request body would be preferred. I saw that for the current fetching of prechunked annotation sources, it already adds media and neuroglancerOrigin query parameters, but I haven't looked how they are populated, but the basic code seems to be already in place.

I would also want to add additional information of the neuroglancer state, such as the selection lists for individual segmentation layers, to the requests, see Filtering Criteria below. I wonder if this could be made in a flexible way that could be integrated into upstream.

Spatial subsampling: I think I don't need that as the request should only fetch annotations that I would actually want to display based on filtering criteria. So I would only provide the spatial0 path.

Filtering criteria: There are multiple options, depending on the use cases. As far as I have seen, the current option to e.g. filter synaptic lines based on the selected segments works entirely in the frontend based on shader code, but the actual data is fetched at a specific sampling level in its entirety. To support the same functionality, show annotations based on the selection lists, I'd need to pass along the selection lists (possibly per individual layer) in the request body. Could you suggest how passing of this state is best achieved in the current codebase, possibly it what done already in another context? The API then returns only the filtered annotations for display at spatial0. Should this work well in terms of refresh/refetch when the selection list state is changed (necessitating another annotation fetch and redraw)? Would this also work when zoomed out and NG possibly wants to fetch subsampled data? If only spatial0 is specified in the info "file", would it always fetch spatial0 data?

Other filtering criteria might be useful later on, such as using a bbox annotation as query to only fetch annotations within the bounding box. Once a logic has been defined to transform NG state to annotation source request body, these could be flexibly added later on without hopefully changing/adding too much code.

I will write later more details regarding the write-use case.

@fcollman It sounds like this should also work in the same way for a Dash component and interaction.
@chrisj Just wanted to let you know about this discussion, as you commented in #317 "Annotation and skeleton code in graphene should be ignored for now. We want to take advantage of the precomputed annotation support but I haven't started working on that yet. It is currently commented out and and we may not include it for our first iteration of graphene." It might me worthwhile to keep in sync with the respective API "protocol" you and I seem to be building.

I do have the following follow-up questions regarding serving annotations from a custom API/database:

When adding the annotation source layer, I would want to add query parameters to the source URL (for project selection, and possibly other filtering information, API tokens etc.). I saw a related discussion Allow query strings for precomputed chunks URLs #316 Allows query params in precomputed chunks #322. It would be nice to show the key-value pair as textfield in the UI panel somewhere for the user to edit them manually if necessary. And/or keep them internally.

Since you mentioned previously that you want to support writing annotations as well, not just reading them, you will need to define a new annotation datasource in Neuroglancer, but you could potentially share some of the code from the precomputed annotation datasource so that it isn't too much work.  Neuroglancer expects all of the data source parameters to be encoded in the datasource "URL", but it is up to you exactly what syntax to use, including whether to use query parameters or other syntax.  While there currently isn't support for displaying these parameters as separate text fields or other controls, you can define a completion function that provides hints.  I had previously thought about supporting separate text fields as you describe (that would simply correspond to portions of the datasource URL), and that could certainly be a nice feature, but I think that is largely an unrelated feature and you might want to hold off on implementing that.

Additionally, these parameters should be added to the annotation data GET requests, either as query parameters again, or in the request body. The request body would be preferred. I saw that for the current fetching of prechunked annotation sources, it already adds media and neuroglancerOrigin query parameters, but I haven't looked how they are populated, but the basic code seems to be already in place.

Given that you will be creating a new datasource, you can fully control how requests are made to your server, and how the responses are decoded.

I would also want to add additional information of the neuroglancer state, such as the selection lists for individual segmentation layers, to the requests, see Filtering Criteria below. I wonder if this could be made in a flexible way that could be integrated into upstream.

The existing annotation framework in Neuroglancer will ask your datasource to provide annotations in the following three ways:

By spatial chunk: the data source specifies a grid, and then Neuroglancer will ask your datasource to provide all annotations within a given grid cell, based on the current view.  (This is ignoring the multi-resolution support, but you can just have a single scale.)
By segment id: the data source specifies a set of named "relationships", the user associates each relationship with a segmentation layer, and then Neuroglancer will ask your datasource for all of the annotations associated with a given segment id via a given relationship.  Currently there is no support for a combined segment id and spatial index.  But that could be added if necessary, similar to how multiscale meshes work.
By annotation id: each annotation must have a unique id.  Neuroglancer will ask the data source to provide a single annotation by its id.  This is used only when you hover over the annotation.

Spatial subsampling: I think I don't need that as the request should only fetch annotations that I would actually want to display based on filtering criteria. So I would only provide the spatial0 path.

The data source specifies the number of spatial subsamplings --- you can specify just a single level.  But then note that if you zoom out Neuroglancer will request a lot of data.  There is a workaround though: you can define a fake second level such that if you zoom out too much annotations just won't be shown at all.

Filtering criteria: There are multiple options, depending on the use cases. As far as I have seen, the current option to e.g. filter synaptic lines based on the selected segments works entirely in the frontend based on shader code, but the actual data is fetched at a specific sampling level in its entirety.

As noted, Neuroglancer only fetches data according to the selected segments.  Only for local annotations (where all annotations are stored in the JSON state) is the filtering done locally (though it is not done in javascript code, not in the shader).
There is a form of filtering that can be done via the shader, though: if your annotations have additional properties, you can test for them and then use the discard; statement in the shader to filter.

To support the same functionality, show annotations based on the selection lists, I'd need to pass along the selection lists (possibly per individual layer) in the request body. Could you suggest how passing of this state is best achieved in the current codebase, possibly it what done already in another context? The API then returns only the filtered annotations for display at spatial0. Should this work well in terms of refresh/refetch when the selection list state is changed (necessitating another annotation fetch and redraw)? Would this also work when zoomed out and NG possibly wants to fetch subsampled data? If only spatial0 is specified in the info "file", would it always fetch spatial0 data?

As mentioned this is essentially already implemented, you just need to define the appropriate annotation "chunk" sources for your datasource.

Other filtering criteria might be useful later on, such as using a bbox annotation as query to only fetch annotations within the bounding box. Once a logic has been defined to transform NG state to annotation source request body, these could be flexibly added later on without hopefully changing/adding too much code.

Currently Neuroglancer will just fetch all annotations that are visible in the current view.  There isn't support for clipping based on a bounding box, but that could probably be added in a way that is independent of the data source if it is needed.

I will write later more details regarding the write-use case.

Thanks for the response. Yes, it makes sense to implement my own data source then. I will report here again how progress is going or any questions that come up. I still need to finish work on the API and some other dependencies before I can resume work on this, hopefully soon.


Update README.md

The actual filename is binjr-adapter-demo-3.0.0.zip

Indeed. Thanks for spotting this!


Allow icons in menus

Can VS Code add the ability to have icons beside menu items? I think it would greatly improve UX. Below is a comparison of context menu examples from some common programs.
I realize this is a duplicate of https://github.com/microsoft/vscode/issues/53868 and https://github.com/microsoft/vscode/issues/173981, but since it's been over 4 years since that issue got closed I am hoping things have changed and you will reconsider whether this is still out-of-scope.

This is very helpful for providing friendly and clear development tools, and we hope it can be adopted

It's a good suggestion. It would be helpful.


Insert release/dev17.12 to VS rel/d17.12

Follow up to #10681

@Cosifne @dotnet/roslyn-infrastructure for a quick review


Can't unlink a previous Org connection if I no longer have access to org

Join org
Create Now "Git Integration" with it
Leave org
Can never get rid of the "Git Integration" in Now. If I click the "To disconnect, go to the app settings on GitHub." link to disconnect it, it 404's. Just have to suffer with seeing red x to signify build failure next to literally every repo I ever make unless I remove Now integration completely.

Going through and removing every association to Zeit and my Github now.

@corysimmons Hi, the problem doesn't seem to be related to this project. Leaving an issue in zeit now will help you.

Okay thanks sorry


add get_config() to  AverageEmbeddingsByWeightFeature class

Currently  AverageEmbeddingsByWeightFeature class is missing a get_config() function, so we get error when we try to use it in the embeddings layer.
issues needs to be solved as a follow up:

this class is not reducing the 3D to 2D which is expected.
this class is not called when we use shared embeddings.

rerun tests

rerun tests


Improved feature parity: Security Analytics

Is your feature request related to a problem? Please describe.
It is not possible to configure the Security analytics (Security reporting settings) with AS3.
Describe the solution you'd like
I would to be able to configure the Security analytics with AS3, as it is possible with the CLI (modify security analytics settings...) or the GUI (Security / Reporting / Settings / Reporting Settings).
Describe alternatives you've considered
I configure the security analytics settings out of AS3, with non declarative commands.
Additional context
Exemple of desired tmsh configuration:
security analytics settings {
acl-rules {
collect-client-ip disabled
collect-dest-ip disabled
collect-dest-port disabled
}
collected-stats-internal-logging disabled
dns {
collect-client-ip disabled
}
dos-l2-l4 {
collect-client-ip disabled
}
l3-l4-errors {
collect-client-ip disabled
collect-dest-ip disabled
}
}

duplicate issue