windows...File association not found for extension .py

Hello,
I was able to install aws-shell on windows successfully using pip, i am using python version 2.7.10.  I get below error running any command...as you can see, even hitting the return key gives the same error...any idea what is causing this ??

I'm not sure why you're getting '""' is not recognized as an internal or external command, but I've seen similar issues when the aws command is not on your PATH.  I think we need to clean up the error messages here and improve the install docs for windows.
It might be worth also adding something in the RC file for specifying the path to the AWS CLI executable.

Hi James, Sorry for the late response and Happy new year !!!
I do have aws command set in my PATH but still seem to get the error.  AWS-SHELL was not in my path and was sitting in c:\python27\scripts\ directory.  I tried putting that in the path as well, no luck...

Forgot to mentioned, i did run a "pip install --upgrade aws-shell" and tried that new version and same issue...

I had the same problem and found this as solution:
https://secretweaponsdigital.wordpress.com/2015/07/23/error-file-association-not-found-for-extension-py/
Error: File association not found for extension .py
To fix “File association not found for extension .py” on Windows, execute the following two commands in a cmd.exe with administrator privileges:
assoc .py=py_auto_file
ftype py_auto_file="C:\Anaconda\python.exe" "%1" %*
The first creates an file association. The second sets the program used to execute the file.

Had the same issue in Cygwin with the cygwin python installed. I removed all of the windows commands from /usr/bin/aws.cmd then renamed the file to aws.py, finally I aliased aws and aws.cmd to aws.py.
mv /usr/bin/aws.cmd /usr/bin/aws.py
alias aws.cmd=aws.py
alias aws=aws.py

why does this software depend on my file association preferences?

In Windows run Windows command as Administrator mode.

This solution worked for me:
assoc .py=py_auto_file
ftype py_auto_file="C:\Anaconda\python.exe" "%1" %*

I had the same problem and found this as solution:
https://secretweaponsdigital.wordpress.com/2015/07/23/error-file-association-not-found-for-extension-py/
Error: File association not found for extension .py
To fix “File association not found for extension .py” on Windows, execute the following two commands in a cmd.exe with administrator privileges:
assoc .py=py_auto_file
ftype py_auto_file="C:\Anaconda\python.exe" "%1" %*
The first creates an file association. The second sets the program used to execute the file.

thanks @detlefm It worked for me. you saved my time


a pull request for issue #122

Coverage remained the same at 99.524% when pulling 740ffdef604f64678b0fa4be861e61beba21fd4a on Yaffle:Yaffle-patch-1 into ea9419f7d41791e06a12de4004bb61e635ef51a3 on peterolson:master.

Thanks, looks good


Update MAS link for Klib, iPic, iHosts, iPaste.

Hi,
I'm author of Klib, iPic, iPaste and iHosts. Just update the Mac App Store link. Welcome to merge.
BR,
Jason

@jaywcjlove Thanks. Have a good day.


dtfmods-core-v1.2.0.zip cannot download

