debugging doesnt work as expected

I want to debug my atmega328p project. I configured platformio.ini to use avr-stub according to the docs: https://docs.platformio.org/en/latest/plus/debug-tools/avr-stub.html#debugging-tool-avr-stub
I set my breakpoint using nvim-dap's default mapping and used Piodebug to debug, but all I am seeing is this in toggleterm:
Processing nanoatmega328 (platform: atmelavr; board: nanoatmega328; framework: arduino)
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/atmelavr/nanoatmega328.html
PLATFORM: Atmel AVR (5.1.0) > Arduino Nano ATmega328
HARDWARE: ATMEGA328P 16MHz, 2KB RAM, 30KB Flash
DEBUG: Current (avr-stub) External (avr-stub, simavr)
PACKAGES:
 - framework-arduino-avr @ 5.2.0
 - toolchain-atmelavr @ 1.70300.191015 (7.3.0)
Warning! `COMPILATIONDB_INCLUDE_TOOLCHAIN` is scoping
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 6 compatible libraries
Scanning dependencies...
Dependency Graph
|-- avr-debugger @ 1.4.0
Warning! `COMPILATIONDB_INCLUDE_TOOLCHAIN` is scoping
Building in release mode
Building compilation database .pio/build/nanoatmega328/compile_commands.json
=========================================================================================================================== [SUCCESS] Took 0.32 seconds ===========================================================================================================================
.
.
Please Press ENTER to continue

[Process exited 0]

It seems like everything is executing as it should, because there are no errors, but this gives me no debugging functionality as is. Am I doing something wrong?

This is what you probably should get:
reparing firmware for debugging...
Processing nanoatmega328 (platform: atmelavr; board: nanoatmega328; framework: arduino)
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Verbose mode can be enabled via `-v, --verbose` option
CONFIGURATION: https://docs.platformio.org/page/boards/atmelavr/nanoatmega328.html
PLATFORM: Atmel AVR (5.1.0) > Arduino Nano ATmega328
HARDWARE: ATMEGA328P 16MHz, 2KB RAM, 30KB Flash
DEBUG: Current (avr-stub) External (avr-stub, simavr)
PACKAGES:
 - framework-arduino-avr @ 5.2.0
 - tool-avrdude @ 1.60300.200527 (6.3.0)
 - toolchain-atmelavr @ 1.70300.191015 (7.3.0)
LDF: Library Dependency Finder -> https://bit.ly/configure-pio-ldf
LDF Modes: Finder ~ chain, Compatibility ~ soft
Found 6 compatible libraries
Scanning dependencies...
Dependency Graph
|-- avr-debugger @ 1.4.0
Building in debug mode
Checking size .pio/build/nanoatmega328/firmware.elf
Advanced Memory Usage is available via "PlatformIO Home > Project Inspect"
RAM:   [==        ]  15.5% (used 317 bytes from 2048 bytes)
Flash: [==        ]  19.7% (used 6062 bytes from 30720 bytes)
Configuring upload protocol...
AVAILABLE: arduino
CURRENT: upload_protocol = arduino
Looking for upload port...
Auto-detected: /dev/ttyUSB0
Uploading .pio/build/nanoatmega328/firmware.hex

avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e950f (probably m328p)
avrdude: reading input file ".pio/build/nanoatmega328/firmware.hex"
avrdude: writing flash (6062 bytes):

Writing | ################################################## | 100% 1.56s

avrdude: 6062 bytes of flash written
avrdude: verifying flash memory against .pio/build/nanoatmega328/firmware.hex:
avrdude: load data flash data from input file .pio/build/nanoatmega328/firmware.hex:
avrdude: input file .pio/build/nanoatmega328/firmware.hex contains 6062 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 1.38s

avrdude: verifying ...
avrdude: 6062 bytes of flash verified

avrdude: safemode: Fuses OK (E:00, H:00, L:00)

avrdude done.  Thank you.

===================================================================================================================================== [SUCCESS] Took 4.66 seconds =====================================================================================================================================
Reading symbols from /home/uname/Documents/programming/lightsensor/arduino/.pio/build/nanoatmega328/firmware.elf...done.
(gdb)


[Feature] Add schema and type ref to flow action

WHY are these changes introduced?

Ticket

WHAT is this pull request doing?

Adds return type ref and schema as optional fields to the Flow action extension

How to test your changes?

Create a Flow action extension in spin, check the resulting extension config in partners

Post-release steps

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[ ] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

/shipit


GN build parity: esp32 platform

The GN build needs support for esp32 platform for parity with automake.

note to whomever does this: please update .vscode/tasks.json


TensorRT engine requires consistent batch size

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes, custom SSD model
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 16.04
TensorFlow installed from (source or binary): nvidia gpu cloud docker container 18.04 for V100
from source for 1080 Ti
TensorFlow version (use command below): 1.7.0
Python version: 2.7
Bazel version (if compiling from source): 0.11.1
GCC/Compiler version (if compiling from source): 5.4.0
CUDA/cuDNN version: 9 / 7
GPU model and memory: V100 (16GB) 1080Ti (11GB)
Exact command to reproduce: N/A

Source code / logs
Run TF-TRT with custom SSD and got the following message:
F tensorflow/contrib/tensorrt/shape_fn/trt_shfn.cc:52] TensorRT engine requires consistent batch size
After commenting out the line 52 in trt_shfn.cc and recompile with bazel, the model ran properly and output expected results. Suspect that this dimension check has a bug and does not cover all the cases.
Use the code example from here and modify to load custom SSD model.

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Exact command to reproduce

Just update the field. Thanks!

/CC @aaroey

@samikama

The error there seems to be a little more restrictive than it is. An engine can run a smaller batch size than it is built for, but with less efficiency than it could if it was built for that batch size. However it can not run a batch size bigger than it is built for so it is not really wrong. We are going to change these code soon for other reasons and I will update the logic there then.

Nagging Assignee @aaroey: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

With #19871 we have less dependence on to the batch size and will be able to create a new engine on the fly at the expense of compute time.

Nagging Assignee @samikama: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @samikama: It has been 29 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

This should be fixed with recent updates, #20350 specifically.


Check tls handshake errors

Was looking into why our nats cluster was logging occasional client side tls handshake errors, and noticed tls handshake errors in this client were being ignored.

Coverage increased (+0.07%) to 93.073% when pulling 1af890482fe2ccd6195f077462191a526feb8cbe on brianshannan:tls_handshake_error into aa1eeb09b71e271bfc2027dabe5c7a90ad37a50f on nats-io:master.


CDU management profile and specification

Proposal for Redfish requirements for a CDU.
Still need to provide a Markdown file for a specification that describes this in text.

I expect a new baseline for Cooling Equipment to exist at some point which will be inherited by this. Refer to column D in this: https://docs.google.com/spreadsheets/d/1XP0wLm1oMLiDfpaf5FXuIATc3lkqokq9Gr05OYNDSEE/edit#gid=0

I expect a new baseline for Cooling Equipment to exist at some point which will be inherited by this. Refer to column D in this: https://docs.google.com/spreadsheets/d/1XP0wLm1oMLiDfpaf5FXuIATc3lkqokq9Gr05OYNDSEE/edit#gid=0

Do you specifically mean that you want to break down the profiles a bit to maximize reuse? So, have one common cooling baseline, and then have the CDU profile inherit from that?

For "Infra Baseline", would it be restricted to "cooling infra"? I think supporting power infra in a common infra baseline would be difficult.

