Build error with AuthProxy on Windows

I have an authentication proxy in my university. Win7 x64 machine.
In cmd I set up an enviroment variables:
SET HTTP_PROXY=username:password@proxyserver.com:port
SET HTTPS_PROXY=username:password@proxyserver.com:port

Calling E:\hie>stack ./install.hs hie-8.6.5 --verbose results with
git submodule sync --recursive
Synchronizing submodule url for 'submodules/HaRe'
Synchronizing submodule url for 'submodules/HaRe/submodules/cabal-helper'
Synchronizing submodule url for 'submodules/HaRe/submodules/ghc-mod'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/HaRe'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/HaRe/submodules/cabal-helper'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/HaRe/submodules/ghc-mod'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/brittany'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/cabal-helper'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/floskell'
Synchronizing submodule url for 'submodules/HaRe/submodules/haskell-ide-engine/submodules/ghc-mod'
Synchronizing submodule url for 'submodules/brittany'
Synchronizing submodule url for 'submodules/cabal-helper'
Synchronizing submodule url for 'submodules/ghc-mod'
git submodule update --init --recursive
stack --stack-yaml=shake.yaml --numeric-version
cabal --numeric-version
cabal v1-update
dieVerbatim: user error (cabal:
'C:\Users\WS-0001\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\usr\bin\curl.exe'
exited with an error:
curl: (28) Connection timed out after 300193 milliseconds
)
Error when running Shake build system:
  at want, called at src\Development\Shake\Internal\Args.hs:81:69 in shake-0.17.9-2jhL6CMFBCPCYba2aXg0ei:Development.Shake.Internal.Args
* Depends on: hie-8.6.5
  at need, called at install.hs:127:9 in main:Main
* Depends on: cabal
* Raised the exception:
user error (Development.Shake.command_, system command failed
Command line: cabal v1-update
Exit code: 1
Stderr:
dieVerbatim: user error (cabal:
'C:\Users\WS-0001\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\usr\bin\curl.exe'
exited with an error:
curl: (28) Connection timed out after 300193 milliseconds
)
)

Seems like Shake build system relies on curl call which is not take into account env variables.
I'm not sure that this problem caused by build config, maybe this is a problem of Shake by itself.

You should try running curl manually and find the options which work in your case. https://curl.haxx.se/docs/manpage.html
Then we can see what can be done. Note that the manual doesn't specify login/password in proxy urls

Thanks for the answer, I'll try that at Monday.

This type of call works fine without enviroment variables.
C:\Users\WS-0001\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\usr\bin\curl.exe -x proxyserver.com:port -U username:password https://github.com/haskell/haskell-ide-engine
With enviroment variables this call works fine
C:\Users\WS-0001\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\usr\bin\curl.exe https://github.com/haskell/haskell-ide-engine
In curl docs I found mention of config file.
I create .curlrc in C:\Users\WS-0001\AppData\Local\Programs\stack\x86_64-windows\msys2-20180531\home\user  with contet
-x proxyserver.com:port
-U username:password

and this type of workaround worked.
Seems like curl called in new instance of cmd, without proper env variables.
Anyway, I'm Ok with my workaround, this issue may be closed.

Where should this workaround be documented?

In README. "Installation behind a proxy" I think


Fix restore from a Django ContentFile

Read directly the file if it's a Django ContentFile (in-memory file).

Hello @dorianamouroux
Thanks for this PR and sorry for my latency.
Could you just update the commit (not another one) with the comment ?

Hello @dorianamouroux
Thanks for this PR and sorry for my latency.
Could you just update the commit (not another one) with the comment ?
Just for curiosity, do you use DBBackup outside of its native mechanisms ?

For what it's worth I hit this issue as well.  However, I also needed to include SFTPStorageFile in the tytpe check of stdin. I applied these changes as well as @ZuluPro's suggestion to the branch 'fix-restore' here:
https://github.com/django-dbbackup/django-dbbackup/tree/fix-restore
I'd love if we can get this merged, but I suspect we want a more generic type check than SFTPStorageFile.  I don't understand the issue enough to make it more of a catch all.

I merged pull request #280 which has this change.


exclude livenessprobe request in rule,fix k8s livenessprobe is unknown in kiali

exclude livenessprobe request in rule,fix k8s livenessprobe is unknown in kiali
https://github.com/istio/istio/issues/10336

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Liv1020
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

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

Hi @Liv1020. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

I signed it!

/assign @rshriram


Login with library

How can I login with library?
I tried to login with
from instascrape import Instascraper

with Instascraper() as insta:
    insta.login("username","password")
    posts = insta.profile("target account").story()
    posts.download_all(dest="./output")

But its return as :
instascrape.exceptions.CheckpointChallengeRequired: Failed to log into Instagram. (message: 'checkpoint challenge solving is required')

Catch the CheckpointChallengeRequired exception and handle it by calling insta.checkpoint_challenge_login.
https://github.com/tnychn/instascrape/blob/e136bb9f6037aed273b37001ab64d933b720cf75/instascrape/instascrape.py#L157-L193


Handle fulfillment component amount consolidation

Motivation
If there are any remaining amounts for any number of either offer or consideration items as part of a single fulfillment, Seaport will consolidate the remaining amounts into the first offer or consideration component.

Solution
cleanUpZeroedComponents -> consolidateComponents

Codecov Report
Patch and project coverage have no change.

Comparison is base (3392de2) 100.00% compared to head (0eb6b3d) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##               1.5     #1037     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           46        25     -21
  Lines         2652      1184   -1468
  Branches       396       134    -262
===========================================
- Hits          2652      1184   -1468

Flag
Coverage Δ

foundry
?

production
100.00% <ø> (ø)

reference
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 40 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Rename resolution to resampling_period

What's needed?
Change resolution to sampling_period for easier understanding what the resolution parameter does.
Proposed solution
resolution: int to sampling_period: timedelta
Use cases
No response
Alternatives and workarounds
No response
Additional context
No response

Should we still make this change @cwasicki? If so I could tackle it next week.

Yes, to me this makes sense.

In my first shot at this, I assume that we only want to change the client to be able to handle timedelta, not PBResamplingOptions(resolution=...)


Remove accidental network calls from specs

When we use real project names that exist in the overrides file, the tests will pull down license files from GitHub. I've fixed all cases of that I could detect here. In addition to being good hygiene for unit tests, this also avoids some test failure modes that are really confusing, especially for folks who are less familiar with the codebase.
Signed-off-by: Daniel DeLeo<EMAIL_ADDRESS>

For the cost of adding some development deps, we could prevent this with WebMock: https://github.com/bblimke/webmock#real-requests-to-network-can-be-allowed-or-disabled

@phiggins I thought it would be uglier to enable the stub on NetFetcher globally, but it was actually a bit nicer. 👍


AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'

Today, our daily gcloud ml-engine job has been broken. The problem may come from the changes in the module grpc-google-iam-v1. It seems that you did an update for the module grpc-google-iam-v1 from 0.11.1 (?) to 0.11.3  on the server-side.
I compared the "broken" version with the "working" version. I realized that the only diff is in the module grpc-google-iam-v1.
Python version: Python 2.7
Google-Cloud version:
google-cloud==0.24.0
google-cloud-storage==1.2.0
grpc-google-iam-v1==0.11.3

It has been broken because the pip tried to install grpc-google-iam-v1==0.11.3 which did not have the attribute RegisterServiceDescriptor in the object SymbolDatabase
Stacktrace:
Traceback (most recent call last): File "/usr/local/bin/pip", line 5, in <module> from pkg_resources import load_entry_point File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3074, in <module> @_call_aside File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3058, in _call_aside f(*args, **kwargs) File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3102, in _initialize_master_working_set for dist in working_set File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 3102, in <genexpr> for dist in working_set File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2633, in activate declare_namespace(pkg) File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2191, in declare_namespace _handle_ns(packageName, path_item) File "/usr/local/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 2126, in _handle_ns loader.load_module(packageName) File "/usr/lib/python2.7/pkgutil.py", line 246, in load_module mod = imp.load_module(fullname, self.file, self.filename, self.etc) File "/root/.local/lib/python2.7/site-packages/google/cloud/pubsub/__init__.py", line 30, in <module> from google.cloud.pubsub.client import Client File "/root/.local/lib/python2.7/site-packages/google/cloud/pubsub/client.py", line 28, in <module> from google.cloud.pubsub._gax import _PublisherAPI as GAXPublisherAPI File "/root/.local/lib/python2.7/site-packages/google/cloud/pubsub/_gax.py", line 19, in <module> from google.cloud.gapic.pubsub.v1.publisher_client import PublisherClient File "/root/.local/lib/python2.7/site-packages/google/cloud/gapic/pubsub/v1/publisher_client.py", line 37, in <module> from google.iam.v1 import iam_policy_pb2 File "/root/.local/lib/python2.7/site-packages/google/iam/v1/iam_policy_pb2.py", line 296, in <module> _sym_db.RegisterServiceDescriptor(_IAMPOLICY) AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'
Steps to reproduce:
It's very easy to reproduce:
Cause of #3736, we have to freeze the following version:
google-cloud == 0.24.0
google-cloud-storage == 1.2.0

ps: I did not test the latest version yet but at least the grpc-google-iam-v1==0.11.3 is not compatible with these versions google-cloud
Workaround: freeze the version grpc-google-iam-v1==0.11.1

@sonlac You can address #3736 instead by upgrading to the latest version (2.18.4) of requests
Can you upgrade to the latest version (1.4.0) of google-cloud-storage (which has a hard lower bound of 2.18.0 for requests) and see if the problem still persists?

@dhermes Thank you. I re-tested by upgrading the packages. In both cases, it always raises the same exception as above.
Don't you think that the problem comes from the module grpc-google-iam-v1-0.11.3?
Case 1:
google-cloud==0.24.0
google-cloud-storage==1.4.0
requests==2.18.4

