Added first draft typing for Shepherd Tour library.

Not all overloads are fully typed out, but this should provide user with
some helpful intellisense and a few compile checks.
https://github.com/HubSpot/shepherd/

Missing test file.  Will resubmit properly.


Focus not returned to delete button if canceling Removal Safety Check dialog

On the /administrator views, focus is not returned to the delete button if the Removal Safety Check dialog is closed, address:

project
subject
badge
skill

PR: #1415

:+1:


DeleteFile GAP

This implementation is required as required upload event.
Please describe how to implement deleteFile ... on Fine Uploader example.
Especially explain WHY POST?
if ($options['enable_cancelation'] === true) {                 $progress = new Route(                     sprintf('%s/_uploader/%s/cancel', $options['route_prefix'], $type),                     array('_controller' => $service . ':cancel', '_format' => 'json'),                     array(),                     array(),                     '',                     array(),                     array('POST')                 );                 $routes->add(sprintf('_uploader_cancel_%s', $type), $progress);             }
I used URL POST /app_dev.php/_uploader/advert/cancel with default params
_method	DELETE qquuid bc2ba2d4-0303-495b-8c57-e7eb54bebaac

Ok found where was problem:
// routing.yml
oneup_uploader:
resource: .
type: uploader
methods: [DELETE, POST]

Please check the FAQs

Why didn't you implement the delete feature provided by Fine Uploader?

FineUploaders delete Feature is using generated unique names we would have to store in order to track down which file to delete. But both the storage and the deletetion of files are tight-coupled with the logic of your very own implementation. This means we leave the delete Feature open for you to implement. Information on how the route must be crafted can be found on the official documentation and on the blog of Fine Uploader.

You need to create a Controller and implement the deletion feature yourself. Unfortunately there is no way we can predict the type of deletion behaviour you need for your specific application. This is therefore out of scope for this bundle.
But basically you return a file id or entity id (or however your application works) back to the frontend uploader which will then know how to call a route that deletes this specific file. Take a look at the official Fine Uploader docs on this topic.
var uploader = new qq.FineUploader({
    deleteFile: {
        endpoint: '{{ path('your-delete-route') }}'
    }
});

Of course I wrote my own Controller.
The problem that people install this module and research code for delete files.
It's like bear + toilet. I spent time for install and explore this Bundle and will write own controller.


Data validator application

I've prepared a converter of MATLAB data files (used to provide data to DiviK) into our text format. No black box tests are provided, since it's just a runnable script and I would like to not to dig into mat-file internal binary format to mock it. White box testing (assertions) are supplied in the respective parsing functions. Converter works both for v7.3 and lower version files.
To test it more reliably, I've created a micro app just for validation of text data file format.

 Make python .mat converter


Is this project actively maintained?

Thanks for this project!
Spending a lot of time debugging gifted chat  - looking at alternatives..

Not fully active, currently only bug fixes if any.

Appreciate your reply!
I cloned and tried to run the example. Didn't  get it working. Can you please check this and offer a remedy? Seems like it's  environmental but I haven't seen this error before.

@ajp8164 Were you able to fix it?


the mask do not pay attention to the suffix permanent char

Hello guys
If I use the following code
<InputMask
  type="text"
  mask="999 €"
  maskChar=""
  alwaysShowMask={true}
  value={10}
/>

I expect to see an input with "10 €" display in it
instead I have "10"
I have the impression all the mask on the right is omitted

after having a look into the code, I notice we dpay attention only to the prefix permanent characters (getPrefix function into formatValue function)
maybe a kind of getSuffix function could help to format the field properly
but I do not master the project so, I can't tell :)

@F4b1n0u It's not about suffix itself, it's about masking values with variable length. While masking requires a lot of hacks and workarounds for different browsers, i'm trying to keep code as simple as possible and not implement things which can be easily done outside of react-input-mask.
With your case you can put div under your input and put there transparent span with input value + colored one with ' €' suffix.


standardized capitalization

Standardized capitalization for variant inspect inheritance, inheritance inside filter select, and consequence in variant panel

quarantest build successful. Demo link at
http://43db0004.quarantest.iobio.io

quarantest build successful. Demo link at
http://b8150dea.quarantest.iobio.io

quarantest build successful. Demo link at
http://78ad5b90.quarantest.iobio.io


chore(pkg): Fix module references

@nikpivkin could you take a look at reviewing this?

LGTM
Should we change the user in the workflow in this PR?

LGTM
Should we change the user in the workflow in this PR?

nice catch, I changed to aqua-bot.


Parse any .gitignore file found

See how ripgrep does this and then implement the same, add a --no-ignore option to the paste command to not do this.

After looking around it seems to be a better plan to:

Check if "git" exists on path.
Call "git check-ignore [paths]".
Filter out the paths that match.


upgrade nextjs 15

here https://nextjs.org/blog/next-15-rc#react-19-rc
fix type error
fix npm package mis in pnpm

@superlbr
Nextjs15 is still in the RC stage, and there are no significant feature additions that would greatly benefit morphic, so we want to proceed with the update cautiously. For now, I'll close this PR. Thank you for your contribution.


Incorrect change for Aurelia Import statement

Description
The results of beautification are not what I expect. I am writing for Javascript and in the Aurelia framework.
Expected Results
The beautified code should have looked like, all on one line:
import {inject} from 'aurelia-framework';

Steps to Reproduce

Add code to Atom editor
Run command Atom Beautify: Beautify Editor
This beautified code does not look right!

Debug
Here is a link to the debug.md Gist: https://gist.github.com/...
https://gist.github.com/JoshuaGarrison27/cbeb34720c6565a7b30b4bcdad237f7a

@JoshuaGarrison27 Would you mind resaving your debug gist from a .txt to a .md file.  It would really improve readability.

Sorry about that. Fixed the file extension.

I see the original and the resultant code sample in the debug.md file.  Would you mind also providing the desired result so that I can tell the maintainers of JS Beautify what to look for?

I did in the original issue post. Where else should I have put it?

You can put the desired code output directly into this thread.

@prettydiff : I believe it would be found at https://github.com/Glavin001/atom-beautify/issues/883#issue-144966851

The beautified code should have looked like, all on one line:

import {inject} from 'aurelia-framework';

@Glavin001 That is correct. I didn't add the entire code because that would cause additional confusion, IMO.

Adding @bitwiseman

I'm not sure I understand:
The input code was
import {
  inject
} from 'aurelia-framework';

That's valid.  There is nothing in the beautifier that will collapse that to one line at this time.

Thanks @bitwiseman
@JoshuaGarrison27 You can either open an issue at https://github.com/beautify-web/js-beautify/issues or change your beautifier to Pretty Diff in the Atom Beautify settings.


New version of presence sensor

Problem description
I have a zigbee presence sensor which has been working successfully for several months. So, I bought a second one for another room. On installing it, I can see that it's a slightly different version and ZHA doesn't create the entities for it. Both are TS0601 devices. The working one has manufacturer ID of _TZE204_ztc6ggyl, whereas the new (non-working) one is _TZE204_ijxvkhd0.
They are (or should be) functionally identical. I think that it just needs that new ID adding to the system?
Solution description
Add the new ID of the device alongside the existing one so that both are recognised.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

Device signature
Device signature
[Paste the device signature here]

Diagnostic information
Diagnostic information
[Paste the diagnostic information here]

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
You very helpfully did a very similar change for me a little while ago when I hit the exact same problem with a soil moisture sensor. I bought a second of these and, in the same way, the later one had a slightly different ID, despite being functionally identical.

Subsequent to this, I then ordered another one from the original supplier, expecting it to be the original model and, instead, it was yet another different one. This new one is
_TZE204_qasjif9e
As before, this should have the same functionality as the original with both presence and illuminance.

Subsequent to this, I then ordered another one from the original supplier, expecting it to be the original model and, instead, it was yet another different one. This new one is
_TZE204_qasjif9e
As before, this should have the same functionality as the original with both presence and illuminance.

Belay that! I have just installed 2023.12.2 and the latter one, at least, seems now to be working. I will check the first one ASAP.
Thank you to whomever fixed this!

I am also having issues with TS0601 by _TZE204_ijxvkhd0.  I loaded the .py quirk below and it doesn't even attach to the device.  No errors in logs.