Yeah that’s the scope. I misspoke and it should be ‘cooling infra’.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Mike Raineri @.>
Sent: Saturday, March 23, 2024 12:15:11 AM
To: opencomputeproject/HWMgmt-OCP-Profiles @.>
Cc: Jones, Mick Bruce @.>; Comment @.>
Subject: Re: [opencomputeproject/HWMgmt-OCP-Profiles] CDU management profile and specification (PR #67)
CAUTION: This email originated from outside of Vertiv. Do not click links or open attachments unless you recognize the sender and know the content is safe.
For "Infra Baseline", would it be restricted to "cooling infra"? I think supporting power infra in a common infra baseline would be difficult.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/opencomputeproject/HWMgmt-OCP-Profiles/pull/67*issuecomment-2015078880__;Iw!!C8PT2x6w!ur_53Shaps0XxqjeKRnHkJNcdAaOJoE_xOT5MWTEWM5YKsRZ6KkRfppo8SA64V90cyY4ZkMYU7EEfNc37F_OnSJ_i9IZ5w$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/ATFDC52OQGX2OTPWWAFTAQ3YZQVF7AVCNFSM6AAAAABDEYNCUOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGA3TQOBYGA__;!!C8PT2x6w!ur_53Shaps0XxqjeKRnHkJNcdAaOJoE_xOT5MWTEWM5YKsRZ6KkRfppo8SA64V90cyY4ZkMYU7EEfNc37F_OnSL8Dm1E9g$.
You are receiving this because you commented.Message ID: @.***>
CONFIDENTIALITY NOTICE: This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed and may contain confidential and privileged information protected by law. If you received this e-mail in error, any review, use, dissemination, distribution, or copying of the e-mail is strictly prohibited. Please notify the sender immediately by return e-mail and delete all copies from your system.

Hi Mike, I did a PR against your fork/branch which contains changes from review with OCP HMLC community for the CDU profile. We can run this revised profile against our revised public-cooling-unit mockup cleanly.
If it makes it easier I have attached the changed file here as it may be easier to do a diff locally and push to your fork instead of trying to resolve changes from my PR.
OCPCoolantDistributionUnitManagement.v0_9_0.json

In LiquidCooling\OCPLiquidCoolingBaseline.v0_9_0.json the substitution variable {CoolingUnitType} does not work in Interop Validator because the regex is looking for an entry ending with "Id". I've fixed this by replacing all occurrences of CoolingUnitType with CoolingUnitTypeId in this profile.

In LiquidCooling\OCPLiquidCoolingBaseline.v0_9_0.json the substitution variable {CoolingUnitType} does not work in Interop Validator because the regex is looking for an entry ending with "Id". I've fixed this by replacing all occurrences of CoolingUnitType with CoolingUnitTypeId in this profile.

Got it; changed it. We might want to see if this is something we should push into the interop validator to better handle.


Fix: edit-mode unit tests that require GPU support when running in env windows or OSX fail

According to readme, GPU is not supported in windows or OSX.  However, there are unit tests that will run automatically when using Unity Test Runner that assume GPU is supported.  These tests will fail and can interfere with CI/CD.
Potential fix is to simply ignore test classes in the "Tests/EditorMode/Gpu" directory when the detected environment is editor inside windows or OSX.

Even with Linux, there are environments that do not support GPUs (and when the library is built by running build.py --desktop cpu), so I think it's a good idea to specify the testCategory when running tests.
https://github.com/homuler/MediaPipeUnityPlugin/blob/77d0f1628cd9fa991b8846202ade9dc531b50487/.github/workflows/macos-test.yml#L118
https://github.com/homuler/MediaPipeUnityPlugin/blob/77d0f1628cd9fa991b8846202ade9dc531b50487/.github/workflows/windows-test.yml#L141


Missing TypeScript declaration file

Version
3.x.x (Vue 3.x)
Describe the bug
I'm not being able to make the typings work on .ts files, the following errors are being shown:
Visual Studio Code 1.62.0:
"Could not find a declaration file for module<EMAIL_ADDRESS>
IntelliJ IDEA 2021.2:
TS2307: Cannot find module '@asigloo/vue-dynamic-forms/dist' or its corresponding type declarations.

Using npm run serve command (on a new scaffolded vue project):
TS7016: Could not find a declaration file for module '@asigloo/vue-dynamic-forms'. <EMAIL_ADDRESS>implicitly has an 'any' type.
  Try `npm i --save-dev @types/asigloo__vue-dynamic-forms` if it exists or add a new declaration (.d.ts) file containing `declare module '@asigloo/vue-dynamic-forms';`

Describe the bug

Scaffold a new Vue 3 project with Vue CLI: vue create hello-world with TypeScript feature
Run npm install @asigloo/vue-dynamic-forms.
Create a main.ts file if not exist.
Add import { createDynamicForms } from '@asigloo/vue-dynamic-forms' to main.ts file.

Expected behavior
The IDE can recognize the typings of imported modules from @asigloo/vue-dynamic-forms on TypeScript files.
System Info
System:
    OS: Windows 10 10.0.19043
    CPU: (16) x64 AMD Ryzen 7 2700 Eight-Core Processor
    Memory: 14.66 GB / 31.93 GB
  Binaries:
    Node: 14.15.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.10 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 95.0.4638.69
    Edge: Spartan (44.19041.1266.0), Chromium (95.0.1020.44)
    Internet Explorer: 11.0.19041.1202
  npmPackages:
    @asigloo/vue-dynamic-forms: ^3.18.0 => 3.18.0

Additional context
No response
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

FWIW, I was seeing this until I add declarations to my main.ts as described in https://github.com/asigloo/vue-dynamic-forms/issues/235, as well as the "failed to resolve component" described in the ticket.

Figure I should add the specific changes to main.ts that I'm referring to.
import { createDynamicForms } from '@asigloo/vue-dynamic-forms';
const VueDynamicForms = createDynamicForms({});
app.use(VueDynamicForms);

Actually...scratch that. The error did disappear, but it's showing up again after reopening the project. Must have just been a fluke.

I am still getting this. Any update?

Actually...scratch that. The error did disappear, but it's showing up again after reopening the project. Must have just been a fluke.

how did you exactly solve this? I can't compile it because it screams for TS declarations. I am unable to find them

please publish your typescript .d.ts  use run build:tsd.


Delete Node in BST added

Hey @Pratik-Shrivastava  thanks for your contribution ❗. Keep up the good job and leave a star if you liked the repo .
Happy hacking 😉


Bring back the resize function for the left sidebar

In v2.5x there is and option to increase the width of the left sidebar.
The current preview v3 doesn't allow this. :-(
I assume this could be related to one of these changes https://github.com/openstreetmap/iD/issues/6461, https://github.com/openstreetmap/iD/issues/6468 or https://github.com/openstreetmap/iD/issues/6119 .

For me, it's letting me do it as usual.

@sun-geo What browser are you using? It's working on Safari.

Scratch that, it's not working on Safari. I must have broken it today.

I must have had some old javascript cached in the tab, since it's not working for me anymore.

Thanks for fixing!


Expand_grid refactor

PR Description
Please describe the changes proposed in the pull request:

Use numpy's mgrid to create cartesian product
Dtypes preserved - This includes pandas extension type arrays (categoricals, nullable integers, ...)
Dispatch method employed for different instances.
Much faster output for expand_grid. Performance penalty for small datasets (less than 10 rows).
SIgnificant performance gains as the dataset grows.

Speed Tests Comparison:
Dev :

In [1]: import pandas as pd; import numpy as np; import janitor

In [2]: %timeit janitor.expand_grid(others = {"x":np.arange(4), "y": np.arange(3)})
418 µs ± 5.95 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [3]: %timeit janitor.expand_grid(others = {"x":np.arange(10), "y": np.arange(20)})
802 µs ± 15.6 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [4]: %timeit janitor.expand_grid(others = {"x":np.arange(100), "y": np.arange(200)})
43.4 ms ± 902 µs per loop (mean ± std. dev. of 7 runs, 10 loops each)

PR:
In [1]: import pandas as pd; import numpy as np; import janitor

In [2]: %timeit janitor.expand_grid(others = {"x":np.arange(4), "y": np.arange(3)})
794 µs ± 39.9 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [3]: %timeit janitor.expand_grid(others = {"x":np.arange(10), "y": np.arange(20)})
798 µs ± 34.9 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

In [4]: %timeit janitor.expand_grid(others = {"x":np.arange(100), "y": np.arange(200)})
940 µs ± 7.09 µs per loop (mean ± std. dev. of 7 runs, 1000 loops each)

This PR improves the expand_grid function.
Please ensure that you have done the following:

[x] PR in from a fork off your branch. Do not PR from <your_username>:dev, but rather from <your_username>:<feature-branch_name>.

[x] If you're not on the contributors list, add yourself to AUTHORS.rst.

[x] Add a line to CHANGELOG.md under the latest version header (i.e. the one that is "on deck") describing the contribution.

Do use some discretion here; if there are multiple PRs that are related, keep them in a single line.

Quick Check
To do a very quick check that everything is correct, follow these steps below:

[x] Run the command make check from pyjanitor's top-level directory. This will automatically run:

black formatting
flake8 checking
running the test suite
docs build

Once done, please check off the check-box above.
If make check does not work for you, you can execute the commands listed in the Makefile individually.
Code Changes

If you are adding code changes, please ensure the following:

[x] Ensure that you have added tests.
[x] Run all tests ($ pytest .) locally on your machine.

[ ] Check to ensure that test coverage covers the lines of code that you have added.
[ ] Ensure that all tests pass.

Documentation Changes

If you are adding documentation changes, please ensure the following:

[x] Build the docs locally.
[x] View the docs to check that it renders correctly.

Relevant Reviewers

Please tag maintainers to review.

@ericmjl

Wonderful, thanks @samukweku!


Arcs Circular Dependencies

There are probably more, but these ones were quickly found:
madge --circular .
Processed 1311 files (20.4s) (105 warnings)
✖ Found 12 circular dependencies!

runtime/recipe/type-checker.js > runtime/ts-build/type.js
runtime/ts-build/type.js > runtime/ts-build/schema.js > runtime/entity.js
runtime/ts-build/type.js > runtime/ts-build/schema.js
runtime/recipe/type-checker.js > runtime/ts-build/type.js > runtime/ts-build/shape.js
runtime/ts-build/type.js > runtime/ts-build/shape.js
runtime/ts-build/type.js > runtime/tuple-fields.js
runtime/ts-build/type.js > runtime/type-variable.js
runtime/manifest.js > runtime/ts-build/storage/storage-provider-factory.js > runtime/ts-build/storage/synthetic-storage.js
runtime/handle.js > runtime/ts-build/reference.js
runtime/arc.js > runtime/recipe-index.js
runtime/ts-build/hosted-slot-consumer.js > runtime/ts-build/hosted-slot-context.js
shell/components/data-explorer.js > shell/components/data-item.js

Would be interested in a discussion of whether this is an short-term or long-term issue; for example, types are circular because they are recursive (i.e. a type can be a type variable that can contain a resolved type). Trying to fix this issue is going to complexify the code; is it worth doing anything soon or something that can be saved for the next type system refactor?

Circular dependencies aren't a problem within modules, but certainly are across module boundaries. As I look at where to draw module boundaries in detail, I'll consult (or regenerate) this list. First I'll get up to speed on madge.

I've installed madge and tried this for myself:
madge --circular .
Processed 918 files (12.5s) (69 warnings)
✖ Found 13 circular dependencies!

build/runtime/recipe/type-checker.js > build/runtime/type.js > build/runtime/interface-info.js
build/runtime/type.js > build/runtime/interface-info.js
build/runtime/recipe/type-checker.js > build/runtime/type.js
build/runtime/recipe/type-checker.js > build/runtime/type.js > build/runtime/schema.js
build/runtime/particle-spec.js > build/runtime/recipe/type-checker.js > build/runtime/type.js > build/runtime/schema.js > build/runtime/reference.js > build/runtime/handle.js
build/runtime/reference.js > build/runtime/handle.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/reference.js > build/runtime/handle.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/reference.js
build/runtime/type.js > build/runtime/schema.js
build/runtime/type.js > build/runtime/type-variable-info.js
build/runtime/manifest.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/synthetic-storage.js
build/runtime/hosted-slot-consumer.js > build/runtime/hosted-slot-context.js
modalities/dom/components/elements/data-explorer.js > modalities/dom/components/elements/data-item.js

None of these look particularly problematic to me, as they all remain within the module I intend to put them in.
I'm going to lower the priority on this but leave it open and assigned to me, just as a reminder to occasionally check this. Feel free to comment and up the priority if you see something that looks serious.

madge needs updating to deal with our current code base. Version 3.4.4 gives the following output. None of these look serious, as they all remain within their modules.
$ madge -c .
Processed 1988 files (26.8s) (96 warnings)
✖ Found 42 circular dependencies!

build/runtime/interface-info.js > build/runtime/recipe/type-checker.js > build/runtime/type.js
build/runtime/recipe/type-checker.js > build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js
build/runtime/entity.js > build/runtime/reference.js
build/runtime/entity.js > build/runtime/reference.js > build/runtime/handle.js
build/runtime/particle-spec.js > build/runtime/particle-check.js
build/runtime/recipe/type-checker.js > build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js > build/runtime/reference.js > build/runtime/handle.js > build/runtime/particle-spec.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js > build/runtime/reference.js > build/runtime/handle.js > build/runtime/particle-spec.js
build/runtime/reference.js > build/runtime/handle.js
build/runtime/handle.js > build/runtime/storage-proxy.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js > build/runtime/reference.js > build/runtime/handle.js > build/runtime/storage-proxy.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js > build/runtime/reference.js > build/runtime/handle.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js > build/runtime/reference.js
build/runtime/type.js > build/runtime/schema.js > build/runtime/entity.js
build/runtime/type.js > build/runtime/schema.js
build/runtime/type.js > build/runtime/type-variable-info.js
build/runtime/recipe/handle.js > build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js
build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js > build/runtime/recipe/handle-connection.js > build/runtime/recipe/recipe-util.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js > build/runtime/recipe/handle-connection.js
build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/slot.js
build/runtime/manifest.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/synthetic-storage.js
build/runtime/manifest.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/volatile-storage.js > build/runtime/runtime.js > build/runtime/arc.js
build/runtime/manifest.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/volatile-storage.js > build/runtime/runtime.js > build/runtime/arc.js > build/runtime/particle-execution-host.js
build/runtime/storage/storage-provider-factory.js > build/runtime/storage/volatile-storage.js > build/runtime/runtime.js > build/runtime/arc.js
build/runtime/manifest.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/volatile-storage.js > build/runtime/runtime.js
build/runtime/runtime.js > build/runtime/testing/fake-slot-composer.js > build/runtime/modality-handler.js > build/runtime/headless-slot-dom-consumer.js > build/runtime/slot-dom-consumer.js
devtools/deps/moment/src/lib/create/check-overflow.js > devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js
devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-array.js > devtools/deps/moment/src/lib/create/local.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-array.js > devtools/deps/moment/src/lib/units/week-calendar-utils.js > devtools/deps/moment/src/lib/units/year.js > devtools/deps/moment/src/lib/moment/get-set.js
devtools/deps/moment/src/lib/units/year.js > devtools/deps/moment/src/lib/moment/get-set.js
devtools/deps/moment/src/lib/create/check-overflow.js > devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js
devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js
devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js > devtools/deps/moment/src/lib/units/day-of-week.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js
devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/valid.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/locale/locales.js > devtools/deps/moment/src/lib/locale/base-config.js
devtools/deps/moment/src/lib/duration/constructor.js > devtools/deps/moment/src/lib/duration/valid.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/duration/constructor.js > devtools/deps/moment/src/lib/duration/valid.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/units/offset.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/units/offset.js > devtools/deps/moment/src/lib/moment/add-subtract.js
modalities/dom/components/elements/data-explorer.js > modalities/dom/components/elements/data-item.js

@raulverag this can be closed now, right? :)

