noob error: EPEERINVALID

Hi!, I'm using a react boilerplate and works nicely, unfortunately when I try install baobab I get his
npm ERR! Linux 3.2.0-86-generic
npm ERR! argv "node" "/home/yo/.linuxbrew/bin/npm" "install" "baobab"
npm ERR! node v0.12.2
npm ERR! npm  v2.13.1
npm ERR! code EPEERINVALID

npm ERR! peerinvalid The package<EMAIL_ADDRESS>does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants webpack@*
npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>npm ERR! peerinvalid Peer<EMAIL_ADDRESS>wants<EMAIL_ADDRESS>
npm ERR! Please include the following file with any support request:
npm ERR!     /home/yo/Downloads/proj/jsprojects/rboiler/react-hot-boilerplate/npm-debug.log

my package file is
{
  "name": "react-hot-boilerplate",
  "version": "1.0.0",
  "description": "Boilerplate for ReactJS project with hot code reloading",
  "scripts": {
    "start": "node server.js"
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/gaearon/react-hot-boilerplate.git"
  },
  "keywords": [
    "react",
    "reactjs",
    "boilerplate",
    "hot",
    "hot",
    "reload",
    "hmr",
    "live",
    "edit",
    "webpack"
  ],
  "author": "Dan Abramov<EMAIL_ADDRESS>(http://github.com/gaearon)",
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/gaearon/react-hot-boilerplate/issues"
  },
  "homepage": "https://github.com/gaearon/react-hot-boilerplate",
  "devDependencies": {
    "babel-core": "^5.1.11",
    "babel-loader": "^5.0.0",
    "css-loader": "^0.15.5",
    "file-loader": "^0.8.4",
    "react-hot-loader": "^1.2.2",
    "react-sortable-mixin": "0.0.1",
    "style-loader": "^0.12.3",
    "url-loader": "^0.5.6",
    "webpack": "^1.7.2",
    "webpack-dev-server": "^1.7.0"
  },
  "dependencies": {
    "react": "^0.13.0"
  }
}

what is the correct way for solve this problem?..thanks!!......

Try running npm install webpack -D. While ^1.7.2 should cover ^1.9.11, it doesn't seem to have installed correctly

thanks it works


Forever list does not show the running processes

Using :
<EMAIL_ADDRESS>nodejs v0.6.7
Constantly reproducible with the following commands:
jdreux@frontend:/opt/test/public-ws$ sudo forever start public-ws.js
info:   Forever processing file: public-ws.js
jdreux@frontend:/opt/test/public-ws$ sudo forever list
info:   No forever processes running
But the process is running!
jdreux@frontend:/opt/test/public-ws$ ps ax | grep node
32431 ?        Ss     0:00 node /usr/local/bin/forever start public-ws.js
32432 ?        Sl     0:00 node /opt/test/public-ws/public-ws.js
32445 pts/0    S+     0:00 grep node

Potentially a duplicate of #223, but cannot test if forever lists processes when not running as root because of my environment setup.

Operating system?

I cannot reproduce this on Ubuntu 11.04 or CentOS 6.x

Or MacOS:
$ sudo forever start examples/server.js -p 8080
info:   Forever processing file: examples/server.js
[forever]$ sudo forever list
info:   Forever processes running
data:       uid  command script                     forever pid  logfile                          uptime
data:   [0] 39T8 node    examples/server.js -p 8080 1001    1002 /Users/Charlie/.forever/39T8.log 0:0:0:3.744
[forever]$ sudo forever stopall
info:   Forever stopped processes:
data:       uid  command script                     forever pid  logfile                          uptime
data:   [0] 39T8 node    examples/server.js -p 8080 1001    1002 /Users/Charlie/.forever/39T8.log 0:0:0:8.469

Happens on Ubuntu 11.04. If you send the examples/server.js file I can try reproducing with that.

Could not reproduce on Max OS with Node 0.6.6

No. It doesn't, lol. How did you install node? I am sitting on a vanilla Rackspace Cloud Ubuntu 11.04 image where this works just fine. Here is how I bootstrapped the image (I am logged in as root):
#
# Update the system
#
apt-get -y update
apt-get -y install git-core build-essential libssl-dev pkg-config

#
# Install node, npm and forever
#
git clone git://github.com/joyent/node.git
cd node
./configure
make && make install
cd ../
npm install forever -g

#
# Clone the forever repository which has examples/server.js
#
git clone git://github.com/nodejitsu/forever.git
cd forever
sudo forever start examples/server.js -p 8080
sudo forever list
sudo forever stopall

This instance had node upgraded from 0.4.10 to 0.6.7 using the make uninstall method. Forever used to work fine before the nodejs upgrade. Could the upgrade process have something to do with it ?

Yes. You need to reinstall forever on the upgrade from 0.4.x to 0.6.x
  npm uninstall forever -g
  npm install forever -g

Uninstalled, reinstalled. Problem still occurs. Is there a more log or verbose traces I could send you to help you with this ?
Thanks again for the support.

Try rm -rf ~/.forever. Other than that. I'm stumped. Sorry.

Still no luck. As a last hope, maybe this trace can help you ?
jdreux@frontend:/opt/test/public-ws$ sudo forever start public-ws.js
info:   Forever processing file: public-ws.js
jdreux@frontend:/opt/test/public-ws$ sudo forever list
info:   No forever processes running
jdreux@frontend:/opt/test/public-ws$ ps ax | grep node
572 ?        Ss     2:46 /usr/sbin/munin-node
620 ?        Ss     0:00 node /usr/local/bin/forever start public-ws.js
621 ?        Sl     0:00 node /opt/test/public-ws/public-ws.js
628 pts/0    S+     0:00 grep node
jdreux@frontend:/opt/test/public-ws$ sudo forever stopall
{
"process": {
"pid": 630,
"uid": 0,
"gid": 0,
"cwd": "/opt/test/public-ws",
"execPath": "/usr/local/bin/node",
"version": "v0.6.7",
"argv": [
"node",
"/usr/local/bin/forever",
"stopall"
],
"memoryUsage": {
"rss": 14745600,
"heapTotal": 8901984,
"heapUsed": 5482184
}
},
"os": {
"loadavg": [
0.60400390625,
0.240234375,
0.13916015625
],
"uptime": 2519703.22595143
},
"trace": [
{
"column": 31,
"file": "/usr/local/lib/node_modules/forever/lib/forever.js",
"function": "Array.0",
"line": 194,
"method": "0",
"native": false
},
{
"column": 40,
"file": "node.js",
"function": "EventEmitter._tickCallback",
"line": 192,
"method": "_tickCallback",
"native": false
}
],
"stack": [
"Error: Cannot find forever process: undefined",
"    at Array.0 (/usr/local/lib/node_modules/forever/lib/forever.js:194:31)",
"    at EventEmitter._tickCallback (node.js:192:40)"
],
"level": "error",
"message": "uncaughtException"
}

@jdreux Nope. I can't reproduce it on a fresh Ubuntu 11.04 machine. Can you try provisioning a fresh Ubuntu 11.04 VM and attempting to reproduce it as well? I'm going to blame this on a bad upgrade from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

I got this problem with a fresh install of<EMAIL_ADDRESS>on a Ubuntu 10.10 machine.
On Mac and on other setups it worked just fine :/.
I compiled node from the tarball.

@mcollina Did you follow the exact ubuntu instructions in the Detailed Forever Installation Instructions? https://github.com/nodejitsu/forever/wiki/Detailed-installation

@mcollina Following those instructions we have forever running just fine on<EMAIL_ADDRESS>(without this problem) on 1,000s of servers running in production at Nodejitsu.

I know that, and it's a really strange issue. Your service is great, but I
need to listen to other ports.
My vps it's on openvz, and it may be an issue with that.
Moreover it's a fairly old machine.
As I see other people have this problem on cheap vps, so it might be some
strange thing involving unix sockets?

@mcollina Not sure I understand what you mean by "listen to other ports", can you elaborate? Overall it seems to be a permission issue with the directory in which forever stores unix sockets for IPC

Sorry,  I mean I have to support other protocols than http.
I've looked at your faq, and you don't support that.
Thanks, I'll take at look at it.

@mcollina I don't think you understood what forever does. It is just a process monitor. You can run any process with it that uses any protocol. Also, forever doesn't use HTTP at all, it uses TCP.

I was referring to nodejitsu! ;)
Il giorno 14/gen/2012 16:47, "Charlie Robbins" <
<EMAIL_ADDRESS>ha scritto:

@mcollina I don't think you understood what forever does. It is just a
process monitor. You can run any process with it that uses any
protocol. Also, forever doesn't use HTTP at all, it uses TCP.

Reply to this email directly or view it on GitHub:
https://github.com/nodejitsu/forever/issues/224#issuecomment-3492953

@mcollina Haha. Thanks. We plan to support that sometime this year.

Fixed in<EMAIL_ADDRESS>Thanks to everyone who provided bug reports :)


My cool stuff

删除了 『mod』 API, 在『tensor属性相关』栏中新增了『paddle.broadcast_shape』 API

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

修改了paddle模块、io模块、jit模块、nn模块、static模块、utils模块、vision模块等7个模块的Overview_cn.rst文件
http://<IP_ADDRESS>:8090/documentation/docs/zh/api/paddle/Overview_cn.html


Added BareMetal platform support for LTP/Kselftest

Added BareMetal platform support for LTP/Kselftest

Please resolve conflicts, so the checks can run.

@LiliDeng LGTM

@paulli2017 I saw error with this test matrix.
canonical 0001-com-ubuntu-server-jammy 22_04-lts-gen2 22.04.202302140 KselftestTestsuite.verify_kselftest: FAILED   failed. SSHException: SSH session not active
Test runs well with main branch.


3 - Allow a  to be passed in to the API for upload

This would essentially add an addCanvases API method.  This would essentially turn the <canvas> into a Blob using the code in Scaling module.   Since we already have an addBlobs and an addFiles, maybe we should just repurpose addFiles to access Blob or <canvas> or File, or <input type="file"> and deprecate addBlobs.
Inspired by my FedEx Day Project (code/docs still need polish), and this Stack Overflow question.

