[storybook]: masthead auto opens on default

Detailed description

Describe in detail the issue you're having.

Everything is working fine if you go directly to the default masthead story, but as soon as you navigate to the search open by default whenever you come back to the original story it's not always open on load. It's almost like the state created previously is still hanging around and affecting the default render.

Is this issue related to a specific component?

masthead / storybook

What did you expect to happen? What happened instead? What would you like to
see changed?

Default to load with a closed search input field
Open by default to load with an opened search input field
Those stay true as you navigate inbetween.

What browser are you working in?

Chrome

What version of the IBM.com Library are you using?

Latest

What offering/product do you work on? Any pressing ship or release dates we
should be aware of?

Steps to reproduce the issue

Open masthead: default
navigate to masthead: search open by default
navigate back to masthead: default

note: I provided the links here, but use the sidebar navigation.

@RobertaJHahn looks like this one can be closed too.


Universalize NavigationView selection indicator animations to fix the occlusion bug of the indicator and provide consistency

The NavigationView selected indicator bar animation is hid under other NavigationViewItems while user invoked a NavigationViewItem not next to the currently selected one. That causes unsmooth animation.
image
Description
Used the PlayIndicatorNonSameLevelAnimations for every indicator related animation
Motivation and Context
Fixes #6957
Create animation consistency
How Has This Been Tested?
By using the repo test app and see the visual effects
Screenshots (if appropriate):

@EP012014 Thanks for bringing this issue to our attention! In order to take this fix, I think it's best to keep single level animation behavior in line with the design spec/existing expectations. Would you be able to update the PR to fix the occlusion while keeping the same animation?

@EP012014 Thanks for bringing this issue to our attention! In order to take this fix, I think it's best to keep single level animation behavior in line with the design spec/existing expectations. Would you be able to update the PR to fix the occlusion while keeping the same animation?

OK, I'll try an approach to this.


ImportError: cannot import name 'TranslatedPart' from 'googletrans.models'

Could anyone please fix the following import error when running "from pygoogletranslation import Translator"? Thanks a lot.
"ImportError: cannot import name 'TranslatedPart' from 'googletrans.models' (/usr/local/lib/python3.7/dist-packages/googletrans/models.py)"

I have the same problem, did you solve that?

pip install googletrans==4.0.0-rc1
this  can work

cd the following path

YOUR PYTHON INSTALL PATH /lib/site-packages/pygoogletranslation/utils.py

comment the code

from googletrans.models import TranslatedPart (about line 8)

write new import

from pygoogletranslation.models import TranslatedPart

cd the following path

YOUR PYTHON INSTALL PATH /lib/site-packages/pygoogletranslation/utils.py

comment the code

from googletrans.models import TranslatedPart (about 8th line)

write new import

from pygoogletranslation.models import TranslatedPart

Thanks! It worked.

This is the error of old import name, and only this.
Due to this, everyone must change to fix his or her code downloaded. This is what the developer should do.

and, it dups with #26.


Text change

Text should be:"Enter node details"

Verified this issue on dev app v2.0.70(437)


Swagger and examples for Microsoft.DataBoxEdge RP

Swagger and examples for Microsoft.DataBoxEdge RP

Can one of the admins verify this patch?


Make shapely installation optional via metrics flag

Shapely seems to be a nice package for polygon metrics. It was a little involved for me to switch it out right now so I opted to make the dependency optional. It can now be installed with:
pip install scale-nucleus[metrics]
or locally
poetry install -E metrics
By default the shapely package is not installed.
I think this is a fine solution for now, we can choose to remove the optional dependency in the future and change out Shapely for something else.

I also looked for the longest time for a package that could handle polygons (especially concave) properly and couldn't find a single one in Python.
I think this makes sense to me, though I wonder if we'd also make numpy and scipy optional as well then, since they're only used for metrics right now as well.

I'm fine with that solution. It's just important that we make it as transparent as possible, that a user would need to install with pip install scale-nucleus[metrics]. Let's also add it to the docstring of the PolygonMetric in order to have it in the API docs later.

We are making a very big change here (how users install the package) for a very small reason (calculating IOU metrics for polygons)

We are making a very big change here (how users install the package) for a very small reason (calculating IOU metrics for polygons)

The change is very easily revertable and currently touches no users (nobody is using metrics locally). It also un-blocks rolling out the CLI.
Promise to re-address in the near future!

Seems like we are closing in favor of removing the dependency. I'm going to close it for now since github bot keeps pinging me.


feat: add Remove-KubePod cmdlet

Blocked by https://github.com/tintoy/dotnet-kube-client/issues/51

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

PowerShell Gallery
GitHub release

Your semantic-release bot :package::rocket:


Question: Does html take fragments as arguments?

I could not find the answer anywhere. Unfortunately the type of the values parameter of TemplateResult is values: readonly unknown[]; and is not really self-explanatory. Therefore I am not sure if I can pass DOM fragments to the html function although I know that it works. But I would like to ask if this could somehow cause problems.
Example:
function createHtmlTemplate(html: string) {
  var template = document.createElement("template")
  template.innerHTML = html.trim()
  return template
}

html`${createHtmlTemplate(`
Hello World
`).content}`

Is this a valid way to use html?
Thank you!

You can use DOM Nodes as values as documented in the supported data types section: https://lit-html.polymer-project.org/guide/template-reference#supported-data-types-for-text-bindings
Passing a Node will insert that node into the DOM, so make sure that the semantics of that are what you want. In the case of a <template> element, inserting the element itself will not cause anything to render because the template contents are stored as a separate document fragment. You probably want to return template.content.
You seem to be basically re-implementing unsafeHTML without the dirty-checking though. WHat's your use case?

@justinfagnani thank you. I have one quick follow-up question before I close this issue: Do SVGs fall under DOM Nodes here?


[Proposal] Consolidate Editor Components

The codebase currently contains 3 separate, but very similar, Editor components:

components/Editor/Editor.js
components/Comments/EmbeddedCommentForm.js
components/Comments/CommentForm.js

All three of these components are rather long, in particular the Editor itself.
I think we should discuss a way of extracting common functionality. For example, the insertImage function between the three files is very similar, and is identical between CommentForm and EmbeddedCommentForm.
Two approaches that spring to mind:

Extract common functions like insertImage to helper methods, converting any values assumed to be on this into additional parameters.
or
Create a base class component (BaseEditor, but maybe with a better name), which contains the core functionality of an editor, and then all 3 implemented editors extend the base class, getting the benefit of common functionality implemented while being able to override / expand upon functionality.

Approach 1 is likely quicker. Approach 2 is likely more proper, but should probably only be done if there's enough overlap between the functions in the 3 components.
Curious to hear everyone's thoughts.
P.S. Please label this pr: Discuss.

@Sekhmet notes on Trello

Editor, CommentForm, EmbeddedCommentForm share similiar logic and should be unified in some way. onImageInserted should use standard callback structure or even Promises


[5.5] [NFC] Small fix to emitModuleJob for compatibility with <=5.3 compilers.

Cherry-pick of https://github.com/apple/swift-driver/pull/617
Some SwiftCI bots are using a 5.3 compiler and errors out on this code with:
swift-driver/Sources/SwiftDriver/Jobs/Planning.swift:188:31: error: variable used within its own initial value
               let emitModuleJob = try emitModuleJob()

@swift-ci please test


Tag images with consul version on docker hub

It would be awesome if these images were tagged with the version of consul they contained on Docker Hub.
So the current latest (as of 2015-6-4) should be tagged as progrium/consul:0.5.2.
This would make it much easier to control which version of Consul you're running when using this image.

+1

+1

