Add bisweb to CORS whitelist

so https://bioimagesuiteweb.github.io/webapp/viewer.html?image=https://api.dandiarchive.org/api/assets/d62f3ac5-2a0f-4170-a2d9-37d9bb2085c0/download/ works (datasets 26, 58, 66 have .nii.gz files)
ref: https://github.com/dandi/dandi-api/issues/256

so https://bioimagesuiteweb.github.io/webapp/viewer.html?image=https://api.dandiarchive.org/api/assets/d62f3ac5-2a0f-4170-a2d9-37d9bb2085c0/download/ works (datasets 26, 58, 66 have .nii.gz files)
ref: dandi/dandi-api#256

The link seems to work without triggering a CORS error. The image is not loading but I don't know if that's a problem on their end or ours.

I see
"Access to XMLHttpRequest at 'https://api.dandiarchive.org/api/assets/d62f3ac5-2a0f-4170-a2d9-37d9bb2085c0/download/' from origin 'https://bioimagesuiteweb.github.io' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

confirming that CORR issue is no longer there, and it is some other "Error with Permissions-Policy header: Unrecognized feature: 'interest-cohort'." - yet to (re)search


dragging and dropping across monitors does not work

Testing #199023
I drag a tab from one window to another monitor and it creates the window (only sometimes, see other issues) in the current monitor's window.

https://github.com/microsoft/vscode/assets/29464607/688ebc33-65a6-4aa7-97d0-6787d42ec653

Similar as for the other drag issue, when you wait a bit before releasing the mouse, does it make it any better?

Yes if I wait a few seconds, it works.

Merging into https://github.com/microsoft/vscode/issues/198128

Same underlying reason as https://github.com/microsoft/vscode/issues/199403#issuecomment-1831268398


ExtLib temporarily not tracking this project

coq-ext-lib normally checks all dependants in its CI, but coq-certicoq takes too long to build, and exhausts the time budget.
coq-community/coq-ext-lib#135 skips the compatibility checking with CertiCoq.
Before we figure out how to add it back (e.g. by switching to GitHub Actions), please be aware of potential incompatibilities with newer versions of ExtLib, and submit complaints via GitHub Issues.

Noted!


Remake Chinese translation

Re-translated by solitary-sails, Iridium, Vessel, Lionkin Park, Qi Yun

I would release it today. Thank you!!

It is released in v1.1.4!


replace zencoding-vim with emmet-vim

Hope that VIMRC can use emmet-vim instead of the old school zencoding-vim

This should be done in latest version

Haven't replace yet?


Is it possible to change the encoding for saving gcode to UTF-8?

In Chinese system, it seems that the generated gcode is not saved in UTF-8 format, resulting in no data underneath, and klipper can't recognise it and print it (can't see the thumbnail). Manually change ‘Output.gcode’ to UTF-8 format before it can be recognised by fluidd (can see thumbnails) and printed.
Is it possible to change the saved encoding to UTF-8?
Translated by DeepL :)

update:
When I enable:“Beta: Use Unicode UTF-8 to get global language support”, it works!
Another question:
“UsedFilamentandExtruderintheG-Codefilearenot found ! choose your settings and click on the Refresh and generate button”
How do I include this data when slicing？

update:
When I enable:“Beta: Use Unicode UTF-8 to get global language support”, it works!
Another question:
“UsedFilamentandExtruderintheG-Codefilearenot found ! choose your settings and click on the Refresh and generate button”
How do I include this data when slicing？

Which slicer are you using ?

Orca Slicer Include this information in the G-Code

in the script, you have to create the preset with the same name as in the Slicer

send me a g-code example file with characters you use.
I would do my best to correct the problem

Thanks for the reply.
Comparing your screenshot with my own file, I found the problem: I have a TradRack multicolour system, so I have multiple filament name after ‘filament_settings_id’
When I use only one filament, it works fine~

@wtda , If you managed to get the script to work with your conditions, when you have time, could you summarize the steps to follow ? for someone who encountered the same problem.
Since this script is only an example solution, and must be developed and integrated into the Slicers, I can't adapt it to all cases.
But if you think any improvement is required at the earliest, let me know and I'll add it to the priority list. Thank you.
Best regards.
Salim.


Mouseover tooltip's capital I and lowercase l are the exact same glyph

Please check if your issue is not a duplicate by searching existing issues
Describe the bug
The capital i and lowercase L share the exact same font glyph in the mouseover tooltip, very confusing for non-native English speakers. Official Runescape fonts have serifs to distinguish the two.
To Reproduce
Steps to reproduce the behavior:

enable Mouse Tooltips plugin
mouseover something with a capital i, and something with a capital l
compare glyphs

Expected behavior
I expected them to be different from one another.
Screenshots

Environment (please complete the following information):

OS: Windows 10 x64
RuneLite version: <IP_ADDRESS>
Launcher version: 2.1.6

Additional context
n/a

Change the "Tooltip Font" setting to anything except "Small" under RuneLite's settings.


The number of data sets returned by querying edge sets depends on whether only one is returned _ from and _ to

ArangoDB Version:        3.6.1
Deployment Mode:        Leader/Follower ("Master/Slave")
Deployment Strategy:    Manual Start
Configuration:               notable server settings,
Infrastructure:               own __Operating System
__:        CentOS Linux release 7.6.1810
Total RAM in your machine:   251
Disks in use:     1T
Used Package:
return only _from and _to , the result count is 11

return not only _from and _to , the result count is 9

Hi,
Please note that 3.6 is EOL (see https://www.arangodb.com/subscriptions/end-of-life-notice/ for details)
I'd advise to upgrade at least to the latest 3.6 bugfix release to see whether the issue persists, but better upgrade to at least 3.8 after checking your applications compatibility.

FWIW, it doesn't appear to be reproducible with a small, arbitrary sample dataset (using the official 3.6.1 Docker image).


How to train chatterbot with emoticons?

Can we train chatterbot with smiley as input or response?
I tried using python library emojione with chatterbot but it didn't help.
anyone succeeded in doing this, your help is appreciated.

@bainadeashish I believe this should work. I'd be more than happy to look into it and add some tests to confirm that it works. There might even be some interesting potential here to add a data set containing emoticons to the chatterbot corpus

@gunthercox  thank you.
if your attempt succeeds i will add corpus for emoticons.

Hi @gunthercox ,i have update on this.
We can use emojipy --Python library for working with emojione.
There are shortcodes associated with each emoticon.
smiling face ---> shortcode is    :grinning:
Hence we can train chatbot as
Input :grinning:  response "You seems to be happy today"
Hence,the task is first convert smiley image into short code.
Hope I have written in a way you should understand it.

@bainadeashish happy to hear from you,Full emoji list  http://www.unicode.org/emoji/charts/full-emoji-list.html

@bainadeashish Thank you for that note, I'll take that into consideration. A preprocessor would probably be the most optimal way to accomplish the conversion you mentioned http://chatterbot.readthedocs.io/en/stable/preprocessors.html


Flushes append vec mmaps only if dirty

Problem
We flush append vecs a lot. Too much, some might say^1.
Some observations: the common case is append-vecs are write-once, yet we call flush() on every append vec for every snapshot. The default is every 100 slots. So we are doing a lot of unnecessary work asking the OS/kernel to re-flush something that doesn't need to be flushed again.
Summary of Changes
Track if an AppendVec's internal mmap is dirty or not. If it has been written to, then it is dirty. If it's dirty, then we flush. Otherwise, no need.
Results
On the left half of the graph is my node running regular master. On the right half I restarted the node with this PR.
Before, flushing took about 1 second. Afterwards, flushing takes about 20 milliseconds.

In addition to these speedups, we should also see improvements to the system as-a-whole, due to stress reduction of not asking the kernel to flush 432,000 files every 100 slots.

Add a counter for dirty mmap
On Mon, Jun 10, 2024, 19:56 Brooks @.***> wrote:

@brooksprumo https://github.com/brooksprumo requested your review on:
#1676 https://github.com/anza-xyz/agave/pull/1676 Flushes append vec
mmaps only if dirty.
—
Reply to this email directly, view it on GitHub
https://github.com/anza-xyz/agave/pull/1676#event-13109032053, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABVSJGJEV3JZ4G74WV6EOTZGZDL7AVCNFSM6AAAAABJDGTD7WVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGEYDSMBTGIYDKMY
.
You are receiving this because your review was requested.Message ID:
@.***>


Newsletters: add 196 (2022-04-20)

[x] Update releases/RCs, add topic links @harding
[x] Client/services section @bitschmidty
[x] LND 5810 routing: send payment metadata @Xekyo

Thanks @harding @Xekyo @adamjonas ! 📨


wayland: fix fullscreen not working on Wayland

Fixed #349

Closing as this change can lead to another issue (See https://github.com/sony/flutter-embedded-linux/issues/349#issuecomment-1661578756)


Coding conventions

Is their a code style description for this project? I am creating a pull request, and have a pretty hard time configuring my IDE to do automatic formatting.
I tried running java-formatter-plugin on my code, which uses an eclipse settings file, but cannot get it to create the same output as the checkstyle plugin expects.
http://www.jillesvangurp.com/2015/01/29/enforcing-code-conventions-in-java/

Have you checked the target folder? The checkstyle document should be in there.

You can find the checkstyle config file that is currently used at https://github.com/spotify/spotify-checkstyle-config/blob/v1.0.2/src/main/resources/spotify_checks.xml
In general you might have more success configuring your IDE to not automatically reformat any lines that you didn't personally edit


Restart button

It would be useful to have a possibility to restart typing in case of really bad performance.

Sure, thx! Will add it in the next release.


Use addons.setPreview to set the preview.

Now we use addons.setPreview and addons.getPreview introduce by the addon api.
This allows addons to decorate the preview area.
See demo:  https://gist.github.com/arunoda/df0b1f83a1189b739b9c3ecfc18e53aa
It's also possible to set the completely new preview. But it won't make sense because it can't load the iframe.

@mnmtanish could you check this?

With the post-message channel, we really don't need to create a dataId every time the page loads. So it is perfectly fine to replace the preview builder completely. The get->wrap->set thing in the gist may cause unexpected bugs and it's just kinda weird.

We used dataId in pagebus because it stored data in local storage which is global. The post-message channel only exists between the parent window and the iframe. We can set a constant key like storybook-channel as an added safety measure. But even that will only be necessary if there are other postmessage exchange between manager and preview pages which don't use the channel.

This PR is not about dataId. Let's talk about in another issue.
I want to way to write some code for designer in the preview area outside of the iframe.
What your suggestion?

This problem is very much related to dataId. It is the only thing the preview builder needs other than the kind and the story. As dataId is not necessary preview builders can be written outside react-storybook repo.
For the designer issue:
myapp/.../addons.js
import '@kadira/storybook-addon-designer/register';

storybook-addon-designer/.../manager.js
// init function
addons.setPreview((selectedKind, selectedStory) => {
  const query = qs({ selectedKind, selectedStory });
  const url = 'iframe.html?${query}';
  return (

-image-

  )
})

react-storybook/.../provider.js
// constructor
if(!addons.getPreview()) {
  // NOTE: load default preview code from preview.js instead
  addons.setPreview((selectedKind, selectedStory) => {
    const query = qs({ selectedKind, selectedStory });
    const url = 'iframe.html?${query}';
    return ;
  })
}

// renderPreview
renderPreview(selectedKind, selectedStory) {
  const previewBuilder = addons.getPreview();
  return previewBuilder(selectedKind, selectedStory);
}

Okay. So, then only one addon could set the preview.
If not, we need to throw an error.
So, user know what's going on and he/she could choose what's needed.
This is apply for both for the database and for the channel.

Okay. Not it looks good.

I'd suggest, that addons.getPreview should be preset with the default preview-function.
As suggested in the initial comment/gist.
That way addons do not need to know how to create the base preview (which could change in future versions) and it would also help addons that only decorate the preview to be mostly independent from other addons that decorate the preview.
A safer approach would be to add additional areas, where we could add components to. But for now this PR would be of great use to me, so I do not have to patch it in by myself. :)

@arunoda any plans to merge this? it currently seems like the dist files are out of sync with the src files...

@mnmtanish Do you think you could give this an look-through and choose to continue or close?


git clone from master failing.

It looks like something committed is breaking clones. I have never sean this before.
bwilcox-1234 $ git clone https://github.com/bwilcox-1234/ChatScript.git
Cloning into 'ChatScript'...
remote: Counting objects: 4200, done.
error: RPC failed; curl 18 transfer closed with outstanding read data remaining
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

I have tested this on both Mac and Ubuntu
$ git --version
git version 2.9.3 (Apple Git-75)

Hey @claytantor, have a look at this:
https://confluence.atlassian.com/bbkb/error-rpc-failed-result-18-http-code-0-301663284.html
I would also recommend switching to ssh authentication for github, which is a lot more convenient and would also make this problem disappear:
https://help.github.com/articles/adding-a-new-ssh-key-to-your-github-account/

Gotcha. Will try and report back.
On Nov 21, 2016 07:49, "Samuel Cousin"<EMAIL_ADDRESS>wrote:

Hey @claytantor https://github.com/claytantor, have a look at this:
https://confluence.atlassian.com/bbkb/error-rpc-failed-
result-18-http-code-0-301663284.html
I would also recommend switching to ssh authentication for github, which
is a lot more convenient and would also make this problem disappear:
https://help.github.com/articles/adding-a-new-ssh-key-
to-your-github-account/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bwilcox-1234/ChatScript/issues/20#issuecomment-261975887,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAY5LihjqLw1j6UGGFoexFhCyrAF88xGks5rAb1sgaJpZM4K0X2R
.

Did this get resolved?  Can it be closed?

verified working with ssh
$ git clone git@github.com:bwilcox-1234/ChatScript.git
Cloning into 'ChatScript'...
X11 forwarding request failed on channel 0
remote: Counting objects: 4859, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 4859 (delta 2), reused 0 (delta 0), pack-reused 4852
Receiving objects: 100% (4859/4859), 350.58 MiB | 2.65 MiB/s, done.
Resolving deltas: 100% (3192/3192), done.
Checking out files: 100% (1221/1221), done.
 $


Function-Expose Request in COD5752 - Get Source Doc. Outbound

Hi Team,
Could we make this function CreateFromSalesOrderHideDialog as 'External' in COD5752 Get Source Doc. Outbound?
Thanks!

Yes, we can :-) Will do!