Successfully installed packages in ml-engine job:
17:08:29.488 Successfully installed chardet-3.0.4 gapic-google-cloud-datastore-v1-0.15.3 gapic-google-cloud-error-reporting-v1beta1-0.15.3 gapic-google-cloud-logging-v2-0.91.3 gapic-google-cloud-pubsub-v1-0.15.4 gapic-google-cloud-spanner-admin-database-v1-0.15.3 gapic-google-cloud-spanner-admin-instance-v1-0.15.3 gapic-google-cloud-spanner-v1-0.15.3 gapic-google-cloud-speech-v1beta1-0.15.3 gapic-google-cloud-vision-v1-0.90.3 google-cloud-0.24.0 google-cloud-bigquery-0.24.0 google-cloud-bigtable-0.24.0 google-cloud-core-0.24.1 google-cloud-datastore-1.3.0 google-cloud-dns-0.24.0 google-cloud-error-reporting-0.24.3 google-cloud-language-0.24.1 google-cloud-logging-0.24.0 google-cloud-monitoring-0.24.0 google-cloud-pubsub-0.24.0 google-cloud-resource-manager-0.24.0 google-cloud-runtimeconfig-0.24.0 google-cloud-spanner-0.24.2 google-cloud-speech-0.24.0 google-cloud-storage-1.4.0 google-cloud-translate-0.24.0 google-cloud-vision-0.24.0 google-resumable-media-0.2.3 grpc-google-iam-v1-0.11.3 grpcio-1.6.0 idna-2.6 pandas-0.20.3 proto-google-cloud-datastore-v1-0.90.4 proto-google-cloud-error-reporting-v1beta1-0.15.3 proto-google-cloud-logging-v2-0.91.3 proto-google-cloud-pubsub-v1-0.15.4 proto-google-cloud-spanner-admin-database-v1-0.15.3 proto-google-cloud-spanner-admin-instance-v1-0.15.3 proto-google-cloud-spanner-v1-0.15.3 proto-google-cloud-speech-v1beta1-0.15.3 proto-google-cloud-vision-v1-0.90.3 requests-2.18.4 urllib3-1.22
and
Case 2:
google-cloud==0.27.0
google-cloud-storage==1.4.0
requests==2.18.4

Successfully installed packages in ml-engine job:
19:25:07.678 Successfully installed chardet-3.0.4 gapic-google-cloud-datastore-v1-0.15.3 gapic-google-cloud-error-reporting-v1beta1-0.15.3 gapic-google-cloud-logging-v2-0.91.3 gapic-google-cloud-pubsub-v1-0.15.4 gapic-google-cloud-spanner-admin-database-v1-0.15.3 gapic-google-cloud-spanner-admin-instance-v1-0.15.3 gapic-google-cloud-spanner-v1-0.15.3 google-cloud-0.27.0 google-cloud-bigquery-0.26.0 google-cloud-bigtable-0.26.0 google-cloud-core-0.26.0 google-cloud-datastore-1.2.0 google-cloud-dns-0.26.0 google-cloud-error-reporting-0.26.0 google-cloud-language-0.27.0 google-cloud-logging-1.2.0 google-cloud-monitoring-0.26.0 google-cloud-pubsub-0.27.0 google-cloud-resource-manager-0.26.0 google-cloud-runtimeconfig-0.26.0 google-cloud-spanner-0.26.0 google-cloud-speech-0.28.0 google-cloud-storage-1.4.0 google-cloud-translate-1.1.0 google-cloud-videointelligence-0.25.0 google-cloud-vision-0.26.0 google-resumable-media-0.2.3 grpc-google-iam-v1-0.11.3 grpcio-1.6.0 idna-2.6 monotonic-1.3 pandas-0.20.3 proto-google-cloud-datastore-v1-0.90.4 proto-google-cloud-error-reporting-v1beta1-0.15.3 proto-google-cloud-logging-v2-0.91.3 proto-google-cloud-pubsub-v1-0.15.4 proto-google-cloud-spanner-admin-database-v1-0.15.3 proto-google-cloud-spanner-admin-instance-v1-0.15.3 proto-google-cloud-spanner-v1-0.15.3 requests-2.18.4 tenacity-4.4.0 urllib3-1.22

For me it comes from the lib grpc-google-iam-v1.
I have downgraded to version 0.11.1: grpc-google-iam-v1==0.11.1 and it is working great now.
Indeed, I use an old version of google-cloud-pubsub: 0.27.0 instead of the latest 0.28.3

@lukesneeringer Can you confirm that grpc-google-iam-v1 (version 0.11.3 or any other) is still needed?

I assume it is, but not sure. I can try to find out.

@selfiebot We haven't actually confirmed it's an issue. It seems like a bad install of protobuf. (PS Are you a person or a bot?)

@dhermes Sorry about that. I commented via an internal thread, and the username surfaced as "selfie bot". :)

I'm having a similar issue to sonlac, although the error is occuring in apache beam. In my case I'm trying to run a dataflow job, the apache beam word count example that can be found here
Python version: Python 2.7
Google-Cloud version:

Google Cloud SDK 174.0.0
alpha 2017.09.15
app-engine-go
app-engine-python 1.9.61
beta 2017.09.15
bq 2.0.27
core 2017.10.02
datalab 20170818
gcloud
gsutil 4.27

I run the following command:
python -m apache_beam.examples.wordcount   --project unique-test-176123   --runner DataflowRunner   --staging_location gs://unique-test/staging   --temp_location gs://unique-test/temp   --output gs://unique-test/output
When I run it, I get the following stacktrace:
Traceback (most recent call last):   File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 174, in _run_module_as_main     "__main__", fname, loader, pkg_name)   File "/usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code     exec code in run_globals   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/examples/wordcount.py", line 126, in <module>     run()   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/examples/wordcount.py", line 105, in run     result = p.run()   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/pipeline.py", line 328, in run     return self.runner.run(self)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/dataflow/dataflow_runner.py", line 264, in run     super(DataflowRunner, self).run(pipeline)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/runner.py", line 133, in run     pipeline.visit(RunVisitor(self))   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/pipeline.py", line 353, in visit     self._root_transform().visit(visitor, self, visited)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/pipeline.py", line 685, in visit     part.visit(visitor, pipeline, visited)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/pipeline.py", line 688, in visit     visitor.visit_transform(self)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/runner.py", line 128, in visit_transform     self.runner.run_transform(transform_node)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/runner.py", line 171, in run_transform     return m(transform_node)   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/dataflow/dataflow_runner.py", line 492, in run_GroupByKey     self.serialize_windowing_strategy(windowing))   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/dataflow/dataflow_runner.py", line 787, in serialize_windowing_strategy     from apache_beam.runners import pipeline_context   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/runners/pipeline_context.py", line 27, in <module>     from apache_beam.portability.api import beam_fn_api_pb2   File "/Users/rubinghv/Library/Python/2.7/lib/python/site-packages/apache_beam/portability/api/beam_fn_api_pb2.py", line 2687, in <module>     _sym_db.RegisterServiceDescriptor(_BEAMFNCONTROL) AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'
I know it's in a different package, but since the error is so rare, I figured it's related.

