Vim mode no longer allows a default key e.g.  to start a key sequence

For LightTable we're looking to upgrade off an old 4.6 version of the vim mode https://github.com/LightTable/Vim/issues/45. One thing holding us back is noticing that starting at 4.7.0 and verified with 5.11.0, default keys like  no longer can be used to start a key sequence e.g. 'b' cannot be bound to anything. This is a blocker for our users who use  as a leader key. To verify this, you can try the following keybinding on the vim demo: CodeMirror.Vim.map("<Space>b", "<PageDown>", "normal");.
I dug into this and from what I can see, starting with 4.7 this happens because '' and 'b' are treated as separate key events e.g. the vim-process-done signal is triggered after each of those keys. With 4.6.0, the vim-process-done signal is only triggered after both '' and 'b' keys are pressed. It's not clear to me if and how this should be fixed. @mightyguava Since you worked on vim changes from 4.6 to 4.7, any thoughts?
I have observed that I can workaround this issue if I unmap the  keybinding. Currently this isn't possible through a public api. If #3814 is merged and we removed this check or overrode it with a force boolean as a third argument, it would be possible to unmap  and workaround this issue. If we don't think this should be fixed, would you take a PR for either change to unmap?

@marijnh I'm aware you're looking for a vim maintainer. I could help with some of those duties but I'd need to be unblocked on this issue so LightTable can use a recent version of CodeMirror. Seems this is a chicken and egg problem :). Would you be open any of these solutions as a PR to unmap a default key:

Add an optional third arg to unmap that is a boolean that disables checking if the keybinding is user defined
Just delete the requirement that only user-defined keybindings can be unmapped
Expose defaultKeymap in the vimApi to allow a user to modify defaultKeymap as desired. This is leaking more internals than I'd like but a possible solution if we're averse to changing unmap

I'd be leaning towards option 2 -- I assume default vim also allows you to unmap default bindings?

Vim doesn't allow unmaping default bindings (see vim.wikia.com).
By default when there are conflicting keys like in the example above vim waits for a short while to decide if sequence was finished or not which http://stackoverflow.com/questions/14737429/how-to-disable-the-timeout-on-the-vim-leader-key but this can be disabled. When timeout option is disabled vim always picks the longest sequence.
The behavior change between 4.6 and 4.7 was caused by a change in  commandMatches to returns all matches instead of stopping after the first one.
Removing  defaultKeymap[i].user check from unmap is probably not a very good long term solution, since that will make support for noremap impossible.

So then it sounds like the 'proper' solution would be for the vim bindings to implement vim's delay for potential multi-stroke key sequences?


Replace junit logging with custom listener and test level priority queuing

The junit stuff is just bugging me right now. It's hacky, finnicky an all other sorts of icky.

I also have problems with jUnit when trying to run humbug on the Drupal code base. For some reason the /tmp/junitlog.humbug.xml file is empty after the analysis step. This later results in this exception:

Humbug\Exception\InvalidArgumentException: Drupal\Tests\node\Unit\Plugin\views\field\NodeBulkFormTest does not exist on previously generated JUnit log

@pfrenssen I have a cleaner JSON format up and running for the future phpspec integration over at https://github.com/padraic/phpspec-extensions. I'll just port that into a PHPUnit listener and we'll be flying :).
After I write more unit tests...;)

Closing as implemented in current master.


Parse custom tags

In this PR the code can parse custom tags in property docblocks.

Codecov Report

Merging #317 (e5358fb) into main (392757f) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main     #317      +/-   ##
============================================
+ Coverage     93.02%   93.06%   +0.03%
- Complexity      476      480       +4
============================================
  Files            60       60
  Lines          1262     1269       +7
============================================
+ Hits           1174     1181       +7
  Misses           88       88

Impacted Files
Coverage Δ

src/Analyzer/NameResolver.php
74.69% <100.00%> (+1.14%)
:arrow_up:

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


Inter font chosen in Table does not allow correct alignment of dates and numbers