Well, madge still finds the following. Clearly the webpack plugin we used has limitations at best or just doesn't work at worst. Damn.
$ madge --circular .
Processed 2086 files (30.7s) (93 warnings)
✖ Found 30 circular dependencies!

build/runtime/recipe/handle.js > build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js
build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js > build/runtime/recipe/handle-connection.js > build/runtime/recipe/recipe-util.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js > build/runtime/recipe/handle-connection.js
build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/particle.js
build/runtime/recipe/slot-connection.js > build/runtime/recipe/recipe.js > build/runtime/recipe/slot.js
build/runtime/manifest.js > build/runtime/runtime.js > build/runtime/arc.js
build/runtime/manifest.js > build/runtime/runtime.js > build/runtime/arc.js > build/runtime/particle-execution-host.js
build/runtime/runtime.js > build/runtime/arc.js
build/runtime/manifest.js > build/runtime/runtime.js > build/runtime/arc.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/synthetic-storage.js
build/runtime/runtime.js > build/runtime/arc.js > build/runtime/storage/storage-provider-factory.js > build/runtime/storage/volatile-storage.js
build/runtime/manifest.js > build/runtime/runtime.js
build/runtime/runtime.js > build/runtime/testing/fake-slot-composer.js > build/runtime/modality-handler.js > build/runtime/headless-slot-dom-consumer.js > build/runtime/slot-dom-consumer.js
devtools/deps/moment/src/lib/create/check-overflow.js > devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js
devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-array.js > devtools/deps/moment/src/lib/create/local.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-array.js > devtools/deps/moment/src/lib/units/week-calendar-utils.js > devtools/deps/moment/src/lib/units/year.js > devtools/deps/moment/src/lib/moment/get-set.js
devtools/deps/moment/src/lib/units/year.js > devtools/deps/moment/src/lib/moment/get-set.js
devtools/deps/moment/src/lib/create/check-overflow.js > devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js
devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js
devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js > devtools/deps/moment/src/lib/units/day-of-week.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/from-string-and-format.js > devtools/deps/moment/src/lib/create/from-string.js
devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/create/from-string-and-array.js > devtools/deps/moment/src/lib/create/valid.js
devtools/deps/moment/src/lib/units/month.js > devtools/deps/moment/src/lib/create/utc.js > devtools/deps/moment/src/lib/create/from-anything.js > devtools/deps/moment/src/lib/locale/locales.js > devtools/deps/moment/src/lib/locale/base-config.js
devtools/deps/moment/src/lib/duration/constructor.js > devtools/deps/moment/src/lib/duration/valid.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/duration/constructor.js > devtools/deps/moment/src/lib/duration/valid.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/units/offset.js
devtools/deps/moment/src/lib/duration/create.js > devtools/deps/moment/src/lib/units/offset.js > devtools/deps/moment/src/lib/moment/add-subtract.js
modalities/dom/components/elements/data-explorer.js > modalities/dom/components/elements/data-item.js
server/dist/deployment/cloud.js > server/dist/deployment/gcp/gcp.js > server/dist/deployment/gcp/gcpdisk.js
server/dist/deployment/cloud.js > server/dist/deployment/gcp/gcp.js > server/dist/deployment/k18s/manager.js

Running from just within the build directory gives the following:
$ cd build
$ madge --circular .
Processed 481 files (3.1s) (3 warnings)
✖ Found 13 circular dependencies!

runtime/recipe/handle.js > runtime/recipe/slot-connection.js > runtime/recipe/recipe.js
runtime/recipe/recipe.js > runtime/recipe/particle.js > runtime/recipe/handle-connection.js > runtime/recipe/recipe-util.js
runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/particle.js > runtime/recipe/handle-connection.js
runtime/recipe/recipe.js > runtime/recipe/particle.js
runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/particle.js
runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/slot.js
runtime/manifest.js > runtime/runtime.js > runtime/arc.js
runtime/manifest.js > runtime/runtime.js > runtime/arc.js > runtime/particle-execution-host.js
runtime/runtime.js > runtime/arc.js
runtime/manifest.js > runtime/runtime.js > runtime/arc.js > runtime/storage/storage-provider-factory.js > runtime/storage/synthetic-storage.js
runtime/runtime.js > runtime/arc.js > runtime/storage/storage-provider-factory.js > runtime/storage/volatile-storage.js
runtime/manifest.js > runtime/runtime.js
runtime/runtime.js > runtime/testing/fake-slot-composer.js > runtime/modality-handler.js > runtime/headless-slot-dom-consumer.js > runtime/slot-dom-consumer.js

The first step, and it might be my last on this, is to add madge to our packages and a command, or flag, or lint step, to sigh.

Sigh now has a cycles command, which is invoked as part of lint. This runs madge in the build directory, as above.

Unassigning as I'm done.

The WIP PR above moves cycles from 11 to 8 (but I have not yet finished updating the tests).

Excitingly, we are down to only 6 remaining after #4360 lands, and #4359 aims to solve those.
1) runtime/recipe/handle.js > runtime/recipe/slot-connection.js > runtime/recipe/recipe.js
2) runtime/recipe/recipe.js > runtime/recipe/particle.js > runtime/recipe/handle-connection.js > runtime/recipe/recipe-util.js
3) runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/particle.js > runtime/recipe/handle-connection.js
4) runtime/recipe/recipe.js > runtime/recipe/particle.js
5) runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/particle.js
6) runtime/recipe/slot-connection.js > runtime/recipe/recipe.js > runtime/recipe/slot.js


Simplified code of Number.prototype.mod