class MmwRadarMotion(CustomDevice):
"""Millimeter wave occupancy sensor."""
signature = {
    #  endpoint=1, profile=260, device_type=81, device_version=1,
    #  input_clusters=[0, 4, 5, 61184], output_clusters=[25, 10]
    MODELS_INFO: [
        ("_TZE204_sxm7l9xa", "TS0601"),
        ("_TZE204_ijxvkhd0", "TS0601"),
        ("_TZE200_ar0slwnd", "TS0601"),
        ("_TZE200_sfiy5tfs", "TS0601"),
        ("_TZE200_mrf6vtua", "TS0601"),
        ("_TZE200_ztc6ggyl", "TS0601"),
        ("_TZE204_ztc6ggyl", "TS0601"),
        ("_TZE204_ztc6ggyl", "TS0601"),
        ("_TZE204_sxm7l9xa", "TS0601"),
        ("_TZE200_wukb7rhc", "TS0601"),
        ("_TZE200_hl0ss9oa", "TS0601"),
        ],


🌱 Tests: Fix data race failures

What kind of change does this PR introduce?
Fixes test failures

[x] PR title follows the guidelines defined in our pull request documentation

Does this PR introduce a user-facing change?
NONE

@raghavkaul  This is blocking other PRs from being merged. Can you please fix this?


Scrape more data from sawlog

The sawlog is a rich source of lots of data, but the Logstash script has to know how to parse it. It's all down to the grok statement which identifies fields to extract and defined their deliniators. Use grokdebug.herokuapp.com to help master your syntax. From there, the data can be emitted to CSV and loaded into Oracle.
Here's an example of something yet to build - when items are moved and deleted in the Catalog, it is all logged. What, who, and when. The Logstash grok currently scrapes this, but the data isn't included in th CSV output, nor loaded into Oracle.

Don't forget to submit a pull request for any changes to the code that would benefit others in the community!
You'll also find loading the data directly into Elasticsearch easier than redefining the Oracle table DDL and load script each time, since in Elasticsearch the 'schema' can evolve based simply on the data that Logstash sends to it.

So you mean there is no way to have the action has done in the logstash output?


Fix a typo in task.go

@hs0210 thanks for the PR.  Can you please sign your commit and force push with the proper DCO?

updated, PTAL.

LGTM


After first song plays, no more songs play until you start another queue

🧐 Have you read the FAQ and viewed similar issues?

[ ] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
Indonesia
What is your Spotify Plan?
Free
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>5.gabf054ab
- Windows: Windows 10 Pro 21H2 19044.2364
- PowerShell: 5.1.19041.2364

📝 Description

After the first song is finished, it stops until you skip the current track

...
📸 Screenshots

more information from the 1st question of the FAQ

I have the same issue. Clean re-installation did nothing.

Does this bug appear if you are using the original Spotify client?
Perhaps this bug is related to this, then try these steps:

Go to Settings > Audio quality and set the Streaming quality to High.

Scroll all the way down to Compatibility and disable hardware acceleration.

Don't know about original client but it is not present on web version(Firefox).
These steps didn't help.
I only started seeing bug last week, this behavior is not consistent though. I can only reproduce this bug like 80% of the times I restart spotify.

well, check it out in the original desktop version

I'll check in a few hours.
But apparently this bug only appears when I start a playlist and restart the app. This doesn't happen if I play single song from search or home and then restart.

So original desktop version(<IP_ADDRESS>5.gabf054ab) also has the same bug.
While reinstalling Spotx noticed that it was also installing the same version instead of the recommended version(<IP_ADDRESS>2.g24733a46).
Manually installed <IP_ADDRESS>2 and now everything works fine.


I cant edit trades, crash on my fabric server

I can edit trades, when i press enter with the command: /professions edi trader crash my server.
https://pastebin.com/9se6me27
this is de crash txt
ty

You must use different taterzens version, that combo of traders+taterzens is incompatible


Error on getMediasByTag()

Hi all
We became an Error if we install the latest version from Github. I download your source code and do "composer install".
If we call the line below we became an error
$medias = Instagram::getMediasByTag('zara', 50);
Error: Using $this when not in object context in InstagramScraper\Instagram::getMediasByTag() (line 392 of instagram-php-scraper/0.5.0/src/InstagramScraper/Instagram.php).
thank you for your help

if you install it from
composer require raiym/instagram-php-scraper
and use the generated autoloud then it works fine!


cron job not working

title, looks like dataset not updating

heroku cloud requires a different setup for cron jobs


Chris Reilly Spring Challenge User Interface

[x] Student should be able to describe and use semantic HTML tags to markup content
[x] Student should be able to demonstrate the use of CSS selectors to style markup
[x] Student should be able to demonstrate CSS specificity and inheritance to create and update styles
[x] Student should be able to identify and use all properties in the box model
[x] Student should be able to demonstrate CSS display properties to build user interface
[x] Student should be able to implement a CSS reset and understand why it’s important for cross browser development
[x] Student should be able to describe and understand that flexbox is a module
[x] Student should be able to demonstrate understanding of flex container properties in flexbox
[x] Student should be able to demonstrate understanding of flex item properties in flexbox
[x] Student should be able to explain why we use the command line interface (CLI), and demonstrate use of basic CLI commands.
[x] Student should be able to sufficiently explain what version control and Git are, and why as software engineers we use them.
[x] Student should be able to demonstrate an ability to fork and clone a repo.
[x] Student should be able to understand branching, and be able to create a branch locally.
[x] Student should be able to explain and properly utilize the git commands: status, add, commit, and push
[x] Student should be able to submit a Pull Request.

Great

Your app runs without any errors or warnings, good job!

There are some CSS styling artifacts showing up on your site.
Your home page and about page don't match the design file. Finish styling the pages and resubmit.
Try to include more detail in your answers to the questions. You missed answering several questions.

Images

Rating 1


Add links to article on messaging bridge pattern

Before selecting the "Create pull request" button:

Enter a meaningful title above^, using a prefix if necessary and keywords "New" or "Update" indicating the nature of changes.

Describe the summary, scope, and intent of this PR:

Now that the messaging bridge article was published, I found a couple of places that would benefit from a link to the article.

Insert links(s) to any related work item(s) or supporting detail:
https://learn.microsoft.com/en-us/azure/architecture/patterns/messaging-bridge

AFTER YOUR PR HAS BEEN CREATED, expand this section for tips and additional instructions.
These are common guidelines for contributions across the repos managed by the Cloud Architecture Content Team (CACT). Some repositories may have additional specific requirements that are not listed here.
Guidance for all contributors

Topic
Guidance

Draft PR
If your PR will be a work-in-progress for more than a day or two, select the Convert to draft link in the upper right of the page (under Reviewers) to change it to a draft. For future reference, you can also do this using the Create pull request button drop-down during PR creation.

ms.date metadata
Don't update an article's "ms.date" metadata property unless you've done a full freshness review of the content. A full freshness review includes changes required to correct or improve the full technical accuracy of the article.Don't update "ms.date" if you're doing targeted changes to improve non-technical aspects of the article, such as editorial quality, art improvements, article template alignment, etc.If you've changed any "ms.date" properties for work that wasn't part of full review for freshness, please reset them to their previous value.

Placement and linking
If you're creating a new article or articles, include updates to the related TOC.yml file to propose where the article(s) should be placed. Also consider other places within the document set where it would be beneficial to cross-reference and link to your new article(s).

PR build
After you open your PR, and for each successive commit that you push to your branch, the publishing platform will run validation on the files in your pull request. A summary of the build results for each file will be inserted inline into your pull request, which includes any build suggestions/warnings/errors. PRs cannot be merged until all build errors and most warnings are resolved.

Publishing
Following a successful merge, most repos publish to the live site at least once per (business) day, usually around 10am Pacific.

Additional resources
Learn.Microsoft.Com contributor guide

Additional guidance for private repos and internal contributors

Topic
Guidance

PR size
If your PR is more than ~5 lines of changes, or you'd like for the changes to go through editorial or larger review, open a contribution request at https://aka.ms/Contribution and include a link to the PR in response #8. Once it's processed, you'll be notified of the next steps.

PR title prefix
Select the Edit button to the right of the PR title if you need to revise it. The following prefixes are reserved for specific contribution types:[Quality Check] - maintenance work related to content quality (edit passes, art improvements, template alignment)[LinkFix] - recurring/adhoc PRs to correct link URLs[Pipeline] - new/updated contributor success pipeline content[WIP] - a work-in-progress draft requiring several days/weeks

PR preview
Following successful build of your PR, publishable files will also include Preview URL links to staged previews of your new/updated articles. Be sure to review these for verification of your intended contributions, or to send to other internal contributors for review.

PR sign-off (public repo)
If an article you own is updated in a public repo PR, you are responsible for sign-off. You will be automatically notified via email. The PR will not be merged until you've had a chance to review and sign-off.

PR sign-off (private repo)
After you've completed your proposed changes, addressed build warnings, and completed all review work, you can begin the sign-off process for review and merge:If your PR is in draft mode, remove "[WIP]" from the title and select Ready for review button at the bottom of the PR.Enter "#sign-off" in a new comment. This comment indicates that you're confident the work meets or exceeds Microsoft's standards for publication, and will trigger the review process.Your PR may be selected for initial review by the CACT. Following CACT review, you may receive questions or requests for additional changes. You should have initial feedback from CACT review within a few business days. If you have an urgent request or need to contact the team, please mention @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers in your PR and someone will get back to you. After CACT review is complete, a CACT #sign-off will be added.Final review/merge is done by the PR review team. The PR team may also respond with feedback, categorized as "Blocking" (requires action from you), or "Non-blocking" (to be addressed in a future PR).

Additional resources
Learn.Microsoft.Com internal contributor guideAuthoring templates: architecture-center-pr, well-architected-prTo contact the CACT use e-mail, or @mention our GitHub team in your PR comments using: @MicrosoftDocs/cloud-architecture-content-team-pr-reviewers

I understand one of the changes here might be in progress but wasn't sure so I included it just in case.

CACT #sign-off

merging


removed datadisk to allow scale after upgrade

What this PR does / why we need it:
When upgrading then scaling a cluster with v0.19.1 or the current master branch, the deployment fails because dataDisk.CreateOption for master nodes in the scale template is "empty" instead of "attach". This part of the template is not needed for scaling agent pools and can be removed.
Which issue this PR fixes: fixes #3478
Special notes for your reviewer:
I had help from @JackQuincy though he may not be able to help with this immediately. I will need more help with testing.
If applicable:

[ ] documentation
[x] unit tests
[x] tested backward compatibility (ie. deploy with previous version, upgrade with this branch)

Release note:

running tests at https://jenkins.azure-containers.io/view/acs-engine/job/k8s-upgrade-and-scale/

@jackfrancis thanks for looking at this!

Any idea when this will be added to a release? I'm needing to use a branch in my project still to get upgrade followed by scaling up to work.

@shanalily do you mean an acs-engine release?

Yep, sorry that was unclear.

ETA next week w/ v0.21.0

Thanks!


Ror4

Coverage decreased (-0.04%) to 84.08% when pulling dc3eb781180c68a531331b20ffe03718341fbe01 on raysuelzer:ror4 into 9c2c5f9742f359e55f85efd84ff3c54c54f36fb5 on MushroomObserver:ror4.

Coverage decreased (-0.04%) to 84.08% when pulling dc3eb781180c68a531331b20ffe03718341fbe01 on raysuelzer:ror4 into 9c2c5f9742f359e55f85efd84ff3c54c54f36fb5 on MushroomObserver:ror4.


Ambiguous class resolution

On the develop branch, when you run:
composer dump-autoload

you are presented with some warnings. Not fatal, but wonder if we can address them.

Are the migration files published to the user's directory from the core package? Because Laravel seems to try to run both.

@Jeroen-G has a point. This happens when migration files are published.
artisan only uses the published migrations. Composer, however, will complain as it autoloads both database directories.
So it's safe to ignore these warnings.

Ok. Thanks for the heads up.


Changing prepublish to pre-publish

When I run npm install, it also runs gulp release (logs here - travis build 7.1)
This is because npm install runs prepublish by default. This is raised as an issue with npm here
For next.js, this might be a feature not a bug. However, if the intention is to check if the repo is setup correctly, then npm test would be a better command to run using a postinstall script.
My assumption is this is an unintentional side effect. @nkzawa, Correct me if I'm wrong.
Changing it to ~prepublish~ pre-publish seems to be the convention.

For npm test to work, gulp test will need to build first

It's intentionally added for convenience of the releasing task even if it has the side effect.
I think we can reconsider the setting when npm4 became common http://blog.lholmquist.org/npm-prepublish-changes.


[3.0] object's bounding boxes are always zero

Operating system or device - Godot version: v3 master, Linux
Issue description:
I've been wondering why performance seems to be affected when I hide objects which are already outside the screen and eventually found out that the bounding boxes are not being calculated and/or used correctly.
get_aabb() always returns a rect with all zeros too.

The function fixed by the pr above just affects the visible aabb used for
the editor, it's unrelated to the internals
On Apr 26, 2017 8:57 AM, "Rémi Verschelde"<EMAIL_ADDRESS>wrote:

Closed #8446 https://github.com/godotengine/godot/issues/8446 via #8538
https://github.com/godotengine/godot/pull/8538.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/8446#event-1057956646, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AF-Z25k93PZCvtJNsA8DTdZ5uIs6sbywks5rzurQgaJpZM4NAJeZ
.

Copying from reverted #8538:

@reduz commented:
Let me try to explain the problem better (cellphone typing sucks). There
are two ways to add data to a mesh (both in Mesh and VisualServer) in 3.0.
One is giving an array of arrays, which is userfriendly but inefficient.
This generates aabbs automatically.
The other is providing a pooled array, which is low level and only
intended to be used for serialization. Does no generation of anything for
performance.
If I'm not mistaken, the mesh aabb should be saved, or pregenerated from
the aabbs of each surface, but never generated when supplying low level
data.
Unfortunately I'm away from computers for two more weeks, so can't check
much :(

Nevermind the original fix was right, I was completely wrong on this one and had to end up doing the same.
It can be closed, in any way.


Governance: Automatically calculate the current version number through Git

What would you like to be added?
Automatically calculate the current version number through Git.
For example, assuming the latest tag is v0.4.2, if HEAD is equal to v0.4.2, then the version number is v0.4.2. If not equal, the version number is v0.4.3-xxxxxx, among them, xxxxxx is ${shortSha}.
Why is this needed?
The current version number is hardcode in the pkg/version/VERSION file, and its value needs to be manually modified before each new version is released, which is not conducive to long-term maintenance.

Could you please confirm if this issue is still open and if I can start working on it?

@rajeshkio Yeah, this issue is currently not aasign to anyone. Welcome to claim it! Maybe you need to know some background of this feature. #362

Thank you. I checked it. My idea is to create a directory 'scripts' and add a script to find the version number and update the pkg/version/VERSION. Is this the right approach or can you recommend any other way.

@rajeshkio I have an idea that has been validated in production here for your reference. The following example can generate version information and some git helpers, which should help you quickly implement this issue.

https://github.com/elliotxx/go-web-template/blob/master/pkg/version/scripts/gen/gen.go
https://github.com/elliotxx/go-web-template/blob/master/pkg/util/gitutil/gitutil.go

ohh it looks like most of the things are already done. Let me try to build and see what is missing.

@rajeshkio Yes, some basic libraries can be reused. Looking forward to your PR!

one silly question maybe. Should I directly import your libraries and use them or should I create new files with almost similar contents for this repo?

@rajeshkio Importing library go-web-template is not suitable. Can be directly copied into the project.

Thought so. I will use the same structure and add or remove contents as needed.

@rajeshkio No problem, you can integrate according to actual needs. 👍

@rajeshkio Hi, I have created a new issue #560  for future optimization.


accuracy is 100% for 1st epoch 10itr/10batches. further it decreases to 0 or very less value

I am trying to run code on my own data (apart from datasets mentioned in paper). During training, it is seen that accuracy is 100% for 1st epoch 1st 10 batches, however it is decreasing to 0 or comparatively very small value throughout further training. Also loss is increasing all time. Snapshot for reference.

The code release in this repo is meant for reproducing the results of research papers.
We help users who have trouble using the code to reproduce results in the paper, but in general we do not provide suggestions on other issues such as how to apply the method to a new task or dataset.

Accuracy of 100% at first few batched is also true for ImageNet and other datasets. This is because you are comparing the positive embedding with negative embedding and the remaining randomly initialized keys in the queue. So, your negative embedding easily gets classified.

I am trying to run code on my own data (apart from datasets mentioned in paper). During training, it is seen that accuracy is 100% for 1st epoch 1st 10 batches, however it is decreasing to 0 or comparatively very small value throughout further training. Also loss is increasing all time. Snapshot for reference.

During the first 10 iterations, the queue is nearly empty (queue size is 65535), so the training accuracy can be very large (easy classification task).

@angy50 Did you finally figure out the reason why it drops to very low values? I confront a similar situation now.


Adding several projects, featuring CNAB

Hi! In this PR I'm suggesting several open source projects from Microsoft for addition to the showcase, and promoting CNAB as a featured project in the homepage.

Thanks Jose.
I suppose we might need to get on some more features to start rotating through projects or better visualizing all these pages...

FYI @crutkas Jose is taking over the PowerToys featured slot with this PR!
(One idea to make the featured capability less manual was to build either a build-time or runtime queue of which projects are featured throughout the week in some form)

An ideal feature would be to randomize who we render in the three featured slots. But the editorial criteria I took for my PR was to feature something dev, something cloud, something platform -- along those lines.

Here are some icons:
Bond:
Dapr: https://dapr.io/images/logos/dapr.svg
Fast fast.svg.zip
ONNX: https://raw.githubusercontent.com/microsoft/onnxruntime/master/docs/images/ONNX_Runtime_icon.png
VFS for Git: https://vfsforgit.org/images/header.png

Thanks @bureado ... we actually have some JS magic for that in the blog posts, if and when we want to keep more curated there; so would be straightforward (https://github.com/microsoft/opensource.microsoft.com/blob/main/index.html#L244)
@ItalyPaleAle @bureado could one of you PR those icons if you have a chance?

I made a PR #46. Couldn't find a logo for all projects, but at least there's some


rbd remap on network failure

Describe the feature you'd like to have
After a node experiences a network outage all rbd images mounted on the node will lose the watcher and be remounted as read-only.
blk_update_request: I/O error, dev rbd3, sector 0 op 0x1:(WRITE) flags 0x3800 phys_seg 1 prio class 0
Buffer I/O error on dev rbd3, logical block 0, lost sync page write
EXT4-fs (rbd3): I/O error while writing superblock
EXT4-fs (rbd3): Remounting filesystem read-only

Perhaps cephcsi can watch PVC and make sure they are remapped if the watcher is none or the file system is mounted as read-only while it shouldn't.
What is the value to the end user? (why is it a priority?)
Recover volumes after a network failure which doesn't affect the pods or anything else.
How will we know we have a good solution? (acceptance criteria)
After a failover from a network failure, mounted RBD images should be remapped and not be read-only if they shouldn't be.

@clwluvw This is not possible with cephcsi as cephcsi is not kubernetes specific (even though we have some kubernetes log (which we are really planning to get rid of soon), This need to be done by some external operator

In order to re-map an RBD image, all users (applications) of the filesystem need to be restarted as well. It is cleaner for an application to report a failure and cause a restart of the container once such a problem happens.
Ceph-CSI has a health-checker that is currently only used with CephFS (see #4200). We had plans to extend that to RBD as well, but this has not been done. It would be possible to report that the volume is unhealthy to kubelet (in the NodeGetVolumeStats reply), which then can take actions on it (currently it only logs, so not much practical recovery yet).

It would be possible to report that the volume is unhealthy to kubelet (in the NodeGetVolumeStats reply), which then can take actions on it (currently it only logs, so not much practical recovery yet).

I guess this would be the best option but it needs to be extended on k8s to restart the pod in case of volume failure.

@clwluvw Yes that is correct but For now, i think you can add a check in the hook to ensure that pvc is writable if not restart the pod. this might work for RWO volumes not for RWX as all the pods need to be scaled down to 0 and scaled back

@Madhu-1 What do you mean by the hook? Do you mean the readinessProbe?

i mean to use Liveness probe which can check for the file in pvc and do restart the container


Fix posit-chronicle to function with default values

Initial error with the empty values file is: Error: failed to create metrics service: no storers found for v1/metrics
Setting LocalStorage.Enabled to true fixes the empty values file problem
I also added a few more CODEOWNERS.  I made some guesses on who makes sense for which based on who has made commits to those charts, and those who I am fairly sure are involved.
So, sorry @matt-urbina @edavidaja @AshleyHenry15 @GCRev and @zachhannum if you are not the proper people.  If you could give me some better names I will be happy to update the lists

I'm not particularly involved in any chart maintenance; I set up the documentation site.

I'm not particularly involved in any chart maintenance; I set up the documentation site.

Removed!

I believe Ashley's involvement was also primarily docs-related.

At https://github.com/rstudio/helm/tree/main/charts/posit-chronicle#storage-configuration we say the default is local storage, so this is changing the code to match the documentation


Piston Micro-tick activation errors

When running this on a server with redstone in the current configuration:

The blocks should be swapping locations, however over time they will eventualy sync up and be pushed backwards and forwards together rather than alternating.
This is consistant with other piston block activity in other areas especialy when powered by different forms of restone.

Interesting issue. It appears to be a problem with the redstone/loading tho.
Have you made sure the behaviour changes reproduceabley from a clean vanilla installation vs a dimthread only(!) installation?

I have this issue too. It only occurs in the nether on my server. The bug is 'breaking' bi-directional slime flying machines causing them to flip travel direction early. This is together with other mods though. I haven't fully tested if it also occurs only with dimthreads.


Rendering & platform support

From reading the Dioxus docs and any resources I could come across (on Discord and the wider web), I understand that blitz (plans to) support the following platforms:

Desktop (Windows, Linux and MacOS)
Mobile (Android & iOS)
Bevy (among other game engines)

While this is an amazing list, I would be interested to know the following (for my own education):

Is the rendering immediate or retained?
Is there any planned support for the web via webgpu a potential use case would be building GUI heavy apps i.e. something similar to Unreal Engine's blueprint editor in Dioxus?
Given that web would be a supported platform via blitz, how would it address SEO related issues (if at all, even if it were through Dioxus)
Any intentions on targetting embedded platforms i.e. Raspberry Pi and some other / more niche platforms used in IoT where GUIs are present

I'm not an expert in renderers or vDOMs so excuse my ignorance, this issue is for me (and people alike) to get a better understanding of blitz and the role it'll play.

Thanks for that provides a much greater insight into the ecosystem, though I'd like to advocate for definitely adding web as one of the primary targets (that is with WebGPU and not just DOM) for when you want to build the next Figma so I can see the benefit of having both rendering strategies.
@Demonthos is there a comparison sheet that has been compiled to view the difference between Blitz and other rendering engines such as UltraLight, WRY etc. and also perhaps the browsers so we can use that to track what features are available?

For multi platform support is root font size reset supported with Blitz?

:root {
	font-size: 62.5%;
}

body {
	font-size: 1.6rem;
}

So I can use rem as units of 10
@Demonthos

@Demonthos is there a comparison sheet that has been compiled to view the difference between Blitz and other rendering engines such as UltraLight, WRY etc. and also perhaps the browsers so we can use that to track what features are available?

I have a private tracking board with what Blitz supports. I'm working on making it public soon.
Currently, Blitz supports a tiny subset of the attribute/elements that you would find in a normal browser, but we are looking to expand these in the future. Right now, Blitz is only really usable for small demos. In the future it will support a larger subset of HTML, but it will likely never support the entire spec.

For multi platform support is root font size reset supported with Blitz?

Selectors are not implemented yet, but they are one of the things (along with https://github.com/DioxusLabs/dioxus/pull/940) that are required for widgets in Blitz, so they are planned.

Thanks for opening up the tracking board and expanding on the topic.

In the future it will support a larger subset of HTML, but it will likely never support the entire spec.

Is there a list of features / elements that Blitz won't support, and the reasoning? I'm interested to know the what and why and see if there are any limitations for my projects.

Is there a list of features / elements that Blitz won't support, and the reasoning? I'm interested to know the what and why and see if there are any limitations for my projects.

There isn't a set list of items that will not be implemented. As we implement more elements and attributes I expect there will be areas that will are both:

Very rairly used in modern websites
Have substantial performance or maintainability impacts for much more common use cases


Errors building klksd on Ubuntu 18.04

Trying to build HEAD from git leads to the following errors:
Making all in src
make[1]: Entering directory '/home/isnow/klks/src'
make[2]: Entering directory '/home/isnow/klks/src'
usage: git rev-list [OPTION] <commit-id>... [ -- paths... ]
  limiting output:
	--max-count=<n>
	--max-age=<epoch>
	--min-age=<epoch>
	--sparse
	--no-merges
	--min-parents=<n>
	--no-min-parents
	--max-parents=<n>
	--no-max-parents
	--remove-empty
	--all
	--branches
	--tags
	--remotes
	--stdin
	--quiet
  ordering output:
	--topo-order
	--date-order
	--reverse
  formatting output:
	--parents
	--children
	--objects | --objects-edge
	--unpacked
	--header | --pretty
	--abbrev=<n> | --no-abbrev
	--abbrev-commit
	--left-right
	--count
  special purpose:
	--bisect
	--bisect-vars
	--bisect-all
make[3]: Entering directory '/home/isnow/klks/src/secp256k1'
make[3]: *** No rule to make target 'libsecp256k1.la'.  Stop.
make[3]: Leaving directory '/home/isnow/klks/src/secp256k1'
Makefile:7529: recipe for target 'secp256k1/libsecp256k1.la' failed
make[2]: *** [secp256k1/libsecp256k1.la] Error 2
make[2]: Leaving directory '/home/isnow/klks/src'
Makefile:7034: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/isnow/klks/src'
Makefile:595: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Before compilation, the following libs and dependencies were installed:
sudo apt install -y libboost-all-dev
sudo apt install -y build-essential libtool autotools-dev automake autogen autoconf pkg-config libssl-dev libevent-dev bsdmainutils
sudo apt install -y git gcc libsecp256k1-dev libzmq3-dev libdb4.8-dev libdb4.8++-dev libqrencode-dev
sudo apt install -y libssl1.0-dev python-virtualenv

sudo apt-add-repository ppa:bitcoin/bitcoin
sudo apt update && sudo apt install -y bitcoin-qt

Before issuing "make", the following commands were run:
libtoolize && aclocal && autoheader && autoconf && automake

Hello,
try compiling starting from step 2 reported on this page
http://kalkulus.trade/manual-installation
Be sure to have following installed for compile QT wallet:
sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libzmq3-dev

Closing issue, no follow up.

Did someone at your site try the guide with Ubuntu 18.04? I cannot really believe anyone did, as  apt  reports:
Package python-software-properties is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or is only available from another source
However the following packages replace it:
    software-properties-common

This, of course is not fatal, but later make gives me in the configure step:
configure: error: Detected LibreSSL: This is NOT supported, and may break consensus compatibility!
Makefile:544: recipe for target 'config.status' failed
make: *** [config.status] Error 1

I think you need to look at https://github.com/PIVX-Project/PIVX/pull/447 - they fixed the libre/openssl problems a year ago.

If you want to contribute you are welcome
Thanks
Il giorno mar 18 dic 2018 alle ore 11:16 Johannes Jander <
<EMAIL_ADDRESS>ha scritto:

I think you need to look at PIVX-Project/PIVX#447
https://github.com/PIVX-Project/PIVX/pull/447 - they fixed the
libre/openssl problems a year ago.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kalkulusteam/klks/issues/13#issuecomment-448169270,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfM8reYGR3p3S4I5v-T4YIevoIngT3a5ks5u6MCIgaJpZM4ZCmx3
.

That does not answer my questions. I am no crypto dev, I cannot contribute in any other way than raising tickets.

Ok , as we said in previous messages we will fix that very soon.Thanks
Il giorno mar 18 dic 2018 alle ore 12:36 Johannes Jander <
<EMAIL_ADDRESS>ha scritto:

That does not answer my questions. I am no crypto dev, I cannot contribute
in any other way than raising tickets.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/kalkulusteam/klks/issues/13#issuecomment-448191425,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfM8rV0bPB-PS2JYF-FsJcQ0x3gx534lks5u6NNOgaJpZM4ZCmx3
.

Seems like installing libssl1.0-dev fixed the problems.

Looks like you already had this installed, as reported on your first post.
By the way, glad that worked.

Thanks a lot, we will add that in the list of needed deps.
Def closing issue.


orders/create  - 500 Oops… You just found an error page

Route [invoice.create] not defined.
InvoiceController note fund

Same here

Hi @ihssane2022  and @bijaya012 ,
Thank you both for bringing this to my attention. 🙏
The issue with the orders/create page has now been resolved. The missing invoice.create route has been defined, and the InvoiceController is now properly implemented. Please pull the latest changes and try again. Let me know if you encounter any other issues!


Stuck at Loading pages (1/6) [> ] 0% [======> ] 10% in browser

Hi,
I'm using 'Single page PDF' example with adjusted paths and autoloader added, it works when run from console but when I run it in a browser it returns "Loading pages (1/6) [> ] 0% [======> ] 10%" and generates no pdf files. I tried $pdf->send and $pdf->saveAs same issue.
Any ideas?

You could try to set 'useExec' => true in the commandOptions. If that doesn't help, I'm sorry, but there's nothing else I can do. wkhtmltopdf sometimes behaves strange, especially when loading content from a remote URL.

I'm having the exact same problem.  I tried setting useExec to true and it didn't help.

setting useExec didn't work for me either, but I tried running wkhtmltopdf trough browser in multiple different ways and got the same error every single time, so this is not a phpwkhtmltopdf
issue

Spent hours looking up the solution to this. For anyone still facing this problem, give this shot: I'd been trying to convert a simple local html file to pdf with wkhtmltopdf in cmd, but it used to freeze at Loading 10% for at least two minutes. Transferred the executable and html files to another machine, and it worked without problems. I proceeded to uninstall wkhtmltopdf from 'Add or remove programs', delete the folder in Program Files, and delete its binary path from %PATH%, and then used just the wkhtmltopdf.exe without installation, and it started working again.
Hope this helps someone.

Same issue on a Ubuntu 20.04, days ago it was working, but now it broke without any change made.
reinstalling didn't work, it still get stuck at
Loading pages (1/6) [===========>                                                ] 19%
If I run a strace:
strace /usr/local/bin/wkhtmltopdf --encoding utf-8 --images knp_snappy63b41bd8de5ba3.36685105.html knp_snappy63b40f25efde63.13123325.pdf
it blocks here:
lstat("/usr/share/fonts/opentype/urw-base35/NimbusSans-Regular.otf", {st_mode=S_IFREG|0644, st_size=82264, ...}) = 0
openat(AT_FDCWD, "/usr/share/fonts/opentype/urw-base35/NimbusSans-Regular.otf", O_RDONLY) = 14
fcntl(14, F_SETFD, FD_CLOEXEC)          = 0
fstat(14, {st_mode=S_IFREG|0644, st_size=82264, ...}) = 0
mmap(NULL, 82264, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fedf9f7d000
close(14)                               = 0
brk(0x555994081000)                     = 0x555994081000
lstat("/usr/share/fonts/opentype/urw-base35/NimbusSans-Bold.otf", {st_mode=S_IFREG|0644, st_size=83264, ...}) = 0
openat(AT_FDCWD, "/usr/share/fonts/opentype/urw-base35/NimbusSans-Bold.otf", O_RDONLY) = 14
fcntl(14, F_SETFD, FD_CLOEXEC)          = 0
fstat(14, {st_mode=S_IFREG|0644, st_size=83264, ...}) = 0
mmap(NULL, 83264, PROT_READ, MAP_PRIVATE, 14, 0) = 0x7fedf9f68000
close(14)                               = 0
brk(0x5559940a2000)                     = 0x5559940a2000
brk(0x5559940c3000)                     = 0x5559940c3000
select(4, [3], [], [], NULL)            = 1 (in [3])
read(3, "\0", 16)                       = 1
read(3, 0x7ffeeb9242d0, 16)             = -1 EAGAIN (Resource temporarily unavailable)
select(4, [3], [], [], NULL

Any idea? That odf file exists and is readable...

@fmonts It seems you also have this problem if you use wkhtmltopdf without our library, right? In that case you should better send your report to the wkhtmltopdf project. This here is only a PHP wrapper around the CLI tool.


New datasets

Freshly coded:

gravinachadic
eppsnorthgermanic
sidwellvietic

Coded some time ago, but needs revision:

grollemundbantu (orthography)
tolmiebritishcolumbia (orthography)

I've done some very basic work on tolmiebritishcolumbia based on your issue (see this branch: https://github.com/lexibank/tolmiebritishcolumbia/tree/wip-profile) but would definitely need more help/guidance to continue with this and make it actually 'good'.

@chrzyki What's the state on this? The issue in tolmiebritishcolumbia persists, but there was some PR related to ortho-profiles.

Is this already fixed, so we can close this issue?
If not, can @MuffinLinwist and I help you with the revision?

tolmiebritishcolumbia is done and just needs a new release. I'll do that today, thank you!

https://github.com/lexibank/tolmiebritishcolumbia/releases/tag/v1.0 was in fact already released with the updated profile and and CONTRIBUTORS, I just forgot to curate the issue accordingly, sorry!


on Windows and Mac, getting error when installing

After installing on 2 different machines (Windows and Mac), whereas I'm able to install noflo and the-graph with no problem, when I attempt to install noflo-ui, I get "Error: EPERM: operation not permitted" when using npm install -g grunt-cli (running as administrator, and in mac using sudo npm install -g grunt-cli), and "Please try running this command again as root/administrator". I have tried a number of workarounds. I had a colleague able to get this running on Linux, but I wanted to see if there is a known resolve to get this installed on Windows?

Do you have grunt installed already (from when you installed noflo)? If so you don't need to install it again.
If not, then try not installing grunt globally (skip -g). And then add ./node_modules/.bin to PATH, or specify the whole path to grunt like ./node_modules/.bin/grunt build

Thanks so much! I was able to just bypass the grunt-cli install and run
grunt build. However, I had to run grunt build --force, as there were 272
errors with a lot of missing file references - is that expected?
Also, using the simple-server example, while simple-server installed and
showed listening on port 3005, the site still didn't load, as there was no
index.html page in the directory. Could that possible be linked to the
build errors, or something else?
On Wed, Nov 23, 2016 at 5:15 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

Do you have grunt installed already (from when you installed noflo)? If so
you don't need to install it again.
If not, then try not installing grunt globally (skip -g). And then add
./node_modules/.bin to PATH, or specify the whole path to grunt like ./node_modules/.bin/grunt
build
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-262643225, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9YmNr39hxHF_62auchQ1D-mObmhaAks5rBLsFgaJpZM4K7GAa
.

No,  272 files missing is a serious problem and probably grunt never succeed so it did not produce an index.html

That's correct - grunt never did produce an index.html. I have spent the
majority of the day resolving all of the missing dependencies; initially I
tried a fresh checkout, checked my environment variables, and installed
grunt-cli - it showed successful, but still showed the 272 errors. I
removed the node_modules folder and did an npm install, and still ended up
with all of those errors. One by one, I went through and resolved the
errors. I only have an index.dist.html available, but also am down to 1
error. This is what I see currently, and results in the UI partially
loading, but unable to find fbp json, showing noflo-ui.js:32776 Uncaught
TypeError: require is not a function(…), and GET
http://localhost:3005/app/$NOFLO_THEME-logo-74.png 404 (Not Found) when
inspecting in the browser (the titles don't render, and clicking on "test"
does not allow the flow based editor will not load - screenshot attached):
I'm not sure why it's so problematic installing on Windows; I've tried
around 7 times, and am hoping there's a more straightforward solution, as
I'm burning a lot of company time dealing with this. Thanks in advance for
any help/suggestions you might be able to provide.
[image: Inline image 1]
c:\noflo\noflo-ui-master>grunt build
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
Running "noflo_browser:main" (noflo_browser) task
c:\noflo\noflo-ui-master\fbp.json not found, running auto-discovery
./~/octo/~/superagent/index.js
Module not found: Error: Cannot resolve 'file' or 'directory'
./lib-cov/node in
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent
resolve file
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.coffee doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.js doesn't exist
resolve directory
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist (directory default file)
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e\package.json doesn't exist (directory description file)
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.coffee]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.js]
@ ./~/octo/~/superagent/index.js 3:4-29
Warning: 1 errors building c:\noflo\noflo-ui-master\app\main.js Use --force
to c
ontinue.
Aborted due to warnings.
c:\noflo\noflo-ui-master>grunt build --force
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
Running "noflo_browser:main" (noflo_browser) task
c:\noflo\noflo-ui-master\fbp.json not found, running auto-discovery
./~/octo/~/superagent/index.js
Module not found: Error: Cannot resolve 'file' or 'directory'
./lib-cov/node in
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent
resolve file
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.coffee doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.js doesn't exist
resolve directory
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist (directory default file)
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e\package.json doesn't exist (directory description file)
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.coffee]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.js]
@ ./~/octo/~/superagent/index.js 3:4-29
Warning: 1 errors building c:\noflo\noflo-ui-master\app\main.js Used
--force, co
ntinuing.
c:\noflo\noflo-ui-master>npm install require
<EMAIL_ADDRESS>node_modules\require
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>c:\noflo\noflo-ui-master>npm install requirejs
<EMAIL_ADDRESS>node_modules\requirejs
c:\noflo\noflo-ui-master>grunt build
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
Running "noflo_browser:main" (noflo_browser) task
c:\noflo\noflo-ui-master\fbp.json not found, running auto-discovery
./~/octo/~/superagent/index.js
Module not found: Error: Cannot resolve 'file' or 'directory'
./lib-cov/node in
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent
resolve file
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.coffee doesn't exist
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e.js doesn't exist
resolve directory
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e doesn't exist (directory default file)
c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\nod
e\package.json doesn't exist (directory description file)
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.coffee]
[c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
.js]
@ ./~/octo/~/superagent/index.js 3:4-29
Warning: 1 errors building c:\noflo\noflo-ui-master\app\main.js Use --force
to c
ontinue.
Aborted due to warnings.
c:\noflo\noflo-ui-master>
On Mon, Nov 28, 2016 at 5:26 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

No, 272 files missing is a serious problem and probably grunt never
succeed so it did not produce an index.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263414588, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Ymr-ybYTUuIRMFhdXqBvMh-F0Jh3ks5rC1UsgaJpZM4K7GAa
.

@mghamry what are the errors you refer to, and how are you resolving them?
Also, what git commit are you on (output of git describe), and what version of NPM are you using. (output of npm -v)?
Problems like c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node doesn't exist on Windows were reported and fixed in https://github.com/noflo/noflo-ui/issues/595

I downloaded the .zip file from the repository (could that be the problem?)
I'm attaching the .zip file. npm -v: 2.14.4
On Tue, Nov 29, 2016 at 6:58 AM, Jon Nordby<EMAIL_ADDRESS>wrote:

@mghamry https://github.com/mghamry what are the errors you refer to,
and how are you resolving them?
Also, what git commit are you on (output of git describe), and what
version of NPM are you using. (output of npm -v)?
Problems like c:\noflo\noflo-ui-master\node_modules\octo\node_modules\superagent\lib-cov\node
doesn't exist on Windows were reported and fixed in #595
https://github.com/noflo/noflo-ui/issues/595
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263552155, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Yt23dX8yxYGvET7V7cRXB4XgilyRks5rDBOCgaJpZM4K7GAa
.

I just pulled and checked git version - I have git 1.9.5, and branched from
here, equivalent to master - ran the install and came up with the 272
errors again. The way I resolved the errors were to install the missing
modules referenced in the errors (several of them). This is my git branch:
https://github.com/mghamry/noflo-ui.git
On Tue, Nov 29, 2016 at 12:28 PM, Maggie Ghamry <
<EMAIL_ADDRESS>wrote:

I downloaded the .zip file from the repository (could that be the
problem?) I'm attaching the .zip file. npm -v: 2.14.4
On Tue, Nov 29, 2016 at 6:58 AM, Jon Nordby<EMAIL_ADDRESS>wrote:

@mghamry https://github.com/mghamry what are the errors you refer to,
and how are you resolving them?
Also, what git commit are you on (output of git describe), and what
version of NPM are you using. (output of npm -v)?
Problems like c:\noflo\noflo-ui-master\node_
modules\octo\node_modules\superagent\lib-cov\node doesn't exist on
Windows were reported and fixed in #595
https://github.com/noflo/noflo-ui/issues/595
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263552155,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWR9Yt23dX8yxYGvET7V7cRXB4XgilyRks5rDBOCgaJpZM4K7GAa
.

@mghamry the problem is very likely the NPM version. webpack is not compatible with NPM versions before 3.x. The error messages you see are consistent with this problem. So you must upgrade to NPM v3 or newer, using npm install -g npm@3 or similar.
I have pushed an update to package.json and README.md that specifies this requirement.

Thanks so much for the fast replies; much appreciated! Ok, so I upgraded to
npm 3, and still had the same errors. So I upgraded to 4.0.2 (npm install
npm@latest -g), and updated node as well. I then still had 1 error to
resolve; the module microflo was missing. So I installed the latest version
of microflo (npm install microflo @latest -g), and got several warnings and
errors, referring to bugs with the serialport module, so I had to run grunt
build --force to overcome that. Here is the output of the error:
c:\dev\noflo-ui>grunt build
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
Running "noflo_browser:main" (noflo_browser) task
c:\dev\noflo-ui\fbp.json not found, running auto-discovery
./~/fbp-protocol-client/src/microflo.coffee
Module not found: Error: Cannot resolve module 'microflo' in
c:\dev\noflo-ui\nod
e_modules\fbp-protocol-client\src
resolve module microflo in
c:\dev\noflo-ui\node_modules\fbp-protocol-client\src
looking for modules in c:\dev\noflo-ui\node_modules
resolve 'file' microflo in c:\dev\noflo-ui\node_modules
resolve file
c:\dev\noflo-ui\node_modules\microflo doesn't exist
c:\dev\noflo-ui\node_modules\microflo.coffee doesn't exist
c:\dev\noflo-ui\node_modules\microflo.js doesn't exist
c:\dev\noflo-ui\node_modules\microflo doesn't exist (module as
directory)
looking for modules in
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_m
odules
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo
doesn
't exist (module as directory)
resolve 'file' microflo in
c:\dev\noflo-ui\node_modules\fbp-protocol-client
node_modules
resolve file
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo d
oesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.j
s doesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.c
offee doesn't exist
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\microflo.coffee]
[c:\dev\noflo-ui\node_modules\microflo.js]
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.js]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.coffee]
@ ./~/fbp-protocol-client/src/microflo.coffee 8:11-30
Warning: 1 errors building c:\dev\noflo-ui\app\main.js Use --force to
continue.
Aborted due to warnings.
c:\dev\noflo-ui>
I then got more errors after trying t install and spin up the simple-server
(which hasn't happened before), but seems to be related:
c:\dev\noflo-ui>npm install simple-server
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please
install th
e latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or
higher
to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will
fail o
n node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as
possible
. Use 'npm ls graceful-fs' to find it in the tree.

<EMAIL_ADDRESS>install c:\dev\noflo-ui\node_modules\serialport
node-pre-gyp install --fallback-to-build

Thanks again for your help - I'll keep trying!
On Tue, Nov 29, 2016 at 12:58 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

@mghamry https://github.com/mghamry the problem is very likely the NPM
version. webpack is not compatible with NPM versions before 3.x. The
error messages you see are consistent with this problem. So you must
upgrade to NPM v3 or newer, using npm install -g npm@3 or similar.
I have pushed an update to package.json and README.md that specifies this
requirement.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263647215, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Yssya5cNYrC2b3m-0lAcSNIDxRwNks5rDGfLgaJpZM4K7GAa
.

Don't use -g when installing normal dependencies, it is only to be used for system-wide tools. It will likely cause problems for webpack. And don't use grunt build --force, it does not solve anything, just hides real errors.
Try to do just npm install microflo.
If that does not works, please remove node_modules completely, do npm install and then grunt build and upload the entire log. From the snippets here it is not really possible to determine what went wrong...

I realized that right after - I am running npm install microflo, but it's
hanging for some reason. I'll remove modules and reload
On Tue, Nov 29, 2016 at 2:06 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

Don't use -g when installing normal dependencies, it is only to be used
for system-wide tools. It will likely cause problems for webpack. And don't
use grunt build --force, it does not solve anything, just hides real
errors.
Try to do just npm install microflo.
If that does not works, please remove node_modules completely, do npm
install and then grunt build and upload the entire log. From the snippets
here it is not really possible to determine what went wrong...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263665919, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Yvkoe9w_sMMuD0tOcvKWv7x6FTOyks5rDHepgaJpZM4K7GAa
.

No luck - I'm attaching the complete logs for a) fresh git checkout from
master and installing microflo, npm install, and grunt build, and then b)
removing node_modules, running npm install, grunt build, and npm install
microflo
On Tue, Nov 29, 2016 at 2:25 PM, Maggie Ghamry<EMAIL_ADDRESS>
wrote:

I realized that right after - I am running npm install microflo, but it's
hanging for some reason. I'll remove modules and reload
On Tue, Nov 29, 2016 at 2:06 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

Don't use -g when installing normal dependencies, it is only to be used
for system-wide tools. It will likely cause problems for webpack. And don't
use grunt build --force, it does not solve anything, just hides real
errors.
Try to do just npm install microflo.
If that does not works, please remove node_modules completely, do npm
install and then grunt build and upload the entire log. From the
snippets here it is not really possible to determine what went wrong...
—
You are receiving this because you were mentioned.
 Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\maggie.ghamry\A
ppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --f
allback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\noflo-ui\npm-debug.log
c:\dev\noflo-ui>grunt build
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
bower cached        git://github.com/Polymer/webcomponentsjs.git#0.5.2
bower validate      0.5.2 against git://github.com/Polymer/webcomponentsjs.git#0
.5.2
bower cached        https://github.com/Polymer/polymer.git#0.5.2
bower validate      0.5.2 against https://github.com/Polymer/polymer.git#0.5.2
bower cached        https://github.com/the-grid/the-graph.git#0.4.3
bower validate      0.4.3 against https://github.com/the-grid/the-graph.git#0.4.
3
bower cached        https://github.com/EightMedia/hammer.js.git#2.0.8
bower validate      2.0.8 against https://github.com/EightMedia/hammer.js.git#~2
.0.8
bower cached        https://github.com/noflo/klayjs-noflo.git#0.3.0
bower validate      0.3.0 against https://github.com/noflo/klayjs-noflo.git#~0.3
.0
bower cached        https://github.com/djdeath/react.animate.git#0.0.3
bower validate      0.0.3 against https://github.com/djdeath/react.animate.git#0
.0.3
bower cached        https://github.com/facebook/react-bower.git#0.14.3
bower validate      0.14.3 against https://github.com/facebook/react-bower.git#0
.14.3
bower cached        https://github.com/FortAwesome/Font-Awesome.git#4.4.0
bower validate      4.4.0 against https://github.com/FortAwesome/Font-Awesome.gi
t#~4.4.0
bower cached        git://github.com/Polymer/core-component-page.git#0.5.6
bower validate      0.5.6 against git://github.com/Polymer/core-component-page.g
it#^0.5.0
bower cached        https://github.com/djdeath/ease.git#5b49e8e9ca
bower validate      5b49e8e9ca against https://github.com/djdeath/ease.git#5b49e
8e9cac9134a417b64c244ae5bc9c7c0eb9c
bower cached        https://github.com/OpenKieler/klayjs.git#0.2.1
bower validate      0.2.1 against https://github.com/OpenKieler/klayjs.git#~0.2.
1
bower install       webcomponentsjs#0.5.2
bower install       the-graph#0.4.3
bower install       polymer#0.5.2
bower install       react.animate-djdeath#0.0.3
bower install       react#0.14.3
bower install       klayjs-noflo#0.3.0
bower install       hammerjs#2.0.8
bower install       font-awesome#4.4.0
bower install       ease-djdeath#5b49e8e9ca
bower install       core-component-page#0.5.6
bower install       klayjs#0.2.1
webcomponentsjs#0.5.2 bower_components\webcomponentsjs
the-graph#0.4.3 bower_components\the-graph
├── font-awesome#4.4.0
├── hammerjs#2.0.8
├── klayjs-noflo#0.3.0
├── polymer#0.5.2
├── react#0.14.3
├── react.animate-djdeath#0.0.3
└── webcomponentsjs#0.5.2
polymer#0.5.2 bower_components\polymer
├── core-component-page#0.5.6
└── webcomponentsjs#0.5.2
react.animate-djdeath#0.0.3 bower_components\react.animate-djdeath
├── ease-djdeath#5b49e8e9ca
└── react#0.14.3
react#0.14.3 bower_components\react
klayjs-noflo#0.3.0 bower_components\klayjs-noflo
└── klayjs#0.2.1
hammerjs#2.0.8 bower_components\hammerjs
font-awesome#4.4.0 bower_components\font-awesome
ease-djdeath#5b49e8e9ca bower_components\ease-djdeath
core-component-page#0.5.6 bower_components\core-component-page
├── polymer#0.5.2
└── webcomponentsjs#0.5.2
klayjs#0.2.1 bower_components\klayjs
Running "noflo_browser:main" (noflo_browser) task
c:\dev\noflo-ui\fbp.json not found, running auto-discovery
./~/fbp-protocol-client/src/microflo.coffee
Module not found: Error: Cannot resolve module 'microflo' in c:\dev\noflo-ui\nod
e_modules\fbp-protocol-client\src
resolve module microflo in c:\dev\noflo-ui\node_modules\fbp-protocol-client\src
looking for modules in c:\dev\noflo-ui\node_modules
resolve 'file' microflo in c:\dev\noflo-ui\node_modules
resolve file
c:\dev\noflo-ui\node_modules\microflo doesn't exist
c:\dev\noflo-ui\node_modules\microflo.coffee doesn't exist
c:\dev\noflo-ui\node_modules\microflo.js doesn't exist
c:\dev\noflo-ui\node_modules\microflo doesn't exist (module as directory)
looking for modules in c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_m
odules
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo doesn
't exist (module as directory)
resolve 'file' microflo in c:\dev\noflo-ui\node_modules\fbp-protocol-client
node_modules
resolve file
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo d
oesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.j
s doesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.c
offee doesn't exist
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\microflo.coffee]
[c:\dev\noflo-ui\node_modules\microflo.js]
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.js]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.coffee]
@ ./~/fbp-protocol-client/src/microflo.coffee 8:11-30
Warning: 1 errors building c:\dev\noflo-ui\app\main.js Use --force to continue.
 Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\maggie.ghamry\A
ppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --f
allback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\noflo-ui\npm-debug.log
c:\dev\noflo-ui>grunt build
Running "inlinelint:all" (inlinelint) task

44 files lint free.

Running "bower-install-simple:deps" (bower-install-simple) task
Executing Bower (Command: install)
Running "noflo_browser:main" (noflo_browser) task
c:\dev\noflo-ui\fbp.json not found, running auto-discovery
./~/fbp-protocol-client/src/microflo.coffee
Module not found: Error: Cannot resolve module 'microflo' in c:\dev\noflo-ui\nod
e_modules\fbp-protocol-client\src
resolve module microflo in c:\dev\noflo-ui\node_modules\fbp-protocol-client\src
looking for modules in c:\dev\noflo-ui\node_modules
resolve 'file' microflo in c:\dev\noflo-ui\node_modules
resolve file
c:\dev\noflo-ui\node_modules\microflo doesn't exist
c:\dev\noflo-ui\node_modules\microflo.coffee doesn't exist
c:\dev\noflo-ui\node_modules\microflo.js doesn't exist
c:\dev\noflo-ui\node_modules\microflo doesn't exist (module as directory)
looking for modules in c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_m
odules
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo doesn
't exist (module as directory)
resolve 'file' microflo in c:\dev\noflo-ui\node_modules\fbp-protocol-client
node_modules
resolve file
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo d
oesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.c
offee doesn't exist
c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.j
s doesn't exist
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\microflo.coffee]
[c:\dev\noflo-ui\node_modules\microflo.js]
[c:\dev\noflo-ui\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.coffee]
[c:\dev\noflo-ui\node_modules\fbp-protocol-client\node_modules\microflo.js]
@ ./~/fbp-protocol-client/src/microflo.coffee 8:11-30
Warning: 1 errors building c:\dev\noflo-ui\app\main.js Use --force to continue.
Aborted due to warnings.
c:\dev\noflo-ui>npm install microflo
npm WARN deprecated<EMAIL_ADDRESS>Jade has been renamed to pug, please install th
e latest version of pug instead of jade
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher
to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail o
n node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible
. Use 'npm ls graceful-fs' to find it in the tree.

