text:
Compile error building curl - following esp32-snippets/curl/build_files/

BTW, thanks for creating the curl build instructions.  I followed the instructions at esp32-snippets/curl/build_files/.  Unfortunately when I make the project, I get the following error:
CC lib/vauth/cleartext.o
/Users/mike/Dev/esp/i2s/components/curl/lib/vauth/cleartext.c:165:1: fatal error: opening dependency file lib/vauth/cleartext.d: No such file or directory
}
^
compilation terminated.
make[1]: *** [lib/vauth/cleartext.o] Error 1
make: *** [curl-build] Error 2

Hi my friend ... looking at it now.   If you can, ping me at #ESP32 on IRC channel that would be great and we can chat live.  Failing that run "ls -l /Users/mike/Dev/esp/i2s/components" and attach the results in a ZIP to this issue.

Hi, tried ping you, but you may have stepped away - or it may be my lack of IRC experience...

Here's the output from ls -l /Users/jeff/Dev/esp/i2s/components
out.txt

nkolban - Thanks for your help today!
Here's the notes captured from for "Getting the ESP32 curl build working if you're developing on MacOS/OSX":

Follow the "Building curl" directions: https://github.com/nkolban/esp32-snippets/tree/master/curl/build_files.
Change back to project root (cd ../..).
Go ahead and "make" the project and let it fail.  This creates the build/curl/lib/ directory among others.
Create two directories:

mkdir build/curl/lib/vauth
mkdir build/curl/lib/vtls

Modify the last line of component.mk so that it reads:

CFLAGS+=-DHAVE_CONFIG_H -DBUILDING_LIBCURL -DMBEDTLS_FS_IO

Oops, hadn't actually included curl yet.  Now that I've added "#include <curl/curl.h>", the following errors are generated:
/Users/jeff/Dev/esp/i2s/build/curl/libcurl.a(mbedtls.o):(.literal.mbed_connect_common+0x8c): undefined reference to mbedtls_x509_crt_parse_file' /Users/jeff/Dev/esp/i2s/build/curl/libcurl.a(mbedtls.o):(.literal.mbed_connect_common+0x90): undefined reference to mbedtls_x509_crt_parse_path'
/Users/jeff/Dev/esp/i2s/build/curl/libcurl.a(mbedtls.o):(.literal.mbed_connect_common+0x94): undefined reference to mbedtls_pk_parse_keyfile' /Users/jeff/Dev/esp/i2s/build/curl/libcurl.a(mbedtls.o):(.literal.mbed_connect_common+0x98): undefined reference to mbedtls_x509_crl_parse_file'
/Users/jeff/Dev/esp/i2s/build/curl/libcurl.a(mbedtls.o): In function mbed_connect_step1': /Users/jeff/Dev/esp/i2s/components/curl/lib/vtls/mbedtls.c:996: undefined reference to mbedtls_x509_crt_parse_file'
/Users/jeff/Dev/esp/i2s/components/curl/lib/vtls/mbedtls.c:996: undefined reference to mbedtls_x509_crt_parse_path' /Users/jeff/Dev/esp/i2s/components/curl/lib/vtls/mbedtls.c:996: undefined reference to mbedtls_x509_crt_parse_file'
/Users/jeff/Dev/esp/i2s/components/curl/lib/vtls/mbedtls.c:996: undefined reference to mbedtls_pk_parse_keyfile' /Users/jeff/Dev/esp/i2s/components/curl/lib/vtls/mbedtls.c:996: undefined reference to mbedtls_x509_crl_parse_file'

Find me on #ESP32 ... we'll go for round 2 :-)

I have a new guess ... are you using the VERY latest ESP-IDF distribution ... see the following which was added in March 2017.   This would be consistent with the problems described ...
https://github.com/espressif/esp-idf/commit/74817c35f3826939337f911263b210f9b7a60efe
If your ESP-IDF is back-level to this ... this would be the problem and the solution would be to use the latest ESP-IDF.

That seems to be it!

If it works, the recipe in this thread needs to be changed to remove -DMBEDTLS_FS_IO which is now the default.

Yes, seems to work well.  Tested it with your testCurl.c code (modified to use example.com instead of the raspberrypi:) successfully returned "<!doctype html> Example Domain..."  Interestingly, I believe it worked even with -DMBEDTLS_FS_IO.  Next I need to configure TLS/SSL.  Luckily I've got your book!

To ensure I was on the latest esp-idf distribution, I needed to clone it from Git.  But, since I originally installed esp-idf following the "official"  DevKit and esp-idf "Getting Started Guide"s, I moved the /esp-idf folder to a safe backup location (and later deleted it).
git clone --recursive https://github.com/espressif/esp-idf.git
...or, if you already installed it from Git...
git pull
git submodule update --init --recursive
cd to your project folder, edit "component.mk" and remove the "-DMBEDTLS_FS_IO" flag - so the last line reads:
CFLAGS+=-DHAVE_CONFIG_H -DBUILDING_LIBCURL

Awesome, thanks again - don't know how you do it!

i have a similar question,
i get an compilation error during the first build caused by error: unknown type name 'curl_off_t'.
do you know where this came from?

The curl_off_t issue has been tracked down and resolved in this issue:
https://github.com/nkolban/esp32-snippets/issues/18

closing with completion.  Don't hesitate tto re-open as needed.

authors: hassfers mgleason nkolban


text:
Add needed #include for value_t

[Describe your pull request here. Please read the text below the line, and make sure you follow the checklist.]

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[x]  The test suite compiles and runs without error.
[x]  Code coverage is 100%. Test cases can be added by editing the test suite.
[x]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for these kind of bugs). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

Add needed #include for value_t

Coverage remained the same at 100.0% when pulling 9d6d87dd535ae29553453cb90def439c85dbdfd3 on blipper:patch-1 into c9c5c016a20399151f251ab1e612497821e82b0b on nlohmann:develop.

You need to amalgamate the headers. Please call
make amalgamate

and commit the single-header file.

I fixed the CI. Please update to the latest develop branch.

Closing in favor of #2948.

source: gharchive/pull-request

authors: blipper coveralls nlohmann

repo: nlohmann/json

license: MIT

license_type: permissive

license_source: github-api


text:
It would also be good to thoroughly update documentation for this feature.

It would also be good to thoroughly update documentation for this feature.
Originally posted by @nmancus1 in https://github.com/nmancus1/parseva-math/issues/61#issuecomment-769600969

In reference to adding support for tree printing ^^^

In reference to adding support for tree printing ^^^

source: gharchive/issue

license: Unlicense


text:
Fix formatting

This PR is a preparation for the task to add a pipeline that checks the formatting.
There shouldn't be any changes of behavior, so you don't need to review it - famous last words.
Readiness checklist

[ ] I added/updated unit tests.
[ ] I added/updated integration tests.
[x] I ensured that the PR title is good enough for the changelog.
[x] I labeled the PR.

It was actually the merge of main into my feature branch. Some of the nuget references weren't updated, which caused some dependency problems, so the build failed.

repo: nmshd/backbone


text:
Why do we not have api to read all the nodes in the graph?

Hi @Neoanarika ,,
It would be nice to have the function to retrieve all the nodes that are part of the existing index.
Was just wondering any reason we did not expose this function?
Thanks in Advance

Hi @vamshin the primary reason is that we have various methods not only graph-baed retrieval. But, I think it can be a good feature to have.

Thanks for the quick reply.
Also if we traverse the graph, do we get back all the points that are inserted in the index or is it lossy(we ignore storing some points). Sorry for the naive question. Just started digging into this :)

@vamshin it's not lossy in the sense that all points are there.

authors: searchivarius vamshin

repo: nmslib/nmslib

license_source: bigquery


text:
Clear nms index memory

I am running a job where after some fixed time the code reruns in the background re-running the part where nms index is initialized and data points are added.
But I am getting errors due to huge memory consumption after sometimes.
My guess is either, vectors are being repeatedly added to a same index or different indexes are being initialized.
So my question is,
How can we empty a nmlib index or completely delete it from memory so we can initialize a new one.

Hi @bipinkc19 memory should be freed once your index variable is out of scope. Although bugs are always possible, there's a test for memory leaks and I also wrote a little program to demonstrate that memory should be normally cleared, please, see the attached file, you need to run it like this:
./test_clear_mem.py '/Users/leo/TextCollect/VectorSpaces/unif100K_100d.txt'

test_prog.zip

So, I guess when I assign the index variable to a class's self variable, it would never release it!?
I usually have to hold on to the index and get the nearest vectors once request is issued.  And I have to refresh it every "x" minutes. When refreshing I guess the index is always in scope, so when i do, self.index.operations the vectors are just  piling up instead of clearing memory.
What would you suggest in this case?

Hi @bipinkc19 out of scope was defined a bit vagule. It should have been more like: "there's no live variable that keeps a reference to the index". Before anything else, could you run the attached program with the attached data like this one and paste the output?
./test_clear_mem_class.py unif100K_100d.txt

Yes, I ran the attached program. It is clearing the memory or the memory size is constant.

So, using
del self.index _var
should do the trick?

Closing the issue, I guess the problem is somewhere else in my code.

Hi @bipinkc19 it might be, hard to tell, it might be some pybind11/Python quirk. I am really curious if del worked for you? I believe it should not be the space here though:

del self.index _var


text:
require pybind11>=2.2.3

Looks like pybind fixed the issue https://github.com/nmslib/nmslib/issues/307 with older versions of pip, see this PR: https://github.com/pybind/pybind11/pull/1190
Upgrading to a newer version might help ease some installs.

This breaks on python 2.7.... I guess we can just wait 6 months 😄

@DeNeutoy Awesome, many thanks. I will create a new mini-version soon.

@DeNeutoy the failure on Python 2.7 is unrelated, it seems to be one of the tests using functions that are not available on 2.7. I will look into this soon.

authors: DeNeutoy searchivarius


text:
packaging: remove outdated comment

Signed-off-by: Antonio Cardace acardace@redhat.com

Closing, made useless by https://github.com/nmstate/nmstate/pull/1361

repo: nmstate/nmstate


text:
Add test template for layer

Layer semantics test (testing if given layer object obeys semantics, such as we shouldn't validate, valid properties should be valid and so on)
Layer properties test (90% gonna be merged to layer semantics)
Layer golden test (with a python script using recorder to generate one single file)

There will be a test template using TEST_P and testing each object will be much simpler than few thousand lines of code.
starting from #1303, planned to be done within layer v2 migration but delayed after layer v2 migration as per request

:octocat: cibot: Thank you for posting issue #1318. The person in charge will reply soon.

authors: taos-ci zhoonit

repo: nnstreamer/nntrainer


text:
[Trivial] Update gitignore file

add ".idea/" in gitignore file

For ignore jetbrain's IDE

Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2596. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

To contributor, We have used 'Signed-off-by:' notation by default to handle the license issues, that result from contributors. Note that 'Is there a Signed-off-by line?' is important because lawyers tell us we must have to it to cleanly maintain the open-source license issues even though it has nothing to do with the code itself.

authors: DonghakPark taos-ci


text:
Improve merge overlap meshes

Added the capability of smooth transitioning overlapping meshes:

The user can now either pass a mesh to be used as the transition.
If no hfun_mesh if passed to merge_overlapping_meshes, it will use the low priority mesh (floodplain, coarse mesh, etc.) as transition.

In addition:

updated tests

addressed issue https://github.com/noaa-ocs-modeling/OCSMesh/issues/172

Passed all tests, closing PR.

repo: noaa-ocs-modeling/OCSMesh


text:
about containerize

and probably remove the add section component in about altogether

done, same for contact

repo: noahgsolomon/Codefolio


text:
Paid cloud version doesn't work (error on render step)

Hi! I tried to generate a video on the website, and it just errors at the rendering step.
I tried it two times, and it errored both times.

Super sorry. Try again it should work now

Yep, it works! Thanks)