Those are equal (verify at Wolfram Alpha: http://www.wolframalpha.com/input/?i=Simplify+((x+mod+n)+%2B+n)+mod+n ). Unless you were using some hack ^^.

Actually, those aren't equal as they won't work the same for negative numbers.


Add additional instructions for extension installation

R

reditorsupport.r
RDebugger.r-debugger

Python

ms-python.python
ms-toolsai.jupyter
ms-toolsai.jupyter-keymap

Quarto

quarto.quarto

General

analytic-signal.preview-pdf

No longer necessary since extensions seem to be installing properly


[SPARK-46993][SQL] Fix constant folding for session variables

What changes were proposed in this pull request?

Remove the unconditional Alias node generation when resolving a variable reference.
Why are the changes needed?

An Alias that is not at the top level of an expression blocks constant folding.
Constant folding in turn is a requirement for variables to be usable as an argument to numerous functions, such as from_json().
It also has performance implications.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing regression tests in sql-session-variables.sql, added a test to validate the fix.
Was this patch authored or co-authored using generative AI tooling?

No

seems the code style check failed

thanks, merging to master/3.5!


ng new logs a warning about entryComponents being deprecated

🐞 Bug report
Command (mark with an x)

[x] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?
Yes, the previous version in which this bug was not present was: v10.0.x
Description
When running ng new, a warning about entryComponents is logged
🔬 Minimal Reproduction
🔥 Exception or Error

> ng new entry-comp-warning --defaults
Option "entryComponent" is deprecated: Since version 9.0.0 with Ivy, entryComponents is no longer necessary.

Ivy Workspace:

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1001.0
@angular-devkit/core         10.1.0
@angular-devkit/schematics   10.1.0
@schematics/angular          10.1.0
@schematics/update           0.1001.0
rxjs                         6.6.2

Anything else relevant?
npx<EMAIL_ADDRESS>new entry-comp-warning --defaults does not raise this warning.

Ummm, this is an interesting one!

> npx<EMAIL_ADDRESS>new admin-console --strict true --routing true --style css
outputs zero warnings
> npx<EMAIL_ADDRESS>new admin-console --strict true --defaults true
spawns few warnings


Xcbeautify GitHub actions format

WIP https://github.com/tuist/xcbeautify/issues/38#issuecomment-1667451590

This is WIP for now, see the comment on the original PR above with respect to the output.

This is WIP for now, see the comment on the original PR above with respect to the output.

Sorry. I completely missed that! 😬

You didn't miss it, I hadn't finished that comment yet - just too fast 🙂

Ok, this is actually a great change - I just completely missed where this shows up. It's on the action overview screen:
https://github.com/SwiftPackageIndex/SwiftPackageIndex-Server/actions/runs/5782600018

and that entry is active and takes you to the test source.

Ok, this is actually a great change - I just completely missed where this shows up. It's on the action overview screen:

Ohh, this is great 👍👍👍👍👍


Simple way to connect Client to private Leshan Server

Hello there,
I don't have much experience with servers, so please forgive me for this basic question.
Issue:
I would like to test some features of my lwm2m client with my own leshan server. The client connects to the public leshan server (coaps://leshan.eclipseprojects.io:5684) without any issues. However, I don't know how I can get the client to connect to the server if I host it myself.
Setup:

Run server demo in Eclipse IDE on my local machine
defined port forwarding for UDP port 5684 on WiFi router
URL: coaps://publicIPv4:5684

Is it even possible to connect the client this way? Or do I need a gateway?
Thanks,
Kurt Simon

You should be able to connect to server locally running it in Eclipse IDE.
Did you try to use :

coaps://localhost:5684
OR  coaps://<IP_ADDRESS>:5684 ?

Thanks, but my client is not running on the same device. I want to connect to the server remotely.
My approach was that this works like with the HTTP server. After all it is possible to access the webapp from outside via http://puplicIPv4:8088 if the port forwarding is set for HTTP port 8088. I was hoping that this could also work for CoAP (if UDP port 5684 is forwarded).

My approach was that this works like with the HTTP server.

It should but sometime network environment could manage TCP and UDP a bit differently and so you could face some issue.
Did you try to see if traffic goes to your dev machine using something like wireshark/tcpdump ?

Thanks for the advice to use Wireshark. I found out that the packets were forwarded to the wrong destination port.
I fixed that, now the registration works.
Thanks for your help, Simon :)

You're welcome. So I guess we can close this issue ?


Fix default value of keyword parameter saveat

Checklist
Thank you for contributing to QuantumToolbox.jl! Please make sure you have finished the following tasks before opening the PR.

[x] Please read Contributor Covenant Code of Conduct
[x] Any code changes were done in a way that does not break public API
[x] Appropriate tests were added and tested locally by running: make test.
[x] Any code changes should be julia formatted by running: make format.
[x] All documents (in docs/ folder) related to code changes were updated and able to build locally by running make docs.

Request for a review after you have completed all the tasks. If you have not finished them all, you can also open a Draft Pull Request to let the others know this on-going work.
Description
The original default value of saveat is given by
saveat = e_ops isa Nothing ? t_l : [t_l[end]]

This causes ambiguity when user specify e_ops = [], because:
[] isa Nothing # false

Therefore, I change it to
saveat = is_empty_e_ops ? t_l : [t_l[end]]

where is_empty_e_ops is pre-defined as
is_empty_e_ops = isempty(e_ops)

and this works becasue
isempty([]) # ture
isempty(nothing) # true

Oh, wait, the code quality failed

But it failed for other reasons. Strange.

Ok, it is a problem related to the new release of Julia v1.11.0. Let's merge it


'7-Zip Not Installed' error

Can't open CBZ or CBR files, even though I have 7-Zip installed...? Why?

Never mind, turned out I just had to place 7zips.exe file into the directory of KCC

or put 7-zip's path into your path environnement variable


Key ( c ) is not showing while typing

In VS CODE , key ( C ) is not a command . the key combination , searching for chords etc are cames while typing letter "c" plz help me soon i am unable to solve any code here

i have see that but that was useless plz any other setting from which i may chnge ans type c

Sounds like you have a bad keybinding. Please follow the advice at https://github.com/microsoft/vscode/wiki/Keybinding-Issues


How do you specify which panel the file is opened in - confusing and not functional

Current behavior is to rotate, i.e. first file in left panel, second in right, third in left and so on IF you use the "view" context menu item (note that the file is editable as well as viewable).
But if you use the "Edit" menubar item the file is always opened in left panel.
Suggest we use "edit" for writable files and "view" for read-only and have edit-left and edit-right or something like that in context menu and double-click for left and alt/option double-click for right or something like that from context menu. For edit menubar item option when selecting would also open file into right window.

For non-emacs users :)

Suggest for "Find" (which by the way works wonderfully!) that displaying of found items (by clicking on link) always open the file in the right side textview if two are open. The use case that comes to mind is having code I'm editing in the left view and using the right view to find something relevant that I need for the code I'm editing.

I personally like the current behavior.  If I'm "browsing" in the file browser, and I double-click there, I want to "add" a new edit to whatever I already have -- my focus is not so clearly on the current active view.
If however I use Edit toolbar or Ctrl-X b, then my focus is more on active view, and it opens there (note: it is now much clearer which is active, and it always opens in active, not left).
I like the further suggestion that all links should open in right edit (if it isn't collapsed).  I'll do that.

Ok! Now that I understand it I like it :)
Yes the active view is now MUCH clearer!


Large subdomain names are failing

It seems there is an upper limit on the size of the subdomain one can create. Create shorter subdomains using branch-${branchname}-hash or deployment-${PR-Number}-hash for URLs.

https://stackoverflow.com/questions/10552665/names-and-maximum-lengths-of-the-parts-of-a-url


 Admittedly the commit message here is somewhat deliberately misformatted - I would need to do a bit more investigation to see exactly what formatting causes this.
brendand@brendand-T450:~/dvol-test$ dvol commit --message="clean stateDF"R$£":R£$F:$£F£:"
59c9f06ad0a54613a72a42d15e29d32e1ef9ac3e
brendand@brendand-T450:~/dvol-test$ dvol log
Unhandled Error
Traceback (most recent call last):
  File "/usr/local/bin/dvol", line 9, in <module>
    load_entry_point('dvol==0.1', 'console_scripts', 'dvol')()
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 629, in main

  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/internet/task.py", line 882, in react
    finished = main(_reactor, *argv)
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 605, in _main

--- <exception caught here> ---
  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 150, in maybeDeferred
    result = f(*args, **kw)
  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/python/usage.py", line 277, in parseOptions
    self.postOptions()
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 598, in postOptions

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 425, in run

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 330, in listCommits

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 101, in output

exceptions.UnicodeEncodeError: 'ascii' codec can't encode character u'\xa3' in position 118: ordinal not in range(128)

brendand@brendand-T450:~/dvol-test$ dvol ls
  VOLUME   BRANCH   CONTAINERS
* moby     master   /dvoltest_redis_1
brendand@brendand-T450:~/dvol-test$ dvol log
Unhandled Error
Traceback (most recent call last):
  File "/usr/local/bin/dvol", line 9, in <module>
    load_entry_point('dvol==0.1', 'console_scripts', 'dvol')()
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 629, in main

  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/internet/task.py", line 882, in react
    finished = main(_reactor, *argv)
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 605, in _main

--- <exception caught here> ---
  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/internet/defer.py", line 150, in maybeDeferred
    result = f(*args, **kw)
  File "/usr/local/lib/python2.7/dist-packages/Twisted-15.5.0-py2.7-linux-x86_64.egg/twisted/python/usage.py", line 277, in parseOptions
    self.postOptions()
  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 598, in postOptions

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 425, in run

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 330, in listCommits

  File "build/bdist.linux-x86_64/egg/dvol/dvol.py", line 101, in output

exceptions.UnicodeEncodeError: 'ascii' codec can't encode character u'\xa3' in position 118: ordinal not in range(128)

Update: I can reproduce this now with as simple a message as:
dvol commit -m "Clean state worth £30"


Chore: Add tool to crawl multiple sites with sonar

Fix #525
@alrra will be nice to get this into Travis and run it periodically somehow. If we end up doing that, we probably want to know how many cores and adapt the number of workers on that (10 might be a bit too much for Travis). It runs a bit slow, so we probably want to trim down the list.
Ideally, this script should be used as followed (from Windows) node crawler.js urls.txt 2>>errors.txt
I can also look into adding the errors directly into a file if we think it makes more sense.
Another option to not pollute the output will be to support not having a formatter or maybe a noop formatter. Don't have any strong opinion about this.

It runs a bit slow, so we probably want to trim down the list.

Yes, Travis CI has time limits.

I can also look into adding the errors directly into a file if we think it makes more sense.

For the Travis scenario, we should make @NellieTheNarwhal open an issue if sonar breaks.

For the Travis scenario, we should make @NellieTheNarwhal open an issue if sonar breaks.

Right now it will not break, I process all the URLs no matter what the result is. I should update the exit code then. Is there an easy way to open the issues?
Probably this should be run every time we do a new release and in the same process do a npm install to make sure there isn't any problem during the installation?

@alrra @sarvaje PR updated and ready for another review.

Closing this in favor of https://github.com/sonarwhal/sonar-tools/pull/5


Updated follow TF to include Map

Summary
When I was viewing bags, I couldn't see the bags in the map frame. I was looking through the functions and I found a bug in the getDescendants function. It was ignoring the possibility of viewing the bag in the rootTransformFrame

Test plan
Tested the function using npm run docs with and without bag files. This always traverses down the tree producing the list expected including the root TF
Versioning impact
Not as far as I know

This makes sense to me. Can you think of any reason not to do this @jtbandes or @brianc?

I think the original idea was that "viewing the bag in the rootTransformFrame" is the same as "not following anything". When the button is off, that should mean the root frame is being used as the camera's origin. But maybe we should show it in the list anyway to make that more obvious?

I do wonder, in this screenshot, there are multiple root frames, in which case it does seem useful to have them in the list. Because I think we don't just use this for following, but also for rendering, but I might be mistaken.

I believe in the screenshot the robot was mislocalized at the start of the bag. So there was no association of the /odom frame with the /map frame which causes the two roots (solid I think on that one, I could go back and double check)

@janpaul123 in other news could you help me with the CI ? Is it flaky?
It currently says:
Too long with no output (exceeded 10m0s): context deadline exceeded

But I don't think anything in this PR could have caused that. Or am I reading it wrong?

Yeah it's a bit flakey since the free circleci machines are very slow. 😬 I'll take a look at this today. 👍

This PR broke the tree representation a bit, but in the end the proper fixed turned out to be really simple, and I included it here: https://github.com/cruise-automation/webviz/pull/313/files#diff-b9112208bba7b2f237d9ef5fcedff919 This should get deployed onto webviz.io in an hour or so. Thanks for your contribution!!

Yep that fix looks perfect. Thanks for the merge


Multi-index key name not meet constraints

https://github.com/EOSIO/eos/blob/11c25394b6dd05cc3c97f0b7471a84f3d7cfbca3/contracts/eosio.msig/eosio.msig.abi#L140
Is it allowed to have multi-index key name that not meet base32 constraints?

