遇到vue dismatch错误等常见问题 先看这里~

首先vue dismatch是vue-template-compiler的坑 他会强制检查当前的vue和vue-template-compiler的版本是否严格匹配，所以一旦你系统中以前装过vue（最常见的情况就是不小心全局安装过vue）所以就会干扰 weex-toolkit。
我做了一个在线修复工具专门修复这种问题
食用方式
weex xbind repair toolkit-repair
然后执行 weex repair就行了~
这个问题也会检测一些环境和权限的问题，做出相应的提示
具体相关问题可以统一在这个issue里回复，

大兄弟很强

大兄弟很强+1

不生效哦。怎么破？一样报错。无法解决。求救。

重复执行的结果是一样的，污染一直存在，无效。
$ weex repair
检测环境中...
环境正常!
检测是否有不匹配的vue污染...
search: /Users/NoraChan/.xtoolkit
search: /Users/NoraChan/.nave/installed/weex/lib/node_modules/weex-toolkit/node_modules/weex-builder/node_modules/vue-template-compiler
/Users/NoraChan/.nave/installed/weex/lib/node_modules/weex-toolkit/node_modules/weex-previewer/node_modules/weex-builder/node_modules/vue-template-compiler
发现版本不匹配的vue污染: /Users/NoraChan/.nave/installed/weex/lib/node_modules/weex-toolkit/node_modules/weex-previewer/node_modules/vue/dist/vue.runtime.common.js
卸载中...
up to date in 11.344s
修复完成
看起来是weex-toolkit自己导致的冲突，但我的weex-toolkit是稳定版本的。请问如何解决
$ weex -v
v1.0.7

weex-builder : v0.2.12
weex-devtool : v0.3.2-beta.7
weex-previewer : v1.3.13
weexpack : v0.4.7-beta.11
toolkit-repair : v0.0.5
$ npm list -g -depth=0
/Users/NoraChan/.nave/installed/weex/lib
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>

@NoraGithub Run npm i weex-toolkit@latest to update your weex-toolkit.

@erha19
Afterweex repair, It doesn't repeat reminding me of version dismatch now. But when I run npm run dev, the error below still comes to me.It's so confusing. I read many answers for several days, but they don't help. Would you please help me for that?
Vue packages version mismatch:

<EMAIL_ADDRESS><EMAIL_ADDRESS>
This may cause things to work incorrectly. Make sure to use the same version for both.
If you are using<EMAIL_ADDRESS>simply update vue-template-compiler.
If you are using<EMAIL_ADDRESS>or vueify, re-installing vue-loader/vueify should bump vue-template-compiler to the latest.

@NoraGithub Here is a simple way that you can just update vue-template-compiler by npm update vue-template-compiler --save on your project, the<EMAIL_ADDRESS>would be the correct version.

It doesn't work. Still the same error.
$ npm list -l -depth=0
<EMAIL_ADDRESS>│ /Users/NoraChan/Desktop/移动端开发/yanxuan-weex-demo
│ a weex project
├──<EMAIL_ADDRESS>│   Babel compiler core.
│   https://github.com/babel/babel/tree/master/packages/babel-core
│   https://babeljs.io/
├──<EMAIL_ADDRESS>│   babel module loader for webpack
│   git+https://github.com/babel/babel-loader.git
│   https://github.com/babel/babel-loader
├──<EMAIL_ADDRESS>│   Fix babel/babel#2212
│   git+https://github.com/59naga/babel-plugin-add-module-exports.git
│   https://github.com/59naga/babel-plugin-add-module-exports#readme
├──<EMAIL_ADDRESS>│   Externalise references to helpers and builtins, automatically polyfilling your code without polluting globals
│   https://github.com/babel/babel/tree/master/packages/babel-plugin-transform-runtime
├──<EMAIL_ADDRESS>│   Babel preset for all es2015 plugins.
│   https://github.com/babel/babel/tree/master/packages/babel-preset-es2015
│   https://babeljs.io/
├──<EMAIL_ADDRESS>│   babel selfContained runtime
│   https://github.com/babel/babel/tree/master/packages/babel-runtime
├──<EMAIL_ADDRESS>│   css loader module for webpack
│<EMAIL_ADDRESS>│   https://github.com/webpack/css-loader#readme
├──<EMAIL_ADDRESS>│   fs-extra contains methods that aren't included in the vanilla Node.js fs package. Such as mkdir -p, cp -r, and rm -rf.
│   git+https://github.com/jprichardson/node-fs-extra.git
│   https://github.com/jprichardson/node-fs-extra
├──<EMAIL_ADDRESS>│   Manage session history with JavaScript
│   git+https://github.com/ReactTraining/history.git
│   https://github.com/ReactTraining/history#readme
├──<EMAIL_ADDRESS>│   launch iOS apps iOS devices from the command line (Xcode 7)
│   git+https://github.com/phonegap/ios-deploy.git
│   https://github.com/phonegap/ios-deploy#readme
├──<EMAIL_ADDRESS>│   This is a tiny utility to get local ip address with in node applications.
│   git+https://github.com/aloksguha/myip.git
│   https://github.com/aloksguha/myip#readme
├──<EMAIL_ADDRESS>│   Reactive, component-oriented view layer for modern web interfaces.
│   git+https://github.com/vuejs/vue.git
│   https://github.com/vuejs/vue#readme
├──<EMAIL_ADDRESS>│   Vue single-file component loader for Webpack
│   git+https://github.com/vuejs/vue-loader.git
│   https://github.com/vuejs/vue-loader
├──<EMAIL_ADDRESS>│   Official router for Vue.js 2
│   git+https://github.com/vuejs/vue-router.git
│   https://github.com/vuejs/vue-router#readme
├──<EMAIL_ADDRESS>│   template compiler for Vue 2.0
│   git+https://github.com/vuejs/vue.git
│   https://github.com/vuejs/vue/tree/dev/packages/vue-template-compiler#readme
├──<EMAIL_ADDRESS>│   state management for Vue.js
│   git+https://github.com/vuejs/vuex.git
│   https://github.com/vuejs/vuex#readme
├──<EMAIL_ADDRESS>│   Effortlessly keep vue-router and vuex store in sync.
│   git+https://github.com/vuejs/vuex-router-sync.git
│   https://github.com/vuejs/vuex-router-sync#readme
├──<EMAIL_ADDRESS>│   Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
│   git+https://github.com/webpack/webpack.git
│   https://github.com/webpack/webpack
├──<EMAIL_ADDRESS>│   Serves a webpack app. Updates the browser on changes.
│   git+https://github.com/webpack/webpack-dev-server.git
│   https://github.com/webpack/webpack-dev-server
├──<EMAIL_ADDRESS>│   a weex compiler tool  used by weex-toolkit (bind on "weex compile")
├──<EMAIL_ADDRESS>│   Weex HTML5 Renderer
│<EMAIL_ADDRESS>│   https://alibaba.github.io/weex
├──<EMAIL_ADDRESS>│   a webpack loader for weex
│   git+https://github.com/weexteam/weex-loader.git
│   https://github.com/weexteam/weex-loader#readme
├──<EMAIL_ADDRESS>│   weex router
│   git+https://github.com/weexteam/weex-components.git
│   https://github.com/weexteam/weex-components#readme
└──<EMAIL_ADDRESS>Weex built-in components for Vue 2.x.
<EMAIL_ADDRESS>http://weex.apache.org/

@erha19  It's already the version 2.5.3 as info described above.  I am reading other's code to quickly start up my own project. It would be great if you could give me a hand for the issue.

@NoraGithub Have you update your weex-toolkit to the latest version? The latest version is above v1.1.0.
If you develop your own project, you should update your weex dependence of weexpack by weex update weexpack and re-create your weex project.

Yes, though there are some errors.
And I am not clear about re-create project. I clone project here.
How many steps does re-create mean?
Does that mean I need to delete some files and create project command may re-create those files   or any other steps?
If I need to delete , which files are affected?
Here is some info:
$ npm list -g -depth=0
/Users/NoraChan/.nave/installed/weex/lib
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing: webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc, required by<EMAIL_ADDRESS>$ weex -v
v1.1.0-beta.6

weexpack : v0.4.7-beta.19
weex-builder : v0.2.13-beta.4
weex-devtool : v0.3.2-beta.7
weex-previewer : v1.3.13-beta.8
toolkit-repair : v0.0.5

This does not seem to be a problem for weex-toolkit, I try to help you
look at your problem，please wait a moment!
2017-11-07 15:58 GMT+08:00 NoraGithub<EMAIL_ADDRESS>
Yes, though there are some errors.
And I am not clear about re-create project. I clone project here
https://github.com/zwwill/yanxuan-weex-demo.
How many steps does re-create mean?
Does that mean I need to delete some files and create project command may
re-create those files or any other steps?
If I need to delete , which files are affected?
Here is some info:
$ npm list -g -depth=0
/Users/NoraChan/.nave/installed/weex/lib
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! peer dep missing: webpack@1 || 2 || ^2.1.0-beta || ^2.2.0-rc,
required by<EMAIL_ADDRESS>$ weex -v
v1.1.0-beta.6

weexpack : v0.4.7-beta.19
weex-builder : v0.2.13-beta.4
weex-devtool : v0.3.2-beta.7
weex-previewer : v1.3.13-beta.8
toolkit-repair : v0.0.5

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/weexteam/weex-toolkit/issues/80#issuecomment-342403675,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJXmXjzqSatSuL4TCjwQZ1oSZux6xAQrks5s0A2jgaJpZM4MgJJq
.

@NoraGithub I have create a PR to fix this issue, see https://github.com/zwwill/yanxuan-weex-demo/pull/20.

@erha19
Many many thanks.
You are super nice and helpful.
Hope the mention symbol @ doesn't disturb you.

use
weex xbind repair toolkit-repair
weex repair

it still not work
01:09:05 : Bundling source...
01:09:07 : ./views/auto/1.0/index.vue?entry=true
Module build failed: Error:
Vue packages version mismatch:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

感谢救命之恩


Add required ReadTheDocs configuration

Should fix broken RTD doc builds. Needed because of https://blog.readthedocs.com/migrate-configuration-v2/
@rpiazza

Failing due to

AttributeError: module 'lxml.etree' has no attribute '_ElementStringResult'

More info on failure:
stixmarx uses that etree property here: https://github.com/mitre/stixmarx/blob/4f906eb15af431c12c36c8683f9bcd60d39c364e/stixmarx/xml.py#L59
But it was removed in this commit: https://github.com/lxml/lxml/commit/eba79343d0e7ad1ce40169f60460cdd4caa29eb3
We could pin lxml to <5.1.1 here or fix that line in stixmarx and make a new release.


Installation guide linked to matt section 5.1

The advice for installing the package says to go through matts github not the grattan one in section 5.1 @wfmackey

GREAT ISSUE TO RAISE LACHIE

everything should go through my Github, ideally

can't tweet but can git


Create 0.5.1 compatibility

I hope that Minecraft version 1.19 (Forge) will add create: 0.5.1 compatibility

The latest version is compatible with Create 0.5.1


sealer join command

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

the new file, pelease add lic , use 'make license' command generator it.

LGTM
/needs test


Document running Telegraf using remote configuration files

When starting Telegraf, you can use a URL with the -config flag to pull a configuration file from a remote endpoint and start Telegraf using that configuration.
Related links