authors: ivryb noahgsolomon


text:
🛑 Rur Forum is down

In 336b5e9, Rur Forum (https://forum.rur.rs) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Rur Forum is back up in bcaa692 after 4 minutes.

repo: nocturo/status


text:
Update MLIR-AIR

Update MLIR-AIR to main (74d1b738aabbb132cc26f9eba560dae5876e7e7c), before we start landing packet-switched routing work in MLIR-AIR and MLIR-AIE.

I don't know what's going on with the peano wheel - i've been messing around there today but it shouldn't have broken the existing wheel. i'll investigate tomorrow

I don't know what's going on with the peano wheel - i've been messing around there today but it shouldn't have broken the existing wheel. i'll investigate tomorrow

Ok. I'll keep trying today, too, to see if there's any changes.

authors: erwei-xilinx makslevental

repo: nod-ai/iree-amd-aie


text:
nock two hosts

hello
I have a node/expressjs subscribe route  which call 2 apis : https://www.google.com:443 (/recaptcha/api/siteverify (use to test if not robot)) and https://api.sparkpost.com:443 (/api/v1/transmissions (use for send email)).
All examples and test/* use already one host but never 2, 3 ... to intercept.
How set nock to intercept this 2 hosts ?
Is-it possible ?
Thank
Ami44

solution
const nock = require("nock");
const nockScope = nock(/.*/); // match all hosts
nock.cleanAll(); // console.error('active mocks: %j', nock.activeMocks());
nockScope.intercept(PATH, METHOD).reply(CODE, RESPONSE); // console.error('active mocks: %j', nock.activeMocks());
nockScope.intercept(PATH, METHOD).reply(CODE, RESPONSE); // console.error('active mocks: %j', nock.activeMocks());

Thanks
Ami44

repo: node-nock/nock

license: mit


text:
Copy path on Context sidebar doesn't copy the full path.

Current Behavior
From this community question:
Pushing the copy button on any property always misses the root object.
Expected Behavior
Should better copy the full path.
Steps To Reproduce

If I push on the copy path button, with the intention to paste it on a change node, or a global.get clause in a function node, I get the following:

And misses the ac_loadsobject.
Environment

Node-RED version: 3.1.1
Node.js version: 18.15.0
npm version: 9.5.0
Platform/OS: Linux
Browser: Firefox

@SergioRius I want to contribute to this issue. Can you assign this issue to me?

authors: MayaSatishRao SergioRius

repo: node-red/node-red


text:
Changed font size in edit function node

Hi there,
I noticed on my several red engine that the font size of the function node is now bigger than the previous version of red. I did not find the place where I could change this ?
Here are two snapshot, the 1st one with the new version

And as you can see much lower on old version.

I'm pretty sure I missed an option somewhere but still can't find it.
Thank you for your help

I noticed this too, font size seems too big in the new version.

Hi,
The font should be the same size as all the others on the page (labels, debug panel etc). On larger res screens the small font was just too small - so keeping them all the same seemed sensible. Ctrl + and - will zoom the whole page of course including fonts.

dceejay
Thanks, that did the trick, I'm reducing the whole page then just increasing the dashboard with zoom + and - (bottom right)  like this, my node stay a good size and menus are still lower size, exactly what I needed ;-)

+1

authors: dceejay hallard shemethy


text:
获取设备状态api有误

lib/api_device.js
make(exports, 'getDeviceStatus', function (deviceId, callback) {
  // https://api.weixin.qq.com/device/get_stat?access_token=ACCESS_TOKEN&device_id=DEVICE_ID
  var url = 'https://api.weixin.qq.com/device/compel_unbind?access_token=' + this.token.accessToken + "&device_id=" + deviceId;
  this.request(url, {dataType: 'json'}, wrapper(callback));
});

请改正.

提pr
发自我的 iPhone

在 2015年5月8日，下午4:06，wxhuang notifications@github.com 写道：
lib/api_device.js
make(exports, 'getDeviceStatus', function (deviceId, callback) {
// https://api.weixin.qq.com/device/get_stat?access_token=ACCESS_TOKEN&device_id=DEVICE_ID
var url = 'https://api.weixin.qq.com/device/compel_unbind?access_token=' + this.token.accessToken + "&device_id=" + deviceId;
this.request(url, {dataType: 'json'}, wrapper(callback));
});
请改正.
—
Reply to this email directly or view it on GitHub.

Fixed in 0e6c7e9459fc81fad7ce8dc2fbac0f86d73e40e9

authors: JacksonTian wxhuang

repo: node-webot/wechat-api


text:
Nodegit Preinstall error on Redhat linux Amazon EC2

Hi, Need some help here.
{ Error: Command failed: /cms/node/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/cms/node/node_modules/nodegit/vendor/openssl/openssl
/cms/node/node_modules/nodegit/vendor/libssh2/missing: Unknown --is-lightweight' option Try /cms/node/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in /cms/node/node_modules/nodegit/vendor/libssh2': configure: error: C compiler cannot create executables See config.log' for more details
at ChildProcess.exithandler (child_process.js:271:12)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:927:16)
at Socket.stream.socket.on (internal/child_process.js:348:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:547:12)

killed: false,
code: 77,
signal: null,
cmd: '/cms/node/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/cms/node/node_modules/nodegit/vendor/openssl/openssl' }
/cms/node/node_modules/nodegit/vendor/libssh2/missing: Unknown --is-lightweight' option Try /cms/node/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in /cms/node/node_modules/nodegit/vendor/libssh2': configure: error: C compiler cannot create executables See config.log' for more details
[nodegit] ERROR - Could not finish preinstall
{ Error: Command failed: /cms/node/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/cms/node/node_modules/nodegit/vendor/openssl/openssl
/cms/node/node_modules/nodegit/vendor/libssh2/missing: Unknown --is-lightweight' option Try /cms/node/node_modules/nodegit/vendor/libssh2/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in /cms/node/node_modules/nodegit/vendor/libssh2': configure: error: C compiler cannot create executables See config.log' for more details
at ChildProcess.exithandler (child_process.js:271:12)
at emitTwo (events.js:125:13)
at ChildProcess.emit (events.js:213:7)
at maybeClose (internal/child_process.js:927:16)
at Socket.stream.socket.on (internal/child_process.js:348:11)
at emitOne (events.js:115:13)
at Socket.emit (events.js:210:7)
at Pipe._handle.close [as _onclose] (net.js:547:12)

killed: false,
code: 77,
signal: null,
cmd: '/cms/node/node_modules/nodegit/vendor/libssh2/configure --with-libssl-prefix=/cms/node/node_modules/nodegit/vendor/openssl/openssl' }
==============================================
I did install gcc 4.9 on the box and did a symlink.
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc492/libexec/gcc/x86_64-unknown-linux-gnu/4.9.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.9.2/configure --disable-multilib -prefix=/usr/local/gcc492 --with-gmp-lib=/usr/local/lib --with-mpfr-lib=/usr/local/lib --with-mpc-lib=/usr/local/lib
Thread model: posix
gcc version 4.9.2 (GCC)
ln -s /usr/local/gcc492/bin/gcc /bin/gcc

Planning to change the OS as i am running out of options.. Will switch to Ubuntu and give it a shot again

still an issue

repo: nodegit/nodegit


text:
update lodash

Updates the lodash version. As of 3.0.0, lodash chainable foreach is lazy, and you have to call .value() at the end of the chain for it to evaluate.

:+1:


text:
Consider replacing request package

Node Version: *
Platform: *
Compiler: *
Module: *

You might want to consider replacing request as it's entering maintenance mode.
https://github.com/request/request/issues/3142
https://github.com/request/request/issues/3143
After a first look it should be relatively easy to replace request with the built-in https library.

Replacing request has been suggested before in a different context but as long as npm still depends on request, we're likely to keep doing so as well.
node-gyp is normally distributed along with npm and they share a copy of request. That's good because it keeps the download size down.
Thanks for the suggestion though!

authors: SimonSchick bnoordhuis

repo: nodejs/node-gyp


text:
npm error code 1