<EMAIL_ADDRESS>install c:\dev\noflo-ui\node_modules\serialport
node-pre-gyp install --fallback-to-build

c:\dev\noflo-ui\node_modules\serialport>if not defined npm_config_node_gyp (node
"C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\
....\node_modules\node-gyp\bin\node-gyp.js" clean )  else (node "" clean )
c:\dev\noflo-ui\node_modules\serialport>if not defined npm_config_node_gyp (node
"C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\
....\node_modules\node-gyp\bin\node-gyp.js" configure --fallback-to-build --mod
ule=c:\dev\noflo-ui\node_modules\serialport\build\Release\serialport.node --modu
le_name=serialport --module_path=c:\dev\noflo-ui\node_modules\serialport\build\R
elease )  else (node "" configure --fallback-to-build --module=c:\dev\noflo-ui\n
ode_modules\serialport\build\Release\serialport.node --module_name=serialport --
module_path=c:\dev\noflo-ui\node_modules\serialport\build\Release )
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYT
HON env variable.
gyp ERR! stack     at failNoPython (C:\Users\maggie.ghamry\AppData\Roaming\npm\n
ode_modules\npm\node_modules\node-gyp\lib\configure.js:449:14)
gyp ERR! stack     at C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\np
m\node_modules\node-gyp\lib\configure.js:404:11
gyp ERR! stack     at C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\np
m\node_modules\graceful-fs\polyfills.js:276:29
gyp ERR! stack     at FSReqWrap.oncomplete (fs.js:123:15)
gyp ERR!  System Windows_NT 6.1.7601
node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "c:\dev\noflo-
ui\node_modules\serialport\node_modules\node-pre-gyp\bin\node-pre-gyp" "in
stall" "--fallback-to-build"
node-pre-gyp ERR! cwd c:\dev\noflo-ui\node_modules\serialport
node-pre-gyp ERR! node -v v6.9.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.26
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd configure --fallback-to-build --module=c:\dev\no
flo-ui\node_modules\serialport\build\Release\serialport.node --module_name=seria
lport --module_path=c:\dev\noflo-ui\node_modules\serialport\build\Release' (1)
<EMAIL_ADDRESS>c:\dev\noflo-ui
--<EMAIL_ADDRESS> +--<EMAIL_ADDRESS> | +--<EMAIL_ADDRESS> | --<EMAIL_ADDRESS>--<EMAIL_ADDRESS>   +--<EMAIL_ADDRESS>   +--<EMAIL_ADDRESS>   | +--<EMAIL_ADDRESS>   | --<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>+--<EMAIL_ADDRESS>| +--<EMAIL_ADDRESS>| --<EMAIL_ADDRESS>   --<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"
})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\maggie.ghamry\A
ppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "microflo"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --f
allback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\noflo-ui\npm-debug.log
c:\dev\noflo-ui>