Is there any documentation on how to implement this anywhere? (thanks)

Yes, we've updated the addFiles API method documentation.  http://docs.fineuploader.com/branch/master/api/methods.html#addFiles


distro.version() returns 'n/a' in Debian13

distro.version() is supposed to eliminate n/a and empty values when other sources contain valid values.
>>> import distro
>>> distro.version()
'n/a'

It returns n/a because lsb_release -a has that value, even though /etc/debian_version contains a valid value
$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux trixie/sid
Release:	n/a
Codename:	trixie

$ cat /etc/debian_version
trixie/sid

Thanks for your report @nagworld9 ! Please see #374.
Bye :wave:


There is an extra scrollbar in the 'Shared Access Signature' dialog for one storage account if click the link 'Learn more about shared access signatures'

Storage Explorer Version: 1.33.0-dev (96)
Build Number: 20240106.11
Branch: main
Platform/OS: Windows 10
Architecture: x64
How Found: From running test cases
Regression From: Not a regression
Steps to Reproduce

Select and right click one storage account.
Click 'Get Shared Access Signature...'.
Click the link 'Learn more about shared access signatures'.
Check there is no extra scrollbar.

Expected Experience
There is no extra scrollbar.
Actual Experience
There is an extra scrollbar.
Here is the record:

Additional Context
This issue doesn't reproduce for blob containers/file shares/queues/tables.

The scroll bar is inserted because the content size increases from the focus border. This is easily fixed by changing the border to an outline, which does not take up any space.

Verified this issue on the build 20240109.2. Fixed.


can you please support an appointment for teudat zehut change?

I need to update my family name and status( I got married) is it possible to order such an appointment?

Hi @naomitayeb, we are not supporting appointments for Teudat zehut change. when we will support it I wlil update.
Thanks!


Remove deprecated ListenerLowCardinalityTags.DELIVERY_TAG

Closes gh-2921

Thank you for the contribution !
But we look into this only next year when we switch to a new version based on the upcoming Spring Framework 7.0.


symbolwinbar.lua:42: attempt to index field 'range' (a nil value)

Description

For some filetypes, the winbar does not work and throws error:
Error detected while processing CursorMoved Autocommands for "<buffer=1>":
Error executing lua callback: ...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:42: attempt to index field 'range' (a nil value)
stack traceback:
        ...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:42: in function 'binary_search'
        ...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:70: in function 'find_in_node'
        ...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:115: in function 'render_symbol_winbar'
        ...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:212: in function <...k/packer/start/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua:208>

This issue seems to happen for code languages that do not have a hierarchy.
Expected Behavior

To either show winbar symbols or silently exit winbar.
Actual Behavior

Shows error and I have to keep pressing <CR> to hide error. But when I press any movement key, error appears again
Neovim Built in Behavior

Not sure what this means?
Details

Reproduce

Open a shell a .sh or .blade.php file (I have only had issues with these)
Do anything

Environment

nvim --version output:

VIM v0.8.0-dev+1963-gee6b21e84
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-ee6b21e/share/nvim"

Run :checkhealth for more info

Operating system: macOS 12.4
lspsaga commit: 08c087adbd5820122a7cd78a3949cdd55bade638

Hmm
Can you edit .local/share/nvim/site/pack/packer/opt/lspsaga.nvim/lua/lspsaga/symbolwinbar.lua and add `vim.pretty_print(node) on line 42?

Hmm I don't have this bug
I opened oh-my-zsh.sh with lsp server bashls

Hi @nullchilly,
I opened symbolwinbar.lua and added vim.pretty_print(tbl) but I cannot get the output of :message due to it being too long and the lspsaga error is making it difficult.
Is there a way to log output to file, perhaps?

Yes, you can use lua standard file open

https://www.tutorialspoint.com/lua/lua_file_io.htm

@codepuncher For the time being you can add to line 39
if tbl[mid].range == nil then
  return nil
end

Still, I don't understand which server is causing it, please post a screenshot of :Lspinfo so I can test

I installed all the language server in your configuration and all of it says All servers of this buffer does not support textDocument/documentSymbol so I guess we need to remove autocmd when it happens?

Anyway, I am going to sleep, good luck with your pr

Thanks @glepnir !


[RelatedArtists] Added a RelatedArtists component

[x] RelatedArtist component
[x] Temporary horizontal RelatedArtists view (until a collection view can be used instead)
[x] Relay for all necessary information

I'm happy with this; could use some feedback on syntax but otherwise it's everything we need for related artists besides the grid view.

You’re on :fire:

Might want to check if those same artist work counts labels are needed on other clients, if so it might be worth it to move to metaphysics.

@sarahscott See how far you can get with just flexbox: https://github.com/artsy/eigen/issues/1136#issuecomment-216986249

I'll give it a shot!

🍏

Awesome 🎉

That Rob Pruitt looks like Artsy Test data

@sarahscott Can you check if what @orta said is true?

It is indeed a Rob Pruitt work!
Puppies everywhere. Puppies on everything.
"Feels Like Love/Safe Place" by Rob Pruitt on Artsy
https://www.artsy.net/artwork/rob-pruitt-feels-like-love-slash-safe-place-1

The puppy won't be so distorted after my image cropping PR.

Thanks for checking 👍


Add mei-friend to the Tools page

This PR contains a description of the mei-friend editor as a proposed addition to the Tools page at https://music-encoding.org/resources/tools.html
Please kindly consider merging, or otherwise please let me know any concerns or suggestions for modification. Thanks!

Thanks for adding this.


Tests useDrag/useDrag

Hi,
I have encountered a problem for testing drag and drop with jest / enzyme.
I use useDrag and useDrop and documentation indicates how to get source and destination ids from getHandlerId() but its for a dragSource uses.
Unable to get source and destination ids. I get my backend and manager from reference.
Can I have some help ?
Thanks

I also cannot test useDrag. The same problem with access to the handlerId.
https://github.com/Zerstoren/battleship/tree/master/src/components/SetShips
Component and testing are described here as an example. Right now I am accessing id manually, but it is not correct. It would not be bad if this handlerId was available during rendering so that it can be passed through props

Okey, one more day research and i found how to set handlerId as prop.
Need use set
    collect: (monitor: DropTargetMonitor): Record<string, string> => ({
      monitorId: monitor.getHandlerId() as string,
    }),

useDrop return two record. One is collectedProps and second is ref. and now we can set props to element
  return (<td ref={drop} data-monitorid={collectedProps.monitorId} className={classNames} onClick={handleClick} />);

In Enzyme found needed tree leaf and read data-monitor. Now it work fine.

Thanks, @Zerstoren! I ended up using this trick to work around #2947. Linking them here so they are related.

Thanks, @Zerstoren! I ended up using this trick to work around #2947. Linking them here so they are related.


Chromatic stories for the rest

🙋 Feature Request

Alert
Breadcrumbs
Calendar?
Datepicker?
Form
Icon
Image
Label
Link
Meter
Progress
Table
Text
View
Well

🤔 Expected Behavior

😯 Current Behavior

💁 Possible Solution

Tabs/Breadcrumbs both rely on measurements that involve font, make sure that the font is already loaded
Tabs might need a delay until screenshot even with the font already loaded
🔦 Context

💻 Examples

🧢 Your Company/Team

🎁 Tracking Ticket (optional)

covered by https://github.com/adobe/react-spectrum/issues/1957


Mounted Routes with JS Classes

The goal is to use the JS Class version of code, which is more efficient long term. When using the CLASS based JS, in the app.js file sample below, an error is received.
// USERROUTER.JS FILE, MODULE.EXPORTS EXAMPLE
const router = express.Router();

router.post('/register', authController.signup);
router.post('/login', authController.login);
router.get('/logout', authController.logout);

module.exports = router;

// USERROUTER.JS FILE, CLASS EXAMPLE
export class UserRouter {
    constructor() {}
    // Open to all users
    register() {
        router.post('/account-register', AuthController.prototype.register);
    }
    login() {
        router.post('/account-login', AuthController.prototype.login);
    }
    logout() {
        router.get('/account-logout', AuthController.prototype.logout);
    }
}

// APP.JS FILE
// Mounted API Routes
const apiVersion = '1.0';
const apiRoutes = `/api/v${apiVersion}`;
app.use(`${apiRoutes}/users`, UserRouter);

NOTE
This project is using Typescript.
Class Example Error: TypeError: Class constructor UserRouter cannot be invoked without 'new'
When using "new" keyword, a different error is received.
// APP.JS FILE, Using the "new" keyword
app.use(`${apiRoutes}/users`, new UserRouter() );

Error W/ New Keyword: TypeError: Router.use() requires a middleware function but got a Object

[...] which is more efficient long term

I'd be careful with this idea; while I'm of belief efficiency comes down to the team and what's therefore best for the team, the community is much more strongly opinionated (the Node.js community that is).
Now regarding your issue, that TypeError actually comes from the router package, located:

https://github.com/pillarjs/router/blob/master/lib/route.js#L215

A few approaches are available; I elected to use reflection (see below).
As a disclaimer, and after giving this method a shot myself, I strongly advise against using classes.
const express = require("express");

const app = express();

class UserRouter {
    constructor() {
        this.router = express.Router();

        this.routes = [
            this.base
        ];
    }

    static methods = (instance) => {
        const state = {
            instance, properties: new Set()
        };

        do {
            Object.getOwnPropertyNames(state.instance).map(item => state.properties.add(item))
        } while ((state.instance = Object.getPrototypeOf(state.instance)));

        return [...state.properties.keys()].filter(item => typeof instance[item] === 'function')
    }

    static initialize = () => {
        const instance = new UserRouter();

        instance.routes.forEach(($) => {
            Reflect.set($, "router", true);
        });

        const methods = UserRouter.methods(instance);

        methods.forEach(($) => {
            const callable = instance[$];
            if (callable["router"] === true) {
                callable(instance.router);
            }
        });

        return instance.router;
    }

    base (router = this?.router) {
        router.get("/", (req, res) => {
            res.send({
                message: "Hello world"
            })
        });
    }
}

app.use("/", UserRouter.initialize());
app.listen(3000, "localhost", () => {
    console.log("Listening on http://localhost:3000");
});

Lastly, as I recommended against using classes, this is because there needs to be a running list, per instance, of applicable functions to call. This is due to the router itself not updating until a method ("get", "put", etc. etc) is explicitly called.
I tried my best to ease those efforts, but reflection was the only means I thought of (which requires that list in the first place).

I'd be careful with this idea...

Thanks for the reply. The idea was to use classes for OOP. With the solution example provided, this seems quite extensive for a "seemingly simple" solution. Starting to sound like Express, Typescript and classes are not the way to go.

I'd be careful with this idea...
Lastly, as I recommended against using classes...

With this in mind, I just might have to abandon classes. Which may also take me down a path to abandon Typescript too. I'm not clear on where the "running list" of functions is at.

Why not return a router and 'attach' the class instance to your app?
For example, you could do something like this:
// USERROUTER.JS FILE, CLASS EXAMPLE
export class UserRouter {
    constructor() {
        this.authController = new AuthController() // this should probably also go inside attach() to access app context
    }

    attach(app) {
        // app is your global app, useful as a context to retrieve settings with app.get()
        return express.Router()
            .post('/register', this.register.bind(this))
            .post('/login', this.login.bind(this))
            .get('/logout', this.logout.bind(this))
    }

    register(req, res, next) {
        return this.authController.register(req, res, next)
    }

    login(req, res, next) {
        return this.authController.login(req, res, next)
    }

    logout(req, res, next) {
        return this.authController.logout(req, res, next)
    }

}

Then, attach the router class:
// APP.JS FILE
// Mounted API Routes
const apiVersion = '1.0';
const apiRoutes = `/api/v${apiVersion}`;
app.use(`${apiRoutes}/users`, new UserRouter.attach(app));

Why not return a router and 'attach' the class instance to your app?

@silentjohnny interesting concept. Not exactly what I'm looking for, but it might work. Will give this a try and see how it goes.

this is my blog routes
export default class BlogRoutes {
  constructor() {
    this.blogController = new BlogController();
    this.authenticationMiddleware = new AuthenticationMiddleware();
    this.deviceDetector = new DeviceDetectorMiddleware();
  }

  /* initialize blog routes */
  attach = (app) =>
    express
      .Router()
      .post(
        '/',
        this.deviceDetector.isDeviceBot,
        this.authenticationMiddleware.verifyApiKey,
        this.addBlog.bind(this)
      )
      .get(
        '/blog/:id',
        this.authenticationMiddleware.verifyApiKey,
        this.searchBlogById.bind(this)
      )
      .get(
        '/',
        this.authenticationMiddleware.verifyApiKey,
        this.searchAllBlogs.bind(this)
      )
      .patch(
        '/blog/:id',
        this.authenticationMiddleware.verifyApiKey,
        this.updateBlog.bind(this)
      )
      .delete(
        '/blog/:id',
        this.authenticationMiddleware.verifyApiKey,
        this.deleteBlog.bind(this)
      );

  addBlog(req, res, next) {
    return this.blogController.addBlog(req, res, next);
  }

  searchBlogById(req, res, next) {
    return this.blogController.searchBlogById(req, res, next);
  }

  searchAllBlogs(req, res, next) {
    return this.blogController.searchAllBlogs(req, res, next);
  }

  updateBlog(req, res, next) {
    return this.blogController.updateBlog(req, res, next);
  }

  deleteBlog(req, res, next) {
    return this.blogController.deleteBlog(req, res, next);
  }
}```