Done. However, more has changed. This github repo manages three Docker Hub images: gliderlabs/consul, gliderlabs/consul-agent, and gliderlabs/consul-server. Each one currently has a latesttag and0.5` tag that currently point to the same thing. Minor revisions will roll into minor versions for now.

@progrium Thanks! This is helpful.
But it would be great to have the patch version number in the tags too. I want to be able to specify in my downstream Dockerfile whether I'm starting with consul 0.5.0 or 0.5.2, for example. Is there a reason you're not including that (for now)?

I'd just rather not maintain that level of granularity. But maybe I can do it with branches... thing is, any update is going to require changes to Docker Hub and that's not something somebody can submit a PR for.


In the defhydra, how to define an function with modifier on?

Hi,
This is no specifically related with hydra, but how could I define a function which will invokes an emacs command (defun + interactive) with a modifier(C-u) on?

Issues in the wrong repo.

ok good! I don't think I could have helped at all! :)


Remove all this 'mutable container' stuff.

I found some crufty code that doesn't seem to do anything useful. I assume that whatever this code is supposed to implement, it isn't supported behavior, since none of the tests broke when I removed it.

This looks awesome!
Will take a deeper look on Monday. Can I ask you to sign the CLA in the meantime? It would block this PR from being merged in.

Yeah, sorry, signing the CLA is against my religion.
 Took maybe 5 minutes to create the PR.

Squashed the changes into #102, moving the discussion there.


IIS Web.Config Publish Inconsistencies

When publishing an application, the way that web.config is written is inconsistent. If the file exists there is some funky update behavior happening that's trying to diff the file but writing out some invalid entries.
Also it's quite unclear what you can and can't do and when using Visual Studio it will frequently overwrite whatever web.config changes you might have made especially when related to arguments.
The default has settings like this:
 <aspNetCore processPath="%LAUNCHER_PATH%" arguments="%LAUNCHER_ARGS%" stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess">
        <environmentVariables>
          <environmentVariable name="ASPNETCORE_ENVIRONMENT" value="Development" />
          <environmentVariable name="WEBCONNECTION_WEBROOT" value="c:\webconnectionprojects\wwthreads\web" />
          <environmentVariable name="WEBCONNECTION_OPENBROWSER" value="True" />
        </environmentVariables>
      </aspNetCore>

which is fine if you leave these as is and adjust only environment variables. I realize this is probably to most predictable approach, but I actually think it's much cleaner to use command arguments in the arguments attribute.
However, if you decide to explicitly set the process path and arguments as I did, the crazy behavior starts happening.
For example, I set the following in my project's web.config:
<aspNetCore processPath=".\WebConnectionWebServer.exe" arguments="--WebRoot c:\webconnectionprojects\wwthreads\web"
            stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout" hostingModel="inprocess" />

If I run out of my publish folder with this exact configuration it works fine - the arguments are passed and the EXE works to bootstrap the app even for IIS Inprocess operation.
But the first time I publish I get this instead:
<aspNetCore processPath="dotnet"
    arguments=".\WebConnectionWebServer.dll --WebRoot c:\webconnectionprojects\wwthreads\web"
    stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout"
    hostingModel="inprocess" />

Uhm, ok I guess that works, but why?
Then, if I publish again it gets worse:
<aspNetCore processPath="dotnet"
    arguments=".\WebConnectionWebServer.dll .\WebConnectionWebServer.dll --WebRoot c:\webconnectionprojects\wwthreads\web"
    stdoutLogEnabled="true" stdoutLogFile=".\logs\stdout"
    hostingModel="inprocess" />

publish again and the DLL name just keeps adding up.
On several occasions I've also seen environment variables that have been changed in the project's web.config, not getting published into the publish output folder.
Expected Behavior
The problem is that the publish behavior for web.config is very inconsistent. In my opinion there's no good reason to keep web.config around in the publish folder and try to sync it up with the project's version...
Web.config should be re-written on each publish/build operation so that there's a sane co-relation between what the project says and the output holds. If different versions are needed for different environments then Transformations are the way to go with this I think.

Related issue
I can't duplicate this now but my project's Web.config has on several occasions been changed by Visual Studio (presumably when running with IIS Express) wiping out my custom processPath and arguments settings and resetting them to the defaults environment defaults. Additionally the Debug tab's settings are often not synced properly with is in web.config.

This looks like an issue in the web sdk, which is updating the web.config. I'm going to transfer this to aspnet/websdk for investigation there.


Yahoo domains do not allow "_" for CNAME

App Id:
Region:
Step:
Status:

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
When trying create a custom domain on my Yahoo hosted site, Yahoo does not allow an underscore, "_" in the CNAME, so I am not able to establish the custom domain due to the format of the name for the AWS cert manager validation server.  Is there a way to set up custom domains another way?  Maybe by using TXT record?
Error message
Error occurs in the Yahoo DNS settings, saying that it is an invalid name (due to the underscore).

Hi, unfortunately we only support cnames at this time and underscore is required in the name of the cname. This thread has some more details: https://forums.aws.amazon.com/thread.jspa?threadID=304209  Of note, we also do not support email verification as mentioned in the thread.


Tailwind cdn is complaining that it shouldn't be run on production.

Suggested work for this:

Follow the tailwind installation and build guide

Suggested work for this:

Follow the tailwind installation and build guide

I assume we use Yarn as a package manager? @jofftiquez
I will submit a draft pr this hacktoberfest 😋


Check fonts in Java 8 2D

Observed behaviour
Heebo passes FB
Expected behaviour
Heebo doesn't render correctly in Java 8's 2D standard library, so I expect FB to check and flag that. Java 9 uses harfbuzz and the problem goes away

[ ] Add a check that renders all the glyphs in the font using the Java 8 2D library, and see if its completely different vs hb-view (Heebo today should fail this.)
[ ] Add a check that renders all the glyphs in the font using the Java 9 2D library, and see if its completely different vs hb-view (Heebo today should pass this.)

Good:

Bad:

While Java 8 is a LTS release, it is now 10 years old. The fact that a font fails in Java 8 is not a font bug, it's a Java 8 bug, which we can't exactly correct. So I think this is out of scope; feel free to reopen if you consider this still important.


Matching route with multiple segments at once

Hi,
is there/will be there any way how to match multiple segments at once named as one? Like with Ruby on Rails it would be  path="/*fullName" or with React Router it can be achieved with path="/:fullName(.*)?"
Example:
<Router>
  <HomePage path="/" />
  <ShowPage path="/*fullName" />
  <HelpPage path="/help" />
</Router>

In this example order of routes would be HelpPage -> ShowPage -> HomePage

For /help it matches HelpPage
For /schovi it matches ShowPage
For /schovi/test/... it matches ShowPage
For / it matches HomePage

Thx!

Need to get some anchor links in the docs, but look for "Trailing Wildcard" here:
https://reach.tech/router/api/RouteComponent

@ryanflorence Thank you. Didn't get that right on the first time. From the documentation, I thought it is used just when you want another Router inside previous.


Your extension isn't loading into Chrome

Your extension isn't loading into Chrome from the extension shop.

@a4jp-com - I'm sure some more information (Chrome version, OS etc.) would help here.


Simplify backtest_metrics

Description of changes: The backtest_metrics utility function is currently trying to do too much stuff: it can take optional training data, and both a predictor or an estimator, and behave differently based on what it's provided with. As a result, backtest_metrics needs to take all sorts of parameters as input (for example regarding multi-processing options in case training is run), and depends on a bunch of model definitions (like GluonEstimator and so on) and data loading utilities (like InferenceDataLoader).
I think this is bad design first of all, but in addition to it this makes it hard (if possible at all) to remove its dependency on MXNet: this prevents us from potentially making it nicely usable with other frameworks.
This PR is simplifying it by letting it take a predictor and test_data only. Note that this only implies that estimator.train is invoked outside, which seems nicer to me.
PROs

Much less code in backtest_metrics, at the (rather low) cost of having to invoke estimator.train outside

CONs

The mechanism to reconstruct an experiment from the logs of backtest_metrics is lost. I think this is fine, and is just a symptom of the fact that this function is trying to do too much. In a sense, logging a whole experiment and being able to reconstruct it would really be the responsibility of some (potentially more general) "experiment runner" component.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Another relevant fact: backtest_metric is not even used in any of the tutorial notebooks, currently


NixOS Waybar module hyprland/workspaces not found

Hi all,
I'm in the middle of a from-scratch NixOS Hyprland build and I'm having issues getting Waybar to work on hyprland. I'm new to NixOS and Hyprland so bare with me :)
Waybar is installed via configuration.nix with environment.systemPackages
Currently, none of the hyprland modules work (workspaces, window, etc)
module hyprland/workspaces: Unknown module: hyprland/workspaces
I applied this overlay to Waybar to enable experimental options but this doesn't seem to have worked:
  nixpkgs.overlays = [
    (self: super: {
      waybar = super.waybar.overrideAttrs (oldAttrs: {
        mesonFlags = oldAttrs.mesonFlags ++ [ "-Dexperimental=true" ];
      });
    })
  ];

I saw some talk of experimental options being enabled by default in the nixpkg but when looking it seems like that hasn't been merged in yet.
Has anyone else run into this problem and found a solution?

Similar issue here, about a week or two ago, waybar stopped displaying workspaces on Hyprland for me on NixOS. I've been using the experimental overlay for months (and it worked previously), no changes made on my side except regular updates.
Weird thing is waybar doesn't show any relevant errors or warnings in console as it did before (when experimental was disabled), that leads me to think this is a different issue. Perhaps in Hyprland since last Waybar release (0.9.22) is from half August.

or not, looks like Hyprland support was added to Waybar quite recently (and quietly):
https://github.com/Alexays/Waybar/wiki/Module:-Hyprland

Similar issue here, about a week or two ago, waybar stopped displaying workspaces on Hyprland for me on NixOS.

Is this because you were using wlr/workspaces, which stopped working on Hyprland recently? Hyprland/workspaces should be used instead.

I know nothing about Nix so I can't really help with the OPs issue, sadly.

yes, I wasn't aware that hyprland/workspaces even existed until a few hours ago

See, in my case, hyprland/workspaces doesn't work but wlr/workspaces does. This is after I applied the experimental patch. Before, wlr/workspaces didn't work either

huh, what version of waybar does that overlay build? What nixpkgs are you at? I'm on unstable and I have the overlay in my user's nixpkgs, not systems. And it works for me (hyprland, not wlr). Using home-manager to config waybar.

It builds Waybar v0.9.18, and I'm using the stable nixpkgs (23.05.3725.715d72e967ec)
My overlay is in system, maybe I should try it with home-manager instead.
I have Waybar set up to read from the standard .config files.

Yeah that's a pretty old version that probably doesn't have hyprland/workspaces yet.

Is there a way to force nixpkgs to use a newer version or do I have to compile it myself from source? I'm new to NixOS sorry

in the overlay, you can specify a newer source to compile from

After reading the wiki on Overlays, would something like this work?
nixpkgs.overlays = [
    (self: super: {
       waybar = super.waybar.overrideAttrs (oldAttrs: {
         src = self.fetchFromGithub {
           owner = "Alexays";
           repo = "waybar";
           rev = "e30fba0b8f875c7f35e3173be2b9f6f3ffe3641e";
           hash = "whatever the hash is here";
         };
         mesonFlags = oldAttrs.mesonFlags ++ [ "-Dexperimental=true" ];
       });
    })
  ];

After reading the wiki on Overlays, would something like this work?
nixpkgs.overlays = [
    (self: super: {
       waybar = super.waybar.overrideAttrs (oldAttrs: {
         src = super.fetchFromGithub {
           owner = "Alexays";
           repo = "waybar";
           rev = "e30fba0b8f875c7f35e3173be2b9f6f3ffe3641e";
           hash = "whatever the hash is here";
         };
         mesonFlags = oldAttrs.mesonFlags ++ [ "-Dexperimental=true" ];
       });
    })
  ];

You could do that or use nixpkgs-wayland and reference the package from their if you dont want to maintain the overlay yourself. https://github.com/khaneliman/khanelinix/blob/main/modules/home/desktop/addons/waybar/default.nix#L130

After reading the wiki on Overlays, would something like this work?
nixpkgs.overlays = [
    (self: super: {
       waybar = super.waybar.overrideAttrs (oldAttrs: {
         src = super.fetchFromGithub {
           owner = "Alexays";
           repo = "waybar";
           rev = "e30fba0b8f875c7f35e3173be2b9f6f3ffe3641e";
           hash = "whatever the hash is here";
         };
         mesonFlags = oldAttrs.mesonFlags ++ [ "-Dexperimental=true" ];
       });
    })
  ];

You could do that or use nixpkgs-wayland and reference the package from their if you dont want to maintain the overlay yourself. You dont even need the experimental = true since we call the hyprland dispatcher directly. https://github.com/khaneliman/khanelinix/blob/main/modules/home/desktop/addons/waybar/default.nix#L130
But, at this point, we should really have a new release for hyprland/workspaces since a lot of people just go off the latest stable and we've seen lots of people being surprised with Hyprland breaking wlr/workspaces and the latest release has very barebones hyprland/workspaces.

yes please... i am here new to nix, and struggle with configuring it with waybar and hyprland...

Is there a way to force nixpkgs to use a newer version or do I have to compile it myself from source? I'm new to NixOS sorry

I'm in the same boat as you, but I grab the latest version from the unstable nix-channel.
  nixpkgs.overlays = let
    nixos-unstable = import <nixos-unstable> {};
  in [
    (final: prev: {
        inherit (nixos-unstable.pkgs) waybar;
    })
    (self: super: {
      waybar = super.waybar.overrideAttrs (oldAttrs: {
        mesonFlags = oldAttrs.mesonFlags ++ [ "-Dexperimental=true" ];
      });
    })
  ];

For this to work you need to add and then update the unstable nix-channel iirc.


Cannot focus an already focused space

Hi everyone !
Since the update to Sonoma 14.2, i cannot move windows across different space.
The error message is the following : cannot focus an already focused space.
This error is still present even after a complet uninstall / install process
Here is my config file :
config.txt

I also sometimes get this and have no idea what causes it. Then it starts working again all of a sudden

the 'complete process' included the system settings caveats listed in the readme for Sonoma? Which differ from Ventura.
Did you also regenerate the sudoers.d file for yabai?
This does sound like it's a yabai issue. If your other keybinds with skhd work, the it most likely isnt a skhd issue.
From what I understand, the logs of skhd catch output of whichever application it's interacting with.

Hi !
Which cavetas are you talking about ?
Yes, i did regenerate the sudoers file.

ah sorry, they're on the yabai repo readme: https://github.com/koekeishiya/yabai
What happens if you just execute the command from the CLI? e.g., yabai -m space --focus 1
If it works, then it would point to a probelm with skhd, if it doesn't then it could be safer to look at yabai

I upgraded the system and the visudo file and it works magicly now 🤷🏻♂


phisical button, presence sensor etc...

Describe the bug
I just integrated Loxone into my HomeAssistant, I can see all controllable devices (like light, electrical plug, ecc...), but I can't see any sensor: phisical button, presence sensor and so on...
It is possible to read the state of the presence sensor or the phisical switch on the wall to make some automation in home assistant?
Firmware of your Miniserver
<IP_ADDRESS>
HomeAssistant install method
Ready to use container for VMware ESXi
Version of HomeAssistant
Core 2024.4.3
Supervisor 2024.04.0
Operating System 12.2
Version of Pyloxone
0.6.4
Update pyloxone
Yes
Log
Settings for the log can be found on the main page under the section Log Configuration

No. A button, nor a presence sensor is a Loxone-block. The structure file (https://www.loxone.com/wp-content/uploads/datasheets/StructureFile.pdf) lists all blocks that are supported by the API and what information is available/controllable.


chore: Replace cobra with kong in cerbosctl

Signed-off-by: Oğuzhan Durgun<EMAIL_ADDRESS>Description
Fixes #626

Codecov Report

Merging #668 (609a69b) into main (11eda47) will increase coverage by 0.67%.
The diff coverage is 9.52%.

:exclamation: Current head 609a69b differs from pull request most recent head 8f2fe83. Consider uploading reports for the commit 8f2fe83 to get more accurate results

@@            Coverage Diff             @@
##             main     #668      +/-   ##
==========================================
+ Coverage   54.03%   54.71%   +0.67%
==========================================
  Files          89       87       -2
  Lines        9268     9153     -115
==========================================
  Hits         5008     5008
+ Misses       3807     3692     -115
  Partials      453      453

Impacted Files
Coverage Δ

cmd/cerbosctl/get/internal/policy/policy.go
0.00% <0.00%> (ø)

cmd/cerbosctl/get/internal/policy/print.go
0.00% <0.00%> (ø)

cmd/cerbosctl/get/internal/policy/sort.go
100.00% <100.00%> (ø)

cmd/cerbosctl/main.go


Add docusaurus search

Hoping for another option besides Algolia. I'm a bit confused about the options.

if our content on the site is small enough the simplest option just seems to be to use the local search option.
if you're wanting to use something specifically that isnt Algolia, their other listed option is self-hosted Typesense search bar.


NetBox 2.4 release preparation

This branch currently is not ready for production until NetBox 2.4 is released, and is intended to track changes upstream that might break deployment (there is a travis cronjob configured to test this branch daily).
You can use this branch to deploy the NetBox 2.4 branch as usual by installing it using ansible-galaxy like below.
ansible-galaxy install https://github.com/lae/ansible-role-netbox/archive/feature/netbox-2.4.tar.gz,v0.6.0-pre,lae.netbox --force

You must specify the following role variables to test the 2.4 branch:
netbox_git: true
netbox_git_version: develop-2.4

Changes

Python 2 support is dropped from the role (still supported by NetBox 2.4 but will be dropped in 2.5 - I'd rather not keep Python 2 support around if no one is configuring a Python 2 deployment with this role) - #26
Workarounds to fix bugs/shortcomings of NetBox <2.3 have been removed - the next version, v0.6.0 should only be used to deploy NetBox 2.3 or higher. Users should stick to v0.5.6 otherwise.
Configuration files are now validated - prevents services from breaking - #18
Ubuntu 18 LTS is now supported
Future-proofing changes for Ansible 2.6 (and one for 2.10) - minimum required Ansible version is now 2.4
Role is now tested with Python 3 and fixes were made to support Python 3

If you'd like to see anything added, deployment-wise, in the next release, feel free to open an issue.

Hi @lae, would you be willing to consider merging bionic support prior to the 2.4 release? This role is the last blocker for my bionic gates to pass.

@logan2211 2.4 seems to have been released (I've left my previous job and haven't set up release notifications for myself yet so missed it). I just bumped the version in group vars, if tests pass (the most recent build before the develop-2.4 branch was deleted upstream did pass https://travis-ci.org/lae/ansible-role-netbox/builds/412833158) I'll merge this, however there's one issue I'd like to close before I tag a release which involves a bit more effort. I'm busy planning for Comiket currently so will be busy until the 12th. You can however specify a specific branch when you're installing roles, e.g.:
ansible-galaxy install lae.netbox,master,lae.netbox

Or if you're using a requirements file:
- src: lae.netbox
  version: master

This'll pull the master branch instead of the latest tagged version.


React Big Scheduler - Antd date picker changes

Hi,
Is there any possible way to change antd date picker week day starts from "Monday" in react big scheduler????

Hi,
I needed the same thing a while ago, I did it in the following way: in the configuration of "moment" I call the property of the week and define the day on which the calendar begins, in your case the day number 1 which is Monday, already that the array starts on Sunday with 0. For example:
moment.locale('en', {             week: {                 dow: 1,                 doy: 1,             },         });
After set objet calendar:
 let schedulerData = new SchedulerData(date, ViewTypes.Week, false, false, {             resourceName: "Name",             schedulerWidth : dimensions,             views: [],         },{             isNonWorkingTimeFunc: this.isNonWorkingTime   });
And finally:
schedulerData.setLocaleMoment(moment);


Spyder won't install with pip's new dependency solver on Python3.9 (ERROR: Requested decorator 4.0.8, (from ipython>=4.0->spyder) has different version in metadata: '4.0.7')

Issue Report Checklist

[x] Searched the issues page for similar reports
[x] Read the relevant sections of the Spyder Troubleshooting Guide and followed its advice
[x] Reproduced the issue after updating with conda update spyder (or pip, if not using Anaconda)
[ ] Could not reproduce inside jupyter qtconsole (if console-related)
[ ] Tried basic troubleshooting (if a bug/error)

[ ] Restarted Spyder
[ ] Reset preferences with spyder --reset
[ ] Reinstalled the latest version of Anaconda
[ ] Tried the other applicable steps from the Troubleshooting Guide

[x] Completed the Problem Description, Steps to Reproduce and Version sections below

Problem Description
If installing Spyder with the newest pip it won't install.
What steps reproduce the problem?

pip --version => 20.3.1 or 20.3.0
python --version => 3.9.0
Please note that both have to be the versions specified , if using 3.8 with pip 20.3.1 it still works and 3.9 with 20.2.4 also works.
pip install spyder => You will get an error

What is the expected output? What do you see instead?
Full error trace:
Paste Traceback/Error Below (if applicable)
» pip install spyder
Collecting spyder
  Using cached spyder-4.2.0-py3-none-any.whl (10.8 MB)
Requirement already satisfied: atomicwrites>=1.2.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.4.0)
Requirement already satisfied: pyls-black>=0.4.6 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.4.6)
Requirement already satisfied: pyls-spyder>=0.1.1 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.2.1)
Requirement already satisfied: python-language-server[all]<1.0.0,>=0.36.1 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.36.1)
Requirement already satisfied: three-merge>=0.1.1 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.1.1)
Requirement already satisfied: qtawesome>=0.5.7 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.0.1)
Requirement already satisfied: watchdog>=0.10.3 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.10.4)
Requirement already satisfied: pexpect>=4.4.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (4.8.0)
Requirement already satisfied: spyder-kernels<1.11.0,>=1.10.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.10.0)
Requirement already satisfied: parso==0.7.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.7.0)
Requirement already satisfied: jsonschema>=3.2.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (3.2.0)
Requirement already satisfied: qdarkstyle>=2.8 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (2.8.1)
Requirement already satisfied: setuptools>=39.0.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (49.6.0)
Requirement already satisfied: pylint>=1.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (2.6.0)
Requirement already satisfied: chardet>=2.0.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (3.0.4)
Requirement already satisfied: pyqtwebengine<5.13 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (5.12.1)
Requirement already satisfied: keyring>=17.0.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (21.4.0)
Requirement already satisfied: intervaltree>=3.0.2 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (3.1.0)
Requirement already satisfied: numpydoc>=0.6.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.1.0)
Requirement already satisfied: pyxdg>=0.26 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.27)
Requirement already satisfied: ipython>=4.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (7.18.1)
Requirement already satisfied: sphinx>=0.6.6 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (3.3.1)
Requirement already satisfied: qtpy>=1.5.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.9.0)
Requirement already satisfied: pygments>=2.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (2.7.1)
Requirement already satisfied: pyqt5<5.13 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (5.12.3)
Requirement already satisfied: qtconsole>=4.7.7 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (5.0.1)
Requirement already satisfied: jedi==0.17.2 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.17.2)
Requirement already satisfied: psutil>=5.3 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (5.7.3)
Requirement already satisfied: diff-match-patch>=20181111 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (20200713)
Requirement already satisfied: cloudpickle>=0.5.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (1.6.0)
Requirement already satisfied: pickleshare>=0.4 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.7.5)
Requirement already satisfied: pyzmq>=17 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (20.0.0)
Requirement already satisfied: nbconvert>=4.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (6.0.7)
Requirement already satisfied: sortedcontainers<3.0,>=2.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from intervaltree>=3.0.2->spyder) (2.3.0)
Requirement already satisfied: pygments>=2.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (2.7.1)
Requirement already satisfied: pickleshare>=0.4 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.7.5)
Requirement already satisfied: setuptools>=39.0.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (49.6.0)
Requirement already satisfied: traitlets>=4.2 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from ipython>=4.0->spyder) (5.0.5)
Requirement already satisfied: backcall in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from ipython>=4.0->spyder) (0.2.0)
Requirement already satisfied: pexpect>=4.4.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (4.8.0)
Requirement already satisfied: prompt-toolkit!=3.0.0,!=3.0.1,<3.1.0,>=2.0.0 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from ipython>=4.0->spyder) (3.0.8)
Requirement already satisfied: decorator in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from ipython>=4.0->spyder) (4.0.10)
Requirement already satisfied: jedi==0.17.2 in ./.cache/pypoetry/virtualenvs/demap-kqoNszLJ-py3.9/lib/python3.9/site-packages (from spyder) (0.17.2)
INFO: pip is looking at multiple versions of decorator to determine which version is compatible with other requirements. This could take a while.
Collecting decorator
  Using cached decorator-4.4.2-py2.py3-none-any.whl (9.2 kB)
INFO: pip is looking at multiple versions of <Python from Requires-Python> to determine which version is compatible with other requirements. This could take a while.
  Using cached decorator-4.4.1-py2.py3-none-any.whl (9.2 kB)
  Using cached decorator-4.4.0-py2.py3-none-any.whl (8.3 kB)
  Using cached decorator-4.3.2-py2.py3-none-any.whl (9.1 kB)
  Using cached decorator-4.3.1-py2.py3-none-any.whl (8.8 kB)
  Using cached decorator-4.3.0-py2.py3-none-any.whl (9.2 kB)
  Using cached decorator-4.2.1-py2.py3-none-any.whl (9.3 kB)
INFO: pip is looking at multiple versions of decorator to determine which version is compatible with other requirements. This could take a while.
  Using cached decorator-4.1.2-py2.py3-none-any.whl (9.1 kB)
  Using cached decorator-4.1.1-py2.py3-none-any.whl (9.0 kB)
  Using cached decorator-4.1.0-py2.py3-none-any.whl (9.0 kB)
  Using cached decorator-4.0.11-py2.py3-none-any.whl (8.9 kB)
  Using cached decorator-4.0.9-py2.py3-none-any.whl (22 kB)
INFO: This is taking longer than usual. You might need to provide the dependency resolver with stricter constraints to reduce runtime. If you want to abort this run, you can press Ctrl + C to do so. To improve how pip performs, tell us what happened here: https://pip.pypa.io/surveys/backtracking
  Using cached decorator-4.0.8-py2.py3-none-any.whl (22 kB)
ERROR: Requested decorator from https://files.pythonhosted.org/packages/ed/69/24345e0d49c700557f135d01f5de03345368303fdee81b54eae28bf6143d/decorator-4.0.8-py2.py3-none-any.whl#sha256=267b0d56f2c44857f0803cefe5ee1b5d661fd17ef78be3b447d295f70d4a9a5d (from ipython>=4.0->spyder) has different version in metadata: '4.0.7'

Versions

Spyder version: 4.2.0
Python version: 3.9
Qt version: NA
PyQt version: 5.12.3
Operating System name/version: MX Linux (Debian 10)

Work arounds

Downgrade pip to 20.2.4
Downgrade python to 3.8
This seems pip specific, so just use conda

PS. I know you don't officially support pip, but I still thought I led you know.
Possible solutions
It seems the problem isn't specially Spyder to blame, but rather that the decorator package has been packaged incorrectly for 4.0.8 (metadata has not been updated). Unfortunately the combination of deps of Spyder, pips new dep resolver, and running Python3.9 has picked exactly that package. A crude solution would be to just specify in the Spyder deps to blacklist decorator==4.0.8 and hopefully pip will pick a correctly packaged version of the decorator package.

Hey @hwalinga, thanks for reporting. decorator is a dependency of IPython:
https://github.com/ipython/ipython/blob/781f97f044dca67cc0ef5c4fad9ec463caf4192f/setup.py#L188
So I think it's better if you report this problem there because when fixed it'll make IPython installable with pip 20.3 and Python 3.9.

Well, yes and no. IPython is perfectly installable with pip 20.3 and Python 3.9, because the dep resolver does not resolve to the problematic version of decorator==4.0.8 when installing only IPython. This happens because of the unique combination of dependencies that Spyder has that make it that pip chooses to try to install this problematic version of decorator.

I think it should be fixed in IPython by making it blacklist decorator 4.0.8, as you said. Or you could tell the decorator maintainers to yank that release because it is faulty.

That's my suggestion because it'll help other projects that (most probably) will encounter the same problem by trying to fix it where it corresponds.

Will do, thank you.


Question regarding the shape of the mask created from the depth.

When running the scripts/splatam.py algorithm on a NerfCapture created dataset, I ran into 2 different issues. The first one is just context in case it has something to do with the second one.
First, the depth and color datasets had different dimensions, but were applied the same permute transformation. So I decided on flattening it:
old_depth.Size([720, 960, 3, 1])
new_depth = torch.flatten(old_depth, start_dim=2)
new_depth.Size([720, 960, 3])

But now I'm running into an issue with the mask generated by the depth dataset, where it doesn't match the shape of the indexed tensor. I've played around with its shape, but I'm not sure I understand what does the point_cld represent, to create an appropriate mask. The error is dumped below.
The point_cld tensor is created by concatenating two different 2 dimensional tensors, so it would make sense it is 2 dimensional as well.
Any help on how to move forward is appreciated!
Traceback (most recent call last):
  File "scripts/splatam.py", line 1033, in <module>
    rgbd_slam(experiment.config)
  File "scripts/splatam.py", line 572, in rgbd_slam
    densify_intrinsics, densify_cam = initialize_first_timestep(dataset, num_frames,
  File "scripts/splatam.py", line 215, in initialize_first_timestep
    init_pt_cld, mean3_sq_dist = get_pointcloud(color, depth, densify_intrinsics, w2c,
  File "scripts/splatam.py", line 117, in get_pointcloud
    point_cld = point_cld[mask]
IndexError: The shape of the mask [518400] at index 0 does not match the shape of the indexed tensor [172800, 6] at index 0

When running the scripts/splatam.py algorithm on a NerfCapture created dataset, I ran into 2 different issues. The first one is just context in case it has something to do with the second one.
First, the depth and color datasets had different dimensions, but were applied the same permute transformation. So I decided on flattening it:
old_depth.Size([720, 960, 3, 1])
new_depth = torch.flatten(old_depth, start_dim=2)
new_depth.Size([720, 960, 3])

But now I'm running into an issue with the mask generated by the depth dataset, where it doesn't match the shape of the indexed tensor. I've played around with its shape, but I'm not sure I understand what does the point_cld represent, to create an appropriate mask. The error is dumped below. The point_cld tensor is created by concatenating two different 2 dimensional tensors, so it would make sense it is 2 dimensional as well.
Any help on how to move forward is appreciated!
Traceback (most recent call last):
  File "scripts/splatam.py", line 1033, in <module>
    rgbd_slam(experiment.config)
  File "scripts/splatam.py", line 572, in rgbd_slam
    densify_intrinsics, densify_cam = initialize_first_timestep(dataset, num_frames,
  File "scripts/splatam.py", line 215, in initialize_first_timestep
    init_pt_cld, mean3_sq_dist = get_pointcloud(color, depth, densify_intrinsics, w2c,
  File "scripts/splatam.py", line 117, in get_pointcloud
    point_cld = point_cld[mask]
IndexError: The shape of the mask [518400] at index 0 does not match the shape of the indexed tensor [172800, 6] at index 0

Hello! Have you solved it?

Yes. The main issue was that the mask was being generated from a 3-channel depth, while the point cloud is created from only 1 of those channels.
Is it expected for the depth to have 3 channels instead of 1?

Hi, this could be an issue with how the data was captured using NeRFCapture. For more info, please see this issue: https://github.com/spla-tam/SplaTAM/issues/59


MarkupSimplifier.SimplifyMarkup w:hint issue

OpenXML power tools <IP_ADDRESS> from Nuget.
When I edit my docx in a RUN with <w:hint="east asia">.
It will add new RUNs with or without <w:hint>.
Then the SimplifyMarkup method can not merge this new RUNs.
Any help?
My tricky work round is Add the same <w:int> to each adjacent runs.
But i don't know if some bad things will happen.
I have read the document about hint:

hint (Font Content Type) | Specifies the  font type which shall be used to format any ambiguous characters in the current  run.   There are  certain characters which are not explicitly stored in the document, and can be  mapped into multiple categories of the four mentioned above. This attribute  shall be used to arbitrate that conflict, and determine how ambiguities in this  run shall be handled. [Note: This is  primarily used to handle the formatting on the paragraph mark glyph, and other  characters that are not stored as text in the WordprocessingML document. end note]   If this  attribute is omitted, then this ambiguity can be resolved by any means  available.   [Example: Consider the run representing the  paragraph mark glyph, which is not stored as a physical character. Since this  could therefore be formatted with any of the fonts specified for the run, this  ambiguity is resolved using the following WordprocessingML:   <w:pPr><w:rPr><w:rFonts w:hint="eastAsia"  /></w:rPr></w:pPr>   The hint attribute specifies that the run must use the eastAsia font  (theme or not, whichever is in use for East Asian text) as defined for this  range. end example]   The possible  values for this attribute are defined by the ST_Hint  simple type (17.18.41).

Closing all issues as this repo is being archived and will no longer be maintained by Microsoft. The project is licensed for continued use and development by forking to your own repo.


blockstack-cli upgrade issue

> blockstack info

Traceback (most recent call last):
  File "/usr/local/bin/blockstack", line 42, in <module>
    from blockstack_client.cli import run_cli, exit_with_error
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/__init__.py", line 25, in <module>
    import client
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/client.py", line 59, in <module>
    from wallet import *
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/wallet.py", line 62, in <module>
    from .backend.crypto.utils import get_address_from_privkey, get_pubkey_from_privkey
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/backend/__init__.py", line 1, in <module>
    from registrar import *
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/backend/registrar.py", line 45, in <module>
    from .queue import get_queue_state, in_queue, queue_removeall
  File "/usr/local/lib/python2.7/site-packages/blockstack_client/backend/queue.py", line 11, in <module>
    import sqlite3
  File "/usr/local/Cellar/python/2.7.12_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sqlite3/__init__.py", line 24, in <module>
    from dbapi2 import *
  File "/usr/local/Cellar/python/2.7.12_1/Frameworks/Python.framework/Versions/2.7/lib/python2.7/sqlite3/dbapi2.py", line 28, in <module>
    from _sqlite3 import *
ImportError: No module named _sqlite3

I've got this issue when upgrading blockstack on macos
I don't want to destroy any wallet/registration info I have - any ideas why this happened?
Thanks!

It appears that your Mac OS installation of python is unable to find the _sqlite3.so C extension module.
See if it exists on the filesystem.
find /usr/local -name _sqlite3.so
If it doesn't exist, try:
brew install sqlite --with-functions

I had upgraded homebrew python on my mac as well - that had a couple of issues.  Fixed that, and now it's working.
I was mainly worried about the wallet I had in blockstack.
Case closed...

Having trouble connecting to the core:
$ blockstack info
Traceback (most recent call last):
File "/usr/local/bin/blockstack", line 42, in
from blockstack_client.cli import run_cli, exit_with_error
File "/usr/local/lib/python2.7/site-packages/blockstack_client/init.py", line 24, in
import app
File "/usr/local/lib/python2.7/site-packages/blockstack_client/app.py", line 37, in
import jsontokens
File "/usr/local/lib/python2.7/site-packages/jsontokens/init.py", line 10, in
from token_signer import TokenSigner
File "/usr/local/lib/python2.7/site-packages/jsontokens/token_signer.py", line 24, in
from .key_loading import load_signing_key
File "/usr/local/lib/python2.7/site-packages/jsontokens/key_loading.py", line 14, in
from cryptography.hazmat.backends.multibackend import MultiBackend
ImportError: No module named multibackend

Hey @oso4 thanks for reporting and happy to help you out. Can you please open an issue in https://github.com/blockstack/blockstack-core?


Changing error message when azure fails

Changing the error message when an azure cluster ends up in a non-success
state.  This is so users have a better idea of where the issue occured.
Issue:
https://github.com/rancher/rancher/issues/11817

LGTM


Issues pasting into the new terminal.

Environment
Windows build number: 10.0.18362.535
Windows Terminal version (if applicable): 0.7.3451.0
Steps to reproduce

Open the program
Open a new Ubuntu terminal tab
Go to another piece of software (Can be anything like a browser, notepad etc) and copy a string.
Paste into the new terminal tab.

Expected behavior
The string would be pasted into the terminal tab instantly
Actual behavior
The is either a delay of 1-4s before the string gets pasted into the terminal or it doesnt get pasted at all.
Other comments
I have reproduced this bug on a self built computer, surface book 2 and a surface laptop 3.

I certainly wouldn't expect that - is there anything else running on your system that might be trying to manage the clipboard? I honestly have no idea how to debug this without a local repro, so any help you could give would be helpful.

There is nothing locally managing the clipboard. What can I do to help you reproduce the bug 🙌

I could reproduce this bug yesterday, but for some reason now I can't. Maybe it's worth noting I also surface book 2.

I honestly have no idea how we'd be able to repro this on my end 😟 Maybe try repro'ing with task manager open. Is there anything that spikes in CPU usage when you paste into the Terminal?
Also, cc'ing @DHowett-MSFT, maybe we could get someone from the clipboard team to help us get some diagnostics here

Ah I think I got a repro. Try this -

Open a new Ubuntu terminal tab
Go to another piece of software (Can be anything like a browser, notepad etc) and copy a string.
Close WT and reopen a new Ubuntu tab
Paste into the new terminal tab.

I'm so sorry I was wrong...😥 It now again can't be reproduced consistently on my end...
But I indeed got a GIF where I was able to repro it several times. Meanwhile, I found nothing noticeble in CPU usage. Hope it could help.
(It's hard to get a long GIF smaller than 10MB)

I'm so sorry I was wrong...😥 It now again can't be reproduced consistently on my end...
But I indeed got a GIF where I was able to repro it several times. Meanwhile, I found nothing noticeable in CPU usage. Hope it could help.
(It's hard to get a long GIF smaller than 10MB)

This is exactly the same issue I have.

We're guessing this is a /dup of #3609 -- right-clicking doesn't seem to focus the terminal itself... but left-clicking will. If you manage to repro this, and then left-click then right-click, does it work?

We're guessing this is a /dup of #3609 -- right-clicking doesn't seem to focus the terminal itself... but left-clicking will. If you manage to repro this, and then left-click then right-click, does it work?

It would still not paste into the terminal.

Hm. Fair enough!

@martinowren Are you still seeing this?


pattern upgrade for configuration mode for Huawei VRP8

Description
Updated huawei_vrp prompt pattern as these were missing valid characters due to differences between VRP version 8 and version 2. VRP version 8 command prompt has "~" and "*" symbols before a hostname in configuration mode which are absent in VRP version 2. See issue #117 for details.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Tested the applied changes with modified test_huawei_vrp.py.
Tested the applied changes by using this library with the real device in the lab.
Checklist:

[x] My code follows the style guidelines of this project (no GitHub actions complaints! run make lint before
committing!)
[ ] I have commented my code, pydocstyle and darglint are happy, docstrings are in google docstring format, and all
docstrings include a summary, args, returns and raises fields (even if N/A)
[x] I have added tests that prove my fix is effective or that my feature works, if adding "functional" tests, please
note if there are any considerations for the vrnetlab setup
[x] New and existing unit tests pass locally with my changes

LGTM, just repointed to develop and split the pattern across two lines to appease pylint! Thanks for the work on this @dptashnik


[QUARKS-204][WIP] Release target, creating the target/… structure

I compared the Ant build ./ant -> target/java8 and Gradle build ./gradlew build -x test -> build/distributions/java8/ using the find . | grep -v ext | sort script.
Although some differences are found, it has a substantially similar structure

Some javax related file name has been changed

[ ] javax.websocket-client.jar(ant) -> quarks.connectors.javax.websocket-client.jar(gradle)
[ ] javax.websocket-server.jar(ant) -> quarks.connectors.javax.websocket-server.jar(gradle)
[ ] quarks.javax.websocket.jar(ant) -> ./connectors/quarks.javax.websocket/lib/(gradle)

There are no svt jar(quarks.test.svt.jar) exist in ant build(I think it's ant build script problem)

[ ] ./test/svt/lib/quarks.test.svt.jar

Because I already started this PR for compare directories&files schema with ant build, it has not been reflected yet about gathered all the jar files in one place with @bjhargrave advise.

I think the wsclient/websockets jar differences are OK.
I think the fvt/svt jar differences are OK.
I agree that working on the console.war and other work to consolidate jar location can be done after this is merged.


linting; implement linting

Port from @jeremyfa coffeescript.
Should be implemented in lib/linting/ only, in the same minimal/clean layout as completion.
Commands register in lib/haxe.js, and implemented in the sub folder.

implementation is in - tweaking/fixes should be filed separately as needed :)


Remove redundant healthchecks

This removes the healthchecks for global services, since we established
they have little to no benefit when used with docker-compose.
Original PR: https://github.com/alphagov/govuk-docker/pull/156

@barrucadu this is my current understanding. Has the situation changed? If they are indeed redundant, then I think we should remove them until we can put a consistent approach in place that can work across the apps.


Feature Request - GetNearby(Vector3 point, int requestedResults)

Using the PointTree, would like a T[] GetNearby(Vector3 point, int requestedResults) method. This would return the requestedResults closest items to point in the tree.
I am going to take a crack at implementing this, but would also appreciate any suggestions/pointers for how one might go about doing this... (i have a "bad" version which simply calls GetNearby with increasing sized maxDistance values until you get the # of results you want)...

i think its called Quadtree nearest neighbor algorithm
there is good illustration how achieve that.
http://ericandrewlewis.github.io/how-a-quadtree-works/
would be cool if someone implement that 🥇

I found this pdf for a Nearest Neighbor algo, and coded an implementation of it, but only a toy/poc.
http://web.archive.org/web/20120907211934/http://ww1.ucmss.com/books/LFS/CSREA2006/MSV4517.pdf


Update styles for page title bar update

Adding styling for the application status label and the actions associated with the application title.
Related: https://github.com/18F/cg-dashboard/pull/776

You have some linting errors in the title_bar.scss file that you can see here: https://circleci.com/gh/18F/cg-style/255?utm_campaign=vcs-integration-link

Should we close this for now (as we backed off on implementing) and keep the branch up?

That sounds good to me... closing.


Replace operator.getitem (WIP)

[ ] Closes #8008
[ ] Tests added / passed
[x] Passes black dask / flake8 dask / isort dask

This is a PR to replace the use of operator.getitem().
[FIXED] on commit 665eae3
Currently, the tests under dask/arraytests/test_slicing.py are not running, getting error when collecting the tests, due to an import problem. Can't quite figure out what's going on, leaving the traceback here.
_____________________________________________________ ERROR collecting dask/array/tests/test_slicing.py _____________________________________________________
ImportError while importing test module '/Users/ncclementi/Documents/git/my_forks/dask/dask/array/tests/test_slicing.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
../__init__.py:3: in <module>
    from . import backends, fft, lib, linalg, ma, overlap, random
../fft.py:13: in <module>
    from .core import concatenate as _concatenate
../core.py:67: in <module>
    from .slicing import cached_cumsum, replace_ellipsis, setitem_array, slice_array
../slicing.py:16: in <module>
    from .utils import getitem
/Users/ncclementi/mambaforge/envs/dask-dev/lib/python3.8/site-packages/_pytest/assertion/rewrite.py:170: in exec_module
    exec(co, module.__dict__)
../utils.py:13: in <module>
    from .core import Array
E   ImportError: cannot import name 'Array' from partially initialized module 'dask.array.core' (most likely due to a circular import) (/Users/ncclementi/Documents/git/my_forks/dask/dask/array/core.py)

The above exception was the direct cause of the following exception:
/Users/ncclementi/mambaforge/envs/dask-dev/lib/python3.8/importlib/__init__.py:127: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
../__init__.py:265: in <module>
    raise ImportError(str(e) + "\n\n" + msg) from e
E   ImportError: cannot import name 'Array' from partially initialized module 'dask.array.core' (most likely due to a circular import) (/Users/ncclementi/Documents/git/my_forks/dask/dask/array/core.py)
E
E   Dask array requirements are not installed.
E
E   Please either conda or pip install as follows:
E
E     conda install dask                 # either conda install
E     python -m pip install "dask[array]" --upgrade  # or python -m pip install

I'm pretty sure the requirements are installed because without the modification I made, the tests run just fine.

I recommend putting this function in chunk.py. That is standard practice.
On Mon, Aug 9, 2021 at 3:49 PM Naty Clementi @.***>
wrote:

@.**** commented on this pull request.
In dask/array/slicing.py
https://github.com/dask/dask/pull/8015#discussion_r685571325:

@@ -13,6 +13,7 @@
from ..base import is_dask_collection, tokenize
from ..highlevelgraph import HighLevelGraph
from ..utils import is_arraylike
+from .utils import getitem

It seems the approach mention by @Illviljan https://github.com/Illviljan
was the one taken in array/slicing.py where the import is within the
scope of the function. I'll go that route, and if we think this is not
optimal we'll modify it.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/8015#discussion_r685571325, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTGJTKSNHQKYDJ3M23TT4BLQTANCNFSM5B2YEVDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

I recommend putting this function in chunk.py. That is standard practice.

Ok, would do that then. : )

Currently, the tests for chunks 5 and 3 of the test_fuse_getter_with_asarray are failing.
https://github.com/dask/dask/blob/758f4e4b97c985fc84fd0b9d5fa0abcf8fda760d/dask/array/tests/test_optimization.py#L322-L339
The problem is in
n_getters = len([v for v in dsk.values() if v[0] in (getitem, getter)])

which returns empty even and it should be 4 and 2 respectively. Still not sure why this is happening or how to fix it.

So I wasn't sure exactly what the intent of the test was.  It appears to be concerned with the specific graph structure when numpy arrays get involved with dask arrays.  I suspect that it's trying to make sure that we treat the numpy array as a separate task, and pull slices out of it.  Looking at git blame it points us to ad9a17529d65cc3fa4b47620e818f209c8106181
That commit fortunately contains some docs
+Interactions with NumPy arrays
+------------------------------
+
+Dask.array operations will automatically convert NumPy arrays into single-chunk
+dask arrays
+
+.. code-block:: python
+
+   >>> x = da.sum(np.ones(5))
+   >>> x.compute()
+   5
+
+When NumPy and Dask arrays interact the result will be a Dask array.  Automatic
+rechunking rules will generally slice the NumPy array into the appropriate Dask
+chunk shape
+
+.. code-block:: python
+
+   >>> x = da.ones(10, chunks=(5,))
+   >>> y = np.ones(10)
+   >>> z = x + y
+   >>> z
+   dask.array<add, shape=(10,), dtype=float64, chunksize=(5,)>
+
+These interactions work not just for NumPy arrays, but for any object that has
+shape and dtype attributes and implements NumPy slicing syntax.
+

Looking at the result of that test when run on main we see the following graph
> /home/mrocklin/workspace/dask/dask/array/tests/test_optimization.py(336)test_fuse_getter_with_asarray()
-> assert n_getters == y.npartitions
(Pdb) pp dsk
{('add-6448668cee955465f4be9c55139a1d4c', 0): (subgraph_callable-1675a9cc-1ba7-47ad-8cc3-49c50df70bdd,
                                               ('rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a',
                                                0),
                                               (5,)),
 ('add-6448668cee955465f4be9c55139a1d4c', 1): (subgraph_callable-1675a9cc-1ba7-47ad-8cc3-49c50df70bdd,
                                               ('rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a',
                                                1),
                                               (5,)),
 ('array-e1c6756960edd62e1d257bbc5c1bc428', 0): array([1.23456789e+09, 1.23456789e+09, 1.23456789e+09, 1.23456789e+09,
       1.23456789e+09, 1.23456789e+09, 1.23456789e+09, 1.23456789e+09,
       1.23456789e+09, 1.23456789e+09]),
 ('rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a', 0): ('rechunk-split-rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a',
                                                         0),
 ('rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a', 1): ('rechunk-split-rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a',
                                                         1),
 ('rechunk-split-rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a', 0): (<built-in function getitem>,
                                                                       ('array-e1c6756960edd62e1d257bbc5c1bc428',
                                                                        0),
                                                                       (slice(0, 5, None),)),
 ('rechunk-split-rechunk-merge-4f9e8f6712e8868198f46c2d4535c66a', 1): (<built-in function getitem>,
                                                                       ('array-e1c6756960edd62e1d257bbc5c1bc428',
                                                                        0),
                                                                       (slice(5, 10, None),))}

While in this branch we see the following graph:
> /home/mrocklin/workspace/dask/dask/array/tests/test_optimization.py(336)test_fuse_getter_with_asarray()
-> assert n_getters == y.npartitions
(Pdb) pp dsk
{('add-6448668cee955465f4be9c55139a1d4c', 0): ('rechunk-merge-rechunk-split-add-6448668cee955465f4be9c55139a1d4c',
                                               0),
 ('add-6448668cee955465f4be9c55139a1d4c', 1): ('rechunk-merge-rechunk-split-add-6448668cee955465f4be9c55139a1d4c',
                                               1),
 ('array-e1c6756960edd62e1d257bbc5c1bc428', 0): array([1.23456789e+09, 1.23456789e+09, 1.23456789e+09, 1.23456789e+09,
       1.23456789e+09, 1.23456789e+09, 1.23456789e+09, 1.23456789e+09,
       1.23456789e+09, 1.23456789e+09]),
 ('rechunk-merge-rechunk-split-add-6448668cee955465f4be9c55139a1d4c', 0): (subgraph_callable-35ce1320-495f-4cd9-b277-0d6dff1e3e98,
                                                                           (<built-in function getitem>,
                                                                            ('array-e1c6756960edd62e1d257bbc5c1bc428',
                                                                             0),
                                                                            (slice(0, 5, None),)),
                                                                           (5,)),
 ('rechunk-merge-rechunk-split-add-6448668cee955465f4be9c55139a1d4c', 1): (subgraph_callable-35ce1320-495f-4cd9-b277-0d6dff1e3e98,
                                                                           (<built-in function getitem>,
                                                                            ('array-e1c6756960edd62e1d257bbc5c1bc428',
                                                                             0),
                                                                            (slice(5, 10, None),)),
                                                                           (5,))}

(I put a breakpoint in the test to print out the graph)
We see that the graphs are very similar, except that the new graph has fused the getitem in with another call.  So my guess is that somewhere we have a graph optimization which specifically avoids fusing operator.getitem calls.  I briefly searched for such an optimization and couldn't find anything.
We have a couple of options:

Find the code that is special-casing operator.getitem and work to understand it.
Get enough confidence from the docs that came along with the commit that this test is overly specific and brittle.  The thing that it wants to test, that the numpy array got cut up with some getitem-like call, is still true, but that the test was overly specific and so failed.  This kind of overly specific testing is common and something that we like to avoid for just this reason.  It slows down future developers.

In principle understanding what is going on is always better.   But that comes at a cost of time, and we have other things to do.  In this situation I would probably relax the test to something like "getitem" in str(v) rather than v[0] is getitem.  This would work with or without the fusion.

Some other questions that I have pending:

Places that might need a replacement but I'm not sure, comments appreciated:

dask/array/linalg.py  We use operator.getitemmultiple times, do we need to replace these ones?
dask/bag/chunk.py , We define our own getitem that works similarly to operator.getitem would this have a similar problem?

We can probably leave linalg and chunk alone.  I did notice that core.py uses getitem as well when getting fields out of a structured array (this is in Array.getitem I think)

Currently,  some doctests are failing and these are legitimate filings. However, I'm not sure how to go about this problem.
The error we are getting is:
___________________ [doctest] dask.array.slicing.slice_array ___________________
132     Also new blockdims with shapes of each block
133
134         ((10, 10, 10, 10), (20, 20))
135
136     Examples
137     --------
138     >>> from pprint import pprint
139     >>> dsk, blockdims = slice_array('y', 'x', [(20, 20, 20, 20, 20)],
140     ...                              (slice(10, 35),), 8)
141     >>> pprint(dsk)
Expected:
    {('y', 0): (<built-in function getitem>, ('x', 0), (slice(10, 20, 1),)),
     ('y', 1): (<built-in function getitem>, ('x', 1), (slice(0, 15, 1),))}
Got:
    {('y', 0): (<function getitem at 0x7faa29de73a0>,
                ('x', 0),
                (slice(10, 20, 1),)),
     ('y', 1): (<function getitem at 0x7faa29de73a0>, ('x', 1), (slice(0, 15, 1),))}

This is happening because I didn't modify the doctest to reflect that we are using our new getitiem function. However, if I use something like this:
>>> pprint(dsk)
    {('y', 0): (<function getitem>, ('x', 0), (slice(10, 20, 1),)),
     ('y', 1): (<function getitem>, ('x', 1), (slice(0, 15, 1),))}

the test will keep failing because is expecting something of the form
 {('y', 0): (<function getitem at 0x7faa29de73a0>,  ('x', 0),(slice(10, 20, 1),)),
     ('y', 1): (<function getitem at 0x7faa29de73a0>, ('x', 1), (slice(0, 15, 1),))}

where this at 0x7faa29de73a0 will change from run to run. Is there a workaround for this or we just don't check for that print anymore?

this at 0x7faa29de73a0 will change from run to run

I think you can change the doctests to
    {('y', 0): (<function getitem at 0x...>, ('x', 0), (slice(10, 20, 1),)),
     ('y', 1): (<function getitem at 0x...>, ('x', 1), (slice(0, 15, 1),))}

The ellipses (...) is like a wildcard match: https://docs.python.org/3/library/doctest.html#doctest.ELLIPSIS

It seems that @gjoseph92 suggestion didn't do the trick. Still getting a failing in those doctests:
___________________ [doctest] dask.array.slicing.slice_array ___________________
132     Also new blockdims with shapes of each block
133
134         ((10, 10, 10, 10), (20, 20))
135
136     Examples
137     --------
138     >>> from pprint import pprint
139     >>> dsk, blockdims = slice_array('y', 'x', [(20, 20, 20, 20, 20)],
140     ...                              (slice(10, 35),), 8)
141     >>> pprint(dsk)
Expected:
    {('y', 0): (<function getitem at 0x...>, ('x', 0), (slice(10, 20, 1),)),
     ('y', 1): (<function getitem at 0x...>, ('x', 1), (slice(0, 15, 1),))}
Got:
    {('y', 0): (<function getitem at 0x7fab44672dc0>,
                ('x', 0),
                (slice(10, 20, 1),)),
     ('y', 1): (<function getitem at 0x7fab44672dc0>, ('x', 1), (slice(0, 15, 1),))}

I see other places where we are using ... in docstrings, we also have a # doctest: +ELLIPSIS comment. For example
https://github.com/dask/dask/blob/95fb60a31a87c6b94b01ed75ab6533fa04d51f19/dask/optimization.py#L30-L31
@ncclementi could you try that out locally to see if that does the trick. Also cc @jsignell for visibility since you've been thinking about doctests recently

Also, I see the gpuCI build is failing. I suspect that is unrelated and will start passing once https://github.com/rapidsai/cudf/pull/9031 is merged, but wanted to double check with @quasiben

@ncclementi could you try that out locally to see if that does the trick. Also cc @jsignell for visibility since you've been thinking about doctests recently.

Will do, although is there a way of running only the doctests that are on array/slicing.py. I thought I run all the doctests and they all passed, but I might have missed something.

I see other places where we are using ... in docstrings, we also have a # doctest: +ELLIPSIS comment. For example

Oh I see, I missed the comment # doctest: +ELLIPSIS

@ncclementi could you try that out locally to see if that does the trick. Also cc @jsignell for visibility since you've been thinking about doctests recently

Tested it locally and they all passed now.

I noticed that they are not passing in CI. Then when checking the other doctests that use  # doctest: +ELLIPSIS I noticed that instead of pprint(dsk) we are doing just dsk, and now I can replicate the fail locally. But I do not know why it fails.

Maybe because pprint just formats it differently? Could be a whitespace difference?

@gjoseph92 Yes, the formatting is definitely what is throwing the error when using dsk instead of pprint(dsk). The problem is that when using pprint I can't reproduce the error locally (it stills fails on CI) and @jrbourbeau either. So we are not quite sure what kind of magic is happening here.

Maybe just drop the pprint? To my eye, the current expected output doesn't look pprinted.

Sorry for the late response. I am able to reproduce the failures locally. They pass locally for me with this diff:
diff --git a/dask/array/slicing.py b/dask/array/slicing.py
index f8b37f78..38d5932e 100644
--- a/dask/array/slicing.py
+++ b/dask/array/slicing.py
@@ -139,7 +139,9 @@ def slice_array(out_name, in_name, blockdims, index, itemsize):
     >>> dsk, blockdims = slice_array('y', 'x', [(20, 20, 20, 20, 20)],
     ...                              (slice(10, 35),), 8)
     >>> pprint(dsk) # doctest: +ELLIPSIS
-    {('y', 0): (<function getitem at ...>, ('x', 0), (slice(10, 20, 1),)),
+    {('y', 0): (<function getitem at ...>,
+                ('x', 0),
+                (slice(10, 20, 1),)),
      ('y', 1): (<function getitem at ...>, ('x', 1), (slice(0, 15, 1),))}
     >>> blockdims
     ((10, 15),)
@@ -602,7 +604,9 @@ def take(outname, inname, chunks, index, itemsize, axis=0):
     >>> chunks
     ((3, 1),)
     >>> pprint(dsk)
-    {('y', 0): (<function getitem at ...>, ('x', 0), (array([1, 3, 5]),)),
+    {('y', 0): (<function getitem at ...>,
+                ('x', 0),
+                (array([1, 3, 5]),)),
      ('y', 1): (<function getitem at ...>, ('x', 2), (array([7]),))}

     When any indexed blocks would otherwise grow larger than

If we're blocked for multiple days on a doctest then we can always skip the doctest.  They're not critical as long as we test the functionality in actual tests.

If we're blocked for multiple days on a doctest then we can always skip the doctest. They're not critical as long as we test the functionality in actual tests.

My sense is that people weren't actually blocked for multiple days on this, but just popping around on different work. But yes :+1: on the sentiment.

Sorry for the late response. I am able to reproduce the failures locally. They pass locally for me with this diff:
diff --git a/dask/array/slicing.py b/dask/array/slicing.py
index f8b37f78..38d5932e 100644
--- a/dask/array/slicing.py
+++ b/dask/array/slicing.py
@@ -139,7 +139,9 @@ def slice_array(out_name, in_name, blockdims, index, itemsize):
     >>> dsk, blockdims = slice_array('y', 'x', [(20, 20, 20, 20, 20)],
     ...                              (slice(10, 35),), 8)
     >>> pprint(dsk) # doctest: +ELLIPSIS
-    {('y', 0): (<function getitem at ...>, ('x', 0), (slice(10, 20, 1),)),
+    {('y', 0): (<function getitem at ...>,
+                ('x', 0),
+                (slice(10, 20, 1),)),
      ('y', 1): (<function getitem at ...>, ('x', 1), (slice(0, 15, 1),))}
     >>> blockdims
     ((10, 15),)
@@ -602,7 +604,9 @@ def take(outname, inname, chunks, index, itemsize, axis=0):
     >>> chunks
     ((3, 1),)
     >>> pprint(dsk)
-    {('y', 0): (<function getitem at ...>, ('x', 0), (array([1, 3, 5]),)),
+    {('y', 0): (<function getitem at ...>,
+                ('x', 0),
+                (array([1, 3, 5]),)),
      ('y', 1): (<function getitem at ...>, ('x', 2), (array([7]),))}

     When any indexed blocks would otherwise grow larger than

Thanks @jsignell
This diff fails locally for me but passes on CI. I wonder what is that is causing this, although for now the CI doctests pass

It's probably a version mismatch thing.

Those tests failures were unrelated to the changes here and have since been resolved in main. Just merged main which should resolve things

@jrbourbeau I think this one is good to go, unless there is anything else we need to tackle.

Thanks for the ping @ncclementi.  Overall this looks good to me and we should get this in sooner rather than later. We can always address config values, etc. in follow-up PRs.
cc @jakirkham @pentschev if you get a quick moment to look at this to make sure this custom getitem is okay from a GPU array perspective

Thanks for the ping @jrbourbeau . After taking a look, I think this is fine for GPUs, for the things that we explicitly support today the tests are all passing, which is in itself a good sign. We don't have GPU tests for getitem explicitly, which are either luckily working/indirectly tested by other tests (e.g., slicing), but for now it's ok to live like that. If we find something that isn't working moving along, we can revisit this.
Thanks @ncclementi for the work here!

Woo, thanks @ncclementi for you work here and to everyone else for reviewing!


Disable rendering of banner with CLI flags

[x] When passed -noshell, LFE should not render the banner
[x] When passed -nobanner, LFE should not render the banner

Note that this should address the concerns expressed in #312.

Work being done in this branch: https://github.com/oubiwann/lfe/tree/enhancement/369/optional-banner

Okay, this is done now. With -noshell:
./bin/lfe -noshell
Erlang/OTP 21 [erts-10.3.4] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe] [dtrace]

lfe>

With -nobanner:
./bin/lfe -nobanner
Erlang/OTP 21 [erts-10.3.4] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe] [dtrace]

lfe>

Business as usual:
Erlang/OTP 21 [erts-10.3.4] [source] [64-bit] [smp:12:12] [ds:12:12:10] [async-threads:1] [hipe] [dtrace]

   ..-~.~_~---..
  (      \\     )    |   A Lisp-2+ on the Erlang VM
  |`-.._/_\\_.-':    |   Type (help) for usage info.
  |         g |_ \   |
  |        n    | |  |   Docs: http://docs.lfe.io/
  |       a    / /   |   Source: http://github.com/rvirding/lfe
   \     l    |_/    |
    \   r     /      |   LFE v1.3-dev (abort with ^G)
     `-E___.-'

lfe>

Since this branch is based upon one that updates TravisCI, I'll wait until #374 is merged before submitting this PR.

I think @rvirding  would like to embed his Ascii Art in every LFE shell :-)

Hehehe ... well, full-disclosure: that's my ASCII art ;-)

@rvirding (or anyone, really): one of the things I'd like feedback on in this PR is the nested case I used here:

https://github.com/oubiwann/lfe/blob/enhancement/369/optional-banner/src/lfe_shell.erl#L233

It's been years since I've written Erlang, and I feel sooo rusty; I feel certain there's a better (possibly pattern-matching) idiom I would have used when my Erlang was fresh ...

@oubiwann please reveal more  secret history of how LFE made

Hehehe -- well, @ mko-io, I happened to be reading through old entries in the mail list today, and came across this thread:

https://groups.google.com/d/msg/lisp-flavoured-erlang/XA5HeLbQQDk/Jdbf0KJV7dUJ

Note that one of the links in that thread has changed, and is now here:

http://docs.lfe.io/current/history.html

It might be nice to do this simultaneously with support for this from rebar.config ... See #103


Unable to parse RSA private key with no padding

In OpenSSHKey init(string key: String, decryptionKey: Data? = nil) there is an assumption that there will be padding.  However generating an RSA key using ssh-keygen -t rsa -b 4096 produces a private key without padding and the below for loop results in a RangeException as paddingLength is 0
       for i in 1..<paddingLength {             guard padding[i - 1] == UInt8(i) else {                 throw InvalidKey()             }         }

Nevermind - using ssh-keygen -t rsa-sha2-256 creates a usable key and is better anyways.


Format verification checkin

Add some format verification to student ids before writing them to the spreadsheet on the checkin

@justinazhang can you please provide parameters of valid student ids?

From Natalia:

CAL ID INFO

Student ID#s are 10-digit student ID number beginning with 30 or an 8-digit ID number beginning with either a 1, 2, 7, or 8.
Employees or affiliates 8-digit ID number beginning with 01 or an 8-digit UCPath ID number that begins with 10.

Our Cal ID scanner gives encrypted IDs in the form of 810:dddddddd, so the IDs will be a mix of this and the 30dddddddd format (if manually typed). Also we use the ID "1" in cases where the visitor is a general community member that does not have an ID.


Map not displaying in the Map Panel

Hi,
I have MULTILINESTRINGS in a table.
I can view the lines in the map panel but with no map layer underneath, just a grey background.

The SRID being used is 27700 (British National Grid), could this be the reason why no map is being show as when I change it to 4326 I do get a map but the lines are not positioned correctly, which is to expected?

The library we use for CRS transformations (CTS from Orbis) doesn't support 27700->4326 conversion. I hope it will some day.
If you are on PostgreSQL then you could use Postgis conversion function ST_Transform (it is smarter than cts).
For example
SELECT ST_Transform('SRID=27700;POINT(258647 665289)'::geometry, 4326)


register branch transaction on server side

What happened:
register branch transaction on server side, now is on client side
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:

@luky116 Can you describe the background of the task in detail?

@luky116 Can you describe the background of the task in detail?

I'm sorry, I've already done that.


fix: Extract aliased constants from identifiers

When constants are imported from other modules, they appear as an alias in the compiled json. As we didn't take them into account when creating the constants map, hints that imported aliased constants would fail. For example:
"starkware.cairo.common.cairo_keccak.keccak.BLOCK_SIZE": {
            "destination": "starkware.cairo.common.cairo_keccak.packed_keccak.BLOCK_SIZE",
            "type": "alias"
        },
        "starkware.cairo.common.cairo_keccak.packed_keccak.BLOCK_SIZE": {
            "type": "const",
            "value": 3
        },

Here the hint executed with access to scope starkware.cairo.common.cairo_keccak.keccak needs the alias in order to access the BLOCK_SIZE constant imported from  starkware.cairo.common.cairo_keccak.packed_keccak

Codecov Report

Merging #278 (7e36fdd) into main (067f139) will increase coverage by 58.75%.
The diff coverage is 82.35%.

@@            Coverage Diff            @@
##           main     #278       +/-   ##
=========================================
+ Coverage      0   58.75%   +58.75%
=========================================
  Files         0       41       +41
  Lines         0     5208     +5208
=========================================
+ Hits          0     3060     +3060
- Misses        0     1898     +1898
- Partials      0      250      +250

Files Changed
Coverage Δ

pkg/parser/parser.go
57.89% <ø> (ø)

pkg/vm/program.go
35.18% <82.35%> (ø)

... and 39 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Item not moved to other list in Update Modal

When moving an item to another list with the "Update Item" modal, the item is removed from the current list but not added to the other list.

Can I use existing move-item reducer object?
The dropdown needs to say "Add item to"

Commit: https://github.com/johneastman/todo/commit/67d8b9f0a51fcd0eace5dbca84d28df0ae2ba85e


API for mobile

Is there a hack to use the API on mobile?

Not really. The speech sythesis part is easier because you can just hook into the device's speech synthesis functionaliy and return that to the browser.
Speech recognition is harder — it relies on having a powerful speech recognition program to pass the spoken content to, which many devices don't have access to.


Test Annotation Framework for Imported CPython test

When importing test currentlyfrom CPython,  they need to be annotated with comments like

# TODO RustPython
or
# TODO: RustPython

or how ever the author likes. Further the original file revision and the orignating python (language) revision is missing in most of the imported tests, what makes tracking nearly impossible.
To improve the convention base "solution", I propose a python annotation framework using decorators to properly annotate the imported test cases, such that they can be tracked and evaluated in a comprehnesive and comfortable way.
Examples can be seen in Lib/test/test_rpt.py.
This the initial implementation. The core functionality is there and tested, but, e.g., the reporting is very rudimentary and more for demonstration purpoposes.

I love this idea!

I agree marking things more than comments is a good idea.

Yeah, lgtm. There might be more skips/expectedFailures to replace with this since this pr was opened, but we can do that as a follow-up

I strongly prefer this idea than current state.
Not sure librptest has to be placed in Lib/test. I basically regard keeping this directory same to CPython as possible as make easier to manage it in future. (Though it is ok if this is technical constraint)
I don't agree rpt.originated_from usage for class. We probably will not compose a test file with multiple class from different CPython versions. It is better to be placed for the file rather than the class.

:+1: for the last paragraph @youknowone


VSR: repair fast-forward

Summary
Follow-up to https://github.com/tigerbeetledb/tigerbeetle/pull/532.

Backups can use SV messages to catch up to the latest log if their log intersects with the primary, even if the backup doesn't have the latest checkpoint.
A new primary will immediately forfeit and start a new view if it is behind the latest checkpoint.
Both of the above require reworknig DVC/SV generation a bit.
And SV invariants are different — the body headers may now be disjoint (to allow inclusion of prior checkpoint triggers ~and the oldest repairable op~).

Pre-merge checklist
Performance:

[x] I am very sure this PR could not affect performance.

The simulator found a couple bugs I'll sort out tomorrow.

@matklad This is ready for review.
I'm not completely happy about putting more logic into Replica.repair(), but didn't find a better spot for it.
Also, https://github.com/tigerbeetledb/tigerbeetle/pull/561/commits/a6da03c6f4ccbe5966b6584391e00ffce6fc22a6 is a bug fix, but not directly related to this PR.

@matklad Can you re-approve? Your approval was auto-dismissed when I pushed the last commit.


Update archives SHA and bump crates versions

Fix #108: Update the SHA values.
Fix #107: Update the readme and inline docs version table.

Hello, I am a code review bot on flows.network.
It could take a few minutes for me to analyze this PR. Relax, grab a cup of coffee and check back later. Thanks!

@L-jasmine @hydai PTAL 🙏

LGTM
Thank you so much for your pr


Replace context data from session to current_user

This part use session to take data about username, so it return empty value. I think it session should be replaced with current_user.
https://github.com/sloria/cookiecutter-flask/blob/master/{{cookiecutter.app_name}}/{{cookiecutter.app_name}}/templates/users/members.html#L4

I think you're right. I would certainly review and merge a PR for this. =)


clarification on usage

So I have the plugin working but some things weren't entirely clear in the documentation

Is simple bar meant to be used with "Auto Hide Menubar" enabled?
By default simple bar is hidden beneath my windows so I had to set top padding in my yabairc. Is that supposed to be the case?
When I set to "floating" mode, simple bar is still hidden beneath my windows unless I add the top padding to yabairc. This ends up being the same as if I didn't enable floating mode. Should it be floating on top of my yabai windows by default?

I learned how to use yabai a couple weeks ago and I'm excited to use simple bar to help me navigate my spaces. Thanks for releasing this plugin!

Hi,

Aesthetically speaking, I find simple-bar better displayed without the system menubar. If you don't use this option, simple-bar will be rendered below the menubar. You can choose what suits you better.
There is an option external_bar that you can set in your .yabairc. See my config below as an example:

yabai -m config top_padding                  0
yabai -m config bottom_padding               0
yabai -m config left_padding                 0
yabai -m config right_padding                0
yabai -m config window_gap                   0
yabai -m config external_bar                 all:28:0

simple-bar is made to work along side yabai in "stack" or "bsp" modes with the external_bar setting. I should specify that in the readme file.

Sorry for my late response and thank you for the compliments, I'm glad it suits you well!


Kong doesn't start

I cloned the repository and tried to run docker-compose up without any changes. As a result kong_1 container doesn't start and the stack trace contains:
kong_1            | 2018/02/22 12:35:13 [warn] postgres database 'kong' is missing migration: (hmac-auth) 2015-09-16-132400_init_hmacauth
kong_1            | Error: /usr/local/share/lua/5.1/kong/cmd/start.lua:28: [postgres error] the current database schema does not match this version of Kong. Please run `kong migrations up` to update/initialize the database schema. Be aware that Kong migrations should only run from a single node, and that nodes running migrations concurrently will conflict with each other and might corrupt your database schema!
kong_1            |
kong_1            |   Run with --v (verbose) or --vv (debug) for more details
kong_1            | prefix directory /usr/local/kong not found, trying to create it
compose_kong_1 exited with code 1

Same here...

I have seen similar problems and had to run migrations multiple times to try and fix this. One time it complained about the oauth2 table, once jwt, and then it works. Then I run it again and complains again about oauth2 table and cycle continues. very weird behavior from the migration functionality running against C*.

I have same problem while running kong on docker. Solved problem with following guides right here Docker Installation.

Hope this help!

Same here...It still can't be solved?

The same trouble for me.

Looks a bit like a race condition to me looks like kong's depends_on is going to wait for the migrations to start, not to complete, so if the migrations take longer than the kong startup then you'll get this error.

Starting compose_kong-database_1 ...
Starting compose_consul_1 ...
Starting compose_kong-database_1
Starting compose_consul_1 ... done
Starting compose_nginx-lb_1 ...
Starting compose_nginx-lb_1 ... done
Starting compose_kong-migration_1 ...
Starting compose_kong-migration_1 ... done
Starting compose_kong-proxy_1 ...
Starting compose_kong-proxy_1 ... done
Starting compose_konga_1 ...
Starting compose_konga_1 ... done
Attaching to compose_kong-database_1, compose_consul_1, compose_nginx-lb_1, compose_kong-migration_1, compose_kong-proxy_1, compose_konga_1
kong-database_1   | LOG:  database system was shut down at 2018-07-28 11:44:26 UTC
consul_1          | ==> WARNING: Bootstrap mode enabled! Do not enable unless necessary
kong-database_1   | LOG:  MultiXact member wraparound protections are now enabled
consul_1          | ==> WARNING: It is highly recommended to set GOMAXPROCS higher than 1
kong-database_1   | LOG:  autovacuum launcher started
kong-database_1   | LOG:  database system is ready to accept connections
nginx-lb_1        | time="2018-07-28T11:45:16Z" level=debug msg="preStart.RunAndWait start"
nginx-lb_1        | time="2018-07-28T11:45:16Z" level=debug msg=preStart.Cmd.Run
consul_1          | ==> Starting raft data migration...
consul_1          | ==> Starting Consul agent...
nginx-lb_1        | time="2018-07-28T11:45:16Z" level=info msg="2018/07/28 11:45:16 [ERR] (vie
same trouble ----

we have a test that validates our docker-compose now so I'm going to close this at this time 👍


Add plot_rank_dist

density (kde/hist/ecdf) + rank

Similarly to plot_trace_dist, it should internally call plot_rank and plot_dist on the different columns. Therefore, it depends on #12 and can't be started until plot_rank is working

as it depends on plot_rank, it needs rank in arivz-stats