Could not dump objects until I modified dump_object.py as per comment

Everything I tried would yield the following error, even on internal Django models:
CommandError: object_class must be provided in the following format: app_name.model_name
Try calling dump_object with --help argument or use the following arguments:
 <[--kitchensink | -k] [--natural] [--query] object_class id [id ...]>

Then I tried the fix from this comment on closed issue #45 and after that I was able to dump objects successfully.
I don't understand what that args line is doing. I could submit a PR removing it but it would be good to know why it is there first.
Django version is 1.9.1.

For anyone else who runs into this or #45, a workaround is to use JSON id lookups instead of ID. E.g. --query '{"pk__in": [1]}'.


How to pass additional cxx flags to the host compiler when CUDA is enabled?

Which flags in user.mk should I modify? BASE_FLAGS, OPTIM_FLAGS, DEBUG_FLAGS?

You can modify any of the variables you mentoined. You can also use CPPFLAGS to just add extra compiler flags, or use CXXFLAGS to set all compiler flags overwriting the default.
When CUDA is enabled, and the flag you want to add is not understood by nvcc but it is for the host compiler, one should prefix the flag with $(XCOMPILER), e.g. we do that for the flag -Wall in the default setting for DEBUG_FLAGS:
DEBUG_FLAGS = -g $(XCOMPILER)-Wall $(BASE_FLAGS)

When CUDA is enabled, XCOMPILER will be set to $(CUDA_XCOMPILER) which is defined as
CUDA_XCOMPILER = -Xcompiler=


scrolling sidebar

if you have lots of files and a small screen this is no good

This one had never been fixed. Will submit a PR.

I lied - the menu uses overflow-y.
#menu {
  position: fixed;
  font-size: 12px;
  overflow-y: auto;

The styles in the generated coverage report found at http://mochajs.org/coverage.html are just outdated. So this problem was resolved! :)


Feature request: SHIFT-LeftClick to View Scene

Would be great to have a shift-left click to have a shortcut to View Scene.
This would make the behavior the same as with LegendKeeper.com.

View scene, as opposed to activate i presume?

View scene, as opposed to activate i presume?

I suppose this could be a configure option. I just imagine if you move from one scene to another from a map pin, you don't per se want to drag all players. And a player couldn't do Active Scene anyhow.


how to apply filters as a List similar to metrics or together, instead of multiple times

I tried the following but numbers dint match exactly
.filter( '537d509ee4b0893ab30616c7' , '637d509ee8b0893ab30616c2' )


Implementing correction by @JChonpca_Huang (#5)

Implementing correction by @JChonpca in issue (#5).

All tests succeeded. Merging this PR. This closes #5. Thanks again to @JChonpca.


docs/devel/networking: no NET_ADMIN, NET_RAW

"as little privileges" is a true guideline, but it sounds a bit vague.
We should specifically discourage virt-launcher from ever making any
use of CAP_NET_ADMIN  and CAP_NET_RAW.
Signed-off-by: Dan Kenigsberg<EMAIL_ADDRESS>
What this PR does / why we need it:
Add specificity to network developer doc
Release note:

/cc @AlonaKaplan @maiqueb

/approve

notes to self about CI failure:
https://prow.apps.ovirt.org/view/gcs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4600/pull-kubevirt-e2e-k8s-1.18/1333016579624931331#1:build-log.txt%3A5956 is failing because a VMI failed to start.
https://storage.googleapis.com/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/4600/pull-kubevirt-e2e-k8s-1.18/1333016579624931331/artifacts/k8s-reporter/nodes/1_journal_kubelet_node02.log has
Nov 29 14:08:47 node02 kubelet[2065]: I1129 14:08:47.272084    2065 topology_manager.go:233] [topologymanager] Topology Admit Handler
Nov 29 14:08:47 node02 kubelet[2065]: I1129 14:08:47.276940    2065 policy_static.go:193] [cpumanager] static policy: Allocate (pod: virt-launcher-testvmimhvvxpmbk2d9762rbp96lcdqqr7k5t258qbm7f744k, container: compute)
Nov 29 14:08:47 node02 kubelet[2065]: I1129 14:08:47.276963    2065 policy_static.go:203] [cpumanager] Pod f6a86fb1-0f33-4915-ac10-9e24cc66008a, Container compute Topology Affinity is: {<nil> false}
Nov 29 14:08:47 node02 kubelet[2065]: I1129 14:08:47.276975    2065 policy_static.go:239] [cpumanager] allocateCpus: (numCPUs: 2, socket: <nil>)
Nov 29 14:08:47 node02 kubelet[2065]: E1129 14:08:47.277018    2065 policy_static.go:208] [cpumanager] unable to allocate 2 CPUs (pod: virt-launcher-testvmimhvvxpmbk2d9762rbp96lcdqqr7k5t258qbm7f744k, container: compute, error: not enough cpus available to satisfy request)
Nov 29 14:08:47 node02 kubelet[2065]: E1129 14:08:47.277033    2065 cpu_manager.go:221] [cpumanager] Allocate error: not enough cpus available to satisfy request

which does not lead me much further

I'll reconsider fighting for this text on another day.


fix: get period-selector with latest button style fixes

Will be superceded by a newer period-selector


Split code from safe-zones catalogue into separate files

Splitting the code into separate files will improve readability and maintainability

Done in 8f74fd80455cb4d7d9afdd45216aa7738cee479e


drop test

Codecov Report

Merging #79 (6fa7016) into main (aa4320d) will increase coverage by 0.32%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main      #79      +/-   ##
==========================================
+ Coverage   30.52%   30.85%   +0.32%
==========================================
  Files          21       18       -3
  Lines        1687     1533     -154
==========================================
- Hits          515      473      -42
+ Misses       1086      978     -108
+ Partials       86       82       -4

Flag
Coverage Δ

unittests
30.85% <ø> (+0.32%)
:arrow_up:

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

Impacted Files
Coverage Δ

crypto/key.go

crypto/secp.go

crypto/bls.go


Improve/Redesign home page

Can I Redesign the home page .
@QAZIMAAZARSHAD  please assign this issue to me.

this issue will take time can you please assign me so that i can send PR on 10

Can I Redesign the home page.
@QAZIMAAZARSHAD please assign this issue to me.

Yes, go ahead.
But keep in mind, pages of other genres follow the same design and theme as of home page, so do not completely change the style of the home page so it looks completely odd compared to other pages.

this issue will take time can you please assign me so that I can send PR on 10

I'll assign you this issue when the contribution period starts from 10th June, then you can start working on this issue.
If you think this issue will take time then you can start working from today but I'll start assigning issues and merging pull requests from 10th June.

Ya sure

@QAZIMAAZARSHAD  whats the theme of this website...

Can you assign me , I also wish to contribute to this issue @QAZIMAAZARSHAD

@QAZIMAAZARSHAD  i need to discuss you something

Fine @coding-geek21, I'll review your PR soon.

Fine @coding-geek21, I'll review your PR soon.

Thank you :)


refactor Block view

tracking issue: #6
Summary
Current Blocks view is a heavy duplication of Transactions and serves no real purpose. Instead, it should link to relevant transactions and ABCI data.
Description

[x] The /block/HEIGHT page currently shows the contents of transactions within the block. Instead, it should show (only):

[x] a list of transaction hashes, each linking to the respective transaction page
[x] a table of the raw ABCI events occurring in the context of the block (not in the context of a transaction within the block). At this stage, the table should not attempt to parse or interpret the events.

closed by #73


Added "equals" validation rule

