multiple nuxt instances in layout

Version
v2.12.2
Reproduction link
https://nuxtjs.org/
Steps to reproduce
Weird thing, I have double nuxt instance in my defalut layout, this is my default.vue file

I tried multiple combinations, I noticed that when I move <nuxt /> to the bottom of parent div, this problem disappear, and everything works fine.

What could be the reason?
What is expected ?

What is actually happening?

This bug report is available on Nuxt community (#c10792)

I believe this could be related to https://github.com/nuxt/nuxt.js/issues/5615 which is fixed in the latest version

same problem in v2.13.0

simple fix, and problem solved, but still this is a bug not solved in latest release
https://github.com/nuxt/nuxt.js/issues/5703

i change  to  and it seems to fix it

simple fix, and problem solved, but still this is a bug not solved in latest release
#5703

Wrap inside a div doesn't work for me :/ I have also this bug in 2.13.3

If the page is rendered server-side with a specific layout like "guest", then the page is changed with another layout like "authenticated", nuxt will not render multiple times the layout. But if I enter directly on the page (with the layout "authenticated"), the bug is happening.


Collections in starting template

I honestly think it would really help developers get started if we had a collection of some sort in our starting example.
Like a lookup map or commented out code or something. Just to save them the trouble looking up how to instantiate a collection

Since native collections work without a problem, I still prefer people to navigate the docs to discover about SDK collections
Specially since collections have small perks such as prefixes that need to be understood


"terminate called without an active exception" in default Pipeline constructor

I have tried reinstalling depthai-core (2.15.4 ), reconfiguring and rebuilding, as well as powercycling my computer and all attatched devices. Code fails when calling default constructor of dai::Pipeline, but I haven't found anyone else encountering this error. Also not a consistent error, this code ran fine then stopped working. Ran into this in the past, and it randomly stopped working. Our application needs high reliability, so this isn't an acceptable problem.
Error:
terminate called without an active exception
terminate called recursively
Thread 1 "Inference" received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
Code Snippet:
// Create pipeline
dai::Pipeline pipeline;
std::string mxID = config->get_camera_order()[cam.idx];
std::string nnPath = config->get_engine_path();
// Print which blob we are using
printf("Using blob at path: %s\n", nnPath.c_str());
// Define sources and outputs
auto camRgb = pipeline.create<dai::node::ColorCamera>();
auto detectionNetwork = pipeline.create<dai::node::YoloDetectionNetwork>();
std::shared_ptr<dai::node::XLinkOut> xoutRgb;
if(get_frames){
    xoutRgb = pipeline.create<dai::node::XLinkOut>();
    xoutRgb->setStreamName("rgb");
}
//auto
auto nnOut = pipeline.create<dai::node::XLinkOut>();

Backtrace:
(gdb) bt
#0  0x0000007fa2ece598 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1  0x0000007fa2ecf974 in __GI_abort () at abort.c:79
#2  0x0000007fa316507c in __gnu_cxx::__verbose_terminate_handler() () at /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#3  0x0000007fa3162c54 in  () at /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#4  0x0000007fa3162ca0 in  () at /usr/lib/aarch64-linux-gnu/libstdc++.so.6
#5  0x00000000004fe8b8 in std::thread::~thread() (this=0x7fffffcef0, __in_chrg=<optimized out>) at /usr/include/c++/7/thread:135
#6  0x00000000006bd4d8 in dai::Resources::Resources() (this=0x10ad638 <dai::Resources::getInstance()::instance>)
    at /home/sprayer/depthai-core/src/utility/Resources.cpp:355
#7  0x00000000006bd340 in dai::Resources::getInstance() () at /home/sprayer/depthai-core/src/utility/Resources.cpp:248
#8  0x00000000006b1748 in dai::<lambda()>::operator()(void) const (__closure=0x7fffffd038)
    at /home/sprayer/depthai-core/src/utility/Initialization.cpp:83
#9  0x00000000006b1914 in dai::initialize(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool) (additionalInfo="", in---Type <return> to continue, or q <return> to quit---
stallSignalHandler=true) at /home/sprayer/depthai-core/src/utility/Initialization.cpp:98
#10 0x00000000005c9a54 in dai::Pipeline::Pipeline() (this=0x7fffffdd40) at /home/sprayer/depthai-core/src/pipeline/Pipeline.cpp:21
#11 0x000000000043544c in CameraRunner::run() (this=0x1364be0) at /home/sprayer/Downloads/ComputeUnit/src/depthai_wrapper.cpp:123
#12 0x0000000000452e44 in main(int, char**) (argc=4, argv=0x7fffffecc8) at /home/sprayer/Downloads/ComputeUnit/src/main.cpp:243

Architecture/OS
Jetpack 4.5.1
Jetson TX2

@ejaybennett
Thanks for the report. We haven't observed this issue on 2.15.4 yet.
By the looks of the backtrace, it seems like the lazyThreadDevice was already existent, causing a destructor to fail... But not sure how it could get into this state. Just to verify, can you add the following to that snippet and retest (Resources.cpp:355):
    // Device resources
    // Create a thread which lazy-loads firmware resources package
    if(lazyThreadDevice.joinable()) {
          printf("joinable thread in constructor\n");
          lazyThreadDevice.join();
    }
    lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMapDevice));

Also, can you post a log with DEPTHAI_LEVEL=debug env var set, when this happens?

I got the following error while trying this:
~/depthai-core$ cmake --build build
[  9%] Built target depthai-resources
[ 11%] Building CXX object CMakeFiles/depthai-core.dir/src/utility/Resources.cpp.o
/home/sprayer/depthai-core/src/utility/Resources.cpp: In lambda function:
/home/sprayer/depthai-core/src/utility/Resources.cpp:337:8: error: ‘lazyThreadDevice’ was not declared in this scope
if(lazyThreadDevice.joinable()) {
^~~~~~~~~~~~~~~~
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:5: error: ‘lazyThreadDevice’ was not declared in this scope
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~~~~~~~~~
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:57: error: ‘mtxDevice’ was not declared in this scope
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~~
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:57: note: suggested alternative: ‘Device’
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~~
Device
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:68: error: ‘cvDevice’ was not declared in this scope
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:68: note: suggested alternative: ‘Device’
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~
Device
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:78: error: ‘readyDevice’ was not declared in this scope
hreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~~~~
/home/sprayer/depthai-core/src/utility/Resources.cpp:341:78: note: suggested alternative: ‘Device’
hreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMap));
^~~~~~~~~~~
Device
CMakeFiles/depthai-core.dir/build.make:803: recipe for target 'CMakeFiles/depthai-core.dir/src/utility/Resources.cpp.o' failed
make[2]: *** [CMakeFiles/depthai-core.dir/src/utility/Resources.cpp.o] Error 1
CMakeFiles/Makefile2:114: recipe for target 'CMakeFiles/depthai-core.dir/all' failed
make[1]: *** [CMakeFiles/depthai-core.dir/all] Error 2
Makefile:145: recipe for target 'all' failed
make: *** [all] Error 2

Sorry: Realized I added it to the wrong places. I added it to the file in the right place, and now get the following error when running:
// Device resources
// Create a thread which lazy-loads firmware resources package
if(lazyThreadDevice.joinable()) {
      printf("joinable thread in constructor\n");
      lazyThreadDevice.join();
}
lazyThreadDevice = std::thread(getLazyTarXzFunction(mtxDevice, cvDevice, readyDevice, CMRC_DEPTHAI_DEVICE_TAR_XZ, RESOURCE_LIST_DEVICE, resourceMapDevice));

@ejaybennett
That is odd - can you share a MRE, so I can try reproducing over at my end?
And a run with DEPTHAI_LEVEL=debug env var set, just if there is anything obvious there..

Thanks for the data point @ejaybennett . Did you happen to compile the library and your project with different compilers?


Use blog intro field on blog index, detail; blog bylines, avatars

Resolves #60