Awesome, thanks!


python3Packages.cattrs: 1.10.0 -> 22.1.0

Description of changes
https://github.com/python-attrs/cattrs/blob/main/HISTORY.rst#2210-2022-04-03

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

New requests-cache release is still not out.


Use status LEDs in ranging examples

The delays don't seem to impede the operation, and this makes them much easier to debug.

The CI build fails on the beta channel due to an issue that seems unconnected to this pull request, and this whole project. The other channels pass. Merging.


#962

improve uI desgin

[x] Have you renamed the PR Title in a meaningful way?

PR Title: feat: Add hover effects, update contact us, and change message color

Related Issue
#962
Description

Added a hover effect on links to improve user interactivity.
Updated the "Contact Us" section for better visual appeal.
Changed the color of the message area to align with the overall design and make it stand out.

These changes enhance the user experience by providing more interactive and visually appealing UI elements.
How Has This Been Tested? ⚙

Manually tested the hover effects on links to ensure they display correctly.
Verified that the "Contact Us" section updates appear as intended.
Confirmed that the message color change does not conflict with the project’s style.

Screenshots 📷

Type of change
What sort of changes have you made:

[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)

Checklist

[x] My code follows the code style of this project.
[x] I have followed the contribution guidelines.
[x] I have performed a self-review of my own code.
[x] I have ensured my changes don't generate any new warnings or errors.
[ ] I have updated the documentation (if necessary).

This format should give the reviewers all the information they need to understand and assess your contribution. Good luck with your pull request!

resolve merge conflicts

Okay I will fix the conflict


feat: asset catalog

closes https://github.com/decentraland/sdk/issues/615

Hello @nicoecheza, a few things that I noticed see from testing:

The rendering of the selected entity seems to be broken: even though I can select entities on the tree and they show on the tree as selected (with the @) they are not always rendered with the highlight in the 3D preview. Also clicking on the cubes in the 3D preview does not always highlight the cube as selected.

The gizmos seem to have disappeared completely

The styles of the catalog when it's showing the different packs looks broken:

We should not render empty categories:

1 & 2 got broken when removing these lines from the gizmos manager (which are actually duplicated with inverted values 🤷 ):

just removed the commit and it works again (idk)
3 & 4 fixed 👍


Update back navigation for create lock screen #5699

Closes #5699

Tests not building. Maybe Xcode 13?

Tests not building. Maybe Xcode 13?

checking


Upgraded Node to 0.6.6 now won't install