@jonparrott @waprin Do you know who would be the point person for dataflow?
I seem to recall previous issues where pickle was being using to serialize Python objects across processes, so this might be related?
@rubinghv Do you mind running pip show protobuf from the same environment where the error occurred? (I'd also be interested in import google.protobuf as pb; print(pb.__version__) if they differ.)

@davidcavazos is new DPE focusing on it @amygdala is DA who tends to know things about it as well ,in case either of them can help.

@dhermes
Sure, no worries, and thanks for the quick reply.
pip show protobuf returns:

Name: protobuf
Version: 3.2.0
Summary: Protocol Buffers
Home-page: https://developers.google.com/protocol-buffers/
Author<EMAIL_ADDRESS>Author-email<EMAIL_ADDRESS>License: New BSD License
Location: /usr/local/lib/python2.7/site-packages
Requires: setuptools, six

When I run import google.protobuf as pb; print(pb.__version__), it prints: 3.2.0

This issue is still occurring even with protobuf on version 3.4.0

@parthmishra Can you run a few commands?
python -m pip show protobuf
python -c 'from google.protobuf import symbol_database; print(getattr(symbol_database.SymbolDatabase, "RegisterServiceDescriptor", None))'

It may be that you are checking the protobuf version and running the code in different interpreters by mistake

Sure, here's my output:
python -m pip show protobuf
Name: protobuf
Version: 3.4.0
Summary: Protocol Buffers
Home-page: https://developers.google.com/protocol-buffers/
Author<EMAIL_ADDRESS>Author-email<EMAIL_ADDRESS>License: 3-Clause BSD License
Location: /usr/local/lib/python2.7/dist-packages
Requires: six, setuptools

and
python -c 'from google.protobuf import symbol_database; print(getattr(symbol_database.SymbolDatabase, "RegisterServiceDescriptor", None))'
<unbound method SymbolDatabase.RegisterServiceDescriptor>

So it looks like there's no issue. The original report was:
AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'

@dhermes so if I'm still getting that AttributeError on a training submission, there is some other decency issue at play?

on a training submission

You need to make sure the interpreter that is running there has an up-to-date version of protobuf. Your local interpreter only tells you about itself.

I come across the same problem as Parthmishra described. I use protobuf-3.4.0, and the output check is as below:
python -c 'from google.protobuf import symbol_database; print(getattr(symbol_database.SymbolDatabase, "RegisterServiceDescriptor", None))'

But when I run the trainning, it show the same error message:
AttributeError: 'SymbolDatabase' object has no attribute 'RegisterServiceDescriptor'
I post a new issue in https://github.com/GoogleCloudPlatform/cloudml-samples/issues/99 to describe the details of my problem.
Is there anything else I can do to solve the problem?

@luckyapplehead I'm not familiar with this service, but the issue is the environment where you "run the training". What is the environment? Provide a link or some other context?

I have solved the problem according to parthmishra's advice as belows:

In your setup.py just list the version number afterwards i.e. protobuf==3.4.0 instead of protobuf (or change your requirements.txt if you're using that instead)

Thanks very much:)


[bug]: watchtowers: need to correctly handle acked updates for closed channels

Background
The logs shown in #7959 reveal a small watchtower client bug:
Basically if we have a updates queued in the tower client already but then the channel is closed, there is a chance that all the info for the channel could be deleted from the tower client and then when the ACK for the update comes back from the server, it will cause an error when we try to store the ACK.
Note that this is unrelated to the bug reported in #7959
Proposed solution:
Since we cant really prevent this scenario from happening, we should instead just account for it. So if we go to ACK an update for a channel that we no longer keep track of in the tower client, we should see this as a "Rogue" update and we should just at least keep track of the number of rogue updates that a session has backed up and we should not error in this case.
Affected versions
This would only have been possible since 0.16.1-beta

Basically if we have a updates queued in the tower client already but then the channel is closed,

Shouldn't we clean up the queue before marking it as closed in this case?

Shouldn't we clean up the queue before marking it as closed in this case?

So we do actually check that the chan still exists when we pop from the queue but there are some other edge cases like: if we have already assigned a SeqNum to an update or we have already backed up the update and we get an ACK back from the server.
We can eventually try to account for all these small edge cases but they will require quite a big re-design and migration since the channel ID is not available in an indexed way in the DB until the ACK is written.
So I think for now, this "catch all" approach is fine due to this also just being a small edge case. Worst that can happen is that we backup a few updates for an already closed channel.


select best approach for executing rslaser Python code on a GPU

Don't think about any code that invokes SRW. This issue is just about Python.

Which part of rslaser code in particular? Propagation?

Yes, propagation.
If you want to be specific, then let's consider propagation types 'n0n2_lct' and 'gain_calc'.
I'm thinking at a high level about the choice between PyTorch vs Numba vs some other technology.

@jeinstei let me know about https://www.taichi-lang.org which is an alternative to numba.

To be clear, I'm not trying to get to production code -- that will wait until the Phase 2b, if it gets funded.
What I want is a short-term effort to reasonably justify the selection of a technology to be used in the future.
Performance/speed is an important criterion, of course.
However, a technology that requires minimal changes to the serial source code would also be attractive.

@bruhwiler @k-wolfinger Do we have any "reference simulations" or configurations that we can agree upon to use for profiling? I'm thinking ones that would highlight specific simulation issues, such as:

More propagation effects (large geometry)
Multi-layer something something (lots of parallelization possibilities)
Simple everything

The fundamental calculation is a laser pulse propagating through a Ti:Sapphire crystal with thermal effects that lead to weak focusing, followed by a drift, where the pulse converges slightly.
The laser pulse can be represented by N slices, where N=10 is a good default, but we can reasonably increase this to 100 or larger. Each laser pulse slice is represented by a wavefront, consisting of Re(Ex), Re(Ey), Im(Ex) and Im(Ey) on a 2D Cartesian mesh. The crystal is represented by M slices, where again M=10 is a good default, but we can reasonably increase this to 100 or larger.
The Cartesian wavefront meshes can be 32 x 32 as a default, but we can imagine that higher resolution simulations will be important in the future, with mesh sizes of 1024 x 1024. When propagating each wavefront through each crystal slice, the linear canonical transform (LCT) developed by Boaz/Dan/Ilya is used, which includes 1 or more FFTs.
In terms of varying the complexity and intensity of the floating point operations, there are two primary axes:

increase the number of interactions (i.e. N*M) from 100 to 10,000
increase the size of the mesh from 32x32 to 1024x1024

I'm going to be "that guy" and ask -- do we have specific commands to run for benchmarking yet? Maybe one config for each of the 4 levels of complexity?
I haven't actually run rslaser yet, so I might be missing something about the practical usage

We have been mostly exercising the library via notebooks.
There are some tests that exercise the library from Python.
@k-wolfinger has agreed to create a plain Python example that executes the scenario described above.
It will be clear from her code how to vary the mesh dimensions and the number of slices.
@gurhar1133 will then create a few examples from Kathryn's code and put them in the repo, so that he can begin doing some profiling on the CPU, and we will have concrete code to consider for the comparative analysis of the various GPU technologies.

For the n0n2_lct propagator there are several calls to the srw code:

For each crystal slice, we iterate over the laser slices
For each of those laser slices, we call srwlib.SRWLWfr once and srwutil.calc_int_from_wfr four times

Given that our algorithms are still dependent on SRW, we cannot proceed with this activity as originally planned.
We do plan to remove this dependence on SRW in the future.


[Bug]: The queries get randomly reorders  in the entity pane when the user rename the new query

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
The queries get randomly reorders  in the entity pane when the user rename the new query

Steps To Reproduce
1. Go to datasource
2. Add a few queries for anyone datasource
3. Now change the query name of the recently added query
4. verify the display

Environment
Release
Version
Cloud

The entity explorer update now orders the items alphabetically


Improve: Add TypeScript declaration file paths for better compatibility

Improve: Add TypeScript declaration file paths for better compatibility

Added types field and ./types export to package.json for improved TypeScript type resolution.
Resolves issues with Could not find a declaration file for module 'react-native-shake' in TypeScript projects.

I was exactly looking for this, thanks @jeroen-van-dijk

Thank you.


Release 0.52.2

Target release date is the end of December 2022
Post release tasks:

[ ] Corral should be switched back to using "release" for FreeBSD releases
[ ] Corral release should be done

Release is underway

Release is complete but the post-release steps need to be done.


dashboard load too slow

a png file with Request URL: https://user-images.githubusercontent.com/2106987/68087873-a0543980-fe94-11e9-8203-62958ce69ed6.png can not be loaded even after 30s..

git clone -b 1.3 https://github.com/apache/incubator-apisix.git /tmp/apisix
cd /tmp/apisix
git submodule init
git submodule update
cd dashboard
yarn

This image is blocked by GFW...
BTW, would you like to have a try on the latest dashboard? here is the demo URL: http://dashboard.apisix.dev/


Enumerable check

Not sure about the implementation here.
Right now we're checking ERC721/ERC1155 for the tab and giving the user a checkmark, but we actually care about Enumerable for that tab to show anything.
might be worth showing the tab always but without the checkmark? or tab always but checkmark when enumerable?
for now, I left it so it shows the tab with checkmark when ERC721/ERC1155 but it tells you that you need to implement enumerable, also hides the Mint button if the contract is not mintable

implementation makes sense to me, we might be able to clean up the underlying logic of "is a feature enabled" more but that's not part of this arc of work


Assigning Key Code's to buttons

I'm seeing that there is a key code option I can assign to a button control, however any attempt to do so is doesn't seem to register.  I've tried going through control.update, the protected control.updateAttribute, and then by doing client.updateControls
I can confirm my other calls via updateControls do work when setting text and spark cost. Protocol defines it as a JavaScript key code if I remember right so any clues as to what I am doing wrong ?

Are you looking to assign a keycode to a button that can be used on the participant side within the browser?
This is a feature that didn't quite make its way into Interactive 2 but we're working on it making a return.

Ahhh ok then yes that is exactly what I mean.  Thank you for the help :)

(Closing out some old GitHub issues. 😊)
Keyboard controls were re-implemented in Interactive 2; see examples/keyboardControls.ts for a full demo


Fix #1303: Move Token Count Logging from XT.py to Agent.py