This looks cool.
In the issue (#60) it looks like they're circular images but am seeing this locally

Would it help with consistency to do crop them 100px width and 100px height?

Oh haha - I just grabbed some open source generic user icons off the internet. They happened to have circular alpha masks in the images themselves, but I wouldn't consider that part of design spec. Do whatever you like here.


Remove need for JSON validator for consts and enums

Re-writes consts as other types, e.g. arrays with specific prefixItems, ints with minimum==maximum, etc. Enums are then written as anyOf(consts).
This lets us use our internal validation logic rather than relying on jsonschema.
Note: I also fixed the grammar-builder's handling of UnsatisfiableSchemaError in anyOf -- it now appropriately propagates only when there are no valid schemas.

Did you check that we get sensible grammars for enum: ["foo", "bar", "baz"] and enum: [1, 2, 3] and also const: 1 and const: "foo" ? in particular the regex for 1 should be /1/

Did you check that we get sensible grammars for enum: ["foo", "bar", "baz"] and enum: [1, 2, 3] and also const: 1 and const: "foo" ? in particular the regex for 1 should be /1/
I think we can live with select("foo", "bar", "baz") instead of lexeme("foo|bar|baz") for enum for now but would be good to fix at some point (compiler can detect all branches that are regexes and combine them)

Currently just calling select for enums, so we get this for enum: ["foo", "bar", "baz"] (1,2,3 looks the same except they aren't treated as json_string lexemes)
[{'Join': {'sequence': [4],
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Lexeme': {'rx': 'foo',
      'contextual': None,
      'temperature': None,
      'json_string': True,
      'json_allowed_escapes': None,
      'json_raw': None,
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Lexeme': {'rx': 'bar',
      'contextual': None,
      'temperature': None,
      'json_string': True,
      'json_allowed_escapes': None,
      'json_raw': None,
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Lexeme': {'rx': 'baz',
      'contextual': None,
      'temperature': None,
      'json_string': True,
      'json_allowed_escapes': None,
      'json_raw': None,
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Select': {'among': [1, 2, 3],
      'max_tokens': None,
      'name': None,
      'capture_name': None}}]

And consts will look the same but without the select. E.g. const: 1
[{'Join': {'sequence': [1],
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Lexeme': {'rx': '(1)',
      'contextual': None,
      'temperature': None,
      'json_string': False,
      'json_allowed_escapes': None,
      'json_raw': None,
      'max_tokens': None,
      'name': None,
      'capture_name': None}}]

For more complex types, e.g. {"const": {"key": "value"}}, we are getting a full grammar out of it, even though we could in principle rewrite it as a regex...
[{'Join': {'sequence': [9],
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Lexeme': {'rx': 'value',
      'contextual': None,
      'temperature': None,
      'json_string': True,
      'json_allowed_escapes': None,
      'json_raw': None,
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': '"key"',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': ': ',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': '',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Join': {'sequence': [2, 3, 1],
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': '{',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': ', ',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'String': {'literal': '}',
      'max_tokens': None,
      'name': None,
      'capture_name': None}},
    {'Join': {'sequence': [6, 5, 8],
      'max_tokens': None,
      'name': None,
      'capture_name': None}}]

I don't think there's much point rewriting general consts as regexes. The one I worry about is a very large enum with just strings in it (I think it's relatively common) - it's easy to do regex and it will avoid parser limits.

I don't think there's much point rewriting general consts as regexes. The one I worry about is a very large enum with just strings in it (I think it's relatively common) - it's easy to do regex and it will avoid parser limits.

Totally. And I like the idea of detecting this kind of situation in the builder itself.

you mean GrammarBuilder? I think it's not always valid (though it would be valid for JSON)


Multiple security vulnerabilities in dependencies

Hi,
We use yarn and yarn audit in our build pipeline and by upgrading to the latest typedoc version (0.14.2), we have more than 20 vulnerabilities reported in the dependencies of typedoc. I have attached a JSON output containing the details.
audit.json.txt

Thanks for sharing, We'll update our dependencies before the next release which should help fix some of these.

In the meantime I was able to circumvent this problem by adding this into my package.json:
"resolutions": {
    "typedoc/highlight.js/gear-lib/knox/debug": "^2.6.9",
    "typedoc/highlight.js/gear-lib/jshint/cli": "^1.0.0",
    "typedoc/highlight.js/gear-lib/less/clean-css": "^4.1.11",
    "typedoc/highlight.js/gear-lib/less/request": "^2.68.0",
    "typedoc/highlight.js/**/uglify-js": "^2.6.0",
    "typedoc/highlight.js/**/handlebars": "^4.0.0",
    "typedoc/highlight.js/**/mime": "^1.4.1",
    "**/minimatch": "^3.0.2",
    "**/micromatch/braces": "^2.3.1"
  }```

So far I didn't get any errors when running typedoc, but it solved the audit warning.

Is the next release scheduled soon? Many teams have policies against using modules that have reported security vulnerabilities. This seems like a big deal to be open for nearly a month...

Sorry, I'm working on some changes that I'm hoping to get into the next release but I may make an interim release.
Most of the security vulnerabilities are things like minimatch so the security vulnerabilities aren't relevant in this use case but I recognize that those things are hard to sort out.


Visual Studio Exception: Bad UTF-8 encoding (U+FFFD; REPLACEMENT CHARACTER)

Steps to Reproduce

Good day!
The problem appeared after updating Android SDK and Visual Studio.
I tried to roll back to the previous versions, but it did not help, I tried to reinstall both too, but it did not help to.
I suspect that the case is in the description, but I don’t understand where it comes from and where to change it
Logs

Logs

Visual Studio - develop for Windows (the doctor check crashed)
X Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
X Exception: Bad UTF-8 encoding (U+FFFD; REPLACEMENT CHARACTER) found while decoding string: [
{
"instanceId": "f5d8c628",
"installDate": "2022-05-12T07:51:04Z",
"installationName": "VisualStudio/17.2.0+32505.173",
"installationPath": "C:\Program Files\Microsoft Visual Studio\2022\Professional",
"installationVersion": "17.2.32505.173",
"productId": "Microsoft.VisualStudio.Product.Professional",
"productPath": "C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe",
"state":<PHONE_NUMBER>,
"isComplete": true,
"isLaunchable": true,
"isPrerelease": false,
"isRebootRequired": false,
"displayName": "Visual Studio Professional 2022",
"description": "����ᨮ���쭠� ��⥣�஢����� �।� ࠧࠡ�⪨, ��⨬��쭮 ���室��� ��� �������� ������.",
"channelId": "VisualStudio.17.Release",
"channelUri": "https://aka.ms/vs/17/release/channel",
"enginePath": "C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service",
"installedChannelUri": "https://aka.ms/vs/17/release/channel",
"releaseNotes": "https://docs.microsoft.com/en-us/visualstudio/releases/2022/release-notes-v17.2#17.2.0",
"thirdPartyNotices": "https://go.microsoft.com/fwlink/?LinkId=661288",
"updateDate": "2022-05-12T07:51:04.216361Z",
"catalog": {
"buildBranch": "d17.2",
"buildVersion": "17.2.32505.173",
"id": "VisualStudio/17.2.0+32505.173",
"localBuild": "build-lab",
"manifestName": "VisualStudio",
"manifestType": "installer",
"productDisplayVersion": "17.2.0",
"productLine": "Dev17",
"productLineVersion": "2022",
"productMilestone": "RTW",
"productMilestoneIsPreRelease": "False",
"productName": "Visual Studio",
"productPatchVersion": "0",
"productPreReleaseMilestoneSuffix": "7.0",
"productSemanticVersion": "17.2.0+32505.173",
"requiredEngineVersion": "3.2.2146.50370"
},
"properties": {
"campaignId": "",
"channelManifestId": "VisualStudio.17.Release/17.2.0+32505.173",
"nickname": "",
"setupEngineFilePath": "C:\Program Files (x86)\Microsoft Visual Studio\Installer\setup.exe"
}
}
]
.


Document preview hotkey, and show all hotkeys in compose button tooltips.

compose: Add keyboard shortcuts to compose control buttons' tooltips.
For more discoverability, the keyboard shortcuts for preview, and bold, italic and link formatting are now displayed in the tooltips of those compose buttons.
help: Document keyboard shortcut for previewing message being composed.
Fixes: CZO issue report

Screenshots and screen captures:

Self-review checklist

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

Communicate decisions, questions, and potential concerns.

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

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

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

Completed manual review and testing of the following:

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

The screenshots look good to me!

Merged, thanks @N-Shar-ma!


[Request] More ESP to Stream Proof

Hi,
Just wanted to ask if the Spectator List, Bomb Timer and Hitmarker could be migrated to the stream proof overlay as they are all visible in OBS and would imagine them being easy enough to put on the new overlay. Also if its not to much to ask maybe a way to track Backtrack ticks using the Stream Proof overlay (I know the last one is alot to ask compared to the others but the only way to track ticks currently is using chams).
Cheers for all the hard work, Hope this feedback helps.

Take a look how recoilcrosshair or purchase list done then do it urself call it in here its ok https://github.com/danielkrupinski/Osiris/blob/b782d0a8cca9c0ff86c277c75f95bb154496cf15/Osiris/Hooks.cpp#L98


Bring back Compile Cache

The compiler cache was disabled in https://github.com/microsoft/vscode-jupyter/commit/0d3d6aec9bd121579958437c8fb765373fa0beae#diff-e9ee95374b26ca61ff24c3145a68e7ef7dbbe68d374dab4f44087612ee7f2649R183 . Not sure renabling it will lead to any problem, let's see.

[ ] Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
[ ] Title summarizes what is changing.
[ ] Has a news entry file (remember to thank yourself!).
[ ] Appropriate comments and documentation strings in the code.
[ ] Has sufficient logging.
[ ] Has telemetry for feature-requests.
[ ] Unit tests & system/integration tests are added/updated.
[ ] Test plan is updated as appropriate.
[ ] package-lock.json has been regenerated by running npm install (if dependencies have changed).

Codecov Report

Merging #10316 (ac19b91) into main (a5d77fb) will increase coverage by 0%.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           main   #10316   +/-   ##
=====================================
  Coverage    64%      64%
=====================================
  Files       204      204
  Lines      9295     9295
  Branches   1505     1505
=====================================
+ Hits       5957     5962    +5
+ Misses     2867     2865    -2
+ Partials    471      468    -3

Impacted Files
Coverage Δ

src/platform/errors/errorHandler.ts
63% <0%> (+<1%)
:arrow_up:

src/platform/common/cancellation.ts
68% <0%> (+5%)
:arrow_up:


BSD33 can't be flashed, not an ESP

I received some smart sockets which I identified as BSD33 (Tasmota template, AliExpress listing)
I tried to flash it but it stays in
SmartConfig complete.
Resending SmartConfig Packets
.................

loop. I found the following line in the web log:
WARNING: it appears this device does not use an ESP82xx and therefore cannot install ESP based firmware.
As far as I seen it's glued together so I don't want to break it, but if it helps I could set up one with the tuya cloud.
The logs:
mqtt
psk
udp
web
wifi

Hi @netpok, what is your question or issue? It seems you have answered it yourself.

I mean it has a Tasmota template so I think there is 99.9% chance that it's ESP based.
Is there a way to  say "I don't care just flash it", I don't see a way to get it apart without breaking it so I would like to leave that as a last try after I bricked it.

It could be that the manufacturer has changed components. Until now the warning message has always been proven right.

I'm sorry. You're right, I got it apart and it turned out it's based on the WinnerMicro W600 (I missed that there are contenders to esp).
Here are some pictures for anyone interested: https://imgur.com/a/UvVetqD

For future readers,

I mean it has a Tasmota template so I think there is 99.9% chance that it's ESP based.

Unfortunately, as you discovered, manufacturers are switching.

Is there a way to say "I don't care just flash it", I don't see a way to get it apart without breaking it so I would like to leave that as a last try after I bricked it.

tuya-convert isn't blocking you, the device is. tuya-convert is just telling you why it won't work.

I'm sorry. You're right, I got it apart and it turned out it's based on the WinnerMicro W600 (I missed that there are contenders to esp).
Here are some pictures for anyone interested: https://imgur.com/a/UvVetqD

Can you explain how you dismantled it?

You need to pry it open.
Just put a screwdriver in the cutout at the earth and apply some force by using the other side of the socket as a pivot point you should be able to crowbar it out without damaging the socket.

You need to pry it open.
Just put a screwdriver in the cutout at the earth and apply some force by using the other side of the socket as a pivot point you should be able to crowbar it out without damaging the socket.

Thanks, that works perfectly. My device is an ESP8266 version.

Did you try to flash it with tuya-convert?

I will try to flash it with my own firmware via a hardware connected serial connection. I just figured out the pinout of the device. I will post the code on Github when I succeed.

OK just wanted to make sure you did not receive a false positive from tuya-convert.

I also ordered this socket and had problems flashing it with tuya-convert. First i thought, it may also be a WinnerMicro chip inside, but then i did a MAC address search and found it was an Espressif Inc. address. I updated tuya-convert to the latest version, but still no luck. My last option was to open the socket and try to flash it by serial connection. Unfortunately i damaged the relais, so it's useles now.
My question is now, if i can do anything to help to flash this socket with tuya-convert, as there is still the original firmware on the ESP8285 chip.
Is this ESP even supported from tuya-convert?
Thanks to @Wim3d and his tutorial on https://www.instructables.com/id/Hardware-and-Software-Hack-Smart-Devices-Tuya-and-/ how to open this socket!

I'm interested for this update, I want my device with tasmota (local) instead of chinese mens 😄 But same error:
 200 POST /d.json?a=tuya.device.config.get&et=1&other={"token":"00000000","region":"US"}&t=20&uuid=61018072286dcd431d74&v=4.1&sign=67dced75c2326f292aa5867a635af4fb (<IP_ADDRESS>) 65.81ms

POST /d.json?a=tuya.device.config.get&et=1&other={"token":"00000000","region":"US"}&t=21&uuid=61018072286dcd431d74&v=4.1&sign=79d7455d48afa0552205ace6c0c884e9
Host: a2.tuyaus.com
User-Agent: TUYA_IOT_SDK
Connection: keep-alive
Content-Type: application/x-www-form-urlencoded; charset=UTF-8
Content-Length: 37

payload 10DD7D39E3A5710D8E6D87D285214BE9
WARNING: it appears this device does not use an ESP82xx and therefore cannot install ESP based firmware
Answer tuya.device.dynamic.config.get
reply {"result":"fn8oBaEAaJe3I+enO7OkYdd0LkD9WHnY6k8vmvctrJZmwwRPzoJwOu8gFAidZ2yT9F2VBmqNqTqJcWuiX4YubOF2yg37JRyuu6tJU5i7kSS7mevrGF2WUpAllBDW/Q5l","t":1598477559,"sign":"bbb089a694774684"}

@Chuckame you cannot use Tasmota on a non-ESP device.

Sadly you first need to port Tasmota to the Allwinner W600 platform (or any other one that your device uses), last time I checked the W600 only had a binary arduino platform for windows so I let it go.
To be honest that was a year ago at least so maybe it changed, but in my opinion it's cheaper to buy an esp based device (I don't know the market shares these days).

Sadly you first need to port Tasmota to the Allwinner W600 platform (or any other one that your device uses), last time I checked the W600 only had a binary arduino platform for windows so I let it go.

@netpok doable by OTA ? Or you don't know ?

To be honest that was a year ago at least so maybe it changed, but in my opinion it's cheaper to buy an esp based device (I don't know the market shares these days).

@netpok Difficult to find on aliexpress, vendors are not saying "yes, it is an esp device, you can flash it !" 😄 Soooooo the only thing to do is to read all comments and search for someone that have already dissociated the device to know if it is an esp82xx 😢 My smart plugs are generic "Tuya" devices with power monitoring, cost only 7€


Update supportedFolders.js

Changes proposed:

[x] Add

Things I've done:

[x] I've pulled the latest master branch
[x] I've run npm install to install all the dependenies
[x] I've checked my code, it is clean.
[ ] I've run ESLint.
[ ] My pull request fixes an issue, I referenced the issue.
[x] My pull request is not too big, otherwise I've already squashed it.
[ ] I've run npm run build to build the extension. (If I had done something with the extension.)

[short comment]
in polymer-tools "dist" folder name is "build"

please use a better title. "Update supportedFolders.js" is not specific.


Add Terraform samples for deploying Delta Sharing server on AWS

This commit adds Terraform samples for deploying a Delta Sharing server on AWS.

@jyousefpour1 is this still needed?


Mixin incompatibility with server_translations_api library

I swear my pack was working fine yesterday. Could it be a race condition?
[16:33:03] [main/ERROR]: Mixin prepare for mod server_translations_api failed preparing text.MutableTextMixin in server_translations_api.mixin.json: org.spongepowered.asm.mixin.transformer.throwables.MixinTargetAlreadyLoadedException Critical problem: server_translations_api.mixin.json:text.MutableTextMixin from mod server_translations_api target net.minecraft.class_5250 was loaded too early.
org.spongepowered.asm.mixin.transformer.throwables.MixinTargetAlreadyLoadedException: Critical problem: server_translations_api.mixin.json:text.MutableTextMixin from mod server_translations_api target net.minecraft.class_5250 was loaded too early.
[16:33:04] [main/ERROR]: A mod crashed on startup!
net.fabricmc.loader.impl.FormattedException: java.lang.RuntimeException: Could not execute entrypoint stage 'preLaunch' due to errors, provided by 'additionalentityattributes'!

full log:
latest.log

actually this is almost certainly related to Fabric 1.15.1+'s MixinExtra's changes

Yes, definitely seems like it.
Not too much I can do on that end on server_translations_api's behalf, sadly.


Upgrade Grafana to 6.3.2

There is a feature I want in 6.2 (multi series gauges) so it would be
nice if this could be up to date

5 minutes from PR to deploy \o/


Add post

Please note that I'm winding down the Read Rust posting frequency and currently
mainly publishing Rust 2021 posts. For more information see my post:
https://www.wezm.net/v2/posts/2020/slowing-read-rust-posting/
If you'd still like to submit your post please fill in the following:
Please add this post:
Post URL: https://gist.github.com/pickfire/3bcceeacf0bae22dd9f03c5053a976e3
Author Name: Ivan Tham
Categories: pick one: Rust 2021

Thanks! Posted.


fatal error: opening dependency file Builds/.dep/main.o.d: No such file or directory

Everytime I start an AVR project, I get the error below:
Compiling: main.c
/usr/local/CrossPack-AVR/bin/avr-gcc -c -mmcu=atmega32u4 -I. -gstabs -DF_CPU=16000000UL  -Os -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -Wall -Wstrict-prototypes -Wa,-adhlns=Builds/main.lst  -std=gnu99 -gstabs -gstrict-dwarf -MD -MP -MF Builds/.dep/main.o.d "/Users/digimenet/Documents/ATmega328P_Dev/ATmega328P_Dev/main.c" -o Builds/main.o
/Users/digimenet/Documents/ATmega328P_Dev/ATmega328P_Dev/main.c:16:1: fatal error: opening dependency file Builds/.dep/main.o.d: No such file or directory
 }
 ^
compilation terminated.
make: *** [Builds/main.o] Error 1

I installed the CrossPack AVR kit.
Then I installed your provided python script, open up xcode, selected the avr project, then tried to compile the main.c template provided and I get that error.
Please help. I need to know what I screwed up, just can not figure it out.
Also, I don't like switching back and forth between OS X and Windows.
Thanks in advance.

Did you try to build a second time ?


WIP: Release v1.0.0

SDK refactoring and optimisation

[x] Preserve header flags
[x] Rebuild initialisation: make it more convenient and less complex
[x] Make it to be as service: initialise connection and work with service commands — not with requests to provider
[x] Make socket client route multiple incoming responses to right requests
[ ] Make tests coverage up to +80%
[ ] Readme
[ ] Contributing guide
[ ] Circle Ci Tests
[ ] Badges 😍

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@b3a7f2c). Click here to learn what that means.
The diff coverage is 57.87%.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   51.21%
=========================================
  Files             ?       12
  Lines             ?      369
  Branches          ?        0
=========================================
  Hits              ?      189
  Misses            ?      146
  Partials          ?       34

Impacted Files
Coverage Δ

crypt/crypt.go
0% <0%> (ø)

crypt/des.go
78.94% <100%> (ø)

crypt/random.go
100% <100%> (ø)

sdk/client/reader.go
20.93% <20.93%> (ø)

sdk/client/channel.go
49.01% <49.01%> (ø)

sdk/client/signKey.go
50.72% <50.72%> (ø)

sdk/client/header.flags.go
69.23% <69.23%> (ø)

service/service.go
71.42% <71.42%> (ø)

sdk/client/message.pool.go
75% <75%> (ø)

sdk/client/writer.go
81.81% <81.81%> (ø)

... and 2 more

Continue to review full report at Codecov.

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


allow multiline values in UI

For some keys it would be really nice to allow the values to span over more than one narrow line, e.g. note, fixme, description, opening_hours, wikipedia, ...
Right now you have to scroll the line to see the whole value, it would be better to get the whole content at a glance. I wouldn't reduce this to particular keys (like the above mentioned ones) but to all values (and potentially keys) that don't fit into the single line.

Are there further blockers for adding multi line support for the additional tags? The UI is in place for note. There is some interest from users:
https://help.openstreetmap.org/questions/47538/how-to-add-description-tag-with-id

I don't think there are any blockers.  The issue is just old and we forgot about it.


feat: add alerts (Tenderly) datasource

This adds a new alerts datasouce, leveraging the Tenderly API in anticipation of Tenderly Alerts for the forthcoming recovery implementation:

Tenderly-specific configuration for: URL, API key, account and project.
IAlertsApi with addContracts and removeContracts methods.
Test-covered TenderlyApi, which implements IAlertsApi.
AlertsModule, providing the TenderlyApi.

Marking as draft whilst I investigate the broken test.

The code looks good, great job! 🚀
But I think the e2e tests are failing because of the lack of some mandatory configuration (alerts key in configuration.ts). Also, as this configuration is mandatory at the moment, this absence is preventing the service from starting if the variables are not set in the environment.
I'd suggest either stating this alerts configuration is mandatory and including it in configuration.validator.ts, .env.sample, docker-compose.yml, ci.yml, etc., or making this configuration optional and using configurationService.get instead of configurationService.getOrThrow, checking the configuration only when TenderlyApi functions are called.

But I think the e2e tests are failing because of the lack of some mandatory configuration (alerts key in configuration.ts). Also, as this configuration is mandatory at the moment, this absence is preventing the service from starting if the variables are not set in the environment.
I'd suggest either stating this alerts configuration is mandatory and including it in configuration.validator.ts, .env.sample, docker-compose.yml, ci.yml, etc., or making this configuration optional and using configurationService.get instead of configurationService.getOrThrow, checking the configuration only when TenderlyApi functions are called.

Thank you for the review! I will convert this to a draft whilst I implement your suggested fix.


Ember Concurrency refactor

Issue Summary
We currently have two spinner buttons:

gh-spin-button - handles promises
gh-task-button - handles ember-concurrency-tasks

In order to implement https://github.com/TryGhost/Ghost/issues/7515 both spinner button components will need to be updated to handle differing styles and behaviours between promises and tasks. I think this is a good time to standardise on one or the other, ember-concurrency gives us a few benefits over promises, especially as tasks can be linked to buttons and be triggered externally (e.g., via keyboard shortcut or other trigger outside of the button components scope) without jumping through lots of hoops to observe promise state.
TODOs

[x] decouple task button from spin button (https://github.com/TryGhost/Ghost-Admin/issues/496)
[ ] move all existing buttons over to ember-concurrency (minimum needed to drop gh-spin-button)

[x] modals (https://github.com/TryGhost/Ghost-Admin/issues/496)
[ ] settings (quite a few here, can be split up)
[ ] editor
[ ] reset password flow @kevinansfield
[ ] signin
[ ] signup

[ ] improve other internal uses of promises by leveraging ember-concurrency

In most cases creating ember-concurrency tasks so that we can use gh-task-button in place of gh-spin-button is fairly straightforward (see https://github.com/TryGhost/Ghost-Admin/pull/496 for examples), if anyone feels like picking up any of the remaining uses of gh-spin-button please comment here with which instances you are tackling, thanks 😄
I'll update the todo list with a name next to any in-progress items.

Some of these (esp. settings) I'm doing as part of the validations refactor.

@acburdine cool, if there are any specific ones you are working on would you mind updating the issue and putting your name next to them? If would be good if we can have both refactors on-going in parallel so that one is not dependent on the other.

Are you still looking for help on this? First time contributor here. I was looking at the signup.hbs and I saw only two instances of the gh-spin-button component. One on the  authenticateWithGhostOrg action that's in the route and the other is the signup action in the controller.
I suppose the same refactor you did in the signin controller could be done here. I could move the authenticateWithGhostOrg from the signup route back into the controller since I think tasks can't be used in routes. Then update the actions into Ember concurrency tasks. I'm not really sure who's calling the authenticate action in the signup route though, or if that should be moved to the controller.

@kevinansfield What do you think?

@ErikCH I'd say if you're still up for it then the help would be appreciated 😄

@acburdine Good meeting you at Emberconf! I'll work on signup. I'll move the authenticateWithGhostOrg method into the controller, update the ember concurrency tasks and see what you guys think.

Looks like you guys already have a handle on setup and signin. Maybe, I'll try to catch the next one.

Hey @ericschultz 👋 Sorry about that, your messages must have got lost in my GitHub notification noise 😞 This issue was part of our 1.0-beta push so had deadlines attached to it.
Keep an eye on GitHub, we're always happy for contributions if anything takes your fancy! If you don't get a response on here straight away pop into the #core-dev channel on our Slack team 😄


text method in Mojo::Dom works now also on nodes of type text, raw and cdata

Summary
Allows to process the text of nodes directly.
Motivation
In traversing a parsed tree the text nodes also need processing as text.
References
#1022

The code can likely be golfed a little, but assuming this is the direction we want to go (allow text to act on nodes as well as elements) then 👍

I'll have to give this a 👎 i'm afraid, because of the inconsistency between text and all_text, as well as the size of the code.

All the tests are still OK with this:
 sub text {
   my $tree = shift->tree;
-  my $type = $tree->[0];
-  if ($type eq 'text' || $type eq 'cdata' || $type eq 'raw') {
-    return $tree->[1];
-  }
-  _text([_nodes($tree)], 0);
+  _text([$tree, _nodes($tree)], 0);
 }

I guess the same change could be applied to all_text(), but with unit tests added.

Afraid it looks like this pull request did not pass the vote.


Added @internal flag to ignore private methods into TypeDocs/ Added method comments.

What kind of change does this PR introduce?
Added comments to methods and added @internal to ignore private methods in documentation.
What is the current behavior?
Run command yarn docs. This command will create v2 version document.
The document includes internal/private methods - thus making it hard to read.
What is the new behavior?
Run yarn docs. This should hide internal/private methods and show comments to method.
Additional context
Add any other context or screenshots.

@meera thank you so much!


feat: add proper transaction data logging

fixes #1106

Currently this requires: https://github.com/stellar/soroban-rpc/pull/90

To be able to print, as well as save to a local file

While the intent of #1106 was, like Leigh said, to reduce developer effort in profiling their transactions and sharing the aggregate data, I wonder whether having a full cache of tx is actually a net benefit? It can allow a developer to review their historical tx as they fine tune the code for limits and fees.
To be clear, I still only need the aggregate data and not the full tx; but now that the cacheing code is written, perhaps we can give it shape to make a useful feature out of it.
@janewang thoughts? Just an idea

now that the cacheing code is written, perhaps we can give it shape to make a useful feature out of it.

It could be pretty nice to offer a soroban history that shows a history of past operations performed and outputs for some operations. I'm not sure of the urgency of this though. Maybe something to add later based on the cache.

reduce developer effort in profiling their transactions and sharing the aggregate data

This PR alone won't address this issue. We'd need a command to convert this cached data into a more succinct form containing just resource information.

now that the cacheing code is written, perhaps we can give it shape to make a useful feature out of it.

It could be pretty nice to offer a soroban history that shows a history of past operations performed and outputs for some operations. I'm not sure of the urgency of this though. Maybe something to add later based on the cache.

100%, let's see what Jane thinks.

This PR alone won't address this issue. We'd need a command to convert this cached data into a more succinct form containing just resource information.

Depending on Jane's response I can whip up some user stories that address the intent of #1106.

Couple minor things I commented inline that can be fixed up when merging.
A bigger issue is that the commands don't tell a clear story.
The cache stores contract specs, but the cache ls and cache read commands don't display contract specs that have been cached.
The cache stores responses to requests to rpc, and they're visible in the cache ls and cache read commands, but they aren't used as a cache, they're used as a log, and the cache ls and cache read commands are accessing that log.
In terms of what should be in the "cache", if we're true to what a cache is and is used for, it should just be the contract specs, and the request/response log should be a separate thing.
I'm inclined to merge just the contract spec caching parts of this PR, simplify the commands to only the clean command. Then we aren't merging commands that we don't really have a goal for that would then be a breaking change later to remove or fixup. We can always circle back to reviving this logic out of the PR at a later date if needed.
@janewang Does that work for you?

Thanks for flagging. I'm filling in for @janewang here.
Could we simply add a new command "log"?
"Cache" can operate on contract specs
"Log" can operate on the log of RPC calls

The term log on its own is overloaded. But yes we can move the actions log / request log items into their own command relatively simply.

Actually a better story is making both subcommands of "cache", which opens space for future development as well.
cache specs
cache simulation
cache tx-log (or something)

I like it. Id change it to:
cache clean // cleans everything
cache info // as it is now dir for everything
cache commandlog ls
cache commandlog read
Basically move the commands that only work for txs into their own. We don't need any fns for spec at the moment. And clean can work for all.
I'm torn on the commandlog vs say requestlog.

Sounds great!
Yeah commandlog is off, I'd make it something that describes the item being worked on more precisely, like preflight, simulation, tx profile, tx


Raw expressions work with insert but not insertWithRelated

I'm trying to use a raw expression for an insert, ie:
Person
  .query()
  .insert({
    age: Person.query().avg('age'),
    firstName: Person.raw("'Jenni' || 'fer'")
  });

However, this does not work if using insertWithRelated instead of insert. Using debug() it seems like the property is simply not picked up (ignored).

This seems like a clear bug. I'll fix this for the 0.5.0 release. I'll probably make an alpha/rc release soon that contains a fix for this. I'll keep you posted.

Fixed in 0.5.0-rc.1. Run npm install objection@next to install.


V2.0 development

Implementing Version 2 of the program.
Added a basic terminal UI and simple validation rules for deposits and withdrawals.

Good job.


imports broken as soon as bad import tried

$ elm-repl
Elm REPL 0.4.1 (Elm Platform 0.15)
See usage examples at https://github.com/elm-lang/elm-repl
Type :help for help, :exit to exit

import Arra
Error when searching for modules imported by module 'Repl':
Could not find module 'Arra'

Potential problems could be:

Misspelled the module name
Need to add a source directory or new dependency to elm-package.json

import Array
Error when searching for modules imported by module 'Repl':
Could not find module 'Arra'

Potential problems could be:

Misspelled the module name
Need to add a source directory or new dependency to elm-package.json

Is this still a problem on the master branch? I believe a similar issue was closed recently. Can you find that issue?


Extend unit tests

Problem
The demonstration of features are in the example folder of AREG SDK. But still there are many objects and many methods that are never tested. In order to test, there is a need to increase amount of unit tests.
Actions
The unit tests are integrated and should be implemented in the tests/units. Each .cpp file should contain one test name. The tests are added in the CMakeFiles.txt by calling addTest() method, which automatically includes the tests in the compilation. The testing module is the AREG engine / framework.
Note
This ticket cannot be assigned to one person since the topic of unit tests is huge.
Please inform for which object / topic you want to create unit test and I'll create a separate ticket and branch, and assign to you.

@aregtech I am interested in working on this issue. Could you assign it to me?

@harshit496, thank you very much.
Since this topic is very huge, i suggest to select 1-3 classes that you'd like to test, so that I'll create a separate issue and you can work on that.

How about if I write tests for the all the classes in appbase dir?

@harshit496 ,
I would suggest classes in base. Classes like string or containers, DateTime, etc.
In appbase the main class is Application, which most probably should be mocked to be able to test. And the Console class I'll soon move out of areg framework.

Sounds good. I can take the three classes you mentioned then

Containers
DateTime
Strings

OK. Let's start with strings. They are big enough :)


cache issues

Unknown behaviors and bugs of new cache feature

cache work flows before sending to MPI ranks
Size of saved cache growing unbounded
cache requiring recompilation for altered meshes, census time, and census bank buffer

After running in Numba mode and getting the compilation cached, we sometimes want to run in pure Python mode again (e.g., to do Python profiling, to compare Python and Numba error messages, etc). Currently, it seems that cached compilation will be used even if we run in Python mode. Is it possible to bypass or ignore the cached compilation in pure Python mode? @jpmorgan98

This is very odd behavior. Like even if it's in Python mode it will run as if in Numba? My only thought is to delete the cache folder all together. It should be in /__pycache__ in your execution directory

It is found that, since we only put the cache decorator in the loop.py, if we make changes in kernel.py, the cache will not recompile.


no coord ref

Hello, I downloaded your files and they have no geographical reference, which one should I assign them?
name file: thetao_Omon_FGOALS-f3-H_hist-1950_r1i1p1f1_gn_195001-195001.nc
link file: https://esgf-data1.llnl.gov/thredds/dodsC/css03_data/CMIP6/HighResMIP/CAS/FGOALS-f3-H/hist-1950/r1i1p1f1/Omon/thetao/gn/v20200917/thetao_Omon_FGOALS-f3-H_hist-1950_r1i1p1f1_gn_195001-195001.nc

Hi, looks like this is an issue specific to OpenDAP, so I'm sorry to inform you it is out of scope for our repository issues.  You may want to look into help or discussion forums for netCDF data.


hOCR renderer can generate zero-length words

Bug report
Thanks for finding the bug! To help us fix it, please make sure that you
include the following information:

A description of the bug
Steps to reproduce the bug. Try to minimize the number of steps needed.
Include the command and/or script that you use. Also include the PDF that
you use.
If relevant, include the output and/or error stacktrace.

The definition of write_word() in converter.py strips the text after it determines it should generate a word, but before it generates the word. Especially in combination with the fix proposed in issue #836, this can result in the generation of zero-length hOCR word spans.

Here's a modification of the fix proposed in #836 which addresses this issue:
    def write_word(self) -> None:
        if len(self.working_text) > 0:
            txt = self._clean_text(self.working_text.strip())
            if len(txt) > 0:
                bold_and_italic_styles = ""
                if "Italic" in self.working_font:
                    bold_and_italic_styles = "font-style: italic; "
                if "Bold" in self.working_font:
                    bold_and_italic_styles += "font-weight: bold; "
                self.write(
                    "%s"
                    % (
                        (
                            self.working_font,
                            self.working_size,
                            bold_and_italic_styles,
                            self.bbox_repr(self.working_bbox),
                            self.working_font,
                            self.working_size,
                            txt
                        )
                    )
                )
        self.within_chars = False

And yes, I know I should be creating a pull request for all these bugs, but I just don't have time right now.


compiler: put in order all of type checkers

Right now, there are many functions with multiple signatures:
func isByteArrayType(t types.Type) bool
func isByteArray(lit *ast.CompositeLit, tInfo *types.Info) bool
...
They also use different ways of type checking. (cast to string or via chain of Underlying() methods).
It is more convenient to have some unified way of looking into things. E.g. via go/types package.

Closed via #959.


Update image ghcr.io/zoriya/kyoo_migrations to df74c60

This PR contains the following updates:

Package
Update
Change

ghcr.io/zoriya/kyoo_migrations
digest
ed7e45b -> df74c60

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


Add "Your Profile" link to user dropdown

Currently, the only way I found to go to your public
profile is to click the "public profile" links at
https://pypi.org/manage/account/

Hi @berkerpeksag thanks for this PR :)
What is the benefit of linking prominently to this page from here?  All of the information on this page is available via the management UI (with more detail).  Is there something missing from the management UI that you get on this page?
I also think we need to test this with some users before merging it - my concern is that the user might confuse the 'profile' link with the 'account settings' link.

The management UI is only for me so I can't share it on my Patreon page or add it to my CV. Also, adding a link to a user's public profile is a common feature on many websites:
python.org (see "View your public profile"):

GitHub (see "Your Profile"):

Twitter (see "Profile"):

Last.fm (see "View profile"):

Superseded by #3255. I accidentally deleted the fork in my profile instead of an organization so I couldn't edit this PR via GitHub.


[wip] Docker compose

this is a work in progress, display of static files currently broken -> i'm fixing :)
The aim of this pull request is to get early feedback on approach!
To do:

make it actually with static assets
elasticbeanstalk setup and docs
README overhaul

How to test this locally in its current state:

get docker :) -> it's in the self service
eval "$(docker-machine env dev)"
docker-compose build
docker-compose run -d
docker-compose run web python manage.py migrate --noinput
docker-compose run web python manage.py collectstatic --noinput --ignore admin
docker-compose run web python manage.py compilestatic

continued work on another branch....


Consider respecting cfg!(fuzzing)

The cfg!(fuzzing) flag is designed as a way to disable checksums validation and similar checks when Rust code is run under fuzzing. This would be helpful to enable differential fuzzing between the many existing Rust zlib implementations.

I don't really follow why calculating checksums would be a problem for fuzzing? the checksum is entirely deterministic, and other implementations should generate the same checksum for the same input bytes. Can you elaborate on what exactly we should do differently when cfg!(fuzzing) is enabled?

This would be for the inflate codepath. There the fuzzer would be generating random sequences of bytes and feeding them to the library as zlib bitstreams. Most (at least initially) would be corrupt for one reason or another, but over time the fuzzer would start to find bitstreams that we valid other than the checksum. Rather than forcing the fuzzer to also look for valid checksums, you can instead have the decompressor return success even when the checksum doesn't match.
This is where miniz_oxide ignores the checksum and here is a fuzz test that found multiple bugs in fdeflate and miniz_oxide by comparing their behavior to each other.

that's interesting. I think a lot of code paths are already covered by the raw (so, no header, no footer) deflate stream but control flow does branch on the raw/zlib/gzip mode.
So, I just naively tried this, and it doesn't seem to do anything?
> cargo +nightly fuzz run inflate_random_bytes

warning: unexpected `cfg` condition name: `fuzzing`
   --> /home/folkertdev/rust/zlib-rs/zlib-rs/src/inflate.rs:901:22
    |
901 |             if !cfg!(fuzzing) {
    |                      ^^^^^^^

so, there must be more to it than that? But the docs suggest to me that the above should just work.

That is unfortunately expected on recent nightlies. The compiler now "helpfully" prints that even though the fuzzer enables the cfg!(fuzzing) flag

It turns out this is not as easy as it seems.
We currently test against zlib-ng in compat mode (so it has the api of the original zlib). We aim to be a drop-in replacement for zlib, so matching its behavior is important.
In our uncompress_random_input fuzzer, we compare our output with that of zlib-ng. The api here does not give any error information beyond the return code integer. Specifically, we cannot know whether a DataError means that the checksum was incorrect, or that something else failed.
So if under fuzzing we allow incorrect checksums, that fuzzer will now no longer detect the case where zlib-ng returns a DataError for some other reason, and we just accept the input.
Is fuzzing against zlib-rs something you're interested in for fdeflate? if that is the actual usecase we could add some __unsafe_skip_checksum_check flag which your fuzzer could use.

That is tricky to deal with. I don't specifically need this for testing fdeflate, so feel free to close
I would recommend designing an interface that exposes the precise error cause. Probably isn't that helpful for end users, but it can make fuzzing differences easier to root cause.

fixed in https://github.com/trifectatechfoundation/zlib-rs/pull/231


failure to install webinstaller on Ubuntu 14.04, 346.59 opensource nvidia driver for GTX 680

Hi,
I'm a newbie to Linux and have been trying for a long time to get the webinstaller up. I followed the installation instructions, but the program did not detect any gpu on my machine. And then, as i was following the training example and got to the training part, there was this error: "ERROR: Check failed: error == cudaSuccess (30 vs. 0) unknown error".
Can anyone help regarding this? Thanks!
Best Regards,
Justin

So you're using an opensource driver? But you were able to build caffe with CUDA support? That's weird, do you even have CUDA installed? I recommend using the Nvidia drivers.
Also, in the future you should post this type of issue on our google group: https://groups.google.com/d/forum/digits-users

The caffe that is bundled in the web installer is set up to use GPUs.  I would suggest finding out why the GPU is not detected.  Fallback would be to build caffe with CPU_ONLY on and drop that in to the web installer directory.

Thanks Luke and Moconnor! the culprit is the opensource driver from xorg-edgers. I installed the proprietary drivers and things are ok now. (the driver installation process is horrible though)

@moconnor725 Could you tell me how to build caffe with CPU_ONLY in web installer? I don't find the caffe file using web installer.thanks

hi i am sorry but i am no longer working on this this and have lost familiarity. however i remembered that i had problems due to GPU, and not CPU.
Sent by Outlook for Android
On Sun, Jan 3, 2016 at 7:11 PM -0800, "fanser"<EMAIL_ADDRESS>wrote:
@moconnor725 Could you tell me how to build caffe with CPU_ONLY in web installer? I don't find the caffe file using web installer.thanks

Reply to this email directly or view it on GitHub:
https://github.com/NVIDIA/DIGITS/issues/89#issuecomment-168570614

@justinvictor Thank for your answer. My computer graphic card don't support CUDA, so i try the CUP-ONLY model and didn't install it. Now i don't know how to solve it. Hope someone come help me.
thanks again!


Export default of type emits invalid code

Bug Report
🔎 Search Terms
Export default type
Export default type reference error
🕗 Version & Regression Information
This has always been the behavior
⏯ Playground Link
Playground link
💻 Code
import type {SyntaxKind} from "typescript"

export default SyntaxKind

Emits ESM

export default SyntaxKind

Emits CommonJs
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = SyntaxKind;

which causes a reference error.
🙁 Actual behavior
Emitted code errors at runtime with reference error
🙂 Expected behavior
If I am default exporting a type I'd like that to be dropped from the emitted code as to not error.
Since this is old behavior I'm guessing this might have something to do with globals that I do not understand? Any clarification on the issue is also super appreciated.

Notably this errors

import type doesn't mean what you think it does: https://github.com/microsoft/TypeScript/issues/54990#issuecomment-1634508462
If there's a bug here, it's that the export default isn't being flagged as an error at compile time.

Thanks for the import type issue! I also agree that it should fail at compile time!
I assumed it wasn't emitted at all - not sure if this is useful to the decision making process but essentially what "bit me" from this behavior was.
Old codebase didn't properly annotate type imports and exports (as well importEqualsDeclaration use).
(Sorry if annotate is the wrong word I should mean isTypeOnly=true on the import/export specifiers)
I wrote a script to fix these cases.
A file that used to be a module now only exported types so webpack dropped it - (at least this is my understanding).
Code that used to say something like
const webpack_default_export = (some_webpack_module.thingThatisType)
became:
const webpack_default_export = (thingThatisType)
which is a reference error at runtime.
I think this is the only weird edge case I missed - but I thought it was worth the bug report - thanks for the fast response and info again - really appreciate it!

Doubt this is wanted/will be accepted but here is the entirety of the change necessary to make this a compile time error
(I went through the tests and ran my own test cases locally this seems to work as intended)
else if (!node.isExportEquals && (getTypeOnlyAliasDeclaration(sym, undefined) || ((getAllSymbolFlags(sym) & SymbolFlags.Value) === 0))) {
          error(id, Diagnostics._0_only_refers_to_a_type_but_is_being_used_as_a_value_here, idText(id));
}

This would be added to checkExportAssignment at the time of writing on line 44685. This causes 22 tests failures as this is a behavior change. Would you be open to a compiler flag - or perhaps adding this as an error to verbatim module syntax? Although I would personally prefer something like this as either a separate flag (verbatimModuleSyntax seems to have a lot of baggage) or as default behavior.
Sorry if this is too intrusive!


libvirt 2.0 xml metadata

Author Name: Denis LDV (Denis LDV)
Original Redmine Issue: 5201, https://dev.opennebula.org/issues/5201
Original Date: 2017-06-23

Not sure it is important or not
I upgraded node and now metadata section in xml is empty
Centos 7
before upgrade:
virsh dumpxml one-XXX
...
<metadata>
    <system_datastore><![CDATA[/var/lib/one//datastores/XXX/XXX]]></system_datastore>
</metadata>
...

1. virsh version
Compiled against library: libvirt 1.2.17
Using library: libvirt 1.2.17
Using API: QEMU 1.2.17
Running hypervisor: QEMU 1.5.3

after upgrade:

1. virsh dumpxml one-XXX
...
<metadata/>
...

1. virsh version
Compiled against library: libvirt 2.0.0
Using library: libvirt 2.0.0
Using API: QEMU 2.0.0
Running hypervisor: QEMU 2.6.0

Original Redmine Comment
Author Name: Javi Fontan (Javi Fontan)
Original Date: 2017-08-23T16:54:26Z

A prefix must be added to all the tags in metadata.

Original Redmine Comment
Author Name: Stefan Kooman (Stefan Kooman)
Original Date: 2017-10-26T07:47:38Z

As discussed with Javi Fontan and Anton Todorov during the ONE EU CONF 2017: There is a clear need for metadata support in libvirt XML's created by OpenNebula. Especially the "NAME" of the virtual machine should be present in the libvirt XML. External tools (for example to do Disaster Recovery) can than make a mapping between ONE-ID and Name. Libvirt allows for Metadata to be added: https://libvirt.org/formatdomain.html#elementsMetadata
A mapping prooposal:
OpenNebula VM "NAME" => libvirt Title
OpenNebula VM Description => libvirt Description
OpenNebula VM Metadata => libvirt Metadata

We are in the process of migrating to telegraf (libvirt plugin based on PR 3592) for collecting VM metrics and sending them to influxdb instead of ONE. Having a "human readable" aka "VM NAME" send with those metrics would be really valuable.

Duplicated #2205


Generic.text("Hello World")    File "/usr/local/lib/python2.7/dist-packages/escpos/escpos.py", line 264, in text      self._raw(text)

Dear community;

I use Rasbian, I got the phoenix printer
(http://pyramidacceptors.com/phoenix-printer/) from PTI. I use Rasbian as OS. I
attach a dump of the details of printer. I used following python code:

from escpos import *
Epson = printer.Usb(0x2504,0x0300)
Epson.text("Hello World")
Epson.cut()

Running this code as root results:

  File "gpio.py", line 5, in <module>
    Epson.text("Hello World")
  File "/usr/local/lib/python2.7/dist-packages/escpos/escpos.py", line 264, in text
    self._raw(text)
  File "/usr/local/lib/python2.7/dist-packages/escpos/printer.py", line 58, in _raw
    self.device.write(self.out_ep, msg, self.interface)
  File "/usr/local/lib/python2.7/dist-packages/usb/core.py", line 625, in write
    fn = fn_map[self._ctx.get_endpoint_type(self, endpoint, intf)]
  File "/usr/local/lib/python2.7/dist-packages/usb/core.py", line 180, in get_endpoint_type
    etype = util.endpoint_type(e.bmAttributes)
AttributeError: 'NoneType' object has no attribute 'bmAttributes'

All the best;

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 18 Jul 2014 at 2:52

I suspect this is a problem with the underlying USB-library. Does anyone still have this problem?
I do not have the means to try reproducing it and if we can't find anyone with this problem I would suggest closing this issue.


Define alma specs

It would be helpful for the alma project to meet with members of the EUS team listing @mzelesky , @pmgreen , @pdiskin  and write specs (scenarios-tests); this would assist with the project development. @kelynch

This is an update from our first meeting on brainstorming and adding some scenarios. https://github.com/pulibrary/marc_liberation/pull/717/commits/5341879253fb1486308f8957575cc48c236dfc5b

This has happened. We will open a new issue when we want to define new specs.


[Feature-Request] Rolling release?

Start with the why:
I am running ROS2 rolling. I need moveit_py, which is not on Humble. So therefore I need rolling, as I want to use U22. U23 is not desired as it isn't LTS.
Move to the what:
A release on rolling
Move to the how:
Release on rolling 😉

Hi @MatthijsBurgh , at this moment we only support latest stable releases (Humble, Iron, Noetic). We could create a separate branch for rolling, but for now it would have to be community-supported.

I don't see a reason to not release the current main branch, which you release to Iron, to release it to rolling. As that is kind of the idea of the rolling distro.

We could create a separate branch for rolling, but for now it would have to be community-supported.

@Serafadam , I would think there'd be a financial incentive to officially support rolling as well, given how it'd help users up to date with the latest supported LTS. The ROS 2 Jazzy release is open for public testing, yet I could not find this package available through the public build farm. It's rather painful when folks are held back from critical security platform upgrades and ROS bug fixes because a component of the stack has not been maintained for the latest LTS. If rolling was actively maintained, then binary package releases for latest LTS releases would be an automated by product, unblocking many of end users and business partners.

at this moment we only support latest stable releases (Humble, Iron, Noetic)

Speaking of LTS releases, hows support for Jazzy coming along? I got this repo to compile locally, but not after patching a large number of  (deprecated?) OpenCV header paths, and fixing undeclared Cmake depacies for ament_index_cpp. Any ETA for Jazzy given it's release is almost upon us? I could open some drive by PRs, but this repo has no CONTRIBUTING file as a guide. Thanks!

@ruffsl Do you have your changes documented anywhere? I'm currently trying to get it to build on rolling, and it'd be incredibly helpful to see how you did it.

@G-Levine , I didn't notice at first that there was an Iron branch here at first, given the number of branches here and the default branch still being pinned to Humble. So the changes for building are even fewer:

https://github.com/luxonis/depthai-ros/pull/533

Haven't tested my Jazzy build of this just yet, as I'm still just getting my CI rolled over to Ubuntu Noble.


Release v27.3.0

Includes:

Allow custom logo link in navigation header (PR #2320)

I think some things may have been merged since this was created so a rebase might be in order.


reLayout if content changed dynamically

Sorry, I couldn't provide a link to CodePen, because it does not have sense.
I have only one question: How can I recalculate height after content changed inside slide-up-down component?

Lol, fixed)
Just added window.dispatchEvent(new Event("resize")); in the end of my @click function


HTTPS produces SSL write errors (linux), SSL read errors (OS X)

Hi,
I have setup a Kitura/HTTPS server. Both under Linux and OS X. When serving a file through the StaticFileServer() middleware, if it is not too small, the transfer is usually truncated and errors are logged to the screen.
The errors differ between Linux and OS X. With Linux it is all WRITE errors and with OS X, it is all READ errors:
OS X (SSL read errors)
[2017-03-18T12:28:55.723+01:00] [ERROR] [IncomingSocketHandler.swift:148 handleRead()] Read from socket (file descriptor 8) failed. Error = Error code: -9806(0x-264E), ERROR: SSLRead, code: -9806, reason: errSSLClosedAbort.
[2017-03-18T12:28:55.855+01:00] [ERROR] [IncomingSocketHandler.swift:148 handleRead()] Read from socket (file descriptor 7) failed. Error = Error code: -36(0x-24), ERROR: SSLRead, code: -36, reason: errSecIO.

Linux (SSL write errors)
[2017-03-18T11:32:15.896Z] [ERROR] [IncomingSocketHandler.swift:265 handleWriteHelper()] Write to socket (file descriptor 7) failed. Error = Error code: 336195711(0x1409F07F), ERROR: SSL_write, code: 336195711, reason: bad write retry.

I have assemble a minimum project that demonstrate the problem. It is available at:
https://github.com/jnigro/kitura-ssl_bug
The project works both with Linux and Mac. Certificates are already created (password = "password"). In the Certs directory there is also the script I used to automate the certificate creation.
The project contains a large image that can be used to easily reproduce the problem:
https://localhost:8090/large.jpg
Versions used:

software
Version

Kitura
1.6.2

Swift
3.0.2

OS X
OS X 10.11 and OS X 10.12

Linux
docker ibmcom/kitura-ubuntu (14.04.5)

For futher details, please check the repository's README.md
Thanks!

@jnigro  I am able to reproduce the problem on os x, and have submitted a PR (IBM-Swift/BlueSSLService/pull/20) to a dependent repo to fix the issue.
The SSLRead, code: -9806 errors probably will not go away on os x without some external work, but can be safely ignored as long as the functionality works after this fix.
However, I am not able to reproduce the problem on linux. Can you confirm that the download fails  on linux as well for you?

Hi na-gupta,
Yes, I can confirm the download fails on Linux. I was using docker, but now I also tried on a full Ubuntu 14.04 installation. Problem is still there.
Are you using 14.04? I think I read in some other thread, that you were using 16.x? Could that be the difference. If I have time today, I will try to test it on Ubuntu 16.x and report back.
On the other side, I tried your fix on Mac. As you said, the transfer now completes successfully, although the errors are still logged.
Thanks!

Adding to my previous reply: I had a little time to test it also on Ubuntu 16.04.02 LTS. Still the same write errors (code 336195711).

I am using Ubuntu 14.04 too. Could you please try deleting your Packages and build folders, rebuild the project and try again. Also, if you still get the error, could you please paste the output of wget https://localhost:8090/large.jpg --no-check-certificate here. Thanks

Hello again. I think I have good information on how you can reproduce the problem now. I went ahead and did what you asked, even though I already cleaned my build and Packages directory in the past with no joy. However, I was surprised when this time the errors did not appear.
That made me look harder on what I was doing differently now. In the past I was connecting from Chrome in a remote Mac computer. So, to isolate the problem, I went back to my Mac and tried to transfer the file using wget. The errors did appear again. It took it 8 tries for wget to get the file. The first 7 tries aborted with 5%, 39%, 7%, 43%, 70%, 97%, 7% and finally 100%. There is one error logged to the server's output for each try.
With this information, the problem is either being triggered by serving to the remote interface (instead of the loopback interface), or because of something the OS X client side does differently. Either way, I think you will be able to reproduce it now.
I am attaching 3 files:

File
Description

build.txt
A full log of the entire process. From cloning the sample project, to running the server.

ok-wget-linux-localhost.txt
The wget output when getting the file from the same Linux host

error-wget-macosx.txt
The wget output when getting the file from a remote OS X computer. It also includes the errors logged when wget failed 7 times.

I hope this helps. Cheers
ok-wget-linux-localhost.txt
build.txt
error-wget-macosx.txt

I was able to reproduce the problem and submitted another pull request (https://github.com/IBM-Swift/BlueSSLService/pull/21) to BlueSSLService, this time with a fix for openssl on linux. Hopefully this resolves the issue once it's merged and tagged. Thanks!

@jnigro This has been fixed in SSLService-0.12.29. Please verify it works ok now on both linux and mac. Thanks!

Thank you na-gupta. That was fast! I already checked and works both on Linux and Mac. OS X continues to  complain of errors, but the transfer is indeed successful.
Thank you!

Thank you to everyone who raised and fixed this! I too was getting a bad write retry error - deleting all packages to force an upgrade to the latest SSLService worked like a charm.


Adding customization options like Paragraph,Font-Family,Font-sizes,un…

#1712

Description

You take a task to changes on portal in new opportunity. I have added following feature
Paragraph
Font-Family
Font-Sizes
Underline
Insert/edit images

Checklist:

[ ] I have performed a self-review of my own code.

closing this PR because a lot of changes. open the new PR with exact changes #1738


Line breaks between every word

Great theme! Not working for me on mac Obisidian v0.14.15 though if you check out the screenshot. I don't have any line breaks there so it should all just be one line 🤔

Hello Sean,
thank you for your email. Apologies for the late reply, I have been busy
with exams. x(
I have addressed this issue in the latest release. Please update the theme
from Obsidian.
Thanks for reaching out and for your valuable feedback.
Regards,
Jaysan
On Wed, Jun 8, 2022 at 5:19 PM Sean W @.***> wrote:

Great theme! Not working for me on mac Obisidian v0.14.15 though if you
check out the screenshot. I don't have any line breaks there so it should
all just be one line 🤔
[image: Screen Shot 2022-06-08 at 7 17 58 AM]
https://user-images.githubusercontent.com/3342937/172639777-eb8aec51-fc54-4cb5-9cf7-b933a1e7d9e8.png
—
Reply to this email directly, view it on GitHub
https://github.com/jaysan0/obsidian-sandstorm/issues/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AW7LFPC6H6Z2UGDBUIX3E6DVOCTXJANCNFSM5YGXA7QA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have addressed this issue in the latest release. Please update the theme from Obsidian. Thanks for the feedback.


Caching

Is it possible to add a flag, that the index.html (the default file) is not cached? My index.html contains only very little code and mainly references to a javascript and a css files. Those files are revved with filerev, so the index.html would be the only file, which does not need to be cached.

Just to be clear you want the ability to exclude the index.html from the war archive?

No, I want the index.html to have a HTTP header cache-control: no-cache, must-revalidate.

The container (Tomcat for example) that you are deploying the WAR should have features that allow you to set the cache-control and other headers for the resources being served in much the same way that .htaccess provides this functionality for Apache.  A WAR is really just a zip file of all your resources and is not technically running any code (unless you package some Java servlet code along side your browser web app in the same WAR).  Prior to HTML5 some success could be achieved by including meta tags inside individual files (index.html for example) like  and this may still work in HTML5 browsers but it is technically not supposed to be allowed in HTML5.  Now with HTML5 you have the tag  which gives you some control but likely not what you are looking to achieve.

Thank you for this information! I found a Tomcat filter which handles this usecase.


ARROW-16809: [C++] Add Benchmarks for FilterNode

13366

 Quality gate: Passed
12 Issues

 12 Code issues

Details

 Quality gate: Passed
12 Issues

 12 Code issues

Details


fix: handle nested variant groups in vscode/playground and fix sourcemaps

Fixes #2888
Fixes #2889
This fixes #2889 and protects against future issues by getting the positions for vscode/playground annotations/tooltips using the same logic that does the actual transformations. In doing so it also provides an interface for all plugins to provide their own annotations (e.g. in this case, transformer-variant-group no longer needs special logic for annotations outside its own package).
#2888 is fixed by making more granular replacements on MagicString (using the same position data calculated for the annotations).

Sure, done


Small/large file chooser

Right now, it looks like there aren't small or large file choosers. That's problematic, when you want to use the file chooser in a form, where all other fields are small. In the end, it looks rather ugly.
Or is there something, that I've missed or overlooked?
I already opened this ticket, but they say, that it's a bootstrap issue: https://github.com/bootstrap-vue/bootstrap-vue/issues/3285

not sure if I understand the issue correctly, but did you try to add the classes btn-sm or btn-lg to the <input type="file" /> ?

At least not directly. bootstrap-vue usually adds the correct classes to the DOM element(s), if you set the size property of its corresponding control (in this case b-form-file). But it seems like small or large file choosers simply don't exist at all right now. Therefore, bootstrap-vue can't set anything, because that functionality simply isn't implemented into bootstrap yet.


Fix wrong error messages for invalid arguments when calling functions through call

This way, the sample code:
extends Node2D

func _ready():
	call("test", [0, 1, 2])

func test(wrong_type : int):
	print(wrong_type)

Produces: "... Cannot convert argument 2 from Array to int".
Changing the line to argptrs++ would change the error to "... Cannot convert argument 1 from Array to int". I'm not completely sure which one is better.
Fixes #25505

Thanks!


User not allowed to login without email confirmation

Hi, I have the following settings:
USER_ENABLE_USERNAME = False
USER_ENABLE_EMAIL = True
USER_ENABLE_CONFIRM_EMAIL = False
USER_ENABLE_LOGIN_WITHOUT_CONFIRM = True
However, I keep getting "Your email address has not yet been confirmed." and the user cannot login.
By the way, I am using the User/UserAuth DataModel

In the interim I added a default to the confirmed_at field in the User model so that it is confirmed automatically upon registration
confirmed_at = db.Column(db.DateTime(), default=utcnow())

The documentation is wrong. The configuration parameter is actually called USER_ENABLE_LOGIN_WITHOUT_CONFIRM_EMAIL. See https://github.com/lingthio/Flask-User/blob/d4c6f4e3be47c9b39842874bd86416f16be250db/flask_user/settings.py#L29

The documentation has been fixed a while ago.


[BUG] Set-PnPTenantSite -NoScriptSite alias for -DenyAddAndCustomizePages not valid

Expected behavior
Running the following should work
Set-PnPTenantSite -Url $siteUrl -NoScriptSite:$false
Actual behavior
An error is returned
Set-PnPTenantSite : Parameter set cannot be resolved using the specified named parameters.
What is the version of the Cmdlet module you are running?
1.2.4-nightly
Which operating system/environment are you running PnP PowerShell on?

[ x ] Windows

If this is intended, the example needs updating.

The NoScriptSite parameter is not present on Set-PnPTenantSite, which explains the error you are getting. You have to use the Set-PnPSite cmdlet instead. The difference is that Set-PnPTenantSite the PnP version of Set-SPOSite and thus matches the parameters of Set-SPOSite. The Set-PnPTenantSite also works on tenant admin level where is Set-PnPSite works directly towards the site itself.

The NoScriptSite parameter is not present on Set-PnPTenantSite, which explains the error you are getting. You have to use the Set-PnPSite cmdlet instead. The difference is that Set-PnPTenantSite the PnP version of Set-SPOSite and thus matches the parameters of Set-SPOSite. The Set-PnPTenantSite also works on tenant admin level where is Set-PnPSite works directly towards the site itself.


Update clip kit api and demonstration for identifier handling

This is a follow up on a previous pull request (Update clip kit api #12).
The issue of metainformation handling has been resolved using a test setup provided by Cheng-Hung Tsai. See test test_metainfo_handling

Hi Jacob. Sorry for taking a while to respond. We were having another critical issue related to cds with invalid length and I need to fix that first. Our codebase changed a lot to fix the issue and I kept having conflict to merge your PR. So I collected your codes and successfully integrate it into the latest dev branch. We'll keep test it before merge it back to the main. Thanks again for your help!

No problem. Thanks again for choosing ClipKIT for your alignment trimming needs.
Lastly, congratulations on joining a great lab - Jason is a superb scientist!


Rule proposal: Naming rule - naming of generic type arguments

I'd like to propose new naming rule for generic parameters. Name should start with "T", second character (if it exists) should be upper case letter or digit. AFAIK Whole BCL follows this convention.
Few valid names: "T", "T1", "TKey", "TValue"
Few invalid names: "t", "Tkey", "Key"
This rule was originally proposed by Andy Reeves here:
http://stylecop.codeplex.com/workitem/6891

I think this makes sense. It's certainly in line with the existing rule that applies to interface names.

:+1:

Grabbing this one


EnableNavigationPropertyPath per parameter for OoasUtil

Hello,
with every new release we have to put the Value vor EnableNavigationPropertyPath hardcoded to false. Is there a way to include it as an parameter for a future release? We have an automatic call per pipeline, so we cannot use the OoasGUI-Tool.
Regards,
Dominic

@DominicRoth we currently pass the parameters as below:
OpenApiConvertSettings settings = new()
{
    EnableNavigationPropertyPath = false
};

OpenApiDocument document = EdmModel.ConvertToOpenApi(Settings);

can you provide further details on a different approach that you have in mind?


Smeshing methods (WIP)

Closes #13

This is based on the wrong branch. Could you please rebase on the v0.2 branch? (https://github.com/spacemeshos/api/commits/v0.2)

should be ready for review now.

buf reports a bunch of breaking changes between the existing v0.1 API (master branch) and these changes. What do we want to do about these? Here's a full report:
> buf check breaking --against-input image.bin
proto/spacemesh/global_state.proto:40:23:RPC "AccountStream" on service "GlobalStateService" changed request type from ".google.protobuf.Empty" to ".spacemesh.AccountId".
proto/spacemesh/types.proto:92:5:Previously present enum value "6" on enum "TransactionStateType" was deleted without reserving the name "PROCESSED".
proto/spacemesh/types.proto:92:5:Previously present enum value "6" on enum "TransactionStateType" was deleted without reserving the number "6".
proto/spacemesh/types.proto:94:20:Enum value "1" on enum "TransactionStateType" changed name from "UNKNOWN" to "REJECTED".
proto/spacemesh/types.proto:95:30:Enum value "2" on enum "TransactionStateType" changed name from "REJECTED" to "INSUFFICIENT_FUNDS".
proto/spacemesh/types.proto:96:23:Enum value "3" on enum "TransactionStateType" changed name from "INSUFFICIENT_FUNDS" to "CONFLICTING".
proto/spacemesh/types.proto:97:19:Enum value "4" on enum "TransactionStateType" changed name from "CONFLICTING" to "PENDING".
proto/spacemesh/types.proto:98:21:Enum value "5" on enum "TransactionStateType" changed name from "PENDING" to "PROCESSED".
proto/spacemesh/types.proto:111:21:Enum value "4" on enum "TransactionType" changed name from "DEPLOY" to "SPAWN_APP".
proto/spacemesh/types.proto:154:5:Previously present enum value "3" on enum "LayerStatus" was deleted without reserving the name "CONFIRMED".
proto/spacemesh/types.proto:154:5:Previously present enum value "3" on enum "LayerStatus" was deleted without reserving the number "3".
proto/spacemesh/types.proto:156:20:Enum value "1" on enum "LayerStatus" changed name from "UNKNOWN" to "APPROVED".
proto/spacemesh/types.proto:157:21:Enum value "2" on enum "LayerStatus" changed name from "APPROVED" to "CONFIRMED".
proto/spacemesh/types.proto:168:1:Previously present field "6" with name "current_layer" on message "NodeStatus" was deleted without reserving the name "current_layer".
proto/spacemesh/types.proto:168:1:Previously present field "7" with name "verified_layer" on message "NodeStatus" was deleted without reserving the name "verified_layer".
proto/spacemesh/types.proto:168:1:Previously present field "6" with name "current_layer" on message "NodeStatus" was deleted without reserving the number "6".
proto/spacemesh/types.proto:168:1:Previously present field "7" with name "verified_layer" on message "NodeStatus" was deleted without reserving the number "7".
proto/spacemesh/types.proto:169:5:Field "1" with name "connected_peers" on message "NodeStatus" changed option "json_name" from "knownPeers" to "connectedPeers".
proto/spacemesh/types.proto:169:12:Field "1" on message "NodeStatus" changed name from "known_peers" to "connected_peers".
proto/spacemesh/types.proto:170:5:Field "2" with name "is_synced" on message "NodeStatus" changed option "json_name" from "minPeers" to "isSynced".
proto/spacemesh/types.proto:170:5:Field "2" on message "NodeStatus" changed type from "uint64" to "bool".
proto/spacemesh/types.proto:170:12:Field "2" on message "NodeStatus" changed name from "min_peers" to "is_synced".
proto/spacemesh/types.proto:171:5:Field "3" with name "synced_layer" on message "NodeStatus" changed option "json_name" from "maxPeers" to "syncedLayer".
proto/spacemesh/types.proto:171:12:Field "3" on message "NodeStatus" changed name from "max_peers" to "synced_layer".
proto/spacemesh/types.proto:172:5:Field "4" with name "top_layer" on message "NodeStatus" changed option "json_name" from "isSynced" to "topLayer".
proto/spacemesh/types.proto:172:5:Field "4" on message "NodeStatus" changed type from "bool" to "uint64".
proto/spacemesh/types.proto:172:12:Field "4" on message "NodeStatus" changed name from "is_synced" to "top_layer".
proto/spacemesh/types.proto:173:5:Field "5" with name "verified_layer" on message "NodeStatus" changed option "json_name" from "syncedLayer" to "verifiedLayer".
proto/spacemesh/types.proto:173:12:Field "5" on message "NodeStatus" changed name from "synced_layer" to "verified_layer".
proto/spacemesh/types.proto:202:21:Enum value "3" on enum "NodeErrorType" changed name from "SIGNAL_SHUT_DOWN" to "PANIC_P2P".
proto/spacemesh/types.proto:206:5:Field "1" with name "error_type" on message "NodeError" changed option "json_name" from "type" to "errorType".
proto/spacemesh/types.proto:206:19:Field "1" on message "NodeError" changed name from "type" to "error_type".

I think we should not worry about 0.1 compatibility because everything is in a flux now and not yet even pass design review. I think it is highly likely that even this will still change in many ways based on design reviews and found issues...


faction-manager.js: NeuroFlux Governor Level -1

Something seems off in the faction-manager NF calculation or is a NF level of -1 actually a thing?
I haven't had time to look into this yet.
Current BitNode: 14.1 (First run)

It's possible that this has the same cause as #406. If so, please close this as duplicate.

I'll leave it open for now as it's a simple case to reproduce, but yeah I believe it's the same root cause, missing a bitnode multiplier in the equation


DOI harvester

For a set of DOI's, retrieve full metadata (and harmonize to common model)?
Following repositories can be used to retrieve metadata

DataCite
OpenAire
Crossref
DOI (accept header bibtex)

Each platform provides dedicated information, so potentially we can query each of them:

openaire acknowledges various sources on which it has found the resource
crossref adds citation links for each of the citations in an article
Datacite has the most elaborate metadata model

from 2500 records in cordis, 48 did not exist in OpenAire, they either can be found on crossref or DOI (bibtext) or do not exist


fix(legacy-plugin-chart-calendar): fix timestamp timezone in Calendar

SUMMARY
Previously, the tooltips in Calendar Heatmap chart where displaying the date with user's local timezone applied. So for instance, if the query returned a date "2015-01-01 00:00:00", for a user in Poland the tooltip would be "2014-12-31 23:00:00" because of the timezone.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Before:

After:

TESTING INSTRUCTIONS

Create a Calendar Heatmap chart
Verify that the dates in the calendar are UTC

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

CC @junlincc

/testenv up


python312Packages.owslib: 0.29.3 -> 0.30.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python312Packages.owslib is: Client for Open Geospatial Consortium web service interface standards
meta.homepage for python312Packages.owslib is: https://www.osgeo.org/projects/owslib/
meta.changelog for python312Packages.owslib is: https://github.com/geopython/OWSLib/releases/tag/0.30.0
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.30.0 with grep in /nix/store/vhcnhppb7hwhjgpvgxvykps4gj6nhja0-python3.12-owslib-0.30.0
found 0.30.0 in filename of file in /nix/store/vhcnhppb7hwhjgpvgxvykps4gj6nhja0-python3.12-owslib-0.30.0

Rebuild report (if merged into master) (click to expand)

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath
python311Packages.cartopy
python311Packages.owslib
python312Packages.owslib
qgis
qgis-ltr

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vhcnhppb7hwhjgpvgxvykps4gj6nhja0-python3.12-owslib-0.30.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python312Packages.owslib https://github.com/r-ryantm/nixpkgs/archive/60f1a036a4f0345f742658228af653729714cbad.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/60f1a036a4f0345f742658228af653729714cbad#python312Packages.owslib

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/vhcnhppb7hwhjgpvgxvykps4gj6nhja0-python3.12-owslib-0.30.0
ls -la /nix/store/vhcnhppb7hwhjgpvgxvykps4gj6nhja0-python3.12-owslib-0.30.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages failed to build:

python311Packages.cartopy
python311Packages.cartopy.dist
qgis
qgis-ltr

4 packages built:

python311Packages.owslib
python311Packages.owslib.dist
python312Packages.owslib
python312Packages.owslib.dist

Maintainer pings
cc @imincik @nh2 @nialov @sikmir @willcohen for testing.

Result of nixpkgs-review pr 294874 run on x86_64-linux 1

4 packages failed to build:

python311Packages.cartopy
python311Packages.cartopy.dist
qgis
qgis-ltr

4 packages built:

python311Packages.owslib
python311Packages.owslib.dist
python312Packages.owslib
python312Packages.owslib.dist

GDAL build is failing on JAVA bindings build error
gdal> [100%] Generating gdal.jar, build/maven/gdal-3.8.4.jar, build/maven/gdal-3.8.4-sources.jar, build/maven/gdal-3.8.4.pom, build/maven/gdal-3.8.4-javadoc.jar
gdal> Buildfile: /build/source/swig/java/build.xml
gdal>
gdal> init:
gdal>      [echo] version = 3.8.4
gdal>
gdal> compile:
gdal>     [mkdir] Created dir: /build/source/build/swig/java/build/classes
gdal>     [javac] Compiling 88 source files to /build/source/build/swig/java/build/classes
gdal>     [javac] warning: [options] bootstrap class path not set in conjunction with -source 7
gdal>     [javac] error: Source option 7 is no longer supported. Use 8 or later.
gdal>     [javac] error: Target option 7 is no longer supported. Use 8 or later.
gdal>
gdal> BUILD FAILED
gdal> /build/source/swig/java/build.xml:25: Compile failed; see the compiler error output for details.

GDAL build is fixed now. I believe this PR is ready to be merged.


[BUG] Does not work in IE8

Works in IE9 and IE10 but not in IE8

Hi, I've forked this repository and added IE8 support - https://github.com/entozoon/pointer_events_polyfill
Use this updated js, and also add a data-pointer-events-none attribute to your element. e.g.
<div data-pointer-events-none></div>


Kite installation on Spyder would require a note on restrictions

Description
What steps will reproduce the problem?

When initiating Spyder for the first time, one can opt to install Kite (www.kite.com). The issue is that Kite is cost-free but also a priced package; the cost-free version is restricted. One can infer that the restrictions of Kite would restrict the Spyder features (v.gr. Larger ML models or Multi-Line Completions generated by deep learning). You may include a note on the implied Spyder restrictions when installing Kite.

We already mention that Kite is not open source in the initial dialog that it's displayed about it.

The issue is that Kite is cost-free but also a priced package; the cost-free version is restricted

We have no idea what those restrictions are, but we provide a link to Kite's website, so users can inform about them.
Also, those restrictions could change in the future, so asking us to keep track of them is too much work, sorry.


xournalpp - pdf annotation tool can't export pdf (cairo error)

Describe the bug
Xournal++ throws a cairo error instead of exporting to pdf. The rest of the app works fine. Tested in versions 1.2.4 and 1.2.5 (unstable)
Steps To Reproduce
Steps to reproduce the behavior:

Launch xournalpp
Open from a pdf
Export to pdf

Expected behavior
PDF is generated
Screenshots

Additional context

AppImage works fine.
Bug also reported from Flatpak users, see https://github.com/xournalpp/xournalpp/issues/5948

Xournal++ team closed the issue because it's system-dependant. Could there be some missing Cairo prerequisites?
Metadata

system: "x86_64-linux"
host os: Linux 6.6.60, NixOS, 24.11 (Vicuna), 24.11.20241213.314e12b
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.24.10
channels(ng): ""
channels(root): "nixos"
nixpkgs: /nix/store/0xbni69flk8380w0apw4h640n37wn1i9-source

Notify maintainers
@sikmir are you experiencing this bug too?

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

Oops, I accidentally pinged the bot. Pinging @sikmir here to be sure :wave: thanks and sorry about that

(I am using Xournal++ PDF export on a not-NixOS-but-close following master; 1.2.5 works fine for me including PDF export, just checked /nix/store/l6kf6zsyq2lplrildfbhbimkplxn8zvq-xournalpp-1.2.5/bin/xournalpp)

According to related issues, error happens when exporting a pdf annotated with png files.
xournalpp maintainer also replied that we might want to update/patch cairo.

Also does not work for me on 1.2.4, 1.2.5 and the Flatpak version https://flathub.org/apps/com.github.xournalpp.xournalpp