glusterfs: 9.2 -> 9.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/glusterfs/versions.
meta.description for glusterfs is: "Distributed storage system"
meta.homepage for glusterfs is: "https://www.gluster.org"
meta.changelog for glusterfs is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/glusterfind passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/fusermount-glusterfs passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gcron.py passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gf_attach passed the binary check.

Warning: no invocation of /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gfind_missing_files had a zero exit code or showed the expected version

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gluster passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gluster-eventsapi passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gluster-georep-sshkey passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gluster-mountbroker passed the binary check.

Warning: no invocation of /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/gluster-setgfid2path had a zero exit code or showed the expected version

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/glusterd passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/glustereventsd passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/glusterfs passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/glusterfsd passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/mount.glusterfs passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/snap_scheduler.py passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.glusterd-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.gluster-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.mount.glusterfs-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.gluster-eventsapi-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.gluster-georep-sshkey-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.gluster-mountbroker-wrapped passed the binary check.

/nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin/.glusterfind-wrapped passed the binary check.

14 of 23 passed binary check by having a zero exit code.

16 of 23 passed binary check by having the new version present in output.

found 9.3 with grep in /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3

found 9.3 in filename of file in /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3

directory tree listing: https://gist.github.com/40412b33e25f6471cbd88bac93d1c1c5

du listing: https://gist.github.com/362249660c999fa09167ec6a084a7b7e

Rebuild report (if merged into master) (click to expand)

33 total rebuild path(s)

15 package rebuild(s)

15 x86_64-linux rebuild(s)
7 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
7 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
bareos
glusterfs
libvmi
qemu_full
qemu_xen
qemu_xen_4_10
qubes-core-vchan-xen
xen
xen-slim
xenPackages.xen-slim
xenPackages.xen-vanilla
xenPackages.xen_4_10-slim
xenPackages.xen_4_10-vanilla
xen_4_10
xen_4_10-slim

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A glusterfs https://github.com/r-ryantm/nixpkgs/archive/f2534072e2d17f11d2e95533b012135cc9d1aa76.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3
ls -la /nix/store/5vbx3k47zmmds7gnmcy36bg7wlbmqrhy-glusterfs-9.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package marked as broken and skipped:

bareos

7 packages built:

glusterfs
libvmi
qemu_full
qemu_xen (qemu_xen_4_10)
qubes-core-vchan-xen
xen
xen-slim

Maintainer pings
cc @7c6f434c for testing.

Result of nixpkgs-review pr 129266 at f2534072 run on aarch64-linux 1

4 packages marked as broken and skipped:

libvmi
qemu_xen
qemu_xen_4_10
qubes-core-vchan-xen

1 package skipped due to time constraints:

bareos

2 packages built successfully:

glusterfs
qemu_full

@ofborg test glusterfs


Input arguments to modcmaes.fmin

From the example in the readme
modularcmaes.fmin(func=sum, dim=5, maxfun=100)

I wonder why the fmin function does not take an initial solution as input and what is the initial value used by fmin (or modularcmaes.ModularCMAES for that matter)?
It seems strange to me to assume a default initial solution value because it heavily depends on the problem and use-case. Similarly, I believe that the initial step-size sigma should be an input to the algorithm for which the user should be commandingly invited to make a decision, because it also depends on the problem and the desired use-case.

Thank you for your comment. We know that documentation is not yet up to standards, and we indeed only have included very minimal usage examples in the readme. We are planning to improve this in the future.
In principle, these and many more parameters can be passed as keyword arguments to both the class and the fmin based ways of calling the method.
For changing the value for sigma, you could pass the option sigma0=... for example, and x0 controls the initial setting of the centre of mass.
Hope this helps.

Thank you for your comment. We know that documentation is not yet up to standards, and we indeed only have included very minimal usage examples in the readme. We are planning to improve this in the future.
In principle, these and many more parameters can be passed as keyword arguments to both the class and the fmin based ways of calling the method.

Right, my point though would be to a lesser extend about which optional parameters can be passed if desired. I rather wanted to raise the question which parameters should be exposed and mandatory to pass in order to best reflect the semantics of the algorithm.


[Bug] All Objects with Outline component are drawn