PS D:\source\czq\20241218\Angular18> npm install ffi-napi --legacy-peer-deps
npm warn deprecated gar@1.0.4: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
npm warn deprecated asar@3.2.0: Please use @electron/asar moving forward.  There is no API change, just a package name change
npm error code 1
npm error path D:\source\czq\20241218\Angular18\node_modules\ffi-napi
npm error command failed
npm error command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build
npm error nothing.c
npm error   win_delay_load_hook.cc
npm error   nothing.vcxproj -> D:\source\czq\20241218\Angular18\node_modules\ffi-napi\build\Release\nothing.lib
npm error   Preprocessing assembly file ......\deps\libffi\src\x86\win64_intel.preasm
npm error   '"call"' は、内部コマンドまたは外部コマンド、
npm error   操作可能なプログラムまたはバッチ ファイルとして認識されていません。
npm error D:\source\czq\20241218\Angular18\node_modules\ffi-napi\build\deps\libffi\ffi.targets(34,5): error MSB3721: コマンド "call "call" "../../../deps/libffi/preprocess_asm.cmd" "../../../deps/libffi/include" "../../../deps/libffi/config/win/x64" "......\deps\libffi\src\x86\win64_intel.preasm" "Release\obj\ffi\win64_intel.asm"" はコード 1 で終了しました。 [D:\source\czq\20241218\Angular18\node_modules\ffi-napi\build\deps\libffi\ffi.vcxproj]
npm error gyp info it worked if it ends with ok
npm error gyp info using node-gyp@11.0.0
npm error gyp info using node@18.20.5 | win32 | x64
npm error gyp info find Python using Python version 3.13.1 found at "C:\Users\changzq\AppData\Local\Programs\Python\Python313\python.exe"
npm error gyp info find VS using VS2022 (17.12.35527.113) found at:
npm error gyp info find VS "C:\Program Files\Microsoft Visual Studio\2022\Enterprise"
npm error gyp info find VS run with --verbose for detailed information
npm error gyp info spawn C:\Users\changzq\AppData\Local\Programs\Python\Python313\python.exe
npm error gyp info spawn args [
npm error gyp info spawn args 'D:\source\czq\20241218\Angular18\node_modules\node-gyp\gyp\gyp_main.py',
npm error gyp info spawn args 'binding.gyp',
npm error gyp info spawn args '-f',
npm error gyp info spawn args 'msvs',
npm error gyp info spawn args '-I',
npm error gyp info spawn args 'D:\source\czq\20241218\Angular18\node_modules\ffi-napi\build\config.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args 'D:\source\czq\20241218\Angular18\node_modules\node-gyp\addon.gypi',
npm error gyp info spawn args '-I',
npm error gyp info spawn args 'C:\Users\changzq\AppData\Local\node-gyp\Cache\18.20.5\include\node\common.gypi',
npm error gyp info spawn args '-Dlibrary=shared_library',
npm error gyp info spawn args '-Dvisibility=default',
npm error gyp info spawn args '-Dnode_root_dir=C:\Users\changzq\AppData\Local\node-gyp\Cache\18.20.5',
npm error gyp info spawn args '-Dnode_gyp_dir=D:\source\czq\20241218\Angular18\node_modules\node-gyp',
npm error gyp info spawn args '-Dnode_lib_file=C:\\Users\\changzq\\AppData\\Local\\node-gyp\\Cache\\18.20.5\\<(target_arch)\\node.lib',
npm error gyp info spawn args '-Dmodule_root_dir=D:\source\czq\20241218\Angular18\node_modules\ffi-napi',
npm error gyp info spawn args '-Dnode_engine=v8',
npm error gyp info spawn args '--depth=.',
npm error gyp info spawn args '--no-parallel',
npm error gyp info spawn args '--generator-output',
npm error gyp info spawn args 'D:\source\czq\20241218\Angular18\node_modules\ffi-napi\build',
npm error gyp info spawn args '-Goutput_dir=.'
npm error gyp info spawn args ]
npm error gyp info spawn C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\MSBuild.exe
npm error gyp info spawn args [
npm error gyp info spawn args 'build\binding.sln',
npm error gyp info spawn args '/clp:Verbosity=minimal',
npm error gyp info spawn args '/nologo',
npm error gyp info spawn args '/p:Configuration=Release;Platform=x64'
npm error gyp info spawn args ]
npm error gyp ERR! build error
npm error gyp ERR! stack Error: C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Current\Bin\MSBuild.exe failed with exit code: 1
npm error gyp ERR! stack at ChildProcess. (D:\source\czq\20241218\Angular18\node_modules\node-gyp\lib\build.js:216:23)
npm error gyp ERR! stack at ChildProcess.emit (node:events:517:28)
npm error gyp ERR! stack at ChildProcess._handle.onexit (node:internal/child_process:292:12)
npm error gyp ERR! System Windows_NT 10.0.19045
npm error gyp ERR! command "C:\Program Files\nodejs\node.exe" "D:\source\czq\20241218\Angular18\node_modules\node-gyp\bin\node-gyp.js" "rebuild"
npm error gyp ERR! cwd D:\source\czq\20241218\Angular18\node_modules\ffi-napi
npm error gyp ERR! node -v v18.20.5
npm error gyp ERR! node-gyp -v v11.0.0
npm error gyp ERR! not ok
npm error A complete log of this run can be found in: C:\Users\changzq\AppData\Local\npm-cache_logs\2024-12-25T01_43_55_397Z-debug-0.log

Duplicate of

node-ffi-napi/node-ffi-napi#269

https://github.com/nodejs/node-gyp/labels/ffi-napi


text:
.txt.asc files are downloaded instead of displayed in browser

Compare https://nodejs.org/dist/v21.2.0/SHASUMS256.txt.asc
With https://r2.nodejs.org/dist/v21.2.0/SHASUMS256.txt.asc

I believe this is because there's a difference in the content-type headers, nginx returns content-type: text/plain while R2 returns content-type: application/pgp-keys. The content type for each file is stored in R2's metadata, I don't believe we can update it after uploading but I could be wrong.
A simple fix would be to just check if it's a .asc file when constructing the serve file response and send a text/plain content type instead of whatever R2 has it as. We already do check if it's a .json file for CORS headers

This one is probably not a big deal. I'm ok with just closing the issue.

I also think this is not a big deal, just funny that R2 has a different content/type for this than nginx.

authors: flakey5 ovflowd targos

repo: nodejs/release-cloudflare-worker


text:
Bug: attachment filestreams not closed in case of error

Hi,
I can't seem to reproduce this reliably but if the nodemailer gets an ECONNREFUSED error, the fs.ReadStreams that were passed as attachments are not always closed when the sendMail callback is invoked. This causes EPERM errors later on when I try to unlink the file
var path = require("path");
var fs = require("fs");
var nodemailer = require("nodemailer");
var smtpPool = require("nodemailer-smtp-pool");

var testFile = path.join(__dirname, "some_file.txt");

// non existing server
var transporter = nodemailer.createTransport(smtpPool( {
	host: "127.0.0.1",
	port: 1237,
	auth: {
		user: "pietje",
		pass: "puk"
	}
}));
transporter.sendMail({
	from: "somebody@someserver.com",
	replyTo: "somebody@someserver.com",
	to: ["somebody@someserver.com"],
	subject: "subject",
	text: "body",
	attachments: [{ filename: path.basename(testFile), content: fs.createReadStream(testFile, {flags: "r"}) }]
}, function(error, info) {
	transporter.close();
      // HERE, the attachment readstream is NOT closed
});

Sorry for ignoring this issue for so long. I don't know a good solution here. If something fails, then opened streams are left unconsumed and thus 'end' never fires. Not all streams are equal either, some stream types have abort() method, some have close(), some have nothing to close them. Trying to consume the stream to the end might not be a good idea either in case it is a large data stream from some slow source. So I would leave the clean up for sending app, since Nodemailer itself does not know enough about the type of the stream and how to properly close it. I'm going to add a not to the docs about it.

Is there a way for the outside world to know then whether the stream has ended when something goes wrong?

repo: nodemailer/nodemailer-smtp-transport


text:
global setting - device types are global

add an application setting, device types are global

added 1m of time spent

mentioned in commit ece6b9e354a149ff1aa73d147bedcb3c406603c0

mentioned in commit 256d6e6c453f9e3d95ccb23074a24c205ee5d703


text:
Chained constructors give Expression type is ambiguous

Aim
Code like this used to compile:
use dep::aztec::{prelude::{NoteViewerOptions, PrivateSet}};
use dep::value_note::value_note::ValueNote;

fn main() -> pub Field {
    let set: PrivateSet<ValueNote> = PrivateSet::new(dep::std::unsafe::zeroed(), 0);
    let options = NoteViewerOptions::new().set_limit(1); // chained construction happening here
    let notes = set.view_notes(options);
    notes[0].unwrap_unchecked().value
}

With this in dependencies:

[dependencies]
aztec = { git = "https://github.com/AztecProtocol/aztec-packages", tag = "master", directory = "noir-projects/aztec-nr/aztec" }
value_note = { git = "https://github.com/AztecProtocol/aztec-packages", tag = "master", directory = "noir-projects/aztec-nr/value-note" }

Here is the code for NoteViewerOptions and private set:
https://github.com/AztecProtocol/aztec-packages/blob/master/noir-projects/aztec-nr/aztec/src/note/note_viewer_options.nr
https://github.com/AztecProtocol/aztec-packages/blob/master/noir-projects/aztec-nr/aztec/src/state_vars/private_set.nr
Expected Behavior
I think it should compile, since the generic of NoteViewerOptions should be resolved to the generic of set that is ValueNote
Bug
Instead it errors with Expression type is ambiguous
To Reproduce

Project Impact
Nice-to-have
Impact Context
No response
Workaround
Some
Workaround Description
Splitting it in two lines works:
use dep::aztec::{prelude::{NoteViewerOptions, PrivateSet}};
use dep::value_note::value_note::ValueNote;

fn main() -> pub Field {
    let set: PrivateSet<ValueNote> = PrivateSet::new(dep::std::unsafe::zeroed(), 0);
    let mut options = NoteViewerOptions::new();
    options = options.set_limit(1);
    let notes = set.view_notes(options);
    notes[0].unwrap_unchecked().value
}

Additional Context
No response
Installation Method
None
Nargo Version
No response
NoirJS Version
No response
Would you like to submit a PR for this Issue?
None
Support Needs
No response

Can you give an example without the aztec dependency? I've tried encoding a version of NoteViewerOptions directly but it works as expected.

Instead it errors with Expression type is ambiguous

Where is the error? On the set_limit call, NoteViewerOptions::new, or somewhere else?

Actually, I added a trait constraint like in the original and the error immediately appeared afterward:
fn main() -> pub Field {
    let _options = NoteViewerOptions::new().set_limit(1);
    0
}

struct NoteViewerOptions<Note, N> {
    limit: u32
}

impl<Note, N> NoteViewerOptions<Note, N> {
    pub fn new() -> NoteViewerOptions<Note, N> where Note: Default {
        NoteViewerOptions { limit: 0 }
    }

    pub fn set_limit(&mut self, limit: u32) -> Self {
        self.limit = limit;
        *self
    }
}

The error is on NoteViewerOptions::new which makes sense since the Note type is never constrained so it doesn't know which type to use to try to find Note: Default
I think an improvement for this error message is that it could try to mention the Note and N generics specifically as needing to be specified.
Rust gives a similar error message here but mentions the original Note and N names, and mentions the context of solving for a trait:
error[E0283]: type annotations needed for `NoteViewerOptions<Note, N>`
  --> foo.rs:2:9
   |
2  |     let _options = NoteViewerOptions::new().set_limit(1); // chained construction happening here
   |         ^^^^^^^^   ---------------------- type must be known at this point
   |
   = note: cannot satisfy `_: Default`
note: required by a bound in `NoteViewerOptions::<Note, N>::new`
  --> foo.rs:12:60
   |