The key_names and key_types fields of the ABI do not do anything and are remnants of an old ABI spec that unfortunately were not pruned prior to 1.0 release. They should be ignored (and preferably left empty).

Also, most of the contracts in contracts folder of the eos repository are old and not maintained. Check out the eosio.contract repository for the most recent versions of the eosio.bios, eosio.system, eosio.msig, eosio.token, and eosio.wrap (formerly known as eosio.sudo) contracts.


Correct port is not being opened

Type: Bug Report
Describe the bug

OS: Windows 10 Enterprise
VS Code Version: 1.78.2
Serial Monitor Extension Version: v0.9.230531001

The selected COM port in the Port drop down is not being opened.
To Reproduce
Steps to reproduce the behavior:

Have serial monitor open
See a COM port in the Port select dropdown
Connect a new USB device to the PC
Refresh the COM ports
Select the newly found COM port
Click start monitoring
See it opens the serial port originally seen in the port select dropdown and not the newly selected com port

Work arounds:

If I close and reopen VSCode and then try to connect to the new comport (without disconnecting the USB device) it then opens the correct COM port.
If I press start monitoring on the old com port, then select the new com port in the drop down then press start monitoring. It opens the new COM port correctly

Expected behavior

Serial monitor correctly connects to the selected COM port

Screenshots

Without new com port:

New usb device connected, port dropdown refreshed and new com port selected

Old com port in view is opened after pressing the start monitoring button and not the selected one:

Additional context
Where I say to connect a new USB device I am using virtualHere to select a com port to open.

@rossb93 I attempted to reproduce this issue and was not able to. Could you provide some more information about what your steps were?
Did you hit refresh, then select the new port, and then try to start monitoring? Was a new port automatically selected when you pressed refresh? Any information, or even better, a gif/video of the bug being reproduced, would be fantastic!
Thanks!

I find this issue is intermittent so not so easy to reproduce. Next time I see an occurrence of it I will try to screen record the repro steps.
As for your questions on my above repro steps:
Did you hit refresh, then select the new port, and then try to start monitoring?
Yes the steps were hit refresh, select the new port, and then select Start Monitoring. At which point it opens a connection with the previously selected COM port instead of the newly selected one
Was a new port automatically selected when you pressed refresh?
No the new port wasn't automatically selected, since the previous port still exists that port remained selected. It was only following a refresh and manually selecting the new port from the dropdown that the new port became selected

I still keep seeing this bug. I can't think of a way to record/gif the bug, but the screenshots above show (specifically screenshot 3) that after pressing Start Monitoring on the selected COM port it opens the serial port for a different COM port that the one selected in the dropdown (opens COM9 instead of COM13). I'm surprised no one else has encountered this bug

i get the same message on ubuntu 23.04 (Jammy Jellyfish) and vscode 1.81.1 and arduino v0.6.0

@Ahmed1893 I think your screenshot may be a different issue. Do you have file logging enabled? I've hit this where I had file logging enabled and the directory I wanted to log to no longer exists on my system and it causes issues opening the port, because it fails to open the file. Could this be your situation?

@Ahmed1893 I just attempted to repro your original issue, and it doesn't seem to reproduce, could you confirm?
Thanks.


MediaMetaData returns null values if player is set to Player.REPEAT_MODE_ONE (Same as Legacy issue #9458 at ExoPlayer repository)

Version
Media3 1.2.1
More version details
No response
Devices that reproduce the issue
AVD Pixel 8 Pro API 34
AVD Pixel 8 Pro API 33
AVD Pixel 3a API 28
Galaxy A50 with Android 11
Devices that do not reproduce the issue
No response
Reproducible in the demo app?
Yes
Reproduction steps

Open PlayerActivity at androidx/media3/demo/main/PlayerActivity.java
Add player.setRepeatMode(Player.REPEAT_MODE_ONE);  after player = playerBuilder.build(); at line 279
Build and run the demo app
Go down to Misc list
Press Google Play (MP3) to play
Seek the seek-bar to the almost end of it ( for example at the 00:56 )
Let the playback continue to end the current item and then repeat the playback.

Expected result
The artwork picture of the item remains the same.
Actual result
The artwork disappears. As I inspected in debug mode, all metadata values but the title are null in the second playback.
Media
https://github.com/androidx/media/assets/76568952/810032e7-74da-4e21-85ec-17250fb41191
Bug Report

[X] You will email the zip file produced by adb bugreport to<EMAIL_ADDRESS>after filing this issue.

Thanks for reporting! We'll fix that (again) for the upcoming 1.3.0 release.


Limit maximum number of jobs

Scrapyd has configuration options jobs_to_keep and finished_to_keep.
It would be good to have both. Containers (Docker) / jobs (Kubernetes) can be removed when it is time according to these options.
For Kubernetes, one could alternatively use a max lifetime (which is possible to set on jobs). But let's start with the two above.

This issue is blocked by https://github.com/q-m/scrapyd-k8s/issues/11 as we need to sort by end_time before cutting off the amount of finished jobs with finished_to_keep


Better auto-indent for TextMate grammars

Description of the Change
Makes auto-indent skip over lines that start with a comment, so they do not interfere.
Alternate Designs
I considered going through the tags of each line manually, which would allow better handling of the following:
stuff
           /* comment */ if (true) {
}          }
|          ^ we technically want it here
^ it will actually go here

This happens because the line we wanted to align with starts with a comment, so we skip over it with the current implementation. However, checking tokens would be a lot more work, and we don't get the caching for free like we do with isCommented(). Plus, Tree-sitter can give us the corresponding line directly, so this is only needed while TextMate grammars are still widely used.
Why Should This Be In Core?
Is core mechanic
Benefits
Fixes bad auto-indenting with things like
class MyClass {
    public void myMethod() {
        if (true) {

        // A comment <- originally used as line to align with; now ignored
        } else if (/* type something here */) {

        }
    }
}

Possible Drawbacks
The check is slightly slower when many comments are present, but only for the very first run. Subsequent runs cache whether lines are commented, so performance is nearly identical to the original. (benchmarks to be added)
Verification Process
Manually (tests to be added?) with above example code, and file with 10 000 consecutive comment lines above an auto-indenting line.
Applicable Issues
Fixes #17364

The last commit puts the changes in a single method, which is then used in the original location & in the other autoindent place. This means the fix also applies to Editor: Auto Indent.
On a different note, how does one write benchmarks 😢?

On a different note, how does one write benchmarks?

The PR that added benchmarks has some details that might help get you started https://github.com/atom/atom/pull/12984

Well, that was my attempt at a benchmark. It seems that earlier rounds are interferring with later ones, so I iterate backwards (most comments are tested first). I only test block comments here, inside of 12 nested switch statements, because checking for specific open scopes when there are many is the most likely performance cost (switch statements were chosen because their contents are scoped).
Checking if it's a line comment is comparatively much faster, because we only look at the first one or two elements in the tokenised line tags.

Turns out this breaks Tree-Sitter grammars. They currently just copy indent rules from TextMate for now, so I don't think this can be merged until that's sorted.

It looks like you'd need to add your new method getPrecedingIndentRow to this list of methods to copy. You'd also need to avoid using tokenizedLineForRow, since that's a textmate-specific API. Fortunately, I think you could just replace this:
tokenizedLine = this.tokenizedLineForRow(activeRow)
if (!tokenizedLine.isComment() && /\S/.test(tokenizedLine.text)) {
  // ...
}

with this:
if (!this.isRowCommented(bufferRow) && !this.buffer.isRowBlank(bufferRow)) {
  // ...
}

It might be worth running your benchmark with Tree-sitter enabled to make sure everything's ok performance-wise.

Good job

Update: Tree-sitter leads to very poor performance here. I revised it to use the more 'sophisticated' behaviour for the first 1000 lines, but revert to the original if that is exceeded. This will cover 99% of reasonable use cases, including the original issue. 1000 is arbitrary, but felt smooth enough when testing with > 1000 lines of 50 spaces above the search start.
Tangentially; maybe we should consider restricting indentation checks to special characters? It currently uses a regex, but that regex is for the whole line. This would be in addition / an alternative to that, up to where the cursor is. E.g. \s*}$ would match if the cursor just typed a } at the start of the line. This would eliminate any lag entirely while typing on the rest of the line AND prevent the jumping while typing that I'm not convinced isn't a bug itself.
I also deleted my original fork with these changes, so I'll be submitting to a new PR. Or, renaming the branch works too.

Thanks very much for reaching out!
As you may have heard, we are migrating from our old first-mate grammar engine to the new Tree-sitter engine. This will enable a number of new features, more consistent syntax highlighting, and better performance, among other benefits. In order to free up our limited resources, we have decided to stop maintaining the first-mate grammar when there is a built-in Tree-sitter grammar available. Since this issue applies only to the first-mate grammar, we are going to close it. Please let us know if we have misunderstood the description of the problem.
We are also planning to leverage tree-sitter for indentation. See https://github.com/atom/atom/pull/18321
Thanks again for your interest in Atom.


Base TODO list

[x] Simple viewer
[x] Controls
[x] GUI
[x] Camera
[x] Animations
[x] Appear / Disappear / Eaten animations
[x] Score
[x] Deadzone
[x] Place the bigger cells on top

[x] client.on.ballResize
[x] client.on.ballAppear
[x] Only those needed (over size wanted)

[x] Text

[x] Name
[x] My mass
[ ] ball.isPlayer
[ ] Others mass

[ ] Display controller
[ ] Graphical enhancements

[ ] White background
[ ] Grid
[ ] Virus styling

[ ] Preferences saving
[ ] Better scale calculation
[ ] Server acting as relay
[ ] Desktop app
[x] package.json
[x] Gulp/Grunt

[x] Browserify
[x] Bower

[x] Only one .js file (use source maps)
[ ] Correct disconnecting / reconnecting

I am wondering if you are still developing this because I am interested in it but it does not seem to draw the cells correctly at the moment.

I'm not currently developping this since currently this was for fun and nodejs practice, but feel free to enhance it :)
I'll probably see if I can fix the game quickly, no promise though.

It seems vndot will fix this for you! :D

VNDOT Plus is now replaced by NEXT


[Feature Request]: Adding all searching snippets

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
adding python snippets of searching algorithms
Record

[X] I agree to follow this project's Code of Conduct
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

Full Name
Mahathi N
Participant Role
GSSOC, Hacktoberfest

@UTSAVS26 Can you please look into this