this is my app js
```javascript
app.use('/api/v1/blogs', new BlogRoutes.attach(app));

but am getting an error
TypeError: BlogRoutes.attach is not a constructor
    at file:///home/moobi-kabelo/Github/Afridek/beempowered/backend/app.js:44:26
    at ModuleJob.run (node:internal/modules/esm/module_job:198:25)
    at async Promise.all (index 0)
    at async ESMLoader.import (node:internal/modules/esm/loader:409:24)
    at async loadESM (node:internal/process/esm_loader:85:5)
    at async handleMainPromise (node:internal/modules/run_main:61:12)

I moved on to Nest.js. It's basically a TypeScript bolt-on for Express. Closing ticket.

@d3m0n-533d maybe I’m wrong, but the correct syntax should be:
new BlogRoutes().attach(app)

I know that is question is geared for express.js but like others have said, a class based solution is not a good fit for the express library/framework; it is better to take a functional approach, which will be cleaner when you consider how the middlewares work. If you want an object oriented/class based solution, use NestJS or Java Spring Boot.

I know that is question is geared for express.js...

@ryanwaite28, as mentioned in 2022, we moved to NestJS.


Add to Google Search Console + request indexing

Via https://smallseotools.com/google-index-checker/, I don't believe https://docs.luxonis.com is currently indexed by Google:

This makes it hard to find everything on Google about our products.
Setup Google Search Console for our docs.

Requested:

...but an issue w/the canonical url:

Looking promising. Just searched for "BW1097" after requesting that this page get indexed:

Seeing that same pages aren't be indexed:

It could also be from the lack of a sidebar display on mobile (and Google has mobile-first indexing) so page links are hidden.

...to be safe, should probably generate a sitemap and submit to Google. See https://github.com/jekyll/jekyll-sitemap.


Update README.md + Dockerize for development

Add some instructions for:

Install dev tools
Use yarn v2 instead of the older yarn v1
Website layout
TODO!
Local testing
Basic instructions for testing

This may change significantly after review :)
Fixes #33
Type of change
Please tick the relevant option by putting an X inside the bracket

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] My code follows the guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings
[x] I have read the CONTRIBUTING document

lgtm!
in the near future, we're going to be rewriting this entire website in nextjs + ts so the database wont even be needed anymore 🥳
Is this ready for merge? I do see you have "TODO!" in the description :)

@bleonard252 @nmcain @larsb24
I've done a little bit chores and dockerized dahlia and added a seeding process. thoughts?

lgtm!
in the near future, we're going to be rewriting this entire website in nextjs + ts so the database wont even be needed anymore
Is this ready for merge? I do see you have "TODO!" in the description :)

The TODO was just something else I think is needed, otherwise. And as far as nextjs + ts, SGTM, although I was wondering if using flutter + wasm might be a "fun" choice, personally I don't particularly like js. I find ts better, but dahliaos is flutter based and I'd lean in that direction over ts.
Actually, I'm learning rust right now and I'm going to be moving more in that direction from everything I can, so rust + wasm could also be a choice :)

Hmm I tried your Step 1 but it "failed":
$ APP_MODE=SEED yarn devstart
[nodemon] 2.0.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node server.js`
/home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/connection.js:694
    throw new MongooseError('The `uri` parameter to `openUri()` must be a ' +
    ^

MongooseError: The `uri` parameter to `openUri()` must be a string, got "undefined". Make sure the first parameter to `mongoose.connect()` or `mongoose.createConnection()` is a string.
    at NativeConnection.Connection.openUri (/home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/connection.js:694:11)
    at /home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/index.js:348:10
    at promiseOrCallback (/home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/helpers/promiseOrCallback.js:9:12)
    at Mongoose._promiseOrCallback (/home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/index.js:1152:10)
    at Mongoose.connect (/home/wink/prgs/dahliaOS/forks/website/.yarn/cache/mongoose-npm-5.12.3-aa9a3d438c-50e05e1057.zip/node_modules/mongoose/lib/index.js:347:20)
    at Object.<anonymous> (/home/wink/prgs/dahliaOS/forks/website/server.js:17:10)
    at Module._compile (node:internal/modules/cjs/loader:1109:14)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1138:10)
    at Module.load (node:internal/modules/cjs/loader:989:32)
    at Function.external_module_.Module._load (/home/wink/prgs/dahliaOS/forks/website/.pnp.js:8238:14)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:76:12)
    at node:internal/main/run_main_module:17:47
[nodemon] app crashed - waiting for file changes before starting...

It behaves better if I also add "DB_URL":
wink@3900x:~/prgs/dahliaOS/forks/website (Update-README.md)
$ APP_MODE=SEED DB_URL=mongodb://localhost yarn devstart
[nodemon] 2.0.7
[nodemon] to restart at any time, enter `rs`
[nodemon] watching path(s): *.*
[nodemon] watching extensions: js,mjs,json
[nodemon] starting `node server.js`
express-session deprecated req.secret; provide secret option server.js:49:3
listening on port 3000

But I'm not sure that is correct either?
Also the rendered README doesn't look right:

lgtm!
in the near future, we're going to be rewriting this entire website in nextjs + ts so the database wont even be needed anymore
Is this ready for merge? I do see you have "TODO!" in the description :)

The TODO was just something else I think is needed, otherwise. And as far as nextjs + ts, SGTM, although I was wondering if using flutter + wasm might be a "fun" choice, personally I don't particularly like js. I find ts better, but dahliaos is flutter based and I'd lean in that direction over ts.
Actually, I'm learning rust right now and I'm going to be moving more in that direction from everything I can, so rust + wasm could also be a choice :)

The entire reason I want to move the website to NextJS is because its INSANELY fast, Like we're talking sub 50ms fast for each page. It would be GREAT for user experience and documentation.
As for the error for the URI, what is your ENV file for the database?

Furthermore, you can change the readme as you want, i just added it as a boiler for now so we don't forget to tell people to seed on their first start.

Furthermore, you can change the readme as you want, i just added it as a boiler for now so we don't forget to tell people to seed on their first start.

Ok, I'll tweak the README.
I don't have an environment file for the database, which is probably the problem! Can you provide a link to a short tutorial on how to setup the DB env, I'll include that link or a short synopsis if possible. Or maybe we can just include an quick and dirty initial enviornemt and a link on how to customize it?
On the other hand it seems all of the content is static and people aren't logging in so why is there a need for the a database in the firstplace?
Oh, and I hope your finals go well, its been a loooooong time since I was in HS, LoL!

Furthermore, you can change the readme as you want, i just added it as a boiler for now so we don't forget to tell people to seed on their first start.