12 |     pub fn new() -> NoteViewerOptions<Note, N> where Note: Default {
   |                                                            ^^^^^^^ required by this bound in `NoteViewerOptions::<Note, N>::new`
help: consider giving `_options` an explicit type, where the type for type parameter `Note` is specified
   |
2  |     let _options: NoteViewerOptions<Note, N> = NoteViewerOptions::new().set_limit(1); // chained construction happening here
   |                 ++++++++++++++++++++++++++++

authors: jfecher sirasistant

repo: noir-lang/noir


text:
feat: Add deprecated attribute

Description
fn main() {
    deprecated();
}

#[deprecated]
fn deprecated() {}

> nargo check
warning: use of deprecated function deprecated
  ┌─ /home/work/subject/oliver/noir/app/src/main.nr:2:5
  │
2 │     deprecated();
  │     ----------

Constraint system successfully built!

Problem
Resolves #879
PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Agree that we should add tests to see how this plays with other attributes.
Also agree, it would be good to have the reason for deprecation, seems to be quite easy to add it like we have with Oracle attribute for example and retain that information until we need to emit a warming. It is not hard blocking for this PR though (wasn't in the issue that it resolves)

As of now, only one attribute per function is currently supported.
https://github.com/noir-lang/noir/blob/ce377186a1d6afa025bd88d7436f61319c30cc33/crates/noirc_frontend/src/ast/expression.rs#L335-L336
I'm not sure how to implement it correctly, but I'll give it a try.

As of now, only one attribute per function is currently supported.
https://github.com/noir-lang/noir/blob/ce377186a1d6afa025bd88d7436f61319c30cc33/crates/noirc_frontend/src/ast/expression.rs#L335-L336
I'm not sure how to implement it correctly, but I'll give it a try.

We can open up another issue for multiple attributes, as that may introduce scope creap. Can you just look into adding the message?

Can you add a test which shows that this warning gets created correctly when parsing a program?

@TomAFrench pending re-review

authors: TomAFrench f01dab1e jfecher kevaundray


text:
Manage TOC:Toogle for multiple files in the same Window

Maybe I do not this right, but I am using Atom as a note editor and like the Markdown format :)
I open multiple note files and I would like to manage a TOC for each of this files.
Unfortunately I have to open a new window to be able to generate a TOC.
Can this be a feature or not ?

Hello,
I've got the exact same issue thus it's not related to your setup. Indeed, It would be good to be able to manage multiple table of content across tabs.
I don't know if nok planned for this.

Thank you @xakraz and @grumpycatt ,
sorry, currently my time is limited because of my study. Nevertheless I noted that issue as an enhancement for the next update.
Happy coding,
Darius

Any updates ?

Same problem here -.-

authors: darkdragon-001 grumpycatt nok xakraz

repo: nok/markdown-toc


text:
Position of dropdown is not correct if page-content is in center

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 1.4.2

Platform and Target: PC

What you did
I have a page-content that is aligned in center of screen.
When I used Autocomplete drop-down, the drop-down appeared with a very high left offset that looked bad. On mobile the drop-down is properly aligned as the page-content is taking full space of screen.
Expected Behavior
The drop-down appears directly below the input even if page-content is not taking complete screen
Actual Behavior
The drop-down appears too much to the right instead of displaying directly below the input
I have implemented a fix, can I do a pull request for it?
Before:

After the fix:

How did you fixed this? I have a similar problem

@chanty6680 here is the change :-)
https://github.com/Trion129/Framework7/blob/4a6d6086a0324cde439172ee9190aacbab9855d6/src/js/autocomplete.js


text:
Domcache results in duplicated ajax pages in dom

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Framework7 Version: 1.5.2

Platform and Target: Phonegap Desktop, Browser

What you did
I have a single view with one inline page inside and a couple of ajax pages. To activate the hash navigation I set: domCache: true
Expected Behavior
I expected that the ajax pages wouldn't be loaded any more as soon as they are cached  AND the cached page will be shown.
Actual Behavior
The cashed page remains in DOM and the ajax page is also loaded. The bad thing about it is that it results in duplication of id's - the code picks the cached page (which is the first in dom) but the fresh loaded page is the one being displayed.
The DOM after first ajax-questions-page loading:

...

...

...

The DOM after second ajax-questions-page loading:

...

...

...

...

Can I prevent this duplication somehow or is there a workaround?
With this behavior domCache makes no sense IMO. I hope this problem will be resolved.
Best,
Adrian Maleska

I have the some problem

Hi, the settings name domCache might be missleading. From what I understand, enabling it will only activate the ability to embed pages into the DOM without using Ajax Pages feature. It has nothing to do with caching pages, I think.

@valnub that's my interpretation of the docs however given the name it is definitely a little misleading

@valnub You conclusion might be right but it's not a solution for the given problem which is: using inline pages together with ajax pages - this is a very common scenario and a problem for everybody with F7.

So you have page x stored in the DOM and page x.html which contains the same page and is being loaded over ajax?

I don't think this is a bug. F7 currently only support using either Ajax pages or cached pages, not both at the same time.
This might rather be a feature request.

@valnub that was my thinking. Hence my request for clarification

@valnub The docs aren't that clear about this topic IMO otherwise I wouldn't even try to mix it. But I agree to change this issue from but to feature request.
@ZanderBrown Actually I have page x in DOM and load y.html over ajax. I end then in having x in the DOM, y.html cached and y.html loaded over Ajax - but the y.html cached version isn't even being used/displayed.

@Hexodus slightly confused here. Have you got a repo/gist we can take a look at?

@ZanderBrown I created a repo to show this behavior:
Repo: F7-Mixing-inline-and-ajax-pages
And for clarification here's a Gif Animation showing what happens. In short the dom is growing because the cached ajax pages aren't being reused.

Same problem here

Someone posted on Stackoverflow a possible workaround. Unfortunately I had no time to check it. In the case someone wants to give it a try:
Stackoverflow possible workaround

I have the same issue:
using some inline pages and most pages over ajax. Cache set to be false, domCache set to be true.
Ajax pages are in domCache and therfor I have problems because I use html ids in the ajax pages...
My workaround:
onPageInit:
$$('.cached').each(function(){
    var pageName = $$(this).data('page');
    if(pageName === page.name){
         $$(this).remove();
    }
});

Has anyone figured this out yet?

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue

authors: Hexodus Kaldrax ZanderBrown dawuwu hellofarhan lancewalk87 nolimits4web valnub


text:
Высота блоков в iOS высчитывается некорректно.

This is a (multiple allowed):

[x] bug

Swiper Version: 3.3.1 jquery

Platform/Target and Browser Versions: iOS 9.1, 9.3, 10

What you did
Поставил вертикальную прокрутку и сделал слайды на всю высоту через 100vh, слайдер на iOS высчитывает почему-то с лишними пикселями. Примерно на 10-20 пикселей ошибается. Я подумал, что проблема в том, что у меня весь js в одном файле из-за этого не успевает правильно построится, поэтому код делил и помещал весь активный в шапку, но все без толку. На android устройствах и пк такой проблемы не заметил. Только на айфонах и айпадах.
Вот живой пример http://knowprof.ru.
Как это лечить? Заранее спасибо за ответ.

Еще актуально? Я честно вроде не вижу бага. Если актально, то укажите проблемные места на скриншоте

Да, моя ошибка, не предоставил скриншотов. Проблему решил переходом на другой плагин.


text:
Equals between PolySparse and PolyDense can throw exception

scala> Polynomial("(0)") == Polynomial("(1)")
java.lang.ArrayIndexOutOfBoundsException: 0
  at spire.math.Polynomial$class.loop$3(Polynomial.scala:272)
  at spire.math.Polynomial$class.equals(Polynomial.scala:283)
  at spire.math.poly.PolySparse.equals(PolySparse.scala:17)
  ... 43 elided

I think this is because the zero polynomial has a coefficient array of size zero, so lhs.degree == rhs.degree is not sufficient to prevent an exception.

I could not reproduce this error:
scala> Polynomial("(0)") == Polynomial("(1)")
res1: Boolean = false

Perhaps the closed issue handled this one too?

Yes, I think we did get this fixed. Thanks for verifying it.

authors: kevinmeredith non rklaehn

repo: non/spire


text:
In both places it says "N_NODES" should I replace it with the max number of nodes in the network?

Hi all,
uint8_t routes[N_NODES]; // full routing table for mesh

int16_t rssi[N_NODES]; // signal strength info

In both places where it says "N_NODES" should I replace it with the max number of nodes in the network?
Thanks,
Zeb

Duh! It relates to this!
#define N_NODES 4
Problem solved, thanks!

repo: nootropicdesign/lora-mesh


text:
Using convert_id() without REST_API

can I use local files downloaded from the KEGG ftp to run convert_id functions?
I would like to let the package run on a machine without internet.
Best wishes
Felix

Thank you always for your suggestion. This is indeed an important feature and I will definitely implement one for specifying the converting table without accessing REST API.

Hi, in 88a401b, convert_id now has following arguments:
file: file for converting IDs
query_column: query column number
convert_column: convert column number
pref: prefix to be added (optional) to the query column
I think most of the cases can be covered including files from downloaded KEGG data, but let me hear your thought!

sounds reasonable, will test it later

repo: noriakis/ggkegg


text:
Compatibility with Gnome 41

Hello,
Is it possible to make this extension compatible with Gnome 41? Thanks!

@lp35  Yes,
there are no any major changes in API's from gnome 40 to 41. I don't have a machine for testing on gnome 41.
Will release it after testing on gnome 41.
Meanwhile can you try out this build
network-stats@gnome.noroadsleft.xyz.shell-extension.zip
gnome-extensions install network-stats%40gnome.noroadsleft.xyz.shell-extension.zip

Then restart the gnome shell, steps here

Support added in extension version 12.


text:
Problem with windows path

I can't tell if this problem is directly related to atom-build but maybe someone encountered the same problem.
I try to build a GO application with a custom build command:
{   "cmd": "$GOROOT/bin/go run {FILE_ACTIVE}",   "shell": true,   "env": {     "GOROOT": "C:/Program Files (x86)/Go",     "GOPATH": "C:/GoRoot"   } }
But this will fail with the message (german):
Der Befehl "C://Program" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Translates into english: Command "C://Program" not found
So the whitespaces in the path break the execution of the build command. Is there a way to use the above path or do I need to change my GO installation dir?

Duplicate of #432

authors: LukasMa noseglid

repo: noseglid/atom-build


text:
Build targets

Basic functionality to solve #37.
Notes:

The user can deselect a target (so that the build:trigger command will run the default, unnamed, build)  by selecting it again in the TargetsView. Not sure what the atom UI paradigm for toggling in a list view is, so we might want to change this. Maybe we could have a "Default" option always available, or there might be a UI convention for this already?
Need to implement returning targets from other tools, currently only returns targets from the atom-build tool.
Needs some tests. Once we have settled on the functionality and implementation, I’m happy to write  the tests before merging.

Cool! Thanks a lot. I think we should use this as a base for the rest (more tests, README, code style and eventual other things). I've pushed this to dev/build-targets.
I suggest we change the key-binding to cmd-alt-t (OS X) or ctrl-alt-t (Linux/Windows), so it has the same meta keys as running the build target.
I really love mark-active part of SelectListView. Good job on finding that. Looks great.

