JTAG debugging over USB cable

Espressif documentation mentions that the ESP32-C3 has built-in JTAG functionality and that "JTAG debugging is through an USB cable connected to the D+/D- USB pins of ESP32-C3. No need for an external JTAG adapter and extra wiring / cable to connect JTAG to ESP32-C3."
When I launch openocd -f board/esp32c3-builtin.cfg with the USB cable connected however I get:
Open On-Chip Debugger  v0.10.0-esp32-20210401 (2021-04-01-15:45)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Warn : Transport "jtag" was already selected
force hard breakpoints
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: esp_usb_jtag: could not find or open device!

Am I using the wrong openocd config? How does this work?
Thanks.

The USB JTAG support works well on the OI-PLUS for me, but I'm using a commercial product that makes things easy, VisualGDB.
I just did a quick test with ESP-IDF 4.3.  Debugging works for me, using the same command and version of openocd as you, but flashing doesn't.  Apparently the flashing problem is fixed in a later release of openocd -- https://github.com/espressif/openocd-esp32/releases/tag/v0.10.0-esp32-20210721.
Are you using the USB port on the OI-PLUS?  I don't think that can be made to work.  Instead, you need to connect a USB breakout board to 5V, GND, GPIO18 and GPIO19, as described here: https://visualgdb.com/tutorials/esp32/esp32-c3/.
Also,  you need to use a WinUSB driver from Espressif, as described here: https://docs.espressif.com/projects/esp-idf/en/latest/esp32c3/api-guides/jtag-debugging/configure-builtin-jtag.html.  I had to manually switch to their driver using this tool: https://visualgdb.com/UsbDriverTool/.
I hope that helps.
Dan.

Thanks for your response Dan.

Are you using the USB port on the OI-PLUS?

I was. Thanks to you I re-read the instructions and now realise that I am suposed to connect with a USB cable through a USB-to_TTL adapter to GPIO18, GPIO19, 5V and GND pins of the board.
I also updated openocd-esp32 to the version that you mentioned (2021-07-21). I am using linux therefore I do not need a driver. However the command openocd -f board/esp32c3-builtin.cfg still returns the same Error: esp_usb_jtag: could not find or open device!. I tried swapping the wires connected to GPIO18 and GPIO19 witth the same result.
Do you have to specify somehow to which COM device the USB adapter is connected? Otherwise, how would openocd know where to find it...
Thanks.

Hi,
I just tried running on Linux, specifically Ubuntu 20.04.
It works for me.  I suspect the difference is that I (unintentionally) installed the 4.4-dev version of ESP-IDF.  Based on my Googling, it seems that USB JTAG support is flaky in ESP-IDF 4.3.x.
Other than that, the only problem I had to deal with was the udev settings.  I think you've already done that, since you didn't get any LIBUSB errors, but you definitely need the udev rules in order for openocd to work.  The udev rules I used are from https://github.com/espressif/openocd-esp32/blob/master/contrib/60-openocd.rules.
I also had problems once I connected with gdb: the gdb session timed out, and the openocd session would have a lot of "usb received only x out of y bytes".  I fixed that by lowering the adapter speed setting.
The openocd command line I ended up using is:
openocd -f interface/esp_usb_jtag.cfg -c "adapter_khz 3000" -f target/esp32c3.cfg
I actually don't know openocd at all - I just copied this from what VisualGDB uses. Maybe the board parm would work, and maybe the interface parm isn't needed, but the above works for me.
Flashing still doesn't work for me.  I found that you can disconnect the 5V cable on the USB breakout board (the one used for JTAG), then connect a second cable to the OI-PLUS's USB C port, then flash the code through USB.
I hope that helps.
Dan.

