Markdown Import breaks latex

Describe the bug
When markdown importing a .md file with latex (math) in it, the imported latexs gets the backslashes doubled, breaking the markdown preview latex rendering.
To Reproduce
Steps to reproduce the behavior:

In VScode, set the import config to a folder with an .md file bug-example.md below.
In VScode command shift p on mac.
Type Dendron: Import Pod
Select import.markdown
Once import is done, open the file.
Click dendron markdown preview
You should see the broken latex render

Expected behavior
A markdown file with this latex code in it $\sum{x}$ should import with same latex code.
Instead it imports with $\\sum{x}$
NOTE:
Dendron Doctor does not cause the bug. It only happens on markdown import.
bug-example.md
$\sum{x}$

Desktop (please complete the following information):

OS: Mac OS

Dendron Log file
Please attach the output of >Dev:Dendron: Open Logs here
{"level":30,"time":1606848693553,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"Logger:configure","msg":"exit","log_level":"info"}
{"level":30,"time":1606848693569,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","stage":"dev","isDebug":false,"logPath":"/Users/franco/Library/Application Support/Code/logs/20201201T135127/exthost1/dendron.dendron","logLevel":"info","extensionPath":"/Users/franco/.vscode/extensions/dendron.dendron-0.18.0","extensionUri":{"$mid":1,"fsPath":"/Users/franco/.vscode/extensions/dendron.dendron-0.18.0","path":"/Users/franco/.vscode/extensions/dendron.dendron-0.18.0","scheme":"file"},"storagePath":"/Users/franco/Library/Application Support/Code/User/workspaceStorage/7fbb629df4efaf03258241407eedda10/dendron.dendron","workspaceFile":{"$mid":1,"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/dendron.code-workspace","external":"file:///Users/franco/Google%20Drive/CS%20Curriculum/Notes/Dendron%20Notes/dendron.code-workspace","path":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/dendron.code-workspace","scheme":"file"},"workspaceFolders":[{"uri":{"$mid":1,"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault","external":"file:///Users/franco/Google%20Drive/CS%20Curriculum/Notes/Dendron%20Notes/vault","path":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault","scheme":"file"},"name":"vault","index":0}]}
{"level":30,"time":1606848693571,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"DendronWorkspace","msg":"initialized"}
{"level":30,"time":1606848693576,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","config":{"version":1,"vaults":[{"fsPath":"vault"}],"site":{"copyAssets":true,"siteHierarchies":["root"],"siteRootDir":"docs","usePrettyRefs":true}},"configMigrated":false,"msg":"read dendron config"}
{"level":30,"time":1606848693831,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","wsConfig":{"folders":[{"path":"vault"}],"settings":{"dendron.rootDir":".","files.autoSave":"onFocusChange","pasteImage.path":"${currentFileDir}/assets/images","pasteImage.prefix":"/","markdown-preview-enhanced.enableWikiLinkSyntax":true,"markdown-preview-enhanced.wikiLinkFileExtension":".md","editor.snippetSuggestions":"inline","editor.suggest.snippetsPreventQuickSuggestions":false,"editor.suggest.showSnippets":true,"editor.tabCompletion":"on"},"extensions":{"recommendations":["dendron.dendron-paste-image","equinusocio.vsc-material-theme","dendron.dendron-markdown-shortcuts","dendron.dendron-markdown-preview-enhanced","dendron.dendron-markdown-links","github.github-vscode-theme"],"unwantedRecommendations":["dendron.dendron-markdown-notes","shd101wyy.markdown-preview-enhanced","kortina.vscode-markdown-notes","mushan.vscode-paste-image"]}},"wsConfigMigrated":{"changed":false,"settings":{"folders":[{"path":"vault"}],"settings":{"dendron.rootDir":".","files.autoSave":"onFocusChange","pasteImage.path":"${currentFileDir}/assets/images","pasteImage.prefix":"/","markdown-preview-enhanced.enableWikiLinkSyntax":true,"markdown-preview-enhanced.wikiLinkFileExtension":".md","editor.snippetSuggestions":"inline","editor.suggest.snippetsPreventQuickSuggestions":false,"editor.suggest.showSnippets":true,"editor.tabCompletion":"on"},"extensions":{"recommendations":["dendron.dendron-paste-image","equinusocio.vsc-material-theme","dendron.dendron-markdown-shortcuts","dendron.dendron-markdown-preview-enhanced","dendron.dendron-markdown-links","github.github-vscode-theme"],"unwantedRecommendations":["dendron.dendron-markdown-notes","shd101wyy.markdown-preview-enhanced","kortina.vscode-markdown-notes","mushan.vscode-paste-image"]}}},"msg":"read wsConfig"}
{"level":30,"time":1606848693842,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","installedGlobalVersion":"0.18.0","migratedGlobalVersion":"0.18.0","previousGlobalVersion":"0.17.0","previousWsVersion":"0.18.0","platform":"darwin","extensions":[{"id":"dendron.dendron-paste-image","version":"1.0.4","active":false},{"id":"equinusocio.vsc-material-theme","version":"33.0.0","active":false},{"id":"dendron.dendron-markdown-shortcuts","version":"0.12.1","active":true},{"id":"dendron.dendron-markdown-preview-enhanced","version":"0.10.11","active":false},{"id":"dendron.dendron-markdown-links","version":"0.6.17","active":false},{"id":"github.github-vscode-theme","version":"1.1.5","active":false}],"vaults":[{"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault"}]}
{"level":30,"time":1606848693843,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"startServeer","logLevel":"info"}
{"level":30,"time":1606848693957,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","msg":"post-start-server","port":51318}
{"level":30,"time":1606848694076,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"ReloadIndex.execute","msg":"enter"}
{"level":30,"time":1606848694612,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"ReloadIndex.execute","msg":"exit"}
{"level":30,"time":1606848694613,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"reloadWorkspace","msg":"post-ws.reloadWorkspace"}
{"level":30,"time":1606848694614,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"reloadWorkspace","msg":"exit"}
{"level":30,"time":1606848694614,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"postReloadWorkspace","msg":"same wsVersion"}
{"level":30,"time":1606848694614,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"postReloadWorkspace","msg":"exit"}
{"level":30,"time":1606848694615,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1606848694616,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"setupViews","msg":"init:backlinks"}
{"level":30,"time":1606848694618,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"activateWorkspace","stage":"dev","msg":"enter"}
{"level":30,"time":1606848694621,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"toggleViews","msg":"views enabled: true"}
{"level":30,"time":1606848694623,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"_activate","msg":"fin startClient"}
{"level":30,"time":1606848694623,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"showWelcomeOrWhatsNew","version":"0.18.0","previousVersion":"0.18.0"}
{"level":30,"time":1606848694623,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"showWelcomeOrWhatsNew","msg":"not first time install"}
{"level":30,"time":1606848707465,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1606848742669,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"d:run","msg":"pre-execute"}
{"level":30,"time":1606848742670,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":{"ctx":"ImportPod"},"opts":{"podChoice":{"label":"dendron.markdown","id":"dendron.markdown","description":"import markdown"},"config":{"src":"/Users/franco/Downloads/Math/"}}}
{"level":30,"time":1606848742840,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"ReloadIndex.execute","msg":"enter"}
{"level":30,"time":1606848742975,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"ReloadIndex.execute","msg":"exit"}
{"level":30,"time":1606848742977,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"d:run","msg":"post-execute"}
{"level":30,"time":1606848742983,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1606848743100,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"VaultWatcher:onDidCreate","uri":{"$mid":1,"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/bug-example.md","path":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/bug-example.md","scheme":"file"}}
{"level":30,"time":1606848743211,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"refreshTree"}
{"level":30,"time":1606848743214,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"TreeView:getChildren","msg":"reconstructing tree"}
{"level":30,"time":1606848743607,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"VaultWatcher:onDidChange","uri":{"$mid":1,"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/probability-statistics.md","path":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/probability-statistics.md","scheme":"file"}}
{"level":30,"time":1606848747126,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","msg":"enter","uri":{"$mid":1,"fsPath":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/bug-example.md","external":"file:///Users/franco/Google%20Drive/CS%20Curriculum/Notes/Dendron%20Notes/vault/bug-example.md","path":"/Users/franco/Google Drive/CS Curriculum/Notes/Dendron Notes/vault/bug-example.md","scheme":"file"}}
{"level":30,"time":1606848747411,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"VaultWatcher:onDidChange","fname":"probability-statistics","msg":"exit"}
{"level":30,"time":1606849524105,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"c:run","msg":"pre-execute"}
{"level":30,"time":1606849524106,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"execute","opts":{}}
{"level":30,"time":1606849524138,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"c:run","msg":"post-execute"}
{"level":30,"time":1606849524381,"pid":59611,"hostname":"francombp.local","name":"dendron","ctx":"WindowWatcher:onDidChangeActiveTextEditor","msg":"enter","uri":{"$mid":1,"fsPath":"/Users/franco/Library/Application Support/Code/logs/20201201T135127/exthost1/dendron.dendron/dendron.log","external":"file:///Users/franco/Library/Application%20Support/Code/logs/20201201T135127/exthost1/dendron.dendron/dendron.log","path":"/Users/franco/Library/Application Support/Code/logs/20201201T135127/exthost1/dendron.dendron/dendron.log","scheme":"file"}}

Still repros. I think we should tackle this + #365 in a sort of "markdown pod improvement" release.

Yup, it's a significant usability issue because it effects core UX of writing notes in Dendron.
I would recommend using the PHP Markdown Extra because it renders nested block level items such as lists in an expected way.
Using tildes interchangeably with colons like the other parsers would offer a better UX to users accustomed to different forms of markdown. Principle of least surprise.

Consolidated into a single pod improvement issue.


add maintainability badge

Description
Include maintainability badge from codeclimate

Codecov Report

Merging #53 (75730b3) into main (8bef74c) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #53   +/-   ##
=======================================
  Coverage   91.82%   91.82%
=======================================
  Files           7        7
  Lines         477      477
=======================================
  Hits          438      438
  Misses         26       26
  Partials       13       13

Flag
Coverage Δ

unittests
91.82% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 32c70bd...75730b3. Read the comment docs.


Spring-Challenge--User-Interface venky-yagatilee

@fireinjun
Completed the Sprint challenge.

@FireInjun
Completed the Sprint challenge.

Git-Comments

[x] Utilizing Meaningful Commit Messages
[x] Committing Often: On Every Breakthrough or Feature Completion.
[x] Submitted a Pull Request with your First & Last Name in the title.

Comments

Congratulations, you have met expectations and are properly utilizing git version control.
 If you have not yet tried it
Using git from the command line with bash you can do the following:

git commit -m "Implemented Desktop Break-Points
> CSS Break-Points with media query at 1024px max-width
> Tested in Chrome, Firefox
> Fluid transition between breakpoints."

Press Enter when you want a new line. When you see the `>`
symbol this means that you have pressed Enter and there is a
new line. Remember to close your quotes at the end of your
message and press Enter to submit the command.


(PUP-2455) Update service provider to use 'ctrun' on Solaris

Prior to this commit, non-SMF Puppet-managed services on Solaris
are not started in their own SMF contracts. If started
by Puppet running as a daemon, the services end up in Puppet's
SMF contract.
There are several negative implications from this scenario:
(1) If Puppet is stopped or restarted, the non-SMF Puppet-managed
services in Puppet's SMF contract are killed (by SMF).
(2) If Puppet-managed services are in Puppet's SMF contract, certain
events impacting any one of the managed services can lead to SMF killing
killing Puppet's contract, also killing all Puppet-managed services
that have ended up in Puppet's SMF contract.
In both scenarios, SMF also places Puppet in the SMF "maintenance"
state.
This commit updates the Puppet service provider to use the Solaris
'ctrun' facility to start Puppet-managed services in their own
SMF contracts.
We also add an acceptance test and update spec tests to accomodate
use of :osfamily in the texecute method override.

Replaces https://github.com/puppetlabs/puppet/pull/3660.

CLA signed by all contributors.

:+1: @branan @kylog if you want to take a look at this, that would be awesome. I'd like to get it merged in sooner rather than later as it's a support escalation.

Do we want new spec tests for this behavior in addition to the acceptance tests?

@haus Yes, thanks.
I'm struggling a bit with with the spec test.
I added this to spec/unit/provider/service/init_spec.rb:
describe "when starting a service on Solaris" do
  it "should use ctrun" do
    Facter.stubs(:value).with(:osfamily).returns 'Solaris'
    provider.expects(:texecute).with(:start, ['/usr/bin/ctrun -l none', '/service/path/myservice', :start], true).returns("")
    provider.start
  end
end

When I execute, I'm seeing this error:
# be rspec spec/unit/provider/service/init_spec.rb
Run options: exclude {:broken=>true, :benchmark=>true}
..................................F

Failures:

  1) Puppet::Type::Service::ProviderInit if the init script is present when starting a service on Solaris should use ctrun
     Failure/Error: provider.start
     Mocha::ExpectationError:
       unexpected invocation: Service[myservice](provider=init).texecute(:start, ['/service/path/myservice', :start], true)
       unsatisfied expectations:
       - expected exactly once, not yet invoked: Service[myservice](provider=init).texecute(:start, ['/usr/bin/ctrun -l none', '/service/path/myservice', :start], true)
       satisfied expectations:
       - allowed any number of times, not yet invoked: Signal.trap(any_parameters)
       - allowed any number of times, invoked once: File.directory?('/alt/service/path')
       - allowed any number of times, invoked once: File.directory?('/service/path')
       - allowed any number of times, invoked once: Puppet::FileSystem.exist?('/service/path/myservice')
       - allowed any number of times, not yet invoked: Facter.value(:osfamily)
     # ./lib/puppet/provider/service/service.rb:39:in `ucommand'
     # ./lib/puppet/provider/service/base.rb:65:in `start'
     # ./spec/unit/provider/service/init_spec.rb:216:in `block (4 levels) in <top (required)>'

Finished in 0.1179 seconds
35 examples, 1 failure

Since we're overriding texecute based on the Facter returning "Solaris" for osfamily,  it seems like allowed any number of times, not yet invoked: Facter.value(:osfamily) may be part of the issue.

@branan @melissa Any ideas regarding the spec test referenced in the previous comment?

Updated commit with a couple of simple spec tests.

Thanks @branan for your help with this!
The just-added spec tests found a valid issue on Ruby 1.8.7, where we can't use regex match on a symbol.
Updated the commit to change
if type =~ /^start/ && Facter.value(:osfamily) == "Solaris"

to
 if type == :start && Facter.value(:osfamily) == "Solaris"

:+1: from me here

:+1:

This requires a merge up into pe-puppet


Removed block check from replacement commands.

As requested, Sprocket has been updated to remove the block check from  and  commands.

Great, thanks. This is a nice step towards cleaning things up. As I mentioned, ultimately, we will need a way to disable ore generation when a block is missing. The current checks around OreBlock will not do the job.

As I mentioned, ultimately, we will need a way to disable ore generation when a block is missing. The current checks around OreBlock will not do the job.

If you have any ideas, I'm all ears.  There may be some things I can try, but for now, I'm not going to be able to do much experimentation.  Changing small things is one thing, but blocking a whole distribution when all its ore blocks are missing is going to be a more significant rewrite.
Can you give a use case where this becomes a problem?

The IC2 config is one use case. Users can disable the block entirely in the config, so there is no block to place. That will break any distribution using that block. You bring up the complicated case of multi-ore distributions. One could imagine complicated adaptive code that would re-weight the remaining blocks. But for now, I would just block a distribution if any blocks are missing. My suggestion was to do this at the option level: have a condition that will define a hidden option, defaulted to none, instead of the usual option. I'm hoping that does not require a rewrite of sprocket.

It won't require a rewrite of the tool, but I will need to do some significant work; I may be able to set a block check on the options sections, setting the distribution to "none" if all associated blocks are missing, but that will require that I go through the source and reacquaint myself with the code for the config section of the program, since the last time I did any significant work on the script was in August; all changes I've made since were tweaks in one or two functions since.

While I'm at it, I think I'll also be adding a new preset to the config: the stratum.  Using a cloud with a thickness of 2 average, 2 deviation, we can provide a more natural formation for mods providing stone, rather than ore.

One way I've done strata in Geologica is using 3 substitutes. One 100% substitution in the middle, with one 50% substitution above and one below. The 50% substitutions blend the stratum with the adjacent ones. This will of course cut across the entire world, so perhaps it should be biome-dependent.

I was actually considering the localized strata configurations I saw in the GT config, but I like your idea, too.  Perhaps two strata presets, one global (using the substitute), and one local (using the clouds with a narrow thickness, and a large radius)

Yes, both are good to have. The GT config is largely copy-and-pasted from the Geologica config.

Anything else from Geologica you think might benefit from a sprocket preset?

Hmmm... I see how we can set up the strata presets, but it occurred to me that I can also use the "huge vein" distribution as a pipe containing lava in order to set igneous rock as the shell.

Or, maybe we can just use the compound vein distribution with igneous rock as the shell.

In either case, we can probably keep the motherlode at 0 to simulate a mantle intrusion...

Yes, dikes would be an interesting feature.

In any event, if you want to track the block check issue, I have added an issue: reteo/Sprocket#1


Support for workspace apps making requests on behalf of users

Description
Slack's workspace apps now support invoking methods on behalf of a specified user.
In order to support this style of calling methods, we need to make changes to SlackClient.api_call() in order to allow a value to be set for the X-Slack-User HTTP header.
An analogous change was made in the Node Slack SDK here: https://github.com/slackapi/node-slack-sdk/issues/608.
Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Pump the brakes on WTA


Out of memory management

With try_reserve available for Vec, the checked operations (e.g. checked_add) could return None when out of memory.
Is this extension possible in checked traits?

(Assuming we bump the MSRV to 1.57 for try_reserve...)
That's certainly possible, but I don't think it's a good idea, because the current purpose of those methods is only to detect arithmetic overflow. I think it would be semantically confusing for this to also conflate OOM.
Maybe it would make sense to have try_op methods which return a Result, and the error type could indicate the type of failure. It may be difficult to thread this through the more complicated operations though, like multiplication and division.


Make Json RPC TLS Test Java 17 friendly

PR description
There was a change in error codes in Java DER decoding between Java 17 and Java 11.  Tests depend on Java 11 error.  Use JUnit5 facilities to ensure the test works proeprly on both with the same codebase.
Fixed Issue(s)

Documentation

[X] I thought about documentation and added the doc-change-required label to this PR if
updates are required.

Changelog

[X] I thought about the changelog and included a changelog update if required.

Fixes #3860


[CNF-5646] Add CSISnapshot capability

Add CSISnapshot capability which allows disabling CSI snapshot
controller operator which is responsible for watching the
VolumeSnapshot CRD objects and manages the creation and
deletion lifecycle of volume snapshots.

/cc @gnufied @jsafrane

/approve
/assign @jsafrane
Jan for lgtm.

/lgtm

/label qe-approved
/label docs-approved
/label px-approved


Create BucknellSolar

Description
App that displays current solar input at the Bucknell University solar farm.
Copilot

🤖 Generated by Copilot at 2938ac3
Summary
🌞📡📦

Added a new applet BucknellSolar that shows the current solar power output from Bucknell University. The applet uses APIs to fetch and decode data and renders a simple icon and text layout.

Solar farm applet
render and schema modules
Autumn sun powers

Walkthrough

Create a new applet for displaying Bucknell University solar farm input (link)

I have read the CLA Document and I hereby sign the CLA


FE: should Map be a tab?

I know the plan is to make Land asset inpects have a minimap above. But should we also link to the general map?

Related: https://github.com/webaverse/app/issues/521

Related: https://github.com/webaverse/app/issues/521

added https://github.com/webaverse/webaverse.com/commit/39c351e1663b815d5a1500a092bd7f51acae5e14

added https://github.com/webaverse/webaverse.com/commit/39c351e1663b815d5a1500a092bd7f51acae5e14


added new requests

Added more requests to the package.
It is now possible to create/upload/connect target models and shiny dashboards.

Since this will be used in other projects, we should think about publishing the repository on pypi or atleast initialize it as an installable python library


Add MetaFilter component, use on ClassifyFailures

Add a metadata filtering component, and tie it to ClassifyFailures
FilterTable
First time working with React, not at all sure if I did this 'right'.
At this point I've tested locally, but not extensively.  Opening this for some input from @rsnyman @john-dupuy @jjaquish  on my approach here.
There's also been discussion of doing this more generically, like the run/result filter page, with separate dropdowns for field and value selection.

Not sure why lint is failing, pre-commit runs cleanly for me.
Investigating now, definitely unrelated to your changes. The same thing happened in #220


[WIP] Initial implementation of new super

Needs cleanup and feedback

@slozier I am not sure I liked how I solved the issue, but it's a WIP and feedback is good.

@slide Hmm, so you only add __class__ if super is defined? The following appears to be perfectly valid in CPython:
class test:
  def test(self):
    return __class__

assert test().test() == test

Here's an example of what I had in mind for adding the __class__ variable: https://github.com/slozier/ironpython3/commit/ff17804e155e2190287df5251f92683eba34e2fc. It seemed to work with the few tests I did, but the Ast stuff is still something of a mystery for me...

Yeah, this only fixed one of the places that __class__ was needed, which is if super is used.

Anyways, I think I would keep the __class__ stuff completely out of the parser...

Yeah, I agree. I wasn't very happy with the way you did it.

I mean the way I did it...Sorry that came out as "you" I definitely like the way you did it.


Create dataset loader for Multilabel Multiclass Sentiment and Emotion Dataset from Indonesian Mobile Application Review

Dataloader name: id_sent_emo_mobile_apps/id_sent_emo_mobile_apps.py
DataCatalogue: http://seacrowd.github.io/seacrowd-catalogue/card.html?id_sent_emo_mobile_apps

Dataset
id_sent_emo_mobile_apps

Description
This dataset contains manually annotated public reviews of mobile applications in Indonesia. Each review is given a sentiment label (positive, negative, neutral) and an emotion label (anger, sadness, fear, happiness, love, neutral).

Subsets
-

Languages
ind

Tasks
Sentiment Analysis

License
Creative Commons Attribution Non Commercial No Derivatives 4.0 (cc-by-nc-nd-4.0)

Homepage
https://github.com/Ricco48/Multilabel-Sentiment-and-Emotion-Dataset-from-Indonesian-Mobile-Application-Review/tree/CreateCodeForPaper

HF URL
-

Paper URL
https://www.sciencedirect.com/science/article/pii/S2352340923006662

#self-assign


programming language pills now also work without comma

Currently when a user signs up and writes their skills in a string without commas the pills on the card view only shows them in one large pill. Now users can either enter their skills with comma "Ruby, Java, Go" Or without comma "Ruby Java Go"

Nice!


leverage scraper plugin: node-build-update-defs

closes #79
the node-build-update-defs plugin is useful on its own. It provides a command such that end users are able to scrape nodejs.org themselves and install the latest available node versions without waiting for a node-build release. Having it as a separate plugin vs a subcommand that ships with node-build sidesteps a couple issues. (namely, conflicts between scraped definitions blocking git-pulls, the node requirement within node-build, separate directories for scraped vs shipped definitions, etc)
So given that the scraper exists in a plugin and stands on its own, it no longer makes sense to ship the scraper with node-build itself. The scraper is/was only used by node-build maintainers.
This PR:

removes the scraper and bin script from node-build
updates the npm-script to leverage the plugin
updates the readme to recommend the plugin

So maintainers of node-build can still run npm run write-definitions as before, to generate/scrape definitions for addition in node-build. The only difference is that the node-build-update-defs plugin must be installed (like a regular nodenv plugin) to enable the write-definitions npm script.
Any objections to this approach?

:+1:

planning on leaving this out there a bit before cutting a release. but i've
been running it locally for a couple weeks when doing node release scrapes.
Works well on the maintainer side. And the nodenv plugin itself is working
nicely from an end user's perspective.
On Wed, Dec 9, 2015 at 2:27 PM, Josh Hagins<EMAIL_ADDRESS>wrote:

[image: :+1:]
—
Reply to this email directly or view it on GitHub
https://github.com/OiNutter/node-build/pull/87#issuecomment-163365098.


fix(utxos): Reverting changes

This PR reverts the prototype code changes that were intended to fix #13. While those changes first appeared to work, they actually just not throwing errors. The change was not returning UTXOs for any address.

:tada: This PR is included in version 1.4.6 :tada:
Your semantic-release bot :package::rocket:


new: support listing suggested open parameters

What type of PR is this?
/kind design
/kind feature
Any specific area of the project related to this PR?
/area plugin-sdk
/area tests
What this PR does / why we need it:
Following the updates of https://github.com/falcosecurity/libs/pull/173, this PR adds support for the list_open_params function symbol to the Go SDK. An example of usage of the functionality, with ad-hoc documentation, is provided by updating the full plugin example.
Source plugins can optionally implement the new sdk.OpenParams interface. If so, they can return a list of suggested open parameters that are valid arguments to be passed to Open().
Which issue(s) this PR fixes:
Special notes for your reviewer:
This depends on https://github.com/falcosecurity/libs/pull/173 and is noted as WIP until it gets merged.
Does this PR introduce a user-facing change?:

new: support listing suggested open parameters

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

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

LGTM label has been added.  Git tree hash: 12d1cb3412f5f860d738f476b01d292a25ff15d3

/check-dco

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

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

/kind feature

/kind design

/area plugin-sdk
/area tests

Closing and reopening to trigger @poiana
/close

@leogr: Closed this PR.

In response to this:

Closing and reopening to trigger @poiana
/close

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

/reopen

@leogr: Reopened this PR.

In response to this:

/reopen

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


Build host lobby view

Would need web sockets for players and host in lobby?
Would the host have control over what screen each player sees? Do they have control over flow of game (i.e. they can select the round, then the question, and then all players see that specific question)...

https://socket.io/get-started/chat/

Host selects startTrivia, next, or back, and that sends a websocket event to update all players screens.
Players answer, which sends a websocket event to update a db of responses.
Players should be able to re-send answers as many times as they want.


Works in dev, does nothing in build

Vue.js version
2.0.3
Reproduction Link
http://jsfiddle.net/5sH6A/848/
Steps to reproduce

Execute the same code in build, "Badalejo component" won't appear + no errors will be shown

What is Expected?
Dev behaviour in build. (Display the newly added component in elements array)
What is actually happening?
The new component isn't shown.

Hi, thanks for filling this issue.
Can you clarify what you mean by 'build' and 'dev'? Are you using npm and a build system like webpack/browserify? If so, you need to provide a github repo for us to look into.

Yes, i'm using Vue's webpack kit.
In npm run dev works, while in npm run build doesn't.
Repo is private :(

If you're using vue's webpack kit, vue-loader would require vue's standalone version in dev, but runtime-only version in build. So I assume that's what caused you problem.
As you're using template option in components, you need to use vue's standalone version. Please check out the section here: http://vuejs.org/guide/installation.html#Standalone-vs-Runtime-only-Build

¡You're right!
An exception would be appreciated if template var is not supported and client is making use of it.

@toberorla Normally it would, but in build the exceptions messages are stripped and in dev it won't throw an exception.. I'll create an issue in vue-loader later.


Use black for format

Need to add to setup.cfg, pre-commit githook, and workflow fixing the pull request.

I will do #37 before this.


Update metadata validation and generation

This PR cleans up the logic to update and validate the metadata file.
It's mostly a cleanup after #2512 based  on the discussion of #2560 and the changes on #3149
Fixes #2560

We're thinking different ways to generate the metadata for a gadget, perhaps we can use GetGadgetInfo(), for this reason this PR only updates the logic to follow the changes on #3149 but doesn't introduce tests as it could be changed very soon again.

Before going on the full motivation of the new approach, let me provide a bit of history on the different steps we've taken. The metadata file was initially conceived to fully describe a gadget, it contained which tracers, snapshotters, toppers, structures and parameters were exposed by it. It was the source of truth and the implementation fully relied on the information contained on this file to work. Then #2512 changed it by relying more on the information contained in the BPF object, this leaded to discuss the role of the metadata file in #2560, where we agreed to make the GADGET_ macros mandatory. Then #3149 happened, making many parts (tracers, structures) of the metadata file useless.
Now, the motivation for having this new approach (where we rely less on the metadata file is). This is mostly taken from #2560 plus some additional thoughts I have:

There were two sources of information: (1) the ebpf object and (2) the metadata file. There was some complex logic to validate that both of them were aligned, also the fallback mechanisms when the metadata file was not present were confusing.
Having two ways to define the gadget (GADGET_ macros vs metadata) created confusion.
Forcing the user to create a metadata file adds more complexity to the gadget creation process. This file should be optional and only provide the "sugar" to make the gadget look better. For instance, if the user only wants to get json output, all column formatting options aren't needed.


Resizing the window to a height of 0 causes multiple consecutive error boxes to appear

Your local environment?
OS: Windows 10 Pro 64-bit Version 1903 (OS Build 18362.388)
Muon: https://github.com/ImVexed/muon/commit/06751b7aab03852d4980fb61c634b74c12b41a1f
What is happening?
Resizing the window to have no height causes multiple consecutive error boxes to appear.  It doesn't crash the program but it's frozen until you click through all the error boxes
What should happen?
No error boxes should appear
Any logs, errors or screenshots?
These are in the order they appear

This is likely upstream and will be reported, but for the time being, we can just do a check here to see if the values are getting too small.


Implement the IsEnabled property on individual segments.

This is a basic implementation.

I created this pull request as an easier way to not be able to select segments. However the segments cannot be selected if they are not displayed. I am currently working on PR #37 to create an ItemsSource of a list of strings that will become segments that can be created
in xaml or bound in the view model. Would you prefer that route over this PR?

Sounds great. I'm travelling at the moment, but will look at it more carefully asap.

I have the ItemsSource property implemented in all platforms. Should we close this PR and open another one? The code in this PR would still be implemented.

Thank you @rjantz3. Your PR have been merged and a new version 3.3.0 NuGet have been published.


Backprojecting a pixel coordinate to a ray in 3D

Hello!
I'm currently trying to cast a 2D bounding box from the front camera feed to the vehicle frame.
My approach is similar to the one in issue #66.
I've also tried using the camera_model that has been released, through waymo_open_dataset.camera.ops.py_camera_model_ops.image_to_world.
I keep hitting a wall however; the points that the pixels are backcast to are superposed, as seen in the following render that should be showing the lines of a pyramid going from the camera center to the projected points in the vehicle frame.
This makes it seem that there is just one line in the pyramid, when in fact there are 4. The camera is represented as the large axis object, and the small ones are the projected points I find from the 4 corners of a bounding box in the image.

Is py_camera_model_ops.image_to_world behaving as expected? When I add the depth information to the pixel coordinates I use 20, like I saw in the tests that were written here. It seems strange to me that all the pixels are projected to the same point. Am I doing something wrong here?
Here is the code I'm using:
import numpy as np
import tensorflow as tf

from waymo_open_dataset.camera.ops import py_camera_model_ops

def project_image_to_vehicle(image, calibration, image_coordinates):
    """Projects from image to global coordinate system.

    Arguments:
        image: image data from dataset_pb2
        calibration: Camera calibration details (including intrinsics/extrinsics).
        points: Points to project of shape [N, 3] in vehicle coordinate system.

    Returns:
        Array of shape [N, 3], with the latter dimension composed of (x, y, z).
    """

    # Populate camera image metadata. Velocity and latency stats are filled with
    # zeroes.
    extrinsic = tf.reshape(
        tf.constant(list(calibration.extrinsic.transform), dtype=tf.float32),
        [4, 4])
    intrinsic = tf.constant(list(calibration.intrinsic), dtype=tf.float32)
    metadata = tf.constant([
        calibration.width,
        calibration.height,
        calibration.rolling_shutter_direction,
    ],
                            dtype=tf.int32)
    camera_image_metadata = list(image.pose.transform)
    camera_image_metadata.append(image.velocity.v_x)
    camera_image_metadata.append(image.velocity.v_y)
    camera_image_metadata.append(image.velocity.v_z)
    camera_image_metadata.append(image.velocity.w_x)
    camera_image_metadata.append(image.velocity.w_y)
    camera_image_metadata.append(image.velocity.w_z)
    camera_image_metadata.append(image.pose_timestamp)
    camera_image_metadata.append(image.shutter)
    camera_image_metadata.append(image.camera_trigger_time)
    camera_image_metadata.append(image.camera_readout_done_time)
    # camera_image_metadata = list(vehicle_pose) + [0.0] * 10

    # Perform projection and return projected image coordinates (u, v, ok).
    return py_camera_model_ops.image_to_world(extrinsic, intrinsic, metadata,
                                            camera_image_metadata,
                                            image_coordinates).numpy()

def cast_pixels_to_ray(bbox: np.ndarray, calibration, image):
    """Cast the bbox to a plane in the vehicle frame
    Arguments:
        bbox [array]: Array of shape (4,2) representing 4 pixel coordinates in the image
        calibration: calibration proto for the given camera
        image: image proto for the given image
    Returns:
        C [array]: Position of the camera in the vehicle frame
        projected_pts [array]: Array of shape (4,3) representing a point along the ray a pixel can be backcast to.
    """
    intrinsic = np.array(calibration.intrinsic).reshape(3,3)
    extrinsic = np.array(calibration.extrinsic.transform).reshape(4,4)
    vehicle_to_image = np.linalg.inv(extrinsic)
    # Homogeneous transform from lidar to cam coords:
    # [R|-R@C] where R is the rotation matrix and C is the center of camera
    R_h = vehicle_to_image[:3,:4]
    # Projection matrix, where K is the intrinsic transform:
    # P = K@[R|-R@C] = [M|-M@C]

    # Axes transform
    tr = np.array([
        [0.0, -1.0, 0.0],
        [0.0, 0.0, -1.0],
        [1.0, 0.0, 0.0]
    ])

    # The projection from vehicle frame to image frame is
    P = intrinsic @ tr @ R_h

    # Center of camera:
    # C = -M^-1 @ p_4 where M=K@R and p_4 is 4th column of P
    C = -np.linalg.inv(P[:3, :3])@P[:,3]

    # This is what I would use to transform pixels to the vehicle frame
    # Not using this because the camera model has further considerations
    backproject = np.linalg.pinv(P)

    # Is it safe to assume that any depth value can be used?
    bbox = np.insert(bbox, 2, values=np.array([20,20,20,20]), axis=1)
    projected_pts = project_image_to_vehicle(bbox, calibration, image)

    return C, projected_pts

Thanks for reporting the issue! I'll investigate and share an update in about a week.


[chip-test, keymgr] Add sequence to test changing OTP root key

Description
Spin-off from the comment https://github.com/lowRISC/opentitan/pull/17739#issuecomment-1487701763.
#17739 removed dynamic latching of OTP root key during block-level keymgr testing. In order to cover the case where OTP root key changes (which should not normally happen), we should write a direct sequence for this.

Duplicate of #17773, so closing this one.

Opps, my bad.. sorry I did not see this one.. Thanks @ballifatih

No worries @cindychip, we can use the other issue. Should we label the other issue with Type:FutureRelease and Triaged so that it is not in M2.5 bucket? Or do you think this should be handled before tape out?


Entering the characters <? blanks the row and terminates a row ending

To reproduce:
Edit a slick cell or update your data set to contain the characters <?
Render the grid.
So far this is the only instance that I have seen that causes the grid to break.

Fixed.

Is there an option to specify the default formatter for all columns?
In some places I intentionally put HTML code into the cells, so now I have to provide an "empty" formatter for each such column. For all other columns (where my content was already properly sanitized) I suffer the additional overhead of the replace call (which probably does not matter, but still).
Personally I'd prefer the old default, with the option of specifying a different default.

Cool, thanks for the quick response!


invalid_grant if request readonly instead of readwrite

Hi,
I followed the authentication instructions as described in the readme. However, I changed the requested permissions to request onedrive.readonly instead of onedrive.readwrite since I only need to read files (see [https://dev.onedrive.com/auth/msa_oauth.htm]).
However, when I request readonly permissions, I get the exception: Exception: invalid_grant.

For me, it gives the same error also with files.readwrite.

Thank you for reaching out and for your patience. This SDK is being officially deprecated. See #209 for more information


VM Data needs update

[Enter feedback here]
This page does not align with what is in Azure from a VM size name  perspective.
Also basic VMs option in portal do not have details on these pages.
Standard DS3 v2 (4 vcpus, 14 GiB memory)
is where in these pages?
How may NICs are available per are not in the portal.  Nor is total throughput.
The max bandwidth numbers on this page do not say if it is per NIC or combined.
-Ken

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

ID: b681fb36-d142-204e-85a7-0ab5f86edc75
Version Independent ID: f71468a6-899e-5c3d-044f-606fca3d4c88
Content: Dv2 and DSv2-series - Azure Virtual Machines
Content Source: articles/virtual-machines/dv2-dsv2-series.md
Service: virtual-machines
Sub-service: vm-sizes-general
GitHub Login: @joelpelley
Microsoft Alias: jushiman

Thanks for brining this to our attention. We will investigate it further and update you shortly.

@ktleach - Standard DS3 v2 (4 vcpus, 14 GiB memory) is mentioned right on the document.
Can you elaborate more on this question - This page does not align with what is in Azure from a VM size name perspective ?

@ktleach - Did you get a chance to look at the above response? Please provide us more details on that. Thank you.

@ktleach - I hope the above response on Standard DS3 V2 answered your question.
At this moment, Since there is no doc update required, We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update to embedded_graphics with prelude

Embedded graphics got a prelude in jamwaffles/embedded-graphics@c5b8eb36425b172cab7b3d33b045b1ef8f71c3bd.
This allows us to fix a lot of the import noise for using embedded_graphics. I've also removed the embedded_graphics dependency from your terminal demo @therealprof.
Some rustfmt stuff snuck in as well, mostly item ordering.

Woohoo!


[BEAM-6242] Fix Portable WordCount PreCommit by caching environment

The WordCount job assumes a shared file system between the different write
transforms. This is not guaranteed if multiple containers are used. Environment
caching ensures that the container is shared.
Post-Commit Tests Status (on master branch)

Lang
SDK
Apex
Dataflow
Flink
Gearpump
Samza
Spark

Go

---
---
---
---
---
---

Java

Python

---

---
---
---

CC @angoenka @tweise

Looks like that fixed the Portable Python PreCommit.

Run Portable_Python PreCommit

I would prefer we change one thing at a time. There wasn't any change to the cache millis in previous PR and I don't see why this would make a difference. There is no need to guess though, running the test repeatedly with the PR phrase should provide a signal.

The caching is the only fix here.
Parallelism was just added to avoid too much concurrency on Jenkins were resources are limited. Parallelism is auto-set form the number of available cores in local execution mode.

Please see PR description of why the caching change was made.

2 runs passed. Running again to verify.

Run Portable_Python PreCommit

As I wrote above I wanted to include it for build consistency and to limit resource usage when running with Jenkins. I get your point. I can remove it although I think it makes sense to add it in this context.
The regression is likely caused by the other PR having removed the worker parallelism in the SDK Harness. So registration will now be deferred where it was done immediately beforehand.

OK, can we change parallelism to 1 then and make it same for batch and streaming?
I'm slightly concerned that we don't understand how the environment caching suddenly becomes an issue (remember we had added that even before the pre-commit job). It wasn't run in the CI though, and perhaps it is just a matter of jobs running slower sometimes (especially with higher parallelism and so the cache timeout hits before completion)?

Revert for change that introduced flakiness: https://github.com/apache/beam/pull/7304

OK, can we change parallelism to 1 then and make it same for batch and streaming?

Why change it to 1? Wouldn't that be a too restrictive?

I'm slightly concerned that we don't understand how the environment caching suddenly becomes an issue (remember we had added that even before the pre-commit job).

The scheduling issues are still unsolved. So any change that affects the scheduling will cause flakiness. On the upside, it helps us to be more aware of these problems.

Closing since flakiness has been resolved by #7304.


Migrate Testing from Jest to Vitest (#27)

Migrate Testing from Jest to Vitest (#27)
:recycle: Current situation & Problem
As described in #27, vitest is a more modern and faster testing framework.
:gear: Release Notes

Added vitest
Removed jest

📚 Documentation
This Pull Request migrates Jest to Vitest according to the official vitest documentation and the Next.js testing guide.
The packages:

@types/jest
jest
jest-environment-jsdom
ts-jest

have been removed
:white_check_mark: Testing
Before
$ npm run test
...
 PASS  app/page.test.tsx
  Home Component
    ✓ renders the Stanford Biodesign Digital Health Next.js Template heading (92 ms)
    ✓ renders the Stanford Biodesign Logo (6 ms)

-------------------------------|---------|----------|---------|---------|-------------------
File                           | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
-------------------------------|---------|----------|---------|---------|-------------------
All files                      |     100 |       75 |     100 |     100 |
 app                           |     100 |       75 |     100 |     100 |
  page.tsx                     |     100 |       75 |     100 |     100 | 19
 packages/example-package/dist |     100 |      100 |     100 |     100 |
  index.js                     |     100 |      100 |     100 |     100 |
-------------------------------|---------|----------|---------|---------|-------------------
Test Suites: 1 passed, 1 total
Tests:       2 passed, 2 total
Snapshots:   0 total
Time:        3.294 s
Ran all test suites.

After
$ npm run test
...
 ✓ app/page.test.tsx (2)
   ✓ Home Component (2)
     ✓ renders the Stanford Biodesign Digital Health Next.js Template heading
     ✓ renders the Stanford Biodesign Logo

 Test Files  1 passed (1)
      Tests  2 passed (2)
   Start at  21:47:52
   Duration  1.77s (transform 86ms, setup 0ms, collect 385ms, tests 103ms, environment 683ms, prepare 100ms)

 % Coverage report from v8
------------------------------|---------|----------|---------|---------|-------------------
File                          | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
------------------------------|---------|----------|---------|---------|-------------------
All files                     |   74.46 |    66.66 |   66.66 |   74.46 |
 app                          |      60 |       50 |      50 |      60 |
  layout.tsx                  |       0 |        0 |       0 |       0 | 1-28
  page.tsx                    |     100 |      100 |     100 |     100 |
 packages/example-package/src |     100 |      100 |     100 |     100 |
  index.ts                    |     100 |      100 |     100 |     100 |
------------------------------|---------|----------|---------|---------|-------------------

Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

[x] I agree to follow the Code of Conduct and Contributing Guidelines.

@ThomasKaar Thank you for the addition and taking a look at the issue!
I have requested a detailed review from @arkadiuszbachorski.
Looking at the PR at a high level, it seems like the coverage report you detail above is also including js files and reports a 0% test coverage for the TS files wich might not be correct.
It might make sense to take a look at some of the chances and mechanisms we made in https://github.com/StanfordBDHG/ENGAGE-HF-Web-Frontend which seems to properly report some TS test coverage despite some elements that we could improve there as well.

Thanks for the brief review!
I reduced the scope of the coverage analysis similar to https://github.com/StanfordBDHG/ENGAGE-HF-Web-Frontend while also including js files with sourceMap enabled so the ts-file can be properly mapped to the js-file in the coverage analysis (I updated the test plan accordingly).
Moreover, I also added licensing information to the newly added vitest.config.mts and ran npm run lint:ci locally to ensure it is working properly

Thank you @ThomasKaar; greatly appreciated!
Just started the builds and I can sync with @arkadiuszbachorski about the next steps 👍


--device option not passed down to tiny-cuda-nn

nesvor has the option --device to specify which GPU is to be used by nesvor. However, the GPU selection is not passed down to the tiny-cuda-nn functions, which will always attempt to use GPU#0.
We have a machine with 2 GPUs. GPU#0 is currently being used, so we try to run nesvor --device 1. However, the following exception occurs:
Traceback (most recent call last):
  File "/opt/conda/bin/nesvor", line 8, in <module>
    sys.exit(main())
  File "/opt/conda/lib/python3.10/site-packages/nesvor/cli/main.py", line 23, in main
    run(args)
  File "/opt/conda/lib/python3.10/site-packages/nesvor/cli/main.py", line 48, in run
    getattr(commands, command_class)(args).main()
  File "/opt/conda/lib/python3.10/site-packages/nesvor/cli/commands.py", line 75, in main
    self.exec()
  File "/opt/conda/lib/python3.10/site-packages/nesvor/cli/commands.py", line 162, in exec
    model, output_slices, mask = train(input_dict["input_slices"], self.args)
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/train.py", line 36, in train
    model = NeSVoR(
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/models.py", line 309, in __init__
    self.build_network(bounding_box)
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/models.py", line 350, in build_network
    self.inr = INR(bounding_box, self.args, self.spatial_scaling)
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/models.py", line 147, in __init__
    self.encoding = build_encoding(
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/models.py", line 48, in build_encoding
    raise e
  File "/opt/conda/lib/python3.10/site-packages/nesvor/inr/models.py", line 39, in build_encoding
    encoding = tcnn.Encoding(
  File "/opt/conda/lib/python3.10/site-packages/tinycudann/modules.py", line 315, in __init__
    super(Encoding, self).__init__(seed=seed)
  File "/opt/conda/lib/python3.10/site-packages/tinycudann/modules.py", line 161, in __init__
    initial_params = self.native_tcnn_module.initial_params(seed)
RuntimeError: CUDA error: out of memory
CUDA kernel errors might be asynchronously reported at some other API call,so the stacktrace below might be incorrect.
For debugging consider passing CUDA_LAUNCH_BLOCKING=1.

I used nvtop to monitor GPU usage during the runtime of NeSVoR.

nesvor started around -110s
nesvor crashed around -60s
we can observe a bump in GPU0 memory consumption right before nesvor crashes

Currently, the tinycudann modules are first allocated on the default GPU (cuda:0) and then moved to the desired device, e.g., (cuda:1). This won't work if cuda:0 has no enough memory. So I need to change the default GPU before creating modules.

Another solution (which is actually recommended by PyTorch) is to set the environment variable CUDA_VISIBLE_DEVICES='1' and then run the algorithm with device=0.


 In particular, the first query after running the program is too slow. In ssmm it works fine. So it doesn't seem to be a DB or query problem. I've tried reinstalling, but nothing changes.
Azure Data Studio version: azuredatastudio 1.40.2 (661384637db384fe5d4e6224069adbe708580b16, 2022-12-22T22:17:02.658Z)
OS version: Windows_NT x64 10.0.19043
Restricted Mode: No
Preview Features: Enabled

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz (8 x 2803)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
15.80GB (5.90GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (5)

Extension
Author (truncated)
Version

admin-pack
Mic
0.0.2

agent
Mic
0.49.0

dacpac
Mic
1.12.0

import
Mic
1.5.4

profiler
Mic
0.12.2

This issue is resolved in the latest insiders build, please give it a try.
Closing as resolved.


Spawn update coro directly through dispatcher

What was changed

Spawn update coro directly through dispatcher
Why?

Calling Go/GoNamed with a context from outside the workflow will fail
because the context doesn't have a handle to dispatcher state.
Checklist

Closes

n/a

How was this tested:

Defect found via sdk-features test for update which will land soon

Any docs updates needed?

No

[...] could have used the root context to start the go named

Do you mean the workflow definition's rootCtx? That's what I was previously using but didn't work. I'd prefer to use GoNamed if you think we can figure out the right Context to use.

My mistake, I thought rootCtx was the same ctx we gave to the user. Ignore me.


ci_view: Fix screen freeze

After the tcell/v2 update, any key press during lab ci view results
in a lock up. It is unclear whether the changes in input handling on
the tcell side are intentional, but we can address the issue by making
the channel that notifies about input events asynchronous and ensure
that we don't overrun its queue.
Fixes #538

@davinkevin does this fix the freeze / crash you mentioned in #406

@davinkevin does this fix the freeze / crash you mentioned in #406

Yeah, this is working well now 👍. So, you can forget my comment in #406.
BTW, I will use the compiled binary I have because it has a lot of fixes and this is way simpler to use now (especially on the CI view…).
Thank @zaquestion && @fmuellner 😉

Yeah, this is working well now 👍. So, you can forget my comment in #406.
BTW, I will use the compiled binary I have because it has a lot of fixes and this is way simpler to use now (especially on the CI view…).
Thank @zaquestion && @fmuellner 😉


[Bug] charts not always sync the axisPointer

Version
5.4.3
Link to Minimal Reproduction
https://codesandbox.io/s/echarts-charts-sync-issue-z4r2qw
Steps to Reproduce
hover on the last chart on the list, you cant see that the sync of the axisPointer works great, but when hovering on the other charts, the last chart doesn't display the axisPointer most of the time.
Current Behavior
I'm trying to create a couple of charts that will be synced (only axisPointer for now).
it does not always work and I don't understand why, for example when hovering the line & bar charts, the last chart in the list is not displaying the axisPointer, but when hovering the last chart i see the axisPointer on all charts
Expected Behavior
i want to be able to sync the axisPointer when hovering on one chart to others, including the custom one
Environment
- OS: Mac OS x Monterey
- Browser: 115.0.5790.114
- Framework<EMAIL_ADDRESS>
Any additional comments?
appreciate any help with that
thank you

Please make an effort to create Minimal Reproduction code, otherwise the chance of getting traction on the issue is minimal.
Minimal Reproduction means preferably straight Javascript code shared through editable examples like this one.
Using React or Angular frameworks is fine, provided that code is short and relevant.
Dumping entire applications is counterproductive since reviewers need to spend their time doing specialized debugging. This is not meant to be used for Github issue resolution.

last chart in the list is not displaying the axisPointer

your last chart is a custom image chart, which I think cannot be connected to the others.
Eventually a core developer could give a definitive answer to that.

@Ovilia i've created the issue with a demo

@spiral2k Your code has error. BTW, please make it minial and use this template instead.


Fix Readme

Make Readme up-to-date with new changes

first one

This is still open

Updated first half.
Additional update to link the proper names to their github pages would still need to be done.

https://github.com/joschw01 - Joe Schweiss

Tom Henehan-tom2470

Dan O'Brien
dobnu

Mohammed Shati
Moshati1315
https://github.com/Moshati1315

Philip Tran
Phitran-neu
https://github.com/Phitran-neu

Mitch Hornsby
https://github.com/mhorns

Peter Sternhagen
https://github.com/petersternhagen

Jayati Samar
smr-j
https://github.com/smr-j


Warning: Function det has the same name as a MATLAB builtin.

Warning: Function det has the same name as a MATLAB builtin. We suggest you rename the
function to avoid a potential name conflict.
My computer is windows8.1 Matlab R2014a

Hi, thanks. I would recommend avoiding using the ‘noprefix’ version of the functions (when calling vl_setup). It is there for (very old) legacy reasons, but it is much preferable to avoid it for exactly such potential issues and simply call all the function with the vl_ prefix.

On 9 Jan 2016, at 07:39, Kai Li<EMAIL_ADDRESS>wrote:
Warning: Function det has the same name as a MATLAB builtin. We suggest you rename the
function to avoid a potential name conflict.
My computer is windows8.1 Matlab R2014a
—
Reply to this email directly or view it on GitHub https://github.com/vlfeat/vlfeat/issues/115.

I am getting same error file using vl_setup in mac OS and Matlab 2016 and how can we avoid using noprefix version.


.epub not found

after generation i can`t find where epub is  saved or saved at all :D waste of my tokens  damn :D

Are you using Colab? If so, open the filesystem in the sidebar and it should be there!

Ah, this might be the problem... so on Colab, typically, new files are stored in the content folder.
So adjust this part of the code:
for i, image in enumerate(data["artifacts"]):
      with open(f"/content/cover.png", "wb") as f: # replace this if running locally, to where you store the cover file
          f.write(base64.b64decode(image["base64"]))

and this part of the code:
create_epub(title, 'AI', chapter_titles, '/content/cover.png')

Change /content/cover.png to whatever makes sense for your filesystem.

I already disabled cover generation because it got already cover I want to put on.

hmm, the next thing you can try is modifying epub.write_epub(f'{title}.epub', book) to specify the directory.

ou yeah now it saves as needed thanks :)

@MartinAbilev If your problem is solved, don't forget to close the issue.


GIT Dependency Infinite Loop

If I give a dependency a key that doesn't match the package name in setup.py, it will loop indefinitely at poetry/mixology/version_solver.py:77, outputting the selecting message like so:
my-package/setup.py
setup(
  package_name='package', # Note: differs from key 'my-package' in pyproject.toml
  version='0.1',
  ...
)

my-main-project/pyproject.toml
...
my-package = { git = "https://github.com/belzoni/my-package", branch = "master" }
...

$ poetry lock -vvv
...
1: selecting my-package (0.1 6fb5254)
1: selecting my-package (0.1 6fb5254)
1: selecting my-package (0.1 6fb5254)
...

However, if I change package_name='my-package' in setup.py, all is good. Leaving this here as a bug report for anyone else with this problem.

How do you expect poetry to know that my-package is satisfied by package? It should likely not loop forever, but it feels like this is somewhat expected.

The name of your dependency must match the name of the package you are trying to install. This is a requirement for git, file and directory dependencies.
But like @bertjwregeer said, this should not cause an infinite loop but rather raise an error to warn the user that there is something wrong.

I agree. I was a bit dubious calling it a 'bug', and was going to suggest it be explicitly documented. But also, yes, it shouldn't fail in this way.

The infinite loop should no longer be a thing in the latest release. Poetry will now warn you about the package name difference.


Handshake and peers fix

Fixes #458, MaxPeers handling and some other related things.

@codecov is sooooo dumb...

@codecov is sooooo dumb...

welcome to the club!


Add documentation for using HWI with Bitcoin Core

From https://gist.github.com/achow101/a9cf757d45df56753fae9d65db4d6e1d

Addressed comments. Also added to readme.

Removed 14689 from the list of PRs as that was merged

ACK c1b1e08

@Sjors @achow101 so I just got around to importing all my trezor addresses.
seems to work great! One thing I noticed is that there doesn't seem to be a way
to get bitcoin-core to generate new addresses on a specific chain?
for example:
$ bitcoin-cli -rpcwallet=trezor getnewaddress "" bech32
bc1qnmhnqlam8d0q2g3q3ttkd3q044naedt55e33xq

$ bitcoin-cli -rpcwallet=trezor getaddressinfo bc1qnmhnqlam8d0q2g3q3ttkd3q044naedt55e33xq | jq -r .hdkeypath
m/49'/0'/2'/0/10

seems in indiscriminately choose the bip49 path instead of the intended bip84.
Might be good to note this as it might trip up people...

@achow101 I did importmulti on the output of these commands:
hwi getkeypool --wpkh --keypool 0 1000
hwi getkeypool --wpkh --keypool --internal 0 1000
hwi getkeypool --sh_wpkh --keypool 0 1000
hwi getkeypool --sh_wpkh --account 1 --keypool 0 1000
hwi getkeypool --sh_wpkh --account 2 --keypool 0 1000
hwi getkeypool --sh_wpkh --internal --account 1 --keypool 0 1000
hwi getkeypool --sh_wpkh --internal --account 2 --keypool 0 1000

I'm guessing I could create two separate wallets, one for the wpkh keypool and the other for the sh_wpkh keypool? does that make sense?

I'm guessing I could create two separate wallets, one for the wpkh keypool and the other for the sh_wpkh keypool? does that make sense?

Yes, you could do that. However, because Bitcoin Core does it's address types based on a runtime command and not a wallet setting, your calls to getnewaddress will need to be followed by the correct address type for that wallet, otherwise you may get the wrong address type. This issue is due to how Bitcoin Core handles public keys and addresses. Unfortunately it cannot be resolved without overhauling the wallet, which is a work in progress, but will take a long time.


Relay works very limited

I have my own LNBits instance and I have specified a lot of relays (from admin account of course). Then I specified only my relay based on your extension in the Nostr client. But because I see that he does not broadcast / receive all the events. For example, inside Amethyst client for a profiles there don't load user profiles (avatars aren't shown) and sending posts doesn't work. Is this normal for this version (that is, it is still raw and not working)? Or should everything work?

Experiencing something similar. When I remove all my relays from my client such that my only relay is the LNBits client, I don’t see most of my followers’ notes and events, and my follower count goes way down. I wonder if the problem is between my keyboard and chair?

It's likely that especially social clients will have weird issues with this extension. It's very hard to predict how clients will react when they get their EOSE events. Some seem to work fine while others don't.

yep, same here, been on amethyst (android) all week and without some extra backup relays, I'd have few to none posts coming through.  Time to read the code base and NIPs, I guess


serviceGroups.list() does not return serviceLevels

Working on the Rates at checkout I have noticed that this sdk does not return serviceLevels when using serviceGroups.list().
The only result is [ {}, {} ] and number of {} depends on the number of shipping options set in Rates at checkout.
On the other hand, direct REST call mentioned here: https://docs.goshippo.com/shippoapi/public-api/#operation/ListServiceGroups returns service levels without a problem.

@radoslaw-sz Thanks for opening up an issue. Do you mind sharing the exact response you're seeing?
Are you seeing an array with empty {}'s (with no service levels entirely) or are the service levels you're expecting to see missing?

hi @jfriedr
as an example, this code:
    const serviceGroups: ServiceGroup[] = await this.shippoClient.serviceGroups.list();
    console.log(serviceGroups[0].serviceLevels);

prints this:
[ {}, {}, {} ]

while on the REST API level, this call:
https://api.goshippo.com/service-groups
returns this:
[
    {
        "description": "next shipping option desc",
        "flat_rate": "10",
        "flat_rate_currency": "USD",
        "free_shipping_threshold_currency": null,
        "free_shipping_threshold_min": null,
        "is_active": true,
        "name": "next shipping option",
        "object_id": "08cbe68eb6ff4155b800f0227fc1ef9a",
        "rate_adjustment": 0,
        "service_levels": [
            {
                "account_object_id": "5f6bd9f4915c4f99a1f942ed0adb3f92",
                "service_level_token": "canada_post_expedited_parcel"
            },
            {
                "account_object_id": "5f6bd9f4915c4f99a1f942ed0adb3f92",
                "service_level_token": "canada_post_expedited_parcel_usa"
            },
            {
                "account_object_id": "5f6bd9f4915c4f99a1f942ed0adb3f92",
                "service_level_token": "canada_post_international_parcel_surface"
            }
        ],
        "type": "LIVE_RATE"
    },
    {
        "description": "standard description",
        "flat_rate": "10",
        "flat_rate_currency": "USD",
        "free_shipping_threshold_currency": null,
        "free_shipping_threshold_min": null,
        "is_active": true,
        "name": "Standard Shipping Option",
        "object_id": "0f5db9d8a7674c35a64c641ba3df85d7",
        "rate_adjustment": 0,
        "service_levels": [
            {
                "account_object_id": "5f6bd9f4915c4f99a1f942ed0adb3f92",
                "service_level_token": "canada_post_tracked_packet_international"
            }
        ],
        "type": "LIVE_RATE"
    }
]

+1 Same

@radoslaw-sz, @jbool24
Please use the newest version and let us know if you still see any issues.
Thanks!


Connectors: make the Table Explorer connector-specific

This PR sets us up to add table/bucket discovery for multiple connectors at once.
This PR:

Reframes the "Tables" Explorer as a "Connector" Explorer
Lists out each connector in the project (but actually, for now, only shows the OLAP connector)
Nests the existing TableExplorer within a connector entry

Next, we will add support for browsing buckets from connected object stores and for browsing tables from connected non-OLAP databases (e.g. Postgres, BigQuery, Snowflake).

LGTM


add option with timeout for specific func.

Codecov Report

Merging #18 (481e3e3) into main (26321ea) will decrease coverage by 0.50%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##             main      #18      +/-   ##
==========================================
- Coverage   99.42%   98.92%   -0.51%
==========================================
  Files          10       10
  Lines         350      371      +21
==========================================
+ Hits          348      367      +19
- Misses          2        4       +2

Impacted Files
Coverage Δ

waitgroup.go
92.85% <88.23%> (-7.15%)
:arrow_down:

panic.go
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Hi @aryehlev! Thanks for the PR. Unfortunately, we don't plan to accept the contribution of any features like this because of the reasons described here.
Specific to this PR, assuming you didn't intend for GoWithContext() to block until completion, spawning a goroutine with GoWithContext would allow the goroutine to survive after the (*WaitGroup).Wait() has returned, which means any panics in that goroutine will be ignored.


Add a trim edges feature

The convolution process currently leaves edge effects.  We should explore if we can reduce edge effects with some clever kwargs in np.convolve.  But we should also just have a .trim_edges feature.

We could create a .trim_edges by just having it be syntactic sugar to a .truncate call and just feeding it the existing wavelength limits, shrunk down by 5 Angstroms or so on either side to chop off edge effects. Thoughts?


[Vuetify] Multiple instances of Vue detected

Version
2.6.3
Reproduction link
https://github.com/begueradj/bugs/tree/master/nuxtVuetifyJest
Steps to reproduce
const localVue = createLocalVue()
localVue.use(Vuetify)

What is expected?
I expect my test to pass without any error or warning messages.
What is actually happening?
The test passes but I receive this nasty red message:
^[[999D  console.error node_modules/vuetify/dist/vuetify.js:25038
    [Vuetify] Multiple instances of Vue detected
    See https://github.com/vuetifyjs/vuetify/issues/4068

    If you're seeing "$attrs is readonly", it's caused by this

The documentation clearly recommends to use localVue.use(Vuetify) so please do not suggest me to Vue.use(Vuetify) unless  if you are a superman able to convince me.
I am using Jest   Nuxt   Vuetify. You can try my github repository provided in the above link.
Billal Begueradj.

Thanks, but this issue belongs in the vue-test-utils repository.


Move checkout form to main settings page

Right now checkout form fields are set in every mailing rule. This should be configured separately from mailing rules since mailing rules are based on triggered events.
Remove the fields Show at Checkout and Checkout Label from the mailing rule settings page, and add these fields to a new section in the main settings page called Checkout Form (see image). Also add a Tags fields, which should have the default text Newsletter.

Added in v2.0 release (#26)


Fix order of operations in Tableau.call.doc

This is minor, but I figure it might save someone else some time.

I just signed the CLA, so not sure if it will require CI to rerun.

Everyone always edits the generated docs instead of the source.
If the multiplication is in circuit order, then that's the wrong way around. I should fix that and then also separately describe it as "before/after" so it's clearer.

This seems to be consistent with what is specified here.

Fixes https://github.com/quantumlib/Stim/issues/819

Moved to https://github.com/quantumlib/Stim/pull/822 so I could edit it to get it merged. Thanks for the fix!


ConfigMap connection refused

I have issues creating a new EKS cluster using master as ref.
I'm submitting a...

[x] bug report
[ ] feature request
[ ] support request - read the FAQ first!
[ ] kudos, thank you, warm fuzzy

What is the current behavior?
When creating a cluster, I get the following error:
Error: Post http://localhost/api/v1/namespaces/kube-system/configmaps: dial tcp <IP_ADDRESS>:80: connect: connection refused
As of 2 days ago, I was able to create clusters successfully so this is a new regression.
If this is a bug, how to reproduce? Please include a code sample if relevant.
module eks {
  source = "github.com/terraform-aws-modules/terraform-aws-eks?ref=master"
  cluster_name    = local.name
  cluster_version = var.eks_config.cluster_version
  subnets         = module.vpc.private_subnets
  vpc_id          = module.vpc.vpc_id

  cluster_endpoint_private_access = true
  write_kubeconfig = false

  node_groups = [
    for wg in var.eks_config.node_groups : {
      name                          = wg.name
      instance_type                 = wg.instance_type
      ami_id                        = data.aws_ami.eks_worker.id
      node_group_desired_capacity   = wg["desired_capacity"]
      node_group_max_capacity       = wg["max_capacity"]
      node_group_min_capacity       = wg["min_capacity"]
      additional_security_group_ids = join(",", [aws_security_group.eks_wg.id, aws_security_group.aurora.id])

      node_group_k8s_labels = {
        "instance-family" = substr(wg.instance_type, 0, 2)
      }

      tags = merge(
        var.tags,
        {
          "k8s.io/cluster-autoscaler/${local.name}" = true
          "Visibility"                              = "private"
        },
      )
    }
  ]
}

What's the expected behavior?
To be able to create a cluster successfully without errors. I have both private and public endpoint enabled.
Are you able to fix this problem and submit a PR? Link here if you have already.
Environment details

Affected module version:
OS:
Terraform version:

Any other relevant info

Issue was with my networking configuration.

@a7i I'm also seeing this error, what specific settings were causing this. I.e. my cluster is created successfully then this error occurs after the fact.

I came across the same issue, the problem was I didn't define provider "kubernetes" { in my main.yml.
Before:
module "eks" {
  source                        = "terraform-aws-modules/eks/aws"
  version                       = "12.0.0"
  cluster_name             = "minuscule"
  subnets                      = module.vpc.public_subnets
  vpc_id                         = module.vpc.vpc_id
  worker_groups_launch_template = [
    {
      name                             = "worker-group-1"
      instance_type              = "t3.small"
      asg_desired_capacity = 2
      public_ip                      = true
    }
  ]
}

To solve this issue:-
data "aws_eks_cluster" "cluster" {
  name = module.eks.cluster_id
}

data "aws_eks_cluster_auth" "cluster" {
  name = module.eks.cluster_id
}

provider "kubernetes" {
  host                   = data.aws_eks_cluster.cluster.endpoint
  cluster_ca_certificate = base64decode(data.aws_eks_cluster.cluster.certificate_authority.0.data)
  token                  = data.aws_eks_cluster_auth.cluster.token
  load_config_file       = false
  version                = "~> 1.11"
}

module "eks" {
  source                        = "terraform-aws-modules/eks/aws"
  version                       = "12.0.0"
  cluster_name             = "minuscule"
  subnets                      = module.vpc.public_subnets
  vpc_id                         = module.vpc.vpc_id
  worker_groups_launch_template = [
    {
      name                            = "worker-group-1"
      instance_type              = "t3.small"
      asg_desired_capacity = 2
      public_ip                      = true
    }
  ]
}

I would suggest seeing an example here as this may change with new TF version (https://github.com/terraform-aws-modules/terraform-aws-eks/tree/master/examples)


fix(tests): Fixed quaternion unit tests

Fixes https://github.com/ethz-asl/kindr_ros/issues/16

Ping

lgtm, @pfankhauser ?

Thanks @reinzor! I'd be happy to merge, could you quickly explain why you did this change? Did the unit tests not work for you?

The unit tests were indeed failing due to the quaternion accuracy.

Ok, not for us, weird. Thanks!

I referred to the wrong issue, should close #14


Status of bluez4

Bbappend for bluez4 directly creates symlinks for systemd service which should be handled through a systemd bbclass.
Also, bluez4 is considered obsolete in Poky since Jethro and is accessed from meta-oe:
http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#migration-2.0-removed-recipes
Are the bbappend additions (audio profiles patch and MediaPoint dbus interface config) something we want to keep configuring by default when using meta-bistro?

No reason to use bluez4 that I can see. I've been using Bluez5 a lot, and everything works.

I agree with @jonte, let's remove this.


Register vaildation failed

I have been using superlogin for almost 2 years without any issue. Over the last few weeks, the register functionality seems to have stopped working without any modification.
I have created a new vagrant box and set up couchdb, and superlogin from scratch, and am getting the very same error.
Using postman I get the following reponse when posting all values:
{     "error": "Validation failed",     "validationErrors": {         "email": [             "Email can't be blank"         ],         "username": [             "Username can't be blank"         ],         "password": [             "Password can't be blank"         ],         "confirmPassword": [             "Confirm password can't be blank"         ]     },     "status": 400 }
My script.js file looks like this:
var express = require('express');
var http = require('http');
var bodyParser = require('body-parser');
var logger = require('morgan');
var cors = require('cors');
var SuperLogin = require('superlogin');

var app = express();
app.set('port', process.env.PORT || 3000);
app.use(logger('dev'));
app.use(bodyParser.json());
app.use(bodyParser.urlencoded({ extended: false }));
app.use(cors());

app.use(function(req, res, next) {
   res.header("Access-Control-Allow-Origin", "*");
   res.header('Access-Control-Allow-Methods', 'DELETE,POST, PUT');
   res.header("Access-Control-Allow-Headers", "Origin, X-Requested-With, Content-Type, Accept");
   next();
});

var config = {
  dbServer: {
    protocol: 'http://',
    host: 'localhost:5984',
    user: '',
    password: '',
    userDB: 'sl-users',
    couchAuthDB: '_users'
  },
  mailer: {
    fromEmail<EMAIL_ADDRESS>    options: {
      service: 'Gmail',
        auth: {
          user<EMAIL_ADDRESS>          pass: 'userpass'
        }
    }
  },
  security: {
    maxFailedLogins: 3,
    lockoutTime: 600,
    tokenLife: 86400,
    loginOnRegistration: true,
  },
  userDBs: {
    defaultDBs: {
      private: ['defaultdbname']
    }
  },
  providers: {
    local: true
  }
}

// Initialize SuperLogin
var superlogin = new SuperLogin(config);

// Mount SuperLogin's routes to our app
app.use('/auth', superlogin.router);

app.listen(app.get('port'));
console.log("App listening on " + app.get('port'));

Same error, any word on this?

Okay, so first, this github's repo is different from what is downloaded through:
npm install --save superlogin@latest,
For whatever reason... If you have a local Redis and CouchDB server setup, download the repo directly and try running the tests.
Second, see if you have<EMAIL_ADDRESS>if so, there's a few things you have to change.
(Colin screwed-up his design-doc parsing by accident in that version.)
superlogin-master/test/ddocs/test.js:
module.exports = {
  test: {
    views: {
      mytest: {
        map: function (doc) {
          emit(doc._id);
        }
      }
    }
  }
};

superlogin-master/designDocs:
module.exports = {
  auth: {
    views: {
      email: {
        map: function(doc) {
          if(doc.email) {
            emit(doc.email, null);
          } else if(doc.unverifiedEmail.email) {
            emit(doc.unverifiedEmail.email, null);
          }
        }
      },
      username: {
        map: function(doc) {
          emit(doc._id, null);
        }
      },
      verifyEmail: {
        map: function(doc) {
          if(doc.unverifiedEmail && doc.unverifiedEmail.token) {
            emit(doc.unverifiedEmail.token, null);
          }
        }
      },
      emailUsername: {
        map: function(doc) {
          emit(doc._id, null);
          if(doc.email) {
            emit(doc.email, null);
          } else if(doc.unverifiedEmail.email) {
            emit(doc.unverifiedEmail.email, null);
          }
        }
      },
      passwordReset: {
        map: function(doc) {
          if(doc.forgotPassword && doc.forgotPassword.token) {
            emit(doc.forgotPassword.token, null);
          }
        }
      },
      session: {
        map: function(doc) {
          if(doc.session) {
            for(var key in doc.session) {
              if(doc.session.hasOwnProperty(key)) {
                emit(key, doc._id);
              }
            }
          }
        }
      },
      expiredKeys: {
        map: function(doc) {
          if(doc.session) {
            for(var key in doc.session) {
              if(doc.session.hasOwnProperty(key) && doc.session[key].expires) {
                emit(doc.session[key].expires, {key: key, user: doc._id});
              }
            }
          }
        }
      }
    }
  }
};

superlogin-master/lib/util: (Look for Object.keys(providers).forEach(function(provider) {)
  Object.keys(providers).forEach(function(provider) {
    ddoc.auth.views[provider] = {
      "map": ddocTemplate.replace(new RegExp('%PROVIDER%', 'g'), provider)
    };

And that should do it.
I'm not sure how active this repo is, but when I have time I'll submit a pull request, or possibly fork this.
Let me know if this helped, @georgemccann :)

Here's a fork with changes implemented: https://github.com/PhilLaFayette/superlogin

Having this issue with your fork @PhilLaFayette :
{
    "error": "Validation failed",
    "validationErrors": {
        "message": "[object Object]",
        "stack": "Error: [object Object]\n    at /home/james/Documents/proj/node_modules/superlogin/lib/user.js:71:15\n    at <anonymous>\n    at process._tickCallback (internal/process/next_tick.js:188:7)"
    },
    "status": 400
}

Hm. I will investigate tomorrow. I remember this cropping up.

I'm trying to understand whether Superlogin is well supported and whether I should use it in my app.
I've got the same issue "Registration validation failed" issue as noted here and it would seem like a critical issue that needs and immediate fix but the author isn't fixing this issue which was reported in  February 2018 and it's now December 2018....hmmm...not a good sign.
Maybe I should be looking for an alternative solution...Anyone know of one that solves the same problems but is properly maintained?

@PhilLaFayette,  since it would appear that you have fixed this issue in your clone and now that I know that Colin is not maintaining this project I'm interested in including your cloned version in my project (call it projectX).
I cloned your "fixed" version of Superlogin. Now I'm wondering how to actually include that into my project given I'm no longer using the NPM version that Colin posted. Thoughts on the best way to do this? Right now I've cloned your version of Superlogin into separate directory from projectX (where I would be invoking it).  I'm relatively new to Nodejs.
Seems like I should remove the superlogin dependency to the superlogin npm from my package-json file and then add an import statement that points to the directory containing the cloned version?  Thoughts?

@PhilLaFayette,  assuming what i've said above is correct...what file do I actually point to execute Superlogin and have it work now that I've cloned it?

Warning: I wouldn't use this in any live project at all. There's lots of npm vulnerabilities and using superlogin allowed a bitcoin miner to be installed on my server.
Someone has released a fixed version for this on NPM if you search for it. I can't remember the package unfortunately as I finished the project some time ago now.

Yikes!  Thanks for the heads up!!! Just curious...How did you detect the bitcoin miner (e.g., antivirus software?). Were there any obvious symptoms (e.g., significant server slowdown, etc.).
I noticed there were quite a few vulnerabilities noted after doing installation and I  used the "npm audit" (?) command to fix some of them but as is typically the case this doesn't fix all vulnerabilities.  I'll research and see what I can come up with.
Again, thanks for the heads up.
Regards,Jet
On Tuesday, December 18, 2018, 4:04:48 AM PST, georgemccann<EMAIL_ADDRESS>wrote:
Warning: I wouldn't use this in any live project at all. There's lots of npm vulnerabilities and using superlogin allowed a bitcoin miner to be installed on my server.
Someone has released a fixed version for this on NPM if you search for it. I can't remember the package unfortunately as I finished the project some time ago now.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

I use AWS and have cloudwatch on the go. The CPU usage started to hit 100% and crash the server after a couple of weeks of deploying the app.
The virus that was installed was particularly foul, as it was able to change it's name to stop you from killing the tasks. I had to destroy the server, and rebuild with the fixed version with updated npm packages.
I'd really look into alternatives to superlogin.

George,  thanks for the info.  I've already installed Superlogin...does that mean I'm already infected (bitcoin miner was in the Superlogin code or one of it's packages?) Or does the bitcoin miner exploit the "weaknesses" in some of the npm dependencies making my system open to attack? Thoughts?
I'm not familiar with any alternatives to Superlogin...but I guess I will have to start looking now.
FYI, when I did the the npm install it noted 22 vulnerabilities with the packages and ZERO of them could be automatically fixed via "npm audit fix".
If the vulnerabilities are not fixed (thus making it susceptible to attack) then I feel like this needs to be POSTED PROMINENTLY on Github (e.g., README) so others don't fall victim to it.  I was completely unaware of the threat until you said something.
Regards,
Jet
On Tuesday, December 18, 2018, 9:13:12 AM PST, georgemccann<EMAIL_ADDRESS>wrote:
I use AWS and have cloudwatch on the go. The CPU usage started to hit 100% and crash the server after a couple of weeks of deploying the app.
The virus that was installed was particularly foul, as it was able to change it's name to stop you from killing the tasks. I had to destroy the server, and rebuild with the fixed version with updated npm packages.
I'd really look into alternatives to superlogin.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

George,  (not sure if I already said this or not but..) I contacted Colin via twitter and said he was going to "try" and update Superlogin to at least address the open vulnerabilities.  Hopefully he will have time to do so.
On a related topic PhilLafayette created a clone in response to  the "Register validation failed" issue that you originally submitted. I tried the clone and I'm still having the same exact issues. Either his clone didn't fix the issue or I'm doing something wrong.  Do you happen to know how to get in touch with him? He seems to be a ghost...no email listed in gitHub, no obvious twitter address (Unless his side gig is giving jamaican cruiseship tourists tours of the island..IREE...LOL).
I know that his clone didn't address the outstanding vulnerabilities but I wanted to at least end on a superlogin highnote and be able to register a user...in the event that Colin doesn't address the vulnerabilities.  I've sunk so much time into Superlogin I'd like to have some inkling of success if I'm forced to abandon it.
Regards,Jet
On Tuesday, December 18, 2018, 9:13:12 AM PST, georgemccann<EMAIL_ADDRESS>wrote:

I use AWS and have cloudwatch on the go. The CPU usage started to hit 100% and crash the server after a couple of weeks of deploying the app.
The virus that was installed was particularly foul, as it was able to change it's name to stop you from killing the tasks. I had to destroy the server, and rebuild with the fixed version with updated npm packages.
I'd really look into alternatives to superlogin.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@PhilLaFayette FYI I tried the cloned version you built to correct this issue but it failed to correct the issue.  Did you actually test your fix?

@jetamartin This is the npm package I used https://www.npmjs.com/package/@sensu/superlogin
This one seems to be clean and stable and I haven't had any problems with it.

Hey @jetamartin,
hope you haven't lost all hope yet. I just found myself in the same situation that you were describing, where @sensu/superlogin throws the same validation error upon signup as the the current npm version of superlogin.
For me, installing @PhilLaFayette's version with
npm i https://github.com/PhilLaFayette/superlogin/tarball/master

fixed it. Hope it does for you as well, or some other person that stumbles upon this.

Hey Christoph,
Thanks for the followup...I actually did give up on Superlogin. I reached out to Colinskow (the author) via twitter in December to see if he had plans to fix Superlogin and he said he would try and fix it in December but I've seen nothing from him...which is a bummer. For now I'm rolling my own now. But if that falls through then I may revisit the version that you referenced.
Thanks again! Really appreciate the follow up.
Cheers,Jet
On Tuesday, February 19, 2019, 10:31:33 AM PST, Christoph Pahmeyer<EMAIL_ADDRESS>wrote:

Hey @jetamartin,
hope you haven't lost all hope yet. I just found myself in the same situation that you were describing, where @sensu/superlogin throws the same validation error upon signup as the the current npm version of superlogin.
For me, installing @PhilLaFayette's version with
npm i https://github.com/PhilLaFayette/superlogin/tarball/master
fixed it. Hope it does for you as well, or some other person that stumbles upon this.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@jetamartin have you found any solution. Here same issue tried all suggesion from comments.


Add more integration tests for corner cases

Test the endpoints with wrong parameters and see you still get the expected response.

[ ] Blocked on #119

With the test migrated to be more composer-like, org_id filter testing, and all 3 upload targets tested, I feel like we're in a pretty good spot atm.