The issue is here>
gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.

node-gyp, which is for building native C++ modules for node.js, requires Python (2).
https://www.python.org/downloads/release/python-2712/
Ideally this serialport and MicroFlo thing would not be direct dependencies, instead loaded like we do with the NoFlo browser runtime... But this requires a bit of work, not gonna happen right now.
Btw, if you upload the log as a file, or use '```' before and after the log, it is much easier to read

Ok. Now it's saying I need to install the .net framework - I'm ultimately
looking to integrate this into Angular.js; is this a normal dependency? I'm
uploading the whole log, but this is highlighted in red:
MSBUILD : error MSB3428: Could not load the Visual C++ component
"VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft
Visua
l Studio 2005 or 3) add the location of the component to the system path if
it
is installed elsewhere.
[c:\dev\noflo-ui\node_modules\serialport\build\binding
.sln]
On Tue, Nov 29, 2016 at 4:12 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

The issue is here>
gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
node-gyp, which is for building native C++ modules for node.js, requires
Python (2).
https://www.python.org/downloads/release/python-2712/
Ideally this serialport and MicroFlo thing would not be direct
dependencies, instead loaded like we do with the NoFlo browser runtime...
But this requires a bit of work, not gonna happen right now.
Btw, if you upload the log as a file, or use '```' before and after the
log, it is much easier to read
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263700407, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9YtZ3yIUQinnkEyC1j69DECRjR-Diks5rDJVUgaJpZM4K7GAa
.