Ok, I'll tweak the README.
I don't have an environment file for the database, which is probably the problem! Can you provide a link to a short tutorial on how to setup the DB env, I'll include that link or a short synopsis if possible. Or maybe we can just include an quick and dirty initial enviornemt and a link on how to customize it?
On the other hand it seems all of the content is static and people aren't logging in so why is there a need for the a database in the firstplace?
Oh, and I hope your finals go well, its been a loooooong time since I was in HS, LoL!

Creating the env stuff is deaddd simple, in the commits, you should have a .env-example, rename that to .env and start the server, i set the examples to be pretty much plug and play!
And thank youu! Appreciate the luck ❤

Using the .env-example worked like a charm! Made a couple tweaks to the README.md.

Great! So we're all set for merge right?

LGTMT

Thank you for everything! ❤

ngl it's kinda rude to remove reviews from people @Looskie

ngl it's kinda rude to remove reviews from people @Looskie

😩😩😩😩 my fault @bleonard252


[Documentation] Load Testing on DevNets and TestNets

Summary
Documents Load Testing on DevNet (and some TestNet?)
Issue

#136
#529

Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[x] Documentation
[ ] Other (specify)

Testing
Documentation changes (only if making doc changes)

[x] make docusaurus_start; only needed if you make doc changes

Local Testing (only if making code changes)

[ ] Unit Tests: make go_develop_and_test
[ ] LocalNet E2E Tests: make test_e2e
See quickstart guide for instructions

PR Testing (only if making code changes)

[ ] DevNet E2E Tests: Add the devnet-test-e2e label to the PR.

THIS IS VERY EXPENSIVE, so only do it after all the reviews are complete.
Optionally run make trigger_ci if you want to re-trigger tests without any code changes
If tests fail, try re-running failed tests only using the GitHub UI as shown here

Sanity Checklist

[ ] I have tested my changes using the available tooling
[ ] I have commented my code
[ ] I have performed a self-review of my own code; both comments & source code
[ ] I create and reference any new tickets, if applicable
[ ] I have left TODOs throughout the codebase, if applicable

Hey @red-0ne - here are some updated load test documentation pages. Would you mind taking a look? Thank you!

@red-0ne actually had a chat with @bryanchriswhite - he'll take a look at this PR. You've got so many other PRs to review at this point! :)

Thank you, @bryanchriswhite. As always — amazing feedback! I addressed most of your points, and have a couple to take care of left. I'll request a review tomorrow once they're taken care of.

@bryanchriswhite all feedback has been addressed now. Thank you! :)


Income marked as negative numbers (how to change)?

Hi there,
I've connected my account (Dutch bank account), however, credited amounts are marked as positive numbers and debited amount are marked as negative numbers. I´d like to turn this around. How do I do that?
Thanks!

I checked with Plaid and this is how the data is recovered through the API. I´ve solved this by adapting the google sheet.

Good evening. I've also observed a flipping of positive and negative for debits and credits.


flaky client generation

This is a typical client generation for me:
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate && node renameLables.js

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Successfully generated Electric client at: ./src\generated\client
Building migrations...
Successfully built migrations

I work on Windows 11.
It usually works sooner or later. Often on the second or third try.

Hi @barbalex, could you run client generation in debug mode npx electric-sql generate --debug.
When it fails in debug mode, you should see a temporary folder. Inside there should be a prisma directory with a schema.prisma file. From the temporary folder, could you try running npx prisma generate and report back here?
If this works, the issue is somewhere else in our generation process. If it fails, the problem is probably in Prisma.

So I did this four times:

npm run backend:down
[+] Running 4/4
✔ Network ps_default       Created                                                                                0.0s
✔ Volume "ps_pg_data"      Created                                                                                0.0s
✔ Container ps-postgres-1  Created                                                                                0.0s
✔ Container ps-electric-1  Created                                                                                0.0s
Attaching to electric-1, postgres-1
npm run backend:start
subscription started for postgres_1
npm run db:migrate
49 migrations applied
npm run client:generate

On time it worked. Three times I got:
PS C:\Users\alexa\ps> npm run client:generate

><EMAIL_ADDRESS>client:generate
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'

So I found the prisma folder inside the tmp folder (I deleted the previous ones before running the commands). And ran npx prisma generate inside:
  PS C:\Users\alexa\ps\.electric_migrations_tmp_sXE9tM\prisma> npx prisma generate
  Environment variables loaded from ..\..\.env
  Prisma schema loaded from schema.prisma

  ✔ Generated Zod Prisma Types to .\..\..\src\generated\client in 811ms

  ✔ Generated Prisma Client (v5.2.0) to .\..\..\src\generated\client in 315ms
  Start using Prisma Client in Node.js (See: https://pris.ly/d/client)
  ```
  import { PrismaClient } from '../../src/generated/client'
  const prisma = new PrismaClient()
  ```
  or start using Prisma Client at the edge (See: https://pris.ly/d/accelerate)
  ```
  import { PrismaClient } from '../../src/generated/client/edge'
  const prisma = new PrismaClient()
  ```

  See other ways of importing Prisma Client: http://pris.ly/d/importing-client

  🛑 Hardcoding URLs in your schema poses a security risk: https://pris.ly/d/datasource-env

So this seems to work?

Indeed, that confirms the problem is with us.
After generating the Prisma and Electric clients, we remove all files and folders that we don't need. This is done here: https://github.com/electric-sql/electric/blob/main/clients/typescript/src/cli/migrations/migrate.ts#L700
It seems that Windows complains if the directory we're trying to delete is non-empty. Could you try to change that line to: return fs.rm(filePath, { recursive: true, force: true }) in node_modules/electric-sql/dist/cli/migrations/migrate.js and then try running it again to see if that fixes it. Perhaps also put a console.log before and after that line, just to get a confirmation that it is that line that is causing the error. So:
console.log("Before rm");
const res = fs.rm(filePath, { recursive: true });
console.log("After rm");
return res;

So I did:

alter https://github.com/barbalex/ps/blob/main/node_modules/electric-sql/dist/cli/migrations/migrate.js:

async function keepOnlyPrismaTypings(prismaDir) {
  const contents = await fs.readdir(prismaDir);
  const proms = contents.map(async (fileOrDir) => {
    const filePath = path.join(prismaDir, fileOrDir);
    if (fileOrDir === "index.d.ts") {
      return fs.rename(filePath, path.join(prismaDir, "prismaClient.d.ts"));
    } else if (fileOrDir !== "index.ts") {
      // return fs.rm(filePath, { recursive: true });
      console.log("Before rm");
      const res = fs.rm(filePath, { recursive: true, force: true });
      console.log("After rm");
      return res;
    }
  });
  await Promise.all(proms);
}

then re-create the project four times, by running:
npm run backend:down
npm run backend:start
npm run db:migrate
npm run client:generate:debug

I have altered the client generation to enable creating generated labels client side. To prevent that alteration from influencing this issue I created a separate command not doing this that I call instead to test this issue:

  "scripts": {
    "client:generate:debug": "npx electric-sql generate --debug",
    "client:generate": "npx electric-sql generate && node renameLables.js"
  },

The result is:
PS C:\Users\alexa\ps> npm run client:generate:debug

><EMAIL_ADDRESS>client:generate:debug
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Successfully generated Electric client at: ./src\generated\client
Building migrations...
Successfully built migrations

PS C:\Users\alexa\ps> npm run client:generate:debug

><EMAIL_ADDRESS>client:generate:debug
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'

PS C:\Users\alexa\ps> npm run client:generate:debug

><EMAIL_ADDRESS>client:generate:debug
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Successfully generated Electric client at: ./src\generated\client
Building migrations...
Successfully built migrations

PS C:\Users\alexa\ps> npm run client:generate:debug

><EMAIL_ADDRESS>client:generate:debug
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Successfully generated Electric client at: ./src\generated\client
Building migrations...
Successfully built migrations

PS C:\Users\alexa\ps> npm run client:generate:debug

><EMAIL_ADDRESS>client:generate:debug
> npx electric-sql generate --debug

Generating Electric client...
Service URL: http://localhost:5133
Proxy URL: postgresql://prisma:********@localhost:65432/ps
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
Before rm
After rm
generate command failed: Error: ENOTEMPTY: directory not empty, rmdir 'C:\Users\alexa\ps\src\generated\client\runtime'

So unfortunaltely that does not seem to have helped.

this has barely happened any more, maybe once in the last week
and nobody else seems to have this problem
so closing

Today on my windows machine I can't generate the client at all.
I had to resort to generating it on my MacBook.

This issue persists on my windows pc. I am forced to create the client on my MacOS notebook and sync it to the pc.

Hi @barbalex, what's the issue that is preventing you from generating the client? Is it still the same "directory not empty" error?

Yes. After about two weeks during which I was forced to create the client on MacOS and sync it to the pc, my pc has now reverted to the behavior in which the client generation SOMETIMES works. So I often have to generate several times, sometimes I need to restart the pc for client generation to finally work. But id does work sporadically.

This issue is four months old. And no one has chimed in, having the same issue. So either few devs are using windows or something is unusual in my setup. Maybe not worth putting in a lot of effort...

Yes this is very odd.. Let's see if this happens to others too or not in which case we can take some actions.


Coordinate description can't be extracted as formatted date-time

Submitted on behalf of an Iris user who isn't on GitHub:
The code for generating this this string:
DimCoord([2020-08-13 00:00:00], standard_name='time', calendar='gregorian', long_name='time', var_name='time')
... is a complex combination of cf_units and numpy, and there is no public API for just getting 2020-08-13 00:00:00 alone.
It is possible to generate the string using your own code:
coord = cube.coord('time')
dt = coord.units.num2date(coord.points[i])
desired_string = str(dt)

...but it would be more useful if there was a public API for doing it.

I just realised you can also do
coord = cube.coord('time')
desired_string = str(coord.cell(i))

That's cool, I haven't come across coord.cell() before. This still looks like a candidate for a convenience function, you've just made it easier to write!

Avoiding num2date has the advantage that you can still get something if the coord is not a time coord.  Using num2date could give you more flexibility to format the string how you like via the datetime.strftime method.

We've discussed this during a @SciTools/peloton meeting, and decided that having this level of convenience would actually make Iris less helpful, as there would be so many convenience functions as to make Iris' API unreadable.
Therefore closing.


"ERROR - Handshake status 400 Bad Request" and then "ERROR - Handshake status 429 Too Many Requests"

2018-08-02 23:13:34,556 - ERROR - Handshake status 400 Bad Request
2018-08-02 23:13:34,558 - ERROR - Traceback (most recent call last):
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_app.py", line 236, in run_forever
host=host, origin=origin)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 69, in handshake
status, resp = _get_resp_headers(sock)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 135, in _get_resp_headers
raise WebSocketBadStatusException("Handshake status %d %s", status, status_message)
websocket._exceptions.WebSocketBadStatusException: Handshake status 400 Bad Request
2018-08-02 23:13:35,536 - ERROR - Handshake status 400 Bad Request
2018-08-02 23:13:35,536 - ERROR - Traceback (most recent call last):
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_app.py", line 236, in run_forever
host=host, origin=origin)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 69, in handshake
status, resp = _get_resp_headers(sock)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 135, in _get_resp_headers
raise WebSocketBadStatusException("Handshake status %d %s", status, status_message)
websocket._exceptions.WebSocketBadStatusException: Handshake status 400 Bad Request
.
.
.
(same error about 200 times in 90 seconds)
.
.
.
2018-08-02 23:15:06,825 - ERROR - Handshake status 400 Bad Request
2018-08-02 23:15:06,826 - ERROR - Traceback (most recent call last):
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_app.py", line 236, in run_forever
host=host, origin=origin)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 69, in handshake
status, resp = _get_resp_headers(sock)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 135, in _get_resp_headers
raise WebSocketBadStatusException("Handshake status %d %s", status, status_message)
websocket._exceptions.WebSocketBadStatusException: Handshake status 400 Bad Request
2018-08-02 23:15:06,848 - ERROR - Handshake status 429 Too Many Requests
2018-08-02 23:15:06,849 - ERROR - Traceback (most recent call last):
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_app.py", line 236, in run_forever
host=host, origin=origin)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 69, in handshake
status, resp = _get_resp_headers(sock)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 135, in _get_resp_headers
raise WebSocketBadStatusException("Handshake status %d %s", status, status_message)
websocket._exceptions.WebSocketBadStatusException: Handshake status 429 Too Many Requests
2018-08-02 23:15:06,875 - ERROR - Handshake status 429 Too Many Requests
2018-08-02 23:15:06,875 - ERROR - Traceback (most recent call last):
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_app.py", line 236, in run_forever
host=host, origin=origin)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_core.py", line 220, in connect
self.handshake_response = handshake(self.sock, *addrs, **options)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 69, in handshake
status, resp = _get_resp_headers(sock)
File "/usr/local/python3.6/lib/python3.6/site-packages/websocket/_handshake.py", line 135, in _get_resp_headers
raise WebSocketBadStatusException("Handshake status %d %s", status, status_message)
websocket._exceptions.WebSocketBadStatusException: Handshake status 429 Too Many Requests
.
.
.
(The error 429 never stopped until I kill the process)