https://docs.influxdata.com/telegraf/v1.14/administration/configuration/
https://github.com/influxdata/telegraf#run-telegraf-with-all-plugins-defined-in-config-file

thanks, @sanderson, @rbetts! addressed in #2802


Help to fix Virtual Server parameter

I am trying to run this app in root domain folder:
www.xboat.com.br
But it just can be opened without CSS in the base url:
www.xboat.com.br/web/
How can I change the right parameter to fix this?
Thanks!

Your DocumentRoot seems wrong. Check if it is correctly configured as described here:
https://github.com/Cocolabs-SAS/cocorico/blob/master/src/Cocorico/CoreBundle/Resources/doc/virtual-hosts.rst.
It should be under the web directory.


Importing samples into Android Studio

Can you elaborate on the comment in the README where it says “NOTE Do not import the project into Android Studio. There is an outstanding issue in Android Studio that requires importing the project in the steps defined below."?

There isn't a link to the outstanding issue, and once you clone it you pretty much have to import the gradle sample project so I'm not clear on what this means.

I'm using Android Studio 1.0.1 and immediately after cloning the project I was prompted if I wanted to open the project. I selected "Yes" and then got an Import Project from Gradle window (see screenshot below), then I simply went with the defaults and selected "OK".

This seems a bit different from what the workflow described in the README for importing the gradle sample project. Would it make sense to also include the workflow I have mentioned in a future version of the README?

Interesting... I see I still had to following the Import Non-Android Studio project from the Welcome Quick Start step even after going thru the step above. Any clue why using the IDE default prompts didn't install the samples the first time?

@andygup Yes, this is why the README recommends not importing the project which is not an ideal workflow.  I do not have an issue # to reference but you can follow the following thread to see that the issue is confirmed by Google and add some comments to help get the fix out :-).

Thanks, I posted a comment to the thread.

can you make a youtube video to show how import the sample into android studio please ?

@kuraii3 We can consider that after we release beta-2.  For now, after you fork/clone are you having issues importing the project?  Depending on the version of Android Studio you are using the verbiage may be slightly different, see screenshot below where you would choose Import project (Ecilpse ADT, Gradle, etc.):

Once you have opened the project on import you can open the project with Open an existing Android Studio project.  The impeded issue is with respect to opening the project initially with Import.

@doneill thanks i managed to import it successfully


Support PrOPPER Renaming

See
https://www.youtube.com/watch?v=AoVkUBsUT-Q

As a reference for my self: Here would be unrenamed original game:

And the imported one:

This actually renames the filenames (gamename)(original 2024)(MOD)(author)(version)

Part of 2.17.0

This doesn't seem to be renaming related files like .ini files.  Presuming you want to replicate the functionality of Popper media manager, it should rename .ini and .directb2s files to match.

There was a bug, fixed with 2.17.3.
You used the latest version?


Missing closing /a element

On https://docs.microsoft.com/en-us/power-bi/admin/service-admin-manage-your-data-storage-in-power-bi, everything from the "Manage items you own" header on down appears as if it is a giant link.  It appears to be missing a closing  element.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e0947245-d1c6-486a-94a1-f8622a4f7efc
Version Independent ID: c837d3a1-75f5-ffd4-a32a-541bab72ffa7
Content: Manage data storage in your workspaces - Power BI
Content Source: powerbi-docs/admin/service-admin-manage-your-data-storage-in-power-bi.md
Service: powerbi
Sub-service: powerbi-service
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Thanks for your comment, @smearp . This issue has been assigned to the doc author for review.

Wow, good catch, @smearp -- thanks for pointing that out! Fixing it now. Update will be live tomorrow afternoon, July 9.


Use PPA version of wslu for ubuntu

The wslu package in this PPA is always the up-to-date version

Thanks, Patrick!


Token factory contract example

Osmosis Token Factory CosmWasm Contract Example
This demo contract provides a 1:1 mapping to the Osmosis token factory
bindings.
The contract messages only do some input validation and
directly call into their respective bindings outlined in the
"Messages" section below.
There are unit tests added to demonstrate how contract
developers might utilize osmo-bindings-test package
to import and use some test utilities.
Messages
There are 4 messages:

ExecuteMsg::CreateDenom maps to OsmosisMsg::CreateDenom
ExecuteMsg::ChangeAdmin maps to OsmosisMsg::ChangeAdmin
ExecuteMsg::BurnTokens maps to OsmosisMsg::MintTokens
ExecuteMsg::MintTokens maps to OsmosisMsg::BurnTokens

Query
1 query:

QueryMsg::GetDenom maps to OsmosisQuery::FullDenom

Changes to Bindings

Added OsmosisQuerier in packages/bindings

It is needed to conveniently call custom osmosis messages and share them across contracts.

Credits

@mattverse with burn and mint tests that were merged in #10

Merging this as this was approved in the duplicate repository that was archived


Initial setup Backend - Sprint1

@peculiaruc Kindly assign this task to Martins (github: Simplemart17)

@raoularavel Let him start and also accept the invite to this repo.


[GHSA-ghg6-32f9-2jp7] XXE in PHPSpreadsheet encoding is returned

Updates

Affected products

Comments
BULNERABILITY

Hi there @oleibman! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

I am a bit of a stranger here. Does this activity require that I do anything, or is it just informative?

Hi @KODIKAS-SERVER, your pull request does not appear to have any changes in it.  Could you please clarify what needs to be changed?
@oleibman, you do not need to do anything. We automatically tag maintainers in these requests for their awareness and to give them an opportunity to provide their opinion on whether the change is appropriate.

CHANGELOG.md

DiccionarioDatosEECAN.xlsx
Listado datos abiertos (1).pdf
BM_Operativa_200612.xls
DPR-EC-09706.1 PS for BIK Port.pdf


Remove un-used json files and absorb multi page test into Star Wars

Changes
Remove the non python model generated json from app/data and absorb the missing backwards test of multi pages. (N.B the others which are being deleted  are now tested in #271 as we are not going to maintain 999.json)
How to test
Make sure the tests run successfully
Who can test
Anyone but @LJBabbage

I've rebased this - looks good to me once CI passes 👍


Add series exercise

Two mildly notable things:

I changed the "overly long slice" to expect an empty list rather than an error, rationalizing that there simply aren't any runs of 4 in a 3 char string. I'm flexible /shrug
I added a test for input with non-numeric characters which expects an Err.

Awesome! :tada:


Feature Request: Fill state bar as counter background

The yellow color of full barrels writing is a hint but then it is already too late. The fill state bar would not mess up the monitor as it could be the background of the counter number. Red and green are no good background colors - I learned that from a colour-blind work mate. Blue, yellow and black could be better choices.

Thank you it looks very good and is highly informative.


chore: add github templates

Using ADX's templates as a basis for consistency.
Add basic templates and processes:

CODEOWNERS
Bugs
FR (to Discussions)
PR
Automate CHANGELOG
Levitate (as comments)
Add to project board (for the new squad)

This does not include:

Code coverage

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

Ty @vickyyyyyyy, I see the note on code coverage, do you want me to include this too?

Yup! Doesn't need to be done now, I just didn't add it for now because I wasn't sure what coverage we wanted to track in the Go package


Error when reading '/C:/Users/Administrator/AppData/Local/Pub/Cache/hosted/pub.flutter-io.cn/dartssh2-2.4.4/lib/next/socket/ssh_socket_js.dart': 系统找不到指定的路径。

Hi Owner,
I try to use your ssh2 and found below error,would you pls double check and reply?
Many Thanks.
Zhangmang
<EMAIL_ADDRESS>Launching lib\main.dart on Chrome in debug mode...
lib\main.dart:1
/C:/Users/Administrator/AppData/Local/Pub/Cache/hosted/pub.flutter-io.cn/dartssh2-2.4.4/lib/src/socket/ssh_socket.dart:4:8: Error: Error when reading '/C:/Users/Administrator/AppData/Local/Pub/Cache/hosted/pub.flutter-io.cn/dartssh2-2.4.4/lib/next/socket/ssh_socket_js.dart': 系统找不到指定的路径。
import 'package:dartssh2/src/socket/ssh_socket_io.dart'
package:dartssh2/…/socket/ssh_socket_io.dart:1
^
/C:/Users/Administrator/AppData/Local/Pub/Cache/hosted/pub.flutter-io.cn/dartssh2-2.4.4/lib/src/socket/ssh_socket.dart:13:18: Error: Method not found: 'connectNativeSocket'.
return await connectNativeSocket(host, port, timeout: timeout);
^^^^^^^^^^^^^^^^^^^

Hello,
It looks like you're using dartssh2 in browser. Currently no browser supports opening TCP connections and to use dartssh2 you have to either compile your app to desktop/mobile version, or implement your own  SSHSocket that relies on other underlying transports such as WebSocket or SSE.

By the way I'd like to hear what you want to build with dartssh2 so I can tailor the package to better fit your (and other's) needs.

Two important things:

Regarding a fix for the error IN ADDITION TO the implementation of our own SSHSocket while waiting for you to get it working, in ssh_socket.dart, line 5 should read if (dart.library.js) 'package:dartssh2/src/socket/ssh_socket_js.dart';, not if (dart.library.js) 'package:dartssh2/next/socket/ssh_socket_js.dart';.
The problem lies in the fact that there is no next directory.

By the way I'd like to hear what you want to build with dartssh2 so I can tailor the package to better fit your (and other's) needs.

I am using dartssh2 to connect to a proxy server, which then connects to other devices from there. Using XTerm to customize and handle the terminal display on the web. Which means, it would be nice to have a friendly way to print responses back for my terminal, while filtering only the needed responses...for some things need to be handled autonomously.