HDDS-9823. Pipeline failure should trigger heartbeat immediately

What changes were proposed in this pull request?
XceiverServerRatis#handlePipelineFailure is called in CSM failure scenarios

XceiverServerRatis#handleNodeSlowness

From StateMachine#notifyFollowerSlowness
Set to hdds.ratis.rpc.slowness.timeout (default value 300s)

Note: Ratis default value is 60s

XceiverServerRatis#handleNoLeader

From StateMachine#notifyExtendedNoLeader
Set to hdds.ratis.notification.no-leader.timeout (default value 300s)

Note: Ratis default value is 60s

XceiverServerRatis#handleInstallSnapshotFromLeader

From StateMachine#notifyInstallSnapshotFromLeader

Currently, XceiverServerRatis#handlePipelineFailure does not trigger Heartbeat to SCM immediately. Instead, it waits until the next heartbeat (default 60s) to send the pipeline close action command. This might cause SCM to still allocate blocks to these "failed" pipelines during this duration which might impact on client writing to these blocks.
To minimize the impact on the client and the datanodes on the failed pipeline. I suggest that the datanode trigger the pipeline close command immediately for every pipeline action close command triggered due to pipeline failure.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-9823
How was this patch tested?
Existing tests.
Clean CI run: https://github.com/ivandika3/ozone/actions/runs/7084351468

@SaketaChalamchala can you please take a look?

@DaveTeng0 can you please take a look?

Thanks @ivandika3 for the patch, @sumitagrawl for the review.


Default to ssh-ng and and builders-use-substituters

Ah right, I forgot that ssh-ng still has a few unsolved complexities in relation to other flags, as described for example in https://github.com/NixOS/nix/pull/5010

@

@phaer any chance you'd want to make it an opt-in feature for now?

Still working on this?

Ah no, sorry for leaving this as a draft for so long & thanks for going through stalled PRs :) . I don't plan to set up too many new hosts and don't currently have time for it.


METRON-624: Updated Comparison/Equality Evaluations in Stellar

General cleanup in Stellar.g4

Refactored the grammar to consistently use fragments instead of inlining things.

Updated the way Stellar transformations were validated

Previously Stellar parsed/evaluated the transformation to validate it. In certain circumstances this would cause failures. For instances, all variables would be resolved to null which would cause an error to be thrown when evaluating transformations such as: '1 < foo', '1 < null'. Both of these statements are syntactically valid.
Now the validation just checks whether the Stellar transformation is syntactically valid. It will not send the transformation through the listener as it once did. It will not validate that variables are defined. It will not validate functions are defined.

Updated comparison/equality expression evaluation