Hi @xiaoxin233 .
I got this same issue before.
Handshake means Bitmex could not authorise your API key.
Please check your api key correctly. (~./bash_Profile)
After add MEXAPI Key , reflesh the bash_Profile.  ( source ~./bash_profile )
please check it.


Make /trade consistent, reliable, and remove item deletion bugs (transactional)

Description:
The risk for item deletion in the /trade command is relatively large. Several database calls are performed sequentially, committing after each one, which is bad if there's any sort of bot lag/freeze/stall, or similar with the psql server, or even the network stack.
Some of these are much less likely than others, nevertheless, we do see this issue crop up with some regularity.
(We see it all the time, but usually it doesn't result in item loss.)
Twice just today it resulted in item loss, however, so I'm making this a top priority.
Changes:

Removes the 4 separate steps and replaces it with a new function, tradePlayerItems
Trade player items prepares 2 queries, one to update each user, and runs both of them in a single transaction, so either both succeed, or neither do.
Adds functions to both users userQueue simultaneously, so that other operations which act on the bank are properly queued. (Even though this should be unnecessary with a single transaction)

Other checks:

[x] I have tested all my changes thoroughly.

I even tested the recipients user queue to make sure it properly delays other addItemsToBank() functions, like buy items.
Everything is working as intended.

I'm closing this PR due to 4 months of inactivity, I'm not denying it, just cleaning up some PRs. feel free to re-open if you want to continue working on it. Although, we'd probably need to discuss the implementation of it. I think this would be better off with refactoring transactItemsFromBank, so we can have a function which returns the plain prisma.user.update promises, so we can update both users in a transaction, and so all bank updates continue to go through one place.


versions

DrawBot and RoboFont users complain about a pop up prompting to install git when launching the latests version of the apps.
I suspect _version.py is requesting it, this feels a bit over engineered  :)

The prompt is actually about installing the OSX dev tools. I'll hope to reproduce it tomorrow, and will try to determine whether it is indeed caused by _version.py.

Hold on. You have to install fonttools in a regular way, not just editable or using pth before you package up your py2app, else the _version.py will be the dynamic one that is meant for git source control, instead of the static one that's generated upon install.

You first need to do pip install -v . from the fonttools source directory. Then you can run your setup.py py2app so that py2app will copy the fonttools package that was installed in your python environment, instead of grabbing it straight from the git repository in your PYTHONPATH.
Another option is to do python setup.py build and have py2app copy the generated build/lib/fontTools package.
Please let me know if that works for you.

And we're back to square one with the version discussion :(

please do not reopen this discussion now.
The correct way to install a python package is... to install by having the installer generate the package metadata.
As I said, It is easy for other application developers bundle fonttools.
They could even simply unzip the source distribution, or the .whl package (you can rename it .zip and extract the content).
I just opened up the Robofont.app package and, indeed, the Contents/Resources/lib/python2.7/fontTools/_version.py is the wrong one.

I understand you don't like to reopen the discussion, but to me this is another proof that the version system is brittle. It tries to do too much too smartly. I don't like how it enforces one way of "correct" deployment, or rather, how it weirdly fails when deployment wasn't done "correctly".

Ok, let me recap.
versioneer computes the package version from the git metadata, so it only works when it is inside a git repository.
When you create a distribution, or run setup.py install, pip install etc., versioneer generates a static _version.py module containing just strings, so git is not required.
py2app works by looking at all the package imported in your python code and copy them inside the .app bundle. If you PYTHONPATH contains the fontTools git repository, py2app copies its content inside your app, but without the .git folder, hence breaking things.
The solution is to make sure that a static version of fontTools package, ie. one that was built or installed, is found by py2app, rather than the git repository. There are also ways of specifying the search path in which py2app should look for packages to bundle.
I hope now things are more clear.

I understand how you made it work. I just don't agree with how you made it work.

As in: the other solution is just put a static version in the code like we always had.

We did already put "a static version in the code":
https://github.com/fonttools/fonttools/blob/master/Lib/fontTools/__init__.py#L12
That should give you the best approximation possible for the latest tagged version, even if a redistributor has bundled the package in a way that makes it impossible to give a precise answer.
A RuntimeWarning is what should be emitted, and that's there for good reasons.
If versioneer is raising an exception instead, then I can look into ways to handle that nicely.

this means git is a requirement for fontTools, please add to the requirements...
Nevertheless this is good or bad practice, forcing users to install git is not so nice.
This prompt must appear for users who which to install fontTools without having git.

No, I'm not adding git to the requirements! How can you even clone the git repository without git?!
I just installed the latest Robofont.app, I unlinked by homebrew git and sudo mv /usr/bin/{git,_git} so that git is no longer in my path.
When I start Robofont.app I don't get any pop-up message or error in the output window. If I import fontTools and print it's version, I get "3.2.3" which is nice and clean, despite the wrong _version.py has been copied.
If you give me more details I can try reproduce and help you debug the issue.
But again, I invite you to think about the difference between a development environment, where tools like git must be available for the development to take place, and the user environment (which Robofont.app belongs) where your library should be installed in the standard way instead of just copied off a git repository.

I'll update the README with instructions on how to bundle fonttools in your app.

@typemytype @justvanrossum
is this the warning message that your users are getting?
http://apple.stackexchange.com/questions/161648/how-to-use-gcc-or-git-without-installing-xcode
xcode-select: note: no developer tools were found at '/Applications/Xcode.app', requesting install. Choose an option in the dialog to download the command   line developer tools.

I still can't reproduce it, maybe tomorrow I'll try on a clean machine without Xcode installed.

No, that is not the message. It's an actual dialog that people actively have to dismiss. It may only be happening on 10.11 or up or 10.12. If I'm lucky, I'm meeting students today with a setup in which this thing is triggered.
Yes, it's good to think about the difference between development and deployment, but fonttools should not push it's preferred way of deployment through user's throats. Look, you've created something that causes a problem where there wasn't a problem before. It needs to be fixed. And therefore I reopened the discussion.
So let me recap the requirements for version info inside fonttools:

to be able to uniquely identify which release is being run, if it's an actual release
if the version that is being run is not a release (ie. in-between from git), identify that that is the case, but nothing more. It is absolutely not necessary to have a git commit identifier embedded.

The current solution is overly complicated, and, as evidenced by this issue, unnecessarily brittle. (I mean seriously, do we need 500 lines of code for a version number? A version number!)
What I want to happen for a release "A.B.C" is this:

bump fontTools.version and setup.py to version "A.B.C"
tag release
git commit
do release stuff: tarballs, zips, wheels, eggs, PyPI, whatever.
bump fontTools.version and setup.py to version "A.B.C+" (The case "this is not a release")
git commit

A script that does all this will surely be simpler and easier to maintain than _version.py.

Ok Just, I surrender. 🏳
You're right, it's not worth keep arguing about this thing.
I'll revert to a static version string as you suggested.
Really sorry for all the trouble.