Resolves #1303
The following modifications were applied:
I have moved the token counting logic to Agent.py and updated XT.py to use the new logic. This should resolve issue #1303.
```xml
<modification>
<file>agixt/XT.py</file>
<operation>replace</operation>
<target>        try:
            prompt_tokens = get_tokens(new_prompt) + self.input_tokens
            completion_tokens = get_tokens(response)
            total_tokens = int(prompt_tokens) + int(completion_tokens)
            logging.info(f"Input tokens: {prompt_tokens}")
            logging.info(f"Completion tokens: {completion_tokens}")
            logging.info(f"Total tokens: {total_tokens}")
        except:
            if not response:
                response = "Unable to retrieve response."
                logging.error(f"Error getting response: {response}")
        try:
            self.auth.increase_token_counts(
                input_tokens=prompt_tokens,
                output_tokens=completion_tokens,
            )
        except Exception as e:
            logging.warning(f"Error increasing token counts: {e}")</target>
<content>        try:
            if not response:
                response = "Unable to retrieve response."
                logging.error(f"Error getting response: {response}")
        except:
            pass</content>
</modification>

<modification>
<file>agixt/Agent.py</file>
<operation>insert</operation>
<target>        return answer</target>
<content>        try:
            prompt_tokens = get_tokens(prompt) + tokens
            completion_tokens = get_tokens(answer)
            total_tokens = int(prompt_tokens) + int(completion_tokens)
            logging.info(f"Input tokens: {prompt_tokens}")
            logging.info(f"Completion tokens: {completion_tokens}")
            logging.info(f"Total tokens: {total_tokens}")
            self.PROVIDER.increase_token_counts(
              input_tokens = prompt_tokens,
              output_tokens = completion_tokens
            )
        except Exception as e:
            logging.warning(f"Error increasing token counts: {e}")
</content>
</modification>

<modification>
<file>agixt/app.py</file>
<operation>replace</operation>
<target>
        if __name__ == "__main__":
            uvicorn.run(app, host="<IP_ADDRESS>", port=7437)
</target>
<content>
        if __name__ == "__main__":
            uvicorn.run(app, host="<IP_ADDRESS>", port=7437)
</content>
</modification>

<modification>
<file>agixt/Agent.py</file>
<operation>replace</operation>
<target>    def load_config_keys(self):
        config_keys = [
            "AI_MODEL",
            "AI_TEMPERATURE",
            "MAX_TOKENS",
            "embedder",
        ]
        for key in config_keys:
            if key in self.AGENT_CONFIG:
                setattr(self, key, self.AGENT_CONFIG[key])</target>
<content>    def load_config_keys(self):
        config_keys = [
            "AI_MODEL",
            "AI_TEMPERATURE",
            "MAX_TOKENS",
            "embedder",
        ]
        for key in config_keys:
            if key in self.AGENT_CONFIG:
                setattr(self, key, self.AGENT_CONFIG[key])
        try:
            self.max_input_tokens = int(self.AGENT_CONFIG["MAX_TOKENS"])
        except Exception as e:
            self.max_input_tokens = 32000</content>
</modification>

<modification>
<file>agixt/Agent.py</file>
<operation>insert</operation>
<target>        if not prompt:
            return ""</target>
<content>        if not prompt:
            return ""
        if hasattr(self.PROVIDER, "increase_token_counts"):
            try:
                prompt_tokens = get_tokens(prompt) + tokens
                self.max_input_tokens = int(self.AGENT_CONFIG["settings"]["MAX_TOKENS"])
                if prompt_tokens > self.max_input_tokens:
                    logging.warning(f"Prompt tokens ({prompt_tokens}) exceeds max input tokens ({self.max_input_tokens})")
            except Exception as e:
                logging.warning(f"Error getting prompt token count: {e}")
</content>
</modification>

The pull request #1307, which moves the token count logging from XT.py to Agent.py, appears to be well-executed and addresses issue #1303 effectively. The code changes are organized into logical blocks, and the modifications to XT.py, Agent.py, and app.py all serve a clear purpose. The token counting logic has been successfully moved to the inference method in Agent.py, and the chat_completions function in XT.py has been updated to remove the old logic. Additionally, the Agent.py code now includes a check for the increase_token_counts method on the provider and includes a check to make sure that the prompt is not empty before calling the model. The code changes also include a check to make sure that the prompt tokens do not exceed the max tokens in the model. The load_config_keys method has been updated to set the max_input_tokens variable. Overall, the changes are well-structured, and I don't see any issues with them.


support for the  tag in yahoo mail ?

Ctrl
renders correctly in this, whereas it doesn't in Yahoo mail.
Image in yahoo mail below of the same text

Is this a limitation of MDhere or Yahoo mail.

The defauls css shipped with markdown here does not include a particular style for <kbd> elements.
You can modify it adding these lines to support it:
kbd {
 display: inline-block;
 margin: 0 .1em;
 padding: .1em .6em;
 font-family: sans-serif;
 font-size: 11px;
 line-height: 1.4;
 color: #242729;
 text-shadow: 0 1px 0 #ffffff;
 background-color: #e4e6e8;
 border: 1px solid #9fa6ad;
 border-radius: 3px;
 box-shadow: 0 1px 1px rgba(12,13,14,0.15),inset 0 1px 0 0 #ffffff;
 white-space: nowrap;
}

Would it be nice to have it in the default css? I think so!
It would also be nice to have a separated css for customizations or additions,
so that if the default css is updated with the extension, the changes would not be lost.

Thanks. I tried yours but I prefer the one that I found elsewhere.
Here's the css style I have:
 kbd {
  -moz-border-radius: 3px;
  /*-moz-box-shadow: 0 1px 0px rgba(0, 0, 0, 0.2), 0 0 0 2px #ffffff inset;*/
  -webkit-border-radius: 3px;
  -webkit-box-shadow: 0 1px 0px rgba(0, 0, 0, 0.2), 0 0 0 2px #ffffff inset;
  background-color: rgb(247, 247, 247);
  border-radius: 3px;
  border: 1px solid rgb(204, 204, 204);
  box-shadow: 0px 1px 0px rgba(0,0,0,0.2), inset 0px 0px 0px 2px #ffffff;
  color: rgb(51, 51, 51);
  display: inline-block;
  font-family: Arial,Helvetica,sans-serif;
  font-size: 10px;
  letter-spacing: 0.6px;
  line-height: 1.4;
  margin: 0px 0.1em;
  padding: 0.1em 0.6em;
  text-shadow: 0 1px 0 #fff;
  text-transform: half-width;
}

It renders like this:

You're right in saying there should be a user style but I don't mind so much now as I've more or less pinned down the style as I like it.


Dilate timeouts according to number of cores

The tests that rely on timeouts/sleeping fail spuriously on Travis. This PR dilates all the timeouts according to the number of CPU cores in the system.

Apparently, Travis reports 8 CPU cores therefore the dilation factor is now read from an env var.


Please add support for sd-xl

same needs

Same

+1
It would be really great if you could provide support for Stable Diffusion XL
Thanks a lot @JulianJuaner , @nqbinhcs  for sharing this amazing work 🥇 !!

Any update?


MRG+1: Fix _plot_topo_onpick (#3871)

Should fix #3871. I went through all mne-python's own related callback functions and seems they can all handle both axes object or pyplot coming.

LGTM. Can you add an entry in doc/whats_new.py in the BUG section, and add a URL for yourself at the bottom if you're not already there?

Thanks for the quick update. I changed the title to have MRG prefix to show that it's ready (from your end) for merge, and MRG+1 to show I approve. Now we just wait for the CIs to come back happy and the next dev to look can merge.

Thanks, happy to contribute,
-- Tk

Current coverage is 85.47% (diff: 100%)

No coverage report found for master at 5355095.

Powered by Codecov. Last update 5355095...d5d3d40

@jaeilepp is that ok for you?
as @jaeilepp wrote this I'd like him to double check.
thx @Teekuningas

Looks good 👍

Looks like the right fix. Thanks @Teekuningas


Add timestamps to electrs logs

The logs from electrs don't have timestamps.

That seems to be an issue with electrs itself then, this is just a Docker container for it

@mutatrum This might be the repo you are looking for: https://github.com/romanz/electrs
Also, electrs log does have timestamps (by now?) so this issue should be closed.


Unstake below min should result in full unstake

Because of this check, we can't go below minimum (including 0):
https://github.com/opentensor/subtensor/blob/a680526f7c5cb72214b07bbea9f5491bd566aa00/pallets/subtensor/src/staking.rs#L476

See: https://github.com/opentensor/subtensor/pull/462

Closing as completed in https://github.com/opentensor/subtensor/pull/462


Change in 0.6.2 breaks usage of source for sudo fragments

The change in version 0.6.2 breaks usage of the source parameter, because source and content cannot be specified to the resource at the same time. Previously the module worked because the inputs were undef by default, but with this change there will always be something passed as the content parameter. Resulting in the following error if the source parameter is used:
Error: Failed to apply catalog: Validation of File[10_global] failed: You cannot specify more than one of content, source, target at /etc/puppet/environments/staging/modules-eis/modules/sudo/manifests/fragment.pp:20

CC: @Phil-Friderici
Since this module is not yet v1.0.0, breaking changes are allowed. Suggest reviewing its functionality and parameters and making a v1.0.0 release.

I hope that https://github.com/Ericsson/puppet-module-sudo/pull/27 can satisfy both use cases.
Please give it a try.

Tried #27 in a local test environment and it solved the issue.

@gusson thanks for reporting and verification. Bugfix released in v0.6.3


Updated project per Xcode

Just updating the test project based on Xcode's recommendations.

Cheers!

Thanks <3


[BUG] After adding service-account-issuer for conformance test cluster-agent goes into crashloopBrackoff

Rancher Server Setup

Rancher version: v2.7.5-rc1
Installation option (Docker install/Helm Chart): Docker and Helm both.
Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.26.4-rancher2-1 Or Any k8s version.
Cluster Type (Local/Downstream): Downstream Custom.

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): Custom (AWS)

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom): Admin

Describe the bug
After adding service-account-issuer for the conformance test cluster-agent goes into CrashloopBackoff. Issue is NOT k8s v1.26 specific.
Services:
  kube-api:
    extra_args:
      service-account-issuer: 'https://xx-xx-xx-xx:6443' (Controlplane IP address)

To Reproduce

Create a rancher server v2.7.5-rc1

Go ahead and create custom cluster (make sure the NGINX is disabled in Advanced Options) with jenkins job add custom host.

Once the cluster is in active state, Edit cluster Yaml.

Add the following extra argument under the kube-api in service.
Services:
kube-api:
extra_args:
service-account-issuer:

Cluster goes into updating state.

Once cluster comes back in active state, download kubeconfig file by clicking on Ellipsis.

Click on Explore and try to access the cluster.

List all pods using kubeconfig from terminal.

Result

User gets logged out.
cattle-cluster-agent and calico-kube-controllers status shows CrashloopBrackOff.

Expected Result
All the pods' status is active.

Screenshots

the reason behind cluster agent getting stuck in CrashLoopBackOff is that the cluster agent and all other pods have the service account token issued by the previous so kube-api-server starts giving UnAuthorized error for all the requests sent to it by those pods.
One workaround to make the cluster active is delete all the existing pods (in all namespaces) so the newly created pods have service account token issued by the updated issuer.
One other way to keep the cluster active after updating issuer is to keep the earlier issuer in service account issuer list.
to set it we will need to add configuration in following manner while updating the issuer:
kube-api:
  extra_args:
    service-account-issuer: 'https://xx.xx.xx.xx:6443' (Control Plane IP address)
  extra_args_array:
    service-account-issuer:
      - rke // keep existing issuer so that pre existing pods continue to work

the "rke" is the issuer which is set by default from KDM. ref

Tested the adding service-account-issuer in the cluster for conformance test.
Adding the extra_args_array as mentioned here, fixed the issue along with the service-account-issuer.
Cluster comes up active successfully, hence closing the issue.


Put format in the path instead of the slightly awkward query param

I was thinking about this and it occurred to me that the format could be specified as an optional extension to the path rather than using the awkward ne_format query param
/v1/query/<query-name>?a=b would use the default formatter while
/v1/query/<query-name>/toml?a=b would use the toml formatter

@jessebmiller It was originally that way; I'm not clear offhand why we changed that.

I can't remember why we did either.
The optional query type prefix does seem to add complexity though. with those three options you can only specify the format if you also specify the query type.

Yeah, I do remember having to address the latter issue. In more recent versions of the api, that prefix is entirely unnecessary and was removed from the routing. In any case, I agree that having the format in the path is a preferable scheme, and will try to work that in soon.

#37


Start / Stop canister

Seems start and stop canister is missing. It would be great for various scenarios - when we want to check how a multi-canister setup will respond when some of the canisters stop.
Would this workaround do it ? Using updateCanisterSettings to put freezing threshold higher than the cycle balance to stop and then moving it down to start?

Adding support for stop and start is pretty trivial, I should be able to add it within the next days. If you need it sooner, feel free to make a PR.

This is released now in v0.4.0.
Docs:

startCanister
stopCanister

Feel free to open a new ticket if you need anything else.


Rebase onto upstream and replace owasm-std with oasis-rs

I intend to force push this as the new oasis branch (and maybe do a cargo release, if we're still doing that).

tests pass. is it possible to enable force pushing onto master?


[5.9][stdlib] Adjust availability of _CharacterRecognizer conformances

This is a cherry pick of #65086, reviewed by @glessard.
These never made it to 5.8, so their availability needs to be bumped to 5.9.
rdar://107909604

@swift-ci test

@swift-ci test windows platform

...
Failed Tests (2):
  Swift(windows-x86_64) :: IRGen/async/hop_to_executor.sil
  Swift(windows-x86_64) :: IRGen/async/non_musttail_target.sil

@swift-ci test windows platform


Docs - Add how to run code examples

Description of change
Added doc on how to run the provided code examples
Todo
Still in draft state as, ideally, I'd like to add links to articles created in PRs that are still open, but the content can be reviewed.
Links to any relevant issues
fixes https://github.com/iotaledger/guild-devx/issues/100
Type of change

Documentation Enhancement

How the change has been tested
Wiki was built locally
Change checklist

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation

Status?

Status?

I think we can close this for the time being. The content is covered in the getting started pages, and since we're in the middle of moving the docs to the wiki, it's bound to generate sync issues


Refactor Tasks

closes #10

add linting via jshint and jscs (copying files from TryGhost/Ghost)
remove unnecessary usage of grunt
fix linting errors

@ErisDS fixed most of the issues, working on linting the tests and fixing whatever travis bug seems to be occuring

@ErisDS all green :+1: should be good to go now :smile:


Disco bus

Contains updates to support board enumeration. This may not be backwards compatible (double check).

Thanks @gbalke, I will test tomorrow after 6. We can also test if this is back compatible.


nomis-data-hub

Environment details
Application Name
nomis-data-hub
Description of application
Nomis-data-hub is the legacy interface solution to facilitate data exchange between nomis, oasys and ndelius. Also produces critical data extracts (ie offloc) for internal (ie mercury) and external consumers (ie police)
GitHub team slug
studio-webops
Environments
Development | Sandbox
Test | Developer
PreProduction | Developer
Production | Developer
Tags

tag
value

application
nomis-data-hub

business-unit
HMPPS

owner
<EMAIL_ADDRESS>

Networking options
Subnet sets

[X] General - this application will use the same subnet as other applications in your business unit
[ ] Isolated - this application has highly sensitive data which must have its own isolated subnet with no network connectivity

How do users connect to the application?

[ ] Over the public internet
[ ] With a purple cabled device (please give details)
[X] With a MoJ Official device

Connectivity to other applications or external parties
Additional features

[ ] Additional VPC Endpoints
[ ] Extended DNS Zones
[ ] Other - please specify

Other information

Definition of done

[x] account created
[x] customer informed

Email sent to the above address stating the environments have been created. Asked them to raise any calls or issues on the ask channel


Add custom init support

error from cloudflare:
22:41:53.418 | + pdm install -G docs
-- | --
22:41:55.883 | Lock file hash doesn't match pyproject.toml, packages may be outdated
22:41:55.883 | Updating the lock file...
22:41:55.992 | python.use_venv is on, creating a virtualenv for this project...
22:41:57.129 | Virtualenv is created successfully at /opt/buildhome/repo/.venv
22:41:57.285 | STATUS: Resolving dependencies
22:41:58.070 | 🔒 Lock failed
22:41:58.071 | Unable to find a resolution for pydantic-core
22:41:58.071 | Please make sure the package name is correct.
22:41:58.073 | See /tmp/pdm-lock-tnl6dsgd.log for detailed debug log.
22:41:58.074 | [ResolutionImpossible]: Unable to find a resolution
22:41:58.074 | Add '-v' to see the detailed traceback
22:41:58.169 | Failed: build command exited with code: 1
22:41:59.027 | Failed: error occurred while running build command


Feature Request: Scheduled Jobs within Assemblyline UI

Background
Our team is increasingly experiencing use cases that demand the ability to schedule containers to run at specific intervals. These could serve various purposes such as automated data ingestion, scheduled results processing, and automated reporting. Currently, the management of additional infrastructure for this process proves time-consuming and exposes Assemblyline (AL) to various systems, complicating oversight.
Proposed Feature
We propose the addition of a new feature in AL that allows us to schedule containers to run at specific intervals, leveraging the existing infrastructure. This feature would be analogous to the process of adding services, but under a dedicated tab specifically for scheduled tasks.
These tasks should have direct access to the submission results, hence streamlining the process by eliminating certain API calls.
New Component: Jobs Tab
The new 'Jobs Tab' in the AL UI will expose the current Jobs process. Just as services are added now in the Services Tab, we can add scheduled jobs, provide a manifest with our ACR instance, credentials, and schedule. In the background, AL will create the Kubernetes Jobs.
Specialized Jobs and Access Management
Some jobs should be tailored to function like the current YARA and configExtractor services, with an updater component that fetches from remote repositories like GitHub and executes scripts from there.
We also foresee scenarios where jobs need restricted data access (for instance, based on TLP restrictions). Therefore, we should be able to set access rules for each job.
Benefits
The key benefits of this feature include:

Simplified management and oversight since all scheduled tasks will be within AL.
Simplified visualisation of failed jobs
Reduced risks, as the need for exposing AL to different systems will be minimized.
Better onboarding process for new teams as they can serve themselves without additional backend access.
Easy update and management of jobs through the AL UI.

In CCCS we use Apache Airflow for scheduling automation with Assemblyline and other system, is that an option for you?
https://airflow.apache.org

Thanks @cccs-jp Airflow is certainly an option and we'll be looking into it. This idea comes from the notion that, at least from an academic sense, you never really "are done" with an analysis, you just reached the limits of your ability to add value at the moment. For instance, one use case would be to; take all domains and mine periodically for whois data or reverse ip, etc..
I understand the complexity of this ask, and please treat it as a nice to have, we'll be looking at how we can leverage Airflow.

Thanks @cccs-jp Airflow is certainly an option and we'll be looking into it. This idea comes from the notion that, at least from an academic sense, you never really "are done" with an analysis, you just reached the limits of your ability to add value at the moment. For instance, one use case would be to; take all domains and mine periodically for whois data or reverse ip, etc..
I understand the complexity of this ask, and please treat it as a nice to have, we'll be looking at how we can leverage Airflow.

Also just adding here, much of this conceptually can be mapped back to what is known as a 'Blackboard System'. FTA:

Status on issue? Is this still something we're interested in pursuing?

We would still love to have the ability to do this through the UI, it will enable analysts to do this directly, I think the only way to do it right now is an Administrator creating an AKS job.

Closing issue for now. If there is still interest in the topic, feel free to re-open!


add nodeSelector kubernetes.io/os: linux to virt-operator csv

What this PR does / why we need it:
this PR adds kubernetes.io/os: linux nodeSelector to virt-operator.
All other components already have this nodeSelector and virt-operator
was missing it
Signed-off-by: Karel Šimon<EMAIL_ADDRESS>Release note:
Add nodeSelector kubernetes.io/os: linux to virt-operator csv manifest

@tiraboschi can you please advice if it is a right way to add the linux node selector to virt-operator? Was there any reason, why the only virt-operator did not have this nodeSelector, but others (controller, handler, ..) have it?

@enp0s3 @tiraboschi can you please review?

/lgtm

/cherry-pick release-0.53

For OLM managed operators, supported OSs and architectures are stated at CSV level with labels:
labels:
    operatorframework.io/arch.<GOARCH>: supported
    operatorframework.io/os.<GOOS>: supported

On the HCO side we are stating:
https://github.com/kubevirt/hyperconverged-cluster-operator/blob/main/deploy/olm-catalog/community-kubevirt-hyperconverged/1.8.0/manifests/kubevirt-hyperconverged-operator.v1.8.0.clusterserviceversion.yaml#L21
  labels:
    operatorframework.io/arch.amd64: supported
    operatorframework.io/os.linux: supported

and this will instruct the OLM about refusing to install our operators on nodes with unsupported OSs and architectures.
See:
https://github.com/operator-framework/olm-docs/blob/master/content/en/docs/advanced-tasks/ship-operator-supporting-multiarch.md
Then we can also add specific node selectors, but this can potentially collide, if not correctly configured,  with the top level statement.


[AVM Module Issue]: Intermittent errors when deploying large configurations with multiple services

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
Bug
(Optional) Module Version
v0.5.0
(Optional) Correlation Id
No response
Description
I've observed that VWAN will intermittently fail installations when deploying multiple hubs with multiple gateways and firewalls.  This appears to be due to sequencing.  Recommend setting explicit dependencies between resources to allow VWAN to only attempt one service in a hub at once.

I'll add a PR to set explicit dependencies between resources to ensure resources don't step on each other.


Section 2-2

Add a sentence that the ApplicationLifecycleListener needs to be removed. The code snippet removes it, but the instructions do not

There's a typo in the instructions. It says to click ApplicationLifecycleListenerEvent but it should be ApplicationLifecycleEvent

https://github.com/Azure-Samples/workshop-migrate-jboss-on-app-service/pull/71


Can not install the package which doesn't support kernel 4.14

Hi,
When I install the ipk or build the package by myself, it throws error:
`root@OW4:~# opkg install luci-app-openclash_0.40.15-beta_all.ipk
Installing luci-app-openclash (0.40.15-beta) to root...
Collected errors:

satisfy_dependencies_for: Cannot satisfy the following dependencies for luci-app-openclash:

 kernel (= 4.14.180-1-e1dd7676581672f6f0bdb1363506dee1)

opkg_install_cmd: Cannot install package luci-app-openclash.`

my kernel is 4.14.180, why does this have such restriction and how to overcome it?
Thanks,
Song

I think you may solve this problem by installing the kernel ipk manually.  https://downloads.openwrt.org/releases/

Use --force-depends when installing


highlight group not found: Normal

When I activate Indent Guides Vim throws this error
Error detected while processing function <SNR>47_IndentGuidesEnable[1]..indent_guides#enable[8]..indent_guides#init_script_vars[7]..indent_guide
s#capture_highlight:
line    2:
E411: highlight group not found: Normal

I commented the code and now it works fine.
  ""let s:hi_normal   = indent_guides#capture_highlight('Normal')

  " remove 'font=<value>' from the s:hi_normal string (only seems to happen on Vim startup in Windows)
  ""let s:hi_normal = substitute(s:hi_normal, ' font=[A-Za-z0-9:]\+', "", "")

Sounds like you're not using a colorscheme, or your colorscheme isn't defining colours for the Normal highlight group.
Try using a different colorscheme, or manually defining the indent guide colours:
let g:indent_guides_auto_colors = 0
hi IndentGuidesOdd  guibg=red   ctermbg=3
hi IndentGuidesEven guibg=green ctermbg=4

Please re-open if this is not the case.


Codes running on CPU

Thanks for your great work again
While running the codes, I found out that at first the codes run on GPU then after some time they start to run on CPU.
Could you explain why is that and was it intended?
Thanks!

Hi, I think the only parts that run on the CPU are poisson surface reconstruction and clean-up steps with Open3D/trimesh. That is because these things do not have a GPU implementation as far as I'm aware. Everything else should be on the GPU though. Is it not the case?

Yes, within a minute GPU usage starts from around 16000mb and drops to approximately 8000mb. From that time CPU usage amount surges. Could there be any other reason?
thanks for your reply

Could you try to debug which tensors are not stored on the GPU?

Like you have mentioned, it was the code "ms.generate_surface_reconstruction_screened_poisson(depth=depth)" which cuased the overusage of CPU. Is there any other alternative way to run this code and replicate your results? Becuase our computing system cannot afford such CPU usage amount.

Becuase our computing system cannot afford such CPU usage amount.

You can always try to run the poisson surface reconstruction in the meshlab GUI, e.g. also see #17


Vite + babel-plugin-styled-components throws

Hello, the problem seem to be related to wrapping svg Icons with styled-components, but it is very hard to follow.
I know this is not much for investigating, but i cant seem to find the proper stack.
Uncaught TypeError: Unable to determine current node version
at versionIncluded (index.js:51:9)

Maybe it's not the case but when I bumped into this error it was because I didn't have twin.macro installed properly in the project. In my case I had a storybook app and tried to use twin.macro inside that but I didn't have twin.macro installed. Very weird error message though.

How are you getting the plugin to work at all in vite? The most recent resolution I see in the other, longer Vite thread is to run very old versions of styled-components, which I am not willing to do.  I just get Error: The following dependencies are imported but could not be resolved:  styled-components/macro and I've rather given up on readable class names during debugging.

Is this plugin supposed to work without macros? on vite it doesn't (SC v6 + plugin)
This does nothing:
 plugins: [
    react({
      babel: {
        plugins: [
          [
            'styled-components',
            {
              displayName: true,
            },
          ],
        ],
      },
    }),


VPN connection metrics, extended statistics and average

fixes #20 #22

Added VPN connection metrics
Added ExtendedStatistics (percentiles)
Added Average Statistic

Thanks a lot 👍


ORTE communications issue on c6gn.16xalrge using EFA

There seems to be some network problems when using EFA on the c6gn instances.
AWS ParallelCluster version: 2.10.0
Pcluster config:

[aws]
aws_region_name = eu-west-1
[global]
cluster_template = default
update_check = true
sanity_check = true
[aliases]
ssh = ssh {CFN_USER}@{MASTER_IP} {ARGS}
[ebs myebs]
shared_dir = /work
volume_size = 1000
[vpc default]
vpc_id =
master_subnet_id =
[cluster default]
key_name =
base_os = ubuntu1804
custom_ami = ami-07b73abb892002aba
scheduler = slurm
master_instance_type = c6g.xlarge
vpc_settings = default
ebs_settings = myebs
queue_settings = compute
[queue compute]
compute_type = spot
enable_efa = true
enable_efa_gdr = false
placement_group = DYNAMIC
compute_resource_settings = default
[compute_resource default]
instance_type = c6gn.16xlarge
max_count = 100
spot_price = 1.2

Error is:

ORTE has lost communication with a remote daemon.
HNP daemon   : [[45674,0],0] on node compute-dy-c6gn16xlarge-1
Remote daemon: [[45674,0],2] on node compute-dy-c6gn16xlarge-3
This is usually due to either a failure of the TCP network
connection to the node, or possibly an internal failure of
the daemon itself. We cannot recover from this failure, and
therefore will terminate the job.

The cluster runs jobs fine with c6g non-EFA instances.
All logs in /var/log/parallelcluster look normal, no related errors or issues.

Hi @SiHubb,
The description says that you're using v2.10.0. We added support for EFA on c6gn instances starting with v2.10.1. From the changelog:
Install EFA kernel module on ARM instances with alinux2 and ubuntu1804. This enables support for c6gn instances.

Would you be willing to trying with the new version?

Hi,
Thanks. Yes upgrading no problem - I upgraded to 2.10.0 on hearing the release of c6gn instances assuming it would be EFA ready - I'll make sure I check in future.
Simon.

Running c6gn's with EFA fine under pcluster 2.10.1 so closing this - thanks for your help.


fix typo

To be able to run this line using pip no spaces are permitted at this point.

@JuliaSprenger Good catch, thanks!


Add missing JavaDocs

Signed-off-by: Martin Mihálek<EMAIL_ADDRESS>

Coverage remained the same at 84.672% when pulling 88bd792da6165882d0a64a8158fe3fa7b9c0d376 on JavaDocs into 9bf24437af54a6fa6361bc572540b695a126359a on master.


Fix #217. Use Appraisal to test the gem

I would merge this on 🟢

@dblock ready!

Thanks, check out #196 pls.

Thanks, check out https://github.com/mongoid/mongoid-rspec/issues/237 if you want to take on some maintenance/release of this gem.


Dify: add global.labels to values file

resolve #90, enable to define global labels.

Thanks for your pr, do you think splitting the config into podLabels and deploymentLabels is better? The would be more clear than just labels.
Would my new proposal cover more use case and more understandable? I don’t use this feature so you opinion also matters.

Thanks for your pr, do you think splitting the config into podLabels and deploymentLabels is better? That would be more clear than just labels.
Would my new proposal cover more use case and more understandable? I don’t use this feature so you opinion also matters.

Personally, I don't think it's necessary. Most of the Charts I've seen only define an option like extraLabel. The main purpose is just to use the label to locate the actual payload (such as a Pod).

如果只是用来定位pod，那helm 自带的label app.kubernetes.io/name label如何呢？能否满足需求？
如果不能，确实需要额外的label，还请在命名和注释上体现这些label是做什么用的，会注入到哪里，以方便后续的使用。

如果只是用来定位pod，那helm 自带的label app.kubernetes.io/name label如何呢？能否满足需求？
如果不能，确实需要额外的label，还请在命名和注释上体现这些label是做什么用的，会注入到哪里，以方便后续的使用。

比如一场景，在 FinOps 需要按照 Pod 统计成本，那么会被某个 team 或者项目的 pod 打上相应 label，比如 example.com/team: devteam，成本计算模块会按照这样 label(或者 annotation)来统计成本。

谢谢解释, 那现在麻烦就加一下注释, 并且改一下名字叫 extraLabels , 明确说明他的用途和效果就可以了.


Changed links / owner of device watcher

Changed owner and all links for the adapter device-watcher to iobroker-community. The only one thing I wasn't able to was to change the owner in npm altough I'm a dev member in the npm iobroker-community. Well, maybe you can change it or assist.

I will take care of it

@ciddi89
Please sent me an invite at npm (mcm1957) so I can do the npm changes

Done


Plugin not reading storage properly.

The plugin seems to have stopped reading the h2 database, and will no longer allow users to connect to my server with luckperms installed. All I have done to the server is delete a few backups. Our server ran out of disk space, so I had to stop the server and delete those, not sure if something within LP got corrupt or not. If you need anymore info just let me know.
Msg when trying to log in: https://gyazo.com/71e63454a1cb5fa46f01f8ee3c0a8194
Console Error: https://pastebin.com/e9Ds9pMT
Old Config: https://pastebin.com/NCct6VXi (This is the config I had when this all started)
New Config: https://pastebin.com/HLNVZaPE

Hmmm, sooo. . . . I fixed it somehow
I just removed the h2 database, booted it with a new one, then put the old one back in, and it works now.


A question on memory

Hello this is a question - with regards to the memory spec on running the OSS LLM - see below:
Note: You should have at least 8 GB of RAM to run the 3B models, 16 GB to run the 7B models, and 32 GB to run the 13B models.
Is the reference to Memory requirement for GPU or the Main Memory (CPU) ? or a combination of GPU Memory and CPU Memory ?
Appreciate a clarity on this.
Thanks in advance.

I have 32 GB RAM and 12 GB GPU VRAM.
I can run all 7B models fine.
When I try to load any of the 13B models I get an error and runner exits with illegal instruction core dump.
Error: llama runner process has terminated

I was able load the 13b llama2 by explicitly specifying ollama run llama2:13b.  I presume if we don't qualify the parameter size, then it defaults to the largest model, hence the cause my error.


Different results in different projects

Hello!
I'm using the decal shader in 2 different projects, both in Unity 2019.4.2f1.
Project #1 is brand new (freshly created), and there my decal looks exactely like expected:

Project #2 has been upgraded multiple times already, and even though I use the same texture, colors and settings in the decal, it looks like this:

What could I check to find out what goes wrong in project #2?
Thank you very much.

It turns out that the intensity is only displayed as in project #1 if Post Processing Bloom is used (which gives this glowing aura).


Possible smart ordering of CLI switches

Right now this call
opustags --add ARTIST=omg --delete ARTIST

adds ARTIST and then deletes the ARTIST, which results in removal of all prior ARTIST entries and not adding ARTIST=omg entry. The proposition is to introduce "smart ordering" (I just called it that) to CLI arguments so that it's always like this:

Global operations such as -e, --import, --delete-all
Deletion operations (--delete)
Update operations (--set)
Insertion operations (--add)

With this, it'd remove all the ARTIST entries and add one ARTIST=omg entry, essentially replacing all artists with omg.
I'm not a fan of this approach since, beside sub-ideal code it needs to introduce, it feels kind of counter-intuitive to me; after all I just told the program to add a tag, and then delete a tag. I'd expect it to do just that - the fact it's a silly thing to do is just my fault for telling it to do something silly.
We could use external opinion on this.

I agree on that it's a bad idea to try to automatically correct user's command without knowing their true intent.
Perhaps an additional flag --fix-ordering-for-me-please (or its opposite, whichever will be default) would be the best of both worlds, provided this flag is known to the user beforehand.
But still, forcibly fixing user's mistakes without their knowledge won't help anyone in the long run.

I see two options:

Make things clear and forbid specifying nonsensical operations (--add then --delete).
Hide these strange behaviors from the man page and let users discovered unexpected possibilities.

Noting also that something like --import --add X=Y --import is strange if we want to preserve the original order. This case is in favor of option 1.


Audio [En]

Here is the lesson folder.
[why?] It's the right time to do podcast because there it is a growing media. You're free to experiment, there's a lot of room to grow. The act of listening to someone can create a nice conection, avoiding prejudice, which makes easier to send a message. Also, you can be less formal than the writing.
[how?]
This is the basic outline of this lesson:

[ ] 1. What are podcasts?
[ ] 2. Reinforce Storytelling
[ ] 3. Scripts
[ ] 4. Interviews
[ ] 5. Capture audio
[ ] 6. Editing
[ ] 7. Disseminating your podcast

You can help by creating fancy slides in Google Presentations using our template, making an activity roadmap in a md in the folder or in Google Docs using our template, gathering resources in a md file in the folder (or here in the Issue) or giving feedback here in the issue.
Please, consider taking a look at our tips on making our lessons more accessible.
[what?] An 8h lesson on science communication by audio.

Hello, and thanks for this initiative :-)
I can't contribute 8h, but about a 16th of that: Knowledge Communication? Back to the Ears! ;-)

[...] introduces concepts and advantages of audio podcasting with particular regards to the use-cases of scientists. In order to help novices take the hurdle of starting a podcast, she explains several gratis software tools and simple work-flow examples. Finally, audience questions and comments were addressed.

Thank you so much, @katrinleinweber ! This is great material! Actually the whole class is 8h long, with the practical activity. Would you be interested in be listed as a facilitator for this lesson?

If you use my recording and/or notes and find them helpful, please do list me. It's all CC-BY ;-)

I assume you that I will help you here, right? :P I will start from scratch? Just to be sure :)

Yaaaasss!! Thank you so much, @mlbonatelli !! I think you can edit the first comment and the README in the lesson folder to change the subjects listed if you need.


Add ability to re-organize over smb/sFTP

What is it
Add protocol support to run organize over network drive locations, e.g., by smb.
When I try to do this, I get a completely sensical and well articulated error:

ValueError: Invalid location smb://nasname._smb._tcp.local/Public/username (protocol
'smb' is not supported)

Why is it important?
I want to re-organize my files on my NAS. The NAS itself supports SSH'ing in and supports a version of python, but it would be awesome to be able to extend organize to be able to include the smb protocol explicitly.

In order to use the smb protocol you need to install fs.smbfs:
https://pypi.org/project/fs.smbfs/
Then you can use a connection string (FS URL) like the given example to connect via smb.


Error Code -11800, AVFoundationErrorDomain

The player has always worked with this video, from today I get this error:

This is the code:
<View style={{ flex: 3 }}>
    <Video
        ref={(ref) => { this.video = ref }}
        style={styles.video}
        url={require('./../../assets/videos/video_promo.mp4')}
        resizeMode='contain'
        inlineOnly={true}
        logo=' '
        onError={(error)=>{
            console.log("Error in Video",error)
        }}
        error={false}
    />
</View>

[X] react-native-af-video-player version: 0.2.1
[X] React Native version:  0.55.4
[X] OS: macOS 10.13.3

@matteocollina Are you getting this error on the Simulator? It seems that react-native-video has some problems with playing videos from local file system inside the Emulator/Simulator: https://github.com/react-native-community/react-native-video/issues/644#issuecomment-358885148
By the way, isn't the path of your resource correct? It seems, that there is either missing one more 'dot' or there are one dot and slash to much => require('../../assets/videos/video_promo.mp4') or require('../../../assets/videos/video_promo.mp4')

@no-weller I do not know why, but it was a temporary mistake. Not changing anything is back to work.


Add the "a single DB for all tenants" model of multi-tenancy

Currently, Prisma-multi-tenant uses the "one DB per tenant" model of multi-tenancy. However, we could also add the possibility to use the "a single DB for all tenants" model of multi-tenancy.
Here is how it would work:

pmt init

Asks which mode to use
If SingleDB, add a "Tenant { id String @id }" model, add "tenantId: String @default('dev')" on all models
Migrate DB, then creates the first tenant: "dev"

const multiTenant = new MultiTenantSingleDB({sharedModels: []})

An option for "shared models" which are shared between tenants (ex: Users?)

const prisma = multiTenant.get('tenant_A')

Adds a middleware to the PrismaClient that adds { where: { tenantId: 'tenant_A' } } on every queries

prisma.users.findMany()

Same as always!

References:

https://github.com/prisma/prisma/pull/3029
https://github.com/prisma/prisma-client-js/issues/770
https://github.com/prisma/prisma/discussions/2846

this is my WIP take on how to solve this:
export const injectTenant = (prisma: PrismaClient, subDomain: string) => {
  prisma.$use(async (params, next) => {
    if (params.model === 'Setting') {
      return next(params)
    }

    if (params.action === 'delete') {
      return next(params)
    }

    if (['create', 'update'].includes(params.action)) {
      params.args.data = { ...params?.args?.data, tenantId: subDomain }

      return next(params)
    }

    if (!params?.args) {
      params = { ...params, args: {} }
    }

    if (!params?.args?.where) {
      params = { ...params, args: { ...params.args, where: {} } }
    }

    if (params.action === 'findOne') {
      params.action = 'findFirst'

      params.args.where = Object.keys(params.args.where).reduce(
        (prev, next) => {
          return { ...prev, [next]: { equals: params.args.where[next] } }
        },
        {}
      )
    }

    if (params?.args?.where?.AND) {
      params.args.where = {
        AND: [{ tenantId: { equals: subDomain } }, ...params.args.where.AND],
      }
    } else {
      if (params?.args?.where && Object.keys(params?.args?.where).length > 0) {
        params.args.where = {
          AND: [
            { tenantId: { equals: subDomain } },
            ...Object.keys(params.args.where).map((key) => ({
              [key]: params.args.where[key],
            })),
          ],
        }
      } else {
        params.args.where = {
          tenantId: { equals: subDomain },
        }
      }
    }

    return next(params)
  })
}

Every model in the db has a tenantId field, which sadly has to be marked optional, since the prisma calls dont know a middleware is injecting the tenantId

I don't have much to add here, except that it would be awesome to have this.
I think a lot of SaaS db's are following a single-db multi-tenant pattern, especially in the early days.
For me it makes no sense to spin up a db for each new customer when I am testing the waters with a blitz app to see if there is a viable market.
This could make this plug-in much more accessible to a wide array of bootstrapping SaaS entrepreneurs using these frameworks like blitz and redwood.
Would love to keep the discussion going here. @BjoernRave how is your solve above working out? It looks like it is missing some cases, but seems like a solid jumping off point. Have you made any adjustments to that since implementing?
I'm no prisma/db expert, but happy to help where I can on this.

Hey guys ! Any news about single DB for all tenants being supported by Prisma ?

@BjoernRave I was curious if the WIP example you provided here is still the best option or have you made progress in other areas?

To much commercial potential that this is not openly shared?
every search in this topic leads to a death end.
I assume so hardcore team members would be able to cook an example up since they know the inner workings of prisma exactly?
Perhaps Citrus for postgresql and prisma integration is the best bet?

@BjoernRave Do you have an update on your version or a Git place where you store it? Then we can improve upon it together. Thanks :-)


How-To guide: base Kubernetes YAML

Thank you for helping make the Radius documentation better!
Please follow this checklist before submitting:

[x] Read the contribution guide
[x] Commands include options for Linux, MacOS, and Windows within codetabs
[x] New file and folder names are globally unique
[x] Page references use shortcodes instead of markdown or URL links
[x] Images use HTML style and have alternative text
[x] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description
Taking over https://github.com/radius-project/docs/pull/748 from @jasonviviano to add a how-to guide on applying a base Kubernetes YAML using Radius.

Issue reference
Fixes: #703

consider using this example instead to illustrate this feature: https://github.com/willdavsmith/radius/blob/willdavsmith/0.30-release-fixes/test/functional/shared/resources/testdata/manifest/basemanifest.yaml


Task: Tested Django-React REST Framework

We need to find a way to make Django speak to React. Basically, the backend must speak to the frontend.  We found Django REST framework which allows to do so.

The task was to setup and test the Django REST framework with some dummy React app. I pushed the results to the branch "test_django_react". This branch SHOULD NOT merge to main. It's just an example for us to view.


fix "GROUP BY' clause

To accommodate changes in newer MySQL versions the fix was introduced in issue #82.
Randy suggested and implemented a fix by adding all  of the select fields to the "GROUP BY' clause.
The queries created with this fix return different set of data than the old ones.
Database mv_clue_2016
OLD query
SELECT
model,
fcst_init,
fcst_valid,
fcst_lead,
fcst_var,
object_id,
object_cat,
'CNT_FSA' stat_name,
COUNT(object_id) stat_value
FROM
mode_header ,
mode_obj_single ,
mode_cts
WHERE
fcst_valid IN ('2016-05-04 01:00:00', '2016-05-04 02:00:00', '2016-05-04 03:00:00', '2016-05-04 04:00:00', '2016-05-04 05:00:00')
AND model IN ('core01_hwt')
AND fcst_lead IN ('10000', '20000')
AND fcst_var = 'APCP_01'
AND fcst_flag = 1
AND simple_flag = 1 AND mode_obj_single.mode_header_id = mode_header.mode_header_id
AND mode_cts.mode_header_id = mode_obj_single.mode_header_id
AND mode_cts.field = 'OBJECT'
GROUP BY fcst_lead, model,fcst_valid;
returns
+------------+---------------------+---------------------+-----------+----------+-----------+------------+-----------+------------+
| model      | fcst_init           | fcst_valid          | fcst_lead | fcst_var | object_id | object_cat | stat_name | stat_value |
+------------+---------------------+---------------------+-----------+----------+-----------+------------+-----------+------------+
| core01_hwt | 2016-05-04 00:00:00 | 2016-05-04 01:00:00 |     10000 | APCP_01  | F001      | CF007      | CNT_FSA   |          8 |
| core01_hwt | 2016-05-04 00:00:00 | 2016-05-04 02:00:00 |     20000 | APCP_01  | F001      | CF000      | CNT_FSA   |         11 |
+------------+---------------------+---------------------+-----------+----------+-----------+------------+-----------+------------+
2 rows in set (0.00 sec)
and a new query
SELECT
model,
fcst_init,
fcst_valid,
fcst_lead,
fcst_var,
object_id,
object_cat,
'CNT_FSA' stat_name,
COUNT(object_id) stat_value
FROM
mode_header ,
mode_obj_single ,
mode_cts
WHERE
fcst_valid IN ('2016-05-04 01:00:00', '2016-05-04 02:00:00', '2016-05-04 03:00:00', '2016-05-04 04:00:00', '2016-05-04 05:00:00')
AND model IN ('core01_hwt')
AND fcst_lead IN ('10000', '20000', '30000')
AND fcst_var = 'APCP_01'
AND fcst_flag = 1
AND simple_flag = 1 AND mode_obj_single.mode_header_id = mode_header.mode_header_id
AND mode_cts.mode_header_id = mode_obj_single.mode_header_id
AND mode_cts.field = 'OBJECT'
GROUP BY
fcst_lead,
model , fcst_valid ,fcst_init ,fcst_var, object_id, object_cat;
returns 32 rows

The test use case 'series_mode_attr' is failed.
Old query:
SELECT
model,
fcst_init,
fcst_valid,
fcst_lead,
fcst_var,
HOUR(fcst_init) init_hour,
object_id,
object_cat,
'CNT_FCA' stat_name,
COUNT(object_id) stat_value
FROM
mode_header ,
mode_obj_single ,
mode_cts
WHERE
HOUR(fcst_init) IN ('12')
AND model IN ('AFWAOCv3.5.1_d01', 'NoahMPv3.5.1_d01')
AND fcst_lead IN ('90000', '120000', '210000', '330000')
AND  fcst_var = 'APCP_03'
AND fcst_flag = 1
AND simple_flag = 0  AND mode_obj_single.mode_header_id = mode_header.mode_header_id
AND mode_cts.mode_header_id = mode_obj_single.mode_header_id
AND mode_cts.field = 'OBJECT'
GROUP BY
fcst_lead,
model,
init_hour  , fcst_valid
Returns 23 rows
New query:
SELECT
model,
fcst_init,
fcst_valid,
fcst_lead,
fcst_var,
HOUR(fcst_init) init_hour,
object_id,
object_cat,
'CNT_FCA' stat_name,
COUNT(object_id) stat_value
FROM
mode_header ,
mode_obj_single ,
mode_cts
WHERE
HOUR(fcst_init) IN ('12')
AND model IN ('AFWAOCv3.5.1_d01', 'NoahMPv3.5.1_d01')
AND fcst_lead IN ('90000', '120000', '210000', '330000')
AND  fcst_var = 'APCP_03'
AND fcst_flag = 1
AND simple_flag = 0  AND mode_obj_single.mode_header_id = mode_header.mode_header_id
AND mode_cts.mode_header_id = mode_obj_single.mode_header_id
AND mode_cts.field = 'OBJECT'
GROUP BY
fcst_lead,
model,
init_hour  , fcst_valid  ,fcst_init  ,fcst_var, object_id, object_cat
Returns 236 rows

I am not sure that I have this database. Is it possible that I can get a backup of this data?

The queries from the second comment are generated for the test database.

I'm working on modifying queries for Hist, Roc and Reliability plots.
Mode and mode-td queries are more complex and will be done for the next (v.3.0 ??) release

I understand a little more. Of course our server is not configured to allow the old query. Therefore I never saw the old results for the failing queries, just failure messages. I had captured new test results and the new test results, of course, passed. My understanding of the mysql group by clause was naive. It causes us to get extra results. I need to understand this further and see if there is a way to restrict the results in a way that the query can still be dynamically generated.

Fix was implemented for Hist, Roc and Reliability.
I will create a new issue for MODE and MODE-TD


Load checkpoint from Bytes [WIP]

What does this PR do?

Fixes # (issue)
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together? Otherwise, we ask you to create a separate PR for every change.
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests?
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @teddykoker! Thanks for updating this PR.

In the file pytorch_lightning/utilities/cloud_io.py:

Line 29:42: W291 trailing whitespace

cc @ananthsub


Fixed typos

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.337%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
920

Relevant Lines:
965

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 95.337%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
920

Relevant Lines:
965

💛  - Coveralls


Sample.eq errors

I recently discovered that equality comparison of two Samples via == could raise a ValueError when the Samples are of different sizes (in particular, if the sample_corrs and/or sample_errs are of a different size). E.g.:
import numpy as np
import pyddm
s1 = pyddm.Sample(sample_corr=np.array([0, 1]), sample_err=np.array([]))
s2 = pyddm.Sample(sample_corr=np.array([0, 1, 2]), sample_err=np.array([]))
s1 == s2

ValueError: operands could not be broadcast together with shapes (2,) (3,) `