After reading this article (https://jason.pureconcepts.net/2017/09/nexmo-sms-admin-laravel) I decided to create a PR to add "equals" rule to Laravel. I think, it could be useful.

See "same" rule.

@taylorotwell same compares with other field value, this PR equals compares with user defined value.
The only way for now is use in:value.

"Same" rule is comparing the data in two different fields, my implementation of "equals" rule  comparing field value with the given string in rules.


Investigate improving Git SCM as done by GitHub for Atom

Investigate ways of improving Git SCM for VSCode by providing features present in GitHub for Atom. They did an excellent job of providing most of actions used when working on a project with Git as source control.
For more info, take a look at GitHub for Atom.

Great suggestion. I agree on the excellent job. But let's keep issues objective, simple and focused.
https://github.com/Microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions#writing-good-bug-reports-and-feature-requests


default-branch-button feature breaks the branch switcher

Here's a GIF:

And a link to the place where this can be reproduced:
https://github.com/File-New-Project/EarTrumpet/blob/<IP_ADDRESS>/README.md

I cannot reproduce in chrome

I can only get it on a tag page not a branch.
@cheap-glitch I used your bitsect feature and it works great!! Thanks

I used your bitsect feature and it works great!! Thanks

I agree, it's awesome :)

Also a bug here

That was already reported in #4239 so I didn't mention it :)

What the heck of a bug is this 😂 I don't understand how can this happen. Nothing in the dom seems to change on mousedown

#4370 has a tiny bit more details on how to reproduce this if needed


EmrEtlRunner: placeholder for S3 encryption

The command line option for S3DistCp is --s3ServerSideEncryption:
http://docs.aws.amazon.com/emr/latest/ReleaseGuide/UsingEMR_s3distcp.html
We need to understand:

Can we switch this on for all S3DistCp operations, or just for ones with S3 destinations
The implications for reading data from S3 (e.g. with our Analytics SDKs)
The implications for loading data into Redshift

I've been having a look at S3 encryption recently.
There's three types of S3 encryption supported: customer provided (SSE-C), Key Management based (SSE-KMS) and S3 managed (SSE-S3).
SSE-C isn't supported by EMR or Redshift COPY so we can eliminate having to deal with that at the moment [1], [2].
Neither SSE-KMS or SSE-S3 required modifying the COPY command to include an ENCRYPTED argument so this doesn't require any changes to the way Redshift is loaded [3].
The --s3ServerSideEncryption flag may work with no changes to the EMR cluster for SSE-S3 but we may need to add an extra Encryption parameter for EMRFS to support SSE-KMS [4] - it looks like there's at least 1 additional step to support SSE-KMS [5]
[1] https://docs.aws.amazon.com/emr/latest/DeveloperGuide/emr-emrfs-encryption.html
[2] https://docs.aws.amazon.com/redshift/latest/dg/c_loading-encrypted-files.html
[3] https://docs.aws.amazon.com/redshift/latest/dg/c_loading-encrypted-files.html
[4] https://docs.aws.amazon.com/emr/latest/DeveloperGuide/emr-emrfs-encryption.html
[5] https://docs.aws.amazon.com/emr/latest/DeveloperGuide/emr-create-security-configuration.html#emr-security-configuration-encryption

Thanks for sharing this @miike !

Thanks a lot for the investigation @miike :+1:
It seems there are 3 work streams:

encryption at rest on S3 which @miike describes thoroughly above (I tend to lean towards SSE-S3 which seems to have the less hassle)
encryption at rest on HDFS in EMR which seems to be a matter of configuration:

https://hadoop.apache.org/docs/r2.7.2/hadoop-project-dist/hadoop-common/SecureMode.html#Data_Encryption_on_RPC
https://hadoop.apache.org/docs/r2.7.2/hadoop-project-dist/hadoop-common/SecureMode.html#Data_Encryption_on_Block_data_transfer.

encryption in transit on Spark in EMR:

RPC (e.g. for shuffle) is encrypted by default with EMR > 5.9.0
HTTP (e.g. to the web interace) is another matter of configuration https://spark.apache.org/docs/latest/security.html#ssl-configuration

https://docs.aws.amazon.com/emr/latest/ManagementGuide/emr-data-encryption-options.html


DevTools: Bring in new logo

This updates the logo on the Chrome DevTools homepage with the one @paulirish provided me today.

Love that logo! :heart_eyes:


Cards with Infest retain the infest counter during Match and Keep

During Match and Keep, the event where you play memory to add cards to your deck, if cards with Infest are in the tableau, the infest icon is visible even while the cards are face down:

(I feel certain there's a funny joke to be made about an insect-themed mechanic causing a software issue...but for the life of me I can't think of what that would be......)

This is not so much a bug with this mod but with stslib. I'll open an issue there


Callback connection -- Listener#onConnected vs connect(callback#onSuccess) ?

Hi -- I'm getting setup with a callback connection and I was wondering, functionally, what is the difference between:
        conn = client.callbackConnection();
        conn = conn.listener(new Listener() {
            @Override
            public void onConnected() {

            }
...
};

and
        conn = client.callbackConnection();
        conn.connect(new Callback<Void>() {
            @Override
            public void onSuccess(Void value) {

            }
...
}

Thanks

Did you ever find out the answer? I'm also confused by this API


MockWebServer not picking up tests

Test running startedTest running failed: Instrumentation run failed due to
'java.lang.IncompatibleClassChangeError'
Empty test suite.
this is my build.gradle file
compile 'com.squareup.okhttp:okhttp:2.2.0'
compile 'com.squareup.okhttp:mockwebserver:2.2.0'
// Or if you use it in androidTest configuration
androidTestCompile 'com.squareup.okhttp:mockwebserver:2.2.0'
and this is my test method
public void testMockWebServerTest() throws Exception {
    // Create a MockWebServer. These are lean enough that you can

create a new
// instance for every unit test.
MockWebServer server = new MockWebServer();
// Schedule some responses.
server.enqueue(new MockResponse().setBody("hello, world!"));
server.enqueue(new MockResponse().setBody("sup, bra?"));
server.enqueue(new MockResponse().setBody("yo dog"));
    // Start the server.
    server.play(9999);

}

Test running startedTest running failed: Instrumentation run failed due to
'java.lang.IncompatibleClassChangeError'
Empty test suite.

This is a problem with your instrumentation testing setup, not OkHttp. I would suggest gathering more information and posting to StackOverflow. The fact that you use MockWebServer doesn't appear to be a factor.


/usr/bin/mono could not be spawned

Hello,
the following message alerted me when I installed ionide-paket using the package ionide-installer in a fresh atom on my mac:

'/usr/bin/mono' could not be spawned. Is it installed and on your path? If so please open an issue on the package spawning the process.

However, mono is available on my path, but is located in /usb/bin/local/mono as I figured via which.
Screenshots for reference:

+1 I am also facing the same error!
And also I am not add new nuget package

Should be fixed in 2.2.5


Handle EINTR in fixed preallocation

@heyitsanthony this seems to be still needed otherwise etcd crashes on etcd with SIGINT.

@heyitsanthony also is there any regression test to prove if this works on other filesystems? I experienced some weird crashes on vagrantfs.

@mfojtik What do you mean by crash? Shouldn't etcd terminate if it receives a SIGINT?

@heyitsanthony https://github.com/openshift/origin/issues/9370

@mfojtik that is unrelated to the preallocation path. It looks like boltdb is getting an EINVAL when opening snap/db file. Please open an issue with the strace information plus the stat information for snap/db (and ideally some way to reliably reproduce) if you believe it's an etcd bug.
Fixed size preallocation isn't used by etcd at the moment so I doubt it could be breaking anything. Closing.


Howto react on socket disconnection

Hi,
my application is using a pointer to a serverresponse to serve data coming from various sources but when the clients disconnects the object gets deleted causing a segfault.
How can i intercept the object deletion? Is there any signal emitted before the definitive delete?
Thanks

please use dev branch instead of master (until i merge the new changes back to master)

qhttp::server::QHttpResponse is an QObject, so you may want to use destroyed() signal.

the preferred approach is to use qhttp::server::QHttpConnection as it has a disonnected() signal. so you will be informed directly if a client disconnects.

Thanks, i've used the disconnected() signal with success!
Great job with QHttp, thanks!


rewrote in Jquery

Completeness: 5
Comfort:4

remember that code you wrote before? :wink: Great job man.

Oh I do... had to revisit what we pair coded during our last meeting : )


Mnist demo.

@jameshensman let me know what you think.

Happy to notebook it if you think that is better, though we should consider what it would add here.

I think this is fine as a python file, but it would be more discoverable if it were a notebook: we could include it in the documentation that way.
Would be nice if

it worked with python 3
it downloaded the 'official' mnist data from Yann's site, instead of our pickle (which won't load in python 3 either. Because pickle is a naughty format.)

Current coverage is 99.12% (diff: 100%)

Merging #200 into master will not change coverage

@@             master       #200   diff @@
==========================================
  Files            22         22
  Lines          1596       1596
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits           1582       1582
  Misses           14         14
  Partials          0          0

Powered by Codecov. Last update 9fbdec8...d092a6c

Hmm I'm not personally sure about requiring Python 3 compatability for PRs. Is that our policy now?

Also the notebook will take a few days to generate.

I don't think it's a policy, but the rest of the code has py3
compatibility. I'm about ready to advocate for a switch to py3.5.
We don't have to run the notebook, just indicate how to reproduce the
result.
On Fri, 9 Sep 2016 at 11:48 Alexander G. de G. Matthews <
<EMAIL_ADDRESS>wrote:

Also the notebook will take a few days to generate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GPflow/GPflow/pull/200#issuecomment-245881217, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAJbDzQToVUqFopNL5Qlgpg9NxUp2TVSks5qoTmDgaJpZM4J41mP
.

Asking for Python 3 compatibility before merging PRs seems like policy!
I'll add an issue to discuss.
I'm happy to switch this script over to a notebook.

Fair comment :)

See #203

Why don't we use the mnist (and other data sets) code provided with tensorflow?
from tensorflow.examples.tutorials.mnist import input_data
mnist = input_data.read_data_sets("MNIST_data/", one_hot=False)

@icouckuy good idea I will have a look.

This looks great.

Could we have it a bit more visible -- perhaps a link from one of the documentation notebooks?

typo: "#achieves 97.94% error." you mean accuracy :)

I've been trying to get a GP classifier working on MNIST myself without any luck. I saw this PR and tried running it myself but I cannot successfully train the model - my accuracy stays close to 10% .
My own attempts to reproduce the Sparse VI GP experiments from this paper have also fallen short:  (Figure 5, Top Left).
Could somebody verify for me that this PR runs correctly for them and achieves ~98% accuracy? Otherwise, is it worth me opening a new issue for my own code to resolve the problems there? (From what I can tell my model parameters hardly change during optimization - even with different constraints, priors, and optimization algorithms/learning rates).

Are you using a GPU and tf1.1? If so, have a look at #415

@AtheMathmo I haven't run this PR for a while but aside from any software issues yes it should work so if it doesn't we should get to the bottom of it. The original code was in GPy so this in fact replicates the experiments from our original paper. I'm afraid I don't know about the software for the paper you referenced. Let me know how it goes.

I just tried this with tensorflow 1.2 instead of 1.1 and it worked as expected. Looks like I was just running into an odd (previously reported) bug.
Thanks!

@athemathmo strange - I got a similar result using py 36 tf 1.2 and float32. Suggests something subtle has changed since I last ran it some months ago, which could be in either GPflow or tf itself. I'll keep you posted. The experiments take a couple of hours each. Worth noting this is still only a PR though :)
The result was originally produced in different code and looking at Daniel's paper that you linked looks to have been repeated by others. I'm still therefore confident this is an issue with this implementation rather than with the method itself.

I'm looking at this now also and experimenting with using LBFGS on the full data. With py3.5, tf1.2 (GPU, float64) and M=300, ARD=False and RBF kernel with fixed variance of 1, after 1000 iterations (about 1h) I get
svgp, test ll: -0.082, test acc: 0.9792
svgp white, test ll: -0.086, test acc: 0.9788

In both cases the lengthscale optimizes to about 10, but with free kernel variance the hyperparmeters diverge. Not sure why this happens.