Thanks Cosimo. Sometimes we need to keep things as simple (and possibly stupid) as possible.
Btw. here is a screenshot of the message. Sorry, it's Polish :) It says something like "would you like to install XCode/dev tools, because it appears you're trying to use git". Apparently, on this computer, the same message appears everytime "save" is done in Glyphs, so there may be some fonttools involved there, too (could be an extension, though).

FontTools 3.3.1 is out.

I actually ran into a different kind of "dependancy hell" myself when I
was trying to hack around fontTools. I applaud your efforts, Cosimo, but
I agree with Just & Frederik that versioneer was a bit over-engineered.
Many thanks for reverting to static!
A.
On 14 Dec 2016, at 9:30, Cosimo Lupo wrote:

Ok Just, I surrender. 🏳
You're right, it's not worth keep arguing about this thing.
I'll revert to a static version string as you suggested.
Really sorry for all the trouble.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/fonttools/fonttools/issues/767#issuecomment-266973706

No problem.
TBH, I preferred the setuptools_scm method over the versioneer one, as the former doesn't attempt to run a git subprocess at import time, but stores the computed string inside the package meta-data. The problem with it was that:

the package metadata is not copied over by py2app/pyinstaller, etc. (wrongly so, IMO);
developers who install-editable have to reinstall, or manually refresh the metadata using the egg_info command, every time they git pull.
For some this was a bit too much. Anyway, I'm glad we finally all agreed!


V2 add volume

What does this PR do and why?
Closes https://github.com/jbx-protocol/juice-interface/issues/691
Screenshots or screen recordings
If applicable, provide screenshots or screen recordings to demonstrate the
changes.
Acceptance checklist

[ ] I have evaluated the
Approval Guidelines
for this PR.
[ ] I have tested this PR in
all supported browsers.

 Just a few edge case comments:
Can we get '0' showing up there when volume is 0, and maybe we should do the same for 'In treasury' while you're there 🤪

Rebasing...


[doc] correct typo in node_postprocessors doc

Description
Correct a copy/paste typo in node_postprocessors doc.
Type of Change

[x] This change requires a documentation update

How Has This Been Tested?

[x] I stared at the code and made sure it makes sense

Thanks!


Support installation in non-default namespaces

Already works out of the box when the namespace is specified when the application is deployed with helm install:
helm install pm averbis/patent-monitor -n averbis


fix: version of react and react-dom are not match

fix #632

I've signed CLA in https://github.com/remix-run/remix/pull/905

Hey @yesmeck !
Although you might've signed in #905 , it appears the current contribs file is lacking you!!

Please go ahead and resign it :)


Allow another shortcut format: url/port plus test command

For example allow
server-test 1234 cypress:run

:tada: This issue has been resolved in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Task - comprehensive specimen: Red trash icon on determiner and type designator

This would seem to imply removal of the entry from the database.  Use gray icon instead for removing from the list?

No, this is real data, added to the system!

I may be wrong, but it seems like until thisperson selected is actually saved, shouldn't the behavior be like the blue undo icon?

In TW red means clicking will touch the database immediately.  This is the case here.  This is a metadata row being created or destroyed, independent of the other related data (collection object).

To my relatively uninformed viewpoint. it looks like it is going to remove the person ... whereas the undo icon seemed more intuitive for a list item from the autocomplete...


UI: Converted data insight dropdown to checkbox dropdown

Describe your changes :

issue: https://github.com/open-metadata/OpenMetadata/issues/8996#issuecomment-1327618489
Added checkbox dropdown for data insight filters

Type of change :

[x] Improvement

Frontend Preview (Screenshots) :

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Can we increase padding around the button? I feel it's too less cc: @devyani-kaushik

Can we increase padding around the button? I feel it's too less cc: @devyani-kaushik

@ShaileshParmar11

Can we increase padding around the button? I feel it's too less cc: @devyani-kaushik

@ShaileshParmar11

Ill take care of it, in the next PR of design improvement thanks


[Question] tthe link of the pre-trained vision tokenizer weight cannot be opened?

Question
Hi, It seems the URL for the pre-trained vision tokenizer weight is not correct. Where can I download the related files: 'vision_tokenizer_config.yaml' and  'vqgan.ckpt'?

Oh sorry for that. I've fixed the link in the updated readme. Please refer to here.

Great, thanks~


[Proposal] dynamic dag based shuffle for mars

This PR proposed a dynamic dag based shuffle for mars, which consists of:

Pull-based Shuffle using Ray Future DAG
Push-based Shuffle using Ray Future DAG
Mitigate Straggler tasks
Dynamically coalescing shuffle partitions
Dynamically splitting shuffle partitions
Support failover by lineage recontruction

Related issue number
https://github.com/mars-project/mars/issues/2916

Theoretical description only will not make a feasible MEP. At least sketches of implementations or API draft is needed for further implementation.

Theoretical description only will not make a feasible MEP. At least sketches of implementations or API draft is needed for further implementation. I also recommend separating this MEP into several sub-MEPs and focus on preliminary shuffle implementation first.

Agreed, I'll close this PR and submit a series of MEPS later.


0.7.1 release

Mostly for wider awareness.
I don't have that much time in the next few days to finish https://github.com/dask/dask-jobqueue/pull/398 so my priority is to cut a 0.7.1 relase and delay that until 0.7.2.
There are already a few useful things in 0.7.1:

different interfaces on scheduler and worker through scheduler_options
all cluster classes: interface set from config file was ignored
LSFCluster switch to use_stdin=True by default (it seems Summit is a bit peculiar)
OARCluster and HTCondor fixes

0.7.1 was pushed on PyPI.

Woot.
On Wed, Mar 25, 2020, 8:28 PM Loïc Estève<EMAIL_ADDRESS>wrote:

0.7.1 was pushed on PyPI.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask-jobqueue/issues/399#issuecomment-604207764,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACKZTH2MBZW63RVILQK3U3RJLDVJANCNFSM4LT43XKA
.

It was not on my radar that dask was released recently, hmmm maybe I could have waited a bit just in case there were unexpected side-effects. I did check that the Dask-Jobqueue tests pass with Dask/distributed 2.13.
Oh well, given the circumstances, what could possibly go (even more) wrong ;-) ?

Many many thanks @lesteve for keeping on working on dask-jobqueue!

@guillaumeeb no problems, I think you were doing the bulk of the work at one point so it is only fair that I take turns too ;-) !


Create devcontainer.json

Description

Related

Testing

Checklist
Before submitting a Pull Request, please ensure the following:

[ ] 🚨 This PR does not introduce breaking changes.
[ ] All CI checks (GH Actions) pass.
[ ] Documentation is updated as needed.
[ ] Tests are updated or added as necessary.
[ ] Code is well-commented, especially in complex areas.
[ ] Git history is clean — commits are squashed to the minimum necessary.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@Ramzifayyaz3161 Could you please describe in what context you would like to use devcontainers (e.g. IDE or ESP-IDF in pure terminal)?


[Enhancement] autovacuum without list tablet metadata