This appears to be due to Sample.__eq__'s use of np.allclose() on the input arrays. If the arrays can be broadcast together, no error is raised; otherwise we get a ValueError.
Thinking more on this also made me wonder: is the equality operator for Samples invariant to array order? Currently it is not; i.e. we have:
s3 = pyddm.Sample(sample_corr=np.array([0, 1]), sample_err=np.array([]))
s4 = pyddm.Sample(sample_corr=np.array([1, 0]), sample_err=np.array([]))
s3 == s4

False

My prior assumption was that it should be, although perhaps I could be mistaken.

This was an interesting case where there was a test case for it but the test case had a bug which masked the bug in the code.  And you are correct, if the sort order is different, we call them different samples.  It is really hard to do sort orders in the correct way and there aren't very many use cases for this.


Adjust Alertmanager SAR to be more specific

This matches recent changes in prometheus[1] and grafana[2]

[1] https://github.com/infrawatch/service-telemetry-operator/pull/549/files#diff-2cf84bcf66f12393c86949ec0d3f16c473a650173d55549bb02556d23aa22bd2R46
[2] https://github.com/infrawatch/service-telemetry-operator/pull/550/files#diff-ae71801975adb4f8dd4aa5479a66ad46e46f17de40f9d147b2e09e13ce26633eR45