The problem is that I kept trying to connect to the GPIO18 and GPIO19 port through a USB-to TTL adapter. Actually the link that you provided (https://visualgdb.com/tutorials/esp32/esp32-c3/) shows that the USB wires have to be directly connected to the pins. Also, the data sheet specifies that  GPIO18 and GPIO19 pins provide USB D+/D- signals, not UART TX/RX.
That option is a lot less appealing than my original expectation of debugging through the USB-C connector of the board. I am going to try to use an external JTAG probe instead (and burn the corresponding fuse).
Anyway, thanks a lot for your help. I hope that flashing gets resolved soon to simplify your process.
Thanks.

For what it's worth, flashing through the USB JTAG connection does work for me now.  I actually don't know what changed from when it failed on Saturday, so this feature might be flaky, or maybe just user error.
Here's what worked for flashing the hello-world sample - it's the same as in the Espressif docs.  As mentioned, I'm using the 4.4dev version of ESP-IDF, so the openocd version is more recent than the one I linked to earlier.
openocd -f board/esp32c3-builtin.cfg -c "program_esp build/hello-world.bin 0x10000 verify exit"

Output:
Open On-Chip Debugger  v0.10.0-esp32-20210902 (2021-09-02-09:38)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
Warn : Transport "jtag" was already selected
Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40101104
Info : Listening on port 3333 for gdb connections
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 24 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 87 KB
Info : Auto-detected flash bank 'esp32c3.flash' size 4096 KB
Info : Using flash bank 'esp32c3.flash' size 4096 KB
** Programming Started **
Info : PROF: Data transferred in 2726.99 ms @ 58.6727 KB/s
** Programming Finished **
** Verify Started **
** Verified OK **
shutdown command invoked

To clarify the type of USB connection I'm using, it's a simple breakout board like this one: https://www.adafruit.com/product/1764.  I think a breakout cable like this would also work, though I don't own one: https://www.adafruit.com/product/4448

I did not want to wait for the delivery of a breakout adapter so I built a frankencable with an old usb cable that cut and soldered to 4 Dupont wires.
On the software side, I deleted the complete esp-idf installation and restarted from scratch with the master branch. After a few I managed to get it installed correctly. Like you, I am now able to do build and upload the binary over the built-in JTAG interface at last. I am not able to debug it yet though. Launching idf.py gdb fails with
Executing action: gdb
riscv32-esp-elf-gdb: error while loading shared libraries: libpython2.7.so.1.0: cannot open shared object file: No such file or directory

This sounds like riscv32-esp-elf-gdb is built with python 2.7 but I only have python 3.9 installed. I don´t feel like installing python 2.7 just for this. Do you have python 2.7 installed?

Yes, I do: Python 2.7.18.  That library was installed by the libpython2.7 package.
I had no idea Python 2.7 was prereq for riscv32-esp-elf-gdb or any other part of ESP-IDF -- there's no mention of it in the ESP-IDF prereqs page.  I must have installed Python 2.7 a long time ago for some other project.
Seems like yet another bug in the ESP-IDF support for this chip, though I don't see any issues about it on the ESP-IDF Github.   If you don't want to install Python 2.7 (or maybe installing just libpython2.7 would work?), maybe you should open an issue on the ESP-IDF Github - they might provide a fix or workaround.

I installed python 2.7 for now and this problem is resolved. I reported the issue to Espressif (https://github.com/espressif/openocd-esp32/issues/181).
Now when I start gdb I get:
Ignoring packet error, continuing...
warning: unrecognized item "timeout" in "qSupported" response
/home/jeancf/Documents/esp32c3/hello_world/build/gdbinit:2: Error in sourced command file:
Remote replied unexpectedly to 'vMustReplyEmpty': PacketSize=4000;qXfer:memory-map:read+;qXfer:features:read+;qXfer:threads:read+;QStartNoAckMode+;vContSupported+

At the same time, on the side of openocd I see:
Info : accepting 'gdb' connection on tcp/3333
Warn : No symbols for FreeRTOS!
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 26 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 88 KB
Info : Auto-detected flash bank 'esp32c3.flash' size 2048 KB
Info : Using flash bank 'esp32c3.flash' size 2048 KB
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 26 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 88 KB
Info : Using flash bank 'esp32c3.irom' size 92 KB
Info : Flash mapping 0: 0x10020 -> 0x3c020020, 26 KB
Info : Flash mapping 1: 0x20020 -> 0x42000020, 88 KB
Info : Using flash bank 'esp32c3.drom' size 28 KB
Warn : negative reply, retrying
Warn : negative reply, retrying
Warn : negative reply, retrying
Error: GDB missing ack(2) - assumed good
Error: GDB missing ack(2) - assumed good
Error: GDB missing ack(2) - assumed good
Info : dropped 'gdb' connection

gdbinit file:
file /home/jeancf/Documents/esp32c3/hello_world/build/hello-world.elf
target remote :3333
mon reset halt
flushregs
thb app_main
c

Neverending nightmare...

That "Error in sourced command file" might be the cause.
I'm using a slightly different gdbinit without the file command -- I copied it from the docs:
target remote :3333
set remote hardware-watchpoint-limit 2
mon reset halt
flushregs
thb app_main
c

I specify the .elf file in the gdb command line instead:
riscv32-esp-elf-gdb -x gdbinit build/hello-world.elf


[Snyk] Upgrade org.apache.logging.log4j:log4j-core from 2.18.0 to 2.20.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade org.apache.logging.log4j:log4j-core from 2.18.0 to 2.20.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released 8 months ago, on 2023-02-18.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

merged from ci


Remove unused wallet context args

Description
We were passing models and me into the wallet test functions. I think they were used in the past for logging but we no longer need them.
I also removed logger from the NWC functions since they don't use it.
Additional Context
Maybe I am overdoing it with small PRs but it's nice to get small changes out of the way so I can focus on the relevant stuff in #1558.
Checklist
Are your changes backwards compatible? Please answer below:
yes
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
5. I looked at all testSendPayment and testCreateInvoice function signatures and saw none of them use these arguments.
Regarding removal of logger: removing an unused argument doesn't break any function calls in JS since you can always call a function with as many arguments as you want, any arguments that aren't defined as parameters are simply not used.
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
n/a
Did you introduce any new environment variables? If so, call them out explicitly here:
no

Maybe I am overdoing it with small PRs but it's nice to get small changes out of the way so I can focus on the relevant stuff in https://github.com/stackernews/stacker.news/issues/1558.

You aren't. It's easier to review one "subject" at a time.


Remove survey test schemas and associated integration tests

What is the context of this PR?
Remove real surveys that are being used in tests. Refactor tests to use test schemas to maintain coverage
How to review
All real schemas and starwars should be removed.
Where tests have been removed, other scenarios should be present
Checklist

[ ] New static content marked up for translation
[ ] Newly defined schema content included in eq-translations repo

@iwootten can you re-review


Allow creating dynamic snippets with empty content for backward compa…

…tibility
Our Terraform provider is currently relying on this implementation.

@Integralist this is for https://github.com/fastly/terraform-provider-fastly/pull/467


Stop! XXX is not a valid candidate. When jenv ls

Here is the log. It looks like missing some line for jenv repo update output. And jenv works well in some machine havenot upgrade...
$ jenv selfupdate

Updating jenv...
Purge existing scripts...
  For me it also affects installs.

this is a bug in some version in linux because of alias problem. fixed, please update to last version

Refresh:
export SDKMAN_DIR="$HOME/.sdkman" && source "$HOME/.sdkman/bin/sdkman-init.sh"


glm4-9b如何量化运行？

Motivation
lmdeploy lite auto_awq THUDM/glm-4-9b-chat --work-dir ~/work/models/glm-4-9b-chat-4bit
提示不支持，无法量化成awq格式，目前huggingface上也没有awq格式的glm4-9b
Related resources
No response
Additional context
No response

python3 -m lmdeploy lite auto_awq /workdir/glm-4-9b-chat

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.9/runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "/workdir/lmdeploy/lmdeploy/__main__.py", line 5, in <module>
    run()
  File "/workdir/lmdeploy/lmdeploy/cli/entrypoint.py", line 36, in run
    args.run(args)
  File "/workdir/lmdeploy/lmdeploy/cli/lite.py", line 139, in auto_awq
    auto_awq(**kwargs)
  File "/workdir/lmdeploy/lmdeploy/lite/apis/auto_awq.py", line 103, in auto_awq
    vl_model, model, tokenizer, work_dir = calibrate(model,
  File "/workdir/lmdeploy/lmdeploy/lite/apis/calibrate.py", line 188, in calibrate
    raise RuntimeError(
RuntimeError: Currently, quantification and calibration of ChatGLMForConditionalGeneration are not supported. The supported model types are InternLMForCausalLM, InternLM2ForCausalLM, QWenLMHeadModel, Qwen2ForCausalLM, BaiChuanForCausalLM, BaichuanForCausalLM, LlamaForCausalLM, LlavaLlamaForCausalLM, MGMLlamaForCausalLM, InternLMXComposer2ForCausalLM.

cc @AllentDan

GLM-4-9B-Chat  performs quite well and it is worth considering to provide support for it. ref https://github.com/InternLM/lmdeploy/issues/1974#issue-2398575348

ref
https://github.com/InternLM/lmdeploy/pull/1993
https://github.com/zhyncs/lmdeploy-build/releases/tag/6367976


Support/bot phosphore

📝 Description

Fixes naming of bot workflow to not glitch markdown
Split github report from full report to prevent failed report
add a clearer error in case pickSiblings fail
Reduces the chance to delegate on cosmos, reduce minAmount

❓ Context

Impacted projects: bot
Linked resource(s): ``

✅ Checklist

[x] Test coverage
[x] Atomic delivery
[x] No breaking changes

📸 Demo

🚀 Expectations to reach
Please make sure you follow these Important Steps.
Pull Requests must pass the CI and be internally validated in order to be merged.

(last run was :x: because the actions was not having the new "github-report" on develop yet, after this merge it should work again)


copr: fix a wrong check in time parsing

Signed-off-by: gengliqi<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: Close #12739
What's Changed:

See #12739

Related changes

Need to cherry-pick to the release branch

Check List
Tests

Unit test

Side effects

No

Release note
Fix a wrong check in datetime when the datetime has a fraction and 'Z'

/run-check-issue-triage-complete

/run-check-issue-triage-complete

/run-check-issue-triage-complete

/merge


Failing to retrieve the variants.yml file

2024-05-10 12:23:17,782 - CRITICAL - Uncaught exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/local/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/home/rm_bot/bugbot/bugbot/rules/variant_expiration.py", line 418, in <module>
    VariantExpiration().run()
  File "/home/rm_bot/bugbot/bugbot/rules/variant_expiration.py", line 98, in __init__
    self.variants = self.get_variants()
  File "/home/rm_bot/bugbot/bugbot/rules/variant_expiration.py", line 137, in get_variants
    resp.raise_for_status()
  File "/home/rm_bot/bugbot/venv/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 404 Client Error: Not Found for url: https://hg.mozilla.org/mozilla-central/raw-file/tip/taskcluster/ci/test/variants.yml

From @jmaher on Matrix:

@ahal rearranged a bunch of files now it is https://searchfox.org/mozilla-central/source/taskcluster/kinds/test/variants.yml


decoder utf-8 for supporting chinese

hi: when i used it for my markdowns . i get error with the coding error. like below.
UnicodeEncodeError: 'ascii' codec can't encode characters in position 322-325: ordinal not in range(128)
i resolved it for decoder with "utf-8" and  pull request for your merge..

I should fix the ASCII/UTF-8 stuff at some point, but this PR contains a bunch of unrelated things.


Bitcoin: Identify new trading strategies for Bitcoin on L2s with low fees

Bitcoin: Identify new trading strategies for Bitcoin on L2s with low fees

Closed as done.


Error due to require_once when using Composer

When using this package via Composer I am getting errors each time a class file calls require_once. The require_once calls should be removed in deference of Composer's autoloader.

I have same issue when create new youtube client: $yt = new Zend_Gdata_YouTube();
PHP Warning:  require_once(Zend/Gdata/Media.php): failed to open stream: No such file or directory in /vendor/zend/gdata/library/Zend/Gdata/YouTube.php on line 27

You can even fix it in your composer.json:
...
    "include-path": [
        "vendor/zend/gdata/library"
    ],
...

And the best fix would be IMHO to add this right into composer.json in this repository.


will at-portal generated event subscription support manual validation?

r.t., seems right now if i generate a event grid subscription at azure portal, the deployment fails right after got a response without validationcode.

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

ID: 9ea53478-b3df-71dd-5ec8-27746a650775
Version Independent ID: 185f045e-d659-6217-3c14-68418c4fe5fe
Content: Azure Event Grid security and authentication
Content Source: articles/event-grid/security-authentication.md
Service: event-grid
GitHub Login: @banisadr
Microsoft Alias: babanisa

@yixue-at-symantec Thanks for the feedback! We will review and get back to you on this.

@yixue-at-symantec It does seem to have failed but it actually is transitioned to manual mode as documented

This authentication mechanism also requires the webhook endpoint to return an HTTP status code of 200 so that it knows that the POST for the validation event was accepted before it can be put in the manual validation mode. In other words, if the endpoint returns 200 but doesn’t return back a validation response programmatically, the mode is transitioned to the manual validation mode. If there is a GET on the validation URL within 5 minutes, the validation handshake is considered to be successful.

The subscription is visible in the portal as well with its provisioningState set to AwaitingManualAction. You check this using the REST API.
Now, if you make a GET call to the validationUrl sent to your webhook, the state is changed to Succeeded.

I just noticed that the manual validation is actually working, but it's sending a wrong notification on the portal says

Deploying Event Subscription:  Deployment has failed with the following error: undefined

Is it possible get this misleading notification removed?
I noticed that if i use arm template to deploy eventgrid subscription instead of add the subscription in "blobstorage>events>add", when transitioned to manual mode it didn't send the "failed" notification.

@yixue-at-symantec We have raised this issue with the concerned team.
We are assigning this issue to the content author to close once the issue is fixed.

I was told that this issue is fixed, so closing the issue.
#please-close


Return render from constructor?

A question I've had for a long time now is how to provide better support for CSR (client side rendering) projects when we don't know what render framework the developer is using (if any).
Current Solution
Developers need to call this.render() themselves. Usually in the constructor() or connected() methods. This, however, is a low quality solution for several reasons:
Component Render Pop
Components that render child Components will often "pop" since they don't render until the node has been bound with the class instance. The deeper the rabbit hole goes, the longer the delay before everything renders.
Janky Child Queries
If a Component needs to query an element from a child/grandchild Component it must wait until the Component has rendered. In libraries like lit-html the render() method run synchronously so you could query the DOM immediately, however since we force developers to wait until the child Components render() method runs developers currently need to create temporary setTimeout methods to provide the DOM ~100ms to render all child DOM nodes before performing a query.
Uncertainty
By forcing each Component to call the render() method manually logic may be placed before the method is called. This means a parent/grandparent Component will never know how long (if at all) it will be until one of it's dependents have rendered.
Possible Solution
Add a new boolean value to the SuperComponent class constructor method. In order to preserve backwards compatibility this value should default to false. When true the SuperComponent class constructor will return the this.render() method.
export default class SuperComponent extends HTMLElement{
    constructor(returnRender = false){
        super();
        if (returnRender) return this.render();
    }
}

I've done no testing but assuming we can return a value from the constructor() this would allow us to output JSX or some other variation of markup from the render() method instead of trying to render the markup ourselves.
import { html } from "lit-html";
export default class ExampleComponent extends SuperComponent {
    constructor(){
        super(true);
    }
    render(){
        return html`

I should be rendered by a parent.

        `;
    }
}

Limitations / Problems
How do we know the parent exists? In frameworks like React, Preact, or Vue everything usually resolves upwards to one Component that binds/renders into a DOM node. Typically this might be some sort of App Component. With SuperComponents a Component could be a standalone Component or a child of another Component.
Below is an example of an Input Component rendering into a parent Component.
// login-form-component.js
import { html, render } from "lit-html"
import Input from "./input-component.js";
export default class LoginFormComponent extends SuperComponent {
    constructor(){
        super();
        this.render();
    }
    render(){
        const view = html`
            ${new Input()}
        `;
        render(view, this);
    }
}

// input-component.js
import { html } from "lit-html";
export default class InputComponent extends SuperComponent {
    constructor(){
        super(true);
    }
    render(){
        return html`
            <input type="text" >
        `;
    }
}

Now the question is: how do we render the InputComponent on it's own? When creating CSR web applications this isn't an issue. There will be some sort of App or Page class that imports and renders the Input Component. However, what if developers want to leverage SSR (server side rendering)? I'm using this library to handle data modeling and state management for Brixi UI and I support both CSR and SSR rendered components.
Alternate Solution 1
The render() method could be modified to accept the boolean value. When true the developer knows they need to return the markup instead of rendering it themselves. This solution would require developers to build a system that works for their individual needs.
// input-component.js
import { html, render } from "lit-html";
export default class InputComponent extends SuperComponent {
    constructor(){
        super();
    }
    render(returnMarkup = false){
        const view = html`
            <input type="text" >
        `;
        if (returnMarkup){
            return view;
        } else {
            render(view, this);
        }
    }
}

// login-form-component.js
import { html, render } from "lit-html"
import Input from "./input-component.js";
export default class LoginFormComponent extends SuperComponent {
    constructor(){
        super();
        this.render();
    }
    render(){
        const view = html`
            ${new Input().render(true)}
        `;
        render(view, this);
    }
}

Alternate Solution 2
We could check if the render() method returns void. This would allow developers to implement their own SSR logic for standalone Components while also providing an official avenue for returning markup. This solution releases developers from taking on the responsibility of adding true or false to their super() function calls, however, would be a breaking change. This also does nothing to assist developers using both CSR and SSR.
export default class SuperComponent extends HTMLElement{
    constructor(){
        super();
        const renderMarkupResult = this.render();
        if (renderMarkupResult != undefined) return renderMarkupResult;
    }
}

After a quick test the constructor() method can return custom data if the output is an object otherwise it returns the class.
class Test{
    constructor(){
        return {
            data: "Hello world",
        };
    }
}
const test = new Test();
console.log(test.data); // Output: "Hello world"

We could consider returning an object with the markup.
export default class SuperComponent extends HTMLElement{
    constructor(){
        super();
        const renderMarkupResult = this.render();
        if (renderMarkupResult != undefined) return { markup: renderMarkupResult };
    }
}

After additional testing the super() method must always be called first (duh) which means that our return will never provide valid markup. Data in the model will not be set until after the super() method call so at best the attempt to call render() in the base SuperComponent class will return an invalid/inaccurate response. In most cases I'd expect it to break entirely.
It appears that Alternate Solution 1 is the best bet which means that no change is required for the base class. Implementing render() returns can be left up to the developers.

While exploring this solution within my own projects I've noticed that the TypeScript compiler throws an error when the render override adds arguments that don't exist on the base method. This issue can be overcome by adding //@ts-ignore however, it's not an ideal solution. I think modifying the base method to support the returnMarkup argument (defaulted to false) would be a welcomed change.


Some QoL changes

???
There is no hardcoded secret in that file???

@Tolfx

??? There is no hardcoded secret in that file???

The testing files has tokens, but only used for testing so nothing to worry about.


Hatch creation issue

The creation of a hatch yielded an dxf file, which AutoCAD 2022 could not read.
The hatch was created like this (inspired by #136):
var file = new DxfFile();
var header = file.Header;
header.SetDefaults();
header.Version = DxfAcadVersion.R2018;
var boundaryPath = new DxfHatch.NonPolylineBoundaryPath(DxfHatch.BoundaryPathType.Polyline);
for(var i=0; i < v.Length-1; ++i)
  boundaryPath.Edges.Add(new DxfHatch.LineBoundaryPathEdge() { StartPoint =v[i], EndPoint =v[i+1] });
boundaryPath.Edges.Add(new DxfHatch.LineBoundaryPathEdge() { StartPoint = v[^1], EndPoint = v[0] });
var hatch = new DxfHatch { PatternName = "SOLID" };
hatch.BoundaryPaths.Add(boundaryPath);
file.Entities.Add(hatch);
file.Normalize();
file.Save("Test.dxf", true);

The error message in AutoCAD was the following (translated from German):
The following error was detected while reading
in HATCH starting at line 1930:
Error: Group code 71 expected.
Invalid or incomplete DXF input -- drawing aborted.

Here is the relevant part from the dxf file starting at line 1930, it contains the code 71:
HATCH
  5
1D
100
AcDbEntity
  8
0
370
     0
430

440
        0
284
     0
100
AcDbHatch
 10
0.0
 20
0.0
 30
0.0
210
0.0
220
0.0
230
1.0
  2
SOLID
 70
     0
 63
   256
 71
     0
 91
        1
 92
        2
 93
        4
 72
     1
 10
860116.930352756
 20
5794971.436
 11
860116.930352756
 21
5794999.004
 72
     1
 10
860116.930352756
 20
5794999.004
 11
860112.9501
 21
5794999.004
 72
     1
 10
860112.9501
 20
5794999.004
 11
860112.9501
 21
5794971.436
 72
     1
 10
860112.9501
 20
5794971.436
 11
860116.930352756
 21
5794971.436
 97
        0
 75
     0
 76
     0
 52
0.0
 41
1.0
 77
     0
 78
     0
 47
1.0
 98
        0
450
        0
451
        0
452
        0
453
        0
460
0.0
461
0.0
462
0.0
463
0.0
470
LINEAR

A hatch generated from within AutoCAD looks slightly different:
HATCH
  5
2BC
330
1F
100
AcDbEntity
  8
0
100
AcDbHatch
 10
0.0
 20
0.0
 30
0.0
210
0.0
220
0.0
230
1.0
  2
SOLID
 70
     1
 71
     1
...

Can you check something for me?  It looks like the difference is that AutoCAD generated codes 2, 70, 71, but this library generated 2, 70, 63, 71.  Can you manually swap the 63 and 71 codes and try to open that?  You can use Notepad or any basic text editor to make the relevant portion of the file read:
...
  2
SOLID
 70
     0
 71
     0
 63
   256
...

The swap changes the error message to "code 91 expected". Swapping this code also changes the error message. It looks like the order of the code should be exactly the same as in the case generated by AutoCAD. I adjusted the order until I got the error message "code 73 expected". According to the specs this is the code for the "Is closed"-flag for the polyline boundary data. It is missing in the output of the library.
Maybe the problem is
92
2

which indicates that the boundary is a polyline despite the fact that I used NonPolylineBoundaryPath.

I changed the c# code to generate a polyline boundary path:
var boundaryPath = new DxfHatch.PolylineBoundaryPath { IsClosed = true };
for(var i=0; i < v.Length; ++i)
  boundaryPath.Vertices.Add(new DxfVertex(Convert(v[i])));
var hatch = new DxfHatch {
  FillMode = DxfHatchPatternFillMode.SolidFill,
  FillColor = DxfColor.FromIndex(color),
  PatternName = "SOLID",
};
hatch.BoundaryPaths.Add(boundaryPath);

Then I had to do the following adjustments (left side version accepted by AutoCAD, right side library output):

Thank you for figuring out the correct order of the codes, this is hugely valuable.  Ultimately the fix is going to need to exist in EntitiesSpec.xml and I'd like it if the changes somewhat matched what the 2018 spec says about HATCH.

For code 63 that apparently needs to be removed, the spec says "For MPolygon, pattern fill color as the ACI".  There are several properties with the predicate "For MPolygon", but I don't see what would classify a hatch as an MPolygon.  Admittedly I'm not terribly familiar with the intricacies of AutoCAD, do you know what "MPolygon" could refer to?  If we can figure out when this value should be written or suppressed, a WriteCondition="" could be added here.
Code 78 is written here, I'm guessing a write condition should be added along the lines of PatternDefinitionLines.Count != 0.
Code 47 for pixel size.  The spec mentions "for associative hatches and hatches created with the Flood method of hatching" and code 71 specifies if the hatch is associative, so perhaps a write condition of IsAssociative would suffice?  I'm not sure what "Flood" means in this context, though.
Codes 452 and 453.  It looks like these just need to be moved down a bit?
Code 463.  The spec says it's reserved, so perhaps writing this value should be disabled?

What are your thoughts on the above?  I can work on some changes to address items 2-5, but I don't know what to do about item 1, code 63 and "MPolygon".

I am not an expert on AutoCAD or DXF files. I am just trying to write an DXF-export for my tool. Having said this, here are my guesses:
Concerning MPolygon the specs says in the very beginning:

The following group codes apply to hatch and MPolygon entities.

I would conclude that MPolygon is a different kind of entity which happens to be very similar to a hatch and shares most of the group codes. But I have no idea how to create a MPolygon in AutoCAD.
Concering 3.: Maybe it is better to related it to code 70 == 0 (pattern fill)? The specs says

... in hatch pattern computation for associative hatches ...

I agree with you on the other points.

I've added a branch write-hatch with some changes, can you see if it helps your scenario?
It includes the following changes from above:

I simply omit writing code 63.  I have no idea what "MPolygon" could mean; I'll have to revisit this.
Added the appropriate write condition for code 78.
I combined both of our suggestions and made the write condition FillMode == DxfHatchPatternFillMode.SolidFill || IsAssociative.  That way the "for associative hatches" condition is met as well as "hatches created with [] Flood" (I'm equating SolidFill with Flood.)
Codes 452 and 453 have been moved.
Code 463 has been removed.

Everything is fine now except the condition FillMode == DxfHatchPatternFillMode.SolidFill || IsAssociative did not work for me. One can have solid fill and still AutoCAD does not expect the group code 42. After changing it to FillMode == IsAssociative as you proposed in the beginning it worked for me.

Can you clarify some points for me?

You mention that code 42 was unexpected.  HATCH doesn't use this code, presumably this was a typo for 47?
What exactly is the condition that worked for you?  FillMode is an enum with values of PatternFill (0) and SolidFill (1), while IsAssociative is a bool.

Sorry for the confusion. It was already late yesterday when I wrote the comment and I got disturbed several times. I corrected it. What I meant was:

Group code 47 indeed.
IsAssociative instead of FillMode == DxfHatchPatternFillMode.SolidFill || IsAssociative

I played around with AutoCAD to generate a hatch containing group code 47, but I was not successful. Instead AutoCAD just froze quite frequently.

I've force-pushed to the write-hatch branch with your condition change.  If you could give it a quick check to make sure I set the condition appropriately, I'll merge this back to main.

The current version of write-hatch works for me.

Thanks for checking, I've merged these changed back to main via commit 38ecfd51d3222dab5dd5ef7198327823133ef997.


Select best-fitting model - 86cuvgxky

From: https://app.clickup.com/t/86cuvgxky
Choose the best-fitting model from the model evaluation table based on all included metrics. Usually, CRPS-based skill scores are sufficient to signify the best-fitting model, but it's always a good idea to include other metrics in the report.

Cancel the interrupted time-series analysis plan


How to optimize?

💬 Question
Do you have any information for make react-native-eva-icons is optimized use for bundler like webpack or facebook/metro ?
React Native Eva Icons Version

Version: 1.3.0

Example Bundle of react-native-icon
The real fact, I'm just use 1 Icon from react-native-icons. After finished bundling, the output bundle of my project it's lot an unused.

Same here. Is there a way to use a babel plugin like what they do with antd?
https://github.com/ant-design/babel-plugin-import

@gianpaj am I right that moving to direct imports should solve this?
https://github.com/artyorsh/react-native-eva-icons#usage

That should work, thanks. But I'm using a package and itself uses RN-eva-icons (react-native-ui-kitten)
And for some reason, I believe all the Icons are bundled
https://github.com/akveo/react-native-ui-kitten/blob/master/src/eva-icons/index.ts

Then I guess this is not the issue for this library.
But in case of using @ui-kitten/eva-icons package, you might want to follow this guide and write your own icon package that reduces using proxies (like it is currently implemented) in favor of direct imports.


refactor: cleanup API config

What this PR changes/adds
Sorry for the long changelog but the concept is quite simple: the need was to avoid "extension depends on extension" behavior we had in the api extensions, the solution evolved in:

remove the subclasses of WebServiceConfiguration as ManagementApiConfiguration, because they were just used to get the context alias for registering the controllers, in every case that is a static value (and now put in the ApiContext interface).
in fact the only service provided by "api-configuration" extensions that is used by other extensions is the url/endpoint one, that can be used for setting up callbacks (ProtocolWebhook for protocol, ControlApiUrl for control, ManagementApiUrl for management)

Why it does that
cleanup
Further notes

extractred a management-api-lib to keep common classes between management-api modules
stopping ServiceExtensionContext from being passed to WebServiceConfigurerImpl

Linked Issue(s)
Closes #4195
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.

Codecov Report
Attention: Patch coverage is 76.99115% with 26 lines in your changes are missing coverage. Please review.

Project coverage is 75.34%. Comparing base (7f20ba5) to head (aed1d63).
Report is 276 commits behind head on main.

Files
Patch %
Lines

...or/api/management/version/VersionApiExtension.java
0.00%
8 Missing :warning:

...tor/dataplane/api/DataPlanePublicApiExtension.java
0.00%
7 Missing :warning:

...r/dataplane/api/DataPlanePublicApiV2Extension.java
0.00%
5 Missing :warning:

...iguration/ManagementApiConfigurationExtension.java
82.35%
3 Missing :warning:

...java/org/eclipse/edc/web/jetty/JettyExtension.java
0.00%
1 Missing :warning:

...or/dataplane/api/DataPlaneControlApiExtension.java
0.00%
1 Missing :warning:

.../dataplane/api/DataPlaneSignalingApiExtension.java
0.00%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #4216      +/-   ##
==========================================
+ Coverage   71.74%   75.34%   +3.60%
==========================================
  Files         919     1035     +116
  Lines       18457    20637    +2180
  Branches     1037     1149     +112
==========================================
+ Hits        13242    15549    +2307
+ Misses       4756     4578     -178
- Partials      459      510      +51

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Change the dependsOn labels for the 'watch' task

Because the task signatures have been changed to npm: <task_name>, the dependsOn calls needed to change as well. Fixes #75

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

@okeefm thanks. Missed that when cleaning up the samples.

@okeefm can you sign the CLA please. Otherwise I cann't merge the PR.

The format has changed for dependent tasks. Will do the changes and closing this PR.


feat: add get class hash at to state reader

This change is

Codecov Report
Attention: Patch coverage is 80.00000% with 2 lines in your changes are missing coverage. Please review.

:exclamation: No coverage uploaded for pull request base (yael/add_get_storage_at_to_rpc_state_reader@ed10ef4). Click here to learn what that means.

Files
Patch %
Lines

crates/gateway/src/rpc_objects.rs
0.00%
1 Missing :warning:

crates/gateway/src/rpc_state_reader.rs
88.88%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@                              Coverage Diff                               @@
##             yael/add_get_storage_at_to_rpc_state_reader      #91   +/-   ##
==============================================================================
  Coverage                                               ?   56.06%
==============================================================================
  Files                                                  ?       14
  Lines                                                  ?      478
  Branches                                               ?      478
==============================================================================
  Hits                                                   ?      268
  Misses                                                 ?      197
  Partials                                               ?       13

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


CI/CD - Swift lint / swift format

Current core setup uses both swift lint and swift format for formatting. While both of them have various useful rules for formatting, when using both you can easily run into conflicts and one of them can invalidate the output of the other.
This may become an issue when you run these two commands in a certain order on the local machine, but the CI executes them in another order.
Based on https://github.com/adobe/aepsdk-core-ios/issues/67#issuecomment-671520955 we decided to use only Swift Lint for now in the Edge project, until we find a need for more granular formatting rules.
Additionally I noticed that ~2mins from the Core CI build time is spent with installing swift lint and format, while Edge uses ~8seconds for that. Feel free to check when you get a chance https://github.com/adobe/aepsdk-edge-ios/blob/main/.circleci/config.yml and @kevinlind can help with guidance for the setup if needed.

cc @yangyansong-adbe @shalehaha

This is how I'm installing SwiftLint, HOMEBREW_NO_AUTO_UPDATE=1 brew install swiftlint && brew cleanup swiftlint.  Updating Homebrew can take some time so it's best to disable auto-updates for the CI nodes.

@shalehaha @emdobrin @kevinlind
I don't think swiftlint can be used to check code format in CI. I have tried locally by using swiftlint lint command and also tried by creating a PR(https://github.com/adobe/aepsdk-edge-ios/pull/172) in Edge repo. But the following unformatted code can still pass CI.
https://github.com/adobe/aepsdk-edge-ios/pull/172/files#diff-16bb6e4ef18e2e302606606882caa26439091a2ec8fed5709310c8b89357cdd9R19
   public class Edge: NSObject, Extension {
        private let LOG_TAG = "Edge" // Tag for logging
    private var networkService: EdgeNetworkService = EdgeNetworkService()
    private var networkResponseHandler: NetworkResponseHandler?
    private var hitQueue: HitQueuing?
    private var currentPrivacyStatus: PrivacyStatus?

And also swiftlint and swiftformat support ignoring rules in config files, we can ignore any rules if there is a conflict.


Secure DNS fails on .works domain

When Secure DNS is turned on and set to use anything other than OS default, .works domain cannot be resolved and returns ERR_NAME_NOT_RESOLVED.
Example: https://howhttps.works/
I'm not sure if this issue is specific to UG, but I cannot reproduce it on Chrome.

Have you tried to reproduce the problem on Linux?

Have you tried to reproduce the problem on Linux?

Can reproduce it on Linux.

Thank you, right as I was about to install a VM 😀

Do you want to move this issue to the core repo?

We could've just moved the issue there…

We could've just moved the issue there…

Ah I didn't know the issue could be literally moved. Shall I close the issue in the core repo?


build: fix android build

https://ci.nodejs.org/job/libuv-test-commit/1623/

Landed in 780c08a6...f9618443. Thanks!


PTZ Zoom Definition Conflicts

If PTZ with zoom is defined on one camera in a view and another camera in the same view is PTZ with no zoom the zoom icons do not appear on the custom:webrtc-camera card with the zoom.
custom:webrtc-camera card code for PTZ with zoom:
    entity_id: camera.barn
    pan: LEFT
  data_right:
    entity_id: camera.barn
    pan: RIGHT
  data_up:
    entity_id: camera.barn
    tilt: UP
  data_down:
    entity_id: camera.barn
    tilt: DOWN
  data_zoom_in:
    entity_id: camera.barn
    zoom: ZOOM_IN
  data_zoom_out:
    entity_id: camera.barn
    zoom: ZOOM_OUT

custom:webrtc-camera card code for PTZ without zoom:
ptz:
  service: switch.turn_on
  data_left:
    entity_id:
      - switch.dining_room_camera_pan_left
  data_right:
    entity_id:
      - switch.dining_room_camera_pan_right
  data_up:
    entity_id:
      - switch.dining_room_camera_tilt_up
  data_down:
    entity_id:
      - switch.dining_room_camera_tilt_down

Same problem with the latest version of v3.1.0


chore: bdd-nh-1585745255 to 0.0.1

chore: Promote bdd-nh-1585745255 to version 0.0.1

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

Needs approval from an approver in each of these files:

OWNERS

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


Added retry block request

@Ross-Kitsis I saw some invalid block number errors that were actually issues with fetching the block (slots 6349005 and 6343891 on staging). I've added a retry loop on the previous slot to hopefully rule out node issues before moving onto older slots. I'm happy to change it if you have other ideas on how to deal with it.

@Ross-Kitsis Can you merge? I don't have the permissions to do it myself


Rename NewClient to NewHTTPClient

Thanks @gobwas -- but we may have to close this.
@sparrc -- can you chime in?

This is fine, that's actually the README

@otoolep  I think we can merge this, @gunnaraasen may have already changed this though

Ha! So it is, it's only the README.
@gobwas -- have you signed the CLA?

@otoolep yes.


fix linting for svg update w/signoff

Notes for Reviewers
This PR fixes #
Signed commits

[ ] Yes, I signed my commits.

@MUzairS15 //


EAS updates are not available when downloading the app after update was published

Build/Submit details page URL
No response
Summary
some context:

I use an Adhoc build
I have the app installed on my Iphone
My friend doesn’t have the app install on his Iphone
We both have our devices setuped with the distribution profile installed correctly.
I made an eas update on my expo app and everything went fine and got the update on my device.

After the eas update, my friend downloaded the app, but didn’t have the update on his app.
Is this the expected behavior or eas updates?
Managed or bare?
managed
Environment
expo-env-info 1.0.5 environment info:
System:
OS: macOS 13.4
Shell: 5.9 - /bin/zsh
Binaries:
Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.4, iOS 16.4, macOS 13.3, tvOS 16.4, watchOS 9.4
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9014738
Xcode: 14.3.1/14E300c - /usr/bin/xcodebuild
npmPackages:
@expo/metro-config: ^0.10.6 => 0.10.7
expo: ^49.0.5 => 49.0.7
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.72.3 => 0.72.3
react-native-web: ~0.19.6 => 0.19.7
npmGlobalPackages:
eas-cli: 3.16.0
expo-cli: 6.3.10
Expo Workflow: managed
✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK
Didn't find any issues with the project!
Error output

Reproducible demo or steps to reproduce from a blank project

Build an app
Push an eas update
Download the app and the update is not available.

Hello,
Did you find a solution ? Changing runtime policy with appVersion or nativeVersion ?

Hello,  i just try with
    "runtimeVersion": {       "policy": "appVersion"     }
And it seems to work

@pCyril Super long delay sorry, no i didnt find a solution. Not sure if this is intended or not..

@pCyril Thanks, ill try this right now. I was still using "runtimeVersion": { "policy": "sdkVersion" } but i didnt saw it was deprecated anyway.

@pCyril I was wrong its now working with appVersion. The thing is that when i first download and open the app, the fix is not there. If i close the app and reopen it, i can see the fix. Not sure why just after downloading the app the fix are not picked up tho.

It still happens to me, I have to add an update when the app is installed for it to work.

@christian1koch I noticed that sometimes you just need to close and reopen the app to see the update.

@christian1koch I noticed that sometimes you just need to close and reopen the app to see the update.

Yeah that fixes it but... it shouldn't be like that right? It should load the update on first load not on the second or third, which doesn't avoid that a user runs into i.e a bug that you already bug fixed through eas update...
I believe this issue should be reopened and addressed properly.

We have the same issue, the updates are not applied on first load, but the second/third. Makes the entire system a bit pointless if you can just reinstall to exploit a potential bug that was fixed through updates...


Dataverse connector: alternate keys

Been 4 years since I've been waiting for alternate key support during the copy data activity.
This is really a critical missing feature in the connector.
Reference: #57237

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

ID: 304d4c46-c0ac-05c9-15eb-d8b677ec5e90
Version Independent ID: 36a79d36-2b72-2722-68e5-e167f9a2cd41
Content: Copy and transform data in Dynamics 365 (Microsoft Dataverse) or Dynamics CRM - Azure Data Factory & Azure Synapse
Content Source: articles/data-factory/connector-dynamics-crm-office-365.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @jianleishen
Microsoft Alias: jianleishen

@mathiasbl
Thanks for your feedback! We will investigate and update as appropriate.

Hi @mathiasbl, and thanks for your question. This forum specifically is for feedback on the documentation itself, but I did search the product idea forum for ADF and found what I think was a similar issue, where a member of the product team responded confirming the suggestion should be posted in the PowerApps feedback forum, since that is the team that would control the feature. I searched there and did find the most upvoted feature that appears to match. You can upvote that one, or if it isn't exactly describing the same thing, you can submit a new suggestion there too. Since this doesn't relate to the ADF documentation unless the PowerApps team implements the feature first, I will go ahead and close this issue now.
#please-close


it seems to be not possible to create a new project with the current schematics version

Environment
Provide the content of the package.json file in the project:
Describe the bug
As I am trying to migrate a schematics project to NS7 I tried to generate a new NS7 project with the current schematics. The new project unfortunately does not build after creation. I would expect that a empty default project runs out of the box when generated
To Reproduce
ng new --collection=@nativescript/schematics testapp --prefix ns  --style scss
Expected behavior
creates a new project which can be run with  ns run ios --emulator --no-hmr --env.aot
Additional context
in tsconfig.json "baseUrl": ".", is missing. When I add it I end up with the next compilation error
cp: no such file or directory: PATH_TO_APP/testapp/App_Resources/iOS/*

Hello @NathanWalker, as I don't know of which priority this bug currently is for you, I am wondering, if you somewhere might have a demo project available which has a running configuration of an schematics NS7 and Angular 10 project with working SCSS support (without shared webapp), like the one I tried to generate with the above mentioned command? I am still trying to migrate my project without success. I hope a reference project will help me to figure out what is missing. If you could share a link to such a project that would be great and would probably also help others who stumble in the same situation. Thanks a lot!
Best regards,
Christoph

@cjohn001 thanks for ping - I'm circling back here on Tuesday to see if can assist. I'll be honest I don't use these schematics myself (we use https://github.com/nstudio/xplat which accomplishes same thing) and I have been shakey on how much we want to continue supporting these. They require a lot of build hand holding that other approaches don't and most likely is the reason for your troubles.
But I know people have invested in these schematics and don't want to leave them hangling; like yourself. So will see what can be done.

Hello @NathanWalker, when trying to rebuild a minimum example for our discussion, I realized that I actually have not used schematics either to generate my project. It was only build with tns create -> Angular and than I added node-sass. I will come back on you when I managed to prepare a reference example showing the same sass errors.

Hello @NathanWalker , I have now got a basic project structure working and will now be going to add sources from my project till things brake. Could be that it takes a while till I come back on you. Seems like I have something from which I can start of now :) Thanks for your help.

@cjohn001 thanks for update - If you run into trouble ping me on Slack and we can try to hop on Zoom together to gain more clarity.

@NathanWalker, thank you very much for the offer, I will use this chance in case I cannot resolve it.


close and open source

Added the Script for open vs close source

Hi @ElizabethN are you free to review this Script?


Improve iDeep version checking

Improve documentation and environment check for ideep (see #5592).

Is it ok to backport >=2.0.0.post3, which will require updating ideep4py if an older version is installed?

Ok, I'll make a separate PR for v4 (which requires >=2.0.0.post1).

for v4

for v5
Jenkins, test this please.

Ah, I noticed that _optional_dependencies was finally not backported to v5. Anyway I'll send separate PR for docs to v5.

Jenkins CI test (for commit a9c2dfa73b3a0be5ff712cd49bd206f4db2bf0cc, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)

The Jenkins failures are unrelated to the PR.


time inject node throws error

After using the latest RedMatic version with latest node-red-contrib-sun-position I am getting the following error in the time inject node:
homematic-raspi daemon.err node-red: getFormattedDateOut date=[object Object] --> format=7  [time-comp.days] - [time-comp.month] [time-comp.dayDiffNames]
homematic-raspi daemon.err node-red[835]: [time-inject:3e2a72f0.04e0be] date.getTime is not a function

Time inject configuration:

I have checked, but I does not get this error. May be you have an other configuration.
Could you please select your time-inject node, export it and coy it here?

[{"id":"fc673fd0.076ee","type":"time-inject","z":"c5ce6edb.7a21","name":"","positionConfig":"8dc5e6c6.592b98","payload":"true","payloadType":"bool","payloadTimeFormat":"0","payloadOffset":"","payloadOffsetType":"none","payloadOffsetMultiplier":60000,"topic":"","time":"sunset","timeType":"pdsTime","timeDays":"*","offset":"","offsetType":"none","offsetMultiplier":60000,"property":"","propertyType":"none","timeAlt":"","timeAltType":"entered","timeAltOffset":0,"timeAltOffsetType":"none","timeAltOffsetMultiplier":60000,"once":false,"onceDelay":0.1,"addPayload1":"on_time","addPayload1Type":"msg","addPayload1Value":"23:00","addPayload1ValueType":"entered","addPayload1Format":"7","addPayload1Offset":"","addPayload1OffsetType":"none","addPayload1OffsetMultiplier":60000,"addPayload1Days":"*","addPayload2":"","addPayload2Type":"none","addPayload2Value":"23:00","addPayload2ValueType":"entered","addPayload2Format":"0","addPayload2Offset":"","addPayload2OffsetType":"none","addPayload2OffsetMultiplier":60000,"addPayload2Days":"*","addPayload3":"","addPayload3Type":"none","addPayload3Value":"","addPayload3ValueType":"date","addPayload3Format":"0","addPayload3Offset":"","addPayload3OffsetType":"none","addPayload3OffsetMultiplier":60000,"addPayload3Days":"*","recalcTime":2,"x":130,"y":100,"wires":[["e4484294.1f6a5","8ebc9dcb.6eba7"]]},{"id":"8dc5e6c6.592b98","type":"position-config","z":"","name":"Zuhause","isValide":"true","longitude":"0","latitude":"0","angleType":"deg","timezoneOffset":"1"}]

Sorry, I can't reproduce the specific problem in my test Environment with Version 0.2.2. (I remember, however, having seen and eliminated this bug in the earlier version).
Regardless of that, I found 2 other bugs.
Could you please install version 0.2.4 and check if your problem still exists with this Version?
(The version 0.2.4  should be available in a short time.)

With 0.2.3 and as well with 0.2.4 the error in my system is gone. All working as expected. Thanks a lot for the fast support.

seems to be fixed with 0.2.4


use greenlets to threebot listing

Description

use greenlets to threebot listing, it will reduce the listing time a lot

Related Issues

https://github.com/threefoldtech/js-sdk/issues/2207

Checklist

[ ] Pre-commit hook is installed to do formatting checks before committing code...etc
[ ] Tests included
[ ] Build pass
[ ] Documentation
[ ] Code format and docstrings

Codecov Report

Merging #2218 (a422333) into development (686f860) will decrease coverage by 0.00%.
The diff coverage is 18.18%.

@@               Coverage Diff               @@
##           development    #2218      +/-   ##
===============================================
- Coverage        32.63%   32.63%   -0.01%
===============================================
  Files              136      136
  Lines            13313    13320       +7
===============================================
+ Hits              4345     4347       +2
- Misses            8968     8973       +5

Impacted Files
Coverage Δ

...mpscale/packages/threebot_deployer/bottle/utils.py
10.63% <18.18%> (+0.45%)
:arrow_up:

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 686f860...a422333. Read the comment docs.

Codecov Report

Merging #2218 (a422333) into development (686f860) will decrease coverage by 0.00%.
The diff coverage is 18.18%.

@@               Coverage Diff               @@
##           development    #2218      +/-   ##
===============================================
- Coverage        32.63%   32.63%   -0.01%
===============================================
  Files              136      136
  Lines            13313    13320       +7
===============================================
+ Hits              4345     4347       +2
- Misses            8968     8973       +5

Impacted Files
Coverage Δ

...mpscale/packages/threebot_deployer/bottle/utils.py
10.63% <18.18%> (+0.45%)
:arrow_up:

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 686f860...a422333. Read the comment docs.