'```'
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
C:\Windows\system32>cd c:\dev\noflo-ui
c:\dev\noflo-ui>npm install

<EMAIL_ADDRESS>install c:\dev\noflo-ui\node_modules\serialport
node-pre-gyp install --fallback-to-build

c:\dev\noflo-ui\node_modules\serialport>if not defined npm_config_node_gyp (node
"C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\
....\node_modules\node-gyp\bin\node-gyp.js" clean )  else (node "" clean )
c:\dev\noflo-ui\node_modules\serialport>if not defined npm_config_node_gyp (node
"C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\
....\node_modules\node-gyp\bin\node-gyp.js" configure --fallback-to-build --mod
ule=c:\dev\noflo-ui\node_modules\serialport\build\Release\serialport.node --modu
le_name=serialport --module_path=c:\dev\noflo-ui\node_modules\serialport\build\R
elease )  else (node "" configure --fallback-to-build --module=c:\dev\noflo-ui\n
ode_modules\serialport\build\Release\serialport.node --module_name=serialport --
module_path=c:\dev\noflo-ui\node_modules\serialport\build\Release )
c:\dev\noflo-ui\node_modules\serialport>if not defined npm_config_node_gyp (node
"C:\Users\maggie.ghamry\AppData\Roaming\npm\node_modules\npm\bin\node-gyp-bin\
....\node_modules\node-gyp\bin\node-gyp.js" build --fallback-to-build --module=
c:\dev\noflo-ui\node_modules\serialport\build\Release\serialport.node --module_n
ame=serialport --module_path=c:\dev\noflo-ui\node_modules\serialport\build\Relea
se )  else (node "" build --fallback-to-build --module=c:\dev\noflo-ui\node_modu
les\serialport\build\Release\serialport.node --module_name=serialport --module_p
ath=c:\dev\noflo-ui\node_modules\serialport\build\Release )
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visua
l Studio 2005 or 3) add the location of the component to the system path if it
is installed elsewhere.  [c:\dev\noflo-ui\node_modules\serialport\build\binding
.sln]
gyp ERR! build error
gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe  failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\maggie.ghamry\AppData\Roamin
g\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:215:12)
gyp ERR!  System Windows_NT 6.1.7601
node-pre-gyp ERR! command "C:\Program Files\nodejs\node.exe" "c:\dev\noflo-
ui\node_modules\serialport\node_modules\node-pre-gyp\bin\node-pre-gyp" "in
stall" "--fallback-to-build"
node-pre-gyp ERR! cwd c:\dev\noflo-ui\node_modules\serialport
node-pre-gyp ERR! node -v v6.9.1
node-pre-gyp ERR! node-pre-gyp -v v0.6.26
node-pre-gyp ERR! not ok
Failed to execute 'node-gyp.cmd build --fallback-to-build --module=c:\dev\noflo-
ui\node_modules\serialport\build\Release\serialport.node --module_name=serialpor
t --module_path=c:\dev\noflo-ui\node_modules\serialport\build\Release' (1)
<EMAIL_ADDRESS>c:\dev\noflo-ui
`-- (empty)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.0.15: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"
})
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\maggie.ghamry\A
ppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install"
npm ERR! node v6.9.1
npm ERR! npm  v4.0.2
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --f
allback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the serialport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs serialport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls serialport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     c:\dev\noflo-ui\npm-debug.log
c:\dev\noflo-ui>
'```'