@xtyxtyx when using the dartssh, we implemented the SSHClient thusly
SSHClient(
hostport: Uri.parse(_host),
login: _username,
print: print,
termWidth: 80,
termHeight: 25,
termvar: 'xterm-256color',
getPassword: () => utf8.encodeBytes(_password),
response: (transport, data) {
if (!_baseConnected) {
if (data.contains('Are you sure you want to continue connecting')) {
_client.sendChannelData(utf8.encodeBytes('yes\n'));
}
if (data.contains('root@localhost's password:')) {
_client.sendChannelData(utf8.encodeBytes('$_password\n'));
setState(() {
_delayIndex = 0;
// additional local logic
});
}
} else {
_terminal.write(data);
}
},
success: () async {
_proxyConnected = true;
_terminal.write('proxy connected.\n\r');
// additional logic to connect to devices
},
disconnected: () {
_terminal.write('disconnected.\n\r');
if (mounted) {
setState(() {
// local variable logic
});
}
},
debugPrint: (str) {
// logging logic
},
tracePrint: (str) {
// logging logic
});

@xtyxtyx just to clarify, needing to verify that my ssh connection within the proxy (that I used the SSHClient to connect to) actually occurred, otherwise I will be in an endless loop of connecting->exposing device to a different port...which closes the ssh session->connecting to that new port-> exposing device to a different port...etc
We had some local logic to account for that loop, but get stuck in that loop without the response handled similarly to how it was in dartssh.


added: support subfolders

fixed: isDirectoryError in get()

@avarx, thanks for your work, and I'm sorry this never got merged in.
Prior versions of cheat were causing us all kinds of headaches, so I re-wrote it from scratch in Go. That being the case, I'll close this PR, as it's now moot.
Please check out v3 if you're still interested in cheat, though. It now does implement nested folder support, along with a handful of other long-requested features.


404 error

I try to Integrate Go Influx Client with Apache SUperset, when I enter link below I get 404 error.
https://docs.influxdata.com/influxdb/cloud-iox/visualize-data/superset/
Relevant URLs

Provide relevant URLs

What products and version are you using?

@Kamil16345 Here's the Superset page that you should have been redirected to: https://docs.influxdata.com/influxdb/cloud-iox/query-data/tools/superset/
I've opened #4872 to fix this. Thank you for reporting.


Collection icon picture is not loading

I suspect resize parameter is issue

https://kodadot.xyz/ahp/collection/89

Maybe @preschian can have a look?

Probably similar one

https://github.com/kodadot/nft-gallery/issues/9194
https://github.com/kodadot/nft-gallery/issues/9216

I suspect resize parameter is issue

checking. Yes, I guess so since the banner loads properly but not the icon


fix(postgres-cdc): set default ssl.mode to disable

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Set default to disable for backward compatibility
related: #15690
Checklist

[ ] I have written necessary rustdoc comments
[ ] I have added necessary unit tests and integration tests
[ ] I have added test labels as necessary. See details.
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[ ] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

LGTM, thanks!


FYI: Related Work

@zero-ui: FYI, a while ago @syoyo did some similar work here: https://github.com/syoyo/nanocanvas (duktape bindings to the cross-platform nanovg library).
I contributed a few pull requests and wrote a very simple layout library that runs on it: https://github.com/prust/lightning-layout.
Recently I've needed a more powerful layout library, with horizontal and vertical flow (it looks like the one you have in ZUI has these), so I'm in the middle of extending it, but I've been working on it in Lua (for the excellent LÖVE runtime, which is written on SDL2) & I haven't finished it or ported it back to the JS yet.

I have a private version that has been ported to duktape and bound to dukluv, https://github.com/creationix/dukluv

https://github.com/syoyo/nanocanvas this project is not suitable for my present job

You can provide a e-mail, I sent you a demo program

@zero-ui: My email address is<EMAIL_ADDRESS>

I can't send mail to your mailbox because it has been identified as spam. Please look directly at my newly submitted code


Fix transform definition in console progress test

and make sure the test fails when the transform definition is invalid.
The test still used registerOutput, which never saw the light.

How come we didn't notice this failing?

It seems like the build currently doesn't fail when you declare a file collection as an input but don't resolve it as part of the build action.


[Server] NoRouteToHostException

00:44:03 [INFO] [WebSocketAPI] New connection from: 0:0:0:0:0:0:0:1
00:44:58 [INFO] [TrackerServer] Tracker timed out: udp://<IP_ADDRESS>
00:45:03 [INFO] [TrackerServer] Handshake received from /<IP_ADDRESS>:6969
00:45:03 [INFO] [TrackerServer] Sensor 0 for udp://10:91:A8:17:F4:B4 status: 1
00:45:03 [INFO] [TrackerServer] Sensor info for udp://<IP_ADDRESS>/0: 1
00:45:11 [INFO] [TrackerServer] Tracker timed out: udp://<IP_ADDRESS>
00:46:21 [SEVERE] java.net.NoRouteToHostException: No route to host
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramChannelImpl.send0(Native Method)
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramChannelImpl.sendFromNativeBuffer(DatagramChannelImpl.java:901)
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:863)
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramChannelImpl.send(DatagramChannelImpl.java:821)
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramChannelImpl.blockingSend(DatagramChannelImpl.java:853)
00:46:21 [SEVERE]       at java.base/sun.nio.ch.DatagramSocketAdaptor.send(DatagramSocketAdaptor.java:218)
00:46:21 [SEVERE]       at java.base/java.net.DatagramSocket.send(DatagramSocket.java:664)
00:46:21 [SEVERE]       at dev.slimevr.vr.trackers.udp.TrackersUDPServer.run(TrackersUDPServer.java:316)

honestly I wasn't sure how it happened. I know it happened a lot when I was testing out my trackers. So I think its related to the communication with the tracker, which makes sense because this is the tracker udp server.
Most likely, we should just explicitly look for this networking error and catch it, print it, and continue on with our day, instead of crashing the thread.

I know why it happens, its just when the UDP socket is trying to bind to a used port


a Context remaining greyed out in filter menu