I installed node 0.6.6 without using sudo as per [this article] (http://increaseyourgeek.wordpress.com/2010/08/18/install-node-js-without-using-sudo/) and now won't install. Here is the output:

npm WARN<EMAIL_ADDRESS>package.json: bugs['web'] should probably be bugs['url']

><EMAIL_ADDRESS>install /home/***********/node_projects/ircd/node_modules/now/node_modules/node-proxy
> make

BUILDING: C++ Component
Checking for program g++ or c++          : /usr/bin/g++
Checking for program cpp                 : /usr/bin/cpp
Checking for program ar                  : /usr/bin/ar
Checking for program ranlib              : /usr/bin/ranlib
Checking for g++                         : ok
Checking for node path                   : ok /home/***********/.node_libraries
Checking for node prefix                 : ok /home/***********/opt
'configure' finished successfully (0.318s)
Waf: Entering directory `/home/***********/node_projects/ircd/node_modules/now/node_modules/node-proxy/src/build'
[1/2] cxx: node-proxy.cc -> build/Release/node-proxy_1.o
npm ERR! Failed unpacking /home/***********/.npm/uglify-js/1.0.6/package.tgz
npm ERR! error installing<EMAIL_ADDRESS>Error: `tar "-zmvxpf" "/home/***********/.npm/uglify-js/1.0.6/package.tgz"`
npm ERR! error installing<EMAIL_ADDRESS>failed with 2
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.<anonymous> (/home/***********/opt/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.emit (events.js:70:17)
npm ERR! error installing<EMAIL_ADDRESS>   at maybeExit (child_process.js:359:16)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.<anonymous> (child_process.js:456:7)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.emit (events.js:67:17)
npm ERR! error installing<EMAIL_ADDRESS>   at Array.1 (net.js:314:10)
npm ERR! error installing<EMAIL_ADDRESS>   at EventEmitter._tickCallback (node.js:192:40)
npm ERR! error installing<EMAIL_ADDRESS>Error: `tar "-zmvxpf" "/home/***********/.npm/uglify-js/1.0.6/package.tgz"`
npm ERR! error installing<EMAIL_ADDRESS>failed with 2
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.<anonymous> (/home/***********/opt/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.emit (events.js:70:17)
npm ERR! error installing<EMAIL_ADDRESS>   at maybeExit (child_process.js:359:16)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.<anonymous> (child_process.js:456:7)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.emit (events.js:67:17)
npm ERR! error installing<EMAIL_ADDRESS>   at Array.1 (net.js:314:10)
npm ERR! error installing<EMAIL_ADDRESS>   at EventEmitter._tickCallback (node.js:192:40)
npm ERR! error installing<EMAIL_ADDRESS>Error: ENOENT, no such file or directory '/home/***********/node_projects/ircd/node_modules/now/node_modules/socket.io/node_modules/socket.io-client/node_modules/___xmlhttprequest.npm/package/package.json'
npm ERR! error installing<EMAIL_ADDRESS>Error: ENOENT, no such file or directory '/home/***********/node_projects/ircd/node_modules/now/node_modules/socket.io/node_modules/socket.io-client/node_modules/___websocket-client.npm/package/package.json'
npm ERR! error installing<EMAIL_ADDRESS>Error: `tar "-zmvxpf" "/home/***********/.npm/uglify-js/1.0.6/package.tgz"`
npm ERR! error installing<EMAIL_ADDRESS>failed with 2
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.<anonymous> (/home/***********/opt/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.emit (events.js:70:17)
npm ERR! error installing<EMAIL_ADDRESS>   at maybeExit (child_process.js:359:16)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.<anonymous> (child_process.js:456:7)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.emit (events.js:67:17)
npm ERR! error installing<EMAIL_ADDRESS>   at Array.1 (net.js:314:10)
npm ERR! error installing<EMAIL_ADDRESS>   at EventEmitter._tickCallback (node.js:192:40)
npm ERR! error installing<EMAIL_ADDRESS>Error: `tar "-zmvxpf" "/home/***********/.npm/uglify-js/1.0.6/package.tgz"`
npm ERR! error installing<EMAIL_ADDRESS>failed with 2
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.<anonymous> (/home/***********/opt/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR! error installing<EMAIL_ADDRESS>   at ChildProcess.emit (events.js:70:17)
npm ERR! error installing<EMAIL_ADDRESS>   at maybeExit (child_process.js:359:16)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.<anonymous> (child_process.js:456:7)
npm ERR! error installing<EMAIL_ADDRESS>   at Socket.emit (events.js:67:17)
npm ERR! error installing<EMAIL_ADDRESS>   at Array.1 (net.js:314:10)
npm ERR! error installing<EMAIL_ADDRESS>   at EventEmitter._tickCallback (node.js:192:40)
npm ERR! Error: `tar "-zmvxpf" "/home/***********/.npm/uglify-js/1.0.6/package.tgz"`
npm ERR! failed with 2
npm ERR!     at ChildProcess.<anonymous> (/home/***********/opt/lib/node_modules/npm/lib/utils/tar.js:217:20)
npm ERR!     at ChildProcess.emit (events.js:70:17)
npm ERR!     at maybeExit (child_process.js:359:16)
npm ERR!     at Socket.<anonymous> (child_process.js:456:7)
npm ERR!     at Socket.emit (events.js:67:17)
npm ERR!     at Array.1 (net.js:314:10)
npm ERR!     at EventEmitter._tickCallback (node.js:192:40)

the first line of meaningless warning is always there, so no worries. are you using a mac? if so try installing xcode. another possibility is that you don't have npm package manager installed, as you just git clone the repository. Last, i think you can try "npm install uglify" and "npm install socket.io" beforehand. hope this can help!

the first line of meaningless warning is always there, so no worries. are you using a mac? if so try installing xcode. another possibility is that you don't have npm package manager installed, as you just git clone the repository. Last, i think you can try "npm install uglify" and "npm install socket.io" beforehand. hope this can help!

Upgrade your tar installation to the latest version and it will be fixed.

Upgrade your tar installation to the latest version and it will be fixed.

@PastorBones what are the results when you try to npm install uglify-js by itself? Do you still encounter the errors or does it succeed?
Eric

@ericz I am able to install uglify-js both with the -g flag and without. However now still fails with the uglify tar error even though uglify is installed both globally and locally within the directory.

Well a quick fix would be to git clone the repo and npm install that way.
Additionally, if you have npm install X -g make sure you also npm link X
Other than that this doesn't seem to be a widespread issue, I am unable to
replicate it.
On Mon, Jan 2, 2012 at 7:17 PM, PastorBones <
<EMAIL_ADDRESS>
wrote:

@ericz I am able to install uglify-js both with the -g flag and without.
However now still fails with the uglify tar error even though uglify is
installed both globally and locally within the directory.

Reply to this email directly or view it on GitHub:
https://github.com/Flotype/now/issues/169#issuecomment-3336054

--
510-691-3951
EECS Student at UC Berkeley
http://ericzhang.com

I think it may have to do with the way I installed Node (without sudo) as I'm having same errors trying to install socket.io. I will probably revert to using sudo again and hoping that fixes the issue.

Ok! Let me know how it turns out
On Mon, Jan 2, 2012 at 8:02 PM, PastorBones <
<EMAIL_ADDRESS>
wrote:

I think it may have to do with the way I installed Node (without sudo) as
I'm having same errors trying to install socket.io. I will probably
revert to using sudo again and hoping that fixes the issue.

Reply to this email directly or view it on GitHub:
https://github.com/Flotype/now/issues/169#issuecomment-3336237

--
510-691-3951
EECS Student at UC Berkeley
http://ericzhang.com

Eh, I haven't installed Node via sudo in more than half a year. Did you set your prefix correctly when installing?
Also, you can generally tell if sudo's required if it gives you a "Permission denied" error.

I figured out the main issue...after installing node v0.6 I never reinstalled npm!! Which has fixed many of the tar errors, however now I'm getting an error at the end that says cb() never called

****@p****:~/node_projects/shared/node_modules$ npm -g install now
npm http GET https://registry.npmjs.org/now
npm http 304 https://registry.npmjs.org/now
npm http GET https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/node-proxy
npm http 304 https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/node-proxy
npm WARN<EMAIL_ADDRESS>package.json: bugs['web'] should probably be bugs['url']

><EMAIL_ADDRESS>install /home/*****/opt/lib/node_modules/now/node_modules/node-proxy
> make

BUILDING: C++ Component
npm http GET https://registry.npmjs.org/socket.io-client/0.8.7
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http GET https://registry.npmjs.org/redis/0.6.7
Checking for program g++ or c++          : /usr/bin/g++
Checking for program cpp                 : /usr/bin/cpp
Checking for program ar                  : /usr/bin/ar
Checking for program ranlib              : /usr/bin/ranlib
Checking for g++                         : ok
Checking for node path                   : ok /home/*****/.node_libraries
Checking for node prefix                 : ok /home/*****/opt
'configure' finished successfully (0.301s)
Waf: Entering directory `/home/*****/opt/lib/node_modules/now/node_modules/node-proxy/src/build'
[1/2] cxx: node-proxy.cc -> build/Release/node-proxy_1.o
npm http 304 https://registry.npmjs.org/socket.io-client/0.8.7
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/redis/0.6.7
npm http GET https://registry.npmjs.org/uglify-js/1.0.6
npm http GET https://registry.npmjs.org/websocket-client/1.0.0
npm http GET https://registry.npmjs.org/xmlhttprequest/1.2.2
npm http 304 https://registry.npmjs.org/uglify-js/1.0.6
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.2.2
[2/2] cxx_link: build/Release/node-proxy_1.o -> build/Release/node-proxy.node
npm http 304 https://registry.npmjs.org/websocket-client/1.0.0
Waf: Leaving directory `/home/*****/opt/lib/node_modules/now/node_modules/node-proxy/src/build'
'build' finished successfully (8.262s)
npm ERR! cb() never called!
npm ERR!
npm not ok

Everything seems to be working though!

Closing. Feel free to reopen if there are additional issues.


Documentation should explain the best way to use this repository

The documentation states "clone this repository to begin".
We should provide a short description of alternate options.
There are three options:

download as a zip
clone (you will not be able to push changes to this repository unless you are added as a developer)
fork (makes a copy of the repository into your own github account, which you can then clone and modify as desired)

If you only want the latest version to develop on, then the zip is a simple option. Clone is the easiest if you want to view the entire history of the project, and if you may at some point want to contribute back.

Agreed. I'll take a crack at writing this up.


Add support for Openshift Container Platform

Small check to see if OCPs oc command line tool is installed and if so change label and binary.

LGTM.  Thanks Petter!


Placeholder to mobile

Placeholder on desktop doesn’t get copied over to the mobile inputs.

Expected Behavior
The Placeholder attribute that’s set on my input should be copied to the mobile input
Current Behavior
The Placeholder isn’t being copied to the new inputs that are created for mobile
Possible Solution
Copy the Placeholder attribute when the mobile inputs are created, or allow a Placeholder Option when creating the datepicker
Steps to Reproduce (for bugs)
http://pelicaninn.nathanaelphilip.com
Your Environment

Version used: 2.3.7
Browser Name and version: Safari
Operating System and version (desktop or mobile): Safari iOS10
Link to your project:

yay!

incorporated in v2.4.2 and released as of now.
Thanks for reporting the issue!

Hi,
I'm using v2.4.4 and it still appears to be an issue in Chrome iOS (Version 56.0).

I'm on 3.6.3 and this appears to still be an issue on both Chrome and Safari on iOS

This isn't a problem with flatpickr.
See #1094 #1103

Understood. Looks like there are some decent workaround in #1103 . Thanks.


"Indexing the Kythe Repository" doesn't work

Steps that I went through:

Go to https://kythe.io/examples/
Install the latest Kythe release into /opt/kythe
The line "See /opt/kythe/README for more information" is untrue, there is no README, but there is a README.md
Scroll to "Indexing the Kythe Repository"
run mkdir command (Success!)
Run ./kythe/extractors/bazel/extract.sh "$PWD" .kythe_compilations (Failure)

./kythe/extractors/bazel/extract.sh: line 50: KYTHE_OUTPUT_DIRECTORY: Missing output directory

Set KYTHE_OUTPUT_DIRECTORY to ./.kythe_compilations based on context clues from the "Extracting compilations" section
Run ./kythe/extractors/bazel/extract.sh "$PWD" .kythe_compilations (Failure)

+ : .kythe_compilations JSON
+ [[ -n '' ]]
+ [[ -n '' ]]
+ KYTHE_RELEASE=/kythe
+ [[ -n '' ]]
+ /kythe/bazelisk query ''
+ xargs -t -L 30 /kythe/bazel_wrapper.sh --bazelrc=/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/kythe --
./kythe/extractors/bazel/extract.sh: line 81: /kythe/bazelisk: No such file or directory
/kythe/bazel_wrapper.sh --bazelrc=/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/kythe --
xargs: /kythe/bazel_wrapper.sh: No such file or directory

I think it has the incorrect path, shouldn't it be /opt/kythe? Looks like there are some hardcoded /kythes in that file, replace all of them with the $KYTHE_RELEASE environment variable.
Replace the definition of KYTHE_RELEASE with KYTHE_RELEASE=${KYTHE_RELEASE-/kythe} so that if the caller sets it then they get the value they proposed
Run ./kythe/extractors/bazel/extract.sh "$PWD" .kythe_compilations (Failure)

+ : .kythe_compilations JSON
+ [[ -n '' ]]
+ [[ -n '' ]]
+ KYTHE_RELEASE=/opt/kythe
+ [[ -n '' ]]
+ /opt/kythe/bazelisk query ''
./kythe/extractors/bazel/extract.sh: line 81: /opt/kythe/bazelisk: No such file or directory
+ xargs -t -L 30 /opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
/opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
xargs: /opt/kythe/bazel_wrapper.sh: No such file or directory

Looks like there are 2 issues here:

./kythe/extractors/bazel/extract.sh: line 81: /opt/kythe/bazelisk: No such file or directory

# This feels icky, but seems to be the best way to install it?
sudo curl -L https://github.com/bazelbuild/bazelisk/releases/download/v1.1.0/bazelisk-linux-amd64 > /opt/kythe/bazelisk && sudo chmod a+xr /opt/kythe/bazelisk

/opt/kythe/bazel_wrapper.sh: No such file or directory

sudo cp ./kythe/extractors/bazel/bazel_wrapper.sh /opt/kythe/bazel_wrapper.sh && sudo chmod a+xr /opt/kythe/bazel_wrapper.sh

Run ./kythe/extractors/bazel/extract.sh "$PWD" .kythe_compilations (Failure)

+ : .kythe_compilations JSON
+ [[ -n '' ]]
+ [[ -n '' ]]
+ KYTHE_RELEASE=/opt/kythe
+ [[ -n '' ]]
+ /opt/kythe/bazelisk query ''
+ xargs -t -L 30 /opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
Loading: 0 packages loaded
ERROR: Error while parsing '': premature end of input
Loading: 0 packages loaded
Loading: 0 packages loaded
/opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
+ /kythe/bazelisk --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
/opt/kythe/bazel_wrapper.sh: line 30: /kythe/bazelisk: No such file or directory
+ RETVAL=127
+ [[ 127 -eq 1 ]]
+ [[ 127 -ne 0 ]]
+ echo 'Bazel build failed with exit code: 127'
Bazel build failed with exit code: 127
+ exit 1

No worries, I know how to fix /opt/kythe/bazel_wrapper.sh: line 30: /kythe/bazelisk: No such file or directory.  I replace all instances of /kythe in /opt/kythe/bazel_wrapper.sh with $KYTHE_RELEASE
Run ./kythe/extractors/bazel/extract.sh "$PWD" .kythe_compilations (Failure)

+ : .kythe_compilations JSON
+ [[ -n '' ]]
+ [[ -n '' ]]
+ KYTHE_RELEASE=/opt/kythe
+ [[ -n '' ]]
+ /opt/kythe/bazelisk query ''
+ xargs -t -L 30 /opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
Loading: 0 packages loaded
ERROR: Error while parsing '': premature end of input
Loading: 0 packages loaded
Loading: 0 packages loaded
/opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
+ KYTHE_RELEASE=/opt/kythe
+ /opt/kythe/bazelisk --bazelrc=/opt/kythe/extractors.bazelrc /usr/local/google/home/achew/kythe .kythe_compilations --override_repository kythe_release=/opt/kythe --
Command '/usr/local/google/home/achew/kythe' not found. Try 'bazel help'.
+ RETVAL=2
+ [[ 2 -eq 1 ]]
+ [[ 2 -ne 0 ]]
+ echo 'Bazel build failed with exit code: 2'
Bazel build failed with exit code: 2
+ exit 1

I'm pretty unsure what do do here... looking at the script it doesn't actually seem to do any argument parsing. I theorize that the docs are out of date and that extract.sh used to parse command line flags in an order but this was replaced by environment variables. this is where I feel like I've walked off the beaten path and everything past here is suspect. Proposed solution is to change the invocation of extract.sh to ./kythe/extractors/bazel/extract.sh build "$PWD"
Run ./kythe/extractors/bazel/extract.sh build "$PWD" (New failure)

+ : .kythe_compilations JSON
+ [[ -n '' ]]
+ [[ -n '' ]]
+ KYTHE_RELEASE=/opt/kythe
+ [[ -n '' ]]
+ /opt/kythe/bazelisk query ''
+ xargs -t -L 30 /opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc build /usr/local/google/home/achew/kythe --override_repository kythe_release=/opt/kythe --
Loading: 0 packages loaded
ERROR: Error while parsing '': premature end of input
Loading: 0 packages loaded
Loading: 0 packages loaded
/opt/kythe/bazel_wrapper.sh --bazelrc=/opt/kythe/extractors.bazelrc build /usr/local/google/home/achew/kythe --override_repository kythe_release=/opt/kythe --
+ KYTHE_RELEASE=/opt/kythe
+ /opt/kythe/bazelisk --bazelrc=/opt/kythe/extractors.bazelrc build /usr/local/google/home/achew/kythe --override_repository kythe_release=/opt/kythe --
ERROR: Skipping '/usr/local/google/home/achew/kythe': not a valid absolute pattern (absolute target patterns must start with exactly two slashes): '/usr/local/google/home/achew/kythe'
WARNING: Target pattern parsing failed.
INFO: Analyzed 0 targets (0 packages loaded, 0 targets configured).
INFO: Found 0 targets...
ERROR: command succeeded, but there were errors parsing the target pattern
INFO: Elapsed time: 27.483s, Critical Path: 0.04s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
+ RETVAL=1
+ [[ 1 -eq 1 ]]
+ echo 'Not all bazel targets built successfully, but continuing anyways.'
Not all bazel targets built successfully, but continuing anyways.
+ exit 0
+ mkdir -p .kythe_compilations
+ find 'bazel-out/*/extra_actions/external/kythe_release' -name '*.kzip'
+ xargs -r /opt/kythe/tools/kzip merge --append --encoding JSON --output .kythe_compilations/compilations.kzip
find: ‘bazel-out/*/extra_actions/external/kythe_release’: No such file or directory
+ /opt/kythe/fix_permissions.sh .kythe_compilations
./kythe/extractors/bazel/extract.sh: line 89: /opt/kythe/fix_permissions.sh: No such file or directory

Add the fix_permissions.sh file to the release with sudo cp ./kythe/release/base/fix_permissions.sh /opt/kythe/ && sudo chmod a+rx /opt/kythe/fix_permissions.sh
Looking at the invocations of bazelisk it looks like there is no build target provided. Looking through the bash script there is a variable $KYTHE_BAZEL_TARGET that looks quite promising.
export KYTHE_BAZEL_TARGET="//..."
Run ./kythe/extractors/bazel/extract.sh build "$PWD" (Build failures)
Looks like normal "I'm missing a dependency" issues. Found this in a dockerfile

apt-get install -y \
      # Kythe C++ dependencies
      uuid-dev flex bison g++ \
      # Kythe misc dependencies
      asciidoc source-highlight graphviz

Run ./kythe/extractors/bazel/extract.sh build -k "$PWD" (This time with -k, just in case)
Several minutes later... Success!

I'm really excited that it was this easy! I took notes so I could attempt a PR to fix these. Expect one in the next day or two.

Sorry you went through all that. That script has evolved into one that assumes it will be executed in a specific docker environment. We should remove the link to it.

@salguarnieri don't be sorry at all, I'm working through indexing right now to see if there are any more issues. If I run into any should I post them on here or as a separate bug?

You can post them here. We appreciate the feedback!

Do you have any ideas on
Step 11/22 : ADD third_party/javac/javac-9-dev-r4023-1.jar /kythe/bin/javac9.jar
Target //kythe/release:docker failed to build

for a bazel build //kythe/release:docker?

@achew22  changing that line to this worked for me
RUN wget https://repo1.maven.org/maven2/com/google/errorprone/javac/9-dev-r4023-1/javac-9-dev-r4023-1.jar -O /kythe/bin/javac9.jar

extracting-other-bazel-based-repositories and "extracting-the-kythe-repository " both don't work on the l.gcr.io/google/bazel:3.1.0 docker image: https://travis-ci.com/github/TokTok/dockerfiles/builds/162740118

The release doesn't work on ubuntu 18.04 either. What does it work on?

@iphydf Can you open up a new issue saying what you are trying to do and what isn't working?


Unable to load igintion-transport9

after Installing ign-transport9 from tutorial
(
installing from source because when installing
sudo apt-get install libignition-transport9-dev
i get an error
Unable to locate package libignition-transport9-dev
)
when trying to cmake ign-sensors i get:
`
Could not find a package configuration file provided by
"ignition-transport9" with any of the following names:
ignition-transport9Config.cmake
ignition-transport9-config.cmake

`

ignition-transport9 has not been released yet so you'll need to install from source.
I recommend following the instructions here for installing the whole ignition stack, either from source or debs: https://ignitionrobotics.org/docs/citadel

Closing since the version is expected not to exist.
Just curious @eladpar , howcome you were trying to install that? Did you see instructions somewhere?

Closing since the version is expected not to exist.
Just curious @eladpar , howcome you were trying to install that? Did you see instructions somewhere?

yes .
after trying to install from Source ign-sensors
one of the prerequisites is ign-transpot -> instaalation Guide ->
https://ignitionrobotics.org/api/transport/9.0/installation.html
I guess the installation guide is corrupt


Pins/Connectors Widget

What is the feature being requested?
Implement a connector view tab
This will display the netlist - show the names of all the nets, connectors in the design and their properties (e.g. which component they belong to and what position they are at).
What are use cases for this feature?
Users will be able to easily see pins/connectors

The net list is a draft pull request, but not finished. https://github.com/Qiskit/qiskit-metal/pull/837


Change Customization topic example

Hi guys,
First, nice work with Djoser, this lib help us a lot!
So, I did this PR to update a Customization documentation to use an existing method because send_email method does not exist in RegistrationView.

Coverage remained the same at 96.053% when pulling e8db8e2edf4ce77b7bdab8c3ba40ab5e1f5d32bb on lerrua:fix_customization_topic into 128812d4852af95ddff5907e0fe1002eadcf1e64 on sunscrapers:master.

We're sorry for long response time. Great catch! I'm merging it in!


glVertexAttribDivisor gives error in macOS arm64

Version
3.3.0 (nightly)
Platform
macOS arm64
JDK
openjdk 17.0.1
Module
opengl
Bug description
glVertexAttribDivisor on Mac gives error everywhere where I have tried using it.
I have tried GL33.glVertexAttribDivisor(0, 0) and non zeros too.
On Linux it works well.
Stacktrace or crash log output
FATAL ERROR in native method: Thread[main,5,main]: No context is current or a function that is not available in the current context was called. The JVM will abort execution.
	at org.lwjgl.opengl.GL33C.glVertexAttribDivisor(Native Method)
	at org.lwjgl.opengl.GL33.glVertexAttribDivisor(GL33.java:614)

Exception Type:        EXC_BAD_ACCESS (SIGABRT)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Codes:       0x0000000000000001, 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

VM Region Info: 0x8 is not in any region.  Bytes before following region:<PHONE_NUMBER>
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      UNUSED SPACE AT START
--->
      __TEXT                      102d74000-102d78000    [   16K] r-x/r-x SM=COW  ...mebrew/*/java

Application Specific Information:
abort() called

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x19e1419b8 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x19e174eb0 pthread_kill + 288
2   libsystem_c.dylib             	       0x19e0b2314 abort + 164
3   libjvm.dylib                  	       0x1043f5d5c os::abort(bool, void*, void const*) + 28
4   libjvm.dylib                  	       0x1041a36f8 jni_FatalError + 196
5   liblwjgl.dylib                	       0x103d2eba8 0x103d00000 + 191400
6   ???                           	       0x10c6358ac ???
7   ???                           	       0x10c631fc8 ???
8   ???                           	       0x10c631fc8 ???
9   ???                           	       0x10c632508 ???
10  ???                           	       0x10c631fc8 ???
11  ???                           	       0x10c632508 ???
12  ???                           	       0x10c632508 ???
13  ???                           	       0x10c631fc8 ???
14  ???                           	       0x10c632508 ???
15  ???                           	       0x10c631fc8 ???
16  ???                           	       0x10c632508 ???
17  ???                           	       0x10c631fc8 ???
18  ???                           	       0x10c631fc8 ???
19  ???                           	       0x10c6322c0 ???
20  ???                           	       0x10c631fc8 ???
21  ???                           	       0x10c631e68 ???
22  ???                           	       0x10c631fc8 ???
23  ???                           	       0x10c631fc8 ???
24  ???                           	       0x10c62c140 ???
25  libjvm.dylib                  	       0x1041533c0 JavaCalls::call_helper(JavaValue*, methodHandle const&, JavaCallArguments*, JavaThread*) + 564
26  libjvm.dylib                  	       0x1041abf58 jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, JavaThread*) + 220
27  libjvm.dylib                  	       0x1041aed04 jni_CallStaticVoidMethod + 224
28  libjli.dylib                  	       0x102eb1934 JavaMain + 2888
29  libjli.dylib                  	       0x102eb3cb4 __JVMInit_block_invoke + 80
30  Foundation                    	       0x19f0f4590 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 24
31  Foundation                    	       0x19f0f4438 -[NSBlockOperation main] + 104
32  Foundation                    	       0x19f0f43c8 __NSOPERATION_IS_INVOKING_MAIN__ + 24
33  Foundation                    	       0x19f0f360c -[NSOperation start] + 804
34  Foundation                    	       0x19f134914 __NSThreadPerformPerform + 212
35  CoreFoundation                	       0x19e240c5c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
36  CoreFoundation                	       0x19e240ba8 __CFRunLoopDoSource0 + 208
37  CoreFoundation                	       0x19e240894 __CFRunLoopDoSources0 + 268
38  CoreFoundation                	       0x19e23f208 __CFRunLoopRun + 820
39  CoreFoundation                	       0x19e23e734 CFRunLoopRunSpecific + 600
40  libjli.dylib                  	       0x102eb3374 CreateExecutionEnvironment + 400
41  libjli.dylib                  	       0x102eaf8b0 JLI_Launch + 1148
42  java                          	       0x102d77bb0 main + 396
43  dyld                          	       0x102f290f4 start + 520

Can you show how you create the window/context (including any glfwWindowHint() calls)?

Can you show how you create the window/context (including any glfwWindowHint() calls)? It's very likely that you have not explicitly specified that you want an OpenGL 3.3 core context via GLFW, in which case macOS will give you an OpenGL 2.1 context.

Yes, you're right, I forgot this:
GLFW.glfwWindowHint(GLFW.GLFW_CONTEXT_VERSION_MAJOR, 3)
GLFW.glfwWindowHint(GLFW.GLFW_CONTEXT_VERSION_MINOR, 3)
GLFW.glfwWindowHint(GLFW.GLFW_OPENGL_PROFILE, GLFW.GLFW_OPENGL_CORE_PROFILE)
GLFW.glfwWindowHint(GLFW.GLFW_OPENGL_FORWARD_COMPAT, 1)

Thanks


big difference between setting title and not setting title

We are using cross decoder to rerank the results.  for some QA pairs. We use following format to get the ranking scores.
<query, para1, title1>
<query, para2, title2>
<query, para3, title3>

model.matching(query: List[str], para: List[str], title: List[str])

There's one observation I notice is, for the same question, setting title give me much better results, top1 or top2. However, If I do not set title,  it is really bad (~top10 for 20 records).
I am curious why title makes a big difference here?  In my case, for query, we have many tiles with same name.  I felt adding title is not a big deal but it is

https://github.com/PaddlePaddle/RocketQA/blob/1746b938d659c7f8d0b9f960e3199dcbd945adac/rocketqa/encoder/cross_encoder.py#L160-L166


Couldn't create node with same name?

I use python api to create topology, and found that it couldn't create node with same name, since the two different switches have same port name.
And another thing is the return value of client.noderule_create has no TID but a UUID, when i query G.V().Has('TID', 'uuid'), there's nothing returned.
But the host node which created by agent has same eth0, eth1, why these can be created? Did i miss something?

I would rather use the websocket API that will allow you to specify an ID instead of using the Name. You can see an example here:
https://github.com/skydive-project/skydive/blob/master/contrib/python/api/samples/inject-nodes1.py

What does the host mean in GraphElement?

I have successfully created the topology by websocket api, but the strange thing is that when i restart the analyzer, the topology is missing.

Sorry that is something I didn't mention but the way the websocket API is working is more or less how the agent communicates with the analyzer, so this is something which is not persistent and the client has to re-inject if the analyzer is stopped. I'll have a look at the issue you have with the node/edge-rules so that you could use it.

Thanks for your kind help, i'll close this issue.


[BUG] correct the navbar of the iskcon page

https://akshitagupta15june.github.io/Moksh/Iskcon/event.html
make it similar to ar meditation page

Please assign it to me

@akshitagupta15june please assign this to me

Please assign it to me.

@akshitagupta15june  please assign this issue to me because I want to work on it.

@akshitagupta15june mam can you please assign this to me. It'll be my first contribution in Moksh.

assigning

I want to work on your project.Please assign the issue to me

Please assign this issue to me ma'am.


Bad Register Modal on Firefox

In my browser, Firefox, the register modal looked bad. Moreover, I can't scroll the modal so I can't fill up the form.

okey

Closed with #325


Brainstorm data quality features

Delta Live Tables added great data quality features that allow users to define filters / rules that identify invalid records.
Since DLT is not OSS yet, and according to DBX that will still take some time, I think it would be beneficial for our users to provide some Data Quality features.
Some ideas:

Filter Framework that allows to identify invalid records
Ability to automatically drop invalid rows
Ability to automatically mark rows as invalid in target table
Ability to write invalid rows to "DLQ" table
Ability to fail on invalid records

WDYT @MrPowers

@robertkossendey - these sound like good suggestions.  I'm guessing some external libs would help for this type of functionality (Great Expectations or PyDeequ perhaps), but don't want to add any dependencies to this lib.  Let's keep this open as a "meta-issue".  When you have ideas for individual functions, feel free to open up a separate issue and we can chat in detail before you put in the work.  Thanks!

@MrPowers I wouldn't like to use any other framework tbh. If you're okay with it I would create a PoC PR that allows you to specify a condition and if that condition is not fulfilled a write would fail.

@robertkossendey - yep, PoC PR sounds like a great next step!

@robertkossendey @MrPowers
Hey guys I actually had built a library to mock the dlt behaviors outside of databricks: dlt-with-debug
I think I can take out the expectation mock apis and add them here in mack.

@souvik-databricks very cool! Maybe you can open up a PR and we can collaborate on that then :)

I will raise the PR on this @robertkossendey


Fix SETNX and MSETNX commands can't guarantee atomicity

@git-hulk @ShooterIT Do you guys remember how this atomicity was broken? Is there any example?
seem the change casue this issue:
<IP_ADDRESS>:6379> msetnx k v1 k v2
(integer) 1

<IP_ADDRESS>:6666> msetnx k v1 k v2
(integer) 0

Redis allow we overriding the same key but kvrocks will fail in this case

Hi @enjoy-binbin

Is there any example?

It should be a bit hard to reproduce, but we did exist since the MSET would write key-value one by one, so it will be partially written the DB if Kvrocks exited in the middle way. The inconsistent behavior you mentioned should be also affected by this implementation.

we already checked whether the key exists before:
  for (StringPair pair : pairs) {
    keys.emplace_back(pair.key);
  }
  if (Exists(keys, &exists).ok() && exists > 0) {
    return rocksdb::Status::OK();
  }

so the exist in for loop looks a bit redundant, in which case we need this exist (the for loop one, i.e. this PR diff)?
and another question is do we want to fix this inconsistency?

we already checked whether the key exists before:
  for (StringPair pair : pairs) {
    keys.emplace_back(pair.key);
  }
  if (Exists(keys, &exists).ok() && exists > 0) {
    return rocksdb::Status::OK();
  }

so the exist in for loop looks a bit redundant, in which case we need this exist (the for loop one, i.e. this PR diff)? and another question is do we want to fix this inconsistency?

Yes, we should use MGet and MSet at once instead of the loop writes.

you mean i remove the for (StringPair pair : pairs) { loop, and then just call a MSet?
something like this:
-  std::string ns_key;
-  for (StringPair pair : pairs) {
-    AppendNamespacePrefix(pair.key, &ns_key);
-    LockGuard guard(storage_->GetLockManager(), ns_key);
-    if (Exists({pair.key}, &exists).ok() && exists == 1) {
-      return rocksdb::Status::OK();
-    }
-    std::string bytes;
-    Metadata metadata(kRedisString, false);
-    metadata.expire = expire;
-    metadata.Encode(&bytes);
-    bytes.append(pair.value.data(), pair.value.size());
-    auto batch = storage_->GetWriteBatchBase();
-    WriteBatchLogData log_data(kRedisString);
-    batch->PutLogData(log_data.Encode());
-    batch->Put(metadata_cf_handle_, ns_key, bytes);
-    auto s = storage_->Write(storage_->DefaultWriteOptions(), batch->GetWriteBatch());
-    if (!s.ok()) return s;
-  }
+  rocksdb::Status s = MSet(pairs, ttl);
+  if (!s.ok()) return s;
+

Yes, but need to check if any key exists before the MSET. MSETNX now is an exclusive command and it'd be better to lock those keys and then remove the exclusive flag from the command.

MSETNX now is an exclusive command and it'd be better to lock those keys and then remove the exclusive flag from the command.

I am not very familiar with the lock part, can you describe it in detail?
the code now may look like:
rocksdb::Status String::MSetNX(const std::vector<StringPair> &pairs, uint64_t ttl, bool *flag) {
  *flag = false;

  int exists = 0;
  std::vector<Slice> keys;
  keys.reserve(pairs.size());
  for (StringPair pair : pairs) {
    keys.emplace_back(pair.key);
  }
  if (Exists(keys, &exists).ok() && exists > 0) {
    return rocksdb::Status::OK();
  }

  rocksdb::Status s = MSet(pairs, ttl);
  if (!s.ok()) return s;

  *flag = true;
  return rocksdb::Status::OK();
}

do you want me to lock the keys before the Exists call (doing a MultiLockGuard guard?)? This will result in an additional AppendNamespacePrefix call since the lock need to call AppendNamespacePrefix and then in Exists it will also need to call AppendNamespacePrefix.
Note that in MSet, there is another AppendNamespacePrefix call, and Mset will do a LockGuard guard.

Yes, need to use MultiLockGuard to lock multi keys, and MSet needs to do a bit of change for supporting the non-lock calls. For calling AppendNamespacePrefix twice, I think it's fine since it is just a little CPU overhead.


Fix deps make function, activate venv before installing crate

What's new in this PR?
Fixes #185
Makefile rule is executed in it's down subshell. Therefore, the activation of the virtual environment in the line with source $(VENV_BIN)/activate was not affecting the subsequent line.

@emdoyle Maybe a good idea to update CI workflow, like this step, and use make functions? Could be a good test for those functions.

@emdoyle Maybe a good idea to update CI workflow, like this step, and use make functions? Could be a good test for those functions.

Yup, that's a great idea. I'll do a pass on the CI action, there are a few other things that change in #183


Haskell HLS v<IP_ADDRESS> should be enabled on .cabal files

Description
The super-recent release of HLS <IP_ADDRESS> allows HLS to work on .cabal files, but only that version (and up). If it is feasible to first detect this and then set the filetypes field, I would be more than happy to make a PR. Otherwise I am sure it can be solved in a custom manner.
Neovim version
--irrelevant
Nvim-lspconfig version
No response
Operating system and version
macOS 12.6.1
Affected language servers
hls
Steps to reproduce
--irrelevant
Actual behavior
https://github.com/neovim/nvim-lspconfig/blob/7d0ce54a4cf6e844d87e49d1576c0fffb6d27a6e/lua/lspconfig/server_configurations/hls.lua#L6
Only supported on haskell and lhaskell filetypes.
Expected behavior
also cabal filetype
Minimal config
--irrelevant

LSP log
--irrelevant

you can make a pr for this.


Document adding ML nodes

Looks like adding ML nodes is missing in the documentation.
I could only figure the right value when tried deployment with some dummy value for topology id, Terraform threw the list of  acceptable values:
'valid topology IDs are "coordinating", "hot_content", "warm", "cold", "frozen", "master", "ml"
Whereas documentation says the following topology ids are supported :
hot_content, warm, cold, coordinating or master

Thanks @AntonChernysh for catching this and letting us know! 🙇♀ I've opened up the above PR to fix this.


⚠ LPDM Handbook (hosted on Divio) has degraded performance

In 7dbe1b1, LPDM Handbook (hosted on Divio) (https://repohubdev.tk) experienced degraded performance:

HTTP code: 500
Response time: 6188 ms

Resolved: LPDM Handbook (hosted on Divio) performance has improved in e56f5c9.


⚠ Bofrost.de has degraded performance

In 7adfc1a, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 997 ms

Resolved: Bofrost.de performance has improved in 9588f2c after 6 minutes.


fix(core): Improve performance of registry lookups

Resolves #116.

Pull Request Test Coverage Report for Build 350

272 of 318 (85.53%)  changed or added relevant lines in 14 files are covered.
12 unchanged lines in 4 files lost coverage.
Overall coverage decreased (-0.5%) to 77.886%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/core/src/registry/MultivalueRegistry.js
15
16
93.75%

packages/classic/src/impl/cursor.js
4
5
80.0%

packages/classic/src/effect/impl.js
30
32
93.75%

packages/core/src/registry/impl/Trie.js
83
85
97.65%

packages/core/src/registry/Registry.js
14
16
87.5%

packages/classic/src/update/impl.js
25
28
89.29%

packages/core/src/registry/RegistryChain.js
48
52
92.31%

packages/classic/src/registry/ActionRegistry.js
36
67
53.73%

Files with Coverage Reduction
New Missed Lines
%

packages/classic/src/impl/cursor.js
1
68.18%

packages/core/src/registry/PatternRegistry.js
1
97.06%

packages/classic/src/update/impl.js
1
79.17%

packages/core/src/registry/AbstractRegistry.js
9
4.0%

Totals

Change from base Build 346:
-0.5%

Covered Lines:
1005

Relevant Lines:
1217

💛  - Coveralls


Add Secondary Market Functionality to Broker Pallet

After extensive deliberation and discussion at Lastic, we have concluded that integrating a secondary marketplace feature directly into the broker pallet is the most efficient approach. Given the limited scope of this addition and the minimal security risks involved, incorporating this functionality into the broker pallet is both practical and effective.
An alternative method could involve creating a separate chain with XCM functionality to handle core transfers and listings. However, maintaining such a solution would introduce significant financial and development overhead. For a feature of this scale, adding three functions directly to the broker pallet is a simpler and more sustainable solution.

There are a couple of reasons why I believe this isn’t a good idea. One might argue that I might be biased because I am working on a project that, among other things, addresses the issues mentioned in this RFC. However, I will do my best to genuinely review this RFC. The following list outlines why I don’t consider implementing marketplace functionality into the broker pallet to be a good idea:

It is important to consider who actually needs Coretime in the first place. Currently, the consumers of Coretime are parachains. Many of these parachains share the goal of being decentralized, self-governing entities. To achieve this goal, a parachain cannot depend on a specific group of people for Coretime procurement. Adding functionality to the broker pallet that resembles a regular NFT marketplace is not the ideal solution.
As mentioned, parachains are transparent, autonomous entities. Due to their transparency, they may encounter issues when interacting with the marketplace described in this RFC. One of the main problems is front-running. Since parachains are transparent, meaning anyone can foresee their market actions, there is a risk that someone could purposefully purchase the region the parachain is looking to procure just before it does. This could leave the parachain without any Coretime, thereby halting its operations.
A possible solution could be for the parachain to rely on a set group of people for Coretime procurement, but this would go against the goal of decentralization.

The user who listed the region for sale can unlist it at any time. This means they can sabotage a parachain that intends to purchase that specific region just before it does so. Again, this could leave the parachain without any Coretime, thereby halting its operations.
Would we allow the trading of regions that are 'active' during the current bulk period (i.e., region.begin < last_committed_timeslice)? Since the RFC doesn’t mention this, I would assume it is inherently allowed. However, trading these regions on the marketplace described in this RFC would have some issues.

These regions are gradually losing value because their potential to be used is wasted by having them listed on the market instead of being assigned to a specific task. These regions shouldn’t have a fixed price; instead, they should have a dynamic price that decreases with each timeslice. This is what we are implementing in the RegionX Coretime marketplace: https://regionx.gitbook.io/wiki/advanced/dynamic-coretime-pricing
The rationale for implementing the described functionality on the Coretime chain is not really convincing to me. The primary argument is that this approach is simpler than implementing it on a separate parachain. However, given Polkadot’s multi-chain architecture, we should leverage its structure along with technologies like XCM to develop multi-chain protocols and applications. We should not hesitate to distribute functionality across multiple chains where it makes sense, which, in my honest opinion, is the case for Coretime marketplaces.

1. It is important to consider who actually needs Coretime in the first place. Currently, the consumers of Coretime are parachains. Many of these parachains share the goal of being decentralized, self-governing entities. To achieve this goal, a parachain cannot depend on a specific group of people for Coretime procurement. Adding functionality to the broker pallet that resembles a regular NFT marketplace is not the ideal solution.

The fact that agile coretime is tradable and accessible to those beyond simply builders is a necessary attribute to it being "agile." This is a benefit to the chain builder as much, if not more so, as it is to the non-builder. There will always be an inherent advantage to a builder who utilizes the coretime for securing and validating a chain over a trader who cannot do anything with it besides resell it. The fact that cores are NFTs make a secondary marketplace possible, and something that has been in the works for thinkers in blockspace since before agile coretime's introduction. (ctrl+f=secondary)
The ideal solution is to make trading as seamless as possible, and the building for competitive secondary coretime markets as simple as possible. This helps the builder who wants to trade their excess coretime just as much as the non-building trader.

One of the main problems is front-running.

Front-running is out of the scope of this RFC as this RFC does not enable, nor protect users from, front-running. Front-running protections can be established in other ways if desired, such as steeper lead-in periods. It could be argued that front-running could be beneficial to the market health of polkadot which does not have any value-extracting mechansims, dissuading a large part of the greater crypto market from participating in Polkadot. At the end of the day, front-running is a result of high-demand for high-value transactions, and would be a good problem to have in the future and "solve" or sort out in a future RFC.
If on-demand coretime is available, there is no halting of any parachain's operations.

A possible solution could be for the parachain to rely on a set group of people for Coretime procurement, but this would go against the goal of decentralization.

I would argue that crowdloans were precisely "parachains relying on a set group of people for coretime procurement," and this has nothing to do with decentralization.

2. The user who listed the region for sale can unlist it at any time. This means they can sabotage a parachain that intends to purchase that specific region just before it does so. Again, this could leave the parachain without any Coretime, thereby halting its operations.

Again, if on-demand coretime is available, there is no halting of any parachain's operations.

3. Would we allow the trading of regions that are 'active' during the current bulk period (i.e., `region.begin < last_committed_timeslice`)? Since the RFC doesn’t mention this, I would assume it is inherently allowed. However, trading these regions on the marketplace described in this RFC would have some issues.
   These regions are gradually losing value because their potential to be used is wasted by having them listed on the market instead of being assigned to a specific task. These regions shouldn’t have a fixed price; instead, they should have a dynamic price that decreases with each timeslice. This is what we are implementing in the RegionX Coretime marketplace: https://regionx.gitbook.io/wiki/advanced/dynamic-coretime-pricing

A simple descending cost model makes sense and is trivial to implement, aside from being obvious.

The rationale for implementing the described functionality on the Coretime chain is not really convincing to me. The primary argument is that this approach is simpler than implementing it on a separate parachain. However, given Polkadot’s multi-chain architecture, we should leverage its structure along with technologies like XCM to develop multi-chain protocols and applications. We should not hesitate to distribute functionality across multiple chains where it makes sense, which, in my honest opinion, is the case for Coretime marketplaces.

Since we are not talking about adding functionality to the relay chain, I fully agree that we should leverage the parachain structure, and in this case we are by adding functionality to the coretime PARACHAIN. System parachains are parachains, and it's up to the community what they should provide. It is in the community's wishes to stop further fragmentation and adding useful functionality to system parachains in an unbiased way makes sense.

One might argue that I might be biased because I am working on a project that, among other things, addresses the issues mentioned in this RFC.

Yes, one might argue this and I definitely believe that you are biased because this RFC would render much of your work outside of your sole control. We believe that Polkadot needs to be easier to develop on for its continued growth, and adding functionality to system chains is the easiest way to encourage growth and reduce the amount of technological gatekeeping that tends to occur with parachains feeling threatened by functionality that helps everyone.
We need to understand that Polkadot is changing with JAM on the distant horizon which threatens the entire parachain model, and continuing a conservative approach will cause a split between JAM and Polkadot that we cannot afford. We must continue to adapt in order to maintain relevance.
That being said, we look forward to feedback on improvements to this RFC from stakeholders without clear conflicts of interest.

To add onto what @phillux metioned, firstly I believe that emphasizing the efforts made towards other solutions (by both Lastic and RegionX) is unproductive if those solutions are less optimal than what this PR proposes.
Building a separate parachain to handle this functionality is inefficient and impractical. The only financial gains would be from secondary Coretime sales. However, to establish and sustain this parachain, significant costs are involved:

Core Purchase: You would need to buy a region on both Kusama and Polkadot, with only around 50 cores available in total.
Maintenance Costs: You need to renew the region monthly, which is financially burdensome.
Revenue Generation: To cover costs, you would need to resell approx. at least 50 regions each month, which is unlikely. (taking a 2% cut from each sale, would cover you only the costs of renewing a region)
Development and Operational Costs: There are additional costs that you wouldn't be able to cover which include development, maintenance, indexing, and other operational expenses.

Therefore, such a chain is financially unsustainable and would require Treasury funding, which is unfair to the community. Additionally, developing a new chain for this functionality would take several months, whereas adding three functions to the broker pallet can be done in a few days.
Moreover, creating a chain solely for this functionality would centralize the secondary marketplace, potentially excluding certain actors from participation. This contradicts the principles of decentralization. Building extended functionality on another system chain also lacks economic sense.
Addressing specific concerns:

Decentralization and Standardization: Integrating the marketplace directly into the broker pallet enhances decentralization for parachains. It provides a standardized and transparent mechanism for all parachains to engage in Coretime trading.

Trading of Active Regions: Allowing the trading of regions that are 'active' during the current bulk period is manageable. Users can adjust pricing at any time, and in my opinion linear pricing curve should not be imposed on them as proposed.

Separate Chain Option: This proposal does not preclude the option of creating a secondary chain that communicates with the Coretime chain via XCM. Users can still transfer regions over XCM and sell them on another chain if they choose.

In conclusion, integrating the secondary market functionality directly into the broker pallet is more efficient, cost-effective, and aligned with the principles of decentralization. This approach reduces overhead, speeds up implementation, and maintains flexibility for future enhancements.

@poppyseedDev Thanks for the writeup. However, I think most of this is off-topic for this RFC. We can discuss it elsewhere.
To answer your main concerns in short: No, the treasury won't have to pay for the Coretime procurement and other costs associated with running the parachain. Also, DOT token holders will vote on the parachain's code upgrades.
If you have further questions or concerns about the parachain, we can discuss them somewhere more appropriate.

My two cents: First of all I do think that having secondary markets live right on the Coretime chain would make perfect sense and this is also why I would love to see smart contracts enabled on Coretime. Until we have that, indeed the next best solution would be to include them in the runtime directly, but first of all I don't think that should go into the broker pallet, for at least a couple of reasons:

The broker pallet is already involved enough.
Secondary markets are certainly implementable in different ways, as evidenced by the discussion on this very ticket, making a biased default implementation right in the broker pallet quite questionable.
Maintainer of the broker pallet is currently Parity. The idea of secondary markets, was to be offered by the community, not by Parity. I don't see how maintenance will not end up being the responsibility of Parity, when integrated into broker directly.

What could work is that teams wanting to offer secondary markets provide additional audited and reviewed pallets that can be deployed on the Coretime chain. Those pallets should be named after the team maintaining them, e.g. region_x_coretime_market/lastic_coretime_market, ....These pallets could then also introduce their own token or fee system, so that the teams maintaining the market get the necessary funding.
There are benefits and downsides to this approach. On the upside, you don't need to run your own parachain, which means less cost, less complexity and better efficiency. On the downside: Less flexibility, slower iteration: The runtime needs to be trusted, hence any changes you make will need to be approved by the fellowship. So I would say this is only viable if those pallets stay small and will not evolve much. And obviously as this is a significant maintenance burden on the fellowship, it is also up to the fellowship to decide whether this is an option at all. In any case this does not scale too well, so mid term we should have smart contracts. Also as there would be maintenance burden on the fellowship it is not clear how this would go together with a for-profit system.
TL;DR, my opinion: Secondary markets on the coretime chain: Yes. In the broker pallet: No. Directly in the runtime: Maybe a reasonable intermediate solution until we have contracts.

What could work is that teams wanting to offer secondary markets provide additional audited and reviewed pallets that can be deployed on the Coretime chain.

Another benefit is simply the precedent of parity using this model somewhere.  It's a great model for many things in the ecosystem outside of the core functionality of polkadot.

instead propose adding smart contract pallets to the Coretime chain?

"Audited" often precludes smart contracts, maybe folks want that eventually, but afaik they're all in flux now anyways.  I'd focus upon (a) messaging endpoints that addressed the initial replies concerns, albeit with some latency, and (b) some really basic secondary market functionality.
Afaik, we do not need anything complex like auctions or real matching here, maybe sell above some price, and buy below some price, with the buy choosing the oldest matching sell, or even the bbuy containg a list of acceptable ones, but buys can fail if all below that price or on the list disappear first.  If you need the list, then the list could be encoded as a merkle tree, so then the collator can shrink the tx to just the sell it picks.  @jonasW3F might've optinions.

I think an RFC (or a wish for change) proposing to add smart contracts to the coretime chain and let the fellowship/token holders decide, certainly makes sense. You should also be aware of this one, currently having huge support. It would make perfect sense to have a wish for change to also add pallet-contracts to the coretime chain, while we are at it. This will not happen until end of year though, if we want something faster, we would need to do Frontier, with the caveats in referendum 885.
For adding a pallet as an intermediate solution: I think this can be proposed to the fellowship. For pursuing this one: I am skeptical it will find support. For the additional pallet solution: I don't know, could go both ways. Contracts, given how 885 is going so far, might be the safest bet, but probably also the one with the longest timeline.

Afaik AssetHub lacks our locks, staking, slashing, and governance, which makes 885 make more sense.  Afaik we've never interfaced smart contracts directly to those pallets before, so maybe 885 should look somewhat like messages anyways.

After extensive deliberation and discussion at Lastic, we have concluded that integrating a secondary marketplace feature directly into the broker pallet is the most efficient approach.

Why not some message interface for the broker pallet?   It already has some transfer function, right?

Why not some message interface for the broker pallet? It already has some transfer function, right?

@burdges would you mind expanding on this?
I have expanded on the proposal to include the possiblity of having this be an extension pallet that would live on the Coretime chain.

We'll anyways have the broker pallent recieve some messages, so then a market functionality could live on multiple other paracahins, right?  Assuming this, what advantages does having a market on the same chain bring?


Unable to commission matter over thread light example. (CON-1277)

Describe the bug
I have not been able to commission the light example using matter over thread. I've tried multiple pathways, however I'm primarily using the Home Assistant OTBR and their Android commissioning app. I've also tried using the Android Home app directly.
The Android device does appear to make a successful bluetooth connection to the ESP32C6 device, however
The error I get in the commissioner app is Can't connect to thread network xyz. Check that your device can work with this network type and try again.
Firmware is built in vscode with the current esp-idf extension. ESP-IDF versions 5.2 and 5.3 were both tried. ESP-Matter was installed in vscode with the Install ESP-MATTER option in the ESP-IDF extension.
Environment

ESP-Matter Commit Id:
ESP-IDF Commit Id:
SoC (eg: ESP32 or ESP32-C3): ESP32-C6
Device Logs (Please attach the log file):

Device Log: (Complete log from boot to commission failure) - esp32c6_matter_thread_light.txt

Host Machine OS: Ubuntu 22.04

Host Machine Python version: 3.10.12

Commissioner app and versions if present: Home Assistant Android App, Android Home App

Commissioner's logs if present:

Some of the OTBR logs:
otbr_commission_log.txt
Any additional details
...

Looks like the esp32c6 was not attached to the thread network of the OTBR you were using. It became a leader at last. Could you enable the CONFIG_OPENTHREAD_CLI on esp32c6 and input this command in the esp32c6's console after the thread credential is set during commissioning to verify that the esp32c6 receives the same thread dataset as the OTBR was set?
matter esp ot_cli dataset active -x

@baylf2000 Any update you can share? Please close the issue if resolved

Closing this now


Support matching multiline lines

I'll try this more and monitor it even more closely before merging.


yield pass: Top level function application for non-generator functions get turned into run calls

This happens when the function being called is not declared in the file. Consider the program:
let assert = require('assert');
assert(true)

which gets turned into:
let assert = require('assert');
let gen  = assert(true)
run(gen)

which is incorrect.
Need to do something about it.

For this and other cases (thinking about adding continuation args to function calls), we may want to do a pass and tag applications of free identifiers in function position as ignore for future transformations. This would handle things like console.log, etc.

As a first pass, yes. We do want to think about FFIs at some point (I.e. Code that hasn't been transformed).


Text incorrectly printed

When the pattern is wider than the success/failure text, the final text is incorrect.
.   My text
..  My text
... My text
✔ My textxt

Using version: 0.3.6
Terminal: iTerm2 3.2.0
Shell: zsh 5.5.1 (x86_64-apple-darwin17.5.0)

Ouch, that shouldn't be happening 🙈

I'm having the same issue as well. Any fix for this?


HTTP.import cache cleanup

It should be possible to automatically cleanup cached page content when it is no longer necessary. For example, once a template is loaded, repeat calls for the same template are typically made within a few moments of each other. After that, the templates aren't used anymore (i.e. one use templates).
It would be nice to automatically cache remote content, then remove it from memory by default. An override should be available for those who need the content to persist for longer periods of time.

Added in 301d7ffa97a5015d844a8f1b461988edbd52fd7b. Defaults to 10 seconds, which is overridable on a global level and an import-by-import basis.


can't install

ℹ Computer information

Spotify version: <IP_ADDRESS>7 (or rather : none since it can't download it)
Plan Spotify: free
Windows version: 7 SP1
PowerShell version: 5.1

📝 Description of the problem
running the install always returns the same error when trying to download spotify :  "could not resolve host : upgrade.scdn.co"
it just stops there

I'm on vacation, I'll come back in a month and fix it

Is this error still happening to you?

for the record it's stll happening, those upgrade.scn.co just won't resolve, it's not behind any firewall/enterprise stuff, pretty much standard home fiber... "workaround" was to wait for spotify installer to catch up then, so the script didn't have to dld...

I did a test to disable downloading via curl, can you try to run the following line directly through powershell and report if there is a similar error?
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; iex "& { $((iwr -useb 'https://raw.githubusercontent.com/amd64fox/Test/main/test.ps1').Content) } -curl_off"

It seems to be related to the file host, check it

Win + R
%WinDir%\System32\Drivers\Etc
Run the host file as administrator and remove all URLs from it

haha, spot on, totally forgot about those old days of hosts editing, must have put the upgrade adresses there around 2014 ^^


move license to apache2.0

All the IP in this repo is owned by CoinCulture (my company :) ). For historical reasons, it was licensed as GPL. But to support our good friends at https://github.com/FuelLabs/fuel-bft and anyone else who might find this code useful, CoinCulture is hereby relicensing the software in this repository as Apache2.0.

Woot.


Run all linters on all files each PR

Otherwise, changes in linting config aren't tested, and quickly you end up with files that don't pass linting, but this is only
picked up the next time someone tries to edit the file.
Same as https://github.com/datapane/datapane-hosted/commit/b7248bd9ab91524fcc9755f8f972fb6e582fa07c for datapane-hosted

@Buroni This fix has exposed a few eslint errors (and lots of warnings, which we can ignore) - see https://github.com/datapane/datapane/runs/7808597548?check_suite_focus=true
I'm not sure how to best address these.
The flake8 errors I'm fixing in another branch.

LGTM - happy to merge & run this in CI going forwards.
The linked GH action above seems to generate a lot of errors from the test modules - shall we disable type-checking for tests (I think it used to be at somepoint).
Whilst we're taking a quick look at this, is it possible to update the autoflake pre-commit step to be more verbose? I'm finding that it's changing my code but not giving enough insight into what it has changed (and maybe why?). This makes things quite tricky as you're never sure if it's changes have broken the code (by removing an import for instance that wasn't added to __all__ during refactoring)

@mands The flake8 errors are fixed now, partly by silencing them for test files as you suggested, done in another branch. (There was some config intended to do that but it wasn't working). I'm completely in favour of silencing any errors/warnings that we aren't intending to do anything about - it's just noise that you have to wade through, and hides real issues.
The remaining 2 eslint errors in this branch need to be fixed before merging, to keep the test suite green. The warnings don't need to be addressed AFAICS.

The remaining 2 eslint errors in this branch need to be fixed before merging, to keep the test suite green. The warnings don't need to be addressed AFAICS.

@Buroni - would you be able to look at this? thanks

I've made the following changes

Fixed existing eslint errors
Replaced deprecated babel-eslint with @babel/eslint-parser and update our other pre-commit dependencies, as we were hitting this bug which exists on older eslint dependencies.
Removed duplicate dp-notebook/ dir which I must have missed when moving things over in the refactor


Add optimization: foo["bar"] ==> foo.bar

The feature was implemented in the following commits:
https://github.com/rspivak/slimit/commit/d76d004b6c44a1a7d28719a6bf4db221b3dfc089
https://github.com/rspivak/slimit/commit/8d4f1a6cd8b263ffbdb4681fd50c2e4f59228752


on focussing text inputs in webview no keyboard pops up

Should we release a hotfix release for this?

Only the design-support branch was affected, therefore the bug wasn't released yet.


BERT preprocess layer runs on CPU

Hi,
When running a BERT model as part of a larger model the preprocess layer seems to run on CPU and then the main BERT component on GPU - this involves lots of ops moving data back and forth and is prohibitively slow.
Is there a way to force all the ops to run on GPU?
Thanks!

While I can't comment on the details of performance in your case, here are some general observations:

Preprocessing deals a lot in string processing and hash table lookups, for which CPUs are much better suited than GPUs. (In fact, most of the respective ops have not even been implemented for GPUs.) For the fast linear algebra inside the actual BERT encoder, it's the opposite. Therefore, it makes sense for TensorFlow to split the work between the two.
It's natural for training data to flow from the CPU to the GPU, because disk or network I/O goes through the CPU. The typical concern is: how much slower does each training step get due to reading training data on top of the unavoidable work for gradient-based training?
If preprocessing adds a significant overhead there (in relation to the model size at hand), the trick is to take preprocessing out of the loop, quite literally. In TensorFlow, you can do this by executing the preprocessor step asynchronously (and hence on separate CPU cores) in a tf.data.Dataset.map() call before feeding the dataset into the training loop. Or you can simply have two programs: one that does preprocessing and writes the results back to disk, and a second that does the training from already-preprocessed data.

For a complete example of the Dataset.map() approach, see https://www.tensorflow.org/tutorials/text/solve_glue_tasks_using_bert_on_tpu and ignore the TPU specifics if you are targeting GPUs.
All that said, is there a concrete, actionable defect with the TensorFlow Hub models, library or documentation that needs tracking here? If yes, please provide a compete reproduction and an explanation of what goes wrong. If not, let's close this issue. We recommend StackOverflow (specifically, tag tensorflow-hub) for general how-to and support questions.

While I can't comment on the details of performance in your case, here are some general observations:

Preprocessing deals a lot in string processing and hash table lookups, for which CPUs are much better suited than GPUs. (In fact, most of the respective ops have not even been implemented for GPUs.) For the fast linear algebra inside the actual BERT encoder, it's the opposite. Therefore, it makes sense for TensorFlow to split the work between the two.
It's natural for training data to flow from the CPU to the GPU, because disk or network I/O goes through the CPU. The typical concern is: how much slower does each training step get due to reading training data on top of the unavoidable work for gradient-based training?
If preprocessing adds a significant overhead there (in relation to the model size at hand), the trick is to take preprocessing out of the loop, quite literally. In TensorFlow, you can do this by executing the preprocessor step asynchronously (and hence on separate CPU cores) in a tf.data.Dataset.map() call before feeding the dataset into the training loop. Or you can simply have two programs: one that does preprocessing and writes the results back to disk, and a second that does the training from already-preprocessed data.

For a complete example of the Dataset.map() approach, see https://www.tensorflow.org/tutorials/text/solve_glue_tasks_using_bert_on_tpu and ignore the TPU specifics if you are targeting GPUs.
All that said, is there a concrete, actionable defect with the TensorFlow Hub models, library or documentation that needs tracking here? If yes, please provide a compete reproduction and an explanation of what goes wrong. If not, let's close this issue. We recommend StackOverflow (specifically, tag tensorflow-hub) for general how-to and support questions.

@arnoegw thanks for that - makes perfect sense.
I will close!

@arnoegw thanks for that - makes perfect sense.
I will close!


[Snyk] Security upgrade sharp-cli from 4.1.1 to 4.2.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json

⚠ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

909/1000  Why? Mature exploit, Has a fix available, CVSS 9.6
Heap-based Buffer Overflow SNYK-JS-SHARP-5922108
No
Mature

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: sharp-cli
    The new version differs by 9 commits.

a02338f 4.2.0
54bc389 Update changelog.
77406b9 Update readme.
ccaa604 Update dependencies to latest.
d41798b Bump sharp to 0.32.3.
47a0eb5 Add unflatten command.
ae9bdbf Update to sharp 0.32.0.
34e1e8c Add interFrameMaxError and interPaletteMaxError.
e567896 Exit process when there are no input files - fixes #83.

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

/lock


Insight 570

Add post for insight 5.7.0
cc @pwalczysko

This is now 2 days old. Should the post date be adjusted or do you want to wait on @pwalczysko's return?

LGTM 👍


Bump urllib3 from 1.22 to 1.26.5 in /Mycroft/skill-echo-utterance

Bumps urllib3 from 1.22 to 1.26.5.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: urllib3
dependency-type: direct:production
...

Signed-off-by: dependabot[bot]<EMAIL_ADDRESS>

1


Tabbing the group expander icon doesn't keep focus in Activities Panel when renaming a folder which contains multiple blobs

Storage Explorer Version: 1.1.0 RC
Platform: Windows/Mac
Architecture: x64
Build Number: 20180502.5
Commit: 48f8a5a0
Regression From: Not a regression
Steps to Reproduce:

Launch Storage Explorer and expand storage accounts.

Open one blob container and rename a folder which contains multiple blobs.

Focus on the group expander icon in Activities Panel using Tab.

Expected Experience:

The group expander icon keeps focus.
Actual Experience:

The group expander icon doesn't keep focus.
More info:
This issue also reproduces when uploading/downloading a directory which contains multiple files.

Verified this issue on the latest build 20190614.7. It doesn't reproduce. So we close it.


the real size of raw/train/database

Thanks for collecting this amazing dataset!
When I try to use the 'rsync -rhz --info=progress2 --ignore-existing rsync://vandaldata.polito.it/sf_xl/raw/train/database' command to download the raw/train/database, it takes about 1.7T of space in my disk before finishing the downloading. I want to know that whether it's because of the precise size of this part of dataset(1TB mentioned in readme.md) or it's because some downloading mechanisim inside the rsync command that makes this happen, for examples some cache operation?
Looking forward to your reply!

I found it's because the file system of my disk is exFAT, which is not suitable for storing many files.
I change it into the ext4 and the problem is solved!