Regarding VCBuild.exe, I do not know if it is normal or not. Have not used Windows in many years. But I have no reason to doubt the message that comes up.
noflo-ui is not suitable for integrating into another app (well except as an iframe). Use https://github.com/the-grid/the-graph for that. It has a lot less dependencies, and actually has an API etc.

Ak. That was what I was initially trying to integrate, but it does not
appear to have the left-click/ search feature that the client wants to
integrate, so that we can edit node properties. I spent a bit of time
trying to troubleshoot that as well, and they ultimately recommended I use
noflo-ui and strip it down so that it could be integrated. If it could only
be integrated as an iframe, that is most likely an unsuitable workaround.
If I have a way to use the-graph to right/left click and edit, that will
help me overcome a major hurdle.
On Tue, Nov 29, 2016 at 4:44 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

Regarding VCBuild.exe, I do not know if it is normal or not. Have not
used Windows in many years. But I have no reason to doubt the message that
comes up.
noflo-ui is not suitable for integrating into another app (well except as
an iframe). Use https://github.com/the-grid/the-graph for that. It has a
lot less dependencies, and actually has an API etc.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263709052, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Ym7z8aAw4s5hBBko7BHosvd2kmX1ks5rDJyygaJpZM4K7GAa
.

the-graph-editor element has the default menus for clicking. And it can be overridden from the outside by passing in menus property to the Polymer element.
https://github.com/the-grid/the-graph/blob/master/the-graph-editor/the-graph-editor.html#L89
Search you will need to implement separately.

I was able to modify the initial menu element to add an edit icon to the
right click menu. I'm not 100% certain how to go about adding the edit
capability/where to display it (ie, if we can't use the search/edit
features in noflo-ui, do I need to add a custom modal?) - I was surprised
that editing wasn't part of the-graph, but in order to salvage this
project, I've got to give them a tough answer tomorrow morning with regard
to keeping this as our library, or looking for something more suitable for
AngularJS integration. If I could even get help with a simple edit
functionality, I would be forever grateful!
On Tue, Nov 29, 2016 at 5:03 PM, Jon Nordby<EMAIL_ADDRESS>wrote:

the-graph-editor element has the default menus for clicking. And it can
be overridden from the outside by passing in menus property to the
Polymer element.
https://github.com/the-grid/the-graph/blob/master/the-
graph-editor/the-graph-editor.html#L89
Search you will need to implement separately.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/noflo/noflo-ui/issues/637#issuecomment-263714177, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AWR9Yvh0qLp6nYjOXmKvluAr7lWpioLuks5rDKEigaJpZM4K7GAa
.


Add draft functions getIncompleteTypingPos and loadHLADb parseSubMatrix reduceTypingPos

Codecov Report

Merging #89 into master will decrease coverage by 3.25%.
The diff coverage is 66.66%.

@@            Coverage Diff             @@
##           master      #89      +/-   ##
==========================================
- Coverage   97.58%   94.32%   -3.26%
==========================================
  Files           9        9
  Lines         372      405      +33
==========================================
+ Hits          363      382      +19
- Misses          9       23      +14

Impacted Files
Coverage Δ

R/prepareHLAdb.R
92.45% <62.5%> (-5.33%)
:arrow_down:

R/HLAdbTools.R
86.36% <76.92%> (-8.88%)
:arrow_down:

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 e10474c...a3dc99c. Read the comment docs.


NSURLSessionDataTask (_AFStateObserving) leaks with version 2.5.2

This is fixed in master. See a13a244526e4110739872904c860edd645accdd1.

Sorry for trouble you. I would check the newest source file (because of new problem next time)     :)


Restore VIVE API layers

Hi,
I am the author of VIVE API layers from HTC.
We've been reported from our developer that when they installed OpenXR Toolkit, the VIVE API layers would be disabled.
They are not able to play the content which uses our features in those API layers afterwards.
And then I found one workaround in "https://github.com/mbucchia/OpenXR-Toolkit/blob/main/XR_APILAYER_MBUCCHIA_toolkit/framework/dispatch.cpp", where it says our "xrEnumerateInstanceExtensionProperties()" function is not compliant with OpenXR.
It seems that you have done two ways to skip our API layers, which I think is reasonable.
Therefore we fixed this issue in our current update in order to avoid complaints from your API layer.
But still we need your help to check it and more importantly to remove that workaround as well as disabling VIVE API layers in your installer.
Thanks in advance.

Hello Kyle,
Thanks for looking into it. What is the version of VIVE Console with your fix, so I can test with it?

It's on our Beta now.
You could go to "Settings->Advcanced->Join Beta" to get the release.

Hi, unfortunately the behavior still looks incorrect to me at this time.
Calling xrEnumerateInstanceExtensionProperties() with nullptr as the first argument makes your API layer only return the extensions that it provides. This blocks an API layer from querying the list of extensions from the runtime. My reading of the spec is that passing nullptr for layerName means to not query a specific API layer, but instead query the entire chain of API layers + the runtime.

Nonetheless I am merging 0e9ca9d94b186843daaaef0798cf5f4248ba4a56 that restores the API layers per your request, and will be released in 1.3.3. But the behavior will still be broken when using Vive console.


Error: Cannot find module '../SearchDialogLibrary'

🚨 The issue tracker is not for questions 🚨
If you have a question, please ask it on https://stackoverflow.com/questions/tagged/botframework
[question]
I am getting this error, cant run the code. What to do?

Hi @aishjain! There is no information here for us to be able to help you. Can you clarify what sample you were running when you got this?

@aishjain The V3 samples have been moved to the v3-sdk-samples branch.
SearchDialogLibrary can be found here:
https://github.com/Microsoft/BotBuilder-Samples/tree/v3-sdk-samples/Node/demo-Search/SearchDialogLibrary

we believe the customer has been helped.


Add option to skip ascending batch sequence validation

https://github.com/moov-io/ach/issues/1022

Codecov Report

Merging #1023 (03dbf24) into master (d4fedeb) will increase coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head 03dbf24 differs from pull request most recent head a0d3460.


Review consistency of graphs

Review consistency of graphs based on comments derived from user testing report.
Things to modify:

Axis labels (bold, modify text?)
Axis labels, placement
Consistency in padding
Consistency in fonts

See page 5 and 6 of the ux report

Completed.


Feature flag to make readthedocs theme default on MkDocs docs

Historically, we were using readthedocs as default theme for MkDocs but in https://github.com/rtfd/readthedocs.org/pull/4556 we decided to change it to get the same behavior when building locally than in Read the Docs.
This commit adds a Feature flag to keep having the old behavior for some particular projects so we can add these project and do not break their documentation (change the theme without asking/reason).

In MkDocs >= 1.0, this will never be a problem as theme is required. Therefore the default will never be used.
In MkDocs >= 0.17 but < 1.0, the theme can be specified in mkdocs.yml as a dict although it is optional. If the user specified it, I believe this PR won't do anything.
In MkDocs < 0.17, the theme was always just a string although it was optional. This should handle that just fine.

In MkDocs >= 1.0, this will never be a problem as theme is required. Therefore the default will never be used.

Why the default will never be used? Because it's mandatory to be a dict like theme.name? If they were using mkdocs>=1.0 they need to be setting the theme manually otherwise, it shouldn't be working right now.

Why the default will never be used? Because it's mandatory to be a dict like theme.name? If they were using mkdocs>=1.0 they need to be setting the theme manually otherwise, it shouldn't be working right now.

This is all correct. In 1.0+, theme.name is mandatory. Nobody is using 1.0+ unless they specify it in their requirements file.

Great, sounds like this can be merged and hotfixed on our release branch.


Have a better error message sent to caml when calling build

At the moment, the error message is not sent to caml in caml_pasta_fp_plonk_index_create.

Fixed in commit https://github.com/MinaProtocol/mina/commit/e95103ab286 as part of the debugging infra for https://github.com/MinaProtocol/mina/pull/14317.