This has been merged to noseglid/atom-build@dev/multiple-targets. We should continue work there (I've pushed your commits, so you will be attributed for the changes you've made so far, and any further changes you'll make).

authors: austinbirch noseglid


text:
Add spaces around -c/-gui/-i grep to prevent matching on other argume…

…nts (such as -coverage).  Issue #23.

released as v3.26. thx!

authors: jesseprusi nosnhojn

repo: nosnhojn/svunit-code


text:
Implement remaining drivers on nb5 API

One of the key promises of NoSQLBench is that of re-usable concepts and workflows. This means that time invested by users to learn more advanced usage patterns will be rewarded with an understanding of how to apply that knowledge elsewhere. The driver interfaces and capabilities are a key focal point for this. In other words, when the drivers support a uniform set of integrations and behaviors, the toolkit becomes simpler and more powerful at the same time.
Challenge
Previously, driver developers had to effectively copy and emulate the behavior which was established by convention, using code which was not managed by the core runtime. As well, the concepts and tooling needed to streamline the process of converting templates to operations was lacking in terms of clarity and supportive APIs.
Remedy

[ ] #431
[ ] #434
[ ] #435
[ ] #436
[x] #438

I suspect that this and the four remaining tasks are complete

repo: nosqlbench/nosqlbench


text:
about the HDR version model

very excellent  work！I have noticed that "627 images were selected as the training set" in the paper. Do you mean the HDR version model ONLY use these 627 images in training period? I was wondering  if you could tell me how to define source domain and target domain only using 627 images?  And could you release the pre-trained model or inference demo? Thks !

We used MIT-Adobe 5K dataset (2250 images) as source domain and used the 627 HDR images as the target domain. I only provide the demo website to show our model. I will release the model ASAP.

authors: lebronyxm nothinglo

repo: nothinglo/Deep-Photo-Enhancer


text:
The factories can be walked from outside

I'm not sure how I did (I think with the hook weapon mod) but zooming out made me look the outside of the factories and you can walk and build outside (If you do, a crash appear after putting some items near the area)

To add to this, it looks like refined concrete can be built on the black void tiles? Stone bricks and normal concrete cannot. If this placement is unrelated to the being able to walk outside the factory area, I can make a different issue.

To add to this, it looks like refined concrete can be built on the black void tiles? Stone bricks and normal concrete cannot. If this placement is unrelated to the being able to walk outside the factory area, I can make a different issue.
EDIT: The refined concrete cannot be removed once placed outside the normal factory bounds. I have a save backup so it's fine, but it's an odd interaction.

Please make a new issue. This is unrelated to the original report.

authors: NevadaActual nikuzo notnotmelon


text:
Update http4s-blaze-server, http4s-circe, ... to 0.21.22

Updates

org.http4s:http4s-blaze-server
org.http4s:http4s-circe
org.http4s:http4s-dsl

from 0.21.1 to 0.21.22.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Applied Migrations

dependency:v0_21@org.http4s:http4s-scalafix:0.21.5

Documentation:

https://github.com/http4s/http4s/releases/tag/v0.21.5

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.http4s" } ]

labels: library-update, semver-patch, scalafix-migrations

Superseded by #303.

repo: notxcain/aecor


text:
firestore syntax problem

chatGPT isn't giving the right code for me to use
prince charming will help me later 💯

charming prince fixed it but forgot to add the initstate i did it myself

repo: nouhelion/charming-prince


text:
Approve button does not available on operations page for some signatories types.

Description
There is case when Approve button is not available for sign operation
Steps to Reproduce

Be invited to multisig
...
Create operation from polkadot.js app
Go to operations page

Expected Behavior
Approve is shown for user who can sign the opoeration
Actual Behavior
Approve button may be unavailable

Status verification: ✅

repo: novasamatech/nova-spektr


text:
Fix typos

Overview
Fixes typos preventing macchiato from being used with the latest version of Ginkgo (1.14.0).

cc @jamillosantos

authors: dustinblackman novln

repo: novln/macchiato


text:
-o is used for both --overview and --outage

One should have another letter then.

Only relevant when adding --outage.

repo: nozel-org/serverbot


text:
Unable to import images from src folder

Currently trying to import images, but without extra configuration am unable to get it to build.
...
=> [✓] App Bundled: 3521.463ms
=> Exporting Routes...
{ SyntaxError: /Users/malonehedges/projectPath/src/assets/myimage.png: Unexpected character '�' (1:0)
> 1 | �PNG
    | ^
...

"Add example configuring webpack to import images from the src folder"?

I’ll look into this asap
On Thu, Oct 12, 2017 at 10:33 AM Malone Hedges notifications@github.com
wrote:

Currently trying to import images, but without extra configuration am
unable to get it to build.
...
=> [✓] App Bundled: 3521.463ms
=> Exporting Routes...
{ SyntaxError: /Users/malonehedges/projectPath/src/assets/myimage.png: Unexpected character '�' (1:0)

1 | �PNG
| ^
...

"Add example configuring webpack to import images from the src folder"?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/36, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCQ8RorD_5Go_1WetIR_sEJRvfqK5ks5srk2AgaJpZM4P3XMH
.

I can't import images either, but the symptoms are slightly different:
import photo from '../assets/starry-night.jpg'

photo now returns a base64 data url for the broken image icon.  lolwat?

Have you looked at: https://github.com/nozzle/react-static/issues/24#issuecomment-337013966 ?

I know an example config is requested but is there a reason this isn't built in? Gatsby enables it by default actually suggests using this method to import assets for seemingly valid reasons.
Sorry if this is already being worked on it was just something I expected to be able to do, maybe I'm spoilt.

This should be fixed in the latest version. Please upgrade both global and local packages to version 2.0.0
Make sure you import and use the withFileLoader from react-static's plugins in your static.config.js file:
import axios from 'axios'
//
import withCss from 'react-static/lib/plugins/withCssLoader'
import withFiles from 'react-static/lib/plugins/withFileLoader'

export default {
  getSiteProps: () => ({
    title: 'React Static',
  }),
  getRoutes: async () => {
    const { data: posts } = await axios.get('https://jsonplaceholder.typicode.com/posts')
    return [
      {
        path: '/',
        component: 'src/containers/Home',
      },
      {
        path: '/about',
        component: 'src/containers/About',
      },
      {
        path: '/blog',
        component: 'src/containers/Blog',
        getProps: () => ({
          posts,
        }),
        children: posts.map(post => ({
          path: `/post/${post.id}`,
          component: 'src/containers/Post',
          getProps: () => ({
            post,
          }),
        })),
      },
      {
        is404: true,
        component: 'src/containers/404',
      },
    ]
  },
  webpack: [withCss, withFiles],
}

Then you can simply import images in your js
import logo from './logo.png'

I know this is an old issue, but I'm curious what is the recommended method now of including images into your website? I've tried putting them in the /src folder and referencing them, but the new images folder doesn't seem to get published on my local build.  I looked through the docs and didn't see any info about how to handle files or assets.

authors: Burnett2k D1no DanWebb malonehedges tannerlinsley whmountains

repo: nozzle/react-static


text:
Error en el encoding al leer un valor del fichero properties

Al obtener del fichero application.properties el valor de la propiedad app.description, debido al encoding del fichero el texto no se muestra correctamente.
En la clase AppConfig se puede ver este problema en la propiedad appDescription

Can I work on this @nmarulo .?
I think i will get resolved by adding PropertySource annotation with encoding parameter in the AppConfig file.

Hello @chinmaym07, thank you for your help on issue #3. 😄
As this project is small, I don't have many tasks to delegate, even so, I am creating these issues to help those who are doing the event.
If this week nobody shows up and you are still interested in this issue I will notify you.

Thanks to you for your interest and help. 😄

Hi @chinmaym07, if you are still interested, you can make this issue. 👌

Done @nmarulo. Thankyou 🙌🏻 💯 .
Please review.

repo: npedidos/rest-api


text:
Want to add contributors profiles into README.md

It will automatically updated whenever anyone contribute to this project

Hello @sb-decoder 👋, thank you very much for the suggestion, although I do not see it very useful, since Github adds those who have contributed on the right side of the website.

authors: nmarulo sb-decoder


text:
Sometimes chromecast doesn't work when launched from within app

Sometimes, when launching from within the app, the sender gets a "reconnection" event (_sessionListener) even though there is no session active on the receiver device. Possible this is some weird caching on the chromecast end? Can't figure out any workaround.

One reason this happens is if you click cast, then exit the casting dialogue midway through the initialization process. This is totally broken on Google's end.

repo: nprapps/austin


text:
Can't request tokenAuth Mutation

Prerequisites

[x] Is it a bug?
[ ] Is it a new feature?
[ ] Is it a question?
[x] Can you reproduce the problem?
[x] Are you running the latest version?
[x] Did you check for similar issues?
[x] Did you perform a cursory search?

Description
I try to login using the tokenAuth Mutation, but when I this, I get:
{
"data": null,
"errors": [
{
"message": "'StrawberryField' object has no attribute 'get_result'",
"locations": [
{
"line": 2,
"column": 5
}
],
"path": [
"tokenAuth"
]
}
]
}
Steps to Reproduce

[Clone this repo]
git clone https://github.com/nrbnlulu/strawberry-django-auth.git
and cd quickstart

[Install requirements.txt]
pip install -r requirements.txt

requirements (btw. I am using an anaconda3 env):
anyio==3.6.1
appdirs==1.4.4
asgiref==3.5.2
attrs @ file://[...]
backports.cached-property==1.0.2
black==19.10b0
certifi @ file://[...]
click==8.1.3
Django==4.0.6
django-admin-display==1.3.0
django-cors-headers==3.13.0
django-filter==22.1
django-mathfilters==1.0.0
graphql-core==3.2.1
h11==0.13.0
idna==3.3
mypy-extensions==0.4.3
packaging==21.3
pathspec==0.7.0
Pillow==9.2.0
psutil==5.9.1
Pygments==2.12.0
PyJWT==2.4.0
pyparsing==3.0.9
python-dateutil==2.8.2
python-multipart==0.0.5
regex @ file://[...]
six==1.16.0
sniffio==1.2.0
sqlparse==0.4.2
starlette==0.20.4
strawberry-django-auth==0.3.3.2
strawberry-django-jwt==0.2.2
strawberry-graphql==0.121.0
strawberry-graphql-django==0.4.0
toml @ file://[...]
typed-ast @ file://[...]
typing_extensions==4.3.0
uvicorn==0.18.2

[Migrating and creating superuser]
python manage.py migrate
python manage.py createsuperuser

[Running server and requesting]

python manage.py runserver
Go to http://localhost:8000/graphql
Sending: (https://nrbnlulu.github.io/strawberry-django-auth/quickstart/#login)
mutation {
tokenAuth(username: "oc7o", password: "1234Password") {
success
errors
obtainPayload {
token
refreshToken
refreshExpiresIn
payload {
exp
origIat
username
}
}
}
}
Expected behavior
Getting something like that... (https://nrbnlulu.github.io/strawberry-django-auth/quickstart/#login)
{
"data": {
"tokenAuth": {
"success": true,
"errors": null,
"obtainPayload": {
"token": "eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJleHAiOjE2NTM2MDkxOTQsIm9yaWdJYXQiOjE2NTM2MDg4OTQsInVzZXJuYW1lIjoibmV3X3VzZXIxIn0.FxXaWKToi5mTzPcKAz16K2GWnIvsTBKio_BEyCdF5fs",
"refreshToken": "e7a784476810f880eb93f3827cd881d834235598",
"refreshExpiresIn": 1654213694,
"payload": {
"exp": 1653609194,
"origIat": 1653608894,
"username": "oc7o"
}
}
}
}
}
Actual behavior
Console Output:
'StrawberryField' object has no attribute 'get_result'
GraphQL request:2:5
1 | mutation {
2 |     tokenAuth(username: "oc7o", password: "1234Password") {
|     ^
3 |     	errors
Traceback (most recent call last):
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/graphql/execution/execute.py", line 528, in await_result
return_type, field_nodes, info, path, await result
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/strawberry_django_jwt/middleware.py", line 129, in resolve
return await result
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/strawberry/schema/schema_converter.py", line 501, in _async_resolver
return await await_maybe(_get_result(source, strawberry_info, **kwargs))
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/strawberry/utils/await_maybe.py", line 12, in await_maybe
return await value
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/gqlauth/bases/mixins.py", line 261, in afield
return await sync_to_async(cls.resolve_mutation)(info, **kwargs)
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/asgiref/sync.py", line 435, in call
ret = await asyncio.wait_for(future, timeout=None)
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/asyncio/tasks.py", line 408, in wait_for
return await fut
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/asgiref/current_thread_executor.py", line 22, in run
result = self.fn(*self.args, **self.kwargs)
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/asgiref/sync.py", line 476, in thread_handler
return func(*args, **kwargs)
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/gqlauth/user/resolvers.py", line 461, in resolve_mutation
res = cls.obtain.get_result(None, None, [cls, info], query_input)
AttributeError: 'StrawberryField' object has no attribute 'get_result'
Stack (most recent call last):
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/strawberry/django/views.py", line 257, in dispatch
result = await self.schema.execute(
File "[...]/opt/anaconda3/envs/oi/lib/python3.10/site-packages/strawberry/schema/schema.py", line 206, in execute
self.process_errors(result.errors, execution_context=execution_context)
Requirements
See above
If you need more infos, pls say.
🐙 oc7o

Hey!
Update strawberry :smile:  Its a known issue

Oh... sometimes anaconda is weird 🧐
Thank you for your help!
😁

repo: nrbnlulu/strawberry-django-auth


text:
Visualisation popup not activated with touch screen

The Visualisation popup is a great new feature, offering huge possibilities.
However, on touch screen, the popup is not activated when the user press on the map marker.

I do not have a touch screen to test on. I will gladly accept a PR.

Sorry it's out of my skills.
I was thinking that someone could link the default click on a marker to open the popup as well.
In that way the touch event that acts as a clic would also open it.
We have a nice 4x24p touch wallscreen dedicated to Kibana, all other features works perfectly, it's very nice.

authors: DavidCroenne nreese


text:
wifi: Pull fixes for RC2

Fixes for:

SR co-ex Boards
TX memory leak
Offloaded Raw TX
FW blobs update

Scan-only firmware patch fix
Co-ex optimization revert
Power backoff fix

net capture build fix

The following west manifest projects have been modified in this Pull Request:

Name
Old Revision
New Revision
Diff

hal_nordic
https://github.com/zephyrproject-rtos/hal_nordic/commit/cb7600a1be4c8b177867e6d463729c07dd3f6d73
https://github.com/zephyrproject-rtos/hal_nordic/commit/1d290096e7d0b84eed9bc428a485ca63be728458 (master)
zephyrproject-rtos/hal_nordic@cb7600a1..1d290096

Note: This message is automatically posted and updated by the Manifest GitHub Action.

repo: nrfconnect/sdk-zephyr


text:
Add BoltDB support

There is a suggestion (hi, @realloc!) to try to use BoltDB as a backend storage for blockchain. I think we can add support for it not removing LevelDB support (via the Store interface), then test it and decide which one should be the default.

I'd recommend going with another compiled library s.a. RocksDB or more recent MS FASTER. While DB IO is certainly not the bottleneck of the system might be worth considering..
https://rocksdb.org/ (several go wrappers available) / https://github.com/Microsoft/FASTER

We have a Store interface that could be used to support just about any key-value DB, so if there is an interest in something else, please submit a separate issue. At the moment I think that adding various DBs is not a priority for us since it doesn't really change much in the end result, we have way more problematic areas than trying to squeeze yet another 0.5% of performance out of our backend DB.
Also, note that MS FASTER tried to solve one particular thing (and supposedly solved it nicely) --- dealing with lots of (concurrent) updates, while we just don't have that problem. Our DB usage pattern is a lot of writes during initial sync, then it's all reads with occasional (~one time in 15 seconds) write and rewrite of the top block pointer at the same time. I think even BerkeleyDB could handle this kind of load reasonably well.
BoltDB is just easy to add and nice to play with to really see whether it makes any difference (I doubt that, but in the end who knows until we really test it).

I believe in some future we can add several DB and do some benchmarking and choose which one fits better by several params like:
how it's maintained/how the code looks like/performance, etc
But as of now already added BoltDB in separate branch(will do a pr tomorrow)

Just as a side note --- I'm currently synchronizing with mainnet and recent blockchain persist messages look like this:
INFO[66867] blockchain persist completed                  blockHeight=2872566 headerHeight=4286335 persisted=192 took=4.466865774s
INFO[66869] blockchain persist completed                  blockHeight=2872626 headerHeight=4286335 persisted=60 took=1.428378985s
INFO[66877] blockchain persist completed                  blockHeight=2872786 headerHeight=4286335 persisted=160 took=6.557633855s
INFO[66877] blockchain persist completed                  blockHeight=2872787 headerHeight=4286335 persisted=1 took=9.697589ms
INFO[66881] blockchain persist completed                  blockHeight=2872871 headerHeight=4286335 persisted=84 took=2.969553877s
INFO[66893] blockchain persist completed                  blockHeight=2873003 headerHeight=4286335 persisted=132 took=11.576151847s
INFO[66900] blockchain persist completed                  blockHeight=2873124 headerHeight=4286335 persisted=121 took=5.524117051s
INFO[66903] blockchain persist completed                  blockHeight=2873209 headerHeight=4286335 persisted=85 took=2.531495163s
INFO[66914] blockchain persist completed                  blockHeight=2873359 headerHeight=4286335 persisted=150 took=9.386064462s
INFO[66918] blockchain persist completed                  blockHeight=2873444 headerHeight=4286335 persisted=85 took=3.735638741s
INFO[66921] blockchain persist completed                  blockHeight=2873501 headerHeight=4286335 persisted=57 took=1.726460232s
INFO[66921] blockchain persist completed                  blockHeight=2873504 headerHeight=4286335 persisted=3 took=68.011841ms
INFO[66932] blockchain persist completed                  blockHeight=2873649 headerHeight=4286335 persisted=145 took=9.850441317s
INFO[66932] blockchain persist completed                  blockHeight=2873650 headerHeight=4286335 persisted=1 took=8.317091ms
INFO[66937] blockchain persist completed                  blockHeight=2873725 headerHeight=4286335 persisted=75 took=4.596761086s
INFO[66945] blockchain persist completed                  blockHeight=2873851 headerHeight=4286335 persisted=126 took=6.578007231s
INFO[66953] blockchain persist completed                  blockHeight=2873939 headerHeight=4286335 persisted=88 took=7.103702191s
INFO[66974] blockchain persist completed                  blockHeight=2874078 headerHeight=4286335 persisted=139 took=19.993060663s
INFO[66976] blockchain persist completed                  blockHeight=2874161 headerHeight=4286335 persisted=83 took=1.345255423s
INFO[66979] blockchain persist completed                  blockHeight=2874277 headerHeight=4286335 persisted=116 took=1.902362157s
INFO[66979] blockchain persist completed                  blockHeight=2874278 headerHeight=4286335 persisted=1 took=5.049681ms
INFO[66986] blockchain persist completed                  blockHeight=2874407 headerHeight=4286335 persisted=129 took=5.989910681s
INFO[66986] blockchain persist completed                  blockHeight=2874408 headerHeight=4286335 persisted=1 took=56.686212ms
INFO[66990] blockchain persist completed                  blockHeight=2874493 headerHeight=4286335 persisted=85 took=2.784959705s
INFO[66995] blockchain persist completed                  blockHeight=2874637 headerHeight=4286335 persisted=144 took=3.800083311s
INFO[66997] blockchain persist completed                  blockHeight=2874731 headerHeight=4286335 persisted=94 took=1.195027s
INFO[67001] blockchain persist completed                  blockHeight=2874875 headerHeight=4286335 persisted=144 took=2.946860945s
INFO[67001] blockchain persist completed                  blockHeight=2874876 headerHeight=4286335 persisted=1 took=4.50594ms
INFO[67003] blockchain persist completed                  blockHeight=2874948 headerHeight=4286335 persisted=72 took=830.322076ms

Notice how much time it takes to flush them. It wasn't like that in the beginning of the sync, it was like 2-10ms for a batch of 200 blocks. So it really does make sense to try different options and compare them.

authors: fabwa roman-khimov volekerb

repo: nspcc-dev/neo-go


text:
Sync pool and client interfaces

reference #380

Session management. As sessions are inherently tied to specific nodes we need to keep this logic of implicit session management by Pool. It should be configurable at the same time.

I thought we decided to sync client/pool interfaces and build some wrapper (high level client) to manage to sessions and other staff inside it.
New pool implementations should be deadly simple and only manage Clients.
Current/old implementation of Pool is going to be live for backward compatibility, until we complete these full circle.
Have plans changed?

Usually you can't create a session with one node and reuse it for another, that's the problem, it can be done transparently and it has to be managed by the Pool, at least in majority of cases. Waiting logic (or slicing, or SyncContainerWithNetwork) is a different thing entirely, it doesn't care about particular node/client, so it can reuse some common interface.

What does pool: Sessions commit mean? Is it a draft PR?

Yes, after discussions some functions interfaces were changed, it was WIP commits. I should to mark them properly, PR as well

Let's narrow down the scope of this PR, leaving #443, #444 and #445 as separate issues.

Can/do we add a compile-time test that proves interfaces are the same?

As we've discussed previously, we don't want to add some monster interface that covers both implementations, it's not really needed. Packages using these functions (so-called "upper layer" like slicer) will just accept the part of the interface they need and that's where we could easily check that both in fact satisfy it.

authors: roman-khimov smallhive

repo: nspcc-dev/neofs-sdk-go


text:
Merging in earlier private changes

Duplicate

repo: ntent/nexus-cli


text:
Hotkey conflict

Description:
After installing Hydrogen package to Atom Editor my ctrl-c hotkey started to does not work. I noticed from keybinding resolver one of the Hydrogen command (interrupt kernel) uses ctrl-c either. By the way, I had to uninstall it and removed this lines from cson files.
Versions:
Atom 1.2.11, Hydrogen: last, OS. Win 10

That's strange. Hydrogen shouldn't add ctrl-c to the keybindings by it self. Checkout the list of keymaps.

Atom 1.2.11

Do you mean Atom 1.21.1? Atom 1.2 almost two years old. This would imply that Hydrogen is very too, since it requires a fairly recent version of Atom.

I can say with full certainty that this is not caused by the hydrogen install itself.
It's possible the keymap is coming from another package or personal keymap file. I'd recommend reinstalling hydrogen in case the install was modified locally. Also check apm links if you may have created a Dev version and added this to the keymap.
Let us know if you have questions!

I applied 'Checkout the list of keymaps' advice of @lgeiger  and it worked. Maybe another package caused the problem like @BenRussert. There was no version problem.

authors: BenRussert lgeiger suatatan

repo: nteract/hydrogen


text:
Support Vegalite 4

Prerequisites

[ x] Have you checked the solutions in our troubleshooting guide for common problems ?
[ x] Have you checked that your issue isn't already filed ?

Description
Altair charts empty in atom/hydrogen
Steps to Reproduce

Try to generate any altair chart (one example below)
Execute
Observe emptiness of output

code
import altair as alt

from vega_datasets import data
import pandas as pd
from urllib.request import urlretrieve

urlretrieve(data.stocks.url, "stocks.csv")
stocks = pd.read_csv("stocks.csv")

alt.Chart(stocks).mark_line().encode(x="date:T", y="price:Q", color="symbol:N")

Any chart will do. The problem seems to have arisen switching to altair 4.0.0 which uses vega lite 4 from altair 3.2.2. Reverting to that version of altair restores the output
Versions
OS version:
Os x catalina

atom --version

Atom    : 1.42.0
Electron: 4.2.7
Chrome  : 69.0.3497.128
Node    : 10.11.0

apm --version

apm  2.4.3
npm  6.2.0
node 10.2.1 x64
atom 1.42.0
python 3.6.9
git 2.16.2

Hydrogen version:

[Your Hydrogen's version]
Hydrogen
├── 2.13.1
Plugins
Have you installed and activated any of the Hydrogen plugins below ?

[ ] hydrogen-python
[ ] Hydrogen Launcher
[ ] Data Explorer

Logs
[Please post any error logs and the output of the developer tools as described in our Debugging Guide.]
Expected behavior
Seein charts
Screenshots
[If applicable, add screenshots to help explain your problem.]
Additional context
[Add any other context about the problem here.]

Hydrogen doesn't yet support Vegalite 4. The nteract Vega library has a published prerelease for Vegalite 4, but for hydrogen to adopt vegalite 4 the package must publish an official release which we do on a monthly schedule

Could you point me to the nteract vega library which is in prerelease? I'd like to keep an eye on it.
Reason (only if you are interested): I maintain a package called altair-recipe that can be used to produce charts in atom with hydrogen, but I got my (few) users stuck with the latest release. If this lib is imminent, I can tell them to downgrade by one step as a workaround. If it isn't I have to do something harder.

@nteract/transform-vega on npm. it's a package in the nteract monorepo. The prelease has vegalite4 support. Hydrogen only works on official releases.

@piccolbo can you try to play around with the current master branch ? There Vegalite 4 will be supported.
Try apm dev Hydrogen and restart Atom.

Sorry to be unresponsive, life took over. I don't see any changes trying the above steps. If I try alt.renderers.enable('mimetype') in analogy with nteract and vscode, I get the following error
SyntaxError: Unexpected token o in JSON at position 1

I just tried apm dev Hydrogen and am seeing the same output:
SyntaxError: Unexpected token o in JSON at position 1

authors: andyreagan aviatesk piccolbo wadethestealth


text:
Add auto-scroll feature

Add basic functionality for the auto-scroll feature.
Special thanks to @lgeiger for helping me getting started!
Fixes #774

Welcome to nteract 🎉 🚀

Does not seem to work for me even with the option enabled. Anyone else have this issue?

@joolius this autoscroll should happen inside the results view. So if you have a for loop that counts to 1000. You should see 1000 rather than 0.

Does not seem to work for me even with the option enabled. Anyone else have this issue?

@juliuscrn
yeah. it's been driving me a bit batty for a while. the behavior i'm seeing is that the output window won't autoscroll during the generation of output, but WILL jump all the way to the end once the kernel has finished running, which...is i don't think what the intended functionality of autoscroll was meant as. i want to see output like i would in a terminal window, i.e. as output is generated, newest output is the bottom line and oldest line gets scrolled out past whatever the window height is. I've tried a full reinstall. manually setting autoScroll under config. no dice. i'm a bit hesitant to start fiddling with the actual config files as that's not my language of choice, so i'd be spitballing at best.

@shr00mie you should open a separate issue for that issue. But a code example and gif would be extremely helpful because intended functionality should be every time the output component is updated.

@wadethestealth Hey, Thomas. Think you assisted me with something last time around when you guys were implementing a new feature. Hope you're doing well. As requested, i'll open up a new issue for this. just grabbed a video. will convert and upload with some example code of behavior.

authors: dwolfschlaeger joolius lgeiger shr00mie wadethestealth


text:
Topic/#2 create private catalog

プライベートカタログの実装 close #2

よさげ :+1:

LGTM

repo: nttcom/metemcyber


text:
在更新模式下 用户更新CK，禁用的变量能自动启用吗？

如果需要更新CK的状态是禁用的，更新后自动启用，这个能实现吗？

正式版v1.7已支持此功能


text:
为什么select top 10 from table 会返回所有的数据

为什么select top 10 from table 会返回所有的数据 我的access 中有1000条数据
query 执行 select top 10 from table 会返回1000条， 有什么方式解决么？
感觉和这个有点类似  https://github.com/nuintun/node-adodb/issues/107
@nuintun

 const ADODB = require("node-adodb")
 const connection = ADODB.open(`Provider=Microsoft.ACE.OLEDB.12.0;Data Source=${filePath};Jet OLEDB:Database Password=${password};`, true)
 connection .query( `SELECT TOP 10, \`column1\` FROM \`table\` ORDER BY \`column1\``)
                    .then((data) => {

})

node-adodb 只负责中转 sql 和返回结果，出现各种查询问题一般都是 sql 不对，自行排查 sql 语句！

repo: nuintun/node-adodb


text:
🛑 Difesa is down

In 8766dda, Difesa (http://www.difesa.it/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Difesa is back up in 57c7c2b.


text:
🛑 Università e ricerca is down

In c83fa59, Università e ricerca (https://www.mur.gov.it/it) was down:

HTTP code: 403
Response time: 570 ms

Resolved: Università e ricerca is back up in 96d5424 after 155 days, 20 hours, 56 minutes.


text:
🛑 Università e ricerca is down

In e7fc1f2, Università e ricerca (https://www.mur.gov.it/it) was down:

HTTP code: 403
Response time: 610 ms

Resolved: Università e ricerca is back up in d55b4ae.


text:
🛑 Guardia di Finanza is down

In 0fef74e, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in 58e94b2 after 5 minutes.


text:
🛑 Guardia di Finanza is down

In 13b0e4f, Guardia di Finanza (https://www.gdf.gov.it) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Guardia di Finanza is back up in b3dcd9f after 12 minutes.


text:
Lua error

I get this error every time I click something from the Outfitter menu. Thank you
Message: ...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1422: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: LibDropdownFrame0:SetPoint.
Time: Wed Jul 31 08:54:31 2024
Count: 1
Stack: ...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1422: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: LibDropdownFrame0:SetPoint.
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1422: in function `Show'
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1558: in function `ToggleMenu'
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1504: in function <...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1503>
Locals: self =  {
menuFrame = LibDropdownFrame0 {
}
}
items =  {
type = "group"
args =  {
}
}
point = "TOPLEFT"
relativeTo = OutfitterItem3OutfitMenu {
point = "TOPLEFT"
xOffset = 0
AutoSelectValue = true
Icon = OutfitterItem3OutfitMenuIcon {
}
relativeTo = OutfitterItem3OutfitMenu {
}
dropDownMenu =  {
}
yOffset = 3
relativePoint = "TOPRIGHT"
ParentItem = OutfitterItem3 {
}
AnchorPoint = "TOPLEFT"
items =  {
}
AnchorRelativePoint = "TOPRIGHT"
Button = Button {
}
}
relativePoint = "TOPRIGHT"
xOffset = 0
yOffset = 3
thank you

I'm going to put up a new version of outfitter with updated version of libdropdown if you can say if that solves it for you. It at least makes outfitter use the same version as all other addons and I don't really see a side effect.

I've just downloaded the new version and the error is still there. ty
Message: ...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1422: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: LibDropdownFrame0:SetPoint.
Time: Tue Aug  6 19:43:55 2024
Count: 1
Stack: ...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1422: Action[SetPoint] failed because[SetPoint would result in anchor family connection]: attempted from: LibDropdownFrame0:SetPoint.
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1422: in function Show' [string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1558: in function ToggleMenu'
[string "@Interface/AddOns/Outfitter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua"]:1504: in function <...tter/Libraries/MC2UIElementsLib/MC2UIElementsLib.lua:1503>
Locals: self =  {
menuFrame = LibDropdownFrame0 {
}
}
items =  {
type = "group"
args =  {
}
}
point = "TOPLEFT"
relativeTo = OutfitterItem2OutfitMenu {
point = "TOPLEFT"
xOffset = 0
AutoSelectValue = true
Icon = OutfitterItem2OutfitMenuIcon {
}
relativeTo = OutfitterItem2OutfitMenu {
}
dropDownMenu =  {
}
yOffset = 3
relativePoint = "TOPRIGHT"
ParentItem = OutfitterItem2 {
}
AnchorPoint = "TOPLEFT"
items =  {
}
AnchorRelativePoint = "TOPRIGHT"
Button = Button {
}
}
relativePoint = "TOPRIGHT"
xOffset = 0
yOffset = 3

It's probably caused by another addon. So testing without other addons would be nice.
Did see some fix weakauras addon used for this in the past but would be nice to know how I can reproduce this myself.

I'll try to find the culprit, I don't use Weakauras addon.

@Meilinn Which other addon?

@b-morgan BlizzMove

authors: Meilinn b-morgan nulian

repo: nulian/Outfitter


text:
Why don't testing execute continuous?

Hi, @nullobject
I think testing should be executed continuous. But https://github.com/nullobject/rein/pull/5 had closed by you.
Why? Because 1.8.7 and 1.9.2 are not supported version ?
if you don't mind, can I add .travis.yml and set up ?

I have added appraisal, thanks.

authors: a-suenami nullobject

repo: nullobject/rein


text:
C897 cli docs

This PR adds a new routine that generates a proper markdown file (docs/CLI.md) based on the commands built for our CLI.
Generating these docs also pointed out a lack of documentation in some places and some opportunities to improve for others. Please review my changes to the commands and make sure they are all correct and that you are ok with the changes.
To generate the CLI.md file, simply run make docs.

I wasn't familiar with how to do go templates so I opted for the simple path (at least for me). :)
I totally agree that we should add a bunch of examples for each. I wasn't sure where to put that on the CLI command structs.

repo: nullstone-io/nullstone


text:
USDE for Progressive, Delete/Recreate

Summary
For Progressive, there are 3 things to consider:

"recreate" fields: Some fields are only safe to change with Progressive and not PPND - this means that even if the user prefers PPND, it should be done with Progressive (or there will be completely breakage otherwise) - the alternative is to delete and re-create (basically, they require a recreation in either case). There can be a "recreateStrategy" for this, which can either be "progressive" or "delete-recreate". And actually if the user's "upgradeStrategy", I think "delete-recreate" should actually mean: "pause, and then delete/recreate"
"data-loss" fields: We still care about all of the data loss fields, which would indicate that we should do "Progressive" rather than "Direct Apply". This is still determined by "upgradeStrategy".
"progressive-desired" fields: if the Image changes, that's a good time to do Progressive, since this is when we can most benefit from the Blue/Green aspect of Progressive. This would be used if upgradeStrategy==progressive. It is only really meaningful for MonoVertex, since for Pipeline we will already do Progressive, since it's a "data loss" field.

Examples of Case 1:
Pipeline:

InterstepBufferServiceName (we should move this from the data loss fields to here)

isbsvc:

provider change: jetstream <-> redis
replicas
PVC
Any field change that is not allowed in a statefulset (not sure what this includes)

Restructuring of the USDE:
I'm thinking something like this...but open to improvements on naming...
dataLoss:                      # case 2: these are the fields we have now
   pipeline:
   interstepbufferservice:
recreate:  # case 1
   pipeline:
   interstepbufferservice:
progressive:    # case 3
   pipeline:
   monovertex:

Configurability in numaplane-controller-config.yaml/user strategy config:
In addition to defaultUpgradeStrategy, we can also have defaultRecreateStrategy for case 1 above (either "delete-recreate" or "progressive").

Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

I'm thinking we would in our usde_config.yaml file have 2 lists instead of just 1.
Currently, we have one list for "PPND" - or we could think of it as a "data loss" list.
We would need to have 2 lists instead. I am thinking either of these options:

One list for "PPND" (which is what we have) - if user preferred strategy is PPND, these are the fields that cause them to do PPND over Direct Apply; a second list for "Progressive" - if user preferred strategy is Progressive, these are the fields that cause them to do Progressive over Direct Apply
One list for "data loss concerns" (which is what we have) and a second list for "requires creating a second pipeline or isbsvc" - if user preferred strategy is PPND, the "data loss concerns" list are the fields that cause them to do PPND over Direct Apply; if user preferred strategy is Progressive, we Progressive over Direct Apply if the field is in either list.

These two options are mostly equivalent; it's just that in the second case the two lists are mutually exclusive and in the first case there's redundancy between the two lists.

Perhaps we can break this into sub-issues. I think the highest priority aspect of this is to add the notion of "recreate" fields, which will cause us to correctly do Progressive rather than "NoStrategy".

moving to future sprint

added matrix of upgrade strategies I'm imagining: https://docs.google.com/spreadsheets/d/1peDmaLS-xvPjFrO_zstUhBwR9cVm8t10W81FjhGJa9c/edit?gid=0#gid=0

repo: numaproj/numaplane


text:
Implement mode “wrap” for numba.stencil

Feature request
Currently, even though numba.stencil is designed in a way that allows different “modes”, it only supports one:

1.11.4.2. mode
The optional mode parameter controls how the border of the output array is handled. Currently, there is only one supported value, "constant".
— https://numba.pydata.org/numba-doc/latest/user/stencil.html#mode

However, other options would certainly be useful. In my case, when dealing with differential equations with periodic boundary conditions, numba.stencil in its current form unfortunately can’t be used. If a mode 'wrap' were implemented, where array accesses outside the valid range would be taken modulo the length of the relevant array dimension, numba.stencil could also handle periodic boundary conditions.
For completeness, perhaps it is worth to draw inspiration from scipy.ndimage (e. g. scipy.ndimage.laplace, scipy.ndimage.convolve) for consistency (considering the identical naming and functionality of cval, perhaps this is already on the radar?):

'reflect' (d c b a | a b c d | d c b a)
The input is extended by reflecting about the edge of the last pixel.
'constant' (k k k k | a b c d | k k k k)
The input is extended by filling all values beyond the edge with the same constant value, defined by the cval parameter.
'nearest' (a a a a | a b c d | d d d d)
The input is extended by replicating the last pixel.
'mirror' (d c b | a b c d | c b a)
The input is extended by reflecting about the center of the last pixel.
'wrap' (a b c d | a b c d | a b c d)
The input is extended by wrapping around to the opposite edge.

Is this currently on the numba roadmap? If not, would it be possible for a high-level breakdown of what this might entail to see if a contributor may be able help out?

I've  created the following decorator, which adds the border using numpy pad and removes it afterwards, effectivley allowing the stencil decorator to use all border options of numpy.pad:
from numba import stencil
import numpy as np

def applyBorder(borderWidth, mode="reflect", **kwargs):
    def advStencil_decorator(func):
        def func_wrapper(a, *parms):
            a=np.pad(a, borderWidth, mode=mode, **kwargs)
            res  = func(a, *parms)
            return res[borderWidth:-borderWidth,borderWidth:-borderWidth]
        return func_wrapper
    return advStencil_decorator

@applyBorder(2, "reflect")
@stencil
def test(a):
    return a[-1,0] + a[1,0]

bla = np.arange(20).reshape((4,5))
print(test(bla))

@kleinsimon Please see the original post.  The design was to integrate different border handling into the stencil decorator itself over time.  A benefit then is that you don't have to specify the borderWidth but it can be computed automatically (or through the neighborhood option.)  Also, have you tested this by calling test from within a parallel region?  I don't think that is going to work.  Can you adapt your approach to work within the stencil decorator and within a parallel context?

Hey! What's the status for this ? It would greatly benefit me.

repo: numba/numba


text:
cache missed for str arguments

Reporting a bug

[x] I have tried using the latest released version of Numba (most recent is
visible in the change log (https://github.com/numba/numba/blob/master/CHANGE_LOG).
[x] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

First define a function with str type argument, and save it to mymod.py
from numba import njit
import numpy as np

@njit(cache=True)
def foo(array, method='abc'):
    pass

Then run this script:
from mymod import foo, np

foo(np.arange(10))

index = foo._cache._cache_file._load_index()
keys = list(index.keys())
# print(index)
print(foo._cache_misses)
print(foo._cache_hits)

print(foo.signatures)
print(foo.signatures[0] == keys[0][0])
print(foo.signatures[0][1].key)
print(keys[0][0][1].key)

run the script for at least 2 times to let it cached
Counter({(array(int64, 1d, C), omitted(default='abc')): 1})
Counter()
[(array(int64, 1d, C), omitted(default='abc'))]
False
(<class 'str'>, 140574134474608)
(<class 'str'>, 140565616270704)

Process finished with exit code 0

I found cache is not working here, because str argument get the hash key from its __id__ method. And it's often the case that the 'abc' from cache and from call_signature don't share the same id. This leads to cache misses.

Many thanks for the report - I can reproduce this behavior, and will bring up a discussion about it in the next triage meeting.

Duplicate of https://github.com/numba/numba/issues/6957 ? Closed by https://github.com/numba/numba/pull/7422 ?

Using current mainline 714c0c44ec64e01e8de52c3906e947d10421f420 which has https://github.com/numba/numba/pull/7422 merged. The above reproducer gives this on second invocation:
Counter()
Counter({(array(int64, 1d, C), omitted(default='abc')): 1})
[(array(int64, 1d, C), omitted(default='abc'))]
True
(<class 'str'>, 'abc')
(<class 'str'>, 'abc')

#7422 fixed. Closing.

authors: auderson gmarkall stuartarchibald


text:
Numba confuses float32 and float64 in numpy-array causing compilation failure

Reporting a bug

[X] I have tried using the latest released version of Numba (most recent is
visible in the release notes
(https://numba.readthedocs.io/en/stable/release-notes-overview.html).
[X] I have included a self contained code sample to reproduce the problem.
i.e. it's possible to run as 'python bug.py'.

Bug description
Minimal reproducing example:

import numpy as np
from numba import njit

@njit
def get_array(velocities):
    return np.zeros((3,), dtype=np.float32)

@njit
def sim_loop():
    velocities = np.zeros((3,), dtype=np.float32)

    for _ in range(10):
        velocities = 3. * get_array(velocities)

sim_loop()

Expected behavior: Compiles
Obeserved behavior: Fails to compile with Cannot unify array(float32, 1d, C) and array(float64, 1d, C) for 'velocities.2'
Full output:

Click to expand
Traceback (most recent call last):
File "/home/user/numba_scalar_mismatch.py", line 15, in
sim_loop()
File "/home/user/miniconda3/envs/py311/lib/python3.11/site-packages/numba/core/dispatcher.py", line 468, in _compile_for_args
error_rewrite(e, 'typing')
File "/home/user/miniconda3/envs/py311/lib/python3.11/site-packages/numba/core/dispatcher.py", line 409, in error_rewrite
raise e.with_traceback(None)
numba.core.errors.TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Cannot unify array(float32, 1d, C) and array(float64, 1d, C) for 'velocities.2', defined at /home/user/numba_scalar_mismatch.py (12)
File "numba_scalar_mismatch.py", line 12:
def sim_loop():

for _ in range(10):
^

During: typing of assignment at /home/user/numba_scalar_mismatch.py (12)
File "numba_scalar_mismatch.py", line 12:
def sim_loop():

for _ in range(10):
^

Tested with:
Python 3.11
numpy 1.26.3
numba 0.58.1
Somehow numba thinks the array is of type float64 but actually multiplying a float32-array with a constant results in a float32-array.
Note that the compilation succeeds when replacing the function call to get_array with the np.zeros((3,), dtype=np.float32)-expression. It also succeeds when velocities is not passed to the function or if the scalar multiplication (or the loop) is omitted.
Seems similar to https://github.com/numba/numba/issues/9025
Thanks for having a look

Thanks for the insightful comment, I assumed that scalar multiplication between a float32 array and a Python scalar (which has 64-bit precision) would always result in a float32 array. Explicitly casting the scalar does indeed solve my problem, thank you.
The initial motivation for creating this issue was mostly because I was confused as to why the otherwise same example would compile if I did not pass the velocities-array to the get_array-function in the for-loop body.
Consider these new examples which I think are equivalent to the original one, only simpler:
(1) Compiles:
@njit
def sim_loop():
    velocities = np.zeros((3,), dtype=np.float32)
    for _ in range(2):
        velocities = np.zeros((3,), dtype=np.float64)
sim_loop()

(2) does not compile (Cannot unify array(float32, 1d, C) and array(float64, 1d, C)):
@njit
def print_array(array): print(f"{array}")

@njit
def sim_loop():
    velocities = np.zeros((3,), dtype=np.float32)
    for _ in range(2):
        print_array(velocities)
        velocities =  np.zeros((3,), dtype=np.float64)
sim_loop()

(3) Compiles again, after unrolling the loop:
@njit
def print_array(array): print(f"{array}")

@njit
def sim_loop():
    velocities = np.zeros((3,), dtype=np.float32)
    print_array(velocities)
    velocities =  np.zeros((3,), dtype=np.float64)
    print_array(velocities)
    velocities =  np.zeros((3,), dtype=np.float64)
sim_loop()

After reading this document about the implementation of the numba type inference, I think I understand why this happens.
Actually, numba supports that a Python variable changes its type during its lifetime, that's why (1) compiles, right ?
It also supports compiling the same function for different argument types, that's why (3) compiles, right ?
But it does not support dynamic dispatch, which would be needed to compile (2), since it depends on the iteration which of the two versions of print_array we have to call, is this correct ?
Many thanks !

Actually, numba supports that a Python variable changes its type during its lifetime, that's why (1) compiles, right ?
It also supports compiling the same function for different argument types, that's why (3) compiles, right ?
But it does not support dynamic dispatch, which would be needed to compile (2), since it depends on the iteration which of the two versions of print_array we have to call, is this correct ?

Yes, yes and yes.
Numba uses these typing restrictions to maximize its (and LLVM's) ability to optimize the function. It more like a performance linter at this point.

Ok, makes sense, thanks for answering my questions

closing this as casting rules will be changed due to https://github.com/numba/numba/issues/9409