Executing autovacuum tasks no longer performs a list of tablet metadata. list tablet metadata is a costly operation, and when there is a large amount of tablet metadata (more than a few million), it takes a very long time for the results to be returned, affecting the speed of the vacuum.
Note that the autovacuum task still lists txn logs, which normally doesn't have too many files and shouldn't take too long, so it hasn't been optimized away for now.
What type of PR is this:

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[x] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 62 / 66 (93.94%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
62
66
93.94%
[127, 167, 168, 169]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 90 / 95 (94.74%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
90
95
94.74%
[130, 211, 212, 213, 214]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 93 / 102 (91.18%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
93
102
91.18%
[131, 216, 217, 218, 219, 220, 221, 222, 223]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 83 / 90 (92.22%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
83
90
92.22%
[130, 132, 211, 212, 213, 214, 215]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 83 / 90 (92.22%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
83
90
92.22%
[130, 132, 211, 212, 213, 214, 215]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:heart_eyes: pass : 83 / 90 (92.22%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/lake/vacuum.cpp
83
90
92.22%
[122, 124, 203, 204, 205, 206, 207]

@Mergifyio backport branch-3.2

@Mergifyio backport branch-3.1


insight: more insight into the running Node process

i.e. event loop delay, cpu utilization, etc.

I think if something like this is requested, it's most likely for local debugging, where we just can't compete with node-clinic


Fix xml to markdown failure

Fix this failure: https://github.com/IntelliTect/CodingGuidelines/runs/5606772816

@Keboo added a workflow dispatch so I can manually run the failing workflow to check it


Add "ATTRIBUTES" functionality

See https://github.com/senzing-garage/garage-roadmap/issues/27

Pull requests:

https://github.com/senzing-garage/sz-sdk-python-abstract/pull/72


Update to LLVM 15

LLVM 16 requires opaque pointers, which we currently can't support (mostly due to use of getPointerElementType() almost everywhere). In LLVM 14, opaque pointers don't seem to work for us (appears to be an issue in the optimization pipeline or elsewhere in the JIT when reading the module). This PR attempts an intermediate upgrade to LLVM 15 with opaque pointers disabled. If this works, we can then enable opaque pointers under LLVM 15, and then the upgrade to 16 should be smooth.

Hopefully this passes tests now - either way it is ready for review. This upgrades our Linux conda builds to LLVM 15 (including clang-format) but continues to run LLVM 14 on Windows and in Docker containers. LLVM 15 is a stepping stone because it supports opaque pointers, but does not require them (LLVM 14 does not support them, LLVM 16 requires them). However, it has bugs in CMake which effect Windows (resolved in LLVM 16). So, the plan is to run LLVM 15 in Conda for a bit while we enable opaque pointers, then upgrade to LLVM 16 on all machines.
If we have to do a release we should be fine to release on LLVM 14 or LLVM 15 (except on Windows) - I did not update meta.yml (though I am not sure that is stilled used by conda-forge). Developers should update conda once this is merged to pickup clang-format improvements.
@kurapov-peter this seems to pass L0 tests but your eyes on the L0 changes would be appreciated!


Showcase Submission for challenges/182-apollonian-gasket

Thank you tobidot for your contribution! A member of the Coding Train team will review it shortly.

Appolonian Gasket
tobidot

Hi @tobidot, this looks so cool! I'm getting an error when running the sketch, is it just me or did something maybe break?

Hey @shiffman ,
Thats weird i get that to when i open it on a fresh new tab, but it works if dev-console is open and i hit reload.
Ah i had the scripts load "asnyc", which means it was random if it worked or not.
Changed it to "defer" now and should run consistently now.
Sorry for the late answer, i had hidden my notifications for github as it is mostly dependabot 😄  🤖

Great! It works now!


Using controls without SPFx (outside of SharePoint)

Category
[ ] Enhancement
[ ] Bug
[x] Question
Version
Please specify what version of the library you are using: [3.0.0]
Question
Maybe be a stupid question, but how hard could it be to use the SPFx controls react outside the SharePoint environment?
I mean, something like hosting on own server, with OAuth connection to SharePoint (so there is no "BaseComponentContext" aka "pageContext", no "spHttpClient", and no "fetchClient", so these needs to be replaced basically?). @fluentui is available without any prerequisites basically. How much work could it be to make this happen? What could be the best strategy here (except "forget it" 😄)
Thank you in advance!

Hi @nbelyh,
It will be hard as many of the controls use BaseComponentContext and some other classes from SPFx.
Unfortunately, there are no interfaces in the SPFx core that we could use in our type definitions instead of classes.
Because of that it could be tricky.
Theoretically, you could create your own implementation of BaseComponentContext and pass it to the controls as yourContext as any.
Probably, it could work.

@AJIXuMuK Thank you for the quick response. Actually I may need just a few controls, like filePicker/folderPicker, peoplePicker, and richText. I'll give it a shot and see how it goes.

@AJIXuMuK One question if I may - what could be a possible replacement for the theme loader? I mean, some controls are using syntax like border-color: "[theme: neutralTertiary, default: #a19f9d]". As far as I understand, this assumes that the styles are being loaded using SPFx. It seems I have found the implementation here: "@microsoft/load-themed-styles". What could be a way to use this to "load the styles manually"?


viz: the series tooltip may be stuck on screen after reopening a snapshot

repro steps:

open a snapshot
move the cursor around, especially on graphs where a tooltip about the current value appears
open a new snapshot
the tooltip at step 2 is stuck and does not go away.

No longer reproducible after upgrading to 7.1.5.


Data

Hiya!
I was wondering if you going to release the data soon (or will wait for the manuscript to be accepted ?) really cool stuff!

hello! Yes, we were waiting for the acceptation... but there's maybe something among the https://braincatalogue.org/please data that you can use? Or were you looking for something in particular?

Great! My main interest is looking at the surfaces for a project I will start later in the year. What is on the catalogue is great and will get me started ! :)


[ci] Configure nightly tests on public CI

This PR sets up the nightly E2E test run. This addresses #16715 but requires some cleanups afterwards (which are also listed in the issue).

Because this is a nightly pipeline, the per-PR CI will not exercise this change. I've tested this on the Release branch manually, and the tests are running correctly. Unfortunately, it looks like one of the tests is failing, but the pipeline itself is successful.
You can see the successful run here.


Combustion simulation

I am pretty new to trixi.jl. it seems to be a great code though.
is there a way to simulate hydrogen combustion by using compressible N-S equations in a pipe?

Compressible Navier-Stokes equations is definitely our business. Maybe also in a pipe if you could start with a 2D setup or have a 3D mesh in a format which Trixi would understand. Chemical reactions are less familiar to most of us. Could you give some details on your model? Is the reaction or the transformation of one species into another something that can be calculated point wise or written as a source term in the equations?

There are some examples with multi-component compressible Euler which I think are very close.

okay thank you, I will check them out and see if it can add them to the N-S equations.

I am currently verifying a set-up of Trixi with multi-species Euler with chemical reactions, hopefully I will have the repo up in a couple of weeks.

I look forward to see the repo for the multi-species Euler with chemical reactions.

@sezerh24 The code is available now: https://github.com/knstmrd/paper_ec_trixi_chem


Add flag to emit LLVM IR after parsing.

This adds the flag --emit-ir which can be used in conjunction with
clspv-opt to develop and debug clspv passes.
The flag emits LLVM IR right after the module has been parsed.  It
seemed the most natural place to dump the IR, because it gives the most
flexibility.  Once the initial IR has been generated, all the passes up
to the problematic one can be applied via clspv-opt.

Since clspv does not expose SPIRV generation as a pass, it's not really possible to go to SPIRV from clspv-opt.  I'm thinking that this could be done either here or as a separate PR.  Thoughts?

I was considering making a second pass around the core of SPIRVProducerPass that sets up output files based on the command line. Definitely could be a separate PR.


do not use ctrl+u with terminal focus

These changes prevent agda mode from "eating" ctrl+u before it makes it to the terminal!
I'm sorry I don't know how to test this locally, but I've made these local changes to my shortcuts file and achieved the desired behavior.

Thanks, this looks great!


background color set to black

Describe the bug
I have just switched from an older version of svelte-feathers (using 'Icon' and setting the name to get the desired icon) to the new version, but the background colour of my icons is now black.

Reproduction
<script>
import { Edit } from 'svelte-feathers';
</script>

 <Edit class="shrink-0 h-4 w-4" />

Version and System Info
System:
    OS: macOS 14.2.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 1.71 GB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.7.1 - ~/.nvm/versions/node/v21.7.1/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v18.7.0/bin/yarn
    npm: 10.5.0 - ~/.nvm/versions/node/v21.7.1/bin/npm
    pnpm: 8.15.6 - ~/.nvm/versions/node/v18.7.0/bin/pnpm
  Browsers:
    Chrome: 123.0.6312.105
    Safari: 17.2.1
  npmPackages:
    @sveltejs/kit: ^2.5.5 => 2.5.5
    svelte: ^4.2.12 => 4.2.12
    svelte-feathers: ^1.0.5 => 1.0.5
    vite: ^5.2.7 => 5.2.7

btw, the red box around the icon is just from my screen capture program.

Ok - if I set fill="transparent" this resolves the issue:
<Edit fill="transparent"  class="shrink-0 h-4 w-4" />


SDL-TTF: Wiki-Pages disappeared

I think once there were Wiki-Pages.
They are empty now: https://wiki.libsdl.org/SDL2/SDL_ttf
Please reactivate it.

https://wiki.libsdl.org/SDL2_ttf

Thanks.

But it's not linked here: https://wiki.libsdl.org/SDL2/Libraries


Module parse failed: Unexpected token

Hi guys!
I’m trying to convert my app design from pxcode to the code of ReactNative.

[Report] Missing package.json in this repo.

After copied the react native code in pxcode, I got the error as follows;
Module not found: Can't resolve 'react-posize'
  4 |  import React from 'react';
  5 |  import { View, StyleSheet, Text, Image, ImageBackground } from 'react-native';
> 6 |  import { Px } from 'react-posize';
    | ^
  7 |
  8 |  export default function Main(props: any) {
  9 |    return (

I found the generated code needed this repository pxcode/posize. So I installed this repository because react-posize is missing in the package manager.
yarn add https://github.com/px2code/posize

But I still got the same error. When I digged this repository, I found package.json is missing in this repository.
I created package.json as follows then the error was disappeared ;)
{
    "name": "react-posize",
    "version": "1.0.0",
    "description": "Posize React Component",
    "main": "./src/index.js",
    "module": "./src/index.js",
    "type": "module",
    "scripts": {},
    "keywords": [
      "react",
      "posize"
    ],
    "author": "James from pxCode",
    "license": "MIT Licence",
    "dependencies": {
      "aphrodite": "^2.4.0",
      "react-bootstrap": "~2.1.1"
    }
}

Missing webpack.

After that, I got another error as follows;
./node_modules/react-posize/src/v1.00.js 183:4
Module parse failed: Unexpected token (183:4)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|     maxDisplay, xxxlDisplay, xxlDisplay, xlDisplay, lgDisplay, mdDisplay ,smDisplay, xsDisplay, trackStyle, areaStyle);
|   return (
>     <div key={'track'}
|          className={
|            [

As far as I know, v1.00.js seems to be broken. Does anyone know how to fix this error?

Mistook to open the issue to px2code/react-posize repo


Add support for KHR_materials_emissive_strength

Objective

Fix blender gltf imports with emissive materials
Progress towards https://github.com/bevyengine/bevy/issues/5178

Solution

Upgrade to gltf-rs 1.3 supporiting KHR_materials_emissive_strength

Changelog

GLTF files using emissiveStrength (such as those exported by blender) are now supported

Migration Guide

The GLTF asset loader will now factor in emissiveStrength when converting to Bevy's StandardMaterial::emissive. Blender will export emissive materials using this field. Remove the field from your GLTF files or manually modify your materials post-asset-load to match how Bevy would load these files in previous versions.

tested on https://github.com/KhronosGroup/glTF-Sample-Models/tree/master/2.0/EmissiveStrengthTest
with main:

with this PR:


[BUG] hover clicking message bug

What is the bug?
make it use translation version of command - because i have "join" translated to polish - "dolacz" and after clicking hover message command that executes is /team join not /team dolacz - so it does not work...
Expected Behaviour
Execute translated command
How to Reproduce
Use newest betterteams
Error message
No response
Output of /teama version
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Storage Method: com.booksaw.betterTeams.team.storage.storageManager.SeparatedYamlStorageManager
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Minecraft Version: git-Paper-496 (MC: 1.20.4)
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Language Selected: pl
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Online mode: false
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Player count: 0
[15:46:57] [Craft Scheduler Thread - 905 - BetterTeams/INFO]: Wersja pluginu: 4.9.4
Additional Information
No response

This bug has been fixed and the patch will be included in the next update. Thank you for reporting.


Anomaly metrics

Brainstorm a set of metrics that can lean to anomaly detection. Anomaly detection in a sense for anything which can improve performance, security...
For instance:

RPC call within the same service
dangerous SQL queries
dangerous patterns in URL

I also have a few suggestions:

anomalous spans with suspiciously long latency (compared to similar spans)
unusual trace structures


Add the data portal navbar to explorer

Desired outcome:

Implementation considerations:

In an ideal world, we have a monorepo so changes to the navbar component will apply to both data portal and explorer pages. Alternatively, we could have a separate component library for the navbar that will be upstream of data portal and explorer. The latter two options are much more overhead than simply copying the navbar and its import dependency tree into explorer. Changes to nav bar styling in data portal will have to be manually mirrored in explorer.
The data portal navigation bar uses Next.js Links/Routers to switch between pages and determine if a page is active or not. Simply adding Next.js dependencies to explorer is not sufficient. Because none of the links in the navbar will be active when on explorer, the router logic is unnecessary (useRouter is used only to check if we are on a particular page for highlighting the link).
The cellxgene information hamburger menu will need to be added to the navbar. The current logo and title can go.

Duplicate of https://app.zenhub.com/workspaces/single-cell-5e2a191dad828d52cc78b028/issues/chanzuckerberg/single-cell-explorer/411


[CODE] Change Timeout to 800ms from 2500ms to enable pinging in 1 second intervals

Change limit to 1 second + extra warning


⚠ Bofrost.fr has degraded performance

In bf85ece, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 840 ms

Resolved: Bofrost.fr performance has improved in 69c8d5b.


wf-recorder: unstable-2019-04-21 -> 0.1

Motivation for this change
https://github.com/ammen99/wf-recorder/compare/ddb96690556371007e316577ed1b14f0cb62e13c...65a29cbdf4c4c3930aa92816edf224f3ce5d385b
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

cc @CrazedProgrammer

Looks good, thanks for doing this!


Notice: Undefined variable: secureRenderer in

I have installed the magento2-hyva-admin.
Update my product grid xml like
vendor/magento/module-catalog/view/adminhtml/layout/catalog_product_index.xml
<page xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:View/Layout/etc/page_configuration.xsd">
    <update handle="hyva_admin_grid"/>
    <body>
        <referenceBlock name="menu">
            <action method="setActive">
                <argument name="itemId" xsi:type="string">Magento_Catalog::catalog_products</argument>
            </action>
        </referenceBlock>
        <referenceBlock name="page.title">
            <action method="setTitleClass">
                <argument name="class" xsi:type="string">complex</argument>
            </action>
        </referenceBlock>
        <referenceContainer name="content">
            <uiComponent name="product_listing"/>
            <block class="Magento\Catalog\Block\Adminhtml\Product" name="products_list"/>
        </referenceContainer>
    </body>
</page>

Getting error like this
exception(s):
Exception #0 (Exception): Notice: Undefined variable: secureRenderer in pub/developer/app/code/Hyva/Admin/view/adminhtml/templates/page/js/require_js.phtml on line 16
Exception #0 (Exception): Notice: Undefined variable: secureRenderer in pub/developer/app/code/Hyva/Admin/view/adminhtml/templates/page/js/require_js.phtml on line 16
#1 include() called at [vendor/magento/framework/View/TemplateEngine/Php.php:59]
#2 Magento\Framework\View\TemplateEngine\Php->render() called at [vendor/magento/framework/Interception/Interceptor.php:58]
#3 Magento\Framework\View\TemplateEngine\Php\Interceptor->___callParent() called at [vendor/magento/framework/Interception/Interceptor.php:138]
#4 Magento\Framework\View\TemplateEngine\Php\Interceptor->Magento\Framework\Interception\{closure}() called at [vendor/magento/framework/Interception/Interceptor.php:153]
#5 Magento\Framework\View\TemplateEngine\Php\Interceptor->___callPlugins() called at [generated/code/Magento/Framework/View/TemplateEngine/Php/Interceptor.php:26]
#6 Magento\Framework\View\TemplateEngine\Php\Interceptor->render() called at [vendor/magento/framework/View/Element/Template.php:271]
#7 Magento\Framework\View\Element\Template->fetchView() called at [vendor/magento/framework/View/Element/Template.php:301]
#8 Magento\Framework\View\Element\Template->_toHtml() called at [vendor/magento/framework/View/Element/AbstractBlock.php:1100]
#9 Magento\Framework\View\Element\AbstractBlock->Magento\Framework\View\Element\{closure}() called at [vendor/magento/framework/View/Element/AbstractBlock.php:1104]
#10 Magento\Framework\View\Element\AbstractBlock->_loadCache() called at [vendor/magento/framework/View/Element/AbstractBlock.php:674]
#11 Magento\Framework\View\Element\AbstractBlock->toHtml() called at [vendor/magento/framework/View/Result/Page.php:249]
#12 Magento\Framework\View\Result\Page->render() called at [vendor/magento/framework/View/Result/Layout.php:171]
#13 Magento\Framework\View\Result\Layout->renderResult() called at [generated/code/Magento/Backend/Model/View/Result/Page/Interceptor.php:193]
#14 Magento\Backend\Model\View\Result\Page\Interceptor->renderResult() called at [vendor/magento/framework/App/Http.php:120]
#15 Magento\Framework\App\Http->launch() called at [generated/code/Magento/Framework/App/Http/Interceptor.php:24]
#16 Magento\Framework\App\Http\Interceptor->launch() called at [vendor/magento/framework/App/Bootstrap.php:261]
#17 Magento\Framework\App\Bootstrap->run() called at [index.php:39]

Hi @https://github.com/navinbhudiya
I don't think you have used Hyva Admin Grids in the way you're supposed to do so.
It's pretty straight forward to use:

Create your module
Create your hyva grid configuration. In that example module could be:
https://github.com/hyva-themes/hyva-admin-test-module/blob/main/view/adminhtml/hyva-grid/products-grid.xml
Update a section or create a new section in the backoffice to display the grid

Check the example module, it's the best way to go:
https://github.com/hyva-themes/hyva-admin-test-module

Hi @https://github.com/navinbhudiya
I don't think you have used Hyva Admin Grids in the way you're supposed to do so.
It's pretty straight forward to use:

Create your module
Create your hyva grid configuration. In that example module could be:
https://github.com/hyva-themes/hyva-admin-test-module/blob/main/view/adminhtml/hyva-grid/products-grid.xml
Update a section or create a new section in the backoffice to display the grid

Check the example module, it's the best way to go:
https://github.com/hyva-themes/hyva-admin-test-module

Please also refer to the documentation at https://github.com/hyva-themes/magento2-hyva-admin/tree/main/doc/1. Overview/3. Walkthrough

Please also refer to the documentation at https://github.com/hyva-themes/magento2-hyva-admin/tree/main/doc/1. Overview/3. Walkthrough

Seems like this issue has resolved itself.

I am getting the same error in magento 2.3.6
with your test extension:
https://github.com/hyva-themes/hyva-admin-test-module

I'll reopen the issue and add a polyfill in the next release.
Unfortunately I've got myself in a bit of a uncomfortable situation where I can't simply create a new release right now because:

Automatic backports to php7.3 with rector is no longer an option
I have a lot of work in the hyva-forms branch.

Because of 1) I want to backport the main branch to 7.3 manually and then use that for releases.
But backporting the main branch now would cause major conflicts when the hyva-forms branch is ready to be merged.
I see two possible ways forward:

Merge hyva-forms now, with half-finished forms support
Backprt to 7.3, implement the polyfill and make a release
Continue hyva-forms development

or

Continue hyva-forms development
Merge when done
Backport, implement polyfill and release

I followed through with the first option. Please upgrade to release 1.1.4 which includes the SecureHtmlRenderere polyfill.


Move mockredis to test requirements

It is not necessary to be installed typically.

It might make sense to remove the DEFENDER_MOCK_REDIS setting altogether - which makes this kind of supported.
Or, when leaving it, it should be documented that mockredis needs to get installed, too.

Coverage decreased (-0.02%) to 91.404% when pulling db9377de55f1385584b587c1b8afc8ee23821e4f on blueyed:move-mockredis into 5aa69bac96e0a82d773d1aa13a817862ccfc555f on kencochrane:master.

Coverage decreased (-0.02%) to 91.404% when pulling db9377de55f1385584b587c1b8afc8ee23821e4f on blueyed:move-mockredis into 5aa69bac96e0a82d773d1aa13a817862ccfc555f on kencochrane:master.

Coverage decreased (-0.02%) to 91.404% when pulling db9377de55f1385584b587c1b8afc8ee23821e4f on blueyed:move-mockredis into 5aa69bac96e0a82d773d1aa13a817862ccfc555f on kencochrane:master.

closing, and replacing with #119


cannt import install_twisted_reactor  with kivy  and twsited application   when  execute a converted .exe

Software Versions

Python:  Python 3.11.4
OS: Windows 10
Kivy: 2.2.1
Kivy installation method: pip

Describe the bug
I made a python server application   with   kivy and  twisted,  it works fine on .py  but not work with a .exe I convert by pyinstaller .
The build is okay but when i execute it , i will face a error like folllowing

Expected behavior
i can fun a .exe build as regular python did.
To Reproduce
make a python app  with  kivy  and twisted .
Add   "
from kivy.support import install_twisted_reactor
install_twisted_reactor() "
to code
Thanks for helping

@icarus0508 Have you tried adding 'twisted.internet._threadedselect' to hiddenimports list in your .spec file?


Not_Null String property doesn't prevent insertion via studio command line or orientjs driver

When a Class is created with Not_Null property, when you try to create a new record from orientdb studio (not via command line), if you not set the Not_Null property it doesn't work and the error message explain why.
But from the command line in studio or from orientjs driver, if I try the same thing (ie not setting a Not_Null property), the query is executed and the record is inserted, and the property that shouldn't be null is empty. I think it shouldn't, the query should return an error. Or this option in the schema is useless.

Just a misunderstanding of mandatory / not_null property.
I'm really confused... Sorry.


Include OIDC_CLIENT_SECRETS in documentation

The configuration variable OIDC_CLIENT_SECRETS is not documented here: https://flask-oidc.readthedocs.io/en/latest/ but a very important one for using the framework.

If you want this resolved i'm maintaining a fork of this with some added extensibility. Feel free to open a PR/issue here:

https://github.com/svintit/flask-oidc-ext/pulls