All objects which have an outline component are drawn all the time. Regardless if  eraseRenderer is set to true or not.
Maybe I misunderstood the concept of the component. But if the outline should not be displayed when eraseRenderer is off, you would need to apply the following patch in OutlineEffect.OnPreRender:
// ...
            if(outlines != null)
            {
                foreach(Outline outline in outlines)
                {
                    LayerMask l = sourceCamera.cullingMask;

                    if(outline != null && l == (l | (1 << outline.originalLayer)))
                    {
                        //PATCH START
                        if (outline.eraseRenderer)
                            continue;
                        //PATCH END

                        for (int v = 0; v < outline.Renderer.sharedMaterials.Length; v++)
// ...

The point of eraseRenderer is to draw an object on top of the outline buffer so it "erases" outlines behind it so yes, it's supposed to render.


4bit inference is slow

Thanks for the excellent work.
When I use 4bit to inference, it's very slow, even slower than 8bit inference.
Will you plan to solve the problem, thanks~

I think Tim is working on the 4bit inference kernel which hopefully will be available in the coming weeks

I think Tim is working on the 4bit inference kernel which hopefully will be available in the coming weeks

During inference, Will the model also convert between fp16 and nf4? If so, does the inference kernel  make up that time?
BTW, maybe you guys can checkout https://github.com/qwopqwop200/GPTQ-for-LLaMa/tree/fastest-inference-4bit. In my test, it is even faster than fp16 in a a10.

Yes, this one is pretty fast around 2x faster in 4bits that fp16.
But faster qlora will be better as it supports most models available. With GPTQ you can pretty much only do gpt like models.

Any updates on the 4bit inference kernel? @JianbangZ
I am also experiencing issues with inference speed.

We have written a small script to convert models trained with QLoRA to CTranslate2 to speed up inference here https://github.com/Actable-AI/llm-utils/blob/main/qlora2ct2/convert_qlora2_ct2.py

@trunghlt thanks for sharing - do you have any benchmarks that compare the speed improvement with CTranslate2?

for us, it's 4x-6x speed up.

thanks @trunghlt what type of hardware are you running? A100s?

We have successfully converted mt0-xxl on RTX6000

We have successfully converted mt0-xxl on RTX6000

What's the absolute number you see? how many token/s or ms/token?

Ctranslate2 have much more than ggml and GPTQ because they support a lot of diffences model, not just encoder only. Also they support batching so inference much more optimize.
And when i tested with mt0 xxl, which takes about  > 40gb if load full, after convert to CT2 and use "int8_float16" quantization, it only takes about <  20gb and inference much faster.
I will provide the benchmark of inference time soon.

@JianbangZ On my setting, if you convert mt0 xxl (13B) model into ct2 (using int8_float16 quantization), and then do inference with compute_type = int8_float16 and 300 samples on RTX6000, there are some numbers:

Beam_size = 1, batch_size = 1 (mean do inference with batch = 1), avg_input_token = 143 (I just split input and calculate the length) --> latency_per_output_token = 25.51ms/tok, output_tok_per_sec = 39.53tok/sec
Beam_size = 1, batch_size = 5, avg_input_token = 143 --> latency_per_output_token = 34.17ms/tok, output_tok_per_sec = 31.65tok/sec

@JianbangZ  @vgoklani  if you further set the batch_size = 4, ((mean do inference with batch = 1) and beam_size = 5 with the same setting as above, the inference speed is 2x faster compared to batch_size = 1: latency_per_output_token=16.65ms/tok, output_tok_per_sec=67.64tok/sec

thanks @trannhatquy how good is the quantization? Do you have a ppl comparison? I'm planning to use MPT-7B and eventually MPT-30B

@vgoklani  I just compare based on my tasks (name entity recognition, absa and relation extraction), the performance (accuracy, f1, recall) of quantization ct2 model of mt0 xxl is just 0.5% to 1.5% lower than the full mt0 xxl model, this decrease is negligible in term of inference speed. And also ctranslate2 support MPT model

We used jetson Orin 16G and found that 4bit is slower than 8bit
8bits: 2.29 tokens/sec
0.73 tokens/sec

How does this deal with the mixed precision problem of merging?
Generally the base model is in 4-bit and the LoRA adapter in 16-bit.  If you merge this your LoRA adapter, its weights are lowered to 4 bit.  -> loss of performance w.r.t. keeping a separate adapter.

How does this deal with the mixed precision problem of merging?
Generally the base model is in 4-bit and the LoRA adapter in 16-bit. If you merge this your LoRA adapter, its weights are lowered to 4 bit. -> loss of performance w.r.t. keeping a separate adapter.

Actually qlora not actually save the model in 4-bit (as far as i know). Its only use 4bit when training and when u merge 16bit adapter to 16 bit base model, the precision is not mixed so i don't think that a problem.


EC2 default AMI is the latest alinux2 for x64

Issue #, if available: N/A
Description of changes: ec2.yaml refers to AMI id directly, which requires the template be updated frequently after every alinux2 release in order to benefit from patches & security updates. The proposed change should alleviates this problem by avoiding direct reference to AMI id, and instead, let SSM to resolve the AMI id of the latest alinux2.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Thanks!


header styling

@Tejas1510 can we do changes in header like this:

@Tejas1510 I would like to work on this..

Go ahead @Khimit

Go ahead @Khimit

I need to change code in .jss2 class but not able to find where it is in
our project folder.
Can you plz help .
I got stuck at that.
On Fri, Jan 1, 2021, 3:31 PM Tejas1510<EMAIL_ADDRESS>wrote:

Assigned #38 https://github.com/Tejas1510/Athavani/issues/38 to @Khimit
https://github.com/Khimit.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Tejas1510/Athavani/issues/38#event-4160834443, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDSJWKK2FCYD3DQIMYAMD3SXWMOHANCNFSM4VQEWB3Q
.

I need to change code in .jss2 class but not able to find where it is in
our project folder.
Can you plz help .
I got stuck at that.
On Fri, Jan 1, 2021, 3:31 PM Tejas1510<EMAIL_ADDRESS>wrote:

Assigned #38 https://github.com/Tejas1510/Athavani/issues/38 to @Khimit
https://github.com/Khimit.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/Tejas1510/Athavani/issues/38#event-4160834443, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDSJWKK2FCYD3DQIMYAMD3SXWMOHANCNFSM4VQEWB3Q
.

I think so you want to add some styling which can be added in style.js file

I think so you want to add some styling which can be added in style.js file

I am able to style heading letters through style.js but not able to change
background colour in heading .
Please suggest something.
On Fri, Jan 1, 2021, 11:38 PM Tejas1510<EMAIL_ADDRESS>wrote:

I think so you want to add some styling which can be added in style.js file
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Tejas1510/Athavani/issues/38#issuecomment-753358841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDSJWJA6QWZVC4OXSV7TPDSXYFQJANCNFSM4VQEWB3Q
.

I am able to style heading letters through style.js but not able to change
background colour in heading .
Please suggest something.
On Fri, Jan 1, 2021, 11:38 PM Tejas1510<EMAIL_ADDRESS>wrote:

I think so you want to add some styling which can be added in style.js file
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Tejas1510/Athavani/issues/38#issuecomment-753358841,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALDSJWJA6QWZVC4OXSV7TPDSXYFQJANCNFSM4VQEWB3Q
.

@Tejas1510 please review my PR #46

@Tejas1510 please review my PR #46


SOLR-15342: Separate out a SolrJ-Zookeeper module

https://issues.apache.org/jira/browse/SOLR-15342

I open this PR in draft to share the evolution of the work. I closed the old PR since it has been open for a while, there have been quite a few changes since then in relation to ZooKeeper and some of the work has been contributed in a separate PR.
I resume the work done in the latter in this one

Thanks for getting this started again @haythemkh! As a first-pass I suggest that we put the current solrj functionality into solrj/core. Once that is committed, we can then do what this PR does, but split it out into solrj/zookeeper instead of solrj-zookeeper. I do not think we want to have all of the solrj libraries as folders under solr/ directly.

Once that is committed, we can then do what this PR does

@HoustonPutman A change like that risks Haythem having to start over an additional time.  I am encouraging him to get this done quickly so avoid it getting stale as what happened last time (which was depressing).  If we want to have solrj/core then I propose that happen in this issue at the end, or in a follow-on PR.

Ok I will do it following this getting merged

oops, was trying to be helpful resolving the merge conflict but forgot to compile locally before pushing, sorry. will try to fix, or else commit reversion logically should also be possible? sorry for the noise.

oops, was trying to be helpful resolving the merge conflict but forgot to compile locally before pushing, sorry. will try to fix, or else commit reversion logically should also be possible? sorry for the noise.

added 3 commits to make it compile a little more but not fully. not sure if it was compiling before actually. again, sorry for the noise.

@haythemkh I know you are using the Google Java Format IntelliJ plugin but not the IntelliJ code style that accompanies it, which ensures that the import wildcards are configured correctly (the plugin can't do that part).  See https://github.com/google/google-java-format#intellij-android-studio-and-other-jetbrains-ides
FYI @epugh it would be cool to mention this somewhere for contributor onboarding

I would love to have your feedback on what we want to do with the nocommits:

These include copying ZkStateReader constants for solrj classes: Utils, PerReplicaStates, ClusterState, DocCollection, Slice, Replica, ZkCoreNodeProps, CloudSolrClient, BaseHttpClusterStateProvider, CollectionAdminRequest, CoreAdminRequest
Use raw "http" instead of going through #getClusterProperty in DatabaseMetaDataImpl

PerReplicaStates

Is there any reason for PRS not to be in the zk module? I don't think it would be used if we aren't communicating with ZK.

Copy of ZkStateReader constants to solrj classes

Would it make more sense to have one ClusterStateProps class to hold these? We could also split it into ClusterProps, CollectionProps, etc, but that might be overkill.

PerReplicaStates is referenced in ClusterState, DocCollection, and Replica.  Based on my very limited understanding of PRS, it's a part of the state of a collection no matter how it's retrieved (via ZK or via SolrClient based ClusterStateProvider).  Am I right @noblepaul @chatman  ?
I do like your suggestion of those 3 "Props" classes for constants.  How do we get there from here?  Directly, even if it changes import statement in lots more classes (I would assume)?  This is the easiest path.  Or do we leave that for another JIRA issue (soon) and for now just remove the nocommits about this to make precommit happy?  Also relatively easy but leaves some WIP.  Or go part way here & now -- add the new classes & constants but only use them in solrj-zookeeper right now and then migrate the rest in another issue?  More work.
I would like to point out that this new separation did move some tests to solrj-zookeeper but it's only four -- that's it.  Many solrj tests indirectly use ZK and I suppose that's okay.  There is a compile time dependency on ZK from solrj tests that is unfortunate but couldn't be avoided in a few cases (without investing additional work):

StreamingTest.streamLocalTests  calls zkStateReader.forceUpdateCollection
TestCloudSolrClientConnections calls cluster.getZkClient()
org.apache.solr.client.solrj.impl.HttpClusterStateSSLTest#testHttpClusterStateWithSSL calls cluster.getZkClient()
Perhaps these might even move but on the other hand, it's not some big deal to add an explicit dependency on solrj tests to ZK when ZK is definitely already there at runtime via the solrj-zookeeper dependency.

There is a weird dependency check problem that I can't figure out:
Execution failed for task ':solr:solrj-zookeeper:analyzeTestClassesDependencies'.
> Dependency analysis found issues.
  usedUndeclaredArtifacts
   - org.apache.solr:solrj-zookeeper:10.0.0-SNAPSHOT@

So solrj-zookeeper's tests depend on solrj-zookeeper.  Well of course it does ;-)

A big obstacle I'm seeing is split packages between solrj & solrj-zookeeper with respect to javadocs.  For example the javadocs for solr-core will now contain broken links to most solrj-zookeeper classes because the javadoc tool can't figure this out (kind of a long-standing deficiency).
Personally, I'm not very sympathetic to the needs of continuing to maintain a javadoc site.  I don't use them, I doubt others do, and moreover for open-source, really the source is what we want to see because it's better / more.  That's me, anyway.  I don't think maintaining them is more important than other goals like modularization, and thus I'm willing for there to be some degradation there.
Options:

In our javadocs, stop linking out to solrj or solrj-zookeeper because they cannot be differentiated by the standard javadoc tool.
Accept broken links; stop checking for them within javadoc folders.
Fix it (not something I'm willing to invest in)

Of course in main/10.0 we can remove the split packages but that's a back-combat break that isn't okay for 9.x.
CC @uschindler -- I'm curious what you think

In our javadocs, stop linking out to solrj or solrj-zookeeper because they cannot be differentiated by the standard javadoc tool.

This seems acceptable for 9.x, and in main branch we could change package names and re-introduce some links if needed?

@sigram There is an abstraction SolrCloudManager and some related classes (DistributedQueue, DistribStateManager, NodeStateProvider) that you introduced once upon a time that don't seem to have anything to do with SolrJ yet you put them there.  I believe these could go to Solr Core.  Most need to at least go to Solrj-zookeeper because of DistributedQueue's reference of ZK classes.

For constants related to the collection's state, I put it in an inner interface DocCollection.CollectionSProps.  The "S" there is for State.  If that's removed, then it's possibly confused with CollectionProperties.  It's mostly an internal set of constants (it's not parameters) so I think it's okay it it doesn't roll off the tongue.  Likewise I put constants for the Replica in Replica.ReplicaSProps.  I'm not married to these choices.
There is a CollectionAdminParams class but it was missing quite a number of parameters that CollectionAdminRequest needed to specify so I moved them there.
There were a handful of other constants then I mostly made private and didn't fret over possible redundancy with ZkStateReader.
Overall I like having these props or params as constants in suitable locations, especially when we don't static import these constants.  It adds clarity to the spots where they are referred to as being related to parameters or properties or whatever it is.
The only thing that remains is the javadoc split package concern.  It should only be a handful of lines of code or so in render-javadoc.adoc to special case them to not inter-link.

At the risk of bikeshedding....   How about ReplicaStateProps.LEADER instead of ReplicaSProps.LEADER since we don't have an existing concept of SProps throughout our codebase?

Other than a CHANGES.txt entry, I think this PR is ready.

Looks like the content about CloudSolrClient in the ref guide (https://solr.apache.org/guide/solr/latest/deployment-guide/solrj.html#building-and-running-solrj-applications)  refers to the use of the solr url for confiugration   I wonder if we should tweak the text thgouh to stress that using ZK is a vulnerability?  Similar to what you put in the upgrade notes?
Also, do we need to mention the need for solrj-zookeeper dependency for CloudSolrClient users?

Really looking forward to this!

Docs look good!

:shipit: ???

Planned commit message after the first line:
• CloudSolrClient builders use reflection to instantiate ZkClientClusterStateProvider when needed
• CollectionAdminParams constants
• CollectionStateProps constants
• SliceStateProps constants
• ReplicaStateProps constants
• SolrJ streaming expressions: don’t depend on ZK anymore
• javadocs: temporarily unlink to solrj modules due to split package issue
• PerReplicaStates.fetch -> PerReplicaStatesFetcher
• ZkStateReader.getCollectionPath -> DocCollection.getCollectionPath

Some other code changes seemed too obscure to mention.

I think it's done and I've addressed comments.  I would love to see this merged soon so as to unblock other efforts that touch lots of files.  If nobody has further review comments, I'll merge it Thursday.


Update README.md

Hi,
This small and useless PR adds two buttons to get your app on F-Droid and Google Play :+1:

Great, thanks!


[Doc bug] tf.sparse.concat doesn't have argument expand_nonconcat_dim

URL(s) with the issue:
https://www.tensorflow.org/api_docs/python/tf/sparse/concat
Description of issue (what needs changing):
The signature of API  tf.sparse.concat  doesn't have argument expand_nonconcat_dim

But in the Argument section, it describes argument expand_nonconcat_dim

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): MacOS Mojave 10.14
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.3.0
Python version: 3.7.6

Added a PR #46040 for the fix.


Allow sending messages to channel from a client that is not a member of a channel

RFC 2811 defines a channel mode n:
No Messages To Channel From Clients On The Outside

When the channel flag 'n' is set, only channel members MAY send
messages to the channel.
This flag only affects users.

We don't have to implement this mode per the subject requirements.
Our current implementation inherently implements this mode, without advertising it to the clients using our server and without any ability to toggle it by channel operators.

This would require refactoring the current implementation, and adding a new channel mode n.


Remove all components

What's it for?

removes components of an entity when a connection ends. to save memory perhaps? it'd be useful to save data of an entity that disconnected.

of an entity???
do you mean the player?


Show full OU hierarchy in overview of Eligibility/Approver

Currently, only the name of assigned OU is displayed, it would be nice if the full Organisation tree structure is shown (e.g. Root -> Layer 1 -> Layer 2)
Example how I see our configuration:

Let's keep it open, at least until  somebody responds

No feedback yet

No feedback yet

We also have an OU structure where the child OUs of some parent OUs are the same name. It looks like it's for the same reason as we have the environment level low down. This would also be a very helpful feature for ourselves.


Can I rely on didChangeConfiguration to be always called after server initialization?

Hi,
Looking at the startup sequence of my LS under VSCode, I noticed that the didChangeConfiguration notification seems to be always sent before the first didOpen. I had the idea to rely on that to get the initial values of my extension settings (to avoid passing them as initialize params, or doing an extra configuration request). But then I realized this behavior doesn't seem to be specified in the LSP. Is it intentional? Can I rely on it? Will it be future proof?
[Trace - 15:17:14] Sending request 'initialize - (0)'.
[Trace - 15:17:23] Sending notification 'initialized'.
[Trace - 15:17:23] Sending notification 'workspace/didChangeConfiguration'.
[Trace - 15:17:23] Sending notification 'textDocument/didOpen'.

No, you can not rely on this since it is not speced that way. In general you should rely on the new way to getting configuration by using the workspace/configuration request that is sent from the server to the client. See https://microsoft.github.io/language-server-protocol/specification#workspace_configuration.


docs: Add semantics to fileReader

The docs at https://github.com/tus/tus-js-client/blob/beea5983cc79d6d61b65d150cef8809114873661/docs/api.md#filereader show the type signatures, but they don't explain what the values mean.
interface FileReader {
  openFile(input: any, chunkSize: number): Promise<FileSource>
}

interface FileSource {
  size: number
  slice(start: number, end: number): Promise<SliceResult>
  close()
}

interface SliceResult {
  // Platform-specific data type which must be usable by the HTTP stack as a body.
  value: any
  done: boolean
}

For example:

What's the meaning of done: boolean, to what value should one set it? The code at https://github.com/tus/tus-js-client/blob/beea5983cc79d6d61b65d150cef8809114873661/lib/upload.js#L784-L791
suggests it's to indicate the end of the stream when uploadLengthDeferred is used. So I guess there are 2 possible cases:
a. uploadLengthDeferred = true, FileSource.size = Infinity -- in that case, probably my slice() function must also be prepared to receive end = Infinity, and I should set done = true exactly when I know that the streaming is now finished.
b. uploadLengthDeferred = false, in that case FileSource.size must be finite, my slice will only be called with finite end, and it is irrelevant what I set done to because the value is not read.
Is there any other contract over what the paremeters in slice(start, end) will be? For example:
a. Is end the exclusive boundary, like in Blob.slice()?
b. Will it be that end - start <= chunkSize (the chunkSize that was passed to openFile())?

One can guess answers from the current code, but since this is an interface, it would be nice to know what invariants will hold in the future.

Good point, thanks for bringing this up. The documentation could definitely be improved here.

2. a. Is end the exclusive boundary, like in Blob.slice()?

Yes, see https://github.com/tus/tus-js-client/blob/beea5983cc79d6d61b65d150cef8809114873661/lib/node/sources/FileSource.js#L41-L46

2. b. Will it be that end - start <= chunkSize (the chunkSize that was passed to openFile())?

If end is finite, yes. But be aware that end might also be Infinity.

What's the meaning of done: boolean, to what value should one set it?

done indicates if subsequent calls to slice will not return any data because the stream has ended. So done can be set in the final slice call where the final data chunk was returned:
{
  done: true,
  value: [some_data]
}

Or done can be set as the only property if you notice that no more data is available:
{
  done: true,
  value: null
}

Note that in this case, tus-js-client might have to send an empty PATCH request to indicate the end of the upload if you used uploadLengthDeferred.
I am not entirely sure if done is only used if uploadLengthDeferred is enabled, but I encourage every implementation to handle it properly because we cannot guarantee that this might not change in the future.
I will make sure to add all these points to the documentation soon.


http.Request method: RequestURI show different result on Mac & centos

http.Request method: RequestURI show different result on Mac & centos, Mac include host, but centos not

Does it happen with normal Go code as well?
I'm not sure I understand the problem, can you write a short program
demonstrating it?
On Thu, Nov 2, 2017 at 10:46 AM, AllinGoo<EMAIL_ADDRESS>wrote:

http.Request method: RequestURI show different result on Mac & centos, Mac
include host, but cents not
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/elazarl/goproxy/issues/255, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAP4ol_hZY9tAosz3705WNRoyeMjaA5sks5syYFNgaJpZM4QPVkl
.


rename default.properties to hadoop-unit-default.properties

to avoid file name conflict

fixed by #13


Docs: hidden-definitions/errors.txt can be gitignored

Motivation
Ignoring hidden-definitions/errors.txt makes git statistics more meaningful (increases signal-to-noise ratio).
Test plan
N/A

Can you commit the results of running tools/scripts/format_website.sh?

Can you commit the results of running tools/scripts/format_website.sh?

run


feat: Refactor: Improve performance and Confusing option zombieKeys v…

feat: Refactor: Improve performance and Confusing option zombieKeys versus zombies
Close #18
Close #109

[x] The commit message is formatted
[x] New functionality includes testing
[x] New functionality has been documented
[x] All user-facing changes accompanied by the correspondent documentation
[x] All tests pass
[x] PR include resolved issues
[x] PR include description

:tada: This PR is included in version 1.18.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fixed typo in documentation. Fixed broken URLs

Also unindented code, and made URL's HTTPS where possible.

Also, it appears that parser.version now returns a string instead of a function, which breaks the example:
parser:on("-v", parser.version)

Error:
lua: /usr/share/lua/5.4/optparse/init.lua:607: assertion failed!
stack traceback:
	[C]: in function 'assert'
	/usr/share/lua/5.4/optparse/init.lua:607: in method 'parse'
	./optparse_test.lua:34: in main chunk
	[C]: in ?

Thanks for the PR!  Approved and merged :)


Fix link for pendulum

Really nice collection of projects, great job!
This PR fix the link for the pendulum project which wasn't in PYTHON.md.

@statox Thank you!


some request and ideas

the files is great but in dark mode it takes more time than light mode. please make pin protected or windows hello protected folder lock. Can there is option for default screen as Home or as drives like in file explorer. it is very promising and beautiful app

Thanks for the feedback. Please check if the same issue may already be open and provide input on those. Otherwise, open separate issues for each new problem/feature request.


Cannot read property 'end' of undefined

I've been trying to animate some personal work but im stumbling with these errors.

Could it be a conflict with my scripts?

Can you post an example? Seems like the error is originating from animations.js.

Here you go

I was having this issue also - I think it is related to using css word-colors like "red" on ln27 of your example.

@ChristopherSant, I believe @jeffcato is right. Try using a hex code instead for colors (e.g., #FF0000).

I'm getting this same error when trying to use it with textDecoration: 'underline'.

I'm getting the samer error when using visibility: 'visible'

I get it when trying to scroll a container on click!
const container = document.getElementById("brands");
prev.addEventListener("click", e => {
  anime({
    targets: container,
    scrollLeft: 240,
    easing: "easeInOut",
    duration: 600
  });
});

But I know the above can be done, because of this CodePen I found.

 It was the easing. I just assumed easeInOut was a value, it's not.

Easing

This is very old, but I had the same issue with display:none. I solved using the begin and complete callbacks
This was the one that helps me - https://codepen.io/Shokeen/pen/XgKbKK?editors=0010
First I use the opacity, but the object is still there, so I can click the object under it. zIndex doesn't help either


Use the cli when creating with Helm

We should add docs on how to be able to interact with Airy Core with the CLI, after installing with Helm.

Done.


PaaS script should install Curl on Ubuntu

Closing, as Curl is needed to download the script itself :) .


paramiko-ssh-config-support

I don't expect this to be merged yet.  I was going to work with lakstorm on the unit tests.

Thank you for your PR.
+1, let's have @lakshmi-kannan take another look and we'll get it in.

Thank you for your PR.
+1, let's have @lakshmi-kannan take another look and we'll get it in.

You should also edit CHANGELOG.rst and call it as a new feature and put your name next to it :)
https://github.com/StackStorm/st2/blob/master/CHANGELOG.rst#in-development

Besides those comments, LGTM. Once you have them addressed, I'll merge.

Nice work, thanks.
It would also be great if you can add corresponding documentation to https://github.com/stackstorm/st2docs

Fixed here: https://github.com/StackStorm/st2/pull/3032

Thanks to both of you - let's continue in #3032 then.


Update images.rst

image.save() instead of image.update()

Thanks for the fix.  Please could you ensure that you commit with git commit -s for future PRs as (as a group defined lxc policy) all commits are supposed to be "signed off" -- see the DCO check above.
I'm merging this as it's a useful documentation fix.
Thanks!


⚠ Bofrost.es has degraded performance

In 7a1bdfa, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 2463 ms

Resolved: Bofrost.es performance has improved in 9a09adb after 19 minutes.


Creation plot

Hello @GaetanDu! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file autopycoin/baseclass.py:

Line 18:1: E302 expected 2 blank lines, found 1
Line 22:1: E302 expected 2 blank lines, found 1
Line 72:80: E501 line too long (81 > 79 characters)
Line 73:80: E501 line too long (83 > 79 characters)
Line 81:31: E261 at least two spaces before inline comment
Line 102:80: E501 line too long (90 > 79 characters)
Line 104:80: E501 line too long (81 > 79 characters)
Line 110:1: E302 expected 2 blank lines, found 1
Line 115:1: E302 expected 2 blank lines, found 1
Line 122:80: E501 line too long (109 > 79 characters)
Line 136:80: E501 line too long (80 > 79 characters)
Line 139:12: E713 test for membership should be 'not in'
Line 140:80: E501 line too long (117 > 79 characters)
Line 143:13: E122 continuation line missing indentation or outdented
Line 144:13: E122 continuation line missing indentation or outdented
Line 145:13: E122 continuation line missing indentation or outdented
Line 146:9: E122 continuation line missing indentation or outdented
Line 150:1: E302 expected 2 blank lines, found 1
Line 156:43: E713 test for membership should be 'not in'
Line 175:80: E501 line too long (83 > 79 characters)

In the file autopycoin/baseclass_field.py:

Line 15:5: E731 do not assign a lambda expression, use a def
Line 43:80: E501 line too long (80 > 79 characters)
Line 50:80: E501 line too long (83 > 79 characters)
Line 55:80: E501 line too long (80 > 79 characters)
Line 65:80: E501 line too long (80 > 79 characters)
Line 110:80: E501 line too long (101 > 79 characters)
Line 122:80: E501 line too long (88 > 79 characters)
Line 126:80: E501 line too long (87 > 79 characters)
Line 133:80: E501 line too long (95 > 79 characters)
Line 141:80: E501 line too long (80 > 79 characters)
Line 164:80: E501 line too long (89 > 79 characters)
Line 175:80: E501 line too long (95 > 79 characters)
Line 187:80: E501 line too long (80 > 79 characters)
Line 201:80: E501 line too long (88 > 79 characters)
Line 202:80: E501 line too long (91 > 79 characters)
Line 213:80: E501 line too long (83 > 79 characters)
Line 216:80: E501 line too long (103 > 79 characters)
Line 225:80: E501 line too long (90 > 79 characters)
Line 232:80: E501 line too long (85 > 79 characters)
Line 237:80: E501 line too long (83 > 79 characters)
Line 245:80: E501 line too long (81 > 79 characters)
Line 263:80: E501 line too long (85 > 79 characters)

In the file autopycoin/baseclass_field_test.py:

Line 39:80: E501 line too long (83 > 79 characters)
Line 100:80: E501 line too long (85 > 79 characters)
Line 105:80: E501 line too long (81 > 79 characters)
Line 140:80: E501 line too long (83 > 79 characters)
Line 141:80: E501 line too long (83 > 79 characters)
Line 142:80: E501 line too long (87 > 79 characters)

In the file autopycoin/baseclass_test.py:

Line 18:67: E252 missing whitespace around parameter equals
Line 18:68: E252 missing whitespace around parameter equals
Line 49:80: E501 line too long (104 > 79 characters)
Line 65:80: E501 line too long (80 > 79 characters)

In the file autopycoin/data/generate_test.py:

Line 69:9: E128 continuation line under-indented for visual indent
Line 70:9: E128 continuation line under-indented for visual indent
Line 71:9: E128 continuation line under-indented for visual indent
Line 72:9: E128 continuation line under-indented for visual indent
Line 74:13: E128 continuation line under-indented for visual indent
Line 75:13: E128 continuation line under-indented for visual indent
Line 76:13: E128 continuation line under-indented for visual indent
Line 77:13: E128 continuation line under-indented for visual indent
Line 78:13: E128 continuation line under-indented for visual indent
Line 79:13: E128 continuation line under-indented for visual indent
Line 80:13: E128 continuation line under-indented for visual indent
Line 81:13: E128 continuation line under-indented for visual indent
Line 82:13: E128 continuation line under-indented for visual indent
Line 83:13: E128 continuation line under-indented for visual indent
Line 84:13: E128 continuation line under-indented for visual indent
Line 101:80: E501 line too long (85 > 79 characters)
Line 107:9: E128 continuation line under-indented for visual indent
Line 108:9: E128 continuation line under-indented for visual indent
Line 109:9: E128 continuation line under-indented for visual indent
Line 110:9: E128 continuation line under-indented for visual indent
Line 112:13: E128 continuation line under-indented for visual indent
Line 113:13: E128 continuation line under-indented for visual indent
Line 114:13: E128 continuation line under-indented for visual indent
Line 115:13: E128 continuation line under-indented for visual indent
Line 116:13: E128 continuation line under-indented for visual indent
Line 117:13: E128 continuation line under-indented for visual indent
Line 118:13: E128 continuation line under-indented for visual indent
Line 119:13: E128 continuation line under-indented for visual indent
Line 120:13: E128 continuation line under-indented for visual indent
Line 121:13: E128 continuation line under-indented for visual indent
Line 122:13: E128 continuation line under-indented for visual indent
Line 145:13: E122 continuation line missing indentation or outdented

In the file autopycoin/dataset/generator.py:

Line 21:80: E501 line too long (84 > 79 characters)
Line 33:80: E501 line too long (84 > 79 characters)
Line 42:80: E501 line too long (94 > 79 characters)
Line 68:80: E501 line too long (114 > 79 characters)
Line 73:80: E501 line too long (123 > 79 characters)
Line 76:80: E501 line too long (123 > 79 characters)
Line 81:80: E501 line too long (84 > 79 characters)
Line 86:80: E501 line too long (127 > 79 characters)
Line 123:80: E501 line too long (325 > 79 characters)
Line 136:7: E261 at least two spaces before inline comment
Line 161:80: E501 line too long (83 > 79 characters)
Line 165:80: E501 line too long (83 > 79 characters)
Line 173:9: E125 continuation line with same indent as next logical line
Line 182:80: E501 line too long (88 > 79 characters)
Line 189:80: E501 line too long (108 > 79 characters)
Line 192:80: E501 line too long (81 > 79 characters)
Line 220:80: E501 line too long (92 > 79 characters)
Line 221:80: E501 line too long (92 > 79 characters)
Line 222:80: E501 line too long (92 > 79 characters)
Line 223:80: E501 line too long (90 > 79 characters)
Line 226:80: E501 line too long (90 > 79 characters)
Line 227:80: E501 line too long (112 > 79 characters)
Line 235:80: E501 line too long (85 > 79 characters)
Line 242:48: E231 missing whitespace after ':'
Line 251:9: E125 continuation line with same indent as next logical line
Line 259:80: E501 line too long (97 > 79 characters)
Line 260:80: E501 line too long (84 > 79 characters)
Line 267:80: E501 line too long (108 > 79 characters)
Line 270:80: E501 line too long (81 > 79 characters)
Line 290:17: E128 continuation line under-indented for visual indent
Line 296:34: E261 at least two spaces before inline comment
Line 315:80: E501 line too long (114 > 79 characters)
Line 324:30: E203 whitespace before ':'
Line 329:53: E203 whitespace before ':'
Line 334:34: E252 missing whitespace around parameter equals
Line 334:35: E252 missing whitespace around parameter equals
Line 366:80: E501 line too long (86 > 79 characters)
Line 387:80: E501 line too long (123 > 79 characters)
Line 390:80: E501 line too long (123 > 79 characters)
Line 401:80: E501 line too long (127 > 79 characters)
Line 404:80: E501 line too long (80 > 79 characters)
Line 416:80: E501 line too long (82 > 79 characters)
Line 474:80: E501 line too long (92 > 79 characters)
Line 474:88: E252 missing whitespace around parameter equals
Line 474:89: E252 missing whitespace around parameter equals
Line 483:80: E501 line too long (100 > 79 characters)
Line 487:80: E501 line too long (91 > 79 characters)
Line 495:80: E501 line too long (194 > 79 characters)
Line 496:1: W293 blank line contains whitespace
Line 497:80: E501 line too long (81 > 79 characters)
Line 499:1: W293 blank line contains whitespace
Line 500:80: E501 line too long (122 > 79 characters)
Line 503:80: E501 line too long (124 > 79 characters)
Line 506:80: E501 line too long (102 > 79 characters)
Line 507:80: E501 line too long (104 > 79 characters)
Line 508:80: E501 line too long (102 > 79 characters)
Line 509:13: E124 closing bracket does not match visual indentation
Line 509:80: E501 line too long (95 > 79 characters)
Line 510:80: E501 line too long (89 > 79 characters)
Line 525:53: E231 missing whitespace after ','
Line 534:80: E501 line too long (93 > 79 characters)
Line 546:80: E501 line too long (101 > 79 characters)
Line 593:73: W291 trailing whitespace
Line 611:80: E501 line too long (103 > 79 characters)
Line 671:31: E225 missing whitespace around operator
Line 689:80: E501 line too long (112 > 79 characters)
Line 702:80: E501 line too long (112 > 79 characters)
Line 715:80: E501 line too long (112 > 79 characters)
Line 728:80: E501 line too long (111 > 79 characters)
Line 730:80: E261 at least two spaces before inline comment
Line 730:80: E501 line too long (113 > 79 characters)
Line 734:80: E501 line too long (82 > 79 characters)
Line 737:80: E501 line too long (82 > 79 characters)
Line 743:80: E501 line too long (109 > 79 characters)
Line 752:80: E501 line too long (82 > 79 characters)
Line 756:80: E501 line too long (84 > 79 characters)
Line 758:80: E501 line too long (136 > 79 characters)
Line 758:103: E261 at least two spaces before inline comment
Line 759:80: E501 line too long (88 > 79 characters)
Line 769:80: E501 line too long (132 > 79 characters)
Line 771:80: E501 line too long (122 > 79 characters)
Line 772:80: E501 line too long (135 > 79 characters)
Line 773:80: E501 line too long (131 > 79 characters)
Line 775:80: E501 line too long (115 > 79 characters)
Line 775:82: E261 at least two spaces before inline comment
Line 778:80: E501 line too long (142 > 79 characters)
Line 779:80: E501 line too long (142 > 79 characters)
Line 781:80: E501 line too long (146 > 79 characters)
Line 783:80: E501 line too long (144 > 79 characters)
Line 784:1: W293 blank line contains whitespace
Line 790:80: E501 line too long (84 > 79 characters)
Line 838:1: W293 blank line contains whitespace
Line 839:80: E501 line too long (87 > 79 characters)

In the file autopycoin/dataset/generator_test.py:

Line 22:12: E225 missing whitespace around operator
Line 23:80: E501 line too long (109 > 79 characters)
Line 36:80: E501 line too long (85 > 79 characters)
Line 36:86: W291 trailing whitespace
Line 37:13: E128 continuation line under-indented for visual indent
Line 39:76: W291 trailing whitespace
Line 40:13: E128 continuation line under-indented for visual indent
Line 42:80: E501 line too long (100 > 79 characters)
Line 42:101: W291 trailing whitespace
Line 43:13: E128 continuation line under-indented for visual indent
Line 43:80: E501 line too long (85 > 79 characters)
Line 45:63: W291 trailing whitespace
Line 46:13: E128 continuation line under-indented for visual indent
Line 48:64: W291 trailing whitespace
Line 49:13: E128 continuation line under-indented for visual indent
Line 51:77: W291 trailing whitespace
Line 52:13: E128 continuation line under-indented for visual indent
Line 52:80: E501 line too long (86 > 79 characters)
Line 82:27: W291 trailing whitespace
Line 83:27: W291 trailing whitespace
Line 84:21: W291 trailing whitespace
Line 85:26: W291 trailing whitespace
Line 86:25: W291 trailing whitespace
Line 87:24: W291 trailing whitespace
Line 88:29: W291 trailing whitespace
Line 89:29: W291 trailing whitespace
Line 90:29: W291 trailing whitespace
Line 92:25: E231 missing whitespace after ','
Line 105:80: E501 line too long (139 > 79 characters)
Line 107:80: E501 line too long (135 > 79 characters)
Line 119:80: E501 line too long (139 > 79 characters)
Line 121:80: E501 line too long (135 > 79 characters)
Line 124:5: E303 too many blank lines (2)
Line 126:14: E201 whitespace after '('
Line 126:80: E501 line too long (161 > 79 characters)
Line 127:14: E201 whitespace after '('
Line 127:80: E501 line too long (161 > 79 characters)
Line 128:14: E201 whitespace after '('
Line 128:80: E501 line too long (155 > 79 characters)
Line 129:14: E201 whitespace after '('
Line 129:80: E501 line too long (159 > 79 characters)
Line 130:14: E201 whitespace after '('
Line 130:80: E501 line too long (158 > 79 characters)
Line 131:14: E201 whitespace after '('
Line 131:80: E501 line too long (126 > 79 characters)
Line 132:14: E201 whitespace after '('
Line 132:80: E501 line too long (160 > 79 characters)
Line 133:14: E201 whitespace after '('
Line 133:80: E501 line too long (140 > 79 characters)
Line 134:14: E201 whitespace after '('
Line 134:80: E501 line too long (137 > 79 characters)
Line 135:14: E201 whitespace after '('
Line 135:80: E501 line too long (137 > 79 characters)
Line 136:14: E201 whitespace after '('
Line 136:80: E501 line too long (138 > 79 characters)
Line 137:14: E201 whitespace after '('
Line 137:80: E501 line too long (119 > 79 characters)
Line 138:14: E201 whitespace after '('
Line 138:80: E501 line too long (119 > 79 characters)
Line 139:14: E201 whitespace after '('
Line 139:80: E501 line too long (152 > 79 characters)
Line 140:14: E201 whitespace after '('
Line 140:80: E501 line too long (153 > 79 characters)
Line 141:80: E501 line too long (151 > 79 characters)
Line 142:80: E501 line too long (174 > 79 characters)
Line 143:80: E501 line too long (174 > 79 characters)
Line 183:14: E201 whitespace after '('
Line 183:80: E501 line too long (189 > 79 characters)
Line 183:101: E231 missing whitespace after ','
Line 183:114: E231 missing whitespace after ','
Line 183:126: E231 missing whitespace after ','
Line 183:134: E231 missing whitespace after ','
Line 183:142: E231 missing whitespace after ','
Line 183:149: E231 missing whitespace after ','
Line 183:181: E231 missing whitespace after ','
Line 184:14: E201 whitespace after '('
Line 184:80: E501 line too long (144 > 79 characters)
Line 184:96: E231 missing whitespace after ','
Line 184:104: E231 missing whitespace after ','
Line 184:136: E231 missing whitespace after ','
Line 185:14: E201 whitespace after '('
Line 185:80: E501 line too long (144 > 79 characters)
Line 185:96: E231 missing whitespace after ','
Line 185:104: E231 missing whitespace after ','
Line 185:136: E231 missing whitespace after ','
Line 186:14: E201 whitespace after '('
Line 186:80: E501 line too long (144 > 79 characters)
Line 186:96: E231 missing whitespace after ','
Line 186:104: E231 missing whitespace after ','
Line 186:136: E231 missing whitespace after ','
Line 187:14: E201 whitespace after '('
Line 187:80: E501 line too long (138 > 79 characters)
Line 187:90: E231 missing whitespace after ','
Line 187:98: E231 missing whitespace after ','
Line 187:130: E231 missing whitespace after ','
Line 188:14: E201 whitespace after '('
Line 188:80: E501 line too long (157 > 79 characters)
Line 188:97: E231 missing whitespace after ','
Line 188:105: E231 missing whitespace after ','
Line 188:146: E231 missing whitespace after ','
Line 189:14: E201 whitespace after '('
Line 189:80: E501 line too long (149 > 79 characters)
Line 189:100: E231 missing whitespace after ','
Line 189:108: E231 missing whitespace after ','
Line 190:14: E201 whitespace after '('
Line 190:80: E501 line too long (166 > 79 characters)
Line 190:106: E231 missing whitespace after ','
Line 190:114: E231 missing whitespace after ','
Line 190:155: E231 missing whitespace after ','
Line 220:1: W293 blank line contains whitespace
Line 243:80: E501 line too long (104 > 79 characters)
Line 245:80: E501 line too long (124 > 79 characters)
Line 247:80: E501 line too long (126 > 79 characters)
Line 252:80: E501 line too long (83 > 79 characters)
Line 254:80: E501 line too long (127 > 79 characters)
Line 278:75: W291 trailing whitespace
Line 279:45: E128 continuation line under-indented for visual indent
Line 279:80: E501 line too long (128 > 79 characters)
Line 280:80: E501 line too long (117 > 79 characters)
Line 284:80: E501 line too long (97 > 79 characters)
Line 290:1: W293 blank line contains whitespace
Line 292:5: E303 too many blank lines (2)
Line 294:80: E501 line too long (118 > 79 characters)
Line 295:80: E501 line too long (125 > 79 characters)
Line 296:80: E501 line too long (137 > 79 characters)
Line 297:80: E501 line too long (144 > 79 characters)
Line 300:21: E128 continuation line under-indented for visual indent
Line 301:21: E128 continuation line under-indented for visual indent
Line 302:21: E128 continuation line under-indented for visual indent
Line 303:21: E128 continuation line under-indented for visual indent
Line 304:21: E128 continuation line under-indented for visual indent
Line 305:21: E128 continuation line under-indented for visual indent
Line 306:21: E128 continuation line under-indented for visual indent
Line 307:21: E128 continuation line under-indented for visual indent
Line 308:21: E128 continuation line under-indented for visual indent
Line 309:21: E128 continuation line under-indented for visual indent
Line 310:21: E128 continuation line under-indented for visual indent
Line 311:21: E128 continuation line under-indented for visual indent
Line 312:21: E128 continuation line under-indented for visual indent
Line 313:21: E128 continuation line under-indented for visual indent
Line 314:21: E128 continuation line under-indented for visual indent
Line 325:1: W293 blank line contains whitespace
Line 338:80: E501 line too long (122 > 79 characters)
Line 339:80: E501 line too long (95 > 79 characters)
Line 358:1: W293 blank line contains whitespace
Line 361:80: E501 line too long (176 > 79 characters)
Line 362:80: E501 line too long (202 > 79 characters)
Line 389:1: W293 blank line contains whitespace
Line 404:80: E501 line too long (86 > 79 characters)
Line 407:23: E128 continuation line under-indented for visual indent
Line 408:21: E128 continuation line under-indented for visual indent
Line 409:21: E128 continuation line under-indented for visual indent
Line 410:21: E128 continuation line under-indented for visual indent
Line 411:21: E128 continuation line under-indented for visual indent
Line 412:21: E128 continuation line under-indented for visual indent
Line 413:21: E128 continuation line under-indented for visual indent
Line 414:21: E128 continuation line under-indented for visual indent
Line 415:21: E128 continuation line under-indented for visual indent
Line 416:21: E128 continuation line under-indented for visual indent
Line 417:21: E128 continuation line under-indented for visual indent
Line 418:21: E124 closing bracket does not match visual indentation
Line 442:1: W293 blank line contains whitespace

In the file autopycoin/display/plot.py:

Line 18:1: E303 too many blank lines (3)
Line 26:80: E501 line too long (84 > 79 characters)
Line 27:80: E501 line too long (90 > 79 characters)
Line 36:80: E501 line too long (91 > 79 characters)
Line 54:80: E501 line too long (82 > 79 characters)
Line 64:1: W293 blank line contains whitespace
Line 65:80: E501 line too long (82 > 79 characters)
Line 71:26: E252 missing whitespace around parameter equals
Line 71:27: E252 missing whitespace around parameter equals
Line 72:31: E252 missing whitespace around parameter equals
Line 72:32: E252 missing whitespace around parameter equals
Line 73:28: E252 missing whitespace around parameter equals
Line 73:29: E252 missing whitespace around parameter equals
Line 74:26: E252 missing whitespace around parameter equals
Line 74:27: E252 missing whitespace around parameter equals
Line 78:80: E501 line too long (87 > 79 characters)
Line 121:80: E501 line too long (117 > 79 characters)
Line 152:80: E501 line too long (107 > 79 characters)
Line 154:80: E501 line too long (90 > 79 characters)
Line 158:80: E501 line too long (119 > 79 characters)
Line 160:80: E501 line too long (97 > 79 characters)
Line 161:80: E501 line too long (91 > 79 characters)
Line 163:80: E501 line too long (96 > 79 characters)
Line 168:80: E501 line too long (100 > 79 characters)
Line 179:80: E501 line too long (86 > 79 characters)
Line 199:80: E501 line too long (84 > 79 characters)
Line 219:25: W292 no newline at end of file

In the file autopycoin/display/table.py:

Line 29:80: E501 line too long (84 > 79 characters)
Line 30:80: E501 line too long (84 > 79 characters)
Line 73:80: E501 line too long (81 > 79 characters)
Line 75:80: E501 line too long (113 > 79 characters)

In the file autopycoin/losses/losses.py:

Line 20:1: E302 expected 2 blank lines, found 1
Line 20:73: E252 missing whitespace around parameter equals
Line 20:74: E252 missing whitespace around parameter equals
Line 20:80: E501 line too long (80 > 79 characters)
Line 74:80: E501 line too long (97 > 79 characters)
Line 85:80: E501 line too long (95 > 79 characters)
Line 110:80: E501 line too long (88 > 79 characters)
Line 130:80: E501 line too long (84 > 79 characters)
Line 266:80: E501 line too long (83 > 79 characters)
Line 271:80: E501 line too long (83 > 79 characters)

In the file autopycoin/models/base_layer.py:

Line 10:80: E501 line too long (91 > 79 characters)
Line 12:80: E501 line too long (93 > 79 characters)
Line 26:80: E501 line too long (86 > 79 characters)

In the file autopycoin/models/base_layer_test.py:

Line 46:52: W292 no newline at end of file

In the file autopycoin/models/nbeats.py:

Line 8:1: E265 block comment should start with '# '
Line 13:80: E501 line too long (80 > 79 characters)
Line 83:80: E501 line too long (89 > 79 characters)
Line 113:1: W293 blank line contains whitespace
Line 235:80: E501 line too long (80 > 79 characters)
Line 242:80: E501 line too long (88 > 79 characters)
Line 265:80: E501 line too long (91 > 79 characters)
Line 272:80: E501 line too long (85 > 79 characters)
Line 278:80: E501 line too long (82 > 79 characters)
Line 323:80: E501 line too long (101 > 79 characters)
Line 360:18: E252 missing whitespace around parameter equals
Line 360:19: E252 missing whitespace around parameter equals
Line 361:25: E252 missing whitespace around parameter equals
Line 361:26: E252 missing whitespace around parameter equals
Line 362:31: E252 missing whitespace around parameter equals
Line 362:32: E252 missing whitespace around parameter equals
Line 363:21: E252 missing whitespace around parameter equals
Line 363:22: E252 missing whitespace around parameter equals
Line 364:16: E252 missing whitespace around parameter equals
Line 364:17: E252 missing whitespace around parameter equals
Line 366:5: E125 continuation line with same indent as next logical line
Line 368:80: E501 line too long (80 > 79 characters)
Line 369:80: E501 line too long (91 > 79 characters)
Line 379:80: E501 line too long (87 > 79 characters)
Line 479:80: E501 line too long (93 > 79 characters)
Line 492:21: E252 missing whitespace around parameter equals
Line 492:22: E252 missing whitespace around parameter equals
Line 493:16: E252 missing whitespace around parameter equals
Line 493:17: E252 missing whitespace around parameter equals
Line 495:5: E125 continuation line with same indent as next logical line
Line 506:80: E501 line too long (87 > 79 characters)

In the file autopycoin/models/nbeats_blocks.py:

Line 7:1: E265 block comment should start with '# '
Line 25:80: E501 line too long (86 > 79 characters)
Line 35:80: E501 line too long (80 > 79 characters)
Line 64:26: E252 missing whitespace around parameter equals
Line 64:27: E252 missing whitespace around parameter equals
Line 65:28: E252 missing whitespace around parameter equals
Line 65:29: E252 missing whitespace around parameter equals
Line 66:24: E252 missing whitespace around parameter equals
Line 66:25: E252 missing whitespace around parameter equals
Line 130:80: E501 line too long (82 > 79 characters)
Line 148:9: E125 continuation line with same indent as next logical line
Line 170:80: E501 line too long (89 > 79 characters)
Line 178:80: E501 line too long (85 > 79 characters)
Line 186:80: E501 line too long (86 > 79 characters)
Line 228:80: E501 line too long (81 > 79 characters)
Line 252:1: W293 blank line contains whitespace
Line 275:1: W293 blank line contains whitespace
Line 287:80: E261 at least two spaces before inline comment
Line 287:80: E501 line too long (113 > 79 characters)
Line 290:80: E501 line too long (91 > 79 characters)
Line 291:80: E501 line too long (93 > 79 characters)
Line 307:13: E122 continuation line missing indentation or outdented
Line 310:80: E501 line too long (136 > 79 characters)
Line 310:103: E261 at least two spaces before inline comment
Line 311:80: E501 line too long (95 > 79 characters)
Line 312:80: E501 line too long (88 > 79 characters)
Line 315:13: E128 continuation line under-indented for visual indent
Line 317:80: E501 line too long (136 > 79 characters)
Line 317:103: E261 at least two spaces before inline comment
Line 318:80: E501 line too long (95 > 79 characters)
Line 319:80: E501 line too long (88 > 79 characters)
Line 322:13: E128 continuation line under-indented for visual indent
Line 334:80: E501 line too long (86 > 79 characters)
Line 342:80: E501 line too long (86 > 79 characters)
Line 348:80: E501 line too long (80 > 79 characters)
Line 366:80: E501 line too long (81 > 79 characters)
Line 388:80: E501 line too long (80 > 79 characters)
Line 390:80: E501 line too long (87 > 79 characters)
Line 396:80: E501 line too long (81 > 79 characters)
Line 398:80: E501 line too long (89 > 79 characters)
Line 399:80: E501 line too long (92 > 79 characters)
Line 403:80: E501 line too long (85 > 79 characters)
Line 406:80: E501 line too long (92 > 79 characters)
Line 409:80: E501 line too long (115 > 79 characters)
Line 443:80: E501 line too long (88 > 79 characters)
Line 469:1: W293 blank line contains whitespace
Line 477:80: E501 line too long (82 > 79 characters)
Line 498:80: E501 line too long (82 > 79 characters)
Line 522:80: E261 at least two spaces before inline comment
Line 522:80: E501 line too long (113 > 79 characters)
Line 555:80: E501 line too long (86 > 79 characters)
Line 557:80: E501 line too long (91 > 79 characters)
Line 561:80: E501 line too long (80 > 79 characters)
Line 578:80: E501 line too long (88 > 79 characters)
Line 579:80: E501 line too long (93 > 79 characters)
Line 584:80: E501 line too long (81 > 79 characters)
Line 604:80: E501 line too long (80 > 79 characters)
Line 606:80: E501 line too long (87 > 79 characters)
Line 612:80: E501 line too long (81 > 79 characters)
Line 614:80: E501 line too long (89 > 79 characters)
Line 615:80: E501 line too long (92 > 79 characters)
Line 619:80: E501 line too long (85 > 79 characters)
Line 622:80: E501 line too long (92 > 79 characters)
Line 625:80: E501 line too long (115 > 79 characters)
Line 685:80: E501 line too long (91 > 79 characters)
Line 686:9: E125 continuation line with same indent as next logical line
Line 688:80: E501 line too long (82 > 79 characters)
Line 698:80: E501 line too long (82 > 79 characters)
Line 714:80: E501 line too long (87 > 79 characters)
Line 783:80: E261 at least two spaces before inline comment
Line 783:80: E501 line too long (113 > 79 characters)
Line 784:27: E225 missing whitespace around operator
Line 784:80: E501 line too long (95 > 79 characters)
Line 786:13: E122 continuation line missing indentation or outdented
Line 786:80: E501 line too long (108 > 79 characters)
Line 794:80: E501 line too long (91 > 79 characters)
Line 797:32: E225 missing whitespace around operator
Line 797:80: E501 line too long (120 > 79 characters)
Line 799:13: E122 continuation line missing indentation or outdented
Line 799:80: E501 line too long (120 > 79 characters)
Line 807:80: E501 line too long (96 > 79 characters)
Line 812:1: E303 too many blank lines (3)
Line 833:80: E501 line too long (80 > 79 characters)
Line 862:80: E501 line too long (81 > 79 characters)
Line 864:80: E501 line too long (89 > 79 characters)
Line 865:80: E501 line too long (92 > 79 characters)
Line 869:80: E501 line too long (85 > 79 characters)
Line 872:80: E501 line too long (92 > 79 characters)
Line 875:80: E501 line too long (115 > 79 characters)
Line 988:80: E261 at least two spaces before inline comment
Line 988:80: E501 line too long (113 > 79 characters)
Line 989:80: E501 line too long (88 > 79 characters)
Line 990:80: E501 line too long (104 > 79 characters)
Line 991:80: E501 line too long (131 > 79 characters)

In the file autopycoin/models/nbeats_blocks_test.py:

Line 13:80: E501 line too long (82 > 79 characters)
Line 19:17: E117 over-indented
Line 20:29: E128 continuation line under-indented for visual indent
Line 21:29: E128 continuation line under-indented for visual indent
Line 22:29: E128 continuation line under-indented for visual indent
Line 23:29: E128 continuation line under-indented for visual indent
Line 24:29: E128 continuation line under-indented for visual indent
Line 25:29: E128 continuation line under-indented for visual indent
Line 26:29: E128 continuation line under-indented for visual indent
Line 26:46: E252 missing whitespace around parameter equals
Line 26:47: E252 missing whitespace around parameter equals
Line 27:29: E128 continuation line under-indented for visual indent
Line 27:48: E252 missing whitespace around parameter equals
Line 27:49: E252 missing whitespace around parameter equals
Line 28:29: E128 continuation line under-indented for visual indent
Line 28:44: E252 missing whitespace around parameter equals
Line 28:45: E252 missing whitespace around parameter equals
Line 32:80: E501 line too long (80 > 79 characters)
Line 33:80: E501 line too long (80 > 79 characters)
Line 45:17: E301 expected 1 blank line, found 0
Line 56:10: E261 at least two spaces before inline comment
Line 57:80: E501 line too long (144 > 79 characters)
Line 58:10: E128 continuation line under-indented for visual indent
Line 60:80: E501 line too long (148 > 79 characters)
Line 61:10: E128 continuation line under-indented for visual indent
Line 63:71: W291 trailing whitespace
Line 64:10: E128 continuation line under-indented for visual indent
Line 64:80: E501 line too long (184 > 79 characters)
Line 65:10: E128 continuation line under-indented for visual indent
Line 65:80: E501 line too long (81 > 79 characters)
Line 67:80: E501 line too long (147 > 79 characters)
Line 68:10: E128 continuation line under-indented for visual indent
Line 68:53: E231 missing whitespace after ','
Line 71:9: E128 continuation line under-indented for visual indent
Line 72:9: E128 continuation line under-indented for visual indent
Line 73:9: E128 continuation line under-indented for visual indent
Line 74:9: E125 continuation line with same indent as next logical line
Line 74:9: E128 continuation line under-indented for visual indent
Line 85:80: E501 line too long (114 > 79 characters)
Line 86:80: E501 line too long (114 > 79 characters)
Line 87:80: E501 line too long (126 > 79 characters)
Line 88:80: E501 line too long (126 > 79 characters)
Line 89:80: E501 line too long (94 > 79 characters)
Line 90:80: E501 line too long (94 > 79 characters)
Line 91:80: E501 line too long (103 > 79 characters)
Line 92:80: E501 line too long (89 > 79 characters)
Line 93:80: E501 line too long (100 > 79 characters)
Line 94:80: E501 line too long (130 > 79 characters)
Line 95:80: E501 line too long (135 > 79 characters)
Line 96:80: E501 line too long (165 > 79 characters)
Line 97:80: E501 line too long (115 > 79 characters)
Line 98:80: E501 line too long (168 > 79 characters)
Line 99:80: E501 line too long (118 > 79 characters)
Line 103:9: E128 continuation line under-indented for visual indent
Line 104:9: E128 continuation line under-indented for visual indent
Line 105:9: E125 continuation line with same indent as next logical line
Line 105:9: E128 continuation line under-indented for visual indent
Line 112:1: W293 blank line contains whitespace
Line 124:30: W291 trailing whitespace
Line 125:5: E128 continuation line under-indented for visual indent
Line 175:80: E501 line too long (87 > 79 characters)
Line 193:9: E125 continuation line with same indent as next logical line
Line 199:9: E122 continuation line missing indentation or outdented
Line 200:9: E122 continuation line missing indentation or outdented
Line 201:9: E122 continuation line missing indentation or outdented
Line 202:9: E122 continuation line missing indentation or outdented
Line 203:9: E122 continuation line missing indentation or outdented
Line 204:9: E122 continuation line missing indentation or outdented
Line 205:9: E122 continuation line missing indentation or outdented
Line 206:9: E122 continuation line missing indentation or outdented
Line 207:9: E122 continuation line missing indentation or outdented
Line 208:9: E122 continuation line missing indentation or outdented
Line 209:9: E122 continuation line missing indentation or outdented
Line 210:9: E122 continuation line missing indentation or outdented
Line 213:80: E501 line too long (86 > 79 characters)
Line 214:80: E501 line too long (86 > 79 characters)
Line 216:80: E501 line too long (86 > 79 characters)
Line 217:80: E501 line too long (86 > 79 characters)
Line 220:5: E122 continuation line missing indentation or outdented
Line 222:9: E122 continuation line missing indentation or outdented
Line 223:9: E122 continuation line missing indentation or outdented
Line 230:5: E122 continuation line missing indentation or outdented
Line 233:9: E122 continuation line missing indentation or outdented
Line 234:9: E122 continuation line missing indentation or outdented
Line 241:5: E122 continuation line missing indentation or outdented
Line 282:80: E501 line too long (88 > 79 characters)
Line 386:9: E125 continuation line with same indent as next logical line
Line 404:10: W292 no newline at end of file

In the file autopycoin/models/nbeats_test.py:

Line 25:1: E302 expected 2 blank lines, found 1
Line 26:2: E111 indentation is not a multiple of four
Line 41:1: E302 expected 2 blank lines, found 1
Line 41:80: E501 line too long (84 > 79 characters)
Line 43:36: E231 missing whitespace after ','
Line 45:34: E231 missing whitespace after ','
Line 47:34: E231 missing whitespace after ','
Line 49:34: E231 missing whitespace after ','
Line 51:33: E231 missing whitespace after ','
Line 52:33: E231 missing whitespace after ','
Line 66:1: E305 expected 2 blank lines after class or function definition, found 1
Line 94:10: E261 at least two spaces before inline comment
Line 97:10: E128 continuation line under-indented for visual indent
Line 97:80: E501 line too long (96 > 79 characters)
Line 99:80: E501 line too long (80 > 79 characters)
Line 101:10: E128 continuation line under-indented for visual indent
Line 101:80: E501 line too long (103 > 79 characters)
Line 103:80: E501 line too long (84 > 79 characters)
Line 105:10: E128 continuation line under-indented for visual indent
Line 105:80: E501 line too long (113 > 79 characters)
Line 106:80: E501 line too long (89 > 79 characters)
Line 108:10: E128 continuation line under-indented for visual indent
Line 108:80: E501 line too long (105 > 79 characters)
Line 112:9: E128 continuation line under-indented for visual indent
Line 113:9: E128 continuation line under-indented for visual indent
Line 114:9: E128 continuation line under-indented for visual indent
Line 115:9: E125 continuation line with same indent as next logical line
Line 115:9: E128 continuation line under-indented for visual indent
Line 123:9: E122 continuation line missing indentation or outdented
Line 136:9: E128 continuation line under-indented for visual indent
Line 137:9: E128 continuation line under-indented for visual indent
Line 138:9: E128 continuation line under-indented for visual indent
Line 139:9: E128 continuation line under-indented for visual indent
Line 140:9: E128 continuation line under-indented for visual indent
Line 141:9: E128 continuation line under-indented for visual indent
Line 142:9: E128 continuation line under-indented for visual indent
Line 143:9: E128 continuation line under-indented for visual indent
Line 144:9: E125 continuation line with same indent as next logical line
Line 144:9: E128 continuation line under-indented for visual indent
Line 165:1: W293 blank line contains whitespace
Line 207:9: E122 continuation line missing indentation or outdented
Line 220:9: E128 continuation line under-indented for visual indent
Line 221:9: E128 continuation line under-indented for visual indent
Line 222:9: E128 continuation line under-indented for visual indent
Line 223:9: E128 continuation line under-indented for visual indent
Line 224:9: E128 continuation line under-indented for visual indent
Line 225:9: E128 continuation line under-indented for visual indent
Line 226:9: E128 continuation line under-indented for visual indent
Line 227:9: E128 continuation line under-indented for visual indent
Line 228:9: E125 continuation line with same indent as next logical line
Line 228:9: E128 continuation line under-indented for visual indent
Line 249:1: W293 blank line contains whitespace
Line 262:80: E501 line too long (80 > 79 characters)
Line 263:80: E501 line too long (80 > 79 characters)
Line 278:9: E122 continuation line missing indentation or outdented
Line 291:9: E128 continuation line under-indented for visual indent
Line 292:9: E128 continuation line under-indented for visual indent
Line 293:9: E128 continuation line under-indented for visual indent
Line 294:9: E128 continuation line under-indented for visual indent
Line 295:9: E128 continuation line under-indented for visual indent
Line 296:9: E128 continuation line under-indented for visual indent
Line 297:9: E128 continuation line under-indented for visual indent
Line 298:9: E128 continuation line under-indented for visual indent
Line 299:9: E125 continuation line with same indent as next logical line
Line 299:9: E128 continuation line under-indented for visual indent
Line 320:1: W293 blank line contains whitespace
Line 334:80: E501 line too long (86 > 79 characters)
Line 371:9: E122 continuation line missing indentation or outdented
Line 449:9: E122 continuation line missing indentation or outdented
Line 471:9: E125 continuation line with same indent as next logical line

In the file autopycoin/models/training.py:

Line 19:80: E501 line too long (91 > 79 characters)
Line 21:80: E501 line too long (92 > 79 characters)
Line 37:51: E261 at least two spaces before inline comment
Line 37:80: E501 line too long (85 > 79 characters)
Line 50:9: E125 continuation line with same indent as next logical line
Line 51:80: E501 line too long (98 > 79 characters)
Line 69:15: E128 continuation line under-indented for visual indent
Line 70:15: E128 continuation line under-indented for visual indent
Line 71:15: E128 continuation line under-indented for visual indent
Line 72:15: E128 continuation line under-indented for visual indent
Line 73:15: E128 continuation line under-indented for visual indent
Line 74:15: E128 continuation line under-indented for visual indent
Line 75:15: E128 continuation line under-indented for visual indent
Line 76:15: E128 continuation line under-indented for visual indent
Line 78:80: E501 line too long (82 > 79 characters)
Line 93:80: E501 line too long (80 > 79 characters)
Line 100:80: E501 line too long (80 > 79 characters)
Line 111:80: E501 line too long (81 > 79 characters)
Line 114:80: E501 line too long (80 > 79 characters)
Line 120:80: E501 line too long (80 > 79 characters)
Line 123:80: E501 line too long (83 > 79 characters)
Line 125:80: E501 line too long (82 > 79 characters)
Line 142:80: E501 line too long (83 > 79 characters)
Line 146:80: E501 line too long (101 > 79 characters)
Line 158:80: E501 line too long (80 > 79 characters)
Line 161:17: E129 visually indented line with same indent as next logical line
Line 165:80: E501 line too long (83 > 79 characters)
Line 169:33: E128 continuation line under-indented for visual indent
Line 169:80: E501 line too long (85 > 79 characters)
Line 170:33: E128 continuation line under-indented for visual indent
Line 170:80: E501 line too long (88 > 79 characters)
Line 171:33: E128 continuation line under-indented for visual indent
Line 171:80: E501 line too long (81 > 79 characters)
Line 200:80: E501 line too long (80 > 79 characters)
Line 207:80: E501 line too long (90 > 79 characters)
Line 209:80: E501 line too long (96 > 79 characters)
Line 210:53: E128 continuation line under-indented for visual indent
Line 214:80: E501 line too long (89 > 79 characters)
Line 217:80: E501 line too long (92 > 79 characters)
Line 219:80: E501 line too long (80 > 79 characters)
Line 224:80: E501 line too long (106 > 79 characters)
Line 226:80: E501 line too long (106 > 79 characters)
Line 228:80: E501 line too long (81 > 79 characters)
Line 241:1: E302 expected 2 blank lines, found 1
Line 250:1: E302 expected 2 blank lines, found 1
Line 254:80: E501 line too long (81 > 79 characters)
Line 255:80: E501 line too long (83 > 79 characters)
Line 256:80: E501 line too long (80 > 79 characters)

In the file autopycoin/models/training_test.py:

Line 115:53: W292 no newline at end of file

In the file autopycoin/uncertainty/mcdropout.py:

Line 45:80: E501 line too long (84 > 79 characters)
Line 140:80: E501 line too long (85 > 79 characters)
Line 146:80: E501 line too long (85 > 79 characters)
Line 149:80: E501 line too long (93 > 79 characters)
Line 150:80: E501 line too long (93 > 79 characters)
Line 151:80: E501 line too long (93 > 79 characters)
Line 167:80: E501 line too long (80 > 79 characters)
Line 191:80: E501 line too long (82 > 79 characters)
Line 193:80: E501 line too long (91 > 79 characters)

In the file autopycoin/utils/__init__.py:

Line 4:80: E501 line too long (86 > 79 characters)

In the file autopycoin/utils/data_utils.py:

Line 36:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (87 > 79 characters)
Line 99:80: E501 line too long (93 > 79 characters)
Line 100:80: E501 line too long (90 > 79 characters)
Line 111:80: E501 line too long (116 > 79 characters)
Line 141:80: E501 line too long (90 > 79 characters)

In the file autopycoin/utils/data_utils_test.py:

Line 76:1: E302 expected 2 blank lines, found 1
Line 153:80: E501 line too long (83 > 79 characters)
Line 159:80: E501 line too long (83 > 79 characters)
Line 165:80: E501 line too long (83 > 79 characters)
Line 171:80: E501 line too long (83 > 79 characters)

In the file autopycoin/utils/testing_utils.py:

Line 176:9: E128 continuation line under-indented for visual indent
Line 234:1: W293 blank line contains whitespace
Line 235:34: W291 trailing whitespace
Line 236:80: E501 line too long (97 > 79 characters)
Line 347:1: E302 expected 2 blank lines, found 1
Line 349:13: E117 over-indented
Line 351:80: E501 line too long (139 > 79 characters)
Line 356:145: W292 no newline at end of file


SolutionContainerVisualizer doesn't set color on spawn

Description

Spawn the "solution container vis cut-out"
Drink from it

This contains watermelon reagent, but it spawns white and it's icon does not have the color applied in the spawn menu. Only when you take a sip does it update.
Screenshots

https://user-images.githubusercontent.com/49448379/115653934-a277b580-a31f-11eb-864c-2b0f023f552f.mp4
Additional context

@Macoron

SolutionContainerVisualState Is not present in the initialization of AppearanceComponent for this prototype it seems.


Question of the zero-shot

Thanks for the great job! In this study, both the 2D backbone lseg and openseg necessitate text labels for input. This approach appears more akin to weakly supervised learning (as described in https://openreview.net/pdf?id=4Q9CmC3ypdE) that leverages scene text labels, rather than true zero-shot learning. Therefore, wouldn't it be more appropriate to benchmark against weakly supervised learning baselines as opposed to zero-shot learning baselines?

@Zhimin-C thanks for your interest in our work! Actually there was also a CVPR reviewer asking a roughly same question, so I will reply to you by copying a paragraph of our answer :)

The terminology for zero-shot learning (ZSL) is ambiguous. In a theoretical ZSL system, there should
be no training data of any kind from seen classes. However, almost all real-world ZSL systems utilize general purpose feature extractors pretrained for proxy tasks on large datasets. For example, 3DGenZ proposes a ZSL variant utilizing image features pretrained on ImageNet (see
section 4.5 in their paper), and OpenSeg, LSeg, CLIP, and
ALIGN proposed ZSL methods trained on alt-text (as we
do). The authors of those papers all describe their methods as ZSL. We followed the same terminology.

So long story short, if you check the original CLIP paper and many of follow-ups, they refer their method as zero-shot. We follow them :)


Can VectorTileSource Reprojection?

raster source can reprojection between the View and source have different projection.
If VectorTileSource  and View have different projection it's not seeming to work.
(source/TileImage.js has ReprojTile, source/VectorTile.js isn't)
Can somebody tell me  is there any way to fix the program.
thanks.
eg:
VectorTileSource is set to EPSG:3857, and the map view projection is set to EPSG:4326.

Fixes #6059.
(vector tiles only 'work' for the projection they were made for)


Pass tintColor to tabBar label

Currently, tab bar icons receive the tintColor prop, but not labels. This is problematic when you use a custom component for the label. Active and non-active labels will be the same color:
e.g.,
function Label({name}) {
  return <Text style={{textAlign: 'center', fontSize: 10}}>{name}</Text>;
}

const TabNavigatorImpl = TabNavigator({
  Home: {
    screen: Home,
    navigationOptions: {
      tabBar: {
        label: props => (<Label name='Home' {...props}/>),
        icon: props => (<IconWrapper name='home' {...props} />)
      }
    }
  },
  Submit: {
    screen: Submit,
    navigationOptions: {
      tabBar: {
        label: props => (<Label name='Submit' {...props}/>),
        icon: props => (<IconWrapper name='create' {...props} />)
      }
    }
  },
  ...
});

Renders a tab bar that looks like this:

tintColor does seem to be respected, however, when passing in a string as the label.

Please send a PR fixing the issue.

I realized that active is getting passed in; that's sufficient for styling.
function Label({name, focused}) {
  return <Text style={{textAlign: 'center', fontSize: 10, color: focused ? '#f00' : '#000'}}>{name}</Text>;
}

Label.propTypes = {
  focused: React.PropTypes.bool.isRequired,
  name: React.PropTypes.string.isRequired
};

Active get's passed to icon too. tintColor should be passed to label if you don't want to manually set color again.

Good solution Pete, I literally just ran across this problem 👍

This is now supported.


Documentation outdated for printline()

Commit 4251e7957e22f4596c95cfd1adadcd92e79ac4b8 seems to have added the strline() function for getting string representations as a replacement for printline(file=None).
Documentation for SE3 still suggests printline() will output a string when supplied with file=None:

Documentation for the new strline() function also doesn't seem to have been built.

I've changed this stuff a lot, used to be all done by printline.  Are these the right primitives?

I haven't noticed a strong convention in the Python community for "making print flexible enough to meet user needs". There's the extendable custom string formatting, but that looks like it may be a deep rabbit hole.
If it was me, my approach would be maximise flexibility for users by minimising work done here:

Have a single function that provides all possible "thing to string" conversion functionality
Make something like NumPy's set_printoptions() to support changing the default string representation globally / in contexts using with (optional)
Drop all support for sending the strings to files, and let users handle that through more generic Python methods available

With the flexibility of maybe swapping out 1 with custom string formatting if you feel the need in the future.


test: Use new specdown features in wrapper

Closing this for now as have realised some way to improve specdown which will make this a lot better.


PR to add tests and configure travis

What does this PR do?
This PR  adds tests to my inverted index project and configures travis
Description of tasks to be completed
Add tests for InvertedIndex class
Add karma.conf.js, .travis.yml and gulpfile.js to project
Add browserify task to gulp file
How can this be manually tested?
N/A
Screeshots
N/A
Relevant Pivotal tracker stories
N/A

Changes Unknown when pulling 0f9d9b8fc2c899d0788c99c351560e7a6152b148 on feature/002/writing-tests into ** on master**.

Changes Unknown when pulling c18bf639139877ddbcf601fed856a85bdb60d2c2 on feature/002/writing-tests into ** on master**.


fix(build): support cssCodeSplit for cjs format

fix #2575

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Description

Additional context

@underfin I think that you could push to force appveyor to re-run.
Thought, Is there an easy way to add a test for this? (Ok to do this in a different PR).


Change RNTooltips extended class to PureComponent

Change logs

Change the class extended by RNTooltips from Component to PureComponent in order to bring shallow-comparison and avoid to create a new popup each time the parent view re-render.

#11

Thanks @StevenMasini for the effort and PR.
I have merged the same. Post fixing the ISSUE: 9, I will push the release.
Thanks
</ Pranav >


Updated style.css - Fixed issue #273

I have added the following two lines of code to style.css -  background-repeat:no-repeat;
background-size:cover;
This will fix the issue of the repeating background-image in the service-container section
If some change is needed in my PR, then please do inform and I will fix it right away.
Thanks

Solve conflict.

#273

I guess another Contributor has solved this issue!

You can work on other issue!


[fix] process failed tx as failed operations

Currently when a transaction fails/reverts we are not returning operations based on on receipt status.
Current code executes
if receipt.Status == types.ReceiptStatusSuccessful {
  // create operations
}

What the ideal behavior is if the transaction is reverted then we send the operation with status as failed.
This PR removes adds a failed check and let it execute all the needed methods.
From what I can see GetRegistryAddresses and GetTobinTax will execute as they don't really depend on status.
TxOpsFromLogs - this will not be needed as for failed tx, there would be no logs? (Is that the correct behavior?)
TxTransfers
I removed the check
if receipt.Status == types.ReceiptStatusFailed {
		return nil, nil
	}

since I believe we will be able to get trace of the failed tx and then InternalTransfersToOperations method will mark the tx as failed and this will return back a failed operation.
ReconcileLogOpsWithTransfers is not needed since we are not matching trace with logs since tx is failed.
Please take a look and let me know if any of above assumptions are wrong are wrong.

Closing as stale, feel free to reopen if this still applies.


If you are not a root user, you cannot use TCPDUMP for validation.

The automatic deployment of the Linux Agent for CEF logging only provides the login for an admin account, not root. Without root access, you cannot run TCPDUMP.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 9cbfa632-1612-9d5f-7f36-3128d7305f14
Version Independent ID: 000c1405-b54f-6668-daac-ac69c97d9601
Content: Collect CEF data in Azure Sentinel Preview
Content Source: articles/sentinel/connect-common-event-format.md
Service: sentinel
GitHub Login: @rkarlin
Microsoft Alias: rkarlin

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@mnuhfer Hi, thanks for your feedback. we changed the commands a bit  - they should work now. Please let me know if you're still encountering problems.
thanks!

#please-close


I have 19 errors when building a solution

Build started...
1>------ Build started: Project: FAST_Registry, Configuration: Release x64 ------
1>data.c
1>C:\openfast\modules\openfast-registry\src\data.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>gen_c_types.c
1>C:\openfast\modules\openfast-registry\src\gen_c_types.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>gen_module_files.c
1>C:\openfast\modules\openfast-registry\src\gen_module_files.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>misc.c
1>C:\openfast\modules\openfast-registry\src\misc.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>my_strtok.c
1>C:\openfast\modules\openfast-registry\src\my_strtok.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>registry.c
1>C:\openfast\modules\openfast-registry\src\registry.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>reg_parse.c
1>C:\openfast\modules\openfast-registry\src\reg_parse.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>sym.c
1>C:\openfast\modules\openfast-registry\src\sym.c(63,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>symtab_gen.c
1>C:\openfast\modules\openfast-registry\src\symtab_gen.c(34,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>type.c
1>C:\openfast\modules\openfast-registry\src\type.c(1,10): fatal error C1083: Cannot open include file: 'stdio.h': No such file or directory
1>Done building project "FAST_Registry.vcxproj" -- FAILED.
2>------ Build started: Project: MAP_dll, Configuration: Release x64 ------
2>Performing Custom Build Tools
2>======================================================================
2>'....\build\bin\Registry.exe' is not recognized as an internal or external command,
2>operable program or batch file.
2>'....\build\bin\Registry.exe' is not recognized as an internal or external command,
2>operable program or batch file.
2>
2>Error running FAST Registry for MAP.
2>
2>======================================================================
2>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets(240,5): warning MSB8065: Custom build for item "....\modules\map\src\MAP_Registry.txt" succeeded, but specified output "c:\openfast\modules\map\src\map_types.h" has not been created. This may cause incremental build to work incorrectly.
2>bstraux.c
2>C:\openfast\modules\map\src\bstring\bstraux.c(1004,26): warning C4267: 'function': conversion from 'size_t' to 'int', possible loss of data
2>C:\openfast\modules\map\src\bstring\bstraux.c(1017,13): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data
2>bstrlib.c
2>C:\openfast\modules\map\src\bstring\bstrlib.c(367,32): warning C4267: 'function': conversion from 'size_t' to 'int', possible loss of data
2>dpmpar.c
2>enorm.c
2>enorm_u.c
2>lmder.c
2>lmpar.c
2>qrfac.c
2>qrsolv.c
2>freedata.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>jacobian.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>lineroutines.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>mapapi.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>maperror.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>mapinit.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>numeric.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>outputstream.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>residual.c
2>C:\openfast\modules\map\src\map.h(38,10): fatal error C1083: Cannot open include file: 'MAP_Types.h': No such file or directory
2>simclist.c
2>Done building project "MAP_dll.vcxproj" -- FAILED.
========== Build: 0 succeeded, 2 failed, 0 up-to-date, 0 skipped ==========

The errors come because Visual Studio is not finding the "stdio.h" file in your C projects. This may be because you are using an old version of Visual Studio / Window SDK or because you have something set incorrectly in the Visual Studio settings. What version of Visual Studio are you using? Also, what platform are you building for? You can see this by opening the properties for the FAST_Registry project in your Visual Studio solution and looking at the Target Platform Version and Platform Toolset values:

Dear Ms. Bonnie Jonkman,
I am using VS2019 v142, I could not find any other version.
Best regards,
Noureddine Alawawdeh

Visual Studio 2019 should be able to find stdio.h. I would try changing the Windows SDK Version to 10.0 (or whatever version of 10 you have installed). It's possible the 8.1 SDK didn't get installed with your version of Visual Studio (I don't think it's a default option).
The screenshot of your Solution Explorer window shows an issue with the Fortran projects: they are all listed as "incompatible". That is a separate issue, but one that you should figure out. Do you have Intel Fortran installed, too?

Dear Ms. Bonnie Jonkman,
I reinstall VS2019 and Fortran, I think that I solved "incompatible" issue, and "stdio.h" too, but still doesn't work. I have 3977 errors as follow:
"========== Build: 2 succeeded, 2 failed, 0 up-to-date, 1 skipped =========="
"5>FAST - 31 error(s), 14 warning(s)"
"3>FASTlib - 3946 error(s), 174 warning(s)"
"4>------ Skipped Build: Project: OpenFAST-Simulink, Configuration: Release_Matlab x64 ------"
are the following configurations Right as depicted for the following: "OpenFast Simulink" and "FAST_Registry" and "MAP_dll"
Best Regards,


LabelPropagation plotting update

Description
Include a summary of this pull request
New dependencies: (Added to requirements_*.txt)
Fixes #170
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue -> bump patch)
[ ] New feature (non-breaking change which adds functionality -> bump minor version)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected -> bump major version)
[ ] Documentation Update
[ ] CI/CD workflows Update

Checklist

[ ] I have added tests that prove that my fix/feature works
[ ] Linters pass locally and I have followed PEP8 code style
[ ] New and existing tests pass locally
[ ] I have updated the documentation if needed
[ ] I have commented hard-to-understand areas in the code

Requirements

[ ] I have updated the MVG version

Stale PR. Closing.


:memo: Add my website to users.md

Hey @MikiVanousek, thanks for using Congo. While I'm happy to add your site to the list, I do think that the description you've chosen for your entry is in poor taste. Is that meant to be funny?

Yeah, it was supposed to be a joke. I understand if you don't like it. I will come up with something better.


Template uses tamague which doesn't work without expo-modules-core

Describe the bug
Error: Unable to resolve module expo-modules-core from /Users/XXX/Projects/MyAppName/node_modules/burnt/build/BurntModule.ios.js: expo-modules-core could not be found within the project or in these directories:
To Reproduce
Steps to reproduce the behavior:

npx react-native init MyAppName --template @criszz77/luna
cd MyAppName
cd ios:pods
yarn ios

Expected behavior
While I research an issue, I found that discussion, which says that there a library specifically for pure react native.
What do you think about library? If you are not okay with that, than probably it would be better to install required expo-modules-core
Desktop:

OS: macOS ventura
Version 13.1

Smartphone:

Device: iphone se 3rd generation
OS: iOS16.2

@krutilins You can also try to remove circumflex/caret like this:

Then run rm -rf node_modules ios/Pods && yarn && cd ios && pod install && cd ..
Perhaps this will help. Or yes, you can add expo unimodules if you want to use the latest version of Tamagui with the Toasts until this gets fixed. Thank you for your patience! Sorry if this is annoying.

Should be fixed now.


add method and service info to the handler context

Not sure if you want to have those generics on the HandlerContext interface. They help to narrow the method info type slightly but don't add that much value. Your call.

Not sure if you want to have those generics on the HandlerContext interface. They help to narrow the method info type slightly but don't add that much value. Your call.

It's not a perfectly clear case, but let's not add the type parameters.

Not sure if you want to have those generics on the HandlerContext interface. They help to narrow the method info type slightly but don't add that much value. Your call.

It's not a perfectly clear case, but let's not add the type parameters.

Agreed. Can always add them later if there's a need.