Bug description
This reminds me of an old bug I opened a long time ago
(for reference : https://github.com/apache/superset/issues/17633)
Font used in Table are not using  "fixed width" - at least for numbers.
As a results, dates are misaligned.
Font reported by html console is : Inter, Helvetica, Arial
If I remove Inter, everything is fine, Hevletica is fine,  just like in my previous issue patch :)
One may argue that Helvetica is not nice, but I favor usability over bells and whistle. (and my end users too). Once again, Inter seems to be a poor choice.
Also, "Table" view is not the only one affected by this, the default "Results" are also displayed using this font, but ok, I can admit it's not a "visualisation" item so it is not intended to be nice. (Well, if so, don't try to put a nice font in it to begin with ? :) )
Screenshot may not be the more obvious one, I can provide more.
How to reproduce the bug
Open any Table displaying some dates.
Screenshots/recordings

Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Firefox
Additional context
Seen this on 4.0.0-rc1
and on 3.0.0
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Yep, I remember that, and your argument still has merit. :)
Inter does have a fixed-width mode, but if I recall correctly, @geido looked into utilizing it and the issue was that in many tables, we cannot determine which columns should be fixed-width and which ones shouldn't be.
Perhaps there's a means to finally fix that... or perhaps the table SIP that @justinpark proposed to replace these with AG Grid will somehow resolve the problem (cc @kgabryje)
Or, perhaps @kasiazjc has a design opinion here, and we just don't need Inter anymore. Removing it would affect not just tables, but the code editor(s) as well, and probabl other components (like the timer in SQL Lab).


Unable to upload Chef files - SSH

I am trying to get Test Kitchen to use Docker containers for our Chef cookbook testing, using chef-solo.
I have the following installed on my machine:

test-kitchen (1.2.1)
docker (1.3.2)
kitchen-docker (1.7.0)

I have a Dockerfile as shown below, which installs the version of Chef we use, as well as the gems needed for testing, etc.
FROM centos:centos6
MAINTAINER Eric Krupnik<EMAIL_ADDRESS>
# Update and install base tools
RUN yum update -y && yum groupinstall -y "Development Tools"

# Install packages needed for Ruby and rmv
RUN yum install -y gcc-c++ patch readline readline-devel zlib zlib-devel
RUN yum install -y libyaml-devel libffi-devel openssl-devel make
RUN yum install -y bzip2 autoconf automake libtool bison iconv-devel
RUN yum install -y which tar

# Install Ruby Version Manager (rvm)
RUN gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3
RUN curl -L get.rvm.io | bash -s stable
RUN source /usr/local/rvm/scripts/rvm
RUN source /etc/profile.d/rvm.sh

# Install Ruby 1.9.3
RUN /bin/bash -l -c "rvm requirements"
RUN /bin/bash -l -c "rvm install 1.9.3"

# Set the Ruby version to use
RUN /bin/bash -l -c "rvm use 1.9.3 --default"

# By default, add the --no-ri and --no-doc to all 'gem install' commands
RUN echo "gem: --no-ri --no-rdoc" > ~/.gemrc

# Install the gems
RUN /bin/bash -l -c "gem install bundler"
RUN /bin/bash -l -c "gem install ohai -v=6.18.0"
RUN /bin/bash -l -c "gem install chef -v=11.6.0"
RUN /bin/bash -l -c "gem install ruby-shadow"
RUN /bin/bash -l -c "gem install minitest-chef-handler -v=1.0.1"
RUN /bin/bash -l -c "gem install ci_reporter -v=1.9.0"
RUN /bin/bash -l -c "gem uninstall ci_reporter -v=2.0.0" || true
RUN /bin/bash -l -c "gem install mixlib-shellout -v=1.4.0"
RUN /bin/bash -l -c "gem uninstall mixlib-shellout -v=1.6.0" || true
RUN /bin/bash -l -c "gem uninstall ohai -v=7.4.0" || true

# Create and populate Test Kitchen cache
# Note: The trailing slashes for the destination are required
RUN mkdir -p /tmp/kitchen/cache
ADD <our_artifactory_url>/com/oracle/java/jdk/7u67/jdk-7u67-linux-x64.tar.gz /tmp/kitchen/cache/
ADD <our_artifactory_url>/org/apache/tomcat/apache-tomcat/7.0.56/apache-tomcat-7.0.56.tar.gz /tmp/kitchen/cache/

I am successfully able to build an image using this Dockerfile, by running the command:
 docker build -t="ekrupnik/test:latest" .

and can confirm that the image exists by running docker images:

REPOSITORY          TAG                 IMAGE ID            CREATED             VIRTUAL SIZE
ekrupnik/test       latest              ca982e782896        27 hours ago          809.3 MB

I then try to set my .kitchen.yml file to use this newly built image, which has the version of Chef I want already installed, and cache preloaded for faster test cycles. My .kitchen.yml file looks like:
---
driver_plugin: docker
driver:
  name: docker
  use_sudo: false
driver_config:
  require_chef_omnibus: false

platforms:
- name: centos
  driver_config:
    platform: centos
    image: ekrupnik/test:latest
suites:
- name: default
  provisioner:
    solo_rb:
      environment: CHEFDEV
  encrypted_data_bag_secret_key_path: "<path_to_the_key>"
  data_bags_path: "../../data_bags"
  roles_path: "../../roles"
  environments_path: "../../environments"
  run_list: ["recipe[rup_utils]", "recipe[minitest-handler]"]
  attributes:
    cloud:
      provider: "ec2"

Looking at the kitchen-docker code, I can see that the docker driver will add certain packages (mostly login and SSH related), both for centos specific packages and then also for all platforms.
When I run kitchen-test -l=debug, I can see it is using the ekrupnik/test:latest and then gets permission denied error when uploading files starts:
-----> Starting Kitchen (v1.2.1)
D      [kitchen::driver::docker command] BEGIN (docker >> /dev/null 2>&1)
D      [kitchen::driver::docker command] END (0m0.02s)
D      Berksfile found at /RUP/workspaces/infrastructure/ccc-chef/cookbooks/rup_utils/Berksfile, loading Berkshelf
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/version.rb:3: warning: already initialized constant VERSION
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/version.rb:4: warning: already initialized constant VERSION_ARRAY
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/version.rb:5: warning: already initialized constant VERSION_MAJOR
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/version.rb:6: warning: already initialized constant VERSION_MINOR
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/version.rb:7: warning: already initialized constant VERSION_BUILD
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/common.rb:99: warning: already initialized constant NaN
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/common.rb:101: warning: already initialized constant Infinity
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/common.rb:103: warning: already initialized constant MinusInfinity
/home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/json-1.8.1/lib/json/common.rb:128: warning: already initialized constant UnparserError
D      Berkshelf 2.0.14 library loaded
-----> Cleaning up any prior instances of <default-centos>
-----> Destroying <default-centos>...
       Finished destroying <default-centos> (0m0.00s).