I'm abandoning this and will return with changes for both Alertmanager and SGs as well as adjustmens to the permissions of the prometheus-stf account to match.

@csibbitt can we delete the branch associated with this PR or do you plan to base off that branch for a future PR?


Make three windows more flexible

@s-katte I would like to work on this issue

Sure! I have assigned it you !


Collected API improvements

Collected API improvements while reviewing https://github.com/xamarin/xamarin-android/pull/89
Namespace should be Xamarin.Zip or Xamarin.Tools.Zip, not Xamarin.ZipSharp. A Sharp suffix adds nothing.
ZipArchive.NumberOfEntries should be named ZipArchive.EntryCount. Alternatively, maybe follow System.IO.Collections and have an Entries property of ICollection<ZipEntry> with a Count property.
ZipEntry.Name should be ZipEntry.FullName, a'la System.IO.Collections, if (I assume!) the value is the "full" name of an entry within the .zip file, e.g. foo/bar/baz.txt instead of just baz.txt.
ZipArchive.AddFile(string, CompressionMethod) should name the CompressionMethod parameter compressionMethod, not just method.

changed the namespace to Xamarin.Tools.Zip
renamed ZipArchive.NumberOfEntries to EntryCount. Using a collection of entries is wasteful (time and memory wise) as EntryCount simply calls a function in the native library that returns the number of entries read from the ZIP directory instead of iterating over all entries
renamed ZipEntry.Name to ZipEntry.FullName
renamed all the CompressionMethod method parameters to compressionMethod