@hughsalimbeni thanks for the update. Originally it was necessary to `freeze' the hypers and inducing points at the beginning of optimization because the optimization surface could lead off to bad local optima as reported in section 5 here:
http://proceedings.mlr.press/v38/hensman15.pdf
You could also ask James about this if you have started in Cambridge.
The mnist experiment actually appeared in our next NIPS paper though in many ways it would have been more natural in the AISTATS one. The code we released at that point is here:
https://github.com/sparseMCMC/NIPS2015/blob/master/experiments/mnist/mnist_demo.py
Note the freezing. It might be a bit fiddly to resurrect this as the GPy versioning wasn't that tight.
In this PR I was hoping to do away with freezing using a better initialization but it seems to have stopped working.

I found in my own implementation that normalizing the input data was far more effective than rescaling between [-1,1]. If I find some time I'll see if that gives any wins for this PR too.

I've noticed the diverging hyperparameters as well. I've also noticed on some similar experiments which I've allowed to run for much longer that eventually, the hyperparameters stop increasing and start dropping back down again, before eventually stabilising.
A longer lengthscale with a larger variance still allows the GP to obtain a similar swing in latent function value between two points, keeping the data fit term the same. However, the variational approximation prefers longer length scales. Perhaps it eventually settles down once the variational approximation (through the inducing point locations) is good enough. It would be nice to test this hypothesis though, and perhaps do something about it. It probably doesn't help training.
I also wonder whether EP based approaches exhibit this effect. I wonder whether it's a consequence of the highly lopsided true posterior combined with a Gaussian approximate posterior. VI gets penalised heavily for placing density in regions where the true posterior is low. EP does not have this behaviour.

@markvdw without further work that would be my hypothesis too.

I'm going to try and get this up to date and in the next couple of days. Did anyone from the discussion want to update their comments?

By training with Adam for a really long time (50 gpu hrs), the error became 1.9%. Not necessarily practical, but it does show that more afressive optimisation can help. May be worth mentioning.
More broadly, I think we don't really understand (our rather, have good rules of thumb) for stochastic optimisation of these objective functions. In NNs, so many things that don't affect the objective function (like batch size) affect performance. It makes it hard to figure out what to do if we really want to optimise the objective...

@markvdw that seems like a very long time. Interesting thoughts though.
I believe @hughsalimbeni ran LBFGS on it which takes the stochastic aspect out of the loop. MNIST isn't that big for us anymore.

Agreed. I've run that experiment as well, although I don't think I ran it to convergence. With some similar models I've got the issue that I just can't fit a single batch on the GPU memory in float64. This is needed to play well with LBFGS.

So I find out doing this that TensorFlow currently allows non-determinism on GPU:
https://github.com/tensorflow/tensorflow/issues/2732
Therefore we can't expect exact replication here. However the initialisation needs to be sufficiently stable not to give large differences.

Also try.contrib decided to randomised the mnist order silently but this is fixable.

@AtheMathmo d7c7f86 restores freezing as we did in the original paper and has repeatedly given me accuracies around 98.0% .
I would advise you to run  with float_type=float32 and jitter_level=1e-4 in your gpflowrc. I plan to make this automatic for this notebook.
Note my comments above about exact TensorFlow determinism.
My apologies for the delay fixing this.
I will now make cosmetic changes to this pull request ready for merging to master.


feat(hooks): migrate TimeGutter.js to react hooks

might be worth bunching these into a a single feature branch so we can release at once. You can still do individual PR's if that's helpful but make them to your feature branch instead of master.

great, I will do it this way in next PRs


ENH: chkfinite flag in scipy.linalg

I added a chkfinite flag to all scipy.linalg functions where it made sense to do so. This flag allows the user to disable the checking for finite floating point numbers in argument arrays. By default the inputs are still verified to be finite. Previously the user had no way to turn off this checking.
This is a desirable change because the checking can be fairly time consuming but also irrelevant for users that have already verified their data otherwise. In particular, it's a useless overhead if the user is repeatedly linalg operations on subarrays of a large array whose elements have already been verified.
(Of course, the downside is some functions hang if given np.Inf or np.NaN as inputs. And othertimes the programs will perform the operations but output garbage, which possibly might be hard to detect as garbage.)
Tests to check the flag worked were added to the existing tests in scipy.lingalg.

Should this be merged? IMHO it should.

I think the hold up was we were trying to figure out if something reasonably fast could be accomplished at the C level, either by directly using C or using cython. If I recall correctly, none of the potential solutions panned out as hoped.
I think there's still some uncertainty about whether this is that desired a feature. I agree that it has great uses, obviously, but there are several potential problems which have made people uncertain about it.

It complicates the API.
For some linalg functions, if given improper input with the checking off the function will silently return incorrect output. (Though in the cases I tested, it was usually easy to recognize the output was incorrect--due to inf's or nan's in the output matrix--but I didn't check if such an output was necessarily true.)
For other linalg functions it would just stall. This is obviously a major problem, and I'm unsure what solutions might exist.

On Wed, Jan 11, 2012 at 08:38:08AM -0800, chrisjordansquire wrote:

I think there's still some uncertainty about whether this is that
desired a feature. I agree that it has great uses, obviously, but there
are several potential problems which have made people uncertain about
it.

I know the drawbacks, but for some of my application the overhead of this
is so high that I sometimes shortcut it through a direct call to blas
(get_blas_func). Not providing this functionality will simply cause some
people to hack around it. At some point advanced users need lower level
access.

+0 from me for merging, but I'd really recommend calling the keyword check_finite instead of chkfinite --- it's better PEP8 style.
(IMO, the checks shouldn't be there in the first place, and the routines should follow a garbage-in-garbage-out principle, similarly as most other routines do --- with the exception of infinite-loop or crash cases.)

I suspect that removing the checks is out of the question, since it almost certainly would break any backwards compatibility. Am I mistaken?

I don't see how we could remove the checks by default given the fact that the algorithms hang or crash with the wrong values.   Ideally, we would fix the underlying algorithms so that they don't crash under bad-data (but just produce bad results).   That would be the "correct" solution.    My understanding is that these algorithms are optimized.  Quite often, optimized algorithms do suffer from such behavior.
However, I don't see the problem with adding this additional keyword argument with a default of "True".   I like check_finite or just check_inputs as the name of the keyword argument.

What about having a finite keyword in the numpy array constructor, then that could be made available in asarray, or maybe something like asfinitearray?

Since nobody argued against it, I think making the change is fine.
I think an extra options will be useful, but I'm still skeptical about actually using it, since we are never sure not to run into corner cases. (During lowess refactoring I made mistakes and got several times the check_finite exception.) One possibility I thought about is to raise an exception on floating point warnings when using this code, for example set ZeroDivisionWarning temporarily to error, while using this in a loop. This could make it a bit safer, if any of the other code in the loop creates a nan or inf.

I think the documentation for this keyword should be more explicit (i.e. may give speed gain, but can result in crashes when input contains inf/nan).
Other than that I'm fine with this.


Update VsUpload.vue

Multiple file upload returns name instead of file

I do not understand what you mean? still not implemented I have to review it before uploading it to production or do you mean something else?

Here are a few screenshots of the results I am getting from the
VsUpload.vue component. I am not sure of how to get the file, is it the
filex?
On 18 May 2018 03:37, "Jamie Bunyassi"<EMAIL_ADDRESS>wrote:

Here are a few screenshots of the results I am getting from the
VsUpload.vue component. I am not sure of how to get the file, is it the
filex?
On 18 May 2018 03:29, "ldrovira"<EMAIL_ADDRESS>wrote:

I do not understand what you mean? still not implemented I have to review
it before uploading it to production or do you mean something else?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/lusaxweb/vuesax/pull/74#issuecomment-390056009, or mute
the thread
https://github.com/notifications/unsubscribe-auth/APHamgJk5Ado082-tb_cYllc85AgAPN0ks5tzhYGgaJpZM4UD8hG
.


improved OctoberCMS & WHMCS detection; changed IONOS icon

WHMCS see https://github.com/AliasIO/wappalyzer/issues/2940#issuecomment-589302219

The icon should be SVG (preferable) or PNG, not JPEG.

Re-Opened in 3x separate PRs
https://github.com/AliasIO/wappalyzer/pull/3019
https://github.com/AliasIO/wappalyzer/pull/3022
https://github.com/AliasIO/wappalyzer/pull/3023


Support to upload icon

Hi there a chance to include a option to upload a custom ico/png for a bookmark?
I use the bookmark without text on chrome to create a "fast panel" and with this I can migrate all my bookmarks:

I assume you mean the bookmarklet? There aren't any reliable solutions for adding an icon for that AFAIK.


why do this,though my cache has the nw version file,  code: 'ETIMEDOUT',

[08:39:25] Starting 'nw'...
[08:40:43] nw-builder { Error: connect ETIMEDOUT <IP_ADDRESS>:80
at Object.exports._errnoException (util.js:896:11)
at exports._exceptionWithHostPort (util.js:919:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1073:14)
code: 'ETIMEDOUT',
errno: 'ETIMEDOUT',
syscall: 'connect',
address: '<IP_ADDRESS>',
port: 80 }

I have the same question

Is this when you don't have a connection is it?

I have the same

the same

@yeyu456 @wangyinlong @Vincent2015   I solved the problem that you'd better download the https://nwjs.io/versions.json  and put it on your own website, and set the url to  NWBuilder parameter
-- manifestUrl  'YourURL'

Thanks for reporting but I'm closing this as a duplicate of #419.


Renaming the f method causes naming conflicts

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

-VS Code Version: 1.88.1
-OS Version: Windows11
-Language：java
Steps to Reproduce:
1.select "m()"
2.click “Rename”
3. new name "t()"
class A {
void m() { // rename m to t
System.out.println("println m");
}
}
class B {
void t() {
System.out.println("println t");
}
class C extends A {
    void test() {
        t();
    }
}

}

/extJava

It looks like this is caused by the Java extension. Please file the issue to the Java extension repository. Make sure to check their troubleshooting instructions and provide relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!


Showing NFTs

[x] Display all NFTs on the chain
[x] Display all NFTs owned by the user

So basically, it's now able to show all the NFTs (including meta, contract address, token ID, etc).


When inserting a new InlinePanel, focus goes to the wrong place.

Issue Summary
When inserting a new InlinePanel, focus goes to the wrong place.
Steps to Reproduce

Navigate to the edit view for a page with an inline panel.
Use keyboard navigation to focus the "add foos" button.
Hit enter.
Observe that:

focus remains on the "add foos" button
this is now at the end of the newly inserted InlinePanel / formset form element
you must navigate back with shift+tab to get to the start of the newly inserted form

https://github.com/wagtail/wagtail/assets/1473980/b2a516d5-9316-48ad-be6f-471927967d29
This adds confusion and extra work for users relying on keyboard navigation or screen readers.
I would instead expect focus to move to the first field in the newly-inserted form.
Technical details

Wagtail version: 5.0.2

hey @nimasmi  i have looked into your problem and i think the default behavior is it does not focus on any inline field,
Screencast from 24-08-23 10:21:16 PM IST.webm

btw it would have been better if focus goes on first inline field

hey @nimasmi  i have gone through documentation in field panel you can pass widget arguments like django as wagtail documentation says FieldPanel('caption_test', widget=forms.TextInput(attrs={'autofocus': 'autofocus'})) in your first inlineField it should work

Thanks for the suggestion @faishal882. It did not work for me, although the inline field was created with the autofocus=autofocus attribute. I don't think this is the right solution, though, because the MDN docs for autofocus this say

it should receive focus when the dialog that it is part of is displayed, but we don't have that
it should receive focus on page load also, but we don't want that

I believe a JS change is the right fix here.

hey @nimasmi  i tried to do achieve same autofocus in inline model in django,  and the same problem happened i think it is the issue which can be raised in django

I agree a JS change is needed and this will be tricky to add a workaround for as there's no JS DOM events for when InlinePanel items are added - https://github.com/wagtail/wagtail/issues/9105 .
This won't be a Django problem though as this is a Wagtail implementation.
It's a bit nuanced also, as the movement of focus to the input won't always be possible as a different target may make sense.
A possibility is to focus on maybe the container or title, adding tabIndex -1, then when focus moves away it will remove the tabIndex.
There are plans to redo parts of the InlinePanel with Stimulus but that may not happen for the next release.
I'm happy to help review any PRs that someone wants to submit for this.

Screencast from 30-08-23 03:31:35 AM IST.webm
hey @lb-  i think on autoscroll to view newly created form is better  then not having it,  even though it didn't completely solved the issue on adding tabindex -1 on newly created inlinePanel the autofocus attribute added via widget still not works. If you permit i can create a PR or if any other solutions in mind please suggest

Another thing to call out is that this will make subsequent 'add item' a bit more annoying. You will not be able to click this multiple times to add a bunch of new items as the scroll will shift your focus away.
However, this is aligned with the similar functionality for adding blocks, where we take you to the field / container that has just been added. So it's probably best to be consistent.

Thanks for addressing this @faishal882!


[bug]: I think I fixed it, go over my comments, i posted them in real time as i fixed this

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
amd
VRAM
25
What version did you experience this issue on?
latest
What happened?
File "/tmp/invokeai-installer-tmpqudz_o41/lib/python3.11/site-packages/plumbum/commands/processes.py", line 17, in _check_process
proc.verify(retcode, timeout, stdout, stderr)
File "/tmp/invokeai-installer-tmpqudz_o41/lib/python3.11/site-packages/plumbum/machines/base.py", line 27, in verify
raise ProcessExecutionError(
plumbum.commands.processes.ProcessExecutionError: Unexpected exit code: 1
Command line: | /mnt/alpha/invokeai/.venv/bin/pip install --require-virtualenv --use-pep517 '/mnt/alpha/InvokeAI/installer[onnx]' --extra-index-url https://download.pytorch.org/whl/rocm5.4.2
Screenshots
No response
Additional context
using the new 7900 XTX
Contact Details
<EMAIL_ADDRESS>

ERROR: Directory '/mnt/alpha/InvokeAI/installer[onnx]' is not installable.

 Please don't rely on it. You probably just need to use APIs in torchvision.transforms.functional or in torchvision.transforms.v2.functional.
warnings.warn(
Traceback (most recent call last):
File "pydantic/utils.py", line 785, in pydantic.utils.get_discriminator_alias_and_values
AttributeError: 'tuple' object has no attribute 'type_'

The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/home/mrgfy/.local/bin/invokeai-web", line 5, in
from invokeai.app.api_app import invoke_api
File "/home/mrgfy/.local/lib/python3.9/site-packages/invokeai/app/api_app.py", line 26, in
from .api.dependencies import ApiDependencies
File "/home/mrgfy/.local/lib/python3.9/site-packages/invokeai/app/api/dependencies.py", line 15, in
from invokeai.app.services.images import ImageService, ImageServiceDependencies
File "/home/mrgfy/.local/lib/python3.9/site-packages/invokeai/app/services/images.py", line 37, in
from invokeai.app.util.metadata import get_metadata_graph_from_raw_session
File "/home/mrgfy/.local/lib/python3.9/site-packages/invokeai/app/util/metadata.py", line 6, in
from invokeai.app.services.graph import Edge
File "/home/mrgfy/.local/lib/python3.9/site-packages/invokeai/app/services/graph.py", line 693, in
class GraphExecutionState(BaseModel):
File "pydantic/main.py", line 197, in pydantic.main.ModelMetaclass.new
File "pydantic/fields.py", line 506, in pydantic.fields.ModelField.infer
File "pydantic/fields.py", line 436, in pydantic.fields.ModelField.init
File "pydantic/fields.py", line 552, in pydantic.fields.ModelField.prepare
File "pydantic/fields.py", line 758, in pydantic.fields.ModelField._type_analysis
File "pydantic/fields.py", line 808, in pydantic.fields.ModelField._create_sub_type
File "pydantic/fields.py", line 436, in pydantic.fields.ModelField.init
File "pydantic/fields.py", line 552, in pydantic.fields.ModelField.prepare
File "pydantic/fields.py", line 629, in pydantic.fields.ModelField._type_analysis
File "pydantic/fields.py", line 666, in pydantic.fields.ModelField._type_analysis
File "pydantic/fields.py", line 780, in pydantic.fields.ModelField.prepare_discriminated_union_sub_fields
File "pydantic/utils.py", line 787, in pydantic.utils.get_discriminator_alias_and_values
TypeError: Type 'BooleanOutput' is not a valid BaseModel or dataclass

FML, i give up

good luck getting this to run, i give up. Gonna try some other gui software.

On Apple M2 MacOS 13.5 I have the same issue:
ERROR: Directory '<PATH>/InvokeAI/installer[onnx]' is not installable. Neither 'setup.py' nor 'pyproject.toml' found.
.. when running the installer downloaded at https://github.com/invoke-ai/InvokeAI/releases/tag/v3.1.1
Any ideas?

update, after running the installer.sh.in (weird extension for a bash script btw) all pkgs are cached and install correctly, then it freaks out  you see, all good. then this.....

Hello.
Maybe you're trying to install StableDiffusion the wrong way.
Did you clone the repo?
Something like git clone https://github.com/invoke-ai/InvokeAI/, or going on https://github.com/invoke-ai/InvokeAI/ and then click on "Code", then "Download ZIP"?
If yes, I think you're missing the standard way to process the installation.
Instead of trying to clone the repository, just go on this page
https://github.com/invoke-ai/InvokeAI/releases
And then download an InvokeAI Installer. Either via the link provided in the descriptions of the releases, or by clicking on the "Assets" dropdown menu below each release, then clicking on the installer provided in the Assets of the release.


Update Package-References-in-Project-Files.md

The PR is not being built because the target branch live is filtered in .openpublishing.publish.config.json on live branch.


Bato.to timeout

Source name
Batoto 1.4.42
Source language
Multi
Describe your suggested feature
I've been receiving timeouts from batoto. can rate limit be increased or maybe add a new configuration to change rate limit like some other extensions?
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with the app itself, I should be opening an issue in the app repository.
[X] I have updated the app to version 0.15.3.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

most likely an issue with bato recently


use new base docker image in uboot course

:+1: we can do a test run through of the course to make sure.


Platform specific dependencies

Is/will_be there possibility, to add dependency for specific platform?
In my case, I need pywin32 on Windows, but only there.

You can use platform markers. See here: https://peps.python.org/pep-0508/


Add thread num test

Proposed changes
Create 10 Workload group to test whether thread num could exceed 4096.

run buildall

run buildall


Improve MongoDB preview data for MongoDB with Nested Arrays

When viewing the MongoDB tables data with nested arrays, the current representation lacks clarity and usability. This becomes prominent when dealing with complex data structures like those encountered in MongoDB, where arrays are commonly used as attributes.

Proposal:
Proposal's description and rationale:

JSON tree view for nested arrays: Use a JSON tree view instead of a table to represent MongoDB collections with nested arrays. It preserves hierarchy for better visualization and understanding of complex data structures, leveraging developers' familiarity with the JSON tree view format.
Enhance existing features: Improve the current JSON viewer (query response tab) by adding expandable and collapsible options.

To discuss:

does it make sense to keep the toggle Table | JSON?
(to keep consistency) can we also improve the response tab as well by applying the collapsable/expandable functionality?

Currently, we already show the collapsible/expandible JSON view in the query response.

We have the CodeEditor component in the code which can be imported and reused for the same.
@carinanfonseca

@NilanshBansal @rohan-arthur I have added task breakdown with estimations in this doc

Since this task was only a breakdown estimation and design review task. Marking this as done.


dockerfile.vim should recognize Dockerfile.multi

Currently Dockerfile.vim seems to only recognize files by the name of "Dockerfile".  From what I've seena common naming convention for multistage builds is "Dockerfile.multi".  Should Dockerfile.vim recognize this filename for syntax highlighting as well?

I'm not sure this is true - https://github.com/ekalinin/Dockerfile.vim/blob/master/ftdetect/Dockerfile.vim#L3
That seems to match any file that starts with Dockerfile.
Are you still having this issue? When I tried to reproduce this it seemed to work without any issues.

Hi, in my case I can open a file named Dockerfile.android and coloration works as expected. So IMO this issue can be closed. @webermaster do you agree ?

Hm. Having trouble with syntax highlighting for Dockerfile (without .multi) as well. Using vim-polyglot I see no highlighting. That said, disabling it with let g:polyglot_disabled = ['dockerfile'] and loading ekalinin/Dockerfile.vim manually works.

@webermaster please, try the latest version of the Dockerfile.vim
Just tried:
➜ vim Dockerfile.multi

and file type was set correctly.


Changed help center links and shortcuts

Description
Help center had the default links and we needed to update them.
Checklist

[X] Discord -> PearAI Discord
[X] Github Issues (this was done already with the link: https://github.com/trypear/pearai-app/issues/new/choose) -> change link to https://github.com/trypear/pearai-app/issues
[X] Keyboard shortcuts: add CMD+[ with "Enlarge Pear chat" and CMD+: for "Close Pear chat"
[X] Documentation and demo video can be kept same for now until we make one ourselves

Hey I have some questions:

The github link was already changed to https://github.com/trypear/pearai-app/issues/new/choose (not: https://github.com/trypear/pearai-app/issues), but I think I should leave it like this. What do you think?
Should I refactor the entire file with eslint or should I leave it like this?

i trust you
refactor dat shieee

I think it's done.


Kgoot/dfaker

OK, I'll left you with quite a bit to start with at least. I'm going to take a closer look at cbg_equation later and fiddle with it to understand what you're doing - looks interesting!

Also copy the output of running with --help and paste it as a comment at the top of the file - that's a nice standard so people can see the CLI options when viewing the raw file on GitHub.

Merging, woohoo! \o/


Unexpected CompileTimeError reported when running tests in co19/LanguageFeatures/nnbd

Running tests from co19/LanguageFeatures/nnbd under strong and weak modes the following unexpected CompileTimeError are reported.
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/extension_method_resolution_A03_t01 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/extension_method_resolution_A03_t02 is new and failed (CompileTimeError, expected Pass)dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/legacy_libraries_A02_t01 is new and failed (CompileTimeError, expected Pass)dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/tripple-shift/null_aware_operator_A09_t12 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/tripple-shift/null_aware_operator_A11_t12 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/tripple-shift/null_aware_operator_A13_t12 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/tripple-shift/null_aware_operator_A15_t12 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/type-aliases/null_promotion_A01_t08 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/type-aliases/type_reification_A01_t05 is new and failed (CompileTimeError, expected Pass)
dartk-strong-linux-release-x64:co19/LanguageFeatures/nnbd/type-aliases/type_reification_A01_t06 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/extension_method_resolution_A01_t03 is new and failed (CompileTimeError, expected Pass)dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t01 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t03 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t05 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t07 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t09 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t11 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t13 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t15 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t18 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/overriding/override_checking_A02_REQ_ARGS_t20 is new and failed (CompileTimeError, expected Pass)
dartk-weak-asserts-linux-release-x64:co19/LanguageFeatures/nnbd/type-aliases/null_promotion_A01_t10 is new and failed (CompileTimeError, expected Pass)

/cc @johnniwinther

Latest set of unxpected CompileTimeError issues
vm-release | co19 | LanguageFeatures/nnbd/extension_method_resolution_A03_t01
vm-release | co19 | LanguageFeatures/nnbd/extension_method_resolution_A03_t02
vm-release | co19 | LanguageFeatures/nnbd/future_flattening_A01_t64
vm-release | co19 | LanguageFeatures/nnbd/future_flattening_A01_t65
vm-release | co19 | LanguageFeatures/nnbd/future_flattening_A01_t66
vm-release | co19 | LanguageFeatures/nnbd/type-aliases/null_promotion_A01_t08
vm-release | co19 | LanguageFeatures/nnbd/type-aliases/type_reification_A01_t05
vm-release | co19 | LanguageFeatures/nnbd/type-aliases/type_reification_A01_t06
vm-release | language | async_star/await_pauses_test
vm-release | language | covariant/subtyping_test
vm-release | ffi | extension_methods_test
vm-release | ffi | function_structs_test
vm-release | language | invalid_returns/async_valid_returns_test
vm-release | ffi | structs_test
vm-release | ffi | vmspecific_static_checks_test/none

Closing this issue. Only remaining compile-time errors are due to nonfunction type aliases. Opened https://github.com/dart-lang/sdk/issues/43261 for these.


[ETFE-3604] Added the AddToList page

Just commenting so I get notifications - I'll be picking up any review comments on Matt's behalf whilst he's off.


Update main README to use v1beta1 sklearn as example

What this PR does / why we need it:
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:

Update MAIN readme to use v1beta1 sklearn example
Update quick install with 0.5 release
Upload kubeflow 0.5 release yaml
Update default image version to latest for development and use tagged version when generating the release

Release note:

/LGTM


Compatibility with the Cmake system in newer esp-idf.

The library is not compatible with the CMake based build system. I being new to CMake am pretty unsure of what's happening. Could you please tweak the library to work with the new system?

@natanaeljr any updates with the cmake inclusion ?

Yes, the library is now compatible with CMake build system. Added in pull request #12.


Feature Request: Semantic Search via existing pluging

Checklist

[X] The feature would be useful to more users than just me.
[X] I have checked the feature overview and the feature doesn't already exist.
[X] Feature Requests regarding daily notes will not be implemented, since there are other Alfred workflows that do focus on daily notes already.
[X] If you are looking for a way to trigger a specific Obsidian command from outside Obsidian, see this comment explaining how you can easily create such a workflow yourself.

Feature Requested
Implement also Semantic Search from the Alfred bar. E.g. using any of these existing plugins https://github.com/solderneer/obsidian-ai-tools , https://github.com/bbawj/obsidian-semantic-search
Alternatives considered
There are plugins that do it but it would be great to do it directly within Alfred for speed
Relevant Screenshot
No response

Being an Alfred plugin, Shimmering Obsidian does not have access to the same kind of APIs as Obsidian plugins do. Thus, such a feature is better suited for Obsidian plugins than an Alfred workflow, sorry.

thanks for the quick reply!
isnt it possible to use part of the plugin functionality within the Alfred
bar? or pass the content of the bar to the plugin as input?
On Mon, 11 Nov 2024 at 10:40, Chris Grieser @.***>
wrote:

Being an Alfred plugin, Shimmering Obsidian does not have access to the
same kind of APIs as Obsidian plugins do. Thus, such a feature is better
suited for Obsidian plugins than an Alfred workflow, sorry.
—
Reply to this email directly, view it on GitHub
https://github.com/chrisgrieser/shimmering-obsidian/issues/200#issuecomment-2467672900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA4VG55DUV5KCLFOV64XIGD2AB3RTAVCNFSM6AAAAABRRH45F2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRXGY3TEOJQGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Test that the cachet:* commands work

This tests that cachet:seed and cachet:metrics work.

Maybe make separate test methods for them?

I thought that, but figured they're overkill? I can do if you think it's a good idea though?

I think it would be useful to keep that atomic, so we can see exactly what's broken if we mess up.

Sure, I'll do that.

Done!

Closing this, I'll just do it again.


Unable to install AngleSharp into a Xamarin forms shared project

I am using 0.9.6 version of AngleSharp.
I tried to install AngleSharp into a Xamarin forms shared project. I found it would not install into either the IOS or the Android projects with the failure
Package 'System.Reflection.Extensions.4.0.0 : System.Reflection [4.0.0, ), System.Runtime [4.0.0, )' does not exist in project 'CelticPools.Droid'

It is OK in a PCL based solution of the same project.

I think this is an old issue (see #85, #349 with PR #350). It's a little bit strange that it still does not work properly. That being said: Can you give more insights on the version of Xamarin you are using? That could potentially be helpful.
Generally, I hope that someone with more experience / knowledge in Xamarin is able to pick this up. I fear I am not able to come up with a good solution here.

I am using Xamarin forms version 2.3.0107. The strange thing is that both the shared and the PCL version are referencing the same .NET framework implementation. MonoAndroid V1.0 and Xamarin.IOS V1.0.

Hi,
I'm from Xamarin support. It seems that, in Visual Studio only (seems to work in Xamarin Studio [Mac])  that AngleSharp version .0.9.5 and 0.9.6 won't install into Xamarin.Android or Xamarin.iOS projects. 0.8.9 - 0.9.4 install as expected. And this is true for either a Xamarin Forms PCL solution or Xamarin Forms Shared solution.
I would think the PR for #350 would resolve this?

Hi @jgold6 - thanks for your remark. I also thought this would help, but apparently it didn't. Is there anything else we can do (i.e., what improvements do you see to the Nuget package)?
Any help is highly welcome. Thanks!

Unfortunately I am no NuGet expert, I was just reporting what I found as the customer who reported this issue also wrote in to Xamarin Support. I would think you can see what differences there are between the working version and non-working versions and what might affect the ability to add the package to Xamarin,Android and Xamarin.iOS projects.
Note also that this works in Xamarin Studio, i.e. I can install AngleSharp versions 0.9.5 and 0.9.6 into an Xamarin Android or Xamarin iOS project in Xamarin Studio on a Mac.

Thanks for the clarification @jgold6 - much appreciated. I will try to resolve the issue!

It works for me, I use Windows Visual Studio with AngleSharp v0.9.9 and Xamarin Forms <IP_ADDRESS> . I am targeting Shared, Droid, iOS  and UWP. I can provide you with more info if needed.

Thanks for the info @genie137 - if it works in a standard setup (sounds that way) I guess we can close this issue, right?


Example for linalg.eig()

    >>> a = np.array([[0., -1.], [1., 0.]])
    >>> linalg.eigvals(a) == linalg.eig(a)[0]
    array([ True,  True])
    >>> linalg.eig(a, left=True, right=False)[1] # normalized left eigenvector
    array([[-0.70710678+0.        j, -0.70710678-0.        j],
           [ 0.        +0.70710678j,  0.        -0.70710678j]])
    >>> linalg.eig(a, left=False, right=True)[1] # normalized right eigenvector
    array([[0.70710678+0.        j, 0.70710678-0.        j],
           [0.        -0.70710678j, 0.        +0.70710678j]])

Thanks @RadZaeem. Note that when you make a mistake and want to add something to a pull request you already opened, you don't have to close it and open a new one. It's preferable to just push a new commit to the same branch from which you made the PR in the first place.

Ok got it.
https://github.com/scipy/scipy/issues/7168

Thanks @RadZaeem


Did the available submissions change?

Did you remove submissions from the competition?
For example, I can still interact with the RSLLM Llama submission via its ID (I saved it locally). Yet, when I query the submissions API, the model is no longer included in the response.

Please see my comment #48 for more info about this.
I have now also disabled creating chats with these submissions

https://github.com/ethz-spylab/satml-llms-ctf-issues/discussions/48#discussioncomment-8335587


Fix DockerTrustSuite SetUpTest

This hopefully makes DockerTrustSuite.SetUpTest less flaky.
Increased the number of attempts to check if Notary is available before giving up.
fixes https://github.com/docker/docker/issues/19393 (fingers crossed)

Janky, why are you failing.. java.lang.IllegalStateException

LGTM

Lol, and gccgo is failing on another flaky test :cry: https://github.com/docker/docker/issues/19368

LGTM. Worth a shot.

It's green, so lets merge!

@thaJeztah I'll let Jenkins test this with the DockerTrustSuite enabled on ARM.

@StefanScherer thanks! As mentioned, we can still tweak this, my primary concern was to get the test at least a bit more reliable :-)

@thaJeztah Sure!
But look, DockerTrustSuite works on ARM:
09:15:39 PASS: docker_cli_build_test.go:5831: DockerTrustSuite.TestBuildContextDirIsSymlink	3.846s
09:15:45 SKIP: docker_cli_create_test.go:332: DockerTrustSuite.TestCreateWhenCertExpired (Currently changes system time, causing instability)
09:15:51 SKIP: docker_cli_pull_trusted_test.go:65: DockerTrustSuite.TestPullWhenCertExpired (Currently changes system time, causing instability)
09:15:57 SKIP: docker_cli_run_test.go:3200: DockerTrustSuite.TestRunWhenCertExpired (Currently changes system time, causing instability)
09:16:12 PASS: docker_cli_build_test.go:5779: DockerTrustSuite.TestTrustedBuild	9.048s
09:16:18 PASS: docker_cli_build_test.go:5810: DockerTrustSuite.TestTrustedBuildUntrustedTag	0.717s
09:16:32 PASS: docker_cli_create_test.go:282: DockerTrustSuite.TestTrustedCreate	7.526s
09:16:52 PASS: docker_cli_create_test.go:359: DockerTrustSuite.TestTrustedCreateFromBadTrustServer	13.584s
09:17:05 PASS: docker_cli_create_test.go:319: DockerTrustSuite.TestTrustedIsolatedCreate	6.406s
09:17:16 PASS: docker_cli_pull_trusted_test.go:35: DockerTrustSuite.TestTrustedIsolatedPull	5.467s
09:17:29 PASS: docker_cli_pull_trusted_test.go:177: DockerTrustSuite.TestTrustedOfflinePull	6.398s
09:17:40 PASS: docker_cli_pull_trusted_test.go:14: DockerTrustSuite.TestTrustedPull	5.648s
09:17:55 PASS: docker_cli_pull_trusted_test.go:205: DockerTrustSuite.TestTrustedPullDelete	9.150s
09:18:14 PASS: docker_cli_pull_trusted_test.go:93: DockerTrustSuite.TestTrustedPullFromBadTrustServer	12.909s
09:18:20 SKIP: docker_cli_pull_trusted_test.go:147: DockerTrustSuite.TestTrustedPullWithExpiredSnapshot (Currently changes system time, causing instability)
09:18:31 PASS: docker_cli_push_test.go:203: DockerTrustSuite.TestTrustedPush	4.832s
09:18:40 PASS: docker_cli_push_test.go:243: DockerTrustSuite.TestTrustedPushWithDeprecatedEnvPasswords	3.494s
09:18:51 PASS: docker_cli_push_test.go:222: DockerTrustSuite.TestTrustedPushWithEnvPasswords	4.913s
09:19:04 PASS: docker_cli_push_test.go:299: DockerTrustSuite.TestTrustedPushWithExistingSignedTag	7.386s
09:19:16 PASS: docker_cli_push_test.go:279: DockerTrustSuite.TestTrustedPushWithExistingTag	5.417s
09:19:22 SKIP: docker_cli_push_test.go:371: DockerTrustSuite.TestTrustedPushWithExpiredSnapshot (Currently changes system time, causing instability)
09:19:28 SKIP: docker_cli_push_test.go:397: DockerTrustSuite.TestTrustedPushWithExpiredTimestamp (Currently changes system time, causing instability)
09:20:11 PASS: docker_cli_push_test.go:255: DockerTrustSuite.TestTrustedPushWithFailingServer	37.082s
09:20:22 PASS: docker_cli_push_test.go:351: DockerTrustSuite.TestTrustedPushWithIncorrectDeprecatedPassphraseForNonRoot	5.328s
09:20:33 PASS: docker_cli_push_test.go:329: DockerTrustSuite.TestTrustedPushWithIncorrectPassphraseForNonRoot	5.369s
09:20:47 PASS: docker_cli_push_test.go:423: DockerTrustSuite.TestTrustedPushWithReleasesDelegation	7.828s
09:20:55 PASS: docker_cli_push_test.go:267: DockerTrustSuite.TestTrustedPushWithoutServerAndUntrusted	1.849s
09:21:11 PASS: docker_cli_run_test.go:3146: DockerTrustSuite.TestTrustedRun	10.244s
09:21:33 PASS: docker_cli_run_test.go:3238: DockerTrustSuite.TestTrustedRunFromBadTrustServer	15.162s
09:21:42 PASS: docker_cli_create_test.go:303: DockerTrustSuite.TestUntrustedCreate	3.202s
09:21:51 PASS: docker_cli_pull_trusted_test.go:49: DockerTrustSuite.TestUntrustedPull	3.195s
09:22:00 PASS: docker_cli_run_test.go:3178: DockerTrustSuite.TestUntrustedRun	3.337s

I'll send a PR for that :smile:


Add initial localization support using Moment.js

Fixes #36

Review status: 0 of 7 files reviewed at latest revision, 1 unresolved discussion.

test/basic.html, line 146 [r1] (raw file):
Magic numbers for a timeout should be avoided in tests. Rather use a waitUntil(condition, callback) pattern

Comments from the review on Reviewable.io

Review status: 0 of 7 files reviewed at latest revision, 1 unresolved discussion.

test/basic.html, line 146 [r1] (raw file):
Done.

Comments from the review on Reviewable.io

Reviewed 6 of 7 files at r1, 1 of 2 files at r2.
Review status: 6 of 7 files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Reviewed 1 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 3 unresolved discussions, all commit checks successful.

test/month-calendar.html, line 29 [r2] (raw file):
Why not extract this function to common?

vaadin-date-picker-overlay.html, line 72 [r2] (raw file):
Could you specify the format of the locale with an example : ES_es ES ES-es ?

vaadin-locale-aware-behavior.html, line 7 [r2] (raw file):
This needs an annotation so as it can be parsed in hydrolysis :100:
/**
*

@polymerBehavior locale
*/

Comments from the review on Reviewable.io

Review status: all files reviewed at latest revision, 4 unresolved discussions.

vaadin-locale-aware-behavior.html, line 43 [r2] (raw file):
I'm thinking if we should fire an event instead of using this override pattern? locale-changed probably can't be used but maybe locale-ready?

Comments from the review on Reviewable.io

Review status: 2 of 9 files reviewed at latest revision, 4 unresolved discussions.

test/month-calendar.html, line 29 [r2] (raw file):
Done.

vaadin-date-picker-overlay.html, line 72 [r2] (raw file):
Done.

vaadin-locale-aware-behavior.html, line 7 [r2] (raw file):
Done.

vaadin-locale-aware-behavior.html, line 43 [r2] (raw file):
Good idea, tried it and it seems a bit cleaner.

Comments from the review on Reviewable.io

Reviewed 2 of 8 files at r3.
Review status: 3 of 9 files reviewed at latest revision, 4 unresolved discussions.

Comments from the review on Reviewable.io

Reviewed 1 of 8 files at r3.
Review status: 4 of 9 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

Comments from the review on Reviewable.io


[GLUTEN-1632][CH]Daily Update Clickhouse Version (20240731)

Auto commit by gluten daily build, please check the build status and merge it if it's green.

Run Gluten Clickhouse CI


Specify astro version compatible per tip

Perhaps a <CompatibleWith version="" /> component?

Yeah sounds good!

We could also look at adding a frontmatter value for the version (making it required), then add an override to show it on the page, and even add a warning if it's targeting an old major (e.g. "This is an Astro 3.0 recipe and may not work well with v4.0 or later")

That sounds powerful!


The Stressapptest won't keep running any more after the first 600sec

it looks working before 600sec of test time but  it just stops  after 600sec.
Linux optane 4.4.0-31-generic #50-Ubuntu SMP Wed Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Log: Commandline - stressapptest -m 56 -i 56 --local_numa -l test4.log -s 3600 -M 667133 --pause_duration 60
Stats: SAT revision 1.0.6_autoconf, 64 bit binary
Log: buildd @ kapok on Wed Jan 21 17:09:35 UTC 2015 from open source release
Log: 1 nodes, 112 cpus.
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7f0169b63000.

Log: Defaulting to 112 copy threads
Log: Total 192076 MB. Free 190754 MB. Hugepages 0 MB. Targeting 182281 MB (94%)
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7f23da35c000.

This is likely one of two problems:

the last line here indicates that stressapptest ran a load step (ramped
112 cores from idle to 100% simultaneously). So it may be that the system
encountered a power related error. Did the system stop responding, or did
stressapptest app stop responding? If the system stopped responding, this
is probably the issue.

The "power spike" feature uses pthread barriers, which have had api
changes over the years. So it may be a bug that this combination of
OS/libpthread/stressapptest just doesn't work properly, and the app is
stuck incorrectly waiting on a mutex. Can you run stressapptest with
"-m 8 --pause_duration
5 --pause_delay 20 -s 300"? This will run through the pthreads code without
causing much load on your system. If the app gets stuck but the system is
still running OK otherwise, this is likely the issue.

On Thu, Oct 26, 2017 at 7:04 PM, Kyewon Ha<EMAIL_ADDRESS>wrote:

it looks working before 600sec of test time but it just stops after 600sec.
Linux optane 4.4.0-31-generic #50
https://github.com/stressapptest/stressapptest/issues/50-Ubuntu SMP Wed
Jul 13 00:07:12 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Log: Commandline - stressapptest -m 56 -i 56 --local_numa -l test4.log -s
3600 -M 667133 --pause_duration 60
Stats: SAT revision 1.0.6_autoconf, 64 bit binary
Log: buildd @ kapok on Wed Jan 21 17:09:35 UTC 2015 from open source
release
Log: 1 nodes, 112 cpus.
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7f0169b63000.

Log: Defaulting to 112 copy threads
Log: Total 192076 MB. Free 190754 MB. Hugepages 0 MB. Targeting 182281 MB
(94%)
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7f23da35c000.

Reply to this email directly, view it on GitHub
https://github.com/stressapptest/stressapptest/issues/52, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ANkUIdHsDUDg0pqY3lOa_sGbvUupuDEvks5swToRgaJpZM4QIczB
.

stressapptest is working well on Redhat 6.8 without stop.  I think stfressapptest app stops responding because the system is still running on Linux.
--> I attached the stressapptest result on Redhat OS

this is the output result .
Log: Commandline - stressapptest -m 8 -l test5.log -s 300 -M 667133 --pause_duration 5 --pause_delay 20
Stats: SAT revision 1.0.6_autoconf, 64 bit binary
Log: buildd @ kapok on Wed Jan 21 17:09:35 UTC 2015 from open source release
Log: 1 nodes, 112 cpus.
Log: Prefer plain malloc memory allocation.
Log: Using memaligned allocation at 0x7e8613ef7000.
Stats: Starting SAT, 667133M, 300 seconds
Log: region number 1 exceeds region count 1
Log: Region mask: 0x1
Log: Seconds remaining: 290
Log: Seconds remaining: 280
Log: Pausing worker threads in preparation for power spike (280 seconds remaining)
Log: Resuming worker threads to cause a power spike (275 seconds remaining)
Log: Seconds remaining: 270
Log: Seconds remaining: 260
Log: Pausing worker threads in preparation for power spike (260 seconds remaining)
Log: Resuming worker threads to cause a power spike (255 seconds remaining)
Log: Seconds remaining: 250
Log: Seconds remaining: 240
Log: Pausing worker threads in preparation for power spike (240 seconds remaining)
Log: Resuming worker threads to cause a power spike (235 seconds remaining)
Log: Seconds remaining: 230
Log: Seconds remaining: 220
Log: Pausing worker threads in preparation for power spike (220 seconds remaining)
Log: Resuming worker threads to cause a power spike (215 seconds remaining)
Log: Seconds remaining: 210
Log: Seconds remaining: 200
Log: Pausing worker threads in preparation for power spike (200 seconds remaining)
Log: Resuming worker threads to cause a power spike (195 seconds remaining)
Log: Seconds remaining: 190
Log: Seconds remaining: 180
Log: Pausing worker threads in preparation for power spike (180 seconds remaining)
Log: Resuming worker threads to cause a power spike (175 seconds remaining)
Log: Seconds remaining: 170
Log: Seconds remaining: 160
Log: Pausing worker threads in preparation for power spike (160 seconds remaining)
Log: Resuming worker threads to cause a power spike (155 seconds remaining)
Log: Seconds remaining: 150
Log: Seconds remaining: 140
Log: Pausing worker threads in preparation for power spike (140 seconds remaining)
Log: Resuming worker threads to cause a power spike (135 seconds remaining)
Log: Seconds remaining: 130
Log: Seconds remaining: 120
Log: Pausing worker threads in preparation for power spike (120 seconds remaining)
Log: Resuming worker threads to cause a power spike (115 seconds remaining)
Log: Seconds remaining: 110
Log: Seconds remaining: 100
Log: Pausing worker threads in preparation for power spike (100 seconds remaining)
Log: Resuming worker threads to cause a power spike (95 seconds remaining)
Log: Seconds remaining: 90
Log: Seconds remaining: 80
Log: Pausing worker threads in preparation for power spike (80 seconds remaining)
Log: Resuming worker threads to cause a power spike (75 seconds remaining)
Log: Seconds remaining: 70
Log: Seconds remaining: 60
Log: Pausing worker threads in preparation for power spike (60 seconds remaining)
Log: Resuming worker threads to cause a power spike (55 seconds remaining)
Log: Seconds remaining: 50
Log: Seconds remaining: 40
Log: Pausing worker threads in preparation for power spike (40 seconds remaining)
Log: Resuming worker threads to cause a power spike (35 seconds remaining)
Log: Seconds remaining: 30
Log: Seconds remaining: 20
Log: Pausing worker threads in preparation for power spike (20 seconds remaining)
Log: Resuming worker threads to cause a power spike (15 seconds remaining)
Log: Seconds remaining: 10
Stats: Found 0 hardware incidents
Stats: Completed: 716558.00M in 300.91s 2381.31MB/s, with 0 hardware incidents, 0 errors
Stats: Memory Copy: 716558.00M at 2385.93MB/s
Stats: File Copy: 0.00M at 0.00MB/s
Stats: Net Copy: 0.00M at 0.00MB/s
Stats: Data Check: 0.00M at 0.00MB/s
Stats: Invert Data: 0.00M at 0.00MB/s
Stats: Disk: 0.00M at 0.00MB/s

Status: PASS - please verify no corrected errors
sat.log

this looks like  only Ubuntu16.04 issue.
Centos 7 has no this problem. Now  i will move to Centos 7 to test system with stresssapptest.


Update specs2-cats, specs2-core to 4.12.9

Updates

org.specs2:specs2-cats
org.specs2:specs2-core

from 4.6.0 to 4.12.9.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.specs2" } ]

labels: library-update, semver-minor

Superseded by #168.


Add Aqara E1 water leak sensor quirk

This quirk is for battery measurement.
Fixes https://github.com/zigpy/zha-device-handlers/issues/2247
-> Waiting for confirmation this quirk adds the battery measurement.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 83.814%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
6856

Relevant Lines:
8180

💛  - Coveralls

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.02 :tada:

Comparison is base (1e9d03b) 83.78% compared to head (0b60be5) 83.81%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##              dev    #2256      +/-   ##
==========================================
+ Coverage   83.78%   83.81%   +0.02%
==========================================
  Files         257      258       +1
  Lines        8167     8180      +13
==========================================
+ Hits         6843     6856      +13
  Misses       1324     1324

Impacted Files
Coverage Δ

zhaquirks/tuya/ts011f_plug.py
100.00% <100.00%> (ø)

zhaquirks/xiaomi/aqara/water_acn001.py
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Link to Json Spec file not working when using relative path

I don't know if it is a bug, but when I use relative path the link generated for the json spec file in the Swagger UI page seems not correct. here's the codes I have in my project:
public IServiceProvider ConfigureServices(IServiceCollection services){
    ...
    services.AddMvcCore().AddApiExplorer();
    services.AddSwaggerGen(c =>
            {
                c.SwaggerDoc("v1", new Info { Title = "my api", Version = "v1" });
            });
    ...
}

public void Configure(IApplicationBuilder app, IHostingEnvironment env)
{
            app.UseSwagger();
            app.UseSwaggerUI(c =>
            {
                c.SwaggerEndpoint("v1/swagger.json", "v1");
            });
}

I tried to set a relative path of the json file, it works well for the ui page and Try it out, but when I click the link of the json file at the top left, it opens me another blank page. I checked the href of the "a" tag. I get this:

v1/swagger.json

The HTML that works looks like below:

/swagger/v1/swagger.json

I don't know what happened during the process of generating the html when I use a relative path. But I don't want to use an absolute path to the spec file because I would probably set the base path later when the Api is running behind a reverse proxy server. Is there any quick fix to this specific case?

I believe this is actually a swagger-ui issue, which is a separate project independent from Swashbuckle. In fact, there appears to be a related issue already posted to that project that you should probably checkout.

Thanks, I fix the problem currently by using a absolute path.


Time axis hour only

It is possible to show only the time on the time axis, I am reviewing the documentation but it is not clear to me how to pass and format the date so that only the time is seen.
Can I see that it should be passed as a timestamp but how do I indicate that it only shows the time?
Example

See https://github.com/tradingview/lightweight-charts/blob/master/docs/time-scale.md#time-scale-options tickMarkFormatter option.

hey @timocov , the link you have provided is broken (as well as many others in the docs). Is there any updated location to find it the docs?

Is there any updated location to find it the docs?

@giladt please refer to a tag instead of master branch. For example for https://github.com/tradingview/lightweight-charts/blob/master/docs/time-scale.md#time-scale-options you use use https://github.com/tradingview/lightweight-charts/blob/v3.6.1/docs/time-scale.md#time-scale-options instead. We're in the process of creating a website for our docs (you can check current state out here https://tradingview.github.io/lightweight-charts) so that's why links don't work any more.


enhancement: detect tabline to offset the notification

Hi and thanks a lot for this plugin, it's very nice to use ! 😀
I just have a small issue : when a notification appears it will appear on top of the tabline, messing up it's background.
It's not a big deal but I've seen other plugins (not about notifications) that detect when the tabline is present to avoid such things.

Thanks again and have a good day !
LazyTanuki

Thanks for the great feedback :grin: Good idea, I hadn't noticed this issue. Please try with the latest commit!

Well that was fast ! Works great, thanks again ! 😉


Get the players that are still in a tournament

Hello,
is there a way to get the players that are still in a tournament ?

Hey! I believe this might be what you're looking for? https://texasholdem.readthedocs.io/en/stable/game_information.html#players. Players still in the tournament (i.e. game) would have states: IN, OUT, TO_CALL, ALL_IN. In other words, not SKIP state.

I'm not sure to know how I can get players who have states IN, OUT, TO_CALL, ALL_IN

Something like
game.player_iter(filter_states=(PlayerState.SKIP,))

should work

Ok thank you.


Shorten enum names

We were including prefixes to avoid collisions, but this made working with them somewhat unwieldy. This PR removes the prefixes except for the UNKNOWN cases.

Just double checking before I merge this:
I think this is a nice compromise between (a) the style guide suggestion to prefix enums rather than nest them in an enclosing message and (b) reducing complexity for users. But it does lose some of the formal specification / scoping (e.g. REACTION_SMILES vs. REACTION_IDENTIFIER_TYPE_REACTION_SMILES).
The nice thing is that there are only a few instances of actual collisions in our schema (when a message contains multiple enums), and we are unlikely to have these collisions outside of the UNKNOWN value.

Would NAME and NONE lead to conflicts as well? I noticed you kept the full prefix for the UNKNOWN options.

The current proto compiles; NAME is used multiple places, but in different messages, so it doesn't lead to a conflict. I guess the question is whether we're ok with using 'NAME' in both places and letting the surrounding code provide the scope. I think I am ok with this since the context should be pretty clear and the prefixes mostly felt redundant.

I'm not opposed to using NAME and NONE in multiple contexts. Feel free to merge this PR


Inject git information into container to see what revision the container is based on.

Yeah, I close this PR since we just figured that /code/ actually already has all the git history and thus all the good stuff to debug.

I was a bit confused because in other docker images where we intend to run them in production, I think we were not shipping the git repos, just the source code. If we get that far we can revisit the idea of putting a revision marker in the image.

oh do we? Is the deployment image not created the same way?

the AMO site is not deployed using Docker containers at all. It's still on VMs that have been built using puppet configs maintained by the ops group. The Docker containers were built with that in mind using some of the same base images (CentOS) but they aren't using the same puppet configs. Our goal is to eventually ship Docker in production where possible.

Ah I see, well, then at least for local development we can quickly debug on what revision a container is based on and for prod it'll happen once containers get shipped or so.


Better failure message when type is sent to Property initializer

Migrated from GitLab: https://gitlab.com/meltano/sdk/-/issues/225
Originally created by @aaronsteers on 2021-09-25 16:32:33

Sometimes we can accept classes in the Property type helper's constructor, and sometimes an initialized object is needed.
The error messaging on this is not clear and can be improved.

View 3 previous comments from the original issue on GitLab


Kong fails to start,/usr/local/share/lua/5.1/kong/cmd/start.lua:37: Permission denied

Please read the CONTRIBUTING.md guidelines to learn on which channels you can
seek for help and ask general questions:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#where-to-seek-for-help
Summary
SUMMARY_GOES_HERE
Steps To Reproduce
1.kong start -c /etc/kong/kong.conf -v
2. My roles and databases
postgres=# \l
                                  List of databases
   Name    |  Owner   | Encoding |   Collate   |    Ctype    |   Access privileges
-----------+----------+----------+-------------+-------------+-----------------------
 kong      | kong     | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 kong1     | jozef    | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 mydb      | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 postgres  | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 |
 template0 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres
 template1 | postgres | UTF8     | en_US.UTF-8 | en_US.UTF-8 | =c/postgres          +
           |          |          |             |             | postgres=CTc/postgres

postgres-# \du
                                   List of roles
 Role name |                         Attributes                         | Member of
-----------+------------------------------------------------------------+-----------
 Ben       |                                                            | {}
 jozef     | Create role, Create DB                                     | {}
 kong      |                                                            | {}
 miki      |                                                            | {}
 postgres  | Superuser, Create role, Create DB, Replication, Bypass RLS | {}

Additional Details & Logs

Kong version ($ kong version)
1.1.0
Kong debug-level startup logs ($ kong start --vv)

kong start --vv
2019/04/20 08:21:25 [verbose] Kong: 1.1.0
2019/04/20 08:21:25 [debug] ngx_lua: 10013
2019/04/20 08:21:25 [debug] nginx: 1013006
2019/04/20 08:21:25 [debug] Lua: LuaJIT 2.1.0-beta3
2019/04/20 08:21:25 [verbose] reading config file at /etc/kong/kong.conf
2019/04/20 08:21:25 [debug] reading environment variables
2019/04/20 08:21:25 [debug] admin_access_log = "logs/admin_access.log"
2019/04/20 08:21:25 [debug] admin_error_log = "logs/error.log"
2019/04/20 08:21:25 [debug] admin_listen = {"<IP_ADDRESS>:8001","<IP_ADDRESS>:8444 ssl"}
2019/04/20 08:21:25 [debug] anonymous_reports = true
2019/04/20 08:21:25 [debug] cassandra_consistency = "ONE"
2019/04/20 08:21:25 [debug] cassandra_contact_points = {"<IP_ADDRESS>"}
2019/04/20 08:21:25 [debug] cassandra_data_centers = {"dc1:2","dc2:3"}
2019/04/20 08:21:25 [debug] cassandra_keyspace = "kong"
2019/04/20 08:21:25 [debug] cassandra_lb_policy = "RequestRoundRobin"
2019/04/20 08:21:25 [debug] cassandra_port = 9042
2019/04/20 08:21:25 [debug] cassandra_repl_factor = 1
2019/04/20 08:21:25 [debug] cassandra_repl_strategy = "SimpleStrategy"
2019/04/20 08:21:25 [debug] cassandra_schema_consensus_timeout = 10000
2019/04/20 08:21:25 [debug] cassandra_ssl = false
2019/04/20 08:21:25 [debug] cassandra_ssl_verify = false
2019/04/20 08:21:25 [debug] cassandra_timeout = 5000
2019/04/20 08:21:25 [debug] cassandra_username = "kong"
2019/04/20 08:21:25 [debug] client_body_buffer_size = "8k"
2019/04/20 08:21:25 [debug] client_max_body_size = "0"
2019/04/20 08:21:25 [debug] client_ssl = false
2019/04/20 08:21:25 [debug] database = "postgres"
2019/04/20 08:21:25 [debug] db_cache_ttl = 0
2019/04/20 08:21:25 [debug] db_resurrect_ttl = 30
2019/04/20 08:21:25 [debug] db_update_frequency = 5
2019/04/20 08:21:25 [debug] db_update_propagation = 0
2019/04/20 08:21:25 [debug] dns_error_ttl = 1
2019/04/20 08:21:25 [debug] dns_hostsfile = "/etc/hosts"
2019/04/20 08:21:25 [debug] dns_no_sync = false
2019/04/20 08:21:25 [debug] dns_not_found_ttl = 30
2019/04/20 08:21:25 [debug] dns_order = {"LAST","SRV","A","CNAME"}
2019/04/20 08:21:25 [debug] dns_resolver = {}
2019/04/20 08:21:25 [debug] dns_stale_ttl = 4
2019/04/20 08:21:25 [debug] error_default_type = "text/plain"
2019/04/20 08:21:25 [debug] headers = {"server_tokens","latency_tokens"}
2019/04/20 08:21:25 [debug] log_level = "notice"
2019/04/20 08:21:25 [debug] lua_package_cpath = ""
2019/04/20 08:21:25 [debug] lua_package_path = "./?.lua;./?/init.lua;"
2019/04/20 08:21:25 [debug] lua_socket_pool_size = 30
2019/04/20 08:21:25 [debug] lua_ssl_verify_depth = 1
2019/04/20 08:21:25 [debug] mem_cache_size = "128m"
2019/04/20 08:21:25 [debug] nginx_admin_directives = {}
2019/04/20 08:21:25 [debug] nginx_daemon = "on"
2019/04/20 08:21:25 [debug] nginx_http_directives = {}
2019/04/20 08:21:25 [debug] nginx_optimizations = true
2019/04/20 08:21:25 [debug] nginx_proxy_directives = {}
2019/04/20 08:21:25 [debug] nginx_sproxy_directives = {}
2019/04/20 08:21:25 [debug] nginx_stream_directives = {}
2019/04/20 08:21:25 [debug] nginx_user = "nobody nobody"
2019/04/20 08:21:25 [debug] nginx_worker_processes = "auto"
2019/04/20 08:21:25 [debug] origins = {}
2019/04/20 08:21:25 [debug] pg_database = "kong"
2019/04/20 08:21:25 [debug] pg_host = "<IP_ADDRESS>"
2019/04/20 08:21:25 [debug] pg_password = "******"
2019/04/20 08:21:25 [debug] pg_port = 5432
2019/04/20 08:21:25 [debug] pg_ssl = false
2019/04/20 08:21:25 [debug] pg_ssl_verify = false
2019/04/20 08:21:25 [debug] pg_timeout = 5000
2019/04/20 08:21:25 [debug] pg_user = "kong"
2019/04/20 08:21:25 [debug] plugins = {"bundled"}
2019/04/20 08:21:25 [debug] prefix = "/usr/local/kong/"
2019/04/20 08:21:25 [debug] proxy_access_log = "logs/access.log"
2019/04/20 08:21:25 [debug] proxy_error_log = "logs/error.log"
2019/04/20 08:21:25 [debug] proxy_listen = {"<IP_ADDRESS>:8000","<IP_ADDRESS>:8443 ssl"}
2019/04/20 08:21:25 [debug] real_ip_header = "X-Real-IP"
2019/04/20 08:21:25 [debug] real_ip_recursive = "off"
2019/04/20 08:21:25 [debug] ssl_cipher_suite = "modern"
2019/04/20 08:21:25 [debug] ssl_ciphers = "ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256"
2019/04/20 08:21:25 [debug] stream_listen = {"off"}
2019/04/20 08:21:25 [debug] trusted_ips = {}
2019/04/20 08:21:25 [debug] upstream_keepalive = 60
2019/04/20 08:21:25 [verbose] prefix in use: /usr/local/kong
2019/04/20 08:21:25 [debug] loading subsystems migrations...
2019/04/20 08:21:25 [verbose] retrieving database schema state...
2019/04/20 08:21:25 [verbose] schema state retrieved
2019/04/20 08:21:25 [verbose] preparing nginx prefix directory at /usr/local/kong
2019/04/20 08:21:25 [verbose] could not start Kong, stopping services
2019/04/20 08:21:25 [verbose] stopped services
Error:
/usr/local/share/lua/5.1/kong/cmd/start.lua:61: /usr/local/share/lua/5.1/kong/cmd/start.lua:37: Permission denied
stack traceback:
	[C]: in function 'error'
	/usr/local/share/lua/5.1/kong/cmd/start.lua:61: in function 'cmd_exec'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:88>
	[C]: in function 'xpcall'
	/usr/local/share/lua/5.1/kong/cmd/init.lua:88: in function </usr/local/share/lua/5.1/kong/cmd/init.lua:45>
	/usr/local/bin/kong:7: in function 'file_gen'
	init_worker_by_lua:47: in function <init_worker_by_lua:45>
	[C]: in function 'xpcall'
	init_worker_by_lua:54: in function <init_worker_by_lua:52>

Kong error logs (<KONG_PREFIX>/logs/error.log)
Kong configuration (the output of a GET request to Kong's Admin port - see
https://docs.konghq.com/latest/admin-api/#retrieve-node-information)
Operating system
Ubuntu 18.04

Can you check if this has any effect:
https://github.com/Kong/kong/pull/4506

Also do you have /usr/local/kong that is writable?

I think so.
root@miki:/usr/local# ls -lia kong
total 76
6554396 drwxr-xr-x  5 root root  4096 апр 19 08:44 .
6553606 drwxr-xr-x 13 root root  4096 апр 19 08:44 ..
6562765 drwxr-xr-x  2 root root  4096 апр 19 08:44 bin
6554732 -rw-r--r--  1 root root 55501 мар 27 02:09 COPYRIGHT
6554949 drwxr-xr-x  3 root root  4096 апр 19 08:44 include
6562768 drwxr-xr-x  4 root root  4096 апр 19 08:44 lib
On Sat, 20 Apr 2019 at 10:13, Aapo Talvensaari<EMAIL_ADDRESS>wrote:

Also do you have /usr/local/kong that is writable?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Kong/kong/issues/4529#issuecomment-485068873, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADGXD6D2TOVPOTJI6S6UOU3PRLGAZANCNFSM4HHJBYTQ
.

I am struggling to understand what should I really do. That commit c1fbfa7 puzzles me.

How did you install and OS details?

if you want to make quick test, then:
sudo chmod -R 777 /usr/local/kong
There are two users:

the one that starts nginx master process (and start kong)
the one that is used to run nginx workers

forget that commit for now as this is not a pg problem. My mistake.

How did you install and OS details?
Ubuntu 18.04. I used the link from the standard repo for Bionic download. After that
 sudo dpkg -i kong-community-edition-1.1.0.bionic.all.deb

I edited kong.conf by uncommenting only these lines
database = postgres

pg_host = <IP_ADDRESS>
pg_port = 5432
pg_timeout = 5000
pg_user = kong
pg_password = mysecretpassword
pg_database = kong

I can't reproduce
docker run -d --name kong-database \
-p 5432:5432 \
-e "POSTGRES_USER=kong" \
-e "POSTGRES_DB=kong" \
postgres:9.6

curl -L -o kong.deb https://bintray.com/kong/kong-community-edition-deb/download_file?file_path=dists/kong-community-edition-1.1.0.bio
nic.all.deb
dpkg -i kong.deb
apt-get install -f

export POSTGRES_USER=kong
export POSTGRES_DB=kong
kong migrations bootstrap
... SNIP ...
23 migrations processed
23 executed
database is up-to-date
kong start --vv
2019/04/20 12:49:35 [verbose] Kong: 1.1.0
2019/04/20 12:49:35 [debug] ngx_lua: 10013
2019/04/20 12:49:35 [debug] nginx: 1013006
2019/04/20 12:49:35 [debug] Lua: LuaJIT 2.1.0-beta3
2019/04/20 12:49:35 [verbose] no config file found at /etc/kong/kong.conf
2019/04/20 12:49:35 [verbose] no config file found at /etc/kong.conf
2019/04/20 12:49:35 [verbose] no config file, skip loadin
... SNIP ...
2019/04/20 12:49:35 [debug] searching for OpenResty 'nginx' executable
2019/04/20 12:49:35 [debug] /usr/local/openresty/nginx/sbin/nginx -v: 'nginx version: openresty/<IP_ADDRESS>'
2019/04/20 12:49:35 [debug] found OpenResty 'nginx' executable at /usr/local/openresty/nginx/sbin/nginx
2019/04/20 12:49:35 [debug] sending signal to pid at: /usr/local/kong/pids/nginx.pid
2019/04/20 12:49:35 [debug] kill -0 `cat /usr/local/kong/pids/nginx.pid` >/dev/null 2>&1
2019/04/20 12:49:35 [debug] starting nginx: /usr/local/openresty/nginx/sbin/nginx -p /usr/local/kong -c nginx.conf
2019/04/20 12:49:35 [debug] nginx started
2019/04/20 12:49:35 [info] Kong started

System information
root@ip-172-31-24-121:/# lsb_release -a
LSB Version:    core-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:    Ubuntu 18.04.2 LTS
Release:        18.04
Codename:       bionic
root@ip-172-31-24-121:/# uname -a
Linux ip-172-31-24-121 4.4.0-1079-aws #89-Ubuntu SMP Tue Mar 26 15:25:52 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I believe this is a duplicate and your problem would be resolved with the suggestions here: https://github.com/Kong/kong/issues/2690#issuecomment-314457853

2019-04-20 17:34:34.005 CEST [1400] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
2019-04-20 17:34:34.006 CEST [1400] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2019-04-20 17:34:34.039 CEST [1419] LOG:  database system was shut down at 2019-04-20 13:55:55 CEST
2019-04-20 17:34:34.054 CEST [1400] LOG:  database system is ready to accept connections
2019-04-20 17:34:34.574 CEST [1708] [unknown]@[unknown] LOG:  incomplete startup packet

Output root@miki:/var/log/postgresql#
What does unknown mean?

@MilenkoM that looks like Postgres log message. Probably nothing bad, and I hardly think it has anything to do with your issues. Did you try:
$ sudo chmod -R 777 /usr/local/kong

Before starting Kong?

I changed permissions now,works perfect.
sudo chmod -R 777 /usr/local/kong
You can close the issue.

Just want to say thank you guys. This fixed issue I had with Kong were not able to load AdminAPI for my plugin, even though Luarock package and module was installed properly.
sudo chmod -R 777 /usr/local/kong


Task/issue 1157 dark light navbar toggler

Changes in this Pull Request:

table header color depending on used theme.

Mandatory checks:

[X] Branch is up to date (latest changes were fetched from the upstream branch before creating this PR)
[X] Changes were tested manually
[ ] Java code changes are unit tested
[ ] Webtests are successful

To be checked by the reviewer:

[ ] Clean Java code and unit tested changes
[X] UI customizablity is preserved: No hard-coded styling and URL references in JSF views

To be checked by the pull request owner:

[ ] .MASTER/job/BES_MASTER_IT/
[ ] .MASTER/job/OSCM_WS_Tests_INTERNAL/
[ ] .MASTER/job/OSCM_WS_Tests_OIDC/
[ ] .MASTER/job/OSCM_Integration_Tests_INTERNAL/
[ ] .MASTER/job/OSCM_Integration_Tests_OIDC/

Cross repository and core changes:

[ ] Interdependent changes have been communicated to the team (if applicable)
[ ] This pull request includes high risk modifications or core changes (e.g API, datamodel, authentication...). Mandatory reviewers: @goebell or @kowalczyka.

OSCM Build References:

est6

Screenshot (if applicable):

This change is

Created new branch from master for this tiny PR.

Created new branch from master for this tiny PR.


Error when running powershell over SSH

I just ran the https://github.com/PowerShell/Win32-OpenSSH/releases/tag/12_22_2015 release from OpenSSH, the 64 bit version. I created the sshd server on windows. Then, I ssh'd on a Linux VM on the same machine, then ssh'd back to Windows. It started a cmd session.
The log bellow showed when I ran powershell interactive, from the cmd session. Every <ENTER> would present the error again.
I hope it helps. If you need more info let me know.
-----------------------------------------------------------------------
Last 0 Keys:

Exception:
System.IO.IOException: The handle is invalid.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.Console.GetBufferInfo(Boolean throwOnNoConsole, Boolean& succeeded)
   at Microsoft.PowerShell.PSConsoleReadLine.Initialize(Runspace runspace, EngineIntrinsics engineIntrinsics)
   at Microsoft.PowerShell.PSConsoleReadLine.ReadLine(Runspace runspace, EngineIntrinsics engineIntrinsics)
-----------------------------------------------------------------------

Most likely a dupe of #158, reopen with additional information if you disagree.


Figure out how to use existing keyboard bindings

We currently hard code controller inputs. This would be infinitely better if we just took the ingame mapping.

a full key rebind system really needs to be implemented including for VR controllers.   this probably needs to be a separate mod but I agree this would help tremendously


[Core]: Handle Kind mentioned in bindings selector

The kind is being removed from the selector.
Here is the proposal - https://docs.google.com/document/d/1-zxAMBpX-ZdpmDTjS0qzmFk5pueOCtLaGa970KJLTNc/edit?usp=sharing


Getting TypeError: Cannot read property 'clientHeight' of undefined

Hello!
I am getting
TypeError: Cannot read property 'clientHeight' of undefined
this error when I try to go to other route using zeit/next.
any hint how to fix this?
Thanks.

@oiojin831 Is this something specific about your routes? I need more data or a real example for this. No idea what would cause it, clientHeight gets called in Parallax.update, which fetches container from this.refs. If it doesn't find the container, something's going on ...

I also came across this while navigating to another page. I don't believe the issue is related to the router. It's a case where both the Layer and Parallax components are unmounted at the same time.
The error reported by @oiojin831 occurs when <Layer> is unmounted, requests an update() on the <Parallax> container, but the container DOM element no longer exists.
It would appear parents are unmounted before their children, which surprises me.

@oiojin831 @storybynumbers Very strange. I have never worked with next, is that specific to it?
Anyway, i have patched it, so that it doesn't take parent for granted. I guess if Parallax goes before the Layer there isn't much point in updating it anyway. It's up on npm as well, would be very glad if you could test if that's already fixing it.

Sorry for the late reaction @drcmda ! The new version is working, I've tested it locally. Thanks! :)