-----> Testing <default-centos>
-----> Creating <default-centos>...
D      [kitchen::driver::docker command] BEGIN (docker -H unix:///var/run/docker.sock build -)
       Sending build context to Docker daemon  2.56 kB
       Sending build context to Docker daemon
       Step 0 : FROM ekrupnik/test:latest
        ---> 380c1d1d996b
       Step 1 : RUN yum clean all
        ---> Using cache
        ---> 4d207a3c779f
       Step 2 : RUN yum install -y sudo openssh-server openssh-clients which curl
        ---> Using cache
        ---> ae2e40e2de42
       Step 3 : RUN ssh-keygen -t rsa -f /etc/ssh/ssh_host_rsa_key -N ''
        ---> Using cache
        ---> 5e84cf748f84
       Step 4 : RUN ssh-keygen -t dsa -f /etc/ssh/ssh_host_dsa_key -N ''
        ---> Using cache
        ---> 3d2e1f2b8476
       Step 5 : RUN useradd -d /home/kitchen -m -s /bin/bash kitchen
        ---> Using cache
        ---> 822b8c1fe35f
       Step 6 : RUN echo kitchen:kitchen | chpasswd
        ---> Using cache
        ---> 14aaba805c8f
       Step 7 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers
        ---> Using cache
        ---> c767c1a531ef
       Step 8 : RUN echo 'kitchen ALL=(ALL) NOPASSWD:ALL' >> /etc/sudoers.d/kitchen
        ---> Using cache
        ---> dac87bcf2c14
       Successfully built dac87bcf2c14
D      [kitchen::driver::docker command] END (0m0.42s)
D      [kitchen::driver::docker command] BEGIN (docker -H unix:///var/run/docker.sock run -d -p 22 dac87bcf2c14 /usr/sbin/sshd -D -o UseDNS=no -o UsePAM=no -o PasswordAuthentication=yes -o UsePrivilegeSeparation=no -o PidFile=/tmp/sshd.pid)
       511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba
D      [kitchen::driver::docker command] END (0m0.41s)
D      [kitchen::driver::docker command] BEGIN (docker -H unix:///var/run/docker.sock inspect 511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba)
       [{
           "AppArmorProfile": "",
           "Args": [
        "-D",
        "-o",
        "UseDNS=no",
        "-o",
        "UsePAM=no",
        "-o",
        "PasswordAuthentication=yes",
        "-o",
        "UsePrivilegeSeparation=no",
        "-o",
        "PidFile=/tmp/sshd.pid"
           ],
           "Config": {
        "AttachStderr": false,
        "AttachStdin": false,
        "AttachStdout": false,
        "Cmd": [
            "/usr/sbin/sshd",
            "-D",
            "-o",
            "UseDNS=no",
            "-o",
            "UsePAM=no",
            "-o",
            "PasswordAuthentication=yes",
            "-o",
            "UsePrivilegeSeparation=no",
            "-o",
            "PidFile=/tmp/sshd.pid"
        ],
        "CpuShares": 0,
        "Cpuset": "",
        "Domainname": "",
        "Entrypoint": null,
        "Env": [
            "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
        ],
        "ExposedPorts": {
            "22/tcp": {}
        },
        "Hostname": "511a400bdd45",
        "Image": "dac87bcf2c14",
        "Memory": 0,
        "MemorySwap": 0,
        "NetworkDisabled": false,
        "OnBuild": null,
        "OpenStdin": false,
        "PortSpecs": null,
        "StdinOnce": false,
        "Tty": false,
        "User": "",
        "Volumes": null,
        "WorkingDir": ""
           },
           "Created": "2015-01-10T18:36:16.541847658Z",
           "Driver": "devicemapper",
           "ExecDriver": "native-0.2",
           "HostConfig": {
        "Binds": null,
        "CapAdd": null,
        "CapDrop": null,
        "ContainerIDFile": "",
        "Devices": [],
        "Dns": null,
        "DnsSearch": null,
        "ExtraHosts": null,
        "Links": null,
        "LxcConf": [],
        "NetworkMode": "bridge",
        "PortBindings": {
            "22/tcp": [
                {
                    "HostIp": "",
                    "HostPort": ""
                }
            ]
        },
        "Privileged": false,
        "PublishAllPorts": false,
        "RestartPolicy": {
            "MaximumRetryCount": 0,
            "Name": ""
        },
        "SecurityOpt": null,
        "VolumesFrom": null
           },
           "HostnamePath": "/var/lib/docker/containers/511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba/hostname",
           "HostsPath": "/var/lib/docker/containers/511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba/hosts",
           "Id": "511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba",
           "Image": "dac87bcf2c14307c7f3cedbd5a2cefd29bc15d741002957241b41bf5dfea9b91",
           "MountLabel": "system_u:object_r:svirt_sandbox_file_t:s0:c857,c920",
           "Name": "/trusting_brattain",
           "NetworkSettings": {
        "Bridge": "docker0",
        "Gateway": "<IP_ADDRESS>",
        "IPAddress": "<IP_ADDRESS>",
        "IPPrefixLen": 16,
        "MacAddress": "02:42:ac:11:00:8d",
        "PortMapping": null,
        "Ports": {
            "22/tcp": [
                {
                    "HostIp": "<IP_ADDRESS>",
                    "HostPort": "49198"
                }
            ]
        }
           },
           "Path": "/usr/sbin/sshd",
           "ProcessLabel": "system_u:system_r:svirt_lxc_net_t:s0:c857,c920",
           "ResolvConfPath": "/var/lib/docker/containers/511a400bdd456b8be5e5bb41c8f34f5e22f9754a75153e9ee9df239ce32b50ba/resolv.conf",
           "State": {
        "ExitCode": 0,
        "FinishedAt": "0001-01-01T00:00:00Z",
        "Paused": false,
        "Pid": 8647,
        "Restarting": false,
        "Running": true,
        "StartedAt": "2015-01-10T18:36:17.032588383Z"
           },
           "Volumes": {},
           "VolumesRW": {}
       }
       ]
D      [kitchen::driver::docker command] END (0m0.03s)
       Finished creating <default-centos> (0m1.51s).
-----> Converging <default-centos>...
       Preparing files for transfer
D      Creating local sandbox in /tmp/default-centos-sandbox-20150110-8584-cgkxm
       Resolving cookbook dependencies with Berkshelf 2.0.14...
D      Using Berksfile from /RUP/workspaces/infrastructure/ccc-chef/cookbooks/rup_utils/Berksfile
       Removing non-cookbook files before transfer
       Preparing data bags
D      Using data bags from /RUP/workspaces/infrastructure/ccc-chef/data_bags
       Preparing environments
D      Using environments from /RUP/workspaces/infrastructure/ccc-chef/environments
       Preparing roles
D      Using roles from /RUP/workspaces/infrastructure/ccc-chef/roles
       Preparing encrypted data bag secret
D      Using secret from /RUP/.chef/access_data_bag_key_CHEFDEV
D      [SSH] kitchen@localhost:49198<{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :password=>"kitchen", :port=>49198}> (sudo -E rm -rf /tmp/kitchen/cookbooks /tmp/kitchen/data /tmp/kitchen/data_bags /tmp/kitchen/environments /tmp/kitchen/roles /tmp/kitchen/clients ; mkdir -p /tmp/kitchen)
D      [SSH] opening connection to kitchen@localhost:49198<{:user_known_hosts_file=>"/dev/null", :paranoid=>false, :password=>"kitchen", :port=>49198}>
       Transfering files to <default-centos>
D      Cleaning up local sandbox in /tmp/default-centos-sandbox-20150110-8584-cgkxm
>>>>>> ------Exception-------
>>>>>> Class: Kitchen::ActionFailed
>>>>>> Message: Failed to complete #converge action: [scp: /tmp/kitchen/dna.json: Permission denied
]
>>>>>> ----------------------
>>>>>> Please see .kitchen/logs/kitchen.log for more details
>>>>>> Also try running `kitchen diagnose --all` for configuration

D      ------Exception-------
D      Class: Kitchen::ActionFailed
D      Message: Failed to complete #converge action: [scp: /tmp/kitchen/dna.json: Permission denied
]
D      ---Nested Exception---
D      Class: RuntimeError
D      Message: scp: /tmp/kitchen/dna.json: Permission denied

D      ------Backtrace-------
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-scp-1.1.2/lib/net/scp.rb:392:in `await_response_state'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-scp-1.1.2/lib/net/scp.rb:363:in `block (3 levels) in start_command'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/channel.rb:311:in `call'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/channel.rb:311:in `process'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:222:in `block in preprocess'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:222:in `each'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:222:in `preprocess'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:205:in `process'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `block in loop'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `loop'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/session.rb:169:in `loop'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-ssh-2.7.0/lib/net/ssh/connection/channel.rb:269:in `wait'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/net-scp-1.1.2/lib/net/scp.rb:279:in `upload!'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/ssh.rb:70:in `upload!'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/ssh.rb:76:in `upload_path!'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:119:in `block in transfer_path'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:119:in `each'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:119:in `transfer_path'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:46:in `block in converge'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/ssh.rb:47:in `initialize'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:43:in `new'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/driver/ssh_base.rb:43:in `converge'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:273:in `public_send'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:273:in `block in perform_action'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:308:in `call'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:308:in `synchronize_or_call'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:283:in `block in action'
D      /home/cccadmin/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/benchmark.rb:280:in `measure'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:282:in `action'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:273:in `perform_action'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:256:in `converge_action'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:246:in `block in transition_to'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:245:in `each'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:245:in `transition_to'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:141:in `verify'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:170:in `block in test'
D      /home/cccadmin/.rvm/rubies/ruby-1.9.3-p551/lib/ruby/1.9.1/benchmark.rb:280:in `measure'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/instance.rb:166:in `test'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/command.rb:109:in `public_send'
D      /home/cccadmin/.rvm/gems/ruby-1.9.3-p551/gems/test-kitchen-1.2.1/lib/kitchen/command.rb:109:in `block (2 levels) in run_action'
D      ----------------------

I can also confirm that the docker container is indeed stared, by running docker ps:
CONTAINER ID        IMAGE               COMMAND                CREATED              STATUS              PORTS                   NAMES
511a400bdd45        dac87bcf2c14        "/usr/sbin/sshd -D -   About a minute ago   Up About a minute   <IP_ADDRESS>:49198->22/tcp   trusting_brattain

If I do NOT use the image I built, and just use a community centos image, things seem to work. I do this by removing the line image: ekrupnik/test:latest from my .kitchen.yml file, and enabling the Chef omnibus installer (require_chef_omnibus: true).
Can anyone please suggest what might be wrong? Has anyone run into this before?
CC: @fnichol

Have you checked dir perms within your image?

I suspect that having RUN mkdir -p /tmp/kitchen/cache in your Dockerfile is creating /tmp/kitchen w/ root:root, and the tk user is unable to write.

@portertech Thank you for the additional set of eyes and the suggestion! This did resolve the issue of being unable to upload the cookbooks, data bags, etc. to the newly spun up Docker container!
Adding chmod statements on the /tmp/kitchen directories is what fixed this issue. Running into a few other issues now which I will be investigating, but those are unrelated to SSH.


deploy website to website01

I've been wondering about using the GitHub deployments API as well. Mostly because there's a more direct view of what was deployed in our PRs. Have you used https://docs.github.com/en/actions/use-cases-and-examples/deploying/deploying-with-github-actions in the past?

I did not (and didn't plan to do that overhaul right now)

Also, it made me look at this file and noticed we made some preparations for the CDN but didn't activate it when we turned on the CDN:
https://github.com/theforeman/jenkins-jobs/blob/4a0b9c2533d48a8a3085908c808975354fde12c6/theforeman.org/pipelines/deploy/website.groovy#L35-L38
Should we do that now?

That's unrelated to which backend the CDN uses, but yes.

https://github.com/theforeman/jenkins-jobs/pull/512

I did not (and didn't plan to do that overhaul right now)

I took a stab at it in https://github.com/theforeman/theforeman.org/pull/2206. What we could even do is to have both in place for a time: GHA for the new host and Jenkins for the old host.


Is there a straightforward way of using Poisson or Negbin with DeepAR instead of Gaussian?

My impression from the DeepAR paper, and the GluonTS paper is that the main emphasis is on full density forecasts, but looking at the tutorials and docs, I don't see any simple way of specifying which type of distribution to model when calling DeepAREstimator, or which distribution is being used by default for that estimator (presumably Normal - but I can't tell).
The only thing I could find so far is the probabilistic forecasting section in the extended tutorial, but that seems to involve building a model (almost) from scratch.
Is there a straightforward way of using Poisson or Negbin with DeepAR instead of Gaussian? And which distribution is DeepAREstimator using by default?

You should be able to just plug in the NegativeBinomialOutput as the distr_output in DeepAR and many other models.

Thanks


SRS: Complete Other Requirements: Appendix A, B, C

SRS ( /10)
Examples: Team E 2022 Team F 2022
Example Mockups: Team C 2022
Need to check if the comments from Deliverable 1 have been addressed.
For any comment that is not addressed (every single one), deduct -2 points.
Fill in the rest of the sections, using information from the project description document.
See this example for an example of the minimum level of detail required.
Unlike this example, your section 4 should be organized into subsections, grouping by general feature area or top-level use cases (i.e. don’t have a sub section for every single use case that is an extension, or instance of)
Has about 15 – 30 functional requirements
If the number of FR is below 15, -10 points
Has about 10 – 15 non-functional requirements.
If the number of NFR is below 10, -10 points
For each wrong requirement deduct -2 points.
For each conflicting/contradictory requirement, deduct -2 points.
If the UI is missing deduct -10 points.
If the UI mockups are not updated significantly i.e. at least 50% more and prior ones improved, deduct -10 points. This is not only the designer's task but they should lead this.
Use cases are required in a separate document.

If there's nothing else we can add to the other parts right now, then I believe it looks fine. We should keep in mind that we might be able to add some things later.


Question about paired-end 10x genomics data

I have 10x 3' sequencing paired-end fastq files, both read files have 150bp (Just like this https://www.biostars.org/p/9529864/), the first read file contains the barcode (16bp) and UMI (12bp) sequence, other sequence should be omitted. Though the sequencing is paired-end, but we only have one fastq file with valid sequence.  I'm confused about the running command

-u read2 --barcode read1 --UMI read1 --readFormat bc:0:15,um:16:27
-1 read1 -2 read2 --barcode read1 --UMI read1 --readFormat bc:0:15,um:16:27,r1:28:-1

A snopshot of my fastq files

In your case, since the other part in read1 is not useful, you shall use the first command "-u read2 --barcode read1 --UMI read1 --readFormat bc:0:15,um:16:27".

Thank you so much for your reply.


Fixing uninstall link

This may fix a broken link.
Signed-off-by: Bridget Kromhout<EMAIL_ADDRESS>

will experiment more later


Add spoken commands for bitwise and/or assignment

As far as I can tell, these actions were never given spoken forms. I am not sure if there is a reason for this, so I wanted to add some in case it was an error.
I made "wise" optional in the command so it does not get too long, but the square brackets can be removed if that does not seem necessary. If this is useful in reducing command length, maybe similar commands could be formatted to make the "wise" in "bitwise" optional.

I've done what I think is a rebase, but I'm uncertain if I did it correctly. Let me know if I need to fix anything.

It looks like you rebased and then merged the rebase into the previous version of your branch. Can you fix that up please?

Fixed and merged.

Thank you for fixing that- I couldn't quite figure out how to. If possible, I'd still like to understand what you did. It looks like you used a force push to get rid of the merge commit I made. Do you mind explaining a little about how you did that?

Sure.

Thanks for letting me know!


fix: dockerfile golang version

Signed-off-by: Alex Jones<EMAIL_ADDRESS>

Build broken, overriding review process


Reinstalls libraries during each deployment

I am trying to use R on Heroku and your buildpack has been helpful so far. However, as I start to increase the number of libraries and then each time I deploy, all the libraries are re-installed from scratch. Is there a way to build libraries on top of a previous successful build?

Hi @maneeshkm
I am aware of this issue; it's covered in issue #29.


Using this from an addon project

I am pulling this into an addon project which I share among a number of sub projects.  I have found that I need to run ember g ember-bootstrap-datetimepicker to pull down all the bower dependencies or I get errors about missing bower dependencies.  So If I had 10 subprojects plus the single addon project, I would need to do this 11 times.
It is possible to automatically serve these bower dependencies to consuming applications of an addon project?

I close this issue because it's old and I can not help.


Build amalgamation from source, support non-standard extensions

Export sqlite3ext.h as a public header, enabling users to include it to define their own extensions.
Instead of using a prebuilt amalgamation, compile it with a prepare_command.
Add the spellfix.c extension as a subspec.

Looks good to me, thanks!


Install instuctions added

The part about Docker Compose does not make sense as there is no compose file. And you are missing the IIIF_IMAGE_CONCURRENCY parameter, which controls the number of threads libvips can use for image processing. By default it takes the number of CPU cores available. Or you specify 0 to make this explicit.

The part about Docker Compose does not make sense as there is no compose file.

I removed it.

And you are missing the IIIF_IMAGE_CONCURRENCY parameter, which controls the number of threads libvips can use for image processing. By default it takes the number of CPU cores available. Or you specify 0 to make this explicit.

I added it to the doc.


Please consider "heatshrink"

heatshrink is a compression library that is optimized for small embedded systems.  It has quite small memory footprint and CPU requirements.
I would be interested to see it compared to regular desktop compression algorithms.
Being designed for embedded use, it is portable.  And the source includes simple command-line compression and decompression tools.
https://github.com/atomicobject/heatshrink

Adding libraries is an issue for squash, the benchmark just uses the squash plugins.
The bug for heatshrink is here: https://github.com/quixdb/squash/issues/52


Images not loading

I just installed the module and the images for 'world and ''map" are not loading. "static" works. Is the source they are being pulled from unavailable? Here is my config and a screenshot of what ends up displaying in MM:
{
disabled: false,
module: "MMM-SunRiseSet",
position: "bottom_center",
config: {
lat: "mylat",
lng: "mylng",
image: "world", //"world" (animation), "map" (animation), "static" (graph)
imageOnly: "yes",       // no = all data, yes = only animated world or map
dayOrNight: "day",   // "night" approaching, "day" approaching (imageOnly: must be "yes", image: must be "world")
useHeader: true,      // true if you want a header
header: "Daylight",      // useHeader must be true
maxWidth: "515px", //default was 515px
}
},

Hey, sorry about that. Yes, the USNO api is down until April.