Automated cleanup of Commands and Requests?

See: http://backbonejs.org/#Events-listenTo
In the case of Backbone's eventing system, listeners are registered on objects and cleaned up automatically on destruction. Such a feature would be a really nice addition to Backbone.Radio, removing the work involved in managing clean-up of every registered event, command, and request handler.
For example, in a view that needs to exchange information with a flash player:
var SomeView = Backbone.View.extend({
  initialize: function() {
    var flashChannel = Backbone.Radio.channel('flash');

    this.listenTo(flashChannel, 'tick', this.onTick);
    this.comply(flashChannel, 'play', this.play);
    this.reply(flashChannel, 'currentTime', this.currentTime);
  },
  onTick: ...
  play: ...
  currentTime: ...
});

If it simplifies matters, perhaps when needing to hand a channel in as an argument the functions can be given new names that indicate the intention to register them for later destruction - complyWith and replyTo, to go along with listenTo.
Lastly, we could wrap the remove function to include stopComplying and stopReplying functions, in addition to stopListening.
Thoughts?

Looks like I'm late to this discussion, but fwiw it seems to me that the 'off' equivalents should have 'off' in the name. e.g.
once => replyOnce / complyOnce
off => replyOff / complyOff

but maybe that ship has sailed if people are already using stopReplying / stopComplying..

@pascalpp, thanks for the suggestion! When we were figuring out the API, we definitely thought about trying to stay as closely as possible to Backbone.Events. One thing that bugged me about using the same exact verbs is that it makes the method names mean nothing taken out of context. If you remove Backbone.Events, and think about the Commands API in isolation, complyOff reads awkwardly to me. stopComplying, on the other hand, is correct grammar. A similar case can be made for the preposition to use for the listenTo equivalents. In some situations, though, it's even worse than reading awkwardly. Such an API can actively obscure what the method does, I think. Consider replyTo. That could just as easily be the method name for the 'regular' API, I think, where an object is responding to an event on itself. To me, replyFor communicates more clearly the fact that some obj is replying for some other target.
Although the naming of the methods is different, the current API is consistent with Events in behavior. Once the PR that solves this problem lands, each Events method will have an analogous method in Commands and Requests. This is a good thing, because all three systems are fairly similar. But if you were to compare the 3 against each other, Requests and Commands make sense to pair togetehr (for more: #186). Events has many differences when compared against those two systems. So it's a delightful consequence that by selecting an API that reads well, it also encodes this natural pairing, even if it is by chance.
There are definitely trade offs with either decision, to be sure, but I'm pleased with the API we've settled on. If you're unconvinced, then we should continue talking! Maybe you're onto something that I'm not picking up on.

@jmeas that makes sense. you're right that it's not good to force things to use the same semantics when the behavior under the hood is different.

What is the status of this feature? I am looking forward to using it :)

WIP. The implementation in #157 needs to be rewritten 'cause of mem leaks and other bugs in Backbone's original implementation of listenTo.

If anyone wants to try their hand @ this, you can find the new listenTo implementation in Backbone's 1.2 branch, and semi-complete unit tests in #157. I doubt I'll have time to do it anytime soon.

I don't use Radio much these days, so I'm still open to PRs!


Update AboutUs