Installing on Windows

I just installed some packages with paq-nvim on Windows. It seems to work so far. Could probably could do to add the following to the README for Windows users. Happy to open a PR if that's preferable.
Windows
git clone https://github.com/savq/paq-nvim.git "$env:LOCALAPPDATA\nvim-data\site\pack\paqs\opt\paq-nvim"

That's good to hear. I'll add it to the readme.
I'll also add a disclaimer indicating that there's currently no testing being done on Windows. libuv should take care of all the OS-dependent magic, but you never know…


How i connet more Accounts

Hey...
How i connect more than one Accounts of Bitfinex?
Need i installed a new Instance of Zenbot?
Thx

I would just spin up multiple zenbot docker containers.

Use PM2  process manager
You can then create a config file like this and call it anything and give it an extentions .yaml
so botz.yaml
Create as many of these bot configs you like in the file
  - script   : ./zenbot.js
    name     : 'bittrex.QTUM-BTC.RSI'
    watch  : true
    restart_delay : 30000
    args    : 'trade bittrex.QTUM-BTC --strategy=rsi --period=1m --min_periods=52 --rsi_periods=14 --oversold_rsi=28 --conf=config1.js'

you should be able to override any of the config options with the args field
Specify a different config file  with --conf=config1.js

I'm also interested on this, since I would like to run zenbot for maybe 10-15 different pairs. But just to be clear Nibzo1; what's the point with this PM2 process manager? Wouldn't it be easiest just to open each zenbot instance running on own terminal window?

To extend on @nibzo1

Create a file name pm2-zenbot1.yml
script   : ./zenbot.js name     : 'gdax.ETH-USD' watch  : true restart_delay : 30000 args    : 'trade --paper'

To start instance with pm2 run from shell:

pm2 start pm2-zenbot1.yml

To confirm process is running:

pm2 status pm2-zenbot1.yml

Dear issue reporter,
We have slightly changed our github issue policy and would now kindly request folks that have questions that they ask them in our zenbot subreddit.
You can find it here: https://reddit.com/r/zenbot
This issue will be closed, but if you disagree with your ticket being marked as a question feel free to leave a comment defending your case.
Thanks for contributing time and effort!
Greetings,
🤖


cleanup BearerException

it should also support other errors than just invalid_token, also insufficient_scope and invalid_request.

it is gone now, so that's solved ;-)


Addition of Sort Array by Parity in Java

🚀 Feature
Addition of Sort Array by Parity in Java
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
It is very famous technique. It is used in questions like -> sort01, sort012, sort by parity
Pitch
(Please explain why this feature should be implemented and how it would be used.)

/assign


Added Portuguese European (pt_PT) translation

Added Portuguese European (pt_PT) translation file to assets/i18n and also edited lib/src/supported_locales.dart to include new pt_PT locale

I've managed to build from my fork and everything is showing perfect in Portuguese :)

Thank you very much for the detailed pull request! I will be releasing a new version later today with that PR included.


Better German translation for Loading/loaded. Maybe it should be even…

… more elaborately like "Apps currently loading data" and "Apps recently loading data"?

find it a bit long...
I don't know is it only apps
and is it only loading (not uploading)
users knows what Loading is for
If I had to do a change it would be a more unusual name, go find "loading" app on the net, billions of sites
Something like "WhoIsLoading(.app)"... hum not terrible "whois", well you get the idea.

+1 for this PR! Right now, the translation is completely unintuitive. Looking up 4a0bbf1 made me understand what "Geladen" is supposed to mean.
I even find the English wording quite confusing. Can you explain the difference between the two sections in the dropdown menu?

Loading -> apps that are using the network right now
Loaded -> apps that used the network recently
I'm going to start merging the translations now, then I'll merge some fixes and release 1.1.1.

People who download Loading App knows why...
so Loading and Loaded menu headings are ok.
In French, I made them "shorter" without even mentionning it is a "load" process.
+"LOADING" = "En cours";   ~running/active, just like in Apple Monitor Utility
+"LOADED" = "Récemment"; ~recent those who where running recently

I'm going to start merging the translations now, then I'll merge some fixes and release 1.1.1.

Great!

Loading -> apps that are using the network right now
Loaded -> apps that used the network recently

I think "Right now" and "Recently" would really be a better wording.

People who download Loading App knows why...

No. I'm one of those who read the readme, downloaded the app and still didn't exactly know what the two categories are. So I think changing the English wording as well would be a good thing.

@derhuerst I propose the same in French "Right now" and "Recently" so we agree :-)
Be careful not downloading viruses ;-)

+1 for the need of a better German translation (I actually had opened another pull request to the same effect)
I think "Loading" for active apps would still be okay and understandable in German, if one wanted to keep the connection to the name Loading, but "Geladen" means something different ("these files/apps have been downloaded"), so that needs to be changed to be understandable IMHO. I would prefer this translation here, both "Aktiv" and "Kürzlich", though.

We can do "Aktiv" and "Kürzlich". I'll merge it in the next version tho, getting 1.2.1 out the door right now.

Sorry for delaying this one, there were a ton of German translations offered and they all had different solutions for how to translate things, so I made it a lower priority than the other ones. I'll look into it next.