root@ubuntu:/etc/ssh/dtf# wget https://www.thecobraden.com/uploads/dtfmods-core-v1.2.0.zip
--2016-05-11 08:18:39--  https://www.thecobraden.com/uploads/dtfmods-core-v1.2.0.zip
Resolving www.thecobraden.com (www.thecobraden.com)... <IP_ADDRESS>
Connecting to www.thecobraden.com (www.thecobraden.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 404 Not Found
2016-05-11 08:18:59 ERROR 404: Not Found.

Closed, as this is a issue with the dtfmods, and not the framework: https://github.com/jakev/dtfmods-core/issues/66


[TW#13155] Documentation of RS-485 related features

Earlier versions of the datasheet state that there is integrated RS-485 support:

ESP32 has three UART interfaces, i.e. UART0, UART1 and UART2, which provide asynchronous communication (RS232 and RS485) and IrDA support, and communicate at up to 5 Mbps.

The current technical reference manual (v1.7) still mentions RS-485 support on page 189:

Supports RS485 Protocol

There is also a very brief documentation of RS-485 related registers.
Due to the very limited documentation, unfortunately no one seems to have managed to successfully use these functionalities yet. Better documentation and an example would therefore be highly appreciated.
This topic is also discussed in the ESP32 forums: https://esp32.com/viewtopic.php?f=13&t=1858
@hwmaier was so kind to provide a software based implementation for the most imminent issue of automated enabling/disabling of the transceiver: https://github.com/espressif/esp-idf/pull/667

Also need these docs

I also need the docs and sample code..help me
TIA.

RS485 support looks like a very nice addition. subscribed to changes on this. Interested to try it when it works :)

Proper RS-485 support would be incredibly useful.

Proper RS-485 support would be incredibly useful.

yeah, that would be a gr8 feature to have!

RS485 support is included since https://github.com/espressif/esp-idf/commit/909eec9c3b174a080e8fed10c0315d43ded5dfd5.


Non-terminating in some challenging likelihoods.

In dual moon, if more slices taken then it hangs.

It hangs with dynamic or adaptive refinement on. Only static sampling works, and only below a certain number of live points.
Bisecting the problem, it seems it starts to hang for num_live_points >= 2126.
This works with the dual moon example:
ns = NestedSampler(log_likelihood, prior_chain, samples_per_step=2125)

results = jit(ns)(random.PRNGKey(42),adaptive_evidence_stopping_threshold=None)

Turning on 64-bit by putting this before any imports resolves the problem, any hints that it's related to hitting the likelihood maximum bound, and squishing the samples onto a plateau.
from jax.config import config
config.update("jax_enable_x64", True)


404 on accessing /store without logging in

If we access /store without logging in, it shows 404 message.
It's better to redirect to login page.

It seems it shows 404 message even if I have logged in as a store user at first time.

After refreshing DB, it does not occurred again, so I'll close this.


[MRG] add gemini model

Closes  https://github.com/MLSysOps/MLE-agent/issues/166
Before submitting this PR, please make sure you have:

[x] confirmed all checks still pass OR confirm CI build passes.
[x] verified that any code or assets from external sources are properly credited in comments and/or in
the credit file.

LGTM, did you tested with success? @leeeizhang

Yes, I have tested both gemini-1.5-flash and gemini-1.5-flash-latest, and they work well in our baseline mode.


Add probes for ha igs

Description

Defines active-passive probes for the roles that need them

Motivation and Context
It is needed in order to have proper HA for all roles. The workaround up to know was to use a Readiness probe and let the "passive" pod in a not Ready state. With the probes in the PR, traffic is routed to pods using labels and selectors (created by the operator).
Closes #309
How Has This Been Tested?
Deployed kubecf with high_availability: true and Diego. Then checked the roles that got the probes to see if only one of the pods has the active label. The relevant services also got a selector. We checked that traffic is actually reaching only one of the pods by looking at their logs.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code has security implications.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

bazel run //dev/cf_operator:apply

fails now with :
clusterrole.rbac.authorization.k8s.io/cf-operator configured
clusterrolebinding.rbac.authorization.k8s.io/cf-operator unchanged
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.
the namespace from the provided object "kubecf" does not match the namespace "cfo". You must pass '--namespace=kubecf' to perform this operation.

it seems the problem is this: https://github.com/helm/helm/issues/980#issuecomment-280730339
(because the operator chart is creating objects in the watch namespace: https://github.com/cloudfoundry-incubator/cf-operator/blob/master/deploy/helm/cf-operator/templates/role-binding.yaml#L6 and that's a problem when you do a helm install --namespace=)

Concourse now fails because of https://github.com/SUSE/kubecf/pull/392

The probes itself look good to me, but I wonder why we're replacing the readiness probe with the active/passive one instead of just adding the active/passive one on top?
I think it might be useful to see the readiness status of the passive pods as well, no?

I'm seeing this now in my deployment (occasionally) with the current PR:
2020-03-02T14:14:50.357Z        DEBUG   active-passive-reconciler       quarksstatefulset/active_passive_reconciler.go:98       validating probe in pod: susecf-scf-diego-api-1               2020-03-02T14:14:50.357Z        DEBUG   controller-runtime.manager.events       recorder/recorder.go:52 Normal  {"object": {"kind":"QuarksStatefulSet","namespace":"scf","name":"susecf-scf-di
ego-api","uid":"3365efd7-fd37-45d9-bc02-40bc79cf33c7","apiVersion":"quarks.cloudfoundry.org/v1alpha1","resourceVersion":"7259"}, "reason": "active-passive", "message": "validating probe in pod: susecf-scf-diego-api-1"}
2020-03-02T14:14:50.517Z        DEBUG   active-passive-reconciler       quarksstatefulset/active_passive_reconciler.go:98       failed to execute active/passive probe: failed executing comma
nd in pod: susecf-scf-diego-api-1, container: bbs-bbs in namespace: scf: command terminated with exit code 1
2020-03-02T14:14:50.517Z        DEBUG   active-passive-reconciler       controller/controller.go:256    periodSeconds probe was not specified, going to default to 30 secs
2020-03-02T14:14:50.517Z        DEBUG   controller-runtime.manager.events       recorder/recorder.go:52 Normal  {"object": {"kind":"QuarksStatefulSet","namespace":"scf","name":"susecf-scf-di
ego-api","uid":"3365efd7-fd37-45d9-bc02-40bc79cf33c7","apiVersion":"quarks.cloudfoundry.org/v1alpha1","resourceVersion":"7259"}, "reason": "active-passive", "message": "failed to execute active/passive probe: failed executing command in pod: susecf-scf-diego-api-1, container: bbs-bbs in namespace: scf: command terminated with exit code 1"}                                       2020-03-02T14:14:50.517Z        DEBUG   controller-runtime.manager.events       recorder/recorder.go:52 Normal  {"object": {"kind":"QuarksStatefulSet","namespace":"scf","name":"susecf-scf-di
ego-api","uid":"3365efd7-fd37-45d9-bc02-40bc79cf33c7","apiVersion":"quarks.cloudfoundry.org/v1alpha1","resourceVersion":"7259"}, "reason": "active-passive", "message": "periodSeconds probe w
as not specified, going to default to 30 secs"}
2020-03-02T14:14:51.337Z        DEBUG   statefulset-rollout-reconciler  statefulset/statefulset_rollout_reconciler.go:71        Reconciling StatefulSet scf/susecf-scf-diego-api
2020-03-02T14:15:04.554Z        INFO    active-passive-reconciler       quarksstatefulset/active_passive_reconciler.go:64       Reconciling for active/passive QuarksStatefulSetscf/susecf-scf
-routing-api

The active label gets set correctly to only one of the two instances:
> kubectl describe pod susecf-scf-diego-api-0 -n scf
Name:         susecf-scf-diego-api-0
Namespace:    scf
Priority:     0
Node:         activepassive-control-plane/<IP_ADDRESS>
Start Time:   Mon, 02 Mar 2020 14:47:30 +0100
Labels:       controller-revision-hash=susecf-scf-diego-api-67bb57d85b
              quarks.cloudfoundry.org/az-index=0
              quarks.cloudfoundry.org/deployment-name=susecf-scf
              quarks.cloudfoundry.org/instance-group-name=diego-api
              quarks.cloudfoundry.org/pod-active=active
              quarks.cloudfoundry.org/pod-ordinal=0
              quarks.cloudfoundry.org/quarks-statefulset-name=susecf-scf-diego-api
              statefulset.kubernetes.io/pod-name=susecf-scf-diego-api-0
Annotations:  quarks.cloudfoundry.org/canary-rollout-enabled: true
              quarks.cloudfoundry.org/version: 1
....
> kubectl describe pod susecf-scf-diego-api-1 -n scf
Name:         susecf-scf-diego-api-1
Namespace:    scf
Priority:     0
Node:         activepassive-control-plane/<IP_ADDRESS>
Start Time:   Mon, 02 Mar 2020 15:04:01 +0100
Labels:       controller-revision-hash=susecf-scf-diego-api-7b54bd848f
              quarks.cloudfoundry.org/az-index=0
              quarks.cloudfoundry.org/deployment-name=susecf-scf
              quarks.cloudfoundry.org/instance-group-name=diego-api                                                                                quarks.cloudfoundry.org/pod-ordinal=1
              quarks.cloudfoundry.org/quarks-statefulset-name=susecf-scf-diego-api
              statefulset.kubernetes.io/pod-name=susecf-scf-diego-api-1

(Note the quarks.cloudfoundry.org/pod-active=active label)
On the other hand, now that I've re-enabled the healthcheck probes, I can see from the pod list that the ones that are passive, now aren't completely ready (since the healtcheck fails):
kubectl get pods -n scf
NAME                                   READY   STATUS    RESTARTS   AGE
susecf-scf-adapter-0                   4/4     Running   0          15m
susecf-scf-adapter-1                   4/4     Running   0          16m
susecf-scf-api-0                       15/15   Running   1          13m
susecf-scf-api-1                       15/15   Running   1          17m
susecf-scf-bits-0                      6/6     Running   0          16m
susecf-scf-bits-1                      6/6     Running   0          17m
susecf-scf-bosh-dns-5df4fd77b5-cjztf   1/1     Running   0          34m
susecf-scf-bosh-dns-5df4fd77b5-g4txv   1/1     Running   0          34m
susecf-scf-cc-worker-0                 4/4     Running   0          16m
susecf-scf-cc-worker-1                 4/4     Running   0          17m
susecf-scf-credhub-0                   5/5     Running   0          16m
susecf-scf-credhub-1                   5/5     Running   0          17m
susecf-scf-database-0                  2/2     Running   0          34m
susecf-scf-diego-api-0                 6/6     Running   2          34m
susecf-scf-diego-api-1                 5/6     Running   2          17m
susecf-scf-doppler-0                   9/9     Running   0          18m
susecf-scf-eirini-0                    9/9     Running   0          34m
susecf-scf-log-api-0                   7/7     Running   0          16m
susecf-scf-log-api-1                   7/7     Running   0          17m
susecf-scf-nats-0                      4/4     Running   0          16m
susecf-scf-nats-1                      4/4     Running   0          17m
susecf-scf-router-0                    5/5     Running   0          16m
susecf-scf-router-1                    5/5     Running   0          17m
susecf-scf-routing-api-0               4/4     Running   0          34m
susecf-scf-routing-api-1               3/4     Running   0          18m
susecf-scf-scheduler-0                 8/8     Running   0          16m
susecf-scf-scheduler-1                 8/8     Running   0          17m
susecf-scf-singleton-blobstore-0       6/6     Running   0          18m
susecf-scf-tcp-router-0                5/5     Running   0          15m
susecf-scf-tcp-router-1                5/5     Running   0          16m
susecf-scf-uaa-0                       6/6     Running   0          13m
susecf-scf-uaa-1                       6/6     Running   0          17m

And their describe indeed shows (taking one for example, but all looks the same):
  Warning  Unhealthy  4m19s (x88 over 18m)  kubelet, activepassive-control-plane  Readiness probe failed: dial tcp <IP_ADDRESS>:3000: connect: connection refused

which might be misleading.
I went a bit further and tried to delete one of the active pod ( susecf-scf-routing-api-0 ), but the situation degradated quickly:
susecf-scf-routing-api-0               0/4     Init:Error   1          26s
susecf-scf-routing-api-1               4/4     Running      0          22m

The susecf-scf-routing-api-1 was correctly marked as active and picked up, so the services are correctly routed to it.
After a bit, everything went as expected:
susecf-scf-routing-api-0               3/4     Running   0          3m1s
susecf-scf-routing-api-1               4/4     Running   0          24m

As @viovanov pointed out (and that was the original reason we needed something different than readiness probes), showing up as non-ready isn't a valid status for a healthy pod. If that was true, we didn't need anything else.

As @viovanov pointed out offline (and that was the original reason we needed something different than readiness probes), showing up as non-ready isn't a valid status for a healthy pod. If that was true, we didn't need anything else.

I was under the assumption that the service itself is actually healthy even on the passive nodes, the probe just opens a connection to a local port after all. But if this is not the case I agree that it makes sense to remove the readiness probe.


refactor: remove panic! from examples

relates #2308

Current dependencies on/for this PR:

main

PR #2454   👈

This stack of pull requests is managed by Graphite.

Merge activity

Feb 20, 3:18 AM EST: @Boshen merged this pull request with Graphite.


Using std::normal_distribution rather than inverse transform sampling?

The lines
https://github.com/ExCALIBUR-NEPTUNE/NESO/blob/9423bffef11c4a22ccdbb9ef92bf93fdeea8fd17/solvers/Electrostatic2D3V/ParticleSystems/charged_particles.hpp#L255-L257
are I think sampling Cartesian components of a velocity vector from independent standard normal distributions, using an inverse transform sampling approach. While it probably has a negligible performance impact overall, for a standard normal distribution inverse transform sampling is generally a relatively inefficient way to generate random variates, and the implementation of random variate generation for std::normal_distribution is likely to be quicker (*). Probably more importantly, inverse transform sampling can also be less numerically stable than alternatives when sampling values in the tails of the distribution, depending on how accurate the inverse cumulative distribution function / (or here inverse error function) approximation is, and also I would say is less readable compared to something like
std::normal_distribution<double> standard_normal(0, 1);
...
auto rvx = standard_normal(rng_phasespace);
auto rvy = standard_normal(rng_phasespace);
auto rvz = standard_normal(rng_phasespace);

Is there some other reason for preferring the current inverse transform sampling approach that I'm missing though?
(*) Sampling with std::normal_distribution appears to be about 2× quicker than the current inverse transform sampling method in the example below on my laptop.

Microbenchmark
#include <chrono>
#include <iostream>
#include <random>
#include <boost/math/special_functions/erf.hpp>

int main() {
    const long int seed =<PHONE_NUMBER>07;
    const int num_draws = 100000000;
    std::mt19937 rng(seed);
    std::uniform_real_distribution<double> standard_uniform(0, 1);
    std::normal_distribution<double> standard_normal(0, 1);
    double draw;

    auto start = std::chrono::high_resolution_clock::now();
    for (int i = 0; i < num_draws; i++) {
        draw = standard_normal(rng);
    }
    auto stop = std::chrono::high_resolution_clock::now();
    std::chrono::duration<double> time_taken = stop - start;

    std::cout << "Time taken for " << num_draws
              << " std::normal_distribution draws: "
              << time_taken.count() << " seconds" << std::endl;

    start = std::chrono::high_resolution_clock::now();
    for (int i = 0; i < num_draws; i++) {
        draw = boost::math::erf_inv(2 * standard_uniform(rng) - 1);
    }
    stop = std::chrono::high_resolution_clock::now();
    time_taken = stop - start;

    std::cout << "Time taken for " << num_draws
              << " boost::math::erf_inv inverse transform sampling draws: "
              << time_taken.count() << " seconds" << std::endl;

    return 0;
}

Output
Time taken for 100000000 std::normal_distribution draws: 2.45805 seconds
Time taken for 100000000 boost::math::erf_inv inverse transform sampling draws: 5.36911 seconds

Hello Matt. Thanks for your interest!

inverse transform sampling can also be less numerically stable than alternatives when sampling values in the tails of the distribution

I didn't know this. Can you provide a source (not that I don't believe you, but I'd like to read more)?
I'd be more than happy to review a PR if you'd like to contribute? Also, out of paranoia, are there any cheeky differing factors of sqrt(2) between these functions?

inverse transform sampling can also be less numerically stable than alternatives when sampling values in the tails of the distribution

I didn't know this. Can you provide a source (not that I don't believe you, but I'd like to read more)?

In looking for a reference for this I think I've instead found that it might have been an outdated belief on my part about the accuracy of numerical approximations to the inverse error function 😅. There is a discussion of the relative precision of the the inverse transform and Box-Muller methods for generating normal random variates in this blog post by Christian Robert which found that counter to his expectations the inverse transform method remained accurate in the tails and I've just a quick investigation with std::normal_distribution and the boost::math::erf_inv based inverse transform sampling approach which suggest both give similarly decent tail probability estimates even quite far in to the tails (both give reasonable estimates for $\mathrm{Pr}(|X| > 6)$ with $X\sim\mathcal{N}(0,1)$). So on the accuracy side it doesn't seem there is any benefit actually.

I'd be more than happy to review a PR if you'd like to contribute?

I'd be happy to submit a PR though equally if you think in the context of above its not worthwhile that's also fine.

Also, out of paranoia, are there any cheeky differing factors of sqrt(2) between these functions?

Good catch - there is indeed a missing factor of sqrt(2) in what I had above as the relationship between the inverse standard normal CDF and inverse error function is $\Phi^{-1}(u) = \sqrt{2} \mathrm{erf}^{-1}(2 u - 1)$ so would need something more like
std::normal_distribution<double> normal_half_var(0, 1 / sqrt(2));
...
auto rvx = normal_half_var(rng_phasespace);
auto rvy = normal_half_var(rng_phasespace);
auto rvz = normal_half_var(rng_phasespace);

to match current distribution.

Great, thanks for this, and I'm happy to hear that I have unknowingly not fallen into a trap by avoiding the extra couple of lines required to write a Box-Muller transform.
I think using a normal distribution is less surprising than the inv_erf function, and more people will understand the intent. If you don't mind pushing a PR, I'd be happy to review + merge.


[Bug]: Missing kissing scenes after lunching mods with mod manager

Operating System
Windows 10
BG3 Mod Manager Version
<IP_ADDRESS>
BG3 Game Version
Patch 4
Bug Summary
Missing kissing scenes (the one where you can speak to your romance option) after launching mods with mod manager. I tried differnet mods. And it seems that after update all mods launched on mod manager couse this problem. If anyone knows how to fix it or have same issue, please respond.
Links
No response

Was just reading another thread and a couple people said it was solved by removing the camp events mod.

Was just reading another thread and a couple people said it was solved by removing the camp events mod.

I dont have that mod. Its general problem only with Shadowheart as far as i know but thank you for commnet. Could you please send me the mentioned thread?

Unfortunately I didnt keep it open. Just spent some time trying to track it back down, and was unable to find it.


Convert Accordion tests from jest to cypress

We want to migrate all tests to Cypress. So lab/src/tests/accordion need to be converted and housed at labs/src/tests/__e2e/accordion
See many existing examples for cypress patterns/conventions
The Cypress tests can consume StoryBook stories as fixtures

Fixed in #307


Add: Pedro Ferreira Mamede's Info

IMPROVE: Add Pedro's Info!
Peace!

Only contributors get that and that's automated.


Chipper parameter optimizer

This notebook from Yonas optimizes the chipper parameters using a set of labeled data.

Codecov Report

Merging #89 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #89   +/-   ##
=======================================
  Coverage   84.77%   84.77%
=======================================
  Files          29       29
  Lines        1741     1741
  Branches      240      240
=======================================
  Hits         1476     1476
  Misses        237      237
  Partials       28       28

Continue to review full report at Codecov.

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


storage: Optimize seek write for many tombstones (#8514)

Cherry-pick of #8514
What problem does this PR solve?
optimize seek write when there are too many tombstones.
Fix https://github.com/tikv/tikv/issues/8486
What is changed and how it works?
Three optimizations:

for batch-get and coprocessor(point-get), use prefix_seek and prefix_same_as_start to get seek every key for write cf, so it can skip tombstones of other keys.
for prewrite, when calculating has_data_in_range use max-skippable-internals-keys to avoid seek too many tombstones.
check key order before calling near_seek for ScanMode::Mixed which save one seek() and several prev() calls

batch-get before and after

prewrite before and after

(before has no tombstone statistics for seek, actually there are a lot)
Related changes

PR to update pingcap/docs/pingcap/docs-cn:
PR to update pingcap/tidb-ansible:
Need to cherry-pick to the release branch

Check List
Tests

Unit test

Release note

Optimize seek write for many tombstones

/merge


App doesn't seem to detect installed NPM packages in Typescript files

There's also no code completion for NPM packages. The Typescript compiles fine and the app runs without errors.

Same BUG bere
App version: 1.5.0(227) - TestFlight

Same issue here. Can't seem to get the editor to detect express types.

Same issue here! Is there any workaround for this?


Feature request - public API for the policies list

It will be great if you could add a public API for the policies collection (the ones that are internal in PolicyBuilder) so it would be possible to cancel or reset a policy. Extremlly useful in integration tests when testing a class that uses the policy features. I want the ability to reset the policy after each test.

Currently I do this:
private void ResetPolicy(Policy policy)
{
var privatePolicy = policy.GetType().GetField("_policy", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic).GetValue(policy);
var exPol = privatePolicy.GetType().GetField("_exceptionPolicy", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic).GetValue(privatePolicy);
var target = exPol.GetType().GetField("_target", System.Reflection.BindingFlags.Instance | System.Reflection.BindingFlags.NonPublic).GetValue(exPol);
var state = target.GetType().GetField("policyState").GetValue(target);
state.GetType().GetMethod("Reset").Invoke(state, null);
}

IPolicy is my interface

Off the top of my head, I don't see any drawback to exposing the policies list. Marking this issue for review.

Thank you

Hi @DennisNerush Many thanks for the idea here and your interest in the Polly library!
Polly does not currently maintain an internal list of the policies which have been created.  I would be reluctant to recommend adding this, because it could constitute a memory leak.  At the moment, if somebody codes Policy.Handle<Whatever>().Retry().Execute(...) (or similar), the single-use policy created is, in due course, garbage-collected.  If otoh Polly were maintaining some static/thread-safe list of all policies created, single-use policies would not be garbage-collected and (think high-volume scenarios) could eventually constitute a memory-leak.  Therefore recommending this one as 'wont fix'
There is nothing of course to stop library users holding references to created policies themselves (var myPolicy = Policy.Handle<Whatever>().Retry();)
Regarding the ability to reset a circuit-breaker policy, this seems like a valuable addition for other reasons too (eg for operational control); keeping #62 open to track that.


Styling leaderboard

IN This PR I present the LeaderBoard app Styling: 🎨
Below are some of my implementations as well as going over the project requirements 🤝 .
Requirements
-Please keep the general layout of the wireframe, this is the only mandatory requirement.
-You can use plain CSS or any CSS framework.
Achievements
-Please keep the general layout 📜  of the wireframe, this is the only mandatory requirement.✅
-You can use plain CSS 🎨 or any CSS framework.📦 ✅
Conclusion
I would love to hear 👂  from you my CR in terms of what can be better implemented 👨💻  for the site thankyou!. And I look forward to hearing from you soon.  🙇

@Olamarx thankyou! 👏  for this key review, I will get to it and fix the issue ⚙.

After  A CR I was requested to make changes ♻  to the LeaderBoard app's Basic UI and Functionality:
Below are some of my implementations as well as going over the Changes requirements 🤝 .
Required Changes
-Adjust ↔  addbutton placement to fit wireframe UI design 🎨.
Achievements
-Adjust ↔  addbutton placement to fit wireframe UI design 🎨. ✅
Conclusion
I would love to hear 👂  from you my CR in terms of what can be better implemented 👨💻  for the site thankyou!. And I look forward to hearing from you soon.  🙇


Cow: Watch ghostwritingproficiency.com

Cow requests the watch of the watch_keyword ghostwritingproficiency\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

ghostwritingproficiency\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Jeff Schaller in Charcoal HQ


Consolidate seds functionality in awk itself

This is the replacement of #879

@lukaswelte can you review that? Thanks.

@kolloch maybe you meant @lloesche to review… :smile:

LGTM


Quickstart Sample Readme

Prereq section specifies "azd --version", which should be "azd version"
Prerequisite check
In a terminal or command window, run dotnet --version to check that the .NET SDK is version 6.0 or later.
Run az --version and azd --version to check that you have the appropriate Azure command-line tools installed.

Fixed in Quickstart repo


SNOW-737313 Add optional parameter chunk_size in create_dataframe

Please answer these questions before submitting your pull requests. Thanks!

What GitHub issue is this PR addressing? Make sure that there is an accompanying issue to your PR.
Fixes #SNOW-737313

Fill out the following pre-review checklist:

[ ] I am adding a new automated test(s) to verify correctness of my new code
[ ] I am adding new logging messages
[ ] I am adding a new telemetry message
[ ] I am adding new credentials
[ ] I am adding a new dependency

Please describe how your code solves the related issue.
Add chunk_size as an optional parameter, default to 10,000.

Codecov Report

Merging #697 (d103517) into main (7a4ae5a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #697   +/-   ##
=======================================
  Coverage   98.72%   98.72%
=======================================
  Files          49       49
  Lines        7985     7985
  Branches     1353     1353
=======================================
  Hits         7883     7883
  Misses         41       41
  Partials       61       61

Impacted Files
Coverage Δ

src/snowflake/snowpark/session.py
98.25% <ø> (ø)

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

I think this change should be for sp connector only. I'm not sure if client in general needs this.

I think this change should be for sp connector only. I'm not sure if client in general needs this.
You might want to move your change to the sp connector repo

I see, that makes sense. Closing this.

Actually, we still need some change in this repo, since Session.create_dataframe calls Session.write_pandas where chunk_size is default to None, which overwrites the default value in SP connector.


Uncaught TypeError: callback is not a function

[Enter steps to reproduce:]

...
...

Atom: 1.16.0 x64
Electron: 1.3.13
OS: Windows 7
Thrown From: imdone-atom package 2.2.3
Stack Trace
Uncaught TypeError: callback is not a function
At C:\Users\***\.atom\packages\imdone-atom\node_modules\async\lib\async.js:649

TypeError: callback is not a function
    at /packages/imdone-atom/node_modules/async/lib/async.js:649:28
    at /packages/imdone-atom/lib/services/imdoneio-client.coffee:54:22
    at /packages/imdone-atom/lib/services/imdoneio-client.coffee:117:14
    at /packages/imdone-atom/lib/services/imdoneio-client.coffee:182:14
    at /packages/imdone-atom/node_modules/nedb/lib/executor.js:29:17)
    at Cursor.execFn (/packages/imdone-atom/node_modules/nedb/lib/datastore.js:520:14)
    at callback (/packages/imdone-atom/node_modules/nedb/lib/cursor.js:126:19)
    at /packages/imdone-atom/node_modules/nedb/lib/cursor.js:193:12
    at /packages/imdone-atom/node_modules/nedb/lib/datastore.js:329:14
    at Object.async.eachSeries (/packages/imdone-atom/node_modules/async/lib/async.js:130:20)
    at /packages/imdone-atom/node_modules/nedb/lib/datastore.js:323:11
    at fn (/packages/imdone-atom/node_modules/async/lib/async.js:582:34)
    at /packages/imdone-atom/node_modules/async/lib/async.js:498:34)
    at runCallback (timers.js:574:20)
    at tryOnImmediate (timers.js:554:5)
    at processImmediate [as _immediateCallback] (timers.js:533:5)

Commands
     -0:37 tree-view:show (atom-workspace.workspace.scrollbars-visible-always.theme-solarized-dark-syntax.theme-one-dark-ui)

Non-Core Packages
atom-django 0.3.2
incremental-search 5.2.1
language-htaccess 0.1.1
language-ini 1.19.0
pigments 0.39.1
script 3.14.1
synced-sidebar 0.4.3
autoclose-tags 0.2.1
autocomplete-bash-builtins 0.3.4
autocomplete-python 1.8.30
busy-signal 1.2.0
color-picker 2.2.5
d3 4.7.4
django-atom 0.2.4
file-icons 2.0.13
fonts 2.0.0
git-log 0.4.1
git-time-machine 1.5.9
highlight-line 0.12.0
highlight-selected 0.12.0
imdone-atom 2.2.3
intentions 1.1.2
linter 1.11.4
linter-pylint 1.2.2
linter-ui-default 0.0.3
minimap 4.26.8
minimap-highlight-selected 4.5.0
minimap-pigments 0.2.2
minimap-split-diff 0.3.7
python-tools 0.6.9
remote-edit 1.8.24
split-diff 1.3.0
symbols-tree-view 0.13.2
tree-view-search-bar 0.1.3

Still getting this error?  Can you provide a way to reproduce?


Nice way to use apigility-doctrine HAL entity return in an RPC service

Is there a nice way of returning a HAL Doctrine Entity in an RPC Service?

Sure thing!
I suggest you have a look at the documentation ;)

Closing issue, unless you have further questions.

Ja, but I can't get it to work with doctrine entities.

Would you be able to detail a bit?
Maybe share a piece of code from your RPC controller?

use ZF\Hal\Entity as HalEntity;

uploadAction(){
        /* upload $path  */
        $media = new \Db\Entity\Media;
        $media->setPath($path);
        $this->em->persist($media);
        $this->em->flush();
        // return array(
        //     'id' => $media->getId(),
        //     'path' => $media->getPath()
        // );
        return array('payload' => new HalEntity($media, $media->getId()));
}

payload has to be passed as a parameter of a ZF\ContentNegotiation\ViewModel instance, as detailed in the documentation (second block of code)
use ZF\Hal\Entity as HalEntity;
use ZF\ContentNegotiation\ViewModel;

public function uploadAction(){
        /* upload $path  */
        $media = new \Db\Entity\Media;
        $media->setPath($path);
        $this->em->persist($media);
        $this->em->flush();

        return new ViewModel([
            'payload' => new HalEntity($media, $media->getId())
        ]);
}

Sadly already tried that as well. :-(

What have you tried that is supposed to work (your example would not)?
What is the result of your code?

Please give as much information as possible, so that we can be helpful. Thank you.

It simply returns a empty {}
Should't there be a easy way to utilize ZF\Apigility\Doctrine\Server\Resource\DoctrineResource to hydrate the Object into HAL in an RPC?

@jensstalder set the content negotiation to haljson
    'zf-content-negotiation' => array(
        'controllers' => array(
            'ModuleName\\V1\\Rpc\\DoRpc\\Controller' => 'HalJson',
        ),

ZF\Apigility\Doctrine\Server\Resource\DoctrineResource is not responsible for hydrating entities. ZF\Hal is. So what is your content-negotiation configuration?

Oh wow! Sorry ^^. that worked like a charm.

Sorry for the rookie mistake...

@TomHAnderson thx for bringing it 10 seconds before me!
@jensstalder That's OK! Glad it worked out!

@jensstalder Documentation (again) at the very bottom! #RTFM :)


Register Correct Plugin Name and Update Roku-client Dependency to v4.0.0

@JarekToro, This is what is logging in Debug mode, last PR registered wrong plugin name.
This will fix that!
Plugin 'homebridge-roku-tv-plugin' tried to register with an incorrect plugin identifier: 'homebridge-roku-tv'. Please report this to the developer!

@JarekToro anyway we can get this merged?

Apologies, Hectic week. Thanks for the PR

Understandable @JarekToro Thanks for merging!


[GIF Search] Favorites and/or recents sometimes get deleted

Extension – GIF Search
Author: @josephschmitt
Description
I noticed that sometimes my favorites / recents were just…gone. After investigating, I noticed a few places where an exception is caught, and as a result, the extension calls clear, which… clears all recents or favorites. This makes it hard to use the favorites feature, as a failed API call could result in them being gone. 😅
Steps To Reproduce

Open Search for GIFs
Select Giphy in the dropdown (though I'm guessing it'll work with the other services, too)
Make sure you have some gifs in "recents" and "favorites"
Press esc to exit to the root search
Open Search for GIFs
You might see an error toast. If you don't, repeat steps 4-5 until you do. This can take a while - sometimes it happens on the first try, other times I had to repeat steps 4-5 for what felt like hundreds of times 😅

I added a bunch of console.logs to all callsites of await clear() and, in my case, I was running into this every single time.

The output was:
11:46:08.322 clearing faves, because: /Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/fetch-error.ts:5
        super(message)
        ^

Error: fetch failed
    at FetchError5 (/Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/fetch-error.ts:5:9)
    at Object.<anonymous> (/Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/request.ts:66:30)
    at step (/Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/fetch-error.ts:11:16)
    at Object.throw (/Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/fetch-error.ts:11:16)
    at rejected (/Users/sorin/Sandbox/raycast/extensions/extensions/gif-search/node_modules/@giphy/js-fetch-api/src/fetch-error.ts:11:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
  status: 0,
  statusText: ''
}

The current behavior
When there's an error fetching the user's favorites and / or recents, their LocalStorage entries are deleted.
The expected behavior
When there's an error fetching the user's favorites and / or recents, their LocalStorage entries are kept so next time the extension is loaded they can (hopefully) be displayed.
Raycast version
Version: 1.38.3

Hmm, I see your point. I think my original reasoning was I didn't want you to get into a state of corrupted fav's. But maybe that's too aggressive. I could maybe add a context menu option for clearing out favs if things go wrong? Wdyt?

I think my original reasoning was I didn't want you to get into a state of corrupted fav's. But maybe that's too aggressive. I could maybe add a context menu option for clearing out favs if things go wrong? Wdyt?

Do we need to clear faves? 🤔 I would just not show them in that case; and if a user tries to add a new fave in this situation, pop a toast informing them why that can't be done, and offering to retry fetching them before. Or something to that effect. 😅


Mac wallet crash - v12.2.4

Hello,
I'm trying to install the mac version (12.2.4) of the wallet on Mojave. But after installing the app crashes when i open it. Is there a way around this?
Termination Reason:    DYLD, [0x1] Library missing

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: @loader_path/libboost_system-mt.dylib
  Referenced from: /Applications/Absolute-Qt.app/Contents/Frameworks/libboost_thread-mt.dylib
  Reason: image not found```

fixed in v12.2.5


Delete_Kyma_Resource step does not complete properly after suspension

Description
In the scenario:

provisioning
suspension
deprovisioning
Delete_Kyma_Resource step is ended prematurely without failure, so it is not completed and marked as logically deleted with non-empty list of not completed steps.

The reason is that we calculate name of resource to be deleted based on runtimeID and for suspended instances runtimeID is empty.
Expected result
In above-mentioned scenario we execute and complete the step.
Actual result
We log error and mark step as succeeded but not completed (step is added to executedButNotCompleted array.
Steps to reproduce

provision
suspend
deprovision

https://github.com/kyma-project/control-plane/pull/2513


Added company from my past internship

Great place to work

Thanks for the PR! Could you put AutomatedInsights above Automattic please? I want to maintain alphabetical order.

All set

Merged in! Thank you so much for your contribution :)


fix: startup was blocked for multiple minutes if the envoy was offline

The retry was too broad and too frequent. We should instead raise and let HA retry so startup can proceed

Thanks for the 👀


Bump version of golang to 1.19

Throw 1.19 into the mix!
Signed-off-by: Davanum Srinivas<EMAIL_ADDRESS>
What type of PR is this?
/kind test

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:
/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind test
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Release note:
NONE

/assign @nikhita @MadhavJivrajani


Don't allow downloaded videos to be NEW in subscriptions

The Issue
Firstly, this is a relatively minor hiccup that occurs during upgrades and when I switch between stable and development versions. The app gets confused about which videos from subscriptions are unread, and usually marks many as unread even though I have seen them before and downloaded most of them.
Steps to Reproduce

Use the stable release of LBRY and subscribe to stuff
Switch to a development version from the repo
Go to the subscriptions tab

Expected Behavior
Ideally, unread vs. read status should persist when you change versions. Failing that, downloaded content (shown with the folder icon) should never be counted as unread.
Actual Behavior
Videos you have in fact seen are now NEW in the subscriptions section - even ones that the app recognises as having been downloaded!
Suggested Solutions
Make downloaded imply read.
System Configuration
{
  "jsonrpc": "2.0",
  "result": {
    "build": "release",
    "desktop": "XFCE",
    "distro": {
      "codename": "Illyria",
      "id": "manjaro",
      "like": "arch",
      "version": "18.0.3",
      "version_parts": {
        "build_number": "3",
        "major": "18",
        "minor": "0"
      }
    },
    "lbrynet_version": "0.32.3",
    "lbryschema_version": "0.0.16",
    "os_release": "4.19.24-1-MANJARO",
    "os_system": "Linux",
    "platform": "Linux-4.19.24-1-MANJARO-x86_64-with-arch-Manjaro-Linux",
    "processor": "",
    "python_version": "3.7.1"
  }
}

Hey Brendon, thanks for the issue. When you switch between Dev and prod modes, the local data directory is different which is why you see 2 different views of the content. There's not much you can do about this.
As far as the downloaded showing unread - we still want this to be unread until you actually go into the file. You still want to know what's new even though it auto downloaded.


Udpate currency pairs list

Based on api/3/info

The CI error is due to monkey-patch allowing any version of active-support.
Active support now only works on Ruby >= 2.2.2.
Two solution here:

Dropping support for Ruby < 2.2.2
Put a max version on active-support, which will drop compatibility with Rails >= 5

Thanks!
I've built v0.5.5 that has this merged in.


No such module SwiftLocation - Xcode 9

Hi,
I have an issue with using SwiftLocation Pod in my recently updated Xcode9. I get a No such module error....
I've added the SwiftLocation.framework also. but it appears 'disabled' in build settings.
Any know issues with Xcode 9?

Thank you for your contribution.
A new rewritten version is available both on master and CocoaPods (marked as 3.0.0-beta). It requires iOS9 and Swift 4.
If you encounter any other problem feel free to open an issue; I'll close because with the new version its now invalid.


session data clean up based on the EXPIRY_TIME

Is your suggestion related to an experience ? Please describe.
In the previous scripts, session data was cleaned up using the CREATED TIME and data was cleared after 14 days of the creation. Hence, old data might stay in the DB for longer time than it should be. The proposed solution is to clear the session data after 2 hours of EXPIRY_TIME.
Describe the improvement
Set session data clean up based on EXPIRY_TIME. And after 2 hours of expiry, it's ready to be cleaned.

This note can be removed from the master brach; https://github.com/wso2/product-is/issues/12803

This note can be removed from the docs; #12803 and update the note This script clears session data that are older than the last 14 days

Doc update will be done in https://github.com/wso2/product-is/issues/14865


bulkfilechanger: Add version 1.70

https://scoop-docs.now.sh/apps/?query=bulkfilechanger
https://github.com/MCOfficer/scoop-nirsoft/blob/master/bucket/bulkfilechanger.json

nice, i did not knew about that scoop-nirsoft bucket!


Months names in English instead of my language

Hello seehase.
Thank you for your improvement of NeoWX skin for Weewx! I've updated my Weewx installation, translated string in history.html.tmpl but months names abbreviations are still generated in English. How/where can I change them?

Have you deleted the rendered HTML file and re-generated the reports?
Month/day, etc. names for WeeWX are actually derived from the host/server operating system, not WeeWX itself; and certainly not the skin. So you will need to change the locale/i18n setting to your locale on the server itself, if it is not already,

Yes, I've removed all files from /var/www/html/weewx. Didn't re-generated reports because Weewx does it on every run (I think so).
I got my locale set, it's visible in Weewx log (OS name, Python version etc.).

OK, I got the solution. First I have done things you recommend - stopped Weewx, cleared WWW directory, re-created reports, checked locale settings (they were perfectly correct - locale -k LC_TIME has proven that month names are translated), finally started Weewx again. But it failed, month names are still in English.
So I looked into the skin's code and found it - in skin.conf :) There is a section named [HistoryReport] with monthnames directive. I had to translate it - 30 seconds of work - and everything is working as expected.
:)

Thanks for help. Problem is now solved so I close the issue.

@stalkerGH awesome! Nice work. Cheers 🥂


Wrongly formating "compatible release" clause

diff --git a/setup.cfg b/setup.cfg
index efc3a0f..662e52c 100644
--- a/setup.cfg
+++ b/setup.cfg
@@ -43,15 +43,15 @@ console_scripts =
 [options.extras_require]
 doc =
     furo
-    sphinx~=3.0
-    sphinx-autodoc-typehints~=1.10
-    sphinxcontrib-autoprogram~=0.1.0
+    sphinx-autodoc-typehints~~=1.10
+    sphinxcontrib-autoprogram~~=0.1.0
+    sphinx~~=3.0
 test =
-    filelock~=3.0
+    filelock~~=3.0
     pytest>=5,<=6
-    pytest-cov~=2.0
+    pytest-cov~~=2.0
     pytest-mock>=2,<=3
-    pytest-xdist~=1.34
+    pytest-xdist~~=1.34
 typing =
     mypy==0.790
     typing-extensions>=<IP_ADDRESS>

https://www.python.org/dev/peps/pep-0440/#compatible-release

@asottile sorry, I misclicked and it created the issue before I typed anything.

oic, sorry for assuming it's spam -- there's a bunch of spam going around today for some reason

No worries :blush:

Thanks, would it be possible to do a release? Or should I wait a bit?

it was already released by the time you made your comment?

I didn't notice, sorry :blush:


Abstract suggestion: Overall data model documentation

Currently, the specification seems to be defined in a very piecemeal-y manner; each part of the API individually specifies what data it expects, what data it returns, and so on.
This makes it somewhat difficult to build well-architected-upfront homeservers and clients, as you'd have to read pretty much the entire specification to build up a comprehensive (mental) model of the different kinds of 'entities' in a Matrix system, and how they relate to each other.
I'd suggest adding some sort of high-level data model documentation, that describes in a relational manner what kind of different data types (users, messages, access tokens, etc.) exist in a Matrix system, and how they relate to other data types. This would still be an abstract model, leaving it up to applications how to implement and persist it exactly.
For example, the kind of model I'm thinking of might be something like this (represented as text):

User

username: String
password: String
devices: [Device]
joined_rooms: [Room]

Device

user: User
access_token: String
display_name: String

Room

name: String
users: [User]
messages: [Message]

Message

body: String
sender: User
recipient: User | Room
parents: [Message]

That's just a simple example, of course (and most likely wrong - I haven't actually read the entire spec yet!), but it hopefully illustrates what I mean. It doesn't necessarily need to be a text representation either, if eg. a visual representation could make it easier to understand.
This data model also wouldn't need to cover 'ephemeral' API data (like eg. the inhibit_login parameter in the /register endpoint), only the persistent data that a developer would need to model into their application architecture.
(This wouldn't have to be part of the specification either, it could act as a non-normative guide separate from it.)

I believe this is what https://matrix.org/docs/spec/#architecture attempts to document - what exactly is missing there?

Hmm. As far as I understand it, that only describes some parts of the data model; specifically those parts necessary for understanding how Matrix itself works. It's certainly useful information, but not comprehensive enough to define the full data model.
As a concrete (if a bit blunt) example: you couldn't fully model your relational database off the descriptions there.
Some specific examples of information deficiencies there:

'Access tokens' (for authentication purposes) are definitely a separate entity, relationally speaking, but are not mentioned in that architectural overview.
The information there is descriptive, not structural; it doesn't contain a scannable listing of different 'fields' within an entity, for example, I would have to infer that from the text (and keep my own notes on that). That's helpful for understanding the protocol, but not for modelling one's own data layer. Hence my example in the original post, which is more of a linear, scannable list of data fields.
It's unclear how different entities relate to each other, and in what quantities. Does an event have a sender and a recipient? Or can it have multiple recipients? Or even multiple senders? Are users joined directly to rooms, or do you need an intermediate 'presence' representation to encode their role within a room? And so on.
What data fields does an 'event' have anyway? Can I represent any kind of message event with a single 'body' field? Or do I need to handle different data structures?

In short: I think the architecture section should remain structured as it currently is, as it (quite effectively!) communicates the overall protocol structure. The more boring data model listing I'm suggesting would be in addition to that, to aid in modeling one's own data persistence layer.


when we can use this network to train our dataset?

Hello author, when i read your paper , i think your work is very meaningful. I want to try out the performance of your network on other datasets, comparing ssd and yolov3.

Me too


Fix gelu_backward

Apparently gelu_backward doesn't broadcast well on mkldnn which is why we were seeing the other error

This feels like something that should be fixed in PyTorch 🤔


chore: Update flags to include long-form options for case

Description
Addition of long options for the existing -i and +i flags.
The rationale behind long options is their self-descriptive nature. Currently, these flags are outliers as they do not have corresponding long options. Introducing them would improve consistency across command-line flags.

Thanks!


Can't get flashed session's messages when handled exception

Hi !
Considering this code:
  async handle (error, { response, session }) {
    if (error.name === 'InvalidSessionException') {
      session.withErrors({session: error.message}).flashAll()
      await session.commit()
      Logger.info(session.all())
      return response.route('signin')
    }

    return super.handle(...arguments)
  }

  async report (error, { request }) {
    Logger.error(`${error.status} ${error.message} on ${request.url()}`)
  }

This is what i have on the console from the logger:
error: 401 E_INVALID_SESSION: Invalid session on /start
info: undefined {"csrf-secret":"GX94AXL5jU6tgV4OCH1V1hnD","__flash__":{"errors":{"session":"E_INVALID_SESSION: Invalid session"}}}

That said i have a null value when try to access the flashed message:
@if(hasErrorFor('session'))

{{getErrorFor('session')}}

@endif

Package version
4.0.0 migrated to 4.1.0
Node.js and npm version
8.11.3

Hey @tnga! 👋
Could you please create a small repository with the minimum amount of code to reproduce?

someone look at #1058

Closing since no answer from issue reporter.


Added external link to substantiate js waypoint

Added a link to a StackoverFlow answer to provide explanation of the formula used in the 'Create a JavaScript Slot Machine' basic javascript waypoint (seeds and renders successfully)
closes #2595

@awesomeaniruddh IMHO this link also needs to be in waypoint "Generate Random Whole Numbers within a Range".

Done!

Wait, don't merge yet, need to amend the commit!

k, can be merged now :D

@awesomeaniruddh remove the dot at the end of: "(an explanation of the formula can be found here**.**):"

yeh, done. Need to start wearing my glasses.

@awesomeaniruddh I'm sorry but you also need to remove backslashes at the end of your links.

The backslashes are there to escape the " character

Oh, of course, sorry, verified and merged, thanks.


How to find out the https proxy？

It seems that there is no distinction between http and https at the moment.

You're correct. I'll add a test for HTTPS proxies during the following days.

We are looking forward to this new function. :)

Has this been done yet? Looking forward to it!


IE11 fix for preact renderer

Requirements

[x] Read the
contribution guidelines.
[ ] Wrote tests.
[ ] Updated docs and upgrade instructions, if necessary.
[ ] Updated TS definitions, if necessary.

Rationale
Preact Renderer does not work in IE11.
Implementation
children is not supported in IE11, falling back to childNodes instead.

Thanks for the PR! I just left a comment. Would like to discuss prior to merging, if that's alright.

So weird. I could have sworn children was available and it seems it is: https://developer.mozilla.org/en-US/docs/Web/API/ParentNode/children. I'll merge this for now to get you working and push a release but it would be good to see what the core issue was.

pushed 0.2.1

I guess it was because of this weird issue: https://stackoverflow.com/questions/39288373/document-children-vs-document-childnodes


sampler buffer is put into resources.sampled_images

sampler buffer is put into resources.sampled_images

This is expected. sampledBuffer is a deprecated construct that is combined with sampler. A samplerBuffer is technically an image, it just has a buffer dimension. To get separate_image here, you need textureBuffer.

thanks


Fix documentation- and contruibuting-link in Readme of Admin

1. Why is this change necessary?
Because your links in the Admin-Readme are outdated.
2. What does this change do, exactly?
It uses new links.
3. Describe each step to reproduce the issue or behaviour.
This is a Readme-File. So I did not write a automated test.
4. Please link to the relevant issues (if any).
None
5. Checklist
Bruh!

Thanks for your contribution, your PR was merged! :tada: :blue_heart:


re-add testing package to pydoc

r: @TheNeuralBit

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

hm I suppose it's just a matter of regenerating the pydocs and running a PR against the website, huh?

oh yeah great point, we don't need to backport. we might want to use (or at least reference) the relevant portion of the build_release_candidate script for that: https://github.com/apache/beam/blob/master/release/src/main/scripts/build_release_candidate.sh#L356-L376

what are the chances that @y1chi could help us run this script to update older releases? :sweat_smile:

what are the chances that @y1chi could help us run this script to update older releases? 😅

I can try.


Fix weird keyboard navigation bug

This fixes a bug where if you type a backspace in a textarea and then click right or left arrow key the app navigates to /{username} rather than the next/previous NFT id. This was because it was registering the Backspace key and "queuing" it up for when the next key press was registered.
https://user-images.githubusercontent.com/13339581/164838867-8fc6a483-f05c-4c10-a914-ae4149453831.mov
Fixed by resetting keyPressed to false when key is released. Also, moved the activeEl declaration outside of the useEffect so that we listen for changes in focused element.

Also, while you're here:
Should we be more explicit and only disable accidental navigation if the user is focused on a textarea? Currently we require the body to be focused. This means that if a user clicked a button ("Additional Information" etc) they also could not navigate until they click on the body again.
I just couldn't think if there were other focused elements that might trigger accidental navigation... So figured this was a bit safer.


Remove rootFolder from AZS config

For a few reasons:

Simplify the config
Match the folder structure for other providers, which are only 2 levels deep not 3 (in front50.yml, s3.bucket == azs.storageAccountName and s3.rootFolder == azs.storageContainerName)
Fix a bug where the 'last_modified' files were stored at the container level and everything else was stored at the (now removed) rootFolder level. Now everything is at the container level.

@scotmoor @rguthriemsft @duftler @ewiseblatt PTAL
We realize this would be a breaking change for existing users of azure storage, but want to fix while it's new and before 1.0. When this and it's companion spinnaker PR https://github.com/spinnaker/spinnaker/pull/1432 are released, I will post in slack telling any possible users to follow the migration steps so that their data is not lost (download all metadata, update & restart front50, upload new metadata)

The naming between providers is confusing, so I'll give an example. Here is a path for an application object before this change:
spinnakervpqhwmi3ntc2e/spinnaker/front50/applications/sample/application-metadata.json
And here is the path after my change:
spinnakervpqhwmi3ntc2e/front50/applications/sample/application-metadata.json
I should've clarified about the levels. I was not counting "type/object container/object data" since that stuff is cloud agnostic (i.e. "applications/sample/application-metadata.json")

Thanks. Makes total sense now.
On Thu, Feb 16, 2017 at 3:27 PM, Eric Jizba<EMAIL_ADDRESS>wrote:

The naming between providers is confusing, so I'll give an example. Here
is a path for an application object before this change:
spinnakervpqhwmi3ntc2e/spinnaker/front50/applications/sample/
application-metadata.json
And here is the path after my change:
spinnakervpqhwmi3ntc2e/front50/applications/sample/
application-metadata.json
I should've clarified about the levels. I was not counting "type/object
container/object data" since that stuff is cloud agnostic (i.e.
"applications/sample/application-metadata.json")
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spinnaker/front50/pull/199#issuecomment-280449429,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEKkGOKIP_USfWy9xr3YG9jOOcJRIJf-ks5rdLEZgaJpZM4MDdGX
.

except I missed where the "sample" directory is when I was looking at your
PR implementation.
On Thu, Feb 16, 2017 at 3:31 PM, Eric Wiseblatt<EMAIL_ADDRESS>wrote:

Thanks. Makes total sense now.
On Thu, Feb 16, 2017 at 3:27 PM, Eric Jizba<EMAIL_ADDRESS>wrote:

The naming between providers is confusing, so I'll give an example. Here
is a path for an application object before this change:
spinnakervpqhwmi3ntc2e/spinnaker/front50/applications/
sample/application-metadata.json
And here is the path after my change:
spinnakervpqhwmi3ntc2e/front50/applications/sample/applicati
on-metadata.json
I should've clarified about the levels. I was not counting "type/object
container/object data" since that stuff is cloud agnostic (i.e.
"applications/sample/application-metadata.json")
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spinnaker/front50/pull/199#issuecomment-280449429,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEKkGOKIP_USfWy9xr3YG9jOOcJRIJf-ks5rdLEZgaJpZM4MDdGX
.


Feature/coverage

Completed coverage ci

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


Reproducibility Issue

I am unable to reproduce the results for CIFAR that you have achieved. The final validation accuracy is around 30% while train accuracy is at 60%.
Im also curious about the loss value during the training of the feature model. Even after 100 epochs, the loss value remains approx. stagnant at 0.0155.  Is this expected?

I'll do a run from scratch when I can access my gpus again net week and report back.

@rsk2327 You are right. We are looking into it. Thanks!

@rsk2327 You are right. We are looking into it. Thanks!

Has this been resolved?

Has this been resolved?

It has been resolved with the removal of LARS, the results in the readme have been updated.

It has been resolved with the removal of LARS, the results in the readme have been updated.

Hi @mdiephuis ,
Is the above problem fixed, because i am facing similar problem when i tried with same training procedure that is mentioned in README
Issue 01:

Script used  - train_classifier.py
I am able to achieve Batch accuracy of ~31% for Training and ~37% for validation and training stopped at 199th epoch
Issue 02:

Script used  - train_features.py
I am able to achieve Loss of ~23% for Training and ~22% for validation and training stopped at 149th epoch
Can you please help me with solution or is this the expected issue. even i am unable to reproduce the results for CIFAR that you have achieved so far


show death rate by age

**Is you
New Microsoft Word Document.docx
replicate as in new case by age histogram by age to also by death rate

The mapping of demographics in Deceased cases are quite low. However, will keep this marked in Deep-dive as a potential idea.

https://github.com/covid19india/covid19india-react/pull/978 is already made !

Addressed by #967


v2.0.4 completely broke the plugin for me

I am looking at jason file and I see two set of config now, and logs show errors. tried to remove one of the config from jason, still fails.
first error
No plugin was found for the accessory "ct200" in your config.json. Please make sure the corresponding plugin is installed correctly.
second error
TypeError: Cannot read properties of undefined (reading 'forEach')
at CT200Platform.discoverDevices (/usr/lib/node_modules/homebridge-ct200/src/platform.ts:200:30)
at HomebridgeAPI. (/usr/lib/node_modules/homebridge-ct200/src/platform.ts:183:18)
at HomebridgeAPI.emit (node:events:402:35)
at HomebridgeAPI.signalFinished (/usr/lib/node_modules/homebridge/src/api.ts:275:10)
at Server.start (/usr/lib/node_modules/homebridge/src/server.ts:173:14)

ok removes old "accessory" from jason and kept the new "platform" also zone is mandatory now I think, so added zone as well and it is working again. It is a bit tricky that you have changed type from accessory to platform, many will not be able to edit this on jason file, which is very sensitive to touch :) you might want to ad to do wiki for help. Thanks a lot for the good work!
I am about to get some radiator valves goes with ct200, would this be added smoothly with this plugin as well?, i think I have to make zones for each correct?

Everything from V2.0.0 upwards is a complete rewrite, which changes the config file format.
The new version has support for multiple devices. If the radiator valves use the same API as the CT200, then yes, most likely it will work.
Each 'zone' is a separate thermostat. So, if you want to control all the temperatures separately (and the bosch app allows it), you have to make zone for each.


Enable sub-second precision on timestamp output

With fluentd 0.14 supporting sub-second time fields, I'd like to get the loggly plugin to support outputting those.
Updated: I've tested this in my cluster with success.  I'm seeing milliseconds in loggly by setting time_precision_digits to 3.

This change is

Worth looking at https://github.com/mururu/fluent-plugin-elasticsearch/commit/e671e36d33f5c196f45f8eedfb237dcd16ce01ec where I found a reference for updating the formatter.

Thanks, will look into this as soon as possible.

0.14 is not yet released so this won´t go into a release perhaps a pre.
Did some testing and I don't get any sub-secounds time stamp in loggly. I get 3 trailing zeros but no values. Did at test log out of time.nsec in function write and value was 0.
Let me know your setup if it's working for you.

I am using this successfully to get accurate sub-second timestamps with
0.14 in production.  My input type is json, and I'm outputting to loggly.
Definitely working for me!
On Apr 4, 2016 2:41 PM, "Patrik Antonsson"<EMAIL_ADDRESS>wrote:

0.14 is not yet released so this won´t go into a release perhaps a pre.
Did some testing and I don't get any sub-secounds time stamp in loggly. I
get 3 trailing zeros but no values. Did at test log out of time.nsec in
function write and value was 0.
Let me know your setup if it's working for you.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/patant/fluent-plugin-loggly/pull/16#issuecomment-205510138

Do you have more info on your setup @chrisleck ? Like os and ruby version.

Sure.  I'm running in a docker container based on debian:latest.  Running Ruby 2.3.0.
Dockerfile:
FROM debian:latest

// Ensure there are enough file descriptors for running Fluentd.
RUN ulimit -n 65536

// Disable prompts from apt.
ENV DEBIAN_FRONTEND noninteractive

// Install prerequisites, ruby, and fluentd.

COPY fluentd.conf ./fluentd/fluentd.conf

// Copy the modified log output plugin - temporary until https://github.com/patant/fluent-plugin-loggly/pull/16
// is merged and pushed.  At that time, also remove the net-http-persistent and yajl-ruby dependencies above in
// favor of the official plugin (fluent-plugin-loggly).
COPY out_loggly_buffered.rb /etc/fluent/plugin/out_loggly_buffered.rb

// Copy the entrypoint script
COPY run.sh ./run.sh

// Execute the entrypoint
CMD bash -c "./run.sh"

fluentd.conf:
// Do not directly collect fluentd's own logs to avoid infinite loops.
<match fluent.**>
  type null
</match>

// Example:
// {"log":"[info:2016-02-16T16:04:05.930-08:00] Some log text here\n","stream":"stdout","time":"2016-02-17T00:04:05.931087621Z"}
<source>
  type tail
  path /var/log/containers/*.log
  pos_file /var/log/fluent-containers.log.pos
  tag kubernetes.*
  read_from_head true
  format json
  time_key time
  time_format %Y-%m-%dT%H:%M:%S.%NZ
</source>

// Replace unicode "line separator" characters with newlines
// This is used to work around docker logs treating each line of log output as a separate log entry.
<filter kubernetes.**>
  type record_transformer
  enable_ruby
  <record>
    log ${log.force_encoding('UTF-8').gsub("\u2028".force_encoding('UTF-8'), "\n")}
  </record>
</filter>

// Add Kubernetes metadata to each record
<filter kubernetes.**>
  type kubernetes_metadata
</filter>

<match kubernetes.**>
   type loggly_buffered
   loggly_url https://logs-01.loggly.com/bulk/${LOGGLY_TOKEN}
   output_include_time true
   time_precision_digits 3

   # Set the chunk limit the same as for fluentd-gcp.
   buffer_chunk_limit 2M
   # Cap buffer memory usage to 2MiB/chunk * 32 chunks = 64 MiB
   buffer_queue_limit 16
   # Flush to loggly every 10 seconds
   flush_interval 10s
   # Never wait longer than 5 minutes between retries.
   max_retry_wait 30
   # Disable the limit on the number of retries (retry forever).
   disable_retry_limit
</match>

Friendly ping for review...

Released as a pre now.
https://rubygems.org/gems/fluent-plugin-loggly/versions/0.1.0.pre

Any word on pulling this in for real?  The code changes have been working for me in production for months now :)


Outro transitions inside conditional blocks

Via SO
{{#if a}}

{{a}}

{{/if a}}

{{#if b !== null}}

{{b}}

{{/if b}}

Fiddle: http://jsfiddle.net/c3y5qr86/2/.

Just realized this will probably work in edge, and indeed, it does.


wast: Add exnref, try_table, and throw_ref

These types and instructions are part of the exception handling rework tracked in (https://github.com/WebAssembly/exception-handling/issues/281).

Just did the rustfmt, but hold up on merging there's been some recent bikeshedding of the binary to work through. I will probably update again.

@alexcrichton Okay, this should be good to go now.

Would you like a crates.io release for this?

Sure thing, doing that in https://github.com/bytecodealliance/wasm-tools/pull/1227


Revert #37 (support for extra rack middleware initialization args)

#37 turned out to be necessitated only by some misbehaviour with the middleware mounting inside Hanami's new router (see https://github.com/hanami/hanami/pull/1046).
We should revert it because it is unnecessary to support extra initialization args, and in a way, they may be misleading to users of the middleware (suggesting that additional args could be passed in the first place, which is not the case).

This seems outdated. Closing.


NIO1 Work around Xcode 13 GM SDK issues

Motivation:
This is a backport of #1956.
Xcode 13 GM shipped with a Swift overlay for libsystem in macOS that marked free's first argument as non-nullable. This leads to an awkward breakage for us, because we're trying to hold a reference to free as a function pointer, and to do that we had an explicit type annotation.
We'd like to keep NIO compiling in Xcode 13 GM.
Modifications:

Defined the free function as a thunk that passes through to the underlying OS free call, but takes its first argument as non-nullable.

Result:
Should compile on the Xcode 13 GM again.

@swift-nio-bot test this please


Can't load configurations dynamically when application is built as a jar

Not sure if this is a feature of the library or just something that's unclear to me, but essentially, I'm trying to build my application into a jar using sbt assembly, but not include my application.conf in the jar (so that qa/production can have different configurations). I've tried putting the application.conf in the same directory as the jar, as well as various other directory structures that seemed like they could potentially work (src/main/resources, etc.), but haven't found a way to get this to work.

Solution is to specify -Dconfig.file, whoops


US/Central Time 1 Hour Off

The following line of code gives the value 18 which is WRONG. 00:00 UTC is 19:00 US/Central NOT 18:00 US/Central.
formatToTimeZone(new Date(Date.UTC(0, 0, 0, 0, 0, 0)), 'HH', {
  timeZone: 'US/Central'
});

Ok, maybe it's because I went too far back in time. I set the year to 2019 and it seems to work as expected.
formatToTimeZone(new Date(Date.UTC(2019, 0, 0, 0, 0, 0)), 'HH', {
  timeZone: 'US/Central'
});


facing the issue during running

found the following error:
ValueError: numpy.ndarray size changed, may indicate binary incompatibility. Expected 96 from C header, got 88 from PyObject

The issue should be resolved with the latest version. Please update the package using pip install 'k-means-constrained>=0.7.2' and report back

I'm closing this for now. Let me know if you require more assistance


Modin not fully utilize CPU

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Ubuntu 18.04
Linux ip-172-30-0-250 4.4.0-1095-aws #106-Ubuntu SMP Wed Sep 18 13:33:48 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Modin installed from (source or binary):
binary
Modin version:
0.6.1
Python version:
3.7
Exact command to reproduce:
Code is run from Jupyter notebook

Describe the problem
It always happen that only one CPU getting used fully.

What is super weird is exact the same code running a bigger machine (32 CPUS) will be parallelized just fine.
Source code / logs
import modin.pandas as pd
df = pd.read_csv('../data_cleaned/guestbook/storycontributionOct4th.csv',error_bad_lines=False,engine='python', encoding='utf-8')
print(df.shape)
def extract_json (row):
    try:
        jsondata = json.loads(row['DataJSON'])
        row['firstname'] = jsondata.get('Firstname')

        content = jsondata.get('Content')
        row['content'] = content
    except Exception as e:
        raise e
    return row

df4 = df2.apply(extract_json, axis=1)

Hi @thangbn, thanks for the report! I have some follow up questions if you could help me understand a little more:
How long is the utilization this low? Do you know which command was running when the utilization was low? Is it near the beginning or end of the run?
We have some good straggler mitigation techniques internally, so I would definitely like to understand what is happening here.

@devin-petersohn thanks for your reply
the utilization is low since it steps into this line which running the apply func on the DataFrame
df4 = df2.apply(extract_json, axis=1)

and staying low for the next 5 mins, after that I just cancelled the task.
To give you more context: the input file have around 1 million+ rows

Thanks @thangbn, would you be able to provide some sample data? I would like to dig into the utilization problem, but it is difficult without the ability to reproduce the behavior.

@devin sure thing. find the small part extracted from the original file attached.
extract.txt

@devin-petersohn  just found out downgrade to 0.5.4 work just fine

closed as no longer reproduced on 0.6.2


Test: Editor Find History persistence

Refs: #92222

[ ] anyOS @isidorn
[ ] anyOS @Yoyokrazy

Complexity: 2
author: @osortega
Create Issue

Summary
We added find history persistence for the text editor this month. It's enabled by default, but can be disabled via setting editor.find.history. The find history is persisted per workspace when enabled and limited to 100.
Steps to Test:

Open a text editor
Ctrl/CMD+F to search, try a few different keywords
Reload the window
You can still navigate between the keywords in history

Please also test if the behavior makes sense to you when you are using find widgets in multiple editor groups.

Blocked on https://github.com/microsoft/vscode/issues/235102
Though I will mark myself as done, and once that is fixed I am happy to verify that bug and test a bit more.

updated setting from isi's issue (updated in the tpi as well) gave me functional behavior as expected. Works here 👍


[BUG] no-custom-classname rule will not honor the project setting for config

Describe the bug
When I add a project setting like described in the README:
"settings": {
  "tailwindcss": {
    "config": "custom-file"
  }
}

to specify the tailwind config file (in .eslintrc), the no-custom-classname will ignore it.
I can workaround the issue by specifying the rule specific config:
    "tailwindcss/no-custom-classname": [
      "warn",
      {
        // NOTE: There is a bug in the eslint-plugin-tailwindcss
        // library that prevents this rule from seeing the project
        // settings. So until that is fixed, we are forced to specify
        // the config file here.
        //
        // We need to specify the file as an absolute path because
        // eslint runs from the root yarn workspace.
        config: path.join(__dirname, 'tailwind.config.js')
      },

I debugged a little bit and it seems the options of the rule have a default defined.
I think that default shadows the project setting:
https://github.com/francoismassart/eslint-plugin-tailwindcss/blob/be3a82673a915e4cd4f48da1ce258b61a4fa4b7c/lib/util/settings.js#L5-L12
eslint config file or live demo
Let me know if you need further information, I can work to provide one.

I believe this may be happening with all rules as I'm experiencing the same with both classnames-order and no-custom-classname.

@davazp & @isaaccuraErnesto ,
Can you try to provide the path to the config in the shared settings via an absolute path ?
// .eslintrc.js
const path = require("path");

...

"settings": {
  "tailwindcss": {
    "config": path.join(__dirname, "custom-file"),
  }
}

I did try but it doesn't work.  Regardless of what I pass in the project setting,  the rule config's default shadows the project config.

Please provide a demo repository and I'll investigate more 😉

Thanks @francoismassart . I created a sample repository here: https://github.com/davazp/eslint-plugin-tailwindcss-issue-212
You can reproduce it by npm installing it and running npm run lint.
I made a custom file for tailwind config at tailwindcss.custom.js. Then, if you look at the .eslintrc.js:
const path = require('path');

module.exports = {
  plugins: ["tailwindcss"],
  parser: '@typescript-eslint/parser',
  rules: {
    // If we remove the {} options here, it will work. With it, the
    // default for the rule takes over project setting.
    "tailwindcss/no-custom-classname": ["error", {}]
  },
  settings: {
    tailwindcss: {
      config: path.join(__dirname, 'tailwindcss.custom.js')
    }
  }
};

I specify the config. However, the plugin will still think myviolet color is unknown.  If you remove the {} from the rule options, then it works.
I hope this helps!  Let me know if I can do anything else.

@francoismassart I too have tried providing the path to the config file via an absolute path without any luck.

That is caused by the default value set in the meta block of each rule...

@davazp & @isaaccuraErnesto
=> npm i<EMAIL_ADDRESS>-D
Waiting for your feedback(s) 😉

@davazp & @isaaccuraErnesto => npm i<EMAIL_ADDRESS>-D
Waiting for your feedback(s) 😉

The upgrade fixes it for me!   Thanks for the work.

@francoismassart I'm working in a mono-repository having a top .eslintrc and a nested .eslintrc for the react application, but I see no luck in having the tailwindcss/no-custom-classname rule working.
To test I added the following:
    "tailwindcss/no-custom-classname": ["off", {
      "config": "ciao",
      "cssFiles": ["src/*.css", "src/**/*.css"]
    }]

ciao file does not exist but the plugin does not throw so I'm assuming that it's not picking the configuration.
Any advice? I tried to move every dependency in both folder's package.json with no luck.

@damianobarbati please, have you ever resolved it or maybe opened a new issue?


Refresh CLI cheat sheet

Refreshed our CLI cheat sheet. Mainly cosmetic, though once secrets-managers are no more then that section can be fully reworked and updated. The rest looks fine to me.
Pre-requisites
Please ensure you have done the following:

[ ] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[ ] If I have added an integration, I have updated the integrations table and the corresponding website section.
[ ] I have added tests to cover my changes.

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Other (add details above)

I think zenml model-registry is also a new CLI command that shuld be here


Fix to run tests

This PR address a few issues.  As a new user to wdio-vscode-service I ran into a few stumbling blocks while getting up and running, and I think this PR will benefit others.  This PR includes:

Added a launch.json file, so one can debug the tests.
Added a "Contributing" section to README.md, so beginners have a set of instructions on getting started.
Removed the grep property from mochaOpts.  When I ran, I found that the tests weren't actually running.  (see https://github.com/webdriverio-community/wdio-vscode-service/issues/41). Removing this option fixes the issue.
Added some fixes to basic.e2e.ts.  After I got the tests to run, I found there were two tests which were failing, and so I added fixes for the tests as well.

It seems like there are some issues with Chromedriver setup. I am currently on vacation and can check back next week.

Thanks @christian-bromann , yea, let's pick up next week.  It looks like my PR is now failing in CI, and is failing due to the presence of console.log(), however I didn't add any logging, and I didn't turn on this lint setting.  Anyway, let's revisit next week, thanks!

Once #45 is merged we should rebase this PR on top of main.

Cool, sounds good @christian-bromann

@jeffb-sfdc mind updating the branch and rebase it on top of main?

Done, though please look over the changes.  I ran into issues resolving the conflicts using GutHub so I resolved them by hand.


What is the difference between this project and AutoGen?

What is the difference between this project and AutoGen?

This project helps you create agents that use LLMs to run specific functions. AutoGen is a higher level library that helps you coordinate conversations with multiple agents. You could theoretically use both together!


Adernet

If you have a problem launching a live-server, please try following steps:

Make sure you use the right hotkeys. After v2.0.0, the keys became ctrl-alt combination.
Try launching live-server from top menu: Package -> live-server -> Start Server to see if it works.

It's not showing in Package -->Live Server --> Start!  It was working fine yesterday ... the Atom updated and it disappeared and I can't seem to get it back!
Any ideas?


[CHECKLIST] QA Reported BUGS and Design Discrepancies

Overview
The below checklist outlines the various BUGS and design discrepancies discovered during early QA process. These issues will need to be resolved prior to our Alpha launch of the Hubble bridge. To follow the QA test case progress view the Notion document here.
Task Checklist
Quick to address

[x] https://github.com/webb-tools/webb-dapp/issues/903
[x] https://github.com/webb-tools/webb-dapp/issues/834
[x] https://github.com/webb-tools/webb-dapp/issues/868
[x] https://github.com/webb-tools/webb-dapp/issues/899
[x] https://github.com/webb-tools/webb-dapp/issues/874
[x] https://github.com/webb-tools/webb-dapp/issues/697
[x] https://github.com/webb-tools/webb-dapp/issues/875
[x] https://github.com/webb-tools/webb-dapp/issues/860
[x] https://github.com/webb-tools/webb-dapp/issues/845
[x] https://github.com/webb-tools/webb-dapp/issues/843
[x] https://github.com/webb-tools/webb-dapp/issues/839
[x] https://github.com/webb-tools/webb-dapp/issues/841
[x] https://github.com/webb-tools/webb-dapp/issues/836
[x] https://github.com/webb-tools/webb-dapp/issues/882
[x] https://github.com/webb-tools/webb-dapp/issues/889
[x] https://github.com/webb-tools/webb-dapp/issues/892
[x] https://github.com/webb-tools/webb-dapp/issues/900

Functional

[x] https://github.com/webb-tools/webb-dapp/issues/920
[x] https://github.com/webb-tools/webb-dapp/issues/919
[x] https://github.com/webb-tools/webb-dapp/issues/873
[x] https://github.com/webb-tools/webb-dapp/issues/872
[x] https://github.com/webb-tools/webb-dapp/issues/871
[x] https://github.com/webb-tools/webb-dapp/issues/869
[x] https://github.com/webb-tools/webb-dapp/issues/867
[x] https://github.com/webb-tools/webb-dapp/issues/861
[x] https://github.com/webb-tools/webb-dapp/issues/859
[ ] https://github.com/webb-tools/webb-dapp/issues/857
[x] https://github.com/webb-tools/webb-dapp/issues/856
[x] https://github.com/webb-tools/webb-dapp/issues/855
[x] https://github.com/webb-tools/webb-dapp/issues/853
[x] https://github.com/webb-tools/webb-dapp/issues/840
[x] https://github.com/webb-tools/webb-dapp/issues/821
[x] https://github.com/webb-tools/webb-dapp/issues/882
[x] https://github.com/webb-tools/webb-dapp/issues/884
[x] https://github.com/webb-tools/webb-dapp/issues/906

Design

[x] https://github.com/webb-tools/webb-dapp/issues/904
[x] https://github.com/webb-tools/webb-dapp/issues/890
[x] https://github.com/webb-tools/webb-dapp/issues/870
[x] https://github.com/webb-tools/webb-dapp/issues/902
[x] https://github.com/webb-tools/webb-dapp/issues/863
[x] https://github.com/webb-tools/webb-dapp/issues/858
[x] https://github.com/webb-tools/webb-dapp/issues/851
[x] https://github.com/webb-tools/webb-dapp/issues/838
[x] https://github.com/webb-tools/webb-dapp/issues/883
[x] https://github.com/webb-tools/webb-dapp/issues/887
[x] https://github.com/webb-tools/webb-dapp/issues/949

Closing in favour of #948


fix bad google drive link in pet tutorial

closes issue #384

Do you think it'd be possible to put this data on OSF or somewhere else where the half life of the link would be better?

Do you think it'd be possible to put this data on OSF or somewhere else where the half life of the link would be better?

I was planning on putting it into an s3 bucket, but I can do OSF instead.


[lit-element] Declarative event emitters

It would be convenient for ergonomics, documentation, React integration, and transpilers to be able to declare what events an element fires.
We could add a decorator (and static block for plain JS, like properties) that allows this by decorating event handler properties. The decorator would create accessors that use addEventListener under the hood.
TypeScript:
class MyElement extends LitElement {
  @event() onFoo!: (e: FooEvent) => any) | null;

  render() {
    html`<button @click=${this._onButtonClick}>Click Me</button>`;
  }

  _onButtonClick(e) {
    this.dispatchEvent(new FooEvent());
  }
}

interface HTMLElementEventMap {
  'foo': FooEvent;
}

JavaScript:
class MyElement extends LitElement {
  static events = {
    onFoo: {},
  };

  render() {
    html`<button @click=${this._onButtonClick}>Click Me</button>`;
  }

  _onButtonClick(e) {
    this.dispatchEvent(new FooEvent());
  }
}

See some similar previous discussion here: https://github.com/Polymer/lit-element/issues/808

This would really take Lit to the next level IMO. If we could declaratively generate statically typed onFooEvent methods for our own components they really start to feel like first class parts of html. Digging the proposed solutions.

This should be an RFC

Hi All,
I also think some resolution here (might be possible to do via mixin) would be very helpful!
As already mentioned in this thread and previous discussions. I would summarize the main aspects of a solution like this (please let me know if you agree/disagree).

typed dispatch:
To make sure event types are linked with definitive event shapes/interfaces. prevents emission of illegal events.

conciseness/ergonimics:
Obviously the solution should be as transparent as possible

single source of truth:
Redundant annotations that need to be kept in alignment should be avoided (lik ts typings + @fires/@event annotations). This menas, for instance the web component analyzer should be able to pick up the event declarations somehow. It is unclear to me if the decorators proposed here would enable this.

no (or little) runtime overhead:
Since (as opposed to pros) events are only created at runtime they need no permanent field in a component class. To me this is kind of my main gripe with the prop decorator-based solutions proposed here and in the past. Maybe the declaration can be a static field in the component?

enumeration of event(types):
The ability to enumerate the events at runtime + typings would allow to fully automate the creation of react wrappers and probably for angular as well. I guess the requmrent to list events when wrapping WCs stems from the lack of enumerability of the events. Shouldn't a solution to declaring events also solve the this wrapper generation issue?

Below i try to categorize the solution proposed here (prop decorators) according to the criteria above.
A few points are not clear to me.
prop decorators (this thread, here and here)

typed dispatch:
✅ yes

conciseness/ergonimics:
✅ clear

single source of truth:
It is unclear to me if the WC analyzer could pick these decorators up, can someone enlighten me?

no (or little) runtime overhead:
a prop decorator will provision a property for each component instance. for a component which emits many different types of events this is not ideal i think.

enumeration:
✅ enumerating the events + their types for a component type at runtime (say for generating wrappers)  should be possible with this.

Are there realistic alternatives to this even? I have sketched up an approach in the past that uses a mixin + a class that enumerates the events as static fields. It avoids creating one property per Event and instead creates a static member that also allows enumeration per component class. Unfortunately it feels a bit more clunky that decorators. If this is even of interest i can create a gist..

This topic has come up again in our project (relatively large enterprise design system).
I was wondering:

are there plans to address this topic in lit?
has anyone taken the route of event decorators and has some feedback/learnings?
thanks in advance!

I'm very much interested in this as well. It seems that you can either handle events through callback attributes/properties or through event listeners. I know there are arguments for using the event listener since you get some decoupling and the ability for multiple listeners but the fact that the callback attributes gets you declared events and strong typing seems to be a big reason to use those over emitting events. I know you've got to deal with the annoying this binding the lit does automatically for event listeners but seems worth the annoyance.


A11y: Manage Household Default Address Accessibility

Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

Tracking: [WI-7954400](https://gus.lightning.force.com/lightning/_classic/%2Fa07B0000008U7nUIAS)

@force2b @RadSFDeveloper The a11y PR is ready for review

The change is pretty much rewriting the original accordion using SLDS accordion and lighting:button instead of <div> with onclick(). onclick() on <div> and <li> are not accessible.

@rjanjanam , can you please take a look at a failing Manage Household robot test due to change in this PR? Thanks.

@RadSFDeveloper The code is updated and ready for review to keep focus onto the modal and change the role of the existing address button into checkbox. The changes from the past code review is adding keyboard access in the controller file to forced focus and revert the lightning:button back to  to add the checkbox role.

Since I know we want to move this forward I'll take my name off the reviewer list so you're not waiting for me.


Provide easy way to parse s3://foo/bar URI into (bucket,key) pair

Describe the feature
It is common to receive s3 object locations via a URI such as s3://foo/bar.  It would be nice if there was some S3Url object that implements FromStr such that I can easily extract the correct bucket and object strings from such a url.
Use Case
I'm always frustrated when I have to rewrite the same "s3 URI" to (bucket , object) parser for every CLI application I write. This involves importing one of the url or http::Uri crates and splitting hostname and path and providing appropriate error handling. Additional several times I messed up by not removing the initial / from the path.
It would be nice if the s3 SDK provided such tooling to make processing s3 URIs more easy.
Proposed Solution
I think some sort of S3Uri object that implements FromStr would be ideal as this integrates nicely into structopt and other CLI tooling.
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

A note for the community

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Can this also support being bi-directional? Going from (bucket, key) <-> uri?

Hey @jmklix  I'm new to rust but looking to contribute to a project and increase my rust knowledge. This seems like a good issue to start, do you think I can work on this? Thanks!


Document why ES db model JSON is different from protobuf JSON

As decided on 2018-06-15 call: https://docs.google.com/document/d/1ZuBAwTJvQN7xkWVvEFXj5WU9_JmS5TPiNbxCJSvPqX0/edit#heading=h.xdsshpxv2gpd

Yes the plan is to run grpc-gateway that will expose json API based on proto. The existing json model at that point would not be needed for the UI, so if you want to move it inside ES (plus converters, which is really why it was shared with UI in the first place), then it's fine.

I will create a copy of it to esl package. Once the UI is fixed to use the new model we can remove the duplicate in model package.

I think we can close this.
We have decided to define a separate model for ES for:

better encapsulation for ES storage - e.g. due to backward compatibility
internal model might change without ES schema