Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all
 blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Force GitHub README to respect dark mode (function() { var style = document.createElement('style'); style.textContent = ' .markdown-body { color-scheme: dark light; } .markdown-body pre { background: #161b22 !important; } .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; } .markdown-body table th, .markdown-body table td { border-color: #30363d !important; } .markdown-body img { background: #0d1117; } .markdown-body blockquote { border-left-color: #8b949e; } .markdown-body hr { border-color: #30363d; } '; document.head.appendChild(style); })(); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Highlight search terms from Google/DuckDuckGo/Bing referrer (function() { var ref = document.referrer; var terms = []; if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) { var url = new URL(ref); var q = url.searchParams.get('q') || url.searchParams.get('p'); if (q) { terms = q.split(/\s+/).filter(function(t) { return t.length > 2; }); } } if (terms.length === 0) return; var style = document.createElement('style'); style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }'; document.head.appendChild(style); function highlight(node) { if (node.nodeType === 3) { // text node var text = node.textContent; var found = false; terms.forEach(function(term) { var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi'); if (regex.test(text)) { found = true; var frag = document.createDocumentFragment(); var parts = text.split(regex); parts.forEach(function(part, i) { if (i % 2 === 0) { frag.appendChild(document.createTextNode(part)); } else { var span = document.createElement('span'); span.className = 'userscript-highlight'; span.textContent = part; frag.appendChild(span); } }); node.parentNode.replaceChild(frag, node); } }); } else if (node.nodeType === 1 && node.childNodes) { // element var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT']; if (!skipTags.includes(node.tagName)) { Array.from(node.childNodes).forEach(highlight); } } } highlight(document.body); // Re-highlight on dynamic content var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1 || node.nodeType === 3) highlight(node); }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Strip utm_, fbclid, gclid, etc. from all links on page (function() { var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content', 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid', 'ref', 'ref_src', 'source', 'medium', 'campaign']; function cleanUrl(url) { try { var u = new URL(url, window.location.origin); var changed = false; trackingParams.forEach(function(p) { if (u.searchParams.has(p)) { u.searchParams.delete(p); changed = true; } }); return changed ? u.toString() : url; } catch (e) { return url; } } function cleanLinks() { document.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } cleanLinks(); var observer = new MutationObserver(function(mutations) { mutations.forEach(function(m) { m.addedNodes.forEach(function(node) { if (node.nodeType === 1) { if (node.tagName === 'A') cleanLinks(); node.querySelectorAll('a[href]').forEach(function(a) { var clean = cleanUrl(a.href); if (clean !== a.href) a.href = clean; }); } }); }); }); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + ' Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Auto-enable theater mode on YouTube (function() { function tryTheater() { var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]'); if (btn && !btn.classList.contains('activated')) { btn.click(); } } // Try immediately tryTheater(); // Try after navigation (SPA) var lastUrl = location.href; setInterval(function() { if (location.href !== lastUrl) { lastUrl = location.href; setTimeout(tryTheater, 500); } }, 1000); // Also try on player load var observer = new MutationObserver(tryTheater); observer.observe(document.body, { childList: true, subtree: true }); })(); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Remove or un-stick sticky/fixed headers that block content (function() { function unstick() { document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) { if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') { el.style.position = 'static'; el.style.top = 'auto'; el.style.zIndex = 'auto'; } }); } unstick(); var observer = new MutationObserver(unstick); observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] }); })(); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + ' Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard
, 'i'); if (__m === '*' || __re.test(location.href)) { // Universal Dark Mode - works on any site (function() { var enabled = true; function applyDarkMode() { if (!enabled) return; // Create style element if it doesn't exist var style = document.getElementById('universal-dark-mode-style'); if (!style) { style = document.createElement('style'); style.id = 'universal-dark-mode-style'; document.head.appendChild(style); } // Dark mode CSS - inverts colors but preserves images/video style.textContent = ' /* Invert everything except media */ html { filter: invert(1) hue-rotate(180deg) !important; background: #1a1a2e !important; } /* Restore images, videos, iframes, canvas */ img, video, iframe, canvas, svg, picture, [style*="background-image"] { filter: invert(1) hue-rotate(180deg) !important; } /* Preserve specific elements that should not be inverted */ .no-dark-mode, .no-dark-mode *, [data-theme="light"], [data-theme="light"], .ace_editor, .ace_editor *, .CodeMirror, .CodeMirror *, .monaco-editor, .monaco-editor *, .markdown-body pre, .markdown-body pre *, .highlight, .highlight *, pre code, pre code * { filter: none !important; } /* Fix common UI elements */ .modal, .popup, .dropdown-menu, .tooltip, .popover { filter: invert(1) hue-rotate(180deg) !important; background: #2d2d44 !important; border-color: #444 !important; } /* Scrollbars */ ::-webkit-scrollbar { background: #1a1a2e !important; } ::-webkit-scrollbar-thumb { background: #444 !important; } ::-webkit-scrollbar-thumb:hover { background: #555 !important; } /* Selection */ ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; } ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; } '; } function removeDarkMode() { var style = document.getElementById('universal-dark-mode-style'); if (style) style.remove(); } // Toggle with Alt+Shift+D document.addEventListener('keydown', function(e) { if (e.altKey && e.shiftKey && e.key === 'D') { e.preventDefault(); enabled = !enabled; if (enabled) { applyDarkMode(); console.log('[Universal Dark Mode] Enabled'); } else { removeDarkMode(); console.log('[Universal Dark Mode] Disabled'); } } }); // Apply on load applyDarkMode(); // Re-apply on dynamic content var observer = new MutationObserver(function(mutations) { if (enabled && !document.getElementById('universal-dark-mode-style')) { applyDarkMode(); } }); observer.observe(document.head, { childList: true }); console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle'); })(); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })(); Updating dependencies of gl-vis modules by archmoj · Pull Request #3421 · plotly/plotly.js · GitHub
Skip to content

Updating dependencies of gl-vis modules - #3421

Merged
archmoj merged 20 commits into
masterfrom
dep2019
Jan 16, 2019
Merged

Updating dependencies of gl-vis modules#3421
archmoj merged 20 commits into
masterfrom
dep2019

Conversation

@archmoj

Copy link
Copy Markdown
Contributor

Various gl-vis modules are updated e.g. to use glslify 6.4.1, etc.

@etpinard
CC: @plotly/plotly_js

@etpinard

etpinard commented Jan 9, 2019

Copy link
Copy Markdown
Contributor

Is glslify the only module you updated in our gl-vis deps? Sorry for being lazy and not checking your commits myself 😄

Comment threadpackage-lock.json Outdated
"vectorize-text": "^3.2.0"
},
"dependencies": {
"glslify": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm. That seems off. Looks like glslify didn't get dedupe.

Can you run npm ls glslify and paste its result here?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other packages (i.e. one layer deep) that updated to the latest for each module.
So it could be a preparation before the third attempt on: #3267
Now all at glslify 7.0.0.
Here is what npm ls glslify show:

Details ├─┬ gl-cone3d@1.2.1 (git://github.com/gl-vis/gl-cone3d.git#08ac6285dd38c2718593de178a5ec471409f34bf) │ └── glslify@7.0.0 ├─┬ gl-contour2d@1.1.4 (git://github.com/gl-vis/gl-contour2d.git#5de59b0654b6dd0f69588efecd6af63ab485bf2b) │ └── glslify@7.0.0 ├─┬ gl-error3d@1.0.10 (git://github.com/gl-vis/gl-error3d.git#33a049e477b384a1a99f2f3d6d55b211d0334d71) │ └── glslify@7.0.0 ├─┬ gl-heatmap2d@1.0.4 (git://github.com/gl-vis/gl-heatmap2d.git#9e41db108e22688625e9f16f48729482433aaa8f) │ └── glslify@7.0.0 ├─┬ gl-line3d@1.1.7 (git://github.com/gl-vis/gl-line3d.git#907b42266a48f0da6ecfecb405d70faa518f2380) │ └── glslify@7.0.0 ├─┬ gl-mesh3d@2.0.3 (git://github.com/gl-vis/gl-mesh3d.git#3256473ac4b8379a5d0a20c73676018c679d70e5) │ └── glslify@7.0.0 ├─┬ gl-plot2d@1.4.0 (git://github.com/gl-vis/gl-plot2d.git#635e24c218590ce332a98aa0258cde6214a64d64) │ └── glslify@7.0.0 ├─┬ gl-plot3d@1.6.1 (git://github.com/gl-vis/gl-plot3d.git#b2d4817d54341b337f7acd936cff565ebcc1bec3) │ ├─┬ gl-axes3d@1.4.2 (git://github.com/gl-vis/gl-axes3d.git#a65c444baafc50c9e46b8a91ecddb9bdd23fb676) │ │ └── glslify@7.0.0 │ ├─┬ gl-spikes3d@1.0.7 (git://github.com/gl-vis/gl-spikes3d.git#3aaf3b028d4afdaafff928b5f63a8ece58e9050e) │ │ └── glslify@7.0.0 │ └── glslify@7.0.0 ├─┬ gl-pointcloud2d@1.0.1 (git://github.com/gl-vis/gl-pointcloud2d.git#d0d0d20991b175083e3e5870e44a069219894ce7) │ └── glslify@7.0.0 ├─┬ gl-scatter3d@1.1.2 (git://github.com/gl-vis/gl-scatter3d.git#5b73a48623f61b6ff5dbbe25fde764e024403528) │ └── glslify@7.0.0 ├─┬ gl-select-box@1.0.2 (git://github.com/gl-vis/gl-select-box.git#6774f655862bd10c6d69a0f147c4c5ce825f0e92) │ └── glslify@7.0.0 ├─┬ gl-streamtube3d@1.1.1 (git://github.com/gl-vis/gl-streamtube3d.git#97024a61c753475cf4aab19600582425a07f7083) │ └── glslify@7.0.0 ├─┬ gl-surface3d@1.4.0 (git://github.com/gl-vis/gl-surface3d.git#31d6995fe20eb230a06c886a160456e9daf3ad69) │ └── glslify@7.0.0 ├── glslify@7.0.0 ├─┬ regl-line2d@3.0.12 (git://github.com/gl-vis/regl-line2d.git#10244979d972a52e983c39a47090d1ac8137d242) │ └── glslify@7.0.0 deduped └─┬ regl-scatter2d@3.1.2 (git://github.com/gl-vis/regl-scatter2d.git#40145179d549513bee2b44abd287514213d841f6) └── glslify@7.0.0

@etpinard

Copy link
Copy Markdown
Contributor

Ok,

image

nicely done. 💪

Go ahead and bump the gl-vis modules' versions.

Comment threadpackage.json Outdated
"regl-line2d": "^3.0.12",
"regl-scatter2d": "^3.1.2",
"regl-splom": "^1.0.5",
"regl-error2d": "git://github.com/gl-vis/regl-error2d#0d27313d932fdb8ffaed17931b7258958bce0b88",

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@etpinard missing npm permission to publish this patch. Hopefully @dy would help?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't have npm publish rights for regl-error2d either 😢

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj you should now have npm publish rights.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do have. Let me publish the new package. Thanks @etpinard.

Comment threadpackage-lock.json
"ndarray": "^1.0.16"
},
"dependencies": {
"binary-search-bounds": {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you check npm ls binary-search-bounds? I think I tried using binary-search-bounds@2.x in gl3d, but I don't think that worked out. We should double-check.

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the note. This test branch related to gl3d (dep2019...dep2019-binary-search) passed on CI.

@archmojarchmojJan 10, 2019

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

And here is the tree.

├─┬ 3d-view@2.0.0 (git://github.com/archmoj/3d-view.git#b45ff1ea06664dbbd72c758eb323e7d99b56bcf5)
│ └─┬ orbit-camera-controller@3.0.0 (git://github.com/archmoj/orbit-camera-controller.git#96ea78ca5b7f925b9cba50773915135d3665c5ee)
│ └─┬ filtered-vector@1.2.4 (git://github.com/archmoj/filtered-vector.git#eead60dee81f3d071e9766b45a1343f48a38ccd8)
│ └── binary-search-bounds@2.0.4 ├─┬ gl-contour2d@1.1.5
│ ├── binary-search-bounds@2.0.4 │ └─┬ cdt2d@1.0.0
│ └── binary-search-bounds@2.0.4 ├─┬ gl-heatmap2d@1.0.5
│ └── binary-search-bounds@2.0.4 ├─┬ gl-line3d@1.1.8
│ └── binary-search-bounds@2.0.4 ├─┬ gl-plot2d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ gl-scatter3d@1.1.3
│ └─┬ vectorize-text@3.2.0
│ └─┬ planar-graph-to-polyline@1.0.5
│ └─┬ point-in-big-polygon@2.0.0
│ ├── binary-search-bounds@1.0.0 │ ├─┬ interval-tree-1d@1.0.3
│ │ └── binary-search-bounds@1.0.0 deduped
│ └─┬ slab-decomposition@1.0.2
│ └── binary-search-bounds@1.0.0 deduped
├─┬ gl-surface3d@1.4.1
│ └── binary-search-bounds@2.0.4 ├─┬ matrix-camera-controller@2.1.3 (git://github.com/archmoj/matrix-camera-controller.git#c0f6874c35c2d980297c2b625c2bebd48b89ffff)
│ └── binary-search-bounds@2.0.4 └─┬ point-cluster@3.1.4
└── binary-search-bounds@2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@archmoj this here is now the only potentially-blocking item.

What are the differences between binary-search-bounds v1.x and v2.x?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we may leave that for another PR. It seems that I don't have permission to patch and publish those modules...

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

mikolalysenko/binary-search-bounds@d047eee#diff-b9cfc7f2cdf78a7f4b91a753d10865a2
This may be relevant to the difference between version 1 and 2.
ndarrays are not supported in Version 2.

@etpinard

Copy link
Copy Markdown
Contributor

Ok, some before and after:

on master:

image

image

now on this branch:

image

which is 🎉 , and

image

which, as you pointed out, only has mikolalysenko/binary-search-bounds@d047eee diff between v1.x and v2.x. So I'd call this an improvement!

@etpinard

Copy link
Copy Markdown
Contributor

@archmoj let's merge this in 💃

Our gl-vis modules have never been this well maintained!

@archmoj

Copy link
Copy Markdown
ContributorAuthor

Thanks @etpinard for another encouraging and great review.
Yes I think we may merge this earlier so that to give the team more time to possibly test any side effect before the v.1.44.0 release.

@archmoj
archmoj merged commit 7c52051 into masterJan 16, 2019
@archmoj
archmoj deleted the dep2019 branch January 16, 2019 18:19
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@archmoj@etpinard