Unable to import sqlite3 without critical compile warnings + runtime error

node-sqlite3 version: 4.0.2 (also attempted 3.1.13)
node version: 10.1.0 (also attempted with 8.8.1)
os and arch: mac os x el capitan 64 bit

I've been trying to get sqlite3 imported into a create-react-app for the past couple days. Any help would be much appreciated. When I initially install and run the app, I get the following compile error:
Failed to compile.

./node_modules/node-pre-gyp/lib/info.js
Module not found: Can't resolve 'aws-sdk'

After I install aws-sdk (either by installing inside ./node_modules/node-pre-gyp or on the project's root), I get the following output in my CLI when I try to run the app:
./node_modules/node-pre-gyp/lib/util/versioning.js
17:20-67 Critical dependency: the request of a dependency is an expression

./node_modules/node-pre-gyp/lib/pre-binding.js
20:22-48 Critical dependency: the request of a dependency is an expression

./node_modules/sqlite3/lib/sqlite3.js
4:14-35 Critical dependency: the request of a dependency is an expression

./node_modules/node-pre-gyp/lib/util/compile.js
Module not found: Can't resolve 'node-gyp' in '/Users/justin/testcode/node_test/test_app/node_modules/node-pre-gyp/lib/util'

./node_modules/node-pre-gyp/lib/util/compile.js
Module not found: Can't resolve 'npm' in '/Users/justin/testcode/node_test/test_app/node_modules/node-pre-gyp/lib/util'

./node_modules/node-pre-gyp/lib/util/nw-pre-gyp/index.html
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type.
| <!doctype html>
| <html>
| <head>

And I get this runtime error:
TypeError: Cannot read property '_handle' of undefined
(anonymous function)
node_modules/set-blocking/index.js:3
  1 | module.exports = function (blocking) {
  2 |   [process.stdout, process.stderr].forEach(function (stream) {
> 3 |     if (stream._handle && stream.isTTY && typeof stream._handle.setBlocking === 'function') {
  4 |       stream._handle.setBlocking(blocking)
  5 |     }
  6 |   })
View compiled
./node_modules/set-blocking/index.js.module.exports
node_modules/set-blocking/index.js:2
  1 | module.exports = function (blocking) {
> 2 |   [process.stdout, process.stderr].forEach(function (stream) {
  3 |     if (stream._handle && stream.isTTY && typeof stream._handle.setBlocking === 'function') {
  4 |       stream._handle.setBlocking(blocking)
  5 |     }
View compiled
(anonymous function)
node_modules/npmlog/log.js:11
   8 | var setBlocking = require('set-blocking')
   9 | var consoleControl = require('console-control-strings')
  10 |
> 11 | setBlocking(true)
  12 | var stream = process.stderr
  13 | Object.defineProperty(log, 'stream', {
  14 |   set: function (newStream) {
View compiled
./node_modules/npmlog/log.js
http://localhost:3000/static/js/bundle.js:72472:30
__webpack_require__
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:678
  675 | };
  676 |
  677 | // Execute the module function
> 678 | modules[moduleId].call(module.exports, module, module.exports, hotCreateRequire(moduleId));
  679 |
  680 | // Flag the module as loaded
  681 | module.l = true;
View compiled
fn
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:88
  85 | 		console.warn("[HMR] unexpected require(" + request + ") from disposed module " + moduleId);
  86 | 		hotCurrentParents = [];
  87 | 	}
> 88 | 	return __webpack_require__(request);
  89 | };
  90 | var ObjectFactory = function ObjectFactory(name) {
  91 | 	return {
View compiled
(anonymous function)
node_modules/node-pre-gyp/lib/node-pre-gyp.js:16
  13 | var fs = require('fs');
  14 | var path = require('path');
  15 | var nopt = require('nopt');
> 16 | var log = require('npmlog');
  17 | log.disableProgress();
  18 | var napi = require('./util/napi.js');
  19 |
View compiled
./node_modules/node-pre-gyp/lib/node-pre-gyp.js
http://localhost:3000/static/js/bundle.js:69853:30
__webpack_require__
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:678
  675 | };
  676 |
  677 | // Execute the module function
> 678 | modules[moduleId].call(module.exports, module, module.exports, hotCreateRequire(moduleId));
  679 |
  680 | // Flag the module as loaded
  681 | module.l = true;
View compiled
fn
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:88
  85 | 		console.warn("[HMR] unexpected require(" + request + ") from disposed module " + moduleId);
  86 | 		hotCurrentParents = [];
  87 | 	}
> 88 | 	return __webpack_require__(request);
  89 | };
  90 | var ObjectFactory = function ObjectFactory(name) {
  91 | 	return {
View compiled
(anonymous function)
node_modules/sqlite3/lib/sqlite3.js:1
> 1 | var binary = require('node-pre-gyp');
  2 | var path = require('path');
  3 | var binding_path = binary.find(path.resolve(path.join(__dirname,'../package.json')));
  4 | var binding = require(binding_path);
View compiled
./node_modules/sqlite3/lib/sqlite3.js
http://localhost:3000/static/js/bundle.js:123571:30
__webpack_require__
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:678
  675 | };
  676 |
  677 | // Execute the module function
> 678 | modules[moduleId].call(module.exports, module, module.exports, hotCreateRequire(moduleId));
  679 |
  680 | // Flag the module as loaded
  681 | module.l = true;
View compiled
fn
/Users/justin/testcode/node_test/test_app/webpack/bootstrap 66935c31b13be3dd3e9e:88
  85 | 		console.warn("[HMR] unexpected require(" + request + ") from disposed module " + moduleId);
  86 | 		hotCurrentParents = [];
  87 | 	}
> 88 | 	return __webpack_require__(request);
  89 | };
  90 | var ObjectFactory = function ObjectFactory(name) {
  91 | 	return {
View compiled
./src/App.js
src/App.js:4
  1 | import React, { Component } from 'react';
  2 | import logo from './logo.svg';
  3 | import './App.css';
> 4 | var sqlite3 = require('sqlite3').verbose();
  5 |
  6 |
  7 | class App extends Component {

I've tried installing from source, installing past versions, using a different node version, and looking into similar issues (#909 , this issue, this issue, and some others) with no luck.
From what I've seen, it appears the issue may stem from how webpack is configured, but my familiarity with webpack is pretty lacking. For reference, create react app automatically configures webpack with this config file.
 You must install peer dependencies yourself.

+<EMAIL_ADDRESS>added 24 packages in 14.92s
npm info ok

I solved it by adding
        externals: {             'sqlite3':'commonjs sqlite3',         }
to the webpack config file

@janglada unfortunately I'm unable to get this to work, but I'm working on it. I saw this solution in issue #698 as well.
When I attempt to add externals: { sqlite3: 'commonjs sqlite3' } to my webpack config file and start the node server via npm start, the server appears to run perfectly fine with no errors in the command line. However, when I open up the browser to interact with the app, I get the following error in the browser console:
external "sqlite3":1 Uncaught ReferenceError: require is not defined
    at Object.sqlite3 (external "sqlite3":1)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object../src/App.js (App.js:4)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object../src/index.js (index.css?f255:26)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object.0 (registerServiceWorker.js:117)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at ./node_modules/ansi-regex/index.js.module.exports (bootstrap c8470ec94022a2bb9e9f:724)
    at bootstrap c8470ec94022a2bb9e9f:724

I could be getting this wrong, but in looking around to understand this issue, it's because when you add externals to the webpack file, it tells webpack to ignore bundling sqlite3 prior to running the app and to load the dependency at run-time. But, that also means sqlite3 won't get loaded within node's execution environment -- the browser attempts to load it. And the browser doesn't have a built-in require function like node does, thus the undefined reference error. I've found some potential solutions to this that I'm currently in the process of exploring

@janglada solution solved my issue

I am having an exact same issue as @j-berman but I am not still able to resolve it. does anyone got any solution/fix ? Below is my error.

[0] Starting the development server...
[0]
[0] Compiled with warnings.
[0]
[0] ./node_modules/sqlite3/lib/sqlite3.js
[0] Critical dependency: the request of a dependency is an expression
[0]
[0] ./node_modules/sqlite3/node_modules/node-pre-gyp/lib/pre-binding.js
[0] Critical dependency: the request of a dependency is an expression
[0]
[0] ./node_modules/sqlite3/node_modules/node-pre-gyp/lib/util/versioning.js
[0] Critical dependency: the request of a dependency is an expression
[0]
[0] ./src/App.js
[0]   Line 19:   'electron_process' is assigned a value but never used  no-unused-vars
[0]   Line 20:   'electron_app' is assigned a value but never used      no-unused-vars
[0]   Line 37:  Expected '===' and instead saw '=='                    eqeqeq
[0]
[0] ./src/Login.js
[0]   Line 5:    'db' is assigned a value but never used                                                                    no-unused-vars
[0]   Line 63:  img elements must have an alt prop, either with meaningful text, or an empty string for decorative images  jsx-a11y/alt-text
[0]
[0] ./node_modules/sqlite3/node_modules/node-pre-gyp/lib/util/compile.js
[0] Module not found: Can't resolve 'npm' in '/Volumes/Example/node_modules/sqlite3/node_modules/node-pre-gyp/lib/util'
[0]
[0] ./node_modules/sqlite3/node_modules/node-pre-gyp/lib/util/nw-pre-gyp/index.html 1:0
[0] Module parse failed: Unexpected token (1:0)
[0] You may need an appropriate loader to handle this file type.
[0] > <!doctype html>
[0] | <html>
[0] | <head>
[0]
[0] Search for the keywords to learn more about each warning.
[0] To ignore, add // eslint-disable-next-line to the line before.
[0]

I think node-pre-gyp requires python 2.7

I already have python 2.7.10 installed

I have the same issue, however, I couldn't solve it. I'm using Angular + Electron, I described my issue here:
https://stackoverflow.com/questions/60363339/using-sqlite-in-an-angular-electron-app-critical-dependency-the-request-of-a
any help would be much appreciated.

I don't think @FrancescoBorzi method works with the most recent angular-electron boilerplate

@TheLazyHatGuy you can add a new answer to my original question :)

@FrancescoBorzi I haven't figured out the answer yet. Tried to apply your suggestion from Stack Overflow but it didn't work

Is there any solution? i'm still having this problem.

I solved it by adding
 externals: { 'sqlite3':'commonjs sqlite3', }
to the webpack config file

Works for me with electron. Buy why?

I really appreciate this more detailed response. I was experiencing the same error with a CRA-based app I'm working on, and now I realize that I will need to shift the sqlite code to a mini-service rather than continuing to try and resolve the error.
Thank you!

@FengYangLiu that makes sense. Unfortunately I've been super busy lately and haven't gotten around to digging much deeper. But, essentially I think the root of this boils down to the sandboxed nature of the browser: the local filesystem isn't inherently available to a web page. I think sqlite3 is designed to run within a node environment with access to the local filesystem (i.e. not from within the browser).

No problem @tim-rohrer :)
Side note, excuse this shameless self-promotion, but I helped make a tool to satisfy my requirements on this and figure it may be useful. I'm planning to release it in the next week. It's end-to-end encrypted sql.js -- an encrypted sql.js database gets loaded from the server and decrypted client-side. All writes to the database are encrypted.
I talked about it a bit here, and made a CRA-based app with it here (can also check the console in that app to see the SQL statements in action)

@tim-rohrer
Here's the end-to-end encrypted sql.js tool I mentioned above! Hope others arriving here may find it useful too:
https://github.com/smallbets/userbase/tree/5b385a68716d28fa989ed70984a22bb73cddfb97/src/userbase-sql.js

@janglada unfortunately I'm unable to get this to work, but I'm working on it. I saw this solution in issue #698 as well.
When I attempt to add externals: { sqlite3: 'commonjs sqlite3' } to my webpack config file and start the node server via npm start, the server appears to run perfectly fine with no errors in the command line. However, when I open up the browser to interact with the app, I get the following error in the browser console:
external "sqlite3":1 Uncaught ReferenceError: require is not defined
    at Object.sqlite3 (external "sqlite3":1)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object../src/App.js (App.js:4)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object../src/index.js (index.css?f255:26)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at fn (bootstrap c8470ec94022a2bb9e9f:88)
    at Object.0 (registerServiceWorker.js:117)
    at __webpack_require__ (bootstrap c8470ec94022a2bb9e9f:678)
    at ./node_modules/ansi-regex/index.js.module.exports (bootstrap c8470ec94022a2bb9e9f:724)
    at bootstrap c8470ec94022a2bb9e9f:724

I could be getting this wrong, but in looking around to understand this issue, it's because when you add externals to the webpack file, it tells webpack to ignore bundling sqlite3 prior to running the app and to load the dependency at run-time. But, that also means sqlite3 won't get loaded within node's execution environment -- the browser attempts to load it. And the browser doesn't have a built-in require function like node does, thus the undefined reference error. I've found some potential solutions to this that I'm currently in the process of exploring

so, do you have a better way to solve this problem, I'm in the same case :(

@eyea
I think this is the main limiting issue:

node-sqlite3 is designed to run within a node environment with access to the local filesystem (i.e. not from within the browser)

And the local filesystem isn't available to JS running in the browser.
But, I did just came across this package called BrowserFS that may help you workaround that. Check out their webpack config. Haven't tried it, I'm not optimistic :/ I bet with some serious hacking this could eventually be made to work, but would be pretty challenging

@eyea
I think this is the main limiting issue:

node-sqlite3 is designed to run within a node environment with access to the local filesystem (i.e. not from within the browser)

And the local filesystem isn't available to JS running in the browser.
But, I did just came across this package called BrowserFS that may help you workaround that. Check out their webpack config. Haven't tried it, I'm not optimistic :/ I bet with some serious hacking this could eventually be made to work, but would be pretty challenging

This https://github.com/mapbox/node-sqlite3/issues/1029#issuecomment-414116796 worked for me.
For those using vue3 cli and they don't have webpack config file - just edit or create vue.config.js file in project root directory and add following:
module.exports = {   configureWebpack: {     externals: {       'sqlite3': 'commonjs sqlite3',     }   } }
Reference: https://stackoverflow.com/a/50304636/4642868


dev: add CFT test cases to verify the source of Cloud Functions

Check source code exists in GCS and HTTP functions

This Pull Request has been included in PR #28.


Post-merge review addressed

Addressing reviewing comments made by @hzxuzhonghu after #10036 got merged.

/lgtm

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu, ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: nmittler
If they are not already assigned, you can assign the PR to them by writing /assign @nmittler in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]
pkg/OWNERS

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

@hzxuzhonghu approved?

I have no permission for /pkg

/assign @ozevren

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: hzxuzhonghu, ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: ozevren
If they are not already assigned, you can assign the PR to them by writing /assign @ozevren in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]
pkg/OWNERS

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

/lgtm
/approve

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

Needs approval from an approver in each of these files:

pilot/OWNERS [hzxuzhonghu]
pkg/OWNERS [ozevren]

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


Allow log events to be emitted with a dynamic log level/severity

Some log events can benefit from their log level being set at run time, but there isn't currently a way to do that. All log events are currently emitted at a level known at compile time, defined by a macro. This is generally a good idea, but not universally.

There's previous discussion on this topic in #9546.
The state of things there is that we're still looking for legitimate use cases for log level definition at runtime. Could provide some examples how you'd like to use this?

I read through #9546 last night after @Sija pointed it out. This seemed like a harmless refactor to me but y'all seem pretty strongly against it.

I don't oppose this change. But it needs justification. That's why I'm asking for use cases.


ImportError: libcudnn.so.8: cannot open shared object file: No such file or directory

Discussed in https://github.com/OpenDevin/OpenDevin/discussions/778

Originally posted by Xxcoincoin April  5, 2024
Hello everyone, I installed OpenDevin on WSL2. I followed the tutorial in LOCAL_LLM_GUIDE.md
So launching in a cuda environment (od)
-make build
-modification of the configuration file
-make run: starts, but error
-make start-backend: not working
I have those errors :
 ab@DESKTOP-6C3GB46:~/OpenDevin$ make run Running the app... /bin/sh: 1: [: unexpected operator make[1]: Entering directory '/home/ab/OpenDevin' Starting backend... make[1]: Entering directory '/home/ab/OpenDevin' Starting frontend... [...] ImportError: libcudnn.so.8: cannot open shared object file: No such file or directory
[...]
8:28:57 PM [vite] ws proxy error:
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /litellm-models
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /default-model
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /litellm-agents
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /litellm-models
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /default-model
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
8:28:57 PM [vite] http proxy error: /litellm-agents
Error: connect ECONNREFUSED <IP_ADDRESS>:3000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16)
`
For the libcudnn error i have installed inside my conda env pip install torch => did not work / same error
Installed cuDNN with the nvidia installer (https://developer.nvidia.com/cudnn-downloads?target_os=Linux&target_arch=x86_64&Distribution=Ubuntu&target_version=22.04&target_type=deb_network) => same error...
I have no clue on what's going on, do you have some ideas ?
Thanks a lot guys !

It should be your environment problem. Search a little about error
ImportError: libcudnn.so.8: cannot open shared object file: No such file or directory

Maybe you can try this or this

What version of Python are you using? I ran into something like this when I accidentally used Python 3.10

I'm going to dedupe this with https://github.com/OpenDevin/OpenDevin/issues/726 since they seem related


I wish /docs/user-guide/pods/multi-container/ not jumping to another section when I click yaml tab

I wish /docs/user-guide/pods/multi-container/ not jumping to another section when I click yaml tab

Fixed. Agreed, strange user behavior.


fix

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 93.245%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
1477

Relevant Lines:
1584

💛  - Coveralls


Wallet can't start on macOS Sierra

I'm trying to open the wallet on macOS Sierra and it works 1/30 times if i do a restart but 99% of the time i can't start it, it becomes unresponsive.
It will stay in the launch bar for about 1-2 minutes then i have to force quit because it will have the "Application not responding" message.
Is there anything i can do to fix this? Thanks,

Not a dev on the project but curious because Apple keeps on shoving the 'upgrade to sierra' on me...have u tried 1) rebooting, 2) verified you have enough memory, 3) verified if enough disk space?

Hi,
Yes i checked all those elements and everything is fine.
I using little snitch but everything is approved and i also tried to stop it while running the wallet app.
I’ve seen this is an app written in javascript, i’m an iOs dev and i’m familiar with UIKit and a few Cocoa apis but not with web technologies used for desktop.
Anyway if there is any info i can provide just let me know.
Regards,
--
Lucian Boboc
iOS Consultant
@lucianboboc

On 25 Dec 2017, at 16:28, gregg dourgarian<EMAIL_ADDRESS>wrote:
Not a dev on the project but curious because Apple keeps on shoving the 'upgrade to sierra' on me...have u tried 1) rebooting, 2) verified you have enough memory, 3) verified if enough disk space?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I have the same problem, on my logs at ==> Logs/cardano-node.log <==. I see
[node.worker.security:ERROR:ThreadId 557] [2017-12-27 11:05:21 CET] self: enqueue instruction EnqueueAll {enqNodeType = NodeRelay, enqMaxAhead = MaxAhead 1, enqPrecedence = PHigh} failed to enqueue message MsgRequestBlockHeaders Nothing to forwarding sets [[]]

Hi guys...also, like many, having intermittent problems with Daedalus on mac (not Sierra).
Just had a situation in which Daedalus was hanging the rest of my system.  Looked suspicious that Daedalus (Haskell?) is causing undetected deadlocks...memory allocation deadlocks.    Rebooting sometimes works i'm because it frees up memory.
As the Cardano blockchain gets longer, memory issues would likely get worse and cause hangs which is what we are seeing here.

Also not opening in El Capitan 10.11.6
`
Process:               cardano-launcher [433]
Path:                  /Applications/Daedalus.app/Contents/MacOS/cardano-launcher
Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes:       0x0000000000000001, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Application Specific Information:
/Applications/Daedalus.app/Contents/MacOS/./librocksdb.5.1.2.dylib
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   librocksdb.5.1.2.dylib        	0x00000001108be87e std::__1::unordered_map<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator >, rocksdb::OptionTypeInfo, std::__1::hash<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::equal_to<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > >, std::__1::allocator<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const, rocksdb::OptionTypeInfo> > >::unordered_map(std::initializer_list<std::__1::pair<std::__1::basic_string<char, std::__1::char_traits, std::__1::allocator > const, rocksdb::OptionTypeInfo> >) + 734
1   librocksdb.5.1.2.dylib        	0x00000001108c996a _GLOBAL__sub_I_column_family.cc + 18186
2   dyld                          	0x00007fff65a7710b ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 265
3   dyld                          	0x00007fff65a77284 ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
4   dyld                          	0x00007fff65a738bd ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 305
5   dyld                          	0x00007fff65a73852 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 198
6   dyld                          	0x00007fff65a73743 ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 127
7   dyld                          	0x00007fff65a739b3 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 75
8   dyld                          	0x00007fff65a660f1 dyld::initializeMainExecutable() + 208
9   dyld                          	0x00007fff65a69d98 dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 3596
10  dyld                          	0x00007fff65a65276 dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 512
11  dyld                          	0x00007fff65a65036 _dyld_start + 54
`


signrawtransaction RPC errors on coldstaking txids

It fails when the wallet is holding the spending key.

Steps to recreate:
listunspent() to find txids with a coldstaking address where the wallet holds the spending key
createrawtransaction [{"txid":"[subject txid]","vout":1}] {"[address1]":[amount1],"[address2]":[amount2]}
signrawtransaction [hash from createrawtransaction]
signrawtransaction will error with "error": "Operation not valid with the current stack size"


Make router and vuex proper packages

What problem does this feature solve?
There's a lot of careful manipulation being done in @vue/cli code because of the above plugins not being proper packages, which we could avoid. Since the implementation of #1202, the format of the above plugins is in a proper plugin format anyway. So, why don't we move them to their own packages in the repo? That way, we could remove all the specialty code written just for these packages.
What does the proposed API look like?
Have 2 new packages @vue/cli-plugin-router, @vue/cli-plugin-vuex

I'm reluctant to add two new generator-only plugins.
Even if we do, we should not mess up users' package.jsons; co-existence of @vue/cli-plugin-vuex and vuex would definitely confuse them.
So we'll still need to add some special logic to remove the plugins after generating the necessary files. Does that worth the refactoring?

So we'll still need to add some special logic to remove the plugins after generating the necessary files. Does that worth the refactoring?

I think yes, because right now the generation is not very consistent and also having these as internal options in cli-service generator is messing with other 3rd party plugins when they are doing this

co-existence of @vue/cli-plugin-vuex and vuex would definitely confuse them.

I actually have no issue about this as an end-user if the cli-plugin-vuex has more helpful commands (like maybe generating a store module etc..)

I actually have no issue about this as an end-user if the cli-plugin-vuex has more helpful commands (like maybe generating a store module etc..)

Yeah, definitely worth it if such features implemented.
It's been on my backlog for a while actually. Just haven't got the time to think about the design.

I will work on this and send a PR for the initial packages. Then we can discuss on the features to be implemented. I am always up for a chat on discord if you need someone to brainstorm with.

😀Cool, much appreciated.


Fixed battery sizing equations to reference computed bank power rather than desired bank power and capacity

-Sets correct battery bank capacity and bank power basis for maximum discharge and charge calculations on both AC and DC connected systems for AC and DC battery sizing options
-Changes * dc_ac efficiency to / ac_dc efficiency for Bank power maximum charge AC calculations when AC connected

Here are a set of diagrams and screenshots showing how the calculations are expected to work:
battery-power-calculations.zip

@dguittet If you have a chance, could you review this pull request? I'd like to have this merged into patch before I start my work reorganizing the battery UI inputs.
Thanks!
Paul.

Looks good! Sorry for the delay.

See #580 for merged changes, this branch has messed up root branches. Closing this PR


Load Data Sets Too Slow In Train Seq2seq Model

Describe the bug
step 'Generating train split' in load_dataset is too slow：

Steps to reproduce the bug
Data： own data，16K16B Mono wav
Oficial Script: run_speech_recognition_seq2seq.py
Add Code：
if data_args.data_path is not None:
print(data_args.data_path)
raw_datasets = load_dataset("audiofolder", data_dir=data_args.data_path, cache_dir=model_args.cache_dir)
raw_datasets = raw_datasets.cast_column("audio", Audio(sampling_rate=16000))
raw_datasets = raw_datasets["train"].train_test_split(test_size=0.005, shuffle=True)
（change cache_dir to other path ，ex:/DATA/cache）
Expected behavior
load data fast,at least 1000+
Generating train split: 387875 examples [32:24:45, 1154.83 examples/s]
Environment info

transformers version: 4.28.0.dev0
Platform: Linux-5.4.0-149-generic-x86_64-with-debian-bullseye-sid
Python version: 3.7.16
Huggingface_hub version: 0.13.2
PyTorch version (GPU?): 1.13.1+cu116 (True)
Tensorflow version (GPU?): not installed (NA)
Flax version (CPU?/GPU?/TPU?): not installed (NA)
Jax version: not installed
JaxLib version: not installed
Using GPU in script?:
Using distributed or parallel set-up in script?:

Hi ! you can speed it up using multiprocessing by passing num_proc= to load_dataset()

already did，but not useful for step Generating train split，it works in step "Resolving data files" & "Downloading data files"

I met the same problem,  terrible  experience

@mariosasko

We need more info about the issue to provide help.
Can you interrupt the process (with num_proc=None) after the load_dataset call when the slowdown occurs? So we can know what part of the code is causing it.
The audiofolder \ imagefolder with metadata is not performant for large datasets. We can make them much faster if drop the nested metadata files feature (not that useful). I plan to work on this soon.
In the meantime, it's better to use Dataset.from_generator (requires replacing the load_dataset calls in the transformers script with Dataset.from_generator) or write a dataset loading script for large datasets.

Can you interrupt the process (with num_proc=None) after the load_dataset call when the slowdown occurs? So we can know what part of the code is causing it.
（I'll try this operation）
The audiofolder \ imagefolder with metadata is not performant for large datasets. Luckily, we can make them much faster if drop the nested metadata files feature (not that useful). I plan to work on this soon.
(My data is indeed a bit large, exceeding 10000 hours of audio data. Looking forward to your improvement work very much)
In the meantime, it's better to use Dataset.from_generator (requires replacing the load_dataset calls in the transformers script with Dataset.from_generator) or write a dataset loading script for large datasets.
（I want to use Dataset.from_generator instead of  load_dataset ，where can i found sample code to load audio&label dataset， I was to do asr task）

Can you interrupt the process (with num_proc=None) after the load_dataset call when the slowdown occurs? So we can know what part of the code is causing it.
Here is the log：
load_dataset.log
（The larger my training data, the slower it loads）

In the meantime, it's better to use Dataset.from_generator (requires replacing the load_dataset calls in the transformers script with Dataset.from_generator) or write a dataset loading script for large datasets.
I tried ‘Dataset. from_generator’ implements data loading, but the testing results show no improvement

I have already solved this problem, referring to #5990 : read audio frist, then use data_generator to change format .


Calendar

As a user
I want a calendar
to have an overview of my date

ac

[ ] there is a calendar on the page
[ ] the calendar is big and above the page

tasks

[ ] create a branch
[ ] create a calendar
[ ] position the calendar on the page

Very short and clear! perfect! :)


Enforce UTF-8 in subject header

This PR explicitely encodes subject headers as UTF-8 over base64 (RFC 1342). This fixes cases where mail servers guess a wrong encoding of subjects like Umlaut test für; some servers rendered  fÃ¼r instead of für.
This probably should be applied to other headers as well, see #304.

There were the following issues with your Pull Request

Commit: 8869130b6d32f4bb34cf91c6128a28b40d012194
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Codecov Report

Merging #315 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #315   +/-   ##
=======================================
  Coverage   90.68%   90.68%
=======================================
  Files           8        8
  Lines         794      794
=======================================
  Hits          720      720
  Misses         74       74

Continue to review full report at Codecov.

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

There were the following issues with your Pull Request

Commit: 8869130b6d32f4bb34cf91c6128a28b40d012194
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Any progress on this?

The fix for the subject header is implemented and can be merged, though I'm waiting for feedback if the fix should be extended to other headers as well.

IMHO it should be done in rust-email.

@amousset That would make sense, but this leaves us with a problem in lettre's API-design: many functions take strings as parameters. Since all Strings in Rust are UTF-8 encoded, functions taking strings are supposed be able to handle any valid UTF-8 byte sequence. This implies UTF-8 encoded headers.
We could make all functions take byte slices instead of strings, which would make it clear that there are no guarantees for unicode working.

There were the following issues with your Pull Request

Commit: 8869130b6d32f4bb34cf91c6128a28b40d012194
Commits must be in the following format: %{type}(%{scope}): %{description}

Guidelines are available at https://github.com/lettre/lettre/blob/master/CONTRIBUTING.md

This message was auto-generated by https://gitcop.com

Thanks! Replaced by #383.


Feature Request: Twitter Handle from Twitter Profile URL

Could you add a feature to extract twitter handles from a twitter url?

This library's focus is to parse text within a tweet and identify linkable components (mentions, hashtags, urls, cashtags). @stevendelarwelle, could you elaborate your request with maybe an example or 2?

for instance you have the url http://www.twitter.com/username
return username

Before adding new features to a library, I like to figure out a few questions:

Why should we add that feature to this specific library?
Does it belong here?
What current problem/bug does it solve?

It's nice to keep libraries as small and focused as possible. If you or someone else can make a case for it, I'm listening and accepting pull requests :)

So the users of the library with a list of user profiles can extract the usernames and tweet at them.
Yes, it's the exact same thing you're doing with the text of the tweet.
It solves the problem of writing extra code to get the username and using this library to tweet at somebody from an application or creating tweet links if you have a list of twitter profiles.

Hi,
We don't want to add rarely used things to this library to keep it compact.
It is already too big, IMO.

When do people obtain a list of profile urls as opposed to screen names?
I'm curious where you are getting those from.
It's not the exact same thing. A Twitter profile URL is not identified
inside of twitter text. What twitter text identifies is a valid screen name
preceded by @ and having the proper edge cases. It also identifies a valid
General URLs for linking, but does not special case profile urls.
Your use case seems application-specific, and could done in one line of
code:

// Returns the screen name of the profile url, or empty string if the
profile url is invalid
function screenNameFromTwitterProfileUrl(profileUrl) {
return profileUrl.replace(/^https?://twitter.com/(\w{1,15})$|.*/,
'$1');
}
Is that helpful?

Tom

On Jan 12, 2017 6:10 PM, "Steve Delarwelle"<EMAIL_ADDRESS>wrote:

So the users of the library with a list of user profiles can
extract the usernames and tweet at them.
Yes, it's the exact same thing you're doing with the text of the
tweet.
It solves the problem of writing extra code to get the username and
using this library to tweet at somebody from an application or creating
tweet links if you have a list of twitter profiles.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/twitter/twitter-text/issues/163#issuecomment-272342403,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACKBPOBmtS3AfePeAyyR1QLGHFey6RHks5rRt0fgaJpZM4Libec
.


Take Screenshots Crashs with waitForUI5 of undefined

Hello,
we want to use WDI5 for our tests with Cucumber. For this we have built a relatively simple test setup. First the launchpad is started and then the app is to be loaded.
This works fine locally. Unfortunately, in the pipeline the app is not loaded and therefore the browser title does not change. To better analyze the problem we wanted to try the screenshot function of WDI5. Unfortunately, this immediately crashes with the following error. The screenshot function is locally and in the pipeline not working.
Why? What are we doing wrong?
Thanks and best regards
Nils
Error log:
2021-04-07T10:23:22.556Z DEBUG @wdio/utils:initialiseServices: initialise service "ui5" as NPM package
2021-04-07T10:23:22.567Z INFO @wdio/cli:launcher: Run onPrepare hook
2021-04-07T10:23:22.568Z DEBUG @wdio/cli:utils: Finished to run "onPrepare" hook in 0ms
2021-04-07T10:23:22.569Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2021-04-07T10:23:22.569Z DEBUG @wdio/cli:utils: Finished to run "onWorkerStart" hook in 0ms
2021-04-07T10:23:22.570Z INFO @wdio/local-runner: Start worker 0-0 with arg:
[0-0] 2021-04-07T10:23:23.315Z INFO @wdio/local-runner: Run worker command: run
[0-0] 2021-04-07T10:23:23.534Z DEBUG @wdio/config:utils: Found 'ts-node' package, auto-compiling TypeScript files
[0-0] 2021-04-07T10:23:23.537Z DEBUG @wdio/local-runner:utils: init remote session
[0-0] 2021-04-07T10:23:23.543Z DEBUG @wdio/utils:initialiseServices: initialise service "ui5" as NPM package

.....

[0-0] 2021-04-07T10:23:30.344Z DEBUG @wdio/local-runner:utils: init remote session
[0-0] 2021-04-07T10:23:30.345Z INFO devtools:puppeteer: Initiate new session using the DevTools protocol
[0-0] 2021-04-07T10:23:30.346Z INFO devtools: Launch Google Chrome with flags: --enable-automation --disable-popup-blocking --disable-extensions --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-sync --metrics-recording-only --disable-default-apps --mute-audio --no-first-run --no-default-browser-check --disable-hang-monitor --disable-prompt-on-repost --disable-client-side-phishing-detection --password-store=basic --use-mock-keychain --disable-component-extensions-with-background-pages --disable-breakpad --disable-dev-shm-usage --disable-ipc-flooding-protection --disable-renderer-backgrounding --force-fieldtrials=*BackgroundTracing/default/ --enable-features=NetworkService,NetworkServiceInProcess --disable-features=site-per-process,TranslateUI,BlinkGenPropertyTrees --window-position=0,0 --window-size=1200,900 --headless --disable-gpu --no-sandbox --disable-dev-shm-usage --disable-browser-side-navigation --window-size=1920,1080
[0-0] 2021-04-07T10:23:30.911Z INFO devtools: Connect Puppeteer with browser on port 50172
[0-0] open url with fallback (this is not causing any issues since its is removed for navigation): #
[0-0] 2021-04-07T10:23:31.113Z INFO devtools: COMMAND navigateTo("http://localhost:3000/#")
[0-0] 2021-04-07T10:23:34.190Z INFO devtools: RESULT null
[0-0] wdio-ui5-service before hook
[0-0] creating internal control map
[0-0] 2021-04-07T10:23:34.194Z INFO devtools: COMMAND executeAsyncScript("return ((done) => {
                setTimeout(() => {
                    if (document.location.href != 'data:,') {
                        // make sure we are not on the initial page
                        done(document.readyState);
                    }
                }, 400);
            }).apply(null, arguments)", <object>)
[0-0] 2021-04-07T10:23:35.114Z INFO devtools: RESULT complete
[0-0] 2021-04-07T10:23:35.151Z INFO devtools: COMMAND executeScript("return (() => {
        // browser context - you may not access client or console
        return !!window.sap;
    }).apply(null, arguments)", <object>)
[0-0] 2021-04-07T10:23:35.168Z INFO devtools: RESULT true
[0-0] sucessfully initialized wdio-ui5 bridge
[0-0] 2021-04-07T10:23:35.170Z DEBUG @wdio/sync: Finished to run "before" hook in 4061ms

.....

[0-0] 2021-04-07T10:23:49.312Z INFO webdriver: COMMAND screenshot("some-id")
[0-0] 2021-04-07T10:23:49.317Z INFO devtools: COMMAND executeAsyncScript("return ((done) => {
            window.bridge
                .waitForUI5()
                .then(() => {
                    window.wdi5.Log.info('[browser wdi5] UI5 is ready');
                    done(true);
                })
                .catch((error) => {
                    console.error(error);
                });
        }).apply(null, arguments)", <object>)
[0-0] Error in "0: die App geladen ist"
waitUntil condition failed with the following reason: Evaluation failed: TypeError: Cannot read property 'waitForUI5' of undefined
    at eval (eval at <anonymous> (:20:16), <anonymous>:3:18)
    at eval (eval at <anonymous> (:20:16), <anonymous>:11:12)
    at __puppeteer_evaluation_script__:20:16
    at new Promise (<anonymous>)
    at __puppeteer_evaluation_script__:2:12
Error: waitUntil condition failed with the following reason: Evaluation failed: TypeError: Cannot read property 'waitForUI5' of undefined
    at eval (eval at <anonymous> (:20:16), <anonymous>:3:18)
    at eval (eval at <anonymous> (:20:16), <anonymous>:11:12)
    at __puppeteer_evaluation_script__:20:16
    at __puppeteer_evaluation_script__:2:12
    at /..../node_modules/webdriverio/src/commands/browser/waitUntil.ts:79:15
    at World.<anonymous>

Our wdio.conf.js is the following:
const dynamicConfig = {};

if (process.env.CI) {
    dynamicConfig.port = 9515;
    dynamicConfig.path = '/';
    dynamicConfig.services = ["chromedriver", "ui5"];
} else {
    dynamicConfig.automationProtocol = "devtools";
    dynamicConfig.services = ["ui5"];
}

exports.config = Object.assign({},{

    runner: 'local',

    specs: [
        './features/**/*.feature'
    ],

    maxInstances: 1,
    capabilities: [{
        browserName: 'chrome',
        'goog:chromeOptions': {
            args: ['--headless', '--disable-gpu',
                   '--no-sandbox', '--disable-dev-shm-usage',
                   '--disable-browser-side-navigation', '--window-size=1920,1080']
        },
        acceptInsecureCerts: true
    }],

    bail: 0,

    baseUrl: 'http://localhost:3000/',

    waitforTimeout: 10000,

    connectionRetryTimeout: 120000,

    connectionRetryCount: 3,

    framework: 'cucumber',
    reporters: ['spec',
        ['junit', {
            outputDir: "./0_wdioTestResults",
            outputFileFormat: function (options) {
                return `results-${options.cid}.xml`;
            }
        }]
    ],

    cucumberOpts: {
        // <string[]> (file/dir) require files before executing features
        require: ['./webapp/test/steps/**/*.js'],
        // <boolean> show full backtrace for errors
        backtrace: true,
        // <string[]> ("extension:module") require files with the given EXTENSION after requiring MODULE (repeatable)
        requireModule: [],
        // <boolean> invoke formatters without executing steps
        dryRun: false,
        // <boolean> abort the run on first failure
        failFast: false,
        // <string[]> (type[:path]) specify the output format, optionally supply PATH to redirect formatter output (repeatable)
        format: ['pretty'],
        // <boolean> hide step definition snippets for pending steps
        snippets: true,
        // <boolean> hide source uris
        source: true,
        // <string[]> (name) specify the profile to use
        profile: [],
        // <boolean> fail if there are any undefined or pending steps
        strict: false,
        // <string> (expression) only execute the features or scenarios with tags matching the expression
        tagExpression: '',
        // <number> timeout for step definitions
        timeout: 60000,
        // <boolean> Enable this config to treat undefined definitions as warnings.
        ignoreUndefinedDefinitions: false
    },

    wdi5: {
        screenshotPath: './screenshots/', // [optional] using the project root
        screenshotsDisabled: false,
        logLevel: 'trace',
        platform: 'browser', // [mandatory] browser | android | ios | electron
        url: '', // [mandatory, not empty] path to your bootstrap html file. If your server autoredirects to a 'domain:port/' like root url use empty string ''
        deviceType: 'web', // [mandatory] native | web
        skipInjectUI5OnStart: false // [optional] true when UI5 is not on the start page, you need to later call <wdioUI5service>.injectUI5(); manually
    },

    beforeSession: function (config, capabilities, specs) {
        //Start Testserver
    },

    beforeFeature: function (uri, feature, scenarios) {
        browser.url("/");
        const pageTitle = browser.getTitle();
        if (pageTitle !== 'sLokales Launchpad') {
            console.error(`Fiori Launchpad is not up, found ${pageTitle}`);
            console.log(browser.getPageSource());
            process.exit(1);
        }
    },
    afterSession: function (config, capabilities, specs) {
        //Kill Testserver
    }
}, dynamicConfig);

The step implementation the following:
const { Given, When, Then } = require('@cucumber/cucumber');

Given(/Ich starte die App/, function() {
    browser.url("#MyFioriObject-display");
    browser.refresh();
});

When(/die App geladen ist/, function() {
    browser.waitUntil( () => {
        browser.screenshot('some-id');
        return browser.getTitle() === "MyAppName";

quick guesstimate: in your test, Given seems to refresh the browser -> so you'd need to re-inject wdi5 again like
// only requiring the service for late inject/init
const _ui5Service = require('wdio-ui5-service').default;
const ui5Service = new _ui5Service();

Given(/Ich starte die App/, function() {
    browser.url("#MyFioriObject-display");
    browser.refresh();
});

When(/die App geladen ist/, function() {
     //  (might work here as well, not sure)
    // ui5Service.injectUI5();
    browser.waitUntil( () => {
        //  re-inject after browser.refresh
        ui5Service.injectUI5();
        browser.screenshot('some-id');
        return browser.getTitle() === "MyAppName";

hth, v.

Hi Nils,
can you please confirm you open a valid url with index file. See wdi5 your empty config parameter url.
url: '', // [mandatory, not empty] path to your bootstrap html file. If your server autoredirects to a 'domain:port/' like root url use empty string ''
For easier issue identification remove the --headless parameter from chrome startup options.

Hi Nils,
can you please confirm you open a valid url with index file. See wdi5 your empty config parameter url.
url: '', // [mandatory, not empty] path to your bootstrap html file. If your server autoredirects to a 'domain:port/' like root url use empty string ''
For easier issue identification remove the --headless parameter from chrome startup options.

haha, "erster" :)

Hallo zusammen,
da können wir ja auf Deutsch weiter machen, wenn es für euch passt 👍
Auf localhost:3000 wird das Launchpad gestartet. Vom Prinzip her dasselbe wie beim UI5-Tooling über UI5 Serve nur halt auf Port 3000. Sprich da kommt ein Launchpad.
Headless habe ich entfernt. Sieht alles normal aus und lokal navigiert der ja auch. Das refresh hab ich extra mal weggenommen. Ändert leider am Verhalten nichts.
Viele Grüße
Nils

just a notice: let's switch back to English. As this might be of interest to other non-German speakers running into a similar problem

just a hunch: any reason why you're wrapping the browser.screenshot(...) into a browser.waitUntil()?
wdi5 uses the same sync approach in coding as wdio, so you  could just do
When(/die App geladen ist/, function() {
        browser.screenshot('some-id');
        expect(browser.getTitle()).toStrictEqual("MyAppName");
}

Hi @vobu
yes. The reason is that I want to wait until the Page is loaded. This needs some time until the Navigation from Launchpad to App is done and the App is fully loaded.
Regards,
Nils

Seems like the framework initialisation fails. (Note to myself: "improve error handling"). The window.bridge should contain sap.ui.test.RecordReplay (https://openui5.hana.ondemand.com/api/sap.ui.test.RecordReplay) which is required. Can you please check e.g. network traffic if RecordReplay is required with errors.

Thanks for your answer! I think I have found the error.
If I don't navigate or navigate only with browser.goTo, taking screenshots works in principle but I get the following error. I already had an issue about this in another context open with you. This is the ticket
If I use browser.url on the other hand the whole WDI5 context is lost. Then I use browser.goTo. This is no problem. Maybe you should only document it.
Unfortunately the SAP UI5 error remains.
This is the error:
[0-0] Error in "0: Ich starte die App"
Evaluation failed: Error: sap.ui.test.autowaiter._autoWaiterAsync#extendConfig - No 'inputToValidate' given but it is a mandatory parameter
    at _validate (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/_ParameterValidator.js?eval:6:509)
    at _.validate (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/_ParameterValidator.js?eval:6:371)
    at v (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/autowaiter/_autoWaiterAsync.js?eval:6:1253)
    at Object.e [as extendConfig] (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/autowaiter/_autoWaiterAsync.js?eval:6:466)
    at Function.R.waitForUI5 (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/RecordReplay.js?eval:6:1935)
    at eval (eval at <anonymous> (:20:16), <anonymous>:3:18)
    at eval (eval at <anonymous> (:20:16), <anonymous>:11:12)
    at __puppeteer_evaluation_script__:20:16
    at new Promise (<anonymous>)
    at __puppeteer_evaluation_script__:2:12
Evaluation failed: Error: sap.ui.test.autowaiter._autoWaiterAsync#extendConfig - No 'inputToValidate' given but it is a mandatory parameter
    at _validate (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/_ParameterValidator.js?eval:6:509)
    at _.validate (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/_ParameterValidator.js?eval:6:371)
    at v (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/autowaiter/_autoWaiterAsync.js?eval:6:1253)
    at Object.e [as extendConfig] (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/autowaiter/_autoWaiterAsync.js?eval:6:466)
    at Function.R.waitForUI5 (https://sapui5.hana.ondemand.com/1.60.31/resources/sap/ui/test/RecordReplay.js?eval:6:1935)
    at eval (eval at <anonymous> (:20:16), <anonymous>:3:18)
    at eval (eval at <anonymous> (:20:16), <anonymous>:11:12)
    at __puppeteer_evaluation_script__:20:16
    at __puppeteer_evaluation_script__:2:12
Error: Evaluation failed: Error: sap.ui.test.autowaiter._autoWaiterAsync#extendConfig - No 'inputToValidate' given but it is a mandatory parameter
    at ExecutionContext._evaluateInternal i/node_modules/puppeteer-core/src/common/ExecutionContext.ts:273:13)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at ExecutionContext.evaluate /node_modules/puppeteer-core/src/common/ExecutionContext.ts:138:12)
    at ElementHandle.evaluate (node_modules/puppeteer-core/src/common/JSHandle.ts:159:12)
    at ElementHandle.$eval (node_modules/puppeteer-core/src/common/JSHandle.ts:820:20)
    at DevToolsDriver.executeAsyncScript (/node_modules/devtools/src/commands/executeAsyncScript.ts:34:20)
    at Browser.wrappedCommand (node_modules/devtools/src/devtoolsdriver.ts:103:26)
    at _checkForUI5Ready (node_modules/wdio-ui5-service/src/lib/wdioUi5-index.js:517:33)

Hi Volker,
Why Closed? The Error is still there.
Regards,
Nils

Hi, in ui5 version 1.60.* some test features work differently than in ^1.80.* Can you please check with a more recent UI5 version.

Yes as mentioned before. This is the ticket form February this year on this repository: https://github.com/js-soft/wdi5/issues/73
This is an bug. There was a bug in the selector but @vobu fixed them. The same bug now occurs in the screen recorder.
The problem is our company uses currently version 1.60.31 and later this year 1.71.25 as 1.71.25 is the latest release for FES on Prem. This two versions have both the same issue.


[Airbrake] [Staging] No such file or directory @ rb_file_s_mtime - /var/www/etmoses/releases/20160418082917/tmp/networks/staging/490/feature/electricity/49a08c0e397826d795e50f9a6a16b08f35708bd965875a2b22d9bb1db5e25bc6.load.current_week.tmp

Airbrake error: #8684
Airbrake project: ETMoses
Error type: Errno::ENOENT
Error message: No such file or directory @ rb_file_s_mtime - /var/www/etmoses/releases/20160418082917/tmp/networks/staging/490/feature/electricity/49a08c0e397826d795e50f9a6a16b08f35708bd965875a2b22d9bb1db5e25bc6.load.current_week.tmp
Where: testing_grounds#data
Occurred at: Apr 18, 2016 11:52:07 UTC
First seen at: Apr 18, 2016 11:52:07 UTC
Occurrences: 1 (1 since last deploy on Apr 18, 2016 08:29:35 UTC)
URL: https://beta-moses.energytransitionmodel.com/testing_grounds/490/data.json
File: [PROJECT_ROOT]/app/services/network_cache/validator.rb
Backtrace:
[PROJECT_ROOT]/app/services/network_cache/validator.rb:43:in mtime
[PROJECT_ROOT]/app/services/network_cache/validator.rb:43:in block (2 levels) in cache_time
[PROJECT_ROOT]/app/services/network_cache/validator.rb:42:in map
[PROJECT_ROOT]/app/services/network_cache/validator.rb:42:in block in cache_time

Closing due to duplicate: #1028


Feature Request: allow toggling between the default behaviour and this plugin's behaviour

Checklist

[X] I have read the README.
[X] The feature would be useful to more users than just me.

Feature Requested
while the endhints greatly improve the process of writing code (since they get out of the way), sometimes reading is easier when the inlay hints are in their original position. it would be nice if there was a way to toggle between the original behaviour and this plugin's behaviour.
i've tried my hand at a sketch of the solution here: https://github.com/vxpm/nvim-lsp-endhints. it probably has uncovered edge cases, but it works as a proof of concept.
Relevant Screenshot
No response

Feel free to make a PR?

you mean as is? if that's what you want, sure. but my lua/neovim api skills are very basic and i'm not sure what i've written is bug-free or even the right way to go about it - that's why i didn't open a pr.

The reason is simply that a PR results in a diff of your fork with the repo so I can have a look. Just by linking your fork I have no idea what you've done.

the fork is a single commit ahead of this repo, but that's my fault - i should have linked the commit. i'll open a pr then.

Oh my bad, haven't checked out the fork, that is just a commit.
Nonetheless, a PR is still helpful for discussion, since you can comment on specific sections of code more easily.
Let's continue at the PR

closed by #7


[Extensibility Enhancement] Report 292 "Copy Sales Document" OnPreReportOnBeforeCopySalesDoc event

Please could you add extra parameters to the OnPreReportOnBeforeCopySalesDoc event in Report 292 "Copy Sales Document" for the following...
* DocType
* DocNo
* SalesHeader

This is to enable us to identify which documents are being copied from/to

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Extend S3DynamoDbLogStore to allow for use with localstack

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

This extends #2408 to allow for subclasses to override getClient(), but also allows AWS_ENDPOINT_URL overrides for the DynamoDb client. We require this in delta-rs so that we can run integration tests of S3DynamoDbLogStore with a localstack container
How was this patch tested?

:shrug: I mean I ran some sbt targets :smile:
Does this PR introduce any user-facing changes?

Few questiosn about the SDK change.

The SDK changes are from #2408 which might better address the question. Aside from the v1 of the SDK being deprecated this year, there are newer APIs which only exist in version 2 that I require.

Next, if the goal is "We require this in delta-rs so that we can run integration tests of S3DynamoDbLogStore with a localstack container" ... can't you test this with delta-rs? build/sbt storageS3DynamoDB/publishM2 and test it with delta-rs?

v1 of the SDK doesn't allow for clean overriding of the DynamoDB endpoint URL the way that v2 does. I don't know if you're suggesting that we fork Delta/Spark just to do integration testing in our CI for delta-rs, or suggesting a one-time integration test here.  :confused:
Anywho, I see this change (in some form, I'm dispassionate about my PR specifically) would also allow Delta/Spark to actually run integration tests like this in CI, since right now I don't believe there is any automated acceptance/integration testing from change to change of S3DynamoDbLogStore

➕ to @rtyler 's PR here, since AWS's Java SDK doesn't support any of the other mechanisms for overriding the AWS endpoint (environment variables, system properties, etc. are all still not supported :( https://docs.aws.amazon.com/sdkref/latest/guide/feature-ss-endpoints.html), the only way to do integration tests with something like localstack is to allow overriding the getClient() method here.

@scottsand-db @rtyler FWIW, this PR has finally been approved which should add support for overriding the endpoint_url via environment variables! https://github.com/aws/aws-sdk-java-v2/pull/5562


Confusing dialogue interaction

After adding a file to be uploaded in assignment submission, and attempting to close the window, the following window appears:

Clicking 'Stay' results in no upload, clicking 'Leave' results in the file being uploaded.
Unsure if this is the intended behaviour, but it's a little bit confusing at least.

Thanks for reporting this, @GohNicho!


Error: syntax error on line 129, col 35

Fix this:
==> default: Error: syntax error on line 129, col 35: `                                  ]' at /tmp/vagrant-puppet/manifests-47361b918842096e6dcad883d3f4924f/site.pp:5 on node localhost.home

The error was related to bad YAML syntax, even though it passed yamllint test. Oh well


Is residue layer considered together as the reflective layer?

Thank you for your excellent research. I am not sure how to interpret the residue layer.
Can I interpret the residue layer as a reflective layer that did not follow the linear assumption and is included in the broadly defined reflective layer?

Thank you for your thoughtful question. In our paper, we consider the residue layer as a third component distinct from both the reflective and transmissive layers. Visually, it can be seen as the coupling between the reflective and transmissive layers. When this residue layer is assigned to either of the two components, it causes a deviation from the ideal ground truth for both.

Thank you for your answer. I will consider the importance of the linear assumption a bit more.


Input translated protein sequences?

Hi,
Just trying out compleasm for the first time. It successfully ran to completion when my input was a transcriptome assembly with nucleotide sequences. However, when I tried running compleasm with an input transcriptome with translated protein sequences the analysis failed. Similar to https://github.com/huangnengCSU/compleasm/issues/12, I got the following:
Traceback (most recent call last):
  File "/home/cfos/miniconda3/envs/compleasm/bin/compleasm", line 10, in <module>
    sys.exit(main())
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/compleasm.py", line 2534, in main
    args.func(args)
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/compleasm.py", line 2376, in analyze
    ar.Run()
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/compleasm.py", line 1158, in Run
    self.Run_busco_mode()
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/compleasm.py", line 1234, in Run_busco_mode
    filtered_species = records_df["Target_species"].unique()
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/pandas/core/frame.py", line 3458, in __getitem__
    indexer = self.columns.get_loc(key)
  File "/home/cfos/miniconda3/envs/compleasm/lib/python3.7/site-packages/pandas/core/indexes/base.py", line 3363, in get_loc
    raise KeyError(key) from err
KeyError: 'Target_species'

Is there a 'proteins' mode like in BUSCO (-m proteins)? Or should compleasm always use a nucelotide input?
Thanks

Great, thanks for the quick reply.


Cube cross section tests fail because cross section has white stripes

The entire object is not recognised?

No longer an issue


Files block in module metadata file is not (well) ordered.

Current Behavior
When doing what should be a pure-refactor change, we see a change in the order of entries in the files [ block in the .module metadata file.
Also, VariantFiles.filesOf is a Set, though the current implementation happens to be an ordered subtype.
The gradle module metadata spec says a files block is an "array".
Expected Behavior
Gradle builds are 100% reproducible and not fragile to configuration ordering.
Alternatively, the maven-publish plugin should register files in a more consistent order.
Also, all outputs of gradle builds should be ordered types, by API guarantee and not just implementation. Right now, a hashset implementation could be permitted by API but could break gradle build reproducibility.
The gradle module metadata spec and relevant gradle APIs should match better.
Context (optional)
The change where we observe this is a migration from one version of the Android Gradle Plugin to another. A lot happens under the hood here.
The code on our side where we add additional files is
libraryAndroidComponentsExtension.onVariants { variant ->
if (variant.buildType == DEFAULT_PUBLISH_CONFIG) {
...
configurations.configureEach { config ->
        if (config.name in publishingVariants) {
            // Register the sample source jar as an outgoing artifact of the publishing variant
            config.outgoing.artifact(copySampleJarTask.flatMap { it.destinationJar })

In our plugin's apply { block.
I don't think anything is happening here that might affect the order of plugin application. The other file (normal output jar) is registered by maven-publish afaik, and likely attached to the creation of these publishing configuration and variants.
Separately, from an API standpoint, reproducible builds require a non-unordered set from filesOf, and the use of a set does not coincide with the metadata spec document.
If the order here does not matter because a consuming gradle will always resolve all files in this block into an unordered set, then the simplest way to ensure reproducible builds here would be to sort the files blocks before writing them.
Related: https://github.com/gradle/gradle/issues/20011
Self-contained Reproducer Project
I think this is an API problem in gradle, evident from looking at source and spec.
If the order of files in the files blocks is supposed to matter, there is likely a separate bug on AGP. If it does not matter, files blocks should be sorted for reproducibility.
Gradle version
8.10.2
Build scan URL (optional)
No response
Your Environment (optional)
No response

The issue is in the backlog of the relevant team and is prioritized by them.


Add jump targets for each config option individually

Sometimes I want to direct people to a specific .coveragerc setting, but there is no anchor.  Add jump targets to each setting.

They had jump targets, but since they weren't headings, there was no way to easily use them in the HTML.  Now every setting is an h3 tag: 361e831059923066c666d1eb35884ddebb70ca30


How to disable multiple tag selection?

How to disable multiple tag selection?I want to select only one tag at a time.

func tagPressed(_ title: String, tagView: TagView, sender: TagListView) {
sender.tagViews.forEach {$0.isSelected = false}
tagView.isSelected = !tagView.isSelected
}


Bug: No timeout for I2C_MODE_BLOCKING

Product: (OC-SDR, OC-LTE, OC-LTE, OC-Power, others)
OC-SDR
Component: (PSU, GBC, BBU, FEM, LED, ME)
GBC/PSU/SDR/FE/SYNC
Category: (Hardware, Software/stack, Firmware/bootloader, Documentation)
Firmware/OCWare
Describe the issue found
Currently, I2C is implemented as I2C_MODE_BLOCKING and do not have any timeout!. This is known issues with TI-RTOS (See: https://e2e.ti.com/support/embedded/tirtos/f/355/t/490300)
Alternate to this is have I2C transaction as non-blocking, by changing the I2C mode to be I2C_MODE_CALLBACK, and have proper callback handling. Note the I2C_Transaction will persists until the transfer function is completed.
Defaults values are: transferMode = I2C_MODE_BLOCKING transferCallbackFxn = NULL bitRate = I2C_100kHz
See I2C_transfer documentation at: http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/2_20_00_06/exports/tirtos_full_2_20_00_06/products/tidrivers_full_2_20_00_08/docs/doxygen/html/_i2_c_8h.html#ae1aa99e1fee4517406018e10025cca0e
Please provide all necessary steps to reproduce the issue

[Originally commented by @markhor ]
I2C_Params documentation used during I2C_Open()
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/2_20_00_06/exports/tirtos_full_2_20_00_06/products/tidrivers_full_2_20_00_08/docs/doxygen/html/struct_i2_c___params.html

[Originally Commented by @markhor ]
I2C TivaC driver information is available at:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/2_20_00_06/exports/tirtos_full_2_20_00_06/products/tidrivers_full_2_20_00_08/docs/doxygen/html/struct_i2_c_tiva___h_w_attrs.html#details
The header file:
http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/tirtos/2_20_00_06/exports/tirtos_full_2_20_00_06/products/tidrivers_full_2_20_00_08/docs/doxygen/html/_i2_c_tiva_8h_source.html

[Originally Commented by imgraham]
While I agree that it would be good to have timeouts while using i2c to help guard against individual tasks getting halted, our system isn't susceptible to the system-wide halting linked above. The system halt bug is an issue with the MSP430 i2c driver implementation which could cause a stall within the HWI - the only way around this is to modify the driver. But like I said, this doesn't apply to us since Tiva uses a completely different implementation.
The good news is that the Tiva drivers seem to be more stable and properly handle devices not being present on the bus - I don't think we've ever seen this issue.
Unfortunately, if we wanted to still safeguard (which isn't a bad idea), the drivers bundled with TI-RTOS for Tiva don't provide the I2C_cancel function. So if we implemented timeouts, there isn't a proper way to stop a transfer in progress. Someone posted a workaround for the MSP430 (https://e2e.ti.com/support/embedded/tirtos/f/355/t/489991) but this requires messing with implementation internals and completely breaks portability. It might be safer to just rely on the watchdog for now if this ever happens.


⚠ Bofrost.be has degraded performance

In 8f4f00f, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1677 ms

Resolved: Bofrost.be performance has improved in 9e97f69 after 1 hour, 20 minutes.


Login broken?

Hello,
I see there's already an issue open for login issues, but I noticed this morning that logging in was no longer working at all using either npx rettiwt login or rettiwt-auth user. In the former case (4.1.1), only {} is returned, and in the latter case (2.1.0), I'm getting the following error:

Error: Failed to authenticate using the given account Credentials
at /Users/jeto/Library/pnpm/global/5/.pnpm/rettiwt-auth@2.1.0/node_modules/rettiwt-auth/dist/Auth.js:235:55

The credentials are fine (I've tried with two accounts) and I can see on the corresponding Twitter account that I got a notification that there was an attempt (not a suspicious one though, so they should not be blocking it).
Feel free to close this if it's the same issue as the other ticket, I wasn't entirely sure.

Yeah that's the same issue (atleast, they are cause by the same code).
I'm working on that issue. It's just that I have been a bit busy lately. I'm trying to resolve it as fast as I possibly can.


Add gocloud to lambda back ends

Adds the govcloud region to the lambda back ends.  This fixes #1614

Coverage increased (+0.0003%) to 92.758% when pulling 5d6655a7eed858caf90cbff6bcea2e18e13d38d7 on nimbis:lambda-govcloud-backend into cb364eedc6e4edcfa3c65f152c7d13f1e5fe2ea4 on spulec:master.

Coverage increased (+0.0003%) to 92.758% when pulling 5d6655a7eed858caf90cbff6bcea2e18e13d38d7 on nimbis:lambda-govcloud-backend into cb364eedc6e4edcfa3c65f152c7d13f1e5fe2ea4 on spulec:master.

Thanks and welcome to Moto!


Pov tree logic ops

Pov exercise using tree logic ops. Resolves #1918
Largely based on the C# POV exercise.

When I looked at the append file locally, my editor corrected some issues with excess whitespace. Additionally, the code examples do not have to be indented. I pushed a commit to fix the issue. Maybe check whether your editor provides some plugin that can fix such formatting issues automatically on save.

I have a feeling the test runner output on the website for this will not look very nice because it can only handle exactly this structure well https://github.com/exercism/go-test-runner/#subtest-format-specification. But this is something we can address in another PR if we feel like it should be improved.


Fix bug in prep_riboviz.nf viz_params

I noted that the YAML file constructed by staticHTML had object names not file paths i.e.
$ cat work/4d/130b4e08bdcc0ce31ec2227379447b/config.yaml
asite_disp_length_file: !!sun.nio.fs.UnixPath {}
codon_positions_file: !!sun.nio.fs.UnixPath {}
features_file: !!sun.nio.fs.UnixPath {}
t_rna_file: !!sun.nio.fs.UnixPath {}

Changing prep_riboviz.nf from:
Map viz_params = [:]
if (is_asite_disp_length_file) {
    viz_params.asite_disp_length_file = asite_disp_length_file
}
if (is_codon_positions_file) {
    viz_params.codon_positions_file = codon_positions_file
}
if (is_features_file) {
    viz_params.features_file = features_file
}
if (is_t_rna_file) {
    viz_params.t_rna_file = t_rna_file
}

to
Map viz_params = [:]
if (is_asite_disp_length_file) {
    viz_params.asite_disp_length_file = asite_disp_length_file.toString()
}
if (is_codon_positions_file) {
    viz_params.codon_positions_file = codon_positions_file.toString()
}
if (is_features_file) {
    viz_params.features_file = features_file.toString()
}
if (is_t_rna_file) {
    viz_params.t_rna_file = t_rna_file.toString()
}

yields a YAML file with the expected paths e.g.
$ cat work/9a/c76bfdac711b068157bf2d0718ac23/config.yaml
{asite_disp_length_file: /home/ubuntu/riboviz/data/yeast_standard_asite_disp_length.txt,
  codon_positions_file: /home/ubuntu/riboviz/data/yeast_codon_pos_i200.RData, features_file: /home/ubuntu/riboviz/data/yeast_features.tsv,
  t_rna_file: /home/ubuntu/riboviz/data/yeast_tRNAs.tsv}

Fixed in viz-params-bug-fix-356.

Relates to #193 and #275.

@FlicAnderson has this given you any issues? The tests passed before and after this bug fix!

I now see why the tests pass. AnalysisOutputs.Rmd only checks for the presence or absence of configuration parameters in the YAML, it doesn't actually use them.

Merged #358.

@FlicAnderson Apologies, this bug was my bad. I'd forgot that the file name variables contain Groovy file objects and not string file names.


csv to parquet

In R, when trying
csv <- open_dataset("data.scv", format = "csv")
csv %>% write_dataset("train_data", format = "parquet")

the following error message appears
Error: Invalid: In CSV column #172: Row #408: CSV conversion error to null: invalid value '0.002861340479143'
Traceback:

1. csv %>% write_dataset("train_data", format = "parquet")
2. write_dataset(., "train_data", format = "parquet")
3. plan$Write(final_node, prepare_key_value_metadata(output_schema$metadata),
 .     options, path_and_fs$fs, path_and_fs$path, partitioning,
 .     basename_template, existing_data_behavior, max_partitions,
 .     max_open_files, max_rows_per_file, min_rows_per_group, max_rows_per_group)
4. ExecPlan_Write(self, node, ...)

How about trying the following?
csv <- readr::read_csv("data.csv")
csv %>% write_dataset("train_data", format = "parquet")

That's one way, but Is there a way to modify csv$schema? I mean column 172 only, not all of it.

You can use the col_types option of the arrow::read_csv_arrow() function.
Like this.
mtcars |> readr::write_csv("test.csv")
ds <- arrow::open_dataset("test.csv", format = "csv", col_types = arrow::schema("cyl" = arrow::utf8()))


"BITOR is completely unknown" exception error

Hello!
In one of my excels I have a formula that uses the BITOR function, and when I try to evaluate the formulas inside a sheet, it throws the next exception error:

{NPOI.SS.Formula.FormulaParseException: Name '_xlfn.BITOR' is completely unknown in the current workbook

Post the source code just in case it can be useful:
using (var fs = new FileStream(fileName, FileMode.Open, FileAccess.Read, FileShare.ReadWrite))
{
    book = (IWorkbook) new XSSFWorkbook(fs);
}
var eval = book.GetCreationHelper().CreateFormulaEvaluator();
try
{
    eval.EvaluateAll();
}

NuGet versions:

DotNetCore.NPOI version: 1.2.0
SharpZipLib version: 1.0.0-rc2

It's not the BITOR function supported in the last release?
Thanks!

I don't think BITOR is supported at all. NPOI simulates the Excel formula engine instead of using the original Excel engine. That's why NPOI doesn't have any dependency on Excel COM API.


Adding Rust implementation of Alba

This PR aims at adding the Rust implementation of Alba. This includes:

Prehashed version & Bounded version: some TODO left to fully implement the recursive hash optimization and look at hash personalization, etc.
(limited) tests:  positive and negative tests. Need to add randomized tests as well as property testing.
(limited) doc: Succinct comments on code that can be compiled with cargo doc
(limited) bench:  bench in tests (add assert!(false) to display) with low parameters, need to separate these in distinct file.

I think we should add Rust CI along with this PR, at a minimum.

I think we should add Rust CI along with this PR, at a minimum.

@abailly-iohk I was thinking the same thing. I am going to work on that 👍

I am going to merge this PR as discussed: we need to start somewhere on the path towards a production-ready library and this is as good a starting point as anything.


EEEOR!!!Recon process aborted. To RESHAPE the number of elements must not change

My systerm is Windows10, Matlab 2017a, MRilab 1.3
When I do a simulation, all seems successful, and the  scan progress bar increase 0% to 100%

however at the end of simulation, two  Out of error

I don't what the error mean, can you help me
there are some information about my simulation

Vobj
size:512,512,35
XDimRes:1.5mm
ZDimRes:5mm
Gyro:73997000
2.Sequence
PSD_FIESTA3D
3.Imaging

This usually occurs when the simulator accumulates unequal data to the prescribed size. See the pulse waveform from your prescription. I duplicated the experiment using the provided info and found the pulse waveform overlapping.

You might want to redesign your experiment (i.e. increase BandWidth) to avoid this error.

Hi, Dr. Liu, Thanks for your kindly answers!
I resesign my experiment, increase BandWidth from 19.2 to 51.2 KHZ，no errors anymore.
 Notice the rewinder is apart from the main gradient by CV1 and CV2 which need to be modified to appropriate value.


[WebAssembly] Abort failure - Abort trap: 6

There seems to be an issue after upgrading to emscripten v1.38.28 within the Mono WASM implementation.  There are random Abort trap: 6 failures while running against the Chakra engine.
Previous versions of emscripten have been working and the other engines that we test against work fine.
The issue from the Mono repo is here:  https://github.com/mono/mono/issues/13195
We have tried to add as much information as we can to the issue.

Attached a testcase.
To reproduce, compile chakra in debug mode and run:
out/Debug/ch -Prejit a.out.js
a.out.js.gz
a.out.wasm.gz

Expected results: runs.
Actual results:
ASSERTION 51860: (/Users/vargaz/ChakraCore/lib/Backend/IRBuilderAsmJs.cpp, line 1044)
!IsLoopBody() || offset <= GetLoopBodyExitInstrOffset()
 Failure: (!IsLoopBody() || offset <= GetLoopBodyExitInstrOffset())

* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode=0x0)
  * frame #0: 0x000000010045e55e ch`IRBuilderAsmJs::InsertLabels(this=0x00007ffeefbf79b8) at IRBuilderAsmJs.cpp:1044
    frame #1: 0x0000000100428fea ch`IRBuilderAsmJs::Build(this=0x00007ffeefbf79b8) at IRBuilderAsmJs.cpp:192
    frame #2: 0x00000001002a907a ch`Func::TryCodegen(this=0x00007ffeefbf7e40) at Func.cpp:408
    frame #3: 0x00000001002a8a54 ch`Func::Codegen(alloc=0x00007ffeefbf8410, workItem=0x0000000108a9d030, threadContextInfo=0x0000000109000058, scriptContextInfo=0x0000000109807058, outputData=0x00007ffeefbf8900, epInfo=0x000000010b914000, runtimeInfo=0x0000000000000000, polymorphicInlineCacheInfo=0x000000010b90e280, codeGenAllocators=0x0000000109031058, codeGenProfiler=0x0000000000000000, isBackgroundJIT=false) at Func.cpp:323
    frame #4: 0x000000010064975d ch`NativeCodeGenerator::CodeGen(this=0x0000000108900aa8, pageAllocator=0x0000000109000420, workItemData=0x0000000106f3ea30, jitWriteData=0x00007ffeefbf8900, foreground=true, epInfo=0x000000010b914000) at NativeCodeGenerator.cpp:894
    frame #5: 0x000000010064c109 ch`NativeCodeGenerator::CodeGen(this=0x0000000108900aa8, pageAllocator=0x0000000109000420, workItem=0x0000000106f3ea08, foreground=true) at NativeCodeGenerator.cpp:1011
    frame #6: 0x000000010064fb29 ch`NativeCodeGenerator::Process(this=0x0000000108900aa8, job=0x0000000106f3ea10, threadData=0x0000000000000000) at NativeCodeGenerator.cpp:1895
    frame #7: 0x000000010070ad24 ch`JsUtil::ForegroundJobProcessor::Process(job=0x0000000106f3ea10) at Jobs.cpp:426

With chakra version e149067c8f1a80462ac77d863b9bfb0173d0ced3

Thank you for the test case, this will make it much easier for me to repro.

@MikeHolman Thank you for the fix.  Do you know when the next release might be out so we can reactivate our CI tests.

We actually have a 1.11 release scheduled for tomorrow, so it should be out then.

Thank you Mike


Failure with mid360

Hi, I am currently testing your wonderful SLAM system, however, I am having quite a few problems setting everything up.
I believe the problems stem from an improper calibration between the IMU and LiDAR frames but I can't seem to make them work
I ran some tests using these calibration tools obtaining the following results:
Refinement result:
Rotation LiDAR to IMU (degree)     = -4.190764 10.136540  0.457075
Translation LiDAR to IMU (meter)   =  0.019770 -0.021399  0.055599
Time Lag IMU to LiDAR (second)     = -0.080000
Bias of Gyroscope  (rad/s)         = -0.000881  0.005376 -0.002475
Bias of Accelerometer (meters/s^2) = 0.234154 0.052154 0.041102
Gravity in World Frame(meters/s^2) = -0.247655 -0.030846 -9.819398

Homogeneous Transformation Matrix from LiDAR to IMU:
 0.984362 -0.020814  0.174923  0.019770
 0.007852  0.997192  0.074470 -0.021399
-0.175982 -0.071932  0.981762  0.055599
 0.000000  0.000000  0.000000  1.000000

However, since I have the sdf file of the robot I know where I placed the sensors, i.e.:
<link name = "lidar_link">
      <pose>0.05 0.0 0.3 0.0 0.0 0.0</pose>

and
<link name = "imu_link">
      <pose>-0.05 0.0 0.26 0.0 0.0 0.0</pose>

respectively.
If I use the geometrically accurate values for the extrinsic translation: extrinsicTrans: [-0.1, 0, -0.04] I obtain the following result:

The only way to obtain a somewhat convincing result is to set the gravity to zero:

I have no clue what else to try, if anyone has any idea I leave a bag here:
https://drive.google.com/drive/folders/1tDSTUFa_cjk_xvQPDTZA-OYF0lj6Kwsk?usp=sharing

Hi, after checking the bag you provided, I think the main problem may be that Livox updated the driver file of their lidar, resulting in the code not reading the point cloud data correctly. The test code was verified based on the test prototype provided by Livox. The old driver files were used. When the product was released, livox upgraded the product driver and changed the lidar topic from livox_ros_driver::CustomMsg to livox_ros_driver2::CustomMsg.
Since we are not using this LIDAR currently, this code will no longer be updated. It is recommended that you refer to other better SLAM projects about mid360, such as FAST_LIO.
If you want to continue using Mid360 based on the LIO-SAM framework, here are my suggestions:

Change the new radar message type livox_ros_driver2::CustomMsg. Debug and verify whether the data reading of each point in the point cloud is normal.
It is recommended to preferentially use the 9-axis imu test, which performed much better than the built-in 6-axis IMU in our experiments.

Hey, I solved the issue. The problem stems from the line where you convert the imu acceleration, given in g by the livox sensor. If I comment out the line acc*=imuGravity in the utility.h file the problem solves itself. I don't understand why setting imuGravity: 1 doesn't achieve the same end result tho.

In the bag you provided, I found that the built-in IMU acceleration range is 9.8. However, in the version I tested earlier, the numerical value was 1, so in this version of the code, the acceleration unit was converted. Now it seems that this conversion is no longer necessary.
setting imuGravity: 1 doesn't achieve the same  result  is because imuGravity also  be used in the IMUPreintegration moudle.  It is a parameter  to 'gtsam::PreintegrationParams'.(  imuPreintegration.cpp :214:     boost::shared_ptr<gtsam::PreintegrationParams> p = gtsam::PreintegrationParams::MakeSharedU(imuGravity);). So the magnitude of this value needs to be the local actual gravitational acceleration


Feature/anontokens v2

Update to latest version of the anonymous token nuget package and changed the feature flag to avoid activating broken implementation in the Smittestopp app.

Pull Request Test Coverage Report for Build 514513077

30 of 30 (100.0%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 85.282%

Files with Coverage Reduction
New Missed Lines
%

Fhi.Smittestopp.Verification.Domain/Dtos/AnonymousTokenResponse.cs
1
92.86%

Totals

Change from base Build 514499136:
-0.01%

Covered Lines:
1619

Relevant Lines:
1847

💛  - Coveralls

Pull Request Test Coverage Report for Build 514513077

30 of 30 (100.0%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.01%) to 85.282%

Files with Coverage Reduction
New Missed Lines
%

Fhi.Smittestopp.Verification.Domain/Dtos/AnonymousTokenResponse.cs
1
92.86%

Totals

Change from base Build 514499136:
-0.01%

Covered Lines:
1619

Relevant Lines:
1847

💛  - Coveralls


Remove CHCONF options from CMake

We currently define certain ChibiOS ch configuration options in two places: CMake and chconf.h. CMake options have priority. We can either remove the variables from CMake so only the ones in chconf are used or vice-versa.

:+1: sounds good.


Example of usage in the browser not working

Hi i used this code example:
   <script<EMAIL_ADDRESS>And get this error:

There’s an issue with version 0.1.5, can you use version 0.1.3 for now, I’m fixing this soon and will notify here.

There’s an issue with version 0.1.5, can you use version 0.1.3 for now, I’m fixing this soon and will notify here.

Thank you very much!

Thank you very much!

Thank you very much!

@sagoncalves , just a quick update that this has been fixed. You can always get the latest version via the script tag    <script<EMAIL_ADDRESS>

Thank you very much!

@sagoncalves , just a quick update that this has been fixed. You can always get the latest version via the script tag    <script<EMAIL_ADDRESS>


Add ability to customize repersonalization fields

fixes #25

@ashrude Thank you so much for working on this issue. The contribution looks good. Is it possible for you to add a test here tests/test_03_repersonalisation.py?

Sure. I can do that tommorow

Sorry it took so long, I was busy with other stuff.
I've added tests for custom fields, I believe I did them correctly but I'm not too familiar with pytest. Let my know if I did anything wrong

@ashrude thank you so much for helping out! its lgtm!


Use package HeatTransfer.jl for heat problems

Heat transfer analysis separated to own package HeatTransfer.jl where development continues.

Coverage increased (+0.2%) to 81.556% when pulling ecba5ed7feb28c6bbbe8c4b5770ac45c143ac05f on HeatTransfer into f0997d8239a55c2761df98a4d12250b3b061e91b on master.


docs(examples): add proxy example

I did add it to the readme. I think?

Anything else required?

Oh sorry, I didn't get a notification of the rebased commit. Thanks!


Fog color default value

crash-2024-08-05_00.14.23-client.txt
steps for reproduce:

run server lost worlds + lost cities
foggy weather on server
try to log in from client
crash on client

have the same problem

It's fixed already. Update Lost Worlds


Post release automated changes for iotoperations releases

Post release automated changes for azure-arm-iotoperations

API change check
API changes are not detected in this pull request.


403 Forbidden error when doing any action, but auth has timed out

Sit on a page that has a POST (e.g., the member/register or the admin/dashboard).

Looks like a 15 or 30 minutes to timeout? Check https://docs.spring.io/spring-security/reference/5.8/servlet/authentication/session-management.html#_detecting_timeouts

Click a button that does a POST
Get a 403 (Forbidden)

If I upgrade to Spring Boot 2.7.11, then that's Security 5.7.8. Probably need to test out Security 6.x when Boot 3.1.0 is released.


Bug

Hello...Last version has  a problem (1.02) I force to install 0.05 version ...Please check last version and come back me

Thanks for the bug report @RashadFG. We have noted it and is under investigation.


links at the bottom of /code-of-conduct need to have page context as the link instead of the full url

Contact information for your local Chapter Leader can be found on http://girl-develop-it.herokuapp.com/chapters
=>something like this
Contact information for your local Chapter Leader can be found on our chapter page.
https://www.dropbox.com/s/qbs4svemk5binjs/Screenshot 2015-01-31 15.46.34.png?dl=0

PR #155 fixes this @AndyLampert


Misalignment of form columns in Expert settings

JabRef version
5.13 (latest release)
Operating system
Windows
Details on version and operating system
No response
Checked with the latest development build (copy version output from About dialog)

[X] I made a backup of my libraries before testing the latest development version.
[X] I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

Appendix
No response

That's a VERY strange bug that depends on label text size.
I've decided it would be better to do this all vertically.


ESM should require file extensions

🐛 Bug Report
import t from './file';
import d from './directory/'

These should both fail to resolve, but since we use the same resolver as for CJS, it doesn't, and the import will work while it would have failed at runtime. This is also the case for dynamic imports.
This might need some support in resolve whenever they add support for ESM? https://github.com/browserify/resolve/issues/222
Place where we call resolve in jest: https://github.com/facebook/jest/blob/c024dec130d9914dcc3418ea74c26f667db3dbfa/packages/jest-runtime/src/index.ts#L395-L398
https://github.com/facebook/jest/blob/c024dec130d9914dcc3418ea74c26f667db3dbfa/packages/jest-runtime/src/index.ts#L423
Node docs: https://nodejs.org/api/esm.html#esm_mandatory_file_extensions
Node issue for better errors: https://github.com/nodejs/node/issues/30603

Would this change fail also when --es-module-specifier-resolution=node is used?

--experimental-specifier-resolution=node is the flag. And yeah, we'd need to keep the logic around for that case... Not sure how to best detect if it has been passed. It's not present in process.argv so we might need to have our own option for this 🙁

Maybe you can get it from process.execArgv.

For what it's worth, ts-node is doing this today.  We check both positional args and also the NODE_OPTIONS environment variable.  If you would like, I'll point you at our implementation.  We could also expose it via our API surface.
There's probably going to be a fair bit of overlap here, both for this and for mapping between rootDir and outDir and between file extensions.  Let me know if collaborating on a shared module to handle this stuff makes sense to you.

I'm using eslint-plugin-import with  "import/extensions": ["error", "ignorePackages"] rule to make sure all imports have extensions

OK, now that TS has announced they'll be forcing Node ESM to use extensions (https://devblogs.microsoft.com/typescript/announcing-typescript-4-5-beta/#new-file-extensions, https://twitter.com/orta/status/1444958295865937920) we need to figure this out (preferably releasing a few weeks before 4.5 goes stable to get ahead of all the people who will complain that Jest doesn't work).

Current plan is to enforce file extensions for ESM resolution (import and import()), but allow some sort of opt-in to the current (i.e. CJS) behavior (like --experimental-specifier-resolution mentioned above does). I don't think I'd like to auto-detect the presence of that flag.
This also impacts https://jestjs.io/docs/configuration#extensionstotreatasesm-arraystring - we might have to start throwing on that and tell people to use type...
/cc @ahnpnl

@cspotcode I'd be very interested to hear how this impacts ts-node 🙂

The file extensions behaviour shouldn't affect ts-node much.  We already align with TS and node as far as file extensions go, and we resolve correctly.
import statements should point to the emitted js (that's what you want to import, after all) and we resolve that to the source .ts, since it's our job to essential emit in-memory, not on the filesystem.  For production you can pre-compile to the filesystem and get rid of ts-node and everything works.
ts-node matches node's behavior regarding --experimental-specifier-resolution, which is to say, if you omit that flag, then file extensions are required.  If you pass that flag via NODE_OPTIONS or whatever, then you get the behavior of that flag.

Currently, the transformer logic follows what Jest asks for. IIRC extensiosToTreatAsESM is a short-term solution to adopt ESM? If we can switch to use type instead, it would be better that we can remove one Jest config option.
In general, for transformer, I think we should just stick to the current approach that transformer should give what Jest needs. Maybe small changes from ts-jest side.

I don't think we can remove extensionsToTreatAsESM, if nothing else since TS doesn't have any plans (I asked Orta) for enforcing extensions when outputting ESM for non-node (even though it's technically invalid ESM, they cannot break everybody outputting it and then consumed by bundlers). So Jest shouldn't force people to use extensions if they don't want. extensionsToTreatAsESM is a nice escape hatch for those cases.
But we should probably expand our current handling to first check extensionsToTreatAsESM, then look at type also for .ts and .tsx

even though it's technically invalid ESM

Isn't the format of module specifiers host-defined, so it's valid ESM?  According to the spec.

Sure, but it's invalid in node (without experimental flag) and browsers, which should cover (completely made up number) 99% of hosts running the code natively, no?

Bundlers are effectively a runtime target.  I simply mean that, in terms of the TS team's decision-making, it is technically valid ESM, which is why they're supporting it.  It's not merely a backwards-compat issue.  A lot of the ecosystem's problems tend to get blamed on TS, when it's actually TS playing along with the ecosystem's desire to be custom at every turn.

Ah right. Fair enough 🙂

related https://github.com/jestjs/jest/issues/15354


Could you publish the API documentation?

The crate https://crates.io/crates/divans contains a documentation link that is actually a link to a blog post. A link to the API documentation would be useful, too.

Is this work going on?


Handle ties properly

Tied matches should not rely on having two Haunted Mines games attached.

Where are tied matches stored in the system?  I don't see this or haunted mines anywhere obvious

Shouldn't be too hard to find a tied game, they either don't have a winner id or it's 0.

What I mean is that I do not see haunted mines getting attached to tied games, per the issue description.

It happens in swiss.php as example for matchestohandle where map id 1 is assigned for draws.

OK, I see that, thanks:
https://github.com/Fabian-Sommer/HeroesLounge/blob/632f4df5accd94b517c7f6d7d16cba8f78c31b20/plugins/rikki/heroeslounge/classes/matchmaking/Swiss.php#L267
So now, I'm curious what the problem is specifically, or what the goal is.

Those matches that we are talking about did not end up getting played. However, in our system it looks like they were played (two games) ending 1-1. This is more of a workaround than proper modeling and looks weird in the various places - for example, when clicking on the match, one can see the two supposed games.
The goal would be to not rely on artificial games to indicate a tie while making it clear on the frontend that the match was a tie due to not being played for some reason. Backend needs a way for mods to mark a game as tied without creating two Haunted Mine games.
Side note: There are some ties that were played properly, we used to have Bo2 for playoffs. These are not concerned in this issue and nothing should change for them, this is purely about games that ended up being a tie for not being played.

how should those games be displayed then?  Also how should they factor into the fvarious calculations for scores wins etc