Bug Report
Important
Please follow this template strictly when reporting bugs.
Reports that do not adhere to this template will not be addressed and will be closed.
App Version: Enter the version number, e.g., 1.2.3
2.0.11
Platform: Linux
Installation Method: Snap
Expected Behavior:
Explain what you expected to happen.
I had used a context, and then reset the filters. I expected all of the contexts in the filter menu to become available.
Actual Behavior:
Explain what actually happened.
When I tried to reset the filters, one of the contexts remained greyed out.
I can click the context inside one of the task lines, and filter that way, but this is less than optimal!
Steps to Reproduce:
(I can't 'reproduce' it since the error is persistent. I do have to different todo.txt tabs open, and they do have different contexts. I have tried resetting everything via ctrl-0 but the context in question remains greyed out.)
(I have tried quitting and restarting the application, as well as unlinking and re-linking the todo.txt files.)
Screenshots:
If applicable, include screenshots that demonstrate the bug.

@jason-mehmel is there any filter (see filter tab in the drawer) enabled, which could hide todos? Without an example, it is hard to reproduce this.


Disparity image appears to be slightly smaller than the Preview image

I am using an OAK-D-Lite device to detect objects and to determine their x, y, z coordinates. So far I have been successful in putting together pipelines to achieve the basic goal. However, the spatial coordinates that I got were somewhat inconsistent.
When I looked closely to compare the disparity images with the preview images, I noticed that the disparity image is slightly smaller than the preview image causing a potential error in depth readings. Below is a simple pipeline that displays both the preview image and the disparity images to illustrate the difference. I've also used the code to capture the attached preview and disparity images for illustration. There is a music stand in the images that can be used as a reference for comparison. I specified stereo.setDepthAlign(dai.CameraBoardSocket.RGB) as I think I need to do. I do not know if this what I would expect or did I do something wrong. Do I have to manually calibrate and align the disparity image to the preview image that I am using for object detection?
import cv2
import depthai as dai

# Create pipeline
pipeline = dai.Pipeline()

# Define RGB source and output
camRgb = pipeline.create(dai.node.ColorCamera)
xoutRgb = pipeline.create(dai.node.XLinkOut)

xoutRgb.setStreamName("rgb")

# Properties
camRgb.setPreviewSize(640, 400)
camRgb.setInterleaved(False)
camRgb.setColorOrder(dai.ColorCameraProperties.ColorOrder.RGB)

# Linking RGB
camRgb.preview.link(xoutRgb.input)

# Define mono camera sources for stereo depth
mono_left = pipeline.createMonoCamera()
mono_left.setResolution(dai.MonoCameraProperties.SensorResolution.THE_400_P)
mono_left.setBoardSocket(dai.CameraBoardSocket.LEFT)
mono_right = pipeline.createMonoCamera()
mono_right.setResolution(dai.MonoCameraProperties.SensorResolution.THE_400_P)
mono_right.setBoardSocket(dai.CameraBoardSocket.RIGHT)

# Create stereo depth node
stereo = pipeline.createStereoDepth()
stereo.setLeftRightCheck(True)
stereo.setDepthAlign(dai.CameraBoardSocket.RGB)
stereo.setOutputSize(640, 400)
stereo.setOutputKeepAspectRatio(False)

# Linking mono cameras to stereo
mono_left.out.link(stereo.left)
mono_right.out.link(stereo.right)

# Create disparity output
disparity_out = pipeline.createXLinkOut()
disparity_out.setStreamName("disparity")
stereo.disparity.link(disparity_out.input)

# Connect to device and start pipeline
with dai.Device(pipeline) as device:

    qRgb = device.getOutputQueue(name="rgb", maxSize=4, blocking=False)
    qDisparity = device.getOutputQueue(name="disparity", maxSize=4, blocking=False)

    while True:

        rgbFrame = qRgb.get().getCvFrame()  # blocking call, will wait until a new data has arrived

        dispFrame = qDisparity.get().getCvFrame()
        disparityMultiplier = 255 / stereo.initialConfig.getMaxDisparity()
        dispFrame = (dispFrame * disparityMultiplier).astype('uint8')
        dispFrame = cv2.applyColorMap(dispFrame, cv2.COLORMAP_JET)

        cv2.imshow("rgb", rgbFrame)
        cv2.imshow("disparity", dispFrame)

        if cv2.waitKey(1) == ord('s'):
          cv2.imwrite('rgb.png', rgbFrame)
          cv2.imwrite('disparity.png', dispFrame)
          print("files written")

        if cv2.waitKey(1) == ord('q'):
            break

Hi @FrancisTse8 ,
Could you run the rgb-depth apigment example code and share results (screenshot)? Just tried it with OAK-D-Lite and it works as expected. But perhaps is due to bad calibration - not sure.
Thanks, Erik

Hello Erik,
Wow, looks like alignment is great with the rgb-depth alignment code. Attached is a screen shot. So, my calibration on the OAK-D-Lite is off? How can I fix it?
Thanks,
Francis.

Hi @FrancisTse8 ,
This alignment also uses the calibration on the camera - so that's not the issue. I think that either your code, or you way of capturing photos is off. I would check both.
Thanks, Erik

Hello Erik,
After playing around with both the rgb-depth alignment code and my simple pipeline code, I think I now understand what is going on. For others who might come across the same issue, I will try to summarize what my understanding is. Please confirm if my understanding is correct.
When stereo.setDepthAlign(dai.CameraBoardSocket.RGB is specified, the disparity output is aligned with the image coming out of the isp. In the rgb-depth alignment example code, the isp output is THE_1080_p sensor output scaled by a factor of 2/3, which provides an rgb output image of size of 1280x720 as displayed by .imshow(). Since stereo.setDepthAlign(dai.CameraBoardSocket.RGB) was specified, the disparity image is aligned to this isp output and has a similar output size of 1280x720. And the blended image will show that the two output images are aligned as in my screen capture. BTW, to decrease the size of the disparity image to be handled, e.g., to do coordinate calculations on the host, specify something like stereo.setOutputSize(640, 360) to scale the disparity image by 1/2. Just make sure that the aspect ratio is the same as the sensor's.
Turned out that there were a couple misunderstandings in my part with my simple pipeline:

While I specified stereo.setDepthAlign(dai.CameraBoardSocket.RGB, I also specified stereo.setOutputSize(640, 400). My intention was that to have the disparity image scaled to 640x400 to match my preview image. Specifying a stereoDepth node output size with a 1:1.6 aspect ratio (while the sensor is at 1:1.777778) caused the disparity output to be scaled to a smaller size.
I cannot just set a preview size (like 640x400, that is a 1:1.6 aspect ratio) and hope to compare the preview image with the disparity image directly. The preview image will be cropped on the two sides.

Thanks,
Francis.

Hi @FrancisTse8 ,
Thanks for explaining the background, and I can confirm your understanding is correct:).
Closing this as it's solved.


ros2 bridge support

I have data in the ros2 format that I'd like to view with webviz.  I was able to connect webviz to my ros1 bridge (using ros1 data), but when I try to connect to the ros2 bridge (which has ros2 data), I get an error on the bridge server side:
$ ros2 run rosbridge_server rosbridge_websocket.py
registered capabilities (classes):
 - <class 'rosbridge_library.capabilities.call_service.CallService'>
 - <class 'rosbridge_library.capabilities.advertise.Advertise'>
 - <class 'rosbridge_library.capabilities.publish.Publish'>
 - <class 'rosbridge_library.capabilities.subscribe.Subscribe'>
 - <class 'rosbridge_library.capabilities.defragmentation.Defragment'>
 - <class 'rosbridge_library.capabilities.advertise_service.AdvertiseService'>
 - <class 'rosbridge_library.capabilities.service_response.ServiceResponse'>
 - <class 'rosbridge_library.capabilities.unadvertise_service.UnadvertiseService'>
[INFO] [rosbridge_websocket]: Rosbridge WebSocket server started on port 9090
[INFO] [rosbridge_websocket]: Client connected. 1 clients total.
[INFO] [rosbridge_websocket]: Client disconnected. 0 clients total.
[INFO] [rosbridge_websocket]: Client connected. 1 clients total.
[ERROR] [rosbridge_websocket]: [Client 1] [id: call_service:/rosapi/topics:1] call_service InvalidServiceException: Service /rosapi/topics
 does not exist

and an error on the web client side:
Error in fetching topics and datatypes
Service /rosapi/topics does not exist

I'm using the ubuntu package ros-dashing-rosbridge-server.  Please advise.

We currently don't support ROS2. And I don't know too much about it, but happy to chat with folks on how we could support it.

I guess I shouldn't close this since it is a good feature request that others might be interested in too!

so you can get this working by using the ros1_bridge for ROS2 and then the normal ROS 1 bridge package.  its a little cloogy but it works :+1:

so you can get this working by using the ros1_bridge for ROS2 and then the normal ROS 1 bridge package. its a little cloogy but it works +1

Can you elaborate on this? I'm new to ROS.  My web client is using the ros1 websocket protocol.  For example, I need to query the websocket server for /rosapi/topics and /rosapi/message_details.

so the ros2 to ros1 bridge is a little funky to get working properly.
you need to have sourced both the ros1 and ros2 setup.bash files you want to use (for me I used ros melodic and ros2 dashing).
let me try and outline it in a list...ill assume you have ros melodic and ros2 dashing installed in your /opt/ros directory.

Terminal 1 - source your ros 2 install if you havent already in your .bashrc and run the example talker node:

source /opt/ros/dashing/setup.bash
ros2 run demo_nodes_cpp talker

You should see it printing a counter going up with each message published.

Terminal 2 - source your ros 1 install and start up roscore:

source /opt/ros/melodic/setup.bash
roscore

Terminal 3 - source your ros 1 install and start up ros1 bridge:

source /opt/ros/melodic/setup.bash
roslaunch rosbridge_server rosbridge_websocket.launch

This will create a websocket for data to be passed to webviz through.

Terminal 4 - source both ros1 and ros2 installs and start up the ros1_bridge following these instructions from the ros1_bridge repo:

 source /opt/ros/dashing/setup.bash
source /opt/ros/melodic/setup.bash
ros2 run ros1_bridge dynamic_bridge

And now open up webviz like normal and tell it to listen to the websocket.....anddd hopefully you see the ROS2 demo node publishing its messages!
Hope this helps!

I think for a longer term vision of webviz it would make more sense to follow the progress of rclnodejs and once it has all or most of the features that webviz needs just have a forked version of webviz that uses that library instead.
not sure of the effort for this but my guess is it would be pretty high.....

Unfortunately internally in Webviz we're pretty tied to the ros1 binary message format, and we're going to lean on it more for performance improvements soon. So we'll have to figure that part out.

Btw @MaxwellGumley @flynneva, I'm trying to get to know our open source community better, and would love to learn more about what you use Webviz for. Could you perhaps shoot me an email at<EMAIL_ADDRESS>

@janpaul123 could you give an update on this? Much appreciated!

I'm not working on Webviz any more, sorry!

Thank you for the previous responses.
The described workarounds ROS2->ROS1->rosbridge->webviz work well, thank you.
Does anyone know if webviz works with the https://github.com/RobotWebTools/ros2-web-bridge?
Are you accepting Pull-Requests for Webviz? I am considering to enable communication with the rosbridge_suite of ROS2.
If you are no longer working on webviz, is it currently not maintained?

I'd suggest checking out https://foxglove.dev/

Thx for your fast response @janpaul123. Somehow, I missed the notification.
I am frequently using https://foxglove.dev/ and it is an amazing successor of webviz.
However, for the current project I need to be able to import a layout.json from a website into my visualiser.
While webviz supports this, afaik, in foxglove this can only be done by logging in and layouts are only shareable organization-wide.
Is there a setting in Foxglove's URL to load a specific layout.json which is hosted on a thirdparty host or to load a "publicly" shared layout via layout-id?

For questions about Foxglove Studio, please join our GitHub or Slack community: https://foxglove.dev/community  You can add your input on this ticket: https://github.com/foxglove/studio/issues/2792


WikiTree API

This is  a bug | feature request.

Prerequisites

[ ] Are you running the latest version?
[ ] Are you reporting to the correct repository?
(enso is made of many specialized packages: https://github.com/laravel-enso)
[ ] Did you check the documentation?
[ ] Did you perform a cursory search?

Description

Steps to Reproduce

Expected behavior

Actual behavior

Copied across, needs refactoring to Enso layout and improving features.

do you have access to wikitree?

Register a test account.


add a section about Retries of the staging actions

I prepared a section on how to manage the retrying of staging actions

Thank you @Slugger70

This looks good, thanks @gmauro! I think I'll integrate this into the hands-on portion in #2371 since it can only help improve reliability!


Add binary download location link to README.md

Updated primary README.md to include a link to the binary download location, for reader convenience.

Hi there, lesterw1. Thanks for your contribution. We already had a link to our downloads in the readme as-is, but arguably they may have been somewhat hard to find.

@zezha-msft and @JohnRusk what do you guys think about putting the download links more out in the open, rather than as a sidenote to a help article?

@adreed-msft I think it's fine!

👍


Completes tags when redoing

If you undo a tag completion and then try to redo it, less-than-slash will insert the rest of the tag despite that the redo has already inserted the rest of the tag, resulting in something silly like </div>div>. What's worse is that you lose your redo history since less-than-slash inserting text is the same as typing it in yourself.
We need to find a way to ensure that the event that triggered the completion wasn't a redo

Just came to report the same issue…

I've just gone to try and fix this bug but now I can't even reproduce it...
@luishdez could you explain exactly what inputs you made for this to occur?

open a new file
save as .html
in editor, type:
<div> </
less-than-slash finishes the tag, great:
`
`
I then use cmd+Z to undo, then I have:
<div> <
then cmd+shift+Z to redo, results in:
`
div>`
bonus:
to go further, undoing again from this point leaves you with:
<div> </di
and then redoing gets you:
<div> </di</div>
NOTE: This is all a rather trivial mess - easy to clean up - compared to the other what's worse issue @MarcoThePoro mentioned: less-than-slash overwrites your 'redo history'
Sometimes while coding I realize I changed/deleted something that I need back the way it was. I will undo SEVERAL steps, highlight and copy the old thing, and then redo all those steps to get back to my latest code with the old snippet in my clipboard ready to inject. I know this is risky (a single accidental keystroke will also erase your redo history) but sometimes it's the only/quickest option.


Windows - Importmulti RPC failed

I've followed the guide from the Ledger blog but I'm getting below error:

How do I proceed?

hey hi @Ekman what is your technical environment please? ty

same error while testing taproot, I am working on it.

Thank you. Sorry for not providing the info yet. If you still need me too I'll look into it tomorrow.

hi @Ekman I released 0.16.0 this morning, it is no longer using importmulti, can you please give it a try? thank you vm

Looks like it's working. Thank you!

Glad to hear that @Ekman ! Thank you.


httpx.ConnectError: [Errno 104] Connection reset by peer

Traceback (most recent call last):
File "/usr/local/lib/python3.10/site-packages/httpcore/_exceptions.py", line 10, in map_exceptions
yield

File "/usr/local/lib/python3.10/site-packages/httpcore/backends/sync.py", line 62, in start_tls
raise exc

File "/usr/local/lib/python3.10/site-packages/httpcore/backends/sync.py", line 57, in start_tls
sock = ssl_context.wrap_socket(

File "/usr/local/lib/python3.10/ssl.py", line 513, in wrap_socket
return self.sslsocket_class._create(

File "/usr/local/lib/python3.10/ssl.py", line 1071, in _create
self.do_handshake()

File "/usr/local/lib/python3.10/ssl.py", line 1342, in do_handshake
self._sslobj.do_handshake()

ConnectionResetError: [Errno 104] Connection reset by peer

Still working fine over here, are you using a proxy?

not any that i know of


Idea: Unlock remote machine via SSH

This is a proof of concept which contains a lot of ugly hacks and it's not intended to be merged.
I would like to use yubikey-full-disk-encryption to unlock a headless machine without the hassle of unplugging/plugging YubiKey. So inspired by the encryptssh hook from mkinitcpio-utils I'm using currently, here's a prototype that utilises SSH port forwarding to achieve this job.
Server-Side Requirements

nc from gnu-netcat
ss from iproute2
a patched mkinitcpio-dropbear (contains an upstream dss fix and a minor change to allow port forwarding)

dropbear (and netconf) needs to be pre-configured according to https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Remote_unlocking_(hooks:_netconf,_dropbear,_tinyssh,_ppp).
mkinitcpio hooks should look like:
HOOKS=(base udev autodetect keyboard keymap modconf block netconf dropbear ykfde filesystems fsck)

Client-Side Requirements

ncat from nmap
ykfde-ssh from this PR

Basically what it does is

Server fires up network and dropbear
Client uses ykfde-ssh Hostname and it:
1.1 starts ncat to listen on <IP_ADDRESS>:9000 and wait for the challenge
1.2 forwards <IP_ADDRESS>:9000 to Server
Server uses ss to detect whether <IP_ADDRESS>:9000 is open
Server uses nc to send the challenge to <IP_ADDRESS>:9000 and obtains the response

I've tested it in a virtual machine and it seems to work pretty smoothly. However the configuration does tend to be overly complex and I actually wonder whether there is a better way of doing this rather than using SSH port forwarding. But @agherzan if you feel comfortable about this idea I can then make some time to tidy it up and submit a proper PR.

Shall we close this PR for now?

Ah, sorry, got busy for a while then completely forgot about this. I still would like to finish this feature, but I can't give you a time frame right now. Is it ok? Or I'm also happy to submit another PR when I actually manage to wrap it up.

Take your time, we can wait 😄

That's absolutely alright. Just wanted to make sure it's still planned sometime in the future.

https://github.com/dracut-crypt-ssh/dracut-crypt-ssh/ does that


memory leak on Windows

In a Visual Studio Windows C++ command line project I get memory leaks for a simple client:
    sio::client s;
    s.connect("http://blah.haha");

These are defined:
#define ASIO_STANDALONE
#define _WEBSOCKETPP_CPP11_STL_
#define _WEBSOCKETPP_CPP11_FUNCTIONAL_

Using the latest client code with OpenSSL 1.1.1.m:
OPENSSL_VERSION_NUMBER=0x101010dfL
OPENSSL_API_COMPAT=0x101010dfL

I enable mem leak reporting by calling this:
void DetectMemoryLeaks()
{
    _HFILE hReportFile = _CRTDBG_FILE_STDERR;

    //Always check for memleaks in debug builds.
    // Calls _CrtDumpMemoryLeaks() on program exit.
    _CrtSetDbgFlag(_CRTDBG_ALLOC_MEM_DF | _CRTDBG_LEAK_CHECK_DF);

    //const int iReportMode = _CRTDBG_MODE_DEBUG | _CRTDBG_MODE_WNDW | _CRTDBG_MODE_FILE;
    int iReportMode = _CRTDBG_MODE_DEBUG | _CRTDBG_MODE_FILE;

    if (GetConsoleWindow() == nullptr)
        iReportMode |= _CRTDBG_MODE_WNDW;

    //Warning: (memleaks)
    _CrtSetReportMode(_CRT_WARN, iReportMode);
    _CrtSetReportFile(_CRT_WARN, hReportFile);

    //Errors:
    _CrtSetReportMode(_CRT_ERROR, iReportMode);
    _CrtSetReportFile(_CRT_ERROR, hReportFile);

    //Asserts:
    _CrtSetReportMode(_CRT_ASSERT, iReportMode);
    _CrtSetReportFile(_CRT_ASSERT, hReportFile);
}

The leaks I get are:
Detected memory leaks!
Dumping objects ->
{4353} normal block at 0x0000023D9CAB9F10, 48 bytes long.
 Data: <                > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
{4352} normal block at 0x0000023D9CB22D60, 64 bytes long.
 Data: <    =           > 10 9F AB 9C 3D 02 00 00 00 00 00 00 00 00 00 00
{4349} normal block at 0x0000023D9CB24E60, 264 bytes long.
 Data: <                > 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
{4348} normal block at 0x0000023D9CB24D80, 160 bytes long.
 Data: < `              > 80 60 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4347} normal block at 0x0000023D9CB24C30, 264 bytes long.
 Data: <i] +  BT'}   *d > 69 5D B6 2B F4 0B 42 54 27 7D 95 AD 96 2A 64 BA
{4346} normal block at 0x0000023D9CB24AE0, 264 bytes long.
 Data: <i] +  BT'}   *d > 69 5D B6 2B F4 0B 42 54 27 7D 95 AD 96 2A 64 BA
{4345} normal block at 0x0000023D9CB24A00, 160 bytes long.
 Data: <@d              > 40 64 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4344} normal block at 0x0000023D9CB24920, 160 bytes long.
 Data: < `              > 80 60 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4343} normal block at 0x0000023D9CB24760, 376 bytes long.
 Data: <            =   > 00 00 00 00 00 00 00 00 00 0E B2 9C 3D 02 00 00
{4342} normal block at 0x0000023D9CAB9420, 48 bytes long.
 Data: <                > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
{4341} normal block at 0x0000023D9CB225E0, 64 bytes long.
 Data: <    =           > 20 94 AB 9C 3D 02 00 00 00 00 00 00 00 00 00 00
{4338} normal block at 0x0000023D9CB24610, 264 bytes long.
 Data: <                > 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
{4337} normal block at 0x0000023D9CB24530, 160 bytes long.
 Data: < `              > 80 60 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4336} normal block at 0x0000023D9CB243E0, 264 bytes long.
 Data: <  ,     X =4 J  > A6 9C 2C BF F5 E0 F6 91 58 84 3D 34 EF 4A A2 80
{4335} normal block at 0x0000023D9CB24290, 264 bytes long.
 Data: <  ,     X =4 J  > A6 9C 2C BF F5 E0 F6 91 58 84 3D 34 EF 4A A2 80
{4334} normal block at 0x0000023D9CB241B0, 160 bytes long.
 Data: <@d              > 40 64 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4333} normal block at 0x0000023D9CB21DA0, 160 bytes long.
 Data: < `              > 80 60 A2 8F F7 7F 00 00 00 00 00 00 00 00 00 00
{4332} normal block at 0x0000023D9CB21650, 376 bytes long.
 Data: <            =   > 00 00 00 00 00 00 00 00 00 0E B2 9C 3D 02 00 00
{3536} normal block at 0x0000023D9CB0F720, 12 bytes long.
 Data: <            > 00 00 00 00 01 00 00 00 01 00 00 00
{3535} normal block at 0x0000023D9CB0FEA0, 520 bytes long.
 Data: <                > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Object dump complete.

Leaks can trigger break points when calling: _CrtSetBreakAlloc(3535);
The {3535} and {3536} leaks is triggered from context::context  from this source:
context::context(context::method m)
  : handle_(0)
{
    ::ERR_clear_error();

The {4332} leak is triggered from SSL_CTX_new in context::context from this source:
// Any supported TLS version.
#if (OPENSSL_VERSION_NUMBER >= 0x10100000L) && !defined(LIBRESSL_VERSION_NUMBER)
  case context::tls:
    handle_ = ::SSL_CTX_new(::TLS_method());

I'm linking against the static versions of OpenSSL:
libssl_static.lib
libcrypto_static.lib

The memory leaks do not occur when linked against the non-static versions of OpenSSL:
libssl.lib
libcrypto.lib

When the above libs are used the following DLLs must exist in the same location as the executable:
libcrypto-1_1-x64.dll
libssl-1_1-x64.dll

But this is what I'm trying to avoid, (having 3rd party DLLs).
So why does it leak for the static libraries of OpenSSL but not for the non-static libraries?

Forgot to mention I'm linking against the static versions of OpenSSL:
libssl_static.lib
libcrypto_static.lib

The memory leaks do not occur when linked against the non-static versions of OpenSSL:
libssl.lib
libcrypto.lib

When the above libs are used the following DLLs must exist in the same location as the executable:
libcrypto-1_1-x64.dll
libssl-1_1-x64.dll

But this is what I'm trying to avoid, (having 3rd party DLLs).
So why does it leak for the static libraries of OpenSSL but not for the non-static libraries?

This OPENSSL_thread_stop man page mentions in the notes that for statically linked versions OPENSSL_thread_stop should be called before exiting  a thread.
So now my question is where is the best place to call OPENSSL_thread_stop?

Just to be sure, the memory leak only happens if you are using TLS? If you are only building the non-TLS version do we have memory leaks?

How do I quickly test that?
I know for sure that its only when statically linking OpenSSL.

You can try linking your example against the non-TLS CMake target sioclient instead to the TLS version sioclient_tls and analyze the memory leak again.
If you are sure that it's only when statically linking OpenSSL I guess then it's already only for the TLS version as OpenSSL is not required for the non-TLS version.
Now, for the OPENSSL_thread_stop I'm not sure which is the best place to call it since we actually don't make any calls to OPENSSL. It's actually the asio library the one that uses OPENSSL and we use the TLS calls from the library. Maybe we could try updating the library version

I tried updated the asio library, but the leak still occurs.

I see, then I suspect that either:

We are not using the asio library properly.
The asio library has the memory leak and we should report it there.

My intuition tells me that 1 is probably the cause since the asio library is quite popular and other people would've found the memory leak as well. So, we would need to check whether our usage of the asio library is correct. I'm not an expert of the asio library so help would be welcome here.

I suspect this is the reason for the leak:

This OPENSSL_thread_stop man page mentions in the notes that for statically linked versions OPENSSL_thread_stop should be called before exiting a thread.


Error trying to apply a filter

I am trying to implement a filter and I keep getting an error trying to apply the catalog.
Error message:
Error: /Stage[main]/Profiles::Sensu/Sensu::Handler[slack]/Sensu_handler[slack]/filters: change from  to maint_filter failed: undefined method `sort' for nil:NilClass
Filter declaration:
sensu::filter { 'maint_filter':
  attributes => { 'maint' => 'false' },
}

Handler declaration:
sensu::handler { 'slack':
  command => 'slack.rb',
  source  => 'puppet:///modules/profiles/sensu/handlers/slack.rb',
  config  => {
    'webhook_url' => '***FILTERED**',
    'channel'     => '#sensu',
  },
  mutator => 'maint_mode',
  filters => ['maint_filter'],
}

Any help would be greatly appreciated.

Snap! Dupe of #374 I think :)

Oops. I did not see that issue already open.


Checking PR builds not triggering for forks

CI checks for PRs from forks are not executing or are not reported properly. After submitting the PR, the status remains at

Expected — Waiting for status to be reported

Branches from members in the Github repo are unaffected.

My process is to push the fork to origin, this will trigger the CI and the checks will run automatically.

@svengabr
Just to be clear: this is your process on the receiving side of a pull request from a fork and not something I need to do differently as a submitter from a fork? Correct?

@svengabr I can do this, but outside contributors can't. For them, it's also more crucial that we can check the build for errors because otherwise I would have to clone and check their fork locally.

Fixed in #601


REPL prints multiple repeated lines if window is too skinny, in pkg mode

Please search existing issues to avoid duplicates.
Details

Atom version: 1.32.1
Julia version: v1.0.1
OS: Mac OS X
Package versions:

Atom.jl:  0.7.9
julia-client: 0.7.9
ink: 0.9.12

Steps to reproduce

Make REPL window skinny
Hit ]
start typing

So one solution to that would be to provide a minimal width for the REPL and show a scrollbar -- is that what you'd want as a solution to this as well?

A scrollbar is also fine, or even the old behaviour where the word was spread down.
This is definitely a "bug", not an "enhancement" as the current behaviour makes it unusable.

Oh right, I kinda misread that. Do you know with which version upgrade this regressed?

Not precisely, it happened after I updated yesterday.

It's not just pkg mode, and this has been around for a long time. I thought there was already an issue on it?

this is what it looks like for me:


Build with clang instead of gcc

We may be hitting a compiler bug that is causing segfaults in production so see if switching compilers makes the problem go away.

Error: Failed to CreateArtifact: Received non-retryable error: Failed request: (409) Conflict: an artifact with this name already exists on the workflow run

Not a seamless upgrade then :facepalm:

@bnoodrhuis You don't have to change build-libv8, just make clang available (e.g in Dockerfiles) and it'll favour clang over GCC.There are a couple of commits before that tried that.On 13 Sep 2024, at 20:22, Ben Noordhuis @.***> wrote:We may be hitting a compiler bug that is causing segfaults in production so see if switching compilers makes the problem go away.
You can view, comment on, or merge this pull request online at:
  https://github.com/rubyjs/libv8-node/pull/61
Commit Summary
14d0459  Build with clang instead of gcc
File Changes  (1 file)
M
libexec/build-libv8
(2)

Patch Links:
https://github.com/rubyjs/libv8-node/pull/61.patch
https://github.com/rubyjs/libv8-node/pull/61.diff
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

yeah @lloeki coaxing this to use clang is not super easy... I thing platform also insists on using GCC here:
https://github.com/rubyjs/libv8-node/blob/7249c5d4ddedea049fa2b8005bd89877ad570887/libexec/platform#L100-L107
We may need to edit this as well ... I changed the container now ... but looking at build log from previous commit ... no clang yet
May change these lines next

We may need to edit this as well ... I changed the container now ... but looking at build log from previous commit ... no clang yet

It's curious how it uses clang++ for some things and ccache x86_64-linux-gnu-g++ for others. I'll look into it.


Update to get rid of sensitive file warning from terraform

what

Updated to local_sensitive_file resource, changed provider versions.

why

This removes a terraform warning

/test all

@brunzefb Thanks for the contribution! Released as https://github.com/cloudposse/terraform-aws-key-pair/releases/tag/0.18.3

@Gowiem I believe this should have been a major release instead of a patch.
Reasoning:

the underlying providers where revved major versions.
aws from 2 to 3
local from 1 to 2

Background:

I use renovatebot and make merge decisions based on semver and tests and changelog. Thankfully my tests caught this.

I believe 1.18.3 should be removed and 2.0.0 be created in its place or a note should be placed on 1.18.3 indicating it's a breaking change and create a 2.0.0 as well.
Thoughts?

@ekristen Good catch. Few things:

Cloud Posse has been avoiding major releases across all our modules similar to how Terraform was managed prior to v1.0 -- We believe we haven't reached a stable 1.0 release for our modules yet since Terraform wasn't 1.0.
That said, I could see this being a minor version bump instead of a patch which would get us closer to what you're thinking.
Lastly, I shouldn't have allowed the AWS provider version bump as it's unnecessary: This doesn't change our AWS provider functionality so therefore there is no reason to block usage of the 2.x AWS provider.

Considering that I will make some updates later today to push out a 0.19 release which reverts the 3.x requirement. I'll also leave a note on the release of 1.18.3. More to come later today -- Thanks for surfacing so quickly.


⚠ Bofrost.at has degraded performance

In 468a0b8, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2069 ms

Resolved: Bofrost.at performance has improved in eea7c71.


Update prompt-toolkit to 1.0.15

I'm noticing that prompt-toolkit==0.57 breaks my ipython==5.3.0 installation (for python 3 at least). Bumping the prompt-toolkit version fixes this, the tests run and cycli seems to work as expected.
PS Thanks for the great tool 👍

Should neokit submodule and invocation updates be in a separate pull request?

I've made a couple of separate PRs addressing a couple of issues I spotted. Bit puzzled how the tests were passing [I would have expected them to fail before #57] , but I can run and use locally.

I think the tests are not being run at all. There is no output on Travis.

Can you separate the update to prompt toolkit into its own PR?


Use the parsed request body rather than ctx.body

The Koa adapter is incorrectly using the response body (ctx.body) instead of the request body (ctx.request.body).

Thanks for this PR! Can you please rebase and fix the failing lint+type checks?

@enisdenjo it should be fixed now. Thanks!

Thank you @jmurzy, great work!

:tada: This PR is included in version 1.22.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Error in MySQL wrapPacket()

This error happens when a discovered attack from MySQl port (from a ping) is logged. I have not found the root cause yet, although this issue does not affect the log record.

Issue fixed by @irinil . There is no error with wrapPacket()


Community contribution required: Typescript Compilebreak after updating from nodejs 8 to 12

We used sanitize-html in a typescript project with node 8.
After upgrading to node 12, the following typescript compilebreaks occurr in sanitize-html and its dependencies:
node_modules/@types/domutils/index.d.ts:6:10 - error TS2614: Module '"../../../../../node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../node_modules/domhandler/lib"' instead?

6 import { DomElement } from "domhandler";
           ~~~~~~~~~~

node_modules/@types/htmlparser2/index.d.ts:17:10 - error TS2614: Module '"../../../../../node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../node_modules/domhandler/lib"' instead?

17 export { DomElement, DomHandlerOptions, DomHandler, Element, Node } from 'domhandler';

node_modules/@types/sanitize-html/index.d.ts:17:10 - error TS2305: Module '"../../../../../node_modules/htmlparser2/lib"' has no exported member 'Options'.

17 import { Options } from "htmlparser2";

In the package.json, we are using
"sanitize-html": "^1.20.1",

and
"@types/sanitize-html": "^1.20.2",

for the typings.
Could anyone else update successfully to node 12?
Side-note - maybe it helps:
It seems the dependency htmlparser2 was ported to typescript in https://github.com/fb55/htmlparser2/commit/759b1220c03e55a895f971deab9f1e94c30a7f61 which was released in https://github.com/fb55/htmlparser2/releases/tag/v4.0.0. Still sanitize-html pulls in "htmlparser2": "^3.10.0", as dependency.

I just noticed that domhandler 3.0.0 is also typescript and therefore those types are used instead of @types/domhandler because domutils 2.0.0 pulls in domhandler ^3.0.0.
So since another dependency pulls in htmlparser2 4.0.0 that pulls in domutils ^2.0.0, domhandler ^3.0.0 is pulled in which overwrites the domutils 1.7.0 version pulled in parallel by sanitize-html.
So I think if sanitize-html would also upgrade the htmlparser2 dependency to ^4.0.0, the issue would be solved.

I've opened an issue asking for some information as to what bc breaks, if
any, come with htmlparser2 4.0.0.
On Fri, Dec 27, 2019 at 5:19 AM ceisele-r<EMAIL_ADDRESS>wrote:

I just noticed that domhandler 3.0.0 is also typescript and therefore
those types are used instead of @types/domhandler because domutils 2.0.0
pulls in domhandler ^3.0.0.
So since another dependency pulls in htmlparser2 4.0.0 that pulls in domutils
^2.0.0, domhandler ^3.0.0 is pulled in which overwrites the domutils 1.7.0
version pulled in parallel by sanitize-html.
So I think if sanitize-html would also upgrade the htmlparser2 dependency
to ^4.0.0, the issue would be solved.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/sanitize-html/issues/320?email_source=notifications&email_token=AAAH27OEE6TUVCILQT723F3Q2XJCBA5CNFSM4J7ZNCY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHW6QTQ#issuecomment-569239630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27JJZDAKAFFWR7KCOH3Q2XJCBANCNFSM4J7ZNCYQ
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

I did upgrade to htmlparser2 4.x, and it works great and all tests pass etc., but one user has reported a similar issue since the upgrade. I need a simple procedure to reproduce this issue. Ideally a failing test case PR.

The upgrade doesn't look like it enforces htmlparser2 4.x, the relevant line of code is:
https://github.com/apostrophecms/sanitize-html/blob/master/package.json#L30

Whoops, somehow didn't push master after publishing, fixed.
On Mon, Feb 24, 2020 at 5:49 PM David Mattia<EMAIL_ADDRESS>wrote:

The upgrade doesn't look like it enforces htmlparser2 4.x, the relevant
line of code is:
https://github.com/apostrophecms/sanitize-html/blob/master/package.json#L30
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/sanitize-html/issues/320?email_source=notifications&email_token=AAAH27OJXKL7MGSOZQ47METRERFGRA5CNFSM4J7ZNCY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZ2W5Q#issuecomment-590588790,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27OZ2O47KLFA3RLC23DRERFGRANCNFSM4J7ZNCYQ
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

This is still broken for me, post upgrade I see the following issues:
ERROR  Failed to compile with 3 errors

 error  in<EMAIL_ADDRESS>
ERROR in /test-project/node_modules/@types/domutils/index.d.ts(6,10):
6:10 Module '"../../../../../../../test-project/node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../../../test-project/node_modules/domhandler/lib"' instead?
    4 | // Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped
    5 |
  > 6 | import { DomElement } from "domhandler";
      |          ^
    7 | /***
    8 |  * Append an element after another
    9 |  *

 error  in<EMAIL_ADDRESS>
ERROR in /test-project/node_modules/@types/htmlparser2/index.d.ts(17,10):
17:10 Module '"../../../../../../../test-project/node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../../../test-project/node_modules/domhandler/lib"' instead?
    15 | import { DomHandler } from 'domhandler';
    16 | import * as DomUtils from 'domutils';
  > 17 | export { DomElement, DomHandlerOptions, DomHandler, Element, Node } from 'domhandler';
       |          ^
    18 |
    19 | export interface ParserOptions {
    20 |

 error  in<EMAIL_ADDRESS>
ERROR in /test-project/node_modules/@types/sanitize-html/index.d.ts(18,10):
18:10 Module '"../../../../../../../test-project/node_modules/htmlparser2/lib"' declares 'Options' locally, but it is not exported.
    16 | ///<reference types="htmlparser2"/>
    17 |
  > 18 | import { Options } from "htmlparser2";
       |          ^
    19 |
    20 | export = sanitize;
    21 |

  [=========================] 100% (completed)

 WEBPACK  Failed to compile with 3 error(s)

Error in<EMAIL_ADDRESS>
  ERROR in /test-project/node_modules/@types/domutils/index.d.ts(6,10):
  6:10 Module '"../../../../../../../test-project/node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../../../test-project/node_modules/domhandler/lib"' instead?
      4 | // Definitions: https://github.com/DefinitelyTyped/DefinitelyTyped
      5 |
    > 6 | import { DomElement } from "domhandler";
        |          ^
      7 | /***
      8 |  * Append an element after another
      9 |  *

Error in<EMAIL_ADDRESS>
  ERROR in /test-project/node_modules/@types/htmlparser2/index.d.ts(17,10):
  17:10 Module '"../../../../../../../test-project/node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../../../test-project/node_modules/domhandler/lib"' instead?
      15 | import { DomHandler } from 'domhandler';
      16 | import * as DomUtils from 'domutils';
    > 17 | export { DomElement, DomHandlerOptions, DomHandler, Element, Node } from 'domhandler';
         |          ^
      18 |
      19 | export interface ParserOptions {
      20 |

Error in<EMAIL_ADDRESS>
  ERROR in /test-project/node_modules/@types/sanitize-html/index.d.ts(18,10):
  18:10 Module '"../../../../../../../test-project/node_modules/htmlparser2/lib"' declares 'Options' locally, but it is not exported.
      16 | ///<reference types="htmlparser2"/>
      17 |
    > 18 | import { Options } from "htmlparser2";
         |          ^
      19 |
      20 | export = sanitize;
      21 |

 ERROR  mochapack exited with code 1.
error Command failed with exit code 1.

Still have the same issue on my end too.

This is also broken for us (https://github.com/matrix-org/matrix-appservice-irc/issues/1003)

Same here, have to use custom / very simplified typeings for now.

Same for me.

We do not use typescript in house, so this will need to be resolved by a community contributor who is familiar with it. We are waiting for a PR, in other words. Thank you for verifying the issue — but past this point please do not add "me too" comments until there is some indication that an attempt has been made to resolve the issue.

I've made a PR to @types/sanitize-html https://github.com/DefinitelyTyped/DefinitelyTyped/pull/43870, which should resolve the issue with htmlparser2 types.

That's great! Since we don't use TypeScript in-house, would someone please check out the PR from @dsyncerek and confirm that it does in fact solve the problem for them as well? cc @kieusonlam @vladimiry @Half-Shot @burtonator

Actually it sounds like there might not be anything to do on our end?

yes, only @types/sanitize-html needs adjustments, as the htmlparser2 v4 has been rewritten to TypeScript, so it uses own typings instead of community @types/htmlparser2.

Until @dsyncerek DefinitelyTyped PR is merged I have solved the issues by fixing the dependencies to these versions:
{
    ...
    "sanitize-html": "1.21.0",
    "@types/sanitize-html": "1.20.2",
    "@types/node": "10.17.21"   //12.12.6 for node 12
    ...
}

PR is merged now 🎉

Thanks @dsyncerek , I can confirm its working not in 1.23.0 with types in 1.23.0.

👍
On Mon, Apr 27, 2020 at 1:53 AM ceisele-r<EMAIL_ADDRESS>wrote:

Closed #320 https://github.com/apostrophecms/sanitize-html/issues/320.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apostrophecms/sanitize-html/issues/320#event-3274084821,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAH27J75ARQHQBBNWXFOODROUMWVANCNFSM4J7ZNCYQ
.

--
THOMAS BOUTELL | CHIEF TECHNOLOGY OFFICER
APOSTROPHECMS | apostrophecms.com | he/him/his

Good Afternoon: I tried everything on this thread still having this problem:
node -v
v15.0.1
"dependencies": {
"@apollo/react-hooks": "^3.1.3",
"apollo-cache-inmemory": "^1.6.5",
"apollo-client": "^2.6.8",
"apollo-link": "^1.2.14",
"apollo-link-context": "^1.0.20",
"apollo-link-http": "^1.5.16",
"classnames": "^2.2.6",
"graphql": "^14.6.0",
"graphql-tag": "^2.10.3",
"jsonwebtoken": "^8.5.1",
"lodash-es": "^4.17.15",
"mid-common": "workspace:",
"react": "^16.12.0",
"react-apollo": "^3.1.3",
"react-dom": "^16.12.0",
"react-router": "^5.1.2",
"react-router-dom": "^5.1.2",
"sanitize-html": "^2.0.0",
"semantic-ui-react": "^2.0.0"
},
"devDependencies": {
"@types/classnames": "2.2.10",
"@types/eslint": "6.1.8",
"@types/jest": "^26.0.15",
"@types/jsonwebtoken": "8.3.9",
"@types/lodash-es": "4.17.3",
"@types/react": "^16.9.19",
"@types/react-dom": "^16.9.7",
"@types/react-router": "5.1.4",
"@types/react-router-dom": "5.1.3",
"@types/sanitize-html": "1.27.0",
"apollo": "^2.22.0",
"current-git-branch": "^1.1.0",
"eslint": "^6.8.0",
"jest": "^26.6.1",
"minimatch": "^3.0.4",
"ts-jest": "^23.10.5"
},
"jest": {
"transform": {
"^.+\.tsx?$": "ts-jest"
},
"testRegex": "(/tests/.|(\.|/)(test|spec))\.(jsx?|tsx?)$",
"moduleFileExtensions": [
"ts",
"tsx",
"js",
"jsx",
"json",
"node"
]
}
}
ERROR:
TS2614: Module '"../../../../../../../Desktop/workflow-ui/node_modules/domhandler/lib"' has no exported member 'DomElement'. Did you mean to use 'import DomElement from "../../../../../../../Users/a-zhaque/Desktop/workflow-ui/node_modules/domhandler/lib"' instead?

@zhaque44 That error doesn't look like it's referencing this package.

I still get the error
node_modules/dom-serializer/lib/index.d.ts:1:13 - error TS1005: '=' expected.

 import type { Node } from "domhandler";

in the typecheck step tsc -p tsconfig.json --noEmit
I'm using "^2.1.2" version of sanitize-html with "@types/sanitize-html": "^1.27.0". Also "@types/node": "8.10.36", as dependency. Does any one have a clue?
Thanks in advance.

I'm facing the same problem
Node version: 12.18.3

"sanitize-html": "^2.1.2",
"@types/sanitize-html": "^1.27.0",
"typescript": "~3.7.2",
"@types/node": "^12.0.0",
"react": "^16.13.1",

<EMAIL_ADDRESS>
TypeScript error in /app/node_modules/@types/sanitize-html/node_modules/dom-serializer/lib/index.d.ts(1,13):

'=' expected.  TS1005

import type { Node } from "domhandler";
                   ^
export interface DomSerializerOptions {
   emptyAttrs?: boolean;
   selfClosingTags?: boolean;

Are these not issues coming from @types/sanitize-html's wrapper? We don't use or maintain the typescript version ourselves.


[FEAT] Localisation

Is your feature request related to a problem? Please describe.
Describe the solution you'd like
Instead of direct names to search for in the macro, will use the correct localised name instead

 Localization


Terminal

Hi!
I discover your docker in BraincHack Bilbao  (thanks to Asier and Ibai ;) ).
I have installed docker and all tools operating, but files and directories I transferred from my local machine (with docker run -it -v <host_path>:<guest_path> dockerfile/neuro) appear in black in the terminal (Basic, Homebrew, Gras....all of them). Attached is a snapshot show them.

Do you know how can I solve that?
Thank you!!
<EMAIL_ADDRESS>OSX 10.11.6

Hi @josepman,
I have never seen that problem. What Terminal app are you using? Have you tried using another?
I don't think it is something caused by the container OS, I am not sure. :/

Hi @alexsavio ,
I don't know what it happened. I just tried with iTerm and this problem was solved.
Another issue to your concern is the possibility to include Octave (or Matlab for personal use) in this container. We have commands from Octave in some scripts that we can't use.
Thank you!

Hi,
Yes, you could also install octave if you wish. The script is already installing the Matlab compiler runtime MCR to run SPM12.
I wanted to keep things small as possible, although the container is quite large still.
Octave would add another gigabyte, wouldn't it? :/


[Enhancement] Disable registration

It will be useful for private SMPs when all players have already registered.
Other players can't register unless they've already registered once.

This kind of sounds like a different use-case alltogether. You'd probably want a more advanced whitelist type of system.
I'll think about it though, maybe there is something I can add that makes this possible.


SPT-4113 History app update

Enabled grabbing proper application revision when creating history field revisions.  Will prevent ValueErrors when accessing old values that no longer exist.

Closing in favor of https://github.com/swimlane/swimlane-python/pull/59


Add CRE (catch rate estimates)

Not sure how to do this yet, nor if there is a reliable enough source of data for this. But decided to open this issue to keep it in mind if I find a way.
Horntracker data comes to mind. Needs more research if it's available for use.

added horntracker links for now

made my own data collection browser extension, database, and site to display it. Slowly but surely collecting data and integrating.


[ENH] Suppress warning message when applying Non-Standard Evaluation

Feature Type

[ ] Adding new functionality to datar

[X] Changing existing functionality in datar

[ ] Removing existing functionality in datar

Problem Description
The code below
    import datar.all as d
    import pandas as pd
    new_name = "y"
    pd.DataFrame(dict(x=[2])) >> d.rename(**{new_name: 'x'})

generates the following warning message:
c:\Users\me\miniconda3\envs\cenv\lib\site-packages\pipda\utils.py:89: PipeableCallCheckWarning:
Failed to detect AST node calling `rename`, assuming a piping call.

Feature Description
Being able to suppress the warning message above.
Additional Context
No response

Could you also indicate the environment where you were running the code? i.e. python script, jupyter, python REPL, etc

For sure @pwwang , I'm using in a .py file in VScode (via its Interactive Window, which uses jupyter kernel).

I can run it with no problem:

here is the version info:
Version: 1.74.3 (system setup)
Commit: 97dec172d3256f8ca4bfb2143f3f76b503ca0534
Date: 2023-01-09T16:59:02.252Z
Electron: 19.1.8
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.25276
Sandboxed: No

vscode-jupyter: v2022.11.1003412109

The problem was indeed with VScode, I updated it to the last version and that warning message disappeared, thank you @pwwang .

@pwwang , I checked that the issue was solved only for python 3.8 (after I updated datar and restarted VScode).
All conda environments I tested with python 3.9 or 3.10 that message appears, even directly in the command prompt (without VScode and ipython), it's very weird...

Steps to reproduce the issue.
Go to Windows OS powershell and type:
conda create --name py3.9 python=3.9
conda activate py3.9
pip install datar[pandas]
python

Then run:
    import datar.all as d
    import pandas as pd
    new_name = "y"
    pd.DataFrame(dict(x=[2])) >> d.rename(**{new_name: 'x'})

It will display this message:
C:\Users\me\miniconda3\envs\py3.9\lib\site-packages\pipda\utils.py:89: PipeableCallCheckWarning: Failed to detect AST node calling `rename`, assuming a piping call.
  warnings.warn(

This is expected.
There is some description here: https://pwwang.github.io/pipda/piping/#fallbacks-when-ast-node-detection-fails
Tracing executing node is not available in the raw python REPL.
How about ipython or bpython?

I could not install bpython to test, but with ipython the same issue occurs and since VScode relies on ipython for its Interactive Window, it inherits the same behavior.

Maybe an option to temporarily silent that message would suffice as a workaround

Awesome, __ast_fallback="piping" works.

Could you provide datar.get_versions() and also the version of your python?

For sure:
python      : 3.9.16 (main, Jan 11 2023, 16:16:36) [MSC v.1916 64 bit (AMD64)]
datar       : 0.11.1
simplug     : 0.2.2
executing   : 1.2.0
pipda       : 0.11.0
datar-numpy : 0.1.0
numpy       : 1.24.1
datar-pandas: 0.2.0
pandas      : 1.5.2

The python version installed on my Windows OS is 3.9.4.

Sorry, I meant ipython.

pipda v0.11.1 was just released. With it, you can change the default fallback of a verb:
# importing ...
d.rename.ast_fallback  = "piping"
# So you don't need to pass "__ast_fallback" to every call
new_name1 = 'y'
new_name2 = 'z'
pd.DataFrame(dict(x=[2])) >> d.rename(**{new_name1: 'x'})
pd.DataFrame(dict(x=[2])) >> d.rename(**{new_name2: 'x'})

pipda v0.11.1 was just released. With it, you can change the default fallback of a verb:

Very nice to know.

Sorry, I meant ipython.

The ipython version is 8.8.0

Looks like the only difference is the platform. I can reproduce the issue on Windows. The snapshot I took was on Linux (WSL).
I'll dig deeper to see if there is a fix.

Great, at least now we know the root cause.


Initializing variable as  typeof at runtime

I want to be able at runtime to initialize some variables types as same as  inputvalue to method, where input is an integer that can be Int32|64, UInt32|64, or BigInt
Ex
def methodx (end_num)
   k = 0.as(typeof(end_num))
   ...
end

But I get this error
in primesutilstesty1a.cr:257: can't cast Int32 to Int64

          k = 0.as(typeof(end_num))

According to docs -- https://crystal-lang.org/docs/syntax_and_semantics/typeof.html -- shouldn't this work?

typeof works as inspected, but as doesn't change the inherent datatype, it just tries to treat the value as that type but the compiler complains if this is not possible. You can't treat an Int32 as an Int64 because they're completely different types with different memory layout.  See https://crystal-lang.org/docs/syntax_and_semantics/as.html
For your use case, you probably need to convert the value from one type to the other.  If this is just about converting number types, you use the regular contstructors: typeof(end_num).new(0). Every number type even has a .zero method, so your example could just be typeof(end_num).zero.
All this obviously doesn't work if end_num is a union type.

If it's a union you can do end_enum.class.zero

Yes, this works: k = typeof(end_num).zero
Thanks :-)
May I recommend including this use of typeof in the documentation for that section, as it would have instructed me on the proper way to use it initially.

@jzakiya It's probably a good idea. Please send a PR to https://github.com/crystal-lang/crystal-book . Thanks!


search-suggestions: Remove is:dm suggestion from get_operator_suggestions

Fixes: https://github.com/zulip/zulip/issues/30320
Currently, there are 2 lists of filterers

one for non-spectators (here)
one for spectators (here)

When you type is: in the search bar as a spectator, it currently suggests "Direct messages" (Issue 30320) because get_operator_suggestions is adding the suggestion.
This PR

Removes the is:dm suggestion from get_operator_suggestions

And since get_is_operator_suggestions doesn't apply to spectators, we no longer suggest "Direct messages" when the user searches "is:" (see screenshot)
For non-spectators, the is:dm suggestion will be populated from get_is_filter_suggestions

Alternatives considered

You can add something like visible_to_spectators on the Suggestion object. This would fix the core problem that suggestions that spectators can't access still appear to them.

Why I didn't implement this: In some cases, you might want the suggestion to appear still, I wasn't sure. In any case, when the user clicks the suggestion, they'll see the modal prompting them to login to access more features.

Screenshots and screen captures:

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[x] Explains differences from previous plans (e.g., issue description).
[x] Highlights technical choices and bugs encountered.
[x] Calls out remaining decisions and concerns.
[x] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[x] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Thanks for the PR @joyhchen! @pratik-pc would you be up for reviewing this? I think you've been working in that code path recently.

@pratik-pc moved the code to get_is_filter_suggestions

This looks good to me now
@timabbott I think this is ready now

@pratik-pc Have you manually tested this PR?

The commit message isn't properly formatted. Check out our GitHub guide and commit guidelines for more details.

Merged, thanks @joyhchen and @pratik-pc, after testing manually and rewriting the commit message.
I think this may not be the best possible implementation, though; it feels like the ideal setup would be for us to be able to declare private as an alias in this declaration, and have the search system take care of it from there.
    const suggestions = [
        {
            search_string: "is:dm",
            description_html: "direct messages",
            incompatible_patterns: [
                {operator: "is", operand: "dm"},
                {operator: "is", operand: "resolved"},
                {operator: "channel"},
                {operator: "dm"},
                {operator: "in"},
            ],
        },


Login Page need beter look

Description
The login page need beter look
https://narayan954.github.io/dummygram/login
Screenshots

Additional information
No response

Yes @suman-tewary you're correct. How'd you like to improve it? Also, would you be working on both login and signup page or only login page for now?

@narayan954  hey i will add a new form with  great styling or i will done this using material-ui/chakra-ui for enhancing it . Please assign this to me under jwoc .

@narayan954 hey i will add a new form with great styling or i will done this using material-ui/chakra-ui for enhancing it . Please assign this to me under jwoc .

that's good, but @suman-tewary has already claimed the issue. If she doesn't reply before tonight, you can claim the issue.

I want to work on this issue under JWOC

Yes @suman-tewary you're correct. How'd you like to improve it? Also, would you be working on both login and signup page or only login page for now?

It would be better to create another issue for the signup page.
Please assign both of the issues and I will fix them by today.

Yes @suman-tewary you're correct. How'd you like to improve it? Also, would you be working on both login and signup page or only login page for now?

It would be better to create another issue for the signup page. Please assign both of the issues and I will fix them by today.

okay, but you can only be assigned on one issue at a time, so after completing this issue, you can open other issue and get assigned.

Yes @suman-tewary you're correct. How'd you like to improve it? Also, would you be working on both login and signup page or only login page for now?

It would be better to create another issue for the signup page. Please assign both of the issues and I will fix them by today.

okay, but you can only be assigned on one issue at a time, so after completing this issue, you can open other issue and get assigned.

ok, do it

Yes @suman-tewary you're correct. How'd you like to improve it? Also, would you be working on both login and signup page or only login page for now?

It would be better to create another issue for the signup page. Please assign both of the issues and I will fix them by today.

okay, but you can only be assigned on one issue at a time, so after completing this issue, you can open other issue and get assigned.

ok, do it

you're assigned already, is there anything else?


Upload via Remote Server (BETA)

This new feature is an awesome idea!
But I found two little issues:

it is unclear if you have to provide the public or private key. You might want to explicitly use "private key" instead of only "key" in the interface
the input text field says in gray<EMAIL_ADDRESS>(which is also a very good idea to guide the user), but I think it must be "scp://user@server.com:/folders/", i.e. a ":" between URL and path.

Thanks! For:

Good idea
I think the code actually expects<EMAIL_ADDRESS>vs "scp://user@server.com:/folders/", could you confirm?

@2) both works, i.e. with or without ":", but I think with ":" is more in line with the traditional scp command in the terminal

Thanks, good to know ... and you are right on more traditional ...


feat: add a feature of whitelist for /lbm.foundation.v1.MsgWithdrawFromTreasury

Description

closes: #527
Motivation and context

Refer to #527.
Checklist:

[x] I followed the contributing guidelines and code of conduct.
[x] I have added a relevant changelog to CHANGELOG.md
[x] I have added tests to cover my changes.
[ ] I have updated the documentation accordingly.
[x] I have updated API documentation client/docs/swagger-ui/swagger.yaml

Blocked by #518.


Fix header

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 96.75%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
387

Relevant Lines:
400

💛  - Coveralls


Demo: Tigris returns an error on delete

Description
This is a draft PR to demonstrate an error with delete:
Code: Code_DEADLINE_EXCEEDED (4)
Message: invalid character '\x1f' in string literal

Readiness checklist

[ ] I added tests for new functionality or bugfixes.
[ ] I ran task all, and it passed.
[ ] I added/updated comments for both exported and unexported top-level declarations (functions, types, etc).
[ ] I checked comments rendering with task godocs.
[ ] (for maintainers only) I set Reviewers, Assignee, Labels, Project and project's Sprint fields.
[ ] I marked all done items in this checklist.

Close the PR as it was created to scope/demostrate the problem.


chore(*): layer-db tracks function execution

This PR makes layer-db track function execution in func_runs() and
func_run_logs() tables. It also removes the following concepts:

Func Bindings
Func Binding Return Values
Func Executions
Actions v1

We have not cleaned up the old standard model tables, but other than
that, we're gtg.

bors try

The main issue I see here is that a failed action will still set a resource prop - it's empty but it's still set nonetheless and therefore the component can never be deleted

bors cancel

bors try

bors merge


Stripe apps CLI stuck on "Waiting for confirmation..." even after accepting terms

Describe the bug
Stripe apps CLI stuck on "Waiting for confirmation..." even after accepting terms
To Reproduce
Steps to reproduce the behavior:

Run stripe apps create hello-world
Copy the URL to accept terms and paste on the browser
Accept Stripe apps terms and conditions on the browser
CLI still showing "Waiting for confirmation..."

Expected behavior
CLI should continue after terms is accepted
CLI

Stripe apps plugin: 1.2.0
Stripe CLI: 1.8.11

@htheodore-stripe That workaround didn't work for me. Still have the same issue.

@htheodore-stripe @svenugopal-stripe any update on this? I was excited to try the new app platform but stuck at the first step.

@hrishimittal thanks for following up on this. I've a potential fix for this. Before that I've a couple of questions..What is the OS env you are trying this on and also can you please share your account id I'll check if the that account id has already accepted the Terms ?

macOS Catalina 10.15.5
Google Chrome Version 101.0.4951.64 (Official Build) (x86_64)
My account email id is<EMAIL_ADDRESS>

Thanks for the response. Could you please try with the latest version of the plugin.( >=  1.2.1)
you can upgrade the stripe plugin
 stripe plugin upgrade apps
 stripe apps --version # should return 1.2.1

Also the URL to accept terms looks like this. Please substitute your stripe account id.
https://dashboard.stripe.com/apps/accept-terms?cliaccount=<acct_xxxxxxxxxx>
Before Accepting..

After accepting

@svenugopal-stripe I followed all those steps - it's got worse. I'm still stuck at the Waiting for confirmation... prompt but now I can't even quit it with ^C.

@svenugopal-stripe I left that stuck prompt open for a while and then it finally worked!! Thanks for your help.

@hrishimittal, glad it finally worked for you and thanks for verifying that. Regarding Ctrl+C will rollout a fix.

@svenugopal-stripe, We are experiencing the same issue with being stuck on Waiting for Confirmation even after the account has accepted the terms. This is after running an upgrade and confirming that stripe apps is running version 1.2.2, as you suggested.
Is there another way to suppress there interactions when deploying an app from bash?

Revisiting this thread to see if anyone is continuing to have this issue, as we are.

Hi @MoneyAlarm1 , would you be able to run the create command with the log-level flag: stripe apps create hellowworld --log-level=debug so we can better identify what the root cause of the issue is.

@MoneyAlarm1 could you also please confirm if you are using multiple Stripe Accounts in Dashboard ?.
Trying to rule out a possibility that Dashboard is logged into one account and the CLI keeps checking for the ToS acceptance on a different account. (this happens due to a bug in dashboard behavior involving multiple accounts today )

I was able to repro this issue when I'm passing --api-key flag to my Stripe apps commands. @MoneyAlarm1, sorry for the delayed response, but would you make sure to not use the --api-key flag and run stripe login to authenticate the CLI instead.


Shop dropdown text enhancement

I changed the text boldness and its size such that it gains the attention of the user
Description
I changed the font size and boldness of all the occourences in shop such that it looks uniform.
Motivation and Context
This change was required at it enhances the visibility of the categories which are the major source of retention of customer on this website

How Has This Been Tested?
I ran this on my local environment several times and the changes are smooth.
Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@VedantAnand17 great work don't forget to give a 🌟

Thank you @MAVRICK-1 🏆


[Discussion] Archive or maintenance plans?

I am wondering about the plans and goals for this repo. Is it meant to be simply an archive of the current state of the CodePush-part of AppCenter? Or are there plans to maintain this project going forward and add adjustments for new releases of React Native?

This repo will be archived on March 31, 2025. Till then we will provide security updates.


virt-viewer: Upgrade to version 6

Issue description
virt-viewer version 6 is out for a month now and adds many features.
Please update the package to version 6.
There also seems to be a bug in version 5 regarding audio passthrough via spice, which only occours in virt-viewer and not in spicy or virt-manager.
Technical details
NixOS details

system: "x86_64-linux"
host os: Linux 4.13.16, NixOS, 18.03pre121925.3eccd0b11d1 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 1.11.15
channels(root): "nixos-18.03pre121925.3eccd0b11d1"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Device details

device: 20J6S0DM00 ThinkPad T470p
cpu: Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
gpu: Intel Corporation Device 591b (rev 04)

virt-viewer 6.0 is in nixos-unstable now.

6.0 and even 7.0 by now


DRAFT: Add modeladmin registry

TODO:

[ ] Add tests for attribute overrides
[ ] Add tests for registry retrieval / query methods
[x] Update documentation
[ ] Add a nice description here to aid review
[ ] Have PR reviewed by a core team member

Hi @kaedroho. I know you have broader plans for modeladmin/snippets... would this kind of thing be useful, or do you think would just make more for you to detangle later?


Deprecate S3KeysUnchangedSensorAsync

What's changed
Deprecate S3KeysUnchangedSensorAsync and fallback to S3KeysUnchangedSensor with deferrable=True
Why this change
The logic of  S3KeysUnchangedSensorAsync has been contributed back to OSS airflow as part of S3KeysUnchangedSensor
S3KeysUnchangedSensorAsync
https://github.com/astronomer/astronomer-providers/blob/b5a9417919d8a13b8e519d2582ce705c4689b7c6/astronomer/providers/amazon/aws/sensors/s3.py#L195-L223
S3KeysUnchangedSensor
https://github.com/apache/airflow/blob/999b70178a1f5d891fd2c88af4831a4ba4c2cbc9/airflow/providers/amazon/aws/sensors/s3.py#L340-L374

This PR is breaking our integration DAGs , @Lee-W to take a look

It maybe an issue with OSS sensor, will leave it to Wei to check once. If it’s an upstream issue, I would suggest reverting this PR for the time being until a new OSS amazon provider including the fix is released.