Number 2 was required in order to update the comparison/equality evaluation.
Now statements such as 1 == '1' will return false.
When comparing numerical values, the standard promotion rules apply (http://docs.oracle.com/javase/specs/jls/se8/html/jls-5.html#jls-5.6.2).
When comparing non-numeric types, compareTo method is used.
When either side is null then '==' and '!=' are used. For all other comparison operators null value would throw exception.

Hey, thanks for the great addition @jjmeyer0!
A few things to note and some context.
Around validation, the initial stellar implementation purposefully ran validation the way that it's implemented, but we can reconsider those things if we want.

The variables resolve to null to ensure that functions could handle null without error.  I understand that Java and most programming languages would NPE on 1 < null, but our data flowing through the topologies will be sparse, so not all variables will be defined for every message.  If a stellar statement is applied to a message where the variable is not defined, I wanted to ensure that it did not fail, but rather did an appropriate thing depending on the operation.
We do function resolution during validation to ensure people have not made a syntactic error in their stellar statements when pushing configs to zookeeper.  We would rather fail fast here.

Around == for floating point numbers.  The initial stellar implementation intended to do an epsilon check on equals involving doubles (e.g. Math.abs(lhs - rhs) < epsilon) as you almost never want strict equality in floating point numbers.
What this does show is that we need more of a rigorous spec and more time spent on documenting the design of Stellar.

One further thought: regarding the validation, I just want to point out that I'd be ok for validation to not execute the statement, but only validate syntactic correctness and function existence.  It just means that we will need to augment StellarProcessorUtils to execute with a map that returns null for its variables to ensure our tests continue to cover the same way.
I do think we should retain the functionality that comparisons involving nulls operate in a sensible way.  I think any comparison involving null should return false sort of like how doubles function with NaN.  Also, the decisions made here should be included in the stellar section of the README.md as part of this PR.
I'm coming around about == operating strictly for doubles.  I could see how that would violate the principle of least surprise for people coming from other languages.  I guess I never had much use for == with doubles and thought I could automatically save people some obvious errors, but I think the current approach is problematic and probably should be scrapped for what this PR does.

@cestella I updated the comparison expressions to return false when either side is null. I'll work on the validation stuff soon.

@cestella if comparing floats/doubles is going to be a common thing maybe we should provide a way to do so easily. Maybe we create functions FLOAT_EQUALS(f1, f2, epsilon) and DOUBLE_EQUALS(d1, d2, epsilon).

@jjmeyer0 Yeah, I tend to agree.  I'll make a follow-on JIRA to add an APPROX_EQUALS.  I feel better about it now that we have an ABS function.

Yeah, this is good work.  I looked at it again after my vacation and I like it.  I give it a +1.

Thanks @cestella. I appreciate it. If no one has already, I'll work on those functions we discussed next.


FP16=0 not working for me

I successfully created the container as the default docker run... command but when I tried setting it up again using the FP16=0 part I get an error "docker: invalid reference format: repository name must be lowercase.".
perhaps I am misunderstanding how to use the variable as I am just getting started with containers in general....
here is my command: docker run --name stablediffusion --gpus all -it -e FP16=0 TOKEN=mytokenhere -p 7860:7860 nicklucche/stable-diffusion
I also tried adding the variable with quotes but it didn¨t work.. any suggestions? (I have a12 GB GPU)

Hi, you need to prepend each environment variable you set with -e, here we're setting two of them so this should be
docker run --name stablediffusion --gpus all -it -e FP16=0 -e TOKEN=mytokenhere -p 7860:7860 nicklucche/stable-diffusion
(notice the -e before the TOKEN variable).
Let me know if that works for you

Hi! Oh yes, that worked. Thanks!


Analyzer: Cannot find definition of new typedef

Reproduction case at dev-6.0:
import 'dart:async';

typedef _RunGuarded = T Function<T>(
  T Function(), {
  void Function(Object, StackTrace) onError,
});

main() {
  _RunGuarded runGuarded = runZoned;
  return runGuarded(() {

  }, onError: (error, trace) {

  });
}

Neither error or trace above have any (noticeable) types (both show up as dynamic on hover in IntelliJ), and I can't control-click on onError. That might be intended, but it's confusing as I assumed it would take me to my typedef.
EDIT: Type inference seems to work, just not on the parameter location. I.e. if I reference trace in the function body, it has a type.

It isn't intentional. It's probably another symptom of having incomplete support for the generic function type syntax.

I haven't seen this in a while


Mitogen fail to run playbook without “/usr/bin/python” on target host

Python 3.7.0
ansible==2.8.6
mitogen==0.2.9
target is Ubuntu 16.04 LTS on AWS

ansible-playbook 2.8.6
  config file = /Users/xxx/Documents/TestCode/ansible.cfg
  configured module search path = ['/Users/xxx/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /Users/xxx/Documents/TestCode/venv/lib/python3.7/site-packages/ansible
  executable location = /Users/xxx/Documents/TestCodeCode/venv/bin/ansible-playbook
  python version = 3.7.0 (default, Aug 22 2018, 15:22:33) [Clang 9.1.0 (clang-9<IP_ADDRESS>)]
Using /Users/xxx/Documents/TestCode/ansible.cfg as config file
host_list declined parsing /Users/xxx/Documents/TestCode/hosts as it did not pass it's verify_file() method
script declined parsing /Users/xxx/Documents/TestCode/hosts as it did not pass it's verify_file() method
auto declined parsing /Users/xxx/Documents/TestCode/hosts as it did not pass it's verify_file() method
Parsed /Users/xxx/Documents/TestCode/hosts inventory source with ini plugin

PLAYBOOK: playbook.yml ***************************************************************************************************************************************************************************************************
1 plays in playbook.yml

PLAY [test] **************************************************************************************************************************************************************************************************************
[top  90289] 14:05:42.544910 D ansible_mitogen.process: inherited open file limits: soft=12800 hard=(infinity)
[top  90289] 14:05:42.545244 D ansible_mitogen.process: could not raise soft open file limit from 12800 to 524288: current limit exceeds maximum limit
[top  90289] 14:05:42.545495 D ansible_mitogen.process: raised soft open file limit from 12800 to 10240
[mux  90293] 14:05:42.565143 D mitogen.service: Pool(e7f0, size=32, th='MainThread'): initialized
[mux  90293] 14:05:42.570270 D ansible_mitogen.process: Service pool configured: size=32
META: ran handlers

TASK [shell] *************************************************************************************************************************************************************************************************************
task path: /Users/xxx/Documents/TestCode/playbook.yml:7
[task 90294] 14:05:42.732986 D ansible_mitogen.process: will use multiplexer 0 (/var/folders/qp/hf3ywx_n19b_jkf7fl9nmr1c0000gn/T/mitogen_unix_atnmhqow.sock) to connect to "a6"
[task 90294] 14:05:42.734415 D mitogen.unix: client: connecting to /var/folders/qp/hf3ywx_n19b_jkf7fl9nmr1c0000gn/T/mitogen_unix_atnmhqow.sock
[mux  90293] 14:05:42.735729 D mitogen.unix: listener: accepted connection from PID 90294: unix_client.90294
[task 90294] 14:05:42.735577 D mitogen.unix: client: local ID is 1, remote is 0
[mux  90293] 14:05:42.742126 D mitogen.parent: creating connection to context 2 using mitogen.ssh
[mux  90293] 14:05:42.988448 D mitogen.parent: command line for Connection(None): ssh -o "LogLevel ERROR" -l ubuntu -i /Users/xxx/.ssh/awsalan2.pem -o "Compression yes" -o "ServerAliveInterval 30" -o "ServerAliveCountMax 10" -o "BatchMode yes" -o "StrictHostKeyChecking no" -o "UserKnownHostsFile /dev/null" -o "GlobalKnownHostsFile /dev/null" -C -o ServerAliveInterval=60 -o ControlMaster=auto -o ControlPersist=300s -o UserKnownHostsFile=/dev/null <IP_ADDRESS> /usr/bin/python -c "'import codecs,os,sys;_=codecs.decode;exec(_(_(\”………………….\”.encode(),\"base64\"),\"zip\"))'"
[mux  90293] 14:05:42.998068 D mitogen.parent: child for Connection(None) started: pid:90295 stdin:119 stdout:119 stderr:121
[mux  90293] 14:05:43.757762 D mitogen.parent: ssh.<IP_ADDRESS>: (unrecognized): bash: /usr/bin/python: No such file or directory
[mux  90293] 14:05:43.759572 D mitogen: <Side of ssh.<IP_ADDRESS> fd 121>: empty read, disconnecting
[mux  90293] 14:05:43.760733 D mitogen: SetupProtocol(ssh.<IP_ADDRESS>): disconnecting
[mux  90293] 14:05:43.761573 D mitogen: <Side of ssh.<IP_ADDRESS> fd 119>: empty read, disconnecting
[mux  90293] 14:05:43.762319 D mitogen.parent: failing connection ssh.<IP_ADDRESS> due to EofError('EOF on stream; last 100 lines received:\nbash: /usr/bin/python: No such file or directory')
[mux  90293] 14:05:43.763103 D mitogen.parent: PopenProcess ssh.<IP_ADDRESS> pid 90295: exited with return code 127
[mux  90293] 14:05:43.763859 D mitogen: BootstrapProtocol(ssh.<IP_ADDRESS>): disconnecting
[mux  90293] 14:05:43.764943 D mitogen: BootstrapProtocol(ssh.<IP_ADDRESS>): disconnecting
[task 90294] 14:05:43.767791 D mitogen: MitogenProtocol(unix_listener.90293): disconnecting
[task 90294] 14:05:43.769088 D mitogen: Waker(fd=55/56): disconnecting
[task 90294] 14:05:43.770311 D mitogen: Router(Broker(6eb8)): stats: 0 module requests in 0 ms, 0 sent (0 ms minify time), 0 negative responses. Sent 0.0 kb total, 0.0 kb avg.
[mux  90293] 14:05:43.771226 D mitogen: <Side of unix_client.90294 fd 118>: empty read, disconnecting
[mux  90293] 14:05:43.772303 D mitogen: MitogenProtocol(unix_client.90294): disconnecting
fatal: [a6]: UNREACHABLE! => {
    "changed": false,
    "msg": "EOF on stream; last 100 lines received:\nbash: /usr/bin/python: No such file or directory",
    "unreachable": true
}

Running playbook without mitogen, Ansible sets ‘interpreter_python’ as "/usr/bin/python3" automatically
changed: [a6] => {
    "ansible_facts": {
        "discovered_interpreter_python": "/usr/bin/python3"
    },
    "changed": true,
    "cmd": "df",
    "delta": "0:00:00.002836",
    "end": "2019-12-17 06:29:16.122794",
    "invocation": {
        "module_args": {
            "_raw_params": "df",
            "_uses_shell": true,
            "argv": null,
            "chdir": null,
            "creates": null,
            "executable": null,
            "removes": null,
            "stdin": null,
            "stdin_add_newline": true,
            "strip_empty_ends": true,
            "warn": true
        }
    },
    "rc": 0,
    "start": "2019-12-17 06:29:16.119958",
    "stderr": "",
    "stderr_lines": [],
    "stdout": “…….”,
    "stdout_lines": [
        ………
    ]
}

ansible-config is as below
ANSIBLE_PIPELINING(/Users/xxx/Documents/TestCode/ansible.cfg) = True
ANSIBLE_SSH_ARGS(/Users/xxx/Documents/TestCode/ansible.cfg) = -C -o ServerAliveInterval=60 -o ControlMaster=auto -o ControlPersist=300s -o UserKnownHostsFile=/dev/null
ANSIBLE_SSH_RETRIES(/Users/xxx/Documents/TestCode/ansible.cfg) = 2
DEFAULT_GATHER_TIMEOUT(/Users/xxx/Documents/TestCode/ansible.cfg) = 10
DEFAULT_LOG_PATH(/Users/xxx/Documents/TestCode/ansible.cfg) = /tmp/ansible.log
DEFAULT_TIMEOUT(/Users/xxx/Documents/TestCode/ansible.cfg) = 60
DEPRECATION_WARNINGS(/Users/xxx/Documents/TestCode/ansible.cfg) = False
HOST_KEY_CHECKING(/Users/xxx/Documents/TestCode/ansible.cfg) = False
PERSISTENT_CONNECT_TIMEOUT(/Users/xxx/Documents/TestCode/ansible.cfg) = 300

Please give this another shot @Ansen04 ; #658 was just merged

@s1113950 Do you think the fixing contains in 0.2.9? I have python3 installed on my VPS but facing a similar error

The fix is not in 0.2.9 @tom10271 . There will be 1 or 2 Mitogen versions released very soon once https://github.com/dw/mitogen/pull/715 lands though, which will contain the fix. In the meantime, you can do what you noted here: https://github.com/dw/mitogen/pull/658#issuecomment-724609344 and get the fix :)


Troubles running "with-typescript" example

Hi!
I'm trying to start razzle "with-typescript" example, and its not working. I've got a bunch of TS errors, here is some of them:
/mnt/c/Files/WSL/www/razzle-ts/node_modules/<EMAIL_ADDRESS>/mnt/c/Files/WSL/www/razzle-ts/node_modules/@types/react-dom/node_modules/@types/react/index.d.ts(3635,13): error TS2403: Subsequent variable
declarations must have the same type.  Variable 'use' must be of type 'SVGProps<SVGUseElement>', but here has type 'SVGProps<SVGUseElement>'.

 ERROR  Failed to compile CLIENT with 173 errors

/mnt/c/Files/WSL/www/razzle-ts/node_modules/<EMAIL_ADDRESS>/mnt/c/Files/WSL/www/razzle-ts/node_modules/@types/react-dom/node_modules/@types/react/index.d.ts(3636,13): error TS2403: Subsequent variable
declarations must have the same type.  Variable 'view' must be of type 'SVGProps<SVGViewElement>', but here has type 'SVGProps<SVGViewElement$
'.

 ERROR  Failed to compile CLIENT with 173 errors

<EMAIL_ADDRESS>/mnt/c/Files/WSL/www/razzle-ts/node_modules/@types/react/index.d.ts(3407,19): error TS2320: Interface 'Element' cannot simultaneously extend $
ypes 'ReactElement<any>' and 'ReactElement<any>'.
  Named property 'type' of types 'ReactElement<any>' and 'ReactElement<any>' are not identical.

 ERROR  Failed to compile CLIENT with 173 errors

<EMAIL_ADDRESS>/mnt/c/Files/WSL/www/razzle-ts/node_modules/@types/react/index.d.ts(3408,19): error TS2320: Interface 'ElementClass' cannot simultaneously ex$
end types 'Component<any, {}>' and 'Component<any, {}>'.
  Named property 'refs' of types 'Component<any, {}>' and 'Component<any, {}>' are not identical.

 ERROR  Failed to compile CLIENT with 173 errors

/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx
/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx(7,24): error TS2345: Argument of type 'string | undefined' is not assignable to parameter of ty$
e 'string'.
  Type 'undefined' is not assignable to type 'string'.

 ERROR  Failed to compile CLIENT with 173 errors

/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx
/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx(13,23): error TS2345: Argument of type 'string | undefined' is not assignable to parameter of t$
pe 'string'.
  Type 'undefined' is not assignable to type 'string'.

After yarn upgrade:

 ERROR  Failed to compile CLIENT with 2 errors

/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx
/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx(7,24): error TS2345: Argument of type 'string | undefined' is not assignable to parameter of type 'string'.
  Type 'undefined' is not assignable to type 'string'.

 ERROR  Failed to compile CLIENT with 2 errors

/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx
/mnt/c/Files/WSL/www/razzle-ts/src/server.tsx(13,23): error TS2345: Argument of type 'string | undefined' is not assignable to parameter of type 'string'.
  Type 'undefined' is not assignable to type 'string'.

OK, I've got the solution: "strictNullChecks": false in tsconfig.json.
Now application is running, but not everything works anyway - styles, for example.

Hmm I actually use Razzle with Typescript daily and am not seeing this problem.

@queses The error you mentioned would be expected if the as string was missing. Does your reference to the variable look like the following?
const assets = require(process.env.RAZZLE_ASSETS_MANIFEST as string);

I'm also running into an issue loading the SVG file from the default template when working with the TypeScript example. For some reason, the logo is undefined on both server and client and I can't see why. Compilation isn't a problem thanks to the importing other assets section of the Webpack docs, but I don't understand why the file isn't loaded.

In case anyone else happens to run into a problem loading an SVG or other type of asset while working with the TypeScript example, I was able to resolve my issue by setting "module": "esnext" in tsconfig.json.

good catch


Adding new Bengali strings

@Neilblaze Can you verify these 7 new strings from machine translation?
English version:
https://github.com/octave-online/oos-translations/commit/acd0cb75f8fc5cab3c2955e09becea4481e3fa2e
Thank you!

@Neilblaze Can you verify these 7 new strings from machine translation?
English version:
https://github.com/octave-online/oos-translations/commit/acd0cb75f8fc5cab3c2955e09becea4481e3fa2e
Thank you!


test(device_info_plus): Add Android display metrics check, fix Android version check

Description
After adding an Android build matrix saw that integration tests fail for device_info_plus on newly added Andoid APIs. As it turned out there was a hardcoded version of Android (30), which caused test to fail on all other versions.
Also, saw that same test was missing check for a newly added device metrics data, so added it as well.
Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I titled the PR using Conventional Commits.
[x] I did not modify the CHANGELOG.md nor the pubspec.yaml files.
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
[x] No, this is not a breaking change.

Test was still failing on API 21 because some properties are not available till API 23:
https://developer.android.com/reference/android/os/Build.VERSION#BASE_OS
https://developer.android.com/reference/android/os/Build.VERSION#PREVIEW_SDK_INT
https://developer.android.com/reference/android/os/Build.VERSION#SECURITY_PATCH
And the implementation had the check for API version, thus, returning null on lower versions:
https://github.com/fluttercommunity/plus_plugins/blob/main/packages/device_info_plus/device_info_plus/android/src/main/java/dev/fluttercommunity/plus/device_info/MethodCallHandlerImpl.java#L73
Fixed it as well.

Is it somewhere in our docs that they return null on lower versions?

Is it somewhere in our docs that they return null on lower versions?

No. we don't have it. I will create a separate PR as I see one more possible improvement for our docs on the website for this plugin.

If even we don't really know, we should put it in the docs of the methods that return null for specific versions.


Added CSV loader for trust ratings

PR Category: Feature
Added CSV loader for trust ratings

I think we need a high-level overview of the design of the trust functionality. A while ago we've employed a system of ADRs that are written in plain-text English. Any bigger functionality, like this one, should have its own ADR submitted first.

hey @sdavidp. if possible, please ammend the original commit (as you fix it in the same PR) and make yourself a coauthor

hey @sdavidp. if possible, please ammend the original commit (as you fix it in the same PR) and make yourself a coauthor. as long as it's possible, we want to have a single commit per single PR. (exception for this is when a separate commit provides a meaningful, separate change and cannot be made into PR separately)

The commits have been squashed and further cleaned up.

hey @sdavidp. if possible, please ammend the original commit (as you fix it in the same PR) and make yourself a coauthor. as long as it's possible, we want to have a single commit per single PR. (exception for this is when a separate commit provides a meaningful, separate change and cannot be made into PR separately)

@marcinwadon hey... @cngo-github  did tell me about doing single commits -- Chuong and I were pairing to resolve some issues and this push was so he could get the code to his machine. I'm sure he'll fix it up according to our standards.
Re. making me a coauthor, Chuong is already looking into that.
Thanks Marcin, I appreciate the detail-oriented approach to the codebase.

Added the code to integrate the CSV upload and parse with the CLI.


using @mixin for .sass file does not register indent

Does this issue occur when all extensions are disabled?: Yes/No
(Only with extensions due to sass compiler (converts sass to css), although should not effect error due to sass compiler extension not being involved with sass syntax)

VS Code Version: 1.73
OS Version: Windows 10 build 19044.2251

Steps to Reproduce:
1.- Create a sass file (foo.sass)
2.- create a mixin and set it to anything (ie: @mixin foo)
3.- hit enter (preferably what you would use to create a new line (ie: enter)
4.- results.
https://user-images.githubusercontent.com/83801755/201548210-ce096183-6190-45e5-bfac-e7847da9f1c6.mp4

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

Indented Sass support comes from an extension (there's only built-in support for SCSS).
Please file the issue against the extension.


Create python-app.yml

This workflow utilizes GitHub actions ecosystem and will run checks for:

any PR that will merge changes into master branch
After any push to master branch

To ensure future changes:

do not break stage of compiling python code to bytecode.
help catch any breaking changes specific to python verion(s)

Reference for CI checks: https://github.com/StephenGemin/facebook-wda/pull/1

the tests require local physical device which is unable to run in CI


Adding Priors

This pull request does the following

Add priors for match and gap scoring : this will handle some of the identifiability issues, while allowing some match scores to be negative (#66)
Add multihead attention layer : this is more or less a multilinear layer that imitates a Gaussian mixture model when generating the scoring matrices (#67)
Add gap masking : this will significantly reduce the memory burden from specifying which positions in the alignment matrix to mask(#63)

This also fixes #65

We're closing this PR, since it looks like a dead end.


Identify Charts that Need RBAC Enabled

what

Identify all charts that need RBAC enabled
Create issue in this repo and associate with PCI/Security project

why

PCI/Security compliance

@osterman
Or even better solution:
I can parametrize rbac based on global env KOPS_AUTHORIZATION_RBAC_ENABLED.
Something like that:
{{ coalesce (env "CHART_RBAC_ENABLED") (env "KOPS_AUTHORIZATION_RBAC_ENABLED") "false" }}

That's interesting - I'm not sure the best approach.
Keep in mind we would like most of these to work on EKS, GKE in addition to Kops.
My main concern is to reduce the size of the PR. So if we can do everything in one smallish PR, I'm okay with it.


Is it possible to test the configuration?

Is it possible to test the configuration without it actually does any thing?
Something like compile the script to check for errors and mabye also run it where results will be written to the terminal but the action will not be fully executed.

the terminal but the action will not be fully executed.

Which action are you referring to? All actions?
Sorry, that's not possible right now. I see a use case for just verifying that a Fastfile is valid, but executing fastlane in a read-only mode wouldn't work probably, as this would require all integrations to implement a read-only mode. Additionally, some actions depends on other action's results.

Yes all actions. But yes I understand that it is not an easy task to implement.

I'll close this issue for now, as it's not on my roadmap. Thanks for your feedback though.


Collection properties are overwritten by elements

Question
When using spring-cloud-starter-consul-config to load properties, the Collection properties are not loaded properly. It might be caused by some defects of PropertySourceBootstrapConfiguration and PropertySourceLocator,  as it only allows a single CompositePropertySource being created when loading from Locator, or I just had some misunderstanding.
Bug report
Spring Cloud version: 2.1.0.M2
Consul properties:
config/application/config.names[0] -> "application name 0"
config/application/config.names[1] -> "application name 1"
config/foo/config.names[0] -> "foo name 0"

bootstrap.properties:
spring.application.name=foo

Simplified domain class:
@ConfigurationProperties(prefix = "config")
public class TestProperties {
    private List<String> names;  // Getter/Setter omitted
}

After started, the TestProperties#getNames() returned [foo name 0, application name 1], shouldn't [foo name 0] be expected?
Enhancement
Collection properties field should overwrite the whole list instead of by elements.

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.


Revert "Ont 435 for case 0.2.1"

Reverts casework/CASE#54

@plbt5 and I tried out the Revert feature, and it generated this PR instead of doing what we thought it would do.  Closing this PR as inapplicable.


Add compression tests for kafka

Add compression tests for kafka. Now we support none,gzip,snappy,lz4,zstd four kinds of the compression algorithm. We should test it.

/label affects-6.1


Errors to compile with CUDA 12.1

This might or might not be an issue.
I had a problem trying to install this with the cuda 12 using the instruction
TORCH_CUDA_ARCH_LIST="7.5" python setup_cuda.py install

and I got the error describe https://github.com/qwopqwop200/GPTQ-for-LLaMa/issues/68 , However before I cross arround that issue I tried to install pytorch with cuda 12.1 support using
pip install --require-virtualenv --pre torch torchvision torchaudio --index-url https://download.pytorch.org/whl/nightly/cu121

And then tried to install with the setup_cuda.py but I ran into a lot of errors.
Granted the torch I have is a nightly build, there are still no stable torch with cuda12 support so it might be a problem with torch not being ready. However it could also be something that might need to be addressed in order to give support for cuda12.

It is possible to get it working with 12.1, unfortunately it's been a while so I don't remember all the details.
I did have to edit a system wide header file for a pybind11 error.
But 'a lot of errors.' isn't really descriptive :/

Thanks a lot, that helped.
just as a minor comment, if someone does not want to temper with system files, I am ussing a virtual environment, so the file I needed to change is venv/lib/python3.11/site-packages/torch/include/pybind11/cast.h and apply the change:
-    return caster.operator typename make_caster<T>::template cast_op_type<T>();
+    return caster;

At the end of the day I was correct it is not a GPTQ-for-LLaMa issue, it is a CUDA issue.


dashboard: remove /64 from IPv6 deployment result

Description
When one deploys via the dashboard and asks for a public IPv6, a /64 is added which brings confusion since it's not required to use the IP.

Implementation
Just remove the /64

verified on devnet
version : ac5cd85

https://app.testlodge.com/a/26076/projects/40893/suites/234374?expand_section=422333#case_4150332

Verified:

Devnet
d2d2622


Three minor patches

What type of PR is this?
/kind bug

What this PR does / why we need it:
See the commit messages for details, but tl;dr SPO didn't work well on
OpenShift.
Which issue(s) this PR fixes:
None

Does this PR have test?
None

Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

NONE

Codecov Report

Merging #433 (bd96862) into master (85a4b3c) will decrease coverage by 0.07%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #433      +/-   ##
==========================================
- Coverage   39.41%   39.33%   -0.08%
==========================================
  Files          22       22
  Lines         992      994       +2
==========================================
  Hits          391      391
- Misses        586      588       +2
  Partials       15       15

Umm, huh?
Error:      	"fatal error: runtime: cannot allocate memory

let me rebase and try again..

Umm, huh?

Hrnhghh.

I think tide merged in between two tests. There is a small gap between reporting dependent steps in GitHub actions.

On Thu, May 06, 2021 at 02:28:06AM -0700, Sascha Grunert wrote:

I think tide merged in between two tests. There is a small gap between reporting dependent steps in GitHub actions.

The test failed with "error: the server doesn't have a resource type
"spod"" which I think is not related to these patches..


Gemini captures incorrect area sometimes (but of the same size)

Hello, I have a strange problem with capturing my components: sometimes gemini saves screenshot with another part of a page, sometimes there is only a part of a desired component and often it's just a top of the page. But each time the size of screenshot is completely the same as the component I want to capture. And what's important - it occurs arbitrarily: this time failed that component on firefox, next time it's another component but in chrome, or in both browsers. So each test-launch fails for this reason on arbitrary components.
For example here are two failed cases:

Need to capture this component with image and caption, but instead it takes screenshot of the area above the picture, like it didn't scroll to the required position before capturing.

Here we need to capture the image with description inside of an article, but gemini just captured the top of the page with navigation.

Contents of .gemini.yml file:
rootUrl: http://....
gridUrl: http://....
compositeImage: true
screenshotsDir: 'screens/desktop'
windowSize: 1280x1024

system:
  projectRoot: ../phantomcss
  debug: false

browsers:
  chrome-latest:
    desiredCapabilities:
      browserName: chrome
  firefox-latest:
    desiredCapabilities:
      browserName: firefox
```yaml

I have a suspicion that this issue caused by the loaded ads: when ad appears - page expand, and content can move to a different position so Gemini captures incorrect area.

so you need to disable any ads for your page for testing

Yes, it's the same problem as https://github.com/gemini-testing/gemini/issues/594


Added new feature to export notes to CSV

Added a new feature to support exporting of notes to CSV in a similar format to Google Calendar's CSV import formatting.
Created CsvUtil class which handles writing to CSV file.
Changed some notes-related prefixes in CLISyntax class.
Changed TAB key behaviour in note add/edit window to add fixed width of four spaces instead.
Updated MESSAGE_USAGE for note edit command.
Changed some JavaDoc comments.
Fixed checkstyle errors in test codes for Note management features.

Resolves #180

Coverage decreased (-2.4%) to 65.258% when pulling 1289986f9901f4bdc7e6e4cb8292eb99f342d08d on jomcruz93:new-feature-export-csv into 8f248e78901d4a5f8454128865e0f45930fd38fb on CS2113-AY1819S1-T16-1:master.