Update AboutUs.md to include my photo and current role (#47).
Add my photo in doc/images/jordanchua.png.
Add my skeletal PPP in docs/team/jordanchua.md (#49).

Codecov Report
Base: 72.15% // Head: 72.15% // No change to project coverage :thumbsup:

Coverage data is based on head (e770146) compared to base (a4dd5f0).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master      #57   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

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

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

Your PNG filename is jordanchua.png.png, please rename it 😄

Updated 👍

You should rename the image instead of the link at AboutUs 😆

Sorry boss i updated it


weblink doesn't support templates

The weblink component doesn't work with template values.  Templated values are never expanded into the URL, so only static URL's are supported.  If templated values were supported, HA could be used to perform RESTful calls.  I'm trying to open maps on GPS coordinates which HA has, but there is no way to construct a valid URL to open the maps app on the phone with.

Could you provide an example yaml?

This is a feature-request rather than a bug though ;)

I see what you mean about features, I guess I was surprised templates didn't work and just assumed they were meant to.
Here is an example.  I have an electric car that reports in location via GPS coordinates.  I'd like to put that in a weblink so I can click on it and see where the car is:
weblink:
entities:
- name: Nissan LEAF
url: https://maps.apple.com/?ll={{ states.sensor.ev_latitude.state }},{{ states.sensor.ev_longitude.state }}&q=LEAF
icon: mdi:car-hatchback
produces the weblink:
https://maps.apple.com/?ll={{ states.sensor.ev_latitude.state }},{{ states.sensor.ev_longitude.state }}&q=LEAF

We should no longer add anything to weblink. Things should move to Lovelace, which already has a card to show a map for devices. https://home-assistant-lovelace-gallery.netlify.com/#demo-hui-map-card


Add a ‘success’ or ‘valid’ class to an input once it has validated

There is an error class, but no corresponding success class. This would be very useful for styling fields that have been correctly filled out.

Is this in development? Any indication when this might get released?

@cferdinandi It would be great.
You already add aria-invalid="true", so aria-invalid="false" after removing error would be great or  a class is-valid.

Hello, I just saw this and other request for enhancements, I think I can easily implement 2 or 3 enhancements as I already did for @cferdinandi validate.js, the thing is i see multiple stall pull requests, are there any guidelines for contribution @cferdinandi ? thanks in advance for your response, and thanks for creating this amazing library

Came here to find out about this - did anyone end up implementing it?


ISSUE: Sensors failing during setup

Describe the bug
The integration now fails to setup sensors. The mail gif does work though. I haven't changed anything that I know of.
Environment (please complete the following information):

OS: MacOS 11.2
Type of device: Mac mini
Home Assistant version: core-2021.2.1
Hassio/Docker/Core: Core
Component version: 0.2.3

Logs
Error while setting up mail_and_packages platform for sensor
Traceback (most recent call last):
File "/Users/homeassistant/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity_platform.py", line 198, in _async_setup_platform
await asyncio.shield(task)
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 74, in async_setup_entry
sensors.append(PackagesSensor(data, variable, unique_id))
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 216, in init
self.update()
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 270, in update
self.data.update()
File "/Users/homeassistant/homeassistant/lib/python3.9/site-packages/homeassistant/util/init.py", line 285, in wrapper
result = method(*args, **kwargs)
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 133, in update
self.fetch(account, data, sensor)
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 158, in fetch
count[sensor] = get_items(account, ATTR_COUNT, self._amazon_fwds)
File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 1007, in get_items
dateobj = datetime.datetime.strptime(arrive_date, "%A, %B %d")
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/_strptime.py", line 568, in _strptime_datetime
tt, fraction, gmtoff_fraction = _strptime(data_string, format)
File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/_strptime.py", line 352, in _strptime
raise ValueError("unconverted data remains: %s" %
ValueError: unconverted data remains: ,
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
I haven't personally changed anything that I know of. It stopped working out of the blue.

I am experiencing this issue as well, on 0.3.0-b41.
Completely clean install, I installed HASS just for this module.

Logger: custom_components.mail_and_packages
Source: custom_components/mail_and_packages/helpers.py:124
Integration: Mail and Packages (documentation, issues)
First occurred: 4:24:10 PM (1 occurrences)
Last logged: 4:24:10 PM
Unexpected error fetching Mail and Packages (smtp.gmail.com) data: [Errno 2] No such file or directory: '/config/www/mail_and_packages/'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 149, in async_refresh
self.data = await self._async_update_data()
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 137, in _async_update_data
return await self.update_method()
File "/config/custom_components/mail_and_packages/init.py", line 64, in async_update_data
return await hass.async_add_executor_job(process_emails, hass, config)
File "/usr/local/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/config/custom_components/mail_and_packages/helpers.py", line 98, in process_emails
image_name = image_file_name(hass, config)
File "/config/custom_components/mail_and_packages/helpers.py", line 124, in image_file_name
for file in os.listdir(path):
FileNotFoundError: [Errno 2] No such file or directory: '/config/www/mail_and_packages/'
Looks like it may not be checking to see if www exists.

What is the path to your configuration directory in your installation?

On mine, I am using docker, so /config.
adding the www directory fixed my issue. Now I just have beta issues.
I added /config/www/mail_and_packages/ and reloaded. All the sensors popped up.
Now I just need to figure out why I get 404s when pulling the image, but that is not an issue for this thread.

It should auto create the directory. I'll look into it.

Any idea on the original error that I'm getting?

dateobj = datetime.datetime.strptime(arrive_date, "%A, %B %d")

It sounds like the email has an unexpected date format.
Should be something like "today/tomorrow,Friday Month Day" and that format isn't what's being seen.

Oh sorry, this is 0.2.3.
Try the 0.3.0 latest beta, should work fine there.

Installed the latest beta, deleted the integration and redid it and I'm getting the same error, as well as a new one:
Logger: homeassistant.components.sensor
Source: custom_components/mail_and_packages/sensor.py:130
Integration: Sensor (documentation, issues)
First occurred: 3:36:45 PM (4 occurrences)
Last logged: 3:41:23 PM
Error while setting up mail_and_packages platform for sensor
Traceback (most recent call last):
  File "/Users/homeassistant/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/entity_platform.py", line 198, in _async_setup_platform
    await asyncio.shield(task)
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 28, in async_setup_entry
    sensors.append(ImagePathSensors(hass, entry, variable, coordinator, unique_id))
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/sensor.py", line 130, in __init__
    self._image = self.coordinator.data[const.ATTR_IMAGE_NAME]
TypeError: 'NoneType' object is not subscriptable

Odd the latest beta was done to fix that error. I'll take a look.

Looks like a leftover variable I didn't clean up, I'll drop a new beta that should fix that up.

Awesome. Thanks.

Both issues should have been addressed in the latest betas. Let me know how it goes.

That fixed it. Thanks so much!

I'm getting this error again on the latest beta:
Logger: custom_components.mail_and_packages
Source: custom_components/mail_and_packages/helpers.py:971
Integration: Mail and Packages (documentation, issues)
First occurred: 3:58:24 PM (1 occurrences)
Last logged: 3:58:24 PM

Unexpected error fetching Mail and Packages (mail.1008n3rd.com) data: unconverted data remains: ,
Traceback (most recent call last):
  File "/Users/homeassistant/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/update_coordinator.py", line 151, in async_refresh
    self.data = await self._async_update_data()
  File "/Users/homeassistant/homeassistant/lib/python3.9/site-packages/homeassistant/helpers/update_coordinator.py", line 139, in _async_update_data
    return await self.update_method()
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/__init__.py", line 78, in async_update_data
    return await hass.async_add_executor_job(process_emails, hass, config)
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/concurrent/futures/thread.py", line 52, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/helpers.py", line 128, in process_emails
    fetch(hass, config, account, data, sensor)
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/helpers.py", line 229, in fetch
    count[sensor] = get_items(account, const.ATTR_COUNT, amazon_fwds)
  File "/Users/homeassistant/.homeassistant/custom_components/mail_and_packages/helpers.py", line 971, in get_items
    dateobj = datetime.datetime.strptime(
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/_strptime.py", line 568, in _strptime_datetime
    tt, fraction, gmtoff_fraction = _strptime(data_string, format)
  File "/Library/Frameworks/Python.framework/Versions/3.9/lib/python3.9/_strptime.py", line 352, in _strptime
    raise ValueError("unconverted data remains: %s" %
ValueError: unconverted data remains: ,


Add end2end part to make it accessible to more users

I left the file paths in, so you can use the same files on the server @nictru.
We have to discuss somethings in our next meeting (e.g. no apptainer for chipseq, good testing data, non default parameters).

LGTM so far


home

create an home page where we explain:

[ ] why we do that
[ ] how to upload a file
[ ] summary of no-copyright-stealing
[ ] News
[ ] new uploaded files
[ ] RSS

see #16


sampleTerrainMostDetailed

Used SampleTerrainMostDetailed method, and removed "level" argument from the exported modules

Should also fix the test file. Note that the second test with invalid level will not be necessary.

Thanks for doing this @baloola!

You're welcome. I found this repo while I was looking for solution for  LoadWithXhr for node. I'm working on a similar tool that works with raster data instead of Geojson. it is currently slow (90 mins for 500MB dataset). But I think it would eventually work.


Update sample data and examples

https://docs.influxdata.com/influxdb/v1.7/query_language/data_download/
Dates on this data are from 2015--we need to update the attachment and also the examples throughout the docs to be more current.

Closing -- file on AWS updated to 2019 timestamps


[1993, 1999, 2003] Upgrade Kubescape to v3.0.8 and fix affected tests

Related issues

#1993
#1999
#2003

Description
(#1993) Kubescape version check

Kubescape version is now checked and the tool+framework is redownloaded if the version does not match.
Avoiding parsing version from the kubescape version command. Don't prefer to maintain a parser for it in the testsuite. We just write the version to a plain text file and check against that.

(#1999) resource_policies

The Resource Policies control has been split in the Kubescape NSA framework.
The test has been split in the testsuite accordingly as cpu_limits and memory_limits tests.
The automated test have also been updated appropriately.
These new tests have been updated in points.yml and rationale doc and the usage doc.

(#1999) hostpath_mounts

This control has been removed from the Kubescape NSA framework, but is a still part of the armosec/regolibrary.
Updated test to run the control directly using the Control ID. We can discuss retaining/removing/replacing this test as a separate discussion.

(#2003) service_account_mapping
The automated spec for service_account_mapping was failing. Turns out that KubectlClient::WORKLOAD_RESOURCES in kubectl_client dependency, does not have ServiceAccount in the list of resources to identify.
The above findings mean that when the Kubescape module's helper functions are used to get the CNF's resources that failed a particular test, the service account is not included as part of CNF's resources.

An update has been made to kubectl_client repo (in the testsuite/2003 branch), to fix this issue.
A shard.override.yml file has also been temporarily added to this PR, to point to the updated dependency's branch.

(#1999) platform:control_plane_hardening
Updated test to use new control name in Kubescape NSA framework.
(#1999) platform:cluster_admin
Updated the name of the Kubescape control. This fixes the test.
(#1999) platform:exposed_dashboard removed

This test does not exist in the Kubescape NSA framework and also not in the armosec regolibrary.
Removed it from the testsuite too.

non_root_containers

Fixed non_root_containers spec by updating the sample used for the check.
Build with error. Screenshot below

(#1999) Other changes

Upgrades Kubescape version to v3.0.8 (latest)

Without this upgrade, linux_hardening test was throwing errors due to invalid rego syntax in the Kubescape control definition.

Added another option to kubescape scan command to force Kubescape to return v1 format JSON.

The Kubescape integration can be updated later as a part of another PR to read JSON v2 output from Kubescape.

Related PRs

https://github.com/cnf-testsuite/kubectl_client/pull/13

How has this been tested:

[x] Covered by existing integration testing
[x] Added integration testing to cover
[ ] Verified all A/C passes

[ ] develop
[ ] master
[ ] tag/other branch

[x] Test environment

[ ] Shared Packet K8s cluster
[ ] New Packet K8s cluster
[x] Kind cluster

[ ] Have not tested

Types of changes:

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Documentation update

Checklist:
Documentation

[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[ ] No updates required.

Code Review

[ ] Does the test handle fatal exceptions, ie. rescue block

Issue

[x] Tasks in issue are checked off

Identified an issue with service_account_mapping and reported here - https://github.com/cnti-testcatalog/testsuite/issues/2003
There is one other failure to look into (non_root_containers). Will take a look in a few hours.

Updates
The previous build passed - https://github.com/cnti-testcatalog/testsuite/actions/runs/8830493531
To move forward

I have merged the PR forkubectl_client - https://github.com/cnf-testsuite/kubectl_client/pull/13
Created a tagged release v1.0.6 for kubectl_client
Removed shard.override.yml from this PR
Updated shard.yml to use kubectl_client v1.0.6 and updated shard.lock

Next steps

I will wait for the build again.
I will also run the cert command for coredns on the pair machine to verify the changes.


2 RX 470s on ROCm 1.8 : OpenCL only sees single device

I have one GPU on PCI 3 slot, and one on PCI 2.
But clinfo only reports one device.
My understanding was that 1.8 removes the PCI 3 restriction.

Aaron,
We said this is the case only with Vega10 currently.  Fiji and Polaris right now still need PCIe Gen3 and PCIe Atomics, we looking into this


proxyconnect tcp: net/http: TLS handshake timeout

Output of helm version:
Client: &version.Version{SemVer:"v2.12.3", GitCommit:"eecf22f77df5f65c823aacd2dbd30ae6c65f186e", GitTreeState:"clean"}
Error: Get https://xxxxxxxxxxxxxxxx.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: proxyconnect tcp: net/http: TLS handshake timeout
Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:38:32Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.2", GitCommit:"bb9ffb1654d4a729bb4cec18ff088eacc153c239", GitTreeState:"clean", BuildDate:"2018-08-07T23:08:19Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud Provider/Platform (AKS, GKE, Minikube etc.):
AKS
Hi,
I have some difficulties using helm at the company. We are behind a proxy. We started with our own squid proxy and helm worked fine with the windows settings of http_proxy and https_proxy.
Our company switched from our own proxy to a service called zscaler. And now we get these TLS handshake timeout messages with helm, but kubectl works.
Error: Get https://xxxxxxxxxxxxxxxx.westeurope.azmk8s.io:443/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller: proxyconnect tcp: net/http: TLS handshake timeout
We have no idea what could go wrong and where the error message does come from. --debug does not bring any additional information.
And why is kubectl working and helm not?
It would be good to improve the logging and differ between own error messages and messages that come from other somewhere else (http client, ...)
Thanks for your help!
Best regards,
Andi

First I should notice that I have changed the path to the kubectl.exe from the above version, which was part of the docker desktop for windows to the newer version, which was installed by azure cli
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"windows/amd64"}
With the newer version at first place in the path, the same error happens.
After that change the IT appartment of my company has found a solution.
I used the https_proxy environment variable with https:// url to our proxy. This works for most of the tools we are using but not for helm or the newer kube. They seem to have some problems with the TLS handshake. We switched from https:// to a http:// url (e.g https_proxy=http://myproxy) and now everything works fine.

First I should notice that I have changed the path to the kubectl.exe from the above version, which was part of the docker desktop for windows to the newer version, which was installed by azure cli
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.3", GitCommit:"721bfa751924da8d1680787490c54b9179b1fed0", GitTreeState:"clean", BuildDate:"2019-02-01T20:08:12Z", GoVersion:"go1.11.5", Compiler:"gc", Platform:"windows/amd64"}
With the newer version at first place in the path, the same error happens.
After that change the IT appartment of my company has found a solution. I used the https_proxy environment variable with https:// url to our proxy. This works for most of the tools we are using but not for helm or the newer kube. They seem to have some problems with the TLS handshake. We switched from https:// to a http:// url (e.g https_proxy=http://myproxy) and now everything works fine.

Thanks!!!!!!!!!


Another gateway deployment with the same name pt143peertube1 already exists

Description
When deploying a Peertube instance with the same gateway name of the old Peertube instance, got this error
Another gateway deployment with the same name pt143peertube1 already exists
Steps to reproduce

Go to Playground
deploy a Peertube instance or any other solution with a gateway name
delete it
deploy another one with the same name

Logs/Alerts

Why does it say freeflow?

Why does it say freeflow?

Tried another solution called Freeflow, the screenshot from there

For k8s, is invalidating keys necessary too?
@AhmedHanafy725

#751 ready for review,

For k8s, is invalidating keys necessary too? @AhmedHanafy725

will open a new issue in case it is necessary

For k8s, is invalidating keys necessary too?

yes, but this can be done on the grid client.

Verified on devnet.
The issue was fixed and now when a solution is deleted and the user tries to deploy another one with the same name it works without any issues.
TF Playground _ Peertube.webm


Dashd crashes after upgrading to <IP_ADDRESS>

Describe the issue
Dashd crashes after upgrading to <IP_ADDRESS>
Started from data which worked well with <IP_ADDRESS>.
Downgraded to <IP_ADDRESS> and now it's working well again.
Can you reliably reproduce the issue?
If so, please list the steps to reproduce below:

Run <IP_ADDRESS>. (txindex=1)
stop
Run <IP_ADDRESS> and it crashes silently. no error mentioned.

Expected behaviour
Tell us what should happen
Dashd should run smoothly.
Actual behaviour
Dashd crashed.
What version of Dash Core are you using?
Compiled from tag v<IP_ADDRESS> (7d8eab2)
Previous version(v<IP_ADDRESS>) was also compiled from same system.
Machine specs:

OS: Ubuntu
CPU: 8
RAM: 32GB
Disk size: 15T
Disk Type (HD/SDD): SSD

Any extra information that might be useful in the debugging process.
Here's the debug.log from v<IP_ADDRESS>
2019-09-04 11:43:52 Dash Core version v<IP_ADDRESS>
2019-09-04 11:43:52 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-09-04 11:43:52 Assuming ancestors of block<PHONE_NUMBER>00001e09926bcf5fa4513d23e870a34f74e38200db99eb3f5b7a70 have valid signatures.
2019-09-04 11:43:52 Default data directory /home/ubuntu/.dashcore
2019-09-04 11:43:52 Using data directory /home/ubuntu/.dashcore
2019-09-04 11:43:52 Using config file /home/ubuntu/.dashcore/dash.conf
2019-09-04 11:43:52 Using at most 8 automatic connections (1048576 file descriptors available)
2019-09-04 11:43:52 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2019-09-04 11:43:52 Using 4 threads for script verification
2019-09-04 11:43:52 RenameThread: thread new name dash-scriptch
2019-09-04 11:43:52 RenameThread: thread new name dash-scriptch
2019-09-04 11:43:52 RenameThread: thread new name dash-scriptch
2019-09-04 11:43:52 RenameThread: thread new name dash-scheduler
2019-09-04 11:43:52 scheduler thread start
2019-09-04 11:43:52 Binding RPC on address <IP_ADDRESS> port 39998 failed.
2019-09-04 11:43:52 HTTP: creating work queue of depth 64
2019-09-04 11:43:52 Config options rpcuser and rpcpassword will soon be deprecated. Locally-run instances may remove rpcuser to use cookie-based auth, or may be replaced with rpcauth. Please see share/rpcuser for rpcauth auth generation.
2019-09-04 11:43:52 HTTP: starting 4 worker threads
2019-09-04 11:43:52 RenameThread: thread new name dash-http
2019-09-04 11:43:52 RenameThread: thread new name dash-httpworker
2019-09-04 11:43:52 RenameThread: thread new name dash-httpworker
2019-09-04 11:43:52 RenameThread: thread new name dash-httpworker
2019-09-04 11:43:52 RenameThread: thread new name dash-httpworker
2019-09-04 11:43:52 Creating backup of /home/ubuntu/.dashcore/wallet.dat -> /home/ubuntu/.dashcore/backups/wallet.dat.2019-09-04-11-43
2019-09-04 11:43:52 Old backup deleted: "/home/ubuntu/.dashcore/backups/wallet.dat.2019-04-19-20-02"
2019-09-04 11:43:52 init message: Verifying wallet...
2019-09-04 11:43:52 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-09-04 11:43:52 Using wallet wallet.dat
2019-09-04 11:43:52 CDBEnv::Open: LogDir=/home/ubuntu/.dashcore/database ErrorFile=/home/ubuntu/.dashcore/db.log
2019-09-04 11:44:01

Have you tried <IP_ADDRESS>?

Sure it is still crashing.
I downloaded v<IP_ADDRESS> binary to check whether compiling was the problem.
dashcore-<IP_ADDRESS>-i686-pc-linux-gnu.tar.gz
No luck still.
2019-12-24 12:48:43 Dash Core version v<IP_ADDRESS>
2019-12-24 12:48:43 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2019-12-24 12:48:43 Assuming ancestors of block<PHONE_NUMBER>00001e09926bcf5fa4513d23e870a34f74e38200db99eb3f5b7a70 have valid signatures.
2019-12-24 12:48:43 Default data directory /home/ubuntu/.dashcore
2019-12-24 12:48:43 Using data directory /home/ubuntu/.dashcore2
2019-12-24 12:48:43 Using config file /home/ubuntu/.dashcore2/dash.conf
2019-12-24 12:48:43 Using at most 125 automatic connections (1048576 file descriptors available)
2019-12-24 12:48:43 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2019-12-24 12:48:43 Using 4 threads for script verification
2019-12-24 12:48:43 RenameThread: thread new name dash-scriptch
2019-12-24 12:48:43 RenameThread: thread new name dash-scriptch
2019-12-24 12:48:43 RenameThread: thread new name dash-scriptch
2019-12-24 12:48:43 RenameThread: thread new name dash-scheduler
2019-12-24 12:48:43 scheduler thread start
2019-12-24 12:48:43 HTTP: creating work queue of depth 16
2019-12-24 12:48:43 No rpcpassword set - using random cookie authentication
2019-12-24 12:48:43 Generated RPC authentication cookie /home/ubuntu/.dashcore2/.cookie
2019-12-24 12:48:43 HTTP: starting 4 worker threads
2019-12-24 12:48:43 RenameThread: thread new name dash-http
2019-12-24 12:48:43 RenameThread: thread new name dash-httpworker
2019-12-24 12:48:43 RenameThread: thread new name dash-httpworker
2019-12-24 12:48:43 RenameThread: thread new name dash-httpworker
2019-12-24 12:48:43 RenameThread: thread new name dash-httpworker
2019-12-24 12:48:43 init message: Verifying wallet...
2019-12-24 12:48:43 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2019-12-24 12:48:43 Using wallet wallet.dat
2019-12-24 12:48:43 CDBEnv::Open: LogDir=/home/ubuntu/.dashcore2/database ErrorFile=/home/ubuntu/.dashcore2/db.log

I have <IP_ADDRESS> crashing during initial block download as well, I'll get to get a crashlog.

I could get it working by compiling again with different option.
./configure --disable-wallet

my previous compile parameter was
./configure --without-miniupnpc --with-incompatible-bdb

Closing as we are well past <IP_ADDRESS> and this issue doesn't affect us anymore. I'm sorry you had these problems. Please open a new issue if you have any more difficulties


#371 Wind Chill Calculator App

Issue : https://github.com/dubesar/Java-A-Z/issues/371

@rufatiani Please add a readme file to your project.

@rufatiani The image is not visible, something wrong. Plz check.

@rufatiani Correct the spelling of "Screenshoot" to "Screenshot"

@rufatiani Resize the image, it's a little big.

@rufatiani It's perfect now. Thank you so much for your valuable contribution. Happy Coding and Keep Contributing!

Give a star if you liked our repo.


the specified path does not lead to a valid tf executable

I am getting this "the specified path does not lead to a valid tf executable" error when I am trying to set path for TFVC. The given path has the tf.exe file but still I am getting the error
idea.log

@gaurangpatel6688 refer here for the solution which I faced too.

Unfortunately, we don't support the tf.exe (you're referring to the one from Visual Studio, I presume). Only tf.cmd from the https://github.com/Microsoft/team-explorer-everywhere is supported.


table.deduplicate(d)

Removes duplicate values from a table

Seems like a niche enough operation for filter + another table to handle tbh

Ehhh
table.uniques = function(t)
    local seen = {}
    t:filter(function(x)
        if seen:contains(x) then return false end
        seen:insert(x)
        return true
    end)
    return t
end

Although might need a different name such as table.deduplicate or table.dedup so we can have table.deduplicated or table.deduped for the copying variant.

Somewhat worth noting that now this can be emulated as followed on 0.10.0:
local t = { "foo", "foo", "bar" }
print(dumpvar(t:countvalues():keys())) -- { "foo", "bar" }

Although probably still worthwhile to have its own function.


Refactoring to support adding units to EMOS coefficients

Description
This PR amends the coefficients cube generated by EMOS, so that instead a cubelist is generated with a separate cube for each coefficient. Each cube can then have the appropriate units.
This PR:

Updates the example coefficients cube in create_coefficients_cube.rst to instead display a coefficients cubelist example.
In ensemble_calibration.py:

Replaced deprecated imp module with importlib.
Converted create_coefficients_cube into create_coefficients_cubelist.
Altered application of EMOS coefficients to use coefficients cubelist directly, rather than using an intermediate dictionary.

In order to perform constrained loading, following merging #1239, I needed to make an edit to create_constrained_inputcubelist_converter to support loading without the strict=True flag. This ensures that more than one cube can be found for a constraint, which is required here to support loading an unknown number of beta cubes.
Update apply_emos_coefficients.py CLI to take in a cubelist.
Update docstring in estimate_emos_coefficients.py
Update tests in test_apply_emos_coefficients.py. I've removed the test_wrong_forecast_coefficients test because now a failure will occur before reaching the "Invalid forecast" error message because of the different types expected by the CLI i.e. the input forecast is a cube but the coefficients are a cubelist. I've also removed the test_wrong_coefficients test because this error is now caught by the constrained loading.
Moved function to helper_functions.py (with minor edits) from test_ApplyEMOS.py for shared usage.
Minor edits to test_ApplyEMOS.py.
Minor edits to test_CalibratedForecastDistributionParameters.py to test a cubelist, rather than a cube.
Removed create_coefficients_cube function and replaced usage with the build_coefficients_cubelist function in  helper_functions.py. Added some simplifications to the testing and general updates to test for cubelists, rather than cubes.

Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 3
- Added 5

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  1
- improver_tests/calibration/ensemble_calibration/helper_functions.py  3
- improver/cli/apply_emos_coefficients.py  3
- improver/calibration/ensemble_calibration.py  2

Complexity decreasing per file
==============================
+ improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 3

Complexity increasing per file
==============================
- improver/calibration/ensemble_calibration.py  2
- improver_tests/calibration/ensemble_calibration/helper_functions.py  3
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  1

Complexity decreasing per file
==============================
+ improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 2

Complexity increasing per file
==============================
- improver/calibration/ensemble_calibration.py  2
- improver_tests/calibration/ensemble_calibration/helper_functions.py  3
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  1

Complexity decreasing per file
==============================
+ improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 3

Complexity increasing per file
==============================
- improver/calibration/ensemble_calibration.py  6
- improver_tests/calibration/ensemble_calibration/helper_functions.py  6

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -1
+ improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11
- improver/calibration/ensemble_calibration.py  1
- improver_tests/calibration/ensemble_calibration/helper_functions.py  1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 4

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -1
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -1
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -1
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -2
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -2
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -1
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -1
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -2
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -1
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  11

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -1
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -2
+ improver/cli/apply_emos_coefficients.py  -1

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1
- Added 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -2
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -2
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5
- improver_tests/calibration/ensemble_calibration/test_CalibratedForecastDistributionParameters.py  1
- improver_tests/calibration/ensemble_calibration/helper_functions.py  1

Complexity decreasing per file
==============================
+ improver/calibration/ensemble_calibration.py  -2
+ improver/cli/apply_emos_coefficients.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 2

Complexity increasing per file
==============================
- improver_tests/calibration/ensemble_calibration/test_CalibratedForecastDistributionParameters.py  1
- improver_tests/calibration/ensemble_calibration/test_ApplyEMOS.py  5
- improver_tests/calibration/ensemble_calibration/helper_functions.py  1

Complexity decreasing per file
==============================
+ improver/cli/apply_emos_coefficients.py  -2
+ improver/calibration/ensemble_calibration.py  -2

Clones added
============
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  9

See the complete overview on Codacy


AGCORDOVA-168 : set cdvMinSdkVersion to max between 16 and the androi…

…d-minSdkVersion preference

:+1:


refactor K8s docs for v21.2

Refactored the K8s documentation for v21.2 to cover db operator tasks in separate articles. This should be easier to update and maintain.
Included changes from #11206.
Also fixes #11109 for all three deployment methods, including some outdated parts in v21.1.

This change is

@udnay This is largely a restructure of the docs to make them more usable/navigable. There aren't really any content changes here, but let me know if you have thoughts on the organization.

@kathancox This is a large update that mostly restructures existing content. See my comment here: https://github.com/cockroachdb/docs/pull/11623#issuecomment-916990752

@keith-mcclellan Can you let me know if this commit https://github.com/cockroachdb/docs/pull/11623/commits/692e85ef35ae1217e75fdbbac62976374bccb65e does it for the EKS-A callout?


Upgrade kubernetes dependeny to fix CVE Warnings

Please update and release a new version of nats-operator which upgrades the kubernetes dependency.
From: https://github.com/kyma-project/kyma/pull/11244#issuecomment-857760868

Turns out nats-operator is using kubernetes 1.15.2 as a dependency and that is causing the security scan to fail in the >job as it is shown here:
"scan": {
"status": "Vulns",
"message": "There are some expired vulnerabilities",
"protecodeID": "579046"
}
The security issue with Kubernetes 1.15.2 is https://nvd.nist.gov/vuln/detail/CVE-2020-8558.

Thanks, will try to see if can fix tomorrow.

Sorry for the delay, a bit stuck figuring out this error updating the dependencies... Continue to investigate... Trying out with the go.mod from sample-controller: https://github.com/kubernetes/sample-controller/blob/master/go.mod
go<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>reading k8s.io/apiextensions-apiserver/go.mod at revision v0.0.0: unknown revision v0.0.0

I'm not knowing a lot about Go but seems like this adresses a similar issue https://github.com/kyma-project/kyma/pull/11920/files

Kubernetes dependencies are now at 1.22.2 as of https://github.com/nats-io/nats-operator/pull/336.
Closing for now.


MainMenu Config Improvements

Improve the MainMenu Interface for the facilitator. Correspond to get the improvements of the issue #5 .

Added instructions in left part, and change fields on right part.
Added a message on the left of start button when bad information is completed in input fields.
Now, check email field, adapt user and test field.

Some options was commented in code, but it was because issue #6 talk about check if right informations are sended in DB. For the interface, do not need it.
The new interface use layout to adapt at all screens. But some times, if you have not the same size of the mockup, the interface are not totally correspond to the mockup.

Hi Bastian!
I finished to do all modifications.
I changed commit names and descriptions. And I applied squash modifications.
You have to tell me about comments on my code at this commit 8d9297d. I am waiting your answer.
Futhermore, I am waiting your verification about commit changements.
Thanks 😉

This commit is making changes to all lines of code in LoggingManager, (removing everything and adding it again?). This might be caused by your IDE? If it is, I suggest that you drop those changes.

It is because I use automatic indentation in Visual Studio, and in this file, VS re-indent all the code. What I do?

I would like if your commit message includes explaining that A) the commit introduces new assets required for the main menu design in issue #10 , B) what the purpose of DestroyBlocker and HighlightText is (what they are used for, why you are introducing them).

I add this lines in the commit description :

Add all new assets and textures for the new design (picts and font-style)
Add scripts to control menu fields and dropdown. HighlightText.cs permits change the default value of any field by "Edit" when your mouse is inside. DestroyBlocker.cs is to destroy the blocker generate by the dropdown and this blocker creates a bug because it changes the size of dropdown when you open it.

Hey @bastianilso ! 🙉
I finish to change all commits to match with your rules. Can you check it and give me a feed back?
Thanks. 👌

OK!
I change all bugs for the font size, I add the same implementation of Whack A Mole project for int fields, and I rebase all commits to match with your last message.
So please, now it's good 🙏

:+1: good job @YoNeXia I have no further remarks. In case we find bugs or things need to change, we can revisit it later.


easyinstall.sh error

I was trying to install the precompiled minecraft server, MCServer, for raspberry pi using the following command from the user manual:
curl -s https://raw.githubusercontent.com/mc-server/MCServer/master/easyinstall.sh | sh

The easyinstall.sh script downloaded and ran but gave an error saying that the curl command had no URL specified.  I found that changing "arm*" to just arm* in the case statement in easyinstall.sh fixed it.
Original code:
...
case $PLATFORM in
        "i686") DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20x86/lastSuccessfulBuild/artifact/MCServer.tar" ;;
        "x86_64") DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20x64/lastSuccessfulBuild/artifact/MCServer.tar" ;;
        # Assume that all arm devices are a raspi for now.
        "arm*") DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20armhf/lastSuccessfulBuild/artifact/MCServer/MCServer.tar"
esac

Fixed code:
...
case $PLATFORM in
        "i686") DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20x86/lastSuccessfulBuild/artifact/MCServer.tar" ;;
        "x86_64") DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20x64/lastSuccessfulBuild/artifact/MCServer.tar" ;;
        # Assume that all arm devices are a raspi for now.
        arm*) DOWNLOADURL="http://builds.cuberite.org/job/MCServer%20Linux%20armhf/lastSuccessfulBuild/artifact/MCServer/MCServer.tar"
esac

I modified the original download command to download just the easyinstall.sh script as follows:
curl -s https://raw.githubusercontent.com/mc-server/MCServer/master/easyinstall.sh > easyinstall.sh

I then made the above edit to easyinstall.sh, made it executable using chmod, and ran it successfully.

Ok. Will fix. Bash is strange.

Thanks for the report BTW, it's good to see someone actually using my scripts.


RS Writer input mapping

Ignored tables are migrated to input mapping of new RS writer. That causes the writer to fail, because there could be more columns in the CSV in S3 then it is in the created DB table.

Fixed in https://github.com/keboola/config-migration-tool/commit/f69dec59e884b6f4d53cbdc9aa3dda48c1b863cb


Problem during training

I having an error when I run train.py with pretrained CIA-SSD  model. Any help would be greatly appreciated! Also, any tips on using this model on a custom dataset with 16 channel lidar data.

@badalpardhi12 From above traceback, there is no points selected for concatenation, and you may check if the class_names are set correctly.  Also, it' easy to change the input lidar data from current 4 channels to 16 channels, you may do it in the config file, but you have to check the data preprocessing files in pipeline carefully to avoid any possible inconsistency.


MacroPreprocessor: resolve Button type inputs

When calling a command from a macro (with an option string), we usually don't want to show a UI dialog.
If the called command contains inputs of type org.scijava.widget.Button, we resolve these without setting them, as we assume that buttons and their callbacks provide some interactivity that is not required when running from macro.
See the closed PR https://github.com/imagej/imagej-legacy/pull/239 for some discussion.

I would have liked to respect a required={false,true} annotation for the Button input, but since Button extends Optional, isRequired() will always resolve to false, see also:
https://github.com/scijava/scijava-common/blob/46ca0d04c5c86eeb51f9daa9f130b0d7c8decd65/src/main/java/org/scijava/command/CommandModuleItem.java#L102-L106

I hope that this solution - while being a bit hacky - is less intrusive than #239, but still meets the requirements of the affected projects.
(/cc @frauzufall @NicoKiaru @tischi @romainGuiet @uschmidt83 @tferr)
Note 1: While in full-fledged scripting languages, you can always call commandService.run("command",false, ...) to avoid the automatic command preprocessing (and hence display of dialogs), this option doesn't exist in an IJ1 macro run("...") call.
Note 2: This pull request still allows commands whose dialog box is nothing else than a button to show a dialog box when invoked from the UI (scenario 1 in this comment by @ctrueden).
Note 3: I tried to add a test for this behavior in https://github.com/imagej/imagej-legacy/commit/401cb9c85dc53646c4f8faced35a08d42d75bf4e, but it's not headless, as it seems this issue only occurs when running from a macro with the UI displayed. In addition, we still cannot distinguish between macro calls with and without option string (run("Test Command") vs. run("Test Command", ""), see also https://github.com/scijava/scijava-common/issues/317#issuecomment-364458528).

See https://github.com/imagej/imagej-legacy/pull/239#issuecomment-1125729713, thanks @biovoxxel for testing!
@hinerm @ctrueden is there any chance we can get this merged and released soon?


Advance Forms

It would be great if we can add support for the follwing form types:
Switch
Range
Textfield
Switches
Additional context

@derron1 we already have:

Switch/Toggle
Slider/Range

The TextArea is missing but we can provide it in the next minor version.

@derron1 we already have:
* [Switch/Toggle](https://vuesion.herokuapp.com/storybook/?path=/story/atoms-toggle--default)

* [Slider/Range](https://vuesion.herokuapp.com/storybook/?path=/story/atoms-slider--range)

The TextArea is missing but we can provide it in the next minor version.

oh appologise ..If we can get Text area in on the next minor version thats great..

Could we also add a input dropdown form

@derron1 do you mean the select component?
In addition there is a dropdown menu and an auto complete.

Yes I was reffering to the  select component sorry I didnt see it..Is there any resson why the styling is completly different to the defualt input.
I was checking the design system for something similar to this!!

The reason is that I prefer native components over fancy ones. They have less code, are accessible and work on every device.
If you want the material design system I recommend you to use vuetify.


My creator credits...

Hello ..., it would be nice if you give me my credits as creator of the dashboard ... =)
I created this dashboard in 2018 ..., If you want to see the latest version 4.0 PREMIUM (up to 100% faster and improved) you can access: http://kofficepanel.com
Or contact me on WhatsApp: +55 48 996377413

You don't have proof of that. Also we don't recommend any solution that isn't self hosted.
If anyone ends up here. Don't trust this guy

Downloading my project, translating it into english and still sending it to github is a bit uneducated ...
I am the only person who actually has the source code for this old version (without being decrypted)
you can clearly see the difference between the decompiled code and my original code.


\bar doesn't always have correct italic correction

Describe the bug:
Stacking accents such as \bar{\bar{...}} does not do the proper italic correction on the outer accent. This was originally reported on StackOverflow.
To Reproduce:
Steps to reproduce the behavior:

Go to https://katex.org
Enter \bar{\bar{X}}

Expected behavior:
LaTeX produces the following:

Screenshots:
KaTeX produces the following:

Environment (please complete the following information):

KaTeX Version: 0.13.11
Device: Desktop
OS: Windows 10
Browser: Chrome
Version: 91

Additional context:
A workaround is to use \overline. \overline{\overline{X}} renders as

I suspect the root cause is the same here as #1821.

Oops, indeed. I totally forgot about that issue, despite having commented there. 🙂 I'll merge this into #1821 then.


NIFI-7203 Add ZooKeeper client and server TLS

Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

[ ] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[ ] Have you written or updated unit tests to verify your changes?
[ ] Have you verified that the full build is successful on both JDK 8 and JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

@jfrazee Is this PR related to/duplicative/complimentary to https://github.com/apache/nifi/pull/4202?

@joewitt Both? I had just finished up the work but with the addition of the client implementation and server tests which hadn't existed previously. Thought I'd throw it up because the tests and client piece would be additive.

@jfrazee as I mentioned on NIFI-7203, during an offline discussion some of us were discussing the approach to a configuration for an embedded ZK instance in NiFi which defines both an HTTP and HTTPS connection. Our position is that unlike an external ZK cluster which may have many different clients, the embedded ZK instance should only listen on the HTTPS port if the admin configures that, as NiFi will only attempt to connect on that port, and listening on HTTP has the potential to expose sensitive information. However, this is different from normal ZK behavior and therefore we listed some potential approaches to reduce confusion. More details are available in this comment, but I would like to hear your perspective on this. Have you encountered any scenarios where an admin intentionally meant for the embedded ZK to listen on both ports?

@alopresto If it's either-or I think the most important thing is to validate and throw an error so the behavior doesn't end up being confusing if both are set and the insecure clientPort is ignored. I wouldn't want it to be just a documented behavior.
There is one situation where having both set is useful -- the API for the status commands don't support TLS, but I think this is in the process of being addressed on the ZK side so it should eventually work itself out.
I'll make some notes over in the NIFI-7203 JIRA.

Closing this in favor of the work in #4250, #4216, and #7372.


Get actual Last Run Result from Get-ScheduledTaskInfo

`Get-ScheduledTaskInfo -TaskName '\FilmCab\file maintenance\back_up_unbackedup_published_media'|Select *
LastTaskResult = 267009, 0x41301: Task is currently running
???? 0x41303: The task has not yet run
NumberOfMissedRuns: 0
LastRunTime is 2/11/2024 1:34:34, but GUI shows 1:34:06!`
Use this in header to get more things like "The Task is currently running" which the Event log doesn't actually say, only that the action started.

I think it's working.


As you are aware, spamming people by scraping their email address and other contact info from GitHub is a violation of the GitHub ToS that can result in getting your account banned.
https://docs.github.com/en/site-policy/github-terms/github-terms-of-service
I never gave you or your any company permission to contact me.
Screenshot of spam contact:

Great way to ruin a project that might otherwise have been interesting.

@Malfrador It is standard practice to report to GitHub directly and post an issue for community visibility when this happens.  Some people also post to HN.
Holding companies accountable for sending spam is not "spam" itself, so please stop with that nonsense.
The GitHub ToS are very clear that this is not permitted.


How to change the "num_class" when using the pre-trained model?

❓ Questions and Help
I want to change the 'num_class' from 81 to 2 based on the pre-trained model. When I simply changed it in config file. I got the error info as followed:

Traceback (most recent call last):
File "", line 4, in
File "/hdd/zhanxinrui/.pycharm_helpers/pydev/_pydev_bundle/pydev_umd.py", line 197, in runfile
pydev_imports.execfile(filename, global_vars, local_vars)  # execute the script
File "/hdd/zhanxinrui/.pycharm_helpers/pydev/_pydev_imps/_pydev_execfile.py", line 18, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/tools/train_net.py", line 208, in
main()
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/tools/train_net.py", line 201, in main
model = train(cfg, args.local_rank, args.distributed)
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/tools/train_net.py", line 65, in train
extra_checkpoint_data = checkpointer.load(cfg.MODEL.WEIGHT)
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/maskrcnn_benchmark/utils/checkpoint.py", line 62, in load
self._load_model(checkpoint)
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/maskrcnn_benchmark/utils/checkpoint.py", line 100, in _load_model
load_state_dict(self.model, checkpoint.pop("model"))
File "/home/zhanxinrui/MOT/maskrcnn-benchmark/maskrcnn_benchmark/utils/model_serialization.py", line 80, in load_state_dict
model.load_state_dict(model_state_dict)
File "/home/zhanxinrui/anaconda/envs/mrcnn-benchmark/lib/python3.6/site-packages/torch/nn/modules/module.py", line 847, in load_state_dict
self.class.name, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for GeneralizedRCNN:
size mismatch for roi_heads.box.predictor.cls_score.weight: copying a param with shape torch.Size([81, 1024]) from checkpoint, the shape in current model is torch.Size([2, 1024]).
size mismatch for roi_heads.box.predictor.cls_score.bias: copying a param with shape torch.Size([81]) from checkpoint, the shape in current model is torch.Size([2]).
size mismatch for roi_heads.box.predictor.bbox_pred.weight: copying a param with shape torch.Size([324, 1024]) from checkpoint, the shape in current model is torch.Size([8, 1024]).
size mismatch for roi_heads.box.predictor.bbox_pred.bias: copying a param with shape torch.Size([324]) from checkpoint, the shape in current model is torch.Size([8]).
size mismatch for roi_heads.mask.predictor.mask_fcn_logits.weight: copying a param with shape torch.Size([81, 256, 1, 1]) from checkpoint, the shape in current model is torch.Size([2, 256, 1, 1]).
size mismatch for roi_heads.mask.predictor.mask_fcn_logits.bias: copying a param with shape torch.Size([81]) from checkpoint, the shape in current model is torch.Size([2]).

I guess I should remove pre-trained predictor weights or not load these weights. But how am I suppose to do this easily,  Can you give me some tips?

https://github.com/facebookresearch/maskrcnn-benchmark/issues/521

#Load the model in python
import torch
model = torch.load("coco_base_pretrained.pth")
#Remove the previous training parameters.
#del model['iteration']
#del model['scheduler']
#del model['optimizer']
#Remove the output layers in COCO, these are the mismatched layers you saw.
#Second stage prediction//删除两次
#del model["model"]["module.roi_heads.box.predictor.cls_score.weight"]
#del model["model"]["module.roi_heads.box.predictor.cls_score.bias"]
#del model["model"]["roi_heads.box.predictor.bbox_pred.weight"]
#del model["model"]["roi_heads.box.predictor.bbox_pred.bias"]
#mask prediction
#del model["model"]["roi_heads.mask.predictor.mask_fcn_logits.weight"]
#del model["model"]["roi_heads.mask.predictor.mask_fcn_logits.bias"]
#RPN
#del model["model"]["rpn.head.cls_logits.weight"]
#del model["model"]["rpn.head.cls_logits.bias"]
#del model["model"]["rpn.head.bbox_pred.weight"]
#del model["model"]["rpn.head.bbox_pred.bias"]
#save the model
torch.save(model, "coco_base_pretrained.pth")
把每行最前面的＃去掉，pth更换成预训练的模型，删除相应不匹配的层。


Add option to limit the amount of sounds playing at the same time

I mapped some sounds to CursorMove so when I hold down, I get blasted by 50 sounds playing all at the same time.
This should also just limit processes spawned when using more heavyweight players in the future (mpv?).
The implementation is hacky, as I don't know how "global" the global variable is, but it works™
Thank you a lot btw for this plugin, I find it very fun :D
Edit: I apparently fucked up my branch name and called it max_options?? I meant max_sounds lol

Thanks again!


jest --changedSince=blablabla crashes

🐛 Bug Report
Running jest --changedSince=blablabla (as long as blablabla is not a branch/tag/commit (anything that's not a valid reference)) crashes with an unhandled rejection.
To Reproduce
Steps to reproduce the behavior:
jest --changedSince=some-bad-revision
Expected behavior
A clean error saying that the reference was impossible to resolve, or something. Probably just show the error from git is best
Link to repl or repo (highly encouraged)
N/A, can be reproduced in any repo with VCS (including the jest repo itself).
Run npx envinfo --preset jest
Paste the results here:
Environment:
  OS: macOS High Sierra 10.13.6
  Node: 8.11.1
  Yarn: 1.9.4
  npm: 6.4.1
  Watchman: 4.9.0
  Xcode: Xcode 9.1 Build version 9B55
  Android Studio: EAP AI-145.3111935 AI-145.3111935

Is it ok if I try my hands on this?

@Keraito go for it!

@Keraito are you still working on this? Mind if I take a look?

For whoever is picking this issue up, Id recommend handling both scenarios where a user uses git and when a user uses mercurial.

Sorry @SimenB @rogeliog, suddenly couldn't quite find the time to work on this, so @khuyn003 go ahead.

When running command npm test -- --changedSince refs/heads/develop I got
(node:29084) UnhandledPromiseRejectionWarning: 128: fatal: bad revision '^refs/heads/develop'

Is the string refs/heads/develop invalid branch reference?

Please open up a separate issue with reproduction steps


4 companies added

Was going to add just Freeagent but also added, Crew, MetaLab, and YouCanBookMe

Oh no! There seems to be some conflicts now :( mind resolving?

Closing for now. Feel free to reopen if you're able to resolve them! Thanks :)


youtube-dl-gui: Update to version 1.8.4, and fix checkver

Closes #9748

[x] I have read the Contributing Guide.

/verify


Add Fable.Import.Test.fsproj to build

all the errors are unrelated and already there. what do we do?

That's because this breaking change: #279. Let me finish v0.5.0, update the bindings and the samples and then we can merge the PR :+1:

cool. just let me know if I have to do something.

New version is about to be released, so let's start fixing these things :+1:


fix: special case NaN in setter

I suppose there is a bug in setter about ‘NaN’ special case.

would you mind adding a unit test to demonstrate the problem solved by this change?

would you mind adding a unit test to demonstrate the problem solved by this change?

Thanks for replay,  the unit test has been added.

Hi, @Rayzhangzhang this PR cause 8 test failures. thx


chore(cli): update all usages and examples

Fixes #1163
This updates all command usages, examples, etc. to use the same syntax, which matches the syntax used for kubectl commands.
In addition, where applicable various variations of command options have been documented in places where a command works with a series of options.

Apart from the esoteric grammar things, this is perfect.


seek waits for a while before pausing and update the position stream

Describe the bug
the seek doesnt pause the video,
i seek (outside of the buffered range)
the video keeps playing
then it decides to seek and buffer
and that delay is random
Expected behavior
seek the video pauses until it gets buffered in the seeked position
Log
Add
import 'package:logging/logging.dart';
import 'package:intl/intl.dart';

add the following lines before registerWith()
  Logger.root.level = Level.ALL;
  final df = DateFormat("HH:mm:ss.SSS");
  Logger.root.onRecord.listen((record) {
    print('${record.loggerName}.${record.level.name}: ${df.format(record.time)}: ${record.message}');
  });

Logs:
https://justpaste.it/hpf7r

same as #160 i guess

So it's a bug in mdk?

yes

I would love to help with it but I don't know how, so I will most probably wait 😢


exists validation issue

Laravel Version: 7.12.0
PHP Version: 7.4.2
Database Driver & Version: dosn't matter

Description:
When we use exists validation like below :
'post_id' => ['required', Rule::exists('posts', 'id')->whereNull('deleted_at')],
if we pass any string after correct id , like : 2foo , input is valid and laravel dosn't throw validation exception

That generally seems to be MySQL behavior: select * from users where id = '1foo'
Will return a user with an ID of 1. Try adding the integer validation rule.


fix: #1872 Chang the type of createLocalVue method

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

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

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

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch.
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue-test-utils/blob/dev/.github/CONTRIBUTING.md#development-setup
[ ] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

@lmiller1990
Thank you for the review.
Can you tell me about when it will be released?

I can do a release this weekend 👍
Please tag me if it is not released by Monday (19th July).

@lmiller1990
Hello, This is a reminder for the release of this pull request.

@coolboy0961 I have release 1.2.2: https://github.com/vuejs/vue-test-utils/releases/tag/v1.2.2


 I was getting many issues that just said, "Doesn't work" or provided very little information. I'm not paid for this work and spending a good bit of time asking the same questions to get the info I need is not helpful. That being said, as long as you don't modify the template you can leave any area of it blank. You can always find me on discord or the forums and I am very willing to help.
This issue is worrying and I'd be interested if it is still an issue in the dev branch. If you haven't completely given up on it, you could give it a test an let me know how it works out for you.

Hi i know you are not paid and I love your work, I have used CCH for month
now, without any issues, then yesterday i changed all my sensor cards, if i
save 1 card it is okay but if i change several cards at once and save it is
fine, but after reload the lovelace file i suddenly back to an old version,
and I had to change every thing again. i just installed HACS and using cch
from there now, it was then all the problems started.
I dont know what to tell you
keep up the great work, and sorry for getting upset, it is just im not a
programmer so i got a little frustating, it happed 3 times in 2 days
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
13.34.48
Den man. 1. jul. 2019 kl. 13.26 skrev Ryan Meek<EMAIL_ADDRESS>
This is in place to make sure I get all the info I need. I was getting
many issues that just said, "Doesn't work" or provided very little
information. I'm not paid for this work and spending a good bit of time
asking the same questions to get the info I need is not helpful. That being
said, as long as you don't modify the template you can leave any area of it
blank. You can always find me on discord or the forums and I am very
willing to help.
This issue is worrying and I'd be interested if it is still an issue in
the dev branch. If you haven't completely given up on it, you could give it
a test an let me know how it works out for you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXRJHBPXLHMFAVKLGTP5HSVDA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY52JFY#issuecomment-507225239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSZO3KXXQIXJLIGALLP5HSVDANCNFSM4H4PIPRQ
.

I can understand the frustration, been there. I've released the changes in the dev branch to 1.1.9b1 which is a pre-release if you wanted to check it out. In HACS you need to make sure that you "Show Beta" on CCH.

I cant find where to enable Beta
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
14.12.52
Den man. 1. jul. 2019 kl. 13.53 skrev Ryan Meek<EMAIL_ADDRESS>
I can understand the frustration, been there. I've released the changes in
the dev branch to 1.1.9b1 which is a pre-release if you wanted to check it
out. In HACS you need to make sure that you "Show Beta" on CCH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXPBYLPGYVCGUPQPW3P5HV3XA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY54GYA#issuecomment-507233120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWUIZYS5U6UPRLULGNTP5HV3XANCNFSM4H4PIPRQ
.

The top right button on the HACS CCH page, click "Show Beta" then click "Reload". You should then see 1.1.9b1 as the "Available option"

found it, I will try it out, I really thank you for your time, pls leave a
link to paypal or something else where i can support you
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
14.15.25
Den man. 1. jul. 2019 kl. 14.13 skrev Dartfrog<EMAIL_ADDRESS>
I cant find where to enable Beta
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 01.07.19
14.12.52
Den man. 1. jul. 2019 kl. 13.53 skrev Ryan Meek<EMAIL_ADDRESS>
:

I can understand the frustration, been there. I've released the changes
in the dev branch to 1.1.9b1 which is a pre-release if you wanted to check
it out. In HACS you need to make sure that you "Show Beta" on CCH.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXPBYLPGYVCGUPQPW3P5HV3XA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY54GYA#issuecomment-507233120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWUIZYS5U6UPRLULGNTP5HV3XANCNFSM4H4PIPRQ
.

No compensation necessary, though I do appreciate the thought. If you feel like buying me a coffee you can do so from the link in the readme here:
https://github.com/maykar/compact-custom-header

I will play with it and see if it will do it again ;o) thanks I bought you
some coffee
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
14.26.46
Den man. 1. jul. 2019 kl. 14.21 skrev Ryan Meek<EMAIL_ADDRESS>
No compensation necessary, though I do appreciate the thought. If you feel
like buying me a coffee you can do so from the link in the readme here:
https://github.com/maykar/compact-custom-header
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWSGBWWO54UCXWQQYPDP5HZDZA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY56IOY#issuecomment-507241531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWVRORUJPWTPZOVSPL3P5HZDZANCNFSM4H4PIPRQ
.

Much appreciated, feel free to continue posting here with your findings.

I was able to reproduce the issue on my side and have implemented a fix in 1.1.9b2. Thanks for reporting it.

thank you i was begining to think i did something ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
16.25.12
Den man. 1. jul. 2019 kl. 16.15 skrev Ryan Meek<EMAIL_ADDRESS>
I was able to reproduce the issue on my side and have implemented a fix in
1.1.9b2. Thanks for reporting it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV4F37JKV3JTFGBQKLP5IGQFA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6IN3Y#issuecomment-507283183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSZQG4R55SVNV6TX6LP5IGQFANCNFSM4H4PIPRQ
.

but where does it get the old lovelace file from ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
16.25.56
Den man. 1. jul. 2019 kl. 16.25 skrev Dartfrog<EMAIL_ADDRESS>
thank you i was begining to think i did something ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 01.07.19
16.25.12
Den man. 1. jul. 2019 kl. 16.15 skrev Ryan Meek<EMAIL_ADDRESS>
:

I was able to reproduce the issue on my side and have implemented a fix
in 1.1.9b2. Thanks for reporting it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV4F37JKV3JTFGBQKLP5IGQFA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6IN3Y#issuecomment-507283183,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSZQG4R55SVNV6TX6LP5IGQFANCNFSM4H4PIPRQ
.

CCH was getting the config on load and wasn't updating it. So it used the config from first load of the page.

okay i will install the b2 when it arrives on hacs
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
16.29.37
Den man. 1. jul. 2019 kl. 16.28 skrev Ryan Meek<EMAIL_ADDRESS>
CCH was getting the config on load and wasn't updating it. So it used the
config from first load of the page.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV5CXJJQJFHQSXT7KDP5IH7TA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6JWTI#issuecomment-507288397,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWWRET22ZO5WI45E4XTP5IH7TANCNFSM4H4PIPRQ
.

In that top right button just hit "reload" and it should be there

i got it
it is installed
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
16.32.37
Den man. 1. jul. 2019 kl. 16.32 skrev Ryan Meek<EMAIL_ADDRESS>
In that top right button just hit "reload" and it should be there
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXABXK2Y67UIAG54VLP5IIOJA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6KDJA#issuecomment-507290020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWWDQWMBFITROIXVRA3P5IIOJANCNFSM4H4PIPRQ
.

will give feedback if anything comes up ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
01.07.19
16.33.02
Den man. 1. jul. 2019 kl. 16.32 skrev Dartfrog<EMAIL_ADDRESS>
i got it
it is installed
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 01.07.19
16.32.37
Den man. 1. jul. 2019 kl. 16.32 skrev Ryan Meek<EMAIL_ADDRESS>
:

In that top right button just hit "reload" and it should be there
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXABXK2Y67UIAG54VLP5IIOJA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6KDJA#issuecomment-507290020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWWDQWMBFITROIXVRA3P5IIOJANCNFSM4H4PIPRQ
.

Hi again there is some isues with show hide tabs i think, if i choose to
show only tab 0 there are more tabs shown?
Yours Sincerely
Kim Poulsen
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
11.07.19
18.57.38
Den man. 1. jul. 2019 kl. 16.33 skrev Dartfrog<EMAIL_ADDRESS>
will give feedback if anything comes up ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 01.07.19
16.33.02
Den man. 1. jul. 2019 kl. 16.32 skrev Dartfrog<EMAIL_ADDRESS>
i got it
it is installed
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 01.07.19
16.32.37
Den man. 1. jul. 2019 kl. 16.32 skrev Ryan Meek<EMAIL_ADDRESS>
:

In that top right button just hit "reload" and it should be there
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWXABXK2Y67UIAG54VLP5IIOJA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY6KDJA#issuecomment-507290020,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWWDQWMBFITROIXVRA3P5IIOJANCNFSM4H4PIPRQ
.

Make sure you are using either hide_tabs or show_tabs, you cannot use both

I know i tried both at separate times
tor. 11. jul. 2019 19.12 skrev Ryan Meek<EMAIL_ADDRESS>
Make sure you are using either hide_tabs or show_tabs, you cannot use both
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWSJUUZXQMM2WDLDAELP65SZNA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXLZOI#issuecomment-510573753,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWT4SFO54Q4ON4IA37DP65SZNANCNFSM4H4PIPRQ
.

If that doesn't solve it, please share your config in a new issue

I can confirm that both are working for me in the current version. Filling out an issue will get me the info I need to troubleshoot and remind me to take a look as soon as I can.

I will send my config tommorow
tor. 11. jul. 2019 19.20 skrev Ryan Meek<EMAIL_ADDRESS>
I can confirm that both are working for me in the current version. Filling
out an issue will get me the info I need to troubleshoot and remind me to
take a look as soon as I can.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWQKKFWVESNBZ2K7VP3P65TUZA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXMMPI#issuecomment-510576189,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWUEFCLKNYGCVPH4C3DP65TUZANCNFSM4H4PIPRQ
.

Hi again, i think it might work BUT, should you not be able to have
different configs for different users? so i can hide some tabs for one user
but show them on another user?
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
12.07.19
17.21.01
Den tor. 11. jul. 2019 kl. 19.23 skrev Dartfrog<EMAIL_ADDRESS>
I will send my config tommorow
tor. 11. jul. 2019 19.20 skrev Ryan Meek<EMAIL_ADDRESS>
I can confirm that both are working for me in the current version.
Filling out an issue will get me the info I need to troubleshoot and remind
me to take a look as soon as I can.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWQKKFWVESNBZ2K7VP3P65TUZA5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZXMMPI#issuecomment-510576189,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWUEFCLKNYGCVPH4C3DP65TUZANCNFSM4H4PIPRQ
.

Yes you can use hide_tabs for main config and show_tabs for another or vice versa. I cannot troubleshoot without knowing if there are any errors or what your config is

Okay here is my config, if i hide using this file or the CCH config, it
hides in all my users, does not matter wich one i log in with
Thank you for helping
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
13.07.19
08.31.49
Den lør. 13. jul. 2019 kl. 02.19 skrev Ryan Meek<EMAIL_ADDRESS>
Yes you can use hide_tabs for main config and show_tabs for another or
vice versa. I cannot troubleshoot without knowing if there are any errors
or what your config is
—
You are receiving this because you authored the thread.
 Your CCH config posted shows no config to hide.
I will say that using CCH with the resources section how you have it will cause caching issues. Meaning that even if you update CCH it would still be using an old version you originally installed. You need to have a version number at the end of your resources and increase the number any time you update it when you install manually. More info in the installation instructions:
https://maykar.github.io/compact-custom-header/
If fixing your resources section doesn't solve the problem, please submit a new issue.

But i use hacs
lør. 13. jul. 2019 14.41 skrev Ryan Meek<EMAIL_ADDRESS>
It's hard to say what your issue is without seeing what you are trying to
do to hide views. Your CCH config posted shows no config to hide.
I will say that using CCH with the resources section how you have it will
cause caching issues. Meaning that even if you update CCH it would still be
using an old version you originally installed. You need to have a version
number at the end of your resources and increase the number any time you
update it when you install manually. More info in the installation
instructions:
https://maykar.github.io/compact-custom-header/
If fixing your resources section doesn't solve the problem, please submit
a new issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV6NCWUUC53OEXPXGLP7HEQ7A5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3Q6YI#issuecomment-511119201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSKJEUAQH4SU242UZLP7HEQ7ANCNFSM4H4PIPRQ
.

i got it to work, will buy some more coffee ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
13.07.19
16.27.28
Den lør. 13. jul. 2019 kl. 15.52 skrev Dartfrog<EMAIL_ADDRESS>
But i use hacs
lør. 13. jul. 2019 14.41 skrev Ryan Meek<EMAIL_ADDRESS>
It's hard to say what your issue is without seeing what you are trying to
do to hide views. Your CCH config posted shows no config to hide.
I will say that using CCH with the resources section how you have it will
cause caching issues. Meaning that even if you update CCH it would still be
using an old version you originally installed. You need to have a version
number at the end of your resources and increase the number any time you
update it when you install manually. More info in the installation
instructions:
https://maykar.github.io/compact-custom-header/
If fixing your resources section doesn't solve the problem, please submit
a new issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV6NCWUUC53OEXPXGLP7HEQ7A5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3Q6YI#issuecomment-511119201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSKJEUAQH4SU242UZLP7HEQ7ANCNFSM4H4PIPRQ
.

@maykar needs coffee too 😉

I thought it worked but if i change one user it will change all users
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5&
13.07.19
16.38.54
Den lør. 13. jul. 2019 kl. 16.27 skrev Dartfrog<EMAIL_ADDRESS>
i got it to work, will buy some more coffee ;o)
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality5& 13.07.19
16.27.28
Den lør. 13. jul. 2019 kl. 15.52 skrev Dartfrog<EMAIL_ADDRESS>
But i use hacs
lør. 13. jul. 2019 14.41 skrev Ryan Meek<EMAIL_ADDRESS>
It's hard to say what your issue is without seeing what you are trying
to do to hide views. Your CCH config posted shows no config to hide.
I will say that using CCH with the resources section how you have it
will cause caching issues. Meaning that even if you update CCH it would
still be using an old version you originally installed. You need to have a
version number at the end of your resources and increase the number any
time you update it when you install manually. More info in the installation
instructions:
https://maykar.github.io/compact-custom-header/
If fixing your resources section doesn't solve the problem, please
submit a new issue.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/maykar/compact-custom-header/issues/152?email_source=notifications&email_token=AHDAOWV6NCWUUC53OEXPXGLP7HEQ7A5CNFSM4H4PIPR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3Q6YI#issuecomment-511119201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHDAOWSKJEUAQH4SU242UZLP7HEQ7ANCNFSM4H4PIPRQ
.

Got me coffee again?! Though I really do appreciate it, please know that it is not required for support and you have been more than generous already.
Please post only your CCH config and if you can do it on github as inserted code instead of an email reply it would be helpful. That way I can be sure indenting is correct. Also, please include your resources section.

☕


Alternative filler algorithms

The Filler from the original SMZ3 randomizer is hard to understand and with recent additions, like picking specific item locations, can be unstable.
We should add different filler algorithms to see how they affect the randomization. If #14 is done, we could even add one that fills items based on distance from other items, or something like that.

This might also allow Tracker to make assumptions about your current location. For example, if you just tracked Fire Rod and then say "track missiles" when there's a missile one or two rooms away could allow tracker to say "Tracked missiles from ".


any methods to accelerate vmdpy？

My program needs to call VMdpy frequently, and It takes a tremendous amount of time.
So I'm wondering whether there is any way to accelerate this process, such as CUDA of GPU, or something like that?

I am looking for same solution, it consumes huge size of memory (even 1 TB for one EEG signal)

The same program, I run quite fast in matlab, but very slow in python


Add flip and unflip textmojis

Added a trick (flip) and a treat (unflip) textmoji (I'm trying to keep it 🎃-themed).
What also works great is setting up Slackbot to reply with :unflip: when someone flips a table, which may very well frustrate them further. 😄

So sorry I never saw this Nick. I love it! Mind rebasing and I'll pull it?
Personally I use tflip to prevent accidental expansion but since these are colon delimited I think :flip: is great.

Closed and replaced with #32


[DOCS]: Create GitHub repository creation tutorial

Describe alternatives you've considered
Would you please share your clear and concise description of any alternative/similar documentation you've considered.
Additional context
Would you please share any other context or screenshots about the documentation request here.

The GitHub Repository Creation Tutorial is now in the document framework.
Content needs creating.